System and program

Abstract

To provide a technology for tracking use relation between a first object and a second object while securing security, and for imparting proxy authority to a proxy individual while the use relation is established.SOLUTION: In a system according to one aspect of the present disclosure, a first terminal of a proxy individual for a first object receives authority imparting information from a terminal of a proxy requesting individual for the first object. A second terminal of an object individual for a second object requests verification of proxy right according to the request from the first terminal. In response to establishment of the verification, at least one of the first terminal and the second terminal transmits a linking request to a management server. In response to establishment of authentication of the proxy requesting individual, the management server sets correspondence between the proxy requesting individual and the object individual, thereby enabling the proxy individual to exercise the authority of the proxy requesting individual by proxy via the object individual.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a system and a program. [Background technology]

[0002] Patent Document 1 proposes a fee collection system for collecting fees for services from vehicle users using a medium such as a card. Specifically, the fee collection system proposed in Patent Document 1 uses the ID of an ETC (Electronic Toll Collection System) card, It is configured to allocate the charge for expressway usage tolls for the target rental car to the target user based on the correspondence between the rental car company, the date and time of rental car use, and the rental car user (billing information, registration information, payment information, and usage information). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-140747 A Summary of the Invention [Problem to be solved by the invention]

[0004] One objective of the present disclosure is to provide a technique for tracking a usage relationship between a first object and a second object while ensuring security, and for granting proxy authority to a proxy individual for the duration of the usage relationship. [Means for solving the problem]

[0005] The system according to the first aspect of the present disclosure includes a management server, a first terminal of a surrogate individual of a first target, and a second terminal of a target individual of a second target. The first terminal is configured to receive authorization information notifying the granting of the authority of agency from a terminal of the surrogate request individual of the first target, and, when a relationship of use between the surrogate individual and the target individual occurs, to exchange data with the second terminal, and to request the verification of the authority of the agency by providing authority verification information to the second terminal in the data exchange. The second terminal is configured to verify the authority of the agency using the authority verification information in response to the request from the first terminal. At least one of the first terminal and the second terminal is configured to transmit a linking request including an authentication request for the agency request individual to the management server in response to the establishment of the verification by the second terminal. The management server is configured to enable the agency exercise of the authority of the agency request individual by the surrogate individual via the target individual by setting a correspondence relationship between the agency request individual and the target individual in response to the establishment of authentication of the agency request individual in response to the authentication request.

[0006] A program according to a second aspect of the present disclosure causes a first terminal of a surrogate individual of a first target to receive, from a terminal of a surrogate request individual of the first target, authority grant information notifying the granting of agency authority, and, when a usage relationship occurs between the surrogate individual and a target individual of a second target, to exchange data with a second terminal of the target individual, and, in the data exchange, to request verification of the agency authority by providing authority verification information to the second terminal, and, in response to the establishment of the verification by the second terminal, to transmit a linking request including a request for authentication of the surrogate request individual to a management server, and, in response to the establishment of the authentication of the surrogate request individual in response to the authentication request, to transmit the linking request jointly with the second terminal, or to cause the second terminal to transmit the linking request, thereby enabling the surrogate individual to exercise by proxy the authority of the surrogate request individual via the target individual. It is.

[0007] A program according to a third aspect of the present disclosure is a program for causing a second terminal of a target individual of a second target to exchange data with a first terminal of the surrogate individual when a usage relationship occurs between a surrogate individual of a first target and the target individual, receiving a request for verification of agency authority from the first terminal in the data exchange, accompanied by authority verification information, verifying the agency authority using the authority verification information in response to the request from the first terminal, and, in response to the success of the verification, sending a linking request including an authentication request for the surrogate request individual to a management server, sending the linking request jointly with the first terminal, or causing the first terminal to send the linking request to the first terminal, thereby enabling the surrogate individual to exercise the authority of the surrogate request individual via the target individual in response to the success of authentication of the surrogate request individual in response to the authentication request. Effect of the Invention

[0008] According to the present disclosure, it is possible to provide a technique for tracking a usage relationship between a first object and a second object while ensuring security, and for granting proxy authority to a proxy individual for the duration of the usage relationship. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a situation to which the present disclosure is applied. [Diagram 2] FIG. 2 shows a schematic diagram of an example of a scenario to which the present disclosure is applied. [Figure 3A] FIG. 3A illustrates an example of the linking information according to the present embodiment. [Figure 3B] FIG. 3B illustrates an example of user information according to the present embodiment. [Figure 3C] FIG. 3C illustrates an example of moving object information according to the present embodiment. [Figure 4]FIG. 4 shows a schematic diagram of an example of data exchange according to the present embodiment. [Figure 5A] FIG. 5A illustrates an example of a process for verifying the power of attorney according to this embodiment. [Figure 5B] FIG. 5B illustrates an example of a process for verifying the power of attorney according to this embodiment. [Figure 6] FIG. 6 shows an example of a process of canceling a link according to this embodiment. [Figure 7A] FIG. 7A shows a schematic diagram of an example of a process of releasing a link by a proxy requesting individual according to this embodiment. [Figure 7B] FIG. 7B shows a schematic diagram of an example of a process of releasing a link by a proxy requesting individual according to this embodiment. [Figure 8] FIG. 8 shows an example of a process for confirming continued use according to this embodiment. [Figure 9] FIG. 9 is a schematic diagram showing an example of a situation in which the association information according to the present embodiment is used. [Figure 10A] FIG. 10A illustrates an example of a hardware configuration of a management server according to this embodiment. [Figure 10B] FIG. 10B illustrates an example of a hardware configuration of the first server according to this embodiment. [Figure 10C] FIG. 10C illustrates an example of a hardware configuration of the second server according to this embodiment. [Figure 10D] FIG. 10D illustrates an example of a hardware configuration of the first terminal according to this embodiment. [Figure 10E] FIG. 10E illustrates an example of a hardware configuration of a second terminal according to the present embodiment. [Figure 10F] FIG. 10F illustrates an example of a hardware configuration of a terminal according to this embodiment. [Figure 11] FIG. 11 shows an example of a software configuration of each device according to the present embodiment. [Figure 12A] FIG. 12A shows an example of a processing procedure for linking settings according to this embodiment. [Figure 12B]FIG. 12B shows an example of a processing procedure for canceling association according to this embodiment. [Figure 13A] FIG. 13A illustrates an example of an authentication process when the first authentication method is adopted. [Figure 13B] FIG. 13B illustrates an example of an authentication process when the first authentication method is adopted. [Figure 14A] FIG. 14A illustrates an example of an authentication process when the second authentication method is adopted. [Figure 14B] FIG. 14B illustrates an example of an authentication process when the second authentication method is adopted. [Figure 15A] FIG. 15A shows a schematic diagram of an example of an authentication process when the 3-1st authentication method is adopted. [Figure 15B] FIG. 15B illustrates an example of an authentication process when the 3-1st authentication method is adopted. [Figure 16A] FIG. 16A illustrates an example of an authentication process when the 3-2 authentication method is adopted. [Figure 16B] FIG. 16B illustrates an example of an authentication process when the 3-2 authentication method is adopted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] According to the system proposed in Patent Document 1, a user can pay highway tolls by ETC even if he or she does not have an ETC card. However, the inventors of the present invention found that the conventional system has the following problems.

[0011] In other words, with the diversification of MaaS (Mobility as a Service), the efficiency of payments, prescriptions, etc. From the viewpoint of convenience of using prescriptions, etc., it is considered that there will be a demand to track the use of a mobile object by another person at the request of a user while ensuring security, and to grant proxy authority to the other person while using the mobile object. For example, when a prescription is issued to a certain person (requester / proxy requesting individual), a case is assumed in which the authority to exercise the issued prescription on behalf of the other person (agent / proxy individual) who uses the mobile object is granted. In this case, it is assumed that while using the mobile object, the other person will use the prescription to obtain the medicine on behalf of the other person. In contrast, in the conventional system, the correspondence between the date and time of use and the user can be stored as usage information according to the rental car contract or reservation, but since this date and time of use depends on the contract or reservation, the usage information does not necessarily match the actual use of the rental car by the user. In addition, for vehicles used without a contract or reservation (e.g., private cars), the generation of usage information is not assumed in the first place. Furthermore, since the usage information is generated according to the user's request, the usage information only indicates the usage of the user, and it is difficult to track the usage of others. Therefore, in the conventional system, it is difficult to ensure security while tracking the use of a mobile object by another person at the request of the user and granting the other person the authority to act as a proxy while the relationship of use is established. This problem does not occur only when a vehicle is used. The same problem can occur when a mobile object other than a vehicle (e.g., an aircraft, a ship, etc.) is used and when multiple types of mobile objects are used. Furthermore, the same problem can occur in any usage situation other than a mobile object.

[0012] In contrast, a system according to a first aspect of the present disclosure comprises a management server, a first terminal of a surrogate individual of a first target, and a second terminal of a target individual of a second target. The first terminal is configured to receive, from a terminal of the surrogate requesting individual of the first target, authority granting information notifying the granting of authority of agency, and, when a usage relationship occurs between the surrogate individual and the target individual, to exchange data with the second terminal, and in the data exchange, to provide authority verification information to the second terminal, thereby requesting verification of the authority of agency. The second terminal is configured to verify the authority of agency using the authority verification information in response to a request from the first terminal. At least one of the first terminal and the second terminal is configured to request the second terminal to verify the authority of agency. The management server is configured to transmit a linking request including an authentication request for the surrogate requesting individual to the management server in response to the establishment of authentication of the surrogate requesting individual in response to the authentication request. The management server is configured to validate the proxy exercise of the authority of the surrogate requesting individual by the surrogate individual via the target individual by setting a correspondence relationship between the surrogate requesting individual and the target individual in response to the establishment of authentication of the surrogate requesting individual in response to the authentication request.

[0013] In the first aspect of the present disclosure, by setting a correspondence (linking) between the proxy requesting individual of the first target and the target individual of the second target, it is possible to track the utilization relationship between the proxy requesting individual and the target individual in response to the request of the proxy requesting individual. In addition, security can be ensured by a verification process of the proxy authority and an authentication process of the proxy requesting individual of the first target. Then, in accordance with the setting of the correspondence between the proxy requesting individual and the target individual, the proxy individual is enabled to exercise the authority of the proxy requesting individual by proxy via the target individual. This allows the proxy individual to exercise at least a part of the authority of the proxy requesting individual on behalf of the proxy requesting individual. Therefore, according to the first aspect of the present disclosure, it is possible to track the utilization relationship between the first target and the second target while ensuring security, and to grant the proxy individual the authority to exercise at least a part of the authority of the proxy requesting individual by proxy while the utilization relationship is established.

[0014] The embodiment of the present disclosure may not be limited to the above example. As another embodiment of the system according to the above embodiment, one aspect of the present disclosure may be an information processing device that realizes all or part of the above components, an information processing method, a program, or a machine-readable storage medium such as a computer that stores such a program. Here, the machine-readable storage medium is a medium that accumulates information such as a program by electrical, magnetic, optical, mechanical, or chemical action. The information processing device may be at least one of the management server, the first terminal, and the second terminal according to the above embodiment. In addition, the system according to the above embodiment may further include at least one of a first server involved in the authentication of the first target and a second server involved in the authentication of the second target.

[0015] For example, a program according to a second aspect of the present disclosure may be a program for causing a first terminal of a surrogate individual of a first target to receive authority granting information notifying the granting of agency authority from a terminal of a surrogate requesting individual of a first target; when a usage relationship occurs between the surrogate individual and the target individual of a second target, to exchange data with a second terminal of the target individual; requesting verification of the agency authority by providing authority verification information to the second terminal in the data exchange; and, upon establishment of verification by the second terminal, sending a linking request including a request for authentication of the surrogate requesting individual to a management server, sending the linking request jointly with the second terminal, or causing the second terminal to send the linking request, thereby enabling the surrogate individual to exercise the authority of the surrogate requesting individual via the target individual, upon establishment of authentication of the surrogate requesting individual in accordance with the authentication request.

[0016] Furthermore, for example, a program related to a third aspect of the present disclosure is a program for causing a second terminal of a target individual of a second target to exchange data with a first terminal of the surrogate individual when a usage relationship occurs between the surrogate individual of a first target and the target individual, to receive a request for verification of the agency accompanied by authority verification information from the first terminal in the data exchange, to verify the agency using the authority verification information in response to the request from the first terminal, and, in response to the verification being established, to send a linking request including a request for authentication of the surrogate request individual to a management server, to send the linking request jointly with the first terminal, or to have the first terminal send the linking request, thereby causing the management server to set a correspondence relationship between the surrogate request individual and the target individual in response to the authentication of the surrogate request individual in response to the authentication request being established, thereby enabling the surrogate individual to exercise the authority of the surrogate request individual via the target individual.

[0017] Hereinafter, an embodiment according to one aspect of the present disclosure (hereinafter also referred to as "the present embodiment") will be described with reference to the drawings. However, the present embodiment described below is merely an example of the present disclosure in all respects. Various improvements or modifications may be made without departing from the scope of the present disclosure. In implementing the present disclosure, a specific configuration according to the embodiment may be appropriately adopted. Note that while the data appearing in this embodiment is described in natural language, more specifically, it is specified in pseudo-language, commands, parameters, machine language, etc. that can be recognized by a computer.

[0018] [1 Application example] FIG. 1 is a schematic diagram showing an example of a scene in which the present disclosure is applied. The system 100 according to the present embodiment is configured with a management server 1, a first terminal 4, and a second terminal 5. The management server 1 is one or more computers configured to record the correspondence (linking) between the first target and the second target. The first terminal 4 corresponds to a representative individual PI of the first target, and the second terminal 5 corresponds to a target individual TA of the second target. A terminal may be provided for each individual of the first target. A terminal may also be provided for each individual of the second target. The first terminal 4 is an example of a terminal of the first target, and the second terminal 5 is an example of a terminal of the second target.

[0019] In this embodiment, the terminal 6 of the proxy requesting individual PR of the first target accepts settings regarding the granting of proxy authority, including the designation of the proxy individual PI. The proxy individual PI may be designated appropriately by another individual of the first target. When settings regarding the granting of proxy authority are made, the terminal 6 directly or indirectly transmits authority granting information AG notifying the granting of proxy authority to the first terminal 4. In response, the first terminal 4 receives the authority granting information AG from the terminal 6 (step S10). Note that indirect transmission may include transmission via an external computer. The terminal 6 is an example of a terminal of the first target. The system 100 may include this terminal 6.

[0020] When a usage relationship occurs between the proxy individual PI and the target individual TA, the first terminal 4 exchanges data with the second terminal 5 (step S20). In this data exchange, the first terminal 4 requests verification of the proxy authority by providing authority verification information AU to the second terminal 5. In response to the request from the first terminal 4, the second terminal 5 verifies the proxy authority using the authority verification information AU (step S30). In response to the establishment of the verification by the second terminal 5, at least one of the first terminal 4 and the second terminal 5 transmits a linking request including a request for authentication of the proxy requesting individual PR to the management server 1 (step S40). Authentication of the proxy requesting individual PR may be performed appropriately at the time of the linking request.

[0021] The management server 1 sets a correspondence (link) between the proxy requesting individual PR and the target individual TA in response to receiving the linking request and establishing authentication of the proxy requesting individual PR in the authentication process in response to the authentication request (steps S50, S60). In one example, the management server 1 may generate linking information D10 indicating the establishment of a correspondence between the first target (proxy requesting individual PR) and the second target (target individual TA), and may store the generated linking information D10. Thereby, the management server 1 validates the proxy exercise of the authority of the proxy requesting individual PR by the proxy individual PI via the target individual TA.

[0022] During the above-mentioned process of setting the correspondence relationship, authentication processing of at least one of the first target proxy individual PI and the second target target individual TA may also be performed in addition to authentication processing of the proxy requesting individual PR. A series of processes from data exchange to linking setting may be performed in real time in response to the occurrence of a usage relationship. The set correspondence relationship (linking) may be released at any timing. In one example, the correspondence relationship may be released in response to the termination of the usage relationship.

[0023] In addition, as long as it is possible to identify each individual for which a correspondence relationship is set, the expression format of the information indicating the setting of the correspondence relationship (the linking information D10) is not particularly limited and may be determined appropriately depending on the embodiment. In one example, each individual of the first target may be given a first identifier I10, and each individual of the first target may be identified by the first identifier I10. Similarly, each individual of the second target may be given a second identifier I20, and each individual of the second target may be identified by the second identifier I20. Setting the correspondence between the proxy request individual PR and the target individual TA may be configured by setting a correspondence between the first identifier I10 given to the proxy request individual PR and the second identifier I20 given to the target individual TA. That is, the setting of the correspondence may be expressed using the first identifier I10 and the second identifier I20.

[0024] As described above, in this embodiment, by setting a correspondence (linking) between the proxy request individual PR of the first target and the target individual TA of the second target, the use relationship between the proxy individual PI and the target individual TA in response to the request of the proxy request individual PR can be tracked. In addition, security can be ensured by the verification process of the proxy right using the authority verification information AU and the authentication process of the proxy request individual PR. Furthermore, in accordance with the setting of the correspondence between the proxy request individual PR and the target individual TA, the proxy individual PI is enabled to exercise the authority of the proxy request individual PR via the target individual TA. This allows the proxy individual PI to exercise at least a part of the authority of the proxy request individual PR on behalf of the proxy request individual PR. Therefore, according to this embodiment, while ensuring security, the use relationship between the first target and the second target can be tracked, and the proxy individual PI can be granted the proxy authority to exercise at least a part of the authority of the proxy request individual PR on behalf of the proxy request individual PR while the use relationship is established.

[0025] (subject) The first object and the second object may not be particularly limited as long as a relationship of use can be established, and may be appropriately selected according to the embodiment. The first object and the second object may be any object, such as an object, a human, or another living thing. Any object may include a virtual object. The establishment of a relationship of use may be, for example, the occurrence of a real or virtual relationship between at least two objects, such as one using the other, one possessing the other, one combining with the other, or one connecting with the other. The system 100 of the present disclosure may be used in any situation where a correspondence relationship between two or more objects is tracked.

[0026] In this embodiment, the setting of a correspondence relationship by proxy of the proxy individual PI in response to a request from the proxy requesting individual PR is permitted for the first object. In contrast, the setting of such a correspondence relationship by proxy may or may not be permitted for the second object. When a form in which a proxy is not permitted for the second object is adopted, one of the first object and the second object that permits link setting by a proxy may be selected as the first object, and the other object that does not permit link setting by a proxy may be selected as the second object.

[0027] (1st server / 2nd server) In one example, first target information O10 regarding the first target may be used to indicate details of each individual of the first target (including the proxy request individual PR and the proxy individual PI). The first target information O10 may include a first identifier I10. The first target information O10 may include information used for authentication of the first target (registered unique information, etc.). Similarly, second target information O20 regarding the second target may be used to indicate details of each individual of the second target (including the target individual TA). The second target information O20 may include a second identifier I20. The second target information O20 may include information used for authentication of the second target. The first target information O10 and the second target information O20 may be held in any storage area. At least a portion of the first target information O10 and the second target information O20 may be held accessible from at least one of the management server 1, the external server, and each terminal (4, 5).

[0028] The first target information O10 and the second target information O20 may be appropriately managed. In the example of FIG. 1, the first server 2 may be configured to manage the first target information O10, and the second server 3 may be configured to The first server 2 and the second server 3 may be configured to manage the second target information O20. Each of the first server 2 and the second server 3 may be configured by one or more server devices. The first target information O10 may be stored in a memory resource provided inside and / or outside the first server 2 so as to be accessible from the first server 2. The second target information O20 may be stored in a memory resource provided inside and / or outside the second server 3 so as to be accessible from the second server 3. The internal memory resource may include, for example, a RAM (Random Access Memory), an auxiliary storage device, a storage medium, etc. The external memory resource may include, for example, an external storage device, an external computer (NAS: Network Attached Storage, etc.), etc. In another example, each target information (O10, O20) may be stored in a memory resource of the management server 1.

[0029] The unit for managing each piece of target information (O10, O20) is not particularly limited and may be appropriately determined depending on the embodiment. At least one of the first target information O10 and the second target information O20 may be managed in a centralized (collectively) manner, or may be managed in a decentralized manner (separately) for each arbitrary group. The server devices constituting each server (2, 3) may be deployed by one or more operating organizations (subjects). At least one of the first server 2 and the second server 3 may be deployed by multiple operating organizations. When deployed by multiple operating organizations, the target information may be shared (i.e., may be managed in a centralized manner), or may be managed in a decentralized manner for each operating organization.

[0030] In addition, the first server 2 may be involved in the authentication of the first target (the proxy requesting individual PR and the proxy individual PI). Being involved in the authentication may include determining whether the authentication is successful (being directly involved) and indirectly involved (for example, providing information for determining whether the authentication is successful). When determining whether the authentication of the first target is successful, the first server 2 is an example of an external server (external authentication server) that determines whether the authentication of the first target is successful. Similarly, the second server 3 may be involved in the authentication of the second target (target individual TA). When determining whether the authentication of the second target is successful, the second server 3 is an example of an external server (external authentication server) that determines whether the authentication of the second target is successful.

[0031] (identifier) In one example, each identifier (I10, I20) may be used to identify each individual of each target (including the proxy request individual PR of the first target, the proxy individual PI of the first target, and the target individual TA of the second target). As long as each identifier (I10, I20) can identify each individual of each target, its data format and configuration may not be particularly limited and may be appropriately selected depending on the embodiment. In one example, each identifier (I10, I20) may be composed of a symbol string including numbers, letters, etc. In another example, each identifier (I10, I20) may use unique information such as identification information uniquely assigned to each individual and information derived from each terminal (4, 5, 6). The uniquely assigned identification information may be, for example, a vehicle registration number, a vehicle identification number (VIN), a personal number, etc. When an IC tag is assigned to each individual, the uniquely assigned identification information may include information held by the IC tag. The information derived from each terminal (4, 5, 6) may be, for example, a MAC address (Media Access Control address), terminal identification information (IMEI: International Mobile Equipment Identifier, IMSI: International Mobile Subscriber Identity, MEID: Mobile Equipment Identifier, ICCID: Integrated Circuit Card ID, other serial numbers, etc.), etc.

[0032] (Management Server) The management server 1 may be configured to set a correspondence relationship between the corresponding individuals of the first and second targets in response to a linking request from at least one of the terminal of the first target and the terminal of the second target. In this embodiment, the terminal of the first target may include a first terminal 4 of the representative individual PI, and the terminal of the second target may include a second terminal 5 of the target individual TA. Correspondence between the first target and the second target Setting the relationship may include setting a correspondence relationship between the proxy request individual PR and the target individual TA in response to a linking request from at least one of the first terminal 4 of the proxy individual PI of the first target and the second terminal 5 of the target individual TA of the second target. In addition to the case of representation by the proxy individual PI, setting the correspondence relationship between the first target and the second target may include setting a correspondence relationship between the corresponding individuals of the first target and the second target in response to a linking request from at least one of the terminals of the corresponding individuals of the first target and the second target. The processing of linking setting of this normal route not based on a proxy may be similar to the linking setting of the proxy route, except for the processing related to the proxy such as setting the proxy authority and verification. In the following description of the proxy route, the first terminal 4 and the second terminal 5 may be replaced with the terminals of the corresponding individuals of the first target and the second target, respectively, and this may constitute the processing of the normal route.

