KR100901703B1 - Method for processing open asynchronous application service event and the open web service gateway which it embodies - Google Patents

Abstract

The present invention relates to an open asynchronous application service event processing method and an open web service gateway implementing the same. The present invention relates to an application service through a web service interface, receives an event registration request from the application service, and receives an event generated from a network. A plurality of Service Capability Features (SCFs) for notifying application services; When the event requested to be registered from the application service is an asynchronous event, the registered event is registered based on a predetermined policy, and when an event is generated from the network, the event is registered to the SCF according to the registered priority for the event. And an event broker for notifying the occurrence of the event, thereby allowing asynchronous events to be registered and notified based on a predetermined policy to prevent collision between SCFs and conflicts between application services and network operations. Has the effect of maximizing.

Open Asynchronous Application Service, Event Broker

Description

Method for processing open asynchronous application service event and the open web service gateway which it embodies}

The present invention relates to an open asynchronous application service event processing method and an open web service gateway implementing the same. In particular, the open asynchronous application service event processing method and the open web implementing the asynchronous event is registered and notified based on a predetermined policy. Relates to a service gateway.

The present invention is derived from the research conducted as part of the IT new growth engine core technology development project of the Ministry of Information and Communication and the Ministry of Information and Communication Research and Development. [Task Management Number: 2005-S-056-02, Title: Open API and Service Platform Technology Development].

In general, open web services gateway in open systems provides a standardized web services API (Application Programming Interface) so that third-party service providers can easily create services without knowledge of the underlying network.Presence, terminal status, terminal location, call Functions such as notification and short message transmission are provided in units of Service Capability Feature (SCF).

This open web services gateway provides an interface for application services that want to use SCF to call APIs in the form of web services. The APIs that application services invoke are divided into synchronous and asynchronous operations according to SCF functions. .

Here, the asynchronous operation is performed when notifying an event occurring in the network, such as presence, terminal status, terminal location, call notification, and the like.

On the other hand, prior to such an event notification process, the application service must precede the process of registering an event condition through an API provided by an open web service gateway.

That is, the asynchronous operation allows an event of interest to be pre-registered in an open web service gateway through an application service, and if an event pre-registered later occurs from the network, an event-related SCF notifies the application service of the event occurrence.

However, in the current event registration process, a case where a plurality of application services register an event for the same condition occurs, causing a collision of the event notification process.

That is, depending on the characteristics of the application service or event, there are various cases where only one application service call is allowed per event or it is necessary to sequentially notify different events for several application services. It is not considered.

Therefore, when a registered event occurs without a coordination procedure from a plurality of application services, an unexpected event notification is made and a method and apparatus for preventing a collision that may occur between an application service and an SCF in an open web service gateway are needed. .

An object of the present invention for solving the above problems is an open asynchronous application service event processing method and an open web service gateway that implements the event notification so that event notification is made without conflict between the application services and SCF in the open web service gateway. To provide.

According to an aspect of the present invention, an open web service gateway receives an event registration request from the application service in association with an application service through a web service interface, and receives the event generated from the network. A plurality of Service Capability Features (SCFs) that notify the service; And when the event requested to be registered from the application service is an asynchronous event, register the requested event based on a preset policy, and when an event is generated from the network, a previously registered priority for the event generated from the network. It includes an event broker for notifying events generated from the network to the SCF corresponding to the rank.

The event broker, when registering an event requested to be registered from the application service, if there is already event registration information for the same event as the event requested to be registered and a collision according to the event registration is predicted, the predicted collision In this case, the event registration priority is determined based on a policy corresponding to the event registration.

The event registration information may include at least one of an event type, an event target terminal number, an event registration SCF, an address of an endpoint, a registration date, and a priority.

When an event occurs from the network, the event broker identifies event registration information corresponding to the triggering condition by using the type of the event generated from the network and an event target terminal number as a triggering condition, and the event registration. It is characterized by notifying the occurrence of the event to the SCF included in the information.

When the number of event registration information corresponding to the triggering condition is one, the event broker notifies the occurrence of the event to the SCF included in the one event registration information, and the number of event registration information corresponding to the triggering condition is' When 2 'or more, the event occurrence is sequentially notified to the SCF included in each of the event registration information according to the priority of each event registration information.

