JP5296602B2 - Service providing system and service providing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To control services based on such a temporary communication relationship that the relationship with a communication mating party is temporary, and to deliver data easily. <P>SOLUTION: When a session management server accepts a delivery request for requesting to deliver data from an information display terminal which is utilized by a communicating user by an SIP phone, the session management server determines whether the information display terminal of a request source of the delivery request concerned is an information display terminal which is utilized paired with the SIP phone establishing the communication by an SIP. When the session management server determines that the information display terminal is a terminal which is utilized paired with the SIP phone establishing the communication by the SIP, the session management server obtains the data to be used for the delivery from a storage source of the data according to the delivery request, and controls the delivery of the data by use of the obtained data. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a service providing system and a service providing method.

  Conventionally, there is a so-called Web service as a service provided to a terminal connected to a network controlled by IP (Internet Protocol). Here, the Web service generally refers to a service that realizes application functions via a network by applying WWW (World Wide Web) related technology. For example, a terminal connected to the Internet receives IM (Instant Messaging) service, which is one of Web services, and realizes chat and image data sharing with other terminals connected to the Internet.

  Further, for example, Patent Literature 1 discloses a technique that eliminates the need for member registration when using a new service by unifying member (community) management. For example, Patent Document 2 discloses a technique for sharing an application using a general browser.

JP 2005-228122 A JP 2003-044429 A

  However, in the above-described conventional technology, when the relationship with the communication partner is temporary (in the case of a relationship that changes to ad hoc), the service cannot be controlled based on such a temporary communication relationship. In addition, there is a problem that data cannot be easily transferred.

  Therefore, the present invention has been made to solve the above-described problems of the prior art, and when the relationship with the communication partner is temporary (in the case of a relationship that changes to ad hoc), such a temporary change is made. It is an object of the present invention to provide a service providing system and a service providing method capable of controlling a service based on various communication relationships and easily exchanging data.

  A service providing system and a service providing method disclosed in the present application are, in one aspect, a service providing system that provides a service on a network to a terminal, and the session management server is provided for each terminal that requests service provision. Communication information collecting means for collecting communication information for identifying the first communication established between the first communication terminal and the other first communication terminal that is used in combination with the terminal and establishes the first communication; Each of communication information indicating the same first communication among a plurality of pieces of communication information collected by the communication information collecting means, and each of the first communication terminals that established the first communication identified by the specified communication information; Link the service from the service providing server with the link information issuing means that issues link information for linking each terminal used in the set to each terminal. When a transfer request for requesting data transfer is received from one of the terminals provided, the request source terminal of the transfer request is identified by the communication information collected by the communication information collecting means. Determining means for determining whether or not a terminal is used in combination with a first communication terminal that has established one communication; and used in combination with a first communication terminal that has established the first communication by the determining means. If the terminal is determined to be a terminal, in accordance with the transfer request, an acquisition unit that acquires data used for the transfer from the storage source of the data, and control of data transfer using the data acquired by the acquisition unit And a delivery control means. In addition, the service providing server includes, for each terminal that requests service provision, a cooperation information collecting unit that collects the cooperation information issued by the cooperation information issuing unit, and a plurality of pieces of cooperation information collected by the cooperation information collecting unit. Service providing control means for controlling service provision so as to link the service provided to each terminal that is the collection source of the identified linkage information is identified. It is characterized by.

  According to one aspect of the service providing system and the service providing method disclosed in the present application, when the relationship with the communication partner is temporary (in the case of a relationship that changes to ad hoc), based on such a temporary communication relationship. Thus, it is possible to control the service and easily exchange data.

FIG. 1 is a diagram for explaining an overview of the service providing system according to the first embodiment. FIG. 2 is a diagram for explaining an overview of the service providing system according to the first embodiment. FIG. 3 is a block diagram showing the configuration of the session management server. FIG. 4 is a block diagram showing the configuration of the service providing server. FIG. 5 is a block diagram showing the configuration of the HGW. FIG. 6 is a block diagram showing the configuration of the SIP phone. FIG. 7 is a block diagram showing the configuration of the information display terminal. FIG. 8A is a schematic diagram illustrating various tables stored in the session management server. FIG. 8-2 is a diagram for explaining various tables stored in the session management server. FIG. 9A is a diagram for explaining a table stored in the service providing server. FIG. 9-2 is a diagram for explaining a table stored in the HGW. FIG. 10 is a sequence diagram illustrating a procedure of processing related to service provision. FIG. 11 is a sequence diagram illustrating a procedure of processing related to service provision. FIG. 12 is a diagram for explaining the delivery flag and the data storage source flag. FIG. 13A is a diagram for explaining various methods. FIG. 13-2 is a diagram for explaining various methods. FIG. 13C is a diagram for explaining various methods. FIG. 13-4 is a diagram for explaining various methods. FIG. 14 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 15 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 16 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 17 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 18 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 19 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 20 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 21 is a sequence diagram illustrating a procedure of processing relating to data transfer. FIG. 22 is a sequence diagram illustrating a procedure of processing relating to data transfer. FIG. 23 is a sequence diagram illustrating a procedure of processing relating to data transfer. FIG. 24 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 25 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 26 is a sequence diagram illustrating a processing procedure related to data transfer. FIG. 27A is a sequence diagram illustrating a processing procedure relating to data transfer. FIG. 27-2 is a sequence diagram illustrating a processing procedure related to data transfer.

  Exemplary embodiments of a service providing system and a service providing method according to the present invention will be described below in detail with reference to the accompanying drawings. In the following, description of main terms used in the embodiment, an overview of the service providing system according to the first embodiment, a configuration of the service providing system according to the first embodiment, a processing procedure by the service providing system according to the first embodiment, The effects of the first embodiment will be described in order, and then other embodiments will be described.

[Explanation of terms]
First, key terms used in the following examples will be described. A “service” is a so-called Web service (a service that realizes an application function via a network by applying a WWW-related technology). In a network controlled by IP such as the Internet, a “service providing server” controls a service, and a “terminal” connected to the network is provided with a “service”.

  By the way, the “service providing server” controls services based on the relationship between each terminal, the relationship between the terminal and the service providing server, or the relationship between users who use the terminal. For example, in the IM service, it is assumed that a user who uses the terminal A and a user who uses the terminal B realize file sharing in the IM service. It is assumed that terminal A has uploaded a file to “service providing server” while terminal B is accessing “service providing server”. In such a case, the “service providing server” transmits a file to the terminal B based on the relationship between the user of the terminal A and the user of the terminal B. That is, the “service providing server” accepts an input of a user ID and a password from a user of the terminal A, and accepts an input of a user ID and a password from a user of the terminal B, for example. And the user of terminal B are identified. Then, if the relationship between the identified user of the terminal A and the user of the terminal B recognizes that file sharing is mutually permitted, the “service providing server” sends a file to the terminal B based on the relationship. Control the service to send.

  In addition, for example, in SNS (Social Networking Service), it is assumed that the user of the terminal A who is the site operator causes the user of the terminal B to browse the site. In such a case, the “service providing server” controls browsing of the site by the user of the terminal B based on the relationship between the user of the terminal A and the user of the terminal B. That is, the “service providing server” has a relationship between the user of the specified terminal A and the user of the specified terminal B, and the relationship that the user of the terminal A is permitted to browse the site by the user of the terminal A If so, the service is controlled so as to permit browsing of the site by the user of the terminal B based on the relationship.

  Also, for example, a case where a “service providing server” that provides music information permits the user of the terminal A to download music information is assumed. In such a case, the “service providing server” controls the download communication by the terminal A based on the relationship between the user of the terminal A and the “service providing server”. That is, the “service providing server” indicates that the relationship between the identified user of the terminal A and the “service providing server” is such that download communication by the user of the terminal A is permitted by the “service providing server”. Based on the relationship, the service provision is controlled so as to permit the download communication by the terminal A.

  As described above, the relationship between each terminal, the relationship between the terminal and the service providing server, or the relationship between users using the terminal has various modes depending on the service content. The “server” still controls services based on these relationships.

  However, the conventional Web service has been provided on the assumption that such a relationship is registered in advance. For example, a conventional “service providing server” registers a relationship between users in a buddy list in advance, and controls services such as chat and image data sharing based on the registered buddy list. On the other hand, the service providing system and the service providing method according to the present invention have not only a relationship such as a pre-registered buddy list but also a temporary relationship with the communication partner (in the case of a relationship that changes to ad hoc). In addition, services such as chat and image data sharing are controlled based on the temporary communication relationship.

