System, management server and program

Abstract

To track use relation between a first object and a second object while securing security, and reduce labor involved therein.SOLUTION: A management server according to one aspect of the present disclosure receives setting of correspondence between a first object and a second object in response to a linking request. When a predetermined condition is not satisfied, the management server acquires authentication results of both the first object and the second object, and sets the correspondence according to the fact that the authentication of both the first object and the second object is established in the acquired authentication results. On the other hand, when the predetermined condition is satisfied, authentication of at least one of the first object and the second object is omitted. The management server acquires authentication result for the other object, and sets the correspondence according to the fact that authentication of the other target is established in the acquired authentication result.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a system, a management server, 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 object 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 reducing the effort required for the tracking. [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 first target, and a second terminal of a second target. At least one of the first terminal and the second terminal is configured to transmit a linking request to the management server in response to the occurrence of a usage relationship between the first target and the second target. The management server is configured to set a correspondence relationship between the first target and the second target based on the linking request. The setting of the correspondence relationship is configured by: acquiring both authentication results of the first target and the second target when a predetermined condition is not satisfied, and setting a correspondence relationship between the first target and the second target in response to authentication of both the first target and the second target being established in the acquired authentication results of the first target and the second target; and omitting authentication of either one of the first target and the second target and acquiring an authentication result of the other target in response to authentication of the other target being established in the acquired authentication result when the predetermined condition is satisfied.

[0006] A management server according to a second aspect of the present disclosure includes a control unit configured to execute, when a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target. The setting of the correspondence relationship is configured by acquiring authentication results of both the first target and the second target when a predetermined condition is not satisfied, and setting a correspondence relationship between the first target and the second target in response to authentication of both the first target and the second target being established in the acquired authentication results of the first target and the second target, and omitting authentication of either one of the first target and the second target and acquiring an authentication result of the other target in response to authentication of the other target being established in the acquired authentication result when the predetermined condition is satisfied.

[0007] A program according to a third aspect of the present disclosure is a program for causing a first terminal of a first target to execute, when a usage relationship occurs between the first target and a second target, a setting of a correspondence relationship between the first target and the second target by transmitting a linking request to a management server, transmitting the linking request in cooperation with a second terminal of the second target, or causing the second terminal to transmit the linking request, to the management server. When a predetermined condition is not satisfied, the linking request includes an authentication request for the first target and the second target, and setting of the correspondence relationship between the first target and the second target is configured to set a correspondence relationship between the first target and the second target in response to both authentications of the first target and the second target executed based on the authentication request being established. When the predetermined condition is satisfied, an authentication request for either the first target or the second target is omitted, the linking request includes an authentication request for the other target, and setting of the correspondence relationship between the first target and the second target is configured to set a correspondence relationship between the first target and the second target in response to authentication of the other target executed based on the authentication request being established.

[0008] A management server according to a fourth aspect of the present disclosure includes a control unit configured to execute, when a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target. The setting of the correspondence relationship is configured to obtain an authentication result of at least one of the first target and the second target when a predetermined condition is not satisfied, and set a correspondence relationship between the first target and the second target in response to authentication being established in the obtained authentication result, and omit authentication of both the first target and the second target when the predetermined condition is satisfied, and set a correspondence relationship between the first target and the second target in response to receiving the linking request.

[0009] A program according to a fifth aspect of the present disclosure is a program for causing a first terminal of a first target to execute, when a usage relationship occurs between the first target and a second target, a linking request to a management server, a linking request to be sent in cooperation with a second terminal of the second target, or a linking request to be sent to the second terminal, thereby causing the management server to set a correspondence relationship between the first target and the second target. When a predetermined condition is not satisfied, the linking request includes an authentication request for at least one of the first target and the second target, and setting the correspondence relationship between the first target and the second target is configured to set a correspondence relationship between the first target and the second target in response to authentication of at least one of the first target and the second target being established based on the authentication request. When the predetermined condition is satisfied, both authentication requests for the first target and the second target are omitted from the linking request, and setting the correspondence relationship between the first target and the second target is configured to set a correspondence relationship between the first target and the second target in response to receiving the linking request. Effect of the Invention

[0010] 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 reducing the effort required for the tracking. [Brief description of the drawings]

[0011] [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. [Diagram 5] FIG. 5 shows an example of a process of canceling a link according to this embodiment. [Figure 6] FIG. 6 shows a schematic diagram of an example of the predetermined condition according to the present embodiment. [Figure 7] FIG. 7 shows a schematic diagram of an example of the predetermined condition according to the present 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 this 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 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 13] FIG. 13 illustrates another example of a situation to which the present disclosure is applied. [Figure 14] FIG. 14 shows an example of an authentication process when the first authentication method is adopted. [Figure 15] FIG. 15 shows an example of an authentication process when the second authentication method is adopted. [Figure 16] FIG. 16 shows an example of an authentication process when the 3-1 authentication method is adopted. [Figure 17A] FIG. 17A illustrates an example of a process of authenticating a first target when the 3-2 authentication method is adopted. [Figure 17B] FIG. 17B illustrates an example of a process of authenticating a second target when the 3-2 authentication method is adopted. [Figure 18A] FIG. 18A illustrates an example of a process of authenticating a first target when the fourth authentication method is adopted. [Figure 18B] FIG. 18B illustrates an example of a process of authenticating a second target when the fourth authentication method is adopted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 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.

[0013] In other words, with the diversification of MaaS (Mobility as a Service), the benefits of efficient payment, etc. From the viewpoint of convenience, it is considered that there will be a demand for tracking the use of a mobile object by a user while ensuring security. In response to this, conventional systems can retain the correspondence between the date and time of use and the user 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 even anticipated. Therefore, conventional systems cannot track the use of a mobile object by a user while ensuring security. It is difficult to achieve this. This problem does not occur only when a vehicle is used. The same problem can occur when a moving object other than a vehicle (e.g., an aircraft, a ship, etc.) is used and when multiple types of moving objects are used. Furthermore, the same problem can occur in any usage situation other than a moving object.

[0014] In contrast, the system according to the first aspect of the present disclosure includes a management server, a first terminal of the first target, and a second terminal of the second target. At least one of the first terminal and the second terminal is configured to transmit a linking request to the management server in response to the occurrence of a usage relationship between the first target and the second target. The management server is configured to set a correspondence relationship between the first target and the second target based on the linking request. The setting of the correspondence relationship is configured by acquiring both authentication results of the first target and the second target when a predetermined condition is not satisfied, and setting a correspondence relationship between the first target and the second target in response to the authentication of both the first target and the second target being established in the acquired authentication results of the first target and the second target, and by omitting authentication of either the first target or the second target and acquiring an authentication result of the other target in response to the authentication of the other target being established in the acquired authentication result when a predetermined condition is satisfied.

[0015] In the first aspect of the present disclosure, the use relationship between the first object and the second object can be tracked by setting a correspondence relationship (linking) between the first object and the second object. In addition, when a predetermined condition is not satisfied, security can be ensured by performing authentication of both the first object and the second object when setting the correspondence relationship. On the other hand, when a predetermined condition is satisfied, authentication of either the first object or the second object can be omitted, thereby reducing the effort. Therefore, according to the first aspect of the present disclosure, the use relationship between the first object and the second object can be tracked while ensuring security, and the effort involved can be reduced.

[0016] 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.

[0017] For example, a management server according to a second aspect of the present disclosure may include a control unit configured to execute, when a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target. Setting the correspondence relationship may be configured by acquiring authentication results of both the first target and the second target when a predetermined condition is not satisfied, and setting a correspondence relationship between the first target and the second target in response to authentication of both the first target and the second target being established in the acquired authentication results of the first target and the second target, and omitting authentication of either the first target or the second target and acquiring an authentication result of the other target in response to authentication of the other target being established in the acquired authentication result when a predetermined condition is satisfied.

[0018] In addition, for example, the program according to the third aspect of the present disclosure may include a program for transmitting a first target to a first terminal of the first target. The program may be a program for causing the management server to set a correspondence relationship between the first target and the second target by transmitting a linking request to the management server, transmitting a linking request in cooperation with a second terminal of the second target, or causing the second terminal to transmit a linking request when a usage relationship occurs between the first target and the second target. When a predetermined condition is not satisfied, the linking request may include an authentication request for the first target and the second target, and setting the correspondence relationship between the first target and the second target may be configured to set the correspondence relationship between the first target and the second target in response to both authentications of the first target and the second target performed based on the authentication request being established. When a predetermined condition is satisfied, an authentication request for either the first target or the second target is omitted, the linking request includes an authentication request for the other target, and setting the correspondence relationship between the first target and the second target may be configured to set the correspondence relationship between the first target and the second target in response to authentication of the other target performed based on the authentication request being established.

[0019] In addition, from the viewpoint of balancing between ensuring security and reducing the effort, the form of omitting authentication need not be limited to the above-mentioned examples. In another example, when a predetermined condition is not satisfied, authentication of at least one of the first target and the second target may be performed, whereas when the predetermined condition is satisfied, authentication of both the first target and the second target may be omitted.

[0020] For example, a management server according to a fourth aspect of the present disclosure may include a control unit configured to execute, when a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target. Setting the correspondence relationship may be configured by acquiring an authentication result of at least one of the first target and the second target when a predetermined condition is not satisfied, and setting the correspondence relationship between the first target and the second target in response to authentication being established in the acquired authentication result, and omitting authentication of both the first target and the second target when the predetermined condition is satisfied, and setting the correspondence relationship between the first target and the second target in response to receiving the linking request.

[0021] Also, for example, a program according to a fifth aspect of the present disclosure may be a program for causing a first terminal of a first target to execute, when a usage relationship occurs between the first target and the second target, a linking request to be sent to a management server, a linking request sent in cooperation with a second terminal of a second target, or a linking request sent to a second terminal, thereby causing the management server to set a correspondence relationship between the first target and the second target. When a predetermined condition is not satisfied, the linking request may include an authentication request for at least one of the first target and the second target, and setting the correspondence relationship between the first target and the second target may be configured to set the correspondence relationship between the first target and the second target in response to authentication of at least one of the first target and the second target being established based on the authentication request. When a predetermined condition is satisfied, both authentication requests for the first target and the second target are omitted from the linking request, and setting the correspondence relationship between the first target and the second target may be configured to set the correspondence relationship between the first target and the second target in response to receiving the linking request.

[0022] 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.

[0023] [1 Application example] FIG. 1 shows a schematic diagram of an example of a scene to which the present disclosure is applied. The system 100 according to this embodiment is composed of 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 a first target VA and a second target WA. The first terminal 4 corresponds to the first target VA, and the second terminal 5 corresponds to the second target WA. The first terminal 4 is provided for each first target VA, and the second terminal 5 is provided for each second target WA.

[0024] In this embodiment, at least one of the first terminal 4 and the second terminal 5 is configured to transmit a linking request to the management server 1 in response to the occurrence of a usage relationship between the first target VA and the second target WA. As an example, a one-to-one usage relationship occurs between the first target VA and the second target WA. That is, a usage relationship occurs between one first target VA and one second target WA. One first target VA is an individual of the first target VA, and one second target WA is an individual of the second target WA. An individual with which a usage relationship has occurred may be referred to as a "corresponding individual" or a "target individual". In response to the occurrence of this usage relationship, at least one of the first terminal 4 corresponding to the corresponding individual of the first target VA and the second terminal 5 corresponding to the corresponding individual of the second target WA transmits a linking request to the management server 1 (step S10).

[0025] In response to this, the management server 1 receives a linking request from at least one of the first terminal 4 of the first target VA and the second terminal 5 of the second target WA. In response to receiving this linking request, the management server 1 accepts the setting of the correspondence between the first target VA and the second target WA (step S20). The management server 1 sets the correspondence (linking) between the first target VA and the second target WA based on the accepted linking request (step S30). In one example, the management server 1 may generate linking information D10 indicating the setting of the correspondence between the first target VA and the second target WA, and may store the generated linking information D10.

[0026] In this embodiment, in relation to the setting of the correspondence relationship, an authentication process of the first target VA and the second target WA is provided. The authentication process of each target (VA, WA) may be performed at any timing before the setting of the correspondence relationship. In addition, a predetermined condition is provided as a condition for enabling the simplification of the authentication process. In response to this, when the predetermined condition is not satisfied, setting the correspondence relationship is configured by acquiring both the authentication results of the first target VA and the second target WA, and setting the correspondence relationship between the first target VA and the second target WA in response to the authentication of both the first target VA and the second target WA being established in the acquired authentication results of the first target VA and the second target WA. On the other hand, when the predetermined condition is satisfied, setting the correspondence relationship is configured by omitting the authentication of one of the first target VA and the second target WA, acquiring the authentication result of the other target, and setting the correspondence relationship between the first target VA and the second target WA in response to the authentication of the other target being established in the acquired authentication result.

[0027] When a usage relationship occurs between the first target VA and the second target WA, data exchange may be executed between the first terminal 4 corresponding to the individual of the first target VA and the second terminal 5 corresponding to the individual of the second target WA. A linking request may be executed in conjunction with this data exchange. A series of processes from the linking request to the linking setting may be executed in real time in response to the occurrence of the usage relationship. After being set, the correspondence relationship (linking) may be released at any timing. In one example, the correspondence relationship may be released in response to the disappearance of the usage relationship.

[0028] Furthermore, as long as each individual with which a correspondence relationship is set can be identified, the format of the information indicating the setting of the correspondence relationship is not particularly limited and may be appropriately determined depending on the embodiment. In one example, a first identifier I10 may be given to each first object VA, and each individual of the first object VA may be identified by the first identifier I10. Similarly, a second identifier I20 may be given to each second object WA, and each individual of the second object WA may be identified by the second identifier I20. In this regard, Accordingly, establishing a correspondence between the first object VA and the second object WA may be configured by establishing a correspondence between a first identifier I10 given to the corresponding individual of the first object VA and a second identifier I20 given to the corresponding individual of the second object WA. That is, the establishment of the correspondence may be expressed using the first identifier I10 and the second identifier I20.

[0029] As described above, in this embodiment, the use relationship between the first target VA and the second target WA can be traced by setting the correspondence (linking) between the first target VA and the second target WA. In addition, in this embodiment, when a predetermined condition is not satisfied, security can be ensured by authenticating both the first target VA and the second target WA when setting the correspondence. On the other hand, when a predetermined condition is satisfied, the authentication of either the first target VA or the second target WA can be omitted, thereby reducing the effort. Therefore, according to this embodiment, the use relationship between the first target VA and the second target WA can be traced while ensuring security, and the effort involved can be reduced.

[0030] (subject) The first object VA and the second object WA may be any object that can establish a relationship of use, and may be selected appropriately according to the embodiment. The first object VA and the second object WA 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 binding to the other, or one connecting to the other. The system 100 of the present disclosure may be used in any situation where a correspondence between two or more objects is tracked.

[0031] (Terminal) Each terminal (4, 5) is related to each target (VA, WA). The relationship between each terminal (4, 5) and each target (VA, WA) is not particularly limited and may be appropriately determined according to the embodiment. In one example, the first terminal 4 may accompany the corresponding first target VA, and the second terminal 5 may accompany the corresponding second target WA. Accompanying may include being temporarily or permanently deployed inside or outside the target, being possessed by the target (human), and being possessed by a human involved with the target (object). Deploying may include loading. Loading may include being placed on the target at all times, as well as being placed on the target at least temporarily when the target is used. Loading may include being possessed by a user of the target. In addition, either the first terminal 4 or the second terminal 5 may be the target itself. In addition, regarding each terminal (4, 5), multiple terminals may be used as terminals of the same individual, such as when one user shares an account between multiple terminals. In this case, multiple terminals used in the same entity may be interpreted as one terminal of one entity.

[0032] (1st server / 2nd server) In one example, first target information O10 regarding the first target VA may be used to indicate details of each individual of the first target VA. The first target information O10 may include a first identifier I10. The first target information O10 may include information (such as registered unique information) used to authenticate the first target VA. Similarly, second target information O20 regarding the second target WA may be used to indicate details of each individual of the second target WA. The second target information O20 may include a second identifier I20. The second target information O20 may include information used to authenticate the second target WA. 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).

