ETSI TS 124 259 V17.0.0 (2022-05)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Personal Network Management (PNM); Stage 3 (3GPP TS 24.259 version 17.0.0 Release 17)

RTS/TSGC-0124259vh00

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Completion
• Completion Date: 13-May-2022

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Personal Network Management (PNM);
Stage 3
(3GPP TS 24.259 version 17.0.0 Release 17)

3GPP TS 24.259 version 17.0.0 Release 17 1 ETSI TS 124 259 V17.0.0 (2022-05)

Reference
RTS/TSGC-0124259vh00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
warranty is made of merchantability or fitness
and/or governmental rule and/or regulation and further, no representation or
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2022.
All rights reserved.
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 2 ETSI TS 124 259 V17.0.0 (2022-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 3 ETSI TS 124 259 V17.0.0 (2022-05)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Overview of personal network management . 9
4.1 General . 9
4.2 Network capabilities . 9
5 Functional entities . 9
5.1 Introduction . 9
5.2 User Equipment (UE) . 9
5.3 Application Server (AS) . 10
5.4 Authentication Proxy . 10
6 Roles for PN-registration. 10
6.1 Introduction . 10
6.2 PN UE . 10
6.3 PNM Application . 11
6.3.1 PN-registration procedure in the IM CN subsystem . 11
6.3.2 PN-registration procedure in the CS domain . 11
6.4 Definition of media feature tag g.3gpp.pne-id . 11
7 Roles for PN-configuration . 12
7.1 Introduction . 12
7.2 PN UE . 12
7.3 PNM application . 14
8 Roles for PN-query . 14
8.1 Introduction . 14
8.2 PN UE . 14
8.3 PNM application . 15
9 Roles for PN redirection . 15
9.1 Introduction . 15
9.2 PN UE . 15
9.3 PNM application . 15
9.3.1 PN UE redirection procedure in the IM CN subsystem . 15
9.3.2 PN UE redirection procedure in the CS domain . 16
10 Roles for PN access control . 16
10.1 Introduction . 16
10.2 PN UE . 17
10.2A PN UE procedures supporting PNE access control . 17
10.3 PNM application . 18
10.3.1 PN access control procedure in the IM CN subsystem . 18
10.3.2 PN access control procedure in the CS domain . 19
10.4 PNM controller IMS application reference identifier . 19
11 Protocol at the Ut reference point . 20
11.1 Introduction . 20
11.2 Roles . 20
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 4 ETSI TS 124 259 V17.0.0 (2022-05)
11.2.1 XCAP client . 20
11.2.2 XCAP server . 20
Annex A (informative): Example signalling flows . 21
A.1 Scope of signalling flows . 21
A.2 Introduction . 21
A.2.1 General . 21
A.2.2 Key required to interpret signalling flows . 21
A.3 Signalling flows . 23
A.3.1 Introduction . 23
A.3.2 Signalling flows for PN-registration. 23
A.3.2.1 PN-registration in the IM CN subsystem using third party registration . 23
A.3.2.2 PN-registration in the IM CN subsystem with subscription to reg event package . 26
A.3.2.3 PN-registration procedure for PNE other than a PN UE . 29
A.3.3 Signalling flows for PN-configuration . 34
A.3.3.1 PN-configuration for PN UE redirection . 34
A.3.3.2 PN-configuration for PN access control . 35
A.3.3.3 PN-configuration for changing PN UE name . 37
A.3.3.4 PN-query . 39
A.3.3.5 PN-deconfiguration . 40
A.3.4 Signalling flows for PN UE redirection . 41
A.3.4.1 PN UE redirection in the IM CN subsystem . 41
A.3.4.2 PN UE redirection in the CS domain . 48
A.3.5 Signalling flows for PN access control . 50
A.3.5.1 PN access control procedure in IM CN subsystem . 50
A.3.5.2 PN access control procedure in CS domain. . 59
A.3.6 Signalling flows for interdomain networking . 61
A.3.6.1 IM CN subsystem to CS domain . 61
A.3.6.2 CS domain to IM CN subsystem . 64
A.4 Example XML document . 66
A.4.1 Introduction . 66
Annex B (normative): PNM XML schema definition . 68
B.1 XML elements structure . 68
B.2 XML schema for PNM . 71
Annex C (normative): Definitions of the PNM XCAP application usage . 74
Annex D (informative): Change history . 75
History . 79

ETSI
3GPP TS 24.259 version 17.0.0 Release 17 5 ETSI TS 124 259 V17.0.0 (2022-05)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 6 ETSI TS 124 259 V17.0.0 (2022-05)
1 Scope
Personal Network Management (PNM) is a home network-based application and provides the home network-based
management of Personal Network (PN) consisting of multiple devices belonging to a single user, as described in
3GPP TS 22.259 [2] and 3GPP TS 23.259 [15].
The present document provides the protocol details for enabling Personal Network management (PNM) services in the
IP Multimedia (IM) Core Network (CN) subsystem based on the protocols of XML Configuration Access Protocol
(XCAP), Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document provides the protocol details for enabling Personal Network management (PNM) services in
Circuit Switched (CS) domain based on the protocols of CAP, MAP, ISUP, USSD and BICC.
The present document is applicable to User Equipment (UEs) and Application Servers (AS) providing PNM
capabilities.
The present document makes no PNM specific enhancements to SIP, SIP events or SDP specified in
3GPP TS 24.229 [3].
The present document makes no PNM specific enhancements to CAP, MAP, ISUP, USSD and BICC.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.259: "Service requirements for Personal Network Management (PNM)".
[3] 3GPP TS 24.229: "IP Multimedia Call Control based on SIP and SDP; Stage 3".
[4] Void.
[5] 3GPP TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua);
Protocol details".
[6] IETF RFC 4825 (May 2007): "The Extensible Markup Language (XML) Configuration Access
Protocol (XCAP)."
[7] Void.
[8] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping
architecture".
[9] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message
contents".
[10] 3GPP TS 24.228 Release 5: "Signalling flows for the IP multimedia call control based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[11] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and
message contents".
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 7 ETSI TS 124 259 V17.0.0 (2022-05)
[12] 3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
[13] 3GPP TS 29.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL)
Phase 3: CAMEL Application Part (CAP) specification".
[14] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD); Stage 3".
[15] 3GPP TS 23.259: "Personal Network Management (PNM); Procedures and Information Flows;
Stage 2".
[16] IETF RFC 4244 (November 2005): "An Extension to the Session Initiation Protocol (SIP) for
Request History Information".
[17] IETF RFC 4458 (April 2006): "Session Initiation Protocol (SIP) URIs for Applications such as
Voicemail and Interactive Voice Response (IVR)".
[18] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services".
[19] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services; Stage 1".
[20] 3GPP TS 23.085: "Closed User Group (CUG) supplementary service; Stage 2".
[21] IETF RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session Initiation
Protocol (SIP)".
[22] IETF RFC 7254 (May 2014): "A Uniform Resource Name Namespace for the Global System for
Mobile Communications Association (GSMA) and the International Mobile station Equipment
Identity (IMEI)".
[23] IETF RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[24] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[25] IETF RFC 7231 (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions given in IETF RFC 4825 [6] apply.
Application usage
Application Unique ID (AUID)
Document Selector
Document URI
Naming Conventions
Node Selector
Node Selector Separator
Node URI
XCAP client
XCAP resource
XCAP root
XCAP root URI
XCAP server
XCAP User Identifier (XUI)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.085 [19] apply:
Incoming Access (IA)
Outgoing Access (OA)
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 8 ETSI TS 124 259 V17.0.0 (2022-05)

For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.259 [2] apply:
Personal Areal Network (PAN)
Personal Network (PN)
Personal Network Element (PNE)
PNE Identifier
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACM Address Complete Message
ANM Answer Message
AS Application Server
BICC Bearer Independent Call Control
BSF Bootstrapping Server Function
CAMEL Customised Applications for Mobile network Enhanced Logic
CAP CAMEL Application Part
CCCF Call Continuity Control Function
CN Core Network
CS Circuit Switched
CUG Closed User Group
FQDN Fully Qualified Domain Name
GBA Generic Bootstrapping Architecture
GMSC Gateway MSC
GRUU Globally Routable User Agent URI
GSM Global System for Mobile communications
HLR Home Location Register
HSS Home Subscriber Server
HTTP Hypertext Transfer Protocol
IA Incoming Access
IAM Initial Address Message
IARI IMS Application Reference Identifier
ICSI IMS Communication Service Identifier
IDP Initial Detection Point
IE Information Element
IFC Initial Filter Criteria
IM IP Multimedia
IMEI International Mobile Equipment Identity
IMS IM CN subsystem
IP Internet Protocol
ISDN Integrated Services Digital Network
ISUP ISDN User Part
MAP Mobile Application Part
MGCF Media Gateway Control Function
MS Mobile Station
MSC Mobile Switching Centre
MSISDN MS international PSTN/ISDN number
NAF Network Application Function
OA Outgoing Access
P-CSCF Proxy Call Session Control Function
PN Personal Network
PNE Personal Network Element
PNM Personal Network Management
PSI Public Service Identity
PSTN Public Switched Telephone Network
S-CSCF Serving Call Session Control Function
SDP Session Description Protocol
SIP Session Initiation Protocol
SRI Send Routing Information
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 9 ETSI TS 124 259 V17.0.0 (2022-05)
TLS Transport Layer Security
UE User Equipment
URI Uniform Resource Identifier
URN Uniform Resource Name
USSD Unstructured Supplementary Service Data
VLR Visitor Location Register
XCAP XML Configuration Access Protocol
XML Extensible Markup Language
4 Overview of personal network management
4.1 General
PNM applications consist of the PN redirection service and the PN access control , both applying only to the
terminating service, as described in 3GPP TS 22.259 [2] and 3GPP TS 23.259 [15]. The PN redirection is a PNM
application that enables redirecting a session addressed to any of the UEs belonging to the PN to a certain UE or a
certain PNE other than a PN UE of their PN, i.e., the default UE or default PNE other than a PN UE for terminating
services. The PN access control is a PNM application that enables users to exercise PN access control to restrict
accesses to certain UEs or certain PNEs other than PN UEs of their PN. The PN may consist of UEs which are only
privately accessed, that is each UE may be accessed only by other UEs of the PN. The PN-User may additionally
modify the access levels of each UE of the PN to be public or private. In this regard the PN behaves similar to a CUG as
specified in 3GPP TS 22.085 [19] and 3GPP TS 23.085 [20], with Outgoing Access and whether Incoming Access is
allowed for the PN UE is dependent on the PN access control list for that PN UE.
In order to make the above happen, the following procedures are provided within this document:
- procedures for PN-registration are specified in clause 6;
- procedures for PN-configuration are specified in clause 7;
- procedures for PN-query are specified in clause 8;
- procedures for session redirection are specified in clause 9; and
- procedures for restricting access to certain UEs are specified in clause 10.
4.2 Network capabilities
In order to support the PNM services the following network capabilities are assumed:
1) provision by the home network operator of PNM specific AS on the IM CN subsystem, as specified in
3GPP TS 24.229 [3];
2) support of CAMEL phase-3 and USSD as specified in 3GPP TS 29.078 [13] and 3GPP TS 24.090 [14].
5 Functional entities
5.1 Introduction
5.2 User Equipment (UE)
To be compliant with this document, a UE shall implement the role of a PN UE (see subclause 6.2, subclause 7.2,
subclause 8.2, subclause 9.2 and subclause 10.2).
The UE shall implement the XCAP client role as described in subclause 11.2.1.
The UE shall implement HTTP digest authentication (see 3GPP TS 24.109 [5]).
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 10 ETSI TS 124 259 V17.0.0 (2022-05)
The UE shall implement Transport Layer Security (TLS) according to the TLS profile specified in
3GPP TS 33.310 [24] annex E.
The UE shall implement the GBA Function as described in 3GPP TS 33.220 [8].
The UE shall initiate a bootstrapping procedure with the bootstrapping server function (BSF) located in the home
network, as described in 3GPP TS 24.109 [5].
5.3 Application Server (AS)
The AS implementing PNM application shall implement the role of a XCAP server (see subclause 11.2.2).
The AS implementing PNM application shall implement the Network Application Function (NAF) as described in
3GPP TS 33.220 [8].
NOTE: For terminating services, the PNM Application in IM CN subsystem is the first Application Server of any
Application Servers in the path of the call.
The AS implementing PNM application shall remove g.3gpp.pne-id media feature tag containing IMEI included in the
Contact header field of requests and responses of SIP methods other than the SIP REGISTER method prior to
forwarding the request or response to the destination.
5.4 Authentication Proxy
The generic requirements for an authentication proxy are defined in 3GPP TS 24.109 [5].
6 Roles for PN-registration
6.1 Introduction
The PN-registration is the procedure where a UE is added to the PN, or a PNE is added to the PAN. As a result of a
successful registration, the UE capabilities are conveyed to the PNM application.
6.2 PN UE
If a PN UE supports the PN controller functionality and is configured to act as a PN controller the PN UE shall include
in the Contact header of the REGISTER request a g.3gpp.iari_ref feature tag containing the IARI value defined in
subclause 10.4.
Upon receiving a REGISTER request sent from a PNE other than a PN UE via the PAN internal interface, the PN UE
shall initiate a SIP REGISTER request as defined in 3GPP TS 24.229 [3] subclause 5.1.1.2.1 with the following
addition:
1) including in the Contact header field a g.3gpp.pne-id media feature tag containing the PNE identifier defined in
subclause 6.4.
If using the multiple registrations mechanism for registering each PNE, the PN UE shall use a different "reg-id" value
when registering the PNE.
If using SIP re-registration procedures for registering another PNE, the PN UE includes a Contact header field for each
registered PNE in the SIP REGISTER request.
There are no PNM specific requirements for registration of the PN UE to the CS domain.
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 11 ETSI TS 124 259 V17.0.0 (2022-05)
6.3 PNM Application
6.3.1 PN-registration procedure in the IM CN subsystem
The PNM AS can be configured with any of various options for obtaining information from the IM CN subsystem
specified in 3GPP TS 24.229 [3], 3GPP TS 29.328 [9] and 3GPP TS 29.329 [12], for example:
a) receipt of REGISTER request which causes a third-party REGISTER request containing in the body the
incoming REGISTER request from the PN UE and the 200 (OK) response to the incoming REGISTER request
to be sent to the PNM application. The PNM application may then obtain information from the body of the third-
party REGISTER request;
b) receipt of REGISTER request which causes a third-party REGISTER request containing in the body a info> element containing the private user identity of the PN UE to be sent to the PNM application. The PNM
application may then subscribe to the reg event package for that user to obtain information; or
c) receipt of REGISTER request which causes a third-party REGISTER request containing in the body a info> element containing the private user identity of the PN UE to be sent to the PNM application. The PNM
application may then use the Sh interface to obtain information.
This document places no requirement on the use of all or any of these mechanisms.
After successful PN-registration, the PNM AS shall enrol the public user identity of the registered PN UE or the
registered PNE identifier in the data base.
6.3.2 PN-registration procedure in the CS domain
When the gsmSCF (CAMEL service for PNM) receives a MAP_NOTE_MM_EVENT message sent from the VLR to
report that the status of the UE set to ‘attached’, the gsmSCF sets the UE registration status in the PN to ‘registered’ and
sends the UE status to the PNM AS.
NOTE: The interface between the gsmSCF and the PNM AS is unspecified.
When the gsmSCF (CAMEL service for PNM) receives a MAP_NOTE_MM_EVENT message sent from the VLR to
report that the status of the UE set to ‘detached’, the gsmSCF sets the UE registration status in the PN to ‘deregistered’
and checks whether the PN UE was the only default UE in the PN. If it was the only default UE in the PN, the gsmSCF
generates a USSD Notify message to the HSS to inform the user.
6.4 Definition of media feature tag g.3gpp.pne-id
Media feature-tag name: g.3gpp.pne-id
ASN.1 Identifier: 1.3.6.1.8.2.8
Summary of the media feature indicated by this tag: This media feature-tag when used in a SIP request or a SIP
response indicates the identifier of a PNE other than a UE.
Values appropriate for use with this feature-tag: URN. When an IMEI is available, the URN shall take the form of a
IMEI URN (see IETF RFC 7254 [22]). If no IMEI is available, the URN shall take the form of a string representation of
a UUID as a URN as defined in IETF RFC 4122 [23].
The feature-tag is intended primarily for use in the following applications, protocols, services, or negotiation
mechanisms: This feature-tag is most useful in a communications application, for describing the capabilities of a device,
such as a PC or PDA.
Examples of typical use: Indicating the identifier of a device which is part of a Personal Area Network.
Related standards or documents: 3GPP TS 24.259: "Personal Network Management (PNM), stage 3".
Security Considerations:
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 12 ETSI TS 124 259 V17.0.0 (2022-05)
UE is not allowed to include g.3gpp.pne-id media feature tag containing IMEI in the Contact header field of requests
and responses of SIP methods other than the SIP REGISTER method except when the request or response is guaranteed
to be sent to a trusted intermediary that will remove the g.3gpp.pne-id media feature tag prior to forwarding the request
or response to the destination. Other security considerations for this media feature-tag are discussed in subclause 12.1 of
IETF RFC 3840 [21].
7 Roles for PN-configuration
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. ) 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;
ETSI
3GPP TS 24.259 version 17.0.0 Release 17 13 ETSI TS 124 259 V17.0.0 (2022-05)
- "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 containing the children and , and the
with a unique value for the "id" attribute containing the children and , as well as the
and the ;
NOTE: A PN user decides the value of the 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 shall be populated with the public
user identity of the PN UE configured by the PN UE to be redirected and indicated by the .
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 containing the children ,  and , and the
with a unique value for the "id" attribute containing the children and ,
as well as the and the ;
NOTE: A PN user decides the value of the 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 shall be populated with the GRUU
of the PNE configured by the PNE to be redirected and indicated by the .
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 containing the children and , the with a unique
value for the "id" attribute containing children and , and the
and ;
- the value of the "UriOfControllerUE" attribute of the shall be populated with the public user
identity of the controller UE indicated by the .
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 containing the children and , the with a
unique value for the "id" attribute containing children ,  and , and the
and ;
- the value of the "UriOfControllerUE" attribute of the shall be populated with the public user
identity of the controller UE indicated by the
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 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
.The XML body of the HTTP PUT request message shall contain:
- the identified by the shared public user identity, the containing an "id" attribute with the
attribute value pointing to the to be changed and the to be changed.
If the PN-configuration is performed for configuring an element within an XML document, the XML body of the HTTP
request messag
...