JP5359666B2 - Host session management server, host session management method, program, and host session management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an upper session management server that is able to easily achieve a communication service that associates a plurality of different apparatuses. <P>SOLUTION: There are included are a media identification part 602 that identifies a plurality of pieces of session kind information related to service kind information represented in a service start instruction in a session DB, a device identification part 603 that identifies device identification information related to a session kind out of device identification information represented in the start instruction that is identified by the media identification part 602 in the session DB, and a session control part 606 that starts a plurality of sessions to perform the service based on a plurality of pieces of session information related to the device identification information that is identified by the device identification part 603 in the session DB. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to an upper session management server, an upper session management method, a program, and an upper session management system that manage communication sessions between a plurality of devices.

  Conventionally, telephone, FAX, IM (Instant Messenger), TV conference, and the like are realized by SIP (Session Initiation Protocol). As the number of real-time communication devices that implement these services has increased, the number of communication means has also increased, improving user convenience.

  For example, Patent Document 1 discloses a method for realizing a video conference using a voice communication device connected to a telephone network and a video communication device connected to a public line network such as the Internet as a service using signaling. Is disclosed.

  Patent Document 2 discloses a method for establishing a session by an information processing apparatus associated with each IP phone when a session by the IP phone is established.

  However, in general provided TV conference systems, fusion of voice communication and video communication is attempted, but it is often provided as a simultaneous system for each vendor, and a TV conference system is formed by combining devices of different vendors. It was difficult to realize.

  In the technology according to Patent Document 1, cooperation between devices other than the telephone and the TV is not considered, and in the technology according to Patent Document 2, dedicated processing is required for each device.

  The present invention has been made in view of the above, and includes an upper session management server, an upper session management method, a program, and an upper session management system capable of easily realizing a communication service in which a plurality of different devices are linked. The purpose is to provide.

  In order to solve the above-described problems and achieve the object, the present invention provides a session management server that manages a communication session between a plurality of devices via a network, the session management server comprising: Receiving means for receiving a start command including information for instructing start of a service using a plurality of sessions, service type information indicating the type of service, and device identification information for identifying a device participating in the service A first storage unit that stores the service type information and session type information indicating a type of session used in the service in association with each other, the device identification information, and the session in which the device is used. Second storage means for associating and storing session type information, and the device identification Information and session information used when the device conducts a session in association with each other, and in the first storage means, the information is associated with the service type information received by the receiving unit. Among the device type information received by the receiving unit, the session type specifying unit that specifies a plurality of the session type information, and the session type information specified by the session type specifying unit in the second storage unit. A plurality of device identification means for identifying the plurality of device identification information associated with each other; and a plurality of the device identification information associated with each of the plurality of device identification information identified by the device identification means in the third storage means. Session information specifying means for specifying session information, and the session information specifying means Ri based on the plurality of session information is identified, characterized in that it comprises a session control means for performing the service by initiating a plurality of sessions.

  In another aspect of the present invention, there is provided a session management method in an upper session management server connected via a network to a session management server that manages communication sessions between a plurality of devices, wherein the upper session management server includes: First storage means for associating and storing service type information and session type information indicating the type of session used in the service, the device identification information, and the session type information of a session in which the device is used Second storage means for storing the information in association with each other, third storage means for storing the device identification information and session information used when the device performs a session in association with each other, and the reception means, From the session management server, start a service that uses a plurality of sessions. A receiving step for receiving a start command including information to be displayed, service type information indicating the type of service, and device identification information for identifying a device participating in the service; Means for identifying a plurality of the session type information associated with the service type information received in the receiving step; and a device specifying means for receiving the device identification information received in the receiving step. Among these, in the second storage means, a device specifying step for specifying a plurality of the device identification information associated with the session type information specified in the session type specifying step, and a session information specifying means, 3 In the storage means, it is specified in the device specifying step. A session information specifying step for specifying a plurality of the session information associated with each of the plurality of device identification information, and a session control means, based on the plurality of session information specified by the session information specifying means, And a session control step for performing the service by starting the session.

  Another embodiment of the present invention is a program executed in a computer connected via a network to a session management server that manages communication sessions between a plurality of devices, the computer including the service type information, First storage means for storing session type information indicating the type of session used in the service in association with each other, the device identification information, and the session type information of the session in which the device is used in association with each other Second storage means for storing, and third storage means for storing the device identification information and session information used when the device performs a session in association with each other, from the session management server, a plurality of sessions For instructing the start of a service that uses the service, and the type of the service A reception step of receiving a start instruction including service type information to be displayed and device identification information for identifying a device participating in the service; and correspondence in the first storage means to the service type information received in the reception step The session type specified in the session type specifying step in the second storage means out of the device identification information received in the receiving step and the session type specifying step for specifying the plurality of session type information A device specifying step for specifying the plurality of device identification information associated with the information, and a plurality of devices associated with each of the plurality of device identification information specified in the device specifying step in the third storage means Session information for identifying the session information of A constant step, based on a plurality of session information identified by the session information identification means, a program for executing a session control step of performing said service to the computer by initiating a plurality of sessions.

  Another aspect of the present invention includes a plurality of devices, a session management server that manages communication sessions between the plurality of devices, and an upper session management server that is connected to the session management server via a network. In the host session system, the first device among the plurality of devices participates in the service, information instructing start of a service using the plurality of sessions, service type information indicating a type of service to be started, and the service. Receiving means for transmitting a start command including device identification information for identifying a device, wherein the upper session management server receives the start command from the first device via the session management server; , The service type information and the type of session used in the service First storage means for storing session type information in association with each other, second storage means for storing the device identification information in association with the session type information of a session in which the device is used, and the device A third storage unit that stores the identification information and session information used when the device performs a session in association with each other; and the first storage unit that is associated with the service type information received by the reception unit. Among the device identification information received by the receiving means, the second storage means corresponds to the session type specified by the session specifying means among the session type specifying means for specifying the plurality of session type information. Device identification means for identifying a plurality of attached device identification information, and the third storage means Session information specifying means for specifying the plurality of session information associated with each of the plurality of device identification information specified by the device specifying means, and a plurality of session information specified by the session information specifying means And session control means for providing the service by starting a plurality of sessions.

  According to the present invention, it is possible to easily realize a communication service in which a plurality of different devices are linked.

