System, management server and management method

Abstract

To provide a technology for properly tracking use relation between a first object and a second object.SOLUTION: A management server according to one aspect of the present disclosure receives setting of correspondence by receiving a linking request in response use relation occurring between a first object and a second object. When the management server receives the setting of second correspondence between a first first object and a second second object different from a first second object while the setting of first correspondence between the first first object and the first second object is established, the management server (I) cancels the first correspondence and establishes the setting of the second correspondence, or (II) does not allow the setting of the second correspondence and maintains the setting of the first correspondence, in accordance with a predetermined rule.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a system, a management server, and a management method. [Background technology]

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

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

[0004] One objective of the present disclosure is to provide a technique for appropriately tracking a usage relationship between a first object and a second object. [Means for solving the problem]

[0005] The system according to the first aspect of the present disclosure includes a management server, a plurality of first terminals corresponding to each of the first targets, and a plurality of second terminals corresponding to each of the second targets. The plurality of first terminals and the plurality of second terminals are configured such that, in response to the occurrence of a usage relationship between the first target and the second target, at least one of the first terminal corresponding to the first target and the second terminal corresponding to the second target transmits a linking request to the management server. The management server is configured to accept a setting of a correspondence relationship between the first target and the second target upon receiving the linking request, and to execute, in accordance with a predetermined rule, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, when accepting a setting of a second correspondence relationship between the first first target and the first second target while the setting of the first correspondence relationship between the first first target and the first second target is established.

[0006] A management server according to a second aspect of the present disclosure includes a control unit configured to receive a linking request from at least one of a first terminal of a first target and a second terminal of a second target in response to the occurrence of a usage relationship between a first target and a second target, and to accept, upon receiving the linking request, a setting of a correspondence relationship between the first target and the second target, and, when a setting of a second correspondence relationship between the first first target and a second second target different from the first second target is accepted while the setting of a first correspondence relationship between a first first target and a first second target is established, to (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) not allow the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule.

[0007] A management method according to a third aspect of the present disclosure includes a management server receiving a linking request from at least one of a first terminal of the first target and a second terminal of the second target in response to the occurrence of a usage relationship between the first target and the second target; The information processing method includes accepting a setting of a correspondence relationship between the second objects, and, if a setting of a second correspondence relationship between the first first object and a second second object different from the first second object is accepted while a setting of a first correspondence relationship between a first first object and a first second object is established, (I) canceling the first correspondence relationship and establishing the setting of the second correspondence relationship, or (II) not allowing the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship, according to a predetermined rule. Effect of the Invention

[0008] According to the present disclosure, it is possible to provide a technique for appropriately tracking a usage relationship between a first object and a second object. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a situation to which the present disclosure is applied. [Diagram 2] FIG. 2 shows a schematic diagram of an example of a scenario to which the present disclosure is applied. [Figure 3A] FIG. 3A illustrates an example of the linking information according to the present embodiment. [Figure 3B] FIG. 3B illustrates an example of user information according to the present embodiment. [Figure 3C] FIG. 3C illustrates an example of moving object information according to the present embodiment. [Figure 4] FIG. 4 illustrates an example of the arbitration process according to the present embodiment. [Diagram 5] FIG. 5 illustrates an example of the arbitration process according to the present embodiment. [Figure 6A] FIG. 6A illustrates an example of arbitration processing based on the success or failure of a predetermined relationship according to this embodiment. [Figure 6B] FIG. 6B illustrates an example of arbitration processing based on the success or failure of a predetermined relationship according to this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a scene in which the association setting according to the present embodiment is locked. [Figure 8] FIG. 8 shows an example of a process of canceling a link 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 terminal according to the present embodiment. [Figure 10C] FIG. 10C illustrates an example of a hardware configuration of the 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 12] FIG. 12 shows an example of a processing procedure for link setting according to the present embodiment. [Figure 13] FIG. 13 shows an example of a processing procedure for canceling association according to this embodiment. [Figure 14] FIG. 14 shows an example of a process of linking settings when the first authentication method is adopted. [Figure 15] FIG. 15 shows an example of a process of linking settings when the second authentication method is adopted. [Figure 16] FIG. 16 shows an example of a process of linking settings when the 3-1 authentication method is adopted. [Figure 17A] FIG. 17A illustrates an example of a process for setting association when the 3-2 authentication method is adopted. [Figure 17B] FIG. 17B illustrates another example of the process of linking settings when the 3-2 authentication method is adopted. [Figure 18A] FIG. 18A illustrates an example of a process of association setting in the case where the fourth authentication method is adopted. [Figure 18B] FIG. 18B illustrates another example of the process of linking settings when the fourth authentication method is adopted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0011] That is, with the diversification of MaaS (Mobility as a Service), it is considered that there will be a demand for appropriately tracking the use of a mobile object by a user from the viewpoint of convenience such as efficient payment. In contrast, in a conventional system, it is possible to hold the correspondence between the use date and time and the user as usage information according to the rental car contract or reservation, but since this usage date and time 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 a vehicle used without a contract or reservation (e.g., a private car), the generation of usage information is not assumed in the first place. Therefore, according to the conventional system, it is difficult to appropriately track the use of a mobile object by a user. Note that this problem does not occur only in a situation where a vehicle is used. The same problem may occur in a situation where a mobile object other than a vehicle (e.g., an aircraft, a ship, etc.) is used and in a situation where multiple types of mobile objects are used. Furthermore, the same problem may occur in any usage situation other than a mobile object.

[0012] In contrast, a system according to a first aspect of the present disclosure includes a management server, a plurality of first terminals corresponding to each of the first targets, and a plurality of second terminals corresponding to each of the second targets. The plurality of first terminals and the plurality of second terminals are configured such that, in response to the occurrence of a usage relationship between the first target and the second target, at least one of the first terminal corresponding to the first target and the second terminal corresponding to the second target transmits a linking request to the management server. The management server is configured to receive the linking request and, when receiving the linking request, to (I) cancel the first correspondence relationship and establish the second correspondence relationship, or (II) not permit the second correspondence relationship to be set and maintain the first correspondence relationship, according to a predetermined rule.

[0013] In the first aspect of the present disclosure, the use relationship between the first object and the second object can be traced by setting a correspondence relationship between the first object and the second object (linking setting). In addition, in the first aspect of the present disclosure, when multiple correspondence relationship settings are generated (linking settings collide), a correspondence relationship setting to be maintained is selected by mediating according to a predetermined rule. Therefore, according to the first aspect of the present disclosure, the use relationship between the first object and the second object can be appropriately traced.

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

[0015] For example, the management server according to the second aspect of the present disclosure may be configured to, in response to the occurrence of a usage relationship between a first target and a second target, obtain a link from at least one of a first terminal of the first target and a second terminal of the second target. The control unit may be configured to receive a linking request, accept the setting of a correspondence relationship between the first object and the second object upon receiving the linking request, and, when a setting of a second correspondence relationship between the first object and the first second object different from the first object is accepted while the setting of a first correspondence relationship between the first object and the first second object has been established, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) not allow the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule.

[0016] Furthermore, for example, a management method according to a third aspect of the present disclosure may be an information processing method in which a management server receives a linking request from at least one of a first terminal of the first target and a second terminal of the second target in response to the occurrence of a usage relationship between the first target and the second target, accepts the setting of a correspondence relationship between the first target and the second target upon receiving the linking request, and, when a setting of a second correspondence relationship between the first first target and a second second target different from the first first target and the first second target is accepted while the setting of a first correspondence relationship between the first first target and the first second target is established, (I) cancels the first correspondence relationship and establishes the setting of a second correspondence relationship, or (II) does not allow the setting of the second correspondence relationship and maintains the setting of the first correspondence relationship, according to a predetermined rule.

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

[0018] [1 Application example] 1 is a schematic diagram showing an example of a situation in which the present disclosure is applied. The system 100 according to this embodiment is composed of a management server 1, a plurality of first terminals 4, and a plurality of second terminals 5. The management server 1 is one or more computers configured to record the correspondence (linking) between first target VAs and second target WAs. Each first terminal 4 corresponds to each first target VA, and each second terminal 5 corresponds to each second target WA.

[0019] In this embodiment, the multiple first terminals 4 and the multiple second terminals 5 are configured such that, in response to the occurrence of a usage relationship between the first target VA and the second target WA, at least one of the first terminal 4 corresponding to the first target VA and the second terminal 5 corresponding to the second target WA transmits a linking request to the management server 1. 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 one first terminal 4 corresponding to the corresponding individual of the first target VA and one second terminal 5 corresponding to the corresponding individual of the second target WA transmits a linking request to the management server 1 (step S10).

[0020] 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 a correspondence relationship between the first target VA and the second target WA (step S20). In response to the accepted linking request, the management server 1 sets a correspondence relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA (step S30).

[0021] In this process, if there is no correspondence setting between the relevant individual of the first target VA that is the subject of the linking request and another second target WA (another individual of the second target WA) different from the second target WA that is the pair of the linking request, no collision of linking settings will occur. The absence of a correspondence setting with another second target WA means that no correspondence setting with multiple second target WAs is established for the same first target VA. Therefore, in such a case, the management server 1 may set the correspondence relationship between the relevant individual of the first target VA and the relevant individual of the second target WA as it is.

[0022] On the other hand, if a corresponding relationship between the individual of the first target VA and another second target WA already exists, the same first target VA will have a plurality of corresponding relationships with the second target WA, resulting in a collision of the linking settings. The fact that a corresponding relationship with another second target WA already exists when a linking request is received corresponds to the fact that a second corresponding relationship between the first first target VA1 and a second second target WA2 different from the first second target WA1 has been received while a first corresponding relationship between the first first target VA1 and the first second target WA1 has been received. In such a case, the management server 1, according to a predetermined rule, (I) cancels the first corresponding relationship and establishes a second corresponding relationship, or (II) does not permit the second corresponding relationship to be set and maintains the first corresponding relationship. Selecting (I) corresponds to selecting a new corresponding relationship (second corresponding relationship) as the corresponding relationship to be held, and selecting (II) corresponds to selecting an existing corresponding relationship (first corresponding relationship) as the corresponding relationship to be held. Not permitting the setting of the second correspondence relationship corresponds to rejecting the association request for setting the second correspondence relationship, whereby the management server 1 mediates the collision of association settings.

