KR101368693B1 - Method and apparatus for processing traffic in internet protocol multimedia subsystem network - Google Patents

Abstract

Traffic processing method in the IMS network according to the present invention is a TWIF (Trouble Watch and Interception Function) transmits a SIP request message including a status check message to a plurality of SIP servers, the first SIP of a plurality of SIP servers within a predetermined time Determining that the first SIP server is in a failure state when no SIP response message is received from the server; And transmitting the SIP response message including the error code to the proxy server when receiving the SIP request message corresponding to the first SIP server from the proxy server.

Description

METHOD AND APPARATUS FOR PROCESSING TRAFFIC IN INTERNET PROTOCOL MULTIMEDIA SUBSYSTEM NETWORK}

The present invention relates to an Internet Protocol Multimedia Subsystem (IMS) network technology, and more particularly, to a traffic processing method and apparatus in an IMS network.

IMS (IP Multimedia Subsystems) is a network technology that integrates wired and wireless environments and is an infrastructure for providing multimedia services such as voice, audio, video, and data based on the 3rd generation mobile communication network IP (Internet Protocol). Because IMS is based on Internet protocol, it uses a packet switched based unfixed call path to increase transmission efficiency and ensure stability. These IMSs can support not only simple one-to-one calls, but also connections involving multiple users.

Meanwhile, Session Initiation Protocol (SIP) is a signaling protocol that specifies a procedure for creating, deleting, or changing a session between clients on a network including the Internet. SIP is completely independent of IP network transport layer protocols and media and defines how clients create, change or terminate connections regardless of content.

SIP performs signaling for creating or controlling a session for transmitting voice or image data between SIP clients on a network through a text-based message. SIP messages are generally sent via a SIP server. The SIP server is located between various networks to deliver SIP messages to and from SIP clients located in the networks.

In this case, when one SIP server is unable to process a message due to a failure in the IMS network, traffic transmitted to the failed server is accumulated until a predetermined time is exceeded because there is no response by the failed SIP server. All SIP servers between the terminal and the fault server must maintain the transaction information of the corresponding traffic, and after the fault server is recovered, it must handle the traffic retransmitted by the failed transaction. Causes an overload of the SIP server.

RFC 3261: Session Initiation Protocol (SIP) 3rd Generation Partnership Project (3GPP) TS 24.229 IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3

Accordingly, an object of the present invention is to provide a traffic processing method and apparatus in an IMS network that can prevent a delay of traffic flowing into a SIP server from an IMS network.

Traffic processing method in the IMS network according to an embodiment for solving the above-described problem, TWIF (Trouble Watch and Interception Function) transmits a SIP request message including a status check message to a plurality of SIP servers, and within a predetermined time Determining that the first SIP server is in a failure state when a SIP response message is not received from a first SIP server among a plurality of SIP servers; And transmitting the SIP response message including the error code to the proxy server when receiving the SIP request message corresponding to the first SIP server from the proxy server.

After determining that the first SIP server is in a failure state, the TWIF changes an Internet Protocol (IP) address corresponding to the first SIP server to an IP address corresponding to the TWIF to a domain name server (DNS). The method further includes the step of transmitting.

After changing the IP address corresponding to the first SIP server and transmitting the IP address to the DNS, the DNS updates the IP address of the first SIP server with an IP address corresponding to the TWIF, and the first SIP server. Sending the updated IP address to the proxy server in response to a query sent from the proxy server to retrieve an IP address corresponding to.

When the proxy server receives the SIP response message including the error code, the proxy server queries the DNS to search for an IP address corresponding to the second SIP server based on a result of determining the SIP request message transmitted from the user agent client. Or a SIP response message including a response failure message to the client.

The TWIF transmits a SIP request message including the status check message to the plurality of SIP servers at predetermined time intervals, and transmits a SIP request message including the status check message to each of the plurality of SIP servers, or The SIP request message including the status check message is transmitted only to specific SIP servers among the plurality of SIP servers.

