KR20070061067A - Method and system for handling the network events in application server using open api based web services - Google Patents

Abstract

A method and a system for notifying a service application of a communication event in an application server supporting a web service-based open API are provided to improve extensibility of a service application by using an event table without hard coding in the search application. The event table(140) stores detail information related to a plurality of events. A service provisioning manager(130) stores the detail information related to the events to the vent table. The service application(110) requests a gateway(200) to start the notification for the event or terminate the notification. An event notification API processor(120) processes the notification of the event received from the gateway by using the detail information related to the events stored in the event table. The event table includes information fields for an ID, event receiving IP(Internet Protocol) address, and event receiving communication port number of a service, the number of activated events, and event information.

Description

Apparatus and method for notifying network events in an application server supporting web services based open APIs {Method and system for handling the network events in application server using open API based web services}

1 is a block diagram illustrating a network connection configuration of a communication network event notification device and an application server in an application server supporting a web service based open API according to the present invention.

2 is a structural diagram of an event table shown in FIG. 1 according to the present invention.

3 is an operation flowchart illustrating a service provisioning method provided by a service provisioning manager in an event notification device according to the present invention.

4 is an operation flowchart illustrating a dynamic event notification request method of a service application in the event notification device according to the present invention.

5 is an operation flowchart illustrating an event notification method in an event notification API processor of the event notification device according to the present invention.

6 is an operation flowchart illustrating a method for requesting termination of dynamic event notification of a service application in the event notification device according to the present invention.

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

100: application server 110: service application

120: API handler for event notification 130: Service Provisioning Manager

140: event table 200: gateway

300: communication network 400: user terminal

The present invention relates to a network event notification device and method in an application server supporting a web service based open API.

In general, a general and simple event notification method in a system supporting an open API is described in the prior patent (Korean Patent Laid-Open Publication No. 2003-0079544), and a general event notification method in a system that is not related to an open system. Korean Patent Publication No. 2004-0004362.

The former patent (Korean Patent Laid-Open Publication No. 2003-0079544) relates to a method for providing a series of processes to register an event and notify an event after installing a service in an application server processing an open API called Parlay. Patent. However, such a technique can handle only static events that must be registered in advance before performing a service, such as a trigger event, and can not process dynamic events that request service notification of interest at runtime. The proposed technique has a disadvantage that it cannot be applied to an application server supporting an open API based on web services.

On the other hand, the latter prior patent (Korean Patent Laid-Open Publication No. 2004-0004362) relates to a very general and basic event notification mechanism that is performed in a general system, and maps indicating correlations between event requesters, notifiers, and notification parameters ( If the event manager is notified of the event from the event notifier after registering the map and the parameter dictionary in advance, the appropriate event requester is detected by referring to the registered map and the notification parameter dictionary, and then the detected event requester is notified of the event. . Because it uses a map and parameter dictionary, even if various events are added, it is possible to modify the map and parameter dictionary without changing the event notification method.

However, this is not applicable to a system supporting a web service based open API, and event notification or a parameter dictionary provided by the above patent is not possible in a system supporting a web service based open API.

Accordingly, the present invention is to solve the above problems according to the prior art, an object of the present invention, in the application server supporting a web service-based open API to support both the notification of static events and dynamic events Web The present invention provides a network event notification device and a method in an application server supporting a service-based open API.

In addition, another object of the present invention is to support a web service-based open API that can improve the scalability of a service application by using an event table without having to hard-code routines necessary to notify an event in the service application. An application server provides a network event notification device and a method thereof.

In order to achieve the above object, a communication network event notification apparatus in an application server supporting a web service-based open API according to the present invention includes: an event table for storing a plurality of event related details; A service provisioning manager for storing event related detailed information in the event table to notify an event; A service application requesting to start notification of a specific event or requesting to end an event notification; It may include an event notification API processor for processing the event notification to the service application using the event-related detailed information stored in the event table for the event received from the gateway by the request of the service application.

The event table includes a service ID, an IP address for event reception of a service, a communication port number for event reception of a service, the number of activated events, and an information field for each event.

The event information stored in the information field for the event includes a correlator, which is information for associating an event type, an event requested by a service, and an event notified by a gateway later, and an API handler for event notification. Contains reference information.

The service provisioning manager creates a new record in the event table and then assigns a service ID to perform the provisioning procedure, and communicates with the service ID assigned to the generated record and the IP address for receiving the service. Port number, information about static events as many as static events, the value of active event count field for counts for static events, static event type for all registered static events and API handler for event notification for that event. As much as the number of references and dynamic events, information about dynamic events is stored in the corresponding fields.

In the service provisioning manager, the information about the static event records the value of the event type [i] field corresponding to the received event as TRUE, and the correlator [i] field corresponding to the received event. The value is recorded as a default value of 0, and the reference value of the notification API processor corresponding to the received event is input, and the value of the corresponding event notification API processor reference [i] field is recorded as the input value.

In the service provisioning manager, a value for receiving a value of a corresponding event notification API processor reference [i] field by receiving a reference value of a notification API processor corresponding to the received event. Record as.

The service application, a) finds a record corresponding to its service ID in the event table, records the value of the event type [i] field corresponding to a desired event as TRUE, and generates a correlation value, Record the value of the correlator [i] field corresponding to the desired event in the record as the generated correlation value; b) extract the value of the reference [i] field to the event notification API handler corresponding to the desired event from the record; After increasing the value of the activated event count field in the record by 1, the gateway is called with the reference to the extracted event notification API processor and the generated correlation value as an input parameter to request the start of event notification.

