KR20210078115A - Apparatus and method for forwarding message of private branch exchange system - Google Patents

Abstract

The present disclosure relates to a message transmission device and a method thereof, configured to allow an application device used in a single node configuration to be used without any change in a multi-node configuration by using an application programming interface (API) interface node. The message transmission device according to an embodiment of the present disclosure is configured to: receive a hyper text transfer protocol (HTTP) or a WebSocket message; convert the received HTTP or WebSocket message into a node internal message; determine which node to transmit the node internal message; transmit the node internal message to the determined node; receive a response message from the determined node; and determine whether to transmit a response message. According to the present invention, it is possible to form a flexible system with scalability.

Description

Apparatus and method of message passing in telephone switching system {APPARATUS AND METHOD FOR FORWARDING MESSAGE OF PRIVATE BRANCH EXCHANGE SYSTEM}

The present disclosure relates to a telephone switching system, and more particularly, to a message delivery apparatus and method using an API (Application Programming Interface) interface node to enable application equipment used in a single node configuration to be used without change in a multi-node configuration.

Existing PBX (Private Branch eXchange) system is composed of a single node or multiple nodes in some cases to communicate between the application server and the node using HTTP (Hyper Text Transfer Protocol) and Websocket. do.

In general, it is used in a small single-node configuration, and when there are many resources, it is often expanded to a multi-node environment. There may be a problem that the service cannot be used with the same application equipment.

The present disclosure provides a message delivery apparatus and method that enable application equipment used in a single node configuration to be used without change in a multi-node configuration by using an API (Application Programming Interface) interface node of a telephone switching system.

A message transfer apparatus of a telephone switching system according to an embodiment of the present disclosure includes an HTTP interface unit that performs an interface function of a Hyper Text Transfer Protocol (HTTP) or WebSocket message; an HTTP system interface unit connected to the HTTP interface unit to perform conversion between the HTTP or WebSocket message and the node internal message; and an API interface unit connected to the HTTP system interface unit to determine a node to transmit the node internal message and to determine whether to transmit a response message received from the node to the HTTP system interface unit.

As an embodiment, the HTTP interface unit may be connected to an application server, and the API interface unit may be connected to at least one node.

In an embodiment, the API interface unit may include: a node determining unit configured to store information on whether at least one node operates normally and a cluster configuration of the at least one node; and an event collection unit for storing the event received from the at least one node and transmitting the received event to the application server.

As an embodiment, the HTTP system interface unit may form the node internal message using a lower level TCP (Transmission Control Protocol) than HTTP.

A message delivery method of a telephone switching system according to an embodiment of the present disclosure includes: receiving a Hyper Text Transfer Protocol (HTTP) or WebSocket (WebSocket) message; converting the received HTTP or WebSocket message into a node internal message; determining a node to which to transmit the intra-node message; transmitting the node internal message to the determined node; receiving a response message from the determined node; and determining whether to transmit the response message.

As an embodiment, converting the received HTTP or WebSocket message into a node internal message may include forming the node internal message using a lower level TCP (Transmission Control Protocol) than HTTP. .

As an embodiment, the determining of the node to which the internal node message is to be transmitted may include, in consideration of whether at least one node is operating normally, another node included in the same cluster when the transmission target node is in an abnormal operating state. determining a node to send the message to.

In an embodiment, converting the response message into an HTTP or WebSocket message; and transmitting the converted HTTP or WebSocket message to an application server (Application Server).

According to the present disclosure, since the application server of the telephone switching system can configure system services using the same configuration regardless of whether it is a single node configuration or a multi-node configuration, a flexible system with scalability can be formed.

1 is a block diagram of a PBX system composed of a single node.
2 and 3 are block diagrams of a PBX system composed of a single node.
4 is an exemplary diagram illustrating a single node configuration of an API (Application Programming Interface) service system according to an embodiment of the present disclosure.
5 is an exemplary diagram illustrating a multi-node configuration of an API service system according to an embodiment of the present disclosure.
6 is an exemplary diagram illustrating a multi-node configuration of an API service system according to an embodiment of the present disclosure.
7 is an exemplary diagram showing the configuration of an API interface according to an embodiment of the present disclosure.