Traffic processing method in the IMS network according to an embodiment for solving the above-described problem, TWIF (Trouble Watch and Interception Function) transmits a SIP request message including a status check message to a plurality of SIP server, the plurality of SIP Determining that the first SIP server is in a restored state based on a SIP response message received from a first SIP server among servers; And a Domain Name Server (DNS) is a query transmitted from a proxy server to update an Internet Protocol (IP) address of the first SIP server and retrieve an IP address corresponding to the first SIP server. Sending the updated IP address to the proxy server in response to.

After determining that the first SIP server is in a restored state, the TWIF further includes changing an IP address corresponding to the first SIP server to an IP address before updating to the DNS.

The TWIF stores a failure history corresponding to the plurality of SIP servers, and determines that the first SIP server is in a restored state based on the failure history when the SIP response message is received from the first SIP server.

The failure history includes a SIP server determined to be in a failure state among the plurality of SIP servers and an IP address corresponding to each of the SIP servers.

An IMS network system according to an embodiment for solving the above problems includes a plurality of Session Initiation Protocol (SIP) servers; A Domain Name Server (DNS) that stores an Internet Protocol (IP) address corresponding to each of the plurality of SIP servers; And a TWIF (Trouble Watch and Interception Function) for monitoring the failure of the plurality of SIP servers at predetermined time intervals, changing the IP address corresponding to each of the plurality of SIP servers, and transmitting the changed IP address to the DNS.

According to the traffic processing method and apparatus in the IMS network according to the present invention, even if a failure occurs in the SIP server in the IMS network, it is possible to prevent the delay of traffic flowing into the server.

1 is a block diagram illustrating an IMS network according to an embodiment of the present invention.
2 is a flowchart illustrating a general traffic processing method when a SIP server fails.
3 is a flowchart illustrating a traffic processing method in case of failure of a SIP server according to an embodiment of the present invention.
4 is a flowchart illustrating a traffic processing method for failback of a SIP server according to an embodiment of the present invention.

Specific structural and functional descriptions of the embodiments of the present invention disclosed herein are for illustrative purposes only and are not to be construed as limitations of the scope of the present invention. And should not be construed as limited to the embodiments set forth herein or in the application.

The embodiments according to the present invention are susceptible to various changes and may take various forms, so that specific embodiments are illustrated in the drawings and described in detail in this specification or application. It is to be understood, however, that it is not intended to limit the embodiments according to the concepts of the present invention to the particular forms of disclosure, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first and / or second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are intended to distinguish one element from another, for example, without departing from the scope of the invention in accordance with the concepts of the present invention, the first element may be termed the second element, The second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between. Other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, the terms "comprises ", or" having ", or the like, specify that there is a stated feature, number, step, operation, , Steps, operations, components, parts, or combinations thereof, as a matter of principle.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined herein. Do not.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the preferred embodiments of the present invention with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

1 is a block diagram illustrating an IMS network according to an embodiment of the present invention. Referring to FIG. 1, an Internet Protocol Multimedia Subsystem (IMS) network 1000 to which the present invention is applied may include a user agent client (hereinafter referred to as a UAC 100), a proxy server 200, and a plurality of user agents. The server includes a user agent server (hereinafter referred to as UAS 300), a DNS (Domain Name Server 400), and a TWIF (Trouble Watch and Interception Function 500).

The UAC 100 performs a function of setting up, modifying, and releasing a call.

The UAC 100 may be connected to the UAS 300 through the proxy server 200. At this time, both terminals communicate using Session Initiation Protocol (SIP). SIP is a protocol developed for establishing a session between voice over Internet Protocol (VoIP) terminals capable of voice communication, such as Internet telephones, personal digital assistants (PDAs), mobile phones, and the like.

When the proxy server 200 receives the request message from the sender, the proxy server 200 directly transmits the request message to the called party. If the proxy server 200 receives the response message in response to the request message, the proxy server 200 transmits the response message to the sender. That is, the proxy server 200 is located between the UAC 100 and the UAS 300 to serve as a gateway.

UAS 300 includes a plurality of UAS 301 to 3xx. The plurality of UASs 301 to 3xx may include servers performing the same function and servers performing different functions.

The UAS 300 may include a Call Session Control Function (CSCF), a Media Gateway Control Function (MGCF), an Application Server (AS), etc., but is not limited thereto. The UAS 300 may be linked by a SIP within the IMS network 1000. All components can be included.

