JP4333325B2 - Service system and service providing method - Google Patents

Description

  The present invention relates to a service system and a service providing method, and the service system of the present invention particularly relates to an application for mutually integrating a SIP environment and a Web (World Wide Web) environment that operate based on a session initiation protocol (SIP). The present invention relates to a system that provides services to connected clients in cooperation. In addition, the service provision method relates to a method of providing a service by linking applications operating in different environments, for example, an alert type that notifies the progress status and termination of a started service from a web browser, for example. It relates to the realization of application (AP).

  Conventionally, the application software (AP) environment based on the Session Initiation Protocol (SIP) and the web, that is, the application software (AP) environment based on the World Wide Web, are constructed as separate AP environments, and APs that meet the requirements are It was running to meet the demands. Thus, the fusion of the two environments described above is not achieved. This is used in the construction of information-providing AP services provided by corporate information systems and international standardized profiles (ISPs) in the conventional Web-AP environment, while the SIP-AP environment is a telephone service. This is due to the use of different applications.

  Further, when linking / connecting server environments realized by such different communication protocols, a method of mediating a protocol conversion gateway is generally employed. This gateway performs HTTP-SIP conversion using an HTTP (Hyper Text Transfer Protocol) protocol, which is a Web environment protocol, and a SIP environment protocol having a SIP interconnection conversion function.

RFC3261 <http://www.ietf.org/rfc/rfc3261.txt> <Http://jcp.org/aboutJava/communityprocess/final/jsr116/index.html>

  However, an HTTP-SIP gateway having an HTTP-SIP conversion function only realizes a simple function according to a protocol conversion rule incorporated in advance in the gateway. For example, the HTTP-SIP gateway cannot change the presence on the database in the SIP environment according to the processing status of one HTTP protocol based on the request contents by one HTTP protocol, and cannot notify the user in the SIP environment. . When notifying the user of the progress of processing in the HTTP environment, the HTTP-SIP gateway holds the HTTP transaction for a long time. This is not an appropriate realization method from the viewpoint of effective use of resources and realization of a user interface as a practical application.

  It is an object of the present invention to provide a service system and a service providing method capable of solving such disadvantages of the prior art, operating by integrating different systems, and notifying each other of AP processing progress status and the like.

  In order to solve the above-described problems, the present invention provides a service system in which information is communicated with each of clients connected to a system constructed in an environment of different communication protocols, and this information is provided as a service. , A first system that operates based on the first communication protocol, and a second system that operates based on the second communication protocol, the first system sending information to be sent to the second system The third communication protocol treated as information to be commonly linked in the first communication protocol and the second communication protocol is processed, and the information by the third communication protocol supplied from the second system is converted into the first communication protocol. The first linkage management means for making information and the requested service instance as a client of the first system The second system includes a first proxy management unit that virtually manages the user agent as a user agent and manipulates the information to be managed. The second system transmits information to be sent to the first system to the third communication protocol. And the second cooperation management means for converting the information according to the third communication protocol supplied from the first system into information of the second communication protocol, and the requested service instance from the second system. And a second proxy management unit that accesses a corresponding function of the first proxy management unit by a virtual user agent and acquires an execution result of the service instance.

  In the service system of the present invention, when a service instance requested by a client connected to the second system is executed, the second proxy management means for this request functions as a proxy user agent (UA) using the second communication protocol. Then, the second cooperation management means is activated, the second cooperation management means makes this request as a request for the third communication protocol, sends it to the first cooperation management means, and the first cooperation management means first The request is processed by the corresponding proxy UA function of the first proxy management means, and the response of the processing result is returned to the first proxy management means, the first linkage management means, and the second linkage. A proxy UA corresponding to a service instance between different communication protocols by sending it to the requesting client via the management means and the second proxy management means and displaying it. It performs management in each system, to provide a service that could not be far.

  Further, in order to solve the above-mentioned problems, the present invention provides a service providing method for communicating information with each of clients connected to a system constructed by an environment of different communication protocols and providing this information as a service. In the method, the information transmitted from the first system in the communication between the first system that operates according to the first communication protocol and the second system that operates according to the second communication protocol is transmitted. A first step of processing and sending to a third communication protocol treated as information to be linked in common in the first communication protocol and the second communication protocol, and a third communication protocol supplied to the second system A second step of processing the information into information of the second communication protocol and sending it, and information of the second communication protocol sent from the second system A third step of processing and sending information to the third communication protocol and a third communication protocol information supplied to the first system to information of the first communication protocol and sending it A fourth step, and virtually as a user agent in the manner of a client in a communication destination system corresponding to a service instance requested from a client connected to one of the first and second systems A fifth step of generating a first activation signal including information corresponding to a service instance in accordance with a proxy access function for accessing a proxy user agent to be managed, and a combination of the first and second steps or A sixth step of sequentially executing one of the third and fourth step sets in response to the first activation signal; and a communication destination system A seventh step of performing information processing corresponding to the service instance by the proxy user agent, an eighth step of generating by the proxy user agent a second activation signal including response information for the information processing, And a tenth step of returning the response information to the requesting client by the proxy access function in the communication source system that requested the service instance. It is characterized by that.

  In the service providing method of the present invention, when a service instance requested by a client connected to the second system is executed, the first access is performed by the proxy user agent (UA) proxy access function for the request using the second communication protocol. Generate an activation signal, make this request a request for the third communication protocol, perform communication between systems, and perform information processing in the first system with the proxy UA function corresponding to the request made in the first communication protocol The second activation signal including the response information of the processing result is generated by the proxy UA, the response information is set to the third communication protocol, the communication is performed between the systems, and the response information is requested by the proxy access function. By sending them to and displaying them, proxy UA processing corresponding to service instances between different types of communication protocols can be performed for each system. It carried out in the absence, to provide a service that could not be far.

  Next, an embodiment of a service system according to the present invention will be described in detail with reference to the accompanying drawings. Referring to FIG. 1, the embodiment of the service system according to the present invention solves the problem of execution of an accurate notification of the processing status of an application, which is a problem in a linkage system such as a conventional HTTP-SIP conversion gateway. The client can know the processing status of the application in either the SIP environment or the Web environment by using the configuration and method that enables flexible cooperation between the SIP application and the Web application.

  In this embodiment, the service system of the present invention is applied to the service providing system 10. The illustration and description of parts not directly related to the present invention are omitted. In the following description, the signal is indicated by the reference number of the connecting line in which it appears.

  As shown in FIG. 1, the service providing system 10 includes a SIP system 12 and a Web system 14 connected via a network 16. The SIP system 12 and the Web system 14 are arranged on network environments belonging to different network domains, and have functional blocks that complement the Web environment and the SIP environment that the SIP system 12 and the Web system 14 originally do not have. It is As a result, the SIP system 12 and the Web system 14 of the service providing system 10 each have one environment corresponding to a system arranged in a LAN environment in one server computer or in the same domain.

  The network 16 is a SOAP (Simple Object Access Protocol) / CORBA (Common Object Request Broker Architecture) network in this embodiment, and plays a role of mediating information between the SIP system 12 and the Web system 14. SOAP is a communication protocol that specifies the data format and message processing rules for messages exchanged between Web services. In the network 16, a SOAP request according to this rule is exchanged between a service requester, a service provider, and a service broker. CORBA is a distributed object technology developed by OMG (Object Management Group).

  The SIP system 12 includes a SIP server 18, a SIP database (SIP-DB) 20, a SIP application server (SIP-AP server) 22, a SIP application interface (SIP-API) 24, a SIP application (SIP-AP) 26, and a Web accessor. Includes component 28 and SIP client 30. The Web system 14 includes a Web server 32, a Web database (Web-DB) 34, a Web application server (Web-AP server) 36, a Web application interface (Web-API) 38, a Web application (Web-AP) 40, Includes a SIP accessor component 42 and a web client 44. Hereinafter, each of these components will be briefly described.

  The SIP server 18 is a server that responds to a client request based on SIP, which is a client-server model protocol that communicates end-to-end, and is specified in particular by the IETF (International Engineering Task Force). For example, it has a function of handling and managing SIP compliant with RFC (Request For Comments) 3261. Of these management functions, the SIP server 18 generally includes three server functions, namely, a SIP proxy server function, a SIP registrar server function, and a SIP location server function. First, the SIP proxy server function is a function of relaying a SIP message as a proxy for a client. Second, the SIP registrar server function is a function for managing client registration. Third, the SIP location server function has a function of managing registered client address information and the like. The SIP server 18 is connected to, for example, SIP softphones 46 and 48 that are constituent elements of the SIP client 30, and exchanges information provided from the SIP-AP server 22 using SIP messages.

  The SIP-DB 20 is a storage managed by the SIP server 18, for example, storing user information, presence information, location information, etc. in association with each other. The SIP-DB 20 is connected to the SIP server 18 and receives information in response to a search request from the SIP server 18. Some have the function of providing In the SIP-DB 20, the user information is client address information and information for authentication. Presence information is information such as whether the client is connected to the SIP system 12, whether the client is activated and used, and whether it is connected to another client. As can be seen from the information, the SIP-DB 20 stores information representing the state of the client.

  The SIP-AP server 22 is a server that operates an application managed by the SIP server 18 according to an operation based on the SIP protocol. The SIP-AP server 22 is connected to the SIP server 18 and the SIP-API 24, respectively. The SIP-API 24 has a function of operating an application in response to a SIP request received by the SIP server 18 and a function of issuing a request to the SIP server 18. SIP requests include session establishment, confirmation response, call termination and presence change.

  The SIP-API 24 is an application interface provided by the SIP-AP server 22. The SIP-AP server 22 is connected to the SIP-AP 26 via the SIP-API 24. A typical SIP-API 24 is a SIP Servlet application interface that is being standardized in JCP (Java (registered trademark) Community Process).

  The SIP-AP 26 is an application that is constructed by the SIP-API 24 to be connected and operates on the SIP-AP server 22. The SIP-AP 26 includes a user agent (UA) generation application (not shown). A UA generation application is a function of an UA, that is, an end system such as application software, which operates as a UA client when generating a SIP request and operates as a UAS (UA Server) when generating a response after processing a request. It has a function. Applications include, for example, IP phone, instant messaging, TV (TeleVision) phone, presence communication, and the like.

  The web accessor component 28 is a generic name for a component group in which the SIP-AP 26 cooperates with the web system 14, and each component represents a library software component. Therefore, the Web accessor component 28 is called when the SIP-AP 26 operates, and is used when communicating with the SIP accessor component 42 described later of the Web system 14. The Web accessor component 28 includes, for example, a proxy UA management unit 50, a linkage management unit 52, and a component application interface (component API) 54 as shown in FIG.

