KR20100003869A - A device for routing sip message and routing method - Google Patents

Abstract

PURPOSE: A routing device and a routing method for differently setting a routing path of an SIP message are provided to simplify transmission/reception of the message by optimizing the set path about IMS(IP Multimedia Subsystem) terminal and non-IMS terminal. CONSTITUTION: An interfacing unit(37) performs an IP-based communication with a routing device. A management data table(31) stores and manages data about data mapping according to the conversion of the SIP message. A message converter(33) changes the non-SIP message into the SIP message. The message converter converts the SIP message into the mapped non-SIP message.

Description

A device for routing SIP message and routing method

The present invention relates to an IP Multimedia Subsystem (IMS), and more particularly, to an apparatus for setting a different routing path for a Session Initiation Protocol (SIP) message by distinguishing between an IMS subscriber and a non-IMS subscriber. It is about a method.

As mobile communication technology develops and mobile communication network evolves, the 3rd generation mobile communication system (IMT-2000) essentially provides Internet services, and has a unique Internet Protocol (IP) address assigned by an Internet service provider (ISP). With the IMT-2000 network, it provides mobile IP that can receive internet service. The adoption of IP-based Internet protocols in mobile networks has been accepted as a gradual trend, and Internet protocols are becoming a part of mobile network technologies. The European-led 3GPP (3rd Generation Project Partnership) and North American-led 3GPP2, which proceeds with the standard of IMT-2000, not only stay here, but also adopt the concept of 'ALL IP NETWORK', which replaces all the infrastructures of the mobile network with IP. The ALL IP network is a next-generation mobile communication network that belongs to the category of IMT-2000 network but has a completely different infrastructure.

The biggest feature of ALL IP network is that it is the first 3GPP network to support IP multimedia service. This feature is specifically implemented by newly added nodes to support IP multimedia services, collectively called the Internet Protocol Multimedia Subsystem (IMS).

That is, IMS is a set of nodes newly introduced to provide an IP multimedia service, and includes a call session control function (CSCF), a home subscriber server (HSS) and an application server (AS). And the like.

1 is a block diagram schematically illustrating an IMS service network according to the prior art.

Referring to FIG. 1, the IMS service network stores all data on user equipment (UE) and subscriber data, and performs information management and authority verification for user profile management and mobility management of a UE. HSS (Home Subscriber Server) for performing functions such as a), Call Session Control Function (CSCF) for performing multimedia call control based on Session Initiation Protocol (SCF), and various It includes an application server (AS: Application Server) for providing IMS services.

The HSS and the call session controller (CSCF) form an IMS core network, and the application server and the SCIM (Service Capability Interaction Manager) form an IMS service network.

The call session controller (CSCF) performs an incoming call gateway, call control, serving profile management, and address processing. Specifically, the CSCF has a proxy-call session control function (P-CSCF), an interrogating-call session control function (I-CSCF), and a serving-call session control function (S-CSCF).

The P-CSCF serves as a proxy and a user agent. The P-CSCF is the first point of point at which the UE connects to the IMS core network. The P-CSCF transfers a Session Initiation Protocol (SIP) registration request message received from the UE to the I-CSCF by referring to the home domain of the UE.

The I-CSCF is the first point of access of the UE to the home network, and several I-CSCFs may exist in one network domain. The I-CSCF receives the address of the S-CSCF from which the SIP registration of the UE is performed from the HSS, and then allocates the S-CSCF to be in charge of the actual registration. In addition, I-CSCF routes SIP messages received from other networks to S-CSCF.

The S-CSCF serves as a register and controls a session of a registered endpoint. The S-CSCF is registered in the HSS so as to correspond to the UE, and then downloads and stores subscriber information of the UE. In addition, the S-CSCF performs a control service while managing session state of an actually registered user terminal (UE). The S-CSCF provides user equipment (UE) with information related to service resources. In addition, the S-CSCF performs authentication with the authentication information received from the HSS at the time of registration of the UE.

