ETSI TS 124 623 V8.5.0 (2012-03)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (3GPP TS 24.623 version 8.5.0 Release 8)

RTS/TSGC-0124623v850

General Information

• Status: Published
• Publication Date: 20-Mar-2012
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Completion
• Due Date: 30-Mar-2012
• Completion Date: 21-Mar-2012

Standards Content (Sample)

Technical Specification
Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services
(3GPP TS 24.623 version 8.5.0 Release 8)

�
3GPP TS 24.623 version 8.5.0 Release 8 1 ETSI TS 124 623 V8.5.0 (2012-03)

Reference
RTS/TSGC-0124623v850
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the 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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2012.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 24.623 version 8.5.0 Release 8 2 ETSI TS 124 623 V8.5.0 (2012-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://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.
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
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 24.623 version 8.5.0 Release 8 3 ETSI TS 124 623 V8.5.0 (2012-03)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Architecture for manipulating supplementary services settings . 6
5 The eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) . 7
5.1 Introduction . 7
5.2 Functional entities . 8
5.2.1 User Equipment (UE) . 8
5.2.1.1 General . 8
5.2.1.2 Subscription for notification of state changes in XML document . 8
5.2.2 Authentication Proxy (AP) . 8
5.2.2.1 Introduction . 8
5.2.2.2 Authentication . 8
5.2.2.2.0 General . 8
5.2.2.2.1 Authentication based on the generic authentication architecture . 8
5.2.2.2.2 Void . 9
5.2.2.3 Authorization . 9
5.2.3 Application Server (AS) . 9
5.2.3.1 General . 9
5.2.3.2 Authentication and authorization . 9
5.2.3.2.0 General . 9
5.2.3.2.1 HTTP digest authentication . 10
5.2.3.3 Subscription acceptance and notification of state changes in XML document . 10
5.3 Roles . 10
5.3.1 XCAP client . 10
5.3.1.1 Introduction . 10
5.3.1.2 Manipulating supplementary services . 10
5.3.2 XCAP server . 11
5.3.2.1 Introduction . 11
5.3.2.2 Manipulation acceptance . 11
6 Supplementary services XCAP application usage . 11
6.1 Structure of the XML document . 11
6.2 XCAP application usage . 12
6.3 XML schema . 13
6.4 Template for a supplementary service XML schema . 14
Annex A (informative): Void . 15
Annex B (normative): Connectivity Aspects when using XCAP . 15
B.1 Scope . 15
B.2 Procedures at the UE . 15
Annex C (informative): Change history . 16
History . 17

