JP2008219723A - Sip service system, apparatus, method and program used therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To utilize both a service which does not utilize a session initiation protocol (SIP) session and a service which utilizes an SIP session, while using an SIP disabled application. <P>SOLUTION: An SIP service registration server 22 holding a corresponding relation between a URL for providing services utilizing SIP session and an SIP-URL is disposed in a network 2 and a client terminal 1 comprises an SIP service session control means 12 which operates as a DNS resolver with respect to an application 11. A session control means 121 of the SIP service session control means 12 causes an SIP service determination means 124 to make an SIP service inquiry to the SIP service registration server 22, upon the receipt of a DNS inquiry request from the application 11 and if it is determined that a service to be provided by a designated URL is an SIP service, an SIP session is established by a first SIP-UA means 123. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a SIP service system for implementing a service using a SIP session, a SIP session control device used therefor, a SIP session control method, and a SIP session control program, and in particular, a SIP session using an application that does not support SIP. The present invention relates to a SIP service system for implementing a utilized service, a SIP session control device used therefor, a SIP session control method, and a SIP session control program.

  In the conventional method, in order to implement a service using a SIP (Session Initiation Protocol) session, a SIP-compatible application (specifically, a client side (service requesting side) application and a server side (service providing side) application) In particular, an application in which SIP-UA (User Argent) is mounted is necessary, and development thereof is indispensable. An existing application that does not support SIP cannot provide or receive a service using a SIP session (hereinafter simply referred to as a SIP service).

  As a technique for receiving an SIP service using an existing application that does not support SIP, for example, Patent Document 1 describes an application that supports DNS (Domain Name System) but does not support SIP. Describes a protocol conversion apparatus that performs address resolution using SIP.

  Further, for example, in Patent Document 2, connection to / disconnection from a DNS name inquiry destination is made using DNS, which is a general protocol, without requiring the LAN terminal to use a special protocol for connection. A proxy gateway apparatus and a communication connection method using the same are described.