[0033] The linking request may be transmitted via any route. In one example, the management server 1 may receive the linking request directly from at least one of the first terminal 4 and the second terminal 5, or may receive it indirectly via an external server. That is, the transmission of the linking request to the management server 1 may be configured by directly transmitting the linking request to the management server 1, or by indirectly transmitting the linking request to the management server 1 via an external server. The external server may include, for example, the first server 2, the second server 3, etc. Also, in one example, the indirect transmission may be configured by simply relaying the linking request by an external computer. In another example, the indirect transmission may be configured by transmitting a request for processing related to the linking to an external computer, such as requesting each server (2, 3) to authenticate each target and having the server transmit the authentication result to the management server 1, and having the external computer transmit some information to the management server 1 according to the result of the execution. That is, the linking request may be transmitted from the external computer to the management server 1 as a result of data communication for another purpose to the external computer. Sending a linking request by at least one of the first terminal 4 and the second terminal 5 may include the first terminal 4 sending a linking request, the first terminal 4 and the second terminal 5 jointly sending a linking request, and the second terminal 5 sending a linking request.

[0034] The management server 1 may receive a linking request (a request for linking setting) in response to the occurrence of a utilization relationship, and may set a correspondence relationship between the relevant individuals of the first target and the second target in response to the received linking request. The management server 1 may receive a release request (a request for releasing the link) in response to the disappearance of the utilization relationship, and may release the correspondence relationship as appropriate in response to the received release request. The linking request and the release request may be configured to specify the relevant individual to be processed in any manner. In a typical example, the linking request and the release request may be configured to specify the relevant individual to be processed by including the first identifier I10 and the second identifier I20, respectively. In the above embodiment, the linking request transmitted from at least one of the first terminal 4 of the proxy individual PI and the second terminal 5 of the target individual TA may be configured to specify the individuals to be linked (proxy request individual PR and target individual TA) by including the first identifier I10 of the proxy request individual PR and the second identifier I20 of the target individual TA. However, the method of specifying the relevant individual to be processed is not limited to such an example, and may be changed as appropriate depending on the embodiment. In another example, at least one of the linking request and the release request may omit at least one of the first identifier I10 and the second identifier I20 by using alternative information. For example, an identifier may be assigned as alternative information to a combination of corresponding individuals of the first target and the second target (linking setting). The identifier may be assigned at any time, for example, when the initial linking setting is performed. At least one of the linking request and the release request may be configured to include this identifier to specify the corresponding individuals of each target to be processed without including at least one of the first identifier I10 and the second identifier I20.

[0035] The management server 1 may be configured by one or more server devices. In this embodiment, the management server 1 associates information regarding the occurrence and disappearance of a correspondence relationship between a first object and a second object. The linking information D10 may be configured to be recorded as information D10. The linking information D10 may be stored in a memory resource arranged inside or outside the management server 1. The internal memory resource may include, for example, a RAM, an auxiliary storage device, a storage medium, etc. The external memory resource may include, for example, an external storage device, an external computer (NAS, etc.), etc.

[0036] The obtained linking information D10 may be used in various situations. In one example, the linking information D10 may be used to track the relationship between the first object and the second object. As a specific example, the linking information D10 may be used to enable the authority linked to either one of the first object and the second object (the first object information O10 and the second object information O20) to be exercised from the other object while the correspondence relationship between the first object and the second object is set. That is, the linking information D10 may be used to enable the authority of either one of the first object and the second object to be exercised from the other object according to the linking between the first object and the second object (FIG. 2 to be described later). In this embodiment, the linking information D10 may be used to enable the proxy individual PI to exercise at least a part of the authority of the proxy request individual PR on behalf of the proxy individual PI via the target individual TA according to the linking between the proxy request individual PR of the first object and the target individual TA of the second object.

[0037] In one example of this embodiment, the linking information D10 may include information on the first identifier I10 and the second identifier I20 of the individual to indicate the combination of the first object and the second object for which a correspondence relationship is set. The management server 1 may acquire each identifier (I10, I20) of each object as appropriate. In one example, the management server 1 may not hold in advance information on the first identifier I10 and the second identifier I20 for which a correspondence relationship is set, but may acquire the information each time from at least one of the servers (2, 3) and the terminals (4, 5). In another example, the management server 1 may hold in advance information on at least one of the first identifier I10 and the second identifier I20 for which a correspondence relationship is set.

[0038] In addition, in one example of this embodiment, when the correspondence is set by the proxy of the proxy individual PI, the linking information D10 may further include information about the proxy. The information about the proxy may include, for example, identification information of the proxy individual PI, information about the proxy right (expiration date, valid authority, etc.), etc. In one example, in order to identify the designated proxy individual PI, the information about the proxy may include the first identifier I10 of the proxy individual PI. The information about the proxy may be appropriately transmitted to the management server 1. The information about the proxy may be transmitted directly or indirectly to the management server 1 from at least one of the first terminal 4 and the terminal 6. The information about the proxy may be transmitted from the terminal 6 to the management server 1 via at least one of the first terminal 4 and the second terminal 5. When the terminal 6 designates the proxy individual PI in an external server such as the first server 2, the information about the proxy may be transmitted directly or indirectly from the external server to the management server 1. In another example, the linking information D10 may not include information about the proxy. The information about the proxy may be held in a place other than the linking information D10, such as the first target information O10, for example. The information regarding the proxy may be managed by an external server such as the first server 2.

[0039] The relationship between the management server 1 and the management organizations of the servers (2, 3) may be arbitrary. In one example, the management organization of the management server 1 may overlap with the management organization of at least one of the first server 2 and the second server 3. In another example, the management organization of the management server 1 may be different from the management organizations of the first server 2 and the second server 3. The system 100 of the present disclosure may be produced by connecting the management server 1 to each terminal (4, 5) via a network, and deploying each in a state in which it is capable of executing the above-mentioned information processing, according to the intention of the management organization of the management server 1. When each server (2, 3) is involved in information processing related to the linking (e.g., authentication processing), each server (2, 3) may be interpreted as being included in the system 100. In this case, the system 100 of the present disclosure may be produced by further connecting the management server 1 to each server (2, 3) via a network, and further deploying each server (2, 3) in a state in which it is capable of executing information processing related to the linking. Furthermore, the terminal 6 of the first target proxy request individual PR may also be produced by the system 1 It may be interpreted as being included in 00.

[0040] (Terminal) The first terminal 4 relates to a proxy individual PI of the first object. The second terminal 5 relates to an object individual TA of the second object. The terminal 6 relates to a proxy request individual PR of the first object. In one example, each terminal (4, 5, 6) may accompany each corresponding individual (PI, TA, PR). Accompanying may include being temporarily or permanently deployed inside or outside the object, being carried by the object (human), and being carried by a human involved with the object (object). Deploying may include loading. Loading may include being placed on the object at least temporarily when the object is used, in addition to being placed on the object at all times. Loading may include being carried by a user of the object. At least one of the first terminal 4, the second terminal 5, and the terminal 6 may be the corresponding individual (PI, TA, PR) itself. Each terminal (4, 5, 6) may be composed of one or more computers. In addition, with regard to each terminal (4, 5, 6), multiple terminals may be used as terminals of the same individual, for example, when one user shares an account among multiple terminals. In this case, multiple terminals used by the same individual may be interpreted as one terminal of one individual.

[0041] In the above embodiment, the first terminal 4 of the proxy individual PI of the first target receives authority granting information AG notifying the granting of the proxy authority from the terminal 6 of the proxy request individual PR of the first target. When a usage relationship occurs between the proxy individual PI and the target individual TA of the second target, the first terminal 4 exchanges data with the second terminal 5 of the target individual TA. In the data exchange, the first terminal 4 requests the verification of the proxy authority by providing authority verification information AU to the second terminal 5. Then, in response to the establishment of the verification by the second terminal 5, the first terminal 4 transmits a linking request including an authentication request of the proxy request individual PR to the management server 1, transmits the linking request together with the second terminal 5, or causes the second terminal 5 to transmit the linking request. As a result, the first terminal 4 causes the management server 1 to set a correspondence relationship between the proxy request individual PR and the target individual TA in response to the establishment of the authentication of the proxy request individual PR in response to the authentication request, thereby validating the proxy exercise of the authority of the proxy request individual PR by the proxy individual PI via the target individual TA.

[0042] In the above embodiment, the second terminal 5 of the target individual TA of the second target exchanges data with the first terminal 4 of the proxy individual PI when a usage relationship occurs between the proxy individual PI of the first target and the target individual TA. In the data exchange, the second terminal 5 receives a request for verification of the proxy authority accompanied by the authority verification information AU from the first terminal 4. In response to the request from the first terminal 4, the second terminal 5 verifies the proxy authority using the authority verification information AU. Then, in response to the establishment of the verification, the second terminal 5 transmits a linking request including an authentication request for the proxy request individual PR to the management server 1, transmits the linking request together with the first terminal 4, or causes the first terminal 4 to transmit the linking request. As a result, the second terminal 5 causes the management server 1 to set a correspondence relationship between the proxy request individual PR and the target individual TA in response to the establishment of authentication of the proxy request individual PR in response to the authentication request, thereby validating the proxy exercise of the authority of the proxy request individual PR by the proxy individual PI via the target individual TA.

[0043] In the above embodiment, the terminal 6 of the proxy requesting individual PR of the first target accepts settings regarding the granting of proxy rights, including the designation of the proxy individual PI. Information processing of the settings regarding the proxy may be executed on the terminal 6, or may be executed on an external computer such as the first server 2 via the terminal 6. Furthermore, the proxy individual PI may be designated as appropriate. In a typical example, the terminal 6 may store an address book, and may accept the selection of the proxy individual PI from an individual (e.g., a user) registered in the address book. In another example, the terminal 6 may access a list of the first target via an external computer such as the first server 2, and may accept the selection of the proxy individual PI from an individual registered in the list. The designation of the proxy individual PI may be performed automatically by computer processing, or may be performed manually by at least partially including a user operation. good.

[0044] When the proxy individual PI is designated, the terminal 6 exchanges data with the terminal (first terminal 4) of the designated proxy individual PI, and provides the first terminal 4 with authorization information AG for notifying the grant of the proxy authority. In response to this, the first terminal 4 receives the authorization information AG from the terminal 6. The authorization information AG may have any configuration as long as it can notify the grant of the proxy authority, and may be appropriately selected depending on the embodiment. In one example, the authorization information AG may include authority verification information AU. In another example, the authorization information AG may be composed of information that simply notifies the grant of the proxy authority. In addition, the data exchange between the terminal 6 and the first terminal 4 may be performed by wireless or wired data communication, or may be performed by a method other than data communication, such as reading a two-dimensional code. In one example, when data communication is adopted, the data exchange between the terminal 6 and the first terminal 4 may be performed by a short mail, an e-mail, a notification in a communication application (e.g., a Social Networking Service application, etc.), etc. Furthermore, the terminal 6 may directly provide the authorization information AG to the first terminal 4, or may indirectly transmit it via an external computer such as the first server 2. As a result, the terminal 6 of the proxy requesting individual PR may grant the authority to authenticate on behalf of the first terminal 4 of the proxy individual PI, and cause it to execute a process of setting up a correspondence relationship with the second target.

[0045] The settings regarding the granting of the proxy authority may include various settings related to the proxy authority other than the designation of the proxy individual PI. In one example, the settings regarding the granting of the proxy authority may include at least one of the settings of the expiration date and the valid authority. Accordingly, at least one of the expiration date and the valid authority may be set for the proxy authority. When the expiration date is set for the proxy authority, the management server 1 may be configured to cancel the correspondence between the proxy request individual PR and the target individual TA in response to the expiration date. When the valid authority is set for the proxy authority, the management server 1 may be configured to cancel the correspondence between the proxy request individual PR and the target individual TA in response to the exercise or extinction of the valid authority by the proxy individual PI. By setting at least one of the expiration date and the valid authority, it is possible to set a restriction on the proxy authority granted to the proxy individual PI. The setting of at least one of the expiration date and the valid authority may be performed automatically by computer processing, or may be performed manually by at least partially including a user operation.

[0046] Information on the proxy individual PI, the expiration date, the validity of the proxy, and other information on the set proxy (proxy information) may be appropriately managed. The proxy information may be managed by at least one of the management server 1, an external computer (e.g., the first server 2), the first terminal 4, the second terminal 5, and the terminal 6. In one example, a setting process related to the proxy may be executed on the first server 2, and the first server 2 may generate the proxy information in response to the execution of this setting process. The first server 2 may manage the proxy information in association with the first target information O10. The first server 2 may notify the management server 1 of the proxy information as appropriate. In another example, information on the proxy individual PI (e.g., the first identifier I10) may be transmitted from the first terminal 4. In another example, the proxy information may be generated in response to a setting process on the terminal 6. The proxy information may be transmitted from the terminal 6 to the first server 2, and may be managed in the first server 2 in association with the first target information O10. In another example, the proxy authority information may be notified to the management server 1 from the first server 2 or the terminal 6 via at least one of the first terminal 4 and the second terminal 5, and may be associated with the association information D10 and managed in the management server 1. For example, the proxy authority information may be transmitted together with the association request. In another example, the proxy authority information may be transmitted directly or indirectly from the terminal 6 to the management server 1, rather than via at least one of the first terminal 4 and the second terminal 5. In this case, the management server 1 may appropriately associate the association request received from at least one of the first terminal 4 and the second terminal 5 with the proxy authority information. The association of the data may be specified by any method. In one example, the data of the association request and the data of the proxy authority information may both include shared information for specifying the association. The shared information may be, for example, a matching information. , and may be composed of information having a relationship in which a correspondence relationship is established. In one example, the shared information may be composed of a first identifier I10 of at least one of the proxy request individual PR and the proxy individual PI. In another example, the shared information may be composed of temporary information such as a random number, a timestamp, a hash value, etc. Note that the timing for setting the valid authority and the expiration date does not have to be limited to the same time as the timing for specifying the proxy individual PI. At least one of the valid authority and the expiration date may be set at any timing before the correspondence relationship is released.

[0047] (Operation example) The first object and the second object may be appropriately selected. In one example, one of the first object and the second object may be a user. One of the first terminal 4 and the second terminal 5 corresponding to the user may be a user terminal related to the user. The other of the first object and the second object may be a use object used by the user. One of the first terminal 4 and the second terminal 5 corresponding to the use object may be a loading terminal loaded on the use object. According to one example of the present embodiment, it is possible to track the use relationship between the user and the use object. In one example, the first object may be a user, and the second object may be a use object. The proxy individual PI of the first object may be a proxy user, and the proxy request individual PR of the first object may be a proxy request user.

[0048] The type of the object of use is not particularly limited as long as it can be used by the user, and may be appropriately selected according to the embodiment. In one example, the object of use may be a moving body (mobility). According to one example of the present embodiment, the usage relationship between the user and the moving body can be tracked. The type of the moving body may be appropriately selected. The moving body may be, for example, a vehicle, a railroad vehicle, an aircraft (aircraft, drone, etc.), a ship, etc. The moving body may be at least one of a manually controlled manned aircraft and an automatically controlled unmanned aircraft. When the moving body is a vehicle, the type of the vehicle may be arbitrarily selected. The type of the vehicle may be, for example, a two-wheeled vehicle, a three-wheeled vehicle, a four-wheeled vehicle, etc. The vehicle may include a private car, a rental car, a shared car, a taxi, a bus, etc. The vehicle may be at least one of an automatic driving vehicle and a manually driving vehicle. The loaded terminal may be called a mobile terminal.

[0049] FIG. 2 is a schematic diagram showing an example of a scene in which the system 100 of the present disclosure is applied. In the example of FIG. 2, the first object is a user and the second object is a moving object. In the following description of the example of FIG. 2, for convenience, the "first" is treated as relating to the user and the "second" is treated as relating to the moving object. However, the correspondence between the "first" and the "second" is not limited to the example of FIG. 2. The "first" and the "second" may be interchangeable. That is, the second object may be the user and the first object may be the moving object.

[0050] When the first target is a user, an example of the first terminal 4 is a user terminal possessed by a proxy user, and an example of the terminal 6 is a user terminal possessed by a proxy requesting user. Each user terminal may be any computer, such as a mobile terminal (such as a smartphone), a dedicated device (such as an electronic key device), or other computer device. A user's account may be shared among multiple computers, and accordingly, each computer sharing the account may be used as a user terminal (the first terminal 4, the terminal 6) of the same user.

[0051] An example of the first identifier I10 is a user identifier (user ID, my ID). The user identifier may be, for example, a user account ID, a personal number, identification information of a user terminal (for example, a MAC address, terminal identification information), etc. An example of the first target information O10 is user information O10A. The user information O10A may include any information related to a user. In one example, the user information O10A may include information related to the authority of the corresponding user (corresponding individual of the user), and thus may be associated with various information E10 for exercising the authority. The various information E10 may include, for example, public personal authentication information, payment information, other service-related information, etc. The public personal authentication information may include, for example, a personal number, etc. The payment information may be, for example, For example, it may include credit card information, internet banking information, electronic payment information, etc. Other service-related information may include, for example, information related to electronic prescriptions (insurer number, prescription information, etc.). The various information E10 may be managed by an external system or may be managed within the system 100. The first server 2 may be deployed by a public institution, a neutral institution, each business operator (vehicle manufacturer, service operator, etc.), etc. The first server 2 may be called a user ID server, my ID server, etc.

[0052] On the other hand, when the second object is a moving object, an example of the second terminal 5 is a moving object terminal (on-board terminal). The moving object terminal may be, for example, a terminal attached inside or outside the moving object, a terminal carried by a person involved in the operation of the moving object (for example, a driver, a conductor, etc.), a device installed in a facility of the moving object (for example, a ticket gate, etc.), etc. When the moving object is a vehicle, the moving object terminal may be called an on-board terminal.

[0053] An example of the second identifier I20 is a mobile body identifier (mobile body ID, car ID). The mobile body identifier may be, for example, an ID of a mobile body account, identification information uniquely assigned to a target mobile body (for example, a vehicle registration number, vehicle identification information, etc.), identification information of a mobile body terminal, etc. An example of the second target information O20 is mobile body information O20A. The mobile body information O20A may include any information related to a mobile body. In the example of FIG. 2, depending on the link setting between the proxy request user and the target mobile body, it may be enabled (activated) that the proxy user exercises at least a part of the authority of various information E10 associated with the user information O10A of the proxy request user via the target mobile body. The second server 3 may be deployed by a public institution, a neutral institution, each business operator (vehicle manufacturer, service operating company, etc.), etc. The second server 3 may be called a mobile body ID server, a car ID server, etc.

[0054] A mobile object is an example of a use. The embodiment of FIG. 2 may be applied to any case in which the user (occupant) of the use changes dynamically. The use may be, for example, a rental object, an accommodation facility, etc., in addition to a mobile object. The rental object may include a rental office, a rental space, etc.

[0055] The system 100 may be configured to set a correspondence (link) between the relevant user (first identifier I10) and the relevant individual of the usage object (second identifier I20) in response to the start of usage of the usage object. The system 100 may also be configured to release the correspondence (link) between the relevant individuals in response to the end of usage. The start and end of usage may be detected by any method, for example, at the timing of getting on and off the vehicle, lending and returning the usage object, etc. In one example, at least one of the start and end of usage may be detected in response to the execution of data exchange between the terminals of the user and the usage object (in the proxy case, the first terminal 4 and the second terminal 5).

[0056] In addition, objects to be used can be divided into at least two types: objects that can be used repeatedly over a long period of time, and objects that can be used temporarily. For convenience of explanation, the former are referred to as "objects to be used regularly" and the latter are referred to as "objects to be used temporarily." An example of an object to be used regularly is an object owned by a user, such as a personal car. It is desirable that an object to be used repeatedly over a long period of time is selected as an object to be used regularly. Examples of objects to be used temporarily are objects owned by persons other than the user, such as rental cars, shared cars, public transportation vehicles, rental objects, and accommodation facilities. Examples of public transportation vehicles include taxis, buses, railroad cars, airplanes, and ships.

[0057] In system 100, the type of the object (whether it is a permanent object or a temporary object) may or may not be distinguished. When distinguishing the type of object, system 100 may determine the type of object by any method. In one example, the target information (mobile object information, etc.) may include information indicating the type of object, and system 100 may determine the type of object based on this information. In another example, the type of object is determined based on information such as an identifier and attribute information. In another example, information indicating the type of the object to be used may be included in information transmitted from at least one of the first terminal 4 and the second terminal 5 to the management server 1, and the system 100 may determine the type of the object to be used based on this information. In another example, when the operating organization of the server (in the example of FIG. 2, the second server 3) that handles the information on the object to be used is determined based on the type of the object to be used, the type of the object to be used may be determined based on the affiliation of the operating organization of the server. The system 100 may switch, for example, the form of the linking setting process, the linking release conditions, the management method of the linking information D10, the authentication process, etc., based on the determined type of the object to be used.

[0058] In addition, the application scene of the system 100 of the present disclosure may not be limited to a scene where a relationship between a user and a usage object is tracked. In another example, both the first object and the second object may be robotic devices configured to operate autonomously by automatic control. The robotic device may include a moving body such as an autonomous driving vehicle or a drone. In a scene where two or more robotic devices autonomously interact with each other, the system 100 of the present disclosure may be used to track the emergence and extinction of a relationship between the robotic devices. In this case, in order for one robotic device (a proxy individual PI) to exercise the authority of another robotic device (a proxy requesting individual PR) by proxy, the system 100 may execute the process of linking by proxy.

[0059] (Linking information) FIG. 3A is a schematic diagram showing an example of the linking information D10 according to the present embodiment. In the example of FIG. 3A, it is assumed that a form is adopted in which the setting of the correspondence relationship is expressed using the first identifier I10 and the second identifier I20. The linking information D10 includes the first identifier I10, the second identifier I20, a setting time, and a release time. The first identifier I10 and the second identifier I20 indicate the corresponding individual of the first target and the corresponding individual of the second target in which the correspondence relationship (linking) is set. When the correspondence relationship is set in the above-mentioned proxy case, the linking information D10 includes the first identifier I10 of the proxy requesting individual PR. The setting time indicates the time when the correspondence relationship is set. The setting time may be configured by a time stamp. The release time indicates the time when the correspondence relationship is released. The value of the release time may be added when a process of releasing the correspondence relationship is executed. The method of expressing the release may not be limited to this example. In another example, the release time may be replaced with at least one of an expiration date and a flag. The expiration date indicates the period during which the setting of the correspondence relationship is valid. In this case, whether the setting of the correspondence is valid or not (i.e., whether the correspondence is set or released) is indicated depending on whether it is within the expiration date or not. When the correspondence is set in the above-mentioned proxy case, the expiration date may be set by the proxy requesting individual PR. The flag indicates whether the correspondence is released or not. The flag may be set when the process of releasing the correspondence is executed. In yet another example, the linking information D10 may include at least one of the expiration date and the flag together with a field of the release time. Furthermore, when the correspondence is set in the above-mentioned proxy case and the valid authority is further set, the linking information D10 may further include information indicating the set valid authority. In order to identify the designated proxy individual PI, the linking information D10 may further include the first identifier I10 of the designated proxy individual PI. The information on the expiration date, the valid authority, and the first identifier I10 of the proxy individual PI is an example of information on the set proxy authority (proxy authority information).

