Service enablement/disablement based on service relationships

• US 8,688,835 B2
• Filed: 07/02/2008
• Issued: 04/01/2014
• Est. Priority Date: 07/02/2008
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Olsson, David
• Primary Examiner(s): Nguyen, Quang N
• Application Number:
  US13/000,324
• Publication Number:
  US 20110145408A1
• Time in Patent Office: 2,099 Days
• Field of Search: 709/203, 709/223, 709/224, 709/226, 709/228, 709/238
• US Class Current: 709/225
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5064 Customer relationship management
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A network (100) may include a provisioning platform (120) and a group of nodes (130). The provisioning platform (120) may include a service management component (540) to define relationships between a group of services and processing logic (420). The processing logic (420) may receive a request to enable or disable a user for a first service, identify a second service that is required by the first service from the service management component (540), identify a first node (130-1 through 130-N) associated with the identified second service, and identify a second node (130-1 through 130-N) associated with the first service. The processing logic (420) may further transmit at least one first parameter to enable or disable the user at the identified first node (130-1 through 130-N), and transmit, when the user has been successfully enabled or disabled at the identified first node (130-1 through 130-N), at least one second parameter to enable or disable the user at the identified second node (130-1 through 130-N).

Claims

1. A computing device-implemented method for enabling or disabling a user for a first service, the method comprising:

receiving a request to enable or disable a user for the first service;

identifying a second service that is required by the first service from a service management component that stores information about services and information indicating relationships between services;

executing, based on the received request, at least one service neutral function common for all services for a specific purpose, the service neutral function including software code and/or configuration for the second service, to enable or disable the user for the identified second service;

executing, after executing the at least one service neutral function for the second service, said at least one service neutral function for the first service to enable or disable the user for the first service;

wherein executing to enable or disable the user for the first service comprises;

executing, after executing a plurality of service neutral functions for the second service, said at least one service neutral function for the first service to enable or disable the user for the first service; and

aborting the execution to enable or disable the user for the first service when the user cannot be enabled or disabled for the identified second service.

2. The computing device-implemented method of claim 1, where the information indicating relationships between services comprises one or more of:

information identifying service versions that are associated with each service,

information identifying whether each service is part of a service package,

information identifying whether a service package is part of another service package,

information identifying whether a service version requires another service version in order to operate, or

information identifying whether a service version requires one of a number of other service versions in order to operate.

3. The computing device-implemented method of claim 1, where the executing at least one service neutral function to enable or disable the user for the identified second service comprises:

identifying a first node relating to the identified second service, adapting, via a first target connector associated with the identified first node, at least one first parameter into a format compatible with the identified first node, and

transmitting the adapted at least one first parameter to the identified first node to enable or disable the user at the identified first node.

4. The computing device-implemented method of claim 3, further comprising:

identifying the first target connector based on information identifying the second service.

5. The computing device-implemented method of claim 3, where the executing at least one service neutral function to enable or disable the user for the first service comprises:

identifying a second node relating to the first service,

adapting, via a second target connector associated with the identified second node, at least one second parameter into a format compatible with the identified second node, and

transmitting the adapted at least one second parameter to the identified second node to enable or disable the user at the identified second node.

6. The computing device-implemented method of claim 1, further comprising:

providing a message, indicating that the enablement or disablement of the user for the first service has failed, when the user has not been successfully enabled or disabled for at least one of the identified second service or the first service.

7. The computing device-implemented method of claim 1, further comprising:

determining, prior to executing the at least one service neutral function, whether it is possible to enable or disable the user for the first service; and

determining, when it is determined to be possible to enable or disable the user for the first service, whether it is possible to enable or disable the user for the second service.

8. The method of claim 1, wherein receiving the request to enable or disable the user for the first service comprises:

receiving the request to enable or disable a wireless user device of the user for the first service, wherein the first service comprises a service provided to wireless user devices via a wireless communications network.

9. A non-transitory computer-readable device storing executable instructions that, when executed by processing logic, perform a method according to claim 1.

10. A system comprising:

a provisioning platform that is configured to;

receive a request to enable or disable a user for a first service,

identify a second service that is required by the first service from a service management component that defines a relationship between the first service and the identified second service,

perform at least one service neutral function common for all services for a specific purpose, the service neutral function including software code and/or configuration for the second service to enable or disable the user for the identified second service,

perform the at least one service neutral function to enable or disable the user for the first service;

perform the at least one service neutral function to enable or disable the user for the first service after performing a plurality of service neutral functions for the second service; and

abort enabling or disabling the user for the first service when the user cannot be enabled or disabled for the identified second service.

11. The system of claim 10, where the service management component stores information for a plurality of services, the information comprising one or more of:

information identifying service versions that are associated with each service of the plurality of services,

information identifying whether each service of the plurality of services is part of a service package,

information identifying whether a service package is part of another service package,

information identifying whether a service version requires another service version in order to operate, or

information identifying whether a service version requires one of a number of other service versions in order to operate.

12. The system of claim 10, where when executing at least one service neutral function to enable or disable the user for the identified second service, the provisioning platform is configured to:

identify a first node relating to the identified second service, and

transmit at least one first parameter to enable or disable the user at the identified first node.

13. The system of claim 12, further comprising:

a first target connector, associated with the identified first node, configured to;

receive the at least one first parameter,

adapt the at least one first parameter into a format compatible with the identified first node, and

transmit the adapted at least one first parameter to the identified first node.

14. The system of claim 12, where, when executing at least one service neutral function to enable or disable the user for the first service, the provisioning platform is configured to:

identify a second node relating to the first service, and

transmit at least one second parameter to enable or disable the user at the identified second node.

15. The system of claim 14, further comprising:

a second target connector, associated with the identified second node, configured to;

receive the at least one second parameter,

adapt the at least one second parameter into a format compatible with the identified second node, and

transmit the adapted at least one second parameter to the identified second node.

16. The system of claim 12, where the provisioning platform is further configured to:

identify the first target connector based on information identifying the second service.

17. The system of claim 10, where the provisioning platform is further configured to:

provide a message, indicating that the enablement or disablement of the user for the first service has failed, when the user has not been enabled or disabled for at least one of the identified second service or the first service.