Embodiments of the present disclosure are exemplified for the purpose of explaining the technical spirit of the present disclosure. The scope of the rights according to the present disclosure is not limited to the embodiments presented below or specific descriptions of these embodiments.

All technical and scientific terms used in this disclosure have the meanings commonly understood by one of ordinary skill in the art to which this disclosure belongs, unless otherwise defined. All terms used in the present disclosure are selected for the purpose of more clearly describing the present disclosure and not to limit the scope of the present disclosure.

As used in this disclosure, expressions such as "comprising", "including", "having", etc. are open-ended terms connoting the possibility of including other embodiments, unless otherwise stated in the phrase or sentence in which the expression is included. (open-ended terms).

Expressions in the singular described in this disclosure may include plural meanings unless otherwise stated, and the same applies to expressions in the singular in the claims.

Expressions such as “first” and “second” used in the present disclosure are used to distinguish a plurality of components from each other, and do not limit the order or importance of the components.

The term “unit” used in the present disclosure refers to software or hardware components such as field-programmable gate arrays (FPGAs) and application specific integrated circuits (ASICs). However, "units" are not limited to hardware and software. A “unit” may be configured to reside on an addressable storage medium, or it may be configured to refresh one or more processors. Thus, by way of example, “part” includes components such as software components, object-oriented software components, class components, and task components, including processors, functions, attributes, procedures, subroutines, and so forth. It includes segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Functions provided within components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts”.

As used in this disclosure, the expression "based on" is used to describe one or more factors affecting the act or action of a decision, judgment, or action described in a phrase or sentence in which the expression is included, the expression being It does not exclude additional factors influencing the actions or actions of decisions, judgments or actions.

In the present disclosure, when a component is referred to as being “connected” or “connected” to another component, the component can be directly connected or connectable to the other component, or a new component It should be understood that other components may be connected or may be connected via other components.

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding components are assigned the same reference numerals. In addition, in the description of the embodiments below, overlapping description of the same or corresponding components may be omitted. However, even if description regarding components is omitted, it is not intended that such components are not included in any embodiment.

1 is a block diagram of a PBX system composed of a single node.

When configuring a single node in the existing Private Branch eXchange (PBX) system, as shown in FIG. 1 , the application server 10 is connected to one node 20 , and the application server 10 and The system connected to the node 20 communicates with HTTP (Hyper Text Transfer Protocol) and WebSocket. HTTP is used when the application server 10 requests an operation or information request from a system connected to the node 20, and a response is transmitted for each request. The system performs a predetermined operation with an HTTP request, and a path that can notify the application of an event that occurred in the system in the middle of this operation is connected through the websocket.

2 is a block diagram of a PBX system composed of multiple nodes.

As shown in FIG. 2 , when the capacity is expanded to a multi-node configuration (2 nodes), the configuration between the application server 10 and the nodes 20, 30, 40, and 50 must be changed. Since the resources possessed by each node are different, the application equipment may have to be structurally changed when expanding while maintaining the existing structure of the system node. In the case of making an HTTP request, the application server 10 must know in advance which node the resource exists, and configure node information so that the node can connect to the node where the resource exists. When receiving an event, it is necessary to connect to all nodes 20, 30, 40, and 50 to receive the generated event. 2 illustrates a case in which one application server 10 and a plurality of nodes 20, 30, 40, and 50 are interlocked, but as the number of application servers 10 increases, the connection configuration becomes complicated, and each node The same settings for authentication processing of the application server 10 should be kept the same. Here, since the connection used for event reception is a connection-oriented protocol, once a service is started to all nodes 20, 30, 40, and 50 in the application server 10, the connection must be continuously maintained.