More specifically, the proxy UA management unit 50 is a component that operates and manages service proxy UA information within the SIP system 12. In particular, the service instance is virtually managed as a UA by regarding the service instance as a SIP client, and the information etc. It is a component that manages operations. As shown in FIG. 2, the proxy UA management unit 50 includes various functional units that manage UAs corresponding to service instances. That is, the proxy UA generation function unit 56, the proxy UA registration function unit 58, the proxy UA deletion function unit 60, the presence setting function unit 62, the message transmission function unit 64, the proxy UA information editing function unit 66, and the proxy UA information search function unit 68 include.

  The proxy UA generation function unit 56 is a module that generates a UA corresponding to a service instance. The proxy UA registration function unit 58 is a module for registering a UA corresponding to a service instance. The proxy UA deletion function unit 60 is a module that deletes a UA corresponding to a service instance. The presence setting function unit 62 is a module for changing the presence information of the UA corresponding to the service instance. The message transmission function unit 64 is a module that transmits a message, that is, a text string, from a UA corresponding to a service instance to a specified UA. The proxy UA information editing function unit 66 is a module for editing UA user information corresponding to a service instance. The proxy UA information search function unit 68 is a module that searches for user information of the UA corresponding to the service instance.

  The linkage management unit 52 has a function of managing a communication environment for accessing the proxy UA management unit 50 from the Web system 14 side or accessing the Web system 14 side in cooperation with the corresponding linkage management unit 70 in the Web system 14. Have. The linked management environment includes, for example, an environment setting corresponding to a SOAP or CORBA protocol.

  The component API 54 is an interface for the SIP-AP 26 to use the corresponding component.

  The Web accessor component 28 is not limited to the components described above, and is used in combination from the SIP-AP 26 side depending on what functions are specifically realized as the SIP-AP 26. In addition to components, it can be expanded as needed depending on the application. It goes without saying that the addition / extension of this component will also add / extend the variations of linkage with the Web system 14.

  Next, returning to FIG. 1, the Web system 14 will be described. The Web server 32 is a server that handles and manages based on HTTP. The web server 32 is connected to web browsers 72 and 74 that are components of the web client 44. The Web server 32 is connected to the Web-DB 34 and the Web-AP server 36 to manage them.

  The Web-DB 34 is a storage for storing information managed by the Web server 32, and some of them have a function of providing information in response to a search request from the Web server 32. The management information to be stored includes client billing information and usage logs. The Web-DB 34 is connected not only to the Web server 32 but also to the Web-AP server 36 so as to provide data.

  The Web-AP server 36 is a server that is always in an activated state and that operates an application managed by the Web server 32 based on HTTP, which is a Web protocol, in response to an operation. Examples of the Web-AP server 36 include open source TOMCAT and BEA (trademark) WebLogic (trademark). The Web-AP server 36 is connected to the Web-AP 40 via the Web-API 38. The Web-AP server 36 may operate the application based on the information in the Web-DB 34.

  The Web-API 38 is an application interface provided by the Web-AP server 36. Web-API 38 includes HTTP Servlet API and EJB (Enterprise Java (trademark) Beans) defined in the J2EE (Java2 Enterprise Edition) environment as typical APIs. The Web-API 38 enables information exchange between the Web-AP server 36 and the Web-AP 40.

  The Web-AP 40 is a Web application that is constructed by the connected Web-API 38 and runs on the Web-AP server 36, and is also connected to the SIP accessor component 42. Web-AP 40 includes, for example, APs such as Internet shopping malls, corporate portals, and content distribution. In addition, the Web-AP 40 may include a matching AP and a DB search AP (not shown), for example. The matching AP collates the UA registration information related to the location information with the update location information, the update time information expressed in time or season, and past information, etc., as the UA location information changes. This is an application that sends messages to UA. The DB search AP is an application that extracts from the Web-DB 34 UA registration information, update position information, update time information, past information, and the like related to position information.

  The SIP accessor component 42 is a generic name for a group of components in which the Web-AP 40 cooperates with the SIP system 12, and is library software called when the Web-AP 40 operates. For example, the following components and APIs exist: The SIP accessor component 42 is used when the Web-AP 40 communicates with the Web accessor component 28 on the SIP system 12. Also in this case, as with the Web accessor component 28, the Web-AP 40 can be used in combination from the Web-AP 40 side depending on what functions are implemented in cooperation with the SIP-AP 26. The SIP accessor component 42 can be expanded at any time according to the use, and the addition / expansion of this component also adds / expands variations of cooperation with the SIP system 12.

  The SIP accessor component 42 includes, for example, a proxy UA management unit 76, a cooperation management unit 70, and a component API 78, as shown in FIG. The proxy UA management unit 76 is a component in the Web system 14 that accesses service proxy UA information managed in the SIP system 12. Thereby, the service providing system 10 accesses the SIP system 12 side from the Web system 14 side, and provides the service proxy UA information read from the SIP system to the Web system 14 to the Web browser. As shown in FIG. 2, the proxy UA management unit 76 includes a proxy UA generation access function unit 80, a proxy UA registration access function unit 82, a proxy UA deletion access function unit 84, a presence setting access function unit 86, and a message transmission access function unit. 88, a proxy UA information editing access function unit 90 and a proxy UA information search access function unit 92 are included as modules.

  The proxy UA generation access function unit 80 is a module for accessing the proxy UA generation function unit 56 on the SIP system 12 side from within the Web system 14. The proxy UA registration access function unit 82 is also a module for accessing the proxy UA registration function unit 58 on the SIP system 12 side from within the Web system 14. Similarly, the proxy UA deletion access function unit 84 is a module that accesses the proxy UA deletion function unit 60 on the SIP system 12 side from within the Web system 14.

  The presence setting access function unit 86 is a module for accessing the change of the presence status of the service from within the function unit 86 and changing the presence of the proxy UA through the presence setting function unit 62 on the SIP system 12 side. The presence change result is notified to the presence information watcher via the SIP server 18. The message transmission access function unit 88 is a module for accessing a change in the service progress status from within the function unit 88 and creating / transmitting a proxy UA message through the message transmission function unit 64 on the SIP system side. The message is notified to the receiving side via the SIP server 18.

  The proxy UA information editing access function unit 90 is a module for accessing the proxy UA information editing function unit 66 on the SIP system 12 side from within the Web system 14. Further, the proxy UA information search access function unit 92 is a module for accessing the proxy UA information search function unit 68 on the SIP system 12 side from within the Web system 14.

  The linkage management unit 70 cooperates with the corresponding linkage management unit 52 in the SIP system 12 and uses the proxy UA management unit 76 to access the SIP system 12 side or from the SIP system 12 side to the Web system 14 side. It has a management function of the communication environment for access. The linkage management environment includes, for example, environment settings corresponding to SOAP and CORBA protocols.

  For example, when the search function of proxy UA management in the SIP system 12 is used from the Web system 14 side, communication between the link management unit 52 and the link management unit 70 is performed in order to access the function of the search access function unit 92 from a remote environment. A search stub for UA information is called and communication is performed via the cooperation management unit 52. The stub to be called at this time differs depending on what is used in the network 16 used for realizing remote access. In this embodiment, a CORBA stub is used when using CORBA for linkage, and a SOAP access stub is used when using SOAP.

  The component API 78 is an interface for the Web-AP 40 to use the corresponding component.

  In this way, the linkage between systems is managed, and based on the functions of proxy UA management corresponding to service instances, for example, registered information is extracted, and information obtained regardless of different systems is requested. It is possible to build an application to be provided to a client who has a problem. In other words, APs built on the Web environment and APs built on the SIP environment can be linked to each other, and the construction, execution, and operation of a Web-VoIP integrated AP can be easily realized. With this construction, information on each system can be shared and used smoothly.

  Next, the communication procedure of the service providing system 10 will be described. The operation of service proxy UA generation using proxy UA management units 52 and 72 will be described with reference to FIG.

  For example, the web browser 72 issues an execution request for “service generation” at time T10 (service generation request signal: Gen._REQ. 100). Here, the request information includes user information as well as request information such as search information and message information to be transmitted. This user information includes information related to contracts such as the user's name, address, age, and address information, and information used for authentication when using the system. Generally, this request is made using a GUI (Graphical User Interface) provided by the Web server 32 displayed on the Web browser 72. The service generation request signal is sent to the Web server 32 / Web-AP server 36.

  The Web server 32 / Web-AP server 36 uses the component API 78 in the proxy UA management unit 76 on the Web side based on the supplied “service generation request”, and starts a launch signal (Launching) 102 at time T12. Is supplied to the proxy UA generation access function unit 80, and the proxy UA generation access function unit 80 is activated. The proxy UA generation access function unit 80 is activated by supplying a startup signal (Launching) 104 to the cooperation management unit 70 at time T14.

  In order to transmit information to the proxy UA management unit 52 of the SIP system 12, the linkage management unit 70 converts the “service generation request” data so as to conform to a commonly used communication protocol, such as SOAP or CORBA. 16 communicates with the cooperation management unit 52 on the SIP system 12 side existing in another domain. The cooperation management unit 70 communicates with the cooperation management unit 52 at time T16, and transmits a “service generation request” issued by the Web browser 72 (Gen._REQ. 106).

  The cooperation management unit 52 supplies the activation signal (Launching) 108 including “service generation request” to the proxy UA generation function unit 56 of the proxy UA management unit 50 at time T18 to start the proxy UA generation function unit 56. As a result, a proxy UA is generated. The proxy UA generation function unit 56 activates the proxy UA registration function unit 58 (not shown). The proxy UA registration function unit 58 registers the service proxy UA information in the SIP-DB 20 managed by the SIP-AP server 22 or the SIP server 18 at time T20 (Registration 110). This registration enables the Web browser 72 to authenticate use of the system.

  After this registration, the proxy UA management unit 50 activates the proxy UA information search function unit 68 when search information is included in the information included in the “service generation request” (not shown). The proxy UA information search function unit 68 instructs the SIP-DB 20 to search for the search information (Search 112). The SIP-DB 20 performs a search process corresponding to the supplied search information. The SIP-DB 20 transmits the search result as a response signal (Response) 114 to the proxy UA information search function unit 68 of the proxy UA management unit 50 at time T24. The search result is URI (Uniform Resource Identifiers) information generated by SIP.

  The proxy UA information search function unit 68 receives the search result, and the proxy UA management unit 50 generates a launch signal (Launching) 116 including the search result (generated SIP-URI information) at time T26, and the cooperation management unit Output to 52. The cooperation management unit 52 is activated by the activation signal 116, and returns a search result (generated SIP-URI information) to the proxy UA management unit 70. For this reason, the cooperation management unit 50 communicates with the cooperation management unit 70 by selecting and using one of SOAP, CORBA, and the like. When the cooperation management unit 52 uses, for example, SOAP, search information supplied based on the HTTP protocol is sent to the cooperation management unit 70 via the network 16 as a response signal (Response) 118 that is a SOAP response at time T28. Is output. The cooperation management unit 70 receives the supplied search information, and transmits the result of “service generation request” to the proxy UA management unit 76 at time T30 (Response 120).

  Next, the proxy UA management unit 76 receives the received “service generation request” result, and returns it to the Web server 32 or the Web-AP server 36 as the execution result of the component API 54 at time T32 (Response 122). The execution result is user information data obtained by the above-described search on the SIP-DB.

  The Web server 32 or the Web-AP server 36 processes the supplied user information search result, that is, the generated SIP-URI information into a format that can be displayed by the Web client. In this case, the data is in SIP-URI format. The Web server 32 or the Web-AP server 36 outputs the service SIP-URI 124 to the Web browser 72 at time T34. The web browser 72 displays the result of “service generation request” on the monitor at time T36.

  By operating in this way, it is possible to easily provide the generated SIP-URI information of the SIP system 12 to the client that has requested the service generation request from the Web browser or the Web client.

  The operation of presence setting in the service providing system 10 will be described with reference to FIG. The components used are exactly the same, and the same reference numerals are used for the components.

  The Web browser 72 issues an execution request for “service presence setting” to the Web server 32 / Web-AP server 36 at time T40. This execution request specifies a SIP-URI and includes user information. As described above, the user information is information related to a contract such as a user's name, address, age, and address information, and information for performing authentication when using the system. The information on the service presence setting request includes, for example, “waiting for execution”, “processing in progress”, “finished”, etc. as contents representing the service status. The execution request is generally performed using a GUI provided by the Web server 32 displayed on the Web browser 72.

  The Web server 32 / Web-AP server 36 supplies the activation signal (Launching) 132 generated based on the “service presence setting request” (Set_REQ) 130 to the proxy UA management unit 76 at time T42. The proxy UA management unit 76 activates the presence setting access function unit 86 using the component API 78 based on the “service presence setting request” (Set_REQ) 130 included in the activation signal 132. As a result, the presence setting access function unit 86 supplies the activation signal (Launching) 134 to the cooperation management unit 70 at time T44 to activate.

  The cooperation management unit 70 communicates with the cooperation management unit 52 existing in another domain on the network 16 at time T46 using either SOAP or CORBA to transmit information to the proxy UA management unit 50. Through this communication, the cooperation management unit 52 receives a “service presence setting request” (Set_REQ.) 136 issued by the Web browser 72.

  The cooperation management unit 52 supplies the generated launch signal (Launching) 138 to the proxy UA management unit 50 at time T48 to activate the presence setting function unit 62. By this activation, the presence setting function unit 62 sets presence.

  The presence setting function unit 62 changes the proxy UA presence information stored in the SIP-DB 20 managed by the SIP-AP server 22 / SIP server 18 at time T50 (Changing 140). After this change, the proxy UA information search function unit 68 is activated and searches the SIP-DB 20 at time T52 (Search 142). The SIP-DB 20 outputs the search result of the proxy UA presence information to the proxy UA information search function unit 68 at time T54 (Response 144). The proxy UA information search function unit 68 supplies the search result of the supplied proxy UA presence information to the presence setting function unit 62.

  By the way, the presence setting function unit 62 notifies the SIP softphone 46 of the change of the presence information registered in the SIP-DB 20, for example. This change notification is executed by the number of watchers asynchronously with the search processing sequence performed after time T54 (Notify 146).

  The proxy UA embedding unit 50 supplies the activation signal (Launching) 148 including the search result to the linkage management unit 52 at time T56, and activates it. The cooperation management unit 52 communicates with the cooperation management unit 70 at time T58 using either SOAP or CORBA (Response 150). The cooperation management unit 70 supplies a response signal 152 to the proxy UA management unit 76 at time T60. The response signal 152 includes a result of “presence setting request”. When the normal setting is successful, the set presence content is transmitted as a result such as “waiting for execution”. If the setting fails, the response signal 152 is transmitted as a result of NG (No Good). The presence setting access function unit 86 of the proxy UA management unit 76 receives the response signal 152 as a result of the “service presence setting request”.

  The proxy UA management unit 76 supplies the Web server 32 / Web-AP server 36 as the execution result of the component API 78 at time T62 (Response 154). This execution result indicates user information data obtained by a search in the SIP-DB 20. The Web server 32 / Web-AP server 36 has a format in which the execution result can be displayed. Examples of the format include a SIP-URI format. The Web server 32 / Web-AP server 36 supplies and displays the result of the “service presence setting request”, that is, the service presence 156, to the Web browser 72 requested at time T64.

  By operating in this way, in response to the presence setting request from the Web browser or Web client, it is set in the SIP-DB 20 of the SIP system 12, and the setting status in the SIP-DB 20 is sent to the client that has requested it as a response signal. Can be provided easily.

  Further, the message transmission operation in the service providing system 10 will be briefly described with reference to FIG. The components used are exactly the same, and the same reference numerals are used for the components.

