1、 ETSI TS 132 181 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management (3GPP TS 32.181 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 181 V14.0.0 (2017-04)1
2、3GPP TS 32.181 version 14.0.0 Release 14Reference RTS/TSGS-0532181ve00 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
3、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 document shall not be modif
4、ied 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. Us
5、ers 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 document, please sen
6、d 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 by written permission
7、 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, PLUGTESTSTM, UMTSTMand the ETS
8、I 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 Trade Marks registered
9、and owned by the GSM Association. ETSI ETSI TS 132 181 V14.0.0 (2017-04)23GPP TS 32.181 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
10、 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
11、 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
12、, 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 their 3GPP identities, UMTS identities or GSM identities. Th
13、ese 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 “shall“, “shall not“, “should“, “should no
14、t“, “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 ETSI TS 132
15、181 V14.0.0 (2017-04)33GPP TS 32.181 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 UDC Framework over
16、view 8g34.1 General overview . 8g34.2 Requirements coming from other Specifications . 8g34.3 Overview of UDC Data and Information Models 8g35 UDC information model infrastructure 10g35.1 Common Baseline Information Model (CBIM) . 10g35.2 Application Information Models (AIM) . 10g35.3 Specialised Inf
17、ormation Model (SpIM) 11g36 UDC information model handling 11g36.1 General . 11g36.2 Initial SpIM Creation from CBIM 13g36.3 AIM Integration into SpIM 13g36.4 Consolidation of User Data in the SpIM 13g36.5.1 Example of consolidation of data in the SpIM using aggregation 13g36.5.2 Example of speciali
18、zation for authentication methods . 14g36.5.3.1 AkaUsim . 15g36.5.3.1.1 Definition. 15g36.5.3.2 CsAka 15g36.5.3.2.1 Definition. 15g36.5.3.3 GPRSAka 15g36.5.3 3.1 Definition. 15g36.5.3.4 EpsAka 16g36.5.3.4.1 Definition. 16g36.5.3.5 ImsAkaIsim . 16g36.5.3.5.1 Definition. 16g36.5.3.6 ImsAka 16g36.5.3.6
19、.1 Definition. 16g36.5.3.7 ImsAkaUsimIsim 16g36.5.3.7.1 Definition. 16g36.5.3.8 GPRSImsBundled . 16g36.5.3.8.1 Definition. 16g36.5.3.9 NassImsBundled . 16g36.5.3.9.1 Definition. 16g36.5.3.10 SipDigest . 17g36.5.3.10.1 Definition. 17g36.5 Construction of AIM 17g37 Application management 17g37.1 Appli
20、cation Access Control Data . 17g37.2 Application Data Model and Mapping to Consolidated Data Model . 17g37.2.1 Application Data Views 17g37.3 Subscription and Notification Related Data . 19g3ETSI ETSI TS 132 181 V14.0.0 (2017-04)43GPP TS 32.181 version 14.0.0 Release 148 Consolidated data model mana
21、gement . 20g38.1 Lifecycle Management of the Consolidated Data Model in the UDR 20g38.2 Activation and Deactivation of Application Adaptation 21g39 Relation to other Information Models 22g39.1 Relation to SuM Network Resource Model 22g3Annex A (informative): Change history . 23g3History 24g3ETSI ETS
22、I TS 132 181 V14.0.0 (2017-04)53GPP TS 32.181 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 appro
23、val. 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 o
24、r 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. Introduction “T
25、he User Data Convergence concept supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends. Network elements and f
26、unctionalities should be designed to access profile data remotely and without storing them permanently locally, i.e. the front-ends shall work in a user dataless configuration.“ TR 22.985 and TS 22.101 provide the requirements for User data convergence so that user data can be moved from where it or
27、iginated, to a facility called User Data Repository (UDR) where it can be accessed, stored and managed in a common way. Convergence of user data unifies the user data access interface and its protocol. In addition, the logical centralization of user data implies the support of user data provisioning
28、, that is, user data manipulation like creation, deletion, reading, modification and other operations. In order to accommodate multiple applications and services, existing and new ones, a framework for model handling and management of the UDC has been developed including: - UDC information model inf
29、rastructure - UDC information model handling - Application management - Consolidated data model management. ETSI ETSI TS 132 181 V14.0.0 (2017-04)63GPP TS 32.181 version 14.0.0 Release 141 Scope The present document specifies the framework for overall management of the User Data Convergence. In orde
30、r to accommodate multiple applications and services, existing and new ones, the framework for model handling and management of the UDC as identified by TS 22.101 includes the following items: - UDC information models: - UDC information model infrastructure containing the common baseline information
31、model (CBIM), application information models (AIM), and the specialised information model (SIM). The CBIM is standardised in TS 32.cde 4. - UDC information model handling: - provide a template and guidelines explaining the design of application information models to be used together with the common
32、baseline information model to create the specialized information model - describe the process to combine the common baseline information model with application information models in order to produce an operator-specific specialised information model - Application management data: - access control da
33、ta for an application to UDC: identification and authentication - assignment to an application data model, including linkage to the consolidated data model - subscription rights for specific events on specific data of specific users - Consolidated data model management - lifecycle management of the
34、consolidated data model in the UDR and in the provisioning entity. - activation/deactivation of application adaptation 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (ident
35、ified 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 ref
36、erence 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 22.985: “Service requirement for the User Data Convergence (UDC)“. 3 3GPP TS 22.101: “Service aspects; Service principles“. 4
37、 3GPP TS 32.182: “User Data Convergence; Common Baseline Information Model “. 5 3GPP TR 32.808: “Study of Common Profile Storage (CPS) Framework of User Data for network services and management“ 6 3GPP TS 33.102: “3G Security; Security architecture” 7 3GPP TS 33.203: “3G security; Access security fo
38、r IP-based services” ETSI ETSI TS 132 181 V14.0.0 (2017-04)73GPP TS 32.181 version 14.0.0 Release 148 3GPP TS 23.335: “User Data Convergence; Technical Realization and Information Flows;Stage 2“ 9 3GPP TS 29.335: “User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interfac
39、e; Stage 3” 10 3GPP TS 32.172: “Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)” 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the fol
40、lowing apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Application Data Model : specific data model used by an application accessing the UDR. It is defined according to the UDC access protocol. It is related to an applicati
41、on information model. Application Data View: a function of the UDR that enables and limits applications access to data within the UDR. Application Information Model : specific information model used by an application accessing the UDR. It is defined with the same method as the common baseline inform
42、ation model. It is related to an application data model. Common Baseline Information Model: basic structure of UDC IOCs, see also definition in 3GPP TS 32.182 4 Consolidated Data Model: Data model containing all data of the User Data Repository. It is the result of the implementation of the entire S
43、pecialized Information Model in the UDR for all applications. Information Model: Information Model denotes an abstract, formal representation of entity types, including their properties and relationships, the operations (e.g. read, write) that can be performed on them, and related rules and constrai
44、ns. In the information model, entities might have network topology relationship with each other. Specialized Information Model: Information model containing all information to be stored in the UDR. It is the result of operator specific specialisation of CBIM with addition of imported AIM. 3.2 Abbrev
45、iations 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. ADM Application Data Model AIM Application Informat
46、ion Model AKA Authentication and Key Agreement AMF Authentication Management Field CBIM Common baseline Information Model CDM Consolidated Data Model ISIM IMS Subscriber Identity Module SpIM Specialised Information Model UDC User Data Convergence UDR User Data Repository UICC Universal Integrated Ci
47、rcuit Card USIM Universal Subscriber Identity Module ETSI ETSI TS 132 181 V14.0.0 (2017-04)83GPP TS 32.181 version 14.0.0 Release 144 UDC Framework overview 4.1 General overview TR 22.985 2 and TS 22.1013 request the baseline information model to be future proof and extensible, i.e. new applications
48、 and/or new service profiles can be added by the operator, if necessary. The flexibility shall also permit new data for existing applications to be introduced, or modified. For the actual information model of an operator Specialized Information Model is described in TR 22.985 2. For the above purpos
49、e this specification defines and describes the infrastructure of UDC Information Models in Clause 5. The correlation and handling of the UDC Information Models is described in Clause 6. 4.2 Requirements coming from other Specifications TR 22.985 2 and TS 22.1013 provide requirements for CBIM and SpIM . These documents also mention the Application Data Models for the Access Interface to the UDC. Specification 23.335 8 in Clause 5.2 defines the requirements for application access to the UDR including authentication and authorisation
