KR20030035320A - Integrating operating method for protocol stack application program interface of VOIP - Google Patents

Abstract

PURPOSE: An integrated operation method for a protocol stack API(Application Program Interface) of a VoIP(Voice over Interface Protocol) is provided to register all events corresponding to each operated protocol so that an API is independently operated as to all protocols. CONSTITUTION: All events and callback functions are registered in a stack core(61). It is checked whether a message of a protocol is inputted through an IP(Internet Protocol) network, and it is judged whether the protocol is a registered protocol(62). If the protocol is the registered protocol, the stack core analyzes the inputted message of the protocol(64). It is checked whether the analyzed command or action of the protocol is registered in a stack database(65). If the analyzed command or action of the protocol is registered in the stack database, the stack core notifies acknowledgement to an API(67). It is judged whether the registered content is 'common' or 'specific'(68). If the registered content is 'common', an operation is performed according to each command or action(69). If the registered content is 'specific', an operation is performed according to the characteristic of each protocol(70).

Description

Integrating operating method for protocol stack application program interface of VOIP}

The present invention relates to a method of operating each protocol in a system using VoIP, in particular, H.323, MGCP (Media Gateway Control Protocol), SIP (Session) which is applied for call or data stream control in VoIP. Application Program Interface (API) that provides interworking function between Core part of protocol such as Initiation Protocol) and MEGACO (Media Gateway Control) and Resource provided by each VoIP system The present invention relates to an integrated software (S / W) operating method that operates independently.

More specifically, in the system using VoIP, an application program interface (API) that is responsible for interworking with resources provided by the system by registering all events corresponding to each protocol operated is independent of all the protocols. It relates to a method to be operated.

FIG. 1 is a block diagram showing a method dependent on each protocol applied to VoIP, i.e., each API for each protocol is provided and operated. The control also has a dependency to control resources for each protocol.

In general, the conventional protocol stack API is developed based on an event in the form of a call back function, and defines only the processing for events occurring in each protocol such as H.323, MGCP, SIP, and MEGACO. It develops S / W dependent on circuit and packet network matching capacity, data stream processing property and capability of system of VoIP equipment, and system specification.

In other words, when a new protocol is applied to the same model, a new stack API is developed for interworking between the protocol and resources.

2 is a transition diagram showing the operation state of the prior art and the present invention.

Conventionally, in order to use the callback function provided in the protocol applied to each API, the desired event and callback function are registered in the stack core. (①).

In the protocol stack including the stack core, the registered event and the callback function are built in a database (D / B). (②).

In addition, when a new event occurs, the protocol processing unit requests registration to the stack core (③), and accordingly, the stack core registers to the stack D / B (④).

In the stack D / B, when a registered event occurs, a callback function registered as a corresponding event can be called to perform a desired task in an API.

In other words, when a registered event occurs in the stack D / B, the result or result and function are notified to the stack core, and the stack core notifies the API to the API. (⑤, ⑥).

However, in the system using the conventional VoIP as described above, each API must exist according to each protocol, and only the events provided by each protocol are registered.

Therefore, API must be applied different version according to the applied protocol, so the function must be re-verified.

The present invention proposes a method of registering and operating all event and callback functions in a stack core so that one API can be commonly applied to each protocol in a system using VoIP.

1 is a block diagram showing a method dependent on each protocol applied to VoIP, i.e., each API for each protocol is provided and operated.

Figure 2 is a transition diagram showing the operating state of the prior art and the present invention

3 is a block diagram showing a method of operating independent of each protocol applied to VoIP, that is, provided with only one API for each protocol.

4 is an operation state diagram for configuring the API and Resource to be applied to each protocol in common as shown in FIG.

5 is a first embodiment of building an API that is not dependent on an applied protocol.

6 is a flowchart illustrating a case where a specific protocol operates.

The protocol stack application program interface integration operation method of the VoIP of the present invention,

In a system using VoIP, in order to register all events corresponding to each protocol so that an application program interface (API) which is in charge of interworking with resources provided by the system operates independently of all the protocols, registering a event or / and callback function with the stack core; A second step of determining whether a protocol input through the IP network is a registered protocol; A third step of analyzing a message of a protocol input from a stack core unit in the case of a registered protocol; A fourth step of determining whether the command or action of the analyzed protocol is registered in the stack D / B in the API; And a fifth step of notifying the ACK from the stack core to the API when the stack is registered in the stack D / B.

The present invention also provides a first process of registering all event and / or callback functions on a stack core; A second step of determining whether a protocol input through the IP network is a registered protocol; A third step of analyzing a message of a protocol input from a stack core unit in the case of a registered protocol; A fourth step of determining whether the command or action of the analyzed protocol is registered in the stack D / B in the API; And a fifth step of notifying the ACK from the stack core to the API when the stack is registered in the stack D / B.

Other objects and features of the present invention will become apparent from the detailed description of the embodiments with reference to the accompanying drawings.

Hereinafter, with reference to the accompanying drawings will be described a method of operation common to each protocol in the VoIP system of the present invention.

FIG. 3 is a block diagram illustrating a method of operating a protocol independent of each protocol applied to VoIP, i.e., having only one API for each protocol. As shown in FIG. Since resource control also has independence, it is controlled as one resource without having to have a resource for each protocol.

That is, even if a new protocol is applied to the same model, it is not necessary to develop a new stack API for interworking between a protocol and a resource.

4 is an operation state diagram for configuring API and Resource to be applied to each protocol in common as shown in FIG.

Register all events that occur in protocols such as H.323, MGCP, SIP, and MEGACO used in the present invention. (Step 41).