[0023] The first first object VA1 is an individual of the first object VA that has accepted the setting of the correspondence relationship. The first first object VA1 may be referred to as the first individual of the first object VA. The first second object WA1 is an individual of the second object WA that has previously established the setting of the correspondence relationship (first correspondence relationship) with the first first object VA1. The first second object WA1 may be referred to as the first individual of the second object WA. The second second object WA2 is an individual of the second object WA that newly requests the setting of the correspondence relationship with the first first object VA1 while the first correspondence relationship is established. The second second object WA2 may be referred to as the second individual of the second object WA. In the following description, for convenience, the first terminal 4 of the first first object VA1 will also be referred to as the "first first terminal 4_1," the second terminal 5 of the first second object WA1 will also be referred to as the "first second terminal 5_1," and the second terminal 5 of the second second object WA2 will also be referred to as the "second second terminal 5_2."

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

[0025] Furthermore, as long as each individual for which a correspondence relationship is set can be identified, the expression 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 target VA, and each individual of the first target VA may be identified by the first identifier I10. Similarly, a second identifier I20 may be given to each second target WA, and each individual of the second target WA may be identified by the second identifier I20. Accordingly, setting the correspondence relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA may be configured by setting a correspondence relationship between the first identifier I10 given to the corresponding individual of the first target VA and the second identifier I20 given to the corresponding individual of the second target WA. That is, the setting of the correspondence relationship is expressed using the first identifier I10 and the second identifier I20. It is okay to do so.

[0026] As described above, in this embodiment, by setting the correspondence between the first target VA and the second target WA, the usage relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA can be traced. In addition, in this embodiment, when a linking setting occurs between one individual of the first target VA and multiple individuals of the second target WA, the management server 1 resolves the collision of the linking setting by performing an arbitration process to select the correspondence to be held according to a predetermined rule. Therefore, according to this embodiment, the correspondence between the first target VA and the second target WA can be appropriately traced.

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

[0028] In this embodiment, when a pegging setting is established for a corresponding individual of the first target VA with each of the multiple individuals of the second target WA, the management server 1 executes an arbitration process to select one pegging setting from the multiple pegging settings as the pegging setting to be held. This arbitration process resolves the collision of pegging settings. In contrast, the handling of pegging settings for a corresponding individual of the second target WA with each of the multiple individuals of the first target VA may be the same as that of the first target VA, or may be different. That is, when a pegging setting is established for a corresponding individual of the second target WA with each of the multiple individuals of the first target VA, the management server 1 may execute an arbitration process to select one pegging setting from the multiple pegging settings as the pegging setting to be held, as in the case of the first target VA. Alternatively, the management server 1 may not execute the arbitration process, and may allow multiple pegging settings for the same second target WA (the same individual of the second target WA). For example, assume a situation in which the first target VA is a user and the second target WA is a moving object. When a moving object is available to multiple users (for example, the moving object is a vehicle capable of carrying multiple passengers), the linking settings of the multiple users for the same moving object may be properly established. In such a case, the establishment of multiple linking settings for the same individual second object WA may be permitted. Of the two objects that track the usage relationship, one object that does not permit the establishment of multiple linking settings may be selected as the first object VA, and the other object that permits the establishment of multiple linking settings may be selected as the second object WA.

