JP2021184538A - Identification information management apparatus, identification information management system, communication system and program - Google Patents

Abstract

To provide an identification information management apparatus, an identification information management system, a communication system and a program, capable of setting the number of identification information used for communication with other terminal unit to an appropriate number, according to a use situation of the identification information in each terminal unit, the identification information being granted to each terminal unit of a plurality of terminal units communicating with each other.SOLUTION: An identification information management apparatus includes: granting means to grant, to each terminal unit of a plurality of terminal units communicating with each other, identification information used for communication with other terminal unit; acquisition means to acquire a use situation of the identification information in each terminal unit, the identification information being granted to each terminal unit by the granting means; and adjustment means to adjust the number of the identification information to be granted to each terminal unit by the granting means, depending on the use situation acquired by the acquisition means.SELECTED DRAWING: Figure 8

Description

The present disclosure relates to identification information management devices, identification information management methods, communication systems and programs.

In Patent Document 1, in a terminal management system having a terminal, a management device, and a communication control device, an ID management means of the communication control device generates and generates a PeerID in response to a request for registration of the PeerID from the terminal or the management device. The ID registration information associated with the PeerID and the address information of the terminal or management device that is the source of the registration request is stored in the storage means, and the generated PeerID is stored in the terminal or management device that is the source of the registration request. It is stated to notify. Further, in Patent Document 1, in a terminal management system having a terminal, a management device, and a communication control device, the ID management means of the communication control device receives a registration request including a PeerID from the terminal or the management device, and the received PeerID. It is also described that the ID registration information associated with the address information of the terminal or the management device that is the transmission source of the registration request is stored in the storage means.

Japanese Unexamined Patent Publication No. 2016-134715

In a system that assigns identification information used for communication with other terminal devices to each terminal device of a plurality of terminal devices that communicate with each other, it is assumed that the number of identification information assigned to each terminal device is left as it is. .. In such a case, if the number of other terminal devices with which each terminal device communicates at the same time increases, there will be no usable identification information, while if the number of other terminal devices with which each terminal device communicates at the same time decreases, it will be used. Possible identification information will be added in vain. Therefore, the number of identification information given to each terminal device cannot be set to an appropriate number according to the usage status of the identification information in each terminal device.

In the present disclosure, the number of identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other is appropriate according to the usage status of the identification information in each terminal device. The purpose is to have a large number.

The identification information management device of the present disclosure includes an giving means for giving identification information used for communication with other terminal devices to each terminal device of a plurality of terminal devices communicating with each other, and the giving means is the above-mentioned respective. The identification information given to each terminal device by the giving means according to the acquisition means for acquiring the usage status of the identification information given to the terminal device in each terminal device and the usage status acquired by the acquisition means. It is an identification information management device provided with an adjusting means for adjusting the number of the above.

According to this identification information management device, the number of identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other is determined by the identification information in each terminal device. The number can be set appropriately according to the usage situation.

Here, the usage status may be the number of the identification information given to each terminal device by the granting means, which has not yet been used for communication with another terminal device.

In this way, the number of identification information used for communication with other terminal devices, which is given to each terminal device of a plurality of terminal devices that communicate with each other, is used for communication with other terminal devices. It can be an appropriate number according to the number of identification information that has not been used yet.

Further, the usage status may be a situation in which the number of the unused identification information exceeds or falls below a specific number.

In this way, the number of identification information used for communication with other terminal devices, which is given to each terminal device of a plurality of terminal devices that communicate with each other, is used for communication with other terminal devices. It can be an appropriate number according to the magnitude relationship between the number of identification information that has not been used yet and the specific number.

Further, the identification information management device of the present disclosure is at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to give the identification information to each terminal device. Based on the above, it may be further provided with a determination means for determining the specific number.

In this way, a specific number to be compared with the number of identification information that has not yet been used for communication with other terminal devices can be set as an appropriate number.

Further, the giving means may give at least the specific number of the identification information to each of the terminal devices when the terminal devices are activated.

In this way, the number of identification information used for communication with other terminal devices, which is given to each terminal device of a plurality of terminal devices that communicate with each other, is used for communication with other terminal devices. It may reduce the possibility that new identification information must be added to each terminal device in order to obtain an appropriate number according to the magnitude relationship between the number of identification information that has not been used yet and the specific number. can.

Further, the identification information management device of the present disclosure is at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to give the identification information to each terminal device. Based on the above, the terminal device may be further provided with a determination means for determining the number of the identification information given when the terminal device is activated.

By doing so, the number of identification information given when each terminal device is activated can be set to an appropriate number.

Further, the identification information management device of the present disclosure clearly indicates the number of the identification information that has not been used yet or the identification information that has not been used yet in the identification information given to each terminal device by the granting means. It may be further provided with a transmission means for transmitting the information to be displayed in the above-mentioned format to each terminal device.

In this way, among the identification information given to each terminal device, the user can be made to recognize the identification information or the number thereof which has not been used for communication with other terminal devices.

Further, the giving means may give each terminal device the identification information prepared in advance to a user who uses each terminal device or a group to which the user belongs.

By doing so, the identification information given to each terminal device can be set according to the user who uses each terminal device.

Further, in the identification information management device of the present disclosure, the information regarding the identification information given to each terminal device by the giving means is the information of the plurality of terminal devices prior to the communication between the plurality of terminal devices. It may be further provided with a control means for controlling so as to be notified to the intermediary device that mediates the above.

In this way, the information regarding the identification information given to each terminal device can be held in the intermediary device that mediates the information of the plurality of terminal devices before the plurality of terminal devices communicate with each other.

Further, the identification information may be information used for establishing P2P communication by the communication means of WebRTC.

By doing so, the number of identification information used for establishing P2P communication by the communication means of WebRTC can be set to an appropriate number according to the usage status of the identification information in each terminal device.

Further, the identification information management method of the present disclosure includes a step of imparting identification information used for communication with another terminal device to each terminal device of a plurality of terminal devices communicating with each other, and to each of the terminal devices. A step of acquiring the usage status of the given identification information in the terminal device and a step of adjusting the number of the identification information given to the terminal device according to the acquired usage status. It is an identification information management method including.

According to this identification information management method, the number of identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other is determined by the identification information in each terminal device. The number can be set appropriately according to the usage situation.

Further, the communication system of the present disclosure includes a plurality of terminal devices that communicate with each other and an identification information management device that manages identification information used by the plurality of terminal devices for communication with other terminal devices. The identification information management device determines the usage status of the identification information given to each terminal device of the plurality of terminal devices by the giving means and the identification information given to each terminal device by the giving means. It is a communication system including an acquisition means to be acquired and an adjustment means for adjusting the number of identification information imparted to each terminal device by the granting means according to the usage status acquired by the acquisition means.

According to this communication system, the number of identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other is determined by the usage status of the identification information in each terminal device. The appropriate number can be set according to the above.

In addition, the program of the present disclosure informs the computer of the usage status of the identification information used for communication with other terminal devices assigned to each terminal device of a plurality of terminal devices communicating with each other in the terminal device. It is a program for realizing the function to be acquired and the function to adjust the number of the identification information given to each of the terminal devices or to request the adjustment according to the acquired usage status.

According to the computer in which this program is installed, the number of identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other is determined by the identification information in each terminal device. It can be an appropriate number according to the usage situation of.

