TS 23.259
PNM – Personal Network Management –
Procedures and Information Flows
V19.0.0 (PDF)
2025/09 48 p.
V18.0.0
2024/03 48 p.
V17.0.0
2022/03 48 p.
V16.0.0
2020/06 48 p.
V15.0.0
2018/09 48 p.
V14.0.0
2017/03 47 p.
V13.0.0
2015/12 48 p.
V12.0.0
2014/09 48 p.
V11.0.0
2012/09 48 p.
V10.0.0
2011/03 48 p.
V9.4.0
2010/06 47 p.
V8.2.0
2008/12 41 p.
- Rapporteur:
- Dr. Lu, Yang
Vodafone GmbH
essential Table of Contents for TS 23.259 Word version: 19.0.0
each title links to the equivalent title in the CONTENT
List of Figures and Tables
| Figure 4.2-1 | Relationship of various service profiles in PN access control |
| Figure 5.1.2-1 | Successful PN-registration procedure in the IM CN subsystem |
| Figure 5.1.3-1 | Successful PN-registration in the CS domain |
| Figure 5.1.4-1 | UE initiates the registration on behalf of the PNE |
| Figure 5.2.2-1 | Successful PN-deregistration procedure in the IM CN subsystem |
| Figure 5.2.3-1 | Procedure to inform the PN-user about the PN-deregistration of the default UE |
| Figure 5.2.4-1 | PN-deregistration procedure for PNE other than a PN UE |
| Figure 5.3.2-1 | Successful PN-configuration procedure in the IM CN subsystem |
| Figure 5.3.3-1 | PN-configuration procedure for PNE in the IM CN subsystem |
| Figure 5.4.2-1 | Successful PN-deconfiguration procedure in the IM CN Subsystem |
| Figure 5.5.2-1 | Successful PN query procedure in the IM CN subsystem |
| Figure 6.1.2-1 | Initial request to UE-1 and redirected to UE-2 by the PNM AS in the IM CN subsystem |
| Figure 6.1.2-2 | Initial request to UE-1 and redirected to UE-2 by the PNM AS in the IM CN subsystem when the UE-2 shares the same public user identity with the UE-1 |
| Figure 6.1.2-3 | Initial request to UE-1 and redirected to UE-3 by the PNM AS in the IM CN subsystem when the initial request to UE-2 fails |
| Figure 6.1.3-1 | Initial request to UE-1 and redirected to PNE-1 by the PNM AS in the IM CN subsystem |
| Figure 6.2.2-1 | Initial request to UE-1 and redirected to UE-2 by the gsmSCF (CAMEL service for PNM) in the CS domain |
| Figure 6.2.2-2 | Initial request to UE-1 and redirected to UE-3 by the gsmSCF (CAMEL service for PNM) in the CS domain when the initial request to UE-2 fails |
| Figure 6.3.2-1 | Initial request in IM CN subsystem and redirected to UE-2 in CS domain by the PNM AS |
| Figure 6.3.3-1 | Initial request in CS domain and redirected to UE-2 in IM CN subsystem by the gsmSCF |
| Figure 7.1-1 | Overview of privacy based access control Procedures and Information Flows |
| Figure 7.1-2 | PN access control execution flow at the PNM AS (AC and ACL stand for Access Control and Access Control List, respectively) |
| Table 1 | Example of a simple access control table PN |
| Figure 7.3.2-1 | High level sequence of PN access control |
| Figure 7.3.3-1 | PN access control in case of PNM AS alone |
| Figure 7.3.3-2 | PNE access control |
| Figure 7.4.2-1 | PN access control Procedure in CS domain |
| Figure 7.4.2-2 | PN access control procedure in CS domain with delay handling. |
| Figure 7.4.3-1 | PN access control procedure in the CS domain (Caller is in the PN access control list) |