FIG. 1 is a diagram illustrating an overall configuration of a communication system 10 according to the first embodiment. FIG. 2 is a block diagram illustrating a main configuration of the upper session management server 600. FIG. 3 is a diagram schematically showing the data configuration of the first table 701. As shown in FIG. FIG. 4 is a diagram schematically showing the data configuration of the second table 702. As shown in FIG. FIG. 5 is a diagram schematically illustrating the data configuration of the third table 703. FIG. 6 is a diagram schematically illustrating the data configuration of the fourth table 704. FIG. 7 is a diagram schematically illustrating the data configuration of the fifth table 705. FIG. 8 is a communication sequence diagram in the communication system 10 when starting a video conference. FIG. 9 is a diagram illustrating a start request. FIG. 10 is a flowchart illustrating detailed processing of the upper session management server 600 in the upper session information generation processing (step S106). FIG. 11 is a diagram showing upper session information. FIG. 12 is a sequence diagram illustrating a session start process executed under the control of the session control unit 606 of the upper session management server 600. FIG. 13 is a sequence diagram showing the upper session termination process. FIG. 14 is a sequence diagram showing a session end process (step S206) executed under the control of the session control unit 606 of the upper session management server 600. FIG. 15 is a communication sequence diagram in this case. FIG. 16 is a diagram illustrating a request. FIG. 17 is a diagram illustrating a request. FIG. 18 is a flowchart showing the processing by the upper session management server 600 in the upper session information update processing (step S308). FIG. 19 is a diagram illustrating the updated upper session information. FIG. 20 is a communication sequence diagram when a midway participant knows information for specifying a service. FIG. 21 is a diagram showing a participation request. FIG. 22 is a diagram showing a response. FIG. 23 is a diagram showing conference designation information. FIG. 24 is a communication sequence diagram showing event registration processing. FIG. 25 is a communication sequence diagram showing an event notification process at the start of the upper session. FIG. 26 is a communication sequence diagram illustrating an event notification process when the upper session information is updated. FIG. 27 is a diagram illustrating a data configuration of the second table 702 after the update. FIG. 28 is a diagram schematically illustrating a data configuration of the second table 712 according to the first modification. FIG. 29 is a diagram showing upper session information. FIG. 30 is a diagram illustrating an overall configuration of a communication system 30 according to the second embodiment. FIG. 31 is a diagram illustrating a communication sequence when the communication system 30 according to the second embodiment starts an upper session as a service. FIG. 32 is a diagram illustrating an overall configuration of a communication system 40 according to the third embodiment. FIG. 33 is a communication sequence diagram illustrating the promotion process to the upper session by the communication system 40. FIG. 34 is a diagram schematically illustrating the data configuration of the second table 722 after the update. FIG. 35 is a diagram illustrating a start request.

  Exemplary embodiments of an upper session management server, an upper session management method, a program, and an upper session management system according to the present invention will be described below in detail with reference to the accompanying drawings.

