Methods and arrangements in a telecommunication network

• US 20040039807A1
• Filed: 03/13/2003
• Published: 02/26/2004
• Est. Priority Date: 04/25/2002
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Berg, Ingvar, Jensen, Lars, Boveda De Miguel, Angel, Lorenzo Hernandez, Manuel, Jonsson, Jens, Eriksson, Anders
• Application Number:
  US10/387,633
• Publication Number:
  US 20040039807A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/42229 Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location diverting calls from one subscriber to another subscriber, i.e. two different subscriptions H04M3/54; selecting arrangements in intelligent networks H04Q3/005
• CPC Class Codes: H04M 3/42272 whereby the subscriber registers to the terminals for personalised service provision
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems

Abstract

The present invention relates to an arrangement and method for providing integration of different data relating to different services in a communication network with a plurality of service providers and service enablers. The system according to the invention provides a common subscriber/user database and subscriber/user data records with user and subscriber information. The subscriber/user data records comprise: at least one identification field identifying a subscriber and a user; and at least one service field specifying at least one selected service from the plurality of services provided in the service network, wherein the at least one selected service is selected by the user or subscriber. At least on of said at least one service field is provides links to affiliate data relating to the subscriber/user and which is stored outside of the common subscriber/user database.

Claims

1. A system for storing and maintaining user and subscriber data in a service network with a plurality of service systems for providing a plurality of services, the system comprising a subscriber/user database, which comprises subscriber/user data records with user and subscriber information, wherein the subscriber/user database is a common subscriber/user database holding subscriber/user information relevant for a plurality of services, and wherein the subscriber/user data records comprise:

at least one identification field identifying a subscriber and a user; and

at least one service field specifying at least one selected service from said plurality of services provided in the service network, wherein the at least one selected service is selected by the user or subscriber,

wherein at least on of said at least one service field is adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database,

whereby the common subscriber/user database and the subscriber/user records facilitate a single access point for accessing user and/or subscriber data in the service network.

2. System according to claim 1, wherein the subscriber/user data records comprise at least the two service fields:

a service subscription field specifying a first group of services available to the subscriber, wherein the services in the first group of services is selected from said plurality of services provided in the service network; and

at least one service activation field, each service activation field specifying a by the user activated service selected from the first group of services,

wherein said service subscription field and/or service activation fields are adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database.

3. System according to claim 2, wherein the user data records comprise:

a plurality of user fields, each user field identifying a user and each user belonging to the subscriber; and

at least one service activation field for each user, which service activation fields are linked to respective user field, the service activation fields specifying a per user group of services available to respective user, the per user groups of services being selections of services from the first group of services, and wherein said service activation fields provides links to affiliate data stored outside of said common subscriber/user database.

4. System according to claim 3, wherein the common subscriber database is a distributed database.

5. System according to claim 3, wherein the user data records stores dependencies between different service systems for performing a complex service.

6. System according to claim 3, wherein the links to affiliate data is in the form of an IP-address, a URL, an HTML-address or an E. 163 address.

7. System according to claim 3, wherein the links to affiliate data is in the form of an address recognizable in an IP based network.

8. System according to claim 5, wherein the user data records for each user comprise a user shared resource field which is linked to the user field and the service activation field and said user shared resource field stores dependencies between service systems, which dependencies are on a user level.

9. System according to claim 5, wherein the user data records comprise a subscriber shared resource field which is linked to the subscriber field and the service subscription field said subscriber shared resource field stores dependencies between service systems, which dependencies are on a subscriber level.

10. System according to claim 3, wherein the user data records for each user stores a plurality of means for identification of the respective user.

11. System according to claim 10, wherein the means for identification is one or more of the following:

a phone number, a personal identification code, an email address, a name or an alias.

12. System according to claim 10, wherein the means for identification is stored in fields also storing dependencies between service systems.

13. System according to claim 2, wherein different service systems in combination forms a complex service or one service system serving as a shared resource for a plurality of other services, the dependencies between the different service systems are stored in a common service database.

14. System according to claim 3, wherein the user data records further comprise a plurality of fields specifying services available to the users, the plurality of fields comprises:

at least one service package field, each service package specifying a group of services available to the subscriber specified in the subscriber field;

a customer segment field 815 adapted for characterizing the subscriber of the subscriber field and specifying service packages; and

at least one offered service field 820 comprising service information for each separate service included in the service package specified by the service package fields.

15. A data record adapted for storing and maintaining user and subscriber data in a service network with a plurality of service systems for providing a plurality of services, the system comprising a subscriber/user database, which comprises subscriber/user data records with user and subscriber information, wherein the subscriber/user database is a common subscriber/user database holding subscriber/user information relevant for a plurality of services, and wherein the subscriber/user data records comprise:

at least one identification field identifying a subscriber and a user; and

at least one service field specifying at least one selected service from said plurality of services provided in the service network, wherein the at least one selected service is selected by the user or subscriber,

wherein at least on of said at least one service field is adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database,

whereby the common subscriber/user database and the subscriber/user records facilitate a single access point for accessing user and/or subscriber data in the service network.

16. Data record according to claim 15, wherein the subscriber/user data records comprise at least the two service fields:

a service subscription field specifying a first group of services available to the subscriber, wherein the services in the first group of services is selected from said plurality of services provided in the service network; and

at least one service activation field, each service activation field specifying a by the user activated service selected from the first group of services,

wherein said service subscription field and/or service activation fields are adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database.

17. Data record according to claim 16, wherein the user data records comprise:

a plurality of user fields, each user field identifying a user and each user belonging to the subscriber; and

