Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 24.623  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…   B…

 

1  ScopeWord‑p. 6
The present document defines a protocol used for manipulating data related to supplementary services. The protocol is based on the eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) RFC 4825. A new XCAP application usage is defined for the purpose of manipulating the supplementary services data. The common XCAP related aspects that are applicable to supplementary services are specified in the present document. The protocol allows authorized users to manipulate service related data either when they are connected to IMS or when they are connected to non IMS networks (e.g. the public Internet).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support XCAP application usage for manipulating data related to supplementary services.
Up

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]
RFC 2616:  "Hypertext Transfer Protocol - HTTP/1.1".
[2]
W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[3]
RFC 2617:  "HTTP Authentication: Basic and Digest Access Authentication".
[4]
RFC 2246:  "The TLS Protocol Version 1.0".
[5]
TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua); Protocol details".
[6]
TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".
[7]  Void.
[8]
RFC 4825:  "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[9]  Void
[10]  Void.
[11]
RFC 5875  (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[12]
ETSI TS 183 038: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Simulation Services; Extensible Markup Language (XML) Document Management; Protocol Specification (Endorsement of OMA-TS-XDM-Core-V1-0-20051103-C and OMA-TS-XDM-Shared-V1-0-20051006-C)".
[13]
ETSI TS 183 023 V1.4.0: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN PSTN/ISDN Simulation Services".
[14]
OMA-TS-XDM_Core-V1_1-20080627-A: "XML Document Management (XDM) Specification".
[15]
TS 23.003: "Numbering, addressing and identification".
[15A]
TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[15B]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[16]
TS 24.315: "IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3".
[17]
TS 33.141: "Presence service; Security".
[18]
RFC 6665  (July 2012): "SIP-Specific Event Notification".
[19]
TS 24.167: "3GPP IMS Management Object (MO); Stage 3".
[20]
TR 21.905: "Vocabulary for 3GPP Specifications".
[21]
TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[22]
TS 24.424: "Management Object (MO) for Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (SS)".
[23]
TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".
[24]
TS 22.011: "Service accessibility".
[25]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[26]
TS 29.292: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem (IMS) and MSC Server for IMS Centralized Services (ICS)".
[27]
TS 33.220: "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA)".
[28]
TS 33.221: "Generic Authentication Architecture (GAA); Support for subscriber certificates".
[29]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
[30]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[31]
TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3".
[32]
TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC".
[33]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[34]
TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks".
Up

3  Definitions and abbreviationsWord‑p. 8

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and RFC 4825 apply.
SS configuration via XCAP:
supplementary services (SS) configuration based on XCAP protocol sent over the Ut interface.
For the purposes of the present document, the following terms and definitions given in TS 22.011 apply:
3GPP PS data off
3GPP PS data off exempt service
For the purposes of the present document, the following terms and definitions given in TS 24.229 apply:
3GPP PS data off status
For the purposes of the present document, the following terms and definitions given in TS 24.501 apply:
NG-RAN
Up

3.2  Abbreviations

For the purposes of the present document, the following abbreviations apply:
5GCN
5G Core Network
5GS
5G System
AP
Authentication Proxy
AS
Application Server
AUID
Application Unique ID
EPS
Evolved Packet System
GPRS
General Packet Radio Service
HTTP
HyperText Transfer Protocol
IMS
IP Multimedia Subsystem
IP-CAN
IP Connectivity Access Network
ISDN
Integrated Services Digital Network
MIME
Multipurpose Internet Mail Extensions
MMI
Man-Machine Interface
NAF
Network Application Function
NGN
Next Generation Network
NG-RAN
Next Generation Radio Access Network
ODB
Operator Determined Barring
PS
Packet Switched
PSTN
Public Switched Telephone Network
SS
Supplementary Service
TLS
Transport Layer Security
UE
User Equipment
URI
Uniform Resource Identifier
WPA
Wrong Password Attempts
XCAP
XML Configuration Access Protocol
XML
eXtended Markup Language
XUI
XCAP User Identifier
Up

4  Architecture for manipulating supplementary services settingsWord‑p. 9
The protocol described in the present document allows to manipulate settings and variables related that influence the execution of one or more supplementary services. Manipulation of the supplementary services take place over the Ut interface (UE to AS), as shown in Figure 1.
(not reproduced yet)
Figure 1: Ut interface
Up
Manipulation of supplementary services does not usually take place during real time operation. Typically users manipulate their services configuration data prior to the invocation and execution of the service.
Authentication of the user with HTTP may take place directly at the AS, such as in Figure 1, or with the support of an Authentication Proxy, such as in Figure 2. The architecture for authentication is provided in TS 33.222.
(not reproduced yet)
Figure 2: Authentication proxy in the Ut interface path
Up

Up   Top   ToC