The service application, a) finds the record corresponding to its service ID in the event table, modifies the value of the event type [i] field corresponding to the desired event in the record to false, and the desired event in the record. After extracting the value of the correlator [i] field corresponding to, modify the value of the correlator [i] field to a default value of 0, b) decrease the value of the activated event count field by 1, and then extract the correlation value. Calls the gateway with an input parameter to terminate the event notification.

When there is a call from the gateway, the event notification API processor finds a record corresponding to its service ID in the event table, extracts a value of an event type [i] field corresponding to an event notified from the gateway. If the extracted value is true, the value of the corrlelator [i] field corresponding to the event notified from the gateway is extracted. If the extracted value is 0, the IP address and communication port for event reception of the service are recorded in the record. After the extraction, the extracted value is used to notify the service application of the event.

When the extracted value is not 0, the event notification API processor compares the extracted correlation value with a correlation value passed from the gateway to a parameter. After extracting the address and communication port, the extracted value is used to notify the service application of the event.

The service application, event notification API handler, and service provisioning manager support a web service-based open API that supports the Parlay X API standardized by the Parlay / OSA group.

Meanwhile, according to an aspect of a method for notifying an event to a service application in an application server supporting a web service based open API according to the present invention, storing event related detailed information in an event table to notify an event to the service application. step; In order to notify the service application of the event, request the gateway to start notification of a specific event, and process the event notification using the event related details stored in the event table for the event corresponding to the event received from the gateway. Thereafter, the method may include requesting the gateway to terminate the event notification.

The storing of the event related detailed information may include: initializing a new record in the event table; Assigning a service ID and recording the assigned service ID in the generated record; Receiving an IP address and a communication port number of a service and recording the same in a record; Receiving information on a static event as many as the number of static events and recording the information in a record; Recording the count for the static event as the value of the activated event count field; Registering a static event type and an event notification reference for the corresponding event with the gateway for all the registered static events; And receiving information about the dynamic event as many as the number of dynamic events that the service application is interested in and recording the information in the record.

Receiving the information about the static event and recording in the record, recording the value of the event type [i] field corresponding to the received event as true (true); Recording a value of a correlator [i] field corresponding to the received event as a default value of 0; And receiving a reference value of the notification API processor corresponding to the received event and recording the value of the corresponding event notification reference [i] field as an input value.

In the receiving of the information about the dynamic event and recording the record, the reference value of the notification API processor corresponding to the received event is input, and the value of the corresponding event notification API processor reference [i] field is received. Recording to a value.

The request for starting notification of a specific event to the gateway may include: finding a record corresponding to a service ID of the gateway in the event table; Recording the value of the event type [i] field corresponding to the desired event in the record as true; Generating a correlation value which is information for associating whether an event requested by the service and an event notified later by the gateway are the same; Recording a value of a correlator [i] field corresponding to a desired event in the record as a generated correlation value; Extracting a value of a reference [i] field of the event notification API processor corresponding to the desired event from the record; Increasing the value of the activated event count field in the record by one; Calling the gateway with an input parameter of the extracted event notification API handler and the generated correlation value.

