Browse Prior Art Database

User Data Harmonization for Subscriber Self Administration

IP.com Disclosure Number: IPCOM000020444D
Original Publication Date: 2003-Dec-25
Included in the Prior Art Database: 2003-Dec-25
Document File: 3 page(s) / 167K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

The evolution of cellular networks, which are a composition of several domains within the 3GPP (3rd Generation Partnership Project) mobile system, and the introduction of new service platforms (e.g. 3G ISP application infrastructure) introduces a wide distribution of user relevant data within different entities of the network. Thus, as user related data are stored in different places within the network, managing those data becomes a difficult task for users, subscribers, network operators and value added service providers as well. Currently, every service collects and controls its own user profiles, which can be held either by the Application Server (AS) or by the Home Subscriber Server (HSS), depending on the underlying architecture. While synchronization of, at least semantically, identical data in different data stores can be achieved by well known mechanism (e.g. GUP, Gatekeeper Update Protocol), harmonization of logically comparable data is still an open point. They have to be configured separately for each service. This can result in potentially inconvenient or even problematic aspects of Subscriber Self Administration. For example, the addition of a new "buddy" to both the "colleagues buddy list" (presence) and the "colleagues group list" (instant messaging) of the same user is not supported. Thus, synchronization can be achieved only by the clients themselves, by administrating the services separately.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 36% of the total text.

Page 1 of 3

S

© SIEMENS AG 2003 file: 2003J15336.doc page: 1

User Data Harmonization for Subscriber Self Administration

Idea: Alessandra Pandolfi, DE-Munich; Martin Gugerell, AT-Vienna

The evolution of cellular networks, which are a composition of several domains within the 3GPP (3rd Generation Partnership Project) mobile system, and the introduction of new service platforms (e.g. 3G ISP application infrastructure) introduces a wide distribution of user relevant data within different entities of the network. Thus, as user related data are stored in different places within the network, managing those data becomes a difficult task for users, subscribers, network operators and value added service providers as well.

Currently, every service collects and controls its own user profiles, which can be held either by the Application Server (AS) or by the Home Subscriber Server (HSS), depending on the underlying architecture. While synchronization of, at least semantically, identical data in different data stores can be achieved by well known mechanism (e.g. GUP, Gatekeeper Update Protocol), harmonization of logically comparable data is still an open point. They have to be configured separately for each service. This can result in potentially inconvenient or even problematic aspects of Subscriber Self Administration. For example, the addition of a new "buddy" to both the "colleagues buddy list" (presence) and the "colleagues group list" (instant messaging) of the same user is not supported. Thus, synchronization can be achieved only by the clients themselves, by administrating the services separately.

In this treatise a method is proposed to solve the problem of management of user related data, which are located in different network entities, for example within the Home Location Register (HLR), the Home Subscriber Server (HSS) or a Application Server (AP) of a given mobile network or Internet Service Provider (ISP). It supports the Subscriber Self Administration of the profile data, enabling internal AP of a given Mobile Network Operator (MNO) to interact with each other, and external AP to interact with the ones belonging to the MNO platform, e.g. achieving synchronization of similar data from different application server, i.e. "Presence Server" within the MNO network and "Presence Server" within the ISP network. For this purpose a new function, the Inter Service Support Function (ISSF), is added to the existing architecture.

The ISSF can be implemented in two different ways. It can be implemented as a stand-alone solution (see Figure 1 and Figure 2), or it can be integrated within the Application Server (see Figure 3). In all figures, user related data (user profiles) are stored within the HSS. However, the method can simply be applied also in the case that the Application Server hold those data. In the following, an embodiment is described and its implementation is explained.

A client wants to add a new member to his "colleagues" buddy list of the P...