[0060] As long as the setting of the correspondence relationship can be indicated, the configuration of the linking information D10 is not limited to the example of FIG. 3A, and may be changed as appropriate depending on the embodiment. In another example, the linking information D10 may further include information indicating the type of the usage object (whether it is a regular usage object or a temporary usage object). The type of the usage object does not necessarily need to be identified by separate information. For example, the type of the usage object may be identified by information such as an identifier. Furthermore, the power of attorney information may be omitted from the linking information D10.

[0061] The data format of the linking information D10 is not particularly limited and may be appropriately selected depending on the embodiment. The linking information D10 may be stored in an arbitrary database. In this example, the linking information D10 may be stored in a relational database such as a table format. In another example, the linking information D10 may be stored in a blockchain platform. In this case, each transaction of setting and canceling the linking may be accumulated in the blockchain as the linking information D10. For example, a transaction of setting the linking may include a first identifier I10, a second identifier I20, and a setting time. A transaction of canceling the linking may include a first identifier I10, a second identifier I20, and a cancel time (or information indicating the cancelation).

[0062] (First target information) The first object information O10 may include any information related to the first object. The first object information O10 may include, for example, a first identifier I10, attribute information of the first object, information related to authority (authority information), information related to the set proxy authority (proxy authority information), etc. In the example of Fig. 2, user information O10A is an example of the first object information O10.

[0063] FIG. 3B illustrates an example of user information O10A according to the present embodiment. In the example of FIG. 3B, the user information O10A includes a user ID (first identifier I10) of a corresponding user, attribute information, and authority information. The attribute information may include any information related to the attributes of the corresponding user. The attribute information may include personal information such as name, address, age, gender, and contact information. The authority information is related to the authority of the corresponding user. The authority information may include, for example, information for linking with a server that executes information processing related to the target authority, information indicating an association with various information E10, and the like.

[0064] If the corresponding user sets the proxy authority as a proxy request user, the user information O10A may further include proxy authority information regarding the set proxy authority. In one example, the proxy authority information may include the user ID of the proxy user (the first identifier I10 of the proxy individual PI), the expiration date, and the valid authority. The proxy authority information may be associated with the authority information.

[0065] The configuration of the user information O10A is not limited to the example of FIG. 3B, and may be appropriately changed depending on the embodiment. For example, the user information O10A (first target information O10) may further include information (e.g., registered unique information, etc.) used for authenticating the user (first target). Also, the proxy authority information may be omitted from the user information O10A (first target information O10). The proxy authority information may be stored in association with at least one of the associated information D10 and the first target information O10, as exemplified in FIG. 3A and FIG. 3B, or may be stored separately from the associated information D10 and the first target information O10.

[0066] The data format of the first target information O10 (user information O10A) is not particularly limited and may be appropriately selected depending on the embodiment. The first target information O10 (user information O10A) may be held in any database platform. In one example, the first target information O10 (user information O10A) may be held in a relational database such as a table format. In another example, the first target information O10 (user information O10A) may be held in a blockchain platform.

[0067] (Second target information) The second object information O20 may include any information related to the second object. The second object information O20 may include, for example, a second identifier I20, attribute information of the second object, information related to authority, etc. In the example of FIG. 2, the mobile object information O20A is an example of the second object information O20.

[0068] FIG. 3C is a schematic diagram illustrating an example of moving body information O20A according to the present embodiment. In the example of FIG. 3C, the moving body information O20A includes a moving body ID (second identifier I20) and attribute information. The attribute information includes number, type, and owner information. When the moving body is a vehicle, the number may be a vehicle registration number. The type may be defined arbitrarily. In one example, the type may be defined to indicate a category that can distinguish between a regular use object and a temporary use object, such as a private car, a rental car, a shared car, a public transportation vehicle, etc. The type may also include a type of the vehicle, such as a vehicle model. The owner information may include any information regarding the owner of the vehicle. The owner information may include personal information of the owner, such as, for example, name, address, age, sex, contact information, etc. The owner may be a corporation.

[0069] The configuration of the mobile object information O20A is not limited to the example of FIG. 3C, and may be modified as appropriate depending on the embodiment. For example, the mobile object information O20A (second object information O20) may further include information (e.g., registered unique information, etc.) used to authenticate the mobile object (second object). The configuration of the attribute information may also be modified as appropriate. For example, the mobile object information O20A (attribute information) may further include information about the mobile object terminal, such as contact information for the mobile object terminal. When adopting a form that allows proxy for the second object, the second object information O20 may further include proxy authority information.

[0070] The data format of the second target information O20 (mobile object information O20A) is not particularly limited and may be appropriately selected depending on the embodiment. The second target information O20 (mobile object information O20A) may be held in any database platform. In one example, the second target information O20 (mobile object information O20A) may be held in a relational database such as a table format. In another example, the second target information O20 (mobile object information O20A) may be held in a blockchain platform.

[0071] (Authentication process) Authentication of the first target proxy requesting individual PR may be performed by any method (specific examples will be described later). Executing the authentication process includes determining whether the authentication is successful. The authentication process may be executed by any computer. In one example, the success or failure of authentication in response to the authentication request may be determined by the management server 1 or an external server (e.g., the first server 2, etc.). By executing the authentication process on the server side, it is expected that security can be ensured.

[0072] This authentication process may be executed at any timing before the correspondence is set. In one example, the authentication process of the proxy requesting individual PR may be executed as a trigger for sending a linking request before issuing the linking request. The linking request may be sent separately from the authentication request in response to the authentication of the proxy requesting individual PR being established in response to the authentication request. Including an authentication request in the linking request may include executing an authentication request as a pre-processing for issuing the linking request (the case of the 3-2 authentication method described later). In another example, the authentication process of the proxy requesting individual PR may be requested together with the linking request and executed together with the processing related to the linking setting (the case of the first authentication method described later, etc.). In yet another example, the authentication process of the proxy requesting individual PR may be started in response to a request from the management server 1 or an external server after the linking request is sent.

[0073] Depending on these, the management server 1 may acquire the authentication result together with the linking request or after the linking request. When authentication is successful, acquiring the authentication result in the management server 1 may include acquiring an authentication result indicating that authentication is successful, and acquiring indirect information such as a linking request in response to the authentication being successful (i.e., indirectly acquiring the authentication result). On the other hand, when authentication is not successful, acquiring the authentication result in the management server 1 may include acquiring an authentication result indicating that authentication is not successful, and the authentication result not reaching the management server 1 (the authentication result is not acquired).

[0074] The computer that executes the authentication process may be changed as appropriate depending on the embodiment. In addition, together with the authentication of the first target proxy request individual PR, authentication of at least one of the proxy individual PI of the first target and the target individual TA of the second target may be performed. The authentication process of the proxy individual PI may be performed in the same manner as the proxy request individual PR. When the authentication process of the proxy individual PI is performed, a correspondence relationship may be set in response to the authentication of the proxy individual PI together with the proxy request individual PR being established. In addition, like the first target, the authentication process of the second target may be performed by any computer. In one example, the success or failure of the authentication of the second target (target individual TA) may be determined by the management server 1 or an external server (e.g., the second server 3, etc.). When the authentication process of the second target target individual TA is performed, a correspondence relationship may be set in response to the authentication of the target individual TA together with the proxy request individual PR being established.

[0075] The order of the authentication process of the first target and the second target is not particularly limited and may be appropriately determined according to the embodiment. The authentication process of the first target may be executed at least partially in parallel with the authentication process of the second target. The authentication request of each target may include data (e.g., an identifier, unique information, a certificate, etc.) used for authenticating each target. When the authentication process of each target is executed by the management server 1 or an external server, acquiring the authentication result in the management server 1 may include acquiring the authentication result by executing the authentication process in the management server 1, or acquiring the authentication result from the external server. For example, the management server 1 may execute the authentication process in response to the received authentication request, or may request the external server to execute the authentication process by sending an authentication request to the external server. Also, for example, a terminal of at least one of the first target and the second target may send an authentication request to the external server. The external server may execute the authentication process in response to the received authentication request, or may request the management server 1 to execute the authentication process by sending an authentication request to the management server 1. When the authentication process is executed, the external server may transmit the authentication result directly to the management server 1, or may transmit the authentication result to the management server 1 via an external computer (for example, at least one of the terminals, etc.).

[0076] (Data Exchange) In this embodiment, a series of processes related to linking settings in the proxy route may be started with data exchange between the first terminal 4 and the second terminal 5 as a trigger. That is, when a utilization relationship occurs between the proxy individual PI and the target individual TA in response to a request from the proxy requesting individual PR, the first terminal 4 and the second terminal 5 may execute data exchange as appropriate. The occurrence of the utilization relationship (start of utilization) may be detected by this data exchange. According to one example of this embodiment, it can be expected that the occurrence of the utilization relationship can be easily detected by data exchange.

[0077] The method of data exchange is not particularly limited and may be appropriately selected depending on the embodiment. In one example, data exchange between the first terminal 4 and the second terminal 5 may be performed by wireless or wired data communication. Wireless communication may be performed by, for example, Near Field Communication (NFC), Bluetooth (registered trademark), Wi-fi (registered trademark), etc. Wired communication may be performed by, for example, a wired Local Area Network (LAN), Universal Serial Bus (USB), etc. Data Data communication may be performed directly between the first terminal 4 and the second terminal 5, or indirectly via another computer. In another example, data exchange may be performed by a method other than data communication, such as reading a two-dimensional code. For example, data exchange may be performed by one of the first terminal 4 and the second terminal 5 displaying data on a display and the other reading the displayed data using a sensor such as an image sensor.

[0078] FIG. 4 shows a schematic diagram of an example of data exchange according to this embodiment. In this example of this embodiment, the first terminal 4 of the representative individual PI may include a short-range wireless communication module 431. The second terminal 5 of the target individual TA may include a short-range wireless communication module 531. Accordingly, data exchange between the terminals may be performed by short-range wireless communication. Note that the type of each short-range wireless communication module (431, 531) is not particularly limited and may be appropriately selected according to the embodiment. The short-range wireless communication may be, for example, NFC, Bluetooth (registered trademark), Wi-fi (registered trademark), etc. (trademark), RFID (Radio-Frequency Identification), ZigBee (registered trademark), infrared transmission, etc. In one example of this embodiment, The occurrence of a usage relationship can be detected by using the data exchange between the representative individual PI and the target individual TA as a trigger. In addition, since it is possible to guarantee that the first terminal 4 and the second terminal 5 are present within a range where short-distance wireless communication is possible, it is expected that the occurrence of a usage relationship between the representative individual PI and the target individual TA can be properly detected.

[0079] The linking request may include at least one of the first identifier I10 of the proxy requesting individual PR and the second identifier I20 of the target individual TA. When the linking request includes the first identifier I10 of the proxy requesting individual PR, the first identifier I10 may be transmitted from at least one of the first terminal 4 and the second terminal 5. When the first identifier I10 is transmitted from the first terminal 4, the first terminal 4 may acquire the first identifier I10 at any timing. In one example, the first terminal 4 may be given the first identifier I10 of the proxy requesting individual PR from the terminal 6 or an external server (such as the first server 2) at the time of the proxy request, or may be held in advance by an address book or the like. Thereby, the first terminal 4 may store the first identifier I10 of the proxy requesting individual PR in the memory resource of the first terminal 4 in advance. The first terminal 4 may acquire the first identifier I10 of the proxy requesting individual PR from the memory resource. In another example, the first terminal 4 may acquire the first identifier I10 of the proxy request individual PR using an input device, a sensor, or the like. When the first identifier I10 of the proxy request individual PR is transmitted from the second terminal 5, the second terminal 5 may be given the first identifier I10 of the proxy request individual PR from the first terminal 4 during data exchange, or may acquire it by a spontaneous operation. In one example, the second terminal 5 may acquire the first identifier I10 from the first terminal 4 by data communication. In another example, the second terminal 5 may acquire the first identifier I10 of the proxy request individual PR from the first terminal 4 by a method other than data communication, such as reading the first identifier I10 displayed in a two-dimensional code on the first terminal 4. In another example, the second terminal 5 may acquire the first identifier I10 of the proxy request individual PR from either the first target (representative individual PI, proxy request individual PR) or the first terminal 4 using a device such as an input device or a sensor. Obtaining from the first object may include, when a human related to the second object exists (e.g., the second object is a human, the second object is operated by a human, etc.) and the first object is an object, obtaining by the human related to the second object operating a device on its behalf. In yet another example, the second terminal 5 may obtain the first identifier I10 of the proxy requesting individual PR from the terminal 6 or an external server (such as the first server 2).

[0080] When the linking request includes the second identifier I20, the second identifier I20 may be transmitted from at least one of the first terminal 4 and the second terminal 5. When the second identifier I20 is transmitted from the second terminal 5, the second terminal 5 may acquire the second identifier I20 at any timing. In one example, the second identifier I20 may be stored in advance in a memory resource of the second terminal 5. The second terminal 5 may acquire the second identifier I20 from the memory resource. In another example, the second terminal 5 may acquire the second identifier I20 using an input device, a sensor, or the like. When the second identifier I20 is transmitted from the first terminal 4, the first terminal 4 may receive the second identifier I20 from the second terminal 5 during data exchange, or may acquire the second identifier I20 by a spontaneous operation. In one example, the first terminal 4 may acquire the second identifier I20 from the second terminal 5 through data communication. In another example, the first terminal 4 may acquire the second identifier I20 from the second terminal 5 by a method other than data communication, such as reading the second identifier I20 displayed as a two-dimensional code on the second terminal 5. In yet another example, the first terminal 4 may acquire the second identifier I20 from either the second object or the second terminal 5 by using a device such as an input device or a sensor. Acquiring from the second object may include acquiring the second identifier I20 by the human associated with the first object operating a device on behalf of the human associated with the first object when there is a human associated with the first object (for example, the first object is a human, the first object is operated by a human, etc.) and the second object is an object.

[0081] The linking request may also include a first identifier I10 of the representative individual PI. , when the first identifier I10 of the surrogate individual PI is included, the first identifier I10 of the surrogate individual PI may be transmitted from at least one of the first terminal 4 and the second terminal 5. When the first identifier I10 of the surrogate individual PI is transmitted from the first terminal 4, the first terminal 4 may acquire the first identifier I10 at any timing. In one example, the first identifier I10 of the surrogate individual PI may be stored in advance in the memory resource of the first terminal 4. The first terminal 4 may acquire the first identifier I10 of the surrogate individual PI from the memory resource. In another example, the first terminal 4 may acquire the first identifier I10 of the surrogate individual PI using an input device, a sensor, or the like. When the first identifier I10 of the surrogate individual PI is transmitted from the second terminal 5, the second terminal 5 may receive the first identifier I10 of the surrogate individual PI from the first terminal 4 during data exchange, or may acquire it by a spontaneous operation. In one example, the second terminal 5 may acquire the first identifier I10 of the surrogate individual PI from the first terminal 4 by data communication. In another example, the second terminal 5 may acquire the first identifier I10 of the surrogate individual PI by a method other than data communication, such as reading the first identifier I10 displayed as a two-dimensional code on the first terminal 4. In yet another example, the second terminal 5 may acquire the first identifier I10 of the surrogate individual PI from either the first object (surrogate individual PI) or the first terminal 4, using a device such as an input device or a sensor.

[0082] For example, in the example of FIG. 2, the first terminal 4 may obtain the second identifier I20 (mobile identifier) ​​from the second terminal 5 by data communication or reading a code. If the second identifier I20 is a vehicle registration number, the first terminal 4 may obtain the second identifier I20 by photographing the license plate with an image sensor and analyzing the obtained image. The first terminal 4 may obtain the second identifier I20 via an input device. The second terminal 5 may obtain the second identifier I20 as appropriate. Also, the second terminal 5 may obtain the first identifier I10 (user identifier) ​​by data communication or reading a code. If the first identifier I10 is a personal number or the like written on a card, the second terminal 5 may obtain the first identifier I10 by photographing the card with an image sensor and analyzing the obtained image. The second terminal 5 may obtain the first identifier I10 via an input device. The first terminal 4 may obtain the first identifier I10 as appropriate.

[0083] When an input device is used to acquire data such as each identifier (I10, I20), one terminal acquiring data from another target may include one target acquiring data of the other target by operating an input device, in addition to the other target acquiring data of the other target by operating an input device. For example, in the example of FIG. 2 above, when the second identifier I20 is a vehicle registration number and an input device is used to acquire the vehicle registration number, the first terminal 4 may acquire the second identifier I20 from the mobile object (second target) by the user (first target) inputting the vehicle registration number via the input device.

[0084] Note that the acquisition of data of the other target by one terminal does not necessarily have to be performed at the time of data exchange. One terminal may acquire data of the other target at any timing different from the data exchange. Any of the above methods may be adopted as the data acquisition method. In this case, the data exchange between the first terminal 4 and the second terminal 5 may function simply as a trigger for starting a series of processes related to the linking setting.

[0085] (Verification process) The verification method of the power of attorney may be appropriately selected according to the embodiment. The configuration of the authority verification information AU may be appropriately determined according to the verification method. In this embodiment, the verification of the power of attorney may be performed by at least one of the following two methods.

[0086] (1) First Method FIG. 5A is a schematic diagram showing an example of the process of the verification process of the power of attorney according to the first method. In the first method, the authority verification information AU may include a contact AU1 that performs the approval process. Accordingly, verifying the power of attorney may be configured by making an inquiry to the contact AU1 included in the authority verification information AU (step S301), and receiving an approval response as a result of execution of the approval process (step S302).

[0087] The authorization process for the power of attorney may be performed automatically by computer processing, or may be performed manually by at least partially involving user operation. The contents of the authorization process may be designed appropriately according to the embodiment. In a simple example, the inquiry may include an approval button, and the approval process may be to operate the approval button included in the inquiry. Furthermore, as long as the inquiry can be notified to the computer that executes the approval process, the contact AU1 is not particularly limited and may be selected appropriately according to the embodiment.

[0088] 5A, the contact AU1 is a contact of the terminal 6. In one example, the approval process may be executed in the terminal 6. In this case, the contact AU1 (the contact of the terminal 6) may be, for example, a telephone number, an email address, account information of a contact application (for example, a Social Networking Service application, etc.), an identification number, etc. However, the computer that executes the authorization process may not be limited to the terminal 6. In another example, the authorization process may be executed by an external computer such as the first server 2. In this case, the contact AU1 may be, for example, an address of the external computer such as a Uniform Resource Locator (URL). The address may be a one-time address. The contact AU1 may be appropriately transmitted to the second terminal 5. In one example, the authorization information AG may include the authorization verification information AU (contact AU1). In the data exchange, the first terminal 4 may provide the contact AU1 included in the authorization information AG to the second terminal 5.

[0089] When the approval process is automatically executed by the terminal 6 or the external computer, the authenticity of the power of attorney may be verified by any method in the approval process. In one example, the authenticity of the power of attorney may be verified by authenticating the proxy individual PI. For example, in response to the designation of the proxy individual PI by the terminal 6, the terminal 6 or the external computer may hold information of the proxy individual PI (the first identifier I10, data used for authentication, etc.) in advance. The second terminal 5 may acquire information of the proxy individual PI from the proxy individual PI or the first terminal 4, and notify the terminal 6 or the external computer of an inquiry including the acquired information. The information of the proxy individual PI may include authentication information for authenticating the proxy individual PI. The authentication information may be appropriately selected depending on the embodiment. In one example, the authentication information may include unique information. The unique information may include, for example, information derived from the subject (individual), information derived from the terminal, information generated temporarily, information generated by any other method, etc. The information derived from the subject may be, for example, biometric information, uniquely assigned identification information, etc. The biometric information may be, for example, a face image, a fingerprint, a voiceprint, etc. The temporarily generated information may be composed of, for example, a timestamp, a random number, a hash value, etc. The terminal 6 or the external computer may verify the authenticity of the agency by comparing the designated information of the proxy individual PI held in advance with the acquired information of the proxy individual PI notified from the second terminal 5. In response to the information matching being established, the terminal 6 or the external computer may return a response indicating approval to the second terminal 5. On the other hand, if the information matching is not established, the terminal 6 or the external computer may return a response indicating non-approval to the second terminal 5 and prompt the second terminal 5 to re-acquire the information of the proxy individual PI.

[0090] 5A, if there is no response from terminal 6 within a certain period of time after notifying terminal 6 of the inquiry (approval request) in step S301, second terminal 5 may notify terminal 6 of a reminder to prompt the response in step S302. If there is no response within the certain period of time, second terminal 5 may make an inquiry to the external computer instead of the reminder, thereby causing the external computer to execute an alternative approval process. If there is no response after the reminder, second terminal 5 may cause the external computer to execute an alternative approval.

[0091] Furthermore, when the first method is adopted, at least one of the first terminal 4 and the second terminal 5 may acquire data used to authenticate the proxy requesting individual PR (e.g., the first identifier I10, unique information, a certificate, etc.) at any timing. In one example, in step S302, the terminal 6 or the external computer may provide the data used to authenticate the proxy requesting individual PR to the second terminal 5 together with a response indicating approval. However, the transmission path of the data used to authenticate the proxy requesting individual PR is not limited to this example, and may be selected appropriately depending on the embodiment. In another example, the terminal 6 or the external computer may provide the data used to authenticate the proxy requesting individual PR to the first terminal 4.

[0092] Furthermore, basically, the data exchange in steps S301 and S302 may be performed by direct or indirect data communication using a wireless or wired connection. However, the data exchange between the second terminal 5 and the computer of the contact AU1 (terminal 6, external computer) is not limited to this example, and may be appropriately selected according to the embodiment. In some cases, a method other than data communication, such as reading a two-dimensional code, may be used for the data exchange between the second terminal 5 and the computer of the contact AU1.

[0093] Furthermore, the second terminal 5 may acquire information for confirming the surrogate individual PI from the first terminal 4 or the surrogate individual PI, and may notify the terminal 6 of the acquired information when making an inquiry for approval. The terminal 6 may prompt the confirmation of the surrogate individual PI by outputting (for example, displaying on a display) information on the surrogate individual PI together with the inquiry for approval. In one example, the information for confirming the surrogate individual PI may be a first identifier I10 of the surrogate individual PI, etc. Furthermore, when the first subject is a user, the information for confirming the surrogate individual PI may include, for example, information used for authentication such as a face image of the surrogate individual PI (surrogate user). In the first terminal 4 and the second terminal 5, this information may be acquired to authenticate the surrogate individual PI when making a linking request. That is, data acquired for authenticating the surrogate individual PI may also be used to confirm the surrogate individual PI in the approval process. This is expected to improve the efficiency of data acquisition.

[0094] (2) Second Method FIG. 5B shows a schematic diagram of an example of the process of the verification process of the agency authority by the second method. In the second method, the second terminal 5 may be further configured to receive notification of authentication information PC1 from the terminal 6 of the agency requesting individual PR (step S100). The authority verification information AU may include the agency authentication information AU2 corresponding to the authentication information PC1. Verifying the agency authority may be configured by comparing the agency authentication information AU2 included in the authority verification information AU with the authentication information PC1 notified from the terminal 6 of the agency requesting individual PR (step S305).

