|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Personal Network Management (PNM);
Procedures and information flows;
Stage 2
(3GPP TS 23.259 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 1 ETSI TS 123 259 V15.0.0 (2018-10)
Reference
RTS/TSGC-0123259vf00
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 23.259 version 15.0.0 Release 15 2 ETSI TS 123 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 23.259 version 15.0.0 Release 15 3 ETSI TS 123 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 and Abbreviations. . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 PNM overview . 7
4.1 General . 7
4.2 PN access control concepts . 8
5 Procedures and information flows for PN configuration. 9
5.1 PN-registration . 9
5.1.1 General . 9
5.1.2 PN-registration procedure in the IM CN subsystem . 9
5.1.3 PN-registration procedure in the CS domain . 10
5.1.4 PN-registration procedure for PNE other than a PN UE . 11
5.2 PN-deregistration. 11
5.2.1 General . 11
5.2.2 PN-deregistration procedure in the IM CN subsystem . 12
5.2.3 PN-deregistration procedure in the CS domain . 12
5.2.4 PN-deregistration procedure for PNE other than a PN UE . 14
5.3 PN-configuration . 14
5.3.1 General . 14
5.3.2 PN-configuration procedure in the IM CN subsystem . 15
5.3.3 PN-configuration procedure for PNE other than a PN UE in the IM CN subsystem. 17
5.4 PN-deconfiguration . 18
5.4.1 General . 18
5.4.2 PN-deconfiguration procedure in the IM CN subsystem . 18
5.5 PN-query . 19
5.5.1 General . 19
5.5.2 PN query procedure . 19
6 Procedures and information flows for PN redirection . 20
6.1 Procedures and information flows in the IP CN subsystem . 20
6.1.1 General . 20
6.1.2 Procedures and information flows for PN UE redirection in the IM CN subsystem . 20
6.1.3 Procedures and information flows for PNE redirection in the IM CN subsystem . 24
6.2 Procedures and information flows in the CS domain . 25
6.2.1 General . 25
6.2.2 Procedures and information flows for PN UE redirection in the CS domain . 25
6.3 Procedures and information flows in the domain interworking. 28
6.3.1 General . 28
6.3.2 Procedures and information flows for PN UE redirection from IM CN subsystem to CS domain . 28
6.3.3 Procedures and information flows for PN UE redirection from CS domain to IM CN subsystem . 29
7 Procedures and information flows for PN access control. 31
7.1 General . 31
7.2 PN access control procedures in the IM CN subsystem . 33
7.3 PN access control procedure in the IM CN subsystem . 34
7.3.1 General . 34
7.3.2 PN access control based on query logic in the IM CN subsystem . 34
7.3.3 PN access control based on access control lists . 35
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 4 ETSI TS 123 259 V15.0.0 (2018-10)
7.4 PN access control procedure in the CS domain . 38
7.4.1 General . 38
7.4.2 PN access control procedure (When the caller is not in the PN access control list) . 38
7.4.3 PN access control procedure in CS domain (When the caller is in the PN access control list) . 41
Annex A (informative): Change history . 43
History . 47
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 5 ETSI TS 123 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 23.259 version 15.0.0 Release 15 6 ETSI TS 123 259 V15.0.0 (2018-10)
1 Scope
The present document provides the procedure details and the information flows for support of Personal Network
Management and Personal Area Network, including the PN redirection and PN access control applications enabled by
Personal Network Management (PNM).
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 TS 22.259: "Service requirements for Personal Network Management (PNM)".
[2] 3GPP TS 23.002: "Network architecture".
[3] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model".
[4] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".
[5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[6] 3GPP TS 22.002: "Bearer Services Supported by a Public Land Mobile Network (PLMN)".
[7] 3GPP TS 22.003: "Circuit Teleservices Supported by a Public Land Mobile Network (PLMN)".
[8] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL)
Phase 4; Stage 2".
[9] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application
functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".
[10] 3GPP TS 23.018: "Basic Call Handling; Technical realization".
[11] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping
architecture".
[12] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD); Stage 2".
[13] 3GPP TS 22.085: "Closed User Group (CUG) Supplementary Services; Stage 1".
[14] 3GPP TS 23.085: "Closed User Group (CUG) supplementary service; Stage 2".
3 Definitions and Abbreviations.
3.1 Definitions
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.259 [1]
subclauses 3.1 and 4.2.1 apply:
Personal Area Network (PAN)
Personal Network (PN)
Personal Network Element (PNE)
PN UE redirection
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 7 ETSI TS 123 259 V15.0.0 (2018-10)
PN access control
PN-user
PNE redirection
default UE
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.002 [2] apply:
Application Server (AS)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.218 [3]
subclause 3.1 apply:
Initial filter criteria
Initial Request
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [4]
subclause 3.1 apply:
Public user identity
Private user identity
Proxy-CSCF (P-CSCF)
Serving-CSCF (S-CSCF)
For the purposes of the present document, the following terms and definitions given in 3GPP TR 21.905 [5] apply:
User Equipment (UE)
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.085 [13] apply:
Incoming Access (IA)
Outgoing Access (OA)
For the purposes of the present document, the following terms and definitions apply:
PN UE name: A name selected by a PN-user for a PN UE of the PN-user's PN and recorded together with other
subscription data like the public/private user identity/identities by the operator in the HSS and the PNM AS by means of
provisioning. A PN UE name (e.g., "MeinSchatz") for a PN UE is unique within the PN-user’s PN.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply.
CUG Closed User Group
PAN Personal Area Network
PN Personal Network
PNE Personal Network Element
PNM Personal Network Management
4 PNM overview
4.1 General
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 PN-user, as described in
3GPP TS 22.259 [1]. These home network-based management functions cover the configuration of the PN-user’s PN
such as PN-registration, PN-deregistration, PN-configuration, PN-deconfiguration and PN-query procedures, and the
operation of the PN-user's PN. Functionality enabled by the PNM comprises the PN UE redirection and the PN access
control applications as described in 3GPP TS 22.259 [1]. In order to provide the PN UE redirection and the PN access
control applications, the PNM is realized as an AS in the IM CN subsystem as described in 3GPP TS 23.002 [2] and as
a CAMEL service in the CS domain as described in 3GPP TS 23.078 [4].
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 8 ETSI TS 123 259 V15.0.0 (2018-10)
4.2 PN access control concepts
The PN access control is one of the PNM applications specified in 3GPP TS 22.259 [1] that enables PN-users to
exercise access control to restrict accesses to certain UE(s) of their PNs. 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 [13] and 3GPP TS 23.085 [14], 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 perform such PN access control the PN-users need to configure a PN access control list for each UE of the
PN. The configuration can be done either in a static or a dynamic way. Besides other additional information, the PN
access control list of a UE within a PN contains all identities (e.g., a SIP URI) which are permitted to be used to initiate
sessions to that UE. In this document, the UE of a PN that is used by the PN-user to exercise access control is referred
to controller UE, whereas the UE of the PN, over which an access control is enabled, is referred to controllee UE. The
controller UE of a PN-user’s PN is assigned by provisioning and the controller UE can configure any UE of the PN as
controllee UE. The PN access control list of the controllee UE is only configurable by the controller UE.
Figure 4.2-1: Relationship of various service profiles in PN access control
An example of the service profiles configuration for PN access control is shown in the above figure 4.2-1. The arrows
indicate the direction of control. Some of the aspects involved are:
- A PN-user's PN consists of two UEs, i.e., UE 1a and UE 1b, where UE 1b is the controllee UE and UE 1a is the
controller UE.
- The service profile of UE 1b is referred to as the controllee UE Service Profile.
- The service profile of UE 1a is referred to as the controller UE Service Profile.
- The assignment of controller UE service profile is done during provisioning.
- Access control of UE 1b by UE 1a is performed with the help of a SIP Application Server (AS), referred to as
PNM AS.
- From UE 1a, the PN-user configures a PN access control list that contains details of PN access control regarding
UE 1b's service profile. This configuration is done over the Ut interface. For example: this PN access control list
can contain a list of UE identities that are allowed to initiate sessions with UE 1b.
- The PNM AS executes the actual PN access control procedures.
- The PNM AS performs PN access control by utilizing the PN access control list.
- If inadequate information present in the access control list to enable PN access control, the PNM AS can query
the controller UE about the information with how to precede the received initial request.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 9 ETSI TS 123 259 V15.0.0 (2018-10)
5 Procedures and information flows for PN
configuration
5.1 PN-registration
5.1.1 General
The PN-registration is a procedure where the PN-user requests authorization to use PNM applications. As a result of a
successful registration, the UE capabilities can be conveyed to the PNM AS.
5.1.2 PN-registration procedure in the IM CN subsystem
Figure 5.1.2-1: Successful PN-registration procedure in the IM CN subsystem
1. The Register information flow sent by a UE arrives at the S-CSCF/Registrar. The Register information flow
contains the private user identity and the public user identity of the UE.
2. The S-CSCF sends a Cx-Put/Cx-Pull containing the private user identity and public user identity to the HSS and
the HSS returns the information flow (eg. the initial filter criteria) to the S-CSCF.
3. Based on the initial filter criteria, the S-CSCF sends a Register information flow to the PNM AS. If the PNM AS
specific data, for instance the PN UE name or the private user identity, which is associated with the initial filter
criteria, is received from the HSS in Step 2, it is delivered to the PNM AS in the Register information flow.
4. The PNM AS sends a Subscribe information flow to obtain the public user identity received in the Register
information flow in Step 3.
5. The S-CSCF sends a Notify information flow to the PNM AS containing the public user identities and the UE
capabilities. If the S-CSCF assigned a GRUU for the UE during the registration, then the GRUU of the UE is
delivered in the Notify information flow.
NOTE: At the same time as Steps 4) and 5) the AS can also contact the HSS using Sh to obtain the information.
Where identical information is received from both sources, it is implementation specific how this is
combined.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 10 ETSI TS 123 259 V15.0.0 (2018-10)
6. Optionally, the PNM AS authorizes the PN-registration by querying the HSS. It is done by sending the private
user identity to the HSS. The HSS checks the public user identity/identities tied to the private user identity and
sends the public user identity/identities and the private user identity back to the PNM AS.
7. The PNM AS then verifies the PN-registration by comparing the public user identity/identities and the PN UE
name or with the other received from S-CSCF in the Step 3. As a result of a successful verification, the PNM AS
enrols the public user identity and the PN UE name or as registered in the data base.
5.1.3 PN-registration procedure in the CS domain
Figure 5.1.3-1: Successful PN-registration in the CS domain
1. The VLR receives a location update request from a UE.
2. The VLR sends the MAP_UPDATE_LOCATION message to the HSS to request the subscription information of
the UE.
3. The HSS sends the MAP_INSERT_SUBSCRIBER_DATA message back to update the VLR with the PNM
subscriber data.
4. The VLR changes the status of the UE to ‘attached’and sends the MAP_NOTE_MM_EVENT message to the
gsmSCF (CAMEL service for PNM) to report the mobile event.
NOTE: To support the mobility management event, the CAMEL Phase 3 or later is required.
5. The gsmSCF setups the UE registration status in the PN to ‘registered’.
6. The gsmSCF will send the UE status to the PNM AS.
NOTE: The interface between the gsmSCF and the PNM AS is unspecified.
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 11 ETSI TS 123 259 V15.0.0 (2018-10)
5.1.4 PN-registration procedure for PNE other than a PN UE
PNE UE S-CSCF PNM AS
1. Register Request
2. User Decision
3. Register
4. Register Response
6. Register
5. Register Response
7. Subscribe
8. Notify
9. Enrol the
PNE
Figure 5.1.4-1: UE initiates the registration on behalf of the PNE
1. The PNE sends a register request to the UE including its capabilities via the PAN internal communication
means.
2. Optionally, based on the user decision, the PNE is allowed to be added to the PAN.
3. The UE sends a SIP register request on behalf of the PNE to the S-CSCF. The Register information flow
contains the private user identity and the public user identity of the UE, the PNE identifier, and the PNE
capabilities.
4. The S-CSCF sends the register response back to the UE.
5. UE forwards the register response to the PNE via the PAN internal communication means.
6. Based on the initial filter criteria, the S-CSCF sends a third party Register information flow to the PNM AS.
7. The PNM AS sends a Subscribe information flow to obtain the public user identities, PNE identifier and the PNE
capabilities.
8. The S-CSCF sends a Notify information flow to the PNM AS containing the public user identities, PNE
identifier and PNE capabilities.
9. The PNM AS enrols the PNE identifier into the PAN.
5.2 PN-deregistration
5.2.1 General
Information shall be offered to the user by sending the status if the de-registered UE is the only default UE of the PN.
Figure 5.2.2-1 provides the procedure in the IM CN subsystem to inform the PN-user about De-registration of the only
default UE in the PN.
Figure 5.2.3-1 provides the procedure in the CS domain to inform the PN-user about De-registration of the only default
UE in the PN.
ETSI
---------------------- Page: 12 ----------------------
3GPP TS 23.259 version 15.0.0 Release 15 12 ETSI TS 123 259 V15.0.0 (2018-10)
Figure 5.2.4-1 provides the procedure to inform the UE about De-registration of the PNE.
5.2.2 PN-deregistration procedure in the IM CN subsystem
Figure 5.2.2-1: Successful PN-deregistration procedure in the IM CN subsystem
1. To de-register, the UE sends a new Register information flow with an expiration value of zero seconds. The
Register information flow contains the private user identity and the public user identity of the UE.
2. Based on the initial filter criteria, the S-CSCF sends Register information flow with an expiration value of zero
seconds to the PNM AS.
3. Optionally, the PNM AS authorizes the PN-registration by querying the HSS. It is done by sending the private
user identity to the HSS. The HSS checks the public user identity/identities tied to the private user identity and
sends it back to the PNM AS.
4. The PNM AS then verifies the PN-registration by comparing the public user identity/identities with the other
received from S-CSCF in the Step 2. As a result of a successful verification, the PNM AS enrols the public user
identity as de-registered in the data base and removes the stored configuration setting related to this specific
public user identity.
5. The PNM AS se
...