[Outline of Service Providing System According to Embodiment 1]
The service providing system according to the first embodiment outlines providing a service on a network to a terminal. When the relationship with a communication partner is temporary (in the case of a relationship that changes to ad hoc), such a temporary service is provided. It controls services based on various communication relationships and facilitates data exchange.

  This outline will be described with reference to FIG. 1 and FIG. FIG. 1 and FIG. 2 are diagrams for explaining an overview of the service providing system according to the first embodiment. The service providing system illustrated in FIGS. 1 and 2 has a configuration in which a terminal side is divided into a SIP (Session Initiation Protocol) phone and an information display terminal used in combination with the SIP phone. The service providing server provides a service based on such a temporary communication relationship to the information display terminal even when the relationship with the communication partner is temporary, such as a communication partner with whom communication has been established. . Here, the SIP phone is a terminal that establishes communication by SIP (note that communication using the established session is also performed), and the information display terminal is a terminal that performs HTTP (HyperText Transfer Protocol) communication. That is. “Used in a group” means, for example, a situation in which a single user uses both a SIP phone and an information display terminal.

  In the service providing system, an HGW (Home Gate Way) is installed in the terminal-side network. 1 and 2, the connection relationship between the HGW, the SIP phone, and the information display terminal is not clearly shown, but the SIP phone and the information display terminal are connected under the HGW. It is a device that controls both SIP communication using a SIP phone and HTTP communication using an information display terminal. That is, both SIP communication using a SIP phone and HTTP communication using an information display terminal are connected to a network via an HGW. In the following, the process of establishing a session by SIP is appropriately expressed as “SIP communication” (that is, “SIP communication” is communication of the session itself established by SIP (for example, a voice path between end users, VPN (Virtual Private Network) etc.).

  On the other hand, in the service providing system, a SIP proxy, a session management server, and a service providing server are installed on the network side. The SIP proxy is a device that controls the process of establishing a session by SIP and the communication of the session itself established by SIP. Further, as will be described later, the session management server is a device that controls the connection destination of the information display terminal and controls data transfer. The service providing server is a device that provides a service to the information display terminal. In the first embodiment, an example in which the SIP proxy, the session management server, and the service providing server are installed as physically different devices will be described, but the present invention is not limited to this. Whether it is set as a physically different device can be arbitrarily changed according to the operation mode of the service provider.

  As described above, the service providing system according to the first embodiment controls services based on such a temporary communication relationship when the relationship with the communication partner is temporary (a relationship that changes to ad hoc). In addition, data is easily exchanged. Therefore, in the following, the outline of the point that the service providing system according to the first embodiment controls the service based on the temporary communication relationship will be described with reference to FIG. Next, an outline of the point that the service providing system according to the first embodiment easily transfers data will be described with reference to FIG.

  As shown in FIG. 1, in the service providing system according to the first embodiment, communication is established between SIP phones and SIP phones by SIP.

  Subsequently, the information display terminal used as a pair in the SIP phone with which the communication is established and the user sends a service start request for requesting to start the service together with the call session information (information for identifying the established communication) to the session. Send to the management server.

  The session management server collects call session information, and specifies call session information indicating the same communication from the collected call session information. That is, the session management server does not collect call session information from only the two information display terminals shown in FIG. 1, but actually, the call management server also calls from a large number of information display terminals not shown in FIG. Session information will be collected. For this reason, the session management server specifies call session information collected from the two information display terminals shown in FIG. 1 from the many call session information collected from such a large number of information display terminals. Then, the session management server issues, to each information display terminal, cooperation information for linking each information display terminal used in combination with each SIP phone that has established communication identified by the specified call session information. To do.

  Then, the information display terminal transmits a service use request for requesting use of the service to the service providing server together with the cooperation information.

  The service providing server collects linkage information and identifies linkage information indicating that the service is linked from the collected pieces of linkage information. That is, similar to the session management server, the service providing server does not collect cooperation information from only the two information display terminals shown in FIG. 1, but in fact, a large number of information display terminals not shown in FIG. Similarly, it will collect collaborative information. For this reason, the service providing server specifies the cooperation information collected from the two information display terminals shown in FIG. 1 from the many pieces of cooperation information collected from such a large number of information display terminals. Then, the service providing server controls the service provision so that the services provided to each of the information display terminals that are the collection sources of the identified cooperation information are linked.

  Subsequently, as shown in FIG. 2, in the service providing system according to the first embodiment, one information display terminal transfers data between information display terminals provided to link services from the service providing server. Send the requested delivery request to the session management server. The delivery request in the first embodiment includes a delivery destination flag that designates a delivery destination and a data storage source flag that designates a storage source of data to be delivered.

  When the session management server accepts the delivery request, whether the information display terminal that is the request source of the delivery request is an information display terminal that is used in combination with a SIP phone that has established communication identified by the collected call session information Determine whether or not. That is, it is determined whether or not the user of the information display terminal is a SIP phone user who has established communication by SIP, for example, whether or not the user is a user who is currently in a call. In the first embodiment, a method for determining that a user is currently in a call will be described. However, the present invention is not limited to this. For example, at least a user who has made a call in the past is used. It may be a method for determining a certain thing.

  When the session management server determines that the user of the information display terminal that is the request source of the delivery request is actually busy, the session management server controls the data delivery according to the delivery request. That is, the session management server according to the first embodiment acquires the data specified by the data storage source flag from the data storage source according to the transfer destination flag and the data storage source flag included in the transfer request, and acquires the data. Control is performed so that data is transferred to the transfer destination specified by the transfer destination flag.

  As described above, in the service providing system according to the first embodiment, the session management server issues cooperation information for realizing service provision based on a temporary communication relationship established by SIP and accepts a data transfer request. For example, it is determined that the requesting user is actually in a call, and then data transfer is controlled. For this reason, a user who uses a SIP phone and an information display terminal as a pair can use a Web service in cooperation with a call partner while making a call, and can extend the call. This makes it possible to easily exchange data.

[Configuration of Service Providing System According to Embodiment 1]
Next, the configuration of the service providing system according to the first embodiment will be described with reference to FIGS. 3 is a block diagram showing the configuration of the session management server, FIG. 4 is a block diagram showing the configuration of the service providing server, FIG. 5 is a block diagram showing the configuration of the HGW, and FIG. FIG. 7 is a block diagram showing a configuration of an information display terminal, and FIGS. 8-1 and 8-2 are diagrams for explaining various tables stored in the session management server. FIG. 9-1 is a diagram for explaining a table stored in the service providing server, and FIG. 9-2 is a diagram for explaining a table stored in the HGW.

  In the following, the configuration of the service providing system will be briefly described, and the processing of each unit will be described in detail in the processing procedure described later.

[Session Management Server]
The session management server 100 is realized by providing each unit described below in a general-purpose server or the like. Particularly, as closely related to the present invention, as shown in FIG. Unit 120 and control unit 130.

  The communication unit 110 includes a general interface and library for HTTP communication, and transmits / receives information to / from the information display terminal 20 and transmits / receives information to / from the HGW 10 and the service providing server 200.

  The storage unit 120 stores information used for various controls in the control unit 130, and particularly as closely related to the present invention, as shown in FIG. 2, a user contract service management table 121 and a contract service information table 122 are stored. And a control session management table 123, an arrival / departure linking ID table 124, a data transfer table 125, and a data table 126.

  The user contract service management table 121 is a table for managing a service contracted by a user (user) who uses the information display terminal 20 (and the SIP phone 30). For example, as shown in FIG. 8A, the user contract service management table 121 stores user identification information and a contract service ID in association with each other. These pieces of information stored in the user contract service management table 121 are registered in advance in the service providing system according to the first embodiment, and are appropriately registered.

  Here, the user identification information is information for identifying the user of the information display terminal 20, and SIP-URI (Uniform Resource Identifier) is used in the first embodiment. The contract service ID (hereinafter also referred to as service ID as appropriate) is an ID for identifying a service. As described above, the user contract service management table 121 stores the user identification information and the contract service ID in association with each other so that the user identified by the user identification information can be subscribed to the service identified by the contract service ID. I manage to be a person.

  The contract service information table 122 is a table for managing various information for each contract service. For example, as shown in FIG. 8A, the contract service information table 122 stores a contract service ID and an access destination URL (Uniform Resource Locator) in association with each other. Here, the access destination URL is the URL of the service providing server 200 that provides the service identified by the contract service ID. These pieces of information stored in the contract service information table 122 are registered in advance and appropriately registered in the service providing system according to the first embodiment.

  The control session management table 123 is a table for managing control session information. For example, as shown in FIG. 8A, the control session management table 123 includes control session information, call session information, an arrival / departure determination flag, call information (start time to end time), an HGW URL, Are stored in association with each other.

  Here, the control session information is information given to the Web browser of the information display terminal 20 in order for the session management server 100 to communicate with the information display terminal 20, and information display This is information that uniquely identifies Web communication established between the terminal 20 and the session management server 100. When a call session information collection unit 131 described later receives a service start request from the information display terminal 20, the call session information collection unit 131 pays out control session information and stores it in the control session management table 123. As the control session information, a method using a “session ID” (such as a cookie ID) that is information given to a browser used when the information display terminal 20 performs Web communication is conceivable. Further, the control session information is generally generated uniquely for each established session.

  Call session information is information that uniquely identifies a session established by SIP between SIP phones 30. When a call session information collection unit 131 to be described later receives a service start request from the information display terminal 20, the call session information collection unit 131 acquires the call session information collection unit 131 from the information display terminal 20 and stores it in the control session management table 123. As call session information, “Call-ID” or “isub”, which is information included in SIP communication, “From”, “To”, “tag”, an IP address, or a combination thereof is used. A method or a method using a combination of other information (for example, “Date”) included in SIP communication is conceivable, and a method using information that can uniquely identify communication established by SIP is used. Any method may be used. Call session information is generally generated uniquely for each established session.

  In addition, the arrival / departure determination flag refers to the SIP phone 30 (the SIP phone 30 used in combination with the information display terminal 20 that has issued the control session information) for the session established by SIP between the SIP phones 30 on the calling side. It is a flag for determining whether there is a callee or a callee. When a call session information collection unit 131 to be described later receives a service start request from the information display terminal 20, the call session information collection unit 131 acquires the call session information collection unit 131 from the information display terminal 20 and stores it in the control session management table 123.

  Call information is information indicating the start time and end time of a session uniquely identified by call session information. When a call session information collection unit 131 to be described later receives a service start request from the information display terminal 20, the call session information collection unit 131 stores the time in the control session management table 123 as the start time. Note that the call session information collection unit 131 described later may acquire the start time from the information display terminal 20 and store it in the control session management table 123. Similarly, when the session management server 100 recognizes that the session has been disconnected, the session management server 100 stores the time in the control session management table 123 as the end time.

  The HGW URL is the URL of the HGW 10 that controls HTTP communication by the information display terminal 20. When a call session information collection unit 131 to be described later receives a service start request from the information display terminal 20, the call session information collection unit 131 acquires the call session information collection unit 131 from the information display terminal 20 and stores it in the control session management table 123.

  As described above, the control session management table 123 is established by the SIP phone 30 (the SIP phone 30 used in combination with the information display terminal 20) in association with the control session information issued by the session management server 100. By storing information relating to a session (hereinafter, call session information, arrival / departure determination flag and call information are referred to as “information relating to a session”), the control session information is paid out to any information display terminal 20. It is to manage whether it is a thing. In FIG. 8A, for convenience of explanation, regular numerical values are exemplified as the control session information and “Call-ID”, but generally random numbers or the like are stored.

  The arrival / departure association ID table 124 is a table for managing the arrival / departure association ID. For example, as shown in FIG. 8A, the arrival / departure association ID table 124 stores control session information, contract service ID, departure / arrival association ID, pseudonym ID, and status in association with each other. ing. A control session that is issued by the call session information collection unit 131 when an after-arrival / incoming linking ID issuing unit 132 receives a service start request from the information display terminal 20 and pays out an arriving / departing linking ID and a pseudonym ID. The information, contract service ID, and status are stored in the arrival / departure association ID table 124.

  Here, the connection ID between calling and arrival is pseudonym information of call session information that uniquely identifies a session established by SIP, and the service providing server 200 includes each information display terminal 20 during a call, that is, a user. Each ID is an ID used for associating each information display terminal 20 in a call with each SIP phone 30. As will be described later, since the connection ID between outgoing and incoming calls is newly issued for each established session (that is, for each call), the service providing server 200 provides the information display terminal 20 for each session (that is, for each call). Each can be tied.

  The pseudonym ID is information for uniquely identifying the combination of the information display terminal 20 and the service used by the information display terminal 20, and the service providing server 200 determines which of the two information display terminals 20. This is an ID used for specifying whether the information display terminal 20 is. That is, the service providing server 200 specifies the two information display terminals 20 by using the link ID between departure and arrival, and controls to link the services provided to the two specified information display terminals 20. However, it is not possible to provide services by distinguishing the two information display terminals 20 only by using the ID between the arrival and departure times. In this respect, since the kana ID is issued for each combination of the information display terminal 20 and the service, the service providing server 200 distinguishes each of the two information display terminals 20 using the kana ID, and each information Control can be performed so as to provide a service adapted to the display terminal 20.

  The status indicates whether or not the user identified by the pseudonym ID is using the service identified by the contract service ID.

  The data transfer table 125 is a table for managing data transfer. For example, as shown in FIG. 8B, the data delivery table 125 includes control session information, call session information, arrival / departure determination flags, delivery destination information, data storage source information, access keys, and data files. The name and status information are stored in association with each other. In FIG. 8-2, the data transfer table 125 is described in three lines, but one line represents one record.

  In addition, the data delivery table 125 stores the delivery destination flag, the data storage source flag, and the service ID included in the delivery request as delivery destination information and data storage source information together with the arrival / departure association ID and pseudonym ID. The delivery destination information and data storage source information are used for processing by the data delivery control unit 134 described later. That is, the data delivery control unit 134 controls data delivery by referring to the delivery destination information and the data storage source information.

  Further, the data delivery table 125 includes, as status information, date and time information when the delivery request has been accepted, date and time information when the access key has been sent, date and time information when the data has been sent, and The date / time information when the data transfer is completed is stored. These date and time information is stored in the data delivery table 125 every time the session management server 100 enters a corresponding state.

  Here, regarding the transfer request, the session management server 100 stores the transfer destination information and the data storage source information in the data transfer table 125 and transmits the timing at which the transfer request is received and an access key (or key information) described later. Data transfer history by storing time information in the status information of the data transfer table 125 at the timing, the timing of transmitting the data to be transferred, the timing of receiving the result notification indicating that the transfer has been completed, etc. Manage information. In the first embodiment, the access key (or key information) used in the delivery and the data file name of the data to be delivered are also stored in the data delivery table 125. Further, the control session information, call session information, and departure / arrival determination flag are information stored in the control session management table 123, but in the first embodiment, they are also stored in the data transfer table 125 for convenience. And

  The data table 126 is a table that stores data that is a target of data transfer. For example, the data table 126 stores data file names and data in association with each other as shown in FIG. As will be described later, there are various methods for data transfer, and the session management server 100 does not always acquire the data to be transferred, but when the session management server 100 acquires data, The management server 100 may store the acquired data in the data table 126 as appropriate. The data file name stored in the data table 126 is the same as the data file name stored in the data transfer table 125.

  As shown in FIG. 3, the control unit 130 is particularly closely related to the present invention, as shown in FIG. 3, a call session information collection unit 131, an arrival / departure linking ID issuing unit 132, a delivery request determination unit 133, a data A delivery control unit 134.

  For each information display terminal 20 that has transmitted a service start request, the call session information collection unit 131 establishes communication established between the SIP phone 30 used in combination with the information display terminal 20 and another SIP phone 30. Call session information for identifying is collected.

  The link ID issuing unit 132 between arrivals and departures specifies call session information indicating the same communication from the plurality of call session information collected by the call session information collection unit 131, and is identified by the identified call session information. A link ID between departure and arrival for linking each information display terminal 20 used in combination with each phone 30 is issued to each information display terminal 20. Further, the arrival / departure association ID issuing unit 132 issues a pseudonym ID.

  When the delivery request determination unit 133 receives a delivery request for requesting data delivery from one information display terminal 20 between the information display terminals 20 provided to cooperate with the service from the service providing server 200, the delivery request determination unit 133 receives the delivery request. Whether the requesting information display terminal 20 is the information display terminal 20 used in combination with the SIP phone 30 that has established communication identified by the call session information collected by the call session information collection unit 131. judge. That is, it is determined whether or not the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. For example, it is determined whether or not the user is a user who is currently talking.

  When the transfer request determination unit 133 determines that the user of the information display terminal 20 that has requested the transfer request is the user of the SIP phone 30 that has established communication by SIP, the data transfer control unit 134 According to the request, data used for delivery is obtained from the data storage source, and data delivery is controlled using the obtained data.

[Service providing server]
The service providing server 200 is realized by providing each unit described below in a general-purpose server or the like, and particularly as closely related to the present invention, as shown in FIG. Unit 220 and control unit 230.

  The communication unit 210 includes a general interface and library for HTTP communication, and transmits and receives information to and from the session management server 100, the information display terminal 20, and the SIP proxy.

  The storage unit 220 stores information used for various controls in the control unit 230, and particularly as closely related to the present invention, as shown in FIG. 4, a Web session information management table 221 and a data table 222 are stored. Prepare.

  The Web session information management table 221 is pseudonym information issued by the session management server 100 as a pseudonym of call session information that uniquely identifies communication established by SIP, and links each information display terminal 20 together. This is a table for managing the information). For example, as shown in FIG. 9A, the Web session information management table 221 stores Web session information, an arrival / departure association ID, a pseudonym ID, an arrival / departure determination flag, and an access key in association with each other. Yes.

  Among these pieces of information stored in the Web session information management table 221, Web session information (provided for the Web browser of the information display terminal 20 so that the service providing server 200 can communicate with the information display terminal 20). Information) is paid out and registered when the service providing server 200 receives a service use request from the information display terminal 20. Further, the arrival / departure association ID, the pseudonym ID, and the arrival / departure determination flag are registered when the service providing server 200 receives a service use request from the information display terminal 20.

  Here, the Web session information is used by the service providing server 200 to identify the information display terminal 20. That is, when the service providing server 200 receives an access from the information display terminal 20, the service providing server 200 acquires the Web session information given to the Web browser of the information display terminal 20 and identifies the information display terminal 20. In addition, the connection / destination link ID is used by the service providing server 200 to link each of the information display terminals 20 during a call, that is, each of the information display terminals 20 each of which a user is calling using the SIP phone 30. It is done. Further, the pseudonym ID is used for specifying which information display terminal 20 of the two information display terminals 20 the service providing server 200 is. That is, the service providing server 200 specifies the two information display terminals 20 by using the link ID between departure and arrival, and controls to link the services provided to the two specified information display terminals 20. However, it is not possible to provide services by distinguishing the two information display terminals 20 only by using the ID between the arrival and departure times. In this respect, since the kana ID is issued for each combination of the information display terminal 20 and the service, the service providing server 200 distinguishes each of the two information display terminals 20 using the kana ID, and each information Control can be performed so as to provide a service adapted to the display terminal 20. The arrival / departure determination flag is used by the service providing server 200 to determine whether the SIP phone 30 used in combination with the information display terminal 20 is the calling side or the called side. Further, as will be described in detail in the description of the processing procedure, the access key specifies the data to be transferred when the service providing server 200 receives the access in connection with the data transfer, and specifies the access source. Used for authentication.

  The data table 222 is a table that stores data to be transferred. For example, the data table 222 stores a kana ID and data in association with each other as shown in FIG. That is, the data table 222 stores the correspondence between the user and the data, and stores the kana ID for identifying the user and the data in association with each other. The service providing server 200 may store the correspondence between the pseudonym ID and the data in the data table 222 from the beginning, or when the data download screen is generated (the information display terminal 20 in step S101 in FIG. 14 to be described later). For example, data on the other party of the call and information on the service providing server 200 are stored in the data table 222 in association with the pseudonym ID of the user of the SIP phone 30 as download data. Data and data of the service providing server 200 may be downloaded.

  Returning to FIG. 4, the control unit 230 is particularly closely related to the present invention, as shown in FIG. 4, as shown in FIG. 4, the arrival / departure association ID collection unit 231, the service provision control unit 232, and the data transfer unit 233. With.

  The arrival / departure association ID collection unit 231 collects the arrival / departure association ID issued by the session management server 100 for each information display terminal 20 that requests the provision of the service, and stores it in the Web session information management table 221. That is, the arrival / departure association ID collection unit 231 collects the arrival / departure association ID from the information display terminal 20 when receiving a service provision request from the information display terminal 20. As described above, since the connection ID between departures and arrivals is newly issued for each established session (that is, for each call), the connection ID collection unit 231 between arrivals and departures is received from each information display terminal 20. As a result of collecting the association IDs, the same arrival / departure association IDs are also collected from the two information display terminals 20. Further, the departure / arrival linking ID collection unit 231 according to the first embodiment collects the kana ID and the arrival / departure determination flag for each information display terminal 20 and stores them in the Web session information management table 221.

  The service provision control unit 232 specifies an arrival / departure association ID indicating that the service is linked from among a plurality of arrival / departure association IDs collected by the arrival / departure association ID collection unit 231, and identifies the identified arrival / departure association Service provision is controlled so that the services provided to each information display terminal 20 that is the collection source of the attached ID are linked.

  The data transfer unit 233 transfers data related to the service according to control by the session management server 100. That is, in the service providing system according to the first embodiment, the data transfer is performed in the session management server 100 by the “information requesting terminal of the request for the transfer request and the SIP phone that established the communication identified by the collected call session information. It is controlled by determining whether or not the information display terminal is used in pairs. In other words, the session management server 100 notifies the service providing server 200 of information such as which data is to be delivered and which information display terminal 20 should be delivered, and controls the service providing server 200. Thus, it can be said that it controls the entire data transfer. The data transfer unit 233 receives such control information from the session management server 100 and transfers data. Details of the processing contents by the data transfer unit 233 will be described in the description of processing procedures to be described later.

  Here, service provision by the service provision server 200 will be considered again. That is, the point that the service provision by the service provision server 200 is controlled based on the relationship between the information display terminals 20 is the same as the conventional service provision server that controls the service based on a pre-registered buddy list. However, it will be described how the service providing server 200 in the first embodiment grasps the “relationship between the information display terminals 20”.

  That is, the service providing server 200 according to the first embodiment, like the conventional service providing server, uses the relationship registered in the storage unit in advance (for example, the relationship registered in the buddy list) as “the relationship between the information display terminals 20”. Instead, the service provision control unit 232 grasps the “relationship between the information display terminals 20” using the arrival / departure association ID. In other words, the service providing server 200 has such a temporary communication relationship even when the relationship with the terminal that is the communication partner is temporary, such as the relationship between the SIP phones 30 that have established the same communication by SIP. Based on this, it is possible to provide a service associated with a temporary communication relationship by associating Web communications performed in each information display terminal 20 with each other.

  Note that, as in the first embodiment, when the first communication is communication in the process of establishing communication by SIP, the “relationship between the information display terminals 20” is an authenticated relationship by SIP. There is a meaning. That is, in SIP communication, Digest (digest) authentication is generally performed, and the fact that communication is established between SIP phones 30 by SIP means that the relationship between each information display terminal 20 has been authenticated. It shows that there is.

[HGW]
The HGW 10 shown in FIG. 5 is realized by providing each unit described below in a general-purpose gateway device or the like, and as particularly closely related to the present invention, as shown in FIG. An HTTP communication unit 11, a storage unit 12, and a control unit 13 are provided.

  The SIP communication unit / HTTP communication unit 11 includes general interfaces and libraries for SIP and HTTP communication, and communication between the SIP phone 30 and the SIP proxy, between the information display terminal 20 and the service providing server 200. Communication, communication between the HGW 10 and the session management server 100, communication between the HGW 10 and the SIP proxy, communication between the HGW 10 and the service providing server 200, and the like.

  The storage unit 12 stores information used for various controls in the control unit 13, and particularly includes a browser session information management table 12a as shown in FIG. 5 that is closely related to the present invention.

  The browser session information management table 12a stores in advance browser session information assigned to the subordinate information display terminal 20. For example, as shown in FIG. 9B, the browser session information management table 12a includes information (SIP phone ID) for uniquely identifying the SIP phone 30, and an information display terminal 20 used in combination with the SIP phone 30. Information for uniquely identifying (information display terminal ID) and browser session information for specifying the information display terminal 20 are stored in advance in association with each other. Further, the browser session information management table 12a stores Call-ID, From, To, an arrival / departure determination flag, and call information in association with each other. Of these pieces of information stored in the browser session information management table 12a, Call-ID, From, and To are, for example, collected and registered by the HGW 10. The arrival / departure determination flag is information generated by the HGW 10 itself from information included in communication established by SIP. Since the HGW 10 knows the SIP phone 30 connected to the subordinate, the HGW 10 can determine whether the corresponding call is an outgoing call or an incoming call.

  Returning to FIG. 5, the control unit 13 includes a service use control unit 13 a and a data transfer unit 13 b as shown in FIG. 5, particularly as closely related to the present invention.

  The service usage control unit 13a controls service usage by the information display terminal 20. The data transfer unit 13b transfers data related to the service according to control by the session management server 100.

[SIP phone]
The SIP phone 30 is realized by a general-purpose SIP phone, and particularly closely related to the present invention is an input unit 32, an output unit 33, and an input / output control I / F unit as shown in FIG. 34 and a SIP communication unit 31.

  Since both are the same as the general-purpose SIP phone 30, a brief description will be given. The input unit 32 inputs information used for the SIP phone 30, operation instructions for performing various processes, and the like using number keys, a microphone, and the like. The output unit 33 outputs the results of various processes by the SIP phone 30 and operation instructions for performing various processes to a display and a speaker. The input / output control I / F unit 34 includes the input unit 32, The information transfer between the output unit 33 and the SIP communication unit 31 is controlled. The SIP communication unit 31 includes a general interface and library for SIP, and the other SIP phone 30 (via the HGW 10). Send and receive information.

[Information display terminal]
The information display terminal 20 is realized by providing each unit described below in a general-purpose PC, an information home appliance, and the like, and particularly as closely related to the present invention, as shown in FIG. An output unit 23, an input / output control I / F unit 24, an HTTP communication unit 21, and a control unit 25.

  The input unit 22 inputs information used for the information display terminal 20 and operation instructions for performing various processes using a keyboard, a mouse, a remote controller, and the like, and the output unit 23 results from various processes performed by the information display terminal 20. In addition, an operation instruction for performing various processes is output to a display, a printer, or the like. The input / output control I / F unit 24 includes an input unit 22, an output unit 23, an HTTP communication unit 21, and a control unit 25. The HTTP communication unit 21 includes a general interface and library for HTTP communication, and transmits / receives information to / from the service providing server 200 via the HGW 10.

  As shown in FIG. 7, the control unit 25 includes a service use unit 25a and a delivery request unit 25b, particularly as closely related to the present invention.

  The service using unit 25a uses a service provided by the service providing server 200. Specifically, the service utilization unit 25a transmits a service provision start request for starting the provision of the service to the session management server 100, or transmits a service utilization request for requesting the use of the service to the service provision server 200. .

  The transfer request unit 25 b transfers data related to the service in accordance with control by the session management server 100. Specifically, the delivery request unit 25b transmits a delivery request for requesting delivery of data related to the service to the session management server 100.

[Procedure of processing by the service providing system according to the first embodiment]
Next, a processing procedure performed by the service providing system according to the first embodiment will be described with reference to FIGS. The processing by the service providing system according to the first embodiment is roughly divided into processing relating to service provision (corresponding to FIG. 1) and processing relating to data delivery (corresponding to FIG. 2), and there are various methods as processing relating to data delivery. is there. In the following, after describing an example of the procedure of processing related to service provision, processing related to data delivery will be described for each of various methods.

  FIG. 10 and FIG. 11 are sequence diagrams showing processing procedures relating to service provision, FIG. 12 is a diagram for explaining a delivery flag and a data storage source flag, and FIGS. FIG. 14 to FIG. 27-2 are sequence diagrams illustrating a procedure of processing relating to data transfer.

