1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelUser DatTechnical reali(3GPP TS 23.3TECHNICAL SPECIFICATION123 335 V13.1.0 (2016mmunications system (Phase elecommunications System (LTE; ata Convergence (UDC); alization and information flowStage 2 .335 version 13.1.0 Release 1316-04) e 2+) (GS
2、M); (UMTS); ws; 13) ETSI ETSI TS 123 335 V13.1.0 (2016-04)13GPP TS 23.335 version 13.1.0 Release 13Reference RTS/TSGC-0423335vd10 Keywords GSM,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 7
3、42 C Association but non lucratif enregistre 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 a
4、nd/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) versi
5、on 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 http:/portal.etsi.org/tb/status/status.asp I
6、f you find errors in the present 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
7、 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. European Telecommunications Standards Institute 2016. All ri
8、ghts reserved. DECTTM, PLUGTESTSTM, 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. GSM and the GSM logo are Trade Marks registered and
9、 owned by the GSM Association. ETSI ETSI TS 123 335 V13.1.0 (2016-04)23GPP TS 23.335 version 13.1.0 Release 13Intellectual 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 pu
10、blicly 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 ET
11、SI 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, o
12、r 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. These
13、 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 not“,
14、 “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 123 335
15、 V13.1.0 (2016-04)33GPP TS 23.335 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 8g
16、34 User Data Convergence architecture 8g34.1 UDC System architecture . 8g34.2 Functional Entities 10g34.2.1 Application Front Ends . 10g34.2.2 Provisioning Front Ends . 10g34.2.3 User Data Repository 11g34.2.4 Other Network Elements 11g34.3 Reference point Ud . 12g34.4 Front-End Session 12g34.5 UDR
17、Session 13g35 User Data convergence information flows . 13g35.1 General . 13g35.2 Requirements 15g35.3 Querying data from the UDR . 16g35.4 Creating data within the UDR 17g35.5 Deleting data from the UDR. 18g35.6 Updating data within the UDR . 19g35.7 Subscription to Notifications 20g35.8 Notificati
18、on of data modification . 21g35.8.1 Description 21g35.8.2 Notifications and transactions . 23g3Annex A (informative): Information flows . 24g3A.0 Introduction 24g3A.1 Information flows with Query data procedure over Ud . 24g3A.1.1 General . 24g3A.1.2 CS terminating call information flow example 24g3
19、A.1.3 IMS re-registration information flow example . 25g3A.2 Information flows with Updating data procedure over Ud. 26g3A.2.1 General . 26g3A.2.2 CS location update information flow example . 27g3A.2.3 IMS service data change information flow example 28g3A.3 Example Information flows for subscripti
20、ons to notifications . 29g3A.3.1 General . 29g3A.3.2 Application Server Subscription information flow example 29g3A.4 Information flows with notification procedure over Ud . 30g3A.4.1 General . 30g3ETSI ETSI TS 123 335 V13.1.0 (2016-04)43GPP TS 23.335 version 13.1.0 Release 13A.4.2 IMS user capabili
21、ty change with notification information flow example 31g3A.4.3 Application Server Notification information flow example without Ud-Notify 32g3A.4.4 Application Server Notification information flow example with Ud-Notify . 33g3A.4.5 Application Server Notification information flow example without Ud-
22、Notify Subscription expired . 34g3A.4.6 Application Server Notification information flow example with Ud-Notify Subscription expired 35g3Annex B (informative): Applicability of the UDC concept to network nodes . 36g3B.1 Introduction 36g3B.2 Basic Prerequisite . 36g3B.3 Step 1 Separating User Data fr
23、om Application Logic 36g3B.4 Step 2 Introducing Provisioning FEs 37g3B.5 Step 3 - Storing outsourced user data in a logically single UDR . 37g3B.6 Step 4 Full Load Sharing and Failover functionality . 38g3B.7 Step 5 Converging user data in the UDR 39g3B.8 Example analysis for HLR . 39g3B.9 Example a
24、nalysis for S-CSCF . 39g3B.10 Example analysis for PCRF and SPR 40g3B.11 Summary 40g3Annex C (informative): Change history . 41g3History 42g3ETSI ETSI TS 123 335 V13.1.0 (2016-04)53GPP TS 23.335 version 13.1.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Par
25、tnership 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 in
26、crease 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 enhancem
27、ents, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The UDC concept (3GPP TS 22.101 3) supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data
28、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 user data remotely and without storing them permanently locally, i.e. the Front Ends shall work in a subscr
29、iber dateless configuration. ETSI ETSI TS 123 335 V13.1.0 (2016-04)63GPP TS 23.335 version 13.1.0 Release 131 Scope The present document describes the procedures and signalling flows associated to the technical realization of the 3GPP User Data Convergence (UDC). It furthermore indicates some requir
30、ements for the stage 3 specifications. Special consideration is put in the following areas: - reference architecture for the UDC concept - general description of procedures for the user data manipulation (e.g. create, delete, update, etc.) - identification of the requirements on the UDC for the appl
31、icability of the mechanisms described in this document. User data convergence is an optional concept to ensure data consistency and simplify creation of new services by providing easy access to the user data, as well as to ensure the consistency of storage and data models and to have minimum impact
32、on traffic mechanisms, reference points and protocols of network elements. Standization of the Data Model for the Ud interface between Front-Ends and the UDR is out of the scope of 3GPP. 2 References The following documents contain provisions which, through reference in this text, constitute provisi
33、ons 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 referen
34、ce 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 TR 22.985: “Service requirement for the User Data Convergenc
35、e (UDC)“. 3 3GPP TS 22.101: “Service aspects; Service principles“. 4 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 5 3GPP TS 23.002: “Network architecture“. 6 3GPP TS 32.182: “User Data Convergence (UDC); Common Baseline Information Model (CBIM)“. 7 3GPP TS 33.210: “3G Security; Net
36、work Domain Security; IP network layer security“. 8 3GPP TS 32.181: “Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management“. 9 3GPP TS 23.179: “Functional architecture and information flows to support mission critical communication services“. ETSI ETS
37、I TS 123 335 V13.1.0 (2016-04)73GPP TS 23.335 version 13.1.0 Release 133 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes preceden
38、ce over the definition of the same term, if any, in 3GPP TR 21.905 1. Front End: a core network functional entity or service layer entity or provisioning entity that can access user data stored in a unique repository. Front End Identifier: A name that uniquely identifies an FE within the set of all
39、FEs accessing an UDR. Front End Cluster: FEs handling the same application may be grouped in clusters to differentiate between them e.g. with regard to geographical location, feature support, vendor, or other characteristics. All FEs within a cluster are treated equally for required purposes (e.g. a
40、uthorization, notifications, etc.). Application type: The application handled by a FE (e.g. HLR) determines the application type of the FE. The application type is derived from the name indicated by a FE. Front End Cluster Identifier: A name that identifies a cluster grouped with FEs supporting the
41、same application. User Data Repository: facility where user data can be accessed stored and managed in a common way. Transaction: a transaction is a sequence of operations towards the User Data Repository (one or several), performed as a single logical unit of work. A logical unit of work must exhib
42、it four properties, called the ACID (Atomicity, Consistency, Isolation, and Durability) properties, to qualify as a transaction. A transaction usually consists of the following steps, start transaction, making updates, and end of transaction; the transaction can finish successfully, in that case it
43、is said the updated data is committed, or unsuccessfully, in that case the transaction is cancelled and the updates made till that moment are rolled back so that the data remains as it were before the transaction. Atomicity: a transaction must be an atomic unit of work; either all of its data modifi
44、cations are performed or none of them is performed. Consistency: when completed, a transaction must leave all data in a consistent state. In the User Data Repository, all rules must be applied to the transaction“s modifications to maintain all data integrity. All internal data structures must be cor
45、rect at the end of the transaction. Isolation: modifications made by concurrent transactions must be isolated from the modifications made by any other concurrent transactions. A transaction either sees data in the state it was in before another concurrent transaction modified it, or it sees the data
46、 after the second transaction has completed, but it does not see an intermediate state. This is referred to as serialization because it results in the ability to reload the starting data and replay a series of transactions to end up with the data in the same state it was in after the original transa
47、ctions were performed. Durability: after a transaction has completed, its effects are permanently in place in the User Data Repository. The modifications persist even in the event of a system failure. 3.2 Symbols For the purposes of the present document, the following symbols apply: Ud reference poi
48、nt between a FE and the UDR ETSI ETSI TS 123 335 V13.1.0 (2016-04)83GPP TS 23.335 version 13.1.0 Release 133.3 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
49、 the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. FE Front End UDC User Data Convergence UDR User Data Repository 4 User Data Convergence architecture 4.1 UDC System architecture Figure 4.1-1 presents the reference UDC architecture. UDC is the logical representation of the layered architecture that separates the user data from the application logic, so that user data is stored in a logically unique repository allowing access from entities handling an application logic, hereby named Application Front Ends. In the arc
