Browse Prior Art Database

Service Configuration and User Registry (SCUR) for IP Multimedia Subsystem (IMS) Networks

IP.com Disclosure Number: IPCOM000191132D
Original Publication Date: 2009-Dec-17
Included in the Prior Art Database: 2009-Dec-17
Document File: 4 page(s) / 55K

Publishing Venue

IBM

Abstract

A Service Configuration and User Registry (SCUR) for IP multimedia subsystem (IMS) networks is disclosed.

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 49% of the total text.

Page 1 of 4

Service Configuration and User Registry (SCUR) for IP Multimedia Subsystem (IMS) Networks

Disclosed is a Service Configuration and User Registry (SCUR) for IP multimedia subsystem (IMS) networks.

SCUR enables telecommunication service providers to easily deploy and manage a large portfolio of IMS services. Master Service executables corresponding to each IMS service and associated configuration data, user profiles, personalization settings are stored in a centralized SCUR database. Therefore, it allows the data to be retrieved from a single source instead of looking around multiple application servers clusters. Further, Software maintenance/upgrade/version control/configuration changes can all be handled through changes to the SCUR database.

In order for implement the proposed SCUR, a Client-Side SCUR (on IMS Device Client) and a Server-Side SCUR (part of IMS core network) are deployed.

Fig. 1 illustrates architecture for the client-side SCUR.

Figure 1

The server-side SCUR stores the master executable version of the IMS services and its associated configuration data. Additionally, licensing information and validity, partner settlement metrics (in case of managed services) may all be stored in the server-side SCUR with appropriate version control.

During IMS service upgrades, network administrators upgrade the corresponding

1

[This page contains 2 pictures or other non-text objects]

Page 2 of 4

master executable version and associated data in the service configuration data layer of the server-side SCUR. Since SCUR is a hierarchical database, previous versions of the IMS service and associated configuration data are also maintained in case rollback is required. Thereafter, upgraded executable code and configuration data is imported into Application Server cluster for execution. In a similar manner, new IMS services can be deployed.

Further, for each IMS service that is installed and active in the IMS network, the server-side SCUR saves service information as keys. The server-side SCUR provides a single interface using which telecommunication providers may determine all active IMS services currently deployed in the IMS network.

Clusters of application servers on which the IMS Services are deployed are configured to reference the appropriate location in SCUR to import the master executable program for the IMS service and the associated configuration data during startup/initialization to run on the application server cluster.

The server-side SCUR also includes a hierarchical database to store high level user profiles of the IMS services consumers. The IMS Service consumers are categorized into two main categories, such as Home Subscriber Profile and 3rd Party Service Provider Profile, therefore the server-side SCUR stores profiles in these 2-levels. The home subscribers are subscribers for a 3G network in which the I...