[Procedure for processing related to service provision]
As shown in FIG. 10, first, the SIP proxy controls communication by both SIP phones 30 (SIP communication unit 31), so that SIP communication in steps S1 to S3 is performed between both SIP phones 30 (SIP communication unit 31). As a result, communication (call) is established between both SIP phones 30 by SIP in step S4. Note that Digest authentication, REGISTER processing, and the like in SIP communication are not shown, but are performed prior to step S1 as in general SIP communication.

  When communication is established between both the SIP phones 30 by SIP, the HGW 10 (service use control unit 13a) acquires by collecting call session information uniquely identifying the communication established by SIP, A departure / arrival determination flag is acquired (step S5). For example, the HGW 10 (service usage control unit 13a) includes “Call-ID”, “From (SIP-URI)”, and “To (SIP-URI)” as call session information in the communication established by SIP. It is obtained by collecting information from the information that is collected. In addition, the HGW 10 (service use control unit 13a) itself generates an “incoming / outgoing determination flag” indicating whether both SIP phones 30 are on the outgoing side or the incoming side from information included in the communication established by the SIP. . The HGW 10 (service usage control unit 13a) issues a signed certificate of the HGW 10 for the acquired call session information and the like, and verifies the call session information by attaching the signed certificate to the call session information. It may be issued in a possible format.

  In the first embodiment, a method has been described in which the HGW collects call session information by itself and generates the arrival / departure determination flag by itself. However, the present invention is not limited to this method. For example, the HGW may collect call session information collected by the SIP proxy by receiving it from the SIP proxy and generate the arrival / departure determination flag by itself. Further, information such as call session information and a departure / arrival determination flag may be added to information notified from the SIP proxy.

  The point that the SIP proxy collects call session information will be briefly described. Since the SIP proxy is a device that controls communication established by SIP or communication established by SIP, It is common to manage information on sessions established by controlling. Therefore, when the SIP proxy establishes a session between the two SIP phones 30 under its own control, “Call-ID”, “From (SIP-URI)”, “To (SIP-URI) as call session information. ) ”Can be collected from the SIP signal of the established session. The SIP proxy then pushes the collected call session information to the HGW 10 that connects the originating SIP phone 30 and the HGW 10 that connects the terminating SIP phone 30 under the push type. Then, the HGW 10 can collect call session information by receiving the call session information collected by the SIP proxy from the SIP proxy.

  In this method, the SIP proxy can verify the call session information by issuing a SIP proxy signed certificate for the call session information and attaching the signed certificate to the call session information. It may be issued in a format.

  Returning to FIG. 10, subsequently, the HGW 10 (service use control unit 13a) collects the SIP phone ID, which is information for uniquely identifying the subordinate SIP phone 30, from the information included in the SIP communication (step S6). . The SIP phone ID is, for example, an extension number of the SIP phone 30. In the case of a configuration in which a plurality of SIP phones 30 are connected under the HGW 10, the SIP-URI is assigned to the HGW 10, and an extension number is assigned to each of the SIP phones 30 under the HGW 10.

  Then, the HGW 10 (service use control unit 13a) specifies the information display terminal 20 used in combination with the SIP phone 30 that established communication by SIP in step S4 (step S7). Specifically, the HGW 10 (service usage control unit 13a) first identifies the information display terminal 20 by searching the browser session information management table 12a using the SIP phone ID as a key, and the browser of the identified information display terminal 20 Information used in combination with the SIP phone 30 that establishes communication by SIP when the session information is compared with the browser session information of each of the plurality of information display terminals 20 that poll the HGW 10 and the browser session information matches. The display terminal 20 is specified.

  Then, the HGW 10 (service usage control unit 13a) issues an access destination change instruction to the information display terminal 20 specified in step S7. Specifically, a redirect instruction for instructing the specified information display terminal 20 to change the access destination to the URL of the session management server 100 is performed together with the call session information and the like (step S8). At this time, for the purpose of notifying the session management server 100 of the URL of the HGW 10, the HGW 10 (service usage control unit 13 a) in the first embodiment also includes the URL of the HGW 10 in the redirect instruction. That is, the URL of the HGW 10 included in the redirect instruction is transmitted to the session management server 100 by the information display terminal 20. In the first embodiment, the HGW 10 stores the URL of the session management server 100 in the storage unit in advance, so that a redirect instruction can be issued to change the access destination to the URL. As a result, the information display terminal 20 receives the redirect instruction and changes the access destination from the URL of the HGW 10 to the URL of the session management server 100.

  Then, the information display terminal 20 (service utilization unit 25a) is redirected, the connection destination is changed to the session management server 100, and a service start request for requesting to start the service is transmitted to the session management server 100 (step) S9). At this time, the information display terminal 20 (service utilization unit 25a) transmits call session information and the like and the URL of the HGW 10 to the session management server 100.

  On the other hand, when the session management server 100 (call session information collection unit 131) receives call session information or the like transmitted from the information display terminal 20, the session management server 100 (call session information collection unit 131) verifies the call session information or the like (step S10). That is, the session management server 100 (call session information collection unit 131) verifies that the call session information or the like is authentic information. For example, the session management server 100 (call session information collection unit 131) verifies that call session information or the like is authentic information by making an inquiry to the SIP proxy. When call session information or the like is received in a verifiable format with a signed certificate attached, the session management server 100 (call session information collection unit 131) verifies the signed certificate, for example. By doing so, it may be verified that the call session information or the like is authentic information.

  Subsequently, when the session management server 100 (call session information collection unit 131) confirms that the call session information or the like is authentic information as a result of the verification in step S10, the call session information or the like, the URL of the HGW 10, and The start time as call information is stored in the control session management table 123, the control session information is paid out, and the paid out control session information is stored in the control session management table 123 (step S11).

  Subsequently, the session management server 100 (call session information collection unit 131) confirms the services available to the information display terminal 20 (originating side) that has transmitted the service start request in the user contract service management table 121, and the contract service. ID is acquired (step S12).

  Then, the session management server 100 (call session information collection unit 131) generates a control page (step S13).

  Subsequently, the session management server 100 (call session information collection unit 131), with respect to the information display terminal 20, a connection destination monitoring function, control session information issued in step S11, and a control page generated in step S13. The contract service ID acquired in step S12 is transmitted (step S14). Here, the connection destination monitoring function is, for example, a Java (registered trademark) Script file and is installed in the information display terminal 20 to establish communication between the information display terminal 20 and the session management server 100. This is a function for monitoring the connection destination of the information display terminal 20.

  Then, the information display terminal 20 displays the control page transmitted from the session management server 100 from the web browser (step S15). Further, the information display terminal 20 installs the connection destination monitoring function transmitted from the session management server 100. Then, the connection destination monitoring function unit establishes communication with the session management server 100 and performs polling using the control session information transmitted from the session management server 100, thereby connecting the information display terminal 20. The previous URL is periodically transmitted to the session management server 100. On the other hand, the session management server 100 periodically monitors the connection destination of the information display terminal 20 that has issued the control session information by confirming the control session information used for polling (step S16).

  In addition, although the information display terminal 20 on the transmission side has been described so far, the same processing is performed on the information display terminal 20 on the reception side. In this way, the connection monitoring function is installed in both the outgoing-side information display terminal 20 and the incoming-side information display terminal 20, and communication is established between each connection destination monitoring function unit and the session management server 100.

  Subsequently, as shown in FIG. 11, when the user of the information display terminal 20 on the transmission side selects a service from the control page displayed on the Web browser (step S20), the information display terminal 20 (service The utilization unit 25a) transmits a service start request to the session management server 100 (step S21). At this time, the information display terminal 20 (service utilization unit 25a) transmits the contract service ID of the selected service to the session management server 100 using the control session information transmitted in step S14. The service start request may be transmitted via the connection destination monitoring function as shown in FIG. 11, or directly from the information display terminal 20 (service utilization unit 25a) without the connection destination monitoring function. It may be transmitted to the session management server 100.

  Then, the session management server 100 (departure / arrival linking ID issuing unit 132) confirms that the control session information transmitted from the information display terminal 20 is registered in the control session management table 123. (Step S22), issuing and linking ID and pseudonym ID are issued (Step S23). An implementation example in which the issued / arrival association ID and pseudonym ID are stored in the between-arrival / association ID table 124 will be described. For example, when the user of the information display terminal 20 on the transmission side selects a service from the control page (when the service is activated), the information display terminal 20 (service use unit 25a) identifies a service ID that identifies the selected service. Is transmitted to the session management server 100. At this time, the information display terminal 20 (service use unit 25a) uses the control session information. Then, the session management server 100 (departure / arrival linking ID issuing unit 132) refers to the control session management table 123 using the control session information used by the information display terminal 20 as a search key, and is transmitted from the information display terminal 20. It is confirmed that the control session information is registered in the control session management table 123. Then, the session management server 100 (departure / arrival association ID issuing unit 132) refers to the inter-departure association ID table 124 using the confirmed control session information. When the control session information is transmitted for the first time by the information display terminal 20 (service utilization unit 25a), the control session information should not yet be stored in the arrival / departure association ID table 124. For this reason, the session management server 100 (departure / arrival linking ID issuing unit 132) issues an arriving / departing linking ID and a pseudonym ID, and associates the issued arriving / departing linking ID and pseudonym ID with the control session information. It is stored in the between-arrival and arrival association ID table 124, and further the contract service ID and status (“in use”) are stored. On the other hand, if transmission of control session information by the information display terminal 20 (service utilization unit 25a) is not the first time, the control session information should be stored in the arrival / departure association ID table 124. For this reason, the session management server 100 (departure / arrival association ID issuing unit 132) issues a new arrival / departure association ID and a pseudonym ID, and has already stored the newly issued inter-departure association ID and pseudonym ID. Is stored in the between-arrival / incoming linking ID table 124 (the inbound / outbound linking ID and the pseudonym ID are updated), and further the contract service ID and status (“in use”) are stored.

  Here, the outgoing / incoming link ID is an ID used in the service providing server 200 to link the outgoing information display terminal 20 and the incoming information display terminal 20. Since communication established by SIP between the caller-side SIP phone 30 and the callee-side SIP phone 30 can be uniquely identified by call session information, the service providing server 200 uses the call session information. For example, the information display terminal 20 on the transmission side and the information display terminal 20 on the reception side can be associated with each other. However, in the case where it is considered that there is a security problem in disclosing the call session information to the service providing server 200 (for example, so that the service providing company does not know which users are accessing from each other) The call session information itself should not be disclosed to the service providing server 200. Therefore, in the first embodiment, in order to make call session information anonymous and capable of being associated, the session management server 100 issues an arrival / departure association ID in the form of a pseudonym. The pseudonym ID is an ID used in the service providing server 200 to identify a calling user or a receiving user. That is, since it is not possible to specify the user only by the ID between the arrival and departure, the information display terminal 20 and the service used by the information display terminal 20 for the purpose of specifying the user by the service provider For each combination, the session management server 100 issues.

  The session management server 100 (departure / arrival association ID issuing unit 132) provides the information display terminal 20 with the URL of the service providing server (obtained in step S12), the arrival / departure association ID, the kana ID, A departure / arrival determination flag is transmitted (step S24). In addition, the session management server 100 (departure / arrival association ID issuing unit 132) according to the first embodiment transmits the inter-departure association ID, the pseudonym ID, and the arrival / departure determination flag in a verifiable format. For example, the session management server 100 (departure / arrival association ID issuing unit 132) issues a signed certificate of the session management server 100 for the inter-arrival association ID, pseudonym ID, and arrival / departure determination flag, and the signed certificate is issued. Attaching between the arrival / departure association ID, the kana ID, and the arrival / departure determination flag, the issue / departure association ID, the pseudonym ID, and the arrival / departure determination flag are issued in a verifiable format. Note that the method is not limited to the method of attaching a signed certificate, and a method of not attaching a certificate may be used.

  On the other hand, the information display terminal 20 (service use unit 25a) connects to the URL transmitted from the session management server 100, and uses the service ID and pseudonym ID and the arrival / departure determination flag transmitted from the session management server 100 as the service. It transmits to the providing server 200 (step S25).

  Then, when the service providing server 200 (departure / arrival association ID collection unit 231) receives the arrival / departure association ID, the pseudonym ID, and the arrival / departure determination flag transmitted from the information display terminal 20, the service provision server 200 (departure / arrival association ID, kana) The ID and the arrival / departure determination flag are verified (step S26). In other words, the service providing server 200 (departure / arrival association ID collection unit 231) verifies the signed certificate attached to the arrival / departure association ID, the pseudonym ID, and the arrival / departure determination flag. It is verified that the kana ID and the arrival / departure determination flag are genuine information. In addition, as a method for verifying that the connection ID between departure and arrival, the pseudonym ID, and the arrival / departure determination flag are authentic information, a method of inquiring the session management server 100 may be used.

  Subsequently, when the service providing server 200 (departure / arrival association ID collection unit 231) confirms that the inter-departure / arrival association ID, the pseudonym ID, and the arrival / departure determination flag are authentic information as a result of the verification in step S26, the arrival / departure is performed. Information to be given to Web communication performed by the information display terminal 20 that has transmitted the association ID, pseudonym ID, and arrival / departure determination flag (Web communication performed by the information display terminal 20 with the service providing server 200 in order to receive service provision) The Web session information is paid out, the paid-out Web session information is stored in the Web session information management table 221, and the arrival / departure association ID, pseudonym ID, and arrival / departure determination flag are stored (step S27). Then, as shown in FIG. 9A, the Web session information management table 221 stores Web session information, an arrival / departure association ID, a pseudonym ID, and an arrival / departure determination flag. As described above, the service providing server 200 (service provision control unit 232) provides services if the service providing server 200 (departure / arrival linking ID collection unit 231) also stores a pseudonym ID and a departure / arrival determination flag. When providing the service, it is possible to control service provision based on the kana ID and the arrival / departure determination flag.

  Subsequently, the service providing server 200 (departure / arrival linking ID collection unit 231) generates a service providing screen (step S28), and displays the generated service providing screen together with the Web session information paid out in step S27 as the information display terminal 20. (Step S29).

  Then, a service providing screen is displayed on the Web browser of the information display terminal 20 (step S30).

  By the way, in the first embodiment, the session management server 100 (departure / arrival linking ID issuing unit 132) controls the information display terminal 20 on the caller side in response to the service start request in step S21 (or immediately) and also receives an incoming call. The information display terminal 20 on the side is also controlled. That is, although not shown in FIG. 11, the incoming-side information display terminal 20 also proceeds to step S31 by the same processing procedure as steps S21 to S23. Step S31 is processing corresponding to step S24 performed for the information display terminal 20 on the transmission side. The information display terminal 20 on the receiving side also performs the same processing procedure as steps S24 to S30, ie, steps S31 to S37. As a result, the service providing screen is also displayed on the Web browser of the information display terminal 20 on the receiving side. . For this reason, both the information display terminal 20 on the transmission side and the information display terminal 20 on the reception side immediately enter the state of using the service.

  In other words, the service providing server 200 (service providing control unit 232) pays out Web session information to the information display terminal 20 on the transmission side in step S27, and stores it in the Web session information management table 221 together with the connection ID between arrival and arrival. In step S34, the Web session information is paid out to the information display terminal 20 on the receiving side, and is stored in the Web session information management table 221 together with the connection ID between arrival and departure. Then, in step S38, the service providing server 200 (the service providing control unit 232), among the plurality of arrival / departure association IDs stored in the Web session information management table 221, each predetermined arrival / departure association ID is a service. , The services provided using each of the Web session information stored in association with each of the arrival / departure association IDs are controlled in association with each other (steps S39 to S42). ).

  For example, one information display terminal 20 (service utilization unit 25a) uploads image data to the service providing server 200 by web communication to which the web session information paid out in step S27 is attached (step S40), and the other It is assumed that the information display terminal 20 (service utilization unit 25a) is accessing the service providing server 200 through Web communication to which the Web session information paid out in step S34 is assigned (step S39). Then, the service providing server 200 (service providing control unit 232) controls the service so that the image data is transmitted to the other information display terminal 20, so that the image data is transmitted to the other information display terminal 20 (step S41). The other information display terminal 20 displays the image data on the output unit 23 (step S42).

  As described above, in the first embodiment, a method has been described in which the session management server 100 controls the information display terminal 20 on the receiving side simultaneously (or immediately) with control of the information display terminal 20 on the outgoing side. The invention is not limited to this. As another method, for example, when the information display terminal 20 on the receiving side selects the service itself and transmits a service start request to the session management server 100 in the same manner as the information display terminal 20 on the calling side, The present invention can be similarly applied to a method in which the management server 100 also controls the information display terminal 20 on the called side. Alternatively, for example, when the originating information display terminal 20 requests the session management server 100 to control the terminating information display terminal 20, the session management server 100 performs step S31 and subsequent steps. The present invention can be similarly applied to the method of starting the process.

[Processing related to data transfer]
First, in the service providing system according to the first embodiment, in a delivery request transmitted from the information display terminal 20 to the session management server 100 or the service providing server 200, a delivery destination flag for designating a delivery destination and storage of data to be delivered are stored. The data storage source flag that specifies the source is included. As a result, the data transfer control unit 134 of the session management server 100 and the data transfer unit 233 of the service providing server 200, as will be described later, according to the transfer destination flag and the data storage source flag included in the transfer request, Control is performed so that the data designated by the save source flag is delivered to the delivery destination designated by the delivery destination flag. For example, the delivery destination flag and the data storage source flag in the first embodiment are as shown in FIG.

  The “own HGW” shown in FIG. 12 is an HGW 10 installed at the same site as the information display terminal 20 that transmits the delivery request (the HGW 10 that controls the connection of the information display terminal 20 to the network, for example, the delivery request. If the information display terminal 20 to be transmitted is the information display terminal 20 on the transmission side, it means the HGW 10 on the transmission side as well. The “calling partner HGW” is an HGW 10 (SIP serving as a call partner) installed at the same site as the SIP phone 30 serving as a call partner of the SIP phone 30 used in combination with the information display terminal 20 that transmits a delivery request. It means the HGW 10 that controls the connection of the phone 30 to the network, for example, if the information display terminal 20 that transmits the delivery request is the information display terminal 20 on the calling side, the HGW 10 on the receiving side. In addition, “both HGWs” mean both the HGW 10 on the calling side and the HGW 10 on the receiving side (both the own HGW and the call partner HGW).

  The “service in use” is an ID that is used when the user designates a service that is currently being used. A service ID in which “status” in the arrival / departure association ID table 124 is “in use” is used. It corresponds to. “Service ID designation” refers to an ID used when a service is designated, and directly designates a service ID regardless of whether the service is being used. In this case, for example, the session management server 100 may confirm whether or not the service can be used by referring to the user contract service management table 121. In other words, for example, the session management server 100 may control data transfer only when it is confirmed that the session management server 100 is available.

  Here, in the service providing system according to the first embodiment, the data delivery control unit 134 of the session management server 100 and the data delivery unit 233 of the service providing server 200 recognize the delivery destination flag, the data storage source flag, and the service ID. It shall be. That is, the data delivery control unit 134 of the session management server 100 and the data delivery unit 233 of the service providing server 200 refer to the delivery destination flag and data storage source flag included in the delivery request, and from the contents of the referenced flag Identify which HGW or server the delivery destination is, or which HGW or server the data storage source is. Then, the data transfer control unit 134 of the session management server 100 and the data transfer unit 233 of the service providing server 200 control subsequent processing procedures so that data is transferred according to the identified data storage source and transfer destination flag. To do.

  In the service providing system according to the first embodiment, as shown in FIGS. 13-1 to 13-4, four types of methods are performed as processing related to data transfer. Specifically, the method 1 is a method in which data is transferred from the service providing server to the HGW by extension of a call based on information on the session managed by the session management server 100 (call session information, arrival / departure determination flag and call information). It is. Method 2 is a method of transferring data from the HGW to the service providing server by extension of the call based on information on the session managed by the session management server 100. Method 3 is a method of transferring data from the service providing server to the service providing server by extension of the call based on information on the session managed by the session management server 100. Method 4 is a method of transferring data from the HGW to the HGW by extension of the call based on information on the session managed by the session management server 100. In the following, first, a specific application example of each method will be described, and then a processing procedure of each method will be described in detail.

[Application example of method 1]
For example, according to method 1, as shown in FIG. 13A, based on information on a session managed by the session management server 100, data such as a store telephone number and menu information is converted into restaurant information by extension of a call. Can be delivered to the HGW from a service providing server (service providing server providing a concierge service).

  For example, in the case of the method 1-1 described later, it is assumed that the user A and the user B (the operator of the concierge service call center) are browsing the restaurant information sharing service site during a call. Note that the screens viewed by the user A and the user B are linked by being controlled by the service providing server. Here, it is assumed that the user A presses a “store information download button” (not shown) displayed on the screen. Then, a delivery request for requesting delivery of data is transmitted from the information display terminal of user A to the session management server. In this delivery request, the service providing server that provides the restaurant information providing service is used as the data storage source, and the local HGW is designated as the delivery destination.

  Then, the session management server determines whether or not the user A and the user B are in a call from information related to the session managed by the own device. The data delivery from the service providing server providing the service to the user A's HGW is controlled. For example, the session management server acquires a store telephone number, menu information, and the like from a service providing server that provides a restaurant information providing service, and transmits the acquired information to the user A's HGW together with browser session information. .

  In this way, since the session management server controls the data transfer based on the call established between the user A and the user B, the user A establishes the call established with the user B. It becomes possible to exchange data with the extension of. That is, since the data is exchanged based on the information on the session managed by the session management server, the user A does not need to perform a login operation for logging in to the session management server or the service providing server. , It is not necessary to input information on the HGW, etc., so that labor is reduced and there is no input mistake. Furthermore, since user A delivers data to the HGW only from a service providing server that can be used during a call, data is handed over to the HGW without permission from a non-subscribed service providing server that cannot be used by the user A. Data can be transferred with peace of mind. In addition, as will be described later, if the session management server manages history information related to data transfer, the user A knows when, with whom, and with which service, what data was transferred. For example, it is possible to accurately grasp the situation when a problem occurs, so that data can be exchanged safely and reliably. Since the store telephone number is stored in the HGW, the user A can easily make a call again without having to input the telephone number again in the telephone directory.

[Application example of method 2]
Further, for example, according to method 2, as shown in FIG. 13-2, based on information on a session managed by the session management server 100, the user's address information and the like are provided from the HGW by extension of the call. It can be passed to a service providing server that provides the service.

  For example, in accordance with the method 2-1 described later, it is assumed that the user A and the user B are browsing the site of the map information providing service during a call. Note that the screens viewed by the user A and the user B are linked by being controlled by the service providing server. Here, it is assumed that the user A and the user B press the “address information upload button” (not shown) displayed on the screen. Then, a transfer request for requesting data transfer is transmitted from both the user A and user B information display terminals to the session management server. In this delivery request, the HGW of the user A or the HGW of the user B is used as the data storage source, and the service providing server is designated as the delivery destination.

  Then, the session management server determines whether or not the user A and the user B are talking on the basis of information on the session managed by the own device. It controls the data transfer from the user B) HGW to the service providing server that provides the map information providing service. For example, address information is acquired from the HGW of the user A, and the acquired address information is transmitted to a service providing server that provides a map information providing service.

  In this way, since the session management server controls the data transfer based on the call established between the user A and the user B, the user A (user B) It is possible to exchange data by extending the call established with the person A). That is, since the data is exchanged based on the information on the session managed by the session management server, the user does not need to perform a login operation to log in to the session management server or the service providing server. There is no need to input information about the HGW, address information, etc., labor is reduced, and input errors are eliminated. Furthermore, since the user delivers data from the HGW only to the service providing server that can be used during a call, the HGW data is handed over to a non-subscribed service providing server that cannot be used by the user. This eliminates the risk of data transfer and enables safe data transfer. In addition, as will be described later, if the session management server manages the history information related to data transfer, the user knows when, with whom, and what data was transferred while using what service. For example, it is possible to accurately grasp the situation when any problem occurs, so that data can be exchanged safely and reliably. If address information is delivered from both users during a call, for example, the service providing server can determine the address located at the intermediate point of both users and provide the service.

  Further, for example, according to the method 2, as in the above example, based on the information about the session managed by the session management server 100, the telephone address is extended from the HGW to the mail order service (call center service) by extension of the call. Can be passed to a service providing server that provides

  For example, in the case of a method 2-1 described later, it is assumed that the user A and the user B (call service center operator) browse the site of the mail order service service during a call. Note that the screens viewed by the user A and the user B are linked by being controlled by the service providing server. Here, it is assumed that the user A presses an “address information upload button” (not shown) displayed on the screen. Then, a delivery request for requesting delivery of data is transmitted from the information display terminal of user A to the session management server. This delivery request is to designate user A's HGW as the data storage source and the service providing server as the delivery destination.

  Then, the session management server determines whether or not the user A and the user B are in a call from the information regarding the session managed by the own device. Controls data transfer from a service provider to a service providing server that provides mail order services. For example, the address information is acquired from the HGW of the user A, and the acquired address information is transmitted to a service providing server that provides a mail order service.

  In this way, since the session management server controls the data transfer based on the call established between the user A and the user B, the user A establishes the call established with the user B. It becomes possible to exchange data with the extension of. That is, since the data is exchanged based on the information on the session managed by the session management server, the user does not need to perform a login operation to log in to the session management server or the service providing server. There is no need to input information about the HGW, address information, etc., labor is reduced, and input errors are eliminated. Furthermore, since the user delivers data from the HGW only to the service providing server that can be used during a call, the HGW data is handed over to a non-subscribed service providing server that cannot be used by the user. This eliminates the risk of data transfer and enables safe data transfer. In addition, as will be described later, if the session management server manages the history information related to data transfer, the user knows when, with whom, and what data was transferred while using what service. For example, it is possible to accurately grasp the situation when any problem occurs, so that data can be exchanged safely and reliably.