In addition, a protocol for recognizing a protocol type dictionary is registered (step 42), and the same job execution event is grouped and the similar job performance event is commonized. (Step 43).

Thereafter, in each job or event execution process, the protocol type is checked in the case of the precognitive form of step 42, and the notification about the result and the operation result is performed. (Step 44,45).

Hereinafter, a description will be given of how to build an API independent of each protocol described above (independent).

Basically, all the events and callback functions provided by H.323, MGCP, SIP, and MEGACO protocol stacks can be handled, and the contents of the job to be processed by each event are the same or similar. A method for defining sub-functions and parameters to enable this and processing accordingly will be described with reference to FIGS. 5 and 6.

First, the configuration of the present invention is the same as the module for registering all events occurring in protocols such as H.323, MGCP, SIP, and MEGACO as described in FIG. It consists of a module for grouping job execution events and making similar job performance events common, and a module for checking protocol types in the case of a precognitive form in each job or event execution process.

In addition, the operation configured as described above is similar to FIG. 2, but different from FIG. 2 is that all event and callback functions that can occur in each protocol are registered in the stack core.

That is, all event and callback functions that can occur in H.323, MGCP, SIP, and MEGACO supported by VoIP of the present invention are registered in the stack core (①).

In the protocol stack including the stack core, the registered event and callbackfunction are constructed in a database (D / B). (②).

In addition, when a new event occurs, the protocol processing unit requests registration to the stack core (③), and accordingly, the stack core registers to the stack D / B (④).

In the stack D / B, when a registered event occurs, a callback function registered as a corresponding event can be called to perform a desired task in an API.

In other words, when a registered event occurs in the stack D / B, the result or result and function are notified to the stack core, and the stack core notifies the API to the API. (⑤, ⑥).

5 is a first embodiment of building an API that is not dependent on an application protocol.

Register the currently applied protocol type using MMC (Man Machine Communication). (Step 51).

Thereafter, only events corresponding to protocols operating in the flag checking step according to each event registration process or job execution process according to event occurrence are registered or a job matching the protocol characteristics is performed. (Step 52).

FIG. 6 illustrates a method in which all the events are registered and only the generated events are performed because the events that the protocol can generate are limited when a specific protocol operates.

Register all event and callback functions with StackCore. (Step 61).

It checks which protocol's message is input through the IP network to determine if it is a registered protocol. (Step 62).

As a result of the determination in step 62, if the protocol is not registered, the NAK is notified from the stack core to the protocol processing unit (step 63). In the case of the registered protocol, the message of the protocol currently input in the stack core unit is analyzed. (Step 64).

On the other hand, the API checks whether the analyzed protocol command or action is registered on the stack D / B (step 65), and if not registered, notifies the NAK from the stack core to the protocol processing unit (step 66). ACK is notified to the API from StackCore. (Step 67).

Is the above registered content common? In operation 68, the operation is performed according to each command or action in the case of common, and in operation 69, the operation is performed in accordance with each protocol characteristic. (Step 70).

As described above, the present invention registers all events corresponding to each protocol operated in a system using VoIP, and an application program interface (API) in charge of interworking with resources provided by the system is connected to all protocols. It relates to a method to operate independently.

Although the preferred embodiment of the present invention has been described above, the present invention may use various changes, modifications, and equivalents. It is clear that the present invention can be applied in the same manner by appropriately modifying the above embodiments.

Accordingly, the above description does not limit the scope of the invention as defined by the limitations of the following claims.

Therefore, according to the present invention, since it is not necessary to develop each API depending on each protocol applied to VoIP, it is possible to immediately switch services without having to perform a re-validation process for application of a supportable API according to a protocol change. .

Also, by grouping the same function and commonizing similar functions, network related resources matching with the higher resources of the API, such as circuit and packet networks, and announcement, interactive voice response and conference provided as additional functions in each protocol. A more efficient VoIP service can be provided by establishing a management system for resources to provide services.

Claims (6)

In a system using VoIP, Register all events corresponding to each protocol operated in the system, so that an application program interface (API) in charge of interworking with the resources provided by the system operates independently of all the protocols. Protocol stack application interface integration operation. The method of claim 1, wherein the API is operated independently of all the protocols. Registering all events occurring in at least one protocol of H.323, MGCP, SIP, or MRGACO provided by the VoIP system; Registering a protocol for prior recognition of the protocol; Grouping the same Job Execution event and / or commonizing the similar Job Execution event; Checking a protocol type in the case of a prior recognition form in each job or event execution process; Detecting an ACK for the event; and operating the protocol stack application program interface of the VoIP. The method according to claim 2, wherein in the step of registering an event occurring in a protocol, only an event corresponding to a protocol operating in a flag check step according to each event registration process or a job execution process according to an event occurrence is registered, A protocol stack application program interface operating method of VoIP, which can perform a job. In a system using VoIP, Registering all events or / and callback functions with the stack core; A second step of determining whether a protocol input through the IP network is a registered protocol; A third step of analyzing a message of a protocol input from a stack core unit in the case of a registered protocol; A fourth step of determining whether the command or action of the analyzed protocol is registered in the stack D / B in the API; And a fifth step of notifying the ACK from the stack core to the API when registered in the stack D / B. 5. The integrated protocol stack application interface of VoIP according to claim 4, further comprising a process of determining whether the registered contents are common to be processed or specific to be processed separately. Way. 6. The method according to claim 5, wherein the operation is performed according to a command or an action in the case of common and in accordance with the characteristics of each protocol.