[0033] 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.

[0034] 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.

[0035] In addition, the first server 2 may be involved in the authentication of the first target VA. 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 is successful for the first target VA, the first server 2 is an example of an external server (external authentication server) that determines whether the authentication is successful for the first target VA. The second server 3 may be involved in the authentication of the second target WA. When determining whether the authentication is successful for the second target WA, the second server 3 is an example of an external server (external authentication server) that determines whether the authentication is successful for the second target WA.

[0036] (identifier) In one example, each identifier (I10, I20) may be used to identify each individual of each target (VA, WA). As long as each identifier (I10, I20) can identify each individual of each target (VA, WA), the data format and configuration may not be particularly limited and may be appropriately selected according to 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 target (VA, WA) and information derived from each terminal (4, 5). 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 the target, the uniquely assigned identification information may include information held by the IC tag. The information from each terminal (4, 5) includes, for example, a MAC address (Media Access Control address), terminal identification information (IMEI: International Mobile Equipment Identifier, IMSI: It may be an International Mobile Subscriber Identity, MEID: Mobile Equipment Identifier, ICCID: Integrated Circuit Card ID, or other serial number).

[0037] (Management Server) The management server 1 is configured to set a correspondence relationship between the first target VA and the second target WA in response to a linking request from at least one of the first terminal 4 and the second terminal 5. 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, sending a linking request to the management server 1 means sending the linking request directly to the management server 1, or sending the linking request indirectly to the management server 1 via an external server. The external server may include, for example, a first server 2, a second server 3, etc. In addition, in one example, the indirect transmission may be configured by simply relaying the linking request by the external computer. In another example, the indirect transmission may be configured by sending a request for processing related to linking to the external computer and having the external computer transmit some information to the management server 1 according to the result of the execution, such as requesting each server (2, 3) to authenticate each target (VA, WA) and having the server transmit the authentication result to the management server 1. In other words, 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.

[0038] The management server 1 may receive a linking request (a request for linking setting) in response to the occurrence of a usage relationship, and may set a correspondence relationship between the relevant individuals of the first target VA and the second target WA 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 usage 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 an arbitrary 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. However, the method of specifying the relevant individual to be processed is not limited to this example, and may be appropriately changed depending on the embodiment. In another example, at least one of the first identifier I10 and the second identifier I20 may be omitted by using alternative information in at least one of the linking request and the release request. For example, an identifier may be assigned as alternative information to the combination (linking setting) of the relevant individuals of the first target VA and the second target WA. The identifier may be assigned at any time, for example, when the linking is initially set. At least one of the linking request and the release request may be configured to include this identifier, thereby specifying the corresponding individual of each target (VA, WA) to be processed, without including at least one of the first identifier I10 and the second identifier I20.

[0039] The management server 1 may be configured with one or more server devices. In this embodiment, the management server 1 may be configured to record information regarding the occurrence and disappearance of a correspondence relationship between a first target VA and a second target WA as association information D10. The association information D10 may be stored in a memory resource disposed at least inside and 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.

[0040] 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 VA and the second object WA. As a specific example, the linking information D10 may be used to enable the authority linked to either one of the first object VA and the second object WA (the first object information O10 and the second object information O20) to be exercised from the other object while the corresponding relationship between the first object VA and the second object WA is set. In other words, the linking information D10 may be used to enable the authority of either one of the first object VA and the second object WA to be exercised from the other object according to the linking between the first object VA and the second object WA (FIG. 2 described later).

[0041] 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 relevant individual to indicate the combination of the first object VA and the second object WA for which a correspondence has been 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 information on the first identifier I10 and the second identifier I20 for which a correspondence has been set in advance, 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 Alternatively, information on at least one of the first identifier I10 and the second identifier I20 that specifies the identifier may be stored in advance.

[0042] 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 of them in a state in which they can execute 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 association (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 they can execute information processing related to the association.

[0043] (Operation example) In one example, one of the first target VA and the second target WA may be a user. The 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 target VA and the second target WA may be a usage object used by the user. The one of the first terminal 4 and the second terminal 5 corresponding to the usage object may be a loading terminal loaded on the usage object. According to one example of the present embodiment, it is possible to track the usage relationship between the user and the usage object.

[0044] 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.

[0045] 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 VA is a user, and the second object WA is a mobile 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 mobile 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 WA may be a user, and the first object VA may be a mobile object.

[0046] When the first target VA is a user, an example of the first terminal 4 is a user terminal. The 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. Typically, the user terminal may be possessed by a user who is the target of association (each individual of the first target VA). The user's account may be shared among multiple computers, and accordingly, each computer sharing the account may be used as a user terminal (first terminal 4) of the same user.

[0047] 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, or identification information of a user terminal (for example, The first target information O10 may be, for example, a user ID, a MAC address, a 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 may be associated with various information E10 for exercising the authority. The various information E10 may include, for example, information on public personal authentication, payment information, other service-related information, etc. The information on public personal authentication may include, for example, a personal number, etc. The payment information may include, for example, credit card information, Internet banking information, electronic payment information, etc. The other service-related information may include, for example, information on 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 (vehicle manufacturer, service management company, etc.), etc. The first server 2 may be called a user ID server, a my ID server, etc.

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

[0049] 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 the mobile body. In the example of FIG. 2, depending on the linking setting between the user and the mobile body, at least a part of the authority of various information E10 associated with the user information O10A may be enabled (activated) to be exercised by the mobile body. The second server 3 may be deployed by a public institution, a neutral institution, each business operator (vehicle manufacturer, service operator, etc.), etc. The second server 3 may be called a mobile body ID server, a car ID server, etc.

[0050] 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.

[0051] 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 use 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 use. The start and end of use 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 use may be detected in response to the execution of data exchange between the first terminal 4 and the second terminal 5.

[0052] 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.

[0053] In the system 100, the type of the usage object (whether it is a regular usage object or a temporary usage object) may or may not be distinguished. When distinguishing the type of the usage object, the system 100 may determine the type of the usage object by any method. In one example, the target information (mobile body information, etc.) may include information indicating the type of the usage object, and the system 100 may determine the type of the usage object based on this information. In another example, the type of the usage object may be determined from information such as an identifier and attribute information. In another example, information transmitted from at least one of the first terminal 4 and the second terminal 5 to the management server 1 may include information indicating the type of the usage object, and the system 100 may determine the type of the usage object based on this information. In another example, when the operating organization of the server (the second server 3 in the example of FIG. 2) that handles the information of the usage object is determined according to the type of the usage object, the type of the usage object may be determined according to the affiliation of the operating organization of the server.

[0054] Furthermore, the system 100 may switch, for example, the process of linking, the condition for releasing the linking, the method of managing the linking information D10, the form of authentication process, and the like, depending on the type of the identified use object.

[0055] In addition, the application scene of the system 100 of the present disclosure may not be limited to a scene of tracking a relationship between a user and a usage object. In another example, both the first object VA and the second object WA may be robotic devices configured to operate autonomously by automatic control. The robotic device may include a moving body such as an autonomous 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.

[0056] As a specific example, one of the first target VA and the second target WA may be a large automated vehicle, and the other may be a small automated vehicle. The large automated vehicle may be configured to accommodate multiple small automated vehicles. The small automated vehicle may not be able to ride in multiple large automated vehicles at the same time (i.e., at one time, the small automated vehicle is only accommodated in one large automated vehicle). Accordingly, the first target VA may be a small automated vehicle, and the second target WA may be a large automated vehicle. The large automated vehicle may collect, transport, and release each small automated vehicle as appropriate. Each small automated vehicle may be operated as appropriate at the release destination. In this case, the system 100 of the present disclosure may be configured to track the operation status (e.g., whether or not it is being transported) by setting the correspondence relationship between the large automated vehicle and the small automated vehicle, switching the state, and canceling it.

[0057] (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 is expressed using a first identifier I10 and a 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 object VA and the corresponding individual of the second object WA to which the correspondence (link) is set. The setting time indicates the time when the correspondence is set. The setting time may be configured by a time stamp. The release time indicates the time when the correspondence is released. The value of the release time may be added when a process of releasing the correspondence is executed. The method of expressing the release is not limited to this example. In another example, the release time may be replaced by at least one of an expiration date and a flag. The expiration date indicates a period during which the setting of the correspondence 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 the expiration date is not reached or not. The flag indicates whether the correspondence has been released. The flag may be set when a process for releasing the correspondence is executed. In yet another example, the association information D10 includes a field for the release time, as well as a field for the expiration date and a field for the flag. It is possible to include either one or the other. Note that, as long as it is possible to indicate the setting of the correspondence relationship, 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 the usage object is a regular usage object or a temporary usage object). The type of the usage object does not necessarily have to be identified by separate information. For example, the type of the usage object may be identified by information such as an identifier.

[0058] 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 held in any database platform. In one example, the linking information D10 may be held in a relational database such as a table format. In another example, the linking information D10 may be held in a blockchain platform. In this case, each transaction of linking setting and release may be accumulated in the blockchain as the linking information D10. For example, the transaction of linking setting may include a first identifier I10, a second identifier I20, and a setting time. The transaction of releasing the linking may include a first identifier I10, a second identifier I20, and a release time (or information indicating release).

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

[0060] FIG. 3B is a schematic diagram showing 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), 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, sex, 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 authority of the target, information indicating association with various information E10, and the like. Note that the configuration of the user information O10A is not limited to the example of FIG. 3B, and may be appropriately changed according to the embodiment. For example, the user information O10A (first target information O10) may further include information (for example, registered unique information, etc.) used for authenticating the user (first target VA).

[0061] 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.

[0062] (Second target information) The second object information O20 may include any information related to the second object WA. The second object information O20 may include, for example, the second identifier I20, attribute information of the second object WA, 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.

[0063] FIG. 3C is a schematic diagram showing an example of mobile object information O20A according to the present embodiment. In the example shown in FIG. 3C, the mobile object information O20A includes a mobile object ID (second identifier I20) and attribute information. The attribute information includes a number, a type (type of object), a type of mobile object, and owner information. If the mobile object is a vehicle, the number may be a vehicle registration number. The type may be defined arbitrarily. In one example, the type is 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 object, etc. In response to this, the second target WA (mobile object) may be identified as a constantly used object or a temporarily used object by the attribute information of the type. However, the method of identifying whether the second target WA is a constantly used object or a temporarily used object is not limited to this example, and may be appropriately selected according to the embodiment. In another example, the second target WA may be identified as a constantly used object or a temporarily used object by other information such as an identifier. The mobile object type indicates, for example, a type such as a car model. When the mobile object type and the type (type of object) are the same, the mobile object type field may be omitted. The owner information may include any information regarding the owner of the mobile object. The owner information may include, for example, personal information of the owner such as name, address, age, sex, contact information, etc. The owner may be a corporation. Note that the configuration of the mobile object information O20A is not limited to the example of FIG. 3C, and may be appropriately changed according to the embodiment. For example, the mobile object information O20A (second target information O20) may further include information (for example, registered unique information, etc.) used for authenticating the mobile object (second target WA). The configuration of the attribute information may also be changed as appropriate. For example, the mobile object information O20A (attribute information) may further include information related to the mobile object terminal, such as contact information for the mobile object terminal.

[0064] 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.

[0065] (Data Exchange) In this embodiment, a series of processes related to the association setting may be started with a data exchange between the first terminal 4 and the second terminal 5 as a trigger. That is, when a usage relationship occurs between the first target VA and the second target WA, the first terminal 4 and the second terminal 5 may be configured to execute data exchange. The occurrence of the usage relationship (start of usage) may be detected by this data exchange. According to one example of this embodiment, it can be expected that the occurrence of the usage relationship can be easily detected by the data exchange.

[0066] 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.

[0067] FIG. 4 shows a schematic diagram of an example of data exchange according to the present embodiment. In this example of the present embodiment, the first terminal 4 may include a short-range wireless communication module 431. The second terminal 5 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. Examples of short-range wireless communication include NFC, Bluetooth (registered trademark), Wi-fi (registered trademark), and RFID (Radio-Frequency Identification). In one example of this embodiment, the occurrence of a usage relationship can be detected by using data exchange via short-distance wireless communication as a trigger. Since it can be guaranteed that the first terminal VA and the second terminal 5 exist, it can be expected that the occurrence of a usage relationship between the first target VA and the second target WA can be properly detected.

[0068] The association request may include at least one of the first identifier I10 and the second identifier I20. When the association request includes the first identifier I10, 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 identifier I10 may be stored in advance in a memory resource of the first terminal 4. The first terminal 4 may acquire the first identifier I10 from the memory resource. In another example, the first terminal 4 may acquire the first identifier I10 using an input device, a sensor, or the like. When the first identifier I10 is transmitted from the second terminal 5, the second terminal 5 may receive the first identifier I10 from the first terminal 4 during data exchange, or may acquire the first identifier I10 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 from the first terminal 4 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 from either the first target VA or the first terminal 4 using a device such as an input device or a sensor. Acquiring from the first target VA may include acquiring the first identifier I10 by the human associated with the second target WA operating a device on behalf of the human associated with the second target WA when there is a human associated with the second target WA (e.g., the second target WA is a human, the second target WA is operated by a human, etc.) and the first target VA is an object.

[0069] Similarly, 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 be given the second identifier I20 by the second terminal 5 during data exchange, or may acquire it by a spontaneous operation. In one example, the first terminal 4 may acquire the second identifier I20 from the second terminal 5 by 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 WA or the second terminal 5 using a device such as an input device or a sensor. Acquiring from the second object WA may include acquiring the second identifier I20 by the human associated with the first object VA operating a device on its behalf when there is a human associated with the first object VA (e.g., the first object VA is a human, the first object VA is operated by a human, etc.) and the second object WA is an object.

[0070] 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. You may obtain it as appropriate.

[0071] 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 WA) by the user (first target VA) inputting the vehicle registration number via the input device.