JP 2006-352753 A (paragraphs 0022-0026, 0032) JP 2006-109316 A (paragraphs 0033 and 0034, FIG. 4)

  If the protocol conversion device described in Patent Document 1 or the gateway device described in Patent Document 2 is used, an SIP service can be used if it is an application that supports DNS even if it is an existing application that does not support SIP. Can receive.

  However, in the protocol conversion device described in Patent Document 1, FDQN (Fully Qualified Domain Name) is unconditionally converted into SIP-URI, so that the connection destination is, for example, when the SIP service is an IP telephone service. It can be applied only to a network system that presupposes that all are SIP-compatible. For example, in addition to the SIP service, a network system that provides a service that does not use an SIP session (for example, an HTTP service performed over a general TCP session) cannot be supported.

  Note that the gateway device described in Patent Document 2 resolves the address using the SIP protocol or transfers it to the DNS server depending on whether the connection destination information included in the DNS inquiry information is an IP telephone number or a SIP-URI. Switching address resolution. Accordingly, it is possible to cope with a network system in which services other than the SIP service are also provided. However, in the communication connection method described in Patent Document 2, in order to establish a SIP session, an IP telephone number or SIP-URI must be specified as connection destination information from a LAN terminal. That is, the user using the LAN terminal must specify the IP telephone number or SIP-URI for the application that executes the DNS inquiry.

  By the way, NGN (Next Generation Network) is being discussed by standardization organizations such as ITU-T as an IP network for integrating telephone service and video communication service using SIP. Assuming that NGN is used, a service provision form is also conceivable in which a certain server provides an HTTP function on a SIP session while providing a communication service such as an authentication function or QoS by SIP.

  If the gateway device described in Patent Document 2 is applied to such a service provision form, the LAN terminal uses an FDQN (specifically, “HTTPQ”) that designates HTTP for an application such as a Web browser. A URL starting with “http: //” is specified, and a SIP-URI has to be specified for a DNS resolver (software that performs address resolution based on a domain name using a name server). Such designation cannot be performed using an existing application (Web browser) that does not support SIP.

  Therefore, the present invention provides a SIP service system that makes it possible to use both a service that does not use a SIP session and a service that uses a SIP session using an existing application that does not support SIP, a SIP session control device, and a SIP session It is an object to provide a control method and a program for SIP session control.

  Specifically, a SIP service system that can provide a non-SIP-compliant application not only without using a SIP session but also with a service using a SIP session without being aware of the SIP session. An object is to provide a SIP session control device, a SIP session control method, and a SIP session control program to be used.

  The SIP service system according to the present invention is a SIP service system for implementing a Web service that uses a SIP session using an application that is not SIP-compliant, and the URL of the Web service that uses the SIP session and the Web service SIP service session for accepting a DNS inquiry request from an application in a SIP service system in which a SIP service registration server (for example, SIP service registration server 22) that holds an associated SIP-URI in association with it is arranged on a communication network Control means (for example, SIP service session control means 12), and the SIP service session control means, when receiving a DNS inquiry request from an application, Determine whether the service provided by the URL is a Web service using a SIP session based on the result of inquiring SIP-URI by specifying the URL specified in the DNS inquiry request to the service registration server When the SIP service session control means determines that the service provided by the URL is a Web service using an SIP session, the SIP session corresponding to the URL obtained as a result of the inquiry is used as the SIP session. And the other party's IP address obtained as a result is returned to the application as a DNS inquiry response.

  The SIP service system is a SIP service system for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that is not compatible with SIP, and a Web service that uses a SIP session. In a SIP service system in which a SIP service registration server (for example, the SIP service registration server 22) that stores and associates the URL of the Web service with the SIP-URI assigned to the Web service on the communication network, SIP service session control means (for example, SIP service session control means 12) that accepts a DNS inquiry request is provided, and the SIP service session control means receives a DNS inquiry from an application. When the registration request is received, based on the result of inquiring the SIP-URI by specifying the URL specified in the DNS inquiry request to the SIP service registration server, the service provided by the URL sends a SIP session. The SIP service session control unit determines whether the service provided by the URL is a Web service using a SIP session, and determines whether the service is a used Web service. A SIP session may be established using the SIP-URI as a partner, and the partner IP address obtained as a result may be returned to the application as a DNS inquiry response.

  Further, when the SIP service session control means determines that the service provided by the URL specified in the DNS inquiry request is not a Web service using the SIP session, the SIP service session control means specifies the DNS inquiry request to the DNS server. An IP address corresponding to the domain name obtained as a result of inquiring an IP address by designating a domain name specified by the URL may be returned to the application as a DNS inquiry response.

  Also, the SIP service session control means cannot obtain an IP address corresponding to the domain name as a result of inquiring the IP address by specifying the domain name specified by the URL specified in the DNS inquiry request to the DNS server. In this case, the SIP service registration server may be inquired about the SIP-URI by specifying the URL specified in the DNS inquiry request.

  Further, the SIP service session control means includes a control unit (for example, session control means 121) that accepts a DNS inquiry request from an application, and a domain specified by the URL for the DNS specified by the control unit. A DNS resolver means (for example, DNS resolver means 125) for inquiring an IP address by designating a name and a SIP for inquiring a SIP-URI by designating the URL to the SIP service registration server for a URL designated by the control unit -URI resolver means (for example, SIP service determination means 124) and SIP user agent means (for example, first SIP-UA means 123) for performing client control by SIP with the SIP-URI specified by the control unit as a destination. )When It may comprise.

  A SIP service session control device according to the present invention is a SIP service session control device for implementing a Web service that uses a SIP session using an application that is not SIP-compliant, and accepts a DNS inquiry request from an application. Service session control means is provided. When a DNS inquiry request is received from an application, the SIP service session control means associates the URL of the Web service that uses the SIP session with the SIP-URI assigned to the Web service. Then, based on the result of inquiring SIP-URI by specifying the URL specified in the DNS inquiry request to the SIP service registration server to be held, the service provided by the URL is It is determined whether or not the web service uses an IP session, and the SIP service session control means obtains the URL obtained as a result of the inquiry when it is determined that the service provided by the URL is a web service using the SIP session. A SIP session is established with the SIP-URI corresponding to the destination as a destination, and the destination IP address obtained as a result is returned to the application as a DNS inquiry response.

  The SIP service session control device is a SIP service session control device for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that does not support SIP. SIP service session control means for receiving a DNS inquiry request is provided, and the SIP service session control means is assigned to the URL of the Web service that uses the SIP session and the Web service when the DNS inquiry request is received from the application. Based on the result of inquiring the SIP-URI by specifying the URL specified in the DNS inquiry request to the SIP service registration server that holds the SIP-URI in association with it. When it is determined whether the service provided by the URL is a Web service using an SIP session, the SIP service session control unit determines that the service provided by the URL is a Web service using an SIP session Alternatively, a SIP session may be established with the SIP-URI corresponding to the URL obtained as a result of the inquiry as a partner, and the partner IP address obtained as a result may be returned to the application as a DNS inquiry response.

  The SIP session control method according to the present invention is a SIP session control method for implementing a Web service that uses an SIP session using an application that is not compatible with SIP, and an SIP service session that accepts a DNS inquiry request from an application. When the control means accepts a DNS inquiry request, the control means associates the URL of the Web service that uses the SIP session with the SIP-URI assigned to the Web service, and Based on the result of inquiring the SIP-URI by specifying the URL specified in the DNS inquiry request, it is determined whether or not the service provided by the URL is a Web service using an SIP session. When the service control unit determines that the service provided by the URL is a Web service using a SIP session, the SIP control unit establishes a SIP session with the SIP-URI corresponding to the URL obtained as a result of the inquiry, The other party IP address obtained as a result is returned to the application as a DNS inquiry response.

  The SIP session control method is a SIP session control method for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session by using a non-SIP-compliant application, and a DNS inquiry from the application. A SIP service session control means for accepting a request, when accepting a DNS inquiry request, associates and holds the URL of a web service that uses the SIP session and the SIP-URI assigned to the web service Whether the service provided by the URL is a Web service using a SIP session based on the result of inquiring SIP-URI by specifying the URL specified in the DNS inquiry request to the registration server. When the SIP service session control unit determines that the service provided by the URL is a Web service using the SIP session, the SIP-URI corresponding to the URL obtained as a result of the inquiry is sent to the other party. It is also possible to establish a SIP session and return the destination IP address obtained as a result to the application as a DNS inquiry response.

  A SIP session control program according to the present invention is a SIP session control program for implementing a Web service that uses an SIP session using an application that is not compatible with SIP, and sends a DNS inquiry request to the computer from the application. If accepted, the URL specified in the DNS inquiry request to the SIP service registration server that holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service in association with each other Based on the result of inquiring the SIP-URI specifying the URL, a process for determining whether or not the service provided by the URL is a Web service using an SIP session, and the service provided by the URL determines the SIP session When the web service is determined to be used, a SIP session is established with the SIP-URI corresponding to the URL obtained as a result of the inquiry as a partner, and the partner IP address obtained as a result is sent to the application as a DNS inquiry response It is characterized by executing a process of replying.

  The SIP session control program is a SIP session control program for implementing a Web service that does not use an SIP session and a Web service that uses an SIP session, using an application that is not compatible with SIP. When a DNS inquiry request is received from an application, the DNS inquiry is sent to the SIP service registration server that holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service in association with each other. Based on the result of inquiring SIP-URI specifying the URL specified in the request, a process for determining whether the service provided by the URL is a Web service using an SIP session, and provided by the URL When the service is determined to be a Web service using a SIP session, a SIP session is established with the SIP-URI corresponding to the URL obtained as a result of the inquiry as a partner, and the partner IP address obtained as a result is determined. A process of returning to the application as a DNS inquiry response may be executed.

  According to the present invention, the SIP service session control means that operates as a DNS resolver for the application controls the SIP session after determining whether it is a SIP service in response to an inquiry request from the application. In addition to services that do not use SIP sessions, services that use SIP sessions can be provided without being aware of SIP sessions. As a result, it is possible to use both a service that does not use a SIP session and a service that uses a SIP session by using an existing application that does not support SIP.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration example of a SIP service system according to the present embodiment. The SIP service system shown in FIG. 1 includes a client terminal 1, a Web server system 3, a name server 21, a SIP service registration server 22, and a SIP server 23. The client terminal 1, the Web server system 3, the name server 21, the SIP registration server 22, and the SIP server 23 are connected via the network 2.

  The client terminal 1 includes an application 11 and SIP service session control means 12.

  The application 11 is an existing application that does not support SIP, such as a Web browser. The application 11 is not limited to a Web browser, but an application that provides a user with various services provided by the server by accessing a predetermined server through network communication using TCP or UDP or a higher communication protocol. Any application that performs a DNS inquiry procedure may be used. For example, it may be a client application that performs network communication with various servers such as a mail server, an IP telephone server, an authentication server, a video distribution server, an FTP server, and a game server. Further, the number of applications 11 is not limited to one, and a plurality of applications 11 may exist.

  Specifically, the application 11 realizes its function by being read into an information processing apparatus that operates according to a program such as a CPU provided in the client terminal 1. Hereinafter, when the expression “application 11 does” is used, it means that the information processing apparatus included in the client terminal 1 performs its operation according to the application 11.

  The SIP service session control means 12 is a means for performing SIP session control as necessary while operating as a DNS resolver for the application 11, and includes a session control means 121, an application monitoring means 122, a first SIP-UA means 123 (SIP-UA # 1 in FIG. 1), SIP service determination means 124, and DNS resolver means 125 are included. Note that the SIP service session control unit 12 is realized by an information processing apparatus such as a CPU that operates according to a program in which each unit included in the SIP service session control unit 12 is implemented as a function.

  The session control unit 121 receives a DNS inquiry from the application 11 and controls other units to perform address resolution for the specified domain name, and to establish and release a SIP session as necessary.

  The application monitoring unit 122 monitors the operation state of the application 11. The application monitoring unit 122 detects at least the end of the application 11 that has established the SIP session. The application monitoring unit 122 holds the protocol information of the application 11. Here, the protocol information is information necessary to establish a SIP session in which at least the SIP service accessed by the application 11 is implemented. For example, the software information (name and identifier) of the application 11 and its information This is information in which a protocol used by the application 11 is associated with a transport layer protocol and a port number. Specifically, there is at least information for describing an SIP INVITE request in association with information included in the DNS inquiry request message from the application 11 or information of the application 11 that can be acquired when the DNS inquiry request message is received. It only needs to be registered. The protocol information may be registered in advance before using the application for receiving the Web service by the user of the client terminal 1, or the application monitoring unit 122 performs communication by TCP or UDP. And the protocol information at that time and the information of the application 11 that performed the communication may be registered in association with each other.

  The first SIP-UA means 123 is a means for executing the SIP-UA function in the client terminal 1. Specifically, the first SIP-UA unit 123 generates a SIP request according to an instruction from a higher-level application or a predetermined condition and transmits it to the SIP server 23, or receives a SIP request from the SIP server 23. The SIP session is established or released by returning a SIP response to the SIP request. The host application for the first SIP-UA means 123 is the session control means 121. In addition, the first SIP-UA unit 123 may implement a communication service such as an authentication function or QoS with another SIP-UA or the SIP server 23 within a SIP compatible range. In the present embodiment, it is assumed that a SIP communication service is implemented with the second SIP-UA means 32 implemented by the Web server 31. The first SIP-UA means 123 can be realized, for example, by causing a CPU included in the client terminal 1 to read general SIP client software.

  The SIP service determination unit 124 is a unit that performs processing for determining whether or not the service provided by the URL specified by the DNS inquiry received from the application 11 is the SIP service. Specifically, the SIP service determination unit 124 transmits a SIP service reference request to the SIP service registration server 22 in accordance with an instruction from the session control unit 121, or a response (SIP service reference response) from the SIP service registration server 22. And so on, address resolution as a SIP service (that is, SIP-URI resolution) is performed.

  The DNS resolver means 125 is a means for executing a function of a general DNS resolver. Specifically, the DNS resolver means 125 performs address resolution by transmitting a DNS inquiry to the name server 21 or receiving a response (DNS inquiry response) from the name server 21 in accordance with an instruction from the upper application. . In the present embodiment, the host application for the DNS resolver means 125 is the session control means 121. The DNS resolver means 125 can also be realized, for example, by causing a CPU provided in the client terminal 1 to read general DNS resolver software.

  The name server 21 is a server device that accepts at least a DNS inquiry in which an FQDN is specified and returns an IP address corresponding to the specified FQDN. The name server 21 holds the correspondence (for example, correspondence table) between the FQDN of the computer connected to the zone managed by itself and the IP address, and adds the IP address corresponding to the designated FQDN to the DNS inquiry. The DNS inquiry response is returned. When the designated FQDN is an FQDN outside the zone managed by the name server 21, the IP address of another name server 21 that manages the zone including the designated FQDN is added. A DNS inquiry response may be returned. The name server is generally called a DNS server. Note that the FQDN held by the name server 21 (or other name server) is an FQDN assigned to a Web server that publishes a Web service using a general TCP session or UDP.

  The SIP service registration server 22 accepts a SIP service reference request in which a URL that can specify a resource providing a Web service is specified on at least a SIP session, and returns a SIP-URI corresponding to the specified URL. It is a server device. The SIP service registration server 22 holds a correspondence relationship (for example, correspondence table) between a URL that can identify a resource providing the SIP service and a SIP-URI currently assigned to the SIP service, and the SIP service In response to the reference request, a SIP service reference response to which the SIP-URI corresponding to the specified URL is added is returned. Note that the SIP service registration server 22 maintains the corresponding relationship in the zone managed by itself, like the name server 21, and the zone indicated by the designated URL is outside the zone managed by itself. In this case, a SIP service reference response to which the IP address of another SIP service registration server 22 that manages the designated zone is added may be returned.

  The SIP server 23 receives a SIP request indicating location registration from the SIP-UA, receives a SIP request indicating a connection request designating a communication partner and forwards it to the communication partner, or receives a SIP response returned from the communication partner. The SIP session between the SIP and the UA is controlled by establishing, releasing or changing the SIP session.

  The Web server system 3 is a server system that provides a communication service based on SIP and provides a Web service on an SIP session, and includes a Web server 31 and second SIP-UA means 32 (the SIP in FIG. 1). -UA # 2).

  The web server 31 is a server device that provides a web service in response to a request from the client terminal 1. For example, it may be an HTTP server that provides an image delivery service by receiving an HTTP request and returning a predetermined HTTP response. The Web server 31 is not limited to an HTTP server that provides an image delivery service using HTTP, but a mail server that provides an email delivery service using SMTP, an IP phone server that provides an IP phone service using VoIP, and an FTP file transfer service. In addition to an FTP server that provides a server, any server device that provides services by performing network communication using TCP or UDP or a higher communication protocol such as an authentication server or a game server may be used.

  The second SIP-UA means 32 is a means for executing the SIP-UA function in the Web server system 3. Specifically, the second SIP-UA means 32 generates a SIP request in accordance with an instruction from the upper application or in accordance with a predetermined condition and transmits it to the SIP server 23, or receives a SIP request from the SIP server 23. The SIP session is established or released by returning a SIP response to the SIP request. The upper application for the second SIP-UA means 32 corresponds to the Web server 31, but an instruction from the Web server 31 is not necessarily required. In addition, the second SIP-UA means 32 may implement a communication service such as an authentication function or QoS with another SIP-UA or SIP server 23 within a SIP compatible range. In the present embodiment, it is assumed that a SIP communication service is performed with the first SIP-UA means 123 installed in the client terminal 1.

  The second SIP-UA means 32 is realized by, for example, a SIP-compatible gateway device in which an optional function for the Web server 31 is set. Note that this can also be realized by causing the CPU included in the Web server 31 to read general SIP client software and setting optional functions for the Web server 31.

  In FIG. 1, the connection relationship according to the protocol is indicated by a broken line. For example, a broken line between the application 11 and the Web server 31 indicates a connection relationship by HTTP. Further, for example, the first SIP-UA means 123-between the second SIP-UA means 32, between the first SIP-UA means 123-the SIP server 23, and between the SIP server 23-second SIP-UA means 32. The broken line between them indicates the connection relationship by SIP. Further, for example, a broken line between the DNS resolver means 125 and the name server 21 indicates a connection relationship according to the DNS protocol.

  Next, the operation of the present embodiment will be described. First, the operation when establishing a SIP session will be described. FIG. 2 is a sequence diagram showing the flow of each process in the SIP service system when establishing a SIP session. FIG. 3 is a flowchart showing an example of the operation of the session control unit 121.

  First, as a precondition, the name server 21 registers a correspondence relationship between a domain name (FQDN) specified from a URL of a website or the like and an IP address. The SIP service registration server 22 registers a correspondence relationship between a URL that can specify a service (SIP service) that uses a SIP session and a SIP-URI. FIG. 4 is an explanatory diagram showing an example of the data configuration of the correspondence relationship (correspondence table) registered in the SIP service registration server 22. As shown in FIG. 4, at least the SIP service registration server 22 registers a URL that can identify the SIP service and a SIP-URI for connecting to the Web server that provides the SIP service. Is done. In the present embodiment, the Web server 31 provides a SIP service. Therefore, at least in the SIP service registration server 22, the URL of the SIP service provided by the Web server 31 and the SIP-URI currently assigned to the SIP service are registered in association with each other. . The SIP service registration server 22 may also register the correspondence relationship of other SIP services.

  As shown in FIG. 2, the URL is input to the application 11 on the client terminal 1 or specified by the link of the Web page (SEQ001). Here, it is assumed that the URL of the SIP service provided by the Web server 31 is specified.

  In addition, the application monitoring unit 122 monitors the operation state of the application 11 and determines that the application 11 is in a running state (SEQ002). The application 11 requests a DNS inquiry message from the DNS resolver in order to check the IP address from the input or designated URL (SEQ003). In the present embodiment, since the SIP service session control means 12 operates as a DNS resolver, the DNS inquiry request message from the application 11 is received by the session control means 121 of the SIP service session control means 12. The application monitoring unit 122 is in a state in which the application 11 is activated by a notification from the session control unit 121 when the session control unit 121 accepts the DNS inquiry request message and establishes the SIP session. May be recognized.

  When the session control means 121 receives a DNS inquiry request message from the application 11 (STEP 01 in FIG. 3), the session control means 121 first causes the DNS resolver means 125 to perform a DNS inquiry (STEP 02 in FIG. 3). The session control unit 121 transfers the DNS inquiry request message to the DNS resolver unit 125, and the DNS resolver unit 125 that has received the DNS inquiry request identifies the domain name specified by the URL specified by the application 11 to the name server 21. A DNS inquiry to which is added is transmitted (SEQ004, 005).

  The name server 21 that has received the DNS inquiry returns a DNS inquiry response indicating the inquiry result corresponding to the correspondence table held (SEQ006). Here, since the designated domain name (the domain name of the Web server 31 that provides the SIP service) is not registered in the name server 21 that manages the designated domain name in the zone, the client The DNS resolver means 125 of the terminal 1 is finally returned with a DNS inquiry response indicating that the inquiry is not applicable. Upon receiving the final DNS inquiry response from the name server 21, the DNS resolver means 125 transmits it to the session control means 121 as a DNS inquiry response message (SEQ007).

  The session control means 121 that has received the DNS inquiry response message determines whether or not the address has been resolved by the DNS resolver means 125, and if it has been resolved (Yes in STEP 03 of FIG. 3), resolves it by the DNS resolver means 125. In order to return the address to the application 11, the received DNS inquiry response message is transmitted to the application 11 (STEP 08 in FIG. 3). On the other hand, if the DNS inquiry result by the DNS resolver means 125 is not applicable (NO in STEP 03 in FIG. 3), the SIP service determination means 124 sends a URL specified by the application 11 if the problem has not been resolved. The SIP service is inquired (STEP 04 in FIG. 3).

  The session control unit 121 transmits, for example, a SIP service inquiry request message to which the URL designated by the application 11 is added by a DNS inquiry request message to the SIP service determination unit 124 (SEQ008). The SIP service determination unit 124 that has received the SIP service inquiry request message transmits a SIP service reference request to which the URL specified by the session control unit 121 is added to the SIP service registration server 22 (SEQ009). The SIP service reference request transmitted to the SIP service registration server 22 is a message indicating that the service provided by the specified URL is inquired as to whether or not the service is provided on the SIP session according to the agreement with the SIP service registration server 22. Any communication message having any data structure may be used.

  The SIP service registration server 22 that has received the SIP service reference request returns a SIP service reference response indicating the inquiry result according to the correspondence table that is held (SEQ010). Here, since the designated URL (the URL of the SIP service provided by the Web server 31) is registered in the SIP service registration server 22 that manages the designated URL as in the zone, the client terminal A SIP service reference response indicating the SIP-URI (SIP-URI of the Web server 31) associated with the URL as an inquiry result is finally returned to the SIP service determination unit 124 of the one. Upon receiving the final SIP service reference response from the SIP service registration server 22, the SIP service determination unit 124 transmits it to the session control unit 121 as a SIP inquiry response message (SEQ011).

  The session control means 121 that has received the SIP inquiry response message determines whether or not the address (that is, SIP-URI) as the SIP service has been resolved by the SIP service determination means 124, and if it has been resolved (FIG. 3). (Yes in STEP05), the SIP session is established in the first SIP-UA means 123 using the address (SIP-URI). If the SIP service address is not resolved by the SIP service determination unit 124 (No in STEP 05 in FIG. 3), a DNS inquiry response indicating no corresponding is returned to the application 11 (STEP 08 in FIG. 3).

  In order to establish a SIP session, the session control unit 121 first inquires of the application monitoring unit 122 about the protocol information of the application 11 that has requested the DNS inquiry (STEP 06 in FIG. 3). For example, the session control unit 121 transmits an application information reference message to which the name of the application 11 and the designated URL are added to the application monitoring unit 122 (SEQ012).

  The application monitoring unit 122 that has received the application information reference message searches the protocol information held by the protocol information used by the designated application 11 and returns an application information response message to which the protocol information is added (SEQ013). For example, protocol information as shown in FIG. 5 is registered in the application monitoring unit 122 in association with the software information (name, etc.) of each application 11. FIG. 5 is an explanatory diagram showing an example of the data structure of the protocol information held by the application monitoring unit 122. In the example shown in FIG. 5, the application 11 “aaa browser software” uses the protocol “HTTP”, and the transport protocol used at that time is TCP, and the used port number is “any” (any can be used). It is shown that. For example, the application monitoring unit 122 may specify the protocol information used by the application 11 based on the designated application name and URL from the protocol information as shown in FIG. Hereinafter, a case where HTTP protocol information of “aaa browser software” is returned will be described as an example.

  The session control unit 121 that has received the application information response message outputs the protocol information included in the application information response message and the SIP-URI obtained by the SIP service inquiry (SIP service reference request) by the SIP service determination unit 124. As a parameter, the SIP session is controlled (established) (STEP07 in FIG. 3). The session control unit 121 adds, for example, protocol information included in the application information response message from the application monitoring unit 122 and SIP-URI included in the SIP service inquiry response message from the SIP service determination unit 124 as SIP parameters. A SIP session establishment request message is transmitted to the first SIP-UA means 123 (SEQ014).

  When the first SIP-UA means 123 receives the SIP session establishment request message from the session control means 121, it transmits an INVITE request to the SIP server 23 based on the SIP parameters included in the SIP session establishment request message. (SEQ015). At this time, the first SIP-UA means 123 generates the SIP-URI and SIP-SDP (body part) as the destination of the INVITE request from the SIP parameters of the SIP session establishment request message received from the session control means 121. . For example, the first SIP-UA unit 123 generates an INVITE request described in SIP-SDP as shown in FIG. 6 with the SIP-URI of the Web server 31 as the destination. FIG. 6 is an explanatory diagram showing an example of SIP-SDP described in the INVITE request. For example, FIG. 6 shows that for SIP-SDP “m” (information about media), media type “data”, port number “49152”, and protocol “HTTP” are described. ing. The final INVITE request is generated not only by SIP parameters but also by information acquired by the first SIP-UA means 123 from the transport layer module and information managed by itself.

  The INVITE request transmitted from the first SIP-UA means 123 of the client terminal 1 is transferred by the SIP server 23 to the second SIP-UA means 32 of the Web server system 3 based on the SIP-URI (SEQ016). ).

  The second SIP-UA means 32 that has received the INVITE request returns an OK response to the SIP server 23 when the session can be established (SEQ017). At this time, the second SIP-UA means 32 returns an OK response in which the IP address of itself (specifically, the Web server system 3 (here, the Web server 31)) is described in SIP-SDP.

  The OK response transmitted from the second SIP-UA means 32 of the Web server system 3 is transferred by the SIP server 23 to the first SIP-UA means 123 of the client terminal 1 that is the request source (SEQ018).

  When the first SIP-UA means 123 receives the OK response, the transport address indicated by the IP address and port number of the Web server system 3 included in the OK response, and the client terminal 1 described in the INVITE request The SIP session is established between the transport address indicated by the IP address and the port number.

  The first SIP-UA unit 123 that has received the OK response transmits a SIP session establishment response message indicating that the SIP session has been established and the transport address of the session partner to the session control unit 121 (SEQ019). At this time, the first SIP-UA means 123 may include an identifier for identifying the SIP session in the SIP session establishment response message. Note that, when the SIP session establishment fails, the first SIP-UA unit 123 may transmit a SIP session establishment response message indicating the fact to the session control unit 121.

  The session control unit 121 that has received the SIP session establishment response message transmits to the application 11 a DNS inquiry response message that uses the IP address of the Web server system 3 (Web server 31) indicated by the SIP session establishment response message as an inquiry result. (SEQ020).

  In other words, when the SIP session is established by the first SIP-UA means 123, the session control means 121 uses the IP address corresponding to the URL specified from the application 11 obtained by the SIP session establishment as the inquiry result. A DNS inquiry response message is returned to the application 11 (STEP08 in FIG. 3). At this time, the session control unit 121 may hold information associating the established SIP session with the application 11 as management information for releasing the SIP session. The session control unit 121 holds, for example, the software information of the application 11 that has established the SIP session and the identifier of the SIP session in association with each other.

  The application 11 receives the DNS inquiry response message from the session control means 121, and performs HTTP communication with the corresponding IP address (SEQ021, 022). This HTTP communication is communication over a SIP session established between the first SIP-UA means 123 and the second SIP-UA means 32.

  In the above operation example, the session control unit 121 first causes the DNS resolver unit 125 to perform a DNS inquiry, and then causes the SIP service determination unit 124 to perform an SIP service inquiry (SIP service reference request) according to the result. Although an example is shown, it is possible to replace this procedure. That is, first, the SIP service determination unit 124 may make a SIP service inquiry, and the DNS resolver unit 125 may make a DNS inquiry according to the result. Note that it is possible to determine which one is to be performed first by setting.

  Next, an operation when releasing a SIP session will be described. FIG. 7 is a sequence diagram showing the flow of each process in the SIP service system when releasing a SIP session. FIG. 8 is a flowchart showing an example of the operation of the application monitoring unit 122. FIG. 9 is a flowchart illustrating an example of the operation of the session control unit 121.

  As shown in FIG. 7, after the application 11 and the Web server 31 perform necessary HTTP communication on the SIP session (SEQ 101 and 102), when the application 11 is terminated, the application monitoring unit 122 terminates the application 11. This is detected (SEQ103). For example, as shown in FIG. 8, after detecting the start of the application, the application monitoring unit 122 activates a timer at a predetermined period (STEPs 11 and 12 in FIG. 8), and the application status at the time of timeout Is checked to determine whether or not the application has ended (STEPs 13 and 14 in FIG. 8). For example, the application monitoring unit 122 receives the software information of the application 11 when the session control unit 121 establishes the SIP session, and the operating system holds the software information based on the software information every time a timeout occurs. The end of the application 11 that has established the SIP session may be detected by referring to the information indicating the activation state of each application.

  When the application monitoring unit 122 detects that the application 11 has been terminated, the application monitoring unit 122 notifies the session control unit 121 (Yes in STEP 14 in FIG. 8, STEP 15). The application monitoring unit 122 transmits, for example, an application state change notification message including the software information of the application whose end has been detected and information indicating the end to the session control unit 121 (SEQ104). Note that the session control unit 121 may determine whether the application has established a SIP session.

  The session control means 121 that has received the application state change notification message detects that the application that has established the SIP session has ended by the application state change notification message, and sends the SIP session to the first SIP-UA means 123. Release (STEPs 21 and 22 in FIG. 9). For example, the session control unit 121 identifies the identifier of the SIP session established for the application based on the software information of the application included in the application state change notification message, and adds a SIP session identifier to the SIP session termination request. The message is transmitted to the first SIP-UA means 123 (SEQ105).

  When the first SIP-UA means 123 receives the SIP session end request message, the first SIP-UA means 123 identifies the SIP session based on the SIP session identifier included in the SIP session end request message, and sends a BYE request to the SIP server 23. It transmits (SEQ106). At this time, the first SIP-UA means 123 generates a BYE request destined for the SIP-URI of the Web server 31.

  The BYE request transmitted from the first SIP-UA means 123 of the client terminal 1 is transferred by the SIP server 23 to the second SIP-UA means 32 of the Web server system 3 based on the SIP-URI (SEQ107). ).

  Receiving the BYE request, the second SIP-UA means 32 recognizes the end of the SIP session and returns an OK response (SEQ108).

  The OK response transmitted from the second SIP-UA means 32 of the Web server system 3 is transferred by the SIP server 23 to the first SIP-UA means 123 of the client terminal 1 that is the request source (SEQ109).

  When the first SIP-UA means 123 receives the OK response, the SIP session between the Web server system 3 (specifically, the Web server 31) and the client terminal 1 established by the previous INVITE request is terminated.

  The first SIP-UA means 123 that has received the OK response transmits a SIP session end response message indicating that the SIP session has ended together with the SIP session identifier to the session control means 121 (SEQ110).

  The session control unit 121 that has received the SIP session end response message clears (deletes) the stored SIP session management information stored in association with the SIP session identifier indicated in the SIP session end response message. do it.

  In the above operation example, the SIP session is released from the client terminal 1 side, but it is also possible to release the SIP session from the Web server 31 side. FIG. 10 is a sequence diagram showing the flow of each process in the SIP service system when releasing a SIP session from the Web server 31 side. FIG. 11 is a flowchart showing an example of the operation of the Web server 31.

  For example, in response to an HTTP request from the client terminal 1, the Web server 31 regards the processing until returning an HTTP response as one transaction, and terminates the SIP session used in the transaction when the transaction ends. You may let them.

  For example, when the Web server 31 receives an HTTP request on the SIP session from the application 11 of the client terminal 1 (SEQ201), the Web server 31 recognizes the start of the transaction and performs necessary transaction processing (STEPs 31 and 32 in FIG. 11). A response is returned (SEQ202).

  When the HTTP response is returned, the second SIP-UA means 32 terminates the SIP session used in the transaction, assuming that the transaction is terminated (STEPs 33 and 34 in FIG. 11). For example, after returning an HTTP response, the Web server 31 may transmit an SIP session end request message to which the transport address for accepting the HTTP request is added to the second SIP-UA means 32 (SEQ203).

  When receiving the SIP session end request message, the second SIP-UA means 32 identifies the SIP session based on the transport address included in the SIP session end request message, and transmits a BYE request to the SIP server 23. (SEQ204). At this time, the second SIP-UA means 32 generates a BYE request whose destination is the SIP-URI of the client terminal 1 found by the previous INVITE request.

  The BYE request transmitted from the second SIP-UA means 32 of the Web server system 3 is transferred by the SIP server 23 to the first SIP-UA means 123 of the client terminal 1 based on the SIP-URI (SEQ205). ).

  The first SIP-UA means 123 that has received the BYE request recognizes the end of the SIP session and returns an OK response (SEQ206).

  The OK response transmitted from the first SIP-UA means 123 of the client terminal 1 is transferred by the SIP server 23 to the second SIP-UA means 32 of the Web server system 3 that is the request source (SEQ207).

  When the second SIP-UA means 32 receives the OK response, the SIP session between the Web server system 3 (specifically, the Web server 31) and the client terminal 1 established by the previous INVITE request is completed. .

  When the first SIP-UA unit 123 of the client terminal 1 recognizes the end of the SIP session, it transmits a SIP session end notification message indicating that the SIP session is ended together with the identifier of the SIP session to the session control unit 121. (SEQ208).

  The session control unit 121 that has received the SIP session end notification message may clear (erase) the management information of the SIP session held in association with the identifier of the SIP session indicated by the SIP session end notification message. At this time, the application monitoring unit 122 may be notified of a message indicating that the application monitoring is ended. When the SIP session is terminated from the Web server 31 side or when the termination is determined based on the communication data amount without directly referring to the operation state of the application 11, the SIP service session control means 12 is connected to the client terminal 1. It can also be realized by a SIP-compatible gateway device.

  As described above, in the present embodiment, the SIP service session control means 12 that operates as a DNS resolver for the application 11 controls the SIP session in response to an inquiry request from the application 11, so the SIP session is used. When providing a Web service, the application 11 for using the Web service can be used only with the conventional DNS inquiry function without performing session control such as establishment or release of a SIP session. Therefore, it is possible to receive a Web service using an SIP session using an existing application 11 that does not support SIP.

  Further, the SIP service session control means 12 uses two registration servers: a name server 21 that is a normal DNS server and a SIP service registration server 22 that registers the URL of the service that uses the SIP session, thereby making a DNS inquiry. Since it is determined whether or not the web service provided by the URL specified in the request is a web service that uses the SIP session, and the SIP session is controlled as necessary, the web service that uses the SIP session and the SIP Both Web services that do not use sessions can be used by the same application in the same system.

  The present invention can be suitably applied to a network in which a Web service using an SIP session and a Web service not using an SIP session are mixed. The SIP service session control means 12 of the present invention can also be suitably applied as a software program installed in a communication terminal (mobile terminal or personal computer) that can be connected to such a network.