[0029] (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, each first terminal 4 may accompany the corresponding first target VA, and each 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.

[0030] (Target information) 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. 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 first target information O10 and the second target information O20 may be stored in any storage area. At least a portion of the first target information O10 and the second target information O20 may be stored so as to be accessible from at least one of the management server 1, the external server, and each terminal (4, 5).

[0031] The first target information O10 and the second target information O20 may be managed appropriately. 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 manage the second target information O20. The first server 2 and the second server 3 may each be configured with 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 of the target information (O10, O20) may be stored in a memory resource of the management server 1.

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

[0033] In one example, at least one of sending the linking request and accepting the setting of the correspondence relationship may include authenticating at least one of the corresponding individual of the first target VA and the corresponding individual of the second target WA. The authentication of the corresponding individual may be performed by any method. The authentication process may be performed by at least one of the terminals (4, 5), an external server (e.g., the first server 2, the second server 3), and the management server 1. In one example, each target information (O10, O20) may include information (registered unique information, etc.) used to authenticate each target (VA, WA). In another example, each server (2, 3) may issue information (time-limited certificate) used to authenticate each target (VA, WA). When at least a part of the authentication process is performed by the external server or the management server 1, the linking request may include data used for authentication. The management server 1 may be configured to execute the linking setting process (step S30) only when authentication is established.

[0034] (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 are not particularly limited and may be appropriately selected depending on the embodiment. In one example, each identifier (I10, I20) may be composed of a symbol string including numbers, letters, etc. In another example, each identifier (I10, I20) may include a unique identifier for each target. The unique information may be, for example, identification information uniquely assigned to the object (VA, WA), information derived from each terminal (4, 5), etc. The unique identification information may be, for example, a vehicle registration number, a vehicle identification number (VIN: Vehicle Identification Number), a personal number, etc. When an IC tag is assigned to the object, the unique identification information may include information held by the IC tag. The information derived from each terminal (4, 5) may be, 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).

[0035] (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. 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 computer (e.g., the first server 2, the second server 3, etc.). That is, transmitting the linking request to the management server 1 may include directly transmitting the linking request to the management server 1 and indirectly transmitting it via an external computer. 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 transmitting 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. That is, the linking request may be transmitted from the external computer to the management server 1 as a result of data communication for another purpose to the external computer.

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

[0037] In one example, before executing the above process (I), the management server 1 may directly or indirectly send an inquiry requesting permission to execute the process (I) to at least one of the first first terminal 4_1 and the second second terminal 5_2. At least one of the first first terminal 4_1 and the second second terminal 5_2 may appropriately generate a response to this inquiry. The management server 1 may execute the above process (I) by obtaining a response of permission from at least one of the first first terminal 4_1 and the second second terminal 5_2.

[0038] The management server 1 may be configured by one or more server devices. The 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 inside and / or outside the management server 1. The internal memory resource may include, for example, a RAM, an auxiliary storage device, a storage medium, etc. The external memory resource may include, for example, an external storage device, an external computer (NAS, etc.), etc.

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

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

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

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

[0043] 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 depending on the embodiment. In one example, the object of use may be a moving object (mobility). According to one example of the present embodiment, it is possible to track the usage relationship between the user and the moving object. The type of the moving object may be appropriately selected. The moving object may be, for example, a vehicle, a railroad car, an aircraft (aircraft, drone, etc.), a ship, etc. The moving object may be manually controlled. The moving body may be at least one of a manned aircraft and an automatically controlled unmanned aircraft. When the moving body is a vehicle, the type of the vehicle may be selected arbitrarily. The type of the vehicle may be selected from, for example, two-wheeled vehicles, three-wheeled vehicles, four-wheeled vehicles, 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 autonomous vehicle and a manually driven vehicle. The on-board terminal may be referred to as a mobile terminal.

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

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

[0046] 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, a MAC address, terminal identification information). 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 an electronic prescription (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, a business operator (such as a vehicle manufacturer or a service operating company), etc. The first server 2 may be called a user ID server, a my ID server, etc.

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

[0048] 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, it may be enabled (activated) for the mobile body to exercise at least a part of the authority of various information E10 associated with the user information O10A. 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. It is okay to do so.

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

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

[0051] In addition, objects of use 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 will be referred to as "objects of regular use" and the latter as "objects of temporary use." An example of an object of regular use is an object owned by a user, such as a personal car. An example of an object of temporary use is an object owned by a person other than the user, such as a rental car, a shared car, a moving object of public transportation, a rental object, or an accommodation facility. Examples of moving objects of public transportation include taxis, buses, railroad cars, airplanes, and ships.

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

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

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

[0055] As a specific example, one of the first target VA and the second target WA may be a large autonomous vehicle, and the other may be a small autonomous vehicle. The large autonomous vehicle may be configured to accommodate multiple small autonomous vehicles. A small autonomous vehicle may not be able to ride in multiple large autonomous vehicles at the same time (i.e., at a time, a small autonomous vehicle can only be accommodated by one large autonomous vehicle). Accordingly, the first target VA may be a small autonomous vehicle, and the second target WA may be a large autonomous vehicle. A large The autonomous vehicle may collect, transport, and release each small autonomous vehicle as appropriate. Each small autonomous 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 between the large autonomous vehicle and the small autonomous vehicle, switching the status, and canceling the status.

[0056] (Data Exchange) In this embodiment, a series of processes related to the association setting may be started with data exchange between the first terminal 4 and the second terminal 5 as a trigger. That is, the occurrence of a usage relationship (start of usage) may be detected by data exchange. The method of data exchange is not particularly limited and may be appropriately selected depending on the embodiment.

[0057] 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 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 terminal reading the displayed data using a sensor such as an image sensor.

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

[0059] 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 the second identifier I20 by a spontaneous operation. In one example, the first terminal 4 may acquire the second identifier I20 from the second terminal 5 through data communication. In another example, the first terminal 4 may acquire the second identifier I20 from the second terminal 5 through data communication. The second identifier I20 may be acquired from the second terminal 5 by a method other than data communication, such as reading the second identifier I20. 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.

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

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

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

[0063] (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 may include at least one of an expiration date and a flag, along with a field for the release time. Note that if the association setting can be indicated, the association information D The configuration of the association information D10 is not limited to the example of FIG. 3A, and may be appropriately changed depending on the embodiment. In another example, the association 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). Note that the type of the usage object does not necessarily need to be identified by separate information. For example, the type of the usage object may be identified by information such as an identifier.

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

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

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

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

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

[0069] 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 mobile object model, 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 may be defined to indicate a category that can distinguish between a regular use object and a temporary use object, such as a private car, a rental car, a shared car, or a public transportation mobile object. The type of mobile object indicates, for example, a type of vehicle, etc. The type of mobile object and the type (type of object) are If they are the same, the mobile object type field may be omitted. The owner information may include any information related to the owner of the mobile object. The owner information may include personal information of the owner, such as, for example, name, address, age, sex, and contact information. The owner may be a corporation. The configuration of the mobile object information O20A is not limited to the example of FIG. 3C and may be changed as appropriate depending on 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 terminal, such as the contact information of the mobile terminal.

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

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

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

[0073] (Prescribed rules) The predetermined rule is configured to mediate a collision of the association settings, that is, to specify which of the first association and the second association should be selected when the above-mentioned first and second association settings are established. If the collision of the association settings can be mediate, the predetermined rule is not particularly limited and may be appropriately specified according to the embodiment. In a simple example, the predetermined rule may include prioritizing the earliest association request. When the predetermined rule of this mode is used, the management server 1 may select (I) to release the first association and to establish the second association in response to a request for association with the second target WA2. In addition, the predetermined rule may include at least one of the following three rules.

[0074] (1) First rule FIG. 4 shows a schematic diagram of an example of arbitration processing according to a first rule in this embodiment. In this example of this embodiment, the first rule may be to follow the selection by the first target VA. The predetermined rule may include the first rule. In this case, the management server 1 may be further configured to receive a selection result ST10 by the first first target VA1. Then, when a second correspondence relationship (second second target WA2) is selected in the received selection result ST10, the management server 1 (I) cancels the first correspondence relationship and sets the second correspondence relationship. On the other hand, if the first correspondence relationship (first second target WA1) is selected in the received selection result ST10, the management server 1 may (II) not permit the setting of the second correspondence relationship and may maintain the setting of the first correspondence relationship.

[0075] In addition, selecting the correspondence relationship may include directly selecting the correspondence relationship to be held, and indirectly selecting the correspondence relationship to be held by selecting the correspondence relationship to be released. Selecting the correspondence relationship may include selecting the corresponding second object WA. The selection may be performed by automatic processing by a computer (terminal) or may be performed manually (by a user operation).

[0076] Furthermore, the selection result ST10 may be generated by at least one of the first first terminal 4_1 of the first first object VA1 and the second second terminal 5_2 of the second second object WA2. In some cases, the selection result ST10 may be generated by the first second terminal 5_1 of the first second object WA1. In the case of manual selection, at least one of the first first terminal 4_1, the first second terminal 5_1, and the second second terminal 5_2 may accept the selection at any timing.

[0077] Furthermore, the selection result ST10 may be directly or indirectly transmitted to the management server 1 from at least one of the first first terminal 4_1, the first second terminal 5_1, and the second second terminal 5_2. In one example, the selection result ST10 may be transmitted from one of the first terminal 4 and the second terminal 5 that has accepted the selection. In another example, the selection result ST10 may be transmitted from another terminal different from the one of the first terminal 4 and the second terminal 5 that has accepted the selection by data exchange.

[0078] Moreover, the selection result ST10 may be acquired at any timing before the arbitration process is executed. In one example, at least one of the first first terminal 4_1, the first second terminal 5_1, and the second second terminal 5_2 may transmit the selection result ST10 to the management server 1 as a spontaneous information process accompanying a linking request. In another example, at least one of the first first terminal 4_1, the first second terminal 5_1, and the second second terminal 5_2 may transmit the selection result ST10 to the management server 1 as a reply to an inquiry from the management server 1. The transmitted selection result ST10 may be appropriately configured to indicate the selection result by the first first target VA1. According to one example of this embodiment, the correspondence relationship to be held can be selected by a simple process.

[0079] (2) Second rule 5 is a schematic diagram showing an example of an arbitration process according to the second rule of this embodiment. In a specific situation, if a certain relationship is established, the setting of the second correspondence relationship is not permitted (selecting (II)), and if the certain relationship is not established, the setting of the second correspondence relationship is permitted (selecting (I)), so that it may be possible to appropriately track the usage relationship between the first target VA and the second target WA.

[0080] For example, in the scene of Fig. 2, if the first second object WA1 is a rental car, from the viewpoint of prohibiting overlapping rentals during the rental period of the rental car that is the first second object WA1, it may be possible to appropriately trace the usage relationship by prohibiting the establishment of a corresponding relationship with another rental car as the second second object WA2. On the other hand, from the viewpoint of multimodality, such as parking a rental car in a parking lot and using a train, it may be possible to appropriately trace the usage relationship by permitting the establishment of a corresponding relationship with another type of moving object as the second second object WA2, even during the rental period of the rental car that is the first second object WA1.

[0081] In the above example, the predetermined relationship is the first second object WA1 and the second second object WA2. The relationship between the first and second targets WA is taken into consideration. However, the relationship to be taken into consideration does not have to be limited to the relationship between the second targets WA. The relationship between the first target VA (first first target VA1) may be taken into consideration as the predetermined relationship. For example, assume a situation in which the first target VA and the second target WA exist in the real world, and the usage relationship occurs when the first target VA and the second target WA are in close proximity to each other. In this situation, when the second second target WA2 (second second terminal 5_2) is far enough away from the first first target VA1 (first first terminal 4_1) that the usage relationship is not satisfied, the usage relationship may be appropriately traced by prohibiting the establishment of the corresponding relationship with the second second target WA2. On the other hand, when the second second target WA2 is close enough to the first first target VA1 that the usage relationship is satisfied, the usage relationship may be appropriately traced by permitting the establishment of the corresponding relationship with the second second target WA2. In this way, it may be desirable from the perspective of properly tracking usage relationships to control whether to prohibit or permit updating of the correspondence relationship settings depending on whether a specified relationship is established between at least one of the first first object VA1, the first second object WA1, and the second second object WA2.

[0082] Therefore, in an example of this embodiment, the second rule may prohibit updating of the setting of the correspondence relationship in response to the establishment of a predetermined relationship between at least one of the first first target VA1, the first second target WA1, and the second second target WA2. The predetermined rule may include the second rule. In response to this, when the predetermined relationship is not established between at least one of the first first target VA1, the first second target WA1, and the second second target WA2, the management server 1 may (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship. On the other hand, when the predetermined relationship is established between at least one of the first first target VA1, the first second target WA1, and the second second target WA2, the management server 1 may (II) not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship.

[0083] Whether or not a predetermined relationship is established may be appropriately determined depending on the embodiment. Any information may be used for the determination. The management server 1 may determine whether or not a predetermined relationship is established using information such as each target information (O10, O20) and information obtained from each terminal (4, 5). When each identifier (I10, I20) indicates an attribute such as the type of each target (VA, WA), the information used for the determination may include each identifier (I10, I20). The information used for the determination may be acquired at any timing before the arbitration process is executed. The management server 1 may acquire the information from at least one of an external server (for example, the first server 2, the second server 3, an external system, etc.) and each terminal (4, 5). In one example, when the information used for the determination is acquired 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 information to the management server 1 by a spontaneous operation accompanying the association request. In another example, at least one of the first terminal 4 and the second terminal 5 may transmit the information to the management server 1 as a reply to an inquiry from the management server 1. The predetermined relationship may be appropriately defined according to the embodiment so as to specify a relationship that prohibits updating of the setting of the correspondence relationship.

[0084] (2-1) Rule 2-1 In one example, focusing on the relationship between the second targets WA, the 2-1 rule may prohibit updating of the setting of the correspondence relationship between the second targets WA where a predetermined relationship is established. The second rule may include the 2-1 rule. In response to this, when a predetermined relationship is not established between the first second target WA1 and the second second target WA2, the management server 1 may (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship. On the other hand, when a predetermined relationship is established between the first second target WA1 and the second second target WA2, the management server 1 may (II) not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship. According to one example of the present embodiment, by using the relationship between the second targets WA, appropriate arbitration for the collision of the association setting can be expected.

[0085] (2-1-1) FIG. 6A is a schematic diagram showing an example of an arbitration process based on the success or failure of a predetermined relationship according to the present embodiment. To deal with the above example of a rental car, the predetermined relationship between the second target WAs may include being of the same type. That is, the rule 2-1 may include prohibiting the update of the setting of the correspondence relationship between the second target WAs of the same type and permitting the update of the setting of the correspondence relationship between the second target WAs of different types. In response to this, when the type of the second second target WA2 is different from the type of the first second target WA1, the management server 1 may (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship. On the other hand, when the type of the second second target WA2 is the same as the type of the first second target WA1, the management server 1 may (II) not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship.

[0086] The type of each second target (WA1, WA2) may be determined appropriately. In one example, the type of each second target (WA1, WA2) may be determined by information such as the second target information O20 (mobile object information O20A) and the second identifier I20. In the example of FIG. 2, the type of each second target (WA1, WA2) may be at least one of the above types and mobile object species included in the mobile object information O20A. According to one example of this embodiment, by using the relationship between the types of the second targets WA, appropriate arbitration for collisions in the linking settings can be expected.

[0087] The type of object to be arbitrated by this rule may be appropriately selected according to the embodiment. In one example, the first object VA may be a user, and the second object WA may be an object used by the user. The 2-1 rule may include prohibiting the updating of the correspondence setting between rental objects. In this case, being rental objects is an example of being the same type. That is, when the type of the first second object WA1 is a rental object, and the type of the second second object WA2 is not a rental object, the management server 1 may (I) cancel the first correspondence and establish the setting of the second correspondence. On the other hand, when the type of the second second object WA2 is a rental object, the management server 1 may (II) not permit the setting of the second correspondence and maintain the setting of the first correspondence. According to one example of the present embodiment, by prohibiting overlapping rentals, appropriate arbitration for the collision of the association setting can be expected.

[0088] The type of the use object may not be particularly limited and may be appropriately selected depending on the embodiment. In one example, the use object may be a vehicle. The rental object may be a rental car. In one example of the present embodiment, in a scene in which a rental car appears, appropriate mediation for a clash of linking settings can be expected.

[0089] In addition, there are cases where the usage period (e.g., rental car contract period, etc.) is regulated by the type of the second target WA, such as the rental item. In this case, if the correspondence relationship (first correspondence relationship) between the second target WA and the relevant individual is cancelled during the usage period by the process (I) above, the management server 1 may suspend the setting of the correspondence relationship (first correspondence relationship) between the second target WA and the relevant individual until the usage period has elapsed. Then, during the suspension, after other correspondence relationships (second correspondence relationships) are cancelled, the management server 1 may restore the setting of the correspondence relationship (first correspondence relationship) between the second target WA and the relevant individual. This allows the setting of the correspondence relationship with the second target WA during the usage period to be quickly restored.

[0090] (2-2) Rule 2-2 FIG. 6B shows an example of an arbitration process based on the success or failure of a predetermined relationship according to this embodiment. In one example, focusing on the relationship between the positions of the above targets (VA, WA), rule 2-2 may be such that if the relationship between the current positions of the first terminal 4 and the second terminal 5 does not satisfy the conditions of the usage relationship, setting of a correspondence relationship with the second target WA corresponding to the second terminal 5 is not permitted. The second rule may include rule 2-2. If the second terminal 5 (second target WA) is the first terminal Not being located within the range in which the utilization relationship of 4 (first target VA) is established is an example of a predetermined relationship.

[0091] In this case, each first terminal 4 may include a positioning module 47. Each second terminal 5 may include a positioning module 57. When the management server 1 accepts the setting of the second correspondence relationship, the management server 1 may further be configured to acquire, from the first first terminal 4_1 corresponding to the first first object VA1, a current position RP10 of the first first terminal 4_1 measured by the positioning module 47 of the first first terminal 4_1, and acquire, from the second second terminal 5_2 corresponding to the second second object WA2, a current position RP20 of the second second terminal 5_2 measured by the positioning module 57 of the second second terminal 5_2. When the relationship of the acquired current positions (RP10, RP20) between the first first terminal 4_1 and the second second terminal 5_2 satisfies the condition of the usage relationship, the management server 1 may (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship. On the other hand, if the relationship between the current locations (RP10, RP20) acquired between the first first terminal 4_1 and the second second terminal 5_2 does not satisfy the conditions of the usage relationship, the management server 1 (II) may not allow the setting of the second correspondence relationship and may maintain the setting of the first correspondence relationship.

[0092] The condition of the usage relationship may be set appropriately. 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 first terminal 4_1 or the current position RP20 of the second second terminal 5_2. 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. 6B assumes a scene in which the current position RP10 of the first first terminal 4_1 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 second terminal 5_2 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 second terminal 5_2 is outside the range DR.

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

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

[0095] Each current position (RP10, RP20) may be transmitted from the first terminal 4_1 and the second terminal 5_2 to the management server 1 at any timing before the arbitration process is performed. In one example, each terminal (4, 5) may report information on each current position to the management server 1 as a spontaneous information process such as periodic transmission. Each terminal (4, 5) may report information on each current position to the management server 1 together with a linking request. In this case, the management server 1 may determine whether or not the condition of the usage relationship is satisfied using information on each current position (RP10, RP20) most recently reported from each terminal (4_1, 5_2). In another example, the management server 1 may directly or indirectly transmit a request to the first terminal 4_1 and the second terminal 5_2 at any timing before the arbitration process is performed. Each terminal (4_1, 5_2) may report information on the most recent current position (RP10, RP20) to the management server 1 in real time in response to this request. The management server 1 may determine whether or not the conditions of the usage relationship are satisfied based on information on the most recent current positions (RP10, RP20) reported in real time. In either case, when information on the most recent current position of at least one of the first terminal 4_1 and the second terminal 5_2 cannot be obtained due to the influence of the power being off or the like, the management server 1 determines that the conditions of the usage relationship are not satisfied. good.

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

[0097] (3) Third Rule For example, in the scene of FIG. 2, it is assumed that a correspondence relationship (first correspondence relationship) is set between a first user who is a first first object VA1 and a first individual of a moving object of public transportation who is a first second object WA1. In this scene, even though the settlement of the moving object of public transportation has not been completed, it is not desirable for the first user to cancel the first correspondence relationship with the first individual of the moving object by using another moving object and establish a new correspondence relationship setting with the other moving object. The other moving object is an example of a second second object WA2 (a second individual of the moving object). In this way, when the corresponding individual of the second object WA is a predetermined type, it may be desirable to refuse to establish a correspondence relationship setting with another individual of the second object WA until a predetermined condition is satisfied (in the above example, the settlement is completed).

[0098] Therefore, in one example of this embodiment, the management server 1 may be further configured to prohibit the release of the correspondence relationship by locking the setting of the correspondence relationship when the correspondence relationship is set with a second target WA of a predetermined type until a predetermined condition is satisfied. The third rule may prohibit the update of the setting of the correspondence relationship while the setting of the correspondence relationship is locked. The predetermined rule may include the third rule.

[0099] FIG. 7 is a schematic diagram showing an example of a scene in which the association setting according to the present embodiment is locked. When the first second target WA1 is of a predetermined type, and the first correspondence is locked because a predetermined condition is not satisfied, and the second correspondence is accepted, the management server 1 may (II) not permit the second correspondence to be set and maintain the first correspondence. That is, the management server 1 may ignore the association request with the second second target WA2. At this time, the management server 1 may directly or indirectly transmit a notification indicating that the setting of another correspondence is prohibited to at least one of the first first terminal 4_1 of the first first target VA1 and the second second terminal 5_2 of the second second target WA2. On the other hand, when the second correspondence is accepted after the first correspondence is unlocked because a predetermined condition is satisfied, the management server 1 may (I) release the first correspondence and establish the second correspondence.

[0100] The predetermined condition may be set as appropriate depending on the embodiment. Moreover, whether or not the predetermined condition is satisfied may be detected as appropriate. In a simple example, the satisfaction of the predetermined condition is detected as a predetermined type of second pair. The detection may be made by a notification from the second terminal 5 corresponding to the individual of the elephant WA. In the above example, when the settlement is completed, the second terminal 5 (first second terminal 5_1) of the individual of the moving object may transmit a notification indicating the settlement completion (satisfaction of the predetermined condition) to the management server 1. The management server 1 may detect the satisfaction of the predetermined condition by receiving this notification. Then, the management server 1 may unlock the setting of the correspondence relationship with the second target WA in response to the detection of the satisfaction of the predetermined condition. In this way, the management server 1 may permit the establishment of a new setting of the correspondence relationship with another individual of the second target WA. Note that the management server 1 may also execute such a locking process for the second target WA of a type other than the predetermined type, or may omit the execution of the locking process for the second target WA of another type. According to an example of the present embodiment, when it is inappropriate to establish the setting of another correspondence relationship, the setting of the established correspondence relationship can be locked to prohibit the establishment of such another correspondence relationship. In this way, it is possible to expect appropriate arbitration for the collision of the association setting.

[0101] The predetermined type may be appropriately selected according to the embodiment. In one example, the first target VA may be a user. The second target WA of the predetermined type may be a moving body of public transportation. The predetermined condition may be that payment (settlement) for the use of the moving body of public transportation is completed. According to one example of the present embodiment, when the fee for the moving body of the transportation is unpaid, it is possible to prohibit transfer to another moving body (establishment of a new correspondence relationship setting with another moving body). This makes it possible to expect appropriate mediation for the collision of the linking setting.

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

[0103] In one example, the continuation of the correspondence relationship may be confirmed 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, the user may be authenticated by, for example, using an image sensor provided on the mobile object to perform face authentication of the user, using a fingerprint reader attached to the steering wheel to perform fingerprint authentication of the user, 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.

[0104] 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, etc. The destination of the confirmation notification does not necessarily have to 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 linking. Confirmation The notification may be configured to send a response directly or indirectly to the management server 1 in response to a user's operation of an operator. If the management server 1 receives a response to the operation of the operator within a predetermined period of time, it may determine that the correspondence relationship continues, and if it does not receive a response, it may determine that the correspondence relationship does not continue.

[0105] In yet another example, when tracking the correspondence between the first object VA and the second object WA in the real world, each terminal (4, 5) may be equipped with a positioning module (47, 57) as in the example of FIG. 6B. The first terminal 4 may measure the current position of the first object VA (first terminal 4) by the positioning module 47, and the second terminal 5 may measure the current position of the second object WA (second terminal 5) by the positioning module 57. Each terminal (4, 5) may transmit the obtained current positions of each object (VA, WA) to the management server 1 directly or indirectly via an external computer such as each server (2, 3). The management server 1 may determine whether the correspondence continues depending on whether the received current positions of each object (VA, WA) are close enough to satisfy a predetermined condition of the usage relationship (for example, the user is riding on a moving object). That is, the management server 1 may determine that the correspondence relationship continues when the current positions of the targets (VA, WA) are close enough to satisfy a predetermined condition, and may determine that the correspondence relationship does not continue when this is not the case. When this form is adopted, the management server 1 may store the obtained information on the current positions of the targets (VA, WA) in association with the association information D10. This enables the management server 1 to track the movement history of each target (VA, WA) as well as the correspondence relationship between the targets (VA, WA). At least a part of the above processing may be executed by a computer other than the management server 1.

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

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

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

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

[0110] Similarly, when the second terminal 5 transmits a release 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 a memory. The first identifier I10 may be stored in the memory resource. When making a release request, the second terminal 5 may obtain the first identifier I10 from the memory resource. When the second terminal 5 sends a release request including the second identifier I20, the second terminal 5 may obtain the second identifier I20 at any timing. In one example, the second identifier I20 may be stored in the memory resource in advance. The second terminal 5 may obtain the second identifier I20 from the memory resource.

[0111] FIG. 8 is a schematic diagram showing an example of a process of untying according to the present embodiment. In the example of FIG. 8, 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.

[0112] The trigger of the release request may be set appropriately according to the embodiment. In one example, when at least one of the first target VA and the second target WA is a user, the release request may be transmitted from at least one of the first terminal 4 and the second terminal 5 by the user's operation of 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, at least one of the first terminal 4 and the second terminal 5 may execute an arbitrary information processing. The execution of this information processing may be used as a trigger to transmit a release request from at least one of the first terminal 4 and the second terminal 5. For example, the arbitrary information processing may be data exchange between the first terminal 4 and the second terminal 5. The method of data exchange when releasing the association may be the same as the data exchange when setting the association. A distinction may be made as to whether the data exchange is when setting the association or when releasing the association. For example, in the example of FIG. 2, the second terminal 5 may be provided with separate sensor devices at the entrance and exit, such as a bus entrance or a train ticket gate. In this case, a distinction may be made between data exchange at the time of linking setup and data exchange at the time of linking release depending on the sensor device used for data exchange. Also, for example, when data exchange is executed by an application of the terminal, the application may be configured to be switchable between a linking setup mode and a linking release mode. In this case, a distinction may be made between data exchange at the time of linking setup and data exchange at the time of linking release depending on the mode of the application.

[0113] In one example, when a release request for the correspondence relationship is received while the setting of the correspondence relationship is locked by the lock process, the management server 1 may reject the received release request. The management server 1 may directly or indirectly transmit a notification indicating that the release of the correspondence relationship is prohibited to at least one of the first terminal 4 and the second terminal 5. On the other hand, after the lock is released due to the satisfaction of a predetermined condition, the management server 1 may accept the release request and release the correspondence relationship. For example, the management server 1 may detect the satisfaction of the predetermined condition in response to the termination of the above-mentioned usage relationship. In one example, the release request may include information indicating the satisfaction of the predetermined condition. In another example, information indicating the satisfaction of the predetermined condition may be transmitted to the management server 1 prior to the release request. Thereby, the management server 1 may accept the release request transmitted in response to the termination of the above-mentioned usage relationship and release the correspondence relationship specified by the release request.

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

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

[0116] In another example, the number of correspondence relationships that can be set for the same individual of the second target WA may be infinite or finite. When the number of correspondence relationships that can be set is finite, an upper limit (threshold) may be set for the number of correspondence relationships that can be set for the same individual of the second target WA. The threshold may be given as appropriate. When the number of correspondence relationships set for the corresponding individual of the second target WA exceeds this upper limit, the management server 1 may cancel at least one of the correspondence relationships set for the corresponding individual of the second target WA. Which correspondence relationship is to be canceled 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 correspondence relationship to be canceled according to the response obtained.

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

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

[0119] 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 the present 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.

[0120] (Use of linked information) As described above, the linking information D10 may be used in various situations. Information D10 may be used simply to track the creation and destruction of relationships between a first object VA and a second object WA.

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

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

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

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

[0125] 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 authorities 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 authorities associated with the target user. If no exercisable authorities are extracted, this process may end. Note that in the first target information O10 (user information O10A), whether or not to permit the mobile object to exercise the authority may be set for each authority. Exercisable authorities may be extracted according to this setting. In addition, when the external system SY1 determines that the authority to be exercised is This process may also end if the authority to be exercised is not included in the exercisable authority. 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.

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

[0127] In addition, for example, when a plurality of users use one individual moving body, such as when a plurality of users are riding in the same vehicle, the user who exercises the authority may be appropriately selected. In one example, the user who exercises the authority may be selected by establishing a correspondence setting of one user among the plurality of users who use the same individual moving body. In another example, a correspondence setting of two or more users among the plurality of users who use the same individual moving body may be established. In this case, the method of exercising the authority may be appropriately adjusted among the two or more users for which the correspondence setting is established. For example, the authority of one or more selected users (representatives) may be exercised. The selection of the user may be performed by at least one of the external system SY1, the first terminal 4, and the second terminal 5. Also, for example, when the exercise of the authority is the payment of a price, the authority of each user may be exercised according to a predetermined rule. As a specific example, the payment price may be allocated equally to each user, and the authority of each user may be exercised for the payment of the allocated price. The price allocated to each user may be appropriately specified.

[0128] In another example, a group may be set in advance among a plurality of users, and a priority may be set for members (users) in the group. For example, when a family uses a private car, one group may be set for each family, and a priority may be set according to the relationship within the family. As an example, the priority of the parent may be set high, and the priority of the child may be set low. Information on the group and priority may be appropriately managed, for example, in the first target information O10 (user information O10A) or the like. In response to this, among a plurality of users who use the same individual moving object, a corresponding relationship setting of two or more users in the same group may be established. In this case, the authority of each user may be exercised according to the priority. For example, if a parent and a child use a private car and the priority of the parent is set high, the authority of the parent may be exercised. Exercising the authority according to the priority may include selecting a user who exercises the authority according to the priority (a user with a higher priority is selected as a target for exercising the authority) and determining the weight of exercising the authority according to the priority (for example, a user with a higher priority is allocated a higher payment amount, etc.).

[0129] Furthermore, the processing procedure for exercising the above 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.

[0130] (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 depending on the embodiment. The network between each device may be appropriately selected from, for example, the Internet, a wireless communication network, a mobile communication network, a telephone network, a dedicated network, a local area network, etc. Data communication between each device may be encrypted using a method such as SSL (Secure Socket Layer) or TLS (Transport Layer Security). In one example, each terminal (4, 5) may be equipped with a SIM (Subscriber Identity Module), and data communication between each terminal (4, 5) and the server (management server 1, first server 2, second server 3) may be performed by encrypted communication using the SIM.

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

[0132] The control unit 11 includes a hardware processor such as a central processing unit (CPU), a random access memory (RAM), and a read only memory (ROM), 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.

[0133] The storage unit 12 may be configured, for example, with a hard disk drive, a solid state drive, a semiconductor memory, etc. The storage unit 12 (as well as RAM and ROM) is an example of a memory resource. In this embodiment, the storage unit 12 stores various information such as a management program 81 and linking information D10. The management program 81 is a program for causing the management server 1 to execute information processing (see Figures 12 and 13 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.

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

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

[0136] 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 instead of the storage unit 12 or together with the storage unit 12. The storage medium 91 is configured so that a machine such as a computer can read various information (stored programs, etc.). The drive 16 is configured to store the information by electrical, magnetic, optical, mechanical or chemical action as described above. 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 disk-type storage medium such as a CD or a DVD, or may be a non-disk-type storage medium such as a semiconductor memory (e.g., a flash memory). The type of the drive 16 may be appropriately selected depending on the type of the storage medium 91. The drive 16 may be connected via an external interface.

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

[0138] (First server, second server) The hardware configuration of each server (2, 3) may be the same as that of the management server 1. In one example, each server (2, 3) may be a computer to which a control unit, a storage unit, a communication interface, an input device, an output device, and a drive are electrically connected. Each server (2, 3) may be composed of one or more computer devices. The processor resource of each server (2, 3) may be composed of one or more processors. The type of processor may be selected as appropriate. The first target information O10 may be stored in at least one of the memory resource of the first server 2 and an external computer (NAS, etc.) accessible to the first server 2. The second target information O20 may be stored in at least one of the memory resource of the second server 3 and an external computer (NAS, etc.) accessible to the second server 3. Regarding the hardware configuration of each server (2, 3), components may be omitted, replaced, or added as appropriate depending on the embodiment. Each server (2, 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, etc.

[0139] (1st terminal) 10B 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.

[0140] 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 relating to the association (FIGS. 12 and 13 to be 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 stores the program 84. and the first identifier I10 may be acquired from the storage medium 94. 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. The first terminal 4 may be operated via the input device 44 and the output device 45.

[0141] Regarding the specific hardware configuration of the first terminal 4, components can be omitted, replaced, and added as appropriate depending on the embodiment. For example, the control unit 41 may include a plurality of hardware processors. The hardware processor may be configured with 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 communication interface 43 may be configured with a plurality of types of modules. For example, the communication interface 43 includes a short-range wireless communication module and a wireless communication module, and the first terminal 4 may perform data communication with the second terminal 5 via the short-range wireless communication module, and perform data communication with the servers (management server 1, first server 2, second server 3) via the wireless communication module. The first terminal 4 may be composed of a plurality of 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, a general-purpose computer, a terminal device (e.g., a smartphone, a tablet PC, etc.), etc.

[0142] (2nd terminal) 10C shows 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.

[0143] 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. 12 and 13 to be 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 perform data communication with other computers (the management server 1, the first server 2, the second server 3, the first terminal 4, etc.) via the communication interface 53. The second terminal 5 may be operated via an input device 54 and an output device 55.

[0144] In addition, with regard to 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 may be acquired each time. In order to acquire data such as the identifier and information used for authentication, the second terminal The second terminal 5 may further include a data acquisition device such as a sensor or a reader. The communication interface 53 may be configured with multiple types of modules, similar to the first terminal 4. The second terminal 5 may be configured with multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The second terminal 5 may be an information processing device designed specifically for the service provided, as well as a general-purpose computer, terminal device, etc.

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

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

[0147] 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 individual of the first target VA and the relevant individual of the second target WA. The reception unit 111 is configured to accept the setting of a correspondence relationship between the relevant individual of the first target VA and the relevant individual of the second target WA by receiving the linking request.

[0148] The setting unit 112 is configured to execute a setting process of the accepted correspondence relationship. The setting process is configured by setting a correspondence relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA specified in the linking request. If a setting of a second correspondence relationship between the first first target VA1 and the second second target WA2 different from the first second target WA1 is accepted while a setting of a first correspondence relationship between the first first target VA1 and the second second target WA2 is established, a collision of the linking settings occurs. In this case, the setting unit 112 is configured to (I) release the first correspondence relationship and establish a setting of a second correspondence relationship, or (II) not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule. The release unit 113 is configured to execute a release process of the correspondence relationship upon receiving a release request from at least one of the first terminal 4 and the second terminal 5 or upon establishment of a predetermined release condition.

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

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

[0151] (2nd terminal) The control unit 51 of the second terminal 5 executes instructions contained in the program 85 by means of 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 binding request (a request for binding setting) to the management server 1. The unbinding request unit 513 is configured to transmit a unbinding request (a request for unbinding) to the management server 1.

[0152] (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, or 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.

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

[0154] 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 transmits a linking request to the management server 1. In one example, in response to the occurrence of the 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. With this data exchange as a trigger, 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 linking request may be transmitted directly to the management server 1, or may be transmitted indirectly via an external computer (the first server 2, the second server 3, etc.).

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

[0156] In step S10, when adopting a form in which a linking request is transmitted from both the first terminal 4 and the second terminal 5, 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 portion 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. In step S20, in order to identify the combination of the relevant individuals of the first target VA and the second target WA for which the setting of the correspondence is currently being requested, the management server 1 may appropriately identify the correspondence of this data (i.e., determine the combination of corresponding data).

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

[0158] 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 data association in response to a match between a combination of identifiers (I10, I20) included in the data received from the first terminal 4 and a 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 data association in response to a relationship being established between the temporary information included in the data received from the first terminal 4 and the temporary information included in the data received from the second terminal 5. The shared information may be shared between the first terminal 4 and the second terminal 5 at any timing. In a typical example, the first terminal 4 and the second terminal 5 may share the shared information when exchanging data.

[0159] In step S25, the control unit 11 of the management server 1 operates as the setting unit 112 and judges whether or not the setting of two or more correspondence relationships between the same individual of the first object VA and two or more different individuals of the second object WA is established (whether or not there is a collision) as a result of the process of step S20. That is, the control unit 11 judges whether or not the process of step S20 corresponds to accepting the setting of a second correspondence relationship between the first first object VA1 and a second second object WA2 different from the first second object WA1 while the setting of the first correspondence relationship between the first first object VA1 and the first second object WA1 is established. In one example, the control unit 11 judges whether or not there is a setting of a correspondence relationship between the individual of the first object VA specified in the accepted linking request and another individual of the second object WA by referring to the linking information D10. This other individual corresponds to the first second object WA1, and the correspondence relationship with the other individual corresponds to the first correspondence relationship. If there is no correspondence relationship with the other individual of the second object WA, the control unit 11 advances the process to step S301. On the other hand, if a corresponding relationship with another individual of the second object WA exists, the control unit 11 advances the process to step S302.

[0160] In step S301, the control unit 11 operates as the setting unit 112 and updates the linking information D10 to establish a setting of a correspondence relationship between the relevant individuals of the first object VA and the second object WA specified by the linking request. In one example, updating the linking information D10 in conjunction 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 proceeds to the next step S40.

[0161] On the other hand, in step S302, the control unit 11 operates as the setting unit 112 and updates the linking information D10 to (I) release the first correspondence and establish the setting of the second correspondence, or (II) rejects the linking request to not permit the setting of the second correspondence and maintain the setting of the first correspondence, according to a predetermined rule. In one example of the present embodiment, at least one of the above three rules may be adopted as the predetermined rule. The update process of the linking information D10 accompanying the release will be described later. After updating the linking information D10, the control unit 11 proceeds to the next step S40. The processes of steps S301 and S302 are one example of the process of setting the correspondence in response to the received linking request (above step S30).

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

[0163] The above process steps 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 process steps depending on the embodiment. For example, the process of linking may include an authentication process for at least one of the first target VA and the second target WA.

[0164] (Unlink) Fig. 13 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. 13 assumes a situation in which a cancellation request is sent directly from the first terminal 4 to the management server 1.

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

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

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

[0168] The above processing procedure is merely an example, and each step may be changed as much as possible. In addition, steps of the above processing procedure may be omitted, replaced, or added as appropriate depending on the embodiment. For example, as described above, the transmission route of the release request is not limited to the example of FIG. 13, 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. In addition, the control unit 11 of the management server 1 may operate as the release unit 113 instead of the above step SZ20, and release the correspondence when a predetermined release condition is met.

[0169] [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 processing of step S30 (step S301, step S302). 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 this embodiment, if a collision occurs between an individual of the first object VA and multiple individuals of the second object WA in the link setting, the collision is mediated by the processes of steps S25 and S302. Therefore, according to this embodiment, the correspondence between the first object VA and the second object WA can be appropriately tracked.

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

[0171] <4.1> In the above embodiment, an authentication process of the first target VA and the second target WA may be executed at least when setting up and / or releasing the association. The authentication process may be executed at least in the management server 1, the external server (the first server 2, the second server 3, etc.), and / or each terminal (4, 5). As an example, at least one of the following four authentication methods may be adopted.

[0172] (A) First authentication method 14 shows a schematic diagram of an example of the process of linking when the first authentication method is adopted. In the first authentication method, the second server 3 authenticates the second target WA in response to a request from the first terminal 4 of the first target VA, and the first server 2 authenticates the first target VA in response to a 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 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.

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

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

[0175] 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. Other information generated by any method may be, for example, a password, This may include a password, a passcode, or other information other than a symbol string.

[0176] 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 SA110, step SB110).

[0177] In step SA110, 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 second terminal 5 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 second terminal 5 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 second terminal 5 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.

[0178] Also, in step SB110, the first terminal 4 acquires the second identifier I20 and the second unique information CA2 from the corresponding individual of the second target WA. The second unique information CA2 corresponds to the second registered unique information CA20. The first terminal 4 may acquire the second identifier I20 and the second unique information CA2 from the second target WA as appropriate in the data exchange. Acquiring from the second target WA may include acquiring from the second terminal 5. For example, the first terminal 4 may acquire at least one of the second identifier I20 and the second unique information CA2 from the second target WA via an input device, a sensor, or the like. The first terminal 4 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.

[0179] In step SA120, 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 first server 2 receives the first authentication request for the corresponding individual of the first target VA. In response to receiving the first authentication request, the first server 2 appropriately executes authentication processing for the first target VA. In one example, the first server 2 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 first server 2 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 first server 2 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 first server 2 reports the authentication result for the corresponding individual of the first target VA to the management server 1. In one example, the first server 2 may transmit the authentication result of the first target VA to the management server 1 with the first identifier I10 of the first target VA attached. The first server 2 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.

[0180] On the other hand, in step SB120, 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 second server 3 receives the second authentication request for the corresponding individual of the second target WA. In response to receiving the second authentication request, the second server 3 appropriately executes authentication processing for the second target WA. In one example, the second server 3 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 second server 3 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 second server 3 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 second server 3 reports the authentication result for the corresponding individual of the second object WA to the management server 1. In one example, the second server 3 The second server 3 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 second server 3 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.

[0181] The second terminal 5 giving a 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. Also, the first terminal 4 giving a 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. In other words, when the first authentication method is adopted in setting up linking, the processes of steps SA120, SA130, SB120, and SB130 are an example of the process of step S10.

[0182] The management server 1 receives the authentication results for the corresponding individual of each target (VA, WA) from each server (2, 3). The management server 1 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 for which the setting of the correspondence relationship is currently requested. If the authentication of both the first target VA and the second target WA is successful in the received authentication results of the first target VA and the second target WA, 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 the setting of the association may be executed in real time in response to the occurrence of the usage relationship.

[0183] In the first authentication method, 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.

[0184] 14 is merely an example, and each step may be modified as much as possible. Furthermore, steps may be omitted, replaced, or added to the above processing procedure as appropriate depending on the embodiment. For example, the processing order of steps SA110 to SA130 and steps SB110 to SB130 is not particularly limited, and may be determined as appropriate depending on the embodiment. At least one of the authentication process of the first target VA (steps SA110 to SA130) and the authentication process of the second target WA (steps SB110 to SB130) may be omitted.

[0185] (B) Second authentication method Fig. 15 shows a schematic diagram of an example of the process of linking settings when the second authentication method is adopted. In the second authentication method, the management server 1 requests authentication from each server (2, 3) in response to a request from at least one of the first terminal 4 and the second terminal 5. That is, 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.

[0186] 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 as a linking request to the management server 1 (step SC120, step SD120). In response to this, the management server 1 transmits the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2 to the management server 1 (step SC120, step SD120). The process of steps SC120 and SD120 receives an authentication request including the second unique information CA2 and the first unique information CA2. The processes of steps SC120 and SD120 are an example of the process of step S10.

[0187] The allocation of data transmission may be appropriately determined according to the embodiment. In one example, the second terminal 5 may be responsible for transmitting the first identifier I10 and the first unique information CA1, and the first terminal 4 may be responsible for transmitting the second identifier I20 and the second unique information CA2. That is, in step SC110, the second terminal 5 may acquire the first identifier I10 and the first unique information CA1 from the first target VA. Acquiring from the first target VA may include acquiring from the first terminal 4. In step SC120, 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 first terminal 4 may acquire the second identifier I20 and the second unique information CA2 from the second target WA. Acquiring from the second target WA may include acquiring from the second terminal 5. In step SD120, the first terminal 4 may transmit to the management server 1 a linking request including the acquired second identifier I20 and second unique information CA2.

[0188] 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 data in a divided manner, the management server 1 may specify the correspondence of the authentication request data by a method such as using the shared information described above in order to specify the combination of the corresponding individual of the first target 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.

[0189] In step SC130, 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 first server 2 may 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 first server 2 returns the authentication result of the corresponding individual of the first target VA to the management server 1.

[0190] Similarly, in step SD130, 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 second server 3 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 second server 3 transmits the authentication result of the corresponding individual of the second target WA to the management server 1.

[0191] 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 both the first target VA and the second target WA received by the management server 1 show that the authentication of both the first target VA and the second target WA is successful, the management server 1 sets a correspondence relationship between the relevant individual of the first target VA and the second target WA. The correspondence relationship setting process 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.

[0192] In the second authentication method, when a usage relationship occurs between the first target VA and the second target WA, the first server 2 and the second server 3 authenticate the first target VA and the second target WA, respectively. These two authentications are expected to ensure security.

[0193] 15 is merely an example, and each step may be modified as much as possible. Furthermore, steps may be omitted, replaced, or added to the above processing procedure as appropriate depending on the embodiment. For example, the processing order of steps SC110 to SC140 and steps SD110 to SD140 is not particularly limited, and may be determined as appropriate depending on the embodiment. At least one of the authentication process of the first target VA (steps SC110 to SC140) and the authentication process of the second target WA (steps SD110 to SD140) may be omitted.

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

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

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

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

[0198] First, in step SE110, the first terminal 4 of the first target VA transmits a request for issuing a first time-limited certificate CB10 to the first server 2 in relation to the first identifier I10 of the first target VA. In response to receiving the request, the first server 2 issues the first time-limited certificate CB10 in relation to the first identifier I10. In step SE120, the first server 2 returns the issued first time-limited certificate CB10 to the first terminal 4. In response, the first terminal 4 receives the issued first time-limited certificate CB10 from the first server 2. The first terminal 4 stores the received first time-limited certificate CB10 so that it can be used as the first certificate CB1. In addition, in step SE130, the first server 2 also notifies the management server 1 of the issued first time-limited certificate CB10. The first server 2 may notify the first time-limited certificate CB10 with the first identifier I10.

[0199] In step SF110, the second terminal 5 of the second target WA transmits a request for issuance of 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 second server 3 issues the second time certificate CB20 in relation to the second identifier I20. In step SF120, the second server 3 returns the issued second time certificate CB20 to the second terminal 5. In response, the second terminal 5 transmits the issued second time certificate CB20 to the second terminal 5. The second terminal 5 receives the second time certificate CB20 from the second server 3. The second terminal 5 stores the received second time certificate CB20 so that it can be used as the second certificate CB2. In step SF130, the second server 3 also notifies the management server 1 of the issued second time certificate CB20. The second server 3 may notify the management server 1 of the second time certificate CB20 with a second identifier I20.

[0200] 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 SE140 and 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 (steps SE150 and 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 the above-mentioned step S10.

[0201] 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 second terminal 5 may obtain the first certificate CB1 from the first terminal 4. In step SE150, the second terminal 5 may transmit a binding request including the first certificate CB1 to the management server 1. In step SF140, the first terminal 4 may obtain the second certificate CB2 from the second terminal 5. In step SF150, the first terminal 4 may transmit a binding request including the second certificate CB2 to the management server 1.

[0202] The sharing of data transmission is not limited to this example. In another example, the first certificate CB1 may be transmitted from the first terminal 4. The second certificate CB2 may be transmitted from the second terminal 5. In addition, each identifier (I10, I20) may be transmitted to the management server 1 together with each certificate (CB1, CB2). 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.

[0203] The management server 1 compares the received first certificate CB1 with the first time-limited certificate CB10 notified from the first server 2. The management server 1 compares the received second certificate CB2 with the second time-limited certificate CB20 notified from the second server 3. The management server 1 may appropriately specify the correspondence of the data to be compared. Specifying the correspondence of the data to be compared means determining the combination of the first time-limited certificate CB10 and the first certificate CB1, and the combination of the second time-limited certificate CB20 and the second certificate CB2 to be compared. As with the correspondence of the data of the authentication request, the management server 1 may specify the correspondence of the data to be compared by a method such as using the shared information described above. The shared information may be each identifier (I10, I20).

[0204] Furthermore, a method of comparing the certificate and the time-limited certificate may be appropriately selected depending on 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 comparison in the authentication may be determined depending on 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 comparison in the authentication may be determined depending on 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 based 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 executed in each terminal (4, 5) or in each server (2, 3). When the conversion process is executed in each server (2, 3), each terminal (4, 5) may receive the converted time certificate (CB10, CB20) from each server (2, 3).

[0205] 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 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 the 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.

[0206] In the method 3-1, when a usage relationship occurs between the corresponding individuals of the first target VA and the second target WA, the first target VA and the second target WA are authenticated using time-limited certificates (CB10, CB20). Each time-limited certificate (CB10, CB20) is configured to expire after the validity period. Therefore, it is possible to prevent the same certificate from being used permanently, which is expected to ensure security.

[0207] 16 is merely an example, and each step may be modified as much as possible. Furthermore, steps may be omitted, replaced, or added to the above processing procedure as appropriate depending on the embodiment. For example, the processing order of steps SE110 to SE150 and steps SF110 to SF150 is not particularly limited, and may be determined as appropriate depending on the embodiment. At least one of the authentication process of the first target VA (steps SE110 to SE150) and the authentication process of the second target WA (steps SF110 to SF150) may be omitted.

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

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

[0210] In addition, in the authentication method of the above 3-1, each certificate (CB1, CB2) and each time-limited certificate ( The matching process of the certificates (CB10, CB20), i.e., the authentication process of each target (VA, WA), is executed by the management server 1. However, the entity that executes the matching process does not need 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).

[0211] (C-2) Authentication method 3-2 In the above authentication method 3-1, the authentication process 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 process is not limited to this example. In the authentication method 3-2, before sending a linking request to the management server 1, at least one of the first terminal 4 and the second terminal 5 may execute an authentication process of at least one of the first target VA and the second target WA in advance between the first server 2 and the second server 3 and at least one of the first server 2 and the second server 3.

[0212] Fig. 17A shows an example of the process of the association setting in the case of adopting the authentication method 3-2. In the example of Fig. 17A, it is assumed that the authentication process of the first target VA is executed and the authentication process of the second target WA is omitted.

[0213] 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-limited certificate CB10 is issued, and the issued first time-limited certificate CB10 is notified to the first terminal 4. At this time, the first server 2 may store the issued first time-limited certificate CB10 in association with the first identifier I10. The first time-limited 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 first terminal 4 provides the issued first time-limited 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.

[0214] In step SG110, 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 first server 2 compares the received first certificate CB1 with the corresponding first time-limited certificate CB10. The corresponding first time-limited certificate CB10 may be acquired as appropriate. In one example, the issued first time-limited certificate CB10 may be stored as the first target information O10, and the first server 2 may extract the corresponding first time-limited certificate CB10 by searching the first target information O10 using the first identifier I10 as a query. In step SG120, the first server 2 returns the result of the comparison to the second terminal 5. In response, the control unit 51 of the second terminal 5 receives the result of the comparison.

[0215] If the received comparison result indicates that the first certificate CB1 and the first time-limited certificate CB10 do not match, the second terminal 5 may terminate the binding setting process as appropriate. The second terminal 5 may request the first terminal 4 to resend the first certificate CB1. On the other hand, if the comparison is successful, the second terminal 5 transmits a binding request including the first identifier I10 and the second identifier I20 to the management server 1 (step SG130). The process of step SG130 is an example of the process of step S10 above.

[0216] In response to this, the management server 1 receives a linking request from the second terminal 5. In response to the linking request, 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) (step SE140) to linking setting may be executed in real time in response to the occurrence of a usage relationship. The other configurations are the same as those of the first authentication method, etc. It may be.

[0217] 17A 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 to the above process steps according to the embodiment.

[0218] For example, the management server 1 may appropriately verify that matching has been established in the first server 2. In one example, the first server 2 may also transmit the result of 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, 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.

[0219] In addition, in the authentication method 3-2, the object to be authenticated may not be limited to the first target VA. In another example, instead of the authentication process of the first target VA, the authentication process of the second target WA may be executed. In yet another example, the authentication process of the second target WA may be executed together with the authentication process of the first target VA.

[0220] FIG. 17B shows a schematic diagram of another example of the process of the association setting in the case of adopting the authentication method 3-2. In the example of FIG. 17B, a scene is assumed in which the authentication process of the second target WA is executed instead of the authentication process of the first target VA. Except for the fact that the first target VA and the second target WA are exchanged, the processing procedure of FIG. 17B may be the same as the processing procedure of FIG. 17A. That is, the processing of steps SF110 and SF120 is executed between the second terminal 5 and the second server 3, whereby the second time certificate CB20 is issued, and the issued second time certificate CB20 is notified to the second terminal 5. In step SF140, the second terminal 5 provides the issued second time certificate CB20 to the first terminal 4 as the second certificate CB2. In addition, the second terminal 5 provides the first terminal 4 with the second identifier I20. In step SH110, 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 second server 3 executes a matching process of the second certificate CB2 and the second time-limited certificate CB20. In step SH120, the second server 3 returns the result of the matching to the first terminal 4. If the result of the matching shows that the second certificate CB2 and the second time-limited certificate CB20 match, 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 management server 1 sets a correspondence relationship between the corresponding individuals of the first target VA and the second target WA. In another example, the authentication process of the first target VA and the second target WA may be executed by executing a series of processes in FIG. 17A and FIG. 17B.

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

[0222] (D) Fourth authentication method FIG. 18A shows an example of a process of binding setting when the fourth authentication method is adopted. The fourth authentication method uses a digital signature and a digital certificate using a private key. The authentication process is executed by the terminal of the other party to be authenticated. When authenticating the first target VA, it is the second terminal 5, and when authenticating the second target WA, it is the first terminal 4. In the example of Fig. 18A, it is assumed that the authentication process of the second target WA is omitted and the authentication process of the first target VA is executed.

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

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

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

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

[0227] 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 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 first terminal 4 may generate the electronic signature CD1 by converting the first identifier I10 and the electronic information into a hash value using a hash function and encrypting the obtained hash value with the first private key CC10.

[0228] In step SI120, the first terminal 4 provides the first identifier I10, the generated digital signature CD1, and the first digital certificate CC1 to the second terminal 5. As a result, the second terminal 5 obtains the first identifier I10, the digital signature CD1, and the first digital certificate CC1 from the first terminal 4. When the first terminal 4 is involved in the generation of at least a portion of the digital information, such as information derived from the first target VA, data regarding the digital information may be provided from the first terminal 4 to the second terminal 5 as the process of step SI120.

[0229] Next, the second terminal 5 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 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, the first electronic certificate CC1 is determined to be valid (i.e., the expiration date has not passed). If the first electronic certificate CC1 is registered in the revocation list, the first electronic certificate CC1 is determined to be invalid. The first server 2 refers to the revocation list and judges whether the first electronic certificate CC1 is valid or not. In step SI135, the first server 2 returns the judgment result to the second terminal 5. 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 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 second terminal 5 may obtain a revocation list and determine whether the first electronic certificate CC1 is valid by referring to the obtained revocation list. If the first electronic certificate CC1 is not valid (i.e., the expiration date has passed), the second terminal 5 may determine that the verification of the validity of the first electronic certificate CC1 is not successful and may appropriately terminate the processing procedure for setting the association. 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 second terminal 5 appropriately obtains the public key of the certification authority. The second terminal 5 uses the obtained public key to decrypt the digital signature of the certification authority included in the first electronic certificate CC1. The second terminal 5 then compares the obtained decrypted data with the remaining information (the proprietary information and the first public key) contained in the first electronic certificate CC1. If the data was encrypted after conversion to a hash value, 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 comparison reveals that the two match, the second terminal 5 determines that the validation of the first electronic certificate CC1 has been successful, and if the two do not match, it determines that the validation of the first electronic certificate CC1 has not been successful.

[0230] The second terminal 5 also verifies the validity of the electronic signature CD1 (step SI140). The second terminal 5 decrypts the electronic signature CD1 using the first public key included in the first electronic certificate CC1. The second terminal 5 compares the obtained decrypted data with the shared information (the first identifier I10 and the electronic information). If the data was encrypted after being converted to a hash value, 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 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.

[0231] If the verification of the validity of both the first electronic certificate CC1 and the electronic signature CD1 is successful, 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 management server 1 sets a correspondence relationship between the corresponding individuals of the first target VA and the second target WA. The correspondence relationship setting process may be the same as that of the above embodiment. Note that a series of processes from data exchange between the terminals (4, 5) to linking setting may be executed in real time in response to the occurrence of a usage relationship. The process of step SI150 is an example of the process of step S10. 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 unsuccessful, the second terminal 5 may appropriately end the processing procedure of linking setting. The second terminal 5 may request the first terminal 4 to resend a series of information.

[0232] Note that the processing procedure in FIG. 18A 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 depending on the embodiment. and additional steps may be added. For example, 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 validity of the electronic signature CD1 may be verified before the validity of the first electronic certificate CC1. The process of verifying the validity of the first electronic certificate CC1 and the process of verifying the validity of the electronic signature CD1 may be performed at least partially in parallel.

[0233] In addition, in the fourth authentication method, the object to be authenticated may not be limited to the first target VA. In another example, instead of the authentication process of the first target VA, the authentication process of the second target WA may be executed. In yet another example, the authentication process of the second target WA may be executed together with the authentication process of the first target VA.

[0234] FIG. 18B shows a schematic diagram of another example of the process of linking when the fourth authentication method is adopted. In the example of FIG. 18B, a scene is assumed in which the authentication process of the second target WA is executed instead of the authentication process of the first target VA. Except for the fact 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 utilization stage, when a utilization 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 (step SJ110, step SJ120). In this data exchange, electronic information is shared between the first terminal 4 and the second terminal 5. The second terminal 5 generates an electronic signature CD2 by encrypting the second identifier I20 and the electronic information using the second private key CC20. 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 first terminal 4 obtains the second identifier I20, the electronic signature CD2, and the second electronic certificate CC2. The first terminal 4 verifies the validity of the second electronic certificate CC2 (steps SJ130 and SJ135). The first terminal 4 also verifies the validity of the electronic signature CD2 (step SJ140). If the verification of the validity of both the second electronic certificate CC2 and the electronic signature CD2 is successful, 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. In response to the linking request, the management server 1 sets a correspondence relationship between the corresponding individuals of the first target VA and the second target WA. The correspondence relationship setting process may be the same as that of 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 established, the first terminal 4 may appropriately end the linking setting process procedure.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 Fig. 18A and Fig. 18B.

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

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

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

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

[0239] 1... management server, 11... control unit, 2...first server, 3...second server, 4...first terminal, 41...control unit, 47...positioning module, 5... second terminal, 51... control unit, 57... positioning module, VA...first target, VA1...first first target, WA…Second target, WA1: 1st secondary target, WA2: 2nd secondary 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 plurality of first terminals each corresponding to each of the first objects; and a plurality of second terminals respectively corresponding to the second objects; Equipped with the plurality of first terminals and the plurality of second terminals are configured such that, in response to the occurrence of a usage relationship between a first target and a second target, at least one of the first terminal corresponding to the first target and the second terminal corresponding to the second target transmits a linking request to the management server; The management server includes: receiving the association request to accept a setting of a correspondence relationship between the first object and the second object; and while a setting of a first correspondence relationship between a first first object and a first second object is established, when a setting of a second correspondence relationship between the first first object and a second second object different from the first second object is accepted, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule; configured to execute system.

2. The management server is further configured to receive a selection result by the first subject; The management server includes: When the second correspondence relationship is selected in the received selection result, (I) canceling the first correspondence relationship and establishing the setting of the second correspondence relationship; When the first correspondence relationship is selected in the selection result, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The system of claim 1 .

3. The management server includes: If a predetermined relationship is not established between the first second object and the second second object, (I) canceling the first correspondence relationship and establishing the second correspondence relationship; If the predetermined relationship is established between the first second object and the second second object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The system of claim 1 .

4. The management server includes: If the type of the second second object is different from the type of the first second object, (I) cancel the first correspondence relationship and establish the second correspondence relationship; If the type of the second second object is the same as the type of the first second object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The system of claim 1 .

5. the first object is a user, The second object is a use object used by the user, When the type of the first second object is a rental object, the management server When the type of the second object is not the rental object, (I) cancel the first correspondence and establish the second correspondence; When the second type of the second object is the rental item, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The system of claim 1 .

6. The object of use is a vehicle, The rental item is a rental car. The system of claim 5.

7. Each of the first terminals comprises a positioning module; Each of the second terminals comprises a positioning module; When the management server receives the setting of the second correspondence relationship, obtaining, from a first first terminal corresponding to the first first object, a current location of the first first terminal measured by a positioning module of the first first terminal; and obtaining, from a second second terminal corresponding to the second second object, a current position of the second second terminal measured by a positioning module of the second second terminal; and further configured to perform The management server includes: If the relationship of the current location acquired between the first terminal and the second terminal satisfies the condition of the usage relationship, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship; If the relationship of the current locations acquired between the first terminal and the second terminal does not satisfy the condition of the usage relationship, (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship. It is configured as follows: The system of claim 1 .

8. the management server is further configured to, when a correspondence relationship is set with a second target of a predetermined type, prohibit cancellation of the correspondence relationship by locking the setting of the correspondence relationship until a predetermined condition is satisfied; When the first and second targets are of the predetermined type, the management server (II) when a setting of the second correspondence relationship is accepted while the first correspondence relationship is locked, the setting of the second correspondence relationship is not permitted and the setting of the first correspondence relationship is maintained; When the setting of the second correspondence relationship is accepted after the lock of the first correspondence relationship is released, (I) the first correspondence relationship is released and the setting of the second correspondence relationship is established. It is configured as follows: The system of claim 1 .

9. the first object is a user, the second object of the predetermined type is a moving object of public transportation, The predetermined condition is that payment for the use of the public transportation vehicle is completed. The system of claim 8.

10. The management server notifies the user that a correspondence relationship between the first object and the second object has been established. In response, the method is further configured to enable the exercise of a right associated with the corresponding first object via the second object with which the correspondence is established. The system of claim 1 .

11. receiving a linking request from at least one of a first terminal of the first target and a second terminal of the second target in response to the occurrence of a usage relationship between a first target and a second target; receiving the association request to accept a setting of a correspondence relationship between the first object and the second object; and while a setting of a first correspondence relationship between a first first object and a first second object is established, when a setting of a second correspondence relationship between the first first object and a second second object different from the first second object is accepted, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule; A control unit configured to execute Management server.

12. The control unit is If a predetermined relationship is not established between the first second object and the second second object, (I) canceling the first correspondence relationship and establishing the second correspondence relationship; If the predetermined relationship is established between the first second object and the second second object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The management server according to claim 11.

13. The control unit is If the type of the second second object is different from the type of the first second object, (I) cancel the first correspondence relationship and establish the second correspondence relationship; If the type of the second second object is the same as the type of the first second object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The management server according to claim 11.

14. the first object is a user, The second object is a use object used by the user, the first second object type is a rental item; The control unit is If the type of the second object is not the rental object, (I) cancel the first correspondence and establish the second correspondence; If the type of the second second object is the rental object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. It is configured as follows: The management server according to claim 11.

15. When the control unit receives the setting of the second correspondence relationship, obtaining, from a first first terminal corresponding to the first first object, a current location of the first first terminal measured by a positioning module of the first first terminal; and obtaining, from a second second terminal corresponding to the second second object, a current position of the second second terminal measured by a positioning module of the second second terminal; and further configured to perform The control unit is If the acquired current location relationship between the first terminal and the second terminal satisfies the condition of the usage relationship, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship; If the acquired relationship of the current locations between the first terminal and the second terminal does not satisfy the condition of the usage relationship, (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship. It is configured as follows: The management server according to claim 11.

16. The control unit is further configured to, when a correspondence relationship is set with a second object of a predetermined type, prohibit cancellation of the correspondence relationship by locking the setting of the correspondence relationship until a predetermined condition is satisfied, When the first and second objects are the predetermined type, the control unit: (II) when a setting of the second correspondence relationship is accepted while the first correspondence relationship is locked, the setting of the second correspondence relationship is not permitted and the setting of the first correspondence relationship is maintained; When the setting of the second correspondence relationship is accepted after the lock of the first correspondence relationship is released, (I) the first correspondence relationship is released and the setting of the second correspondence relationship is established. It is configured as follows: The management server according to claim 11.

17. The management server receiving a linking request from at least one of a first terminal of the first target and a second terminal of the second target in response to the occurrence of a usage relationship between a first target and a second target; receiving the association request to accept a setting of a correspondence relationship between the first object and the second object; and while a setting of a first correspondence relationship between a first first object and a first second object is established, when a setting of a second correspondence relationship between the first first object and a second second object different from the first second object is accepted, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship, or (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship, according to a predetermined rule; Execute Management method.

18. the first object is a user, The second object is a use object used by the user, the first second object type is a rental item; The management server includes: If the type of the second object is not the rental object, (I) cancel the first correspondence and establish the second correspondence; If the type of the second second object is the rental object, (II) not permitting the setting of the second correspondence relationship and maintaining the setting of the first correspondence relationship. The management method according to claim 17.

19. When the management server receives the setting of the second correspondence relationship, obtaining, from a first first terminal corresponding to the first first object, a current location of the first first terminal measured by a positioning module of the first first terminal; and A second second terminal corresponding to the second second object transmits a positioning module of the second second terminal. obtaining a current location of the second terminal as measured by a second module; Further execute The management server includes: If the acquired current location relationship between the first terminal and the second terminal satisfies the condition of the usage relationship, (I) cancel the first correspondence relationship and establish the setting of the second correspondence relationship; If the acquired relationship of the current locations between the first terminal and the second terminal does not satisfy the condition of the usage relationship, (II) do not permit the setting of the second correspondence relationship and maintain the setting of the first correspondence relationship. The management method according to claim 17.

20. the management server further executes, when a correspondence relationship is set with a second target of a predetermined type, prohibiting cancellation of the correspondence relationship by locking the setting of the correspondence relationship until a predetermined condition is satisfied; When the first and second targets are of the predetermined type, the management server (II) when a setting of the second correspondence relationship is accepted while the first correspondence relationship is locked, the setting of the second correspondence relationship is not permitted and the setting of the first correspondence relationship is maintained; When the setting of the second correspondence relationship is accepted after the lock of the first correspondence relationship is released, (I) the first correspondence relationship is released and the setting of the second correspondence relationship is established. The management method according to claim 17.

Images