[Application example of method 3]
Further, for example, according to the method 3, as shown in FIG. 13C, based on information related to a session managed by the session management server 100, a service providing that provides photo data and photo sharing service by extension of a call Transfer from the server to a service providing server that provides a photo print service is possible.

  For example, in accordance with a method 3-1 described later, it is assumed that the user A and the user B are browsing the photo sharing service site during a call. Note that the screens viewed by the user A and the user B are linked by being controlled by the service providing server. Here, it is assumed that the user A selects a predetermined photograph displayed on the screen and presses a “purchase button” displayed on the screen. Then, a delivery request for requesting delivery of data is transmitted from the information display terminal of user A to the session management server. This delivery request designates a service providing server that provides a photo sharing service as a data storage source and a service providing server that provides a photo print service as a delivery destination.

  Then, the session management server determines whether or not the user A and the user B are talking on the basis of the information on the session managed by the own device. It controls the delivery of photo data from the service providing server to the service providing server that provides the photo print service. For example, the session management server acquires the corresponding photo data by transmitting information identifying the selected photo to the service providing server being used by the user A and the user B, and acquires the corresponding photo data. The photograph data is transmitted to the service providing server designated as the delivery destination.

  In this way, since the session management server controls the data transfer based on the call established between the user A and the user B, the user A communicates with the user B (user A). It becomes possible to exchange data by extending the call established between the two. In other words, since the data is exchanged based on information on the session managed by the session management server, the user does not need to perform a login operation to log in to the session management server or the service providing server. Is reduced and there are no typing mistakes. Furthermore, since the user passes data only between service providing servers that can be used during a call, there is a risk that data may be passed without permission between service subscriber servers that cannot be used by the user. The data can be exchanged with peace of mind. In addition, as will be described later, if the session management server manages the history information related to data transfer, the user knows when, with whom, and what data was transferred while using what service. For example, it is possible to accurately grasp the situation when any problem occurs, so that data can be exchanged safely and reliably. In this application example, for example, a service providing server that provides a photo print service stores the address information of the user A in advance as shown in FIG. Therefore, the service providing server that provides the photo print service prints the photo data transmitted from the service providing server that provides the photo sharing service, and delivers the photo data to the home of the user A using the address information of the user A. can do.

[Application example of method 4]
Further, for example, according to method 4, as shown in FIG. 13-4, based on the information about the session managed by the session management server 100, the extension of the call, photo data, etc., between the HGWs of the users who are calling Can be handed over.

  For example, in accordance with a method 4-1 described later, it is assumed that the user A and the user B are browsing a photo sharing service site during a call. Note that the screens viewed by the user A and the user B are linked by being controlled by the service providing server. Here, it is assumed that the user B selects a predetermined photograph displayed on the screen and presses a “send button” displayed on the screen. Then, a delivery request for requesting delivery of data is transmitted from the information display terminal of user B to the session management server. This delivery request is to designate the user A's HGW as the data storage source and the user B's HGW as the delivery destination.

  Then, the session management server determines whether or not the user A and the user B are talking on the basis of the information on the session managed by the own device. The delivery of photo data from the user A's HGW to the user B's HGW is controlled from the provided service providing server. For example, the session management server acquires corresponding photo data from the user A's HGW, and transmits the acquired photo data to the user B's HGW designated as the delivery destination.

  In this way, since the session management server controls the data transfer based on the call established between the user A and the user B, the user A communicates with the user B (user A). It becomes possible to exchange data by extending the call established between the two. That is, since the data is exchanged based on the information on the session managed by the session management server, the user does not need to perform a login operation to log in to the session management server or the service providing server. There is no need to input information on HGW, etc., labor is reduced, and there are no input mistakes. Furthermore, since the user delivers data only to and from the other party, there is no possibility that the HGW data will be handed over without permission, and the data can be delivered safely. In addition, as will be described later, if the session management server manages the history information related to data transfer, the user knows when, with whom, and what data was transferred while using what service. For example, it is possible to accurately grasp the situation when any problem occurs, so that data can be exchanged safely and reliably.

  Hereinafter, method 1 to method 4 will be described in order. In any of the methods 1 to 4, the user of the service providing system renews the details of the delivery destination information and data storage source information (for example, URL, user ID, telephone number, etc.) in detail. Without being disclosed in 100, it is possible to realize data transfer only by transmitting a transfer request designating a transfer destination flag or a data storage source flag. Further, the HGW 10 can make the HTTP access from the external network non-permitted, and it is not necessary to open the HTTP server to the external network. In any of methods 1 to 4, the session management server 100 appropriately stores and stores status information related to data transfer, so that history information on data transfer is managed and data transfer is ensured. can do.

[Method 1]
As described above, the method 1 is a method of transferring data from the service providing server 200 to the HGW 10 through the control of the session management server 100 based on the determination that the user is currently in a call. As shown in FIGS. 14 to 18, the method 1 includes, for example, methods 1-1 to 1-5. The difference between the methods will be briefly described. First, in the methods 1-1 to 1-3, a transfer request for requesting data transfer is transmitted to the session management server 100. Method 1-4 is a method in which a delivery request is transmitted to the service providing server 200. As described above, the service providing system according to the first embodiment is a user who is actually in a call regardless of whether the delivery request is transmitted to the session management server 100 or the service providing server 200. Based on the determination that there is, data can be transferred from the service providing server 200 to the HGW 10.

  Further, as a difference between the methods 1-1 to 1-3, the method 1-1 and the method 1-2 are such that the session management server 100 directly transmits / receives data to be transferred (session). In contrast to the method 1-3, the management server 100 acquires the data itself to be transferred once and sets the acquired data as a transmission / reception target. In contrast, in the method 1-3, the session management server 100 transfers the data. Although it is controlled, it does not directly send or receive data to be transferred. For this reason, for example, when method 1-3 is adopted when data with high confidentiality is to be transferred, data is not acquired by session management server 100, and method 1-1 or method 1- Compared to 2, security can be further improved. In addition, since it is not necessary for the session management server 100 to hold such data, the load on the session management server 100 can be reduced. Furthermore, the session management server 100 can grasp that data has been transferred between users without holding such data. Further, as a difference between the method 1-1 and the method 1-2, as will be described later, by adopting the method 1-2, a home network (network of HGW 10 or lower) compared to the method 1-1. The information display terminal 20 does not need to upload data, and the information display terminal 20 having a low capability can be handled.

  In addition, the scheme 1-1 to the scheme 1-4 are schemes performed without assuming data encryption (although the scheme 1-1 to the scheme 1-4 can encrypt the communication channel). The method 1-5 is a method of encrypting data and then delivering it. For this reason, when method 1-5 is combined with method 1-1 or method 1-2, even if method 1-1 or method 1-2 is used, for example, data with high confidentiality is to be transferred. Can be applied to. That is, as described above, the method 1-1 and the method 1-2 are methods in which the session management server 100 directly transmits / receives data to be transferred, but the method 1-5 encrypts data. Therefore, if the data cannot be decrypted, the session management server 100 does not substantially acquire the data and can further improve the security. Further, in the method 1-5, if the session management server 100 later acquires the key information of both users, it is possible to verify the validity of the data to be delivered. For example, when data transmission from the session management server 100 to the HGW 10 is performed by the redirect method as in the method 1-1, the external communication port of the HGW 10 does not have to be disclosed to the outside, and the security is further improved. It becomes possible to do. This is a common effect when the redirect method is adopted also in methods other than the method 1-1.

[Method 1-1]
The method 1-1 will be described with reference to FIG. As shown in FIG. 14, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S <b> 101). For example, in steps S30 and S37 of FIG. 11, the service providing screen provided by the service providing server 200 is displayed on the Web browser of the information display terminal 20. For this reason, the user on the outgoing side and the user on the incoming side are in a situation where the site provided by the service providing server 200 can be browsed using the information display terminal 20 during a call. Further, the service providing screens that are viewed by the calling user and the receiving user are linked by being controlled by the service providing server 200. Here, for example, a user on the transmission side presses a delivery button of the browser displayed on the screen.

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (Step S102). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred. Here, the data transfer will be explained. As the data to be transferred, for example, when the request source of the transfer request is the data to be transferred or the call partner of the request source has the disclosure right. There are cases where the data that the service provider has is subject to delivery, or data that the service providing server has the disclosure right is subject to delivery. Note that the disclosure right is an authority to determine whether or not the data that is the target of the delivery request may be disclosed.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. In addition, the service ID “1001” is included to request that the data related to the service “1001” provided by the service providing server 200 be transferred to the own HGW 10. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. Whether or not (step S103). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  As a method for confirming whether or not the user is actually in a call, in addition to the method for determining by the above-described control session information, a method for determining by the link ID between arrivals and departures (provided for the delivery request) A method of referring to the control session management table 123 using the arrival / departure linking ID), a method of determining by the pseudonym ID (a method of referring to the control session management table 123 using the pseudonym ID assigned to the delivery request) There are various methods such as a method of determining by using an ID between a departure and arrival and a pseudonym ID (a method of referencing the control session management table 123 using the ID between a departure and arrival and an ID assigned to a delivery request). . Note that the various methods can be applied as described above, and the same applies to the other methods 1 to 4 described below.

  In the first embodiment, the user of the information display terminal 20 is actually calling as a method for determining whether or not the information display terminal 20 is used in combination with the SIP phone 30 that has established communication by SIP. Although the method for determining whether the user is a medium user has been described, the present invention is not limited to this. For example, when it is sufficient to determine that the user has made a call at least in the past, the delivery request determination unit 133 may confirm that the control session information “1111111111” is stored. In this case, however, it is assumed that the session management server 100 manages the past call history. That is, it is assumed that the session management server 100 stores a record in which the end time of the call information is recorded as history information in the control session management table 123 for a certain period. In this regard, the same applies to other methods 1 to 4 described below.

  Further, as illustrated in FIG. 14, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S <b> 102. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, since the data storage source flag is “5”, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request, The user identification information “0311111111” is acquired from the call session information and the arrival / departure determination flag associated with the control session information “1111111111”. Next, the delivery request determination unit 133 refers to the user contract service management table 121 using the acquired user identification information “0311111111”, and confirms the contract service ID associated with the user identification information “0311111111”. That is, it is confirmed whether or not “1001” is associated as the contract service ID. Then, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information, and uses the between arrival / departure association ID and the pseudonym ID acquired from the between arrival / departure association ID table 124. Further, the data storage source flag “5” and the service ID “1001” included in the delivery request are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S102 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S104 to S110 according to the transfer request.

  First, the data transfer control unit 134 acquires data to be transferred. Specifically, the data delivery control unit 134 refers to the contract service information table 122 using the service ID “1001” included in the delivery request. Then, the data delivery control unit 134 searches the URL “http://example1.co.jp” of the service providing server stored in association with the contract service ID “1001”, and the pseudonym ID “kamei1111” and the arrival / departure A data acquisition request including the interlink ID “lin3333” is transmitted to the URL “http://example1.co.jp” (step S104).

  Then, the data delivery unit 233 of the service providing server 200 refers to the data table 222 using the kana ID “kamei1111” included in the data acquisition request, and stores the data stored in association with the kana ID “kamei1111”. Is acquired (step S105). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data transfer unit 233 transmits the data acquired in step S105 to the session management server 100 as a response to the data acquisition request transmitted from the session management server 100 (step S106).

  Next, the data transfer control unit 134 refers to the data transfer table 125, and from the transfer destination flag “1” stored in the transfer destination information, the data transfer destination is the HGW 10 on the transmission side that is the same as the information display terminal 20. The control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Subsequently, the data transfer control unit 134 transmits the data acquired in step S106 and the call session information “ui123456789” to the information display terminal 20 that has requested the transfer request, and refers to the control session management table 123. By transmitting the URL “http://192.168.1.10/returm” of the HGW acquired in this way, a redirect instruction to the HGW 10 is performed (step S107). Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. Further, as will be described below, the HGW 10 determines whether or not the data to be delivered is data transmitted from a reliable device, and is certainly delivered under the control of the session management server 100. The purpose is to verify whether the data is correct. The HGW 10 also has an object of grasping which call corresponds to which call the HGW 10 grasps about the transferred data.

  Further, as illustrated in FIG. 14, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the data in step S <b> 107. For example, the delivery request determination unit 133 stores the time information (date and time) of data transmission in step S107 in “data transmission completed” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S108). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  When the data transfer unit 13b succeeds in verifying the call session information in step S108, the data transfer unit 13b stores the data received in step S107 in the storage unit 12 (step S109).

  Thereafter, the data transfer unit 13b transmits information that can verify the correspondence between step S107 and step S110 to the session management server 100, thereby notifying the result as a response to step S107 (step S110). ). For example, the data transfer unit 13b transmits the call session information acquired in step S107 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S107, the random number may be transmitted in step S110.

  Further, as illustrated in FIG. 14, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S <b> 110. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S110 in the “delivery completed” status information.