Meanwhile, the HSS is responsible for all information of a UE subscriber for call / session control. This includes all the functions of the home location register (HLR) in the existing 3G network, and also includes the signaling protocol related to the information about the IMS subscriber. There may be one or several such HSS depending on the number of subscribers and the configuration capability of the network in one same network.

The HSS is a subscriber's master database with basic information related to the subscriber. Such information includes subscriber identifier (ie number and address information), subscriber security information (ie network access control information for authentication and authorization verification), subscriber location information (ie registration and inter-system level mobility information). ) And service profile information of the subscriber.

Based on the above information, the HSS largely provides a home location register / authentication (HLR / AUC) function and an IP multimedia function for an IP multimedia service. In the figure, a UE transmits a service request message to a P-CSCF for a multimedia service. The P-CSCF sends this service request message back to the I-CSCF and selects the corresponding S-CSCF from the I-CSCF. The S-CSCF then provides the information related service to the endpoint.

If there are multiple HSSs in the operator's IMS network, the S-CSCF must access the registered HSS to obtain the subscriber's information. The S-CSCF performs a procedure of acquiring an address of the HSS using a subscriber locator function (SLF) (not shown) to find a registered HSS among a plurality of HSSs.

The application server (AS) may be instant messaging (IM), presence (Presence), Voice Call Continuity (VCC), Push-To-Talk (PTT), Voice over Internet Protocol (VoIP), Group List Management Server (GLMS), A network element that delivers IP multimedia services to subscribers, including IMS Centralized Services (ICS).

The SCIM (Service Capability Interaction Manager) is a multimedia complex service platform that transmits a request transmitted from a CSCF to an AS or performs IMS terminal information inquiry, subscriber inquiry, and access information inquiry using an ISC interface.

The user registers with IMS using the prescribed SIP REGISTER method. This is a mechanism for notifying the IMS of addresses belonging to the IMS and from which SIP user identification can be reached. In 3GPP, when an IMS terminal (or SIP terminal) performs registration, the IMS authenticates the user and assigns the S-CSCF to the user from the set of available S-CSCFs. While the criteria for allocating S-CSCF are not defined by 3GPP, they may include load sharing and service requirements. It should be noted that the assignment of S-CSCF is a key factor in controlling user access to IMS-based services.

During the registration process, the I-CSCF is responsible for selecting an S-CSCF if it has not already been selected. The I-CSCF receives the required S-CSCF capability from the home subscriber server (HSS) of the home network and selects an appropriate S-CSCF based on the received capability. When a registered user continues to send a session request to the IMS, the P-CSCF may forward the request to the selected S-CSCF based on the information received from the S-CSCF during the registration procedure. In an IMS service network, application servers (ASs) are provided to implement IMS service functionality. The application server provides the service to the end user in the IMS system and can be connected as an end point via the 3GPP-compliant Mr interface or "linked" by the S-CSCF via the 3GPP-compliant ISC interface. In the latter case, the Initiation Filter Criterion (IFC) is used by the S-CSCF to determine which application server should be "linked" during SIP session establishment. The IFC is received by the S-CSCF from the HSS during the IMS registration procedure as part of the user profile.

Figure 1 shows the IMS Service Control (ISC) interface between the AS and S-CSCF as well as other interfaces within the IMS. Although the AS of FIG. 1 is shown as having only one interface to the S-CSCF, in practice the ISC interface extends over a communication network to which many (or all) CSCF servers of a given operator network are connected, so that the AS can do all of these. You will recognize that you will be communicating with the CSCF.

Although not shown in the figure, an additional interface Ut exists between the AS and the user terminal UE. The Ut interface allows a user to manage information related to services such as, for example, the creation and assignment of public service identities, such as authentication policy management, negotiation policy management, etc. used by " current " services.

In order to use the SIP-based IMS service through the IMS network of FIG. 1, the UE needs to be a mobile communication terminal (ie, an IMS terminal) supporting a SIP stack capable of processing SIP messages. However, most mobile communication terminals currently used do not support such a SIP stack. Accordingly, various efforts have been made to provide a SIP-based IMS service for a non-IMS terminal (or non-IMS terminal) having no SIP stack in the terminal.