[0095] The authentication information PC1 may be the same as the authentication information of the proxy individual PI in the first method. In one example, the authentication information PC1 may be composed of temporarily generated information. The authentication information PC1 may include unique information of the proxy individual PI. The proxy authentication information AU2 corresponds to the authentication information PC1. In one example, the authentication information PC1 held in the terminal 6 or an external computer (such as the first server 2) may be transmitted to the first terminal 4 together with the authorization information AG, and the authentication information PC1 transmitted to the first terminal 4 may be used as the proxy authentication information AU2. That is, the authorization information AG may include the authentication information PC1 as the authority verification information AU (proxy authentication information AU2), and in the data exchange, the first terminal 4 may provide the proxy authentication information AU2 included in the authorization information AG to the second terminal 5. In another example, the authentication information PC1 may be registered in advance, and the proxy authentication information AU2 may be acquired corresponding to the authentication information PC1 when verifying the proxy authority. The authentication information PC1 may be held in the first target information O10. For example, when the first object is a user, the authentication information PC1 may be a registered face image, and the proxy authentication information AU2 may be a face image acquired when the proxy authority is verified. That is, the authority verification information AU (proxy authentication information AU2) may be acquired when the proxy authority is verified.

[0096] The second terminal 5 may receive the authentication information PC1 directly or indirectly. The second terminal 5 may obtain the authentication information PC1 at any timing before executing the verification process of the proxy authority. In addition, the target individual TA of the second target may be designated by the proxy request individual PR or may be selected by the proxy individual PI.

[0097] In one example, the terminal 6 may include a short-range wireless communication module and may exchange data with the second terminal 5 by close proximity wireless communication. The second terminal 5 individual with which this data exchange is to be performed may be designated as the target individual TA. The second terminal 5 may receive authentication information PC1 during this data exchange. The data exchange may be performed by wireless or wired data communication other than short-range wireless communication, or may be performed by a method other than data communication, such as reading a two-dimensional code.

[0098] In another example, the terminal 6 may access a list of second targets when setting up a proxy, and designate an individual (target individual TA) to be permitted to be linked to a proxy from among the individuals registered in the list. The list may include information such as identification information of each individual of the second targets and contact information of the terminal (second terminal 5). The list may be stored in the terminal 6 or an external computer (e.g., the second server 3). The designation of the target individual TA may be performed automatically by computer processing, or may be performed manually by at least partially including a user operation. After the target individual TA is designated, the terminal 6 may notify the terminal (second terminal 5) of the designated target individual TA of the authentication information PC1. In response to this, the second terminal 5 may receive the authentication information PC1.

[0099] In yet another example, the target individual TA may be specified by the proxy individual PI, not by the proxy request individual PR. For example, the proxy request individual PR may specify the second target within an arbitrary range, such as belonging to a specific management organization, and the proxy individual PI may select the target individual TA from within that range. As an example of this case, data such as the authentication information PC1 may be held in an external computer such as the first server 2. When the second terminal 5 starts data exchange with the first terminal 4, the second terminal 5 may access the external computer and download data such as the authentication information PC1 as the process of step S100. The data to be downloaded may be selected appropriately. For example, in the external computer, data such as the authentication information PC1 may be held in association with at least one of the proxy request individual PR and the proxy individual PI. The second terminal 5 may accept the designation of at least one of the proxy request individual PR and the proxy individual PI by an operation by the proxy individual PI, data from the first terminal 4 (such as the first identifier I10), etc., and may download data corresponding to the designated individual. After downloading the data, the second terminal 5 may accept a use application from the proxy individual PI and execute a verification process in step S305. Note that even when the target individual TA is specified by the proxy request individual PR, the second terminal 5 may download data such as authentication information PC1 when the proxy individual PI uses it. For example, when the validity start time of the proxy right is specified in advance by the proxy request individual PR, the second terminal 5 may download data such as authentication information PC1 in response to the arrival of the validity start time.

[0100] The method of matching the authentication information PC1 and the proxy authentication information AU2 may be appropriately determined according to the information adopted as each piece of information (PC1, AU2). In one example, the second terminal 5 may determine whether the matching is successful or not according to the degree of agreement between the authentication information PC1 and the proxy authentication information AU2. In another example, the second terminal 5 may determine whether the matching is successful or not according to whether a correspondence relationship is established between the authentication information PC1 and the proxy authentication information AU2. As a specific example, a predetermined calculation process (hashing, etc.) may be applied to at least one of the authentication information PC1 and the proxy authentication information AU2 in a computer on the transmission path. For example, the proxy authentication information AU2 may be generated by hashing the authentication information PC1. The predetermined calculation process may be executed in at least one of the terminal 6, the first terminal 4, the second terminal 5, and an external computer (e.g., the first server 2, etc.). In response to this, the second terminal 5 may determine whether the matching is successful or not depending on whether a corresponding relationship defined by a predetermined arithmetic process is established between the authentication information PC1 and the proxy authentication information AU2. For example, the second terminal 5 may hash the authentication information PC1 and determine whether the matching is successful or not depending on whether the obtained hash value matches the proxy authentication information AU2. The matching process may be executed by an external computer such as the first server 2, and the second terminal 5 may obtain the result of the matching from the external computer. Indirectly receiving the authentication information PC1 may include receiving the result of the matching executed by this external computer. If the matching is successful (i.e., the verification of the proxy authority is successful), the first terminal 4 and the second terminal 5 may proceed to processing related to the linking request. On the other hand, if the matching is not successful, the second terminal 5 may not permit the proxy linking process and may urge the first terminal 4 to resend the proxy authentication information AU2.

[0101] At least one of the first terminal 4 and the second terminal 5 may acquire data used for authenticating the proxy requesting individual PR (e.g., the first identifier I10, unique information, a certificate, etc.) at any timing. In one example, in step S100, the second terminal 5 may acquire data used for authenticating the proxy requesting individual PR together with the authentication information PC1 from the terminal 6 or an external computer. However, the transmission path of the data used for authenticating the proxy requesting individual PR is not limited to such an example and may be appropriately selected depending on the embodiment. In another example, the first terminal 4 may acquire data used for authenticating the proxy requesting individual PR together with the authorization information AG. The method of acquiring data used for authentication is not particularly limited and may be appropriately selected depending on the embodiment. In one example, the data used for authentication may be acquired by any device such as an input device or a sensor. The data used for authentication may be received from a device already held.

[0102] According to at least one of the first method and the second method, proper verification of the power of attorney can be expected. When the first method or the second method is adopted, the authority verification information AU may include a contact AU1 for performing the approval process or a proxy authentication information AU2 used for verification.

[0103] (Notification processing) In one example, when at least one of the processes of setting and canceling the association is executed, the management server 1 may transmit a notification indicating the execution result to at least one of the first terminal 4 and the second terminal 5. The transmission path of the notification is not particularly limited and may be determined appropriately according to the embodiment. The management server 1 may directly notify at least one of the first terminal 4 and the second terminal 5. Alternatively, the management server 1 may indirectly notify at least one of the first terminal 4 and the second terminal 5 via an external computer such as each server (2, 3).

[0104] In addition, when notifying directly, the management server 1 may appropriately acquire contact information of each terminal (4, 5). The contact information may be a telephone number, an email address, account information for a communication application (for example, a Social Networking Service application), an identification number, etc. The management server 1 may acquire information indicating contact information for each terminal (4, 5) at any timing. In one example, the management server 1 may acquire information indicating contact information at the timing of receiving a request such as a linking request or a release request. The information indicating contact information may be transmitted from at least one of each terminal (4, 5) and each server (2, 3).

[0105] Also, in one example, when a correspondence relationship between the proxy requesting individual PR and the target individual TA is set by the proxy individual PI, the management server 1 may transmit a notification to the terminal 6 of the proxy requesting individual PR to inform the terminal 6 of the correspondence relationship being set. The management server 1 may transmit this notification directly or indirectly to the terminal 6. When transmitting the notification directly, the management server 1 may acquire the contact information of the terminal 6 at any timing. In one example, when adopting a form in which the contact information of the terminal 6 is used as the contact information AU1 in the first method described above, at least one of the first terminal 4 and the second terminal 5 may , the contact information AU1 may be transmitted to the management server 1 together with the linking request. In another example, the management server 1 may appropriately acquire the contact information of the terminal 6 from an external computer such as the first server 2. In yet another example, in a case where the management server 1 and the terminal 6 perform data communication, the management server 1 may acquire the contact information of the terminal 6 in this data communication. Similarly, when the correspondence is released, the management server 1 may transmit a notification to the terminal 6 of the proxy requesting individual PR to inform it of the release of the correspondence.

[0106] (Unlink) In this embodiment, the management server 1 may cancel the correspondence relationship upon receipt of a cancellation request from at least one of the first terminal 4 and the second terminal 5 or upon establishment of a predetermined cancellation condition. In addition, the management server 1 may cancel the correspondence relationship due to a factor related to the proxy requesting individual PR.

[0107] (I) Request for cancellation In one example, the release request may be configured to indicate the correspondence relationship to be released by including at least one of the first identifier I10 of the proxy requesting individual PR and the second identifier I20 of the target individual TA. When the linking information D10 includes the first identifier I10 of the proxy individual PI as agency information, the release request may be configured to indicate the correspondence relationship to be released by including the first identifier I10 of the proxy individual PI. In another example, the release request may be configured to indicate the correspondence relationship to be released by including substitution information.

[0108] When the first terminal 4 transmits a release request including the second identifier I20, the first terminal 4 may acquire the second identifier I20 at any timing. In one example, when making a linking request, the first terminal 4 may acquire the second identifier I20 and store the acquired second identifier I20 in the memory resource. When making a release request, the first terminal 4 may acquire the second identifier I20 from the memory resource. Also, when the first terminal 4 transmits a release request including the first identifier I10 of the proxy requesting individual PR, the first terminal 4 may acquire the first identifier I10 of the proxy requesting individual PR at any timing. In one example, the first terminal 4 may acquire the first identifier I10 of the proxy requesting individual PR together with the authorization information AG and store the acquired first identifier I10 in the memory resource. When making a release request, the first terminal 4 may acquire the first identifier I10 of the proxy requesting individual PR from the memory resource. When a relationship is established in advance between the proxy individual PI and the proxy request individual PR, the first identifier I10 of the proxy request individual PR may be stored in advance in the memory resource. In addition, when the first terminal 4 transmits a release request including the first identifier I10 of the proxy individual PI, the first terminal 4 may acquire the first identifier I10 of the proxy individual PI at any timing. In one example, the first identifier I10 of the proxy individual PI may be stored in advance in the memory resource. The first terminal 4 may acquire the first identifier I10 of the proxy individual PI from the memory resource.

[0109] Similarly, when the second terminal 5 transmits a release request including the first identifier I10 of the proxy request individual PR, the second terminal 5 may acquire the first identifier I10 of the proxy request individual PR at any timing. In one example, when requesting verification or linking of the proxy right, the second terminal 5 may acquire the first identifier I10 of the proxy request individual PR, and may store the acquired first identifier I10 in the memory resource. In the release request, the second terminal 5 may acquire the first identifier I10 of the proxy request individual PR from the memory resource. When the second terminal 5 transmits an authentication request including the first identifier I10 of the proxy individual PI, the second terminal 5 may acquire the first identifier I10 of the proxy individual PI in a similar manner to the first identifier I10 of the proxy request individual PR. In addition, when the second terminal 5 transmits a release request including the second identifier I20, the second terminal 5 may acquire the second identifier I20 at any timing. In one example, the second identifier I20 may be stored in advance in the memory resource. The second terminal 5 may obtain the second identifier I20 from a memory resource.

[0110] FIG. 6 is a schematic diagram showing an example of a process of untying according to the present embodiment. In the example of FIG. 6, as a first route, the first terminal 4 directly transmits an unbinding request to the management server 1 (step SZ10). As a second route, the first terminal 4 gives an instruction to the second terminal 5 (step SZ10A) to cause the second terminal 5 to directly transmit an unbinding request to the management server 1 (step SZ11A). However, the transmission route of the unbinding request is not limited to this example. The first terminal 4 may indirectly transmit the unbinding request to the management server 1 via an external computer such as the first server 2. In the second route, the second terminal 5 may indirectly transmit the unbinding request to the management server 1 via an external computer such as the second server 3. Note that the origin of the unbinding request is not limited to the first terminal 4. In another example, the second terminal 5 may directly or indirectly transmit the unbinding request to the management server 1. Furthermore, the second terminal 5 may give an instruction to the first terminal 4 to cause the first terminal 4 to directly or indirectly send a release request to the management server 1. After receiving the release request, the management server 1 refers to the linking information D10 and releases the correspondence specified by the identifier included in the release request. After this release process, the management server 1 may transmit a notification indicating the result of the release process to at least one of the first terminal 4 and the second terminal 5, as in the case of setting the link. Furthermore, the management server 1 may transmit a notification to the terminal 6 of the proxy requesting individual PR to inform it that the correspondence has been released.

[0111] In one example, the process of the release request may include an authentication process of at least one of the first target and the second target. The authentication process at the time of release may be similar to the authentication process at the time of the above-mentioned binding setting. However, the authentication process may not necessarily be executed at the time of the release request. In another example, the process of the release request may be simplified by omitting the authentication process.

[0112] The trigger of the release request may be set appropriately depending on the embodiment. In one example, when at least one of the first target and the second target is a user, the release request may be transmitted from at least one of the first terminal 4 and the second terminal 5 by the operation of at least one of the first terminal 4 and the second terminal 5 by the user (including the proxy user). That is, the trigger of the release request may be an operation by the user. In another example, with the end of the usage relationship, at least one of the first terminal 4 and the second terminal 5 may execute an arbitrary information processing. The execution of this information processing may be used as a trigger to transmit a release request from at least one of the first terminal 4 and the second terminal 5. For example, the arbitrary information processing may be data exchange between the first terminal 4 and the second terminal 5. The method of data exchange when releasing the association may be the same as the data exchange when setting the association. A distinction may be made as to whether the data exchange is when setting the association or when releasing the association. For example, in the example of FIG. 2, the second terminal 5 may be provided with separate sensor devices at the entrance and exit, such as a bus entrance or exit, a train ticket gate, etc. In this case, a distinction may be made between data exchange at the time of linking setup and data exchange at the time of linking release depending on the sensor device used for data exchange. Also, for example, when data exchange is executed by an application of the terminal, the application may be configured to be switchable between a linking setup mode and a linking release mode. In this case, a distinction may be made between data exchange at the time of linking setup and data exchange at the time of linking release depending on the mode of the application.

[0113] (II) Termination Conditions The cancellation condition indicates a condition for canceling the correspondence relationship of the target, and may be defined as appropriate depending on the embodiment.

[0114] In one example, the release condition may be defined so that the correspondence relationship is released at an arbitrarily set release time. The release time may be given, for example, by a user or another application (such as a scheduler). In this case, the management server 1 may release the target correspondence relationship upon arrival of the release time. The release time may be set as the expiration date of the association information D10. If the release time is set as the expiration date, the management server 1 may treat the target correspondence relationship as having been released upon arrival of the release time.

[0115] In another example, the number of correspondences that can be set for the same individual of each target may be infinite or finite. When the number of correspondences that can be set is finite, an upper limit (threshold) may be set for the number of correspondences that can be set for the same individual. The threshold may be given as appropriate. When the number of correspondences set for at least one of the first target and the second target exceeds this upper limit, the management server 1 may cancel at least one of the correspondences set for the corresponding individual. Which correspondences to cancel may be determined as appropriate according to the priority, order, type of target, etc. The management server 1 may send an inquiry regarding the cancellation to at least one of the first terminal 4 and the second terminal 5, and determine the correspondences to be canceled according to the response obtained.

[0116] For example, as in the example of FIG. 2, a scene is assumed in which the first object is a user and the second object is a use. In this case, the number of users that can be linked to the same use may be infinite or finite. When the number of users that can be linked is finite, the upper limit of the number of users that can be linked may be appropriately given by a threshold value. The threshold value may be set according to the attribute of the use (e.g., the possible number of passengers). When the management server 1 newly accepts the setting of a correspondence relationship for the relevant individual of the use, it may refer to the linking information D10 and extract the previous correspondence relationship that has been set and maintained for the relevant individual of the use. When the newly accepted setting of the correspondence relationship causes the overlap of the setting of the correspondence relationship for the relevant individual of the use to exceed the threshold value, the management server 1 may discard the request for the newly accepted setting of the correspondence relationship or cancel at least one of the extracted previous correspondence relationships. When canceling the previous correspondence relationship, the management server 1 may determine the correspondence relationship to be canceled according to the priority and order of the users (e.g., the earlier the correspondence relationship is set, the more it is canceled).

[0117] As a specific example, in the example of FIG. 2, it is assumed that the moving object is a private car, and that the first user and the second user are, for example, family members, and thus share the target private car. The private car may be interpreted as a constantly used object. For ease of explanation, it is assumed that the number of users that can be linked to the target private car is one. In this case, while a correspondence relationship between one of the first user and the second user and the target private car has been set, in response to receiving the setting of a correspondence relationship between the other user and the target private car, the management server 1 may cancel the previous correspondence relationship (the correspondence relationship between one of the first user and the target private car).

[0118] The same may be true for users. That is, the number of objects that can be linked to the same user may be infinite or finite. When the number of objects that can be linked is finite and the number of correspondence relationships set for the user exceeds the upper limit, the management server 1 may discard a newly received request for setting a correspondence relationship, or cancel at least one of the previous correspondence relationships extracted. When canceling a previous correspondence relationship, the management server 1 may determine the correspondence relationship to be canceled according to the priority and type of the object (for example, whether it is a permanent object or a temporary object), etc.

[0119] (III) Cancellation by proxy requester In the case of a proxy, the correspondence between the proxy request individual PR and the target individual TA set by the proxy individual PI may be released by the proxy request individual PR. The method of releasing by the proxy request individual PR may be designed appropriately according to the embodiment. In this embodiment, at least one of the following two methods may be adopted.

[0120] (III-1) Request for release from the proxy requester FIG. 7A shows an example of a process (first release method) of releasing a link by the proxy requesting individual PR. In the first release method, the management server 1 may receive a release request from the terminal 6 of the proxy requesting individual PR. As a result, the management server 1 is further configured to release the correspondence between the proxy requesting individual PR and the target individual TA in response to receiving the release request from the terminal 6. good.

[0121] Similar to the release request from at least one of the first terminal 4 and the second terminal 5, the release request from the terminal 6 may be configured to indicate the correspondence relationship to be released by including at least one of the first identifier I10 of the proxy requesting individual PR, the first identifier I10 of the proxy individual PI, and the second identifier I20 of the target individual TA. The release request from the terminal 6 may be configured to indicate the correspondence relationship to be released by including substitution information.

[0122] The transmission path of the release request may be appropriately selected according to the embodiment. In the example of FIG. 7A, the terminal 6 directly transmits the release request to the management server 1 (step SZ20). The transmission path of the release request may not be limited to this example. The terminal 6 may indirectly transmit the release request to the management server 1 via the first server 2, the first terminal 4, the second terminal 5, etc. The terminal 6 may give an instruction to at least one of the first terminal 4 and the second terminal 5 to cause at least one of the first terminal 4 and the second terminal 5 to directly or indirectly transmit the release request to the management server 1. Other configurations of the release request from the terminal 6 may be similar to the release request from at least one of the first terminal 4 and the second terminal 5 described above.

[0123] (III-2) Setting new correspondence relationships by proxy requesting individuals 7B shows a schematic example of a process (second release method) of releasing the link by the proxy requesting individual PR. In the second release method, the management server 1 may be further configured to release the correspondence relationship between the proxy requesting individual PR and the target individual TA in response to the proxy requesting individual PR setting a correspondence relationship between the proxy requesting individual PR and another individual TO of the second target. In other words, the management server 1 may release the correspondence relationship with the target individual TA previously set by the proxy requesting individual PR in response to the new correspondence relationship being set by the proxy requesting individual PR.

[0124] The correspondence between the proxy requesting individual PR and the other individual TO of the second target may be set by processing the normal route described above. In one example, in response to the occurrence of a usage relationship between the proxy requesting individual PR and the other individual TO of the second target, data exchange may be performed between the terminal 6 of the proxy requesting individual PR and the terminal 5_1 of the other individual TO of the second target. At least one of the terminal 6 of the proxy requesting individual PR and the terminal 5_1 of the second target may transmit a linking request to the management server 1. In response to the linking request, the management server 1 may set the correspondence between the proxy requesting individual PR and the other individual TO of the second target.

[0125] By setting a new correspondence relationship with the other individual TO, the proxy requesting individual PR becomes able to exercise authority via the other individual TO. In order to prevent the exercise of authority via the other individual TO and the exercise of authority via the target individual TA from coexisting, the management server 1 may cancel the correspondence relationship with the target individual TA that was previously set when this new correspondence relationship is set. In another example, the management server 1 may maintain both the correspondence relationship with the other individual TO and the correspondence relationship between the proxy individual PI and the target individual TA, thereby allowing the exercise of authority via the other individual TO and the exercise of authority via the target individual TA to coexist.

[0126] As described above, the management server 1 may cancel the correspondence relationship upon receiving a cancellation request from at least one of the first terminal 4 and the second terminal 5 or upon the establishment of a predetermined cancellation condition. The management server 1 may also cancel the correspondence relationship due to a factor related to the proxy requesting individual PR. This makes it possible to track the disappearance of the usage relationship between the first object and the second object. Note that the linking information D10 after the correspondence relationship has been cancelled may be saved as history.

[0127] (Confirmation of continued use) As one of the optional configurations, after setting the correspondence relationship between the first and second target individuals, the management server 1 checks whether the usage relationship between the target individuals continues. When a correspondence relationship is set by the proxy route, the management server 1 may further execute a process (confirmation process) to confirm the continuation of the usage relationship between the proxy individual PI and the target individual TA. The method of confirming the continuation of usage may be appropriately selected depending on the embodiment. In this embodiment, at least one of the following three methods may be adopted as the method of confirming the usage relationship.

[0128] (i-1) Verification process by authentication In one example, the management server 1 may confirm the continuation of the usage relationship by authenticating at least one of the first target (representative individual PI) and the second target (target individual TA) via at least one of the first terminal 4 and the second terminal 5. The authentication method may be any method, similar to the linking setting, etc. In the example of FIG. 2, for example, the user may be authenticated by a method such as performing face authentication of the user using an image sensor provided on the mobile object, performing fingerprint authentication of the user using a fingerprint reader attached to the steering wheel, having the user speak and performing voiceprint authentication using a microphone provided on the mobile object, etc. The authentication process may be executed by at least one of the terminals (4, 5), the servers (2, 3), and the management server 1. When the authentication process is executed by the servers (2, 3), data used for authentication may be directly transmitted from the terminals (4, 5) to the servers (2, 3), or may be indirectly transmitted via an external computer such as the management server 1. When the management server 1 executes the authentication process, data used for authentication may be sent directly from the terminals (4, 5) to the management server 1, or may be sent indirectly via an external computer such as each server (2, 3). The management server 1 may acquire the authentication result as appropriate, and may determine that the usage relationship continues if the target authentication is established in the acquired authentication result, and may determine that the usage relationship does not continue if the authentication is not established.