The Web browser 72 issues a “message transmission” execution request (Send_REQ.) 160 to the Web server 32 / Web-AP server 36 at time T70. The user information and GUI handled here are the same as those described above. The Web server 32 / Web-AP server 36 generates a launch signal 162 based on the received “message transmission request” (Send_REQ.) 160, and outputs it at time T72. The activation signal 162 activates the message transmission access function unit 88 using the component API 78.

  The message transmission access function unit 88 activates the cooperation management unit 70 at time T74 (Launching 164). The cooperation embedding unit 70 communicates with the cooperation management unit 52 existing in another domain on the network 16 at time T76 using one of SOAP, CORBA, and the like. The cooperation manager 52 receives the “message transmission request” (Send_REQ.) 166. The cooperation management unit 52 activates the message transmission function unit 64 at time T78 (Launching 168).

The message transmission function unit 64 sends a message 170 to the SIP soft phone 46, which is a SIP client, at time T80 and displays it on the monitor. The SIP client corresponds to the message recipient. The message transmission function unit 64 receives a message response from the SIP softphone 46 (not shown). The message transmission function unit 64 supplies (Launching) 172 including the response content to the cooperation management unit 50 at time T82 and starts it.

The link embedding unit 52 communicates with the link management unit 70 at time T82 using one of SOAP, CORBA, and the like to send a response of the transmission result (Response 174). The cooperation management unit 70 receives the result of the “message transmission request” issued by the Web browser 72. The cooperation management unit 70 transmits the message to the message transmission access function unit 88 of the proxy UA management unit 76 at time T86 (Response 176).

  The message transmission access function unit 88 receives the supplied “message transmission request” result, and outputs it to the Web server 32 / Web-AP server 36 as the execution result of the component API 78 at time T88 (Response 178). The Web server 32 / Web-AP server 36 processes the result of the message transmission request into a format that can be displayed. For example, there is a SIP-URI format. The Web server 32 / Web-AP server 36 supplies a response signal (Response 180) to the Web browser 72 at time T90. The web browser 72 displays the result of “message transmission request” on the monitor.

  By operating in this way, the proxy UA management units 50 and 76 and the linkage management units 54 and 70 are used to track a service on the Web and configure a message in the service providing system 10 from one system to the other system. And a notification result can be supplied to the transmission source. In addition, since HTTP transactions are not suspended for a long time, effective use of resources and realization of a user interface as a practical application can be easily performed.

  Next, a first modification of the service providing system 10 to which the present invention is applied will be described with reference to FIG. The service providing system 10 according to the present embodiment is a case where the SIP system 12 and the Web system are arranged on one computer. Here, with respect to the constituent elements, the same reference numerals are given to the portions common to the previous embodiment, and the description thereof is omitted. As shown in FIG. 6, the service providing system 10 is connected by process cooperation on the same computer. As is apparent from this connection, the service providing system 10 of this embodiment does not go through a network connection. Further, the linkage management units 52 and 70 shown in FIG. 1 are not intentionally arranged as components, but function call function units that perform linkage management in the same manner as the web accessor component 28 and the SIP accessor component 42, respectively. Connect different systems with 182. For example, the function call function unit 182 may include a program using a function call of C language or C ++ language or a method call of Java (trademark) language. The operation procedure is the same as in the previous embodiment.

  Even with this configuration, it is possible to mutually link an AP built on the Web environment and an AP built on the SIP environment as in the previous embodiment. As a result, the construction, execution, and operation of a Web-VoIP integrated AP can be easily realized. Further, in this embodiment, by building a system on a single computer environment, it is possible to realize integration of Web-AP and VoIP-AP in a small computer environment.

  Next, a second modification of the service providing system 10 to which the present invention is applied will be described with reference to FIG. In the service providing system 10 of this embodiment, a SIP system 12 and an FTP (File Transfer Protocol) system 190 are connected by a network 16. Here, the SIP system 12 and the FTP system 180 are arranged on network environments belonging to different network domains. Further, the SIP system 12 and the FTP system 190 are arranged in a LAN environment in one server computer or in the same domain as in the first embodiment.

  The SIP system 12 uses the same configuration as that of the first embodiment, is given the same reference numerals, and a description thereof is omitted. However, in this embodiment, the function of the accessor component in the SIP system 12 is exactly the same as that of the Web accessor component 28. However, since it is not Web-compatible and is FTP, the name is FTP accessor component 29.

  The other system, FTP system 190, includes FTP server 192, FTP database (FTP-DB) 194, FTP application server (FTP-AP server) 196, FTP application interface (FTP-API) 198, FTP application (FTP- AP) 200, SIP accessor component 202 and FTP client 204. Below, each component is demonstrated easily.

  The FTP server 192 is a server that handles and manages FTP. The FTP-DB 194 is a storage that stores information managed by the FTP server 192, and is a database. The information to be stored is file information transferred by FTP. The FTP-AP server 196 is a server that operates an AP that operates a file transfer protocol (FTP) managed by the FTP server 192. FTP-API 198 is an AP interface provided by FTP-AP server 196. The FTP-AP 200 is an FTP-AP that is constructed by the FTP-API 198 and operates on the FTP-AP server 196. APs include, for example, APs such as peer-to-peer file exchange and file sharing between two parties.

  The SIP accessor component 202 is a general term for a component group (software component) in which the FTP-AP 200 cooperates with the SIP system 12. The SIP accessor component 202 is the same as the SIP accessor component 42 of the Web system 14 described above. In other words, the proxy UA management unit 76, the cooperation management unit 70, and the component API 78 are included. The function of each component is the same as in the first embodiment described above.

  The FTP client 204 is a client connected to the FTP server 192 and set in an environment that uses the function provided by the FTP-AP 200. The FTP client 204 may have a plurality of FTP client terminals 206 and 208. The FTP client 204 generally has a text display screen.

  With this configuration, it is possible to construct an application that provides the obtained information to a requested client regardless of different systems. That is, the AP constructed on the FTP system 190 and the AP constructed on the SIP system 12 can be linked to each other, and construction, execution, and operation of a combined FTP and VoIP AP are easily realized. With this construction, information on each system can be shared and used smoothly. Further, by adding various components on the FTP accessor component 29 and the SIP accessor component 202, it is possible to expand the fusion type of FTP and VoIP. Along with the types of SIP-AP and FTP-AP to be implemented, various types of integrated APs of FTP and VoIP can be realized by increasing the number of components.

  Next, a message transmission operation using the service providing system 10 of the second modification will be briefly described with reference to FIG. In this embodiment, file contents are handled as SIP message information, and file update information by file transfer is realized as SIP message transmission processing.

  As an operation procedure, first, the FTP client 194 issues a “file transfer request” request to the FTP server 192 / FTP-AP server 196 at time T100 through a text display screen (FT_REQ. 210). The FTP server 192 / FTP-AP server 196 executes file transfer based on the received “file transfer request”. After this execution, the FTP server 192 / FTP-AP server 196 reads the SIP-URI of the destination to which the message is transmitted and the content of the message to be transmitted from the contents of the transferred file. The FTP server 192 / FTP-AP server 196 generates a launch signal (Launching) 212 including the read SIP-URI and the content of the transmission message, and supplies it to the proxy UA management unit 76 at time T102. The proxy UA management unit 76 supplies the activation signal 212 to the message transmission access function unit 88 by the interface function of the component API 78, and activates the message transmission access function unit 88.

  The message transmission access function unit 88 generates a launch signal (Launching) 214 for the cooperation management unit 70 and supplies it to the cooperation management unit 70 at time T104. The cooperation management unit 70 is activated by the activation signal 214 supplied. The linkage management unit 70 uses one of SOAP, CORBA, etc., and generates a request signal (FT_REQ.) 216 corresponding to the protocol to be used, and the linkage exists in another domain on the network 16 at time T106. It communicates with the management unit 52.

  The cooperation management unit 52 receives the supplied request signal (FT_REQ.) 216 as a “file transfer request”. The cooperation management 52 generates a launch signal (Launching) 218 for the message transmission function unit 64 in the proxy UA management unit 50 based on the received request signal 216. The cooperation manager 52 outputs the activation signal 218 to the proxy UA manager 50 at time T108.

  The proxy UA management unit 50 activates the message transmission function unit 64 by the activation signal 218 supplied. The message transmission function unit 64 outputs the message content included in the activation signal 218 supplied at time T110 to the SIP softphone 46 as message information (Message) 220. The SIP softphone 46 displays message information 220 supplied as a message recipient.

  Although not shown, the message transmission function unit 64 receives a reception response of the message information 220 from the SIP softphone 46 as a message transmission result. The message transmission function unit 64 outputs a launch signal 222 including a reception response to the cooperation management unit 52 at time T112. The cooperation management unit 52 is activated in response to the reception of the activation signal 222. The link management unit 52 uses one of SOAP, CORBA, etc. to send the transmission result to the different FTP systems 180 via the network 16, and the transmission result can be handled by the selected protocol (Response) 224 is sent to the cooperation management unit 70 at time T114. The cooperation management unit 70 transmits a “file transfer request” result (Response) 226 to the message transmission access function unit 88 of the proxy UA management unit 76 at time T116.

  The proxy UA management unit 76 receives the result of “file transfer request”. The message transmission access function unit 88 supplies the reception result to the FTP server 192 / FTP-AP server 196 at time T118 as the execution result of the component API 78 (Response 228). The supplied FTP server 192 / FTP-AP server 196 processes the result of the message transmission request into a format that can be displayed. The format is, for example, a SIP-URI format. The FTP server 192 / FTP-AP server 196 outputs the message transmission request result (Response) 230 processed at time T120 to the FTP client 206. The FTP client 206 displays the result of the “file transfer request” as a code.

  By operating in this way, file transfer processing is executed in the FTP system 190, and when it is completed, the file update information representing the file contents is handled as SIP message information in the SIP system 12, and a message transmitted from the FTP system 190 Are also supplied to the SIP system 12, and the FTP client 206 can manage the file status as a result of the SIP message transmission supplied from the SIP system 12.

  In this embodiment, the client of the Web system 12 or FTP system 190 causes the SIP system 12 to perform processing corresponding to the service instance, and the processing result is displayed on the requesting client. The information is not limited to processing, and information can be provided by a reverse sequence. That is, the proxy UA process can be performed from the SIP system 12 to the Web system 12 or the FTP system 190.

  By configuring as described above, for example, when executing a service instance requested by a client connected to the Web system 14, the proxy UA management unit 76 for this request functions as a proxy UA using the HTTP protocol, and the cooperation management unit 70 The coordination manager 70 makes this request for one of the SOAP / CORBA protocols, sends it to the linkage manager 52, and the linkage manager 52 makes the SIP protocol request, and the proxy UA manager 50 responds. The proxy UA function is used to process the request, and the response of this processing result is sent to the requesting client via the proxy UA management unit 50, the linkage management units 52 and 70, and the proxy UA management unit 76, and displayed for dissimilar communication. Proxy UA processing corresponding to service instances between protocols is performed in each system, providing services that could not be done by conversion gateways so far, Web system 14 for a long time No pending processing over, it is possible to effectively utilize the resources, it is possible to realize a suitable user interface.

  The proxy UA management unit 50 generates, registers, and deletes a user agent as a proxy, changes presence information as a user agent, sends a message as a user agent to a designated destination, edits user information that represents the user agent, and a user The function unit 56 to 68 that manages the search of user information representing the agent is included, and the proxy UA management unit 76 includes the function units 80 to 92 that access the function units 56 to 68 of the proxy UA management unit 50. Thus, in particular, HTTP processing (transaction) for notifying the user of the progress of each processing described above in the HTTP environment can be quickly performed.

  By using either SOAP or CORBA as a protocol that can be handled in common for the SIP and HTTP protocols and the SIP and FTP protocols, information can be communicated even between systems in different system environments.

  The service providing system 10 can reduce the system configuration by accommodating the SIP system 12 and the Web system 14 in the same computer. In addition, by providing the functions of the cooperation management units 52 and 70 in a predetermined function call, it is not necessary to mount the cooperation management units 52 and 70 as respective components, which contributes to downsizing of the apparatus. By interposing a network between the SIP system 12 and the Web system 14 or between the SIP system 12 and the FTP system 190, each system can be distributed and the service providing system 10 can be arranged flexibly. be able to.

  The service providing system 10 includes the SIP system 12 and the Web system 14 and the SIP system 12 and the FTP system 190 configured by computers, and the programs for operating the system 10 include the linkage management unit 52, the proxy UA management unit 50, and the linkage. By functioning as the management unit 70 and the proxy UA management unit 76, the system configuration can be further reduced in size, and it is possible to flexibly respond to requests for addition or reduction of the configuration, version upgrade, and the like.

  Further, according to the service providing method of the present invention, for example, when a service instance requested by a client connected to the Web system 14 is executed, an activation signal is generated by the proxy access function of the proxy user agent (UA) for this request using the HTTP protocol. (Launching) 104 is generated, this request is made a request expressed using one of SOAP / CORBA, communication between systems is performed, and the information in the SIP system 12 by the proxy UA function corresponding to the request made in the SIP protocol Process, the launch signal (Launching) 116 including the response information of this processing result is generated by the proxy UA, the response information is set to one of SOAP / CORBA, communication between the systems is performed, and the response information is set to the proxy access function Each system performs proxy UA processing corresponding to service instances between different types of communication protocols. By performing in-time, it is possible to provide a service that could not before. In particular, in the Web system 14, there is no processing suspension for a long time, and resources can be used effectively.

  The proxy user agent generates, registers, and deletes as a user agent corresponding to the requested service instance, changes presence information as a user agent, sends a message to a specified destination as a user agent, and transmits user information as a user agent. Edit and search user information as a user agent, proxy access can be created, registered, deleted, presence change, message transmission, user information edit and user information search, respectively, HTTP environment The HTTP process (transaction) for notifying the user of the progress of each process described above can be quickly performed.

  In addition, the service provision method uses either SOAP or CORBA as a protocol that can be handled in common for the SIP and HTTP protocols and the SIP and FTP protocols, so that information can be communicated even between systems in different system environments. be able to.

  The present invention is not limited to the above-described embodiments. If a protocol that fuses between different protocols and the protocol used by this protocol are linked and managed, APs to be constructed can be linked to each other. Can be easily constructed, executed, and operated.