As part of such efforts, Korean Patent Publication No. 0592882 (hereinafter referred to as Patent Document 1) and Korean Patent Application Publication No. 2007-67471 (hereinafter referred to as Patent Document 2) can be given.

Patent Document 1 converts a message (for example, a CSP (Client Server Protocol) message) received from a non-IMS terminal between a user terminal (UE) and a CSCF to a corresponding SIP message that is mapped and transmitted to the AS through CSCF. And a proxy server converting a SIP message received from an AS via the CSCF into a message (for example, a CSP message) that can be recognized by the non-IMS terminal and transmitting the same to a non-IMS terminal. .

However, since the proxy server of Patent Document 1 is installed between the user terminal and the CSCF, the message from the IMS terminal must be processed as well as the message from the non-IMS terminal.

Therefore, a more simplified method of providing IMS services for non-IMS terminals is required.

That is, the present inventors transfer the SIP message from the IMS terminal to the application server through the CSCF without passing through the proxy server of Patent Document 1, and the message from the non-IMS terminal (ie, the non-SIP message) is A method of routing a SIP message from the application server to the CSCF or the proxy server by determining whether the called subscriber is an IMS subscriber or a non-IMS subscriber is transmitted to the application server via a proxy server.

An object of the present invention is to enable the support of all IMS services not only IMS subscribers but also non-IMS subscribers.

In addition, another object of the present invention is to determine the type of recipient subscriber (IMS subscriber or non-IMS subscriber) to receive the SIP message for the IMS service, and to change the routing path of the message so as to match the determined type. .

It is another object of the present invention to further simplify the message processing mechanism by establishing different message delivery paths for IMS subscribers and non-IMS subscribers.

Other objects and advantages of the invention will be described below and will be appreciated by the practice of the invention. Furthermore, the objects and advantages of the present invention can be realized by means and combinations indicated in the appended claims.

In order to achieve the above object, the present invention provides an application between an application server of IMS, a call session control server (CSCF) and a gateway device (an apparatus for performing protocol conversion to provide IMS services to non-IMS subscribers). Disclosed are a type of a subscriber (IMS subscriber or a non-IMS subscriber) to receive a message from a server, and a routing device and a routing method for different routing paths of a message so as to conform to the determined type.

First, the routing device according to the first aspect of the present invention, an IMS (IP Multimedia Subsystem) subscriber network for providing an IMS service to a mobile communication terminal that supports a Session Initiation Protocol (SIP) or a mobile communication terminal that does not support SIP In order to interface the communication between the non-IMS subscriber network for providing IMS service and the application server of the IMS service network, the message received from the application server is analyzed to identify the subscriber to receive the message, and the subscriber is non Discrimination means for determining whether to be an IMS subscriber or an IMS subscriber; And routing means for routing the message to the IMS subscriber network if the subscriber is an IMS subscriber and for routing the message to the non-IMS subscriber network if the subscriber is a non-IMS subscriber.

In this case, the IMS subscriber network is an IP network including a Serving-Call Session Control Function (S-CSCF), and the non-IMS subscriber network is an IP network including a gateway device for converting a SIP message and a non-SIP message. to be.

In addition, the routing device of the present invention, the subscriber identity information (URI: Uniform Resource Identifier), subscriber type information (USER TYPE) for determining whether the subscriber is an IMS subscriber or a non-IMS subscriber and the address of the S-CSCF Message receiving means for parsing and analyzing a message received from a database or an external network node that stores and manages information or address information of the gateway device.

The determining means checks the URI of the subscriber from the header of the parsed message and determines whether the subscriber is an IMS subscriber or a non-IMS subscriber by querying the database using this URI.

If the subscriber to receive the message is an IMS subscriber, the routing means extracts address information of the S-CSCF assigned to the subscriber from the database, and uses the address information to transfer the message to the corresponding S-CSCF. If the subscriber to receive the message is a non-IMS subscriber, the address information of the gateway device to which the subscriber belongs is extracted from the database, and the message is sent to the corresponding gateway device using the address information. .