When the number of event registration information corresponding to the triggering condition is '2' or more, the event broker determines the priority of the event registration information and if the event registration information having the priority of '0' is present, the priority is set. The event occurrence is notified to the SCF included in the event registration information '0', and if the event registration information having the priority '0' does not exist, the event registration information is included in each of the event registration information according to the priority of each event registration information. SCF is sequentially notified of the occurrence of the event.

If there is no event registration information whose priority is '0', the event broker determines the event registration information according to the priority of each event registration information when the number of SCFs included in the event registration information is '2' or more. The event generated from the network is sequentially notified to SCFs of 2 or more included in the event, and if the number of SCFs included in the event registration information is one, the event for each event registration information is sent to one SCF included in the event registration information. It is characterized by passing the type and priority of.

Each of the plurality of SCFs, when the type and priority of the plurality of events are transmitted from the event broker, sequentially transmitting from the event of the event registration information of the higher priority according to the priority to the corresponding application service It features.

Each of the plurality of SCFs may include a web service processor configured to provide a web service interface to the application service so that the application service is connected to the application service. Grasp the event requested to be registered from the connected application service, and classify it into asynchronous and synchronous events, and transmit a registration request for an asynchronously divided event to the event broker, and the event requested by the event broker is the application service. It characterized in that it comprises a logic processing unit to be transmitted to.

Preferably, the open web service gateway further comprises a policy DB for storing a plurality of policy data according to the policy.

Preferably, the open web service gateway further comprises a gateway OAM processing unit for generating, modifying and deleting the policy data.

An open asynchronous application service event processing method of an open web service gateway including a plurality of SCFs according to another aspect of the present invention for achieving the above object, an open web service gateway including a plurality of SCF (Service Capability Feature) An open asynchronous application service event processing method comprising: receiving an event registration request transmitted from an application service through at least one of the plurality of SCFs; An event registration step of registering the requested event for each SCF based on a predetermined policy when an event received through at least one of the plurality of SCFs is asynchronous; Receiving an event generated from a network; And an event notification step of notifying an event generated from the network to the application service through a corresponding SCF according to a priority determined by a predetermined policy.

The event registering step may include: determining whether there is already event registration information for the same event as the event for which registration is requested; If there is an event registration information for the same event and a collision is predicted according to the event registration, determining an event registration priority based on a policy corresponding to the predicted collision and registering the event; It is characterized by including.

The event registration step may be registered as event registration information including at least one of an event type, an event target terminal number, an event registration SCF, an address of an endpoint, a registration date, and a priority.

The event notification step may include identifying event registration information corresponding to the triggering condition by using a type of an event generated from the network and an event target terminal number as a triggering condition; And notifying an event generated from the network to a corresponding application service through the SCF included in the identified event registration information.

In the event notification step, when the number of event registration information corresponding to the triggering condition is one, an event generated from the network is notified to a corresponding application service through an SCF included in the one event registration information. .

In the event notification step, when the number of event registration information corresponding to the triggering condition is '2' or more, the priority of each event registration information is checked to determine whether there is event registration information having a priority of '0'. step; If there is event registration information having the priority '0', the event generated from the network is notified to the corresponding application service through the SCF included in the event registration information, and the event registration having the priority '0' is registered. If the information does not exist, checking whether the number of SCFs included in the determined event registration information is equal to or greater than '2'; When the number of SCFs identified from the event registration information is '2' or more, the event generated from the network is sequentially notified to '2' or more SCFs included in the event registration information according to the priority of the event registration information. It further comprises a step.

The event notification step may further include, when the number of SCFs identified from the event registration information is one, transferring the type and priority of the event for each event registration information to one SCF identified from the event registration information. It is characterized by.

The open asynchronous application service event processing method and apparatus according to the present invention as described above allows the asynchronous event to be registered and notified based on a predetermined policy, so that the collision between the SCF and the application service in advance for the event. Prevent and maximize the operation of the network.