3 is a block diagram of a PBX system composed of multiple nodes.

In order to solve the problem of the PBX system configuration as shown in FIG. 2 , as shown in FIG. 3 , an open source HA proxy/reverse web proxy 60 may be used. In this case, the HTTP connection can be configured simply, but the application server 10 still needs to know which node the desired resource exists and include it in the HTTP request and provide information so that the reverse web proxy in the HA proxy can do routing. In the websocket connection, the connection to all nodes in the application server 10 should be maintained, not different from FIG. 2 .

4 is an exemplary diagram illustrating a single node configuration of an API (Application Programming Interface) service system according to an embodiment of the present disclosure.

As shown in FIG. 4 , the API service system 100 includes an application server 110 , a Hyper Text Transfer Protocol (HTTP) interface unit 120 , an HTTP system interface unit 130 , a system application 140 , and a message. A switch 150 may be included. According to an embodiment, the external path of the message inside the node 160 is not used in a single node configuration, but may be used in a multi-node configuration.

The HTTP interface unit 120 may perform an interface function of HTTP and WebSocket messages. According to an embodiment, the HTTP interface unit 120 transmits only a normal HTTP request to the HTTP system interface unit 130 , and an abnormal HTTP request is not transmitted to the HTTP system interface unit 130 . can

The HTTP system interface unit 130 may be connected to the HTTP interface unit 120 to perform conversion between an HTTP or WebSocket message and a node internal message. That is, the HTTP system interface unit 130 may convert an HTTP request into a system (node, 160) internal message so that the system can process the HTTP request, and convert the node 160 internal message into an HTTP message. According to an embodiment, when converting an HTTP request to an internal message of the node 160 , the processing load of the node 160 is not used by using HTTP, but by using a lower level TCP (Transmission Control Protocol) than HTTP. (load) can be reduced.

The system application 140 may process internal messages of the node 160 to provide an actual service.

The message switch 150 may serve to change the transmission direction to transmit the internal messages of the node 160 to the inside or the outside of the node 160 .

As shown in FIG. 4, in the case of a single node configuration, the service flow is as follows. In order for the external application server 110 to request a service from the node 160 , authentication related information may be set in advance in the node 160 , and an attempt may be made to access the node 160 using HTTP. The node 160 checks the authentication information of the application server 110 attempting to access, and when the authentication information is confirmed, transmits an authentication-related token to the application server 110, and if the authentication information is not confirmed, the application server Access may not be allowed for the access attempt of 110 . When the authentication is normally completed, the application server 110 may attempt a WebSocket connection to the node 160 using the token information received from the node 160 after the authentication is completed.

If the authentication process is successful, the application server 110 is ready to perform an actual function and can use a system function such as making a call using the HTTP API. Various events occurring in the middle of this service may be transmitted from the node 160 to the application server 110 through the websocket.

5 is an exemplary diagram illustrating a multi-node configuration of an API service system according to an embodiment of the present disclosure.

As shown in FIG. 5 , the API service system 200 includes a first application server 210 , an API interface node 220 , a second application server 230 , a first node 240 , a second node ( 250 ) and a third node 260 . The API interface node 220 includes an HTTP interface unit 221 , an HTTP system interface unit 222 , and an API interface unit 223 , and the first node 240 includes an HTTP interface unit 241 , an HTTP system. It may include an interface unit 242 , a system application 243 , and a message switch 244 .

Compared to the single node configuration shown in FIG. 4 , an API interface node 220 that connects all external HTTP/Websockets may be added. The API interface node 220 is connected to the first application server 210 outside, and a plurality of nodes including the first node 240 , the second node 250 , and the third node 260 inside. can be connected

Between the first application server 210 and the API interface node 220, the HTTP/WebSocket protocol is used, and the API interface node 220 and the first node 240, the second node 250, and the third node ( 260), TCP including functions corresponding to HTTP/WebSocket can be used.

