7 Roles for PN-configuration
24.2593GPPPersonal Network Management (PNM)Release 17Stage 3TS
7.1 Introduction
This clause specifies the PN-configuration and PN-deconfiguration procedures for supporting PN UE redirection, PN access control and PN UE name changing.
NOTE: A text string together with angled brackets (e.g. <PNUEName>) represents an XML element defined by the XML schema in Annex B.
Subclause A.3 provides examples of signalling flows for PN-configuration and PN-deconfiguration.
7.2 PN UE
In order for the PN UE to initiate the PN-configuration procedure for creating/replacing or deleting an XML document, an element within an XML document or an attribute of an element within an XML document, the PN UE shall know the data structure and constraints defined by the PNM XML schema in annex B. The PN UE shall also know what HTTP URI to use based on the naming conventions for constructing the HTTP URIs described in annex C.
The PN UE initiates the PN-configuration procedure or the PN-deconfiguration procedure by sending a HTTP PUT request or a HTTP DELETE request message with:
– Request-URI field indicating to the PNM application the desired location where the XML document, an element within an XML document or an attribute of an element within an XML document which is requested to be configured as follows:
– if the PN-configuration procedure performed for configuring an XML document, the Request-URI is constructed with a document URI pointing to the XML document;
– if the PN-configuration procedure performed for configuring an element within an XML document, the document selector of the Request-URI is constructed with a document URI pointing to the XML document containing the element to be configured, and the node selector of the Request-URI with a node URI identifying the element to be configured;
– if the PN-configuration procedure performed for configuring an attribute of an element within an XML document, the document selector of the Request-URI is constructed with a document URI pointing to the XML document containing the element to be queried and the node selector of the Request-URI with a node URI identifying the attribute to be configured;
– Host field indicating the Internet host and port number of the PNM application;
– User-Agent field containing information about the user agent originating the request and the static string (e.g. 3gpp-gba) to indicate to the NAF that the UE supports 3GPP-bootstrapping based authentication;
– Referer field indicating the address (URI) of the resource from which the URI for the PNM application is obtained;
– Authorization field containing the credentials obtained by means of executing the bootstrapping procedure with the BSF as described in 3GPP TS 33.220 [8];
– Content-Type field indicating
– "application/pnm+xml", if the PN-configuration is performed for configuring an XML document;
– "application/xcap-el+xml" as in IETF RFC 4825 [6], if the PN-configuration is performed for configuring an element within an XML document;
– "application/xcap-att+xml" as in IETF RFC 4825 [6], if the PN-configuration is performed for configuring an attribute of an element within an XML document;
If the PN-configuration is performed for creating/replacing the XML document for the PN UE redirection purpose, the XML body of the HTTP PUT request message shall contain:
– the <RedirectedUserID> containing the children <PNUEID> and <PNUEName>, and the <RedirectingUserID> with a unique value for the "id" attribute containing the children <PNUEID> and <PNUEName>, as well as the <RedirectionLevel> and the <RedirectionPrio>;
NOTE: A PN user decides the value of the <RedirectionLevel> element based on the PN UE capabilities. According to the requirements of 3GPP TS 22.259 [2], this document supports three values (a global level for all services, a service level for selected services and a service component level for different media).
– the value of the "UriOfRedirectedUser" attribute for the <UERedirection> shall be populated with the public user identity of the PN UE configured by the PN UE to be redirected and indicated by the <RedirectedUserID>.
If the PN-configuration is performed for creating/replacing the XML document for the PNE redirection purpose, the XML body of the HTTP PUT request message shall contain:
– the <RedirectedUserID> containing the children <PNUEID>, <PNEID> and <PNEName>, and the <RedirectingUserID> with a unique value for the "id" attribute containing the children <PNEID> and <PNEName>, as well as the <RedirectionLevel> and the <RedirectionPrio>;
NOTE: A PN user decides the value of the <RedirectionLevel> element based on the PNE capabilities. According to the requirements of 3GPP TS 22.259 [2], this document supports three values (a global level for all services, a service level for selected services and a service component level the different media).
– the value of the "UriOfRedirectedUser" attribute for the <PNERedirection> shall be populated with the GRUU of the PNE configured by the PNE to be redirected and indicated by the <RedirectedUserID>.
If the PN-configuration is performed for creating/replacing the XML document for the PN access control purpose, the XML body of the HTTP PUT request message shall contain:
– the <ControllerUE> containing the children <PNUEID> and <PNUEName>, the <ControlleeUE> with a unique value for the "id" attribute containing children <PNUEID> and <PNUEName>, and the <PNAccessControlList> and <PNAccessControlType>;
– the value of the "UriOfControllerUE" attribute of the <AccessControl> shall be populated with the public user identity of the controller UE indicated by the <ControllerUE>.
If the PN-configuration is performed for creating/replacing the XML document for the PNE access control purpose, the XML body of the HTTP PUT request message shall contain:
– the <ControllerUE> containing the children <PNUEID> and <PNUEName>, the <ControlleePNE> with a unique value for the "id" attribute containing children <PNUEID>, <PNEID> and <PNEName>, and the <PNAccessControlList> and <PNAccessControlType>;
– the value of the "UriOfControllerUE" attribute of the <AccessControl> shall be populated with the public user identity of the controller UE indicated by the <ControllerUE>
NOTE: The PNE here stands for the PNE other than a PN UE, i.e. ME, MT or TE of a PAN.
If the PN-configuration is performed for the PN UE name changing purpose, and if the PN UE does not know the value of the "id" attribute of the <UEName> to be changed, the UE shall first initiate the PN-query procedure as specified in clause 8 in order to cache a copy of the XML document containing the value of the "id" attribute of that <UEName>.The XML body of the HTTP PUT request message shall contain:
– the <PNUEID> identified by the shared public user identity, the <UEName> containing an "id" attribute with the attribute value pointing to the <UEName> to be changed and the <Name> to be changed.
If the PN-configuration is performed for configuring an element within an XML document, the XML body of the HTTP request message shall contain:
– the XML element to be configured.
If the PN-configuration is performed for configuring an attribute of an element within an XML document, the XML body of the HTTP request message shall contain:
– the value of the attribute of an element to be configured.
7.3 PNM application
In order for the PNM application to support the PN-configuration procedure for creating/replacing or deleting an XML document, an element within an XML document or an attribute of an element within an XML document, the PNM application shall know the data structure and constraints imposed by the PNM XML schema in annex B. The PNM application shall also be configured to be able to handle the HTTP URIs described in annex C.
Upon receiving a HTTP PUT request or a HTTP DELETE request message, the PNM application verifies the Authorization header by using the bootstrapping transaction identifier B-TID and the key material Ks_NAF obtained from the BSF (as described in 3GPP TS 33.220 [8]). If the verification succeeds, the PNM application obtains the private user identity associated with the received public user identity. The PNM application then authorizes the PN UE by comparing the received public user identity with the preconfigured one identified by the private user identity.
If the authorization succeeds, the PNM application shall perform the requested action and generate a response in accordance with IETF RFC 4825 [6].