at least one service activation field for each user, which service activation fields are linked to respective user field, the service activation fields specifying a per user group of services available to respective user, the per user groups of services being selections of services from the first group of services, and wherein said service activation fields provides links to affiliate data stored outside of said common subscriber/user database.

18. Data record according to claim 16, wherein the user data records stores dependencies between different service systems for performing a complex service.

19. Data record according to claim 18, wherein the user data records for each user comprise a user shared resource field which is linked to the user field and the service activation field and said user shared resource field stores dependencies between service systems, which dependencies are on a user level.

20. Data record according to claim 18, wherein the user data records comprise a subscriber shared resource field which is linked to the subscriber field and the service subscription field said subscriber shared resource field stores dependencies between service systems, which dependencies are on a subscriber level.

21. Data record according to claim 17, wherein the user data records for each user stores a plurality of means for identification of the respective user.

22. Data record according to claim 21, wherein the means for identification is one or more of the following:

a phone number, a personal identification code, an email address, a name or an alias.

23. Data record according to claim 21, wherein the means for identification is stored in fields also storing dependencies between service systems.

24. Data record according to claim 17, wherein the user data records further comprise a plurality of fields specifying services available to the users, the plurality of fields comprises:

at least one service package field, each service package specifying a group of services available to the subscriber specified in the subscriber field;

a customer segment field adapted for characterizing the subscriber of the subscriber field and specifying service packages; and

at least one offered service field comprising service information for each separate service included in the service package specified by the service package fields.

25. A user data model adapted for storing and maintaining user and subscriber data in a service network with a plurality of service systems for providing a plurality of services, the system comprising a subscriber/user database, which comprises subscriber/user data records with user and subscriber information, wherein the user data model is adapted for facilitating storage of user and subscriber data in a common subscriber/user database, and the common subscriber/user database holds subscriber/user information relevant for a plurality of services, and the user data model comprises:

at least one identification object identifying a subscriber and a user; and

at least one service object specifying at least one selected service from said plurality of services provided in the service network, wherein the at least one selected service is selected by the user or subscriber,

wherein at least on of said at least one service object provides links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database,

whereby the common subscriber/user database and the data model facilitate a single access point for accessing user and/or subscriber data in the service network.

26. Data model according to claim 25, wherein the subscriber/user data records comprise at least the two service objects:

a service subscription object specifying a first group of services available to the subscriber, wherein the services in the first group of services is selected from said plurality of services provided in the service network; and

at least one service activation object, each service activation object specifying a by the user activated service selected from the first group of services, wherein said service subscription object and/or service activation objects are adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user database.

27. Data model according to claim 26, wherein the user data model comprise:

a plurality of user objects, each user object identifying a user and each user belonging to the subscriber; and

at least one service activation object for each user, which service activation object is linked to respective user object, each service activation object specifying a per user group of services available to respective user, the per user groups of services being selections of services from the first group of services, and wherein said service activation objects provides links to affiliate data stored outside of said common subscriber/user database.

28. Data model according to claim 27, wherein the user data model defines dependencies between different service systems for performing a complex service.

29. Data model according to claim 28, wherein the user data model for each user comprise a user shared resource object which is linked to the user object and the service activation object, and said user shared resource object defines dependencies between service systems, which dependencies are on a user level.

30. Data model according to claim 28, wherein the user data model comprise a subscriber shared resource object which is linked to the subscriber object and the service subscription object, and said subscriber shared resource object defines dependencies between service systems, which dependencies are on a subscriber level.

31. Data model according to claim 28, wherein the user data model for each user defines a plurality of means for identification of the respective user.

32. Data model according to claim 31, wherein the means for identification is one or more of the following:

a phone number, a personal identification code, an email address, a name or an alias.

33. Data model according to claim 31, wherein the means for identification is defined in objects also storing dependencies between service systems.

34. Data model according to claim 27, wherein the user data model further comprise a plurality of objects specifying services available to the users, the plurality of objects comprises:

at least one service package object, each service package specifying a group of services available to the subscriber specified by the subscriber object;

a customer segment object adapted for characterizing the subscriber of the subscriber object and specifying service packages; and

at least one offered service object comprising service information for each separate service included in the service package specified by the service package objects.

35. A method of accessing user and subscriber data in a service network, wherein the service network comprises a plurality of service systems offering a plurality of services, the method comprising the steps of:

accessing a single access point in the service network;

requesting to read and/or write data from the single access point,

retrieving or transferring data from or to a subscriber/user data record via the single access point, wherein the user data record wherein the subscriber/user data records comprise;

at least one identification field identifying a subscriber and a user; and

at least one service field specifying at least one selected service from said plurality of services provided in the service network, wherein the at least one selected service is selected by the user or subscriber, wherein at least on of said at least one service field is adapted for providing links to affiliate data relating to the subscriber/user and which affiliate data is stored outside of said common subscriber/user databaseREFREF.

36. The method according to claim 35 further comprising the step of:

checking if the subscriber/user data record comprises information on dependencies between different service systems.

37. The method according to claim 36 wherein the step of checking comprises

checking the service activation field, user shared resource field and the subscriber shared resource field for links indicating dependencies between different service systems.

38. The method according to claim 35 further comprising the steps, to be taken if affiliate data which is not stored within the single access point is required, of

accessing the single access point for retrieving links to the affiliate data and information required to access the affiliate data;

accessing an affiliate data repository using the link and information retrieved in the previous step.

40. A computer program product directly loadable into the internal memory of a processing means within a unit in the service network, comprising the software code means adapted for controlling the steps of claim 35REF.

41. A computer program product stored on a computer usable medium, comprising readable program adapted for causing a processing means in a processing unit for a unit in the service network to control an execution of the steps of any of the claims 35REF.

39. The method according to any of claims REF38 wherein the steps are performed by a software client.