[0129] (i-2) Confirmation process by notification In another example, when at least one of the first target and the second target is a user (for example, the case of FIG. 2), the management server 1 may directly or indirectly send a confirmation notification including an operator to at least one of the first terminal 4 and the second terminal 5. The operator may be configured to include, for example, a confirmation button, a reply button, a link, etc. The destination of the confirmation notification does not necessarily correspond to the user. In the case of FIG. 2, the management server 1 may send a confirmation notification to at least one of the first terminal 4 and the second terminal 5. The destination of the confirmation notification may overlap with or be different from the destination of the notification indicating the result of the processing related to the association. The confirmation notification may be configured to directly or indirectly return a response to the management server 1 in response to the operation of the operator by the user. When the management server 1 receives a response to the operation of the operator within a predetermined period, it may determine that the usage relationship continues, and when it does not receive a response, it may determine that the usage relationship does not continue.

[0130] (i-3) Verification process using location information FIG. 8 illustrates an example of a process for confirming continued use according to this embodiment. When tracking a usage relationship in the real world, the first terminal 4 may include a positioning module 47. The first terminal 4 may be further configured to measure the current location of the first terminal 4 using the positioning module 47 of the first terminal 4 and transmit the measurement result of the current location of the first terminal 4 to the management server 1. The second terminal 5 may include a positioning module 57. The second terminal 5 may be further configured to measure the current location of the second terminal 5 using the positioning module 57 of the second terminal 5 and transmit the measurement result of the current location of the second terminal 5 to the management server 1.

[0131] In response to this, the management server 1 sets the correspondence relationship between the proxy request individual PR and the target individual TA, and then receives the measurement results of the current positions (RP10, RP20) of each terminal (4, 5) from each terminal (4, 5), determines in real time whether the measurement results of the current positions (RP10, RP20) of each terminal (4, 5) received satisfy the conditions of the usage relationship, and if the measurement results of the current positions (RP10, RP20) of each terminal (4, 5) satisfy the conditions of the usage relationship, The method may be further configured to determine that the utilization relationship between I and the target individual TA is continuing, and if not, to determine that the utilization relationship is not continuing.

[0132] The condition of the usage relationship may be set appropriately according to the embodiment, such as, for example, being close enough that the users are riding on a moving object. In one example, the condition of the usage relationship may be specified by a range DR of distance based on the current position RP10 of the first terminal 4 or the current position RP20 of the second terminal 5. In this case, whether or not the condition of the usage relationship is satisfied may be determined depending on whether or not it is within the range DR. FIG. 8 assumes a scene in which the current position RP10 of the first terminal 4 is used as a reference. In this scene, it may be determined that the condition of the usage relationship is satisfied because the current position RP20 of the second terminal 5 is within the range DR. On the other hand, it may be determined that the condition of the usage relationship is not satisfied because the current position RP20 of the second terminal 5 is outside the range DR.

[0133] The range DR may be appropriately set so as to be able to determine the second object with which the usage relationship occurs. The shape of the range DR may be arbitrarily defined. The range DR may be defined so that the distances in each direction are the same, or may be defined so that the distances differ in at least some directions.

[0134] The type of each positioning module (47, 57) is not particularly limited and may be appropriately selected depending on the embodiment. Each positioning module (47, 57) may be, for example, a GPS (Global Positioning Satellite) module, a GNSS (Global Navigation Satellite System) module, etc.

[0135] The current positions (RP10, RP20) of the terminals (4, 5) may be transmitted to the management server 1 at any timing before the confirmation process is executed. In one example, the terminals (4, 5) may report information on their current positions to the management server 1 as spontaneous information processing such as periodic transmission. In this case, the management server 1 may use the current positions most recently reported from the terminals (4, 5) as the current positions (RP10, RP20) to determine whether or not the conditions of the usage relationship are satisfied. In another example, the management server 1 may directly or indirectly transmit a request to the terminals (4, 5) at any timing before the confirmation process is executed. In response to this request, the terminals (4, 5) may report their most recent current positions (RP10, RP20) to the management server 1 in real time. The management server 1 may determine whether or not the conditions of the usage relationship are satisfied from the information on the most recent current positions (RP10, RP20) reported in real time. In either form, if information on the most recent current location of at least one of the first terminal 4 and the second terminal 5 cannot be obtained due to factors such as the power being turned off, the management server 1 may determine that the conditions of the usage relationship are not met.

[0136] Further, the destination of the information of each current position may be appropriately selected according to the embodiment. In one example, the destination of the information of each current position may be the management server 1. Accordingly, the information of each current position may be managed by the management server 1. In another example, the destination of the information of each current position may be an external server (the first server 2, the second server 3, etc.). Accordingly, the information of each current position may be managed by the external server. The management server 1 may acquire the information of each current position (RP10, RP20) from the external server. Reporting to the management server 1 may include reporting directly to the management server 1 and reporting indirectly to the management server 1 via the external server. The reported information of each current position may be discarded after it is no longer used in the confirmation process, or may be stored as history for at least a predetermined period of time. When the form of reporting directly to the management server 1 is adopted, the information of each current position may be stored in the management server 1 or in an external server (the first server 2, the second server 3, NAS, etc.). Similarly, when indirect reporting to the management server 1 is adopted, information on each current location may be stored in the management server 1 or in an external server. According to one example of the present embodiment, the continuity of the usage relationship can be appropriately confirmed by using the relationship between the locations of the first terminal 4 and the second terminal 5.

[0137] (ii) When it is determined that the utilization relationship is continuing, the management server 1 may maintain the setting of the correspondence relationship between the relevant individuals. On the other hand, when it is determined that the utilization relationship is not continuing, the management server 1 may cancel the correspondence relationship between the relevant individuals. In the case of a proxy, in response to determining that the utilization relationship between the proxy individual PI and the target individual TA is continuing, the management server 1 may maintain the setting of the correspondence relationship between the proxy request individual PR and the target individual TA. On the other hand, in response to determining that the utilization relationship between the proxy individual PI and the target individual TA is not continuing, the management server 1 may cancel the correspondence relationship between the proxy request individual PR and the target individual TA. After the correspondence relationship is set, the management server 1 may be configured to update the status of the correspondence relationship by repeatedly executing the confirmation process periodically or irregularly until the correspondence relationship is canceled.

[0138] When the management server 1 determines that the usage relationship is not continuing, the management server 1 may immediately cancel the corresponding relationship, or may hold the relationship for a predetermined period and then release the relationship. The timing of the release may be appropriately determined according to the embodiment. When the latter method is adopted, if the continuation of the usage relationship is confirmed by at least one of the above methods during the hold, the management server 1 may restore the setting of the corresponding relationship. This makes it possible to quickly restore the setting of the corresponding relationship without immediately releasing the relationship when the user temporarily leaves the network, for example.

[0139] (Use of linked information) As described above, the linking information D10 may be used in various situations. In one example, the linking information D10 may be used simply to track the emergence and extinction of a relationship between a first object and a second object.

[0140] In another example, the linking information D10 may be used to enable at least a part of the authority linked to either the first object or the second object to be exercised from the other object while a correspondence relationship is set between the first object and the second object. For example, the management server 1 may be configured to further execute validating the exercise of the authority associated with the corresponding first object via the second object with which the correspondence relationship is set in response to the establishment of the correspondence relationship between the first object and the second object. Also, the management server 1 may be configured to further execute invalidating the exercise of the authority in response to the cancellation of the correspondence relationship. In the case of a proxy, in response to the setting of the correspondence relationship between the proxy request individual PR and the target individual TA by the proxy individual PI, the management server 1 may validate the proxy exercise of at least a part of the authority of the proxy request individual PR via the target individual TA by the proxy individual PI. On the other hand, in response to the cancellation of the correspondence relationship, the management server 1 may invalidate the proxy exercise of the authority. 2, the association information D10 may be used to enable at least a part of the authority associated with the user to be exercised from the mobile body while a correspondence relationship is set between the user and the mobile body. According to one example of the present embodiment, permission and prohibition of the exercise of authority of the first object by the second object can be controlled by setting and canceling the correspondence relationship.

[0141] FIG. 9 is a schematic diagram showing an example of a usage scenario of the linking information D10 according to the present embodiment. FIG. 9 assumes a scenario in which the authority linked to the user in the example of FIG. 2 is exercised from a mobile body. In the case of a proxy, the user attempting to exercise the authority is a proxy user (proxy individual PI). It is also assumed that the linking information D10 is configured to include a first identifier I10 and a second identifier I20, thereby indicating a first target (user) and a second target (mobile body) in which a correspondence relationship is set. It is also assumed that the information of the user is managed by the first server 2, and the information of the mobile body is managed by the second server 3. The external system SY1 is arranged in a place where various services are exercised (for example, a parking lot, etc.), and is configured to execute information processing for providing the target service to a user who has the target authority. The configuration and services of the external system SY1 are not particularly limited, and are appropriately selected according to the embodiment. That's fine.

[0142] First, in step U10, the external system SY1 may acquire the second identifier I20 (mobile body identifier) ​​from the target mobile body. A method for acquiring the second identifier I20 may be appropriately selected depending on the embodiment. In one example, the external system SY1 may acquire the second identifier I20 from the second terminal 5 by exchanging data with the second terminal 5. The method of data exchange may be similar to the data exchange between the first terminal 4 and the second terminal 5. In another example, when the second identifier I20 is a vehicle registration number, the external system SY1 may acquire the second identifier I20 by photographing the license plate with an image sensor and analyzing the obtained image.

[0143] In step U20, the external system SY1 may use the acquired second identifier I20 as a query to inquire of the management server 1 whether or not there is a valid correspondence relationship for the target moving object at the target date and time. "Valid" means that the setting of the correspondence relationship is maintained at the target date and time. Basically, the target date and time is the present (instantaneous), but is not limited to this. For example, when executing a payment process at a past date and time, the target date and time may be a past date and time. If there is a valid correspondence relationship, the first identifier I10 (user identifier) ​​of the user linked to the target moving object is extracted. In the case of a proxy, the user identifier of the proxy requesting user (the first identifier I10 of the proxy requesting individual PR) is extracted. On the other hand, if there is no valid correspondence relationship and a user linked to the target moving object is not extracted, this process may end.

[0144] In step U30, the external system SY1 may use the extracted first identifier I10 as a query to inquire of the first server 2 about the exercisable authority of the user associated with the target moving object. The first server 2 may refer to the first target information O10 (user information O10A) to extract the exercisable authority associated with the target user. If the exercisable authority is not extracted, this process may end. In the first target information O10 (user information O10A), whether or not to permit the exercise of the authority by the moving object may be set for each authority. The exercisable authority may be extracted according to this setting. Also, if the target authority that the external system SY1 is going to exercise is not included in the exercisable authority, this process may end. The authority to be exercised may be appropriately specified at any timing. In one example, the authority to be exercised may be specified in advance in the external system SY1, or may be specified by the user.

[0145] In step U40, when the exercisable authority includes the target authority, the external system SY1 may execute a process for exercising the target authority. As a result, the authority associated with the user is exercised from the mobile body, and the user can receive a service via the mobile body. For example, when the authority information includes information on public personal authentication and the target authority is related to public personal authentication, the user can receive a public service via the mobile body. Also, for example, when the authority information includes payment information and the target authority is related to payment, the user can receive a payment service via the mobile body. The payment service may be, for example, payment for parking fees, highway fees, drive-through fees, public transportation fees, rental fees, and the like. Also, for example, when the authority information includes information on an electronic prescription and the target authority is receipt of medicine prescribed by an electronic prescription, the user can exercise the electronic prescription via the mobile body and receive the medicine.

[0146] In the case of a proxy, the proxy user (proxy individual PI) exercises the authority linked to the proxy requesting user (proxy requesting individual PR) via the target mobile object (target individual TA) and can receive services according to the results of the exercise. For example, consider a situation in which the authority information includes information regarding an electronic prescription and the target authority is to receive medicine prescribed by electronic prescription. In this case, the proxy requesting user can grant proxy authority to another user (proxy user), such as a taxi driver, and receive the prescribed medicine via a mobile object without having to go and collect the prescribed medicine himself. You can ask another user to collect the data.

[0147] The above processing procedure for exercising authority is merely an example, and each step may be modified as much as possible. Steps of the above processing procedure may be omitted, replaced, or added as appropriate depending on the embodiment. In addition, in the above processing procedure, the user may be replaced with a first object, and the moving object may be replaced with a second object. Furthermore, in the above processing procedure, "first" and "second" may be interchanged.

[0148] (Data communication between devices) Data communication between each device (management server 1, first server 2, second server 3, first terminal 4, second terminal 5, and terminal 6) is not particularly limited and may be appropriately selected depending on the embodiment. The network between each device may be appropriately selected from, for example, the Internet, a wireless communication network, a mobile communication network, a telephone network, a dedicated network, a local area network, etc. Data communication between each device may be performed using SSL (Secure Socket Layer), TLS (Transport Layer Security), etc. In one example, each of the terminals (4, 5, 6) may include a Subscriber Identity Module (SIM), and data communication between each of the terminals (4, 5, 6) and the servers (management server 1, first server 2, second server 3) may be performed by encrypted communication using the SIM.

[0149] [2 Configuration example] [Hardware configuration example] (Management Server) 10A is a schematic diagram showing an example of a hardware configuration of the management server 1 according to the present embodiment. The management server 1 according to the present embodiment is a computer to which a control unit 11, a storage unit 12, a communication interface 13, an input device 14, an output device 15, and a drive 16 are electrically connected.

[0150] The control unit 11 includes a hardware processor, such as a CPU (Central Processing Unit), The management server 1 includes a random access memory (RAM), a read only memory (ROM), etc., and is configured to execute any information processing based on programs and various data. The control unit 11 (CPU) is an example of a processor resource of the management server 1.

[0151] The storage unit 12 may be configured, for example, with a hard disk drive, a solid state drive, a semiconductor memory, etc. The storage unit 12 (as well as RAM and ROM) is an example of a memory resource. In this embodiment, the storage unit 12 stores various information such as a management program 81 and linking information D10. The management program 81 is a program for causing the management server 1 to execute information processing (see Figures 12A and 12B described below) relating to setting and canceling the correspondence between the first object and the second object. The management program 81 includes a series of commands for the information processing.

[0152] The communication interface 13 is configured to perform wired or wireless communication via a network. The communication interface 13 may be configured, for example, by a wired LAN (Local Area Network) module, a wireless LAN module, etc. The management server 1 may perform data communication with other computers (the first terminal 4, the second terminal 5, etc.) via the communication interface 13.

[0153] The input device 14 is, for example, a device for inputting information such as a mouse, a keyboard, or an operation button. The output device 15 is, for example, a device for outputting information such as a display or a speaker. An operator can operate the management server 1 by using the input device 14 and the output device 15. The input device 14 and the output device 15 may be integrally configured as, for example, a touch panel display. The input device 14 and the output device 15 may be configured as an external interface. The external interface may be appropriately configured to connect to an external device in a wired or wireless manner, for example, via a Universal Serial Bus (USB) port, a dedicated port, a wireless communication port, or the like.

[0154] The drive 16 is a device for reading various information such as a program stored in the storage medium 91. At least one of the management program 81 and the association information D10 may be stored in the storage medium 91 instead of or together with the storage unit 12. The storage medium 91 is configured to accumulate various information (stored programs, etc.) by electrical, magnetic, optical, mechanical, or chemical action so that a machine such as a computer can read the information. The management server 1 may acquire at least one of the management program 81 and the association information D10 from the storage medium 91. The storage medium 91 may be a disk-type storage medium such as a CD or DVD, or may be a non-disk-type storage medium such as a semiconductor memory (e.g., a flash memory). The type of the drive 16 may be appropriately selected according to the type of the storage medium 91. The drive 16 may be connected via an external interface.

[0155] In addition, with regard to the specific hardware configuration of the management server 1, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 11 may include multiple hardware processors. The hardware processor may be a microprocessor, a field-programmable gate array (FPGA), a digital signal processor (DSP), a GPS (GPS), or a combination of these. The input device 14, the output device 15, and the drive 16 may be configured by a graphics processing unit (U), an application specific integrated circuit (ASIC), etc. Either of them may be omitted. The association information D10 may be stored in an external computer (e.g., NAS, etc.) accessible to the management server 1, instead of in the storage unit 12. The management server 1 may be composed of multiple computers. In this case, the hardware configurations of the computers may or may not match. The management server 1 may be an information processing device designed specifically for the service provided, as well as a general-purpose server device, a general-purpose computer, etc.

[0156] (First server) 10B shows a schematic diagram of an example of a hardware configuration of the first server 2 according to this embodiment. The first server 2 according to this embodiment is a computer in which a control unit 21, a storage unit 22, a communication interface 23, an input device 24, an output device 25, and a drive 26 are electrically connected. The control unit 21 to the drive 26 and the storage medium 92 of the first server 2 may be configured similarly to the control unit 11 to the drive 16 and the storage medium 91 of the management server 1, respectively.

[0157] The control unit 21 (CPU) is an example of a processor resource of the first server 2, and the storage unit 22 (and RAM, ROM) is an example of a memory resource of the first server 2. In this embodiment, the storage unit 22 stores various information such as a program 82 and first target information O10. The program 82 is a program for causing the first server 2 to execute information processing related to the authentication of the first target. The program 82 includes a series of instructions for the information processing. At least one of the program 82 and the first target information O10 may be stored in a storage medium 92 instead of or together with the storage unit 22. The first server 2 may acquire at least one of the program 82 and the first target information O10 from the storage medium 92. The first server 2 may perform data communication with another computer via the communication interface 23. The first server 2 may be operated via an input device 24 and an output device 25.

[0158] In addition, regarding the specific hardware configuration of the first server 2, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 21 may include multiple hardware processors. The hardware processors include a microprocessor, an FP It may be configured with a GA, DSP, GPU, ASIC, etc. At least one of the input device 24, the output device 25, and the drive 26 may be omitted. The first target information O10 may be stored in an external computer (e.g., NAS, etc.) accessible by the first server 2, instead of the storage unit 22. The first server 2 may be configured with a plurality of computers. In this case, the hardware configurations of the computers may or may not be the same. The first server 2 may be an information processing device designed exclusively for the service provided, as well as a general-purpose server device, a general-purpose computer, etc.

[0159] (Second server) 10C shows a schematic diagram of an example of a hardware configuration of the second server 3 according to this embodiment. The second server 3 according to this embodiment is a computer to which a control unit 31, a storage unit 32, a communication interface 33, an input device 34, an output device 35, and a drive 36 are electrically connected. The control unit 31 to the drive 36 and the storage medium 93 of the second server 3 may be configured similarly to the control unit 11 to the drive 16 and the storage medium 91 of the management server 1, respectively.

[0160] The control unit 31 (CPU) is an example of a processor resource of the second server 3, and the storage unit 32 (and RAM, ROM) is an example of a memory resource of the second server 3. In this embodiment, the storage unit 32 stores various information such as the program 83 and the second target information O20. The program 83 is a program for causing the second server 3 to execute information processing related to the authentication of the second target. The program 83 includes a series of instructions for the information processing. At least one of the program 83 and the second target information O20 may be stored in a storage medium 93 instead of or together with the storage unit 32. The second server 3 may acquire at least one of the program 83 and the second target information O20 from the storage medium 93. The second server 3 may perform data communication with another computer via the communication interface 33. The second server 3 may be operated via an input device 34 and an output device 35.

[0161] Regarding the specific hardware configuration of the second server 3, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 31 may include multiple hardware processors. The hardware processor may be configured with a microprocessor, FPGA, DSP, GPU, ASIC, or the like. At least one of the input device 34, the output device 35, and the drive 36 may be omitted. The second target information O20 may be stored in an external computer (e.g., NAS, etc.) accessible by the second server 3, instead of the storage unit 32. The second server 3 may be configured with multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The second server 3 may be an information processing device designed specifically for the service provided, as well as a general-purpose server device, a general-purpose computer, or the like.

[0162] (1st terminal) 10D shows an example of a hardware configuration of the first terminal 4 according to the present embodiment. The first terminal 4 according to the present embodiment is a computer to which a control unit 41, a storage unit 42, a communication interface 43, an input device 44, an output device 45, a drive 46, and a positioning module 47 are electrically connected. The control unit 41 to the drive 46 and the storage medium 94 of the first terminal 4 may be configured similarly to the control unit 11 to the drive 16 and the storage medium 91 of the management server 1, respectively.

[0163] The control unit 41 (CPU) is an example of a processor resource of the first terminal 4, and the storage unit 42 (and RAM, ROM) is an example of a memory resource of the first terminal 4. In this embodiment, the storage unit 42 stores various information such as a program 84 and authority verification information AU. The program 84 is a program for causing the first terminal 4 to execute information processing relating to the linking (FIGS. 12A and 12B to be described later). The program 84 executes a series of commands for the information processing. The program 84 may be stored in a storage medium 94 instead of or together with the storage unit 42. The first terminal 4 may acquire the program 84 from the storage medium 94. The first terminal 4 may be operated via the input device 44 and the output device 45.

[0164] The first terminal 4 may perform data communication with other computers via the communication interface 43. In one example, the communication interface 43 may be configured with multiple types of modules. For example, the communication interface 43 may include a short-range wireless communication module 431 and another wireless communication module (e.g., a cellular communication module, etc.). The first terminal 4 may perform data communication with the second terminal 5 via the short-range wireless communication module 431, and may perform data communication with servers (the management server 1, the first server 2, the second server 3, etc.) via the other wireless communication module.

[0165] In addition, regarding the specific hardware configuration of the first terminal 4, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 41 may include multiple hardware processors. The hardware processor is configured by a microprocessor, FPGA, DSP, GPU, ASIC, ECU (Electronic Control Unit), etc. At least one of the input device 44, the output device 45, the drive 46, and the positioning module 47 may be omitted. The storage unit 42 may store the first identifier I10 of the proxy individual PI. Alternatively, the first identifier I10 of the proxy individual PI may not be stored in the storage unit 42 and may be acquired each time. In order to acquire data such as the identifier and information used for authentication, the first terminal 4 may further include a data acquisition device such as a sensor or a reading device. The first terminal 4 may be composed of multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The first terminal 4 may be an information processing device designed specifically for the service provided, as well as a general-purpose computer, a terminal device (e.g., a smartphone, a tablet PC, etc.), etc.

[0166] (2nd terminal) 10E shows a schematic diagram of an example of a hardware configuration of the second terminal 5 according to the present embodiment. The second terminal 5 according to the present embodiment is a computer to which a control unit 51, a storage unit 52, a communication interface 53, an input device 54, an output device 55, a drive 56, and a positioning module 57 are electrically connected. The control unit 51 to the drive 56 and the storage medium 95 of the second terminal 5 may be configured similarly to the control unit 11 to the drive 16 and the storage medium 91 of the management server 1, respectively.

[0167] The control unit 51 (CPU) is an example of a processor resource of the second terminal 5, and the storage unit 52 (and RAM, ROM) is an example of a memory resource of the second terminal 5. In this embodiment, the storage unit 52 stores various information such as the program 85 and the second identifier I20 of the target individual TA. The program 85 is a program for causing the second terminal 5 to execute information processing related to the linking (FIGS. 12A and 12B described later). The program 85 includes a series of instructions for the information processing. At least one of the program 85 and the second identifier I20 may be stored in the storage medium 95 instead of the storage unit 52 or together with the storage unit 52. The second terminal 5 may acquire at least one of the program 85 and the second identifier I20 from the storage medium 95. The second terminal 5 may be operated via the input device 54 and the output device 55.

