21.2 Study on sa5 mtosi xml Harmonization uid_390037

Resources: S5

References

Document	Title/Contents
WID(s)
SP-070305	SID on SA5 MTOSI - XML Harmonization
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 32.818	Telecommunication management; Study on 3GPP SA5 / MTOSI XML harmonization

Supporting Individual Members: Nortel, Huawei, Alcatel-Lucent, Ericsson, ZTE.

Industry-wide there is a need for harmonization of XML specification methodologies, best practices and guidelines.

SA5 has studied the TMF MTOSI solutions on XML specification methodologies, best practices and guidelines.

This study determined harmonization items with respect to the 3GPP and TMF 608 XML specifications. It identified possible updates to MTOSI XML framework as well as to 3GPP SA5 XML specifications based on dialogue between 3GPP SA5 and TM Forum MTOSI.

TR 32.818 conclusion:

This study assessed whether MTOSI XML recommendations could be considered for future SA5 XML-Based implementations.

On methodology, SA5 is willing to help MTOSI to align with SA5's specifications structure (Requirements, IS, SS).

Concerning IRP specifications, the following was agreed:

• Existing IRP specifications (and their future versions) such as SuM, Notification etc., that have already a SOAP implementation shall be kept untouched.

• Existing IRP specifications that do not have a defined SOAP SS could be considered for XML-Based implementation, considering MTOSI XML recommendations.

• For new IRP specifications requiring XML-based implementation, MTOSI XML recommendation should be considered.

Model harmonization was not needed.

TR 32.818 is a guideline for SA5 Rel-8 and beyond.

21.3 Study of Common Profile Storage Framework of User Data for network services and management uid_390038

Resources: S5

References

Document	Title/Contents
WID(s)
SP-060263	SID on Common Profile Storage (CPS) Framework of User Data for network services and management
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 32.808	Telecommunication management; Study of Common Profile Storage (CPS) Framework of User Data for network services and management

Supporting Individual Members: T-Mobile, Siemens, Nokia, Cingular, Vodafone, Huawei, Orange.

This study is linked to Rel-6 Subscription Management (SuM) and Rel-6 Generic User Profile (GUP).

Introducing a Common Profile Storage (CPS) Framework of User Data ("Common" meaning common to all applications) for network services and management applications could significantly enhance the ability of 3GPP networks to offer complex and combined services in the areas of:

• Multimedia;

• Data services;

• Value Added Services;

• End-to-end applications.

In light of developments both within 3GPP (e.g. IMS, MBMS, OCS, PCC) and outside 3GPP (e.g. NGN, OMA, etc.) with a growing number of physically disjoint but logically correlated user data stored in several data bases a consolidation and co-ordination of these is needed to prevent further redundancy and possible contradiction and to enable operators to administer and provision complex and combined services.

An initial study of user-related data - in and outside 3GPP - assessed the properties of such a CPS Framework based on:

• needs of Network Elements (NEs) like MMS-RS, HLR, HSS, BM-SC and

• features like Service Management, Subscription Management (SuM) and Charging Management.

Efforts within the mobile and Next Generation Network (NGN) communities to define advanced services within the network (e.g. 3GPP, TISPAN) provided valuable drive for developing the CPS Framework functionality for 3GPP.

This study:

• analysed the consequences of creating one common data model structure for an end-user

  • looked at the existing data specifications in 3GPP;

  • addressed issues like minimizing data redundancy, access control, providing views for applications;

  • analyzed the relationship between an end-user and a subscriber as defined by 3GPP;

• analysed and evaluated current initiatives inside and outside 3GPP;

• analysed the gap between 3GPP specifications (e.g. GUP, SuM, etc.) and existing/emerging solutions with centralized respectively distributed storage models.

• proposes a way forward for standardizing inside or outside 3GPP the "gap" (if existent).

Service Aspects

SA5 investigated features of user data storage arising from the fact that user data is handled within a CPS Framework (with centralized or distributed storage models) and accessed from a variety of NEs and enterprise applications. SA5 studied the need to develop user data management capabilities arising from service requirements (defined by SA1).

MMI-Aspects

SA5 studied the interface aspects between subscriber/user and service provider.

TR 32.808 conclusions - proposed standardization actions based on the gaps with the current 3GPP concepts:

• Introduce the Concept of End-User (in SA1)

• Introduce the Concept of Contract (in SA1)

• Introduce the network function Common Profile Store (CPS)

Spin-off New Rel-9 SA1 Feature on User Data Convergence (UDC) UID_400034