The DNS 400 may store and update an Internet Protocol (IP) address corresponding to a domain of each of the plurality of SIP servers, and transmit an IP address corresponding to the SIP server in response to a request of the proxy server 200.

At this time, the SIP server performs a process for the request of the SIP client that sent the message by itself, and generates a request message of its own to transmit to the SIP client which is the destination of the message. In the present invention, the proxy server 200 and the plurality of UAS 300 may be included in the SIP server.

The TWIF 500 monitors the failure of the plurality of SIP servers at predetermined time intervals. The TWIF 500 may monitor the failure of each of the plurality of SIP servers, or may monitor the failure of only the major SIP servers of the plurality of SIP servers.

The TWIF 500 may store and manage a SIP server determined to be in a failure state among the plurality of SIP servers and an IP address corresponding thereto as a failure history.

In addition, the TWIF 500 may change the IP address corresponding to each of the plurality of SIP servers and transmit the changed IP address to the DNS 400. A detailed process thereof will be described later with reference to FIGS. 3 to 4.

2 is a flowchart illustrating a general traffic processing method when a SIP server fails. Referring to FIG. 2, the UAC 100 transmits a SIP request message for call setup to the proxy server 200 (S201).

The proxy server 200 transmits a query for searching for an IP address corresponding to the first UAS 301 to the DNS 400 based on a result of determining the SIP request message (S202) and the DNS 400. In response to the query transmitted from the proxy server 200, the IP address corresponding to the first UAS 301 is transmitted to the proxy server 200 (S203). The proxy server 200 transmits a SIP request message to the first UAS 301 based on the IP address corresponding to the first UAS 301 (S204).

In this case, the proxy server 200 determines that a failure occurs in the first UAS 301 when the SIP response message is not received even after exceeding a predetermined time after transmitting the SIP request message to the first UAS 301. In order to process the call by another UAS, a query for searching for an IP address corresponding to the second UAS 302 is transmitted to the DNS 400 (S205).

The DNS 400 transmits an IP address corresponding to the second UAS 302 to the proxy server 200 in response to the query transmitted from the proxy server 200 (S206).

The proxy server 200 transmits a SIP request message to the second UAS 302 based on the IP address corresponding to the second UAS 302 (S207), and the second UAS 302 from the proxy server 200. The SIP response message is transmitted to the proxy server 200 in response to the transmitted request (S208). The proxy server 200 transmits a SIP response message to the UAC 100 (S209).

However, according to the traffic processing method illustrated in FIG. 2, when a failure occurs in the first UAS 301 in step S204, the SIP request message transmitted from the proxy server 200 is fixed because the first UAS 301 does not respond. There is a delay until timeout and subsequent SIP request messages accumulate. In addition, due to the failure of the first UAS 301, it is necessary to retransmit the SIP request message.

3 is a flowchart illustrating a traffic processing method in case of failure of a SIP server according to an embodiment of the present invention. In the embodiment of the present invention, a case where a failure occurs in the first UAS 301 will be described as an example, but is not limited thereto. A failure occurs in a plurality of SIP servers including the proxy server 200 or the plurality of UAS 300. It can also be applied if it occurs.

1 and 3, the TWIF 500 transmits a SIP request message including a status check message to the second UAS 302 (S301), and the second UAS 302 sends a SIP request message. In response to the TWIF 500 transmits a SIP response message (S302).

The TWIF 500 determines that there is no failure in the second UAS 302, and transmits a SIP request message including a status check message to the first UAS 301 (S303).

If the TWIF 500 does not receive a SIP response message from the first UAS 301 within a preset time, the TWIF 500 determines that a failure has occurred in the first UAS 301, and TWIF determines an IP address corresponding to the first UAS 301. Change to the IP address corresponding to (500) and transmits to the DNS (400) (S304).

In this case, the DNS 400 may update and store the IP address corresponding to the first UAS 301 with the IP address corresponding to the TWIF 500. In addition, the TWIF 500 may store an IP address corresponding to the first UAS 301 and the first UAS 301 that are determined to have a failure.

Next, the UAC 100 transmits a SIP request message for call setup to the proxy server 200 (S305).

