B.2 XML schema for PNM
24.2593GPPPersonal Network Management (PNM)Release 17Stage 3TS
Table B.2-1 contains the XML schema definition for an XML document for the PN configuration and query over the Ut interface.
Table B.2-1: XML schema for PNM
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="uri:3gpp:pnm"
xmlns="uri:3gpp:pnm"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!– This import brings in the XML language attribute xml:lang–>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<!– The PNConfiguration element –>
<xs:element name="PNConfiguration" type="pnConfRequest"/>
<xs:element name="PNUEID" type="xs:anyURI"/>
<xs:element name="PNUEName" type="xs:string"/>
<!– The whole PNM PN-configuration specific data set –>
<xs:complexType name="pnConfRequest">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:choice>
<xs:element name="UERedirection" type="UERedirectionType"/>
<xs:element name="AccessControl" type="AccessControlType"/>
<xs:element name="NameofPNUE" type="PNUENameType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:anyAttribute namespace="##other" processContents="lax">
</xs:complexType>
<!– The UERedirection data set –>
<xs:complexType name="UERedirectionType">
<xs:sequence>
<xs:element name="RedirectedUserID" maxOccurs="1">
<xs:complexType>
<xs:sequence>
<xs:element ref="pnm:PNUEID"/>
<xs:element ref="pnm:PNUEName"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:complexType>
<xs:anyAttribute namespace="##other" processContents="lax">
</xs:element>
<xs:element name="RedirectingUserID" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element ref="pnm:PNUEID"/>
<xs:element ref="pnm:PNUEName"/>
<xs:element name="RedirectionLevel" type="RedirectionLevelType" minOccurs="0"/>
<xs:element name="RedirectionPrio" type="positiveInteger" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:attribute name="id" type="xs:positiveInteger" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax">
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="UriOfRedirectedUser" type="xs:anyURI" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax">
</xs:complexType>
<!– The AccessControl data set –>
<xs:complexType name="AccessControlType">
<xs:sequence>
<xs:element name="ControllerUE" maxOccurs="1">
<xs:complexType>
<xs:sequence>
<xs:element ref="pnm:PNUEID"/>
<xs:element ref="pnm:PNUEName"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:element>
<xs:element name="ControlleeUE" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element ref="pnm:PNUEID"/>
<xs:element ref="pnm:PNUEName"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:element name="PNAccessControlList" type="ACListType" minOccurs="0"/>
<xs:element name="PNAccessControlType" type="ACType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:attribute name="id" type="xs:positiveInteger" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="UriOfControllerUE" type="xs:anyUIR" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!– The PNUEName data set –>
<xs:complexType name="PNUENameType">
<xs:element ref="pnm:PNUEID" maxOccurs="1"/>
<xs:sequence maxOccurs="unbounded">
<xs:element name="UEName" type="UENameType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<xs:complexType name="UENameType">
<xs:sequence maxOccurs="unbounded">
<xs:element name="Name" type="xs:string"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
<xs:attribute name="id" type="xs:positiveInteger" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
<!– The Simple Types –>
<xs:simpleType name="RedirectionLevelType">
<xs:restriction base="xs:string">
<xs:enumeration value="application"/>
<xs:enumeration value="component"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="RedirectionPrioType">
<xs:restriction base="xs:positiveInteger">
<xs:enumeration value="1"/>
<xs:enumeration value="2"/>
<xs:enumeration value="3"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="ACListType">
<xs:list itemType="xs:string"/>
</xs:simpleType>
<xs:simpleType name="ACType">
<xs:restriction base="xs:string">
<xs:enumeration value="Controller"/>
<xs:enumeration value="NonController"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
NOTE 1: The <xs:any> and <xs:anyAttribute> elements within the complex types allow for compatible standard extensions in future releases.
NOTE 2: This document supports three values of the priority for the <RedirectionPrioType> element (High, medium and low).
Annex C (normative):
Definitions of the PNM XCAP application usage
XCAP requires an application usage to fulfil a number of steps in the definition of such application usage. The remainder of this annex specifies the required definitions of the PNM XCAP application usage.
Application Unique ID (AUID): Each XCAP application usage is associated with a unique name called the Application Unique ID (AUID). The AUID defined by the PNM application usage falls into the vendor‑proprietary namespace of XCAP AUID, where 3GPP is considered a vendor.
The AUID allocated to the PNM XCAP application usage is:
pnm.3gpp.org
Default namespace: XCAP requires application usages to declare the default namespace. The default namespace of the PNM XCAP application usage is:
http://uri.3gpp.org/params/xml/pnm/xcap
MIME type: The MIME type of PNM XML documents is:
application/pnm+xml
Naming conventions: By default, a PNM XML document is stored under the user’s Home Directory (which is located under the "users" sub‑tree). In order to facilitate the manipulation of a PNM XML document, the present document defines a default XML file name:
pnm.xml
XCAP root URI: The XCAP root defines all contexts in which all XCAP resources defined by the operator (e.g., an operator with a domain name of example.com) exist and the corresponding XCAP root URI is:
xcap.example.com
XCAP User Identify (XUI): Each user known to the XACP server is associated with a user name, called XCAP User Identifier (XUI), which is pre-configured at the PN UE. The XUI for PNM can be the shared public user identity used of the PN user.
Validation Constraints: The <PNUEName> child elements of all <RedirectedUserID> and <RedirectingUserID> child elements of a <UERedirection> element shall have different values.
The <PNUEName> child elements of all <ControllerUE> and <ControlleeUE> child elements of an <AccessControl> element shall have different values.
Data Semantics: Data semantics are defined above.
Resource Interdependencies: There are no resource interdependencies in this application usage beyond those defined by the schema.
Authorization Policies: This application usage does not change the default authorization policy defined by XCAP.
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2007-08 |
Skeleton of the TS (C1-072012) |
– |
0.0.0 |
||||
|
2007-08 |
Version 0.1.0 created as a result of incorporating the following contributions at CT1#48. C1-071648 – PNM Stage 3 – Annex B PNM XML Scheme Definition C1-072094 – PNM stage 3 Clause 4 Overview C1-072095 – PNM stage 3 Clause 5 Roles for PN-registration C1-072096 – PNM stage 3 Clause 10 Protocol at the Ut reference point |
0.0.0 |
0.1.0 |
||||
|
2007-10 |
C1-072607 – TS 24.259 Annex A.2 C1-072608 – Signalling Flow for PN-registration in the IM CN subsystem C1-072610 – TS24.259-010-cleanup C1-072615 – Signalling flow for Access Control Proc. in CS Domain C1-072616 – Signalling flow for session redirection in CS domain C1-072695 – A.3.1 — Signal flow for PN-configuration for PN UE redirection C1-072696 – A.3.2 — Signal flow for PN-configuration for PN access control C1-072697 – A.3.3 — Signal flow for PN-query C1-072698 – A.3.4 — Signal flow for PN-deconfiguration C1-072721 – Signalling Flow for PNM Session Redirection in the IM CN subsystem |
0.1.0 |
0.2.0 |
||||
|
2007-11 |
C1-072782 XML update C1-072783 Annex 3.1 C1-073093 TS 24.259 CS domain Annex A.3.8 and A.3.9 C1-073095 Roles for PN UE redirection C1-073224 Roles for PN-Registration C1-073225 CS Network capabilities |
0.2.0 |
0.3.0 |
||||
|
2008-02 |
C1-080193 PN Stage 3 Flows Cleanup C1-080238 Roles for PN-configuration and PN-query C1-080239 Signalling flow for PN UE Name changing C1-080240 signalling flow cleanup C1-080468 Signalling Flow for PN Access Control in IM CN Subsystem C1-080469 Signalling flow for interdomain networking C1-080471 PN UE role in Access Control C1-080656 gsmSCF Capability in PN UE redirection C1-080659 PN Access Control in IM CN Subsystem |
0.3.0 |
0.4.0 |
||||
|
2008-04 |
C1-081017 PN UE Name signalling flow update C1-081299 PNM Scope in CS Domain C1-081350 Solution for the call delay problem in PN access control procedure C1-081351 The roles of gsmSCF for PN-registration C1-081435 Error procedures in the Roles for PN UE redirection |
0.4.0 |
0.5.0 |
||||
|
2008-05 |
C1-081959 PNM Editorial Corrections C1-081960 Addressing Editors Notes regarding PN Access Control C1-081961 Cleanup of PN UE Redirection C1-081962 PN UE redirection in CS domain |
0.5.0 |
0.6.0 |
||||
|
2008-05 |
Email review / airi changed to iari in clause 10.2 and 10.3 |
0.6.0 |
0.6.1 |
||||
|
2008-05 |
Email review / updating change history |
0.6.1 |
0.6.2 |
||||
|
2008-05 |
Editorial corrections done by MCC |
0.6.2 |
1.0.0 |
||||
|
2008-06 |
C1-082467 Correction of PN access control procedure C1-082468 Some cleanup of PNM Signaling flows C1-082637 XML schema update in TS 24.259 C1-082638 XCAP usage for PN configuration in TS 24.259 |
1.0.0 |
1.1.0 |
||||
|
2008-08 |
C1-083482 Cleanup of Signalling flows for PN-registration |
1.1.0 |
1.2.0 |
||||
|
2008-10 |
C1-084036 TS 24.259 clean-up C1-084401 Interaction with supplementary services C1-084403 PN-Configuration flow update C1-084406 Conveying PN UE information using 3rd party Registration C1-084445 Cleanup of PNM flows |
1.2.0 |
1.3.0 |
||||
|
2008-11 |
C1-084771 24.259 clean-up C1-085263 PNM Flow Cleanup C1-085482 PNM Closed User Group functionality |
1.3.0 |
1.4.0 |
||||
|
2008-11 |
Version 2.0.0 created for presentation to CT#42 for approval |
1.4.0 |
2.0.0 |
||||
|
2008-12 |
CT#42 |
Version 8.0.0 created after approval in CT#42 |
2.0.0 |
8.0.0 |
|||
|
2009-03 |
CT#43 |
CP-090133 |
0002 |
Conveying PN UE information using 3rd party Registration and ICSI/IARI corrections |
8.0.0 |
8.1.0 |
|
|
2009-03 |
CT#43 |
CP-090133 |
0003 |
Flow updates |
8.0.0 |
8.1.0 |
|
|
2009-06 |
CT#44 |
CP-090427 |
0004 |
Correction of 3GPP URN link |
8.1.0 |
8.2.0 |
|
|
2009-06 |
CT#44 |
CP-090427 |
0005 |
1 |
Cleanup of PNM stage 3 |
8.1.0 |
8.2.0 |
|
2009-06 |
CT#44 |
Editorial cleanup by MCC |
8.1.0 |
8.2.0 |
|||
|
2009-12 |
CT#46 |
CP-090924 |
0006 |
3 |
Procedures of PNE-registration |
8.2.0 |
9.0.0 |
|
2009-12 |
CT#46 |
CP-090924 |
0007 |
2 |
Procedures of PNE-configuration |
8.2.0 |
9.0.0 |
|
2009-12 |
CT#46 |
CP-090924 |
0008 |
1 |
Overview of PNM in Rel-9 |
8.2.0 |
9.0.0 |
|
2009-12 |
CT#46 |
CP-090924 |
0009 |
Procedures of PNE redirection |
8.2.0 |
9.0.0 |
|
|
2010-03 |
CT#47 |
CP-100136 |
0014 |
1 |
PNE definition in 24.259 |
9.0.0 |
9.1.0 |
|
2010-03 |
CT#47 |
CP-100135 |
0017 |
1 |
XML example clarification |
9.0.0 |
9.1.0 |
|
2010-03 |
CT#47 |
CP-100135 |
0019 |
1 |
Access flow corrections |
9.0.0 |
9.1.0 |
|
2010-03 |
CT#47 |
CP-100135 |
0020 |
1 |
Editorial corrections |
9.0.0 |
9.1.0 |
|
2010-03 |
CT#47 |
CP-100136 |
0021 |
1 |
Procedures of PAN access control |
9.0.0 |
9.1.0 |
|
2010-03 |
CT#47 |
Editorial cleanup by MCC |
9.0.0 |
9.1.0 |
|||
|
2010-06 |
CT#48 |
CP-100356 |
0023 |
Editorial corrections |
9.1.0 |
9.2.0 |
|
|
2010-06 |
CT#48 |
CP-100356 |
0025 |
2 |
Example flows of PNE registration |
9.1.0 |
9.2.0 |
|
2010-06 |
CT#48 |
CP-100356 |
0026 |
4 |
Procedures of PNE registration |
9.1.0 |
9.2.0 |
|
2010-09 |
CT#49 |
CP-100502 |
0028 |
2 |
Correction to value of feature tag g.3gpp.pne-id |
9.2.0 |
9.3.0 |
|
2010-09 |
CT#49 |
CP-100502 |
0029 |
1 |
g.3gpp.pne-id security considerations |
9.2.0 |
9.3.0 |
|
2010-09 |
CT#49 |
CP-100519 |
0027 |
PNM XCAP application usage |
9.3.0 |
10.0.0 |
|
|
2011-09 |
CT#53 |
CP-110667 |
0031 |
Updating IMEI URN draft reference |
10.0.0 |
10.1.0 |
|
|
2011-12 |
CT#54 |
CP-110866 |
0033 |
Inclusion of media feature tag ASN.1 identifier for g.3gpp.pne-id |
10.1.0 |
10.2.0 |
|
|
2012-03 |
CT#55 |
CP-120104 |
0038 |
1 |
Updating IMEI URN draft reference |
10.2.0 |
10.3.0 |
|
2012-03 |
CT#55 |
CP-120124 |
0034 |
1 |
IETF reference update |
10.3.0 |
11.0.0 |
|
2012-12 |
CT#58 |
CP-120784 |
0041 |
1 |
Updating IMEI URN draft reference |
11.0.0 |
11.1.0 |
|
2013-09 |
CT#61 |
CP-130489 |
0044 |
1 |
Updating IMEI URN draft reference |
11.1.0 |
11.2.0 |
|
2013-12 |
CT#62 |
CP-130730 |
0047 |
1 |
Updating IMEI URN draft reference |
11.2.0 |
11.3.0 |
|
2014-03 |
CT#63 |
CP-140120 |
0050 |
1 |
Updating IMEI URN draft reference |
11.3.0 |
11.4.0 |
|
2014-09 |
CT#65 |
CP-140636 |
0053 |
1 |
Updating IMEI URN draft reference to RFC 7254 |
11.4.0 |
11.5.0 |
|
2014-09 |
Post CT#65 |
Upgrade to Rel-12 |
11.5.0 |
12.0.0 |
|||
|
2015-06 |
CT#66 |
CP-150328 |
0054 |
Aligning TLS profiles used by CT1 specifications with SA3 agreed TLS profile |
12.0.0 |
13.0.0 |
|
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-10 |
Upgrade to Rel-15 |
15.0.0 |
|||||
|
2020-07 |
SA-88e |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2021-12 |
CT#94e |
CP-213031 |
0055 |
B |
Reference update for HTTP/1.1 protocol |
17.0.0 |
|