Method of processing open asynchronous application service event and open web service gateway implementing the same

• US 8,046,419 B2
• Filed: 11/29/2007
• Issued: 10/25/2011
• Est. Priority Date: 12/01/2006
• Status: Expired due to Fees

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Choi, Young Il, Chung, Ki Sook, Lee, Byung Sun
• Primary Examiner(s): Bates; Kevin
• Assistant Examiner(s): MCADAMS, BRAD
• Application Number:
  US11/947,363
• Publication Number:
  US 20080133683A1
• Time in Patent Office: 1,426 Days
• Field of Search: 709/206, 709/207
• US Class Current: 709/207
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A method of processing an open asynchronous application service event and an open web service gateway implementing the method are provided. The open web service gateway includes: a plurality of SCFs (service capability features) operatively connected to an application service through a web service interface, receives an event registration request from the application service, and notifies an event occurring in a network to the application service; and an event broker registering the registration-requested based on a predetermined policy in correspondence with the SCFs, when the registration-requested event received from the application service is an asynchronous event, and notifies an occurrence of the event in the network to the SCFs according to a registered priority of the event. Accordingly, an asynchronous event is registered and notified based on a predetermined policy, so that it is possible to prevent event registration conflict between the SCFs and between the application services and to maximize network operation efficiency.

Claims

1. An open web service gateway comprising:

a memory;

a plurality of service capability features (SCF) processors operatively connected to an application service through a web service interface, and configured to receive a registration request for a first event from the application service and to notify a second event occurring in a network to the application service; and

an event broker configured to register the first event based on a predetermined policy in correspondence with the SCF processors if the first event received from the application service is an asynchronous event, and to notify an occurrence of the second event in the network to a corresponding SCF processor according to a registered priority of the second event.

2. The open web service gateway of claim 1, wherein, when an event registration conflict is predicted in the registration of the first event due to existence of event registration information on an event equal to the first event, the event broker determines an event registration priority based on a policy corresponding to the predicted conflict to register the first event.

3. The open web service gateway of claim 2, wherein the event registration information includes one or more of event information, event-associated terminal number information, event registration SCF information, EndPoint information, registration date information, and priority information.

4. The open web service gateway of claim 3, wherein when the second event is occurred in the network, the event broker uses information of the second event and an event-associated terminal number as a triggering condition to determine event registration information corresponding to the triggering condition and notifies the occurrence of the second event to an SCF processor corresponding to the determined event registration information.

5. The open web service gateway of claim 4,

wherein, when the number of the event registration information corresponding to the triggering condition is one, the event broker notifies the occurrence of the second event to an SCF processor corresponding to the one event registration information, and

wherein, when the number of the event registration information corresponding to the triggering condition is two or more, the event broker sequentially notifies the occurrence of the second event to SCF processors corresponding to the two or more event registration information according to priorities of the two or more event registration information.

6. The open web service gateway of claim 5,

wherein, when the number of the event registration information corresponding to the triggering condition is two or more, the event broker determines the priorities of the two or more event registration information,

wherein, if there is event registration information having a priority of 0, the event broker notifies the occurrence of the second event to an SCF processor corresponding to the event registration information having the priority of 0, and

wherein, if there is no event registration information having the priority of 0, the event broker sequentially notifies the occurrence of the second event to the SCF processors corresponding to the two or more event registration information according to the priorities of the two or more event registration information.

7. The open web service gateway of claim 6,

wherein, when there is no event registration information having the priority of 0, the event broker determines whether or not the number of the SCF processors corresponding to the two or more event registration information is two or more,

wherein, if the number of the SCF processors is two or more, the event broker sequentially notifies the occurrence of the second event to the SCF processors corresponding to the two or more event registration information according to the priorities of the two or more event registration information, and

wherein, if the number of the SCF processors is one, the event broker transmits a plurality of event information and priority information corresponding to the two or more event registration information to the one SCF processor.

8. The open web service gateway of claim 7, wherein, when the plurality of event information and priority information is transmitted from the event broker, the one SCF processor sequentially transmits events corresponding to the two or more event registration information to the application service in the order of the priorities included in the priority information.

9. The open web service gateway of claim 1, wherein each of the SCF processors comprises:

a web service processing unit configured to provide the web service interface to the application service so that the application service can access to the SCF processor, and

a logic processing unit configured to identify whether the first event is an asynchronous or synchronous event, to transmit the registration request of the first event identified as the asynchronous event to the event broker, and to transmit the second event received from the event broker to the application service.

10. The open web service gateway of claim 1, further comprising a policy DB configured to store a plurality of policy data corresponding to the predetermined policy.

11. The open web service gateway of claim 1, further comprising a gateway OAM (operation-and-maintenance) processing unit configured to generate, modify, and remove a plurality of policy data corresponding to the predetermined policy.

12. A method of processing an open asynchronous application service event in an open web service gateway including a plurality of SCF processors, the method comprising:

receiving a registration request of a first event transmitted from an application service through at least one of the SCF processors;

registering the first event based on a predetermined policy when the first event is an asynchronous event;

receiving a second event occurring in a network; and

notifying the second event to the application service through a corresponding SCF processor according to a priority determined based on the predetermined policy.

13. The method of claim 12, wherein the registering of the first event comprises:

determining whether or not event registration information on an event equal to the first event already exists; and

determining an event registration priority based on a predetermined policy to register the first event when an event registration conflict is predicted in the registration of the first event due to the existence of the event equal to the first event.

14. The method of claim 13, wherein the event registration information includes one or more of event information, event-associated terminal number information, event registration SCF information, EndPoint information, registration date information, and priority information.

15. The method of claim 14, wherein the notifying the second event comprises:

using event information and event-associated terminal number information of the second event as a triggering condition to determine event registration information corresponding to the triggering condition; and

notifying the second event to the application service through an SCF processor corresponding to the determined event registration information.

16. The method of claim 15, wherein the second event is notified to the application service through an SCF corresponding to one event registration information when the number of the event registration information corresponding to the triggering condition is one.

17. The method of claim 15, wherein the notifying of the second event further comprises:

if the number of event registration information corresponding to the triggering condition is two or more, determining priorities of the two or more event registration information, and determining whether or not there is event registration information having a priority of 0;

if there is event registration information having the priority of 0, notifying the second event to the application service through an SCF processor corresponding to the event registration information having the priority of 0 and, if there is no event registration information having the priority of 0, confirming whether or not the number of SCF processors corresponding to the two or more event registration information is two or more; and

if the number of SCF processors is confirmed two or more, sequentially notifying the second event to the application service through said SCF processors according to priorities of the two or more event registration information.

18. The method of claim 17, wherein the notifying of the second event notification further comprises sequentially notifying events of the two or more registration information to the application service, starting from the event corresponding to the highest priority, according to the priorities of the two or more event registration information when the number of the SCF processors determined from the two or more event registration information is one.