The request for terminating the notification of the specific event to the gateway may include: finding a record corresponding to the service ID of the gateway in the event table; Modifying the value of the event type [i] field corresponding to the desired event in the record to false; Extracting the value of the correlator [i] field corresponding to the desired event from the record, and then modifying the value of the correlator [i] field to a default value of 0; Decreasing the value of the activated event count field in the record by one; Calling the gateway with the extracted correlation value as an input parameter.

The event notification processing using the event related detailed information stored in the event table as an event corresponding to the event notified by the gateway, when there is a call from the gateway, finds a record corresponding to its service ID in the event table. step; Extracting a value of an event type [i] field corresponding to an event notified from the gateway in a record; If the extracted value is true, extracting a value of a corrlelator [i] field corresponding to an event notified by a gateway; If the value of the extracted event type [i] field is 0, the event event IP address and communication port of the service are extracted from the record and the event is transmitted to the service application using the extracted event reception IP address and communication port. It includes the step of delivering.

Comparing the extracted correlation value with a correlation value passed from the gateway to a parameter when the value of the extracted event type [i] field is not the default value 0; As a result of the comparison, if the two correlation values coincide with each other, the event reception IP address and communication port of the service are extracted from the record and the event is notified to the service application using the extracted event reception IP address and communication port.

The application server supports a web service based open API supporting Parlay X API standardized by Parlay / OSA group.

Prior to the description of an apparatus and method for notifying a network event in an application server supporting a web service based open API according to the present invention, the application field of the present invention will be briefly described.

The open web API based on the present invention is a Parlay X API standardized by a standardization group called OSA / Parlay.

The systems required to support the Parlay X API are largely an application server (AS), a gateway, a communication network, and a terminal. The application server provides an overall environment for executing a service application. The service application written by the service programmer is mounted on the application server and executed. The gateway acts as a middleware between the application server and the communication network. The communication network and the terminal represent a conventional wired or wireless communication network and the communication terminal.

The Parlay X API includes the APIs that the service application needs to request gateway access to the network, the APIs that the service application requests to start event notification from the gateway, or end the event notification, and the notifications that the gateway needs to notify network events. There is an API for it. The first and second of these APIs are both implemented at the gateway, and the third is implemented at the service application side.

Service applications that use the Web services-based open API require two kinds of event notifications. One is to notify the static event that should be registered in advance before the service application is executed, and request that the service application notify the event as needed at runtime, then terminate the event notification after receiving the event notification. There is a notification of the requesting dynamic event.

A service application that uses a web service-based open API consists of three elements: First, it is the main logic part of the service, which contains the main logic that the service ultimately wants to perform. Second, we need web service client code to request the open API of the gateway. Third, a web service server that implements an API for receiving communication network events from a gateway is required. The first and second of these are usually implemented as one program, and the third is implemented as a web service server, which is an independent program. Logically, however, all three elements make up a service application.

In order for a service application to run on an application server, the service must be provisioned. The information that should be provided to the application server regarding event processing in the provisioning phase includes the following information.

First, a reference of a web service server that implements an open API for event notification for each service ID, the type of static event that the service is interested in, the IP address and communication port number of the service for receiving the event, and the static event. URL) must be provided. The application server registers static events for the service by informing the gateway of the type of static events and the reference of the web service server that implements the open API for notification.

Static events are registered with application servers and gateways through the provisioning phase of services that provide users with accounts, account access rights, account-related rights, and the necessary resources for account management to deliver events to services. Then, when the corresponding event occurs in the actual communication network, the gateway extracts the reference of the web service server implementing the notification API and calls the event notification operation of the web service server of the reference.

The called web service server extracts the event receiving IP address and communication port number of the service registered in the provisioning step and delivers the event using the extracted IP address.

The service application may request or terminate the start of notification of dynamic events as needed at run time. When the service application asks the gateway to start notifying a particular event, it must pass a reference to the web service server that implements the open API for event notification and the newly created correlation value.