[Method 1-2]
The method 1-2 will be described with reference to FIG. As shown in FIG. 15, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S201).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S202). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. In addition, the service ID “1001” is included to request that the data related to the service “1001” provided by the service providing server 200 be transferred to the own HGW 10. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S203). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  As shown in FIG. 15, the delivery request determination unit 133 of the session management server 100 stores the status information in the data delivery table 125 after accepting the delivery request in step S202. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, since the data storage source flag is “5”, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request, The user identification information “0311111111” is acquired from the call session information and the arrival / departure determination flag associated with the control session information “1111111111”. Next, the delivery request determination unit 133 refers to the user contract service management table 121 using the acquired user identification information “0311111111”, and confirms the contract service ID associated with the user identification information “0311111111”. That is, it is confirmed whether or not “1001” is associated as the contract service ID. Then, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information, and uses the between arrival / departure association ID and the pseudonym ID acquired from the between arrival / departure association ID table 124. Further, the data storage source flag “5” and the service ID “1001” included in the delivery request are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information (such as the date and time when the delivery request is received) related to the delivery request received in step S202 in “request received” of the status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S204 to S214 in accordance with the transfer request.

  Specifically, the data transfer control unit 134 first issues an access key (step S204). The data transfer control unit 134 stores the issued access key in a record stored in the data transfer table 125 in association with the control session information “1111111111”. Here, the access key is identification information for uniquely specifying the delivery request, such as a random number or a character string. That is, the access key is for managing the correspondence between the request and the data in order to determine which data should be downloaded in response to the data download request from the HGW 10. The access key is also used to determine whether the access is from the HGW 10 permitted by the session management server 100. For example, when issuing the access key, the data delivery control unit 134 associates the IP address (such as a prefix in the case of IPv6) of the information display terminal 20 that has transmitted the delivery request in step S202 with the issued access key. Remember. Then, as will be described later, when the access key is received from the HGW 10 again, the correspondence between the access key and the IP address is determined, and whether the access is from the HGW 10 during a call when the IP address matches ( In the case of data delivery based on history information, it is possible to determine whether or not the access is from the HGW 10 that has made a call in the past. Note that the entity that transmits the delivery request in step S202 is the information display terminal 20, and the entity that transmits the access key in step S207 is the HGW 10. However, since the address conversion is performed in the HGW 10, the IP addresses of the two match. I think that.

  Next, the data transfer control unit 134 refers to the data transfer table 125, and from the transfer destination flag “1” stored in the transfer destination information, the data transfer destination is the HGW 10 on the transmission side that is the same as the information display terminal 20. The control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Subsequently, the data transfer control unit 134 transmits the access key issued in step S204 and the call session information “ui123456789” to the information display terminal 20 that is the request source of the transfer request, and also stores the control session management table 123. By transmitting the URL “http://192.168.1.10/returm” of the HGW acquired by reference, a redirect instruction to the HGW 10 is performed (step S205). Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. In addition, the HGW 10 determines whether or not the data to be delivered is data transmitted from a reliable device, and whether or not the data has been delivered under the control of the session management server 100. There is also the purpose of verifying. The HGW 10 also has an object of grasping which call corresponds to which call the HGW 10 grasps about the transferred data.

  As shown in FIG. 15, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the access key in step S205. For example, the delivery request determination unit 133 stores the time information (date and time) of access key transmission in step S205 in “access key transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S206). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  When the data transfer unit 13b succeeds in verifying the call session information in step S206, the data transfer unit 13b transmits the access key received in step S205 to the session management server 100 (step S207).

  On the other hand, the data transfer control unit 134 of the session management server 100 verifies the access key (step S208). Specifically, the data transfer control unit 134 refers to the data transfer table 125 using the access key, and acquires the service ID “1001” held in association with the access key. As described above, when the data transfer control unit 134 stores the IP address of the information display terminal 20 and the access key in association with each other in step S204, the data transfer control unit 134 stores the access key. Whether the access is from the HGW 10 during a call with a matching relationship with the IP address of the HGW 10 that has been transmitted (in the case of data transfer based on history information, whether the access is from the HGW 10 that has made a call in the past) Can be determined.

  Then, the data delivery control unit 134 refers to the contract service information table 122 using the service ID “1001”. Then, the data delivery control unit 134 searches the URL “http://example1.co.jp” of the service providing server stored in association with the contract service ID “1001”, and the pseudonym ID “kamei1111” and the arrival / departure A data acquisition request including the interlinking ID “lin3333” is transmitted to the URL “http://example1.co.jp” (step S209).

  Then, the data delivery unit 233 of the service providing server 200 refers to the data table 222 using the kana ID “kamei1111” included in the data acquisition request, and stores the data stored in association with the kana ID “kamei1111”. Is acquired (step S210). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data delivery unit 233 transmits the data acquired in step S210 to the session management server 100 as a response to the data acquisition request transmitted from the session management server 100 (step S211).

  Next, the data delivery control unit 134 transmits the data acquired in step S210 to the source HGW 10 that transmitted the access key in step S207 (step S212). The access key is stored in the data delivery table 125 in association with the control session information. Therefore, the data transfer control unit 134 acquires the control session information by referring to the data transfer table 125 using the access key, and refers to the control session management table 123 using the acquired control session information. Thus, the URL of the source HGW 10 that transmitted the access key can be acquired.

  Further, as shown in FIG. 15, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the data in step S212. For example, the delivery request determination unit 133 stores the time information (date and time) of data transmission in step S212 in “data transmission completed” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 stores the data in the storage unit 12 (step S213), and then the data transfer unit 13b stores information that can verify the correspondence between step S205 and step S214 in the session. By transmitting to the management server 100, the result is notified as a response to step S205 (step S214). For example, the data transfer unit 13b transmits the call session information and the access key acquired in step S205 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with call session information or data in step S205 or step S212, the random number may be transmitted in step S214.

  Further, as shown in FIG. 15, the delivery request determination unit 133 of the session management server 100 stores the status information in the data delivery table 125 after receiving the result notification in step S214. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S214 in the “delivery completed” status information.

[Effect of Method 1-2]
As described above, according to method 1-2, it is possible to further reduce the load on the home network (network of HGW 10 or lower) as compared with method 1-1, and the information display terminal 20 can transmit data. Can be handled even by the information display terminal 20 having a low capability. That is, in method 1-1, when data is transferred to the HGW 10, the data is transferred from the session management server 100 to the information display terminal 20, and then the data is transferred from the information display terminal 20 to the HGW 10, so that the data size is large. Until the data was transferred to the HGW 10, it was necessary to go through the home network twice and traffic increased. On the other hand, in the method 1-2, only the access key is notified to the HGW 10 and the data is downloaded to the HGW 10, so that the data is moved only between the HGW 10 and the session management server 100. Compared to 1, it is possible to reduce the amount of traffic in the home network. Further, since the information display terminal 20 does not need to upload data, the information display terminal 20 having a low capability can be supported. In addition, the effect of method 1-1 is inherited as it is.

[Method 1-3]
The method 1-3 will be described with reference to FIG. As shown in FIG. 16, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S301).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S302). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. In addition, the service ID “1001” is included to request that the data related to the service “1001” provided by the service providing server 200 be transferred to the own HGW 10. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. Whether or not (step S303). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Also, as illustrated in FIG. 16, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S302. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, since the data storage source flag is “5”, the delivery request determination unit 133 refers to the control session management table 123 and calls session information associated with the control session information “1111111111”. Also, the user identification information “0311111111” is acquired from the arrival / departure determination flag. Next, the delivery request determination unit 133 refers to the user contract service management table 121 using the acquired user identification information “0311111111”, and confirms the contract service ID associated with the user identification information “0311111111”. That is, it is confirmed whether or not “1001” is associated as the contract service ID. Then, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information, and uses the between arrival / departure association ID and the pseudonym ID acquired from the between arrival / departure association ID table 124. Further, the data storage source flag “5” and the service ID “1001” included in the delivery request are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S302 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S304 to S314 in accordance with the transfer request.

  First, the data delivery control unit 134 refers to the contract service information table 122 using the service ID “1001” included in the delivery request. Then, the data delivery control unit 134 searches the URL “http://example1.co.jp” of the service providing server stored in association with the contract service ID “1001”, and sends an access key acquisition request to the URL “ It transmits to “http://example1.co.jp” (step S304).

  Then, the data delivery unit 233 of the service providing server 200 issues an access key (step S305). Here, the access key is identification information for uniquely specifying the delivery request, such as a random number or a character string.

  Then, the data transfer unit 233 transmits the access key issued in step S305 to the session management server 100 as a response to the access key acquisition request transmitted from the session management server 100 (step S306).

  Subsequently, the data transfer control unit 134 stores the access key received in step S306 in a record stored in the data transfer table 125 in association with the control session information “1111111111”. In addition, the data transfer control unit 134 transmits the access key, the URL of the service providing server 200 and the call session information “ui123456789” received in step S306 to the information display terminal 20 that has requested the transfer request, and performs control. By transmitting the HGW URL “http://192.168.1.10/returm” acquired with reference to the session management table 123, a redirection instruction to the HGW 10 is performed (step S307). At this time, the data transfer control unit 134 refers to the control session management table 123 using the control session information “1111111111”, and acquires the URL of the HGW 10. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. In addition, the HGW 10 determines whether or not the data to be delivered is data transmitted from a reliable device, and whether or not the data has been delivered under the control of the session management server 100. There is also the purpose of verifying. The HGW 10 also has an object of grasping which call corresponds to which call the HGW 10 grasps about the transferred data.

  Also, as illustrated in FIG. 16, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the access key in step S307. For example, the delivery request determination unit 133 stores the time information (date and time) of access key transmission in step S307 in “access key transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S308). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  If the data transfer unit 13b succeeds in verifying the call session information in step S308, the data transfer unit 13b transmits the access key received in step S307 to the service providing server 200 together with the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333”. (Step S309).

  Then, the data delivery unit 233 of the service providing server 200 verifies the received access key (step S310), refers to the data table 222 using the kana ID “kamei 1111” received together with the access key, and uses the kana ID “kamei 1111”. The data stored in association with is acquired (step S311). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data transfer unit 233 transmits the data acquired in step S311 to the HGW 10 as a response to the access key transmitted from the HGW 10 (step S312).

  On the other hand, the data transfer unit 13b of the HGW 10 stores the data in the storage unit 12 (step S313), and thereafter, the data transfer unit 13b stores information that can verify the correspondence between step S307 and step S314 as a session. By transmitting to the management server 100, the result is notified as a response to step S307 (step S314). For example, the data transfer unit 13b transmits the call session information and the access key acquired in step S307 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with call session information or data in step S307 or step S312, the random number may be transmitted in step S314.

  Also, as illustrated in FIG. 16, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S <b> 314. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S314 in the “delivery completed” status information.

[Method 1-4]
Method 1-4 will be described with reference to FIG. As shown in FIG. 17, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S401).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the Web session information is added to the service providing server 200 (Step S402). At this time, the delivery request unit 25b includes the delivery destination flag in the delivery request.

  For example, the delivery request unit 25b includes “1” (own HGW) as the delivery destination flag in the delivery request to which the Web session information “aaaaaaaaaaaa” is added, and thus relates to the service “1001” provided by the service providing server 200. Requesting the data to be transferred to the own HGW 10.

  On the other hand, the data delivery unit 233 of the service providing server 200 issues an access key (step S403). Here, the access key is identification information for uniquely specifying the delivery request, such as a random number or a character string.

  For example, the data transfer unit 233 refers to the Web session information management table 221 using the Web session information “aaaaaaaaaaaa”, stores the arrival / departure link ID “lin3333” stored in association with the Web session information “aaaaaaaaa”, and The pseudonym ID “kamei1111” is acquired. Then, the data transfer unit 233 holds the access key in the Web session information management table 221.

  Next, the data transfer unit 233 redirects the transfer request received in step S402 to the session management server 100 with the access key issued in step S403 attached (step S404). The data transfer unit 233 transfers the transfer request including the data storage source flag “5”, the service ID “1001”, and the pseudonym ID in addition to the transfer destination flag already included. Further, the transfer of the delivery request in step S404 may be a direct transfer method using HTTP communication instead of the redirect method.

  As shown in FIG. 17, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer of the transfer request in step S <b> 404. For example, the delivery request determination unit 133 first refers to the departure / arrival association ID table 124 using the kana ID “kamei1111” given to the delivery request, and stores the control request stored in association with the kana ID “kamei1111”. Session information “1111111111” is acquired. Further, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111”, and records “control control information” for the record stored in association with the control session information “1111111111”. Information from “session information” to “departure / departure determination flag” is stored in the data delivery table 125.

  Next, since the data storage source flag is “5”, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request, The user identification information “0311111111” is acquired from the call session information and the arrival / departure determination flag associated with the control session information “1111111111”. Next, the delivery request determination unit 133 refers to the user contract service management table 121 using the acquired user identification information “0311111111”, and confirms the contract service ID associated with the user identification information “0311111111”. That is, it is confirmed whether or not “1001” is associated as the contract service ID. Then, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information, and stores the arrival / departure association ID acquired from the arrival / departure association ID table 124. Further, the data storage source flag “5” and the service ID “1001” included in the delivery request are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the transfer of the delivery request accepted in step S404 (such as the date and time when the delivery request was received) in the “request acceptance” status information.

  When the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. Is determined (step S405). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S406 to S413 in accordance with the transfer request.

  First, the data transfer control unit 134 stores the access key received in step S404 in a record stored in the data transfer table 125 in association with the control session information “1111111111”. Further, the data transfer control unit 134 transmits the access key received in step S404, the URL of the service providing server 200 and the call session information “ui123456789” to the information display terminal 20 that has requested the transfer request, and performs control. By transmitting the URL “http://192.168.1.10/returm” of the HGW obtained by referring to the session management table 123, a redirect instruction to the HGW 10 is performed (step S406). At this time, the data transfer control unit 134 refers to the control session management table 123 using the control session information “1111111111”, and acquires the URL of the HGW 10. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. In addition, the HGW 10 determines whether or not the data to be delivered is data transmitted from a reliable device, and whether or not the data has been delivered under the control of the session management server 100. There is also the purpose of verifying. The HGW 10 also has an object of grasping which call corresponds to which call the HGW 10 grasps about the transferred data.

  In addition, as illustrated in FIG. 17, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the access key in step S <b> 406. For example, the delivery request determination unit 133 stores the time information (date and time) of access key transmission in step S406 in “access key transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S407). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S407, the data transfer unit 13b transmits the access key received in step S406 to the service providing server 200 together with the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333”. (Step S408).

  Then, the data delivery unit 233 of the service providing server 200 verifies the received access key (step S409), refers to the data table 222 using the kana ID “kamei1111” received together with the access key, and uses the kana ID “kamei1111”. The data stored in association with is acquired (step S410). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data transfer unit 233 transmits the data acquired in step S410 to the HGW 10 as a response to the access key transmitted from the HGW 10 (step S411).

  On the other hand, the data transfer unit 13b of the HGW 10 stores the data in the storage unit 12 (step S412), and then the data transfer unit 13b stores information that can verify the correspondence between step S406 and step S413 in the session. By transmitting to the management server 100, the result is notified as a response to step S406 (step S413). For example, the data transfer unit 13b transmits the call session information and the access key acquired in step S406 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with call session information or data in step S406 or step S411, the random number may be transmitted in step S413.

  In addition, as illustrated in FIG. 17, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S413. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S413 in the “delivery completed” status information.

[Method 1-5]
Method 1-5 will be described with reference to FIG. As shown in FIG. 18, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S501).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (Step S502). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred. Here, the data transfer will be explained. As the data to be transferred, for example, when the request source of the transfer request is the data to be transferred or the call partner of the request source has the disclosure right. There are cases where the data that the service provider has is subject to delivery, or data that the service providing server has the disclosure right is subject to delivery.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. In addition, the service ID “1001” is included to request that the data related to the service “1001” provided by the service providing server 200 be transferred to the own HGW 10. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S503). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  As shown in FIG. 18, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S502. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, since the data storage source flag is “5”, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request, The user identification information “0311111111” is acquired from the call session information and the arrival / departure determination flag associated with the control session information “1111111111”. Next, the delivery request determination unit 133 refers to the user contract service management table 121 using the acquired user identification information “0311111111”, and confirms the contract service ID associated with the user identification information “0311111111”. That is, it is confirmed whether or not “1001” is associated as the contract service ID. Then, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information, and uses the between arrival / departure association ID and the pseudonym ID acquired from the between arrival / departure association ID table 124. Further, the data storage source flag “5” and the service ID “1001” included in the delivery request are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information (such as the date and time when the delivery request is received) related to the delivery request received in step S502 in “request received” of the status information.

  Subsequently, the data transfer control unit 134 controls data transfer shown in step S504 and subsequent steps according to the transfer request.

  Specifically, the data transfer control unit 134 refers to the data transfer table 125, and from the transfer destination flag “1” stored in the transfer destination information, the data transfer destination is the same as that of the information display terminal 20 on the transmission side. The HGW 10 is identified, and the control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Subsequently, the data transfer control unit 134 transmits a public key request and call session information “ui123456789” for requesting transmission of a public key to the information display terminal 20 that is the request source of the transfer request, and for control. By transmitting the URL “http://192.168.1.10/returm” of the HGW acquired with reference to the session management table 123, a redirection instruction to the HGW 10 is performed (step S504). Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. Further, as will be described below, the HGW 10 determines whether or not the data to be delivered is data transmitted from a reliable device, and is certainly delivered under the control of the session management server 100. The purpose is to verify whether the data is correct. The HGW 10 also has an object of grasping which call corresponds to which call the HGW 10 grasps about the transferred data.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S505). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, the data transfer unit 13b of the HGW 10 acquires the public key and the secret key stored in the storage unit (Step S506). A public key and a secret key may be generated each time.

  Then, the data transfer unit 13b transmits the public key acquired in step S506 to the session management server 100 by redirection (step S507). At this time, the data transfer unit 13b transmits to the session management server 100 information that can verify the correspondence between step S504 and step S507. For example, the data transfer unit 13b transmits the call session information acquired in step S504 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S504, the random number may be transmitted in step S507.

  Then, the data transfer control unit 134 of the session management server 100 refers to the data transfer table 125 using the call session information received in step S507, and stores data storage source information (corresponding to the call session information) ( Data storage source flag “5” and service ID “1001”) are acquired (step S508). Further, the data delivery control unit 134 refers to the contract service information table 122 using the data storage source flag “5” and the service ID “1001”. Then, the data delivery control unit 134 searches the URL “http://example1.co.jp” of the service providing server stored in association with the contract service ID “1001”, and the public key and pseudonym ID “kamei1111”. ] And a data acquisition request including the arrival / departure association ID “lin3333” is transmitted to the URL “http://example1.co.jp” (step S509).

  Then, the data delivery unit 233 of the service providing server 200 refers to the data table 222 using the kana ID “kamei1111” included in the data acquisition request, and stores the data stored in association with the kana ID “kamei1111”. Is acquired (step S510). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data delivery unit 233 of the service providing server 200 encrypts the data with the public key received in step S509 (step S511).

  As for the subsequent processing procedure, any of Step 1-1 in Step 1-1 of Method 1-1, Step S212 in Step 1-2 of Method 1-2, and Step S305 in Step 1-3 of Mode 1-3 may be combined. At this time, since the data is encrypted, the decryption processing is performed in the processing procedure of the method 1-2 or the method 1-2. For example, in the case of method 1-1, before storing data in step S109, the HGW 10 decrypts the encrypted data using the private key acquired in step S506, and stores the decrypted data. . Further, for example, in the case of method 1-2, before storing the data in step S213, the HGW 10 decrypts the encrypted data using the private key acquired in step S506, and stores the decrypted data. Store. Further, for example, in the case of method 1-3, before storing data in step S313, the HGW 10 decrypts the encrypted data using the secret key acquired in step S506, and stores the decrypted data. Store.

[Method 2]
As described above, the method 2 is a method of transferring data from the HGW 10 to the service providing server 200 by controlling the session management server 100 based on the determination that the user is currently in a call. As shown in FIGS. 19 to 23, the method 2 includes, for example, methods 2-1 to 2-5. The difference between each method will be briefly described. First, method 2-1 to method 2-3 and method 2-5 are methods in which a transfer request for requesting data transfer is transmitted to the session management server 100. On the other hand, the method 2-4 is a method in which a delivery request is transmitted to the service providing server 200. For this reason, the service providing system according to the first embodiment is a user who is actually in a call regardless of whether the delivery request is transmitted to the session management server 100 or the service providing server 200. Based on the determination, data can be transferred from the HGW 10 to the service providing server 200.

  In addition, as a difference between the methods 2-1 to 2-3 and the method 2-5, the method 2-1 and the method 2-2 are such that the session management server 100 directly transmits data to be transferred. Whereas the method 2-3 and the method 2-5 are the methods for transmitting and receiving (once acquired), the session management server 100 controls the data transfer, but directly transmits and receives the data to be transferred. It is a method that does not. For this reason, by adopting method 2-3 or method 2-5, for example, when highly confidential data is to be transferred, data is not acquired by the session management server 100, and method 2- Compared with 1 and method 2-2, security can be further improved.

  In addition, as the difference between the method 2-1 and the method 2-2, as will be described later, by adopting the method 2-2, a home network (network of HGW 10 or lower) compared to the method 2-1. It becomes possible to further reduce the load. Further, as a difference between the method 2-3 and the method 2-5, according to the method 2-5, since data transmitted from the HGW 10 to the service providing server 200 is encrypted, the service is provided from the HGW 10. It becomes possible to ensure the delivery of data to the server 200. That is, the service providing server 200 cannot obtain a key for decrypting the encrypted data unless making an inquiry to the session management server 100. Further, since the session management server 100 transmits the key, it plays the role of a delivery certificate that proves that the HGW 10 has surely transmitted data to the service providing server 200.