It is a figure which showed the whole structure example of the communication system to which this embodiment is applied. It is a figure which showed the hardware configuration example of the management server in this embodiment. It is a figure which showed the example of the initial state of the communication system in this embodiment. It is a figure which showed the example of the state immediately after the peer ID was given to the terminal apparatus in the communication system in this embodiment. It is a figure which showed the example of the state when the communication between the terminal apparatus is performed in the communication system in this embodiment. It is a figure which showed the example of the state when the peer ID is newly given to the terminal apparatus in the communication system in this embodiment. It is a figure which showed the example of the state when the peer ID is newly given to the terminal apparatus in the communication system in this embodiment. It is a block diagram which showed the functional composition example of the management server in the communication system of this embodiment. It is a graph which showed the relationship between the number of initial peer IDs and the charge required when the number of initial peer IDs is adopted. It is a figure which showed the method of determining the optimum initial peer ID number. It is a sequence diagram which showed the 1st operation example of the communication system in this embodiment. It is a sequence diagram which showed the 1st operation example of the communication system in this embodiment. It is a sequence diagram which showed the 2nd operation example of the communication system in this embodiment. It is a sequence diagram which showed the 2nd operation example of the communication system in this embodiment. It is a sequence diagram which showed the 3rd operation example of the communication system in this embodiment. It is a sequence diagram which showed the 3rd operation example of the communication system in this embodiment.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the following, peer-to-peer communication (hereinafter referred to as “P2P communication”) by WebRTC (Web Real-Time Communication) will be described as an example. WebRTC is a framework that realizes real-time communication on a Web browser.

[Overall configuration of communication system]
FIG. 1 is a diagram showing an overall configuration example of a communication system 10 to which the present embodiment is applied. As shown in the figure, the communication system 10 is configured by connecting terminal devices 100a to 100d, a management server 200, and a signaling server 300 to a communication line 900. Although the terminal devices 100a to 100d are shown in the figure, they may be referred to as a terminal device 100 when it is not necessary to distinguish between them. Although the figure shows four terminal devices 100, two, three, or five or more terminal devices 100 may be provided.

The terminal device 100 is a device used for performing real-time communication by P2P communication with another terminal device 100. In the following, the terminal device 100 will be described as being used by, but not limited to, a remote supporter who supports work remotely and a plurality of field workers who receive work support from the remote supporter. do. In particular, the terminal device 100a is assumed to be used by the user A of the user ID "A" who is a remote supporter. Further, the terminal devices 100b, 100c, and 100d are assumed to be used by the user B of the user ID "B", the user C of the user ID "C", and the user D of the user ID "D", respectively, who are field workers. .. As the terminal device 100a, for example, a desktop PC, a notebook PC, a mobile information terminal or the like may be used, and as the terminal devices 100b to 100d, for example, a mobile information terminal or the like may be used.

The management server 200 assigns each terminal device 100 a peer ID used for P2P communication with another terminal device 100, and manages the granting status of which peer ID is added to which terminal device 100. It is a server. The management server 200 holds a peer ID management list in order to manage the status of granting peer IDs. In this embodiment, the peer ID is used as an example of the identification information used for communication with other terminal devices. As the management server 200, for example, a general-purpose personal computer may be used.

The signaling server 300 is a server for exchanging information such as peer IDs with each other in order to perform P2P communication by WebRTC between the terminal devices 100. The signaling server 300 manages the connection state of which terminal device 100's peer ID registered by each terminal device 100 is connected to which terminal device 100's peer ID. The signaling server 300 holds a peer ID registration list in order to manage the connection status of the peer ID. With reference to this peer ID registration list, the signaling server 300 grasps the peer ID of the terminal device 100 of the communication partner of the peer ID included in the communication request from the terminal device 100, and relays the P2P communication between the terminal devices 100. do. In the present embodiment, the signaling server 300 is provided as an example of the mediation device that mediates the information of the plurality of terminal devices prior to the plurality of terminal devices communicating with each other.

The communication line 900 is a communication means used for information communication between the terminal device 100 and the management server 200, and between the terminal device 100 and the signaling server 300. As the communication line 900, for example, the Internet may be used.

[Hardware configuration of management server]
FIG. 2 is a diagram showing a hardware configuration example of the management server 200 according to the present embodiment. As shown in the figure, the management server 200 includes a CPU (Central Processing Unit) 201 which is a calculation means, a RAM (Random Access Memory) 202 which is a storage means, a ROM (Read Only Memory) 203, and a storage device 204. The RAM 202 is a main storage device (main memory), and is used as a working memory when the CPU 201 performs arithmetic processing. Data such as a program and a set value prepared in advance are stored in the ROM 203, and the CPU 201 can directly read the program and the data from the ROM 203 and execute the process. The storage device 204 is a means for storing programs and data. A program is stored in the storage device 204, and the CPU 201 reads the program stored in the storage device 204 into the main storage device and executes the program. Further, the storage device 204 stores and stores the result of processing by the CPU 201. As the storage device 204, for example, a magnetic disk device, an SSD (Solid State Drive), or the like is used.

[Outline of the present embodiment]
In the communication system 10 having such a configuration, in the present embodiment, the number of peer IDs initially assigned to the terminal device 100 (hereinafter referred to as "initial number of peer IDs") depends on the attributes of the user and the like. It shall be set. Further, a lower limit of the number of peer IDs reserved as peer IDs that can be used for communication with the other terminal device 100 (hereinafter referred to as "lower limit peer ID number") is also set. In such a state, the communication system 10 monitors the connection status in the terminal device 100, and when the number of usable peer IDs of the terminal device 100 is less than or exceeds the lower limit number of peer IDs, the peer ID is added. Or delete it. Hereinafter, such a schematic operation will be specifically described. The number of initial peer IDs and the number of lower limit peer IDs may be equal to or different from each other, but in the description of this outline, the case where they are different will be taken as an example. Specifically, for the terminal device 100a used by the remote supporter, the number of initial peer IDs is 5 and the number of lower limit peer IDs is 3. Further, the number of initial peer IDs of the terminal devices 100b to 100d used by the field worker is set to 3. Further, in the description of this outline, only the case where the peer ID is added is taken as an example.

FIG. 3 is a diagram showing an example of an initial state of the communication system 10 in the present embodiment.

As shown in the figure, the management server 200 manages the user ID of the user, the attributes of the user, the peer ID that can be assigned to the terminal device 100 logged in by the user ID, and the peer ID state. It has a management list 210. As described above, in the peer ID management list 210, a peer ID that can be assigned to each user ID of the user is prepared in advance. Alternatively, a peer ID that can be assigned to each user attribute may be prepared in advance. Here, the attribute of the user is, for example, whether it is a remote supporter or a field worker, or a position such as a department manager or a section manager. Alternatively, in the peer ID management list 210, a peer ID that can be assigned to each attribute of the group to which the user belongs may be prepared in advance. For example, peer IDs "A_1", "A_2", ... Can be assigned to the terminal device 100a logged in by the user A who is a remote supporter. Peer IDs "B_1", "B_2", ... Can be assigned to the terminal device 100b logged in by the user B who is a field worker. A peer ID "C_1", ... Can be assigned to the terminal device 100c logged in by the user C who is a field worker. A peer ID "D_1", ... Can be assigned to the terminal device 100d logged in by the user D who is a field worker. In the initial state, the peer ID is not assigned to any of the terminal devices 100, so that the states of all the peer IDs are "not assigned" in the peer ID management list 210.