[0168] The second terminal 5 may perform data communication with another computer via the communication interface 53. In one example, similar to the first terminal 4, the communication interface 53 may be configured with a plurality of types of modules. For example, the communication interface 53 may include a short-range wireless communication module 531 and another wireless communication module. The second terminal 5 may perform data communication with the first terminal 4 via the short-range wireless communication module 531, and may perform data communication with a server via the other wireless communication module.

[0169] Regarding the specific hardware configuration of the second terminal 5, components can be omitted, replaced, and added as appropriate depending on the embodiment. For example, the control unit 51 may include multiple hardware processors. The hardware processor may be configured with a microprocessor, FPGA, DSP, GPU, ASIC, ECU, etc. At least one of the input device 54, the output device 55, the drive 56, and the positioning module 57 may be omitted. The second identifier I20 may not be stored in the storage unit 52, but may be acquired each time. In order to acquire data such as the identifier and information used for authentication, the second terminal 5 may further include a data acquisition device such as a sensor or a reading device. The second terminal 5 may be configured with multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The second terminal 5 may be a general-purpose computer, a terminal device, etc., in addition to an information processing device designed specifically for the service provided.

[0170] (Terminal) 10F shows a schematic diagram of an example of a hardware configuration of the terminal 6 according to this embodiment. The terminal 6 according to this embodiment is a computer to which a control unit 61, a storage unit 62, a communication interface 63, an input device 64, an output device 65, and a drive 66 are electrically connected. The control unit 61 to the drive 66 and the storage medium 96 of the terminal 6 may be configured similarly to the control unit 11 to the drive 16 and the storage medium 91 of the management server 1, respectively.

[0171] The control unit 61 (CPU) is an example of a processor resource of the terminal 6, and the storage unit 62 (and RAM, ROM) is an example of a memory resource of the terminal 6. In this embodiment, the storage unit 62 stores various information such as the program 86 and the first identifier I10 of the proxy requesting individual PR. The program 86 is a program for causing the terminal 6 to execute information processing related to the setting and cancellation of the correspondence relationship by the proxy. The program 86 includes a series of instructions for the information processing. At least one of the program 86 and the first identifier I10 may be stored in the storage medium 96 instead of the storage unit 62 or together with the storage unit 62. The terminal 6 may acquire at least one of the program 86 and the first identifier I10 from the storage medium 96. The terminal 6 may perform data communication with another computer via the communication interface 63. The terminal 6 may be operated via the input device 64 and the output device 65.

[0172] In addition, regarding the specific hardware configuration of the terminal 6, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 61 may include multiple hardware processors. The hardware processor may be configured by a microprocessor, an FPGA, a DSP, a GPU, an ASIC, an ECU (Electronic Control Unit), etc. At least one of the input device 64, the output device 65, and the drive 66 may be omitted. The first identifier I10 may not be stored in the storage unit 62, but may be acquired each time. As with the first terminal 4 and the second terminal 5, the terminal 6 may further include a data acquisition device such as a sensor or a reader to acquire data such as an identifier and a certificate. The communication interface 63 may include a short-range wireless communication module and other wireless communication modules. The terminal 6 may be configured to be able to measure the current location of the terminal 6 by including a positioning module. The terminal 6 may be configured of multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The terminal 6 may be an information processing device designed specifically for the service provided, as well as a general-purpose computer, a terminal device, etc.

[0173] [Software configuration example] FIG. 11 illustrates an example of a software configuration of each device (the management server 1, the first server 2, the second server 3, the first terminal 4, the second terminal 5, and the terminal 6) according to this embodiment.

[0174] (Management Server) The control unit 11 of the management server 1 loads the management program 81 stored in the storage unit 12 into the RAM, and causes the CPU to execute instructions included in the management program 81. As a result, the management server 1 operates as a computer including a reception unit 111, a setting unit 112, a release unit 113, and a notification unit 114 as software modules.

[0175] The reception unit 111 is configured to receive a linking request directly or indirectly from at least one of the terminals of the first target and the second target in response to the occurrence of a usage relationship between the relevant individuals of the first target and the second target. The reception unit 111 is configured to receive a request to set a correspondence relationship between the relevant individuals of the first target and the second target by receiving the linking request. In the case of a proxy, the reception unit 111 is configured to receive a linking request from at least one of the first terminal 4 and the second terminal 5 in response to the occurrence of a usage relationship between the proxy individual PI of the first target and the target individual TA of the second target. The reception unit 111 is configured to receive this linking request in response to the occurrence of a usage relationship between the proxy request individual PR of the first target and the target individual TA of the second target.

[0176] The setting unit 112 is configured to execute a process of setting a correspondence relationship between the relevant individuals of the first target and the second target based on the linking request. In the case of a proxy, the setting unit 112 is configured to set a correspondence relationship between the proxy requesting individual PR and the target individual TA in response to authentication of the proxy requesting individual PR being established. The release unit 113 is configured to execute a process of releasing the correspondence relationship in response to reception of a release request from at least one of the first terminal 4 and the second terminal 5 or establishment of a predetermined release condition. The release unit 113 is configured to execute a process of releasing the correspondence relationship due to a factor related to the proxy requesting individual PR.

[0177] The notification unit 114 is configured to transmit a notification indicating a result of the execution of the correspondence relationship setting process to at least one of the first terminal 4 and the second terminal 5. The notification unit 114 is configured to transmit a notification indicating a result of the execution of the correspondence relationship cancellation process to at least one of the first terminal 4 and the second terminal 5. The notification unit 114 is configured to transmit a notification indicating that the correspondence relationship has been set to the terminal 6. In addition, the notification unit 114 is configured to transmit a notification indicating that the correspondence relationship has been cancelled to the terminal 6.

[0178] When adopting a form in which the authentication process of at least one of the first target and the second target is executed by the management server 1, the management server 1 may be configured to further include an authentication unit 115 as a software module. The authentication unit 115 may be configured to execute the authentication process of at least one of the first target and the second target.

[0179] (First server) When adopting a form in which the authentication process of the first target is executed by the first server 2, the control unit 21 of the first server 2 may execute instructions included in the program 82 by a CPU. As a result, the first server 2 may operate as a computer including an authentication unit 211 as a software module. The authentication unit 211 is configured to execute the authentication process of the first target in response to an authentication request for the first target.

[0180] (Second server) When adopting a form in which the authentication process of the second target is executed by the second server 3, the control unit 31 of the second server 3 may execute instructions included in the program 83 by the CPU. In this way, the second server 3 may operate as a computer including an authentication unit 311 as a software module. The authentication unit 311 is configured to execute the authentication process of the second target in response to an authentication request for the second target.

[0181] (1st terminal) The control unit 41 of the first terminal 4 executes instructions included in the program 84 by the CPU. As a result, the first terminal 4 operates as a computer including a data exchange unit 411, a setting request unit 412, and an unbinding request unit 413 as software modules. The data exchange unit 411 is configured to execute data exchange with the second terminal 5. The setting request unit 412 is configured to transmit a linking request (a request for linking setting) to the management server 1. The unbinding request unit 413 is configured to transmit an unbinding request (a request for unbinding) to the management server 1.

[0182] (2nd terminal) The control unit 51 of the second terminal 5 executes instructions included in the program 85 by the CPU. As a result, the second terminal 5 operates as a computer including a data exchange unit 511, a setting request unit 512, and a release request unit 513 as software modules. The data exchange unit 511 is configured to execute data exchange with the first terminal 4. The setting request unit 512 is configured to transmit a linking request to the management server 1. The release request unit 513 is configured to transmit a release request to the management server 1.

[0183] (Terminal) The control unit 61 of the terminal 6 executes instructions included in the program 86 by the CPU. As a result, the terminal 6 operates as a computer having a proxy request unit 611 and a release request unit 612 as software modules. The proxy request unit 611 is configured to receive settings regarding the granting of proxy authority, including the designation of a proxy individual PI, and to directly or indirectly transmit authority grant information AG to the first terminal 4 of the designated proxy individual PI. The release request unit 612 is configured to transmit a release request to the management server 1.

[0184] (others) In this embodiment, an example is described in which each software module of each device is realized by a general-purpose CPU. However, some or all of the above software modules may be realized by one or more dedicated processors. Each of the above modules may be realized as a hardware module. With respect to the software configuration of each device, modules may be omitted, replaced, and added as appropriate depending on the embodiment. For example, when adopting a form in which a linking request is transmitted from only one of the first terminal 4 and the second terminal 5, the setting request unit may be omitted from the other terminal. Similarly, when adopting a form in which an unlinking request is transmitted from only one of the first terminal 4 and the second terminal 5, the unlinking request unit may be omitted from the other terminal. An authentication unit may be omitted from a device that omits the execution of an authentication process.

[0185] [3 Example of operation] (Linking settings) 12A shows an example of a processing procedure for linking setting by the system 100 according to this embodiment. The following processing procedure is an example of an information processing method executed by a computer. Among the following processing procedures, the processing procedure of the management server 1 is an example of a management method executed by a computer.

[0186] In step S10, the control unit 61 of the terminal 6 operates as a proxy request unit 611 and accepts settings regarding the granting of proxy authority, including the designation of a proxy individual PI. The control unit 61 directly or indirectly notifies the first terminal 4 of the designated proxy individual PI of the authorization information AG. In response to this, the control unit 41 of the first terminal 4 receives the authorization information AG.

[0187] In step S20, in response to the occurrence of a utilization relationship between the representative individual PI and the target individual TA, the control unit 41 of the first terminal 4 operates as a data exchange unit 411 and executes data exchange with the second terminal 5. The control unit 51 of the second terminal 5 operates as a data exchange unit 511 and executes data exchange with the first terminal 4. The data exchange may be performed by short-range wireless communication. In this data exchange, the control unit 41 of the first terminal 4 requests the second terminal 5 to verify the authority of the proxy by providing the authority verification information AU to the second terminal 5.

[0188] In step S30, the control unit 51 of the second terminal 5 verifies the authority of agency using the authority verification information AU in response to a request from the first terminal 4. At least one of the above two methods may be used as a method of verifying the authority of agency. When the first method is adopted, the above-mentioned processes of steps S301 and S302 are an example of the process of step S30. When the second method is adopted, the above-mentioned process of step S305 is an example of the process of step S30. In step S35, a branch destination of the process is determined depending on whether the authority of agency is verified. When the verification is successful, the control unit 51 of the second terminal 5 proceeds to the next step S40. On the other hand, when the verification is not successful, the control unit 51 of the second terminal 5 returns the process to step S20 and prompts the first terminal 4 to resend the authority verification information AU. Note that when the verification is not successful, the first terminal 4 and the second terminal 5 may appropriately end the process procedure related to the linking setting related to this operation example.

[0189] In step S40, at least one of the first terminal 4 and the second terminal 5 transmits a linking request including a request for authentication of the proxy requesting individual PR to the management server 1. The control unit 41 of the first terminal 4 may operate as a setting request unit 412 and transmit the linking request to the management server 1. The control unit 51 of the second terminal 5 may operate as a setting request unit 512 and transmit the linking request to the management server 1. The first terminal 4 and the second terminal 5 may transmit the linking request together, or one of the first terminal 4 and the second terminal 5 may transmit the linking request. One of the first terminal 4 and the second terminal 5 may give an instruction to the other terminal, and the other terminal may transmit the linking request. In addition, the linking request may be transmitted directly to the management server 1, or may be transmitted indirectly via an external server. The control unit 11 of the management server 1 operates as a reception unit 111 and receives the linking request.

[0190] In step S40, when the first terminal 4 and the second terminal 5 jointly transmit a linking request, one linking request may be transmitted in parts from the first terminal 4 and the second terminal 5, or the same linking request may be transmitted. When transmitting in parts, a part of the data of the linking request may be transmitted from the first terminal 4, and the remaining data may be transmitted from the second terminal 5. Partial overlap may be permitted between the part of the data and the remaining data. In step S20, in order to identify the combination of the relevant individuals of the first and second targets currently requesting the setting of a correspondence relationship, the management server 1 may appropriately identify the correspondence of this data (i.e., determine the combination of corresponding data).

[0191] The correspondence of data may be specified by any method. In one example, the data transmitted from each terminal (4, 5) may include shared information for specifying the correspondence of data. The shared information may be composed of information having a relationship, such as, for example, a match or a correspondence relationship. The management server 1 may specify the correspondence of data in response to the establishment of a relationship between the shared information included in the data received from one of the first terminal 4 and the second terminal 5 and the shared information included in the data received from the other terminal.

[0192] The shared information may be configured arbitrarily. In one example, the shared information may be configured by a combination of a first identifier I10 of the proxy requesting individual PR and a second identifier I20 of the target individual TA. The management server 1 may identify the correspondence of the data in accordance with a match between the combination of identifiers (I10, I20) included in the data received from the first terminal 4 and the combination of identifiers (I10, I20) included in the data received from the second terminal 5. The shared information may include the first identifier I10 of the proxy individual PI. In another example, the shared information may be configured by temporary information such as a random number, a timestamp, a hash value, etc. In this case, the management server 1 may identify the correspondence of the data in accordance with a match between the temporary information included in the data received from the first terminal 4 and the combination of identifiers (I10, I20) included in the data received from the second terminal 5. The correspondence of data may be specified according to the establishment of a relationship between the temporary information included in the shared information and the shared information. The shared information may be shared at any timing between the first terminal 4 and the second terminal 5. In a typical example, the first terminal 4 and the second terminal 5 may share the shared information when exchanging data.

[0193] In step S45, the management server 1 and the external server authenticate the proxy requesting individual PR in response to the authentication request. The first server 2 is an example of an external server. In this embodiment, the authentication process of the proxy requesting individual PR may be executed by the management server 1 or the first server 2. In one example, the control unit 11 of the management server 1 may operate as an authentication unit 115 and authenticate the proxy requesting individual PR. In another example, the control unit 21 of the first server 2 may operate as an authentication unit 211 and authenticate the proxy requesting individual PR. The management server 1 or the first server 2 may obtain data used for authentication of the proxy requesting individual PR from at least one of the first terminal 4 and the second terminal 5, or may obtain it from the terminal 6 of the proxy requesting individual PR.

[0194] The processing order of steps S40 and S45 may be appropriately determined according to the embodiment. In one example, at least one of the first terminal 4 and the second terminal 5 may send an authentication request to the management server 1 or the first server 2. In response to this authentication request, the management server 1 or the first server 2 may authenticate the proxy requesting individual PR. The management server 1 or the first server 2 may return the authentication result of the proxy requesting individual PR to at least one of the first terminal 4 and the second terminal 5. In response to the authentication result that the authentication of the proxy requesting individual PR is established, at least one of the first terminal 4 and the second terminal 5 may send a linking request to the management server 1. In another example, at least one of the first terminal 4 and the second terminal 5 may send a linking request including an authentication request to the first server 2, and the first server 2 may authenticate the proxy requesting individual PR in response to this authentication request. When the authentication of the proxy requesting individual PR is established, the first server 2 may send a linking request including the authentication result of the proxy requesting individual PR to the management server 1. In yet another example, at least one of the first terminal 4 and the second terminal 5 may send a linking request including an authentication request to the management server 1. The management server 1 may authenticate the proxy requesting individual PR in response to the authentication request. Alternatively, the management server 1 may request the first server 2 to authenticate the proxy requesting individual PR by forwarding the authentication request to the first server 2. The first server 2 may authenticate the proxy requesting individual PR in response to the request and return the authentication result to the management server 1. In this way, the management server 1 may obtain the authentication result of the proxy requesting individual PR.

[0195] Furthermore, the subject of the authentication process does not have to be limited to the proxy requesting individual PR. In one example, at least one of the proxy individual PI and the target individual TA may be authenticated along with the proxy requesting individual PR. The control unit 11 of the management server 1 may operate as an authentication unit 115 and authenticate at least one of the proxy individual PI and the target individual TA. The control unit 21 of the first server 2 may operate as an authentication unit 211 and authenticate the proxy individual PI. The control unit 31 of the second server 3 may operate as an authentication unit 311 and authenticate the target individual TA.

[0196] In step S50, the branching destination of the process is determined depending on whether the authentication is successful. If the authentication of the proxy requesting individual PR is successful, the control unit 11 of the management server 1 proceeds to the next step S60. On the other hand, if the authentication of the proxy requesting individual PR is not successful, the control unit 11 of the management server 1 may return to step S45 and request at least one of the first terminal 4, the second terminal 5, and the terminal 6 to resend the data used to authenticate the proxy requesting individual PR. Note that if the authentication is not successful, the management server 1 may appropriately terminate the processing procedure related to the linking setting related to this operation example.

[0197] In step S60, the control unit 11 of the management server 1 operates as the setting unit 112 and updates the linking information D10 so as to establish a setting of a correspondence relationship between the first object (the proxy requesting individual PR) and the second object (the object individual TA) specified by the linking request. In one example, Updating the linking information D10 in accordance with the setting of the correspondence relationship may be configured by generating new linking information D10 indicating the specified correspondence relationship. In this embodiment, the management server 1 sets the correspondence relationship between the proxy requesting individual PR and the target individual TA, thereby validating the proxy exercise of the authority of the proxy requesting individual PR by the proxy individual PI via the target individual TA.

[0198] In step S70, the control unit 11 operates as the notification unit 114 and directly or indirectly transmits a notification indicating the result of executing the correspondence setting process to at least one of the first terminal 4 and the second terminal 5. The control unit 11 may directly or indirectly transmit a notification indicating that the correspondence has been set to the terminal 6. When the notification of the result is completed, the processing procedure regarding the association setting according to this operation example ends.

[0199] The above process is merely an example, and each step may be modified as much as possible. Furthermore, steps may be omitted, replaced, or added as appropriate in accordance with the embodiment.

[0200] (Unlink) Fig. 12B shows an example of a processing procedure for canceling a link by the system 100 according to this embodiment. The following processing procedure is an example of an information processing method executed by a computer. Among the following processing procedures, the processing procedure of the management server 1 is an example of a management method executed by a computer. Note that the example of Fig. 12B assumes a situation in which a cancellation request is sent directly from the first terminal 4 to the management server 1.

[0201] In step SZ10, the control unit 41 of the first terminal 4 operates as the cancellation request unit 413 and transmits a request to cancel the correspondence relationship to the management server 1. In response to this, the control unit 11 of the management server 1 receives the cancellation request. The correspondence relationship to be requested to be cancelled may be designated as appropriate. The trigger for the cancellation request may be selected as appropriate depending on the embodiment.

[0202] In step SZ102, the control unit 11 operates as the release unit 113 and updates the association information D10 so as to release the setting of the correspondence specified by the received release request. In one example, updating the association information D10 in accordance with the release of the correspondence may be configured by recording information indicating the release. For example, when the association information D10 has the configuration of FIG. 3A, the control unit 11 may release the target correspondence by adding the release time to the corresponding association information D10 or setting a release flag. When the association information D10 is configured on a blockchain platform, the control unit 11 may release the target correspondence by generating a transaction indicating the release of the association and adding the generated transaction to the blockchain.

[0203] In step SZ103, the control unit 11 operates as the notification unit 114 and transmits the execution result of the association release process to the first terminal 4. When the notification of the result is completed, the processing procedure for association release according to this operation example ends.

[0204] The above processing procedure is merely an example, and each step may be changed as much as possible. In addition, steps of the above processing procedure may be omitted, replaced, or added as appropriate depending on the embodiment. For example, as described above, the transmission route of the release request is not limited to the example of FIG. 12B, and may be selected as appropriate depending on the embodiment. The release request may be transmitted from the second terminal 5 (release request unit 513) or the terminal 6 (release request unit 612). The management server 1 (notification unit 114) may transmit a notification indicating that the correspondence has been released to the terminal 6. The process of the release request may include authentication processing of at least one of the first target and the second target. In addition, the control unit 11 of the management server 1 may operate as the release unit 113 instead of the above step SZ102, and release the correspondence when a predetermined release condition is met. The control unit 11 may The control unit 11 may operate as the canceling unit 113 and cancel the correspondence relationship with the target individual TA in response to the setting of the correspondence relationship with another individual TO of the second target by the proxy requesting individual PR. Furthermore, the control unit 11 may operate as the canceling unit 113 and, after setting the correspondence relationship, execute the above-mentioned confirmation process of continued use for the set correspondence relationship at any timing.

[0205] [Features] In this embodiment, information indicating the setting of the correspondence relationship between the proxy request individual PR of the first target and the target individual TA of the second target is recorded by the processing of step S60. This recording makes it possible to track the use relationship between the proxy individual PI and the target individual TA in response to the request of the proxy request individual PR. In addition, security can be ensured by the verification processing of step S30 and the authentication processing of step S45. Furthermore, in accordance with the setting of the correspondence relationship between the proxy request individual PR and the target individual TA, the proxy individual PI is enabled to exercise the authority of the proxy request individual PR via the target individual TA. This allows the proxy individual PI to exercise at least a part of the authority of the proxy request individual PR on behalf of the proxy request individual PR. Therefore, according to this embodiment, while ensuring security, the use relationship between the first target and the second target can be tracked, and the proxy individual PI can be granted the proxy authority to exercise at least a part of the authority of the proxy request individual PR on behalf of the proxy request individual PR while the use relationship is established.

[0206] [4 Variations] Although the embodiment of the present disclosure has been described in detail above, the above description is merely an example of the present disclosure in every respect. It goes without saying that various improvements or modifications can be made without departing from the scope of the present disclosure. For example, the following modifications are possible. In the following, the same reference numerals are used for the same components as in the above embodiment, and the description of the same points as in the above embodiment is omitted as appropriate. The following modifications can be combined as appropriate.

[0207] In the above embodiment, the authentication process may be executed in at least one of the management server 1 and the external server (the first server 2, the second server 3, etc.). Data communication when executing the authentication process may be designed appropriately according to the embodiment. As an example, at least one of the following three authentication methods may be adopted.

[0208] (A) First authentication method FIG. 14A shows a schematic diagram of an example of a process of linking when the first authentication method is adopted. In the example of FIG. 14A, the above-mentioned first method is adopted as a method for verifying the power of attorney, and a situation is assumed in which a form is adopted in which the proxy request individual PR and the target individual TA are authenticated when linking is set. In the first authentication method, the second terminal 5 executes authentication processing of the second target in response to a request (authentication request) from the terminal of the first target. In response to a request (authentication request) from the terminal of the second target, the first server 2 executes authentication processing of the first target. The first terminal 4 and the second terminal 5 request the first server 2 and the second server 3 to authenticate the proxy request individual PR and the target individual TA as a linking request, and have the result of the authentication reported to the management server 1. As a result, the first terminal 4 and the second terminal 5 transmit the linking request to the management server 1. The request transmitted from each terminal (4, 5) to each server (2, 3) is an example of a linking request including an authentication request. The process in which each terminal (4, 5) sends an authentication request to each server (2, 3) and has each server (2, 3) send the authentication result to the management server 1 is an example of a process in which the first terminal 4 and the second terminal 5 jointly send a linking request.