In addition, the open asynchronous application service event processing method and apparatus according to the present invention as described above, the priority for event notification is determined based on the policy set by the operator, it is easy to change the dynamic event notification policy. Has the effect of doing so.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, in describing in detail the operating principle of the preferred embodiment of the present invention, if it is determined that the detailed description of the related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

In addition, the same reference numerals are used for parts having similar functions and functions throughout the drawings.

1 is a diagram illustrating a network configuration of an open system according to a preferred embodiment of the present invention.

Referring to FIG. 1, the open system may include an open web service gateway 100, an application service 200, and terminals 300a, 300b, and 300c interworking with a wired network, a wireless network, and an IP network.

Here, the open web service gateway 100 provides an interface through which an application service 200 that wants to use the SCF set therein can call an API in the form of a web service, and provides functions for a wireless network, a wired network, and an IP network. Abstract it as an open API and provide it as a web service.

The open web service gateway 100 may interoperate with at least one open application service 200, and may include at least one or more protocols, that is, WAP / WIN (Wireless Application Protocol / Wireless Intelligent Network) or INAP (Intelligent Network Application Protocol). ) And web services for multiple networks in conjunction with SIP (session initiation protocol).

 In addition, the open web service gateway 100 provides functions such as three-way call connection, call event notification, short / multimedia message transmission, presence, terminal status information, terminal location notification, and the like, so that each function may be implemented through a different SCF. do.

The application service 200 performs an open application service by interworking with the open web service gateway 100 using an application service logic and an open API.

Meanwhile, the open web service gateway 100 registers an event requested to be registered from the application service 200 according to a preset policy, and notifies the application service 200 of the event generated from the network according to the registered priority. can do.

Next, look at the open web service gateway 100 in more detail.

2 is a block diagram showing an open web service gateway according to an embodiment of the present invention.

As shown in FIG. 2, the open web service gateway 100 includes a plurality of SCFs including a web service processing unit 110 and a logic processing unit 120, an event broker 130 including an event DB 140, and a policy DB. 150, the protocol message processor 160 and the gateway OAM processor 170 may be configured.

In such an open web service gateway 100, the web service processing unit 110 of each SCF provides a web service interface to the application service 200, so that the application service 200 opens the web service gateway 100 through the web service interface. )).

The logic processing unit 120 is responsible for actual SCF functions such as presence, terminal status, terminal location, call notification, short message transmission, and the like, and requests for event registration of the application service 200 transmitted through the interworking web service processing unit 110. Implement the event registration processing logic for.

The event broker 130 implements event registration logic for event registration requests sent from SCFs that require asynchronous operation processing, that is, event registration and notification functions, and implements event notification logic for events generated from the network. Thus, an event requiring registration and notification may be registered and notified based on the policy of the policy DB 150 described later.

The event broker 130 manages event registration information of an event requested to be registered through the event DB 140, and the managed event registration information is adjusted based on policy data obtained from the policy DB 150. Be sure to

Accordingly, in implementing the event registration logic for the event registration request, the event broker 130 checks whether there is a conflict with the existing event registration information stored in the event DB 140 for the event that is requested to be registered, and conflicts with the inspection result. If there is a surname, it adjusts the collision according to the policy retrieved from the policy DB 150 and then registers the requested event.

The policy DB 150 stores and manages policy data input by an operator through the gateway OAM processing unit 170.

The protocol message processing unit 160 performs a function of providing an event requested for registration from the application service 200 to a network, and performs a function of notifying an SCF of an event generated from the network.

Next, the event registration information of the open web service gateway 100 having such a configuration will be described in detail.

3 is a view showing an event registration information table according to an embodiment of the present invention.

This is managed from event DB 140.

Referring to FIG. 3, event registration information is managed in a table, event type, event target terminal number information, event registration SCF, address of an endpoint (eg, uniform resource locator), and registration. The event target terminal number information and the type of the event among the information, including the date and priority, are event triggering conditions, so as to grasp the corresponding condition of the type of the event being requested and notify the notification request event registration SCF. do.

In the event registration information table, the priority and registration date serve to notify the event broker 130 of the event triggering condition generated event to the corresponding SCF sequentially.