[Method 2-1]
The method 2-1 will be described with reference to FIG. As shown in FIG. 19, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S601).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (Step S602). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “1” (own HGW) as the data storage source flag. By including, it requests | requires passing the data which the HGW10 of a transmission side memorize | stores to the service provision server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S603). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Further, as illustrated in FIG. 19, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S <b> 602. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and stores the data storage source flag “1” included in the transfer request. In addition to storing in the original information, the inter-departure / arrival association ID and the pseudonym ID acquired from the inter-departure / arrival association ID table 124 are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S602 (such as the date and time when the delivery request is received) in the “request acceptance” of the status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S604 to S615 in accordance with the transfer request.

  Specifically, the data transfer control unit 134 refers to the data transfer table 125, and from the data storage source flag “1” stored in the data storage source information, the transmission source of the data is the same as that of the information display terminal 20 The control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Subsequently, the data transfer control unit 134 transmits a data transmission request to the HGW 10 (step S604). Specifically, the data transfer control unit 134 transmits call session information “ui123456789” to the information display terminal 20 that is the request source of the transfer request, and the HGW acquired by referring to the control session management table 123 The URL “http://192.168.1.10/returm” is transmitted to give a redirect instruction to the HGW 10, and a request indicating a data transmission request is also transmitted at the time of the redirect instruction. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies call session information (step S605). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S605, the data transfer unit 13b generates a “data list page” describing the index information of the data stored in the HGW 10 (step S606). The “data list page” is transmitted to the information display terminal 20 (step S607). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S608).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S609). Then, the delivery request unit 25b of the information display terminal 20 notifies the selection information of the data selected by the user to the HGW 10 (Step S610).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires data specified by the selection information received in step S609 from the storage unit (step S611), and transmits the acquired data to the session management server 100 by redirection. (Step S612). At this time, the data transfer unit 13b transmits information that can verify the correspondence between steps S604 and S612 to the session management server 100. For example, the data transfer unit 13b transmits the call session information acquired in step S604 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S604, the random number may be transmitted in step S612.

  Then, the data delivery control unit 134 of the session management server 100 refers to the data delivery table 125 using the call session information “ui123456789”, and the delivery destination flag “4” stored in association with the call session information “ui123456789”. ”Is acquired. Next, since the delivery destination flag “4” is information indicating “in-use service”, the data delivery control unit 134 stores the control stored in the data delivery table 125 in association with the call session information “ui123456789”. The service ID “1001” of the service whose status is “in use” is acquired by referring to the arrival / departure association ID table 124 using the session information “1111111111”. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, searches for the URL “http://example1.com” of the service providing server, and the URL “http: // Data is transmitted to “example1.com” (step S613). The data delivery control unit 134 according to the first embodiment transmits data together with the pseudonym ID “kamei 1111” and the arrival / departure association ID “lin3333”.

  Then, the data delivery unit 233 of the service providing server 200 stores the data received in step S613 in the data table 222 in association with the kana ID “kamei1111” received in step S613 (step S614).

  Thereafter, the data delivery unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 613 and step S615 to the session management server 100, thereby notifying the result as a response to step S613. Is performed (step S615). For example, the data transfer unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S613. Alternatively, when a random number is transmitted together with data in step S613, the random number may be transmitted in step S615.

  Further, as illustrated in FIG. 19, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S615. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S615 in the “delivery completed” status information.

[Method 2-2]
The method 2-2 will be described with reference to FIG. As shown in FIG. 20, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S <b> 701).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (Step S702). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “1” (own HGW) as the data storage source flag. By including, it requests | requires passing the data which the HGW10 of a transmission side memorize | stores to the service provision server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S703). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Also, as illustrated in FIG. 20, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S <b> 702. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and stores the data storage source flag “1” included in the transfer request. In addition to storing in the original information, the inter-departure / arrival association ID and the pseudonym ID acquired from the inter-departure / arrival association ID table 124 are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S702 (such as the date and time when the delivery request is received) in the “request acceptance” of the status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S704 to S715 in accordance with the transfer request.

  Specifically, the data transfer control unit 134 refers to the data transfer table 125, and from the data storage source flag “1” stored in the data storage source information, the transmission source of the data is the same as that of the information display terminal 20 The control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Subsequently, the data transfer control unit 134 transmits a data transmission request to the HGW 10 (step S704). Specifically, the data transfer control unit 134 transmits call session information “ui123456789” to the information display terminal 20 that is the request source of the transfer request, and the HGW acquired by referring to the control session management table 123 The URL “http://192.168.1.10/returm” is transmitted to give a redirect instruction to the HGW 10, and a request indicating a data transmission request is also transmitted at the time of the redirect instruction. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S705). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S705, the data transfer unit 13b generates a “data list page” describing the index information of the data stored in the HGW 10 (step S706). The “data list page” is transmitted to the information display terminal 20 (step S707). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S708).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S709). Then, the delivery request unit 25b of the information display terminal 20 notifies the selection information of the data selected by the user to the HGW 10 (Step S710).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires data specified by the selection information received in step S709 from the storage unit (step S711), and transmits the acquired data to the session management server 100 (step S712). ). At this time, the data transfer unit 13b transmits information that can verify the correspondence between steps S704 and S712 to the session management server 100. For example, the data transfer unit 13b transmits the call session information acquired in step S704 or the control session information as information with which the correspondence can be verified. Alternatively, when a random number is transmitted together with the call session information in step S704, the random number may be transmitted in step S712.

  Then, the data delivery control unit 134 of the session management server 100 refers to the data delivery table 125 using the call session information “ui123456789”, and the delivery destination flag “4” stored in association with the call session information “ui123456789”. ”Is acquired. Next, since the delivery destination flag “4” is information indicating “in-use service”, the data delivery control unit 134 stores the control stored in the data delivery table 125 in association with the call session information “ui123456789”. The service ID “1001” of the service whose status is “in use” is acquired by referring to the arrival / departure association ID table 124 using the session information “1111111111”. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, searches for the URL “http://example1.co.jp” of the service providing server, and the URL “http: Data is transmitted to “/example1.co.jp” (step S713). The data delivery control unit 134 according to the first embodiment transmits data together with the pseudonym ID “kamei 1111” and the arrival / departure association ID “lin3333”.

  Then, the data delivery unit 233 of the service providing server 200 stores the data received in step S713 in the data table 222 in association with the kana ID “kamei1111” received in step S713 (step S714).

  After that, the data delivery unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 713 and step S715 to the session management server 100, thereby notifying the result as a response to step S713. Is performed (step S715). For example, the data transfer unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S713. Alternatively, when a random number is transmitted together with data in step S713, the random number may be transmitted in step S715.

  As illustrated in FIG. 20, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S <b> 715. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S715 in the “delivery completed” status information.

[Method 2-3]
The method 2-3 will be described with reference to FIG. As shown in FIG. 21, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S801).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S802). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “1” (own HGW) as the data storage source flag. By including, it requests | requires passing the data which the HGW10 of a transmission side memorize | stores to the service provision server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S803). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Further, as illustrated in FIG. 21, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S <b> 802. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and stores the data storage source flag “1” included in the transfer request. In addition to storing in the original information, the inter-departure / arrival association ID and the pseudonym ID acquired from the inter-departure / arrival association ID table 124 are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S802 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S804 to S818 according to the transfer request.

  Specifically, the data transfer control unit 134 first issues key information (step S804). Here, the key information is information for verifying the validity of the data transmission destination, such as a random number or a character string. That is, the session management server 100 is information for assuring the correct data transmission destination (the session management server 100 determines which transmission destination corresponds to the data among the users currently in use during a call). To notify and guarantee). By using such key information, it becomes possible for the user to reliably transfer data on an information basis related to the session without notifying the transmission destination of a telephone number or the like. Further, the data transfer control unit 134 stores the issued key information in a record stored in the data transfer table 125 in association with the control session information “1111111111”.

  Next, the data transfer control unit 134 refers to the data transfer table 125, and from the data storage source flag “1” stored in the data storage source information, the data storage source is the same as that of the information display terminal 20 on the transmission side. The HGW 10 is identified, and the control session management table 123 is referred to using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Further, the data transfer control unit 134 refers to the data transfer table 125 and acquires the transfer destination flag “4” stored in the transfer destination information. Since the delivery destination flag “4” is information indicating “service in use”, the data delivery control unit 134 refers to the departure / arrival association ID table 124 using the control session information “1111111111”, and the status is “ Service ID “1001” of the service “in use” is acquired. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, and acquires the URL “http://example1.co.jp” of the service providing server.

  Subsequently, the data delivery control unit 134 transmits a data transmission request to the HGW 10 (step S805). Specifically, the data transfer control unit 134 sends the key information, call session information “ui123456789”, and the URL “http:” of the service providing server issued in step S804 to the information display terminal 20 that has requested the transfer request. //example1.co.jp ”and a redirect instruction to the HGW 10 by sending the URL“ http://192.168.1.10/returm ”of the HGW obtained by referring to the control session management table 123 In the case of this redirect instruction, a request indicating that it is a data transmission request is also transmitted. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  In addition, as illustrated in FIG. 21, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the key information in step S805. For example, the delivery request determination unit 133 stores the time information (date and time) of the key information transmission in step S805 in “key information transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S806). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S806, the data transfer unit 13b generates a “data list page” describing the index information of the data stored in the HGW 10 (step S807). The “data list page” is transmitted to the information display terminal 20 (step S808). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S809).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S810). Then, the delivery request unit 25b of the information display terminal 20 notifies the selection information of the data selected by the user to the HGW 10 (Step S811).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires data specified by the selection information received in step S811 from the storage unit (step S812), and acquires the acquired data together with the key information received in step S805 in step S805. Is transmitted to the URL of the service providing server 200 received in step S813.

  Then, the data delivery control unit 134 of the service providing server 200 requests the session management server 100 to verify the key information received in step S813 (step S814).

  On the other hand, the data transfer control unit 134 of the session management server 100 refers to the data transfer table 125 using the key information received in step S814, and confirms that the key information received in step S814 is stored. The key information issued by itself is verified (step S815).

  Then, the data transfer control unit 134 acquires and acquires the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” of the data storage source information stored in association with the key information in the data transfer table 125. The pseudonym ID and the link between departure and arrival are transmitted to the service providing server 200 (step S816).

  Then, the data delivery unit 233 of the service providing server 200 stores the data received in step S813 in the data table 222 in association with the kana ID “kamei1111” received in step S816 (step S817).

  Thereafter, the data passing unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 816 and step S818 to the session management server 100, thereby notifying the result as a response to step S816. Is performed (step S818). For example, the data delivery unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S816. Alternatively, when a random number has been transmitted in step S816, the random number may be transmitted in step S818.

  Further, as illustrated in FIG. 21, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S818. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S818 in the “delivery completed” status information.

[Method 2-4]
The method 2-4 will be described with reference to FIG. As shown in FIG. 22, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S <b> 901).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the Web session information is added to the service providing server 200 (Step S902). At this time, the delivery request unit 25b includes the data storage source flag in the delivery request.

  For example, the delivery request unit 25b uses the data stored in the originating HGW 10 by including “1” (own HGW) as the data storage source flag in the delivery request to which the Web session information “aaaaaaaaaaaa” is added. Request to be delivered to the service providing server 200.

  On the other hand, the data delivery unit 233 of the service providing server 200 issues an access key (step S903). Here, the access key is identification information for uniquely specifying the delivery request, such as a random number or a character string.

  For example, the data transfer unit 233 refers to the Web session information management table 221 using the Web session information “aaaaaaaaaaaa”, stores the arrival / departure link ID “lin3333” stored in association with the Web session information “aaaaaaaaa”, and The pseudonym ID “kamei1111” is acquired. Then, the data passing unit 233 holds the access key in the storage unit 220.

  Next, the data transfer unit 233 redirects the transfer request received in step S902 to the session management server 100 with the access key issued in step S903 attached thereto (step S904). The data transfer unit 233 transfers the transfer request including the transfer destination flag “1” and the pseudonym ID in addition to the data storage source flag already included.

  Also, as illustrated in FIG. 22, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer of the transfer request in step S <b> 904. For example, the delivery request determination unit 133 first refers to the departure / arrival association ID table 124 using the kana ID “kamei1111” given to the delivery request, and stores the control request stored in association with the kana ID “kamei1111”. Session information “1111111111” is acquired. Further, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111”, and records “control control information” for the record stored in association with the control session information “1111111111”. Information from “session information” to “departure / departure determination flag” is stored in the data delivery table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and stores the data storage source flag “1” included in the transfer request. In addition to storing in the original information, the inter-departure / arrival association ID and the pseudonym ID acquired from the inter-departure / arrival association ID table 124 are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the transfer of the transfer request received in step S904 (such as the date and time when the transfer of the transfer request is received) in the “request reception” of the status information.

  When the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S905). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S906 to S917 according to the transfer request.

  Specifically, the data transfer control unit 134 refers to the data transfer table 125, and from the data storage source flag “1” stored in the data storage source information, the transmission source of the data is the same as that of the information display terminal 20 The control session management table 123 is referenced using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Further, the data transfer control unit 134 refers to the data transfer table 125 and acquires the transfer destination flag “4” stored in the transfer destination information. Since the delivery destination flag “4” is information indicating “service in use”, the data delivery control unit 134 refers to the departure / arrival association ID table 124 using the control session information “1111111111”, and the status is “ Service ID “1001” of the service “in use” is acquired. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, and acquires the URL “http://example1.co.jp” of the service providing server.

  Subsequently, the data delivery control unit 134 transmits a data transmission request to the HGW 10 (step S906). Specifically, the data transfer control unit 134 sends the access key, call session information “ui123456789” received in step S904, and the URL “http: of service providing server” to the information display terminal 20 that is the request source of the transfer request. //example1.co.jp ”and a redirect instruction to the HGW 10 by sending the URL“ http://192.168.1.10/returm ”of the HGW obtained by referring to the control session management table 123 In the case of this redirect instruction, a request indicating a data transmission request is also transmitted. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  In addition, as illustrated in FIG. 22, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the access key in step S <b> 906. For example, the delivery request determination unit 133 stores the time information (date and time) of access key transmission in step S906 in “access key transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S907). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S907, the data transfer unit 13b generates a “data list page” that describes the index information of the data stored in the HGW 10 (step S908). The “data list page” is transmitted to the information display terminal 20 (step S909). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S910).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S911). Then, the delivery request unit 25b of the information display terminal 20 notifies the HGW 10 of data selection information selected by the user (step S912).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires data specified by the selection information received in step S912 from the storage unit (step S913), and acquires the acquired data together with the access key received in step S906 in step S906. Is transmitted to the URL of the service providing server 200 received in step S914 (step S914).

  Then, the data delivery control unit 134 of the service providing server 200 verifies the access key received in step S914 (step S915). If the verification is successful, the data received in step S914 is associated with the pseudonym ID “kamei1111”. Is stored in the data table 222 (step S916).

  Thereafter, the data delivery unit 233 of the service providing server 200 notifies the result (step S917). For example, the data transfer unit 233 transmits the pseudonym ID “kamei1111”.

  Also, as illustrated in FIG. 22, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S917. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S917 in the “delivery completed” status information.

[Method 2-5]
The method 2-5 will be described with reference to FIG. As shown in FIG. 23, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S1001).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S1002). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “1” (own HGW) as the data storage source flag. By including, it requests | requires passing the data which the HGW10 of a transmission side memorize | stores to the service provision server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S1003). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Also, as shown in FIG. 23, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S1002. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and stores the data storage source flag “1” included in the transfer request. In addition to storing in the original information, the inter-departure / arrival association ID and the pseudonym ID acquired from the inter-departure / arrival association ID table 124 are stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S1002 (such as the date and time when the delivery request is received) in the “request acceptance” of the status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S1004 to S1020 according to the transfer request.

  Specifically, the data transfer control unit 134 first issues key information (step S1004). Here, the key information is information for verifying the legitimacy of the transmission side, such as a random number or a character string. Further, the data transfer control unit 134 stores the issued key information in a record stored in the data transfer table 125 in association with the control session information “1111111111”. In addition, the data delivery control unit 134 generates a key for encryption / decryption (step S1005).

  Next, the data transfer control unit 134 refers to the data transfer table 125, and from the data storage source flag “1” stored in the data storage source information, the data storage source is the same as that of the information display terminal 20 on the transmission side. The HGW 10 is identified, and the control session management table 123 is referred to using the control session information “1111111111”. Then, the data delivery control unit 134 acquires the URL “http://192.168.1.10/returm” of the HGW stored in association with the control session information “1111111111”.

  Further, the data delivery control unit 134 refers to the data delivery table 125 and acquires Call-ID “ui123456789” as call session information stored in association with the control session information “1111111111”.

  Further, the data transfer control unit 134 refers to the data transfer table 125 and acquires the transfer destination flag “4” stored in the transfer destination information. Since the delivery destination flag “4” is information indicating “service in use”, the data delivery control unit 134 refers to the departure / arrival association ID table 124 using the control session information “1111111111”, and the status is “ Service ID “1001” of the service “in use” is acquired. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, and acquires the URL “http://example1.co.jp” of the service providing server.

  Subsequently, the data delivery control unit 134 transmits a data transmission request to the HGW 10 (step S1006). Specifically, the data transfer control unit 134 sends the key information issued in step S1004, the key generated in step S1005, the call session information “ui123456789”, and the service to the information display terminal 20 that has requested the transfer request. Sending the URL “http://example1.co.jp” of the providing server and the URL “http://192.168.1.10/returm” of the HGW obtained by referring to the control session management table 123 Then, a redirect instruction to the HGW 10 is performed, and at the time of the redirect instruction, a request indicating a data transmission request is also transmitted. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  Also, as shown in FIG. 23, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the key information in step S1006. For example, the delivery request determination unit 133 stores the time information (date and time) of the key information transmission in step S1006 in the “key information transmitted” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S1007). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S1007, the data transfer unit 13b generates a “data list page” describing the index information of the data stored in the HGW 10 (step S1008). The “data list page” is transmitted to the information display terminal 20 (step S1009). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S1010).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S1011). Then, the delivery request unit 25b of the information display terminal 20 notifies the HGW 10 of data selection information selected by the user (step S1012).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires the data specified by the selection information received in step S1012 from the storage unit, and uses the acquired data with the key (key for encryption) received in step S1006. Encryption is performed (step S1013).

  Then, the data transfer unit 13b transmits the encrypted data to the URL of the service providing server 200 received in step S1006 together with the key information received in step S1006 (step S1014).

  Then, the data delivery control unit 134 of the service providing server 200 requests the session management server 100 to verify the key information received in step S1014 (step S1015).

  On the other hand, the data transfer control unit 134 of the session management server 100 refers to the data transfer table 125 using the key information received in step S1015, and confirms that the key information received in step S1015 is stored. The key information issued by itself is verified (step S1016).

  Then, the data transfer control unit 134 acquires and acquires the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” of the data storage source information stored in association with the key information in the data transfer table 125. The pseudonym ID and the arrival / departure association ID and the key (decryption key) generated in step S1005 are transmitted to the service providing server 200 (step S1017).

  Then, the data delivery unit 233 of the service providing server 200 decrypts the data received in step S1014 with the key received in step S1017 (step S1018), and associates the data with the pseudonym ID “kamei1111” received in step S1017. Store in the table 222 (step S1019).

  Also, as shown in FIG. 23, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting the key in step S1017. For example, the delivery request determination unit 133 stores the time information (date and time) at which the key is transmitted in step S1017 in “data transmission completed” in the status information.

  Thereafter, the data delivery unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 1017 and step S1020 to the session management server 100, thereby notifying the result as a response to step S1017. Is performed (step S1020). For example, the data transfer unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S1017. Alternatively, when a random number has been transmitted in step S1017, the random number may be transmitted in step S1020.

  Also, as illustrated in FIG. 23, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S1020. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S1020 in the “delivery completed” status information.

