4 UDC Framework overview

32.1813GPPFramework for Model Handling and ManagementRelease 17Telecommunication managementTSUser Data Convergence (UDC)

4.1 General overview

TR 22.985 [2] and TS 22.101[3] 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 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 purpose 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.101[3] 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.

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 (Clause 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 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 process 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 operator 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.

Figure 4.3-1 UDC Data and Information Models Overview with 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.

Figure 4.3-2 UDC Data and Information Models Overview with separate ADM generation for the Application/Front-End