The proxy server 200 transmits a query for searching for an IP address corresponding to the first UAS 301 to the DNS 400 based on a result of determining the SIP request message (S306), and the DNS 400 sends a proxy server. In response to the query transmitted from 200, the IP address corresponding to the first UAS 301 is transmitted to the proxy server 200 (S307). In this case, the DNS 400 transmits the IP address corresponding to the TWIF 500 updated in step S304 to the proxy server 200 as the IP address corresponding to the first UAS 301.

The proxy server 200 transmits a SIP request message to the TWIF 500 based on the transmitted IP address (S308). When receiving the SIP request message corresponding to the first UAS 301 from the proxy server 200, the TWIF 500 transmits a SIP response message including an error code to the proxy server 200 (S309). .

In this case, the TWIF 500 may set different error codes according to a plurality of SIP servers in the SIP response message. For example, the TWIF 500 may set an error code of "408" indicating a time out state of a SIP server or an error code of "5xx" indicating an error state of a SIP server.

When the proxy server 200 receives the SIP response message including the error code, the second UAS to process the call by another UAS based on a result of determining the SIP request message transmitted from the UAC 100. A query for searching for an IP address corresponding to 302 is transmitted to the DNS 400 (S310). However, when the proxy server 200 receives a SIP response message including an error code (Error) from the TWIF 500, the proxy server 200 may transmit a SIP response message including the response failure message to the UAC 100.

The DNS 400 transmits an IP address corresponding to the second UAS 302 to the proxy server 200 in response to the query transmitted from the proxy server 200 (S311). According to an embodiment of the present disclosure, the first UAS 301 and the second UAS 302 may be SIP servers having the same function.

The proxy server 200 transmits a SIP request message to the second UAS 302 based on the IP address corresponding to the second UAS 302 (S312), and the second UAS 302 from the proxy server 200. The SIP response message is transmitted to the proxy server 200 in response to the transmitted request (S313). The proxy server 200 transmits a SIP response message to the UAC 100 (S314).

That is, the TWIF 500 can process a transaction without delay between the client and the server in the IMS network 1000 by transmitting an appropriate response message for the incoming traffic.

4 is a flowchart illustrating a traffic processing method for failback of a SIP server according to an embodiment of the present invention. 1 and 3 to 4, the TWIF 500 transmits a SIP request message including a status check message to the second UAS 302 (S401), and the second UAS 302 The SIP response message is transmitted to the TWIF 500 in response to the SIP request message (S402).

Next, the TWIF 500 transmits a SIP request message including a status check message to the first UAS 301 (S403). The first UAS 301 having recovered from the failure transmits the SIP response message to the TWIF 500 in response to the SIP request message (S404).

When the TWIF 500 receives the SIP response message transmitted from the first UAS 301, the TWIF 500 determines that the first UAS 301 is in a restored state based on the stored failure history and corresponds to the first UAS 301. The IP address is changed to an IP address before being updated and transmitted to the DNS 400 (S405). Then, the DNS 400 receives and stores the changed IP address of the first UAS 301.

Next, the UAC 100 transmits a SIP request message for call setup to the proxy server 200 (S406).

The proxy server 200 transmits a query for searching for an IP address corresponding to the first UAS 301 to the DNS 400 based on the result of determining the SIP request message (S407), and the DNS 400 sends a proxy server. In response to the query transmitted from the 200, the IP address corresponding to the first UAS 301 is transmitted to the proxy server 200 (S408).

The proxy server 200 transmits a SIP request message to the first UAS 301 based on the IP address corresponding to the first UAS 301 (S409), and the first UAS 301 from the proxy server 200. The SIP response message is transmitted to the proxy server 200 in response to the transmitted request (S410). The proxy server 200 transmits a SIP response message to the UAC 100 (S411).

Although the present invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

100: user agent client
200: proxy server
300: user agent server
400: Domain Name Server
500: Trouble Watch and Interception Function

Claims (13)

