1、 ETSI TR 1Universal Mobile TelStudy on User Data(3GPP TR 29.9TECHNICAL REPORT 129 935 V13.0.0 (2016elecommunications System (LTE; ta Convergence (UDC) data m.935 version 13.0.0 Release 1316-01) (UMTS); a model 13) ETSI ETSI TR 129 935 V13.0.0 (2016-01)13GPP TR 29.935 version 13.0.0 Release 13Referen
2、ce RTR/TSGC-0429935vd00 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 p
3、resent 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/or print versions of the present document shall not be modified without the prior written authorization of
4、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 kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware tha
5、t 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: https:/p
6、ortal.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 mod
7、ified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit
8、 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 registered and owned by the GSM Association. ETSI ETSI TR 129 935 V13.0.0 (2016-01)23GPP TR 29.935 version 13.0.0 Release 13
9、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
10、 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 IPR Policy, no investigation, including IPR searche
11、s, 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 Report (TR) has been produced by ETSI
12、 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, U
13、MTS, 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“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ET
14、SI 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 V13.0.0 (2016-01)33GPP TR 29.935 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Mod
15、al 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 data with a TAS-FE . 9g34.2.3
16、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 12g36.2 Directory Information Tr
17、ee 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 Service Data . 17g310 UDC EPS S
18、ervice 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.2.3 Implicit Registration Set
19、. 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 . 22g3ETSI ETSI TR 129 935 V13.0.0 (2016-01)43GPP TR 29.935 version 13.0.0 Relea
20、se 1311.1.3.3 Implicit Registration Set Data . 23g311.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 Alternative C . 26g311.1.4.1 IMS Su
21、bscription 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.5.1 IMS Private Identity 31g3
22、11.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 37g312 Conclusion and Recomme
23、ndation 40g3Annex A: Change history 42g3History 43g3ETSI ETSI TR 129 935 V13.0.0 (2016-01)53GPP TR 29.935 version 13.0.0 Release 13Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work wit
24、hin 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
25、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 ha
26、ve been incorporated in the document. ETSI ETSI TR 129 935 V13.0.0 (2016-01)63GPP TR 29.935 version 13.0.0 Release 131 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 application and the User Data
27、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 follow the concepts of the Fram
28、ework 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 definition: names, syntax, se
29、mantics; - 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 and Management“ 5 3GPP TS 23.0
30、08: “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 point“ ETSI ETSI TR 129 935 V13.0
31、.0 (2016-01)73GPP TR 29.935 version 13.0.0 Release 1310 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 description“ 12 3GPP TS 29.272
32、: “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 Network (E-UTRAN) access“ 14 3GPP T
33、S 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 IETF RFC 1035: “DOMAIN NAMES - I
34、MPLEMENTATION 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 Initiation Protocol“ 21 IETF RF
35、C 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 contents“ 25 3GPP TS 23.845: “Study o
36、n 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 over the definition of the same
37、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 abbreviations given in TR 21.905 1 and t
38、he 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 Reference Data Model TAS Telephony Ap
39、plication Server ETSI ETSI TR 129 935 V13.0.0 (2016-01)83GPP TR 29.935 version 13.0.0 Release 13UDC 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 4517 6 or a derived syntax that
40、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 (mixed case with first letter of
41、 word capitalized), e.g. NumericString. ETSI ETSI TR 129 935 V13.0.0 (2016-01)93GPP TR 29.935 version 13.0.0 Release 13Derived Syntax name Description UInt8 This syntax is derived from the Integer syntax 6. The structure is further constrained to a maximum length of 1 and the values are further cons
42、trained 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. The structure is further constr
43、ained 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 to F. HexString32 This syntax is d
44、erived 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 structure is further constrained to a m
45、aximum 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 maximum length of 63 characters. CaseI
46、gnore 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 constrained to the decimal digits (0 throu
47、gh 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 consecutive zero groups collapsed into a
48、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. IPv6Prefix This syntax is derived from the Printabl
49、eString 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 or characters A to F, th