That is, the event broker 130 gives the highest priority to an event having a priority of '0' at the time of event notification so that it is notified exclusively, and the registration date and priority for an event whose priority is not '0'. To be notified in ascending order.

Next, the operation of the open web service gateway 100 that performs event registration and notification will be described in detail.

4 is a signal flow diagram illustrating an asynchronous event registration process of an open web service gateway according to an embodiment of the present invention.

As shown in FIG. 4, the application service 200 that wants to generate an event for a network accesses the SCF web service processing unit 110 in the open web service gateway 100 through a web service interface, and then registers an event. Call event registration API for the request (S101).

When the event registration request is requested from the application service 200 according to the event registration API call, the web service processor 110 calls the event registration processing logic of the logic processor 120 (S102), and the logic processor 120 receives the event. Through the implementation of the registration processing logic to determine whether the event requested to be registered from the application service 200 requires asynchronous or synchronous operation processing (S103).

When the event condition requested to be registered from the application service 200 is synchronously determined through event registration processing logic, the logic processing unit 120 transmits the requested event to the protocol message processing unit 160 through a protocol message. When the event is provided to the network (S104), and the event requested to be registered from the application service 200 is determined to require asynchronous operation processing, the event broker 130 requests the registration of the corresponding event (S105). ).

Next, when event registration is requested from the logic processing unit 120 of the SCF, the event broker 130 performs event registration logic based on policy information obtained from the policy DB 150 to register the corresponding event (S106). ).

In addition, when the event broker 130 registers the event requested to be registered according to the event registration logic in the event DB 140, the event broker 130 transmits the registered event to the protocol message processor 160 through the protocol message and provides the corresponding event to the network. (S107).

5 is a flowchart illustrating event registration logic of an open web service gateway according to an exemplary embodiment of the present invention.

The event registration logic shown in FIG. 5 is event registration logic performed from the event broker 130 of the open web service gateway 100.

Thus, referring to FIG. 5, when event registration is requested from the logic processing unit 120 of the SCF, the event broker 130 first grasps the requested event of registration (S201), and checks the event registration information table of the event DB 140. Call (S202).

Next, the event broker 130 checks whether the same type of event as the event requested for registration exists from the called event property information table (S203), and determines that the same type of event does not exist as a result of the inspection. If the registration event requested to register in the event DB (140) (S204).

However, when the event broker 130 determines that an event registration conflict occurs due to the registration of the event requested because the event type exists in the event registration information table, the event type equal to the type of the event requested to be registered exists. In step S205, the policy DB 150 is retrieved and the policy data corresponding to the event registration collision case predicted to occur is called (S206).

In this case, the event registration conflict may be an event registration conflict within the same SCF, an event registration conflict between multiple SCFs, or an event registration conflict between the application servers 200.

That is, the event registration conflict is when the event registration request event SCF already exists, when the same event as the event requested to be registered from any SCF is already registered from another SCF, the event registration request application service 200 This may occur when there is an event of.

Accordingly, the event broker 130 determines the event registration priority based on the called policy, and then registers the event requested to be registered in the event DB 140 including the determined priority (S207).

If the event registration priority is not determined based on the called policy data, the event broker 130 may access the gateway OAM processing unit 170 and request the supplementation of the called policy.

6 is a signal flow diagram illustrating an event notification process of an open web service gateway according to an exemplary embodiment of the present invention.

As shown in FIG. 6, in the open web service gateway 100, when the protocol message processing unit 160 receives an event generated from a network (S301), an event received through a protocol message is sent to the event broker 130. It transmits (S302).

When the event is transmitted from the protocol message processing unit 160, the event broker 130 performs event notification logic (S303), and delivers the event to the SCF identified as a corresponding event delivery target according to the event notification logic (S304).

Accordingly, the SCF receives the event delivered from the event broker 130 through the logic processor 120, checks the application service 200 to notify the received event, and then calls the event notification API call from the web service processor 110. The event notification is made to the confirmed application service 200 (S305, S306).

7 is a flowchart illustrating event notification logic of an open web service gateway according to an exemplary embodiment of the present invention.