In addition, the routing device of the present invention comprises a subscriber URI, subscriber type information, address information of the S-CSCF or address information of the gateway device based on a register message received through the IMS subscriber network or the non-IMS subscriber network. Subscriber information registration means for registering the subscriber registration information in the database may be further included.

In addition, the gateway device, the mobile communication terminal that does not support the SIP protocol and the interface for performing IP-based communication with the routing device; a management data table for storing and managing data for data mapping according to conversion of a non-SIP message or a SIP message; A message conversion unit converting a non-SIP message into a mapped SIP message and converting a SIP message into a mapped non-SIP message with reference to the management data table; Through the interfacing unit, the non-SIP message received from the mobile communication terminal that does not support the SIP protocol is analyzed to extract data necessary for converting into a SIP message recognizable by the routing device, and then the converted A non-SIP message generation and analysis unit for transmitting a SIP message to the interfacing unit; And analyzing the SIP message received from the routing device through the interfacing unit, extracting data necessary for converting into a non-SIP message that can be recognized by a mobile communication terminal that does not support the SIP protocol, and then converting the SIP message. SIP message generation and analysis unit for transmitting the non-SIP message to the interfacing unit.

The routing method according to the second aspect of the present invention provides an IMS (IP Multimedia Subsystem) subscriber network for providing an IMS service to a mobile communication terminal supporting a Session Initiation Protocol (SIP) or an IMS to a mobile communication terminal not supporting SIP. Receive a SIP Register message from a non-IMS subscriber network to provide a service; Subscriber registration step of confirming subscriber URI, subscriber type information (information for determining whether subscriber is IMS subscriber or non-IMS subscriber), source address information from the SIP Register message, and constructing subscriber registration information ; Receiving a SIP message from an application server of an IMS service network; Extracting a subscriber URI from the SIP message and confirming the subscriber type information and the sender address information using the subscriber URI; And routing the SIP message to the IMS subscriber network or a non-IMS subscriber network based on the subscriber type information and the sender address information.

According to the present invention, all IMS services can be provided even for a non-IMS terminal (or non-IMS terminal) in which a SIP stack is not provided in a mobile communication terminal. In addition, by optimizing the message transmission paths for the IMS terminal and the non-IMS terminal differently, the message transmission and reception are simplified and the system is more efficient.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

First, Figure 2 is a block diagram of an IMS network according to a preferred embodiment of the present invention.

2, the IMS network of the present invention includes a non-IMS subscriber network, an IMS subscriber network and an IMS service network. The non-IMS subscriber network includes a non-IMS terminal (UE2, 53) and a gateway device (G / W, 30), and the IMS subscriber network includes a call session controller (CSCF) 41 and a home subscriber server (HSS). IMS core network 40 and IMS terminals UE1 and 51, each of which is comprised of 42), wherein the IMS service network includes an application server unit (AS) 10 and a routing device 20.

 The user terminal UE1 51 and the UE2 53 communicate with an IMS service network including an application server unit (AS) 10 through an access network (not shown) of the mobile communication system. In this case, the IMS terminal UE1 51 uses a call session controller (CSCF) 41 and a session initiation protocol (SIP), and the non-IMS terminal UE2 53 is connected to the gateway device (G / W, 30). Use a non-SIP protocol such as Client Server Protocol (CSP).

The call session controller (CSCF) 41 is a P-CSCF that forms the first point of contact with the IMS terminal UE1 51, and the S-CSCF and UE1 51 that provide IP multimedia services for the UE1 51. It is defined as I-CSCF that identifies the corresponding S-CSCF and sends the SIP request received from UE1 51 to the corresponding S-CSCF.

The home subscriber server (HSS) 42 stores all data on the subscriber, and performs functions such as profile management of the user and information management and authority verification for mobility management of the user terminal.

The application server unit (AS) 10 includes IM (Present Messaging), Presence (Voice), Voice Call Continuity (VCC), Push-To-Talk (PTT), Voice over Internet Protocol (VoIP), Group List (GLMS). A network element for delivering an IP multimedia service including a management server (IMS Centralized Services), etc. to a subscriber, and comprising at least one application server (ie, AS1, AS2 ... ASn).