The correlation value is information for associating whether an event requested by the service and an event notified later by the gateway are the same. When the event occurs, the gateway extracts the reference of the web service server implementing the open API for event notification received from the service and calls the event notification operation of the web service server of the reference and passes the correlation value as a parameter.

In order to finally deliver the event to the service, the called web service extracts the event receiving IP address and communication port number of the service registered in the provisioning step and delivers the event using the extracted web address.

Hereinafter, a preferred embodiment of a network event notification device and a method thereof in an application server supporting a web service based open API according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a network event notification device and a network connection configuration in an application server supporting an open API based on a web service according to the present invention.

As shown in FIG. 1, the network configuration of the event processing system according to the present invention may include an application server 100, a gateway 200, a communication network 300, and user terminals 400. Can be.

The application server 100 may include a service application 110, an event notification API processor 120, a service provisioning manager 130, and an event table 140.

The service application 110 created by the service programmer is deployed in the application server 100 and executed.

The event notification API handler 120 provides a processing function for an API that must be implemented at the service application 110 in order to be notified of a communication network event from the gateway 200 among web service based open APIs, and forms a server of a web service. Is implemented.

The service provisioning manager 130 provides a function of storing and managing the data obtained after providing the service provisioning procedure in the event table 140.

The event table 140 stores information necessary for notifying a network event to all services mounted in the application server 100. Here, the structure of the event table 140 shown in FIG. 1 will be described with reference to FIG. 2.

FIG. 2 is a diagram illustrating the structure of an event table shown in FIG. 1.

As shown in FIG. 2, the event table 140 includes a service ID field 141, an IP address field 142 for event reception of a service, a communication port number field 143 for event reception of a service, and the number of activated events. Field 144, event type field 145, Correlator field 146, event notification AIP processor reference field 147, the event type field 145, Correlator field 146, event notification AIP The processor reference field 147 may include a plurality of processors.

The service ID information in the service ID field 141 indicates a service identifier and is used as a primary key in the event table 140.

The event receiving IP address field 142 and the communication port number field 143 of the service indicate an IP address and a communication port number required by the event notification API processor 120 as a communication means for notifying an event to a service.

The activated event number field 144 indicates the total number of events that the service wants to be notified of and is displayed as the sum of the number of static events and dynamic events.

Event type [i] 145 indicates whether the i th event is activated by the current service as a true or false value. Here, each event corresponds to an event type [i] in the range up to [1..n]. If the i th event corresponds to any static event and is a service registered as a static event by the provisioning procedure, the event type [i] has a true value, otherwise it has a false value.

If the i th event corresponds to an arbitrary dynamic event, and the service application requests the gateway 200 to notify the event at runtime, the event type [i] has a true value and the It has a false value. Or if the service application 110 requests to terminate the corresponding event notification at run time, the value of the event type [i] has a false value.

The Correlator [i] field 146 is for recording a correlation value for associating an event requested by the service when the i-th event is notified from the gateway 200. The correlation value recorded in the Correlator [i] field is not assigned to the static event, but only when the service application 110 requests the event notification from the gateway 200 for the dynamic event, the correlation value is generated and passed as a parameter. In this case, before passing the parameter value to the gateway 200, the service application 110 records the generated correlation value in the corresponding correlator [i] field. When the service application 110 requests the gateway 200 to end dynamic event notification, the correlator [i] value is initialized to the default value of zero.

Meanwhile, the event handler API handler reference [i] field 147 is a reference (eg, URL) to a web service server that implements an API for receiving notification of the i-th event from the gateway 200 among web service-based open APIs. ).

Next, the service provisioning procedure provided by the service provisioning manager 130 shown in FIG. 1 will be described step by step.

3 is an operational flowchart of a service provisioning procedure provided by the service provisioning manager 130.

First, the service provisioning manager 130 creates a new record to be added to the event table 140 and initializes (all values of the event type [i] field are false) (1300).

After initialization, the service provisioning manager 130 assigns the service ID and records the assigned value as the value of the service ID field of the record (1310).

In operation 1320, an IP address and a port number for receiving an event of a service are input and recorded in a corresponding field of the record.

Then, the type of the static event is received and the value of the event type [i] field corresponding to the corresponding event is set to true and the value of the correlator [i] field is set to a default value of 0 (1330).

A reference to an event handler for event notification for a static event is input and recorded in the reference [i] field (1340).