[0209] The first server 2 is configured to be able to access a first storage device that stores first registered unique information CA10 for authenticating a first object. The first storage device may be configured by at least one of a memory resource of the first server 2 and an external storage device (such as a NAS). The first registered unique information CA10 may be included in the first object information O10. The second server 3 is configured to be able to access a second storage device that stores second registered unique information CA20 for authenticating a second object. The second storage device may be configured by at least one of the memory resource of the second server 3 and an external storage device (such as a NAS). The second registered unique information CA20 may be included in the second target information O20.

[0210] Each registered unique information (CA10, CA20) is unique information registered in advance for the authentication of each target. The unique information does not need to be particularly limited in data format and configuration as long as it can be used for authentication, and may be appropriately selected depending on the embodiment. The unique information may be composed of any information, such as information derived from the target, information derived from the terminal, information generated temporarily, or information generated by any other method.

[0211] The information derived from the subject may be, for example, biometric information, uniquely assigned identification information, etc. The biometric information may be, for example, a face image, a fingerprint, a voiceprint, etc. The uniquely assigned identification information may be, for example, a vehicle registration number, a vehicle identification number, a personal number, etc. When an IC tag is assigned to the subject, the uniquely assigned identification information may include information held by the IC tag. The information derived from the terminal may be, for example, a MAC address, terminal identification information, etc. The temporarily generated information may be, for example, a one-time password, a private address (dynamically generated address), etc. The temporarily generated information may be composed of a timestamp, a random number, a hash value, etc. The information generated by any other method may include, for example, a password, a passcode, and other information other than a symbol string.

[0212] First, in step S10, the control unit 61 of the terminal 6 performs settings related to the granting of proxy authority and notifies the first terminal 4 of the authorization information AG of the designated proxy individual PI. In one example, the control unit 61 of the terminal 6 may notify the first terminal 4 of the authorization information AG including the first identifier I10 and contact information AU1 of the proxy request individual PR. In response, the first terminal 4 receives the authorization information AG.

[0213] In step S20, the first terminal 4 and the second terminal 5 exchange data. In this data exchange, the control unit 41 of the first terminal 4 may provide the first identifier I10 and contact information AU1 of the proxy request individual PR to the second terminal 5. The control unit 51 of the second terminal 5 may acquire the first identifier I10 and contact information AU1 of the proxy request individual PR from the proxy individual PI or the first terminal 4. In addition, in this data exchange, the control unit 41 of the first terminal 4 may acquire the second identifier I20 and the second unique information CA2 of the target individual TA from either the target individual TA or the second terminal 5. The method of acquiring the second identifier I20 and the second unique information CA2 may be appropriately selected depending on the embodiment. In one example, the control unit 41 of the first terminal 4 may acquire at least one of the second identifier I20 and the second unique information CA2 of the target individual TA using an input device, a sensor, or the like. In another example, the second identifier I20 and the second unique information CA2 may be stored in advance in the second terminal 5, and the control unit 41 of the first terminal 4 may acquire the second identifier I20 and the second unique information CA2 through data exchange with the second terminal 5.

[0214] In step S301, the control unit 51 of the second terminal 5 transmits an inquiry to the contact AU1. In step S302, the control unit 51 of the second terminal 5 receives an approval response as a result of the execution of the approval process. In one example, the contact AU1 may be a contact of the terminal 6, and the control unit 51 of the second terminal 5 may transmit an inquiry to the terminal 6. In response to the reception of the inquiry, the control unit 61 of the terminal 6 may execute the approval process and return an approval response to the second terminal 5. The control unit 61 of the terminal 6 may transmit the first unique information CA1 of the proxy request individual PR together with the approval response to the second terminal 5. In response to this, the control unit 51 of the second terminal 5 may receive the approval response and the first unique information CA1 of the proxy request individual PR from the terminal 6. In another example, the control unit 51 of the second terminal 5 may transmit an inquiry to an external computer, and may receive the first unique information CA1 of the proxy request individual PR from the external computer together with the approval response. The method of acquiring the first unique information CA1 may be appropriately selected according to the embodiment. In one ... the terminal 6, and may receive the first unique information CA1 of the proxy request individual PR together with the approval response from the external computer. The control unit 61 of the second terminal 5 may acquire the first unique information CA1 from the proxy requesting individual PR using an input device, a sensor, etc. The terminal 6 may retain the first unique information CA1 in advance. The control unit 51 of the second terminal 5 may receive the first unique information CA1 directly or indirectly from the terminal 6. Each identifier (I10, I20) and each unique information (CA1, CA2) are examples of data used for authentication. By receiving a response indicating approval, verification of the authority to act as the proxy is established.

[0215] In step SA410, the control unit 51 of the second terminal 5 transmits an authentication request including the first identifier I10 and the first unique information CA1 of the proxy requesting individual PR to the first server 2. In response to this, the control unit 21 of the first server 2 receives the authentication request of the proxy requesting individual PR. The control unit 21 of the first server 2 operates as the authentication unit 211 and executes authentication processing of the proxy requesting individual PR. In one example, the control unit 21 may extract the first registered unique information CA10 of the proxy requesting individual PR from the first target information O10 by searching the first target information O10 using the first identifier I10 included in the authentication request as a query. The control unit 21 may compare the extracted first registered unique information CA10 with the first unique information CA1 included in the authentication request. The comparison may be performed appropriately depending on the unique information used. The control unit 21 may determine whether or not authentication of the proxy requesting individual PR is successful depending on the result of the comparison. In step SA420, the control unit 21 reports the authentication result for the proxy requesting individual PR to the management server 1. In one example, the control unit 21 may transmit the authentication result of the proxy requesting individual PR to the management server 1 together with the first identifier I10 of the proxy requesting individual PR. The control unit 21 may transmit the authentication result to the management server 1 regardless of whether the authentication is successful or not, or may transmit the authentication result to the management server 1 only if the authentication is successful.

[0216] On the other hand, in step SB410, the control unit 41 of the first terminal 4 transmits an authentication request including the second identifier I20 and the second unique information CA2 of the target individual TA to the second server 3. In response to this, the control unit 31 of the second server 3 receives the authentication request of the target individual TA. The control unit 31 of the second server 3 operates as the authentication unit 311 and executes the authentication process of the target individual TA. In one example, the control unit 31 may extract the second registered unique information CA20 of the target individual TA from the second target information O20 by searching the second target information O20 using the second identifier I20 included in the authentication request as a query. The control unit 31 may compare the extracted second registered unique information CA20 with the second unique information CA2 included in the authentication request. The comparison may be performed appropriately depending on the unique information used. The control unit 31 may determine whether the authentication of the target individual TA is successful or not depending on the result of the comparison. In step SB420, the control unit 31 reports the authentication result of the target individual TA to the management server 1. In one example, the control unit 31 may transmit the authentication result of the target individual TA to the management server 1 together with the second identifier I20 of the target individual TA. The control unit 31 may transmit the authentication result to the management server 1 regardless of whether the authentication is successful or not, or may transmit the authentication result to the management server 1 only if the authentication is successful.

[0217] The second terminal 5 giving an authentication request to the first server 2 and having the first server 2 transmit the authentication result to the management server 1 is an example of the second terminal 5 transmitting a linking request to the management server 1. The first terminal 4 giving an authentication request to the second server 3 and having the second server 3 transmit the authentication result to the management server 1 is an example of the first terminal 4 transmitting a linking request to the management server 1. That is, when the first authentication method is adopted in setting the linking, the processes of steps SA410, SA420, SB410, and SB420 are an example of the processes of steps S40 and S45. This form of authentication request is an example of a form in which authentication processing is executed together with the linking request.

[0218] The control unit 11 of the management server 1 receives the authentication results for each individual (PR, TA) from each server (2, 3). The control unit 11 may specify the correspondence of the authentication result data by a method such as using the above-mentioned shared information in order to specify the combination of the relevant individuals of the first and second targets currently requesting the establishment of a correspondence relationship. When the authentication of both the proxy requesting individual PR and the target individual TA is established in the received authentication result, the control unit 11 may specify the correspondence of the proxy requesting individual PR and the target individual TA by using the above-mentioned shared information. and the target individual TA. The process of setting the correspondence relationship may be the same as that of the above embodiment. Note that a series of processes from data exchange between the terminals (4, 5) to linking setting may be executed in real time in response to the occurrence of a usage relationship.

[0219] In the first authentication method, in response to the occurrence of a usage relationship between a first target and a second target, the first server 2 and the second server 3 respectively authenticate the first target and the second target. At this time, authentication of the first target is requested by the second terminal 5 of the second target. Authentication of the second target is requested by the first terminal 4 of the first target. In other words, cross authentication is performed in which each party does not proceed with its own authentication, but proceeds with the authentication of the other party. This is expected to ensure security.

[0220] FIG. 13B shows an example of a process of linking when the first authentication method is adopted as the authentication method and the second method is adopted as the verification method of the proxy authority. When the first authentication method is adopted, the system 100 may adopt the second method instead of the first method as the verification method of the proxy authority. When the second method is adopted, in step S20, the control unit 41 of the first terminal 4 may provide the proxy authentication information AU2 to the second terminal 5. The proxy authentication information AU2 may be acquired as appropriate. In one example, in step S10, the first terminal 4 may receive authorization information AG including the authentication information PC1 as the proxy authentication information AU2 from the terminal 6. In another example, the first terminal 4 may acquire the proxy authentication information AU2 from the proxy individual PI at any timing.

[0221] At any timing before executing the process of step S305, the control unit 51 of the second terminal 5 may acquire the authentication information PC1 by the process of step S100. In one example, in the setting of step S10, the target individual TA may be designated, and the terminal 6 may transmit the authentication information PC1 to the second terminal 5 of the designated target individual TA. In this way, the control unit 51 of the second terminal 5 may acquire the authentication information PC1. In another example, in response to the occurrence of a utilization relationship with the representative individual PI (for example, in response to the start of data exchange with the first terminal 4), the control unit 51 of the second terminal 5 may download the authentication information PC1 from an external computer. The control unit 51 of the second terminal 5 may acquire the first unique information CA1 of the representative requesting individual PR together with the authentication information PC1.

[0222] In step S305, the control unit 51 of the second terminal 5 verifies the proxy authority by comparing the proxy authentication information AU2 and the authentication information PC1. If the comparison is successful (verification is successful), the control unit 51 of the second terminal 5 may execute the processes of steps SA410 and SB410 and thereafter together with the control unit 41 of the first terminal 4. On the other hand, if the comparison is unsuccessful, the control unit 51 of the second terminal 5 may prompt the first terminal 4 to resend the proxy authentication information AU2. If the comparison is unsuccessful, the control unit 51 of the second terminal 5 may appropriately end the processing procedure related to the association setting. Other processing procedures when the second method is adopted as the verification method may be the same as those when the first method of FIG. 13A is adopted.

[0223] 13A and 13B are merely examples, and each step may be modified as much as possible. Steps of the above processing steps may be omitted, replaced, or added as appropriate depending on the embodiment. For example, authentication of the second target (target individual TA) may be omitted. Authentication of the proxy individual PI may also be performed in a similar manner to that of the proxy request individual PR.

[0224] Furthermore, regardless of whether or not authentication of the proxy individual PI is performed, the first identifier I10 of the proxy individual PI may be transmitted from the first terminal 4 or the first server 2 to the management server 1. In one example, the first identifier I10 of the proxy individual PI may be transmitted to the management server 1 in at least one of the authentication route of the first target (step SA410, step SA420) and the authentication route of the second target (step SB410, step SB420). In response to this, the management server 1 may As a process for setting the correspondence between the request individual PR and the target individual TA, linking information D10 that further includes the first identifier I10 of the representative individual PI may be generated.

[0225] Furthermore, the transmission path of the authentication result does not need to be limited to the example of Figures 13A and 13B. In another example, the first terminal 4 may receive the authentication result of the target individual TA from the second server 3, and the second terminal 5 may receive the authentication result of the proxy requesting individual PR from the first server 2. In response to this, each terminal (4, 5) may transmit a linking request including the received authentication result of each individual (PR, TA) to the management server 1. Alternatively, one of the first terminal 4 and the second terminal 5 may exchange data on the authentication result with the other terminal, and the other terminal may transmit a linking request including the authentication result of each individual (PR, TA) to the management server 1.

[0226] Furthermore, the transmission path of the first unique information CA1 of the proxy requesting individual PR may be changed as appropriate depending on the embodiment. In another example, the second terminal 5 may transmit an authentication request for the proxy requesting individual PR to the first server 2 without the first unique information CA1 of the proxy requesting individual PR being present. In response to this authentication request, the first server 2 may request the first unique information CA1 from the terminal 6 of the proxy requesting individual PR. The terminal 6 may acquire the first unique information CA1 as appropriate and transmit it to the first server 2. As a result, the first server 2 may acquire the first unique information CA1 to be used for authenticating the proxy requesting individual PR.

[0227] (B) Second authentication method FIG. 14A shows a schematic diagram of an example of a process of linking setting when the second authentication method is adopted. In the example of FIG. 14A, the above-mentioned first method is adopted as a method for verifying the power of attorney, and a situation is assumed in which a form is adopted in which the proxy requesting individual PR and the target individual TA are authenticated when linking is set. In the second authentication method, the management server 1 requests authentication from each server (2, 3) in response to a request from at least one of the first terminal 4 and the second terminal 5. That is, the external server (the first server 2, the second server 3) authenticates each individual (PR, TA) in response to an authentication request included in a linking request transmitted from at least one of the first terminal 4 and the second terminal 5. The data (unique information) used for authentication is the same as that in the first authentication method. The request transmitted from the first terminal 4 and the second terminal 5 to the management server 1 is an example of a linking request including an authentication request.

[0228] First, the processes of steps S10, S20, S301, and S302 may be executed in the same manner as in the first authentication method. After the second terminal 5 receives a response indicating approval, at least one of the first terminal 4 and the second terminal 5 transmits an authentication request including the first identifier I10 of the proxy requesting individual PR, the first unique information CA1 of the proxy requesting individual PR, the second identifier I20 of the target individual TA, and the second unique information CA2 of the target individual TA as a linking request to the management server 1 (steps SC410 and SD410). In response to this, the control unit 11 of the management server 1 receives the authentication request including the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2. The processes of steps SC410 and SD410 are an example of the process of step S40.

[0229] The division of data transmission may be appropriately determined depending on the embodiment. In one example, the second terminal 5 may be responsible for transmitting the first identifier I10 and the first unique information CA1, and the first terminal 4 may be responsible for transmitting the second identifier I20 and the second unique information CA2. For example, in either step S20 or step S302, the control unit 51 of the second terminal 5 may acquire the first identifier I10 and the first unique information CA1 of the proxy requesting individual PR. In step SC410, the control unit 51 of the second terminal 5 may transmit a linking request including the acquired first identifier I10 and first unique information CA1 of the proxy requesting individual PR to the management server 1. On the other hand, in step S20, the control unit 41 of the first terminal 4 may acquire the second identifier I20 and the second unique information CA2 of the target individual TA from either the target individual TA or the second terminal 5. In step SD410, The control unit 41 of the first terminal 4 may transmit to the management server 1 a linking request including the acquired second identifier I20 and second unique information CA2 of the target individual TA.

[0230] The sharing of data transmission need not be limited to this example. In another example, at least one of the first identifier I10 and the first unique information CA1 may be transmitted from the first terminal 4. At least one of the second identifier I20 and the second unique information CA2 may be transmitted from the second terminal 5. When adopting a form of transmitting data in a divided manner, the management server 1 may specify the correspondence of the authentication request data by a method such as using the shared information described above in order to specify the combination of the corresponding individual of the first target and the second target that is currently requesting the setting of the correspondence relationship. In yet another example, the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2 may be transmitted from only one of the first terminal 4 and the second terminal 5.

[0231] In step SC420, the control unit 11 of the management server 1 requests the first server 2 to authenticate the proxy requesting individual PR by transmitting the first identifier I10 and the first unique information CA1 from the received data to the first server 2. In response, the control unit 21 of the first server 2 operates as the authentication unit 211, compares the first unique information CA1 and the first registered unique information CA10, and may determine whether or not the authentication of the proxy requesting individual PR has been successful depending on the result of the comparison. In step SC430, the control unit 21 of the first server 2 returns the authentication result of the proxy requesting individual PR to the management server 1.

[0232] Similarly, in step SD420, the control unit 11 of the management server 1 requests the second server 3 to authenticate the target individual TA by sending the second identifier I20 and the second unique information CA2 to the second server 3. In response, the control unit 31 of the second server 3 operates as an authentication unit 311, and may compare the second unique information CA2 and the second registered unique information CA20, and determine whether or not the authentication of the target individual TA has been successful depending on the result of the comparison. In step SD430, the control unit 31 of the second server 3 sends the authentication result of the target individual TA to the management server 1.

[0233] The control unit 11 of the management server 1 receives authentication results for each individual (PR, TA) from each server (2, 3). If the authentication of both the proxy requesting individual PR and the target individual TA is successful in the received authentication results, the control unit 11 sets a correspondence relationship between the proxy requesting individual PR and the target individual TA. The process of setting the correspondence relationship may be the same as in the above embodiment. Note that a series of processes from data exchange between the terminals (4, 5) to linking setting may be executed in real time in response to the occurrence of a usage relationship. The other configurations may be the same as those of the first authentication method.

[0234] In the second authentication method, in response to the occurrence of a usage relationship between the first target and the second target, authentication of the first target and the second target is performed by the first server 2 and the second server 3, respectively. These two authentications are expected to ensure security.

[0235] FIG. 14B shows a schematic diagram of an example of a process of linking setting in the case where the second authentication method is adopted as the authentication method and the second method is adopted as the verification method of the power of attorney. When the second authentication method is adopted, the system 100 may adopt the second method instead of the first method as the verification method of the power of attorney. As in the first authentication method, in step S20, the control unit 41 of the first terminal 4 may provide the proxy authentication information AU2 to the second terminal 5. At any timing before executing the process of step S305, the control unit 51 of the second terminal 5 may acquire the authentication information PC1 by the process of step S100. The control unit 51 of the second terminal 5 may acquire the first unique information CA1 of the proxy request individual PR together with the authentication information PC1. In step S305, the control unit 51 of the second terminal 5 verifies the power of attorney by comparing the proxy authentication information AU2 and the authentication information PC1. When the comparison is successful (the verification is successful) Then, the processes after step SC410 and step SD410 may be executed. The other procedures may be similar to those in the above-mentioned Figures 13B and 14A.

[0236] Note that the processing procedures of FIG. 14A and FIG. 14B are merely examples, and each step may be modified as much as possible. Steps of the above processing procedures may be omitted, replaced, or added as appropriate depending on the embodiment. For example, similar to the above first authentication method, authentication of the second target (target individual TA) may be omitted. Authentication of the proxy individual PI may also be performed in a similar manner to that of the proxy request individual PR. The management server 1 may generate linking information D10 that further includes the first identifier I10 of the proxy individual PI. The transmission route of the first unique information CA1 of the proxy request individual PR may be modified as appropriate depending on the embodiment. In another example, the first unique information CA1 of the proxy request individual PR may be transmitted from the terminal 6 to the first server 2.

[0237] Furthermore, the transmission path of the authentication result may not be limited to the examples of Figures 14A and 14B. In another example, the authentication process of at least one of the first target and the second target may be executed by the management server 1, not by an external server. For example, the management server 1 may hold at least one of the first registered unique information CA10 and the second registered unique information CA20. Alternatively, the management server 1 may acquire at least one of the first registered unique information CA10 and the second registered unique information CA20 by inquiring of at least one of the first server 2 and the second server 3. In response to this, the control unit 11 of the management server 1 may operate as an authentication unit 115 and execute the authentication process of at least one of the first target and the second target.

[0238] (C-1) Authentication method No. 3-1 Fig. 15A shows a schematic example of a process for linking when the 3-1 authentication method is adopted. The example of Fig. 15A assumes a situation in which the above-mentioned first method is adopted as a method for verifying the power of attorney, and a form of authentication is adopted in which the proxy requesting individual PR and the target individual TA are authenticated when linking is set. The 3-1 authentication method uses a time-limited certificate for authentication instead of unique information. The authentication process is executed by the management server 1.

[0239] The first server 2 is configured to issue a first time-limited certificate CB10 to each individual of the first subjects. The second server 3 is configured to issue a second time-limited certificate CB20 to each individual of the second subjects.

[0240] Each time-limited certificate (CB10, CB20) is configured to expire when its validity period expires. As long as expiration due to the expiration of the validity period can be controlled, the configuration of each time-limited certificate (CB10, CB20) is not particularly limited and may be appropriately selected depending on the embodiment. Each time-limited certificate (CB10, CB20) may include any information. In one example, each time-limited certificate (CB10, CB20) may be configured with a random number, a timestamp, a hash value, etc. Each time-limited certificate (CB10, CB20) may be configured with temporary information such as a one-time password.

[0241] The validity period of each time-limited certificate (CB10, CB20) may be managed as appropriate. Revocation due to the passage of the validity period may be identified as appropriate. For example, whether or not a time-limited certificate in question has expired may be identified by the fact that the expiration date set in the time-limited certificate has passed, the time-limited certificate has been added to a revocation list, the time-limited certificate has been deleted from a validity list, the time-limited certificate has been updated to a new time-limited certificate, information indicating the expiration (e.g., a timestamp) has been added, or the like. When reference information such as a revocation list or a validity list is used to manage the validity period, the reference information may be stored in any storage device accessible from the system 100. Typically, the reference information of each time-limited certificate (CB10, CB20) may be stored in each server (2, 3).

[0242] First, in step SE910, the control unit 61 of the terminal 6 of the proxy request individual PR The control unit 21 of the first server 2 transmits a request for issuing a first time certificate CB10 to the first server 2 in relation to the first identifier I10 of the individual PR. In response to receiving the request, the control unit 21 of the first server 2 issues the first time certificate CB10 in relation to the first identifier I10. In step SE920, the control unit 21 of the first server 2 returns the issued first time certificate CB10 to the terminal 6. In response, the terminal 6 receives the issued first time certificate CB10 from the first server 2. The control unit 61 of the terminal 6 stores the received first time certificate CB10 so that it can be used as the first certificate CB1. In step SE930, the control unit 21 of the first server 2 also notifies the management server 1 of the issued first time certificate CB10. The control unit 21 may notify the management server 1 of the first time certificate CB10 with the first identifier I10.

[0243] Similarly, in step SF910, the control unit 51 of the second terminal 5 of the target individual TA transmits a request for issuing a second time certificate CB20 to the second server 3 in relation to the second identifier I20 of the target individual TA. In response to receiving the request, the control unit 31 of the second server 3 issues the second time certificate CB20 in relation to the second identifier I20. In step SF920, the control unit 31 of the second server 3 returns the issued second time certificate CB20 to the second terminal 5. In response to this, the second terminal 5 receives the issued second time certificate CB20 from the second server 3. The control unit 51 of the second terminal 5 stores the received second time certificate CB20 so that it can be used as the second certificate CB2. Also, in step SF930, the control unit 31 of the second server 3 notifies the management server 1 of the issued second time certificate CB20. The control unit 31 may notify the second time certificate CB20 by attaching a second identifier I20.

