1、 ETSI TS 124 623 V14.1.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); 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
2、version 14.1.0 Release 14) floppy3TECHNICAL SPECIFICATION ETSI ETSI TS 124 623 V14.1.0 (2017-04)13GPP TS 24.623 version 14.1.0 Release 14Reference RTS/TSGC-0124623ve10 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 4
3、7 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in
4、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 th
5、e 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 https:
6、/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, elec
7、tronic 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. European Tel
8、ecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM
9、 and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 124 623 V14.1.0 (2017-04)23GPP TS 24.623 version 14.1.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information p
10、ertaining 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 Sec
11、retariat. 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
12、 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 iden
13、tities, 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. Modal verbs terminology In the present docume
14、nt “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 wh
15、en used in direct citation. ETSI ETSI TS 124 623 V14.1.0 (2017-04)33GPP TS 24.623 version 14.1.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviati
16、ons . 7g34 Architecture for manipulating supplementary services settings . 8 g35 The eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) 8g35.1 Introduction 8g35.2 Functional entities 9g35.2.1 User Equipment (UE) . 9g35.2.1.1 General 9g35.2.1.2 Subscription for notification of stat
17、e changes in XML document . 9g35.2.1.3 Policy on access type used for XCAP . 9g35.2.2 Authentication Proxy (AP) . 11g35.2.2.1 Introduction . 11g35.2.2.2 Authentication . 11g35.2.2.2.0 General 11g35.2.2.2.1 Authentication based on the generic authentication architecture . 12g35.2.2.2.2 Void . 12g35.2
18、.2.3 Authorization 12g35.2.3 Application Server (AS) . 12g35.2.3.1 General 12g35.2.3.2 Authentication and authorization 13g35.2.3.2.0 General 13g35.2.3.2.1 HTTP digest authentication . 13g35.2.3.3 Subscription acceptance and notification of state changes in XML document . 13g35.2.3.4 Validation agai
19、nst service capability . 13g35.3 Roles . 14g35.3.1 XCAP client 14g35.3.1.1 Introduction . 14g35.3.1.2 Manipulating supplementary services . 14g35.3.1.2.1 General 14g35.3.1.2.2 U E temporarily prevented from manipulating supplementary service settings via XCAP . 14g35.3.1.2.3 Supplementary service se
20、ttings manipulation errors . 15g35.3.1.2.4 HTTP retry when no response is received . 15g35.3.1.3 Password change . 15g35.3.2 XCAP server . 15g35.3.2.1 Introduction . 15g35.3.2.2 Manipulation acceptance . 16g35.3.2.3 User not allowed to manipulate settings via XCAP 16g35.3.2.4 Supplementary Service s
21、ubscription errors . 16g35.3.2.5 Password management 16g35.3.2.5.1 General 16g35.3.2.5.2 Password check . 17g35.3.2.5.3 Password change . 17g36 Supplementary services XCAP application usage . 17g36.1 Structure of the XML document . 17g36.2 XCAP application usage 18g3ETSI ETSI TS 124 623 V14.1.0 (201
22、7-04)43GPP TS 24.623 version 14.1.0 Release 146.3 XML schema 20g36.4 Template for a supplementary service XML schema . 21g36.5 XML schema for password change 22g3Annex A (informative): Void . 23g3Annex B (normative): Connectivity Aspects when using XCAP . 24g3B.1 Scope 24g3B.2 Procedures at the UE 2
23、4g3Annex C (informative): Change history . 25g3History 27g3ETSI ETSI TS 124 623 V14.1.0 (2017-04)53GPP TS 24.623 version 14.1.0 Release 14Foreword This Technical Specification (TS) was been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Adva
24、nced 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 TS
25、G 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 indicate
26、s 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 ETSI TS 124 623 V14.1.0 (201
27、7-04)63GPP TS 24.623 version 14.1.0 Release 141 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 d
28、efined 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 o
29、r 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 do
30、cuments 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.
31、- 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 Pr
32、otocol - 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 inter
33、face (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 (
34、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; E
35、xtensible 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/ISD
36、N 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“. ETSI ETSI TS 124 623 V14.1.0 (2017-04)73GPP TS 24
37、.623 version 14.1.0 Release 1415 3GPP TS 23.003: “Numbering, addressing and identification“. 16 3GPP TS 24.315: “IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3“. 17 3GPP TS 33.141: “Presence service; Security“. 18 IETF RFC 6665 (July 2012): “SIP-Specific Event Notification“
38、. 19 3GPP TS 24.167: “3GPP IMS Management Object (MO); Stage 3“. 20 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 21 3GPP TS 33.310: “Network Domain Security (NDS); Authentication Framework (AF)“. 22 3GPP TS 24.424: “Management Object (MO) for Extensible Markup Language (XML) Configuration A
39、ccess Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (SS)“. 23 3GPP TS 22.030: “Man-Machine Interface (MMI) of the User Equipment (UE)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.9
40、05 20 and IETF RFC 4825 8 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AP Authentication Proxy AS Application ServerAUID Application Unique ID HTTP HyperText Transfer Protocol IMS IP Multimedia Subsystem ISDN Integrated Services Digital Networ
41、k MIME Multipurpose Internet Mail Extensions MMI Man-Machine Interface NAF Network Application Function NGN Next Generation Network ODB Operator Determined Barring PSTN Public Switched Telephone Network TLS Transport Layer Security UE User Equipment URI Uniform Resource Identifier WPA Wrong Password
42、 AttemptsXCAP XML Configuration Access Protocol XML eXtended Markup LanguageXUI XCAP User Identifier ETSI ETSI TS 124 623 V14.1.0 (2017-04)83GPP TS 24.623 version 14.1.0 Release 144 Architecture for manipulating supplementary services settings The protocol described in the present document allows to
43、 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. Figure 1: Ut interface Manipulation of supplementary services does not usually
44、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
45、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. Figure 2: Authentication proxy in the Ut interface path 5 The eXtensible Markup Language (XML) Configuration Access Protocol (XCAP) 5.1 Introduction For the
46、 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,
47、 so that these components can be directly accessed by HTTP (see IETF 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.
48、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 IETF 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 s
49、erver 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. UEUtASUEUtAuthenticationProxyASUtETSI ETSI TS 124 623 V14.1.0 (2017-04)93GPP TS 24.623 version 14.1.0 Release 14Figure 3: XCAP architecture According to XCAP (see IETF RFC 4825 8), each application that