Further, the signaling server 300 has a peer ID registration list 310 in which the connection state of the peer ID assigned to the terminal device 100 is registered. However, in this state, since the peer ID is not assigned to any of the terminal devices 100, the peer ID is not registered in the peer ID registration list 310.

FIG. 4 is a diagram showing an example of a state immediately after a peer ID is assigned to the terminal device 100 in the communication system 10 in the present embodiment.

Here, it is assumed that a peer ID is assigned to the terminal devices 100a to 100d. The number of initial peer IDs of the terminal device 100a logged in by the user A who is a remote supporter is 5 as described above. Therefore, it is assumed that "A_1", "A_2", "A_3", "A_4", and "A_5" are assigned to the terminal device 100a. Further, the number of initial peer IDs of the terminal devices 100b, 100c, 100d logged in by the users B, C, and D who are field workers is 3 as described above. Therefore, it is assumed that the terminal devices 100b are given peer IDs "B_1", "B_2", and "B_3". It is assumed that the terminal devices 100c are given peer IDs "C_1", "C_2", and "C_3". It is assumed that the terminal devices 100d are given peer IDs "D_1", "D_2", and "D_3". In this state, in the peer ID management list 210 of the management server 200, as shown in the figure, the peer IDs "A_1", "A_2", "A_3", "A_4", "A_5", "B_1", "B_2", The states of "B_3", "C_1", "C_2", "C_3", "D_1", "D_2", and "D_3" have been changed from "not granted" to "waiting for connection" (peer ID "C_2"). , "C_3", "D_2", "D_3" are not shown).

Further, in this state, the peer ID assigned to the terminal device 100 is registered in the peer ID registration list 310 of the signaling server 300 as being used for communication with another terminal device 100. However, since no peer ID is connected to another peer ID, the connection status is not registered for all peer IDs.

The schematic operation of the communication system 10 when assigning a peer ID in this way will be described by taking the case of assigning a peer ID to the terminal device 100a as an example.

First, when the user A logs in with the user ID "A", the terminal device 100a accepts the login (step 11). At that time, the terminal device 100a transitions the screen to the connection screen for connecting to the other terminal device 100. At the same time, the terminal device 100a requests the management server 200 to assign the peer ID (step 12). Then, the management server 200 determines the peer ID to be assigned to the terminal device 100a from the peer ID management list 210 based on the user ID "A" input by login (step 13). Then, the management server 200 assigns the determined peer ID to the terminal device 100a (step 14). Further, the management server 200 updates the state of the peer ID assigned to the terminal device 100a among the peer IDs included in the peer ID management list 210 from "not assigned" to "waiting for connection" (step 15). After that, the terminal device 100a notifies the signaling server 300 of the assigned peer ID (step 16). As a result, the signaling server 300 registers the notified peer ID in the peer ID registration list 310 (step 17).

FIG. 5 is a diagram showing an example of a state when communication between the terminal devices 100 is performed in the communication system 10 in the present embodiment.

Here, it is assumed that communication is performed between the terminal device 100a and the terminal device 100b using the peer ID “A_1” of the terminal device 100a and the peer ID “B_1” of the terminal device 100b. Further, it is assumed that communication is performed between the terminal device 100a and the terminal device 100c using the peer ID "A_2" of the terminal device 100a and the peer ID "C_1" of the terminal device 100c. Further, it is assumed that communication is performed between the terminal device 100a and the terminal device 100d using the peer ID "A_3" of the terminal device 100a and the peer ID "D_1" of the terminal device 100d. In this state, in the peer ID management list 210 of the management server 200, as shown in the figure, the states of the peer IDs "A_1", "A_1", "A_3", "B_1", "C_1", and "D_1" are "connected". It has been changed from "Waiting" to "Connecting".

Further, in this state, the peer IDs "B_1", "C_1", and "D_1" of the communication partner are connected to the peer ID registration list 310 of the signaling server 300 as the connection states of the peer IDs "A_1", "A_1", and "A_3", respectively. Is registered. Further, the peer ID "A_1" of the communication partner is registered as the connection state of the peer ID "B_1" (the connection states of the peer IDs "C_1" and "D_1" are not shown).

FIG. 6 is a diagram showing an example of a state when a peer ID is newly assigned to the terminal device 100a in the communication system 10 in the present embodiment. However, here, it is assumed that the management server 200 determines whether or not to newly assign a peer ID to the terminal device 100a.

In FIG. 5, among the peer IDs “A_1”, “A_2”, “A_3”, “A_4”, and “A_5” assigned to the terminal device 100a, the peer IDs “A_1”, “A_2”, and “A_3” are other. It is used for communication with the terminal device 100 of. As a result, in the terminal device 100a, the number of usable peer IDs is two, which is less than the lower limit number of peer IDs. Therefore, it is assumed that one peer ID "A_6" is newly assigned to the terminal device 100a as shown by a thick line below the terminal device 100a. In this state, in the peer ID management list 210 of the management server 200, the state of the peer ID "A_6" is changed from "not granted" to "waiting for connection" as shown by the thick line.

Further, in this state, as shown by the thick line in the peer ID registration list 310 of the signaling server 300, the peer ID "A_6" newly assigned to the terminal device 100a is used for communication with the other terminal device 100. Registered as being.

Regarding the schematic operation of the communication system 10 when the peer ID is newly assigned in this way, the case where the usable peer ID of the terminal device 100a falls below the lower limit number of peer IDs by starting the communication with the terminal device 100b Let's take an example.

First, the terminal devices 100a and 100b notify the management server 200 that communication has started as a connection status (step 21). Then, the management server 200 determines the number of available peer IDs and determines the peer IDs to be assigned to the terminal device 100a (step 22). Specifically, the management server 200 first determines whether or not the number of available peer IDs is less than the lower limit number of peer IDs. Next, if the number of usable peer IDs is less than the lower limit peer ID number, the management server 200 needs to add the number obtained by subtracting the number of usable peer IDs from the lower limit peer ID number. Decide on the number of. Next, the management server 200 determines the determined number of peer IDs among the peer IDs that can be assigned to the terminal device 100a but are not assigned to the terminal device 100a as the peer IDs to be assigned to the terminal device 100a. Then, the management server 200 assigns the determined peer ID to the terminal device 100a (step 23). Further, the management server 200 updates the state of the peer ID assigned to the terminal device 100a among the peer IDs included in the peer ID management list 210 from "not assigned" to "waiting for connection" (step 24). After that, the terminal device 100a notifies the signaling server 300 of the assigned peer ID (step 25). As a result, the signaling server 300 registers the notified peer ID in the peer ID registration list 310 (step 26).

FIG. 7 is also a diagram showing an example of a state when a peer ID is newly assigned to the terminal device 100a in the communication system 10 in the present embodiment. However, here, a second embodiment is assumed in which the terminal device 100a itself determines whether or not to newly assign a peer ID to the terminal device 100a.

In FIG. 5, among the peer IDs “A_1”, “A_2”, “A_3”, “A_4”, and “A_5” assigned to the terminal device 100a, the peer IDs “A_1”, “A_2”, and “A_3” are other. It is used for communication with the terminal device 100 of. As a result, in the terminal device 100a, the number of usable peer IDs is two, which is less than the lower limit number of peer IDs. Therefore, it is assumed that one peer ID "A_6" is newly assigned to the terminal device 100a as shown by a thick line below the terminal device 100a. In this state, as in FIG. 6, in the peer ID management list 210 of the management server 200, the state of the peer ID “A_6” is changed from “not granted” to “waiting for connection”.