[Method 3]
Method 3 is a method of transferring data from the service providing server 200 to the service providing server 200 under the control of the session management server 100 based on the determination that the user is currently in a call. As shown in FIGS. 24 to 25, the method 3 includes, for example, methods 3-1 and 3-2. The difference between the methods will be briefly described. First, the method 3-1 is a method for transferring data without encrypting it, whereas the method 3-2 is for transferring data after it is encrypted. It is a method. For this reason, the method 3-2 can be applied to, for example, a case where highly confidential data is to be transferred. That is, as described above, the method 3-1 is a method in which the session management server 100 directly transmits / receives data to be transferred, but the method 3-2 encrypts the data and then transfers the data. If the session management server 100 cannot decrypt the data, the session management server 100 does not substantially acquire the data, and the security can be further improved. That is, according to method 3-2, since the data to be transferred is encrypted, the session management server 100 cannot grasp the contents of the data to be transferred. In other words, for example, if the data is personal information, the session management server 100 can avoid the difficulty of managing the personal information and can reduce the risk of managing the data. On the other hand, the session management server 100 can verify the encrypted data as a third party. That is, for example, when a dispute regarding data transfer between the service providing server A and the service providing server B occurs at a later date (a dispute such as passing or not passing data), the session management server 100 stores the key information. If provided, the evidence data can be restored and verified as a third party.

[Method 3-1]
The method 3-1 will be described with reference to FIG. As shown in FIG. 24, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S1101).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S1102). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. ) And the service ID “1002” to request that the data related to the service “1002” provided by the service providing server 200 be transferred to the service providing server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S1103). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Further, as illustrated in FIG. 24, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S1102. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and also stores the data storage source flag “5” included in the transfer request, the service ID. “1002” is stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S1102 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S1104 to S1109 according to the transfer request.

  First, the data transfer control unit 134 acquires data to be transferred. Specifically, the data delivery control unit 134 refers to the contract service information table 122 using the service ID “1002” included in the delivery request. Then, the data transfer control unit 134 searches the service providing server URL “http://example2.co.jp” stored in association with the contract service ID “1002”, and the pseudonym ID “kamei1111” and the arrival / departure information. A data acquisition request including the interlinking ID “lin3333” is transmitted to the URL “http://example2.co.jp” (step S1104).

  Then, the data delivery unit 233 of the service providing server 200 refers to the data table 222 using the kana ID “kamei1111” included in the data acquisition request, and stores the data stored in association with the kana ID “kamei1111”. Is acquired (step S1105). Depending on the contents of the service, for example, the data transfer unit 233 refers to the Web session information management table 221 using the link between arrivals and departures “lin3333” included in the data acquisition request, and associates between arrivals and departures. The kana ID “kamei 3111” stored in association with “lin3333” is acquired, and the data stored in association with the kana ID “kamei 3111” is obtained by referring to the data table 222 using the kana ID “kamei 3111”. May be obtained.

  Then, the data delivery unit 233 transmits the data acquired in step S1105 to the session management server 100 as a response to the data acquisition request transmitted from the session management server 100 (step S1106).

  Then, the data transfer control unit 134 of the session management server 100 uses the control session information “1111111111” because the transfer destination flag “4” is information indicating “service in use”. The service ID “1001” of the service whose status is “in use” is acquired. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, searches for the URL “http://example1.co.jp” of the service providing server, and the URL “http: Data is transmitted to “/example1.co.jp” (step S1107). The data delivery control unit 134 according to the first embodiment transmits data together with the pseudonym ID “kamei 1111” and the arrival / departure association ID “lin3333”.

  Then, the data transfer unit 233 of the service providing server 200 stores the data received in step S1107 in the data table 222 in association with the kana ID “kamei1111” received in step S1107 (step S1108).

  After that, the data delivery unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 1107 and step S1109 to the session management server 100, thereby notifying the result as a response to step S1107. Is performed (step S1109). For example, the data delivery unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S1107. Alternatively, when a random number is transmitted together with data in step S1107, the random number may be transmitted in step S1109.

  Further, as illustrated in FIG. 24, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S1109. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S1109 in the “delivery completed” status information.

[Method 3-2]
The method 3-2 will be described with reference to FIG. In the example shown in FIG. 25, an example in which data is transferred to the service providing server 200 that is currently being used is described. However, the present invention is not limited to this, and the service provided by the other party is currently provided. The present invention can be similarly applied to a case of transferring data to the server 200. As shown in FIG. 25, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S1201).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S1202). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “4” (service in use) as the transfer destination flag in the transfer request to which the control session information “1111111111” is added, and “5” (contract service ID designation) as the data storage source flag. ) And the service ID “1002” to request that the data related to the service “1002” provided by the service providing server 200 be transferred to the service providing server 200 in use. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S1203). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Also, as illustrated in FIG. 25, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S1202. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the transfer request determination unit 133 stores the transfer destination flag “4” included in the transfer request in the transfer destination information, and also stores the data storage source flag “5” included in the transfer request, the service ID. “1002” is stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S1202 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S1204 to S1213 according to the transfer request.

  First, the data delivery control unit 134 acquires a public key and a secret key. Specifically, since the delivery destination flag “4” is information indicating “in-use service”, the data delivery control unit 134 refers to the between-arrival / arrival association ID table 124 using the control session information “1111111111”. Then, the service ID “1001” of the service whose status is “in use” is acquired. Then, the data transfer control unit 134 refers to the contract service information table 122 using the service ID “1001”, searches for the URL “http://example1.co.jp” of the service providing server, and makes a public key request. It transmits with respect to URL "http://example1.co.jp" (step S1204).

  Then, the data delivery unit 233 of the service providing server 200 acquires a public key and a secret key (step S1205), and transmits the public key to the session management server 100 (step S1206).

  The data transfer control unit 134 of the session management server 100 refers to the contract service information table 122 using the service ID “1002” included in the transfer request. Then, the data delivery control unit 134 searches the URL “http://example2.co.jp” of the service providing server stored in association with the contract service ID “1002”, and the URL “http: // example2 The public key acquired in step S1206 is transmitted to “.co.jp” (step S1207). Note that the data delivery control unit 134 according to the first embodiment transmits the public key together with the pseudonym ID “kamei 1111” and the arrival / departure association ID “lin3333”.

  Then, the data delivery unit 233 of the service providing server 200 refers to the data table 222 using the kana ID “kamei1111” included in the data acquisition request, and stores the data stored in association with the kana ID “kamei1111”. And the acquired data is encrypted with the public key received in step S1207 (step S1208).

  Then, the data delivery unit 233 transmits the data encrypted in step S1208 to the session management server 100 (step S1209).

  Then, the data transfer control unit 134 of the session management server 100 searches for the URL “http://example1.co.jp” of the service providing server and encrypts the URL “http://example1.co.jp”. Data is transmitted (step S1210). The data delivery control unit 134 according to the first embodiment transmits data together with the pseudonym ID “kamei 1111” and the arrival / departure association ID “lin3333”.

  Then, the data transfer unit 233 of the service providing server 200 decrypts the data received in step S1210 with the private key acquired in step S1205 (step S1211), and associates it with the pseudonym ID “kamei1111” received in step S1210. The data is stored in the data table 222 (step S1212).

  Thereafter, the data passing unit 233 of the service providing server 200 transmits information that can verify the correspondence between step 1210 and step S1213 to the session management server 100, thereby notifying the result as a response to step S1210. Is performed (step S1213). For example, the data transfer unit 233 transmits the pseudonym ID “kamei1111” and the arrival / departure association ID “lin3333” acquired in step S1210. Alternatively, when a random number is transmitted together with data in step S1210, the random number may be transmitted in step S1213.

  Also, as illustrated in FIG. 25, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S1213. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S1213 in the “delivery completed” status information.

[Method 4]
The method 4 is a method of transferring data from the HGW 10 of the call partner to the HGW 10 of the requester of the transfer request by the session management server 100 controlling based on the determination that the user is currently in a call. As shown in FIGS. 26 to 27, the method 4 includes, for example, the types of methods 4-1 and 4-2. The difference between the methods will be briefly described. First, the method 4-1 is a method in which data is transferred without being encrypted, whereas the method 4-2 is performed after data is encrypted. It is a method. For this reason, the method 4-2 can be applied to, for example, a case where highly confidential data is to be transferred. That is, as described above, the method 4-1 is a method in which the session management server 100 directly transmits / receives data to be transferred, but the method 4-2 transfers data after encrypting the data. If the session management server 100 cannot decrypt the data, the session management server 100 does not substantially acquire the data, and the security can be further improved. That is, according to method 4-2, since the data to be transferred is encrypted, the session management server 100 cannot grasp the contents of the data to be transferred. In other words, for example, if the data is personal information, the session management server 100 can avoid the difficulty of managing the personal information and can reduce the risk of managing the data. On the other hand, the session management server 100 can verify the encrypted data as a third party. That is, for example, in the event of a dispute regarding data transfer between the HGWs 10 at a later date (such as a dispute in which data is transferred or not), the session management server 100 restores evidence data if key information is provided. Can be verified as a third party.

[Method 4-1]
The method 4-1 will be described with reference to FIG. As shown in FIG. 26, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S1301).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S1302). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request with the control session information “1111111111” and “2” (call partner HGW) as the data storage source flag. By including, it requests | requires passing the data which HGW10 of the receiving side memorize | stores to HGW10 of a transmission side. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S1303). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Also, as shown in FIG. 26, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S1302. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information and uses the arrival / departure association ID and the pseudonym ID acquired from the arrival / departure association ID table 124. The data storage source flag “2” that is stored in the delivery destination information and included in the delivery request is stored in the data storage source information, and the departure / arrival association ID and the pseudonym acquired from the arrival / departure association ID table 124 The ID is stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S1302 (such as the date and time when the delivery request is received) in the “request acceptance” of the status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S1304 to S1321 in accordance with the transfer request.

  Specifically, the data transfer control unit 134 determines that the data storage source is the receiving side HGW 10 different from the requesting information display terminal 20 based on the data storage source flag “2” included in the transfer request. And the control session management table 123 is referred to using the control session information “1111111111”. Then, the data transfer control unit 134 searches for the same call session information “ui123456789” as the call session information “ui123456789” stored in association with the control session information “1111111111”, and searches for the control session information “3333333333”. get.

  Further, the data transfer control unit 134 identifies from the transfer destination flag “1” included in the transfer request that the data storage source is the same HGW 10 on the transmission side as the requesting information display terminal 20, and performs control. The control session management table 123 is referred to using the session information “1111111111”. Then, the data transfer control unit 134 acquires the URL “http://192.168.1.10/return” of the HGW stored in association with the control session information “1111111111”.

  Then, the data delivery control unit 134 identifies the information display terminal 20 of the control session information “33333333333” from the polling information display terminals 20, and whether or not data transmission is possible to the identified information display terminal 20. Confirmation screen (dialog is screen) for confirming is transmitted (step S1304). For example, on the confirmation screen, “You have received a data transfer request from the other party, but are you sure you want to download it?”

  Then, the delivery request unit 25b of the information display terminal 20 displays a confirmation screen on the output unit 23 (step S1305), for example, a confirmation screen displayed on the output unit 23 of the information display terminal 20 by the user on the receiving side. Is pressed using the input unit 22 (step S1306). Then, the delivery request unit 25b of the information display terminal 20 notifies the session management server 100 of the approval by the user (step S1307).

  Subsequently, the data transfer control unit 134 of the session management server 100 transmits a data transmission request to the incoming HGW 10 (step S1308). Specifically, the data transfer control unit 134 transmits the call session information “ui123456789” to the information display terminal 20 on the receiving side, and at the same time, obtains the URL “HGW obtained by referring to the control session management table 123“ By transmitting “http://192.168.3.10/returm”, a redirect instruction to the HGW 10 is performed, and at the time of this redirect instruction, a request indicating that it is a data transmission request is also transmitted. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  Then, the data transfer unit 13b of the HGW 10 verifies the call session information (step S1309). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the verification of the call session information is successful in step S1209, the data transfer unit 13b generates a “data list page” that describes the index information of the data stored in the HGW 10 (step S1310). The “data list page” is transmitted to the information display terminal 20 (step S1311). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S1312).

  Here, for example, the user on the transmission side browses the “data list page” displayed on the output unit 23 of the information display terminal 20 and presses a selection button for selecting predetermined data using the input unit 22. (Step S1313). Then, the delivery request unit 25b of the information display terminal 20 notifies the HGW 10 of data selection information selected by the user (step S1314).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires the data specified by the selection information received in step S1314 from the storage unit (step S1315), and transmits the acquired data to the session management server 100 by redirection. (Step S1316). At this time, the data transfer unit 13b transmits information that can verify the correspondence between steps S1308 and S1316 to the session management server 100. For example, the data transfer unit 13b transmits the call session information acquired in step S1308 or the control session information as information with which the correspondence can be verified. Alternatively, when a random number is transmitted together with the call session information in step S1308, the random number may be transmitted in step S1316.

  Subsequently, the data delivery control unit 134 identifies from the delivery destination flag “1” that the data delivery destination is the same HGW 10 on the transmission side as the requesting information display terminal 20, and information on the request source of the delivery request. The data acquired in step S1316 and the call session information “ui123456789” are transmitted to the display terminal 20, and the URL of the HGW acquired by referring to the control session management table 123 “http://192.168.1.10/returm” ] Is sent to the HGW 10 to instruct redirection (step S1317). At this time, the data transfer control unit 134 refers to the control session management table 123 using the control session information “1111111111”, and acquires the URL of the HGW 10. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  Also, as illustrated in FIG. 26, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting data in step S1317. For example, the delivery request determination unit 133 stores the time information (date and time) of data transmission in step S1317 in “data transmission completed” in the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies the call session information (step S1318). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  When the data transfer unit 13b succeeds in verifying the call session information in step S1318, the data transfer unit 13b stores the data received in step S1317 in the storage unit 12 (step S1319).

  After that, the data transfer unit 13b transmits information that can verify the correspondence between step S1317 and step S1320 to the session management server 100, thereby notifying the result as a response to step S1317 (step S1320). ). For example, the data transfer unit 13b transmits the call session information acquired in step S1317 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S1317, the random number may be transmitted in step S1320.

  Further, as illustrated in FIG. 26, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S1320. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S1320 in the “delivery completed” status information.

  In addition to the above-described processing procedure, for step S1317 and subsequent steps, for example, data can be transferred by the same processing procedure as step S204 in FIG.

[Method 4-2]
The method 4-2 will be described with reference to FIGS. 27-1 and 27-2. As illustrated in FIG. 27A, for example, the user on the transmission side presses the delivery button of the browser displayed on the output unit 23 of the information display terminal 20 using the input unit 22 (step S1401).

  Then, the transfer request unit 25b of the information display terminal 20 transmits a transfer request to which the control session information is added to the session management server 100 (step S1402). At this time, the delivery request unit 25b includes the delivery destination flag and the data storage source flag in the delivery request, and also includes the service ID in the delivery request as necessary. However, the service ID can be omitted when data related to the service currently being used is to be transferred.

  For example, the transfer request unit 25b includes “1” (own HGW) as the transfer destination flag in the transfer request with the control session information “1111111111” and “2” (call partner HGW) as the data storage source flag. By including, it requests | requires passing the data which HGW10 of the receiving side memorize | stores to HGW10 of a transmission side. In addition, although the method for giving the control session information to the delivery request has been described, the method is not limited to this method, and a method for assigning a departure / arrival linking ID or a pseudonym ID is given instead of the control session information. A technique or a technique of assigning a departure / arrival linking ID and a pseudonym ID may be used.

  On the other hand, when the delivery request determination unit 133 of the session management server 100 accepts the delivery request, the user of the information display terminal 20 that is the request source of the delivery request is the user of the SIP phone 30 that has established communication by SIP. It is determined whether or not (step S1403). For example, it is determined whether or not the user is a user who is currently talking.

  Specifically, the delivery request determination unit 133 refers to the control session management table 123 using the control session information “1111111111” assigned to the delivery request. Then, the delivery request determination unit 133 confirms that the control session information “1111111111” is stored and confirms the call information “January 7, 2009, 22:35” (the call end time is It is determined that the user of the information display terminal 20 is actually the user who is talking on the phone by confirming the call state that is not recorded.

  Further, as illustrated in FIG. 27A, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the transfer request in step S1402. For example, the transfer request determination unit 133 first refers to the control session management table 123 using the control session information “1111111111” given to the transfer request, and is stored in association with the control session information “1111111111”. For each record, information from “control session information” to “departure / departure determination flag” is stored in the data transfer table 125.

  Next, the delivery request determination unit 133 stores the delivery destination flag “1” included in the delivery request in the delivery destination information and uses the arrival / departure association ID and the pseudonym ID acquired from the arrival / departure association ID table 124. The data storage source flag “2” that is stored in the delivery destination information and included in the delivery request is stored in the data storage source information, and the departure / arrival association ID and the pseudonym acquired from the arrival / departure association ID table 124 The ID is stored in the data storage source information.

  Subsequently, the delivery request determination unit 133 stores time information related to the delivery request accepted in step S1402 (such as the date and time when the delivery request is received) in the “request acceptance” status information.

  Subsequently, the data transfer control unit 134 controls the data transfer shown in steps S1404 to S1425 according to the transfer request.

  Specifically, the data transfer control unit 134 determines that the data storage source is the receiving side HGW 10 different from the requesting information display terminal 20 based on the data storage source flag “2” included in the transfer request. And the control session management table 123 is referred to using the control session information “1111111111”. Then, the data transfer control unit 134 searches for the same call session information “ui123456789” as the call session information “ui123456789” stored in association with the control session information “1111111111”, and searches for the control session information “3333333333”. get. Further, the data transfer control unit 134 acquires the URL “http://192.168.3.10/return” of the HGW stored in association with the control session information “33333333333”.

  Further, the data delivery control unit 134 identifies from the delivery destination flag “1” included in the delivery request that the data delivery destination is the same HGW 10 on the transmission side as the requesting information display terminal 20, and performs control. The control session management table 123 is referred to using the session information “1111111111”. Then, the data transfer control unit 134 acquires the URL “http://192.168.1.10/return” of the HGW stored in association with the control session information “1111111111”.

  Then, the data delivery control unit 134 identifies the information display terminal 20 of the control session information “33333333333” from the polling information display terminals 20, and whether or not data transmission is possible to the identified information display terminal 20. A confirmation screen (dialog is screen) for confirming is transmitted (step S1404). For example, on the confirmation screen, “You have received a data transfer request from the other party, but are you sure you want to download it?”

  Then, the delivery request unit 25b of the information display terminal 20 displays a confirmation screen on the output unit 23 (step S1405), for example, a confirmation screen displayed on the output unit 23 of the information display terminal 20 by the user on the receiving side. Is pressed using the input unit 22 (step S1406). Then, the delivery request unit 25b of the information display terminal 20 notifies the session management server 100 of the approval by the user (step S1407).

  Subsequently, the data transfer control unit 134 of the session management server 100 acquires a public key and a secret key. Specifically, the data delivery control unit 134 transmits a public key request together with call session information “ui123456789” to the information display terminal 20 that is the request source of the delivery request, and refers to the control session management table 123. The redirection instruction to the HGW 10 is performed by transmitting the URL “http://192.168.1.10/returm” of the HGW acquired in step S1408. Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  Then, the data transfer unit 13b of the HGW 10 verifies the call session information (step S1409). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the call session information is successfully verified in step S1409, the data transfer unit 13b acquires a public key and a secret key (step S1410), and transmits the acquired public key to the session management server 100 by redirection ( Step S1411). At this time, the data transfer unit 13b transmits information that can verify the correspondence between steps S1408 and S1411 to the session management server 100. For example, the data transfer unit 13b transmits the call session information acquired in step S1408 or the control session information as information with which the correspondence can be verified. Alternatively, when a random number is transmitted together with the call session information in step S1408, the random number may be transmitted in step S1411.

  Subsequently, the data transfer control unit 134 of the session management server 100 identifies the information display terminal 20 of the control session information “33333333333” from the polling information display terminals 20, and sends the information display terminal 20 to the identified information display terminal 20. The public key received in step S1411 is transmitted together with the call session information “ui123456789”, and the HGW URL “http://192.168.3.10/returm” acquired by referring to the control session management table 123 is transmitted. Thus, a redirect instruction to the HGW 10 is performed (step S1412). Here, the purpose of transmitting call session information (for example, Call-ID) is that call session information is information that can uniquely identify a call between the HGW 10 and the session management server 100. The HGW 10 also has an object of verifying whether or not data is surely delivered under the control of the session management server 100.

  Then, the data transfer unit 13b of the HGW 10 verifies the call session information (Step S1413). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  Then, when the verification of the call session information is successful in step S1413, the data transfer unit 13b generates a “data list page” describing the index information of the data stored in the HGW 10 (step S1414). The “data list page” is transmitted to the information display terminal 20 (step S1415). Then, the delivery request unit 25b of the information display terminal 20 displays the “data list page” received from the HGW 10 on the output unit 23 (step S1416).

  Here, for example, the user browses the “data list page” displayed on the output unit 23 of the information display terminal 20, and presses a selection button for selecting predetermined data using the input unit 22 (step S1417). ). Then, the delivery request unit 25b of the information display terminal 20 notifies the HGW 10 of data selection information selected by the user (step S1418).

  On the other hand, the data transfer unit 13b of the HGW 10 acquires data specified by the selection information received in step S1418 from the storage unit (step S1419), and encrypts the acquired data with the public key acquired in step S1412 ( In step S1419), it is transmitted to the session management server 100 by redirection (step S1420). At this time, the data transfer unit 13b transmits information that can verify the correspondence between steps S1412 and S1420 to the session management server 100. For example, the data transfer unit 13b transmits the call session information acquired in step S1412 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S1412, the random number may be transmitted in step S1420.

  Subsequently, the data delivery control unit 134 identifies from the delivery destination flag “1” that the data delivery destination is the same HGW 10 on the transmission side as the requesting information display terminal 20, and information on the request source of the delivery request. The data acquired in step S1421 and the call session information “ui123456789” are transmitted to the display terminal 20, and the URL of the HGW acquired by referring to the control session management table 123 “http://192.168.1.10/returm” ] Is transmitted to the HGW 10 to instruct redirection (step S1421).

  Also, as illustrated in FIG. 27B, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after transmitting data in step S1421. For example, the delivery request determination unit 133 stores the time information (date and time) of data transmission in step S1421 in “data transmission completed” of the status information.

  On the other hand, the data transfer unit 13b of the HGW 10 verifies call session information (step S1422). Specifically, the data transfer unit 13b refers to the browser session information management table 12a using the call session information “ui123456789” and uses the same call session information as the call session information managed by the browser session information management table 12a. Verify that there is.

  When the data transfer unit 13b succeeds in verifying the call session information in step S1422, the data transfer unit 13b decrypts the data acquired in step S1421 with the private key acquired in step S1410 (step S1423) and stores it in the storage unit 12 (step S1422). S1424).

  Thereafter, the data transfer unit 13b transmits information that can verify the correspondence between step S1421 and step S1425 to the session management server 100, thereby notifying the result as a response to step S1421 (step S1425). ). For example, the data transfer unit 13b transmits the call session information acquired in step S1421 or the control session information as information that can verify the correspondence. Alternatively, when a random number is transmitted together with the call session information in step S1421, the random number may be transmitted in step S1425.

  Further, as illustrated in FIG. 27, the transfer request determination unit 133 of the session management server 100 stores the status information in the data transfer table 125 after receiving the result notification in step S1425. For example, the delivery request determination unit 133 stores the time information (date and time) of the result notification received in step S1425 in the “delivery completed” status information.

  Note that the processing procedure described above for method 1 to method 4 is merely an example, and the order, the data transmission destination, and the like can be changed as appropriate. Moreover, about the method 1-the method 4, about the process sequence which transmitted data using the redirect, it can change suitably to the process procedure which transmits directly, without using a redirect.