[0244] The processes of steps S10, S20, S301, and S302 may be executed in the same manner as the above-mentioned first authentication method, etc. After the second terminal 5 receives the response indicating approval, at least one of the first terminal 4 and the second terminal 5 transmits an authentication request including the first certificate CB1 of the proxy requesting individual PR and the second certificate CB2 of the target individual TA as a linking request to the management server 1 (steps SE410 and SF410). In response to this, the management server 1 receives the first certificate CB1 corresponding to the first time-limited certificate CB10 and the second certificate CB2 corresponding to the second time-limited certificate CB20. The processes of steps SE410 and SF410 are an example of the process of the above-mentioned step S40. The request transmitted from at least one of the first terminal 4 and the second terminal 5 is an example of a linking request including an authentication request.

[0245] The allocation of data transmission may be appropriately determined depending on the embodiment. In one example, the second terminal 5 may be responsible for transmitting the first certificate CB1 of the proxy requesting individual PR, and the first terminal 4 may be responsible for transmitting the second certificate CB2 of the target individual TA. That is, in step SE410, the control unit 51 of the second terminal 5 may transmit a linking request including the first certificate CB1 of the proxy requesting individual PR to the management server 1. In step SF410, the control unit 41 of the first terminal 4 may transmit a linking request including the second certificate CB2 of the target individual TA to the management server 1.

[0246] However, the sharing of data transmission is not limited to this example. In another example, the first certificate CB1 may be transmitted from the first terminal 4. The second certificate CB2 may be transmitted from the second terminal 5. In addition, the identifiers (I10, I20) of each individual (PR, TA) may also be transmitted to the management server 1 together with each certificate (CB1, CB2). In this case, each identifier (I10, I20) and each certificate (CB1, CB2) are an example of data used for authentication. Each identifier (I10, I20) may be transmitted from at least one of the first terminal 4 and the second terminal 5. When adopting a form of transmitting in a divided manner, the management server 1 may specify the correspondence of the authentication request data by a method such as using the shared information described above in order to specify the combination of the individual of the first target and the second target that is currently requesting the setting of the correspondence relationship. In yet another example, the first certificate CB1 and the second certificate CB2 may be transmitted from only one of the first terminal 4 and the second terminal 5.

[0247] Each terminal (4, 5) may acquire each certificate (CB1, CB2) as appropriate. When the second terminal 5 transmits the first certificate CB1 of the proxy request individual PR, the second terminal 5 may acquire the first certificate CB1 together with the approval response in step S302, or may acquire the first certificate CB1 via the first terminal 4 in steps S10 and S20. When the first terminal 4 transmits the first certificate CB1 of the proxy request individual PR, the first terminal 4 may acquire the first certificate CB1 together with the authorization information AG in step S10, or may acquire the first certificate CB1 via the second terminal 5 in steps S302 and S20. When the first terminal 4 transmits the second certificate CB2 of the target individual TA, the first terminal 4 may acquire the second certificate CB2 from the second terminal 5 in step S20.

[0248] The control unit 11 of the management server 1 operates as the authentication unit 115 and collates the received first certificate CB1 with the first time certificate CB10 notified from the first server 2. The control unit 11 of the management server 1 operates as the authentication unit 115 and collates the received second certificate CB2 with the second time certificate CB20 notified from the second server 3. The control unit 11 may appropriately specify the correspondence of the data to be collated. Specifying the correspondence of the data to be collated means determining the combination of the first time certificate CB10 and the first certificate CB1, and the combination of the second time certificate CB20 and the second certificate CB2 to be collated. As with the correspondence of the data of the authentication request, the control unit 11 may specify the correspondence of the data to be collated by a method such as using the shared information. The shared information may be each identifier (I10, I20).

[0249] Furthermore, a method of matching the certificate and the time-limited certificate may be appropriately selected according to the relationship between them. In one example, the time-limited certificate (CB10, CB20) may be used as the certificate (CB1, CB2) as is. In this case, the success or failure of the matching in the authentication may be determined according to whether the time-limited certificate (CB10, CB20) and the certificate (CB1, CB2) match. In another example, the time-limited certificate (CB10, CB20) may be arbitrarily converted, and the converted time-limited certificate (CB10, CB20) may be used as the certificate (CB1, CB2). In this case, the success or failure of the matching in the authentication may be determined according to whether a predetermined relationship is established between the time-limited certificate (CB10, CB20) and the certificate (CB1, CB2). For example, the first time-limited certificate CB10 may be converted into a hash value, and the obtained hash value may be used as the first certificate CB1. Accordingly, whether or not the relationship is established may be determined depending on whether or not the hash value of the first time certificate CB10 matches the first certificate CB1. The conversion may include data manipulation such as deletion and addition. At least one of the first time certificate CB10 and the second time certificate CB20 may be used as a certificate as is, and the other may be used as a certificate after conversion. The conversion process may be performed in each terminal (4, 5, 6) or in each server (2, 3). When the conversion process is performed in each server (2, 3), each terminal (5, 6) may receive the converted time certificate (CB10, CB20) from each server (2, 3).

[0250] The control unit 11 of the management server 1 may determine whether or not the authentication of each individual (PR, TA) is successful depending on the result of each comparison. If the comparison is not successful, the authentication is not successful. If the first time certificate CB10 / second time certificate CB20 have expired due to the expiration of the validity period, the comparison of the first target / second target is not successful. On the other hand, if the first time certificate CB10 and the second time certificate CB20 are valid and each comparison is successful, the authentication of both the proxy request individual PR and the target individual TA is successful. If the authentication of both the proxy request individual PR and the target individual TA is successful, the control unit 11 of the management server 1 sets a correspondence relationship between the proxy request individual PR and the target individual TA. The process of setting the correspondence relationship may be the same as that of the above embodiment. Note that a series of processes from data exchange between the terminals (4, 5) to linking setting may be executed in real time depending on the occurrence of the usage relationship. Other configurations may be the same as the first authentication method, etc.

[0251] In the third-first method, in response to the occurrence of a relationship of use between the first and second targets, Authentication of the first and second targets is performed using time-limited certificates (CB10, CB20). Each time-limited certificate (CB10, CB20) is configured to expire after the validity period. This makes it possible to prevent the same certificate from being used permanently, which is expected to ensure security.

[0252] FIG. 15B shows an example of a process of linking when the 3-1 authentication method is adopted as the authentication method and the above-mentioned second method is adopted as the verification method of the power of attorney. When the 3-1 authentication method is adopted, the system 100 may adopt the second method instead of the above-mentioned first method as the verification method of the power of attorney. As with the above-mentioned first authentication method, in step S20, the control unit 41 of the first terminal 4 may provide the proxy authentication information AU2 to the second terminal 5. At any timing before executing the process of step S305, the control unit 51 of the second terminal 5 may obtain the authentication information PC1 by the process of step S100. The control unit 51 of the second terminal 5 may obtain the first certificate CB1 of the proxy request individual PR together with the authentication information PC1. In step S305, the control unit 51 of the second terminal 5 verifies the power of attorney by collating the proxy authentication information AU2 and the authentication information PC1. If the match is successful (if the verification is successful), the processes in steps SE410 and SF410 and thereafter may be executed. The other procedures may be the same as those in FIG. 15A.

[0253] Note that the processing procedures in Figures 15A and 15B are merely examples, and each step may be modified as much as possible. Steps of the above processing procedures may be omitted, replaced, or added as appropriate depending on the embodiment. For example, similar to the above-mentioned first authentication method, authentication of the second target (target individual TA) may be omitted. Authentication of the proxy individual PI may also be performed in a similar manner to that of the proxy request individual PR. The management server 1 may generate linking information D10 that further includes a first identifier I10 of the proxy individual PI.

[0254] Furthermore, the issuance of each time-limited certificate (CB10, CB20) does not necessarily have to be based on a request (demand) from each terminal (4, 5). Each server (2, 3) may generate each time-limited certificate (CB10, CB20) on its own initiative. In this case, the processes of steps SE910 and SF910 may be omitted.

[0255] Furthermore, the issuance of each time certificate (CB10, CB20) (steps SE910 to SE930, steps SF910 to SF930) may be executed at any timing before the request for linking setting (steps SE410, SF410). In one example, the issuance of each time certificate (CB10, CB20) may be executed in advance before data exchange between the first terminal 4 and the second terminal 5 is executed (step S20). In another example, the issuance may be executed after the start of data exchange between the first terminal 4 and the second terminal 5 and before the linking request is transmitted. From the viewpoint of reducing the number of steps in linking setting, it is preferable to issue each time certificate (CB10, CB20) at the former timing.

[0256] In the authentication method of the above 3-1, the comparison process of each certificate (CB1, CB2) and each time-limited certificate (CB10, CB20), that is, the authentication process of each target, is executed by the management server 1. However, the subject that executes the comparison process does not have to be limited to the management server 1. In another example, the management server 1 may request each server (2, 3) to perform the comparison process by transmitting each certificate (CB1, CB2) to each server (2, 3). In this way, the comparison process may be executed by each server (2, 3). In other words, the authentication process of at least one of the first target and the second target may be executed by an external server. In one example, the control unit 21 of the first server 2 may operate as the authentication unit 211 and may determine whether the authentication of the first target is successful or not by comparing the first certificate CB1 received from the management server 1 with the first time-limited certificate CB10. The control unit 21 may return the authentication result of the first target to the management server 1. The control unit 31 of the second server 3 operates as an authentication unit 311 and authenticates the second certificate received from the management server 1. The control unit 31 may determine whether the authentication of the second target has been successful by comparing the second time certificate CB2 with the second time certificate CB20. The control unit 31 may return the authentication result of the second target to the management server 1. In this case, the notification of each time certificate (CB10, CB20) (steps SE930 and SF930) may be omitted. In another example, the management server 1 may perform authentication processing for at least one of the first target and the second target, and an external server may perform authentication processing for the other target.

[0257] Furthermore, the transmission path of the first certificate CB1 of the proxy requesting individual PR may be changed as appropriate depending on the embodiment. In another example, at least one of the first terminal 4 and the second terminal 5 may transmit an authentication request for the proxy requesting individual PR to the management server 1 without the first certificate CB1 of the proxy requesting individual PR being present. The management server 1 may request the first certificate CB1 from the terminal 6 directly or indirectly via an external server such as the first server 2. In response to this request, the terminal 6 may transmit the first certificate CB1 directly or indirectly to the management server 1. As a result, the management server 1 may obtain the first certificate CB1 to be used for authenticating the proxy requesting individual PR.

[0258] (C-2) Authentication method 3-2 In the above authentication method 3-1, authentication processing of each individual (PR, TA) is executed in the management server 1 in response to a linking request from at least one of the first terminal 4 and the second terminal 5. However, the timing of executing the authentication processing need not be limited to this example. In the authentication method 3-2, authentication processing of at least one of the proxy requesting individual PR and the target individual TA may be executed between at least one of the first server 2 and the second server 3 and at least one of the first terminal 4 and the second terminal 5, using as a trigger for sending a linking request to the management server 1.

[0259] Fig. 16A shows an example of the process of linking settings when the authentication method 3-2 is adopted. Fig. 16A assumes a scene in which authentication processing of the first target (proxy requesting individual PR) is executed.

[0260] First, between the terminal 6 and the first server 2, the processes of steps SE910 and SE920 may be executed in the same manner as in the authentication method of the above-mentioned 3-1. As a result of the execution, a first time certificate CB10 is issued, and the issued first time certificate CB10 is notified to the terminal 6. At this time, the first server 2 may store the issued first time certificate CB10 in association with the first identifier I10. The first time certificate CB10 may be saved as the first target information O10. The notification to the management server 1 (step SE930) may be omitted. The processes of steps S10, S20, and S30 may be executed in the same manner as in the authentication method of the above-mentioned 3-1. Either the first method or the second method may be adopted as the method of verifying the power of attorney. As a result, the second terminal 5 acquires the first identifier I10 and the first certificate CB1.

[0261] In step SG410, the control unit 51 of the second terminal 5 transmits an authentication request including the first identifier I10 and the first certificate CB1 to the first server 2. In response to receiving the authentication request, the control unit 21 of the first server 2 operates as the authentication unit 211 and compares the received first certificate CB1 with the corresponding first time certificate CB10. The corresponding first time certificate CB10 may be acquired as appropriate. In one example, the issued first time certificate CB10 may be stored as the first target information O10, and the control unit 21 of the first server 2 may extract the corresponding first time certificate CB10 by searching the first target information O10 using the first identifier I10 as a query. In step SG420, the control unit 21 of the first server 2 returns the result of the comparison to the second terminal 5. In response, the control unit 51 of the second terminal 5 receives the result of the comparison.

[0262] In the case where the received comparison result indicates that the first certificate CB1 and the first time-limited certificate CB10 do not match, the control unit 51 of the second terminal 5 may end the processing procedure for setting the association as appropriate. In one example, the control unit 51 may request the terminal 6 to resend the first certificate CB1. If the match is successful, the control unit 51 transmits a linking request including the first identifier I10 and the second identifier I20 to the management server 1 (step SG430). The processes of steps SG410, SG420, and SG430 are an example of the processes of steps S40 and S45 described above.

[0263] In response, the management server 1 receives a linking request from the second terminal 5. In response to the linking request, the control unit 11 of the management server 1 sets up a correspondence relationship between the first target (proxy requesting individual PR) and the second target (target individual TA). The process of setting up the correspondence relationship may be similar to that of the above embodiment. Note that a series of processes from data exchange between the terminals (4, 5) to setting up the linking may be executed in real time in response to the occurrence of a usage relationship. Other configurations may be similar to those of the first authentication method, etc.

[0264] The subject of authentication by the 3-2 authentication method does not need to be limited to the first subject. The second subject may also be authenticated by the same method.

[0265] Fig. 16B shows a schematic diagram of another example of the process of linking setting when the 3-2 authentication method is adopted. Fig. 16B assumes a scene in which authentication processing of a second target (target individual TA) is executed. Except for the fact that the first target and the second target are interchanged and processing related to a proxy is omitted, the processing procedure of Fig. 16B may be the same as the processing procedure of Fig. 16A.

[0266] That is, the processes of steps SF910 and SF920 are executed between the second terminal 5 and the second server 3, whereby the second time certificate CB20 is issued and the issued second time certificate CB20 is notified to the second terminal 5. In step S20, the control unit 51 of the second terminal 5 provides the issued second time certificate CB20 to the first terminal 4 as the second certificate CB2. In addition, the control unit 51 of the second terminal 5 provides the second identifier I20 to the first terminal 4. In step SH410, the control unit 41 of the first terminal 4 transmits an authentication request including the second identifier I20 and the second certificate CB2 to the second server 3. In response to this, the control unit 31 of the second server 3 operates as the authentication unit 311 and executes a process of matching the second certificate CB2 and the second time certificate CB20. In step SH420, the control unit 31 of the second server 3 returns the result of the matching to the first terminal 4. If the comparison result shows that the second certificate CB2 and the second time-limited certificate CB20 match, the control unit 41 of the first terminal 4 transmits a linking request including the first identifier I10 and the second identifier I20 to the management server 1 (step SH430). In response to this, the management server 1 receives the linking request from the first terminal 4. In response to the linking request, the control unit 11 of the management server 1 sets a correspondence relationship between the relevant individuals of the first target (proxy requesting individual PR) and the second target (target individual TA).

[0267] In the 3-2 authentication method, the authentication process is executed before the association request is made. This can reduce the processing load on the management server 1. Also, the processing time from the association request to the setting process can be shortened.

[0268] 16A and 16B are merely examples, and each step may be changed as much as possible. Steps of the above-described process may be omitted, replaced, or added as appropriate depending on the embodiment. The processing order of the authentication of the first target and the authentication of the second target is not particularly limited, and may be determined as appropriate depending on the embodiment.

[0269] Furthermore, in the processing procedure of FIG. 16A, the management server 1 may appropriately verify that matching has been established in the first server 2. In one example, the first server 2 may also transmit the result of the matching to the management server 1. For example, the authentication request may further include the second identifier I20. If matching is established, the first server 2 may transmit the result of the matching, including the first identifier I10 and the second identifier I20, to the management server 1. This allows the first server 2 to 1 to validate a linking request for the combination of the first identifier I10 and the second identifier I20 specified by the result of the matching. That is, in one example, verification of the matching success may be configured by receiving the result of the matching. The management server 1 may be configured to hold the result of the matching from the first server 2, accept a request for linking setting for the combination of the first identifier I10 and the second identifier I20 specified by the result of the matching, and reject other requests for linking setting. Similarly, in the processing procedure of FIG. 16B, the management server 1 may appropriately verify that the matching success is achieved in the second server 3.

[0270] 16A and 16B, each server (2, 3) may transmit the authentication result to the management server 1 instead of returning it to each terminal (4, 5). This transmission form is an example of a form in which a linking request is transmitted to the management server 1 via an external server and an authentication process is executed together with the linking request.

[0271] [5 Supplementary Note] The processes and means described in the present disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0272] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Or, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration for implementing each function can be flexibly changed.

[0273] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, a semiconductor drive (e.g., a solid-state drive), and any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0274] 1... management server, 11... control unit, 2...first server, 21...control unit, 3... second server, 31... control unit, 4...first terminal, 41...control unit, 47...positioning module, 5... second terminal, 51... control unit, 57... positioning module, 6... terminal, 61... control unit, PI: (first target) proxy individual, PR: (first target) proxy request individual, TA: (second target) target individual, I10...first identifier, I20...second identifier, O10…First target information, O10A…User information, O20…second target information, O20A…mobile information, D10: Linking information, E10: Various information

Claims

1. Management server, A first terminal of a surrogate individual of the first subject; and A second terminal of the second target individual; Equipped with The first terminal is receiving authorization information notifying the granting of the agency from a terminal of the first target agency requesting individual; When a relationship of use between the surrogate individual and the target individual occurs, data is exchanged with the second terminal; and In the data exchange, providing authority verification information to the second terminal to request verification of the power of attorney; It is configured as follows: the second terminal is configured to verify the power of attorney using the authority verification information in response to the request from the first terminal; At least one of the first terminal and the second terminal is configured to transmit a linking request including a request for authentication of the representative requesting individual to the management server in response to the establishment of the verification by the second terminal, The management server is configured to, in response to authentication of the surrogate requesting individual in response to the authentication request being established, set a correspondence relationship between the surrogate requesting individual and the target individual, thereby validating the surrogate individual's proxy exercise of the authority of the surrogate requesting individual via the target individual. system.

2. The power of attorney has a set expiration date, the management server is further configured to cancel the correspondence between the representative request individual and the target individual upon arrival of the expiration date. The system of claim 1 .

3. The power of attorney has valid authority; The management server is further configured to cancel the correspondence between the surrogate request individual and the target individual in response to the exercise or extinction of the valid authority by the surrogate individual. The system of claim 1 .

4. The management server is further configured to cancel the correspondence relationship between the surrogate request individual and the target individual in response to receiving a cancellation request from the terminal of the surrogate request individual. The system of claim 1 .

5. The management server is further configured to release the correspondence relationship between the surrogate request individual and the target individual in response to the surrogate request individual setting a correspondence relationship between the surrogate request individual and the second target other individual. The system of claim 1 .

6. The authority verification information includes a contact point for performing an authorization process; Verifying said power of attorney Contacting the contact information included in the authority verification information; and receiving an approval response as a result of execution of the approval process; It is composed of: The system of claim 1 .

7. The second terminal is further configured to receive a notification of authentication information from the terminal of the proxy requesting individual, the authority verification information includes proxy authentication information corresponding to the authentication information; The verification of the proxy authority is configured by comparing the proxy authentication information included in the authority verification information with the authentication information notified from the terminal of the proxy requesting individual. The system of claim 1 .

8. transmitting the binding request to the management server includes directly transmitting the binding request to the management server, or indirectly transmitting the binding request to the management server via an external server. The system of claim 1 .

9. The success or failure of the authentication in response to the authentication request is determined by the management server or an external server. The system of claim 1 .

10. The data exchange is performed by short-range wireless communication. The system of claim 1 .

11. the first terminal comprises a positioning module; The first terminal is Measure the current location of the first terminal by a positioning module of the first terminal; Transmitting a measurement result of the current location of the first terminal to the management server; The method further comprises: the second terminal comprises a positioning module; The second terminal is Measure the current location of the second terminal by a positioning module of the second terminal; Transmitting a measurement result of the current location of the second terminal to the management server; The method further comprises: The management server includes: After setting the correspondence relationship between the proxy request individual and the target individual, receiving measurement results of the current locations of the first terminal and the second terminal from the first terminal and the second terminal; determining in real time whether the received measurement results of the current locations of the first terminal and the second terminal satisfy the conditions of the usage relationship; If the measurement results of the current positions of the first terminal and the second terminal satisfy the conditions of the usage relationship, the setting of the correspondence relationship between the proxy request individual and the target individual is maintained, and if not, the correspondence relationship is canceled. Further configured as follows: The system of claim 1 .

12. the first object is a user, the surrogate individual of the first subject is a surrogate user; The first target proxy requesting individual is a proxy requesting user, The second object is a use object used by the user. A system according to any one of claims 1 to 11.

13. The object of use is a moving object. The system of claim 12.

14. A first terminal of a surrogate individual of a first subject is receiving, from a terminal of the first target proxy requesting individual, authorization information notifying the granting of the proxy authority; When a usage relationship occurs between the surrogate individual and a second target individual, data is exchanged with a second terminal of the target individual; In the data exchange, providing authority verification information to the second terminal to request verification of the power of attorney; and in response to the establishment of the verification by the second terminal, sending a linking request including an authentication request for the surrogate request individual to a management server, sending the linking request together with the second terminal, or having the second terminal send the linking request, thereby causing the management server to set a correspondence relationship between the surrogate request individual and the target individual in response to the establishment of authentication of the surrogate request individual in response to the authentication request, thereby enabling the surrogate individual to exercise by proxy the authority of the surrogate request individual via the target individual; In order to execute program.

15. At least one of an expiration date and a validity period is set for the power of attorney. The program according to claim 14.

16. The authority verification information includes a contact performing the authorization process or a proxy authentication information used for the verification. The program according to claim 14.

17. On a second terminal of the second target individual, When a relationship of use occurs between a surrogate individual of a first target and the target individual, data is exchanged between the surrogate individual and a first terminal of the target individual; receiving, in the data exchange, a request for verification of authority from the first terminal, the request carrying authority verification information; Verifying the power of attorney using the authority verification information in response to the request from the first terminal; and in response to the establishment of the verification, sending a linking request including a request for authentication of the surrogate requesting individual to a management server, sending the linking request together with the first terminal, or having the management server send the linking request to the first terminal, thereby causing the management server to set a correspondence relationship between the surrogate requesting individual and the target individual in response to the establishment of authentication of the surrogate requesting individual in response to the authentication request, thereby enabling the surrogate individual to exercise the authority of the surrogate requesting individual via the target individual; In order to execute program.

18. At least one of an expiration date and a validity period is set for the power of attorney.

18. The program according to claim 17.

19. The authority verification information includes a contact point for performing an authorization process; Verifying said power of attorney Contacting the contact information included in the authority verification information; and receiving an approval response as a result of execution of the approval process; It is composed of:

18. The program according to claim 17.

20. The second terminal further receives a notification of authentication information from the terminal of the proxy requesting individual. Let them go, the authority verification information includes proxy authentication information corresponding to the authentication information; The verification of the proxy authority is configured by comparing the proxy authentication information included in the authority verification information with the authentication information notified from the terminal of the proxy requesting individual.

18. The program according to claim 17.

Images