Further, in this state, similarly to FIG. 6, the peer ID "A_6" newly assigned to the terminal device 100a in the peer ID registration list 310 of the signaling server 300 is used for communication with the other terminal device 100. Registered as a thing.

The schematic operation of the communication system 10 when the peer ID is newly assigned will be described by taking as an example the case where the usable peer ID of the terminal device 100a is less than the lower limit number of peer IDs.

First, the terminal device 100a grasps the connection status with another terminal device 100 (step 31). Further, the terminal device 100a determines the number of peer IDs that need to be added (step 32). Specifically, the terminal device 100a first determines whether or not the number of available peer IDs is less than the lower limit number of peer IDs. Next, if the number of usable peer IDs is less than the lower limit peer ID number, the terminal device 100a needs to add the number obtained by subtracting the number of usable peer IDs from the lower limit peer ID number. Decide on the number of. Then, the terminal device 100a requests the management server 200 to assign the determined number of peer IDs (step 33). Then, the management server 200 determines the peer ID to be assigned to the terminal device 100a (step 34). Specifically, among the peer IDs that can be assigned to the terminal device 100a but are not assigned, the number of peer IDs determined by the terminal device 100a is determined as the peer IDs to be assigned to the terminal device 100a. Then, the management server 200 assigns the determined peer ID to the terminal device 100a (step 35). Further, the management server 200 updates the state of the peer ID assigned to the terminal device 100a among the peer IDs included in the peer ID management list 210 from "not assigned" to "waiting for connection" (step 36). After that, the terminal device 100a notifies the signaling server 300 of the assigned peer ID (step 37). As a result, the signaling server 300 registers the notified peer ID in the peer ID registration list 310 (step 38).

In the above, the terminal device 100a itself determines whether or not to newly assign a peer ID when the terminal device 100a is communicating with another terminal device 100, but the terminal device 100a accepts a login. The number of peer IDs to be given at the time may be determined by the terminal device 100a itself. In this case, the terminal device 100a may determine the number of initial peer IDs based on the user ID of the logged-in user, and request the management server 200 to assign the peer ID.

[Functional configuration of management server]
FIG. 8 is a block diagram showing a functional configuration example of the management server 200 in the communication system 10 that performs such a schematic operation. As shown in the figure, the management server 200 in the present embodiment includes a peer ID storage unit 220, a peer ID number storage unit 230, a reception unit 240, a peer ID number determination unit 250, and a peer ID number update unit 260. , A peer ID acquisition unit 270 and a transmission unit 280 are provided.

The peer ID storage unit 220 stores the peer ID management list 210 exemplified in FIGS. 3 to 7.

The peer ID number storage unit 230 has an initial peer ID number, which is the number of peer IDs assigned to the terminal device 100 when the user logs in to the terminal device 100, and a usable peer ID reserved in the terminal device 100. The lower limit peer ID number, which is the lower limit of the number, is stored. Here, the number of initial peer IDs and the number of lower limit peer IDs may be the same value or different values as described above.

When the terminal device 100 is activated and the user logs in to the terminal device 100, the receiving unit 240 receives a request for assigning a peer ID from the terminal device 100. The request for assigning the peer ID includes the user ID of the user who has logged in to the terminal device 100.

Further, when the terminal device 100 communicates with another terminal device 100, the receiving unit 240 receives the connection status from the terminal device 100 to the other terminal device 100 in the first embodiment, and the second embodiment receives the connection status with the other terminal device 100. In the embodiment, the terminal device 100 receives a determined number of peer ID grant requests or deletion requests. In this case, the receiving unit 240 is an example of an acquisition means for acquiring the usage status of the identification information in each terminal device.

The peer ID number determination unit 250 determines the optimum initial peer ID number (hereinafter, referred to as “optimal initial peer ID number”). The method for determining the optimum number of initial peer IDs will be described later. Further, when the initial number of peer IDs and the lower limit peer ID number are the same value, the peer ID number determination unit 250 also determines the optimum lower limit peer ID number (hereinafter, referred to as “optimum lower limit peer ID number”) at the same time. become. Alternatively, when the initial number of peer IDs and the lower limit peer ID number are different values, the peer ID number determination unit 250 may determine the optimum lower limit peer ID number. In the following, for convenience, the optimum initial peer ID number and the optimum lower limit peer ID number will be collectively referred to as the “optimal peer ID number”.

The peer ID number update unit 260 updates the initial peer ID number stored in the peer ID number storage unit 230 with the optimum initial peer ID number determined by the peer ID number determination unit 250. Further, the peer ID number update unit 260 may update the lower limit peer ID number stored in the peer ID number storage unit 230 with the optimum lower limit peer ID number determined by the peer ID number determination unit 250.

When the terminal device 100 is activated and the user logs in to the terminal device 100, the peer ID acquisition unit 270 acquires the peer IDs of the initial number of peer IDs stored in the peer ID number storage unit 230. The peer ID acquisition unit 270 may acquire a peer ID prepared in advance for a user who has logged in to the terminal device 100 or a group to which the user belongs. For example, the peer ID may be acquired from the peer IDs associated with the user ID included in the peer ID grant request received by the receiving unit 240 in the peer ID management list 210. In this case, the peer ID acquisition unit 270 is an example of a giving means for giving identification information to each terminal device of a plurality of terminal devices communicating with each other.

Further, in the first embodiment, when the terminal device 100 communicates with another terminal device 100, the peer ID acquisition unit 270 includes the number of peer IDs that can be used in the terminal device 100 and the peer ID number storage unit. Compare with the lower limit peer ID number stored in 230. As a result, if the number of usable peer IDs is less than the lower limit peer ID number, the peer ID acquisition unit 270 needs to add by subtracting the number of usable peer IDs from the lower limit peer ID number. Determine the number of peer IDs. Then, the peer ID acquisition unit 270 acquires a determined number of peer IDs among the peer IDs that can be assigned to the terminal device 100 included in the peer ID management list 210 but are not assigned. On the other hand, if the number of available peer IDs exceeds the number of lower limit peer IDs, the peer ID acquisition unit 270 subtracts the number of lower limit peer IDs from the number of available peer IDs, so that the peer needs to be deleted. Determine the number of IDs. Then, the peer ID acquisition unit 270 identifies a determined number of peer IDs among the peer IDs assigned to the terminal device 100 included in the peer ID management list 210 in the order of the oldest assigned time. Alternatively, in the second embodiment, when the terminal device 100 is communicating with another terminal device 100, the peer ID acquisition unit 270 requests to assign or delete the number of peer IDs determined by the terminal device 100. Is determined by the receiving unit 240. As a result, if the receiving unit 240 receives the peer ID assignment request, the peer ID acquisition unit 270 can assign the peer ID to the terminal device 100 included in the peer ID management list 210, but the peer ID is not assigned. Among them, the terminal device 100 acquires the determined number of peer IDs. On the other hand, if the receiving unit 240 receives the peer ID deletion request, the peer ID acquisition unit 270 is assigned the peer ID among the peer IDs assigned to the terminal device 100 included in the peer ID management list 210. Specifies the number of peer IDs determined by the terminal device 100 in chronological order. In this case, the number of peer IDs that can be used in the terminal device 100 is an example of the number of identification information given to each terminal device that has not yet been used for communication with other terminal devices. The lower limit number of peer IDs stored in the peer ID number storage unit 230 is an example of a specific number. Further, the peer ID acquisition unit 270 is an example of adjustment means for adjusting the number of identification information given to each terminal device according to the usage status of the identification information in each terminal device.