[Effect of Example 1]
As described above, in the service providing system according to the first embodiment, the session management server 100 is used by the user in combination with the information display terminal 20 for each information display terminal 20 that requests the provision of service. Call session information identifying communication established between the SIP phone 30 and the other SIP phone 30 is established. In addition, the session management server 100 identifies call session information indicating the same communication from the collected call session information, and is paired with each SIP phone 30 that has established communication identified by the identified call session information. Cooperation information for linking each information display terminal 20 to be used is issued to each information display terminal 20. When a transfer request for requesting data transfer is received from one of the information display terminals 20 between the information display terminals 20 provided so as to cooperate with the service from the service providing server 200, information on the request source of the transfer request is received. It is determined whether or not the display terminal 20 is a terminal used in combination with the SIP phone 30 that has established communication by SIP. When it is determined that the information display terminal 20 is used in combination with the SIP phone 30 that has established communication by SIP, the data used for the transfer is acquired from the data storage source according to the transfer request, and the acquired data is used. Control the data transfer.

  As described above, in the service providing system according to the first embodiment, the session management server 100 issues an arrival / departure linking ID for realizing service provision based on a temporary communication relationship established by SIP, When a delivery request is accepted, data delivery is controlled after confirming that the user who has requested the delivery request is busy. For this reason, a user who uses the SIP phone 30 and the information display terminal 20 as a pair can use the Web service in cooperation with the other party while making a call, for example. It becomes possible to exchange data easily by extending the number of times.

  In other words, without the above mechanism, data can only be transferred between browsers between the information display terminal 20 on the sending side and the information display terminal 20 on the receiving side. In addition, the session management server 100 cannot guarantee data transfer. If the session management server 100 cannot guarantee the delivery of data, for example, the user should have passed the personal information stored in the HGW 10 to the service providing server 200, but the service providing server actually The service provision server may be a spoofing service intervening in the middle of using the service, and the user may pass the personal information to the service provisioning server.

  However, according to the above mechanism, data transfer is guaranteed by the session management server 100, that is, the session management server 100 connects the incoming / outgoing association ID between the outgoing information display terminal 20 and the incoming information display terminal 20 with each other. The session management server 100 guarantees the data transfer destination and storage source (for example, the service providing server 200 being used). As a result, if the user trusts the session management server 100, the user can exchange data with peace of mind.

  The delivery request in the first embodiment includes a delivery destination flag that designates a delivery destination and a data storage source flag that designates a storage source of data to be delivered, and the session management server 100 receives the delivery request. In accordance with the delivery destination flag and the data storage source flag included in the data, control is performed so that the data designated by the data storage source flag is delivered to the delivery destination designated by the delivery destination flag.

  In addition, the session management server 100 according to the first embodiment issues an arrival / departure association ID, and sets a kana ID that identifies the user of the information display terminal 20 or the information display terminal 20 as a pair with the arrival / departure association ID. And using the pseudonym ID, the delivery destination or data storage source specified in the delivery request is specified, and delivery is controlled.

  In addition, the session management server 100 according to the first embodiment controls the data transfer so that the data to be transferred is transferred after being encrypted using the key information of the transfer destination.

  For this reason, if the user trusts the session management server 100, the user can exchange data with peace of mind.

  The first embodiment of the present invention has been described so far, but the present invention may be implemented in various different forms other than the first embodiment.

[Data to be transferred]
In the above embodiment, it has been assumed that the data to be transferred is data related to the service. However, the present invention is not limited to this, and can be applied to a case where data is simply exchanged during a call. For example, when data is exchanged between HGWs, method 4-1 and method 4-2 can be applied regardless of the service providing server. However, in this case, the session management server does not need to issue a connection ID between arrivals and departures as information for linking services. Therefore, for example, the session management server determines whether the call session information included in the delivery request is call session information managed by the session management server, and if the determination result is successful, the data A method of controlling the delivery of a message can be considered.

[Session management function]
In the above embodiment, the “session cooperation function” has been described as being provided in a session management server physically different from the SIP proxy or service providing server, but the present invention is not limited to this. . The present invention can be similarly applied to a case where the “session cooperation function” is provided in the SIP proxy or a case provided in the service providing server.

[Destination monitoring function]
In the above-described embodiment, the information display terminal includes a general-purpose Web browser, and the “connection destination monitoring function” includes a JavaScript file that operates on the Web browser (by being transmitted from the session management server, “ Although the technique provided with the “connection destination monitoring function” has been described, the present invention is not limited to this. The present invention can be similarly applied to a method in which the information display terminal includes a dedicated application, and the dedicated application includes a “connection destination monitoring function” in advance.

[Linkage ID between departure and arrival]
In the above-described embodiment, a method has been described in which the connection / departure link ID newly issued by the session management server is used as the “departure / departure link ID” used when the service providing server controls the Web services in association with each other. However, the present invention is not limited to this. The present invention can be similarly applied to a method of diverting call session information itself (for example, Call-ID) that is call information. In other words, the “departure / arrival linking ID” means that when the service providing server provides the web service to a plurality of terminals in association with each other, each of the plurality of terminals establishes communication by SIP. As long as the information can be recognized.

[Signed certificate]
In the above embodiment, when the SIP proxy or session management server transmits information to another device, it issues a signed certificate of its own device and stores the information in a verifiable format with the signed certificate attached. Although the transmission method has been described, the present invention is not limited to this. The present invention can be similarly applied to a method of simply transmitting information without attaching a signed certificate. In this case, it is not necessary to verify the information on the information receiving side.

[Polling]
In the above-described embodiments, the method of performing communication using appropriate polling between the information display terminal and the HGW, between the information display terminal and the session management server, etc. has been described, but the present invention is limited to this. Instead of polling, push-type or pull-type communication may be used instead of polling (in this case, access is required only when necessary).

[Terminal configuration]
The service providing system according to the present invention is not limited to the configuration exemplified in the above embodiment. That is, in the service providing system according to the present invention, first, in terms of the configuration on the terminal side, whether or not the HGW is installed on the terminal side, whether the terminal is a separated type of SIP phone and information display terminal, There are options such as whether the SIP phone function and the information display function are integrated. Also, in terms of which device collects call session information, whether the SIP proxy collects call session information, the HGW collects call session information, or the terminal (SIP phone or SIP phone function) calls There is an option to collect session information. Further, there is an option of whether to transmit call session information collected by the SIP proxy to the HGW or to a terminal (SIP phone or SIP phone function). In addition, there are options such as whether the configuration on the calling side and the configuration on the receiving side are the same or different, and options such as whether or not the information display terminal is connected as a terminal under the HGW. The above embodiments show only some combinations of these options, and the present invention is not limited to these configurations. In other words, the present invention can be similarly realized with respect to other configurations by using the above-described method or a known method.

[SIP proxy]
In the above embodiment, a case where a single SIP proxy mediates a SIP signal (including SIP specific signals, types such as INVITE and 200 OK, and parameters such as From and To) is described. However, the present invention is not limited to this. The present invention can be similarly applied to a case where a plurality of SIP proxies mediate a SIP signal and a case where an AS (Application Server) in NGN (Next Generation Network) mediates a SIP signal.

[Past call users]
In the above embodiment, a method for determining whether a user is currently in a call has been described. However, the present invention is not limited to this. For example, at least a user who has made a call in the past. It may be a technique for determining that the person is a person. In this method, for example, if the user creates data during a call, the data can be acquired as information related to a past call after the call is disconnected. For example, the user can store conversation data during a call in the HGW, and the session management server can download the conversation data only to the other party who has made the call. For example, a case where the user calls the call center to make an inquiry, hangs up the call, and receives a separate response can be considered. At this time, the user disconnects the call once, but the service providing server 200 on the call center side uses the session information of the call to send the text (data) of the answer to the question to the HGW 10 on the user side at a later date. ) In other words, when the service providing server 200 notifies the session management server 100 of the session information when the inquiry is received and requests the data delivery, the session management server 100 intervenes in the data delivery, and the past call history Based on the information, the response information is transferred to the HGW 10 on the user side. When data is transferred from the session management server 100 to the HGW 10 on the user side, data may be transmitted directly from the session management server 100 to the HGW 10 instead of browser redirection.

[Setting of delivery destination flag and data storage source flag]
The setting of the delivery destination flag and the data storage source flag is not limited to the combination described in the first embodiment, and data can be delivered in various patterns that can be combined. For example, in the method 1 and the method 2 described in the first embodiment, data is transmitted to the caller information display terminal 20 or data is transmitted from the caller information display terminal 30. Depending on the setting of the delivery destination flag and the data storage source flag, data can be transmitted to the HGW 10 of the other party, or data can be transmitted from the HGW 10 of the other party to the service providing server 200.

  In addition, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. Further, all or any part of each processing function performed in each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

  The service providing method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. This program can be distributed via a network such as the Internet. The program can also be executed by being recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, and a DVD and being read from the recording medium by the computer.

DESCRIPTION OF SYMBOLS 100 Session management server 110 Communication part 120 Memory | storage part 121 User contract service management table 122 Contract service information table 123 Control session management table 124 Calling / separation ID table 130 Control part 131 Call session information collection part 132 Issue ID Unit 133 delivery request determination unit 134 data delivery control unit 200 service provision server 210 communication unit 220 storage unit 221 Web session information management table 230 control unit 231 arrival / departure linking ID collection unit 232 service provision control unit 233 data delivery unit 10 HGW
11 SIP communication unit / HTTP communication unit 12 Storage unit 12a Browser session information management table 13 Control unit 13a Service usage control unit 13b Data transfer unit 20 Information display terminal 21 HTTP communication unit 22 Input unit 23 Output unit 24 Input / output control I / F Unit 25 control unit 25a service use unit 25b delivery request unit 30 SIP phone 31 SIP communication unit 32 input unit 33 output unit 34 input / output control I / F unit

Claims (12)

A service providing system for providing a service on a network to a terminal,
Session management server
Communication for identifying a first communication established between a first communication terminal that is used in combination with the terminal and establishes a first communication and another first communication terminal for each terminal that requests service provision Communication information collecting means for collecting information;
Each of the first communication terminals that have identified communication information indicating the same first communication from among a plurality of pieces of communication information collected by the communication information collecting means and have established the first communication identified by the identified communication information Linkage information issuing means for issuing linkage information for linking each terminal used in combination with each terminal,
When a transfer request for requesting data transfer is received from one of the terminals provided to link the services from the service providing server, the request source terminal of the transfer request is collected by the communication information collecting means Determining means for determining whether or not the terminal is used in combination with the first communication terminal that has established the first communication identified by the communicated information;
When it is determined by the determination means that the terminal is used in combination with the first communication terminal that has established the first communication, the target data to be transferred or the target data is determined in accordance with the transfer request. Access means for acquiring from the storage source of the target data , access means for acquiring from the storage source of the target data ;
Using the target data or the access information acquired by the acquisition means, and a delivery control means for controlling delivery of the target data so as to deliver the target data to a delivery destination ,
Service providing server
Cooperation information collecting means for collecting cooperation information issued by the cooperation information issuing means for each terminal that requests service provision;
A service that identifies linkage information indicating that a service is to be linked from among a plurality of linkage information collected by the linkage information collection means, and links the services provided to each terminal that is the collection source of the identified linkage information. A service providing system comprising: a service providing control means for controlling providing. The delivery request includes a delivery destination flag for designating a delivery destination and a data storage source flag for designating a storage source of target data to be delivered,
The transfer control means transfers the target data specified by the data storage source flag to the transfer destination specified by the transfer destination flag according to the transfer destination flag and the data storage source flag included in the transfer request. The service providing system according to claim 1, wherein control is performed so as to deliver the service. The linkage information issuing means issues the linkage information and issues identification information for identifying the terminal or a user of the terminal as a set of linkage information and information,
Before Ki受 only passes control means includes wherein the using the identification information issued by the link information issuing means, controls the identify and pass the designated transfer destination or data save source in the delivery request The service providing system according to claim 2. Before Ki受 only passes control means, target data to be passed is, as passed after being encrypted using the key information delivery destination, and wherein the controller controls the delivery of the target data The service providing system according to any one of claims 1 to 3. The service providing system is connected to a first communication terminal that is a terminal that establishes the first communication and a second communication terminal that is a terminal that uses the service, and the connection to the network by the first communication terminal And a gateway device that controls connection to the network by the second communication terminal,
5. The service providing system according to claim 1, wherein the delivery control unit controls delivery of the target data from the service providing server to the gateway device. The service providing system is connected to a first communication terminal that is a terminal that establishes the first communication and a second communication terminal that is a terminal that uses the service, and the connection to the network by the first communication terminal And a gateway device that controls connection to the network by the second communication terminal,
The service providing system according to any one of claims 1 to 4, wherein the delivery control unit controls delivery of the target data from the gateway device to the service providing server. 5. The delivery control unit controls delivery of the target data from the service providing server to another service providing server different from the service providing server. Service provision system. The service providing system is connected to a first communication terminal that is a terminal that establishes the first communication and a second communication terminal that is a terminal that uses the service, and the connection to the network by the first communication terminal And a gateway device that controls connection to the network by the second communication terminal,
The gateway device is connected to a first communication terminal on a transmission side that transmits the first communication and a second communication terminal that is connected to a first communication terminal on a reception side that receives the transmission. A gateway device,
5. The service according to claim 1, wherein the delivery control unit controls delivery of the target data between the first gateway device and the second gateway device. 6. Offer system. The service providing system according to claim 1, further comprising history information management means for managing history information related to delivery of the target data controlled by the delivery control means. The delivery control means is issued at the storage source of the target data as information for determining whether or not it is a delivery destination permitted to access the target data, instead of the target data to be delivered , wherein the access information, by relaying to transfer away from the target data storage source, the service providing system according to any one of claims 1 to 9, characterized in that to control the transfer of the target data . The transfer control means, when relaying target data to be transferred from the session management server to the gateway device, instead of directly transmitting to the gateway device, the second communication connected to the gateway device The service providing system according to claim 5 or 8 , wherein the service is transmitted by redirection via a terminal. A service providing method for providing a service on a network to a terminal,
The session management server
Communication for identifying a first communication established between a first communication terminal that is used in combination with the terminal and establishes a first communication and another first communication terminal for each terminal that requests service provision A communication information collecting process for collecting information;
Each first communication terminal that identifies communication information indicating the same first communication from among a plurality of pieces of communication information collected by the communication information collection step and establishes a first communication identified by the identified communication information A linkage information issuing step of issuing linkage information for linking each of the terminals used in combination with each of the terminals;
When a transfer request for requesting data transfer is received from one of the terminals provided to link the services from the service providing server, the request source terminal of the transfer request collects by the communication information collecting step A determination step of determining whether or not the terminal is used in combination with the first communication terminal that has established the first communication identified by the communication information performed;
When it is determined in the determination step that the terminal is used in combination with the first communication terminal that has established the first communication, the target data to be transferred or the target data is changed according to the transfer request. access information for acquiring the target data storage source, an acquisition step of acquiring from the target data storage source,
Using the target data or the access information acquired by the acquisition step, and a delivery control step for controlling delivery of the target data so as to deliver the target data to a delivery destination ,
Service providing server
For each terminal that requests service provision, a collaborative information collection step that collects the collaborative information issued by the collaborative information issue step;
A service that identifies linkage information indicating that a service is to be linked from among a plurality of linkage information collected by the linkage information collection step, and links the services provided to each terminal that is the collection source of the identified linkage information. A service providing method comprising: a service providing control step for controlling providing.

Images