|
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 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 1 ETSI TS 124 259 V15.0.0 (2018-10)
Reference
RTS/TSGC-0124259vf00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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
If you find errors in the present document, please send your comment to one of the following services:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 2 ETSI TS 124 259 V15.0.0 (2018-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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
---------------------- Page: 3 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 3 ETSI TS 124 259 V15.0.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 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 . 10
6.3.1 PN-registration procedure in the IM CN subsystem . 10
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 . 11
7.1 Introduction . 11
7.2 PN UE . 12
7.3 PNM application . 13
8 Roles for PN-query . 14
8.1 Introduction . 14
8.2 PN UE . 14
8.3 PNM application . 14
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 . 16
10.2A PN UE procedures supporting PNE access control . 17
10.3 PNM application . 17
10.3.1 PN access control procedure in the IM CN subsystem . 17
10.3.2 PN access control procedure in the CS domain . 18
10.4 PNM controller IMS application reference identifier . 19
11 Protocol at the Ut reference point . 19
11.1 Introduction . 19
11.2 Roles . 19
11.2.1 XCAP client . 19
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 4 ETSI TS 124 259 V15.0.0 (2018-10)
11.2.2 XCAP server . 19
Annex A (informative): Example signalling flows . 20
A.1 Scope of signalling flows . 20
A.2 Introduction . 20
A.2.1 General . 20
A.2.2 Key required to interpret signalling flows . 20
A.3 Signalling flows . 21
A.3.1 Introduction . 21
A.3.2 Signalling flows for PN-registration. 22
A.3.2.1 PN-registration in the IM CN subsystem using third party registration . 22
A.3.2.2 PN-registration in the IM CN subsystem with subscription to reg event package . 24
A.3.2.3 PN-registration procedure for PNE other than a PN UE . 27
A.3.3 Signalling flows for PN-configuration . 32
A.3.3.1 PN-configuration for PN UE redirection . 32
A.3.3.2 PN-configuration for PN access control . 34
A.3.3.3 PN-configuration for changing PN UE name . 35
A.3.3.4 PN-query . 37
A.3.3.5 PN-deconfiguration . 38
A.3.4 Signalling flows for PN UE redirection . 40
A.3.4.1 PN UE redirection in the IM CN subsystem . 40
A.3.4.2 PN UE redirection in the CS domain . 47
A.3.5 Signalling flows for PN access control . 49
A.3.5.1 PN access control procedure in IM CN subsystem . 49
A.3.5.2 PN access control procedure in CS domain. . 58
A.3.6 Signalling flows for interdomain networking . 60
A.3.6.1 IM CN subsystem to CS domain . 60
A.3.6.2 CS domain to IM CN subsystem . 62
A.4 Example XML document . 65
A.4.1 Introduction . 65
Annex B (normative): PNM XML schema definition . 66
B.1 XML elements structure . 66
B.2 XML schema for PNM . 69
Annex C (normative): Definitions of the PNM XCAP application usage . 72
Annex D (informative): Change history . 73
History . 77
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 5 ETSI TS 124 259 V15.0.0 (2018-10)
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
---------------------- Page: 6 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 6 ETSI TS 124 259 V15.0.0 (2018-10)
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] IETF RFC 2616 (June 1999): "Hypertext Transfer Protocol (HTTP) – HTTP/1.1".
[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".
[12] 3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 7 ETSI TS 124 259 V15.0.0 (2018-10)
[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)".
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)
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)
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 8 ETSI TS 124 259 V15.0.0 (2018-10)
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
TLS Transport Layer Security
UE User Equipment
URI Uniform Resource Identifier
URN Uniform Resource Name
USSD Unstructured Supplementary Service Data
VLR Visitor Location Register
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 9 ETSI TS 124 259 V15.0.0 (2018-10)
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]).
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].
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 24.259 version 15.0.0 Release 15 10 ETSI TS 124 259 V15.0.0 (2018-10)
5.3 Application Server (AS)
The AS implementing PNM application shall implement the role of a XCA
...