When the terminal device 100 is activated and the user logs in to the terminal device 100, the transmission unit 280 transmits the peer ID acquired by the peer ID acquisition unit 270 to the terminal device 100. In this case, the transmission unit 280 is an example of the control means for controlling the mediation device to be notified of the information regarding the identification information given to each terminal device. At that time, the transmission unit 280 may simultaneously transmit information for displaying the peer ID to the terminal device 100 in a format clearly indicating the usage status of the peer ID. Here, the format in which the usage status of the peer ID is specified includes a format in which the usable peer ID is specified, a format in which the number of usable peer IDs is specified, and the like. In this case, the transmission unit 280 clearly indicates the number of identification information given to each terminal device that has not yet been used for communication with other terminal devices or the identification information that has not yet been used. This is an example of a transmission means for transmitting information to be displayed in a format to each terminal device.

Further, when the terminal device 100 communicates with another terminal device 100, the transmission unit 280 transmits the peer ID to the terminal device 100 if the peer ID acquisition unit 270 has acquired the peer ID to be assigned. .. On the other hand, if the peer ID acquisition unit 270 specifies the peer ID to be deleted when the terminal device 100 is communicating with another terminal device 100, the transmission unit 280 issues an instruction to delete the peer ID to the terminal device 100. Send to.

[Method of determining the optimum number of peer IDs]
Here, it is assumed that the management server 200 executes the process of determining the peer ID assigned to each terminal device 100 by using the service of AWS Lambda. In this case, it is necessary to balance between the two competing factors. One factor is the execution time of AWS Lambda (hereinafter referred to as "Lambda execution time"), and the other factor is the number of executions of AWS Lambda (hereinafter referred to as "Lambda execution number"). In AWS Lambda, the longer the Lambda execution time and the larger the number of Lambda executions, the higher the charge system is.

FIG. 9 is a graph showing the relationship between the number of initial peer IDs and the charge required when the number of initial peer IDs is adopted. The larger the number of initial peer IDs, the longer the Lambda execution time for generating peer IDs. Therefore, as shown in the graph, the larger the number of initial peer IDs, the higher the usage fee of AWS Lambda. On the other hand, when the number of usable peer IDs assigned to the terminal device 100 is less than the lower limit number of peer IDs, the management server 200 uses AWS Lambda to determine the peer IDs again. At that time, the smaller the number of initial peer IDs, the more frequently AWS Lambda is executed, and the number of times Lambda is executed increases. Therefore, as shown in the graph, the smaller the number of initial peer IDs, the higher the AWS Lambda usage fee. Further, in this case, the charge for connecting to the signaling server 300 also increases.

Therefore, it is not preferable that the Lambda execution time is long and the number of Lambda executions is large. It is necessary to determine the optimal number of initial peer IDs so that an accurate trade-off is maintained between the Lambda execution time and the number of Lambda executions.

By the way, by taking the average of the time series data of the number of calls of a certain user in a certain period, the average number of calls E (Calls) which is the average value of the number of calls received by the user during the period can be obtained. If such a peer ID with an average number of calls E (Calls) can be assigned to the terminal device 100 in one AWS Lambda execution, this is the best possible hit obtained by participating in the user's call request. .. Therefore, the optimal number of initial peer IDs for a user may be equal to the average number of calls E (Calls) for that user.

FIG. 10 is a diagram showing a method of determining such an optimum number of initial peer IDs. In the figure, the average number of calls E (Calls) has changed from 4.83, 4.66, 4.66, 5.00, and 5.50 from the first week to the fifth week. In this case, since the average number of calls E (Calls) does not exceed 5 in the peer ID number determination unit 250 from the first week to the fourth week, the optimum initial peer ID number is set to 5, and the average number of peer IDs is set to 5 in the fifth week. Since the number of calls E (Calls) exceeds 5, the optimum number of initial peer IDs may be set to 6. The average number of calls may be acquired by the receiving unit 240 from each terminal device 100.

In FIG. 10, the average number of calls E (Calls) is obtained by taking the average of the number of calls per week, but it may be obtained by taking the moving average of the number of calls. At that time, as the moving average, any of simple moving average, exponential moving average, weighted moving average and the like may be used.

Further, the peer ID number determination unit 250 may obtain the optimum initial peer ID number that can be selected for each user by learning the call tendency of each user and logically estimating the optimum initial peer ID number. good. Here, it is desirable that the optimum number of initial peer IDs is required so that the user can confidently say that the number of calls is exactly the number of optimal initial peer IDs at a certain point in time. When estimating the optimum number of initial peer IDs, the user's call data is analyzed from the following viewpoints. Such perspectives include, for example, calls received in the last month, calls received at the same time in the same year in the last few years, calls received by users of the same level, and user attributes. Of these, the attributes of the user are, for example, whether they are remote supporters or field workers, or positions such as department managers and section managers. Alternatively, from such a viewpoint, geographical location, seasonal factors, etc. can be considered.

In the above case, the peer ID number determination unit 250 is based on at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to give the identification information to each terminal device. This is an example of a determination means for determining the number of identification information given when each terminal device is activated.

Although the method for determining the optimum initial peer ID number has been described above, the peer ID number determination unit 250 may determine the lower limit peer ID number in the same manner.

In this case, the peer ID number determination unit 250 is based on at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to give the identification information to each terminal device. , Is an example of a determination means for determining a specific number.

[Communication system operation]
11-1 and 11-2 are sequence diagrams showing a first operation example of the communication system 10 in the present embodiment. Here, the number of initial peer IDs and the number of lower limit peer IDs of the terminal device 100a are both 3, the number of initial peer IDs and the number of lower limit peer IDs of the terminal device 100b are both 2, and the initial number of the terminal devices 100c is 2. It is assumed that the number of peer IDs and the number of lower limit peer IDs are both 3.

As shown in FIG. 11-1, it is assumed that the terminal device 100a accepts the login of the user A and requests the management server 200 for the peer ID (step 101).

Then, the management server 200 assigns three peer IDs "A_1", "A_2", and "A_3" to the terminal device 100a (step 102). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100a. Next, the peer ID acquisition unit 270 acquires three peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these three peer IDs to the terminal device 100a.

As a result, the terminal device 100a registers the three peer IDs in the signaling server 300 (step 103). At this point, the peer IDs "A_1", "A_2", and "A_3" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 301.

Next, it is assumed that the terminal device 100b accepts the login of the user B and requests the management server 200 for the peer ID (step 104).

Then, the management server 200 assigns two peer IDs "B_1" and "B_2" to the terminal device 100b (step 105). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100b. Next, the peer ID acquisition unit 270 acquires two peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these two peer IDs to the terminal device 100b.

As a result, the terminal device 100b registers two peer IDs in the signaling server 300 (step 106). At this point, the peer IDs "A_1", "A_2", "A_3", "B_1", and "B_2" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 302. ..

Here, it is assumed that the user A communicates with the terminal device 100b of the user B by using the terminal device 100a (step 107). In this case, the terminal devices 100a and 100b notify the management server 200 that communication with the other terminal devices 100 has been established (steps 108 and 109).