In the traffic processing method when a Session Initiation Protocol (SIP) server fails in an Internet protocol Multimedia Subsystem (IMS) network,
The TWIF (Trouble Watch and Interception Function) transmits a SIP request message including a status check message to a plurality of SIP servers, and if a SIP response message is not received from a first SIP server among the plurality of SIP servers within a predetermined time. Determining that the first SIP server is in a failure state;
When the TWIF receives a SIP request message corresponding to the first SIP server from a proxy server, transmitting a SIP response message including an error code to the proxy server; And
When the proxy server receives the SIP response message including the error code, the proxy server transmits a query to a domain name server (DNS) or fails to respond to search for an IP address corresponding to the second SIP server based on the error code. Sending a SIP response message including the message to the user agent client,
The TWIF is a traffic processing method in the IMS network for setting a different error code according to each of the plurality of SIP server. The method of claim 1, wherein after determining that the first SIP server is in a fault state
The TWIF further comprises the step of changing the Internet Protocol (IP) address corresponding to the first SIP server to the IP address corresponding to the TWIF to transmit to the DNS. The method of claim 2, wherein after changing the IP address corresponding to the first SIP server and transmitting the changed IP address to the DNS,
The DNS updates the IP address of the first SIP server with an IP address corresponding to the TWIF and in response to a query sent from the proxy server to retrieve an IP address corresponding to the first SIP server. And transmitting the updated IP address to the proxy server. delete The method of claim 1,
The TWIF transmits a SIP request message including the status check message to the plurality of SIP servers at predetermined time intervals.
A method for handling traffic in an IMS network that transmits a SIP request message including the status check message to each of the plurality of SIP servers, or transmits a SIP request message including the status check message only to specific SIP servers among the plurality of SIP servers. . In the traffic processing method after the Session Initiation Protocol (SIP) server failure recovery in the Internet protocol Multimedia Subsystem (IMS) network,
A TWIF (Trouble Watch and Interception Function) sends a SIP request message including a status check message to a plurality of SIP servers, and the first SIP is based on a SIP response message received from a first SIP server of the plurality of SIP servers. Determining that the server is in a restored state;
The TWIF converts an Internet Protocol (IP) address corresponding to the first SIP server into an IP address before updating to a domain name server (DNS); And
The DNS updates the IP address of the first SIP server and the updated IP address in response to a query sent from a proxy server to retrieve an IP address corresponding to the first SIP server. Transmitting the traffic to the proxy server. delete The method according to claim 6,
The TWIF stores an error history corresponding to the plurality of SIP servers, and determines that the first SIP server is in a restored state based on the failure history when the SIP response message is received from the first SIP server. How to handle traffic in the network. 9. The method of claim 8,
The failure history is a traffic processing method in an IMS network including a SIP server determined to be in a failure state of the plurality of SIP servers and IP addresses corresponding to each of the SIP servers. Multiple Session Initiation Protocol (SIP) servers;
A Domain Name Server (DNS) for storing an Internet Protocol (IP) address corresponding to each of the plurality of SIP servers and transmitting an IP address corresponding to each of the SIP servers in response to a request of a proxy server; And
It includes a TWIF (Trouble Watch and Interception Function) for monitoring the failure of the plurality of SIP server at a predetermined time interval, changing the IP address corresponding to each of the plurality of SIP server and transmits to the DNS,
The DNS updates a corresponding IP address among the plurality of SIP servers based on an IP address transmitted from the TWIF, transmits the updated IP address,
The TWIF transmits a SIP response message including an error code to the proxy server when a SIP request message corresponding to a SIP server determined to be in a failure state is transmitted from the proxy server. The method of claim 10, wherein the TWIF is
When the plurality of SIP servers are monitored, when it is determined that a first SIP server is in a failure state, the first SIP server and the IP address corresponding to the first SIP server are stored, and the first SIP server is stored. IMS network system for changing the IP address corresponding to the server to the IP address corresponding to the TWIF to transmit to the DNS. The method of claim 11, wherein the TWIF is
As a result of monitoring the plurality of SIP servers, if it is determined that the first SIP server is in a restored state among the plurality of SIP servers, the IP address corresponding to the stored first SIP server is changed to an IP address before changing. IMS network system to send to DNS. The method of claim 10, wherein the TWIF is
IMS network system for monitoring the failure of each of the plurality of SIP server, or only the failure of the specific SIP server of the plurality of SIP server.

Images