Management server, management method, and storage medium
A management server according to one aspect of the present disclosure includes at least one processor. The processor receives a first identifier, first unique information, a second identifier, and second unique information in response to occurrence of a use relationship between a first target and a second target, requests authentication of the first target by transmitting the received first identifier and the received first unique information to a first server, requests authentication of the second target by transmitting the received second identifier and the received second unique information to a second server, and sets a correspondence between the first identifier and the second identifier when both the first target and the second target have successfully been authenticated.
1 . A management server comprising a memory and at least one processor, wherein the processor is configured to perform operations of:
receiving, in response to occurrence of a physical use relationship between a first target and a second target for using the second target by the first target, a first identifier of the first target, first unique information of the first target, a second identifier of the second target, and second unique information of the second target from at least one of a first terminal of the first target and a second terminal of the second target;
requesting a first server to authenticate the first target by transmitting the received first identifier and the received first unique information to the first server;
receiving a result of authentication of the first target from the first server;
requesting a second server to authenticate the second target by transmitting the received second identifier and the received second unique information to the second server;
receiving a result of authentication of the second target from the second server;
setting a correspondence between the first identifier and the second identifier when the received results of the authentication show that both the first target and the second target have successfully been authenticated; and
recording a time at which the correspondence is set as a starting time of the first target being linked with the second target, wherein
the management server, the first terminal, the second terminal the first server, and the second server are separate and distinct from each other.
2 . The management server according to claim 1 , wherein the processor is further configured to terminate the correspondence in response to reception of a termination request from at least one of the first terminal and the second terminal or satisfaction of a predetermined termination condition.
3 . The management server according to claim 1 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least one of the first terminal and the second terminal includes:
receiving the second identifier and the second unique information from the first terminal; and
receiving the first identifier and the first unique information from the second terminal.
4 . The management server according to claim 1 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least one of the first terminal and the second terminal includes:
receiving the first identifier and the second unique information from the first terminal; and
receiving the second identifier and the first unique information from the second terminal.
5 . The management server according to claim 1 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least one of the first terminal and the second terminal includes:
receiving the second identifier and the first unique information from the first terminal; and
receiving the first identifier and the second unique information from the second terminal.
6 . The management server according to claim 1 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least one of the first terminal and the second terminal includes receiving the first identifier, the first unique information, the second identifier, and the second unique information from one of the first terminal and the second terminal.
7 . The management server according to claim 1 , wherein:
the first target is a user;
the first terminal is a user terminal associated with the user;
the second target is a use item to be used by the user; and
the second terminal is a load terminal to be loaded on the use item.
8 . The management server according to claim 7 , wherein the use item is a mobile body.
9 . The management server according to claim 7 , wherein the user terminal associated with the user is a proxy user terminal possessed by a proxy user who acts as proxy for the user.
10 . The management server according to claim 9 , wherein the physical use relationship between the first target and the second target occurs through data communication between a target user terminal possessed by the user and the proxy user terminal and data communication between the proxy user terminal and the load terminal.
11 . The management server according to claim 7 , wherein:
the user terminal associated with the user is a target user terminal possessed by the user; and
the physical use relationship between the first target and the second target occurs by data communication between the target user terminal and the load terminal with mediation of a proxy user terminal possessed by a proxy user who acts as proxy for the user.
12 . The management server according to claim 7 , wherein:
the user terminal associated with the user is a target user terminal possessed by the user; and
one identifier corresponding to the user out of the first identifier and the second identifier is associated with proxy authority of another user than the user.
13 . A management method comprising executing, by a management server:
receiving, in response to occurrence of a physical use relationship between a first target and a second target for using the second target by the first target, a first identifier of the first target, first unique information of the first target, a second identifier of the second target, and second unique information of the second target from at least one of a first terminal of the first target and a second terminal of the second target;
requesting a first server to authenticate the first target by transmitting the received first identifier and the received first unique information to the first server;
receiving a result of authentication of the first target from the first server;
requesting a second server to authenticate the second target by transmitting the received second identifier and the received second unique information to the second server;
receiving a result of authentication of the second target from the second server; and
setting a correspondence between the first identifier and the second identifier when the received results of the authentication show that both the first target and the second target have successfully been authenticated; and
recording a time at which the correspondence is set as a starting time of the first target being linked with the second target, wherein
the management server, the first terminal, the second terminal, the first server, and the second server are separate and distinct from each other.
14 . The management method according to claim 13 , wherein the management server is configured to further execute terminating the correspondence in response to reception of a termination request from at least the first terminal and the second terminal or satisfaction of a predetermined termination condition.
15 . The management method according to claim 13 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least the first terminal and the second terminal includes:
receiving the second identifier and the second unique information from the first terminal; and
receiving the first identifier and the first unique information from the second terminal.
16 . The management method according to claim 13 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least the first terminal and the second terminal includes:
receiving the first identifier and the second unique information from the first terminal; and
receiving the second identifier and the first unique information from the second terminal.
17 . The management method according to claim 13 , wherein the receiving the first identifier, the first unique information, the second identifier, and the second unique information from at least the first terminal and the second terminal includes:
receiving the second identifier and the first unique information from the first terminal; and
receiving the first identifier and the second unique information from the second terminal.
18 . The management method according to claim 13 , wherein:
the first target is a user;
the first terminal is a user terminal associated with the user;
the second target is a use item to be used by the user; and
the second terminal is a load terminal to be loaded on the use item.
19 . The management method according to claim 18 , wherein the use item is a mobile body.
20 . A non-transitory computer-readable storage medium storing instructions that are executable by one or more processors and that cause the one or more processors to perform functions comprising:
receiving, in response to occurrence of a physical use relationship between a first target and a second target for using the second target by the first target, a first identifier of the first target, first unique information of the first target, a second identifier of the second target, and second unique information of the second target from at least one of a first terminal of the first target and a second terminal of the second target;
requesting a first server to authenticate the first target by transmitting the received first identifier and the received first unique information to the first server;
receiving a result of authentication of the first target from the first server;
requesting a second server to authenticate the second target by transmitting the received second identifier and the received second unique information to the second server;
receiving a result of authentication of the second target from the second server;
setting a correspondence between the first identifier and the second identifier when the received results of the authentication show that both the first target and the second target have successfully been authenticated; and
recording a time at which the correspondence is set as a starting time of the first target being linked with the second target, wherein
the management server, the first terminal, the second terminal, the first server, and the second server are separate and distinct from each other.