Then, the management server 200 assigns one new peer ID to the terminal device 100a (step 110). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100a to establish communication with another terminal device 100. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100a in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 2 which is the number of unused peer IDs is less than 3 which is the lower limit number of peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be added, by subtracting the number of unused peer IDs from the lower limit number of peer IDs. Then, the peer ID acquisition unit 270 acquires one peer ID "A_4" which is a necessary number to be added from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits this one peer ID to the terminal device 100a.

Further, the management server 200 also assigns one new peer ID to the terminal device 100b (step 111). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100b to establish communication with another terminal device 100. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100b in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 1 which is the number of unused peer IDs is less than 2 which is the lower limit number of peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be added, by subtracting the number of unused peer IDs from the lower limit number of peer IDs. Then, the peer ID acquisition unit 270 acquires one peer ID "B_3" which is a necessary number to be added from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits this one peer ID to the terminal device 100b.

As a result, the terminal device 100a registers one peer ID in the signaling server 300 (step 112). Further, the terminal device 100b also registers one peer ID in the signaling server 300 (step 113). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 303, the peer IDs "A_1", "A_2", "A_3", "B_1", "B_2", "A_4", "B_3" is registered. However, the peer IDs "A_1" and "B_1" are in use, which is not the information registered in the signaling server 300, but is shown by striking through for convenience. ..

Next, as shown in FIG. 11-2, it is assumed that the terminal device 100c accepts the login of the user C and requests the management server 200 for the peer ID (step 114).

Then, the management server 200 assigns three peer IDs "C_1", "C_2", and "C_3" to the terminal device 100c (step 115). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100c. Next, the peer ID acquisition unit 270 acquires three peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these three peer IDs to the terminal device 100c.

As a result, the terminal device 100c registers the three peer IDs in the signaling server 300 (step 116). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 304, the peer IDs "A_1", "A_2", "A_3", "B_1", "B_2", "A_4", "B_3", "C_1", "C_2", and "C_3" are registered. However, the peer IDs "A_1" and "B_1" are still in use, which is not the information registered in the signaling server 300 for these peer IDs, but is shown by striking through for convenience. There is.

Here, it is assumed that the user A disconnects the communication with the terminal device 100b of the user B using the terminal device 100a (step 117). In this case, the terminal devices 100a and 100b notify the management server 200 that the communication with the other terminal devices 100 has been disconnected (steps 118 and 119). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 305, the peer IDs "A_1", "A_2", "A_3", "B_1", "B_2", "A_4", "B_3", "C_1", "C_2", and "C_3" are registered. Since the peer IDs "A_1" and "B_1" are no longer in use, the strikethrough has been removed.

Then, the management server 200 deletes one oldest peer ID assigned to the terminal device 100a (step 120). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100a that the communication with the other terminal device 100 is disconnected. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100a in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 4 which is the number of unused peer IDs exceeds 3 which is the lower limit number of peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be deleted, by subtracting the lower limit number of peer IDs from the number of unused peer IDs. Then, the peer ID acquisition unit 270 identifies one of the earliest peer IDs “A_1” assigned to the terminal device 100a from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits an instruction to delete this one peer ID from the terminal device 100a.

The management server 200 also deletes one oldest peer ID assigned to the terminal device 100b (step 121). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100b that the communication with the other terminal device 100 is disconnected. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100b in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 3 which is the number of unused peer IDs exceeds 2 which is the lower limit peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be deleted, by subtracting the lower limit number of peer IDs from the number of unused peer IDs. Then, the peer ID acquisition unit 270 identifies one of the earliest peer IDs "B_1" assigned to the terminal device 100b from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits an instruction to delete this one peer ID from the terminal device 100b.

As a result, the terminal device 100a deletes one peer ID from the signaling server 300 (step 122). The terminal device 100b also deletes one peer ID from the signaling server 300 (step 123). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 306, the peer IDs "A_2", "A_3", "B_2", "A_4", "B_3", "C_1", "C_2" and "C_3" are registered.

In the above, in steps 108 and 109, each terminal device 100 notifies the management server 200 that communication with the other terminal device 100 has been established, but this is not the case. Each terminal device 100 determines whether it is necessary to add a peer ID by itself, determines the number of peer IDs to be added if it is necessary to add a peer ID, and adds the determined number of peer IDs. May be requested from the management server 200. In that case, in steps 110 and 111, each terminal device 100 determines that it is necessary to add a peer ID, determines the number of peer IDs that need to be added, and the management server 200 determines each terminal device 100. Will transmit the number of peer IDs determined by the terminal device 100 to each terminal device 100.

Further, in the above, in steps 118 and 119, each terminal device 100 notifies the management server 200 that the communication with the other terminal device 100 has been disconnected, but this is not the case. Each terminal device 100 determines whether it is necessary to delete the peer ID by itself, determines the number of peer IDs to be deleted if it is necessary to delete the peer ID, and deletes the determined number of peer IDs. May be requested from the management server 200. In that case, in steps 120 and 121, each terminal device 100 determines that the peer ID needs to be deleted, determines the number of peer IDs that need to be deleted, and the management server 200 determines each terminal device 100. Will send the deletion instruction of the number of peer IDs determined by to each terminal device 100.

In the first operation example shown in FIGS. 11-1 and 11-2, since the peer IDs of all communication partners are not assigned in advance, the peer IDs assigned to the terminal device 100 by the management server 200 Even if usage occurs according to the number, the cost can be suppressed. Further, since the peer ID is not assigned every time there is a connection request, the real-time property of communication is less likely to be impaired.

12-1 and 12-2 are sequence diagrams showing a second operation example of the communication system 10 in the present embodiment. Again, the number of initial peer IDs and the number of lower limit peer IDs of the terminal device 100a are both 3, the number of initial peer IDs and the number of lower limit peer IDs of the terminal device 100b are both 2, and the initial number of the terminal devices 100c is 2. It is assumed that the number of peer IDs and the number of lower limit peer IDs are both 3.

In FIGS. 12-1 and 12-1, steps 131 to 153 are the same as steps 101 to 123 in FIGS. 11-1 and 11-2, and registration contents 331 to 336 are shown in FIGS. 11-1 and 11-2. Since the registered contents are the same as those of 301 to 306, the description thereof will be omitted.

After that, in this second operation example, the peer ID number determination unit 250 redetermines the initial peer ID number based on the time-series data of the number of calls during operation. Here, the case where the number of initial peer IDs of the terminal device 100a is 5 and the number of initial peer IDs of the terminal device 100b is 3 is taken as an example.

In this case, as shown in FIG. 12-2, it is assumed that the terminal device 100a accepts the login of the user A and requests the management server 200 for the peer ID (step 154).

Then, the management server 200 assigns five peer IDs "A_1", "A_2", "A_3", "A_4", and "A_5" to the terminal device 100a (step 155). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100a. Next, the peer ID acquisition unit 270 acquires five peer IDs, which is the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these five peer IDs to the terminal device 100a.

As a result, the terminal device 100a registers five peer IDs in the signaling server 300 (step 156). At this point, the peer IDs "A_1", "A_2", "A_3", "A_4", and "A_5" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 337. ..

Next, it is assumed that the terminal device 100b accepts the login of the user B and requests the management server 200 for the peer ID (step 157).

Then, the management server 200 assigns three peer IDs "B_1", "B_2", and "B_3" to the terminal device 100b (step 158). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100b. Next, the peer ID acquisition unit 270 acquires three peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these three peer IDs to the terminal device 100b.