The gateway device (G / W, 30) is interposed between the subscriber station UE2 (53) and the application server (AS) 10 to convert between the SIP message and the CSP (Client Server Protocol) message as shown in Figure 3 Has

In addition, the routing device 20 delivers SIP messages received through the IMS subscriber network and the non-IMS subscriber network to the corresponding application servers AS1, AS2... ASn, and forwards them from the application server 10. It routes the SIP message to either the IMS subscriber network or the non-IMS subscriber network according to the type of the called subscriber. That is, the routing device 20 analyzes the message received from the application server 10 to determine the type (IMS subscriber or non-IMS subscriber) of the called party to which the message is to be delivered, and according to the determined type Deliver message to IMS subscriber network or to non-IMS subscriber network.

First, the internal configuration of the gateway device G / W 30 according to the present invention will be described in more detail with reference to FIG. 3.

As shown in the figure, the gateway device (G / W) 30 according to the present invention includes an IP-based interface unit 37, a CSP message generation and analysis unit 34, a SIP message generation and analysis unit 35, and a message. The conversion unit 33 and the management data table 31 are included.

The interface unit 37 is for communicating with the subscriber station UE2 53 and the routing device 20 of the IMS service network, which do not support the SIP function, from the subscriber station UE2 53 or the routing device 20. The received message is branched to the CSP message generating and analyzing unit 34 and the SIP message generating and analyzing unit 35, respectively.

Here, the CSP message generating and analyzing unit 34 analyzes a message (CSP message) transmitted from the subscriber station UE2 53 without the SIP function and converts the message into a SIP message that can be recognized by the routing device 20. Data necessary for conversion is extracted, and the extracted data is transferred to the message conversion unit 33 for message conversion. In addition, the SIP message generation and analysis unit 35 analyzes the SIP message received through the routing device 20 from the SIP-based application server 10, the subscriber station UE2 (53) without the SIP function Extracts data necessary to convert the message into a message (CSP message) that can be recognized, and transfers the extracted data to the message conversion unit 33 for message conversion.

The message converting unit 33 uses data extracted from the CSP message generating and analyzing unit 34 and the SIP message generating and analyzing unit 35 to form a corresponding message mapped to the data. Convert to That is, the message conversion unit 33 converts the CSP message input from the CSP message generation and analysis unit 34 into a SIP message that can be recognized by the routing device 20. In addition, the message conversion unit 33 is a non-SIP message that can recognize the SIP message input from the SIP message generation and analysis unit 35 in the subscriber station UE2 53 without the SIP function (that is, CSP message).

The data converted in this way is transmitted to the CSP message generation and analysis unit 34 and the SIP message generation and analysis unit 35, respectively, and the respective messages are again transferred to the destination UE2 through the interface unit 37. Or routing device). Here, the management data table 31 stores data for data mapping according to message conversion in the message conversion unit 33.

Next, the internal configuration of the routing device 20 according to the present invention will be described in more detail with reference to FIG. 4.

As shown in the figure, the routing device 20 according to the present invention includes an IP-based interface unit 21, a message processing unit 22, a subscriber registration processing unit 24, a subscriber type determination unit 23 and a path determination unit ( 26). In addition, the routing device 20 of the present invention is a subscriber registration information database 25 to query subscriber registration information such as subscriber identification information (USER ID), subscriber type information (USER TYPE) and source address information (LOCATION) See.

The interface unit 21 transfers the message received from the call session controller (CSCF) 41 of the IMS subscriber network or the gateway device (G / W, 30) of the non-IMS subscriber network to the corresponding application server 10. The message received from the application server 10 branches to the call session controller (CSCF) 41 of the IMS subscriber network or the gateway device (G / W, 30) of the non-IMS subscriber network.

The message processing unit 22 parses the message received from the interface unit 21, analyzes the header of the parsed message, and transfers the message to the subscriber registration processing unit 24 to register the subscriber (see FIG. 6). ) Or transmit the message to the subscriber type determination unit 23 to perform the message routing procedure (see FIG. 7).