[0072] 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.

[0073] (Notification processing) When at least one of the processes of setting and releasing 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 depending on the embodiment. In one example, the management server 1 may directly notify at least one of the first terminal 4 and the second terminal 5. In another example, 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).

[0074] 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 of 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).

[0075] (Authentication process) The authentication of the first target VA and the second target WA may be performed in any manner (specific examples are described below). The authentication process of the first target VA may be performed before or after the authentication process of the second target WA. The authentication process of the first target VA may be performed at least partially in parallel with the authentication process of the second target WA.

[0076] The authentication process of the first target VA and the second target WA may be executed by at least one of the management server 1, an external server (for example, the first server 2, the second server 3), the first terminal 4, and the second terminal 5. Moreover, the authentication process of the first target VA and the second target WA may be executed at any timing before the correspondence is set. In one example, the authentication of at least one of the first target VA and the second target WA may be executed before issuing a linking request. In another example, the authentication of at least one of the first target VA and the second target WA may be requested together with the linking request and executed together with the process related to the linking setting. Requesting together with the linking request may include the authentication request being included in the linking request. The authentication request may be referred to as an authentication request. In yet another example, the authentication of at least one of the first target VA and the second target WA may be started in response to a request from the management server 1 or the external server after the linking request is transmitted. In response to these, in the management server 1, the authentication result may be acquired before receiving the linking request, may be acquired together with the linking request, or may be acquired after receiving the linking request. The authentication result is included in the linking request, and thus, is associated with the linking request. The authentication result may be acquired together with the binding request, or may be acquired separately from the binding request. Furthermore, when authentication is not established, acquiring the authentication result in the management server 1 may include acquiring an authentication result indicating that authentication is not established, and the authentication result not reaching the management server 1 (the authentication result is not acquired).

[0077] In one example, the success or failure of authentication of the first target VA and the second target WA may be determined by the management server 1 or an external server. Determining the success or failure of authentication corresponds to executing an authentication process. In one example, the authentication process of both the first target VA and the second target WA may be executed by either the management server 1 or the external server. In another example, the authentication process of one of the first target VA and the second target WA may be executed by the management server 1, and the authentication process of the other may be executed by the external server. The external server may be, for example, the first server 2, the second server 3, etc. Obtaining the authentication result in the management server 1 may be configured by obtaining the authentication result by executing the authentication process in the management server 1, or by obtaining the authentication result from the external server. For example, at least one terminal of the first target VA and the second target WA may transmit a linking request including an authentication request to the management server 1. The authentication request of each target (VA, WA) may include data (for example, an identifier, unique information, a certificate, etc.) used to authenticate each target (VA, WA). 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, at least one of the terminals 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 directly send the authentication result to the management server 1, or may send the authentication result to the management server 1 via an external computer (for example, at least one of the terminals, etc.). As described above, the timing of sending the authentication request is not limited to this example. The authentication request may be sent in data communication with the management server 1 or the external server before or after issuing the linking request. In one example of this embodiment, security can be expected to be ensured by executing the authentication process on the server side.

[0078] In another example, the authentication process of at least one of the first target VA and the second target WA may be executed by at least one of the first terminal 4 and the second terminal 5. Acquiring the authentication result in the management server 1 may include acquiring the authentication result from at least one of the terminals. For example, at least one of the terminals may execute the authentication process of at least one of the targets as a spontaneous operation. Also, for example, at least one of the terminals may execute the authentication process in response to a request from the management server 1 or an external server. At least one of the terminals may appropriately transmit the authentication result to the management server 1 together with the association request or separately from the association request. Among the first terminal 4 and the second terminal 5, the terminal that executes the authentication process and the terminal that transmits the authentication result may be the same or different. When the terminal that executes the authentication process and the terminal that transmits the authentication result are different, the authentication result may be appropriately exchanged between the terminals (4, 5).

[0079] (Unlink) In this embodiment, the management server 1 may be configured to 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.

[0080] (I) Request for cancellation In one example, the release request may be configured to indicate the correspondence relationship of the release target by including at least one of the first identifier I10 and the second identifier I20. In another example, the release request may be configured to indicate the correspondence relationship of the release target by including replacement information.

[0081] When the first terminal 4 transmits an unlock 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 an unlock request, the first terminal 4 may acquire the second identifier I20 from the memory resource. Also, when the first terminal 4 transmits an unlock request including the first identifier I10, the first terminal 4 may acquire the first identifier I10 at any timing. In one example, the first identifier I10 may be stored in advance in the memory resource. The first terminal 4 may acquire the first identifier I10 from the memory resource.

[0082] Similarly, when the second terminal 5 transmits an unlock request including the first identifier I10, the second terminal 5 may acquire the first identifier I10 at any timing. In one example, when making a linking request, the second terminal 5 may acquire the first identifier I10 and store the acquired first identifier I10 in the memory resource. In the case of an unlock request, the second terminal 5 may acquire the first identifier I10 from the memory resource. Also, when the second terminal 5 transmits an unlock 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 acquire the second identifier I20 from the memory resource.

[0083] FIG. 5 is a schematic diagram showing an example of a process of untying according to the present embodiment. In the example of FIG. 5, 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. Also, the second terminal 5 may instruct 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 binding information D10 and releases the correspondence specified by the identifier included in the release request. After this release process, the management server 1 may send a notification indicating the result of the release process to at least one of the first terminal 4 and the second terminal 5, in the same manner as when the binding was set.

[0084] In one example, the process of the release request may include an authentication process of at least one of the first target VA and the second target WA. The authentication process at the time of release may be similar to the authentication process at the time of the above-mentioned link 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.

[0085] 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 VA and the second target WA is a user, an release request may be transmitted from at least one of the first terminal 4 and the second terminal 5 by the user operating at least one of the first terminal 4 and the second terminal 5. 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, an arbitrary information processing may be executed in at least one of the first terminal 4 and the second terminal 5. 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 appropriately between data exchange when setting the association and data exchange when releasing the association. For example, in the example of FIG. 2, In the above, 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.

[0086] (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.

[0087] 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.

[0088] In another example, the number of correspondences that can be set for the same individual of each target (VA, WA) 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 VA and the second target WA 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.

[0089] For example, as in the example of FIG. 2, a scene is assumed in which the first object VA is a user and the second object WA 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).

[0090] 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).

[0091] The same can be said about users. That is, The number 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 extracted correspondence relationships. 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.

[0092] 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. According to an example of this embodiment, it is possible to track the disappearance of the usage relationship between the first target VA and the second target WA. Note that the association information D10 after the correspondence relationship is cancelled may be saved as history.

[0093] (Normal processing / Simple processing) In this embodiment, if a certain condition is not met, authentication processing of both the first target VA and the second target WA is executed. On the other hand, if a certain condition is met, authentication processing of either the first target VA or the second target WA is omitted. In the following, for convenience of explanation, the processing of the former route in which authentication processing of both the first target VA and the second target WA is executed (i.e., authentication processing is not omitted) is also referred to as "normal processing of linking setting". The processing of the latter route in which authentication processing of either the first target VA or the second target WA is omitted and a correspondence relationship is set is also referred to as "simplified processing of linking setting".

[0094] Omitting authentication may include omitting acquisition of authentication results. Omitting authentication in the management server 1 may include the management server 1 omitting execution of authentication processing, and the management server 1 omitting acquisition of authentication results executed in devices other than the management server 1. In the latter case, execution of authentication processing may be omitted in the other devices.

[0095] Switching between the normal processing and the simplified processing may be performed by any method. In one example, when performing the authentication processing, at least one of the management server 1, the external server (the first server 2, the second server 3, etc.), the first terminal 4, and the second terminal 5 may determine whether or not a predetermined condition is satisfied. As a result of this determination processing, whether or not to execute the simplified processing may be switched. Any of the devices may determine whether or not a predetermined condition is satisfied based on at least one of information held by itself and information provided by another device. The information used for the determination may be appropriately selected according to the predetermined condition. In another example, for example, a program including a mode for executing the simplified processing is installed only in a terminal that may satisfy the predetermined condition, such as a terminal of a use object that allows the simplified processing, and whether or not to execute the simplified processing may be switched by the operation of this terminal. The processing of the mode for executing the simplified processing may include, for example, storing information of the other party to be associated, transmitting an association request by the simplified processing, and the like. As described above, switching between normal processing and simplified processing may be achieved as a result of executing any information processing such as a judgment processing, or may be achieved by satisfying certain conditions without involving information processing.

[0096] The linking request by the simplified processing may be transmitted from at least one of the first terminal 4 and the second terminal 5. At least one of the first terminal 4 and the second terminal 5 may transmit the linking request by the simplified processing directly to the management server 1, or may transmit it indirectly to the management server 1 via an external computer (e.g., an external server such as the first server 2 or the second server 3). When the authentication processing is performed by an external server, omitting authentication may include omitting data communication with the external server, and performing data communication with the external server but omitting the execution of the authentication processing and performing the next information processing.

[0097] As an example, in a case where the authentication process is performed by the management server 1 or an external server, The first terminal 4 of the first target VA may be configured to execute, when a usage relationship occurs between the first target VA and the second target WA, by sending a linking request to the management server 1, sending a linking request in cooperation with the second terminal 5 of the second target WA, or causing the second terminal 5 to send a linking request, so as to cause the management server 1 to set a correspondence relationship between the first target VA and the second target WA. If a predetermined condition is not satisfied, the linking request may include an authentication request for the first target VA and the second target WA. The authentication process of each target (VA, WA) in response to the authentication request may be executed by at least one of the management server 1 and an external server (the first server 2, the second server 3, etc.). The setting of the correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to the authentication of both the first target VA and the second target WA executed based on the authentication request being established. On the other hand, if a predetermined condition is satisfied, the authentication request for one of the first target VA and the second target WA may be omitted, and the linking request may include an authentication request for the other target. Setting a correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to the authentication of the other target being established based on the authentication request.

[0098] Similarly, when the authentication process is performed by the management server 1 or an external server, the second terminal 5 of the second target WA may be configured to execute, when a usage relationship occurs between the first target VA and the second target WA, to cause the management server 1 to set a correspondence relationship between the first target VA and the second target WA by transmitting a linking request to the management server 1, transmitting a linking request in cooperation with the first terminal 4 of the first target VA, or causing the first terminal 4 to transmit a linking request. If a predetermined condition is not satisfied, the linking request may include an authentication request for the first target VA and the second target WA. The authentication process of each target (VA, WA) in response to the authentication request may be executed by at least one of the management server 1 and an external server (the first server 2, the second server 3, etc.). The setting of the correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to the authentication of both the first target VA and the second target WA executed based on the authentication request. On the other hand, if a predetermined condition is satisfied, the authentication request for one of the first target VA and the second target WA may be omitted, and the linking request may include an authentication request for the other target. Setting a correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to the authentication of the other target being established based on the authentication request.

[0099] Whether the processing to be executed is simplified processing or normal processing may be appropriately determined. In one example, when adopting a form in which the authentication processing is executed in at least one of the management server 1 and the external server, at least one of the management server 1 and the external server may determine whether the simplified processing or normal processing is executed according to information included in a linking request from at least one of the first terminal 4 and the second terminal 5. For example, the linking request may include information indicating whether the processing to be executed is simplified processing or not, and whether the simplified processing or normal processing is executed may be determined according to this information. In addition, for example, whether the simplified processing or normal processing is executed may be determined according to information on at least one of the first target VA and the second target WA, such as the first identifier I10, the second identifier I20, or a combination thereof.

[0100] In one example, the linking request by simplified processing may include the first identifier I10 and the second identifier I20. The first identifier I10 and the second identifier I20 included in the linking request may be acquired from at least one of the terminals (4, 5) and the external server in the process of being sent from at least one of the first terminal 4 and the second terminal 5 to the management server 1. However, as described above, the configuration of the linking request by simplified processing is not limited to this example. In another example, In a linking request by simplified processing, at least one of the first identifier I10 and the second identifier I20 may be omitted by using substitute information.

[0101] Also, in one example, in the simplified processing, the transmission form of the authentication process of the other of the first target VA and the second target WA may be the same as or different from the transmission form of the normal processing. For example, in the normal processing, a form is assumed in which the first terminal 4 requests the second server 3 to authenticate the second target WA, and the second terminal 5 requests the first server 2 to authenticate the first target VA. In this case, in one example, in the simplified processing, the first terminal 4 may request the second server 3 to authenticate the second target WA. Alternatively, the second terminal 5 may request the first server 2 to authenticate the first target VA. In another example, in the simplified processing, the first terminal 4 may request the first server 2 to authenticate the first target VA. Alternatively, the second terminal 5 may request the second server 3 to authenticate the second target WA.

[0102] As an optional configuration, at least one of the management server 1 and the external server (first server 2, second server 3, etc.) may acquire identification information (MAC address, terminal identification information, etc.) of at least one of the first terminal 4 and the second terminal 5 for which simplified processing is permitted as a registration process of targets for which simplified processing is permitted, and store the acquired identification information. This registration process may be executed at any timing, such as when setting up a past association. At least one of the management server 1 and the external server may be configured to accept a request for setting up association using simplified processing only from a terminal identified by the identification information.

[0103] In one example, the trigger of the request for the simplified processing of the linking setting may be the same as that of the normal processing. That is, the data exchange between the first terminal 4 and the second terminal 5 may be used as a trigger to cause at least one of the first terminal 4 and the second terminal 5 to transmit a request for the simplified processing of the linking setting. However, the trigger of the simplified processing may not be limited to such an example. In another example, when at least one of the first target VA and the second target WA is a user, a request for the simplified processing of the linking setting may be transmitted from at least one of the first terminal 4 and the second terminal 5 by the user's operation of the terminal. That is, the trigger of the request for the simplified processing of the linking setting may be an operation by the user. In another example, the trigger of the request for the simplified processing of the linking setting may be an instruction by another application (such as a scheduler). In another example, an arbitrary information processing may be executed by at least one of the first terminal 4 and the second terminal 5 in response to the occurrence of a usage relationship. This optional information processing may be used as a trigger to transmit a request for linking setting by simplified processing from at least one of the first terminal 4 and the second terminal 5.