As a result, the terminal device 100b registers the three peer IDs in the signaling server 300 (step 159). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 338, the peer IDs "A_1", "A_2", "A_3", "A_4", "A_5", "B_1", "B_2" and "B_3" are registered.

In the second operation example shown in FIGS. 12-1 and 12-2, since the peer IDs of all communication partners are not assigned in advance, the peer IDs assigned to the terminal device 100 by the management server 200 Even if usage occurs according to the number, the cost can be suppressed. Further, since the peer ID is not assigned every time there is a connection request, the real-time property of communication is less likely to be impaired. In addition, the number of peer IDs given to the terminal device 100 by the management server 200 is optimized by redetermining the number of peer IDs based on the time-series data of the number of calls during operation.

13-1 and 13-2 are sequence diagrams showing a third operation example of the communication system 10 in the present embodiment. Here, the number of initial peer IDs and the number of lower limit peer IDs of the terminal device 100a are 2 and 1, respectively, the number of initial peer IDs of the terminal device 100b is 2, and the number of initial peer IDs of the terminal device 100c is 3. Suppose there is.

As shown in FIG. 13-1, it is assumed that the terminal device 100a accepts the login of the user A and requests the management server 200 for the peer ID (step 161).

Then, the management server 200 assigns two peer IDs "A_1" and "A_2" to the terminal device 100a (step 162). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100a. Next, the peer ID acquisition unit 270 acquires two peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these two peer IDs to the terminal device 100a.

As a result, the terminal device 100a registers two peer IDs in the signaling server 300 (step 163). At this point, the peer IDs "A_1" and "A_2" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 361.

Next, it is assumed that the terminal device 100b accepts the login of the user B and requests the management server 200 for the peer ID (step 164).

Then, the management server 200 assigns two peer IDs "B_1" and "B_2" to the terminal device 100b (step 165). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100b. Next, the peer ID acquisition unit 270 acquires two peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these two peer IDs to the terminal device 100b.

As a result, the terminal device 100b registers two peer IDs in the signaling server 300 (step 166). At this point, the peer IDs "A_1", "A_1", "B_1", and "B_2" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 362.

Here, it is assumed that the user A communicates with the terminal device 100b of the user B by using the terminal device 100a (step 167). In this case, the terminal devices 100a and 100b notify the management server 200 that communication with the other terminal devices 100 has been established (steps 168 and 169). At this point, the peer IDs "A_1", "A_1", "B_1", and "B_2" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 363. However, the peer IDs "A_1" and "B_1" are in use, which is not the information registered in the signaling server 300, but is shown by striking through for convenience. .. Here, since 1 which is the number of usable peer IDs is not less than 1 which is the lower limit peer ID number, the management server 200 does not assign a new peer ID.

Next, it is assumed that the terminal device 100c accepts the login of the user C and requests the management server 200 for the peer ID (step 170).

Then, the management server 200 assigns three peer IDs "C_1", "C_2", and "C_3" to the terminal device 100c (step 171). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100c. Next, the peer ID acquisition unit 270 acquires three peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these three peer IDs to the terminal device 100c.

As a result, the terminal device 100c registers the three peer IDs in the signaling server 300 (step 172). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 364, the peer IDs "A_1", "A_2", "B_1", "B_1", "C_1", "C_2", "C_3" is registered. However, the peer IDs "A_1" and "B_1" are still in use, which is not the information registered in the signaling server 300 for these peer IDs, but is shown by striking through for convenience. There is.

Here, it is assumed that the user C communicates with the terminal device 100a of the user A by using the terminal device 100c (step 173). In this case, the terminal devices 100a and 100c notify the management server 200 that communication with the other terminal devices 100 has been established (steps 174 and 175). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 365, the peer IDs "A_1", "A_2", "B_1", "B_1", "C_1", "C_2", "C_3" is registered. However, the peer IDs "A_1", "A_1", "B_1", and "C_1" are in use, and although this is not the information registered in the signaling server 300 in these peer IDs, it is canceled for convenience. It is shown by drawing a line.

Then, the management server 200 assigns one new peer ID to the terminal device 100a (step 176). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100a to establish communication with another terminal device 100. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100a in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 0, which is the number of unused peer IDs, is less than 1, which is the lower limit number of peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be added, by subtracting the number of unused peer IDs from the lower limit number of peer IDs. Then, the peer ID acquisition unit 270 acquires one peer ID "A_3" which is a necessary number to be added from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits this one peer ID to the terminal device 100a.

As a result, the terminal device 100a registers one peer ID in the signaling server 300 (step 177). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 366, the peer IDs "A_1", "A_2", "B_1", "B_1", "C_1", "C_2", "C_3" and "A_3" are registered. However, the peer IDs "A_1", "A_1", "B_1", and "C_1" are still in use, which is not the information registered in the signaling server 300 in these peer IDs, but for convenience. It is shown by striking through.

Here, as shown in FIG. 13-2, it is assumed that the user A disconnects the communication with the terminal device 100b of the user B using the terminal device 100a (step 178). In this case, the terminal devices 100a and 100b notify the management server 200 that the communication with the other terminal devices 100 has been disconnected (steps 179 and 180). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 367, the peer IDs "A_1", "A_2", "B_1", "B_1", "C_1", "C_2", "C_3" and "A_3" are registered. Since the peer IDs "A_1" and "B_1" are no longer in use, the strikethrough has been removed.

Then, the management server 200 deletes one oldest peer ID assigned to the terminal device 100a (step 181). Specifically, first, the receiving unit 240 receives a notification from the terminal device 100a that the communication with the other terminal device 100 is disconnected. Next, the peer ID acquisition unit 270 is assigned to the terminal device 100a in the peer ID management list 210 stored in the peer ID storage unit 220, but the number of unused peer IDs and the number of peer IDs are stored. Compare with the lower limit peer ID number stored in 230. Here, 2 which is the number of unused peer IDs exceeds 1 which is the lower limit number of peer IDs. Therefore, the peer ID acquisition unit 270 obtains 1, which is the number of peer IDs that need to be deleted, by subtracting the lower limit number of peer IDs from the number of unused peer IDs. Then, the peer ID acquisition unit 270 identifies one of the earliest peer IDs “A_1” assigned to the terminal device 100a from the peer ID management list 210 stored in the peer ID storage unit 220. Next, the transmission unit 280 transmits an instruction to delete this one peer ID from the terminal device 100a.

As a result, the terminal device 100a deletes one peer ID from the signaling server 300 (step 182). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 368, the peer IDs "A_2", "B_1", "B_2", "C_1", "C_2", "C_3", "A_3" is registered.

After that, also in this third operation example, the peer ID number determination unit 250 redetermines the initial peer ID number based on the time-series data of the number of calls during operation. Here, the case where the number of initial peer IDs of the terminal device 100a is 5 and the number of initial peer IDs of the terminal device 100b is 3 is taken as an example.

In this case, it is assumed that the terminal device 100a accepts the login of the user A and requests the management server 200 for the peer ID (step 183).

Then, the management server 200 assigns five peer IDs "A_1", "A_2", "A_3", "A_4", and "A_5" to the terminal device 100a (step 184). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100a. Next, the peer ID acquisition unit 270 acquires five peer IDs, which is the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these five peer IDs to the terminal device 100a.