For example, the message processor 22 analyzes the header part of the parsed message to distinguish whether the message is a "Register" message or an "Invite" message (or a Subscribe message, Notify message, Publish message, etc.), In the case of a "Register" request, the message is transmitted to the subscriber registration processor 24, and in the case of a "Invite" request, the message is transmitted to the subscriber type determination unit 23.

The subscriber registration processor 24 receives a "Register" message from the message processor 22 and builds subscriber registration information as shown in FIG. 5 in the subscriber registration database. That is, subscriber identification information (USER ID), subscriber type information (USER TYPE), and source address information (LOCATION) are extracted from the message received from the message processor 22, and stored in the subscriber registration information database 25. do.

The subscriber identification information (USER ID) means, for example, a phone number such as "URI", and the subscriber type information (USER TYPE) means that the subscriber is an IMS subscriber (C) or a non-IMS subscriber (M). Indicates cognition. In addition, the caller address information (LOCATION) indicates the S-CSCF address information assigned for the subscriber when the subscriber is an IMS subscriber (C), the subscriber belongs to the non-IMS subscriber (M) The address information of the gateway device G / W is shown.

In addition, the subscriber type determination unit 23 receives a SIP message (Invite message, Subscribe message, Notify message, Publish message, etc. delivered from an application server) from the message processing unit 22, and the message header unit "URI" Query the subscriber registration information database 25 to determine whether the called party to receive the message is an IMS subscriber (C) or a non-IMS subscriber (M).

The route determining unit 26 receives subscriber type information (M or C) from the subscriber type determining unit 23, and source address information (CSCF) of a called subscriber to which a corresponding message is to be delivered using the "URI" information. Address information or G / W address information) is extracted from the subscriber registration information database 25. Accordingly, the interface unit 21 based on the source address information received from the route determining unit (eg, "Invite" message, "Subscribe message", "Notify message", "Publish message", etc.). ) To the IMS subscriber network (S-CSCF) or to the non-IMS subscriber network (G / W).

In order to determine the routing address of the message received from the application server, the routing device shown in FIG. 4 determines the subscriber's type using the " URI " Based on this, the address information of the network element (CSCF or G / W) to be routed next is determined. However, the subscriber type determination unit 23 and the route determination unit 26 are integrated into one function module (path determination module), and the subscriber function “URI” is used in the integrated function module without discriminating the subscriber type. It is also possible to modify the form to extract the address information of the network element (CSCF or G / W) to be directly routed next.

By using the routing device 20 and the gateway device 30 of the above-described configuration, IMS service is provided for the IMS terminal UE1 supporting the SIP protocol as well as the non-IMS terminal UE2 not supporting the SIP protocol. The process will be described with reference to FIGS. 6 and 7.

First, FIG. 6 is a procedure flow diagram illustrating a process in which an IMS subscriber or a non-IMS subscriber registers with the IP multimedia subsystem via a CSCF or gateway device (G / W).

The IMS subscriber transmits a SIP message requesting registration to the CSCF 41 by using a mobile communication terminal (UE1) 51 supporting the SIP stack, and the non-IMS subscriber uses a mobile communication terminal (which does not support the SIP stack). The UE 2) 53 transmits a CSP message requesting registration to the gateway device 30 (S101). At this time, the gateway device (G / W) 30 converts the CSP message into a SIP message. Then, the routing device 20, and the CSCF (S-CSCF) transfers the SIP message received from the mobile communication terminal UE1 to the routing device (30).

The routing device receiving the registration request message from the IMS terminal UE1 or the non-IMS terminal UE2 parses and analyzes the corresponding message, and analyzes the subscriber message (USER URI) and subscriber type information (IMS subscriber or non-IMS subscriber). And subscriber registration information such as source address information (CSCF address information or G / W address information), and store it in the subscriber registration information database 25 (S103).

The routing device 20 which has completed the construction of subscriber registration information in this way transmits the registration request message (Register message) to the corresponding application server 10 (S104).

Accordingly, the application server 10 sets up the service environment using the subscriber profile information included in the registration request message and sends a response message to the subscriber station (UE). (S105, S106, S107)