According to an embodiment, the first node 240 , the second node 250 , and the third node 260 may include the same configuration as the node 160 illustrated in FIG. 4 .

In the API interface node 220 , the HTTP interface unit 221 and the HTTP system interface unit 222 may perform the same functions as the HTTP interface unit 120 and the HTTP system interface unit 130 illustrated in FIG. 4 . .

The HTTP system interface unit 222 converts the HTTP message into a node internal message. The API interface unit 223 receives an internal HTTP request, analyzes the node internal message, and transmits the node internal message to a certain node. and receive the response and decide whether to forward it or not. The internal configuration of the HTTP system interface unit 222 will be described later.

6 is an exemplary diagram illustrating a multi-node configuration of an API service system according to an embodiment of the present disclosure.

6, in order to provide a high availability service, a predetermined number (eg, two) of nodes is bundled to form a cluster, and the nodes 240 and 250 belonging to the cluster are Even if the service is not performed, the information of other nodes can be stored in the same way. For example, the first node 240 and the second node 250 may be configured to store the same information and perform respective services. If a state in which normal processing is impossible occurs while the first node 240 is performing a service, it may be configured such that the second node 250 performs the service performed by the first node 240 .

7 is an exemplary diagram illustrating the configuration of an API interface unit according to an embodiment of the present disclosure.

As shown in FIG. 7 , the API interface unit 223 may include a node determination unit 223 - 1 and an event collection unit 223 - 2 .

The API interface node 220 continuously observes and records whether the nodes are operating normally. When the node determining unit 223-1 determines the service node, the HTTP request must be transmitted from the table in which the nodes are normally operating or not. If a node is in an abnormal state, it can decide to forward a message to another node in the same cluster. That is, when the API interface unit 223 determines the service node, when the first node 240 is determined to be in an abnormal operating state, the API interface unit 223 may transmit an HTTP request (message) to the second node 250 existing in the same cluster. have. In addition, when this message is delivered, authentication information is checked so that only the authenticated message is delivered to the second node 250 for processing, and the second node 250 can be configured so that additional authentication is not required.

The event collection unit 223 - 2 may store events received from all nodes and deliver the received events to the first application server 210 . The event is a message transmitted from the nodes 240 and 250 to the first application server 210, and if the event collection unit 223-2 is not present, the first application server 210 maintains a WebSocket connection to all nodes. Should be.

In a multi-node configuration, the operation of each node is functionally the same as in a single-node configuration. However, a message switch may be additionally installed. When a message switch is connected to an application server connected to a node, the node is independent of the connection to the API interface node and can operate in a single node configuration. On the other hand, when the message switch is connected to the API interface node, all requests and events can be transmitted/received from the API interface node. According to an embodiment, a message used for all request and event transmission/reception may include, but is not limited to, a TCP message.

A message flow to be achieved through the present disclosure in a multi-node configuration is as follows. After the multi-node configuration, when the first application server 210 transmits an HTTP request to the API interface node 220, the HTTP interface unit 221 included in the API interface node 220 only sends a normal HTTP request to the HTTP system interface unit ( 222) can be forwarded. The HTTP system interface unit 222 converts the HTTP/WebSocket request into a system internal TCP message and transmits it to the API interface unit 223 . The HTTP system interface unit 222 may also perform a function of converting a system message into an HTTP WebSocket message. On the other hand, the API interface unit 223 analyzes the received HTTP request to determine which node the message is to be transmitted including the high availability function, and the node (eg, 240) to which the request message is transmitted. It can be delivered through an external TCP message interface. At this time, the system should set the message switch 244 to use an external TCP message. The system can analyze the received message and send a response to the TCP port that received the request. This response message is transmitted to the API interface node 220, and when the node determining unit 223-1 of the API interface unit 223 transmits a response, the response message is transmitted externally through the HTTP system interface unit 222 and the HTTP interface unit 221. The request/response in a multi-node configuration may be completed by being transferred to the first application server 210 of The event path requests a connection from the first application server 210 to the API interface node 220, and when it is normally connected, it is connected to the API interface node 220 through one websocket connection, and the API interface unit 223. The event collection unit 223 - 2 included in may collect all event messages and deliver them to the first application server 210 .