ETSI
3GPP TS 24.623 version 8.5.0 Release 8 4 ETSI TS 124 623 V8.5.0 (2012-03)
Foreword
This Technical Specification (TS) was been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN) and originally published as ETSI TS 183 023
[13]. It was transferred to the 3rd Generation Partnership Project (3GPP) in January 2008.
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
3GPP TS 24.623 version 8.5.0 Release 8 5 ETSI TS 124 623 V8.5.0 (2012-03)
1 Scope
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 [8]. 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.
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] IETF RFC 2616: "Hypertext Transfer Protocol - HTTP/1.1".
[2] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[3] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication".
[4] IETF RFC 2246: "The TLS Protocol Version 1.0".
[5] 3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua);
Protocol details".
[6] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application
functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS)".
[7] Void.
[8] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol
(XCAP)".
[9] Void
[10] Void.
[11] IETF 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".
ETSI
3GPP TS 24.623 version 8.5.0 Release 8 6 ETSI TS 124 623 V8.5.0 (2012-03)
[14] OMA-TS-XDM_Core-V1_1-20080627-A: "XML Document Management (XDM) Specification".
[15] 3GPP TS 23.003: "Numbering, addressing and identification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in IETF RFC 4825 [8] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AP Authentication Proxy
AS Application Server
AUID Application Unique ID
HTTP HyperText Transfer Protocol
ISDN Integrated Services Digital Network
MIME Multipurpose Internet Mail Extensions
NAF Network Application Function
NGN Next Generation Network
PSTN Public Switched Telephone Network
TLS Transport Layer Security
UE User Equipment
URI Uniform Resource Identifier
XCAP XML Configuration Access Protocol
XML eXtended Markup Language
4 Architecture for manipulating supplementary services
settings
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.
UE AS
Ut
Figure 1: Ut interface
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 3GPP TS 33.222 [6].
NOTE: The Network Application Function (NAF) can be an AS.
ETSI
3GPP TS 24.623 version 8.5.0 Release 8 7 ETSI TS 124 623 V8.5.0 (2012-03)
Authentication
UE AS
Proxy
Ut Ut
Figure 2: Authentication proxy in the Ut interface path
5 The eXtensible Markup Language (XML)
Configuration Access Protocol (XCAP)
5.1 Introduction
For the purpose of manipulating data stored in an application server the XML Configuration Access Protocol
(XCAP) [8] is used. XCAP allows a client to read, write and modify application configuration data, stored in XML
format on a server. XCAP maps XML document sub-trees and element attributes to HTTP URIs, so that these
components can be directly accessed by HTTP (see RFC 2616 [1]). XCAP uses the HTTP methods PUT, GET, and
DELETE to operating on XML documents stored in the server.
In the case of supplementary services, the data stored in a server is related to the execution of that given service. The
present document defines a new XCAP Application Usage for the purpose of allowing a client to manipulate data
related to supplementary services.
XCAP (see RFC 4825 [8]) defines two logical roles: XCAP client and XCAP servers. An XCAP client is an HTTP/1.1
compliant client. Similarly an XCAP server is an HTTP/1.1 compliant server. The XCAP server acts as a repository of
XML documents that customize and modify the execution of the supplementary services. Figure 3 depicts the XCAP
architecture where an XCAP client sends an HTTP/1.1 request to an XCAP server. The server replies with an HTTP/1.1
response.
XCAP XCAP
client server
HTTP request
HTTP response
Figure 3: XCAP architecture
According to XCAP (see RFC 4825 [8]), each application that makes use of XCAP defines its own XCAP application
usage. The present document defines an supplementary services XCAP application usage in clause 6. This application
usage defines the XML schema W3C REC-xmlschema-1-20010502 [2] for the data used by the application, along with
other key pieces of information.
XCAP focuses on the definition of XML documents that are compliant with the XML schema and constrains defined
for a particular XCAP application usage. XCAP allows application to provide XML documents that are common for all
users or XML documents that affect the service of a given user.
Central to XCAP is the construction of the HTTP URI that points to particular XML document or certain components of
it. A component in an XML document can be an XML element, attribute, or the value of it.
ETSI
3GPP TS 24.623 version 8.5.0 Release 8 8 ETSI TS 124 623 V8.5.0 (2012-03)
5.2 Functional entities
5.2.1 User Equipment (UE)
5.2.1.1 General
The UE implements the role of an XCAP client, as described in clause 5.3.1.
For systems where Generic Authentication Architecture [6] is used, the UE shall support the authentication mechanisms
specified in 3GPP TS 33.222 [6] and 3GPP TS 24.109 [5].
For systems where Generic Authentication Architecture [6] is not used, the UE shall support RFC 2617 [3] and
RFC 2246 [4] according to ETSI TS 183 038 [12].
On sending an HTTP request, the UE may indicate the user's identity intended to be used with the AS by adding a
HTTP X-3GPP-Intended-Identity header (3GPP TS 24.109 [5]) to the outgoing HTTP request.
5.2.1.2 Subscription for notification of state changes in XML document
In order to keep the supplementary services state synchronized with the network elements and other terminals that the
user might be using, the UE should subscribe to changes in the XCAP simserv documents by generating a SUBSCRIBE
request in accordance with draft-RFC 5785 [11].
5.2.2 Authentication Proxy (AP)
5.2.2.1 Introduction
An Authentication Proxy is an HTTP/1.1 RFC 2616 [1] compliant server whose main purpose is to authenticate the user
requests. The Authentication Proxy is used to separate the authentication procedure and the Application Server (AS)
specific application logic to different logical entities.
The AP is configured as a HTTP reverse proxy, i.e. the FQDN of the AS is configured to the AP such a way that the IP
traffic intended to the AS is directed to the AP by the network. The AP performs the authentication of the UE. After the
authentication procedure has been successfully completed, the AP assumes the typical role of a reverse proxy, i.e. the
AP forwards HTTP requests originating from the UE to the correct AS, and returns the corresponding HTTP responses
from the AS to the originating UE.
...