ETSI TR 129 935-2017 Universal Mobile Telecommunications System (UMTS) LTE Study on User Data Convergence (UDC) data model (V14 0 0 3GPP TR 29 935 version 14 0 0 Release 14)《通用移动通信_1.pdf

1、 ETSI TR 129 935 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Study on User Data Convergence (UDC) data model (3GPP TR 29.935 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 129 935 V14.0.0 (2017-04)13GPP TR 29.935 version 14.0.0 Release 14Reference RTR/TSGC-042

2、9935ve00 Keywords 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 Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document

3、 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/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case o

4、f 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 kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document

5、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.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal

6、.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 photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified

7、 without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of i

8、ts 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 its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 129 935 V14.0.0

9、 (2017-04)23GPP TR 29.935 version 14.0.0 Release 14Intellectual 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

10、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 (https:/ipr.etsi.org/). Pursuant to the ETSI

11、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 T

12、his Technical Report (TR) 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 ET

13、SI 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 “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as desc

14、ribed 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 TR 129 935 V14.0.0 (2017-04)33GPP TR 29.935 version 14.0.0 Release 14Contents Intellectual Propert

15、y Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 General considerations . 8g34.1 General syntax definitions 8g34.2 MMTEL data 9g34.2.1 Introduction. 9g34.2.2 MMTEL d

16、ata with a TAS-FE . 10g34.2.3 MMTEL data with an HSS-FE . 10g34.2.4 MMTEL Data and CS Supplementary Services data 10g34.2.5 Supplementary Services RDM principle . 10g35 Identifier . 12g35.1 Object classes and their attributes 12g36 UDC Service Profile . 12g36.1 Object classes and their attributes 12

17、g36.2 Directory Information Tree 13g36.2.1 Alternative A 13g36.2.2 Alternative B . 13g36.2.3 Alternative C . 14g36.2.4 Alternative D 15g37 UDC Service Data shared by several domains . 16g37.1 Object classes and their attributes 17g37.1.1 AuC Subscriber Data 17g38 UDC CS Service Data 17g39 UDC GPRS S

18、ervice Data . 17g310 UDC EPS Service Data 17g311 UDC IMS Service Data 18g311.1 Object classes and their attributes 18g311.1.1 General 18g311.1.2 Alternative A 18g311.1.2.1 IMS Data . 18g311.1.2.2 Service Profile Data 19g311.1.2.2.1 Service Profile . 19g311.1.2.2.2 Initial Filter Criteria . 19g311.1.

19、2.3 Implicit Registration Set . 20g311.1.2.4 Public Identity . 20g311.1.2.5 Private Identity 21g311.1.3 Alternative B . 21g311.1.3.1 IMS Data . 21g311.1.3.2 Service Profile Data 22g311.1.3.2.1 Service Profile . 22g311.1.3.2.2 Initial Filter Criteria . 22g311.1.3.3 Implicit Registration Set Data . 23

20、g3ETSI ETSI TR 129 935 V14.0.0 (2017-04)43GPP TR 29.935 version 14.0.0 Release 1411.1.3.3.1 Implicit Registration Set 23g311.1.3.3.2 Alias Group . 23g311.1.3.3 Public Identity. 23g311.1.3.4 Repository Data . 24g311.1.3.5 Private Identity 25g311.1.3.6 Reference Location Information . 25g311.1.4 Alter

21、native C . 26g311.1.4.1 IMS Subscription 26g311.1.4.2 Service Profile . 26g311.1.4.3 Initial Filter Criteria 27g311.1.4.4 Implicit Registration Set . 28g311.1.4.5 Public Identity . 28g311.1.4.6 Repository Data. 29g311.1.4.7 Alias Group. 30g311.1.4.8 Private Identity 30g311.1.5 Alternative D 31g311.1

22、.5.1 IMS Private Identity 31g311.1.5.2 IMS Public Identity . 32g311.1.5.3 IMS Service Profile . 33g311.1.5.4 Alias Group . 33g311.2 Directory Information Tree 33g311.2.0 General 33g311.2.1 Alternative A 33g311.2.2 Alternative B . 35g311.2.3 Alternative C . 36g311.2.4 Alternative D 37g311.3 UML model

23、 37g312 Conclusion and Recommendation 40g3Annex A: Change history 42g3History 43g3ETSI ETSI TR 129 935 V14.0.0 (2017-04)53GPP TR 29.935 version 14.0.0 Release 14Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are

24、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 fi

25、rst 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

26、when editorial only changes have been incorporated in the document. ETSI ETSI TR 129 935 V14.0.0 (2017-04)63GPP TR 29.935 version 14.0.0 Release 141 Scope The present document analyses and evaluates the definition of a Reference Data Model (RDM) for Ud interface between Front-Ends (FEs) for the HSS

27、application and the User Data Repository (UDR). The stage 3 of the Ud interface in the User Data Convergence (UDC architecture) is defined in 3GPP TS 29.335 2. The Reference Data Model (RDM) shall comply with the Common Baseline Information Model for UDC as defined in 3GPP TS 32.182 3 and it shall f

28、ollow the concepts of the Framework for Model Handling and Management as defined in 3GPP TS 32.181 4. The analysis will comprise the general considerations impacting the RDM for HSS. The analysis will comprise the following topics: - The general considerations impacting the RDM for HSS; - Attributes

29、 definition: names, syntax, semantics; - Object classes User Data Repository Access Protocol over the Ud interface“ 3 3GPP TS 32.182: “Telecommunication management; User Data Convergence (UDC); Common Baseline Information Model“ 4 3GPP TS 32.181: “User Data Convergence; Framework for Model Handling

30、and Management“ 5 3GPP TS 23.008: “Organization of subscriber data“ 6 IETF RFC 4517: “Syntaxes and Matching Rules“ 7 3GPP TS 23.003: “Numbering, addressing and identification“ 8 IETF RFC 4291: “IP Version 6 Addressing Architecture“ 9 3GPP TS 29.214: “Policy and Charging Control over Rx reference poi

31、nt“ ETSI ETSI TR 129 935 V14.0.0 (2017-04)73GPP TR 29.935 version 14.0.0 Release 1410 3GPP TS 32.251: “Telecommunication management; Charging management; Packet Switched (PS) domain charging“ 11 3GPP TS 32.298: “Telecommunication management; Charging management; Charging Data Record (CDR) parameter

32、description“ 12 3GPP TS 29.272: “Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol“ 13 3GPP TS 23.401: “General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Netwo

33、rk (E-UTRAN) access“ 14 3GPP TS 23.060: “General Packet Radio Service (GPRS); Service description; Stage 2“ 15 3GPP TS 36.413: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“ 16 3GPP TS 29.212: “Policy and Charging Control over Gx reference point“ 17 IE

34、TF RFC 1035: “DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION“ 18 3GPP TS 23.015: “Technical realization of Operator Determined Barring (ODB)“ 19 3GPP TS 29.364: “IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability“ 20 IETF RFC 3261 “SIP: Session I

35、nitiation Protocol“ 21 IETF RFC 2396: “Uniform Resource Identifiers (URI): generic syntax“ 22 IETF RFC 3966 “The tel URI for Telephone Numbers“ 23 IETF RFC 4282: “The Network Access Identifier“ 24 3GPP TS 29.228: “IP Multimedia (IM) Subsystem Cx and Dx interface; signalling flows and message content

36、s“ 25 3GPP TS 23.845: “Study on User Data Convergence (UDC) evolution“ 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence ov

37、er the definition of the same term, if any, in TR 21.905 1. Reference Data Model for HSS: Reference Data Model for HSS is an Application Data Model that operations on Ud interfaces supporting HSS applications shall comply to. 3.2 Abbreviations For the purposes of the present document, the abbreviati

38、ons given in 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 TR 21.905 1. CB Call Barring CDIV Call DiversionLDAP Lightweight Directory Access Protocol MMTEL Multimedia TelephonyRDM Referen

39、ce Data Model TAS Telephony Application Server ETSI ETSI TR 129 935 V14.0.0 (2017-04)83GPP TR 29.935 version 14.0.0 Release 14UDC User Data Convergence 4 General considerations 4.1 General syntax definitions The LDAP attributes in this document are defined as having a syntax specified in IETF RFC 45

40、17 6 or a derived syntax that will be specified in this section. The description of a derived syntax will contain the name of the IETF RFC 4517 6 syntax from which it was derived as well as any additional structure and value constraints. Syntax names should follow the rules set by IETF RFC 4517 6 (m

41、ixed case with first letter of word capitalized), e.g. NumericString. ETSI ETSI TR 129 935 V14.0.0 (2017-04)93GPP TR 29.935 version 14.0.0 Release 14Derived Syntax name Description UInt8 This syntax is derived from the Integer syntax 6. The structure is further constrained to a maximum length of 1 a

42、nd the values are further constrained from 0 to 255. UInt16 This syntax is derived from the Integer syntax syntax 6. The structure is further constrained to a maximum length of 2 and the values are further constrained from 0 to 65535. UInt32 This syntax is derived from the Integer syntax syntax 6. T

43、he structure is further constrained to a maximum length of 4 and the values are further constrained from 0 to 4294967295. HexString This syntax is derived from the PrintableString syntax 6. The values are further constrained to the decimal digits (0 through 9), characters “a” to “f” or characters “A

44、” to “F”. HexString32 This syntax is derived from the HexString syntax. The structure is further constrained to a maximum length of 32 characters. FQDN This syntax is used to represent an Fully Qualified Domain Name (FQDN) (see IETF RFC1035 17) and is derived from the PrintableString syntax 6. The s

45、tructure is further constrained to a maximum length of 255 and the values are further constrained to one or more labels separated by the period (“.“) character. Each label consists of the decimal digits (0 through 9), characters “a“ to “z“, characters “A“ to “Z“, the hyphen (“-) character and has a

46、maximum length of 63 characters. CaseIgnore IPv4Address This syntax is derived from the PrintableString syntax 6 and is used to represent IPv4 addresses formatted in dot-decimal notation without leading zeros. The structure is further constrained to a maximum length of 15 and values are further cons

47、trained to the decimal digits (0 through 9) and the period (.) character. IPv6Address This syntax is derived from the PrintableString syntax 6 and is used to represent IPv6 addresses formatted in hexadecimal colon-separated notation without leading zeros in each group and with the largest run of con

48、secutive zero groups collapsed into a single empty group (see IETF RFC 4291 8). The structure is further constrained to a maximum length of 39 and the values are further constrained to the decimal digits (0 through 9), characters “a” to “f” or characters “A” to “F” and the colon (:) character. IPv6P

49、refix This syntax is derived from the PrintableString syntax 6 and is used to represent an IPv6 prefix formatted in CIDR (Classless Inter-domain Routing) notation, i.e. an IPv6 address (formatted in IPv6Address syntax), a slash (/) character and a decimal value indicating the size in bits of the address prefix (see IETF RFC 4291 8). The structure is further constrained to a maximum length of 43 and the values are further constrained to the decimal digits (0 through 9), characters “a” to “f