ETSI TS 129 335-2017 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE User Data Convergence (UDC) User data reposit.pdf

1、 ETSI TS 129 335 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3 (3GPP TS 29.335 version 14.0.0 Release 14) TECHNICA

2、L SPECIFICATION ETSI ETSI TS 129 335 V14.0.0 (2017-04)13GPP TS 29.335 version 14.0.0 Release 14Reference RTS/TSGC-0429335ve00 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 - NAF 742 C

3、 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 electronic and/o

4、r 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 (PDF) version k

5、ept 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:/portal.etsi.org/TB/ETSIDeliverableStatus.

6、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, electronic or mechanical, including photocopyi

7、ng 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 2017.

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. oneM2M logo is protected for the benefit of i

9、ts Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 335 V14.0.0 (2017-04)23GPP TS 29.335 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The

10、 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 fro

11、m the ETSI Secretariat. 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 (

12、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 t

13、heir 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. Modal verbs terminology In the

14、present document “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 delivera

15、bles except when used in direct citation. ETSI ETSI TS 129 335 V14.0.0 (2017-04)33GPP TS 29.335 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Defini

16、tions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 Protocol 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 Sess

17、ion . 9g35.4 Transactions . 9g35.5 SOAP Authentication . 9g36 User Data Convergence Messages . 10g36.1 General . 10g36.2 Query 10g36.3 Create . 10g36.4 Delete . 10g36.5 Update 10g36.6 Subscribe 10g36.7 Notify . 11g36.8 Abandon operation . 12g37 Information Elements . 12g37.1 Information Element Type

18、s with LDAP 12g37.2 Information Elements for Subscriptions and Notifications 12g38 Security. 12g3Annex A (normative): SOAP Subscription and Notification . 14g3A.1 XML schema for Subscribe Request 14g3A.2 XML schema for Subscribe Response . 14g3A.3 XML schema for Notify Request . 15g3A.4 XML schema f

19、or Notify Response . 16g3Annex B (informative): LDAP Message flows and Transaction flows for UDC . 17g3B.1 General LDAP Message flow for UDC 17g3B.2 LDAP Transaction flows for UDC . 17g3Annex C (informative): Messages Based on SOAP 19g3C.1 General . 19g3C.2 Protocol Stack for Messages Based on SOAP

20、. 19g3ETSI ETSI TS 129 335 V14.0.0 (2017-04)43GPP TS 29.335 version 14.0.0 Release 14C.3 SOAP Based Query 20g3C.4 SOAP Based Create 20g3C.5 SOAP Based Delete 20g3C.6 SOAP Based Update 20g3C.7 SOAP Based Abandon . 21g3Annex D (informative): Change history . 22g3History 23g3ETSI ETSI TS 129 335 V14.0.

21、0 (2017-04)53GPP TS 29.335 version 14.0.0 Release 14Foreword This Technical Specification 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

22、 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

23、 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 129 335 V14.0.0 (2017

24、-04)63GPP TS 29.335 version 14.0.0 Release 141 Scope The present document specifies 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 inter

25、actions between the FE and the UDR for Ud reference point, in particular: - The details 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 Da

26、ta Convergence Stage 2 description (architecture and information flows) is specified 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 multivend

27、or interoperability between FEs and UDR specific integration projects are needed. Some 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. - Refere

28、nces 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 GS

29、M document), a non-specific reference implicitly refers to the latest version of that 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“

30、. 4 IETF RFC 4510: “Lightweight Directory Access Protocol (v3)“. 5 IETF RFC 5805: “Lightweight 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 Proto

31、col HTTP/1.1“. 8 IETF RFC 4511: “Lightweight Directory Access Protocol (LDAP): The Protocol“. 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: “Lightweig

32、ht Directory Access Protocol (LDAP): Directory Information Models“. 12. 3GPP TS 32.182: “Telecommunication management; User Data Convergence (UDC); Common Baseline Information Model“. 13 Void 14 Void ETSI ETSI TS 129 335 V14.0.0 (2017-04)73GPP TS 29.335 version 14.0.0 Release 1415 3GPP TS 33.210: “3

33、G Security; Network Domain Security; IP network layer security“. 16 IETF RFC 4513: “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. .

34、18 OASIS “Directory Services Markup Language v2.0“ (30 April 2002) http:/www.oasis-open.org/. 19 3GPP TR 29.935: “Study on UDC Data Model“. 20 OASIS: “ Web Services Security: SOAP Message Security 1.1 OASIS Standard Specification, 1 February 2006“, https:/www.oasis-open.org/committees/download.php/1

35、6790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf. 21 OASIS: “Web Services Security: “UsernameToken Profile 1.1 OASIS Standard Specification, 1 February 2006“, https:/docs.oasis-open.org/wss/v1.1/wss-v1.1-spec-os-UsernameTokenProfile.pdf. 3 Definitions, symbols and abbreviations 3.1 Definitions For the

36、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 definition of the same term, if any, in 3GPP TR 21.905 1. LDAP Session: starts with LDAP Bind Operation and ends with LDAP U

37、nbind 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 repository. Front End Identifier: A name that uniquely identifies an FE within the set of all FEs accessing an UDR. Fron

38、t 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 other characteristics. All FEs within a cluster are treated equally for required purposes (e.g. authorization, notification

39、s, 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. Front End Cluster Identifier: A name that identifies a cluster grouped with FEs supporting the same application. User Dat

40、a 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 reference point between a FE and the UDR 3.3 Abbreviations For the purposes of the present document, the abbreviations give

41、n 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.905 1. FE Front End UDR User Data Repository ETSI ETSI TS 129 335 V14.0.0 (2017-04)83GPP TS 29.335 version 14.0.0 Releas

42、e 14NDS Network Domain Security 4 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 details. Subscription messages and Notification messages on the Ud interface shall make use of SOAP 6. See section 4.3 for

43、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 Protocol Stack for Ud Subscriptions/Notifications Figure 4.3-1 shows the protocol layering used for Ud Subscription/Notificati

44、on. Figure 4.3-1 Protocol Layering for Subscription/Notification ETSI ETSI TS 129 335 V14.0.0 (2017-04)93GPP TS 29.335 version 14.0.0 Release 145 General Messages 5.1 General This section describes common messages for UDC to establish sessions and administrate transactions. For an existing session,

45、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 Front-End shall first establish a transport connection with the UDR. The transport connection shall be a TCP connection. T

46、he 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 of the transport connection, the FE shall initiate a LDAP session by sending a LDAP BindRequest message. The establishme

47、nt 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 BindRequest message. The UDR shall support the “unauthenticated authentication mechanism of simple Bind“ and the “name/pas

48、sword 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 the FE Cluster Identifier. If the FE provided the Front End Identifier the UDR may also derive the Front End Cluster Iden

49、tifier. 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 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 relate a number of update ope