(First embodiment)
FIG. 1 is a diagram showing an overall configuration of a communication system 10 according to the first embodiment of the present invention. The communication system 10 provides various services realized by a plurality of sessions using a plurality of devices. Each session is performed between various devices. Examples of services include video conferencing and games. Video conferencing and games are realized in cooperation with a plurality of types of sessions such as audio and video. A plurality of sessions that are started to realize a predetermined service in this way are referred to as upper sessions.

  Various devices installed in the conference room A and various devices installed in the conference room B are used in the service. In the service, a portable terminal owned by a conference participant can also be used. In addition, a predetermined device can be used at the remote site.

  In the conference room A, a microphone A101, a speaker A102, a camera A103, and a display A104 are installed. In the conference room A, it is assumed that there are a user A1 and a user A2 who are service users. In the conference room A, a PC-A 105 used by the user A1 is brought. In the conference room B, a microphone B201, a speaker B202, a camera B203, and a display B204 are installed. Assume that there are a user B1 and a user B2 in the conference room B. The devices installed in the conference room A and the conference room B are all connected to the network 20.

  In the conference room A and the conference room B, the communication system 10 provides services such as video conferencing sharing voice and video. Device C is a device that can only be viewed, and user C can view the conference using device C. Thus, the user C can connect to the network 20 from the remote site using the device C300 and participate in the service.

  The communication system 10 includes, in addition to devices installed in the conference room A and the conference room B, an audio server 400 that manages audio, a video server 410 that manages video, and a data server 420 that manages data. . The communication system 10 also includes a session management server 500 that manages the session of each device, an upper session management server 600, a session DB 700 that stores information related to the session, and a conference control server 800 that controls the conference. .

  The microphone A 101 and the microphone B 201 transmit the captured audio data to the audio server 400. The audio server 400 synthesizes a plurality of received audio data and transmits the synthesized audio data to the speaker A102 or the speaker B202.

  The speaker A102 and the speaker B202 acquire audio data from the audio server 400 and reproduce the audio. Camera A 103 and camera B 203 transmit the captured video data to video server 410. The video server 410 appropriately processes (combines, etc.) the received plurality of video data, and transmits it to the display A 104 or the display B 204. The display A 104 and the display B 204 acquire video data from the video server 410 and reproduce it.

  The PC-A 105 is a notebook PC equipped with a Web browser and transmits / receives data to / from the data server 420. The PC-A 105 can also access the web site of the conference control server 800. The device C300 is a terminal that can only receive audio and video.

  Communication between microphone A101, microphone B201, speaker A102, speaker B202, camera A103, camera B203, display A104, display B204, PC-A105, device C300, audio server 400, video server 410, and data server 420 is a session management server. 500. The microphone A101, microphone B201, speaker A102, speaker B202, camera A103, camera B203, display A104, display B204, PC-A105, and device C300 used in this embodiment are the session management server 500 or the upper session management server 600. Any session can be started according to the request from. This control is realized by a 3PCC (3rd Party Call Control) mechanism. In addition, as another example, you may implement | achieve using another special control API.

  In this embodiment, the microphone A101, the speaker A102, the camera A103, and the display A104 are all directly connected to the network 20, but as another example, the microphone A101 and the speaker A102 pass through the PC-A105. Then, it may be connected to the network 20. Thus, the configuration of each device is not limited to the embodiment.

  Further, the types and number of devices included in the communication system 10 are not limited to those in the embodiment, and it is only necessary to include devices necessary for a plurality of sessions started in a service desired to be provided.

  The session DB 700 stores various types of information such as information about the user who uses the service, information about the device used for the session, and information necessary to start the session. The session DB 700 is connected so as to be accessible from the session management server 500 and the upper session management server 600, and is read, written, and updated in response to a request from the session management server 500 or the upper session management server 600. As another example, the session DB 700 may be connected to the network 20. In this case, the session management server 500 and the upper session management server 600 access the session DB 700 via the network 20.

  The session management server 500 manages device IDs for identifying devices connected to the network 20 (various devices 101 to 105, 201 to 204, 300 and servers 400, 410, 420 installed in the conference room). The session management server 500 appropriately transfers a connection request (call) from the device to the counterpart device and starts a session. The session management server 500 also manages the addition and deletion of sessions between devices and the termination of sessions after the session starts. The session management server 500 transfers the call to the upper session management server 600 as necessary.

  The call transfer is executed when the session information regarding the call satisfies a predetermined condition. The condition is, for example, “If the call originator is microphone A, the call is transferred to the upper session management server”. This condition is stored in the session DB 700. Upon receiving a call, the upper session management server 600 checks whether or not the condition stored in the session DB 700 is satisfied. The call is transmitted to the upper session management server 600.

  In the present embodiment, it is assumed that all calls received by session management server 500 are transferred to upper session management server 600. Call control and call transfer are realized by SIP (Session Initiation Protocol) or IMS (IP Multimedia Subsystem). Since these techniques are known, details are omitted.

  The upper session management server 600 appropriately processes the call received from the session management server 500 and sends it back to the session management server 500. This function corresponds to an AS (Application Server) in IMS. The upper session management server 600 integrally manages a plurality of sessions included in the upper session.

  Further, the upper session management server 600 provides an API so that it can be commonly used by a plurality of service providing servers. This API can be executed via HTTP, and enables addition / editing / deletion of upper sessions and control of upper sessions. However, for security reasons, it is assumed that a server that can operate the API of the upper session management server 600 is a specific server that can be trusted, and each server is permitted to control only a specific upper session. In the present embodiment, a conference control server 800 is connected to the upper session management server 600, and the conference control server 800 can only perform control related to the conference service with respect to the upper session management server 600. it can.

  The conference control server 800 manages a video conference being performed in the communication system 10. For example, when a plurality of conferences are simultaneously performed, the plurality of conferences are managed.

  FIG. 2 is a block diagram illustrating a main configuration of the upper session management server 600. The upper session management server 600 includes a communication unit 601, a media identification unit 602, a device identification unit 603, a session information identification unit 604, an upper session information management unit 605, a session control unit 606, and a session DB management unit 607. And have.

  The communication unit 601 transmits / receives various information to / from the session management server 500 and the conference control server 800 via the network 20. The communication unit 601 receives a service start command such as a video conference. When the communication unit 601 receives a start command, the media specifying unit 602 refers to the session DB 700 and specifies a plurality of media started in the service. Here, the media indicates the type of data transmitted / received in the session, such as “audio” or “video”. When the communication unit 601 receives the start command, the device specifying unit 603 refers to the session DB 700 and specifies a plurality of devices used in the service.

  The upper session information management unit 605 generates upper session information including a plurality of devices specified by the device specifying unit 603. Here, the upper session information is information necessary for starting the upper session, and specifically includes information indicating a plurality of devices that start each of the plurality of sessions included in the upper session. The upper session information management unit 605 also updates the content of the upper session information based on the information received by the communication unit 601.

  The session control unit 606 controls each session based on the upper session information generated by the upper session information management unit 605. Specifically, it manages the start, update, and end of a session. When starting a session, a session start request is transmitted to the device that starts the session via the communication unit 601. The request to the upper session management server 600 is transmitted via the session management server 500 or via an API provided by the upper session management server 600. At the start of a session, the session management server 500 refers to the session DB 700 and identifies session information of a session necessary for realizing the service. Here, the session information is information necessary for starting a session. The session information includes, for example, information such as a session ID for identifying the session, a device IP address, and a port number.

  When the upper session starts and ends, and when the upper session is updated, the session control unit 606 generates an event and notifies the already registered server of the event via the communication unit 601. To do.

  The session DB management unit 607 reads information from the session DB 700, edits and updates information stored in the session DB 700, and adds information to the session DB 700.

  3 to 7 are diagrams schematically illustrating a data configuration of the session DB 700. FIG. 3 is a diagram schematically showing the data configuration of the first table 701. As shown in FIG. In the first table 701, a device set / user name, a device set / user ID, and a service type are associated with each other. The device set / user name is the name of the device set or user. In the present embodiment, the device set is based on a conference room in which devices used for a session are installed. For example, the device set “conference room A” is a group that includes devices installed in the conference room A, that is, a microphone A101, a speaker A102, a camera A103, and a display A104. The user name is a user name of a user who participates in the conference. The device set / user ID is information for identifying a device set or a user. The service type is information indicating the type of service such as a video conference or a game.

  In the present embodiment, the device set is a conference room unit, but the device set is not limited to the present embodiment as long as the device set is a group having the device to be used as a member.

  FIG. 4 is a diagram schematically showing the data configuration of the second table 702. As shown in FIG. In the second table 702, service types, media, server IDs, and types are associated with each other. Media is the name of the media used in the service. “Interactive” indicates that the communication is bidirectional. As other communication directions, there are “active” indicating transmission and “passive” indicating transmission. The server ID is information for identifying a server used by the media. In this embodiment, it is the server ID of the audio server 400, the video server 410, and the data server 420. The type indicates the communication method of the corresponding media. For example, there is “relay” indicating that the corresponding media performs communication by relaying the server.

  The service type “tv-conference” is associated with media “audio” and “video”, and the communication direction of both media is “interactive”. Therefore, it can be seen that the video conference as the upper session uses two-way communication of “audio” and “video”.

  Further, the server “ID” and the type “relay” are associated with the medium “video”. This indicates that “video” connects the server identified by the server ID as a relay. Note that the server ID and type are not associated with the media “audio”. This indicates that “audio” is directly connected without a repeater.

  FIG. 5 is a diagram schematically illustrating the data configuration of the third table 703. In the third table 703, the device set / user ID and the device ID are associated with each other. The device ID is information for identifying a device associated with the corresponding device set or user. For example, the device set ID of the conference room A is associated with the device ID of the device installed in the conference room A. The user ID of the user A is associated with the device ID of the device used by the user A. Note that, as described in FIG. 1, the user B does not have his own device, and participates in the video conference using the device installed in the conference room B, so the device ID for the user B is registered. Absent.

  FIG. 6 is a diagram schematically illustrating the data configuration of the fourth table 704. In the fourth table 704, device names, device IDs, and media are associated with each other. In order to conduct a session between devices, it is necessary to satisfy two conditions. The first is that the devices performing the session are associated with the same medium, that is, the session types of the devices performing the session are the same. The second is that the communication direction of the device performing the session corresponds, that is, “active” and “passive”. By referring to the medium and the communication direction in the fourth table 704, it is possible to specify two devices that perform a session.

  FIG. 7 is a diagram schematically illustrating the data configuration of the fifth table 705. In the fifth table 705, a session name, a session ID, a device ID, a medium, a communication direction, an IP address, a port number, and a media attribute are associated with each other.

  The session name is the name of the session. The session ID is information for identifying a session. The device ID is a device ID of a device used for the session. For example, since the microphone A101 accesses the voice server 400, the session name “voice” is associated with the device IDs of the microphone A101 and the voice server 400. That is, when the “voice” session is established, the voice data can be transmitted from the microphone A 101 to the voice server 400. The media indicates the media realized by the session, and the communication direction indicates the communication direction with respect to various servers of the devices installed in the conference room. The IP address and port number indicate the IP address and port number of each device. The media attribute indicates the attribute of the corresponding media.

  The session DB 700 according to the present embodiment corresponds to the first storage unit, the second storage unit, and the third storage unit described in the claims. More specifically, the second table corresponds to the first storage means, the fourth table corresponds to the second storage means, and the fifth table corresponds to the third storage means.

  FIG. 8 is a communication sequence diagram in the communication system 10 when starting a video conference. Here, a case where a video conference is started in the conference room A and the conference room B will be described. In this case, the devices in the conference room A and the conference room B need to be connected to a common audio service and video service, respectively. Processing for this is performed in this communication sequence.

  First, the user A transmits a start request to the session management server 500 from the PC-A 105 to the conference room B as a video conference start command (step S100). FIG. 9 is a diagram illustrating a start request. The start request includes the user ID “userA@xxx.co.jp” of the user A who is the sender, and the device set IDs “roomA@xxx.co.jp” of the conference room A and the conference room B used for the video conference. , “RoomB@xxx.co.jp”, the service to be started, that is, the service type “tv-conference” of the video conference, and the video conference held in the conference room A and the conference room B are distinguished from other video conferences. Information such as service ID “tv-conference-1 @ xxx.co.jp-1 @ xxx.co.jp” is included. Hereinafter, a case where the start request illustrated in FIG. 9 is transmitted will be described as an example.

  The session management server 500 inquires of the session DB 700 about the transfer destination of the received start request (step S102). In the present embodiment, since the condition that all requests are transferred to the upper session management server 600 is stored in the session DB 700, the session management server 500 transfers the start request to the upper session management server 600 (steps). S104). Upon receiving the start request, the upper session management server 600 generates upper session information while referring to the session DB 700 (step S106).

  Then, the upper session management server 600 returns the upper session information as a response to the session management server 500 (step S108). When receiving the response, the session management server 500 returns a response to the PC-A 105 (step S110). Then, a confirmation response is transmitted from the PC-A 105 to the upper session management server 600 via the session management server 500 (step S112), and the upper session management server 600 starts a plurality of sessions based on the upper session information (step S112). S114). This completes the communication sequence.

  FIG. 10 is a flowchart illustrating detailed processing of the upper session management server 600 in the upper session information generation processing (step S106). In the upper session management server 600, when the communication unit 601 receives a start request, first, the service type and service ID of the start request transmission source (From header), destination (To header), and service to be started (body service) are displayed. Specify (step S120). Next, based on this information and the first table 701 of the session DB 700, it is confirmed whether the transmission source and the destination, that is, the device set participating in the service, supports the service to be started.

  In the example shown in FIG. 9, “roomA@xxx.co.jp” indicating the conference room A as the transmission source, “roomB@xxx.co.jp” indicating the conference room B as the destination, and “video conference” as the service “ “tv-conference” is set. In the first table 701 shown in FIG. 3, both “roomA@xxx.co.jp” and “roomB@xxx.co.jp” are associated with the service type “tv-conference”. Therefore, it can be seen that both the conference room A and the conference room B of the transmission source and the destination support the video conference. In other words, the upper session for the service “video conference” can be started.

  In step S122, when the device set as the transmission source and destination indicated in the start request supports the service indicated in the start request (step S122, Yes), the process proceeds to step S124. If it is not supported (No at step S122), the service cannot be started, and the process ends as it is.

  In step S124, the media identifying unit 602 refers to the second table 702 shown in FIG. 4 and identifies the media associated with the video conference service type, that is, the media used in the service (step S124). . Thus, the media specifying unit 602 specifies a plurality of media used in the service.

  Here, by default, as shown in FIG. 4, “audio” is directly connected without a repeater, and “video” is connected via the video server 410 “video-server@xxx.co.jp”. It is defined in the session DB 700. However, in the body of the start request, it is specified that the audio server 400 “audio-server@xxx.co.jp” is used for the relay “relay” of “audio”. In this case, priority is given to the start request, and a session using the voice server 400 indicated in the start request is started.

  Next, the device identification unit 603 refers to the third table 703 and identifies the device ID of the device included in the device set (step S126). In this example, the device identification unit 603 identifies devices associated with the conference room A “roomA@ricoh.co.jp” and the conference room B “roomB@ricoh.co.jp”. In conference room A, microphone A101 “micA@ricoh.co.jp”, speaker A102 “speakerA@ricoh.co.jp”, camera A103 “cameraA@ricoh.co.jp”, display A104 “displayA@ricoh.co.jp” .jp "are associated with each other. Similarly, the conference room B includes a microphone B201 “micB@ricoh.co.jp”, a speaker B202 “speakerB@ricoh.co.jp”, a camera B203 “cameraB@ricoh.co.jp”, and a display B204 “displayB @ ricoh.co.jp "is associated and specified.

  Next, the device identifying unit 603 refers to the fourth table 704, and identifies the media supported by each device identified in step S126 and the media supported by the server identified in the second table 702 (step S128). In this example, a plurality of devices associated with the device sets of the conference room A and the conference room B in the third table 703, the video server 410 specified by the second table 702, and the audio server indicated in the start request Identify 400 supported media.

  The device identifying unit 603 identifies the device ID associated with the medium identified in step S124 in the fourth table 704 from the device IDs identified in step S126 (step S130). The device identified by the device ID specified in step S130 is a device that starts a session using media used in the service. At this time, “active” is a side that transmits information, and “passive” is a side that receives information. Therefore, it should be noted that only “active” and “passive” pairs can transmit and receive information.

  Next, the upper session information management unit 605 generates upper session information used when starting an upper session based on the device ID specified by the device specifying unit 603 (step S132). Specifically, referring to the fifth table 705, information such as a session ID, an IP address, a port number, and a media attribute associated with the device that starts the session is extracted, and the upper session is based on these information. Generate information.

  FIG. 11 is a diagram showing upper session information. As described above, the upper session information includes information on each of a plurality of sessions started in a service called a video conference. In addition, a service ID for identifying this service is included. In the session start process (step S110) described in FIG. 8, the session control unit 606 of the upper session management server 600 starts an upper session, that is, a plurality of sessions, based on the upper session information.

  Since the upper session information includes the service ID, the session management server 500 can make an inquiry to the upper session management server 600 as necessary using the value of the service ID. Since the service ID is created by the device, the service ID included in the upper session information that has already been generated by the upper session information management unit 605 may overlap. In such a case, the upper session information management unit 605 changes the service ID included in the upper session information to be different from the service ID received from the device.

  FIG. 12 is a sequence diagram illustrating a session start process executed under the control of the session control unit 606 of the upper session management server 600. Here, a session between microphone A101 and voice server 400 will be described. The session control unit 606 transmits a connection request between the microphone A 101 and the voice server 400, that is, a session start request to the session management server 500 via the communication unit 601 based on the upper session information (step S140). Next, the session management server 500 makes a transfer destination inquiry to the session DB 700 (step S142), acquires information necessary for starting the session, and transmits a connection instruction including the device ID of the voice server 300 to the microphone A101 (step S142). S144). When session management server 500 receives a response to the connection instruction from microphone A 101 (step S146), it returns a response to host session management server 500 (step S148).

  Next, when the session management server 500 receives a call including the device ID of the voice server 400 from the microphone A 101 (step S150), the session management server 500 makes an inquiry about the transfer destination to the session DB 700 (step S152). To get. Then, a connection instruction is transmitted to the voice server 400 (step S154). Next, the session management server 500 returns a response to the microphone A101 (step S156). When the session management server 500 receives the confirmation response from the microphone A101 (step S158), the session management server 500 notifies the voice server 400 to that effect (step S160), and the session between the voice server 400 and the microphone A101 is started. Is transmitted to the voice server 400. The above processing is realized by a 3PCC mechanism.

  Although the session start process between the microphone A 101 and the voice server 400 has been described here, all other session start processes such as the session start process between the microphone B 201 and the voice server 400 are the same process.

  Through the above process, the microphone A101, which is a device in the conference room A, and the speaker A102 are connected to the audio server 400, thereby realizing two-way audio communication. Further, when the camera A 103 and the display A 104 are connected to the video server 410, bidirectional video communication can be realized. The same applies to the device in the conference room B.

  As described above, in the communication system 10 according to the present embodiment, when a service such as a video conference is started, a plurality of sessions by a plurality of different devices used in the video conference based on the upper session information. Can start.

  FIG. 13 is a sequence diagram showing the upper session termination process. When a service termination request is transmitted from the PC-A 105 or the like (step S200), the session management server 500 inquires of the transfer destination to the session DB 700 (step S202), and transfers the termination request to the upper session management server 600. (Step S204). The upper session management server 600 notifies the session management server 500 of the end of the session (step S206), and then ends the upper session while referring to the session DB 700 (step S208). When the session management server 500 receives the session end notification, it returns a response to the PC-A 105 (step S210).

  FIG. 14 is a sequence diagram showing a session end process (step S206) executed under the control of the session control unit 606 of the upper session management server 600. The session control unit 606 transmits a session disconnection request to the session management server 500 via the communication unit 601 (step S210). The session management server 500 makes an inquiry about the transfer destination to the session DB 700 (step S212), and transmits a disconnection request to the microphone A101 (step S214). Then, when the session management server 500 receives a response indicating that the session has been completed from the microphone A 101, the session management server 500 returns a response to the upper session management server 600 (step S216). Thus, the session between the microphone A101 and the voice server 400 ends. Similarly, the upper session management server 600 ends all the plurality of sessions included in the upper session.

  As described above, when a service termination request is received, all of a plurality of sessions used in the service can be terminated. That is, the service termination timing can also be controlled in units of upper sessions.

  Furthermore, in the communication system 10 according to the present embodiment, a new user can participate in the service while the service is being executed. FIG. 15 is a communication sequence diagram in this case. Here, a case where the user C participates in the middle of the video conference in the conference room A and the conference room B will be described.

  As can be seen from the first table 701 in FIG. 3, the device C300 used by the user C does not support the video conference. Therefore, first, the web page of the conference control server 800 is accessed using the device C300. That is, a participation request is transmitted to the conference control server 800 (step S300).

  By the way, the conference control server 800 can use the function of the upper session management server 600 through the API. The conference control server 800 transmits a request as shown in FIG. 16 to the upper session management server 600 in advance. The request indicates the service type and event in addition to the transmission source. The event is an event regarding the service such as start or update of the service.

  When the upper session management server 600 transmits this request, the upper session information is notified to the conference control server 800 when the service specified in the request, that is, the video conference is started or updated. Therefore, the conference control server 800 can always know whether a video conference has started or updated.

  The conference control server 800 provides a list of video conferences currently being held on the Web page. User C refers to the list of video conferences, selects a video conference that he / she wishes to participate in, and presses a participation button shown on the web page. Accordingly, a response including information indicating the video conference that the user wants to participate from the device C300 is transmitted to the conference control server 800 (step S302).

  When receiving the response, the conference control server 800 sends the request shown in FIG. 17 as a call to the upper session management server 600 (step S304). At this time, HTTP can be used. As shown in FIG. 17, the request includes the device ID of the conference control server that is the transmission source, the user ID of the midway participant, the service type and service ID of the service desired to participate. The upper session management server 600 returns a response to the call to the conference control server 800 (step S306).

  Next, the upper session management server 600 updates the upper session information (step S308), and starts a new session based on the upper session information (step S310). The process when starting a new session is the same as the process described with reference to FIG.

  FIG. 18 is a flowchart showing the processing by the upper session management server 600 in the upper session information update processing (step S308). In the upper session information update process, first, the media specifying unit 602 of the upper session management server 600 specifies the user ID of the midway participant, the service type and service ID of the service desired to participate from the request received in step S304. (Step S320). Next, the media identifying unit 602 refers to the first table 701 shown in FIG. 3 and confirms whether the halfway participant's device supports the service he / she wants to join (step S322).

  Next, the media identifying unit 602 identifies the media associated with the service type of the service indicated in the request with reference to the second table 702 (step S324). Next, the media identifying unit 602 refers to the third table 703, identifies the device ID associated with the user ID of the participant (step S326), and further refers to the fourth table 704 to perform step S326. The medium associated with the device ID specified in step S328 is specified (step S328).

  Next, the device identification unit 603 uses the device ID associated with the medium identified in step S324 in the fourth table 704 from the device IDs identified in step S326, and the device ID of the device that starts the session. (Step S330).

  Next, the upper session information management unit 605 updates already generated upper session information based on the device ID specified by the device specifying unit 603 (step S334). This completes the upper session information update process (step S308).

  As specific processing in response to the request in FIG. 17, the media specifying unit 602 first confirms that the user C supports the video conference based on the first table 701 (step S322). Further, the media “audio” and “video” associated with the video conference are specified from the second table 702 (step S324). Further, the media specifying unit 602 specifies the device C “device@xxx.co.jp”, which is the device of the user C, from the third table 703 (step S326).

  Then, the media “audio” and “video” of the device C are specified from the fourth table 704 (step S328). In this example, the media of the device C and the media associated with the service “video conference” are both “audio” and “video”. Therefore, the device C is specified as a device that starts a session (step S330).

  Then, with reference to the fifth table 705, the session information associated with the device ID of the device C is specified (step S332), and the upper session information is updated based on the specified session information (step S334). At this time, the upper session to be updated is specified by the service ID. FIG. 19 is a diagram illustrating the updated upper session information. In the upper session information shown in FIG. 18, the underlined portion indicates the updated content.

  When the device C300 supports the upper session and the user C knows the conference ID of the conference held in the conference room A and the conference room B, the device C 300 joins the conference control server 800. It is not necessary to send a request. FIG. 20 is a communication sequence diagram when a midway participant knows information for specifying a service. In this case, first, the user C transmits a request shown in FIG. 21 from the device C300 as a participation request to the upper session management server 600 via the session management server 500 (steps S340 to S344). The request shown in FIG. 21 does not include a body. Further, in the request, the service desired to participate is specified by the device set ID of the conference room B, but it is sufficient that information that can identify the service desired to participate is included. The device set ID of the conference room B Instead, the device set ID and service ID of the conference room A may be included.

  In response to the participation request, the upper session management server 600 returns a response shown in FIG. 22 to the device C300 via the session management server 500 (step S346). FIG. 22 is a diagram showing a response. As shown in FIG. 22, the response includes the service ID of the service being performed in the conference room B.

  The device C300 refers to the service included in the response, and transmits conference designation information including the service ID of the service that the device C300 desires to participate to the upper session management server 600 via the session management server 500 (step S348). FIG. 23 is a diagram showing conference designation information. As shown in FIG. 23, the conference designation information in this example includes a video conference service ID “tv-conference-1@xxx.co.jp”. Here, media information and the like in the upper session information can be omitted.

  Through the above processing, the upper session management server 600 can acquire the user ID of the participant and the service ID of the service desired to participate. Based on these pieces of information, the upper session management server 600 updates the upper session information (step S308) and starts a new session (step S310). Note that these processes are the same as those described with reference to FIGS. 15 and 16.

  Furthermore, withdrawal during a video conference is also possible. For example, when the device C300 wishes to withdraw from the video conference, a withdrawal request is transmitted to the upper session management server 600 via the session management server 500 as in the case of participation. The withdrawal request includes the device ID of the device that desires withdrawal, that is, the device ID of the device C300 and the service ID of the service that desires withdrawal (upper session).

  In the upper session management server 600, when the communication unit 601 receives the withdrawal request, the upper session information unit 605 identifies the upper session information of the upper session identified by the service ID, and is included in the withdrawal request from the upper session information. The information regarding the session using the device identified by the device ID is deleted. The session control unit 606 then ends the session using the device identified by the device ID included in the withdrawal request based on the updated upper session information by the upper session information management unit 605.

  In the communication system 10 according to the present embodiment, by further registering an event in the session DB 700, when a registered event is generated or updated, predetermined information is notified to a previously registered notification destination. Is done.

  FIG. 24 is a communication sequence diagram showing event registration processing. The conference control server 800 transmits an event registration instruction to the upper session management server 600 (step S400). The event registration instruction includes the type of the upper session as an event and the event notification destination. The upper session management server 600 returns a response to the event registration instruction to the conference control server 800 (step S402), and stores the event indicated in the event registration instruction and the notification destination in the session DB 700 in association with each other.

  FIG. 25 is a communication sequence diagram showing an event notification process at the start of the upper session. When the upper session starts (step S410), the upper session management server 600 inquires of the notification destination associated with the started upper session to the session DB 700 (step S412). Then, the notification destination is received from the session DB 700 (step S414). When the notification destination is the conference control server 800, the conference control server 800 is notified of the higher session information (step S416), and a response indicating that the notification is received from the conference control server 800 is received (step S418). Processing is complete.

  FIG. 26 is a communication sequence diagram illustrating an event notification process when the upper session information is updated. When the upper session information is updated (step S420), the upper session management server 600 makes an inquiry about the notification destination associated with the updated upper session to the session DB 700 (step S422). Then, the notification destination is received from the session DB 700 (step S424). When the notification destination is the conference control server 800, the conference control server 800 is notified of the upper session information (step S426), and a response indicating that the notification is received from the conference control server 600 is received (step S428). Processing is complete.

  In the communication system 10 according to the present embodiment, a session started in a service can be added or deleted, that is, updated. FIG. 27 is a diagram illustrating a data configuration of the second table 702 after the update. Thus, the server ID “data-server@xxx.co.jp” of the data server 420 is newly associated with the service type of the video conference. The update is performed by the conference control server 800 using the API of the upper session management server 600, for example.

  Further, when the session DB 700 is updated during the video conference in the conference room A and the conference room B described above, the device identification unit 603 refers to the third table 703 shown in FIG. A device that can communicate with the data server 420 is identified from the devices corresponding to the conference room A and the conference room B and the devices used by the users participating in the conference.

  In this example, it can be seen that the PC-A 105 owned by the user A1 can communicate with the data server 420. Therefore, the upper session management server 600 notifies the PC-A 105 via the session management server 500 that the data communication is possible in accordance with the event notification process at the time of updating the upper session shown in FIG. Thereby, the user A1 can know that the data server 420 can be used. Then, the user A1 can use data communication such as instructing the start of a session between the data server 420 and the PC-A 105 as necessary and acquiring data from the data server 420. The session start process between the PC-A 105 and the data server 420 is the same as the process described with reference to FIG. 12, and the microphone A101 and the voice server 400 in FIG. 12 are replaced with the PC-A1-5 and the data server 4420, respectively. Good. Note that the session start processing by the PC-A 105 is the same as the processing described with reference to FIG. 12, and when the session is established, data is transmitted from the data server 420 to the PC-A 105. As described above, in the communication system 10, an arbitrary session can be added to an already registered higher session.

  As another example, the upper session management server 600 uses the PC in addition to or instead of notifying the PC-A 105 that data communication has become possible after updating the session DB 700. -A session between the A105 and the data server 420 may be started.

  When desiring to delete a session, for example, the conference control server 800 transmits a delete instruction to the upper session management server 600. The deletion instruction includes the service type of the deletion source service and the medium to be deleted. When the session management server 600 receives the deletion instruction, the session DB management unit 607 updates the session DB 700 according to the deletion instruction. Specifically, in the second table 702, the media associated with the service type specified by the service type included in the deletion instruction is deleted. In this way, unnecessary sessions can be deleted from the upper session.

  As described above, in the communication system 10 according to the present embodiment, it is possible to add or delete a session included in an already registered higher level session. It is possible to provide an upper session, that is, a service suitable for the usage form.

  As a first modification of the communication system 10 according to the present embodiment, privileged access may be permitted in an upper session. FIG. 28 is a diagram schematically illustrating a data configuration of the second table 712 according to the first modification. In the second table 712, the additional access right is further associated with the service ID. The additional access right is information indicating whether or not access to the server is permitted, and “privileged” indicates that a privilege is given to a participant in the corresponding service. That is, the additional access right is access restriction information indicating permission or prohibition of special access while the service is being performed. For example, as shown in FIG. 28, when “privileged” is associated with a video conference, a participant in the video conference can access that is not originally permitted.

  In FIG. 28, “privileged” is associated with the data server 420 in the video conference. Therefore, participants in the video conference are permitted to access the data server 420 that is not originally permitted only during the video conference. The access right is notified from the upper session management server 600 to the data server 420 via the session management server 500 during call control. When the data server 420 receives this notification, the data server 420 permits special access during the designated session. That is, the session control unit 606 of the upper session management server 600 can start a corresponding session when the “privileged” additional access right is associated. In this way, by providing a privilege, it is possible to provide a service with excellent convenience.

  As a second modification, the upper session management server 600 may further control the start and end timings of the upper session. Specifically, the upper session information management unit 605 of the upper session management server 600, for example, in accordance with an instruction from the conference control server 800, includes upper timing information including timing information indicating the start and end timing of each session included in the upper session. Generate session information. FIG. 29 is a diagram showing upper session information. Thus, since the upper session information includes the start and end timings, the session control unit 606 can control the start and end timings of each session according to these timings.

  The conference control server 800 may manage a video conference using this function. Specifically, the conference control server 800 acquires upper session information including start and end timings. Thereby, the start and end timing of each video conference can be known. Therefore, notification of the start or end of the video conference from the host session management server 600 at the timing when the video conference is actually started and ended is not necessary.

  As a third modification, in the present embodiment, the session DB 700 associates various data with a plurality of tables, but the upper session and the plurality of sessions included therein are associated with each other. Each session and a device used in each session need only be associated with each other, and the data configuration of session DB 700 is not limited to the present embodiment.

  As a fourth modification example, in the present embodiment, the upper session management server 600 receives a service start command in units of device sets, but instead designates a device to participate in the service. A service start command may be received. In this case, it is not necessary to specify a plurality of corresponding devices from the device set, and higher session information using the device indicated in the start command is generated.

