ETSI TS 132 181-2016 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management User Data Convergence (UDC) Framework for Model Handling and Management (V13.pdf

1、 ETSI TS 1Universal Mobile TelTelecommUser DatFramework for M(3GPP TS 32.1TECHNICAL SPECIFICATION132 181 V13.0.0 (2016elecommunications System (LTE; munication management; ata Convergence (UDC); Model Handling and Managem.181 version 13.0.0 Release 1316-02) (UMTS); e ent 13) ETSI ETSI TS 132 181 V13

2、.0.0 (2016-02)13GPP TS 32.181 version 13.0.0 Release 13Reference RTS/TSGS-0532181vd00 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

3、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 document sha

4、ll 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

5、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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, pleas

6、e 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 by written permi

7、ssion 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 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand th

8、e 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. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132

9、181 V13.0.0 (2016-02)23GPP TS 32.181 version 13.0.0 Release 13Contents Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 UDC Framework overview 7g34.1 General overview . 7g34.2 Requirements coming from other Spec

10、ifications . 7g34.3 Overview of UDC Data and Information Models 7g35 UDC information model infrastructure 9g35.1 Common Baseline Information Model (CBIM) . 9g35.2 Application Information Models (AIM) . 9g35.3 Specialised Information Model (SpIM) 10g36 UDC information model handling 10g36.1 General .

11、 10g36.2 Initial SpIM Creation from CBIM 12g36.3 AIM Integration into SpIM 12g36.4 Consolidation of User Data in the SpIM 12g36.5.1 Example of consolidation of data in the SpIM using aggregation 12g36.5.2 Example of specialization for authentication methods . 13g36.5.3.1 AkaUsim . 14g36.5.3.1.1 Defi

12、nition. 14g36.5.3.2 CsAka 14g36.5.3.2.1 Definition. 14g36.5.3.3 GPRSAka 14g36.5.3 3.1 Definition. 14g36.5.3.4 EpsAka 15g36.5.3.4.1 Definition. 15g36.5.3.5 ImsAkaIsim . 15g36.5.3.5.1 Definition. 15g36.5.3.6 ImsAka 15g36.5.3.6.1 Definition. 15g36.5.3.7 ImsAkaUsimIsim 15g36.5.3.7.1 Definition. 15g36.5.

13、3.8 GPRSImsBundled . 15g36.5.3.8.1 Definition. 15g36.5.3.9 NassImsBundled . 15g36.5.3.9.1 Definition. 15g36.5.3.10 SipDigest . 16g36.5.3.10.1 Definition. 16g36.5 Construction of AIM 16g37 Application management 16g37.1 Application Access Control Data . 16g37.2 Application Data Model and Mapping to C

14、onsolidated Data Model . 16g37.2.1 Application Data Views 16g37.3 Subscription and Notification Related Data . 18g38 Consolidated data model management . 19g38.1 Lifecycle Management of the Consolidated Data Model in the UDR 19g38.2 Activation and Deactivation of Application Adaptation 20g3ETSI ETSI

15、 TS 132 181 V13.0.0 (2016-02)33GPP TS 32.181 version 13.0.0 Release 139 Relation to other Information Models 21g39.1 Relation to SuM Network Resource Model 21g3Annex A (informative): Change history . 22g3History 23g3ETSI ETSI TS 132 181 V13.0.0 (2016-02)43GPP TS 32.181 version 13.0.0 Release 13Forew

16、ord 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 approval. Should the TSG modify the contents of the present document, it will be

17、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

18、 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 “The User Data Convergence concept supports a layered architecture, separating

19、 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 functionalities should be designed to access profile data remotely and withou

20、t 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 originated, to a facility called User Data Repository (UDR) where it can be ac

21、cessed, 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, that is, user data manipulation like creation, deletion, reading, modifica

22、tion 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 infrastructure - UDC information model handling - Application management - Cons

23、olidated data model management. ETSI ETSI TS 132 181 V13.0.0 (2016-02)53GPP TS 32.181 version 13.0.0 Release 131 Scope The present document specifies the framework for overall management of the User Data Convergence. In order to accommodate multiple applications and services, existing and new ones,

24、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 model (CBIM), application information models (AIM), and the specialised info

25、rmation 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 baseline information model to create the specialized information model - des

26、cribe 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 data for an application to UDC: identification and authentication - assignment

27、 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 consolidated data model in the UDR and in the provisioning entity. - activat

28、ion/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 (identified by date of publication, edition number, version number, etc.) or non-s

29、pecific. - 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

30、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 3GPP TS 32.182: “User Data Convergence; Common Baseline Information Model “

31、. 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 ETSI ETSI TS 132 181 V13.0.0 (2016-02)63GPP TS 32.181 version 13.0.0 Release 137 3GPP TS 33.203: 3G security; Access security fo

32、r IP-based services 8 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 interface; Stage 3 10 3GPP TS 32.172: Subscription Management (SuM) Network Resource Model

33、(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 following apply. A term defined in the present document takes precedence over the definit

34、ion 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 application information model. Application Data View: a function of the UDR that enables and li

35、mits 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 information model. It is related to an application data model. Common Baseline Information M

36、odel: 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 Specialized Information Model in the UDR for all applications. Information Model: Infor

37、mation 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 constrains. In the information model, entities might have network topology relationship with e

38、ach 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 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905

39、 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 Information Model AKA Authentication and Key Agreement AMF Authentication Management Field CBI

40、M 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 Circuit Card USIM Universal Subscriber Identity Module ETSI ETSI TS 132 181 V13.0.0 (201

41、6-02)73GPP TS 32.181 version 13.0.0 Release 134 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 and/or new service profiles can be added by the operator, if necessary. The flexibili

42、ty 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 purpose this specification defines and describes the infrastructure of UDC Information Model

43、s 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

44、to the UDC. Specification 23.335 8 in Clause 5.2 defines the requirements for application access to the UDR including authentication and authorisation. Specification 29.335 9: defines as Access Protocol over the Ud interface LDAP (Clause 4) and as Data Model on the interface LDAP Directory Schema (C

45、lause 7). 4.3 Overview of UDC Data and Information Models Figures Fig.4.3-1 and Fig.4.3-2 below show the data and information models contained in the UDC framework including the UDR and the Application Front Ends. Boxes outlined in black. connecting Information and Data Models represent the process

46、steps needed to produce the output model (pointed to by an outgoing arrow) from an input model (shown by the source of an incoming arrow).As shown in these figures, the Specialized Information Model can be both an input and output model, i.e. its current version is used as an input model to a proces

47、s that generates an enhanced version when an Application Information Model new to the UDR is integrated and consolidated. Fig.4.3-1 below shows the case of internal integration model handling, where implementation of the Application is under responsibility of the operator . In this situation operato

48、r specification of the AIM leads to the Application Data Model (ADM), that gets implemented in the application FE and in the Application Data Model View in the UDR. ETSI ETSI TS 132 181 V13.0.0 (2016-02)83GPP TS 32.181 version 13.0.0 Release 13Figure 4.3-1 UDC Data and Information Models Overview wi

49、th Operator integration model handling Figure 4.3-2 below shows the case of generation of the Application Data Model (ADM) for an Application/Front-End when the development of the application is not the responsibility of the operator. In this situation, both the CBIM and the AIM of the application are used to generate the ADM being implemented in the Application/Front-End. Common Baseline IM (CBIM)Specialized IM (SpIM)Consolidated Data Model (CDM)App Data View Information ElementInformation procedureApp IM (AIM)Customise