1、 ETSI TR 122 985 V14.0.0 (2017-03) Universal Mobile Telecommunications System (UMTS); Service requirements for the User Data Convergence (UDC) (3GPP TR 22.985 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 122 985 V14.0.0 (2017-03)13GPP TR 22.985 version 14.0.0 Release 14Reference RTR/TSGS
2、-0122985ve00 Keywords 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 de Grasse (06) N 7803/88 Important notice The present document
3、 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 modified without the prior written authorization of ETSI. In case o
4、f 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
5、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 send your comment to one of the following services: https:/portal
6、.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 of ETSI. The content of the PDF version shall not be modified
7、 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 ETSI logo are Trade Marks of ETSI registered for the benefit of i
8、ts 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 TR 122 985 V14.0.0 (2017-03)23GPP TR 22.985 version 14.0.0 Release 14Intel
9、lectual 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 publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Righ
10、ts (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, ha
11、s 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. Foreword The present document may refer to technical specification
12、s 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs
13、 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 deliverabl
14、es except when used in direct citation. ETSI ETSI TR 122 985 V14.0.0 (2017-03)33GPP TR 22.985 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definiti
15、ons 5g33.2 Symbols 5g33.3 Abbreviations . 5g34 General description. 6g34.1 Introduction 6g35 User Data 8g35.1 User data basic concept 8g35.2 User data category 8g35.2.1 Introduction. 8g35.2.2 User Subscription Data . 8g35.2.3 User content Data . 8g35.2.4 User Behaviour Data . 9g35.2.5 User Status Da
16、ta . 9g35.3 User data convergence 9g35.4 Common baseline information model and data model . 10g35.4.1 Introduction to User Data Modelling 10g35.4.2 Requirements for the baseline information model 10g35.4.3 Requirement for data models 11g35.4.4 Management of information model and data model . 11g36 R
17、equirement of user data convergence. 12g36.1 Introduction 12g36.2 Redundancy, Scalability and Load control Aspects . 13g36.3 Network Considerations . 13g36.4 User data interface 13g36.5 Subscription/Notification . 13g36.6 Access control 13g36.7 Management of user data . 14g36.7.1 Self care system: .
18、 14g36.7.2 Application server and user service configuration 14g36.8 Data federation . 14g3Annex A: Change history 15g3History 16g3ETSI ETSI TR 122 985 V14.0.0 (2017-03)43GPP TR 22.985 version 14.0.0 Release 14Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership P
19、roject (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
20、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, corr
21、ections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 122 985 V14.0.0 (2017-03)53GPP TR 22.985 version 14.0.0 Release 141 Scope The present document describes the concept of the 3GPP User Data Convergence (UDC). It fu
22、rthermore collects some architectural requirements and should be taken as guideline in stage 2 and 3 work. The UDC will simplify the overall network topology and interfaces, avoid data duplication and inconsistency and simplify creation of new services by providing easy access to the user data. Spec
23、ial consideration is put on the following areas: - Categorization of the user data of services which would be converged in UDC - Identification of the requirements on the common data model framework with focus on extensibility - Identification of the requirements on the UDC for the support of new se
24、rvices including their provisioning 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.
25、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 th
26、e present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions, symbols and abbreviations 3.1 Definitions 3.2 Symbols 3.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
27、present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. UDC User Data Convergence UDR User Data Repository ETSI ETSI TR 122 985 V14.0.0 (2017-03)63GPP TR 22.985 version 14.0.0 Release 144 General description 4.1 Introduction In the current 3GPP system,
28、 user data are scattered in several domains (e.g. CS, PS, IMS) and different network entities (e.g. HLR, HSS, Application Servers). With the increase of user data entities and the resulting data types, it is more difficult for integrated services to access necessary user information from plural enti
29、ties. The scenario mentioned herein is kind of called “User Data Silo”, which is the major paradigm of user data deployment for the time being, as illustrated by Fig.1. Figure 1 User Data Silo With the user data silos, user data are independently accessed, stored and managed independently. That brin
30、gs many challenges to network deployment and evolution. Different user data access interfaces impose complexity on network topology as well as on application development, especially for booming Internet services and incoming IP-based UE applications; separated user data increases management workload
31、. Moreover, new networks and services such as IMS are expected, so that the introduction of their user data only makes things worse, not to mention network and service convergence even if those user data have a lot in common and are correlated to each other. Separation also undermines the value of u
32、ser data mining. User data convergence is required to ensure the consistency of storage and data models. User data convergence will simplify overall network topology and interfaces, overcome the data capacity bottleneck of a single entry point, avoid data duplication and inconsistency and reduce CAP
33、EX and OPEX. Also it will simplify the creation of new services and facilitate service development and deployment though a common set of user data. Finally it will promote service and network convergence to support the increasing number of new services including Internet services and UE applications
34、. In this regard, a new facility User Data Repository (UDR) should be considered for user data convergence. ETSI ETSI TR 122 985 V14.0.0 (2017-03)73GPP TR 22.985 version 14.0.0 Release 14Figure 2 User Data Convergence As illustrated by Fig. 2, User Data Convergence, as opposed to User Data Silo, is
35、simply to move the user data from where it belonged, to a facility here called User Data Repository (UDR) where it can be accessed, stored and managed in a common way. Despite of the diversity of user data structures for different services, user data can be decomposed and reformed by a common data m
36、odel 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 in data model will unify the user data access interface and its protocol, which w
37、ill promote new service application development. Thereby, the capability of user data convergence can be open to creation of data-less applications. ETSI ETSI TR 122 985 V14.0.0 (2017-03)83GPP TR 22.985 version 14.0.0 Release 145 User Data 5.1 User data basic concept There are plenty of data distrib
38、uted in the 3GPP system which is used to perform the services, for instance, the configuration data of a network entity, the session data of a multimedia call, the IP address of a terminal, etc. With respect to user data, it refers to all kinds of the information related to users who make use of the
39、 services provided by the 3GPP system. In 3GPP system, user data is spread widely through the different entities (e.g. HLR, HSS, VLR, Application servers) and also the type of user data is various. It is of paramount importance to categorize the user data before going through the convergence of user
40、 data. 5.2 User data category 5.2.1 Introduction The UDC shall support multiple application user data simultaneously, e.g. HSS and others. Any application can retrieve data from the UDC and store data in it. The applications shall be responsible of updating the UDC with the dynamic changes of the us
41、er profile due to traffic reasons (e.g. user status, user location) or as a consequence of subscriber procedures. The hereafter data classification highlights some major differences regarding two of the characteristics : Size per user and real time applicability. 5.2.2 User Subscription Data Before
42、a user can enjoy a service, he may need to subscribe the service first. The subscription data relates to the necessary information the mobile system ought to know to perform the service. User identities (e.g. MSISDN, IMSI, IMPU, IMPI), service data (e.g. service profile in IMS) , and transparent dat
43、a (data stored by Application Servers for service execution) are the examples of the subscription data. This kind of user data has a lifetime as long as the user is permitted to use the service and may be modified during the lifetime. User may be accessed and configured via various means, e.g. custo
44、mer service, web interface, UE Presence service. The subscription data is composed of different types such as authentication data, configuration data, etc. Different type of data may require different levels of security. 5.2.3 User content Data Some applications may have to store content defined by
45、the user and that here may be quite large (e.g. Photos, videos) User content data can reach very high volume (e.g. Hundreds of Mbytes and more), and the size required to store them may largely vary over time. They generally do not require the real time constraints as user profile data may require. S
46、torage of user data content is not typically subject of UDR. Storage of user data content is not typically subject of UDR. UDC on user content data can be achieved by converging them with links or references, such as URLs, to other entity. ETSI ETSI TR 122 985 V14.0.0 (2017-03)93GPP TR 22.985 versio
47、n 14.0.0 Release 145.2.4 User Behaviour Data Such data concerns the usage of services by a user as services are consumed. Generally there are event data records that can be generated on various events in the usage of services by a user and that can be used not only for charging or billing purposes b
48、ut e.g. for user profiling regarding user behaviour and habits, and that can be valuable for marketing purposes. The amount of such data is also quite different from other categories, they present a cumulative effect as such data can be continuously generated by the network implying a need for corre
49、sponding storage. Usage data may require real time aspects about their collection (e.g. for on line charging), they are also often characterized by a high amount of back office processing (e.g. Billing, user profiling). The data related to user behavior comprises - call-related or session-related dynamic data (e.g. session state, MSRN) which are transitory and only valid during a session - location-related data (e.g. VLR number, SGSN number) or/and registration status (e.g. MS status, registration status in IMS domain) which are valid between location updates or