(Second Embodiment)
FIG. 30 is a diagram illustrating an overall configuration of a communication system 30 according to the second embodiment. The communication system 30 further includes a presence server 900. The presence server 900 manages the presence information of the devices of the communication system 30. Presence information is information indicating the status of each device, for example, whether the device is offline or online. The presence server 900 according to the present embodiment further manages information related to the upper session, that is, services such as whether each device is in a video conference as presence information.

  FIG. 31 is a diagram illustrating a communication sequence when the communication system 30 according to the second embodiment starts an upper session as a service. When the upper session management server 600 generates the upper session information (step S106), the upper session management server 600 next requests presence information from the presence server 900 (step S170), and acquires the presence information of the devices related to each session included in the upper session. (Step S172). The acquisition of information from the presence server 900 can be realized by a known presence distribution mechanism such as SIP or XMPP (extensible messaging and presence protocol).

  Based on the presence information, the session control unit 606 of the upper session management server 600 confirms whether or not the devices related to each session are in a communicable state. For example, when presence information indicating offline is acquired for a predetermined device, it is understood that communication is impossible. On the other hand, when the presence information indicating online is acquired, it can be determined that communication is possible.

  If all devices related to the session are communicable (step S174, Yes), the session control unit 606 of the upper session management server 600 starts a session based on the upper session information (step S110). In this way, by referring to the presence information of all devices related to the upper session, the start of a plurality of sessions included in the upper session can be adjusted to an appropriate timing.

  Furthermore, when the session control unit 606 starts a session, the session control unit 606 transmits upper session information to the presence server 900 (step S176). When the presence server 900 receives the upper session information, the presence server 900 updates the presence information based on the upper session information (step S178).

  For example, when a session related to a video conference is started, upper session information of the video conference is transmitted to the presence server 900. Based on the upper session information, the presence server 900 rewrites the presence of the participant in the video conference to “during video conference”. In this way, by using presence information, finer session control can be performed.

  The upper session information is a meaningful set including a plurality of different sessions. Therefore, more accurate presence information can be provided by using such higher-level session information. In addition, the presence server 900 automatically generates presence information in response to an instruction from the upper session management server 600, thereby making it unnecessary to manually update the presence information by the user. In addition, the presence server 900 can use such information for service logging or the like by subscribing the start, update, and end of the upper session.

  The remaining configuration and processing of the communication system 30 according to the present embodiment are the same as those of the communication system 10 according to the first embodiment.