[0104] In addition, in one example, the process of canceling the correspondence relationship set by the simplified process (the process of canceling for the simplified process) may be the same as the process of canceling the association in the normal process described above (the process of canceling for the normal process). However, the process of canceling for the simplified process may not necessarily match the process of canceling for the normal process. The correspondence relationship set by the simplified process may be canceled as appropriate. In another example, when the transmission route of the request to set the correspondence relationship by the simplified process is different from the transmission route of the request to cancel for the normal process, the transmission route of the request to cancel for the simplified process may be aligned with the transmission route of the request to set the correspondence relationship by the simplified process.

[0105] In the simplified processing, the target for which the authentication process is omitted may be either the first target VA or the second target WA, and may be appropriately selected depending on the embodiment. The target for which the authentication process is omitted may be selected, for example, depending on the type, relationship, etc. of each target (VA, WA). In one example, the first target VA may be a user, and the second target WA may be a usage object used by the user. When a predetermined condition is satisfied, the authentication of either the first target VA or the second target WA (the authentication that is omitted) may be the authentication of the usage object. The authentication of the other target (the authentication that is not omitted) may be the authentication of the user. According to one example of this embodiment, the procedure is simplified by omitting the authentication of the usage object while ensuring security by user authentication. This can reduce the time required for

[0106] (Prescribed conditions) The predetermined condition specifies whether the normal process or the simplified process is to be executed. The predetermined condition may be appropriately determined according to the embodiment. In one example, when the occurrence and disappearance of a usage relationship is repeated between the same combination of the first target VA and the second target WA, the system 100 may execute the authentication process of the first target VA and the second target WA each time, and repeat the setting and cancellation of the correspondence relationship. However, when the occurrence and disappearance of the usage relationship are repeated frequently, the same authentication process will be executed each time, which may be troublesome. Therefore, it is desirable that the predetermined condition is specified so that the simplified process is selected for the combination of the first target VA and the second target WA that may frequently occur and disappear such a usage relationship. The predetermined condition may include at least one of the following two conditions.

[0107] (1) First condition 6 is a schematic diagram showing an example of a predetermined condition (first condition) according to the present embodiment. For example, if at least one of the first target VA and the second target WA is of a specific type, such as a constantly used object, the frequency with which the usage relationship is repeatedly created and terminated may increase. Thus, the first condition may be that at least one of the first target VA and the second target WA is of a specific type. The predetermined condition may include the first condition.

[0108] That is, when the type of the first target VA and the second target WA is not a specific type, the system 100 may set the correspondence relationship by normal processing. On the other hand, when the type of at least one of the first target VA and the second target WA is a specific type, the system 100 may set the correspondence relationship by simplified processing. In one example, a specific type may be set for each of the first target VA and the second target WA. In another example, a specific type may be set for only one of the first target VA and the second target WA, and the other target may be omitted. According to one example of the present embodiment, it is possible to control whether or not to execute simplified processing depending on the type of at least one of the first target VA and the second target WA.

[0109] The specific type may be set appropriately according to the embodiment. In one example, the first target VA may be a user, and the second target WA may be a usage object used by the user. The fact that at least one of the first target VA and the second target WA is a specific type may include that the usage object is a regular usage object that is repeatedly used by the user. That is, the first condition may include that the usage object is a regular usage object that is repeatedly used by the user. A regular usage object is more likely to repeatedly generate and disappear a usage relationship than a temporary usage object. Therefore, according to one example of the present embodiment, by allowing a simplified process for a regular usage object, it is possible to track the usage relationship between the user and the usage object while ensuring security, and to reduce the effort involved. Note that the simplified process may or may not be allowed for a temporary usage object. In one example, the system 100 may be configured to establish a correspondence setting by normal processing every time a usage relationship occurs by not allowing a simplified process for a temporary usage object.

[0110] This switching of the authentication mode according to the type may be performed by any method. In one example, before starting the execution of the authentication process, at least one of the management server 1, the external server, the first terminal 4, and the second terminal 5 may identify the type of at least one of the first target VA and the second target WA, and determine whether to execute normal processing or simplified processing according to the identification result. Starting the execution of the authentication process may be, for example, at least one of the first terminal 4 and the second terminal 5 acquiring data to be used for authentication. The external server may be, for example, the first server 2, the second server 3, etc. The type of at least one of the targets may be identified as appropriate. In one example, the type of at least one of the targets may be identified based on each target information (such as an identifier, attribute information, etc.) O10, O20). In the case of the above-mentioned object of use, whether the object of use is a constantly used object may be identified according to attribute information (e.g., type, type of moving object) included in the moving object information O20A. At least one of the devices may hold information for identifying the type in advance, and identify the type of at least one of the objects by this information. Alternatively, at least one of the devices may identify the type of at least one of the objects by referring to information held in an external device. At least one of the first terminal 4 and the second terminal 5 may determine whether to execute normal processing or simplified processing, and start execution of the authentication process in a mode according to the result of the determination. Alternatively, at least one of the terminals may receive a determination result from at least one of the management server 1 and the external server, and start execution of the authentication process in a mode according to the received determination result. In another example, a program including a mode for executing simplified processing may be installed only in a terminal of an object that satisfies a specific type condition, such as a terminal of a constantly used object (the second terminal 5 in FIG. 2), and whether or not to execute simplified processing may be switched by the operation of this terminal.

[0111] (2) Second condition FIG. 7 shows an example of a predetermined condition (second condition) according to this embodiment. It is possible to determine whether a usage relationship is repeatedly created and deleted from the history of the association setting. Thus, the second condition may be that a correspondence relationship has been set in the past for the same combination (combination of the same individuals) of a first object VA and a second object WA. The predetermined condition may include the second condition.

[0112] That is, if a correspondence relationship has not been set in the past for a combination of the same individual of the first object VA and the second object WA, the system 100 may set the correspondence relationship by normal processing. On the other hand, if a correspondence relationship has been set in the past for a combination of the same individual, the system 100 may set the correspondence relationship by simplified processing. According to one example of this embodiment, security is ensured by performing authentication processing in normal processing mode at least once, and thereafter, the effort can be reduced by performing authentication processing in simplified processing mode.

[0113] The switching of the authentication mode according to the second condition may be performed by any method. Information on the combination of the first target VA and the second target WA for which a correspondence relationship has been set in the past may be managed by at least one of the management server 1, the external server, the first terminal 4, and the second terminal 5. Managing may include updating (generating) and deleting data held in at least one of the memory in the device itself and the memory of the external device.

[0114] In one example, the linking information D10 may be maintained as a history even after the correspondence is released. The management server 1 may determine, based on the history of the linking information D10, whether or not the combination of the corresponding individual of the first target VA and the second target WA for which a linking request has been received is a combination for which a correspondence has been set in the past. If it is determined that the combination is a combination for which a correspondence has been set in the past, the management server 1 may accept the linking setting by simplified processing. Furthermore, the management server 1 may transmit, to at least one of the first terminal 4 and the second terminal 5, a command to enable simplified processing for the combination (for example, a command to start processing related to authentication in simplified processing mode).

[0115] In another example, at any timing such as when setting up a link in the normal processing mode, the first terminal 4 may acquire the second identifier I20 of the second object WA, and store the acquired second identifier I20 as a counterpart with whom a correspondence relationship was previously established (i.e., a counterpart with whom simplified processing is permitted). Similarly, the second terminal 5 may acquire the first identifier I10 of the first object VA, and store the acquired first identifier I10 as a counterpart with whom simplified processing is permitted. In this way, at least one of the first terminal 4 and the second terminal 5 may hold information on a counterpart with whom a correspondence relationship was previously established, and the stored information may be used. The terminal may determine whether to execute normal processing or simplified processing by using the information of the other party stored in the terminal. For example, in at least one of the terminals, by executing the linking setting in the normal processing mode, the linking setting in the simplified processing mode may be enabled for the same other party. In response to this, at least one of the terminals may be configured to be able to execute a linking request in the simplified processing mode for the corresponding other party.

[0116] In another example, when the external server is involved in the authentication process, the external server may store the combination of the first target VA and the second target WA in an accessible storage area. For example, the first server 2 may accept the authentication of the first target VA by receiving data used for authenticating the first target VA together with the first identifier I10. At this time, the first server 2 may also receive the second identifier I20 of the second target WA, which is the other party with which the correspondence is to be set. The first server 2 may retain information of the other party with which the correspondence was previously set by storing the first identifier I10 (the first target information O10) in association with the second identifier I20. The same applies to the second server 3. In response to this, when the external server is newly involved in the authentication process, the external server may refer to the retained information to determine whether the combination of the first target VA and the second target WA for which the correspondence is to be set by the authentication process involved is a combination with which the correspondence was previously set. If it is determined that the combination is a combination with which the correspondence was previously set, the external server may accept the linking setting by the simplified process. Furthermore, the external server may transmit, to at least one of the first terminal 4 and the second terminal 5, a command to enable simplified processing for the combination (for example, a command to start processing related to authentication in simplified processing mode).

[0117] In one example, after the simplified processing mode is enabled by performing the authentication process in the normal processing mode once, the system 100 may be configured to permanently perform the linking setting in the simplified processing mode. That is, the range of the past may be infinite. In another example, the enablement of the simplified processing mode may be temporary, and after the enablement of the simplified processing mode is canceled, the authentication process in the normal processing mode may be performed again. That is, the range of the past may be finite. The enablement of the simplified processing mode may be canceled for any reason, such as the expiration date.

[0118] Furthermore, when performing a process related to authentication in the normal processing mode, at least one of the first terminal 4 and the second terminal 5 may store at least a part of data used for authentication (e.g., an identifier, unique information, a certificate, etc.) in a memory resource. Then, when starting to perform a process in the simplified processing mode, at least one of the first terminal 4 and the second terminal 5 may read the data used for authentication from the memory resource and perform the process related to authentication using the read data.

[0119] The first condition and the second condition may be used in combination. That is, the predetermined condition may include that a correspondence relationship has been set for the same combination of the first target VA and the second target WA in the past, and at least one of the first target VA and the second target WA is a specific type. According to an example of the present embodiment, by requesting authentication processing by normal processing at least once for the specific type, it is possible to expect security assurance while reducing the effort.

[0120] In addition, when the first condition and the second condition are used in combination, the first target VA may be a user, and the second target WA may be a usage object used by the user. And, the fact that at least one of the first target VA and the second target WA is a specific type may include that the usage object is a regular usage object that is repeatedly used by the user. According to an example of the present embodiment, by requesting authentication processing by normal processing at least once for a regular usage object, it is possible to reduce the effort and ensure security.

[0121] The type of the object of use may be appropriately selected depending on the embodiment. In one example, the object of use may be a moving object (example of FIG. 2). This makes it possible to ensure security in scenes where a moving object appears, while tracking the usage relationship and reducing the effort involved. In another example, the object of constant use may be a private car. It is possible to reduce the effort involved in tracking the usage relationship regarding a private car.

[0122] (Confirmation of continued use) As an optional configuration, after setting the correspondence between the corresponding individual of the first target VA and the corresponding individual of the second target WA, the management server 1 may further execute a process (confirmation process) for confirming whether the correspondence continues or not. The method of confirming the continuation of use may be appropriately selected according to the embodiment.

[0123] (i-1) Verification process by authentication In one example, the management server 1 may confirm the continuation of the correspondence by authenticating at least one of the first target VA and the second target WA 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 server (2, 3), data used for authentication may be directly transmitted from the terminals (4, 5) to the server (2, 3), or may be indirectly transmitted via an external computer such as the management server 1. When the authentication process is executed by the management server 1, data used for authentication may be directly transmitted from the terminals (4, 5) to the management server 1, or may be indirectly transmitted via an external computer such as each of the servers (2, 3). The management server 1 may acquire authentication results as appropriate, and if the acquired authentication results show that the target has been authenticated, it may determine that the correspondence relationship continues, and if the authentication has not been established, it may determine that the correspondence relationship does not continue.

[0124] (i-2) Confirmation process by notification In another example, when at least one of the first target VA and the second target WA 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, for example, a confirmation button, a reply button, a link, or the like. 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 return a response directly or indirectly to the management server 1 in response to the operation of the operator by the user. When the management server 1 receives a response by the operation of the operator within a predetermined period, it may determine that the correspondence relationship continues, and when it does not receive a response, it may determine that the correspondence relationship does not continue.