The event notification logic shown in FIG. 7 is the event notification logic performed from the event broker 130 of the open web service gateway 100.

Thus, referring to FIG. 7, when an event is received from the protocol message processor 160 (S401), the event broker 130 calls an event registration information table from the event DB 140 (S402).

Then, the event broker 130 checks the event registration information corresponding to the received event from the event registration information table, and checks whether the number of the event registration information that is found is '2' or more (S403).

When the event broker 130 determines that the number of event registration information corresponding to the received event is one other than '2', the event broker 130 transmits the received event to the SCF included in the corresponding event registration information (S404). ).

However, if it is determined that the number of event registration information corresponding to the received event is '2' or more, the event broker 130 determines the priority of each event registration information to determine whether there is event registration information having a priority of '0'. Check whether or not (S405).

If the event broker 130, as a result of the check, has event registration information having a priority of '0', the event broker 130 delivers the received event to the SCF included in the event registration information (S406), and the priority is '0'. If the event registration information does not exist, it is checked whether the number of SCFs identified from the event registration information corresponding to the received event is '2' or more (S407).

Accordingly, when the event broker 130 determines that the number of SCFs identified from the event registration information is '2' or more, the event broker 130 sequentially processes the received events with the SCFs included in the event registration information according to the priority of the event registration information. Transfer to (S408).

When the number of SCFs identified from the event registration information is one other than '2', the event broker 130 determines that the event registration information corresponding to the received event is event registration information generated from one SCF. In operation S409, the type and priority of an event included in each event registration information are transmitted to a corresponding SCF.

Here, the SCF may sequentially transmit the event of the event registration information having high priority according to the priority of the event registration information received from the event broker 130 to the corresponding application service 200.

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and it is common in the art that various substitutions, modifications, and changes can be made without departing from the technical spirit of the present invention. It will be apparent to those skilled in the art.

1 is a diagram showing a network configuration of an open system in a preferred embodiment of the present invention;

2 is a block diagram showing an open web service gateway according to an embodiment of the present invention;

3 is a view showing an event registration information table according to an embodiment of the present invention;

4 is a signal flow diagram illustrating an asynchronous event registration process of an open web service gateway according to an embodiment of the present invention;

5 is a flowchart illustrating event registration logic of an open web service gateway according to an embodiment of the present invention;

6 is a signal flow diagram illustrating an event notification process of an open web service gateway according to an embodiment of the present invention;

7 is a flowchart illustrating event notification logic of an open web service gateway according to an exemplary embodiment of the present invention.

* Description of the symbols for the main parts of the drawings *

100: open web service gateway 110: SCF web service processing unit

120: SCF logic processing unit 130: event broker

140: event DB 150: policy DB

160: protocol message processing unit 170: gateway OAM processing unit

200: application service 300: terminal

Claims (18)