(Third embodiment)
FIG. 32 is a diagram illustrating an overall configuration of a communication system 40 according to the third embodiment. The communication system 40 includes a data server 420, a session management server 500, an upper session management server 610, and a session DB 700, and a telephone A110 and a telephone B120 that are connected to the network 20.

  In the communication system 40 according to the third embodiment, a single session can be promoted to an upper session. For example, during a call between the user A and the user B using the telephone A110 and the telephone B120, the user A may desire to access the data server 420, such as wanting to show the specific moving image data to the user B. In such a case, the upper session management server 610 generates upper session information for an upper session obtained by adding another session called data communication to a single session called a call.

  FIG. 33 is a communication sequence diagram illustrating the promotion process to the upper session by the communication system 40. Here, as described above, during the call between the phone A110 and the phone B120, in addition to the call between the phone A110 and the phone B120, a host session including a session related to data communication between the phone A110 and the phone B and the data server 420 is newly added. An example of generating the data will be described.

  First, a data sharing request is transmitted from the telephone A110 to the upper session management server 610 via the session management server 500 (steps S500 to S506). The data sharing request includes information regarding the current call, the user ID of user A and the device ID of phone A, the user ID of user B and the device ID of phone B, the medium of data communication desired to be added, and the communication destination. The information necessary for starting the data communication session of the telephone A and the telephone B, such as the server ID of the data server 420 which is the server, is included.

  When the upper session management server 610 receives the data sharing request, the session DB management unit 607 updates the session DB 700 based on the data sharing request (step S508). When the upper session management server 610 receives a response indicating the completion of update from the session DB 700 (step S510), registration of the upper session including data communication to the session DB 700 is completed for the telephone A110 via the session management server 500. A response indicating this is transmitted (step S512). In step S512, a response may be transmitted not only to the phone A110 but also to the phone B120. Thereby, both the user A and the user B can know that the upper session has been added.

  In the update process of the session DB 700, the second table 722 is updated. FIG. 34 is a diagram schematically illustrating the data configuration of the second table 722 after the update. Thus, in addition to the already registered video conference, a service (higher level session) called “data supply call” is newly added. The “data sharing call” is associated with the medium “data” for data communication in addition to the medium “audio” corresponding to the call.

  In the first table 701, the third table 703, the fourth table 704, and the fifth table 705, it is assumed that various types of information regarding the phone A and the phone B are registered in advance.

  User A transmits a start request shown in FIG. 35 after confirming the addition of a higher-level session to session DB 700 by receiving the response. Thereby, upper session information is generated and a session included in the upper session is started. In this example, a session between the telephone A 110 and the data server 420 and a session between the telephone B and the data server 420 are started. Thereby, user A and user B can download data from the data server 420. The process after the start request is transmitted is the same as the process described with reference to FIG.

  Through the above processing, a single session can be promoted to an upper session, so that data communication can be performed during a call. Furthermore, when it is desired to restrict the data communication, the additional access right may be specified in the data sharing request. Thereby, the additional access right can also be registered as shown in FIG.

  For example, there may be a case where access to a product or server is temporarily permitted during a conference call with a customer. In this case, it is often necessary to monitor employees for security reasons such as ISMS (Information Security Management System). Therefore, by adding data communication with an additional access right (privilege) during the upper session of the conference call, monitoring and limited access (access only while the conference call is ongoing) are possible.

  The remaining configuration and processing of the communication system 40 according to the third embodiment are the same as the configuration and processing of the communication system according to the other embodiments.

  The host session management server of the present embodiment includes a control device such as a CPU, a storage device such as a ROM (Read Only Memory) and a RAM, an external storage device such as an HDD and a CD drive device, and a display device such as a display device. And an input device such as a keyboard and a mouse, and has a hardware configuration using a normal computer.

  A program executed by the host session management server of the present embodiment is an installable format or executable format file, such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), or the like. Recorded on a readable recording medium.

  Further, the program executed by the upper session management server of the present embodiment may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. Further, the program executed by the upper session management server of the present embodiment may be configured to be provided or distributed via a network such as the Internet.

  Further, the program of this embodiment may be configured to be provided by being incorporated in advance in a ROM or the like.

  The program executed by the upper session management server of the present embodiment includes the above-described units (communication unit, media identification unit, device identification unit, session information identification unit, upper session information management unit, session control unit, session DB management unit). ), And as actual hardware, the CPU (processor) reads the program from the storage medium and executes the program, so that the respective units are loaded onto the main storage device, and the respective units are installed on the main storage device. To be generated.

