Maintenance of third party service's subscription information

• US 7,185,087 B2
• Filed: 08/23/2002
• Issued: 02/27/2007
• Est. Priority Date: 10/26/2001
• Status: Expired due to Fees

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Gourraud, Christophe
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Refai; Ramsey
• Application Number:
  US10/226,274
• Publication Number:
  US 20030084147A1
• Time in Patent Office: 1,649 Days
• Field of Search: 709/204, 709/207, 709223-226, 709/240, 709/220, 719/318, 707/1, 707/2
• US Class Current: 709/224
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5032 Generating service level reports
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing

Abstract

The present invention relates to two methods, an apparatus and to a Service Capability Server (SCS) for controlling interactions between a network and a third party service. The SCS comprises capabilities for receiving a trigger request for at least one event from the third party service. The SCS is also capable of communicating with an apparatus in the network to add a trigger in a trigger table of the apparatus and capable of receiving a notification from the trigger table of an occurrence of the at least one event. The notification comprises the third party service reference, the reference to the at least one event and a reference to at least one user registered to the third party service within the network. The SCS is further capable of informing the third party service of the received notification of the occurrence of the at least one event.

Claims

1. An apparatus for managing registration of users of a network to a third party service, the third party service being provided from outside the network, the apparatus performing the steps of:

receiving a registration request from a user, registration requests includes a third party service reference which refers to a third party service that the user is registered to;

generating a registration record for the registration request in a registration table, the registration record comprises;

the third party service reference from the registration request; and

a reference to the user from which the registration request has been received;

receiving a trigger request from a Service Capability Server (SCS), the trigger request being originally sent by a third party service to the SCS

generating a trigger record for the trigger request in a trigger table, the trigger request and the trigger record comprising;

a reference to at least one event for which the third party service needs to be notified of; and

a reference to the third party service from which the trigger request has been received; and

upon detection of an event in the network;

checking the trigger table to find a correspondence between the detected event and the trigger record;

if a correspondence is found, sending an event notification to the SCS, the event notification comprising;

the corresponding reference to the detected event;

the corresponding third party service reference; and

the corresponding reference of the user associated with the third party service; and

forwarding the event notification from the SCS to the corresponding third party service identified in the event notification, wherein the third party service can then provide a service to the user.

2. The apparatus of claim 1 wherein the reference to the user is provided by the network.

3. The apparatus of claim 1 wherein the third party service reference is an Internet Protocol address.

4. A Service Capability Server (SCS) for controlling interactions between a network and a third party service, the third party service being provided from outside the network, the SCS performing the steps of:

receiving a trigger request for at least one event from the third party service, the third party request comprising;

a reference to the at least one event for which the third party service needs to be notified of; and

a reference to the third party service from which the trigger request has been received; and

communicating with an apparatus in the network to generate a trigger record in a trigger table of the apparatus, the trigger record, corresponding to the received trigger request, comprises;

the reference to the at least one event for which the third party service needs to be notified of; and

the reference to the third party service from which the trigger request has been received upon detection of an event on the network by the apparatus, and a correspondence between the detected event and the trigger table has been found by the apparatus, receiving an event notification from the apparatus, the event notification comprising;

the corresponding reference to the detected event;

the corresponding third party service reference; and

the corresponding reference of a user associated with the third party service; and

forwarding the event notification to the corresponding third party service identified in the event notification, wherein the third party service can then provide a service to the user.

5. The SCS of claim 4 wherein the reference to the user is provided by the network.

6. The SCS of claim 4 wherein the third party service reference is an Internet Protocol address.

7. A method for managing third party service'"'"'s registration information within a network, the third party service being provided from outside the network, the network and the third party service interacting with each other through a Service Capability Server (SCS), the method comprising steps of:

receiving a registration request from a user by an apparatus in the network, the registration request includes a third party service reference, which refers to a third party service that the user is registered to;

generating a registration record for the registration request in a registration table on the apparatus, the registration record comprising;

the third party service reference from the registration request; and

a reference to the user from which the registration request has been received;

receiving a trigger request from a Service Capability Server (SCS), the trigger request being originally sent by a third party service to the SCS;

generating a trigger record for the trigger requests, the trigger record being part of a trigger table, the trigger request and the trigger record comprising;

a reference to at least one event for which the third party service needs to be notified of; and

a reference to the third party service from which the trigger request has been received; and

upon detection of an event in the network;

checking the trigger table to find a correspondence between the detected event and the trigger record;

if a correspondence is found, sending an event notification to the SCS, the event notification comprising;

the corresponding reference to the detected event;

the corresponding third party service reference; and

the corresponding reference of the user associated with the third party service; and

forwarding the event notification from the SCS to the corresponding third party service identified in the event notification, wherein the third party service can then provide a service to the user.

8. The method of claim 7 wherein the step of forwarding the event notification further comprises:

analyzing an existing Service Level Agreement (SLA) between the network and the third party service; and

adding the trigger record in an apparatus of the network in accordance with the SLA.

9. The method of claim 7 wherein the reference to the third party service is an Internet Protocol address.