As such, in the state in which subscriber registration is completed through FIG. 6, the routing device 20 may view SIP messages (eg, Invite message, Subscribe message, Notify message, Publish message, etc.) from the application server 10. Routing follows the flow chart shown in FIG.

The routing device 20 having received the SIP message from the application server 10 checks the "URI" from the header of the SIP message. (S201, S203) The subscriber registration database 25 is identified using this "URI". Inquiry is made to determine the type of the called subscriber who will receive the SIP message (S205). That is, it is determined whether the called subscriber to receive the message is an IMS subscriber (C) or a non-IMS subscriber (M). )

At this time, when the called subscriber is an IMS subscriber, in order to route the corresponding SIP message to the IMS subscriber network, address information of the S-CSCF allocated for the subscriber is extracted from the subscriber registration information database 25 (S209).

The routing device 20 confirming the S-CSCF address information transmits the SIP message to the corresponding S-CSCF. (S211) The S-CSCF calls the corresponding destination terminal UE1 according to the SIP message. Processing proceeds (S213).

On the other hand, when the called subscriber is determined to be a non-IMS subscriber in step S207, in order to route the SIP message to the non-IMS subscriber network, the address information of the G / W 30 to which the subscriber belongs is registered in the subscriber registration information database ( 25). (S208)

The routing device 20 confirming the G / W 30 address information transmits the SIP message to the corresponding G / W 30. (S210) G / W receiving the SIP message from the routing device 20 30 converts the SIP message into a CSP message that can be recognized by the non-IMS terminal (S212), and then transmits the SIP message to a corresponding called terminal UE2 (S214).

As described above, in the case of FIG. 7, the routing device 20 that checks the subscriber URI from the header of the message received from the application server 10 uses the URI to determine the subscriber's type information (IMS subscriber C) or non- IMS subscriber (M)) is shown as essentially confirming. However, this determination of subscriber type is not an essential procedure in the present invention. That is, the routing device 20 directly checks the address information necessary for routing the corresponding message from the subscriber registration database 25 using the subscriber URI, and checks the corresponding message based on the confirmed address information. It can also be transmitted by G / W of S-CSCF or non-IMS subscriber network.

In addition, in the present invention, although the non-IMS subscriber and the G / W device is described as communicating based on the CSP protocol, many communication protocols other than the CSP protocol can be used, the G / W device is all non- Must be able to convert SIP protocol to SIP protocol.

In the above described with reference to the accompanying drawings, preferred embodiments of the present invention in detail. However, embodiments of the present invention can be variously modified or applied by those skilled in the art, the scope of the technical idea according to the present invention should be determined by the claims to be described later will be.

The following drawings, which are attached to this specification, illustrate preferred embodiments of the present invention, and together with the detailed description of the present invention serve to further understand the technical spirit of the present invention, the present invention includes matters described in such drawings. It should not be construed as limited to.

1 is a block diagram of an IP multimedia subsystem according to the prior art.

2 is a block diagram of an IP multimedia subsystem according to the present invention.

FIG. 3 is an internal functional block diagram of a gateway device applied to FIG. 2.

4 is an internal functional block diagram of a routing device applied to FIG. 2.

5 is a data structure diagram of subscriber registration information stored and managed in a subscriber registration information database.

6 is a flowchart of a subscriber registration procedure according to the present invention.

7 is a flowchart of a procedure for routing a message from an application server to a called subscriber.

Claims (15)