10, 30, 40 Communication system 20 Network 101 Microphone A
102 Speaker A
103 Camera A
104 Display A
105 PC-A
201 Mike B
202 Speaker B
203 Camera B
204 Display B
205 PC-B
400 Audio server 410 Video server 420 Data server 500 Session management server 600, 610 Upper session management server 601 Communication unit 602 Media identification unit 603 Device identification unit 605 Upper session information management unit 606 Session control unit 607 Session DB management unit 700 Session DB
800 Conference control server 900 Presence server

JP 2006-135954 A JP 2006-319697 A

Claims (16)

An upper session management server connected via a network to a session management server that manages communication sessions between a plurality of devices,
A start command including information instructing start of a service using a plurality of sessions, service type information indicating the type of service, and device identification information for identifying a device participating in the service from the session management server Receiving means for receiving;
First storage means for storing the service type information and session type information indicating the type of session used in the service in association with each other;
Second storage means for storing the device identification information in association with the session type information of a session in which the device is used;
Third storage means for storing the device identification information in association with session information used when the device performs a session;
In the first storage means, a session type specifying means for specifying a plurality of the session type information associated with the service type information received by the receiving means;
Of the device identification information received by the receiving means, device specifying means for specifying a plurality of the device identification information associated with the session type information specified by the session specifying means in the second storage means When,
In the third storage means, session information specifying means for specifying the plurality of session information associated with each of the plurality of device identification information specified by the device specifying means;
A host session management server comprising: session control means for performing the service by starting a plurality of sessions based on a plurality of pieces of session information specified by the session information specifying means. Based on a plurality of the session information specified by the session information specifying means, further comprising upper session information management means for generating higher session information used when starting a plurality of sessions,
The upper session management server according to claim 1, wherein the session control unit starts a plurality of the sessions based on the upper session information. The upper session information management means generates the upper session information including service identification information for identifying a service indicated in the upper session information,
While the service is being performed, the receiving means, from a participating device that desires new participation in the service, the device identification information of the participating device, the service type of the service that is desired to participate, and the service Further receiving a join request including service identification information identifying the service;
The session specifying means specifies the session type information associated with the service type information received by the receiving means in the first storage means,
The device identification unit includes the device identification associated with the session type identified by the session identification unit in the second storage unit among the device identification information of the participating device received by the reception unit. Identify information,
The session information specifying means specifies the session information associated with the device identification information specified by the device specifying means in the third storage means,
The upper session information management means updates the upper session information identified by the service identification information received by the receiving means, based on the session information specified by the session information specifying means,
3. The upper session management server according to claim 2, wherein the session control unit starts a new session with the participating device based on the upper session information updated by the upper session information management unit. . The receiving means includes information requesting withdrawal of the device participating in the service from the service during a session between a plurality of devices corresponding to the service, and the device of the device participating in the service. Further receiving a withdrawal request including identification information and service identification information identifying the service in which the device is participating;
The upper session information management means includes information on a session using the device identified by the device identification information received together with the withdrawal request from the upper session information identified by the service identification information received by the receiving means. Delete,
The session control means terminates a session using the device indicated by the device identification information received together with the withdrawal request based on the higher session information after deletion by the higher session information management means. The upper session management server according to claim 2. The receiving means further receives an addition request including information requesting addition of a new session to the service, the service type information of the service, and the session type information of the new session;
The update means for adding the session type information of the new session in association with the service type information received by the receiving unit in the first storage unit. Top session management server. The receiving means further receives a deletion request including information requesting deletion of a predetermined session included in the service, the service type information of the service, and the session type information of a predetermined session;
The update means for deleting the session type information included in the deletion request associated with the service type information received by the receiving unit from the first storage unit. 1. The upper session management server according to 1. The receiving means further receives an instruction to end the service,
The upper session management server according to claim 1, wherein the session control means terminates a plurality of sessions related to the service when the receiving means receives the termination command. The first storage means further stores access restriction information indicating permission or prohibition of special access during service in association with the service type information,
2. The upper session according to claim 1, wherein the session control information starts the plurality of sessions when the access control information indicating permission of the access is stored in the first storage unit. Management server. The receiving means receives the start command including start time information indicating a start time of the service;
The upper session management server according to claim 1, wherein the session control means starts the plurality of sessions at the start time when the reception means receives the start time information. The receiving means receives the start command including end time information indicating an end time of the service;
The upper session management server according to claim 1, wherein the session control unit ends the plurality of sessions at the end time when the receiving unit receives the end time information.   The host system according to claim 1, further comprising a transmission unit configured to transmit status information indicating the start, update, or end of each session to the outside when the plurality of sessions start, update, or end. Session management server. The receiving means further receives status information indicating the status of the device;
The session control unit, when all devices used for the plurality of sessions can start a session based on the state information of each of the plurality of devices used for the plurality of sessions, The upper session management server according to claim 1, wherein the upper session management server is started.   The reception means receives the start instruction including information requesting the start of the higher-level session including the session and the device identification information of the device performing the predetermined session during the start of the predetermined session. In this case, the session control unit starts the session specified by the device type information. The upper session management server according to claim 1, A session management method in a session management server that manages a communication session between a plurality of devices and a host session management server connected via a network,
The upper session management server is:
First storage means for storing the service type information and session type information indicating the type of session used in the service in association with each other;
Second storage means for storing the device identification information in association with the session type information of a session in which the device is used;
Third storage means for storing the device identification information and session information used when the device performs a session in association with each other;
The receiving means receives from the session management server information for instructing the start of a service using a plurality of sessions, service type information indicating the type of service, and device identification information for identifying a device participating in the service. A receiving step for receiving a start instruction including:
A session type specifying unit for specifying a plurality of the session type information associated with the service type information received in the receiving step in the first storage unit;
Among the device identification information received by the receiving step by the device specifying unit, a plurality of the device identification information associated with the session type information specified by the session type specifying step in the second storage unit Device identification step to identify
A session information specifying unit for specifying a plurality of session information associated with each of the plurality of device identification information specified in the device specifying step in the third storage unit;
A session control unit, comprising: a session control step for performing the service by starting a plurality of sessions based on a plurality of session information specified by the session information specifying unit. A program for causing a computer connected via a network to a session management server for managing a communication session between a plurality of devices,
The computer
First storage means for storing the service type information and session type information indicating the type of session used in the service in association with each other;
Second storage means for storing the device identification information in association with the session type information of a session in which the device is used;
Third storage means for storing the device identification information and session information used when the device performs a session in association with each other;
A start command including information instructing start of a service using a plurality of sessions, service type information indicating the type of service, and device identification information for identifying a device participating in the service from the session management server A receiving step for receiving;
In the first storage means, a session type specifying step for specifying a plurality of the session type information associated with the service type information received in the receiving step;
Of the device identification information received in the reception step, device identification that identifies a plurality of the device identification information associated with the session type information identified in the session type identification step in the second storage unit Steps,
In the third storage means, a session information specifying step for specifying a plurality of the session information associated with each of the plurality of device identification information specified in the device specifying step;
A program for causing the computer to execute a session control step of performing the service by starting a plurality of sessions based on a plurality of session information specified by the session information specifying means. An upper session system comprising a plurality of devices, a session management server for managing communication sessions between the plurality of devices, and an upper session management server connected to the session management server via a network,
The first device of the plurality of devices is
Transmission means for transmitting a start command including information instructing start of a service using a plurality of sessions, service type information indicating a type of service to be started, and device identification information for identifying a device participating in the service Have
The upper session management server includes a receiving unit that receives the start command from the first device via the session management server;
First storage means for storing the service type information and session type information indicating the type of session used in the service in association with each other;
Second storage means for storing the device identification information in association with the session type information of a session in which the device is used;
Third storage means for storing the device identification information in association with session information used when the device performs a session;
In the first storage means, a session type specifying means for specifying a plurality of the session type information associated with the service type information received by the receiving means;
Among the device identification information received by the receiving means, device specifying means for specifying a plurality of device identification information associated with the session type specified by the session specifying means in the second storage means; ,
In the third storage means, session information specifying means for specifying the plurality of session information associated with each of the plurality of device identification information specified by the device specifying means;
A host session management system comprising session control means for performing the service by starting a plurality of sessions based on a plurality of session information specified by the session information specifying means.

Images