Due to the above configuration, the first application server 210 can perform the same operation regardless of whether the configuration is a single node or a multi-node configuration. That is, the first application server 210 may include a flexible system structure with scalability because it can provide system services using the same connection regardless of whether it is a single node configuration or a multi-node configuration.

Although the method has been described through specific embodiments, the method can also be implemented as computer-readable code on a computer-readable recording medium. The computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device. In addition, the computer-readable recording medium is distributed in a computer system connected through a network, so that the computer-readable code can be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing the above embodiments can be easily inferred by programmers in the art to which the present disclosure pertains.

Although the technical spirit of the present disclosure has been described by the examples shown in some embodiments and the accompanying drawings, it does not depart from the technical spirit and scope of the present disclosure that can be understood by those of ordinary skill in the art to which the present disclosure belongs. It should be understood that various substitutions, modifications, and alterations within the scope may be made. Further, such substitutions, modifications and variations are intended to fall within the scope of the appended claims.

10: application server 20,30,40,50: node
100,200: API service system 110: application server
120,221: HTTP interface unit 130,222: HTTP system interface unit
140: system application 150: message switch
160: node 210: first application server
220: API interface node 230: second application server
240: first node 250: second node
260: third node 223: API interface unit
223-1: node determination unit 223-2: event collection unit

Claims (8)

A message passing device in a telephone switching system, comprising:
HTTP interface unit performing an interface function of HTTP (Hyper Text Transfer Protocol) or WebSocket (WebSocket) message;
an HTTP system interface unit connected to the HTTP interface unit to perform conversion between the HTTP or WebSocket message and the node internal message; and
An API interface unit connected to the HTTP system interface unit to determine whether a node to transmit the node internal message is transmitted, and whether to transmit a response message received from the node to the HTTP system interface unit,
A message passing device in a telephone switching system. According to claim 1,
The HTTP interface unit is connected to an application server (Application Server),
The API interface unit is connected to at least one node,
A message passing device in a telephone switching system. According to claim 1,
The API interface unit,
a node determining unit configured to store information on whether at least one node is operating normally and a cluster configuration of the at least one node; and
Storing the event received from the at least one node, and comprising an event collection unit for transmitting the received event to the application server,
A message passing device in a telephone switching system. According to claim 1,
The HTTP system interface unit,
Forming the message inside the node using a lower level TCP (Transmission Control Protocol) than HTTP,
A message passing device in a telephone switching system. A method for delivering a message in a telephone switching system, comprising:
Receiving a Hyper Text Transfer Protocol (HTTP) or WebSocket (WebSocket) message;
converting the received HTTP or WebSocket message into a node internal message;
determining a node to which to transmit the intra-node message;
transmitting the node internal message to the determined node;
receiving a response message from the determined node; and
Comprising the step of determining whether to transmit the response message,
a method of passing messages in a telephone exchange system; 6. The method of claim 5,
The step of converting the received HTTP or WebSocket message into a node internal message comprises:
Using a lower level TCP (Transmission Control Protocol) than HTTP, comprising the step of forming the message inside the node,
A method of message delivery in a telephone exchange system. 6. The method of claim 5,
The step of determining the node to which the node internal message is to be transmitted comprises:
In consideration of whether at least one node operates normally, determining another node included in the same cluster as a node to transmit the internal message to when the transmission target node is in an abnormal operating state,
A method of message delivery in a telephone exchange system. 6. The method of claim 5,
converting the response message into an HTTP or WebSocket message; and
Further comprising the step of transmitting the converted HTTP or WebSocket message to an application server (Application Server),
A method of message delivery in a telephone exchange system.

Images