A plurality of Service Capability Features (SCFs) for receiving an event registration request from the application service in association with an application service through a web service interface, and notifying the application service of an event generated from a network; And If the event requested to be registered from the application service is an asynchronous event, the registered event is registered based on a preset policy. If an event is generated from the network, the previously registered priority is applied to an event generated from the network. An open web services gateway including an event broker that notifies an event generated from the network to an SCF corresponding to a rank. The method of claim 1, The event broker, In registering the event requested to be registered from the application service, if event collision information for the same event as the registration request event already exists and a collision according to the registration of the registration request event is predicted, And an event registration priority based on a policy corresponding to a case, to register the requested event. The method of claim 2, The event registration information, An open web service gateway comprising at least one of an event type, an event target terminal number, an event registration SCF, an address of an endpoint, an registration date, and a priority. The method of claim 3, The event broker, When an event occurs from the network, the event registration information corresponding to the triggering condition is determined by using the type of the event generated from the network and the event target terminal number as the triggering condition, and the SCF included in the identified event registration information. Open web service gateway, characterized in that to notify the event generated from the network. The method of claim 4, wherein The event broker, When the number of event registration information corresponding to the triggering condition is one, an event generated from the network is notified to the SCF included in the one event registration information, and the number of event registration information corresponding to the triggering condition is '2'. In the case of the above, the open web services gateway according to the priority of each event registration information, the event generated from the network to the SCF included in each of the event registration information sequentially. The method of claim 5, The event broker, When the number of event registration information corresponding to the triggering condition is greater than or equal to '2', the priority of the event registration information is determined, and if the event registration information having the priority of '0' exists, the event having the priority of '0' Notify the event generated from the network by the SCF included in the registration information, and if there is no event registration information with the priority '0' to the SCF included in each of the event registration information according to the priority per event registration information Open web service gateway, characterized in that to sequentially notify the events generated from the network. The method of claim 6, The event broker, If the event registration information having the priority of '0' does not exist, and if the number of SCFs included in the event registration information is '2' or more, '2' included in the event registration information according to the priority of the event registration information The SCF is notified of events generated from the network in sequence, and if the number of SCFs included in the event registration information is one, the type and priority of the event according to the event registration information to one SCF included in the event registration information. Open web services gateway, characterized in that for delivering. The method of claim 7, wherein Each of the plurality of SCFs, When the type and priority of the event for each event registration information is transmitted from the event broker, the open web, characterized in that for sequentially transmitting from the event of the event registration information of high priority according to the priority to the corresponding application service Service gateway. The method of claim 1, Each of the plurality of SCFs, A web service processor configured to provide a web service interface to the application service so that the application service is connected; And Grasp the event requested to be registered from the connected application service, and classify it into asynchronous and synchronous events, and transmit a registration request for an asynchronously divided event to the event broker, and the event requested by the event broker is the application service. Open web service gateway comprising a logic processing unit to be transmitted to. The method of claim 1, An open web service gateway, characterized in that it further comprises a policy DB for storing a plurality of policy data according to the policy. The method of claim 10, And a gateway OAM processing unit for creating, modifying, and deleting the policy data. In the open asynchronous application service event processing method of an open web services gateway including a plurality of service capability (SCF), Receiving an event registration request transmitted from an application service through at least one of the plurality of SCFs; An event registering step of registering the registered event based on a predetermined policy when an event received through at least one of the plurality of SCFs is asynchronous; Receiving an event generated from a network; And And an event notification step of notifying an event generated from the network to the application service through a corresponding SCF according to a priority determined by a predetermined policy. The method of claim 12, The event registration step, Determining whether event registration information for the same event as the registered request event already exists; And If there is an event registration information for the same event and a collision is predicted according to the registration of the requested event, the registration request is determined after determining an event registration priority based on a policy corresponding to the predicted collision. And registering the registered event. The method of claim 13, The event registration step, An open asynchronous application service event processing method according to claim 1, wherein the event registration terminal comprises at least one of event type, event target terminal number, event registration SCF, address of endpoint, registration date and priority. The method of claim 14, The event notification step, Identifying event registration information corresponding to the triggering condition by using a type of an event generated from the network and an event target terminal number as a triggering condition; And And informing the corresponding application service of an event generated from the network through the SCF included in the determined event registration information. The method of claim 15, The event notification step, When the number of event registration information corresponding to the triggering condition is one, an open asynchronous application service event process of notifying the corresponding application service of an event generated from the network through an SCF included in the one event registration information. Way. The method of claim 15, The event notification step, If the number of event registration information corresponding to the triggering condition is greater than or equal to '2', checking whether the event registration information having the priority of '0' exists by checking the priority of the event registration information; If there is event registration information having the priority '0', the event generated from the network is notified to the corresponding application service through the SCF included in the event registration information, and the event registration having the priority '0' is registered. If the information does not exist, checking whether the number of SCFs included in the determined event registration information is equal to or greater than '2'; And When the number of SCFs identified from the event registration information is greater than or equal to '2', sequentially notifying events generated from the network to '2' or more SCFs included in the event registration information according to the priority of the event registration information; Open asynchronous application service event processing method characterized in that it further comprises. The method of claim 17, The event notification step, And when the number of SCFs identified from the event registration information is one, transmitting the type and priority of the event for each event registration information to one SCF identified from the event registration information. How to handle application service events.

Images