1、 ETSI TR 132 901 V14.0.0 (2017-05) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases (3GPP TR 32.901 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 132 90
2、1 V14.0.0 (2017-05)13GPP TR 32.901 version 14.0.0 Release 14Reference RTR/TSGS-0532901ve00 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
3、e 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/or print versions of the present documen
4、t 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
5、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.aspx If you find errors in the present
6、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 photocopying and microfilm except as authorized b
7、y 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. All rights reserved. DECTTM, PLUGTESTST
8、M, 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 its Members GSM and the GSM logo are Tra
9、de Marks registered and owned by the GSM Association. ETSI ETSI TR 132 901 V14.0.0 (2017-05)23GPP TR 32.901 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 essent
10、ial 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
11、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)
12、which are, or may be, or may become, essential to the present document. 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 i
13、dentities. 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 “should“, “should not“, “may“
14、, “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 TR 132 901 V14.0
15、.0 (2017-05)33GPP TR 32.901 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 8g33 Definitions and abbreviations . 8g33.1 Abbreviations . 8g34 Example SpIMs 10g34.1 Example SpIM for Preferred Currency 10g3
16、4.2 Example SpIM for User Name . 10g35 Applications . 11g35.1 Application Information Models (AIM) . 11g35.1.1 Information Object Classes . 11g35.1.1.0 General 11g35.1.1.1 UdcASServiceProfile 12g35.1.1.2 UDCBasicServiceProfile. 12g35.1.1.3 UDCCSCFServiceProfile 12g35.1.1.4 UdcHSSServiceProfile 12g35
17、.1.1.5 UdcSpecialServicesProfile 12g35.1.1.6 UdcCSServiceProfile 12g35.1.1.7 UdcEPSServiceProfile 12g35.1.1.8 UdcGPRSServiceProfile . 12g35.1.1.9 UdcIMSServiceProfile 12g35.1.1.10 UdcMMTelServiceProfile . 12g35.1.2 CS/GPRS 13g35.1.2.1 HLR. 13g35.1.3 EPS . 13g35.1.3.1 HSS . 13g35.1.4 IMS . 14g35.1.4.
18、1 CSCF . 14g35.1.4.2 MMTel 14g35.2 SPIM Level 14g35.2.1 Preferred Currency Use Case 14g35.2.1.1 Setting or modification of the value of this data item . 15g35.2.1.2 Scenarios for use of the data element 15g35.2.2 Age and Birth Date Use Case . 15g35.2.2.1 Setting or modification of the value of this
19、data item . 15g35.2.2.2 Scenarios for use of the Age data element 15g35.2.3 Name Use Case. 16g35.2.3.1 Input for Name 16g35.2.3.2 Scenarios for use of the data element Name . 16g35.2.4 Gender Use Case . 16g35.2.4.1 Setting or modification of the value of this data item . 16g35.2.4.2 Scenarios for us
20、e of the data element 16g35.2.5 Preferred Language Use Case . 16g35.2.5.1 Setting or modification of the value of this data item . 17g35.2.5.2 Scenarios for use of the data element 17g35.2.6 Friend/Friends List Use Case 17g35.2.6.1 Setting or modification of the value of this data item . 17g35.2.6.2
21、 Scenarios for use of the data element 17g36 Recommendations regarding provisioning guidelines and requirements . 18g3ETSI ETSI TR 132 901 V14.0.0 (2017-05)43GPP TR 32.901 version 14.0.0 Release 14Annex A: Change history 19g3History 20g3ETSI ETSI TR 132 901 V14.0.0 (2017-05)53GPP TR 32.901 version 1
22、4.0.0 Release 14Foreword This Technical Report 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 documen
23、t, 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
24、. 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 TR 132 901 V14.0.0 (2017-05)63GPP TR 32.901 version 14.0.0 Release
25、141 Scope 3GPP TR 22.985 Service requirement for the UDC 5 describes the architecture of the User Data Convergence, a concept that proposes to move the user data from where it has been distributed and siloed in Network Elements, Applications, and other network resources to a single logical consolida
26、ted facility here called User Data Repository (UDR) where it can be accessed, stored and managed in a common way. The introduction of a User Data Convergence of user data for network services and management applications could significantly enhance the ability of 3GPP based networks to offer complex
27、and combined services. User data can be decomposed and reformed by a common data model framework (e.g. tree-like data model, rational data model) provided by UDR. In that case, user data categorized by services can be regrouped and identified by user ID, leaving no data redundancy. Also, convergence
28、 in data model will unify the user data access interface and its protocol, which will promote new service application development. Thereby, the capability of user data convergence can be open to creation of data-less applications. Methods for data protection against access by unauthorized parties ar
29、e outside the scope of this document. 3GPP TS 32.181 UDC Framework for Model Handling and Management 3 and 3GPP TS 29.335 UDC; User Data Repository Access Protocol over the Ud interface; Stage 3 4 provide various types of information and data models associated with the architecture of UDC. These inc
30、lude the Common Baseline Information Model (CBIM) (see 3GPP TS 32.182 7), the Specialized Information Model (SpIM), Application Information Models (AIMs), Application Data Models (ADMs), and the Consolidated Data Model (CDM) of the User Data Repository (UDR). Figure 1 from 3GPP TS 32.181 UDC Framewo
31、rk for Model Handling and Management 3 shows the operational environment of the UDC. Figure 1.1: Evolution of the CDM in a UDR BSSGenerate new CDMAppl 1Appl2newApplnew AIMnew AIMGenerate ADM and mapping and new SpIMSpIMSpIMUdUdUdData Model(CDM)Appl1ViewAPPL2viewAPPL 3 viewAPPLnviewFullDataVi ewProvi
32、sioningGatewayConsolidatedETSI ETSI TR 132 901 V14.0.0 (2017-05)73GPP TR 32.901 version 14.0.0 Release 14In addition to the models previously mentioned, Figure 1.1 introduces the aspect of the Provisioning Gateway, which is essential for the operation of the UDR. The Provisioning Gateway provides a
33、single logical point for access to provisioning of user data for all services in the UDR. The Provisioning Gateway is shown supporting an interaction with the operators BSS; by implication this interaction is associated with the provisioning of user subscription and service data in the UDR via the P
34、rovisioning Gateway. This study analyzes the progression of information models displayed in the above figure using some specific application examples, in particular the applications of HSS-IMS and MMTel. It provides guidelines and preliminary requirements for the BSS provisioning capabilities and in
35、formation model handling when new applications and related services are implemented in the operators UDR by doing the following: - Develop several example initial SpIMs for discussion purposes. - Examine what BSS interactions with the Provisioning Gateway would be required to support provisioning of
36、 user service and subscription data in the UDR for these SpIMs. - Study the relationship to the information model of 3GPP TS 32.172 Subscription Management (SuM) Network Resource Model (NRM) IRP Information Service 9. - Develop understanding of CBIM-derived entities of Application Information Models
37、 (AIM) for HSS-IMS and MMTel from application data elements available in 3GPP TS 29.364 IMS Application Server service data descriptions for AS interoperability 11, 3GPP TS 23.008 Organization of subscriber data 12, and other relevant specifications. - Discuss the integration and consolidation of th
38、ese AIM entities with the example initial SpIMs above. - Evaluate the potential changes to the BSS provisioning interactions for the implementation of HSS-IMS and MMTel applications in the UDR and implications concerning the information model of 3GPP TS 32.172 Subscription Management (SuM) Network R
39、esource Model (NRM) IRP Information Service 9. This study does not derive findings concerning the Ud reference point, the subject of 3GPP TR 23.845 Study on UDC Evolution 10. ETSI ETSI TR 132 901 V14.0.0 (2017-05)83GPP TR 32.901 version 14.0.0 Release 142 References The following documents contain p
40、rovisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication and/or edition number or version number) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-spe
41、cific 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“
42、. 2 3GPP TS 23.335: “User Data Convergence (UDC); Technical realization and information flows; Stage 2“. 3 3GPP TS 32.181: “User Data Convergence (UDC); Framework for Model Handling and Management“. 4 3GPP TS 29.335: “User Data Convergence (UDC); User Data Repository Access Protocol over the Ud inte
43、rface; Stage 3“. 5 3GPP TR 22.985: “Service requirement for the User Data Convergence (UDC)“. 6 3GPP TS 22.101: “Service aspects; Service principles“. 7 3GPP TS 32.182: “User Data Convergence; Common Baseline Information Model“. 8 3GPP TR 32.808: “Study of Common Profile Storage (CPS) Framework of U
44、ser Data for network services and management“. 9 3GPP TS 32.172: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 10 3GPP TR 23.845: “Study on UDC Evolution“. 11 3GPP TS 29.364: “IP Multimedia System (IMS) Application Server (A
45、S) service data descriptions for AS interoperability“. 12 3GPP TS 23.008: “Organization of subscriber data“. 3 Definitions and abbreviations 3.1 Abbreviations For the purposes of the present document, the following abbreviations apply: AIM Application Information Model ADM Application Data Model BSS
46、 Business Support System CBIM Common Baseline Information Model CDM Consolidated Data Model CPS Common Profile Storage FE Front End HSS Home Subscriber Server IMS IP Multimedia System IRP Integration Reference Point IS Information Service ETSI ETSI TR 132 901 V14.0.0 (2017-05)93GPP TR 32.901 version
47、 14.0.0 Release 14LDAP Lightweight Directory Access Protocol MMTel MultiMedia TelephonyNRM Network Resource Model RDM Reference Data Model SpIM Specialized Information Model SuM Subscription Management UDC User Data Convergence UDR User Data Respository ETSI ETSI TR 132 901 V14.0.0 (2017-05)103GPP T
48、R 32.901 version 14.0.0 Release 144 Example SpIMs 4.1 Example SpIM for Preferred Currency A user can request that any charging or pricing information be provided using a specific currency. The method is operator specific, but the example shown below is typical of what would transpire to derive the S
49、pIM and resulting Data Model. Specialized IM (SpIM) for User Currency Preferrence Appl IM (AIM) Operator currency selection process CBIM information for currency selection Integrate AIM into SpIM and consolidate 4.2 Example SpIM for User Name A user can request that his/her name be made available for messaging and special services as a particular value, e.g. “Jane M. Doe”, or “Dr. Terry W. Smith IV”. The method is operator specific, but the example shown below is typical of what would transpire to derive the SpIM and resulting Da
