|
TECHNICAL REPORT
Universal Mobile Telecommunications System (UMTS);
LTE;
Study on User Data Convergence (UDC) data model
(3GPP TR 29.935 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 1 ETSI TR 129 935 V15.0.0 (2018-10)
Reference
RTR/TSGC-0429935vf00
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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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 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 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
If you find errors in the present document, please send your comment to one of the following services:
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 without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks 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 trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 2 ETSI TR 129 935 V15.0.0 (2018-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 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 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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This 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 ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "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 when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 3 ETSI TR 129 935 V15.0.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 General considerations . 8
4.1 General syntax definitions . 8
4.2 MMTEL data . 8
4.2.1 Introduction. 8
4.2.2 MMTEL data with a TAS-FE . 9
4.2.3 MMTEL data with an HSS-FE . 9
4.2.4 MMTEL Data and CS Supplementary Services data . 9
4.2.5 Supplementary Services RDM principle . 9
5 Identifier . 11
5.1 Object classes and their attributes . 11
6 UDC Service Profile . 11
6.1 Object classes and their attributes . 11
6.2 Directory Information Tree . 12
6.2.1 Alternative A . 12
6.2.2 Alternative B . 12
6.2.3 Alternative C . 13
6.2.4 Alternative D . 14
7 UDC Service Data shared by several domains . 15
7.1 Object classes and their attributes . 16
7.1.1 AuC Subscriber Data . 16
8 UDC CS Service Data . 16
9 UDC GPRS Service Data . 16
10 UDC EPS Service Data . 16
11 UDC IMS Service Data . 17
11.1 Object classes and their attributes . 17
11.1.1 General . 17
11.1.2 Alternative A . 17
11.1.2.1 IMS Data . 17
11.1.2.2 Service Profile Data . 18
11.1.2.2.1 Service Profile . 18
11.1.2.2.2 Initial Filter Criteria . 18
11.1.2.3 Implicit Registration Set . 19
11.1.2.4 Public Identity . 19
11.1.2.5 Private Identity . 20
11.1.3 Alternative B . 20
11.1.3.1 IMS Data . 20
11.1.3.2 Service Profile Data . 21
11.1.3.2.1 Service Profile . 21
11.1.3.2.2 Initial Filter Criteria . 21
11.1.3.3 Implicit Registration Set Data . 22
11.1.3.3.1 Implicit Registration Set . 22
ETSI
---------------------- Page: 4 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 4 ETSI TR 129 935 V15.0.0 (2018-10)
11.1.3.3.2 Alias Group . 22
11.1.3.3 Public Identity . 22
11.1.3.4 Repository Data . 23
11.1.3.5 Private Identity . 24
11.1.3.6 Reference Location Information . 24
11.1.4 Alternative C . 25
11.1.4.1 IMS Subscription . 25
11.1.4.2 Service Profile . 25
11.1.4.3 Initial Filter Criteria . 26
11.1.4.4 Implicit Registration Set . 27
11.1.4.5 Public Identity . 27
11.1.4.6 Repository Data . 28
11.1.4.7 Alias Group . 28
11.1.4.8 Private Identity . 28
11.1.5 Alternative D . 29
11.1.5.1 IMS Private Identity . 29
11.1.5.2 IMS Public Identity . 30
11.1.5.3 IMS Service Profile . 31
11.1.5.4 Alias Group . 31
11.2 Directory Information Tree . 31
11.2.0 General . 31
11.2.1 Alternative A . 31
11.2.2 Alternative B . 32
11.2.3 Alternative C . 33
11.2.4 Alternative D . 34
11.3 UML model . 34
12 Conclusion and Recommendation . 37
Annex A: Change history . 39
History . 40
ETSI
---------------------- Page: 5 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 5 ETSI TR 129 935 V15.0.0 (2018-10)
Foreword
rd
This Technical Report has been produced by the 3 Generation 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 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 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
---------------------- Page: 6 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 6 ETSI TR 129 935 V15.0.0 (2018-10)
1 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 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 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 definition: names, syntax, semantics;
- Object classes & Directory Information Tree: object classes names, attributes grouping, LDAP entries,
Distinguished Names and Relative Distinguished Names.
Directory information trees, object classes and attributes in this report should be considered informative since they are
subject to additions and/or modification depending on the specific implementation as illustrated in the presented
alternatives in this technical report. Even the assignment of attributes to object classes may be redistributed, for
example,because the normalization of object classes across different domains may result in attributes being moved to a
superclass. Naming is provisional. Diagrams used and naming convention are not standardized.
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 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 that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"
[2] 3GPP TS 29.335: "User Data Convergence (UDC);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.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 point"
[10] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched
(PS) domain charging"
ETSI
---------------------- Page: 7 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 7 ETSI TR 129 935 V15.0.0 (2018-10)
[11] 3GPP TS 32.298: "Telecommunication management; Charging management; Charging Data
Record (CDR) parameter 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 Network (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] IETF 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 Initiation 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 contents"
[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 over 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 abbreviations 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 Diversion
LDAP Lightweight Directory Access Protocol
MMTEL Multimedia Telephony
RDM Reference Data Model
TAS Telephony Application Server
UDC User Data Convergence
ETSI
---------------------- Page: 8 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 8 ETSI TR 129 935 V15.0.0 (2018-10)
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 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 word capitalized), e.g. NumericString.
Derived 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 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]. The 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" 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 structure 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 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 constrained 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 consecutive 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.
IPv6Prefix 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" or characters "A" to "F", the colon (:)
character and the slash (/) character.
Name10 This syntax is derived from the PrintableString syntax [6]. The structure is further
constrained to a maximum length of 10 characters. CaseIgnore.
String This syntax corresponds to Printable String syntax according to IETF RFC 4517 [6].
Enumerated This syntax corresponds to Numeric String syntax according to IETF RFC 4517 [6],
where the maximum length is defined by the number of included numerals.
Table 4.1-1
4.2 MMTEL data
4.2.1 Introduction
The specification of the MMTEL data in the Reference Data Model over Ud has to define for which Application FEs it
will be applied. Two cases are identified.
- MMTEL data specification over Ud applies to the Ud interface between a Telephony Application Server Front-
end (TAS-FE) and the UDR.
ETSI
---------------------- Page: 9 ----------------------
3GPP TR 29.935 version 15.0.0 Release 15 9 ETSI TR 129 935 V15.0.0 (2018-10)
- MMTEL data specification over Ud applies to the Ud interface between a HSS-FE (supporting IMS) and the
UDR.
4.2.2 MMTEL data with a TAS-FE
The Ud interface supported by a TAS is an alternative way to store its MMTEL data in a UDR instead of using the Sh
interface and an HSS-FE. For this purpose another protocol (i.e. reusing Ud protocol) to centrally store MMTEL Data in
addition to Sh has to be assessed and confirmed. This is out of the scope in the present release of the specifications.
4.2.3 MMTEL data with an HSS-FE
With a HSS-FE, MMTEL data are transported over a Sh interface as transparent data within repository data. Then,
regarding to the storage on the UDR by the HSS-FE, two sub-cases are identified:
- It is normally stored as transparent data in the UDR in the same way as any other transparent data coming from
an AS over Sh, so not requiring a data modelling of the MMTEL data over the Ud between a HSS-FE and the
UDR.
- The transparent data is analysed by the HSS-FE application logic and translated into data complying with the
MMTEL RDM over Ud. In the other way, the HSS-FE application logic builds a Sh transparent data from t
...