Subsequently, it is determined whether information is collected for all static events (1350). If the information is collected for all static events as a result of the determination, the number of static events is recorded in the record as a value of the activated event count field ( 1360).

Subsequently, the service provisioning manager 130 registers a reference to the event notification API processor corresponding to the static event type to the gateway 200 (1370).

Once registration for the static event is complete, gather information about the dynamic event. For all dynamic events of interest to the user, a reference of the event notification API handler is input and recorded in the corresponding reference [i] (1380).

As described above, when the service provisioning procedure is completed by the service provisioning manager 130, a method of requesting the gateway 200 to start notification of a dynamic event provided by the service application 110 will be described.

4 is an operational flowchart illustrating a procedure for requesting a gateway to initiate notification of a dynamic event provided by the service application 110.

First, the service application 110 finds a record corresponding to its service ID in the event table 140 from the service ID field 141 (1400).

The event type value of the event type [i] field 145 corresponding to the event of interest in the record is modified to true (1410).

After the service application 110 generates the correlation value (1420), the service application 110 records the corresponding value of the correlator [i] field in the corresponding field of the event table 140, that is, the Correlator field 146. (1430).

Next, the service application 110 extracts a reference value of the event notification API processor from the reference [i] field 147 of the corresponding event notification API processor (1440).

In operation 1450, the service application 110 increases the value of the activated event count field 144 by one.

In operation 1460, the gateway 200 is called using the extracted reference value of the event notification API processor and the generated correlation value as input parameters.

As described above, when the gateway 200 requests the start of notification of the dynamic event provided by the service application 110, and there is a call from the gateway 200, the event notification API processor 120 to the service application 110. You will be notified of the event.

Hereinafter, the event notification method according to the present invention will be described in detail and step by step.

5 is a flowchart illustrating an operation of an event notification method in the event notification API processor of the event processing system according to the present invention.

As shown in FIG. 5, first, an event handler for event notification for a static event or a dynamic event of the application server 100 is waiting for a call for event notification from the gateway 200 (1500). The gateway 200 determines whether there is a call (1510).

As a result of the determination, when called from the gateway 200, the event notification API processor 120 finds a record corresponding to the service ID associated with itself from the service ID field 141 of the event table 140 (1520).

The value of the event type [i] corresponding to the event transmitted from the gateway 200 from the record is extracted from the event type field 145 (1530).

Subsequently, it is determined whether the extracted event type value is true (1540). If the extracted event type value is not true, the corresponding event is discarded and the call is waited for from the gateway 200. Return to the state (1550).

However, when the event type value stored in the event type field 145 of the event table 140 is true in step 1540, whether the correlator (i) value of the event table 140 is the default value "0" is determined. Determine (1560).

As a result of determination, if the value of correlator [i] of the event table 140 is 0, it is a static event, and thus, the IP address and port extracted from the event table 140 (1590) are extracted from the event table 140 for receiving a service. The event will be notified using the number (1600).

However, if the value of correlator [i] of the event table 140 is not 0 in step 1560, the value of the correlator [i] recorded in the event table 140 is passed by the gateway 200 as a parameter. In operation 1570, it is determined whether or not to coincide with each other.

As a result of determination, when the values of correlator [i] recorded in the event table 140 coincide with the correlation values passed by the gateway 200 as parameters, the receiving IP address and the communication port number are extracted from the event table ( 1590) Forward the event to the service (1600).

Meanwhile, if the correlator [i] values recorded in the event table 140 in step 1570 do not coincide with the correlation values passed by the gateway 200 as parameters, the corresponding events are discarded and returned to the standby state (1580). .

As such, the service application 110 requests the gateway 200 to terminate notification of the dynamic event. This operation will be described in detail with reference to FIG. 6.

6 is a flowchart illustrating an operation of a method for requesting termination of dynamic event notification of a service application in an event processing system according to the present invention.

As shown in FIG. 6, the service application 110 first finds a record for the service ID corresponding to itself from the service ID field 141 in the event table 140 (1610).

The service application 110 modifies the value of the event type [i] field 145 corresponding to the event of interest from the record for the searched service ID to false (1620).

The service application 110 then extracts the value of the corresponding correlator [i] field 146 and initializes the value of correlator [i] to a default value of 0 (1630).

