Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.259  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…   A…

 

1  Scopep. 6

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 TS 22.259 and TS 23.259.
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 TS 24.229.
The present document makes no PNM specific enhancements to CAP, MAP, ISUP, USSD and BICC.
Up

2  Referencesp. 6

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.259: "Service requirements for Personal Network Management (PNM)".
[3]
TS 24.229: "IP Multimedia Call Control based on SIP and SDP; Stage 3".
[4]  Void.
[5]
TS 24.109: "Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details".
[6]
RFC 4825  (May 2007): "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)."
[7]  Void.
[8]
TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture".
[9]
TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents".
[10]
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]
TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
[12]
TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
[13]
TS 29.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3: CAMEL Application Part (CAP) specification".
[14]
TS 24.090: "Unstructured Supplementary Service Data (USSD); Stage 3".
[15]
TS 23.259: "Personal Network Management (PNM); Procedures and Information Flows; Stage 2".
[16]
RFC 4244  (November 2005): "An Extension to the Session Initiation Protocol (SIP) for Request History Information".
[17]
RFC 4458  (April 2006): "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)".
[18]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[19]
TS 22.085: "Closed User Group (CUG) Supplementary Services; Stage 1".
[20]
TS 23.085: "Closed User Group (CUG) supplementary service; Stage 2".
[21]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[22]
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]
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[24]
TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[25]
RFC 7231  (June 2014): "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
Up

3  Definitions, symbols and abbreviationsp. 7

3.1  Definitionsp. 7

For the purposes of the present document, the following terms and definitions given in RFC 4825 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 TS 22.085 apply:
Incoming Access (IA)
Outgoing Access (OA)
For the purposes of the present document, the following terms and definitions given in TS 22.259 apply:
Personal Areal Network (PAN)
Personal Network (PN)
Personal Network Element (PNE)
PNE Identifier
Up

3.2  Abbreviationsp. 8

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
XCAP
XML Configuration Access Protocol
XML
Extensible Markup Language
Up

4  Overview of personal network managementp. 9

4.1  Generalp. 9

PNM applications consist of the PN redirection service and the PN access control , both applying only to the terminating service, as described in TS 22.259 and TS 23.259. 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 TS 22.085 and TS 23.085, 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.
Up

4.2  Network capabilitiesp. 9

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 TS 24.229;
  2. support of CAMEL phase-3 and USSD as specified in TS 29.078 and TS 24.090.

Up   Top   ToC