1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelUser DatUser data repository a(3GPP TS 29.3TECHNICAL SPECIFICATION129 335 V13.0.0 (2016communications system (Phaelecommunications System (LTE; ata Convergence (UDC); access protocol over the Ud Stage 3 .335 version 13.0.0 Release 1316-01) hase 2+
2、); (UMTS); d interface; 13) ETSI ETSI TS 129 335 V13.0.0 (2016-01)13GPP TS 29.335 version 13.0.0 Release 13Reference RTS/TSGC-0429335vd00 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 47 16 Siret N 348 623 562 00017
3、 - 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 print. The content of any elec
4、tronic 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 the Portable Document Format (PD
5、F) 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/stat
6、us.asp 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, electronic or mechanical, including photocop
7、ying 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 Telecommunications Standards Institute 2016
8、. 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 and the GSM logo are Trade Marks regist
9、ered and owned by the GSM Association. ETSI ETSI TS 129 335 V13.0.0 (2016-01)23GPP TS 29.335 version 13.0.0 Release 13Intellectual 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 an
10、y, 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 o
11、n 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 on the ETSI Web server) which are, or m
12、ay 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 identitie
13、s. 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 document “shall“, “shall not“, “should“, “shou
14、ld 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 when used in direct citation. ETSI ETSI TS
15、 129 335 V13.0.0 (2016-01)33GPP TS 29.335 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 Proto
16、col Stack 8g34.1 General . 8g34.2 Protocol Stack for Ud Data Access Messages 8g34.3 Protocol Stack for Ud Subscriptions/Notifications . 8g35 General Messages . 9g35.1 General . 9g35.2 Open Link for a LDAP Session 9g35.3 Close Link for a LDAP Session . 9g35.4 Transactions . 9g36 User Data Convergence
17、 Messages . 9g36.1 General . 9g36.2 Query 9g36.3 Create . 10g36.4 Delete . 10g36.5 Update 10g36.6 Subscribe 10g36.7 Notify . 11g36.8 Abandon operation . 11g37 Information Elements . 12g37.1 Information Element Types with LDAP 12g37.2 Information Elements for Subscriptions and Notifications 12g38 Sec
18、urity. 12g3Annex A (normative): SOAP Subscription and Notification . 13g3A.1 XML schema for Subscribe Request 13g3A.2 XML schema for Subscribe Response . 13g3A.3 XML schema for Notify Request . 14g3A.4 XML schema for Notify Response . 15g3Annex B (informative): LDAP Message flows and Transaction flo
19、ws for UDC . 16g3B.1 General LDAP Message flow for UDC 16g3B.2 LDAP Transaction flows for UDC . 16g3Annex C (informative): Messages Based on SOAP . 18g3C.1 General . 18g3C.2 Protocol Stack for Messages Based on SOAP . 18g3ETSI ETSI TS 129 335 V13.0.0 (2016-01)43GPP TS 29.335 version 13.0.0 Release 1
20、3C.3 SOAP Based Query 19g3C.4 SOAP Based Create 19g3C.5 SOAP Based Delete 19g3C.6 SOAP Based Update 19g3C.7 SOAP Based Abandon . 20g3Annex D (informative): Change history . 21g3History 22g3ETSI ETSI TS 129 335 V13.0.0 (2016-01)53GPP TS 29.335 version 13.0.0 Release 13Foreword This Technical Specific
21、ation has been produced by the 3rdGeneration Partnership Project (3GPP). 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
22、 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 a
23、ll 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 129 335 V13.0.0 (2016-01)63GPP TS 29.335 version 13.0.0 Release 131 Scope The present document specifies
24、the stage 3 of the Ud interface between the Front-Ends (FEs) and the User Data Repository (UDR) in the User Data Convergence (UDC architecture). This 3GPP Technical Specification (TS) specifies the protocol and interactions between the FE and the UDR for Ud reference point, in particular: - The deta
25、ils of the LDAP protocol that are to be considered - The details of the SOAP envelope that provide support for subscriptions to notifications and notifications about data changes service (S/N operations). The User Data Convergence Stage 2 description (architecture and information flows) is specified
26、 in 3GPP TS 23.335 10. The UDR data model used with LDAP (i.e. attributes, object classes and directory information tree) is implementation specific and is left outside the scope of 3GPP specifications. For multivendor interoperability between FEs and UDR specific integration projects are needed. So
27、me examples of Ud data models are described in 3GPP TR 29.935 19. 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
28、 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 tha
29、t document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TR 41.001: “GSM Release specifications“. 3 3GPP TR 21 912 (V3.1.0): “Example 2, using fixed text“. 4 IETF RFC 4510: “Lightweight Directory Access Protocol (v3)“. 5 IETF RFC 5805: “L
30、ightweight Directory Access Protocol (LDAP) Transactions“. 6 W3C Recommendation “Simple Object Access Protocol (SOAP) 1.2“ (27 April 2007). http:/www.w3.org/TR/. 7 IETF RFC 2616 (June 1999): “Hypertext Transfer Protocol HTTP/1.1“. 8 IETF RFC 4511: “Lightweight Directory Access Protocol (LDAP): The P
31、rotocol“. 9 IETF RFC 4528: “Lightweight Directory Access Protocol (LDAP) Assertion Control“. 10 3GPP TS 23.335: “User Data Convergence (UDC); Technical realization and information flows“. 11 IETF RFC 4512: “Lightweight Directory Access Protocol (LDAP): Directory Information Models“. 12. 3GPP TS 32.1
32、82: “Telecommunication management; User Data Convergence (UDC); Common Baseline Information Model“. 13 Void ETSI ETSI TS 129 335 V13.0.0 (2016-01)73GPP TS 29.335 version 13.0.0 Release 1314 Void 15 3GPP TS 33.210: “3G Security; Network Domain Security; IP network layer security“. 16 IETF RFC 4513: “
33、Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms“. 17 National Institute of Standards and Technology, FIPS Pub 197: Advanced Encryption Standard (AES), 26 November 2001. . 18 OASIS “Directory Services Markup Language v2.0“ (30 April 2002) http:/www.oasis-o
34、pen.org/. 19 3GPP TR 29.935: “Study on UDC Data Model“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the def
35、inition of the same term, if any, in 3GPP TR 21.905 1. LDAP Session: starts with LDAP Bind Operation and ends with LDAP Unbind Operation or Notice of Disconnection. Front End: a core network functional entity or service layer entity or provisioning entity that can access user data stored in a unique
36、 repository. Front End Identifier: A name that uniquely identifies an FE within the set of all FEs accessing an UDR. Front End Cluster: FEs handling the same application may be grouped in clusters to differentiate between them e.g. with regard to geographical location, feature support, vendor, or ot
37、her characteristics. All FEs within a cluster are treated equally for required purposes (e.g. authorization, notifications, etc.). Application type: The application handled by a FE (e.g. HLR) determines the application type of the FE. The application type is derived from the name indicated by a FE.
38、Front End Cluster Identifier: A name that identifies a cluster grouped with FEs supporting the same application. User Data Repository: facility where user data can be accessed stored and managed in a common way. 3.2 Symbols For the purposes of the present document, the following symbols apply: Ud re
39、ference point between a FE and the UDR 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21
40、.905 1. FE Front End UDR User Data Repository NDS Network Domain Security ETSI ETSI TS 129 335 V13.0.0 (2016-01)83GPP TS 29.335 version 13.0.0 Release 134 Protocol Stack 4.1 General Data access messages on the Ud interface shall make use of IETF RFC 4510 4 and IETF RFC 4511 8. See section 4.2 for de
41、tails. Subscription messages and Notification messages on the Ud interface shall make use of SOAP 6. See section 4.3 for details. 4.2 Protocol Stack for Ud Data Access Messages Figure 4.2-1 shows the protocol layering used for UDR data access. Figure 4.2-1 Protocol Layering for Data Access 4.3 Proto
42、col Stack for Ud Subscriptions/Notifications Figure 4.3-1 shows the protocol layering used for Ud Subscription/Notification. Figure 4.3-1 Protocol Layering for Subscription/Notification ETSI ETSI TS 129 335 V13.0.0 (2016-01)93GPP TS 29.335 version 13.0.0 Release 135 General Messages 5.1 General This
43、 section describes common messages for UDC to establish sessions and administrate transactions. For an existing session, UDC messages are exchanged between the FE and the UDR. See figure B.1-1 in Annex B for general LDAP message flows. 5.2 Open Link for a LDAP Session To initiate a LDAP session, a F
44、ront-End shall first establish a transport connection with the UDR. The transport connection shall be a TCP connection. The IP Layer may be secured according to section 8. When IPsec is used, an IPsec connection may support several TCP connections, each supporting a LDAP session. After establishment
45、 of the transport connection, the FE shall initiate a LDAP session by sending a LDAP BindRequest message. The establishment of the LDAP session shall comply with IETF RFC 4511 8. It shall be done before sending any other LDAP message. FE Identifier or FE Cluster Identifier shall be included in the B
46、indRequest message. The UDR shall support the “unauthenticated authentication mechanism of simple Bind“ and the “name/password authentication mechanism of simple Bind“ in the “simple authentication method“ specified in IETF RFC 4513 16. The UDR derives the application type from the FE Identifier or
47、the FE Cluster Identifier. If the FE provided the Front End Identifier the UDR may also derive the Front End Cluster Identifier. NOTE: As security is handled at IP Layer (see section 8), optional security mechanisms (TLS, SASL) described in IETF RFC 4513 16 specification are not required for Ud. 5.3
48、 Close Link for a LDAP Session Termination of the LDAP session may be initiated by the FE by sending an UnbindRequest message or by the UDR by sending a Notice of Disconnection message. The termination of the LDAP session shall comply with IETF RFC 4511 8 5.4 Transactions In order to allow FEs to re
49、late a number of update operations, such as Create (see 6.3), Delete (see 6.4), and Update (see 6.5), and have them performed in one unit of interaction, the transaction concept in IETF RFC 5805 “Lightweight Directory Access Protocol (LDAP) Transactions“ 5 shall be supported. See figure B.2-1 in Annex B for LDAP Transaction flow. If used, they shall only be used for a single subscriber in order to decrease the complexity of transactions. LDAP server shall terminate the transaction if the timer is expired.
