Content for  TS 32.181  Word version:  17.0.0

Top   Top   None   None   Next
0…   4…


0  Introductionp. 5

"The 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 functionalities 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 originated, 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, 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 infrastructure
  • UDC information model handling
  • Application management
  • Consolidated data model management.

1  Scopep. 6

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, 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 information model (SIM). The CBIM is standardised in TS 32.182.
  • 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
    • 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 data 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 consolidated data model in the UDR and in the provisioning entity.
    • activation/deactivation of application adaptation

2  Referencesp. 6

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.
  • 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 the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TR 22.985: "Service requirement for the User Data Convergence (UDC)".
TS 22.101: "Service aspects; Service principles".
TS 32.182: "User Data Convergence; Common Baseline Information Model".
TR 32.808: "Study of Common Profile Storage (CPS) Framework of User Data for network services and management"
TS 33.102: "3G Security; Security architecture"
TS 33.203: "3G security; Access security for IP-based services"
TS 23.335: "User Data Convergence; Technical Realization and Information Flows;Stage 2"
TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3"
3GPP TS 32.172: "Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)"

3  Definitions and abbreviationsp. 7

3.1  Definitionsp. 7

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
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 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 information model. It is related to an application data model.
Common Baseline Information Model:
basic structure of UDC IOCs, see also definition in TS 32.182
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:
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 constrains. 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  Abbreviationsp. 7

For the purposes of the present document, the abbreviations given in TR 21.905 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.
Application Data Model
Application Information Model
Authentication and Key Agreement
Authentication Management Field
Common baseline Information Model
Consolidated Data Model
IMS Subscriber Identity Module
Specialised Information Model
User Data Convergence
User Data Repository
Universal Integrated Circuit Card
Universal Subscriber Identity Module

Up   Top   ToC