It is a block diagram which shows the structural example of a SIP service system. It is a sequence diagram which shows the flow of each process in this SIP service system at the time of establishing a SIP session. 4 is a flowchart showing an example of the operation of a session control unit 121. It is explanatory drawing which shows an example of the data structure of the corresponding relationship registered into the SIP service registration server. It is explanatory drawing which shows an example of a data structure of the protocol information which the application monitoring means 122 hold | maintains. It is explanatory drawing which shows an example of SIP-SDP described in an INVITE request. It is a sequence diagram which shows the flow of each process in this SIP service system at the time of releasing a SIP session. 5 is a flowchart showing an example of the operation of an application monitoring unit 122. 4 is a flowchart showing an example of the operation of a session control unit 121. It is a sequence diagram which shows the flow of each process in this SIP service system at the time of releasing a SIP session from the Web server 31 side. 3 is a flowchart illustrating an example of an operation of a Web server 31.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Client terminal 11 Application 12 SIP service session control means 121 Session control means 122 Application monitoring means 123 1st SIP-UA means (SIP-UA # 1)
124 SIP service determination means 125 DNS resolver means 2 Network 21 Name server 22 SIP service registration server 23 SIP server 3 Web server system 31 Web server 32 Second SIP-UA means (SIP-UA # 2)

Claims (11)

A SIP service system for implementing a Web service using a SIP session using an application that is not SIP-compatible,
In a SIP service system in which a SIP service registration server that associates and holds a URL of a Web service that uses a SIP session and a SIP-URI assigned to the Web service is disposed on a communication network.
SIP service session control means for receiving a DNS inquiry request from the application,
When the SIP service session control means receives a DNS inquiry request from an application, the SIP service session control means designates the URL specified in the DNS inquiry request to the SIP service registration server based on the result of inquiring the SIP-URI. Determining whether the service provided by the URL is a Web service using an SIP session;
When the SIP service session control means determines that the service provided by the URL is a Web service using the SIP session, the SIP service session control means sets the SIP session corresponding to the SIP-URI corresponding to the URL obtained as a result of the inquiry. An SIP service system characterized in that a destination IP address obtained as a result of the establishment is returned to the application as a DNS inquiry response. A SIP service system for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that does not support SIP,
In a SIP service system in which a SIP service registration server that associates and holds a URL of a Web service that uses a SIP session and a SIP-URI assigned to the Web service is disposed on a communication network.
SIP service session control means for receiving a DNS inquiry request from the application,
When the SIP service session control means receives a DNS inquiry request from an application, the SIP service session control means designates the URL specified in the DNS inquiry request to the SIP service registration server based on the result of inquiring the SIP-URI. Determining whether the service provided by the URL is a Web service using an SIP session;
When the SIP service session control means determines that the service provided by the URL is a Web service using the SIP session, the SIP service session control means sets the SIP session corresponding to the SIP-URI corresponding to the URL obtained as a result of the inquiry. An SIP service system characterized in that a destination IP address obtained as a result of the establishment is returned to the application as a DNS inquiry response. When the SIP service session control means determines that the service provided by the URL specified in the DNS inquiry request is not a Web service using the SIP session, the SIP service session control means uses the URL specified in the DNS inquiry request to the DNS server. The SIP service system according to claim 1 or 2, wherein an IP address corresponding to the domain name obtained as a result of inquiring an IP address by specifying a specified domain name is returned to the application as a DNS inquiry response. When the SIP service session control means inquires of the DNS server about the IP address by specifying the domain name specified by the URL specified in the DNS inquiry request, the IP address corresponding to the domain name cannot be obtained. The SIP service system according to claim 1 or 2, wherein the SIP service registration server is inquired of the SIP-URI by designating the URL designated in the DNS inquiry request. SIP service session control means
A control unit for receiving a DNS inquiry request from an application;
DNS resolver means for inquiring an IP address by specifying a domain name specified by the URL with respect to a DNS server specified by the control unit;
SIP-URI resolver means for instructing the SIP service registration server to inquire about the SIP-URI for the URL specified by the control unit;
The SIP service system according to any one of claims 1 to 4, further comprising SIP user agent means for performing client control by SIP with a SIP-URI designated by the control unit as a destination. A SIP service session control apparatus for implementing a Web service that uses a SIP session using an application that is not compatible with SIP,
SIP service session control means for receiving a DNS inquiry request from the application,
When the SIP service session control means receives a DNS inquiry request from an application, the SIP service session control means associates and holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service. Based on the result of inquiring SIP-URI by specifying the URL specified in the DNS inquiry request to the registration server, it is determined whether the service provided by the URL is a Web service using a SIP session. ,
When it is determined that the service provided by the URL is a Web service using a SIP session, the SIP service session control means uses a SIP-URI corresponding to the URL obtained as a result of the inquiry as a destination of the SIP session. An SIP service session control apparatus characterized in that a destination IP address obtained as a result is returned to the application as a DNS inquiry response. A SIP service session control device for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that does not support SIP,
SIP service session control means for receiving a DNS inquiry request from the application,
When the SIP service session control means receives a DNS inquiry request from an application, the SIP service session control means associates and holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service. Based on the result of inquiring SIP-URI by specifying the URL specified in the DNS inquiry request to the registration server, it is determined whether the service provided by the URL is a Web service using a SIP session. ,
When it is determined that the service provided by the URL is a Web service using a SIP session, the SIP service session control means uses a SIP-URI corresponding to the URL obtained as a result of the inquiry as a destination of the SIP session. An SIP service session control apparatus characterized in that a destination IP address obtained as a result is returned to the application as a DNS inquiry response. A SIP session control method for implementing a Web service using a SIP session using an application that is not SIP-compatible,
When the SIP service session control means for accepting a DNS inquiry request from the application accepts a DNS inquiry request, it corresponds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service. Then, based on the result of inquiring the SIP-URI by specifying the URL specified in the DNS inquiry request to the SIP service registration server to be held, the service provided by the URL uses the SIP session. Whether or not
When the SIP service session control means determines that the service provided by the URL is a Web service using an SIP session, the SIP session corresponding to the URL obtained as a result of the inquiry is used as the SIP session. And a destination IP address obtained as a result is returned to the application as a DNS inquiry response. A SIP session control method for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that does not support SIP,
When the SIP service session control means for accepting a DNS inquiry request from the application accepts a DNS inquiry request, it corresponds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service. Then, based on the result of inquiring the SIP-URI by specifying the URL specified in the DNS inquiry request to the SIP service registration server to be held, the service provided by the URL uses the SIP session. Whether or not
When the SIP service session control means determines that the service provided by the URL is a Web service using an SIP session, the SIP session corresponding to the URL obtained as a result of the inquiry is used as the SIP session. And a destination IP address obtained as a result is returned to the application as a DNS inquiry response. A SIP session control program for implementing a Web service that uses a SIP session using an application that is not compatible with SIP,
On the computer,
When a DNS inquiry request is received from an application, the DNS inquiry is sent to the SIP service registration server that holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service in association with each other. A process for determining whether the service provided by the URL is a Web service using an SIP session based on the result of inquiring the SIP-URI by specifying the URL specified in the request, and provided by the URL When the service is determined to be a Web service using a SIP session, a SIP session is established with the SIP-URI corresponding to the URL obtained as a result of the inquiry as a partner, and the partner IP address obtained as a result is As a DNS inquiry response SIP session control program for executing processing to send back to the application. A SIP session control program for implementing a Web service that does not use a SIP session and a Web service that uses a SIP session, using an application that does not support SIP,
On the computer,
When a DNS inquiry request is received from an application, the DNS inquiry is sent to the SIP service registration server that holds the URL of the Web service that uses the SIP session and the SIP-URI assigned to the Web service in association with each other. A process for determining whether the service provided by the URL is a Web service using an SIP session based on the result of inquiring the SIP-URI by specifying the URL specified in the request, and provided by the URL When the service is determined to be a Web service using a SIP session, a SIP session is established with the SIP-URI corresponding to the URL obtained as a result of the inquiry as a partner, and the partner IP address obtained as a result is As a DNS inquiry response SIP session control program for executing processing to send back to the application.

Images