[0125] (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.

[0126] Accordingly, the management server 1 may be further configured to, after setting the correspondence relationship between the first target VA and the second target WA, receive measurement results of the current location (RP10, RP20) of each terminal (4, 5) from each terminal (4, 5), determine in real time whether the received measurement results of the current location (RP10, RP20) of each terminal (4, 5) satisfy the conditions of the usage relationship, and determine that the correspondence relationship between the first target VA and the second target WA continues if the measurement results of the current location (RP10, RP20) of each terminal (4, 5) satisfy the conditions of the usage relationship, and if not, determine that the correspondence relationship does not continue.

[0127] 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.

[0128] The range DR may be appropriately set so as to be able to determine the second object WA 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.

[0129] 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.

[0130] 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.

[0131] Further, the destination of the report of the information of each current location may be appropriately selected depending on the embodiment. In one example, the destination of the report of the information of each current location may be the management server 1. Accordingly, the information of each current location may be managed by the management server 1. In another example, the destination of the report of the information of each current location may be an external server (first server 2, second server 3, etc.). Accordingly, the information of each current location may be managed by the external server. The management server 1 may acquire information of each current location (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 location 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 a form of directly reporting to the management server 1 is adopted, information on each current location may be stored in the management server 1 or may be stored in an external server (first server 2, second server 3, NAS, etc.). Similarly, when a form of indirectly reporting to the management server 1 is adopted, information on each current location may be stored in the management server 1 or may be stored in an external server. According to one example of this embodiment, the continuation of the correspondence can be appropriately confirmed by using the relationship between the positions of the first target VA and the second target WA (first terminal 4 and second terminal 5).

[0132] (ii) When it is determined that the correspondence relationship continues, the management server 1 may maintain the setting of the correspondence relationship. On the other hand, when it is determined that the correspondence relationship does not continue, the management server 1 may cancel the correspondence relationship. 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.

[0133] When the management server 1 determines that the correspondence relationship is not continuing, the management server 1 may immediately cancel the correspondence relationship, or may hold the correspondence relationship for a predetermined period and then release the correspondence 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 correspondence relationship is confirmed by at least one of the above methods during the hold, the management server 1 may restore the setting of the correspondence relationship. This makes it possible to quickly restore the setting of the correspondence relationship without immediately canceling the correspondence relationship when the user is temporarily away, for example.

[0134] (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 VA and a second object WA.

[0135] In another example, the association information D10 may be used to enable at least a part of the authority associated with either the first target VA or the second target WA to be exercised from the other while a correspondence relationship is set between the first target VA and the second target WA. For example, the management server 1 may be configured to further execute, in response to the establishment of a correspondence relationship between the first target VA and the second target WA, enabling the exercise of the authority associated with the corresponding first target VA via the second target WA with which the correspondence relationship is set. In addition, the management server 1 may be configured to further execute, in response to the cancellation of the correspondence relationship, invalidating the exercise of the authority. In the example of FIG. 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, the permission and prohibition of the exercise of the authority of the first target VA by the second target WA can be controlled by setting and canceling the correspondence relationship.

[0136] FIG. 9 is a schematic diagram showing an example of a usage scene of the association information D10 according to the present embodiment. FIG. 9 assumes a scene in which the authority associated with the user is exercised from a mobile body in the example of FIG. 2. It is also assumed that the association information D10 is configured to include a first identifier I10 and a second identifier I20 to indicate a first target VA (user) and a second target WA (mobile body) in which a correspondence relationship is set. It is also assumed that the information of the user is managed by a first server 2, and the information of the mobile body is managed by a 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 having the target authority. The configuration and services of the external system SY1 are not particularly limited, and may be appropriately selected according to the embodiment.

[0137] 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.

[0138] 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. 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.

[0139] 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.

[0140] 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.

[0141] 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 VA, and the moving body may be replaced with a second object WA. Furthermore, in the above processing procedure, "first" and "second" may be interchanged.

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

[0143] [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.

[0144] 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.

[0145] 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 Figs. 12A and 12B described below) relating to setting and canceling the correspondence between the first target VA and the second target WA. The management program 81 includes a series of commands for the information processing.

[0146] 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 server 2, the second server 3, the first terminal 4, and the second terminal 5) via the communication interface 13.

[0147] The input device 14 is, for example, a device for inputting a mouse, a keyboard, an operation button, etc. The output device 15 is, for example, a device for outputting a display, a speaker, etc. 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, for example, by a touch panel display or the like. The input device 14 and the output device 15 may be connected via an external interface. The external interface may be appropriately configured to connect to an external device by wire or wirelessly, for example, by a Universal Serial Bus (USB) port, a dedicated port, a wireless communication port, etc.

[0148] The drive 16 is a device for reading various information such as programs stored in a storage medium 91. At least one of the management program 81 and the linking information D10 may be stored in the storage medium 91 in place 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 linking information D10 from the storage medium 91. The storage medium 91 may be a disc such as a CD or a DVD. The drive 16 may be a disk-type storage medium, 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.

[0149] 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.

[0150] (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.

[0151] 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 authentication of the first target VA. 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 other computers (such as the second terminal 5 and the management server 1) via the communication interface 23. The first server 2 may be operated via an input device 24 and an output device 25.

[0152] 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 processor may be configured with a microprocessor, FPGA, DSP, GPU, ASIC, or the like. 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 multiple 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 specifically for the service provided, as well as a general-purpose server device, a general-purpose computer, or the like.

[0153] (Second server) FIG. 10C is a schematic diagram illustrating 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 in 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.

[0154] 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 WA. 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 other computers (such as the first terminal 4 and the management server 1) via the communication interface 33. The second server 3 may be operated via an input device 34 and an output device 35.

[0155] 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.

[0156] (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.

[0157] 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 a first identifier I10. The program 84 is a program for causing the first terminal 4 to execute information processing related to the association (FIGS. 12A and 12B described later). The program 84 includes a series of instructions for the information processing. At least one of the program 84 and the first identifier I10 may be stored in a storage medium 94 instead of or together with the storage unit 42. The first terminal 4 may acquire at least one of the program 84 and the first identifier I10 from the storage medium 94. The first terminal 4 may be operated via an input device 44 and an output device 45.

[0158] The first terminal 4 may perform data communication with other computers (the management server 1, the first server 2, the second server 3, the second terminal 5, etc.) 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 other wireless communication modules. The first terminal 4 may be provided with a short-range 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 the servers (the management server 1, the first server 2, and the second server 3) via other wireless communication modules.

[0159] 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 first identifier I10 may not be stored in the storage unit 42. The first identifier I10 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.

[0160] (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.

[0161] 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 a program 85 and a second identifier I20. The program 85 is a program for causing the second terminal 5 to execute information processing related to the association (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 a storage medium 95 instead of 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 an input device 54 and an output device 55.

[0162] The second terminal 5 may perform data communication with other computers (such as the management server 1, the first server 2, the second server 3, and the first terminal 4) via the communication interface 53. In one example, similar to the first terminal 4, the communication interface 53 may be configured with multiple 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 the server via the other wireless communication module.

[0163] Regarding the specific hardware configuration of the second terminal 5, components can be omitted, replaced, or 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 does not need to be stored in the memory unit 52. The second identifier I20 is, The second terminal 5 may be acquired each time. In order to acquire data such as an identifier and information used for authentication, the second terminal 5 may further include a data acquisition device such as a sensor or a reader. The second terminal 5 may be composed of multiple computers. In this case, the hardware configuration of each computer may or may not be the same. The second terminal 5 may be an information processing device designed specifically for the service provided, as well as a general-purpose computer, terminal device, etc.

[0164] [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, and the second terminal 5) according to this embodiment.

[0165] (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.

[0166] The reception unit 111 is configured to receive a linking request directly or indirectly from at least one of the first terminal 4 of the relevant individual of the first target VA and the second terminal 5 of the relevant individual of the second target WA in response to the occurrence of a usage relationship between the relevant individuals of the first target VA and the second target WA. The reception unit 111 is configured to receive a setting of a correspondence relationship between the relevant individuals of the first target VA and the second target WA by receiving the linking request.

[0167] The setting unit 112 is configured to execute a process of setting a correspondence relationship between the corresponding individuals of the first target VA and the second target WA based on the linking request. When a predetermined condition is not satisfied, the setting unit 112 is configured to acquire both authentication results of the first target VA and the second target WA, and set a correspondence relationship between the first target VA and the second target WA in response to the authentication of both the first target VA and the second target WA being established in the acquired authentication results of the first target VA and the second target WA. In addition, when a predetermined condition is satisfied, the setting unit 112 is configured to omit authentication of one of the first target VA and the second target WA, acquire an authentication result of the other target, and set a correspondence relationship between the first target VA and the second target WA in response to the authentication of the other target being established in the acquired authentication result. The release unit 113 is configured to execute a process of releasing the correspondence relationship in response to the reception of a release request from at least one of the first terminal 4 and the second terminal 5 or the establishment of a predetermined release condition.

[0168] 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 release process to at least one of the first terminal 4 and the second terminal 5.

[0169] When adopting a form in which the authentication process of at least one of the first target VA and the second target WA 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 VA and the second target WA.

[0170] (First server) When adopting a form in which the authentication process of the first target VA 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. In this way, the first server 2 may operate as a computer having an authentication unit 211 as a software module. The authentication unit 211 is configured to execute the authentication process of the first target VA in response to an authentication request for the first target VA.

[0171] (Second server) When adopting a form in which the authentication process of the second target WA 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 having an authentication unit 311 as a software module. The authentication unit 311 is configured to execute the authentication process of the second target WA in response to an authentication request for the second target WA.

[0172] (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.

[0173] When adopting a form in which the authentication process of at least one of the first target VA and the second target WA is executed by the first terminal 4, the first terminal 4 may be configured to further include an authentication unit 414 as a software module. The authentication unit 414 may be configured to execute the authentication process of at least one of the first target VA and the second target WA.

[0174] (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 an unbinding 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 (a request for linking setting) to the management server 1. The unbinding request unit 513 is configured to transmit an unbinding request (a request for unbinding) to the management server 1.

[0175] When adopting a form in which the authentication process of at least one of the first target VA and the second target WA is executed by the second terminal 5, the second terminal 5 may be configured to further include an authentication unit 514 as a software module. The authentication unit 514 may be configured to execute the authentication process of at least one of the first target VA and the second target WA.

[0176] (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.

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

[0178] In step S10, in response to the occurrence of a usage relationship between the corresponding individuals of the first object VA and the second object WA, at least one of the control unit 41 of the corresponding first terminal 4 and the control unit 51 of the corresponding second terminal 5 sends a linking request to the management server 1.

[0179] In one example, in response to the occurrence of a usage relationship, the control unit 41 of the corresponding first terminal 4 may operate as a data exchange unit 411 and execute data exchange with the corresponding second terminal 5. The control unit 51 of the second terminal 5 may operate as a data exchange unit 511 and execute data exchange with the first terminal 4. The data exchange may be performed by short-range wireless communication. Triggered by this data exchange, the control unit 41 of the first terminal 4 may operate as a setting request unit 412 and transmit a 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 a linking request to the management server 1. The first terminal 4 and the second terminal 5 may transmit a linking request together, or one of the first terminal 4 and the second terminal 5 may transmit a 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 a linking request. Furthermore, the association request may be sent directly to the management server 1, or may be sent indirectly via an external computer (the first server 2, the second server 3, etc.).

[0180] In step S20, the control unit 11 of the management server 1 operates as a reception unit 111 and receives a linking request directly or indirectly from at least one of the first terminal 4 of the relevant individual of the first target VA and the second terminal 5 of the relevant individual of the second target WA. By receiving this linking request, the control unit 11 accepts the setting of a correspondence relationship between the relevant individual of the first target VA and the relevant individual of the second target WA.

[0181] In step S10, 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 between the part of the data and the remaining data may be permitted. In step S20, in order to identify the combination of the relevant individuals of the first target VA and the second target WA that are 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).

[0182] 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.

[0183] The shared information may be configured arbitrarily. In one example, the shared information may be configured by a combination of a first identifier I10 and a second identifier I20. 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. In another example, the shared information may be configured by temporary information such as a random number, a timestamp, or a hash value. In this case, 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 correspondence of data may be specified in response to the establishment of a relationship between the first terminal 4 and the second terminal 5. 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.

[0184] In step S25, the destination of the process is determined depending on whether or not a predetermined condition is satisfied. If the predetermined condition is not satisfied, the process proceeds to step S301. On the other hand, if the predetermined condition is satisfied, the process proceeds to step S311. In one example, whether or not the predetermined condition is satisfied may be determined by at least one of the management server 1, the external server (the first server 2, the second server 3, etc.), the first terminal 4, and the second terminal 5. The destination of the process may be determined depending on the result of the determination. In another example, the destination of the process may be determined depending on the operation mode of at least one of the first terminal 4 and the second terminal 5. In another example, the predetermined condition may include at least one of the above two conditions.

[0185] In step S301, the control unit 11 of the management server 1 operates as the setting unit 112 and acquires both the authentication results of the first target VA and the second target WA. In step S302, the control unit 11 operates as the setting unit 112 and determines whether or not the authentication of both the first target VA and the second target WA is established in the acquired authentication result. If the authentication of at least one of the first target VA and the second target WA is not established, the control unit 11 rejects the linking request and proceeds to step S40. As a result, the control unit 11 omits the setting of the correspondence relationship. On the other hand, if the authentication of both the first target VA and the second target WA is established, the control unit 11 proceeds to step S320.

[0186] In step S311, the control unit 11 of the management server 1 operates as the setting unit 112, and omits authentication of one of the first target VA and the second target WA, and obtains the authentication result of the other target. In one example, the first target VA may be a user, and the second target WA may be a usage object. Authentication of the usage object may be omitted, and the control unit 11 may obtain the authentication result of the user.

[0187] In step S312, the control unit 11 operates as the setting unit 112 and determines whether or not the authentication of the other target is established in the acquired authentication result. If the authentication of the other target is not established, the control unit 11 rejects the linking request and proceeds to step S40. As a result, the control unit 11 omits setting of the correspondence relationship. On the other hand, if the authentication of the other target is established, the control unit 11 proceeds to step S320. The fact that the authentication of the other target is established may include the fact that the login state of the other target continues.

[0188] The authentication process of the first target VA and the second target WA may be performed by at least one of the management server 1, an external server (for example, the first server 2, the second server 3), the first terminal 4, and the second terminal 5. The control unit 11 of the management server 1 may operate as an authentication unit 115 and perform the authentication process of at least one of the first target VA and the second target WA. The control unit 21 of the first server 2 may operate as an authentication unit 211 and perform the authentication process of the first target VA. The control unit 31 of the second server 3 may operate as an authentication unit 311 and perform the authentication process of the second target WA. The control unit 41 of the first terminal 4 may operate as an authentication unit 414 and perform the authentication process of at least one of the first target VA and the second target WA. The control unit 41 of the second terminal 5 may operate as an authentication unit 514 and perform the authentication process of at least one of the first target VA and the second target WA. The authentication process may be performed at any timing before the processes of steps S301 and S311 are performed.

[0189] In step S320, the control unit 11 operates as the setting unit 112 and executes a linking process to establish a correspondence relationship between the first object VA and the second object WA 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. After updating the linking information D10, the control unit 11 advances the process to the next step S40. Note that the processes of steps S301, S302, S311, S312, and S320 are an example of the process of setting the correspondence relationship in response to the received linking request (step S30 above).

[0190] In step S40, the control unit 11 operates as the notification unit 114, and directly or indirectly transmits a notification indicating the result of the execution of the correspondence setting process to at least one of the first terminal 4 and the second terminal 5. When the notification of the result is completed, the processing procedure regarding the association setting according to this operation example ends.

[0191] The above process is merely an example, and each step may be changed as much as possible. In addition, the above process may be omitted, replaced, or added as appropriate depending on the embodiment. For example, the branch of step S25 may be placed before step S20 or step S10.

[0192] (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.

[0193] 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.

[0194] In step SZ20, 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.

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

[0196] The above processing procedure is merely an example, and each step may be modified as much as possible. Furthermore, 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). The process of the release request may include authentication processing of at least one of the first target VA and the second target WA. Furthermore, the control unit 11 of the management server 1 operates as a release unit 113 instead of the above step SZ20, and performs the following when a predetermined release condition is met. Furthermore, the control unit 11 may operate as the canceling unit 113 and, after setting the correspondence relationship, execute the above-mentioned confirmation process for continuing use for the set correspondence relationship at any timing.

[0197] [Features] In this embodiment, information indicating the setting of the correspondence relationship between the corresponding individuals of the first target VA and the second target WA is recorded by the process of step S320. This recording makes it possible to trace the usage relationship between the corresponding individuals of the first target VA and the second target WA. In addition, in this embodiment, when a predetermined condition is not satisfied, authentication of both the first target VA and the second target WA is performed when setting the correspondence relationship (the route of step S301 is selected). This makes it possible to ensure security. On the other hand, when a predetermined condition is satisfied, authentication of either the first target VA or the second target WA is omitted (the route of step S311 is selected). This makes it possible to reduce the effort. Therefore, according to this embodiment, it is possible to track the usage relationship between the first target VA and the second target WA while ensuring security, and to reduce the effort involved.

[0198] [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.

[0199] <4.1> In the above embodiment, in the normal processing mode, authentication processes of both the first target VA and the second target WA are executed, whereas in the simplified processing mode, one of them is omitted. However, from the viewpoint of balancing between ensuring security and reducing effort, omitting the authentication process can be applied to cases other than such an allocation. The form of omitting the authentication process is not limited to the example of the above embodiment. In another example, in the normal processing mode, authentication of at least one of the first target VA and the second target WA is executed, whereas in the simplified processing mode, authentication of both the first target VA and the second target WA may be omitted.

[0200] FIG. 13 is a schematic diagram showing another example of a situation to which the present disclosure is applied. The control unit 11 of the management server 1 may be configured to set a correspondence relationship between the first target VA and the second target WA based on a linking request transmitted from at least one of the first terminal 4 of the first target VA and the second terminal 5 of the second target WA when a usage relationship occurs between the first target VA and the second target WA. In this setting process, if a predetermined condition is not satisfied, the control unit 11 may acquire an authentication result of at least one of the first target VA and the second target WA, and set a correspondence relationship between the first target VA and the second target WA according to the authentication being established in the acquired authentication result. On the other hand, if a predetermined condition is satisfied, the control unit 11 may omit authentication of both the first target VA and the second target WA, and set a correspondence relationship between the first target VA and the second target WA according to receiving a linking request.

[0201] Also, in one example, when adopting a form in which the authentication process is performed by the management server 1 or an external server, the control unit 41 of the first terminal 4 of the first target VA may be configured to, when a usage relationship occurs between the first target VA and the second target WA, send a linking request to the management server 1, send a linking request in cooperation with the second terminal 5 of the second target WA, or have the second terminal 5 send a linking request, thereby causing the management server 1 to set a correspondence relationship between the first target VA and the second target WA. If a predetermined condition is not satisfied, the linking request includes an authentication request for at least one of the first target VA and the second target WA. Setting a correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to authentication of at least one of the first target VA and the second target WA being established based on the authentication request. When a predetermined condition is satisfied, both authentication requests for the first target VA and the second target WA may be omitted from the linking request. Setting a correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to receiving the linking request.

[0202] Similarly, the control unit 51 of the second terminal 5 of the second target WA may be configured to execute, when a usage relationship occurs between the first target VA and the second target WA, to cause the management server 1 to set a correspondence relationship between the first target VA and the second target WA by transmitting a linking request to the management server 1, transmitting a linking request in cooperation with the first terminal 4 of the first target VA, or causing the first terminal 4 to transmit a linking request. If a predetermined condition is not satisfied, the linking request may include an authentication request for at least one of the first target VA and the second target WA. Setting the correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to the authentication of at least one of the first target VA and the second target WA being established based on the authentication request. If a predetermined condition is satisfied, both the authentication requests for the first target VA and the second target WA may be omitted from the linking request. Setting a correspondence relationship between the first target VA and the second target WA may be configured by setting a correspondence relationship between the first target VA and the second target WA in response to receiving a linking request.

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

[0204] (A) First authentication method FIG. 14 shows a schematic diagram of an example of a process of linking settings when the first authentication method is adopted. In the first authentication method, the second server 3 executes authentication processing of the second target WA in response to a request (authentication request) from the first terminal 4 of the first target VA. The first server 2 executes authentication processing of the first target VA in response to a request (authentication request) from the second terminal 5 of the second target WA. Each terminal (4, 5) requests each server (2, 3) to authenticate each other as a linking request, and has the server (2, 3) report the authentication result to the management server 1. As a result, each terminal (4, 5) transmits a 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. Moreover, the process from the transmission of a request from each terminal (4, 5) to each server (2, 3) to the transmission of 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 transmit a linking request together.

[0205] The first server 2 is configured to be able to access a first storage device that stores first registered unique information CA10 for authentication of the first target VA. The first storage device may be configured by at least one of the memory resources of the first server 2 and an external storage device (NAS, etc.). The first registered unique information CA10 may be included in the first target information O10. The second server 3 may be configured to be able to access a second storage device that stores second registered unique information CA20 for authentication of the second target WA. The second storage device may be configured by at least one of the memory resources of the second server 3 and an external storage device (NAS, etc.). The second registered unique information CA20 may be included in the second target information O20.

[0206] Each registered unique information (CA10, CA20) is used to authenticate each target (VA, WA). The unique information is unique information registered in advance. The unique information may have any data format and structure that can be used for authentication and may be appropriately selected according to 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.

[0207] 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.

[0208] First, when a usage relationship occurs between the first object VA and the second object WA, data exchange is executed between the corresponding first terminal 4 and second terminal 5 (step SA110, step SB110). The authentication process in the normal processing mode will be described below.

[0209] In step SA110, the control unit 51 of the second terminal 5 acquires the first identifier I10 and the first unique information CA1 from the corresponding individual of the first target VA. The first unique information CA1 corresponds to the first registered unique information CA10. The control unit 51 may acquire the first identifier I10 and the first unique information CA1 from the first target VA as appropriate in the data exchange. Acquiring from the first target VA may include acquiring from the first terminal 4. For example, the control unit 51 may acquire at least one of the first identifier I10 and the first unique information CA1 from the first target VA via an input device, a sensor, or the like. The control unit 51 may acquire at least one of the first identifier I10 and the first unique information CA1 from the first terminal 4 in the data exchange.

[0210] Also, in step SB110, the control unit 41 of the first terminal 4 acquires the second identifier I20 and the second unique information CA2 from the corresponding individual of the second object WA. The second unique information CA2 corresponds to the second registered unique information CA20. The control unit 41 may acquire the second identifier I20 and the second unique information CA2 from the second object WA as appropriate in the data exchange. Acquiring from the second object WA may include acquiring from the second terminal 5. For example, the control unit 41 may acquire at least one of the second identifier I20 and the second unique information CA2 from the second object WA via an input device, a sensor, or the like. The control unit 41 may acquire at least one of the second identifier I20 and the second unique information CA2 from the second terminal 5 in the data exchange. Each identifier (I10, I20) and each unique information (CA1, CA2) is an example of data used for authentication.

[0211] In step SA120, the control unit 51 of the second terminal 5 transmits a first authentication request including the first identifier I10 and the first unique information CA1 to the first server 2. In response to this, the control unit 21 of the first server 2 receives the first authentication request for the corresponding individual of the first target VA. The control unit 21 of the first server 2 operates as the authentication unit 211, and performs authentication processing of the first target VA as appropriate in response to receiving the first authentication request. In one example, the control unit 21 may extract the first registered unique information CA10 of the corresponding individual of the first target VA from the first target information O10 by searching the first target information O10 using the first identifier I10 included in the first 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 first 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 corresponding individual of the first target VA is successful depending on the result of the comparison. In step SA130, the control unit 21 outputs the authentication result for the corresponding individual of the first target VA. The control unit 21 reports the authentication result of the first target VA to the management server 1. In one example, the control unit 21 may transmit the authentication result of the first target VA to the management server 1 together with the first identifier I10 of the first target VA. 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.

[0212] On the other hand, in step SB120, the control unit 41 of the first terminal 4 transmits a second authentication request including the second identifier I20 and the second unique information CA2 to the second server 3. In response to this, the control unit 31 of the second server 3 receives the second authentication request for the corresponding individual of the second target WA. The control unit 31 of the second server 3 operates as the authentication unit 311, and appropriately executes authentication processing for the second target WA in response to receiving the second authentication request. In one example, the control unit 31 may extract the second registered unique information CA20 of the corresponding individual of the second target WA from the second target information O20 by searching the second target information O20 using the second identifier I20 included in the second 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 second authentication request. The comparison may be performed appropriately depending on the unique information used. The control unit 31 may determine whether or not authentication of the corresponding individual of the second target WA is successful depending on the result of the comparison. In step SB130, the control unit 31 reports the authentication result for the corresponding individual of the second target WA to the management server 1. In one example, the control unit 31 may transmit the authentication result of the second target WA to the management server 1 together with the second identifier I20 of the second target WA. 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.

[0213] The second terminal 5 giving the first 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 the second 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 SA120, SA130, SB120, and SB130 are an example of the process of step S10. This form of authentication request is an example of a form in which authentication processing is executed together with the linking request.

[0214] The control unit 11 of the management server 1 receives the authentication result for the corresponding individual of each target (VA, WA) 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 corresponding individual of the first target VA and the second target WA that is currently requesting the setting of the correspondence relationship. When the authentication of both the first target VA and the second target WA is established in the received authentication result of the first target VA and the second target WA, the control unit 11 sets the correspondence relationship between the corresponding individual of the first target VA and the second target WA. The setting process of 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 the setting of the association may be executed in real time in response to the occurrence of the usage relationship.

[0215] In the first authentication method, in the normal processing mode, in response to the occurrence of a usage relationship between the corresponding individuals of the first target VA and the second target WA, the first server 2 and the second server 3 respectively authenticate the corresponding individuals of the first target VA and the second target WA. At this time, authentication of the first target VA is requested from the second terminal 5 of the second target WA. Authentication of the second target WA is requested from the first terminal 4 of the first target VA. 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.

[0216] The processing procedure in FIG. 14 is merely an example, and each step may be changed as much as possible. In addition, the above processing procedure may be omitted, replaced, or modified as appropriate according to the embodiment. For example, the processing order of the authentication of the first target VA (steps SA110 to SA130) and the authentication of the second target WA (steps SB110 to SB130) is not particularly limited and may be determined appropriately according to the embodiment.

[0217] When the simplified processing mode is selected, the authentication process of either the first target VA or the second target WA may be omitted. The linking request in the simplified processing mode may be configured to appropriately specify the corresponding individual of the first target VA and the second target WA. In one example, when performing authentication of one of the first target VA and the second target WA, data transmitted in the authentication route of the one target may include an identifier of the one target as well as an identifier of the other target. For example, when authenticating the first target VA, data transmitted from the second terminal 5 to the management server 1 via the first server 2 may include the first identifier I10 and the second identifier I20.

[0218] Also, similarly to the above <4.1>, in the normal processing mode, authentication processing of at least one of the first target VA and the second target WA is executed, whereas in the simplified processing mode, both the first target VA and the second target WA may be omitted. In this case, at least one of the first terminal 4 and the second terminal 5 may omit the authentication request and appropriately transmit a linking request to the management server 1.

[0219] In addition, the transmission path of the authentication result may not be limited to the example of FIG. 14. In another example, the first terminal 4 may receive the authentication result of the second target WA from the second server 3, and the second terminal 5 may receive the authentication result of the first target VA 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 target (VA, WA) to the management server 1. Alternatively, one of the first terminal 4 and the second terminal 5 may exchange the authentication result with the other terminal, and the other terminal may transmit a linking request including the authentication results of the first target VA and the second target WA to the management server 1. This form is an example of a form in which authentication processing is performed before issuing a linking request.

[0220] (B) Second authentication method FIG. 15 shows a schematic diagram of an example of a process of linking settings when the second authentication method is adopted. In the second authentication method, the management server 1 requests each server (2, 3) to perform authentication in response to a request from at least one of the first terminal 4 and the second terminal 5. That is, at least one of the first terminal 4 and the second terminal 5 transmits a linking request including an authentication request for each target (VA, WA). 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. In addition, this form of authentication request is an example of a form in which authentication processing is executed after a linking request. The authentication processing in the normal processing mode will be described below.

[0221] First, when a usage relationship occurs between the corresponding individuals of the first object VA and the second object WA, data exchange is executed between the corresponding first terminal 4 and second terminal 5 (step SC110, step SD110). At least one of the first terminal 4 and the second terminal 5 transmits an authentication request including the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2 to the management server 1 as a linking request (step SC120, step SD120). 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 SC120 and SD120 are an example of the process of step S10.

[0222] The division of data transmission may be appropriately determined depending on the embodiment. In one example, the second terminal 5 may be in charge of transmitting the first identifier I10 and the first unique information CA1, and the first terminal 4 may be in charge of transmitting the second identifier I20 and the second unique information CA2. That is, in step SC110, the control unit 51 of the second terminal 5 transmits the first identifier I10 and the first unique information CA1 to the first target VA The acquiring from the first object VA may include acquiring from the first terminal 4. In step SC120, 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 to the management server 1. In step SD110, the control unit 41 of the first terminal 4 may acquire the second identifier I20 and the second unique information CA2 from the second object WA. The acquiring from the second object WA may include acquiring from the second terminal 5. In step SD120, the control unit 41 of the first terminal 4 may transmit a linking request including the acquired second identifier I20 and second unique information CA2 to the management server 1.

[0223] The sharing of data transmission is not 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 in a divided manner, the management server 1 may specify the correspondence of the authentication request data by a method such as using the above shared information in order to specify the combination of the corresponding individual of the first target VA and the second target WA 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.

[0224] In step SC130, the control unit 11 of the management server 1 requests the first server 2 to authenticate the corresponding individual of the first target VA 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 may operate as the authentication unit 211, compare the first unique information CA1 and the first registered unique information CA10, and determine whether or not the authentication of the corresponding individual of the first target VA has been successful depending on the result of the comparison. In step SC140, the control unit 21 of the first server 2 returns the authentication result for the corresponding individual of the first target VA to the management server 1.

[0225] Similarly, in step SD130, the control unit 11 of the management server 1 requests the second server 3 to authenticate the corresponding individual of the second target WA by transmitting 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 corresponding individual of the second target WA has been successful depending on the result of the comparison. In step SD140, the control unit 31 of the second server 3 transmits the authentication result of the corresponding individual of the second target WA to the management server 1.

[0226] The control unit 11 of the management server 1 receives authentication results for the relevant individual of each target (VA, WA) from each server (2, 3). If the authentication results for the first target VA and the second target WA received show that both the first target VA and the second target WA have been successful, the control unit 11 of the management server 1 sets a correspondence relationship between the relevant individual of the first target VA and the second target WA. 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. Other configurations may be the same as those of the first authentication method.

[0227] In the second authentication method, in the normal processing mode, when a usage relationship occurs between the corresponding individuals of the first target VA and the second target WA, the corresponding individuals of the first target VA and the second target WA are authenticated by the first server 2 and the second server 3, respectively. These two authentications are expected to ensure security.

[0228] The processing procedure in FIG. 15 is merely an example, and each step may be changed as much as possible. In addition, steps may be omitted, replaced, or added as appropriate for the above processing procedure depending on the embodiment. For example, authentication of the first target VA (steps SC110 to SC The processing order of the authentication of the second target WA (steps SD110 to SD140) and the authentication of the second target WA (steps SD110 to SD140) is not particularly limited, and may be determined appropriately depending on the embodiment.

[0229] When the simplified processing mode is selected, the authentication process of either the first target VA or the second target WA may be omitted. As in the first authentication method, the linking request in the simplified processing mode may be configured to appropriately specify the corresponding individual of the first target VA and the second target WA. Also, as in <4.1> above, in the normal processing mode, the authentication process of at least one of the first target VA and the second target WA is executed, whereas in the simplified processing mode, both the first target VA and the second target WA may be omitted.

[0230] In addition, the transmission path of the authentication result may not be limited to the example of FIG. 15. In another example, the authentication process of at least one of the first target VA and the second target WA 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 VA and the second target WA.

[0231] (C-1) Authentication method No. 3-1 16 is a schematic diagram showing an example of a process of binding setting when the authentication method 3-1 is adopted. The authentication method 3-1 uses a time-limited certificate for authentication instead of unique information. The authentication process is executed by the management server 1.

[0232] The first server 2 is configured to issue a first time-limited certificate CB10 for each instance of the first object VA. The second server 3 is configured to issue a second time-limited certificate CB20 for each instance of the second object WA.

[0233] 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.

[0234] The validity period of each time-limited certificate (CB10, CB20) may be managed as appropriate. Revocation due to the lapse of the validity period may be identified as appropriate. For example, whether or not the target time-limited certificate 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). The authentication process in the normal processing mode will be described below.

[0235] First, in step SE110, the control unit 41 of the first terminal 4 of the first target VA transmits a request for issuance of a first time-limited certificate CB10 to the first server 2 in association with the first identifier I10 of the first target VA. In response to receiving the request, the control unit 21 of the first server 2 issues the first time-limited certificate CB10 in association with the first identifier I10. In step SE120, the first server 2 The control unit 21 of the first terminal 4 returns the issued first time certificate CB10 to the first terminal 4. In response, the first terminal 4 receives the issued first time certificate CB10 from the first server 2. The control unit 41 of the first terminal 4 stores the received first time certificate CB10 so that it can be used as the first certificate CB1. Furthermore, in step SE130, 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 attached.

[0236] In step SF110, the control unit 51 of the second terminal 5 of the second target WA transmits a request for issuing a second time certificate CB20 to the second server 3 in relation to the second identifier I20 of the second target WA. 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 SF120, 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. In addition, in step SF130, the control unit 31 of the second server 3 also 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.

[0237] When a usage relationship occurs between the corresponding individuals of the first target VA and the second target WA, data exchange is performed between the corresponding first terminal 4 and second terminal 5 (step SE140, step SF140). At least one of the first terminal 4 and the second terminal 5 transmits an authentication request including the first certificate CB1 and the second certificate CB2 as a linking request to the management server 1 (step SE150, step SF150). 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 processing of steps SE150 and SF150 is an example of the processing of step S10. 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. This form of authentication request is an example of a form of performing authentication processing together with or after the linking request.

[0238] The division of data transmission may be appropriately determined according to the embodiment. In one example, the second terminal 5 may be in charge of transmitting the first certificate CB1, and the first terminal 4 may be in charge of transmitting the second certificate CB2. That is, in step SE140, the control unit 51 of the second terminal 5 may obtain the first certificate CB1 from the first terminal 4. In step SE150, the control unit 51 of the second terminal 5 may transmit a linking request including the first certificate CB1 to the management server 1. In step SF140, the control unit 41 of the first terminal 4 may obtain the second certificate CB2 from the second terminal 5. In step SF150, the control unit 41 of the first terminal 4 may transmit a linking request including the second certificate CB2 to the management server 1.

[0239] 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. Also, each identifier (I10, I20) may 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 corresponding individual of the first target VA and the second target WA 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.

[0240] 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).

[0241] 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) or each server (2, 3). When the conversion process is performed in each server (2, 3), each terminal (4, 5) may receive the converted time certificate (CB10, CB20) from each server (2, 3).

[0242] The control unit 11 of the management server 1 may determine whether or not the authentication of the corresponding individual of each target (VA, WA) 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 / the second time certificate CB20 have expired due to the expiration of the validity period, the comparison of the first target VA / the second target WA 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 first target VA and the second target WA is successful. If the authentication of both the first target VA and the second target WA is successful, the control unit 11 of the management server 1 sets a correspondence relationship between the corresponding individual of the first target VA and the second target WA. 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.

[0243] In the method 3-1, in the normal processing mode, when a usage relationship occurs between the corresponding individuals of the first target VA and the second target WA, the authentication of each of the first target VA and the second target WA is performed using a time-limited certificate (CB10, CB20). Each time-limited certificate (CB10, CB20) is configured to expire after the validity period has passed. Therefore, it is possible to prevent the same certificate from being used permanently, which is expected to ensure security.

[0244] The processing procedure in FIG. 16 is merely an example, and each step may be changed as much as possible. In addition, steps may be omitted, replaced, or added as appropriate for the above processing procedure depending on the embodiment. For example, authentication of the first target VA (steps SE110 to SE The processing order of the authentication of the second target WA (steps SF110 to SF150) and the authentication of the second target WA (steps SF110 to SF150) is not particularly limited, and may be appropriately determined depending on the embodiment.

[0245] 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 SE110 and SF110 may be omitted.

[0246] Furthermore, the issuance of each time certificate (CB10, CB20) (steps SE110 to SE130, steps SF110 to SF130) may be executed at any timing before the request for linking setting (steps SE150, SF150). 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 (steps SE140, SF140). 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 transmission of a linking request. 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.

[0247] When the simplified processing mode is selected, the authentication process of either the first target VA or the second target WA may be omitted. As in the first authentication method, the linking request in the simplified processing mode may be configured to appropriately specify the corresponding individual of the first target VA and the second target WA. Also, as in <4.1> above, in the normal processing mode, the authentication process of at least one of the first target VA and the second target WA is executed, whereas in the simplified processing mode, both the first target VA and the second target WA may be omitted.

[0248] In the above authentication method 3-1, the matching process of each certificate (CB1, CB2) and each time-limited certificate (CB10, CB20), i.e., the authentication process of each target (VA, WA), is executed by the management server 1. However, the subject that executes the matching 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 matching process by transmitting each certificate (CB1, CB2) to each server (2, 3). In this way, the matching process may be executed by each server (2, 3). In other words, the authentication process of at least one of the first target VA and the second target WA 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 VA has been successful by matching 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 VA to the management server 1. Furthermore, the control unit 31 of the second server 3 may operate as an authentication unit 311 and determine whether authentication of the second target WA has been successful by comparing the second certificate CB2 received from the management server 1 with the second time-limited certificate CB20. The control unit 31 may return the authentication result of the second target WA to the management server 1. In this case, the notification (steps SE130 and SF130) of each time-limited certificate (CB10, CB20) may be omitted. In another example, the management server 1 may perform authentication processing for at least one of the first target VA and the second target WA, and an external server may perform authentication processing for the other.

[0249] (C-2) Authentication method 3-2 In the above authentication method 3-1, authentication processing of each target (VA, WA) is executed 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 is not limited to this example. In the authentication method 3-2, before transmitting a linking request to the management server 1, authentication processing of at least one of the first target VA and the second target WA may be executed in advance by at least one of the first terminal 4 and the second terminal 5 between the first server 2 and the second server 3 and at least one of the first server 2 and the second server 3. The form of this authentication request This embodiment is an example of a form in which authentication processing is executed before a linking request is made.

[0250] 17A is a schematic diagram showing an example of the process of association setting in the case where the 3-2 authentication method is adopted, assuming a scene in which authentication processing of the first target VA is executed.

[0251] First, between the first terminal 4 and the first server 2, the processes of steps SE110 and SE120 may be executed in the same manner as in the authentication method of the above 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 first terminal 4. 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 SE130) may be omitted. In step SE140, the control unit 41 of the first terminal 4 provides the issued first time certificate CB10 to the second terminal 5 as the first certificate CB1. Also, the first terminal 4 provides the first identifier I10 to the second terminal 5. In response to this, the second terminal 5 acquires the first identifier I10 and the first certificate CB1 from the first target VA.

[0252] In step SG110, 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 SG120, the control unit 21 of the first server 2 returns the result of the comparison to the second terminal 5. In response to this, the control unit 51 of the second terminal 5 receives the result of the comparison.

[0253] If 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 terminate the processing procedure for setting up the linkage as appropriate. The control unit 51 may request the first terminal 4 to resend the first certificate CB1. On the other hand, if the comparison is successful, the control unit 51 transmits a linkage request including the first identifier I10 and the second identifier I20 to the management server 1 (step SG130). The processing of step SG130 is an example of the processing of step S10 above.

[0254] 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 a correspondence relationship between the relevant individuals of the first target VA and the second target WA. 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 (step SE140) between the terminals (4, 5) to setting the linking may be executed in real time in response to the occurrence of a usage relationship. Other configurations may be the same as those of the first authentication method, etc.

[0255] The authentication target by the 3-2 authentication method does not have to be limited to the first target VA. The second target WA may also be authenticated by the same method.

[0256] FIG. 17B shows a schematic diagram of another example of the process of linking settings when the 3-2 authentication method is adopted. FIG. 17B assumes a scene in which authentication processing of the second target WA is executed. Except for the point that the first target VA and the second target WA are switched, the processing procedure of FIG. 17B may be similar to the processing procedure of FIG. 17A. That is, by executing the processing of steps SF110 and SF120 between the second terminal 5 and the second server 3, a second time certificate CB20 is issued, and the issued second time certificate CB20 is notified to the second terminal 5. In step SF140, the control unit 51 of the second terminal 5 transmits the issued second time certificate CB20 to The second certificate CB20 is provided to the first terminal 4 as the second certificate CB2. The control unit 51 of the second terminal 5 provides the second identifier I20 to the first terminal 4. In step SH110, 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 matching process of the second certificate CB2 and the second time-limited certificate CB20. In step SH120, the control unit 31 of the second server 3 returns the result of the matching to the first terminal 4. In the result of the matching, if the matching of the second certificate CB2 and the second time-limited certificate CB20 is established, 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 SH130). 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 object VA and the second object WA.

[0257] When adopting an omission form of the authentication process similar to the above embodiment, in the normal processing mode, the authentication process of the first target VA and the second target WA according to Fig. 17A and Fig. 17B may be executed. On the other hand, in the simplified processing mode, the authentication process of either the first target VA or the second target WA may be omitted.

[0258] In the 3-2 authentication method, in the normal processing mode, the authentication process is executed before the association request. 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.

[0259] 17A and 17B are merely examples, and each step may be changed as much as possible. In addition, steps may be omitted, replaced, or added as appropriate for the above processing procedure depending on the embodiment. The processing order of the authentication of the first target VA and the authentication of the second target WA is not particularly limited, and may be determined as appropriate depending on the embodiment.

[0260] For example, the management server 1 may appropriately verify that matching has been established in the first server 2 in the processing procedure of FIG. 17A. In one example, the first server 2 may also transmit the result of matching to the management server 1. For example, the authentication request may further include the second identifier I20. When matching is established, the first server 2 may transmit the result of matching including the first identifier I10 and the second identifier I20 to the management server 1. In this way, the first server 2 may enable the management server 1 to request association with the combination of the first identifier I10 and the second identifier I20 specified in the result of matching. That is, in one example, the verification of matching establishment may be configured by receiving the result of matching. The management server 1 may be configured to hold the result of matching from the first server 2, accept a request for association setting with the combination of the first identifier I10 and the second identifier I20 specified in the result of matching, and reject other requests for association setting. Similarly, in the processing procedure of FIG. 17B, the management server 1 may appropriately verify that matching has been established in the second server 3.

[0261] Also, similarly to the above <4.1>, in the normal processing mode, at least one of the authentication processes of the first target VA and the second target WA according to Fig. 17A and Fig. 17B may be executed. On the other hand, in the simplified processing mode, the authentication processes of both the first target VA and the second target WA may be omitted.

[0262] 17A and 17B, 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.

[0263] (D) Fourth authentication method FIG. 18A shows a schematic diagram of an example of the process of linking settings when the fourth authentication method is adopted. The fourth authentication method uses an electronic signature and an electronic certificate using a private key. The authentication process is executed by the terminal of the other party to be authenticated. The terminal of the other party to be authenticated is the second terminal 5 when authenticating the first target VA, and is the first terminal 4 when authenticating the second target WA. FIG. 18A assumes a scene in which the authentication process of the first target VA is executed.

[0264] As a preparation stage (pre-processing), a combination of a first secret key CC10 and a first public key to be used for authenticating the first target VA is generated. The method of generating the first secret key CC10 and the first public key is not particularly limited and may be appropriately selected depending on the embodiment. The first secret key CC10 and the first public key may be generated by at least one of the first terminal 4 and an external computer (the first server 2, the certification authority, etc.).

[0265] Next, a first electronic certificate CC1 for the first public key is generated by the certification authority. In one example, the certification authority may generate the first electronic certificate CC1 in response to a request from the first terminal 4. The certification authority may be the first server 2 or an external server other than the first server 2. As long as the authenticity of the first public key can be verified, the configuration of the first electronic certificate CC1 is not particularly limited and may be appropriately selected according to the embodiment. In one example, the first electronic certificate CC1 may be composed of an electronic signature by the certification authority, ownership information, and a first public key. The certification authority holds a combination of a public key and a private key. The electronic signature by the certification authority may be generated by encrypting the ownership information and the first public key with the private key of the certification authority. In a specific example, the electronic signature by the certification authority may be generated by converting the ownership information and the first public key into a hash value by a hash function and encrypting the obtained hash value with the private key of the certification authority.

[0266] The first electronic certificate CC1 is provided to the first terminal 4 by the certification authority. The first electronic certificate CC1 may be stored in any memory area. The expiration date of the first electronic certificate CC1 may be managed by a revocation list. The revocation list may also be stored in any memory area. The first electronic certificate CC1 and the revocation list may be stored in the first server 2, or in an external server accessible from the first server 2. When the first terminal 4 holds the first private key CC10 and the first electronic certificate CC1, preparations for authentication processing of the first target VA are completed.

[0267] In the usage stage, first, when a usage relationship occurs between the corresponding individuals of the first target VA and the second target WA, data exchange is executed between the corresponding first terminal 4 and second terminal 5 (steps SI110, SI120). In this data exchange, electronic information is shared between the first terminal 4 and the second terminal 5. The electronic information may be composed of any information such as a random number, a timestamp, etc. The electronic information may include information derived from the first target VA, such as the owner information of the first terminal 4.

[0268] The electronic information may be generated by at least one of the first terminal 4 and the second terminal 5. When the second terminal 5 is involved in the generation of at least a part of the electronic information, data on the electronic information may be provided from the second terminal 5 to the first terminal 4 as the process of step SI110. The control unit 41 of the first terminal 4 generates the electronic signature CD1 by encrypting the first identifier I10 and the electronic information using the first private key CC10. In a specific example, the control unit 41 of the first terminal 4 may generate the electronic signature CD1 by converting the first identifier I10 and the electronic information into hash values ​​using a hash function and encrypting the obtained hash value with the first private key CC10.

[0269] In step SI120, the control unit 41 of the first terminal 4 provides the first identifier I10, the generated electronic signature CD1, and the first electronic certificate CC1 to the second terminal 5. As a result, the second terminal 5 obtains the first identifier I10, the electronic signature CD1, and the first electronic certificate CC1 from the first terminal 4. The first terminal 4 has been involved in the generation of at least a portion of the electronic information, such as information derived from the first target VA. In this case, data regarding the electronic information may be provided from the first terminal 4 to the second terminal 5 as the processing in step SI120.

[0270] Next, the control unit 51 of the second terminal 5 operates as the authentication unit 514 and verifies the validity of the first electronic certificate CC1 (steps SI130 and SI135). In the example of FIG. 18A, it is assumed that the first server 2 holds a revocation list. In step SI130, the control unit 51 of the second terminal 5 inquires of the first server 2 whether the first electronic certificate CC1 is valid or not. If the first electronic certificate CC1 is not registered in the revocation list, it is determined that the first electronic certificate CC1 is valid (i.e., the expiration date has not passed). If the first electronic certificate CC1 is registered in the revocation list, it is determined that the first electronic certificate CC1 is not valid. The first server 2 refers to the revocation list and determines whether the first electronic certificate CC1 is valid or not. In step SI135, the first server 2 returns the determination result to the second terminal 5. The control unit 51 of the second terminal 5 may also inquire of the first server 2 whether the first identifier I10 is valid or not. If the revocation list is stored in an external server, the control unit 51 of the second terminal 5 may directly or indirectly (for example, via the first server 2) inquire of the external server whether the first electronic certificate CC1 is valid. In another example, the control unit 51 of the second terminal 5 may acquire the revocation list and determine whether the first electronic certificate CC1 is valid by referring to the acquired revocation list. If the first electronic certificate CC1 is not valid (i.e., the expiration date has passed), the control unit 51 of the second terminal 5 may determine that the verification of the validity of the first electronic certificate CC1 is not established and may appropriately terminate the processing procedure of the association setting. The control unit 51 of the second terminal 5 may request the first terminal 4 to resend a series of information. On the other hand, if the first electronic certificate CC1 is valid, the control unit 51 of the second terminal 5 appropriately acquires the public key of the certification authority. The control unit 51 of the second terminal 5 decrypts the digital signature of the certification authority included in the first electronic certificate CC1 using the acquired public key. Then, the control unit 51 of the second terminal 5 compares the obtained decrypted data with the remaining information (the proprietary information and the first public key) included in the first electronic certificate CC1. If the information is encrypted after conversion to a hash value, the control unit 51 of the second terminal 5 converts the proprietary information and the first public key into a hash value using a hash function, and compares the obtained hash value with the decrypted data.If the two match, the control unit 51 of the second terminal 5 determines that the verification of the validity of the first electronic certificate CC1 is successful, and if the two do not match, it determines that the verification of the validity of the first electronic certificate CC1 is not successful.

[0271] The control unit 51 of the second terminal 5 also operates as an authentication unit 514 and verifies the validity of the electronic signature CD1 (step SI140). The control unit 51 of the second terminal 5 decrypts the electronic signature CD1 using the first public key included in the first electronic certificate CC1. The control unit 51 of the second terminal 5 compares the obtained decrypted data with the shared information (the first identifier I10 and the electronic information). If the information is encrypted after being converted into a hash value, the control unit 51 of the second terminal 5 converts the shared information (the first identifier I10 and the electronic information) into a hash value using a hash function, and compares the obtained hash value with the decrypted data. If the two match in the comparison, the control unit 51 of the second terminal 5 determines that the verification of the validity of the electronic signature CD1 is successful, and if the two do not match, determines that the verification of the validity of the electronic signature CD1 is not successful.

[0272] If the verification of the validity of both the first electronic certificate CC1 and the electronic signature CD1 is successful, authentication of the first target VA is successful. In this case, the control unit 51 of the second terminal 5 transmits a linking request including the first identifier I10 and the second identifier I20 to the management server 1 (step SI150). In response to this, the management server 1 receives the linking request from the second terminal 5. 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 VA and the second target WA. 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 process of step SI150 may be the same as the process of step S10 above. On the other hand, if the verification of the validity of at least one of the first electronic certificate CC1 and the electronic signature CD1 is not successful, the second terminal 5 may end the binding setup process as appropriate. The second terminal 5 may request the first terminal 4 to resend a series of information.

[0273] The authentication target by the fourth authentication method does not have to be limited to the first target VA. The second target WA may also be authenticated by the same method.

[0274] FIG. 18B shows a schematic diagram of another example of the process of the association setting in the case where the fourth authentication method is adopted. FIG. 18B assumes a scene where the authentication process of the second target WA is executed. Except that the first target VA and the second target WA are replaced, the process procedure and each data of FIG. 18B may be the same as the process procedure and each data of FIG. 18A. That is, in the preparation stage, a combination of the second private key CC20 and the second public key is generated. Next, a second electronic certificate CC2 for the second public key is generated by the certification authority. In one example, the second electronic certificate CC2 may be composed of the electronic signature of the certification authority, the ownership information, and the second public key. The second electronic certificate CC2 is provided from the certification authority to the second terminal 5. In the use stage, when a use relationship occurs between the corresponding individuals of the first target VA and the second target WA, data exchange is executed between the corresponding first terminal 4 and the second terminal 5 (step SJ110, step SJ120). In this data exchange, electronic information is shared between the first terminal 4 and the second terminal 5. The control unit 51 of the second terminal 5 generates an electronic signature CD2 by encrypting the second identifier I20 and electronic information using the second private key CC20. The control unit 51 of the second terminal 5 provides the second identifier I20, the generated electronic signature CD2, and the second electronic certificate CC2 to the first terminal 4. As a result, the control unit 41 of the first terminal 4 obtains the second identifier I20, the electronic signature CD2, and the second electronic certificate CC2. The control unit 41 of the first terminal 4 operates as the authentication unit 414 and verifies the validity of the second electronic certificate CC2 (steps SJ130 and SJ135). The control unit 41 of the first terminal 4 also operates as the authentication unit 414 and verifies the validity of the electronic signature CD2 (step SJ140). If the validity of both the second electronic certificate CC2 and the electronic signature CD2 is verified, the authentication of the second target WA is verified. In this case, 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 SJ150). In response to this, the management server 1 receives the linking request from the first terminal 4. The control unit 11 of the management server 1 sets a correspondence relationship between the relevant individuals of the first object VA and the second object WA in response to the linking request. The process of setting the correspondence relationship may be the same as in the above embodiment.On the other hand, if the verification of the validity of at least one of the second electronic certificate CC2 and the electronic signature CD2 is not successful, the first terminal 4 may end the binding setting process as appropriate. The first terminal 4 may request the second terminal 5 to resend a series of information. In another example, the authentication process of the first target VA and the second target WA may be performed by executing the series of processes in Figures 18A and 18B.

[0275] When adopting an omission form of the authentication process similar to the above embodiment, in the normal processing mode, the authentication process of the first target VA and the second target WA according to Fig. 18A and Fig. 18B may be executed. On the other hand, in the simplified processing mode, the authentication process of either the first target VA or the second target WA may be omitted.

[0276] In the fourth authentication method, at least one of the first target VA and the second target WA is authenticated using a private key and an electronic certificate. This is expected to ensure security. Also, by performing authentication processing on the terminal side before a linking request, it is expected to reduce the processing load on the management server 1. Also, the processing time from the linking request to the setting process can be shortened.

[0277] Note that the processing procedures in FIG. 18A and FIG. 18B are merely examples, and each step may be changed as far as possible. In addition, the steps of the above processing procedures may be changed as appropriate according to the embodiment. Omissions, substitutions, and additions are possible. For example, in the processing procedure of Fig. 18A, the processing order of verifying the validity of the first electronic certificate CC1 (steps SI130 and SI135) and verifying the validity of the electronic signature CD1 (step SI140) may be changed as appropriate. In another example, the verification of the validity of the electronic signature CD1 may be performed before the verification of the validity of the first electronic certificate CC1. The verification process of the validity of the first electronic certificate CC1 and the verification process of the validity of the electronic signature CD1 may be performed at least partially in parallel. The same applies to the relationship between the verification of the validity of the second electronic certificate CC2 and the verification of the validity of the electronic signature CD2.

[0278] Also, similarly to the above <4.1>, in the normal processing mode, at least one of the authentication processes of the first target VA and the second target WA according to Fig. 18A and Fig. 18B may be executed. On the other hand, in the simplified processing mode, the authentication processes of both the first target VA and the second target WA may be omitted.

[0279] [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.

[0280] 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.

[0281] 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]

[0282] 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, VA: 1st target, WA: 2nd target, 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 the first target, and A second terminal of the second target; Equipped with At least one of the first terminal and the second terminal is configured to transmit a binding request to the management server in response to the occurrence of a usage relationship between the first target and the second target; the management server is configured to set a correspondence relationship between the first object and the second object based on the association request; The setting of the correspondence relationship includes: If certain conditions are not met, obtaining authentication results of the first object and the second object together; and setting a correspondence relationship between the first target and the second target according to the fact that authentication of both the first target and the second target is established in the acquired authentication results of the first target and the second target; and If the predetermined condition is satisfied, Omitting authentication of one of the first target and the second target and acquiring an authentication result of the other target; and setting a correspondence relationship between the first target and the second target in response to authentication of the other target being established in the obtained authentication result; Consists of: system.

2. the first object is a user, The second object is a use object used by the user, The predetermined condition includes that the object is a regular object that is repeatedly used by the user. The system of claim 1 .

3. The predetermined condition includes that a correspondence relationship has been set in the past for the same combination of the first object and the second object. The system of claim 1 .

4. The predetermined condition includes that the type of at least one of the first object and the second object is a specific type. The system of claim 1 .

5. the predetermined condition includes that a correspondence relationship has been set in the past for the same combination of the first object and the second object, and that at least one of the first object and the second object is a specific type. The system of claim 1 .

6. the first object is a user, The second object is a use object used by the user, The type of at least one of the first object and the second object being a specific type includes that the object is a regular object that is repeatedly used by the user. The system of claim 5.

7. The object of use is a moving object. The system of claim 6.

8. The regularly used object is a personal car. The system of claim 7.

9. the first object is a user, The second object is a use object used by the user, When the predetermined condition is satisfied, authentication of one of the first object and the second object is authentication of the object of use, and authentication of the other object is authentication of the user. The system of claim 1 .

10. 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 .

11. The success or failure of authentication of the first target and the second target is determined by the management server or an external server. The system of claim 1 .

12. Upon occurrence of a usage relationship between the first object and the second object, the first terminal and the second terminal are configured to perform data exchange. The system of claim 1 .

13. The data exchange is performed by short-range wireless communication. The system of claim 12.

14. 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 first object and the second object, 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 locations of the first terminal and the second terminal satisfy the condition of the usage relationship, maintaining the setting of the correspondence relationship between the first object and the second object, and if not, canceling the correspondence relationship. Further configured as follows: The system of claim 1 .

15. When a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target; a control unit configured to execute The setting of the correspondence relationship includes: If certain conditions are not met, obtaining authentication results of the first object and the second object together; and setting a correspondence relationship between the first target and the second target according to the fact that authentication of both the first target and the second target is established in the acquired authentication results of the first target and the second target; and If the predetermined condition is satisfied, Omitting authentication of one of the first target and the second target and acquiring an authentication result of the other target; and setting a correspondence relationship between the first target and the second target in response to authentication of the other target being established in the obtained authentication result; Consists of: Management server.

16. the first object is a user, The second object is a use object used by the user, The predetermined condition includes that the object is a regular object that is repeatedly used by the user. The management server according to claim 15.

17. the predetermined condition includes that a correspondence relationship has been set in the past for the same combination of the first object and the second object, and that at least one of the first object and the second object is a specific type. The management server according to claim 15.

18. When a usage relationship occurs between a first target and a second target, setting a correspondence relationship between the first target and the second target based on a linking request transmitted from at least one of a first terminal of the first target and a second terminal of the second target; a control unit configured to execute The setting of the correspondence relationship includes: If certain conditions are not met, obtaining an authentication result of at least one of the first target and the second target; and setting a correspondence relationship between the first object and the second object according to a result of authentication being obtained, and omitting authentication of both the first target and the second target when the predetermined condition is satisfied, and setting a correspondence relationship between the first target and the second target in response to receiving the association request; Consists of: Management server.

19. On the first terminal of the first target, When a usage relationship occurs between the first target and the second target, the management server sets a correspondence relationship between the first target and the second target by transmitting a linking request to a management server, transmitting the linking request in cooperation with a second terminal of the second target, or causing the management server to transmit the linking request to the second terminal; A program for executing If certain conditions are not met, The association request includes a request to authenticate the first object and the second object, setting a correspondence relationship between the first object and the second object is configured by setting a correspondence relationship between the first object and the second object in response to authentication of the first object and the second object performed based on the authentication request being both established, If the predetermined condition is met, An authentication request for one of the first target and the second target is omitted, and the linking request includes an authentication request for the other target, Setting a correspondence relationship between the first object and the second object is configured by setting a correspondence relationship between the first object and the second object in response to authentication of the other object performed based on the authentication request being established. program.

20. On the first terminal of the first target, When a usage relationship occurs between the first target and the second target, the management server sets a correspondence relationship between the first target and the second target by transmitting a linking request to a management server, transmitting the linking request in cooperation with a second terminal of the second target, or causing the management server to transmit the linking request to the second terminal; A program for executing If certain conditions are not met, the linking request includes a request to authenticate at least one of the first target and the second target, setting a correspondence relationship between the first object and the second object is configured by setting a correspondence relationship between the first object and the second object in response to authentication of at least one of the first object and the second object being established based on the authentication request, If the predetermined condition is met, Both authentication requests for the first object and the second object are omitted from the binding request; Setting a correspondence relationship between the first object and the second object is configured to set a correspondence relationship between the first object and the second object in response to receiving the linking request. program.

Images