It is a block diagram which shows the schematic structure of the service provision system to which the service system of this invention is applied. It is a block diagram which shows the structural example of the accessor component shown in FIG. It is a sequence chart explaining the operation | movement procedure with respect to the service generation request in the service provision system shown in FIG. It is a sequence chart explaining the operation | movement procedure with respect to the presence setting request in the service provision system shown in FIG. It is a sequence chart explaining the operation | movement procedure with respect to the message transmission request in the service provision system shown in FIG. It is a block diagram which shows the schematic structure of the 1st modification with respect to the structure of FIG. It is a block diagram which shows the schematic structure of the 2nd modification with respect to the structure of FIG. It is a sequence chart explaining the operation | movement procedure with respect to the message transmission request in the service provision system shown in FIG.

Explanation of symbols

10 Service delivery system
12 SIP system
14 Web system
16 SOAP / CORBA network
18 SIP server
20 SIP-DB
22 SIP-AP server
26 SIP-AP
28 Web Accessor Component
30 SIP client
32 Web server
34 Web-DB
36 Web-AP server
40 Web-AP
42 SIP accessor components
50, 76 Proxy UA Management Department
52, 70 Cooperation Management Department
54, 78 Component API

Claims (9)

In a service system that provides information as a service by communicating information with each of clients connected to a system constructed by an environment of a different communication protocol, the service system includes:
A first system operating based on a first communication protocol;
A second system that operates based on a second communication protocol,
The first communication protocol is a session initiation protocol, the second communication protocol is a hypertext transfer protocol,
The first system processes information to be transmitted to the second system into a third communication protocol that is handled as information that is commonly linked in the first communication protocol and the second communication protocol, and is supplied from the second system. First linkage management means for converting information according to the third communication protocol to information of the first communication protocol;
A first proxy management unit configured to set the requested service instance in a client of the first system, virtually manage the proxy as a user agent, and operate information to be managed;
The first proxy management means further includes a proxy generation function block that generates the user agent corresponding to the requested service instance;
A pre-proxy registration functional block for registering the user agent corresponding to the service instance;
A proxy deletion functional block for deleting the user agent corresponding to the service instance;
A presence setting function block for changing presence information of the user agent corresponding to the service instance;
A message transmission function block for transmitting a message from the user agent corresponding to the service instance to the specified user agent;
A proxy information editing function block for editing user information of the user agent corresponding to the service instance;
A proxy information search function block for searching for user information of the user agent corresponding to the service instance,
The second system processes information to be transmitted to the first system into a third communication protocol, and converts information based on the third communication protocol supplied from the first system into information of the second communication protocol. 2 linkage management means,
A second proxy that accesses the corresponding function of the first proxy management means from the second system to the requested service instance by a virtual user agent, and acquires the execution result of the service instance by proxy and a management means only including,
The second proxy management means further includes a proxy generation access function block for accessing the proxy generation function block on the first system side from the second system,
A proxy registration access function block for accessing the proxy registration function block on the first system side from a second system;
A proxy deletion access function block for accessing the proxy deletion function block on the first system side from the second system;
A presence setting access functional block for accessing a change in the presence status of the service from here and changing the presence of the user agent through the presence setting functional block on the first system side;
A message transmission access functional block for accessing a change in the service progress status from here and creating and transmitting the message of the user agent through the message transmission functional block on the first system side;
A proxy information editing access function block for accessing the proxy information editing function block on the first system side from the second system;
Service system characterized by including Mukoto the proxy information retrieval access function blocks from the second system for accessing the proxy information retrieval function blocks of the first system side. In a service system that provides information as a service by communicating information with each of clients connected to a system constructed by an environment of a different communication protocol, the service system includes:
A first system operating based on a first communication protocol;
A second system that operates based on a second communication protocol,
The first communication protocol is a session initiation protocol, the second communication protocol is a file transfer protocol,
The first system processes information to be transmitted to the second system into a third communication protocol that is handled as information that is commonly linked in the first communication protocol and the second communication protocol, and is supplied from the second system. First linkage management means for converting information according to the third communication protocol to information of the first communication protocol;
A first proxy management unit configured to set the requested service instance in a client of the first system, virtually manage the proxy as a user agent, and operate information to be managed;
The first proxy management means further includes a proxy generation function block that generates the user agent corresponding to the requested service instance;
A pre-proxy registration functional block for registering the user agent corresponding to the service instance;
A proxy deletion functional block for deleting the user agent corresponding to the service instance;
A presence setting function block for changing presence information of the user agent corresponding to the service instance;
A message transmission function block for transmitting a message from the user agent corresponding to the service instance to the specified user agent;
A proxy information editing function block for editing user information of the user agent corresponding to the service instance;
A proxy information search function block for searching for user information of the user agent corresponding to the service instance,
The second system processes information to be transmitted to the first system into a third communication protocol, and converts information based on the third communication protocol supplied from the first system into information of the second communication protocol. 2 linkage management means,
A second proxy that accesses the corresponding function of the first proxy management means from the second system to the requested service instance by a virtual user agent, and acquires the execution result of the service instance by proxy Management means,
The second proxy management means further includes a proxy generation access function block for accessing the proxy generation function block on the first system side from the second system,
A proxy registration access function block for accessing the proxy registration function block on the first system side from a second system;
A proxy deletion access function block for accessing the proxy deletion function block on the first system side from the second system;
A presence setting access functional block for accessing a change in the presence status of the service from here and changing the presence of the user agent through the presence setting functional block on the first system side;
A message transmission access functional block for accessing a change in the service progress status from here and creating and transmitting the message of the user agent through the message transmission functional block on the first system side;
A proxy information editing access function block for accessing the proxy information editing function block on the first system side from the second system;
Service system characterized by including Mukoto the proxy information retrieval access function blocks from the second system for accessing the proxy information retrieval function blocks of the first system side. 3. The service system according to claim 1 , wherein the service system is one of SOAP (Simple Object Access Protocol) and CORBA (Common Object Request Broker Architecture) which can be handled by both the first and second communication protocols. Is used for the third communication protocol. In service system according to any one of claims 1 to 3, the service system, the service system to which the first system and a second system is characterized in that it is housed in the same computer. 5. The service system according to claim 4 , wherein the service system represents the functions of the first cooperation management means and the second cooperation management means by a predetermined function call, and realizes these functions. system. In service system according to any one of claims 1 to 3, the service system, service system network between the first and second systems, characterized in that the interposed. The service system in a computer to implement the service of the service system according to any one of claims 1 to 5, each of the first system and the second system is a computer, the computer, the first A computer-readable recording medium having recorded thereon a program for functioning as first cooperation management means and first proxy management means in the system and as second cooperation management means and second proxy management means in the second system. In a service providing method for communicating information with each of clients connected to a system constructed by an environment of different communication protocols and providing the information as a service, the method includes:
The first communication protocol is a session initiation protocol and the second communication protocol is one of a hypertext transfer protocol and a file transfer protocol;
Of the communication between the first system that operates according to the first communication protocol and the second system that operates according to the second communication protocol, the information transmitted from the first system is the first communication. A first step of sending information processed by the first linkage management means that processes to a third communication protocol treated as information to be linked in common in the protocol and the second communication protocol, to the second system;
The second communication protocol information processed by the second linkage management means that processes the third communication protocol information supplied to the second system into the second communication protocol information is processed into the second communication protocol information. Two steps;
A third step of sending the information processed by the second cooperation management means for processing the information of the second communication protocol sent from the second system into the information of the third communication protocol, to the first system;
The information supplied by the first linkage management means for processing the information of the third communication protocol supplied to the first system into the information of the first communication protocol is processed into the information of the first communication protocol. 4 processes,
A proxy that is set as a client in a communication destination system corresponding to a service instance requested from a client connected to one of the first and second systems, and is virtually managed as a user agent. A fifth step of generating a first activation signal by an access proxy management means for generating a first activation signal including information corresponding to the service instance according to a proxy access function for accessing a user agent;
A sixth step of executing one set of steps in the first and second step sets or the third and fourth step sets in response to the first activation signal;
A seventh step of performing information processing corresponding to the service instance by the proxy user agent in the communication destination system in the first and second cooperation management means;
An eighth step of generating a second activation signal by proxy management means for generating a second activation signal including response information to the information processing by the proxy user agent;
A ninth step of executing the other set of steps in response to the second activation signal;
Look including a tenth step to return to the client that requested the response information by the proxy access function at the service instance communication source system requesting a
The proxy user agent generates information for the user agent corresponding to the requested service instance, registers information and deletes information, changes presence information for the user agent, and changes from the user agent to a designated destination. Sending a message, editing user information for the user agent and searching for the user information for the user agent
The proxy access includes the generation, registration, deletion, presence change, message transmission, user information editing, and user information search, respectively . 9. The method according to claim 8 , wherein the method uses any one of SOAP (Simple Object Access Protocol) and CORBA (Common Object Request Broker Architecture) which can be handled by both the first and second communication protocols. A service providing method characterized by being used for a communication protocol.

Images