IP Multimedia Subsystem (IMS) subscriber network to provide IMS service to mobile communication terminal supporting Session Initiation Protocol (SIP) or non-IMS subscriber network and IMS to provide IMS service to mobile communication terminal not supporting SIP A routing device for interfacing communication between application servers in a service network. Determining means for analyzing a message received from the application server to identify a subscriber to receive the message, and to determine whether the subscriber is a non-IMS subscriber or an IMS subscriber; Routing means for routing the message to the IMS subscriber network if the subscriber is an IMS subscriber and for routing the message to the non-IMS subscriber network if the subscriber is a non-IMS subscriber. . The method of claim 1, The IMS subscriber network is an IP network including a Serving-Call Session Control Function (S-CSCF), and the non-IMS subscriber network is an IP network including a gateway device for converting SIP messages and non-SIP messages. Characterized in that the routing device. The method of claim 2, Uniform Resource Identifier (URI), subscriber type information (USER TYPE) for determining whether the subscriber is an IMS subscriber or a non-IMS subscriber, address information of the S-CSCF or address information of the gateway device The routing device further comprises a database for storing and managing. The method of claim 3, wherein And a message receiving means for parsing and analyzing a message received from an external network node. The method of claim 4, wherein the determining means, And determining the subscriber's URI from the header of the parsed message and querying the database using the URI to determine whether the subscriber is an IMS subscriber or a non-IMS subscriber. The method of claim 5, wherein the routing means, If the subscriber to receive the message is an IMS subscriber, the address information of the S-CSCF assigned to the subscriber is extracted from the database, and the message is sent to the corresponding S-CSCF using the extracted address information. If the subscriber receiving the message is a non-IMS subscriber, extracting the address information of the gateway device to which the subscriber belongs, from the database, and sending the message to the corresponding gateway device using the extracted address information. Characterized in that the routing device. The method according to any one of claims 3 to 6, Registering subscriber registration information consisting of subscriber URI, subscriber type information, address information of S-CSCF or address information of gateway device in the database based on a register message received through the IMS subscriber network or the non-IMS subscriber network. And a subscriber information registration means. The method of claim 7, wherein the gateway device, A mobile communication terminal that does not support the SIP protocol and an interfacing unit for performing IP-based communication with the routing device; a management data table for storing and managing data for data mapping according to conversion of a non-SIP message or a SIP message; And And a message converting unit converting a non-SIP message into a mapped SIP message and converting a SIP message into a mapped non-SIP message with reference to the management data table. The method of claim 8, Through the interfacing unit, the non-SIP message received from the mobile communication terminal that does not support the SIP is analyzed to extract data necessary for converting into a SIP message recognizable by the routing device, and then the converted SIP A non-SIP message generation and analysis unit for transmitting a message to the interfacing unit; And Through the interfacing unit, the SIP message received from the routing device is analyzed to extract data necessary for converting into a non-SIP message that can be recognized by a mobile communication terminal that does not support the SIP, and then the converted non And a SIP message generation and analysis unit for transmitting a SIP message to the interfacing unit. The method of claim 9, Routing device, characterized in that the non-SIP message is a CSP (Client Server Protocol) message. SIP from an IP Multimedia Subsystem (IMS) subscriber network for providing IMS services to a mobile communication terminal supporting Session Initiation Protocol (SIP) or a non-IMS subscriber network for providing IMS services to a mobile communication terminal not supporting SIP. Receive a Register message; Subscriber registration step of confirming subscriber URI, subscriber type information (information for determining whether subscriber is IMS subscriber or non-IMS subscriber), source address information from the SIP Register message, and constructing subscriber registration information ; Receiving a SIP message from an application server of an IMS service network; Extracting a subscriber URI from the SIP message and confirming the subscriber type information and the sender address information using the subscriber URI; And Routing the SIP message to the IMS subscriber network or a non-IMS subscriber network based on the subscriber type information and the source address information. The method of claim 11, The IMS subscriber network is an IP network including a Serving-Call Session Control Function (S-CSCF), and the non-IMS subscriber network is an IP network including a gateway device for converting SIP messages and non-SIP messages. A routing method characterized by the above. The method of claim 12, And the sender address information is address information of the S-CSCF or address information of the gateway device. The method of claim 13, wherein the routing step comprises: If it is determined by the subscriber type information that a subscriber to be received is an IMS subscriber, the SIP message is sent to the corresponding S-CSCF based on the address information of the S-CSCF. If it is determined by the subscriber type information that the subscriber to receive the message is a non-IMS subscriber, routing the SIP message to the corresponding gateway device based on the address information of the gateway device. The method of claim 14, The gateway device converts the SIP message into a Client Server Protocol (CSP) message and transmits it to the called subscriber.

Images