As a result, the terminal device 100a registers five peer IDs in the signaling server 300 (step 185). At this point, the peer IDs "A_1", "A_2", "A_3", "A_4", and "A_5" are registered in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 369. ..

Next, it is assumed that the terminal device 100b accepts the login of the user B and requests the management server 200 for the peer ID (step 186).

Then, the management server 200 assigns three peer IDs "B_1", "B_2", and "B_3" to the terminal device 100b (step 187). Specifically, first, the receiving unit 240 receives the request for the peer ID from the terminal device 100b. Next, the peer ID acquisition unit 270 acquires three peer IDs, which are the initial number of peer IDs stored in the peer ID number storage unit 230, from the peer ID management list 210 stored in the peer ID storage unit 220. do. Next, the transmission unit 280 transmits these three peer IDs to the terminal device 100b.

As a result, the terminal device 100b registers three peer IDs in the signaling server 300 (step 188). At this point, in the peer ID registration list 310 of the signaling server 300, as shown in the registration content 370, the peer IDs "A_1", "A_2", "A_3", "A_4", "A_5", "B_1", "B_2" and "B_3" are registered.

In the above, in steps 168, 169, 174, and 175, each terminal device 100 notifies the management server 200 that communication with the other terminal device 100 has been established, but this is not the case. Each terminal device 100 determines whether it is necessary to add a peer ID by itself, determines the number of peer IDs to be added if it is necessary to add a peer ID, and adds the determined number of peer IDs. May be requested from the management server 200. In that case, in steps 168 and 169, each terminal device 100 determines that it is not necessary to add the peer ID, and does not request the management server 200 to add the peer ID. Further, in steps 174 and 175, each terminal device 100 determines that it is necessary to add a peer ID, determines the number of peer IDs that need to be added, and the management server 200 determines that each terminal device 100 needs to add the peer ID. The determined number of peer IDs will be transmitted to each terminal device 100.

Further, in the above, in steps 179 and 180, each terminal device 100 notifies the management server 200 that the communication with the other terminal device 100 has been disconnected, but this is not the case. Each terminal device 100 determines whether it is necessary to delete the peer ID by itself, determines the number of peer IDs to be deleted if it is necessary to delete the peer ID, and deletes the determined number of peer IDs. May be requested from the management server 200. In that case, in steps 179 and 180, each terminal device 100 determines that the peer ID needs to be deleted, determines the number of peer IDs that need to be deleted, and the management server 200 determines each terminal device 100. Will send the deletion instruction of the number of peer IDs determined by to each terminal device 100.

In the third operation example shown in FIGS. 13-1 and 13-2, since the peer IDs of all communication partners are not assigned in advance, the peer IDs assigned to the terminal device 100 by the management server 200 Even if usage occurs according to the number, the cost can be suppressed. Further, since the peer ID is not assigned every time there is a connection request, the real-time property of communication is less likely to be impaired. In addition, the number of peer IDs given to the terminal device 100 by the management server 200 is optimized by redetermining the number of peer IDs based on the time-series data of the number of calls during operation.

[Modification example]
In the above embodiment, after the management server 200 assigns the peer ID to the terminal device 100, the terminal device 100 notifies the signaling server 300 of the peer ID, but this is not the case. After the management server 200 assigns the peer ID to the terminal device 100, the peer ID may be notified to the signaling server 300.

Further, in the above embodiment, the signaling server 300 is provided separately from the management server 200, but this is not the case. The management server 200 may have the function of the signaling server 300. In this case, after the management server 200 assigns the peer ID to the terminal device 100, the management server 200 updates the peer ID registration list held by the management server 200.

Other changes and configuration substitutions that do not deviate from the scope of the technical ideas of this disclosure are included in this disclosure.

[program]
The processing performed by the terminal device 100 or the management server 200 in the present embodiment is prepared as, for example, a program such as application software.

This program has a function of acquiring the usage status of the identification information used for communication with other terminal devices given to each terminal device of a plurality of terminal devices communicating with each other in the terminal device. It is a program for realizing the function of adjusting the number of the identification information given to each of the terminal devices or requesting the adjustment according to the acquired usage status.

The program that realizes this embodiment can be provided not only by communication means but also by storing it in a recording medium such as a CD-ROM.

100 ... terminal device, 200 ... management server, 220 ... peer ID storage unit, 230 ... peer ID number storage unit, 240 ... reception unit, 250 ... peer ID number determination unit 260 ... peer ID number update unit, 270 ... peer ID Acquisition unit, 280 ... Transmission unit, 300 ... Signaling server

Claims (13)

An assigning means for imparting identification information used for communication with other terminal devices to each terminal device of a plurality of terminal devices communicating with each other.
Acquiring means for acquiring the usage status of the identification information given to each terminal device by the giving means in each terminal device, and
An adjusting means for adjusting the number of the identification information given to each terminal device by the giving means according to the usage situation acquired by the acquiring means.
Identification information management device equipped with. The usage status is the number of the identification information given to each terminal device by the granting means, which is not yet used for communication with other terminal devices, according to claim 1. Identification information management device. The identification information management device according to claim 2, wherein the usage status is a situation in which the number of unused identification information exceeds or falls below a specific number. The specific number is determined based on at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to attach the identification information to each terminal device. The identification information management device according to claim 3, further comprising a decision-making means. The identification information management device according to claim 3, wherein the granting means grants at least the specific number of the identification information to each terminal device when the terminal device is activated. Each terminal device is activated based on at least one of the attributes of the user who uses each terminal device, the communication history of the user, and the cost required to attach the identification information to each terminal device. The identification information management device according to claim 5, further comprising a determination means for determining the number of the identification information given when the identification information is created. Information for displaying the identification information given to each terminal device by the giving means in a format clearly indicating the number of the identification information that has not been used or the identification information that has not been used yet. The identification information management device according to claim 2, further comprising a transmission means for transmitting to each terminal device. The identification information management device according to claim 1, wherein the granting means assigns the identification information prepared in advance to a user who uses each terminal device or a group to which the user belongs. Information about the identification information given to each of the terminal devices by the giving means is notified to the intermediary device that mediates the information of the plurality of terminal devices before the plurality of terminal devices communicate with each other. The identification information management device according to claim 1, further comprising a control means for controlling. The identification information management device according to claim 1, wherein the identification information is information used for establishing P2P communication by a communication means of WebRTC. A step of assigning identification information used for communication with other terminal devices to each terminal device of a plurality of terminal devices communicating with each other, and
A step of acquiring the usage status of the identification information given to each terminal device in each terminal device, and
A step of adjusting the number of the identification information given to each of the terminal devices according to the acquired usage status, and a step of adjusting the number of the identification information.
Identification information management method including. With multiple terminal devices that communicate with each other,
An identification information management device that manages identification information used by the plurality of terminal devices for communication with other terminal devices, and an identification information management device.
Including
The identification information management device is
The giving means for giving the identification information to each terminal device of the plurality of terminal devices, and
Acquiring means for acquiring the usage status of the identification information given to each terminal device by the giving means in each terminal device, and
An adjusting means for adjusting the number of the identification information given to each terminal device by the giving means according to the usage situation acquired by the acquiring means.
Communication system with. On the computer
A function to acquire the usage status of the identification information used for communication with other terminal devices assigned to each terminal device of a plurality of terminal devices that communicate with each other, and the usage status of each terminal device.
A function for adjusting the number of the identification information given to each terminal device or requesting the adjustment according to the acquired usage status.
A program to realize.

Images