Personalization of telecommunications services

• US 20050143066A1
• Filed: 04/10/2003
• Published: 06/30/2005
• Est. Priority Date: 04/15/2002
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Niemi, Kari J
• Application Number:
  US10/511,103
• Publication Number:
  US 20050143066A1
• Time in Patent Office: Days
• US Class Current: 455/432.300
• CPC Class Codes: H04M 3/42136 Administration or customisation of services
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

A method for personalizing services in a mobile communications system, the services being used on the basis of a parameter list (pam-1, pam-N) and a service data profile (1-1, 1-2, 1-3, N-1, N-2). The parameter list comprises the parameters needed for providing a service. The service data profile defines levels for the parameters in the parameter list, the parameter values being re-trieved from the levels when the service is being used. The levels include, for example, global (gl), service-specific (se) and subscriber-specific (su) levels. The service data profiles of a particular service differ from one another accord-ing to the level on which the parameter values have been defined.

Claims

1. A method for personalizing a service in a telecommunications system, the method comprising at least the steps of

maintaining a parameter list for a service, the list comprising parameters associated with the service,

further comprising the steps of

maintaining a value on at least two different levels for at least a first parameter, the first level being more individualizing than the second level;

and

maintaining at least two service data profiles for the service, the profiles both comprising definitions of the levels for the parameters and the profiles differing from one another at least in that in the first service data profile the first parameter value is on the first level, whereas in the second service data profile it is on the second level.

2. A method according to claim 1, comprising the steps of

indicating the service data profile to be used for providing a service to a subscriber in subscriber data residing in the system;

and

providing the service to the subscriber by using the values defined for the parameters on the levels according to the service data profile definitions.

3. A method according to claim 1, wherein the first level is a system- or service-specific level and the second level is a subscription-specific level in which a parameter value is separately defined for each subscription in the system.

4. A method according to claim 1, wherein the parameters of the parameter list that are not available for a particular service data profile are indicated in the service data profile.

5. A method according to claim 1, further comprising the step of determining in the service data profile not only common parameters included in each service data profile, but also service-data-profile-specific parameters that relate only to the service data profile in question.

6. A method according to claim 1, further comprising the step of maintaining a parameter list for a service, the list being associated with the first service data profile and comprising references only to parameters associated with the first service data profile.

7. A telecommunications system software product comprising a computer-readable program stored in a program storage means, the program comprising a first routine for maintaining a parameter list for a service, the list comprising parameters associated with the service, wherein the program comprises a second routine for maintaining at least a first parameter value on at least two different levels, the first level being more individualizing than the second the profiles both comprising definitions of the levels for the parameters and the profiles differing from one another at least in that in the first service data profile the value of the first parameter is on the first level, whereas in the second service data profile it is on the second level.

8. A software product according to claim 7, wherein the program comprises a fourth routine to indicate in the system subscriber data the service data profile to be used for providing a service to the subscriber, and a fifth routine for providing the service to the subscriber by using the parameter level values defined on the basis of the service data profile definitions.

9. A software product according to claim 7, wherein the program further comprises a routine for identifying those parameters in a parameter list which are not available in the service data profile.

10. A software product according to claim 7 wherein the program further comprises a routine for identifying in the service data profile not only common parameters included in each service data profile, but also service-data-profile-specific parameters that relate only to the service data profile in question.

11. A software product according to claim 7, wherein the program further comprises a routine for maintaining for the service a parameter list associated with the first service data profile, the list including references only to parameters associated with the first service data profile.

12. A telecommunications system comprising

a network node for maintaining for a service a parameter list of parameters associated with the service,

wherein the system is configured to

maintain at least a first parameter value on at least two different levels, the first level being more individualizing than the second level;

and to

maintain at least two service profiles for the service, the profiles both comprising definitions of the levels for the parameters and the profiles differing from one another at least in that in the first service data profile the value of the first parameter is on the first level, whereas in the second service data profile it is on the second level.

13. A telecommunications system according to claim 12, wherein the system is further configured to

indicate in the system subscriber data the service data profile to be used for providing the service to a subscriber;

and to

provide the service to the subscriber by using parameter values defined on levels according to the service data profile definitions.

14. A telecommunications system according to claim 12, wherein the system is further configured to indicate the parameters that are not available for the service data profile.

15. A telecommunications system according to claim 12, wherein the system is configured to maintain in the service data profile not only common parameters included in each service data profile but also service-data-profile-specific parameters only associated with the service data profile in question.

16. A telecommunications system according to claim 12, wherein the system is further configured to maintain for the service a parameter list associated with the first service data profile, the list including references only to parameters associated with the first service data profile.

17. A network node for maintaining a parameter list of parameters associated with a service in a telecommunications system, wherein the network node comprises memory means for

maintaining a value for at least a first parameter on at least two different levels, the first level being more individualizing than the second level;

and for

maintaining at least two service data profiles for a service, the profiles both comprising parameter level definitions and the profiles differing from one another at least in that in the first service data profile the value of the first parameter is on a first level, whereas in the second service data profile it is on a second level.

18. A network node according to claim 17, wherein the network node is a service database in a mobile communications system.

19. A network node for providing a service in a telecommunications system in which a list of the parameters for the service is maintained, wherein for providing the service to the subscriber, the network node comprises:

a first routine to find out in the subscriber data of the system which one of the service data profiles of the service has been subscribed to, the service data profiles comprising definitions of the levels for the parameters and the profiles differing from one another in relation to at least one parameter level definition; and

a second routine for retrieving the parameter values from the levels based on the definitions in the service data profile.

20. A network node according to claim 19, wherein the network node is a service platform (SEP) in a mobile communications system.