The service application 110 decreases the value of the activated event count field 144 by 1 (1640).

The event notification is terminated by calling the gateway 200 using the extracted correlation value as an input parameter (1650).

Apparatus and method for event notification in an application server supporting a web service-based open API according to the present invention as described above supports notification of both static and dynamic events, and notifies the event because it uses an event table. In order to improve the service application's scalability and maintain the service by having to refer to the table without the need to hard-code routines in the service application.

Claims (21)

An apparatus for notifying a service application of an event delivered through a gateway in an application server supporting a web service-based open API, An event table for storing a plurality of event related detailed information; A service provisioning manager for storing event related detailed information in the event table; A service application requesting the gateway to start notification of a specific event or requesting to end event notification; A communication network event in an application server supporting an open API based on a web service including an event handler for processing an event notification using event related information stored in the event table as an event corresponding to an event received from the gateway. Notification device. The method of claim 1, The event table is In the application server supporting the web service-based open API, including the service ID, the IP address for event reception of the service, the communication port number for event reception of the service, the number of active events, and information fields for each event. Network event notification device. The method of claim 2, Event information stored in the information field for the event, It supports web service based open API which includes event type, correlation value which is information for linking whether event requested by service and event notified by gateway later are the same, and reference information about API handler for event notification. Apparatus for communicating network events in an application server. The method of claim 1, The service provisioning manager, To perform the provisioning procedure, create a new record in the event table, assign a service ID, assign the service ID to the record, assign the IP address and communication port number of the service, and assign the static event Information about the number of active events for the number of static events, the static event type for all registered static events, a reference to the API handler for event notifications for that event, and information about the dynamic events by the number of dynamic events. Apparatus for communicating network events in an application server that supports a web service-based open API, characterized in that stores each in a corresponding field. The method of claim 4, wherein In the service provisioning manager, the recording of information on the static event records the value of the event type [i] field corresponding to the received event as true and correlator [i] corresponding to the received event. It records the value of the field as a default value, receives a reference value of the notification API processor corresponding to the input event, and records the value of the corresponding event notification API processor reference [i] field as the input value. Network event notification device in an application server that supports a web service-based open API. The method of claim 4, wherein In the service provisioning manager, recording of information on a dynamic event receives a reference value of a notification API handler corresponding to the received event, and receives a value of a corresponding event notification API processor reference [i] field. Apparatus for notifying a network event in an application server that supports a web service-based open API, characterized in that the value is recorded. The method of claim 1, wherein the service application, Find the record corresponding to the service ID of the event table in the event table, record the value of the event type [i] field corresponding to the desired event as true, generate a correlation value, and then correspond to the desired event in the record. record the value of the correlator [i] field as the generated correlation value, Extract the value of the reference [i] field for the event notification API handler corresponding to the desired event in the record, increase the value of the activated event count field in the record by 1, and then add the reference to the extracted event notification API handler. Apparatus for notifying a network event in an application server supporting an open API based on a web service, characterized by requesting a start of event notification by calling a gateway with a generated correlation value as an input parameter. The method of claim 1, wherein the service application, Find the record corresponding to the service ID of the event table in the event table, modify the value of the event type [i] field corresponding to the desired event in the record to false, and correlator [i] corresponding to the desired event in the record. After extracting the value of the field, modify the value of the correlator [i] field to the default value, After reducing the value of the activated event count field in the record by 1, calling the gateway with the extracted correlation value as an input parameter, requesting to terminate the event notification, Network event notification device. The method of claim 1, The event notification API processor When there is a call from the gateway, the record corresponding to the service ID of the gateway is found in the event table, the value of the event type [i] field corresponding to the event notified by the gateway is extracted, and the extracted value is true. ), The value of the corrlelator [i] field corresponding to the event notified by the gateway is extracted. If the extracted value is the default value, the IP address and communication port for event reception of the service are extracted from the record, and then the extracted IP is extracted. Apparatus for notifying a network event in an application server supporting an open API based on a web service, characterized in that an event is notified to a service application using an address and a communication port. The method of claim 9, The event notification API processor, If the extracted correlation value is not the default value, the extracted correlation value and the correlation value passed from the gateway to the parameter are compared. If the two values match with each other as a result of the comparison, the record indicates the IP address and communication port for event reception of the service. Apparatus for communication network event in an application server supporting an open API based on a web service, characterized in that the event is notified to the service application using the extracted value. The method of claim 1, The service application, the event notification API processor, and the service provisioning manager supports the Parlay X API standardized by the Parlay / OSA group, the network network event notification device in the application server that supports the open API, Web services. In an application server supporting a web service based open API, a method of notifying an event to a service application through a gateway, Storing event related detailed information in an event table to notify the service application of the event; And Requesting the gateway to start notification of a specific event, processing an event notification using the event related detailed information stored in the event table for an event corresponding to the event received from the gateway, and then sending an event notification to the gateway. A network event notification method in an application server that supports a web service based open API comprising requesting to terminate.  The method of claim 12, The event table is In the application server supporting the web service-based open API, including the service ID, the IP address for event reception of the service, the communication port number for event reception of the service, the number of active events, and information fields for each event. Network event notification method. The method of claim 13, Event information stored in the information field for the event, Support web service based open API, including event type, correlation value which is information for linking whether event requested by service and event notified by gateway later are the same, and reference information about API handler for event notification. Network event notification method in the application server. The method of claim 12, The storing of the event related detailed information may include: Creating and initializing a new record in the event table; Assigning a service ID and recording the assigned service ID in the generated record; Receiving an IP address and a communication port number of a service and recording the same in a record; Receiving information on a static event as many as the number of static events and recording the information in a record; Recording the count for the static event as the value of the activated event count field; Registering a static event type and an event notification reference for the corresponding event with the gateway for all the registered static events; And And receiving information on the dynamic event as many as the number of dynamic events that the service is interested in and recording the information in a record. The method of claim 15, Receiving information about the static event and recording the record, Recording a value of an event type [i] field corresponding to an input event as true; Recording a value of a correlator [i] field corresponding to the received event as a default value; And An application server supporting a web service-based open API comprising receiving a reference value of a notification API processor corresponding to an input event and recording a value of a corresponding event notification reference [i] field as an input value. Network event notification method in. The method of claim 15, Receiving information about the dynamic event and recording in a record, Receiving a reference value of the notification API processor corresponding to the received event and recording the value of the corresponding event notification API processor reference [i] field as an input value; Network event notification method in application server that supports API. The method of claim 12, Request to start notification for a specific event to the gateway, Finding a record corresponding to its service ID in the event table; Recording the value of the event type [i] field corresponding to the desired event in the record as true and generating a correlation value; Recording a value of a correlator [i] field corresponding to a desired event in the record as a generated correlation value; Extracting a value of a reference [i] field of the event notification API processor corresponding to the desired event from the record; Increasing the value of the activated event count field in the record by one; And A communication network event notification method in an application server supporting an open API based on a web service, comprising: calling a gateway as an input parameter with a reference to the extracted event notification API handler and a generated correlation value. The method of claim 12, Request termination of the notification for the specific event to the gateway, Finding a record in the event table corresponding to the service ID thereof; Modifying the value of the event type [i] field corresponding to the desired event in the record to false; Extracting the value of the correlator [i] field corresponding to the desired event from the record, and then modifying the value of the correlator [i] field to a default value; Decreasing the value of the activated event count field in the record by one; And A communication network event notification method in an application server supporting an open API based on a web service, comprising: calling a gateway using the extracted correlation value as an input parameter. The method of claim 12, The event notification processing using the event related detailed information stored in the event table as an event corresponding to the event notified by the gateway, If there is a call from the gateway, finding a record corresponding to its service ID in the event table; Extracting a value of an event type [i] field corresponding to an event notified from the gateway in a record; If the extracted value is true, extracting a value of a corrlelator [i] field corresponding to an event notified by a gateway; And If the extracted correlation value is a default value, extracting an IP address and a communication port of an event reception service of the service from the record and using the extracted value to deliver an event to a service application; Network event notification method in an application server that supports the. The method of claim 20, Comparing the extracted correlation value with a correlation value passed from the gateway to a parameter when the extracted correlation value is not the default value; And If the two values match each other, extracting an IP address and a communication port for receiving an event of a service from a record, and notifying the service application of the event using the extracted value; Network event notification method in application server that supports API.

Images