System, management server and management method

Abstract

To provide a technology for easily 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 to use relation occurring between a first object and a second object. When setting of two or more correspondences is established with two or more different second objects for the same first target in response to receiving the setting of correspondence based on two or more linking requests for the same first object, the management server activates setting of one correspondence of the two or more correspondences, and deactivates setting of the other correspondence settings, in accordance with status information.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 fee collection system for collecting fees for services from vehicle users using a medium such as a card. Specifically, the fee collection system proposed in Patent Document 1 uses the ID of an ETC (Electronic Toll Collection System) card, It is configured to allocate the charge for expressway usage tolls for the target rental car to the target user based on the correspondence between the rental car company, the date and time of rental car use, and the rental car user (billing information, registration information, payment information, and usage information). [Prior art documents] [Patent documents]

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

[0004] One objective of the present disclosure is to provide a technique for easily 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 by receiving the linking request, and, in response to accepting the setting of the correspondence relationship by two or more of the linking requests for the same first target, when two or more correspondence relationship settings with two or more different second targets are established for the same first target, to execute the following in response to status information obtained from at least one of the first target and the two or more second targets for which the two or more correspondence relationship settings are established, to activate one of the two or more correspondence relationship settings and deactivate the other correspondence relationship settings.

[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, accept a setting of a correspondence relationship between the first target and the second target upon receiving the linking request, and, when two or more correspondence relationship settings with two or more different second targets are established for the same first target in response to accepting the setting of the correspondence relationship based on two or more linking requests for the same first target, activate one of the two or more correspondence relationship settings and make the other correspondence relationship settings inactive in response to status information obtained from at least one of the first target and the two or more second targets between which the two or more correspondence relationship settings are established.

[0007] A management method according to a third aspect of the present disclosure includes: a management server that manages a relationship between a first target and a second target; and, when two or more correspondence relationship settings with two or more different second targets are established for the same first target in response to the acceptance of the correspondence relationship settings based on two or more of the linking requests for the same first target, making one of the two or more correspondence relationship settings active and making the other correspondence relationship settings inactive in response to status information obtained from at least one of the first target and the two or more second targets for which the two or more correspondence relationship settings are established. Effect of the Invention

[0008] According to the present disclosure, it is possible to provide a technique for easily 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 4A] FIG. 4A illustrates an example of a process for selecting a binding setting to be activated according to this embodiment. [Figure 4B] FIG. 4B illustrates an example of a process for selecting a binding setting to be activated according to this embodiment. [Figure 4C] FIG. 4C illustrates an example of a process for selecting a binding setting to be activated according to this embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a scene in which an active binding setting according to the present embodiment is locked. [Figure 6] FIG. 6 shows an example of a process of canceling a link according to this embodiment. [Figure 7] FIG. 7 is a schematic diagram showing an example of a situation in which the association setting according to the present embodiment is maintained in an active or inactive state. [Figure 8] FIG. 8 is a schematic diagram showing an example of a scene in which the association release according to this embodiment is executed. [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] In other words, with the diversification of MaaS (Mobility as a Service), the benefits of efficient payment, etc. From the viewpoint of convenience, it is considered that there will be a demand for easily tracking the use of a mobile object by a user. 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 easily 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 a setting of a correspondence relationship between the first target and the second target by receiving the linking request, and, in response to receiving the setting of a correspondence relationship by two or more linking requests for the same first target, when two or more correspondence relationship settings with two or more different second targets are established for the same first target, to execute the following in response to status information obtained from at least one of the first target and the two or more second targets for which the two or more correspondence relationship settings are established, to activate one of the two or more correspondence relationship settings and deactivate the other correspondence relationship settings.

[0013] In the first aspect of the present disclosure, the use relationship between the first object and the second object can be tracked by setting a correspondence relationship between the first object and the second object (linking setting) and activating the linking setting. In addition, in the first aspect of the present disclosure, multiple linking settings are permitted for one first object (one individual of the first object), and the use relationship can be tracked by switching the state (active / non-active). If multiple linking settings are not permitted for one first object, linking setting and release will be repeated every time a use relationship occurs and disappears, which may lead to an increase in work. In particular, when the same use relationship occurs and disappears repeatedly, linking setting and release of the same content will be repeated, which may lead to an increase in unnecessary processing costs. In contrast, in the first aspect of the present disclosure, at least in some cases, it is possible to respond to the occurrence and disappearance of a use relationship by switching the state without repeating linking setting and release. This makes it possible to simplify the management of the linking. Therefore, according to the first aspect of the present disclosure, the use relationship between the first object and the second object can be easily tracked. be.

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

[0015] For example, a management server according to a second aspect of the present disclosure may include a control unit configured to receive 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, accept a setting of a correspondence relationship between the first target and the second target upon receiving the linking request, and, when two or more correspondence relationship settings with two or more different second targets are established for the same first target in response to accepting the setting of the correspondence relationship based on two or more linking requests for the same first target, activate one of the two or more correspondence relationship settings and make the other correspondence relationship settings inactive in response to status information obtained from at least one of the first target and the two or more second targets between which the two or more correspondence relationship settings are established.

[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 a first target and a second target, accepts the setting of a correspondence relationship between the first target and the second target by receiving the linking request, and, if two or more correspondence relationship settings with two or more different second targets are established for the same first target in response to accepting the setting of the correspondence relationship due to two or more linking requests for the same first target, activates one of the two or more correspondence relationship settings and makes the other correspondence relationship settings inactive in response to status information obtained from at least one of the first target and the two or more second targets between which the two or more correspondence relationship settings are established.

[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 first terminals 4 and the second terminals 5 are a first target VA and a second target VA. In response to the occurrence of a usage relationship between the target WAs, 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 is configured to transmit 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 a correspondence relationship setting has not been established for the corresponding individual of the first target VA with other second target WAs (i.e., two or more correspondence relationships have not been established for the same first target VA with two or more different second target WAs), no collision of linking settings will occur. Therefore, the management server 1 may set an active correspondence relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA as is. The fact that a correspondence relationship setting has not been established with other second target WAs may include, in addition to the absence of a correspondence relationship setting with other second target WAs, regardless of the state (active / non-active), the existence of a nonactive correspondence relationship with other second target WAs, but no active correspondence relationship.

[0022] On the other hand, if a correspondence relationship between the individual of the first target VA and another second target WA has already been established, a collision of the linking settings occurs. The fact that a correspondence relationship between the individual of the first target VA and another second target WA has already been established means that two or more correspondence relationships between the individual of the first target VA and two or more different second target WAs are established in response to the acceptance of the setting of the correspondence relationship by two or more linking requests for the same first target VA. The fact that a correspondence relationship between the individual of the first target VA and another second target WA has already been established may be constituted by the existence of an active correspondence relationship between the individual of the first target VA and another second target WA. In this case, the management server 1 acquires status information ST10 from at least one of the first target VA and the two or more second target WAs for which two or more correspondence relationships are established. Then, the management server 1 activates one of the two or more correspondence relationships and deactivates the other correspondence relationships according to the acquired status information ST10. In this way, the management server 1 mediates the collision of the linking settings.

[0023] In addition, 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 relevant individual of the first target VA and the second terminal 5 corresponding to the relevant individual of the second target WA. A linking request may be executed in association 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. A correspondence relationship (linking) maintained in an active or non-active state may be released at any timing. In response to the disappearance of the usage relationship, an active correspondence relationship may be changed to non-active or released.

[0024] In addition, as long as each individual with 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 according to the embodiment. In one example, a first identifier I10 may be given to each first object VA, and the first identifier I10 may identify the first object VA. Each individual of the object VA may be identified. Similarly, each second object WA may be given a second identifier I20, and each individual of the second object WA may be identified by the second identifier I20. Accordingly, establishing a correspondence relationship between the corresponding individual of the first object VA and the corresponding individual of the second object WA may be configured by establishing a correspondence relationship between the first identifier I10 given to the corresponding individual of the first object VA and the second identifier I20 given to the corresponding individual of the second object WA. That is, the establishment of the correspondence relationship may be expressed using the first identifier I10 and the second identifier I20.

[0025] As described above, in this embodiment, the setting of the correspondence relationship between the first target VA and the second target WA (linking setting) and the activation process make it possible to trace the use relationship between the corresponding individual of the first target VA and the corresponding individual of the second target WA. In addition, in this embodiment, a linking setting is permitted for each individual of the first target VA with each of multiple individuals of the second target WA. When multiple linking settings are established and the linking settings for the corresponding individual of the first target VA collide, the collision is mediated by switching the state (active / non-active), and this makes it possible to properly trace the use relationship regarding the corresponding individual of the first target VA. If multiple linking settings are not permitted for each individual of the first target VA, linking setting and cancellation will be repeated every time a use relationship is created and destroyed, which may lead to an increase in labor. In particular, when the same use relationship is repeatedly created and destroyed, linking setting and cancellation of the same content will be repeated, which may lead to an unnecessary increase in processing costs. In contrast, in this embodiment, in at least some scenes where the usage relationship is tracked, it is possible to deal with the occurrence and disappearance of the usage relationship by switching the state without repeating the setting and canceling of the association. This makes it possible to simplify the management of the association. Therefore, according to this embodiment, it is possible to easily track the usage relationship between the first object VA and the second object WA.

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

[0027] In this embodiment, when a pegging setting is established for the 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 an active pegging setting. In contrast, the handling of the pegging setting for the 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 the 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 an active pegging setting, as in the case of the first target VA. Alternatively, the management server 1 may not execute the arbitration process, and may allow multiple active pegging settings for the same 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), active binding settings for each of the multiple users for the same moving object may be properly established. In such a case, multiple active binding settings for the same second object WA may be permitted. Of the two objects tracking the usage relationship, one object that does not permit multiple active binding settings may be selected as the first object VA, and the other object that permits multiple active binding settings may be selected as the second object WA.

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

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

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

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

[0032] In one example, at least one of sending a 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 each terminal (4, 5), an external server (for example, the first server 2, the second server 3), and a management server. The linking request may be executed by at least one of the external server or 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 executed 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 if authentication is successful.

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

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

[0035] The management server 1 may be configured to set an active correspondence relationship between the first target VA and the second target WA, or update the status of the correspondence relationship from non-active to active, in response to the occurrence of a usage relationship. The binding request (request for binding setting) may include a request to establish a new binding setting, and a request to change the status of an existing binding setting from non-active to active. If a binding setting does not exist between the respective individuals, the binding request may be constituted by a request to establish a new binding setting. If a binding setting exists between the respective individuals, the binding request may be constituted by a request to change the status of the corresponding existing binding setting.

[0036] Information indicating whether or not a linking setting exists between the respective individuals may be appropriately managed. In one example, at least one of the first terminal 4 and the second terminal 5 may check the linking setting before transmitting a linking request. By referring to the linking information D10, it may be determined whether or not a linking setting exists between the relevant individuals. In another example, at least one of the first terminal 4 and the second terminal 5 may be configured to record a history of past linking requests, and by referring to this history, it may be determined whether or not a linking setting exists between the relevant individuals. The past history may be generated by individual processing of the terminal, or may be generated by sharing the linking information D10 of the relevant individuals with the management server 1. Depending on the result of the determination, at least one of the first terminal 4 and the second terminal 5 may transmit, as a linking request, either a request to establish a new linking setting or a request to change the state of the corresponding existing linking setting to active.

[0037] In yet another example, the first terminal 4 and the second terminal 5 may transmit a linking request without distinguishing whether or not a linking setting exists between each of the relevant individuals. In this case, when processing the linking request, it may be determined whether or not a linking setting already exists between each of the relevant individuals. For example, the management server 1 may determine whether or not an existing linking setting exists between the relevant individual of the first target VA and the relevant individual of the second target WA specified by the linking request by referring to the linking information D10. Also, for example, whether or not a linking setting already exists between each of the relevant individuals may be determined by an external computer such as the first server 2 or the second server 3. In one example, the external computer may determine whether or not a target linking setting exists by referring to the linking information D10. In another example, the external computer may be configured to record a linking history separately from the linking information D10, and may determine whether or not a target linking setting exists by referring to this history. The linking history may be generated by an individual process of the external computer, or may be generated by at least partially sharing the linking information D10 with the management server 1. Depending on the result of the determination, the management server 1 may execute either a process of establishing a new binding setting or a process of changing the state of the corresponding existing binding setting to active.

[0038] In one example of this embodiment, if there is no existing active linking setting with other individuals of the second target WA, the management server 1 may establish a new correspondence setting or change the state of the specified existing correspondence to active in response to the linking request. In this way, the management server 1 may set an active correspondence between each relevant individual. The absence of an existing active linking setting with other individuals of the second target WA may include the absence of an existing linking setting with other individuals of the second target WA for the relevant individual of the first target VA, and the existence of an existing linking setting with other individuals of the second target WA for the relevant individual of the first target VA, but all existing linking settings with other individuals of the second target WA are inactive.

[0039] On the other hand, if there is an existing active pegging setting with another individual of the second object WA, if the active pegging setting is established as it is in response to the pegging request (i.e., a new active pegging setting is established or the state of the corresponding existing pegging setting is changed to active), multiple active pegging settings are established for the same individual of the first object VA, and a collision of pegging settings occurs. Therefore, the management server 1 makes one correspondence setting active and other correspondence settings non-active according to the status information ST10 by the above arbitration process. In this way, the management server 1 resolves the collision of pegging settings. The arbitration rule by the status information ST10 (i.e., the method of selecting the active correspondence) may be appropriately determined according to the embodiment. In a simple example, the management server 1 may set the state of the correspondence specified by the earliest pegging request to active and the state of the other correspondences to non-active. In this case, the status information ST10 may be configured by any information that can determine whether it is the earliest or not. In one example, the status information ST10 may be configured by information such as a time stamp, a transmission time of the association request, a reception time of the association request, and information indicating that the association request has been received, etc. Another example of the arbitration rule will be described later (FIGS. 4A to 4C).

[0040] In one example of the present embodiment, in relation to a pegging request, an authentication process of at least one of the first target VA and the second target WA may be executed. For example, when a request is made to establish a new pegging setting, an authentication process of at least one of the first target VA and the second target WA may be executed. When a request is made to change the state of an existing pegging setting, an authentication process similar to that of a request to establish a new pegging setting may be executed. However, when this form is adopted, the same process may be repeated, which may lead to an increase in processing costs. Therefore, when a request is made to change the state of an existing pegging setting, at least a part of the authentication process may be omitted. As a result, it is preferable that the process when a request is made to change the state of an existing pegging setting is configured more simply than the process when a request is made to establish a new pegging setting. For example, at least one of the first terminal 4 and the second terminal 5 may appropriately acquire data used for authentication when a request is made to establish a new pegging setting. By storing the data used for authentication acquired when a request is made to establish this new pegging setting, the process of acquiring data used for authentication may be omitted when a request is made to change the state of an existing pegging setting. In addition, for example, the authentication process itself may be omitted. In one example, when a request is made to establish a new binding setting, authentication processing of both the first target VA and the second target WA is performed, whereas when a request is made to change the state of an existing binding setting, authentication processing of at least one of the first target VA and the second target WA may be omitted. In another example, when a request is made to establish a new binding setting, authentication processing of at least one of the first target VA and the second target WA is performed, whereas when a request is made to change the state of an existing binding setting, authentication processing of both the first target VA and the second target WA may be omitted. According to one example of the present embodiment, a reduction in processing costs can be expected.

[0041] In addition, the management server 1 may be configured to cancel the correspondence between the first target VA and the second target WA, or to update the state of the correspondence from active to non-active, in response to the termination of the usage relationship. When the usage relationship is terminated, at least one of the first terminal 4 and the second terminal 5 may transmit a request for canceling the association (cancellation request) to the management server 1. The cancellation request may be transmitted directly or indirectly to the management server 1, similar to the association request. The cancellation request may include a request to invalidate the corresponding association setting (cancellation in the narrow sense) and a request to change the state of the existing association setting from active to non-active. Invalidating the association setting may include deleting the association setting, providing information indicating the cancellation, and indicating the establishment of the cancellation condition. Providing information indicating the cancellation may include, for example, adding the cancellation time, setting a flag indicating the cancellation, accumulating a transaction indicating the cancellation, and the like. Indicating the establishment of the cancellation condition may include, for example, the expiration date set has passed, and the like. Whether to invalidate the linking setting or change the state of the linking setting may be appropriately selected by at least one of the terminals (4, 5), the management server 1, and an external computer (for example, the first server 2, the second server 3, etc.). In one example, after the correspondence is invalidated, the invalidated correspondence may be treated as not existing. Accordingly, when a linking request is issued again for the same combination of the first target VA and the second target WA after the invalidation, the management server 1 may execute a process of establishing a new linking setting. While the correspondence (linking) setting is maintained, the state of the correspondence may be updated at any timing other than the above. In addition, the release (invalidation or deactivation) in a broad sense may be read as "dissolution", and the release (invalidation) of the agreement may be called "release".

[0042] In one example of this embodiment, similar to the above-mentioned pegging request, authentication processing of at least one of the first target VA and the second target WA may be executed in association with the release request. When making a request to change the state of an existing pegging setting, authentication processing similar to that when requesting to invalidate the pegging setting may also be executed. When making a request to change the state of an existing pegging setting, at least a part of the authentication processing may be omitted. Thereby, the processing when making a request to change the state of an existing pegging setting may be configured more simply than the processing when requesting to invalidate the pegging setting. In another example, When the above-mentioned linking request is made, at least one of the first target VA and the second target WA is authenticated, whereas when the release request is made, at least a part of the authentication process may be omitted. As a result, the process when the release request is made may be configured more simply than the process when the linking request is made.

[0043] The linking request and the release request may be configured to specify the relevant individual to be processed by any method. 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 such an example, and may be appropriately changed according to the embodiment. In another example, at least one of the linking request and the release request may omit at least one of the first identifier I10 and the second identifier I20 by using alternative information. For example, an identifier may be assigned as alternative information to a combination (linking setting) of the relevant individuals of the first target VA and the second target WA. The assignment of the identifier may be performed at any timing, such as the initial linking setting. At least one of the linking request and the release request may be configured to specify the relevant individual of each target (VA, WA) to be processed by including this identifier, without including at least one of the first identifier I10 and the second identifier I20.

[0044] Regarding the pegging request, the method of specifying each relevant individual between the request to establish a new pegging setting and the request to change the state of the existing pegging setting may be the same or different. In one example, the request to change the state of the existing pegging setting may be configured to specify each relevant individual more easily than the request to establish a new pegging setting. For example, the request to establish a new pegging setting may be configured to include the first identifier I10 and the second identifier I20, whereas the request to change the state of the existing pegging setting may be configured to include the above-mentioned alternative information. Similarly, regarding the release request, the method of specifying each relevant individual between the request to disable the pegging setting and the request to change the state of the existing pegging setting may be the same or different. In one example, the request to change the state of the existing pegging setting may be configured to specify each relevant individual more easily than the request to disable the pegging setting. For example, the request to disable the pegging setting may be configured to include the first identifier I10 and the second identifier I20, whereas the request to change the state of the existing pegging setting may be configured to include the above-mentioned alternative information.

[0045] The management server 1 may be configured with one or more server devices. In this embodiment, the management server 1 may be configured to record information regarding the occurrence and disappearance of a correspondence relationship between a first target VA and a second target WA as association information D10. The association information D10 may be stored in a memory resource disposed at least inside and outside the management server 1. The internal memory resource may include, for example, a RAM, an auxiliary storage device, a storage medium, etc. The external memory resource may include, for example, an external storage device, an external computer (NAS, etc.), etc.

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

[0047] In one example of this embodiment, the association information D10 includes a first target VA and In order to indicate the combination of the second target WA, information on the first identifier I10 and the second identifier I20 of the relevant individual may be included. The management server 1 may acquire each identifier (I10, I20) of each target 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 to be established, 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 to be established.

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

[0049] (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, the usage relationship between the user and the usage object can be easily tracked.

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

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

[0052] When the first target VA is a user, an example of the first terminal 4 is a user terminal. The user terminal may be, for example, a mobile terminal (such as a smartphone), a dedicated device (such as an electronic key device), or any other computer device. Typically, the user terminal may be owned by a user who is the target of association (each individual of the first target VA). The user's account is , 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.

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

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

[0055] 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 setting of an active association between a user and a mobile body, it may be enabled (activated) that at least a part of the authority of various information E10 associated with the user information O10A is exercised by the mobile body. The second server 3 may be deployed by a public institution, a neutral institution, each business operator (vehicle manufacturer, service operator, etc.), etc. The second server 3 may be called a mobile body ID server, a car ID server, etc.

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

[0057] The system 100 may be configured to set an active link between the user (first identifier I10) and the individual (second identifier I20) of the object in response to the start of use of the object, or to update the state of the link from inactive to active. The system 100 may also be configured to update the state of the link between the individual from active to inactive, or to release the link 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 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.

[0058] In addition, the items to be used are those that can be used repeatedly for a long period of time and those that can be used temporarily. They can be divided into at least two types. For convenience of explanation, the former will be referred to as "regular use items" and the latter as "temporarily used items." An example of a regular use item is an item owned by a user, such as a personal car. An example of a temporary use item is an item owned by a person other than the user, such as a rental car, a shared car, a public transportation vehicle, a rental item, or an accommodation facility. Examples of public transportation vehicles include taxis, buses, railroad cars, airplanes, and ships.

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

[0060] In addition, the system 100 may switch, for example, the linking setting process, the conditions for switching the state (active / non-active), the conditions for releasing the linking, the method for managing the linking information D10, the authentication process, etc., depending on the type of usage identified.

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

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

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

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

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

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

[0067] 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 acquire the first identifier I10 by analyzing the captured image. The second terminal 5 may acquire the first identifier I10 via an input device. The first terminal 4 may acquire the first identifier I10 as needed.

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

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

[0070] (Linking information) FIG. 3A is a schematic diagram showing an example of the linking information D10 according to the present embodiment. In the example shown in 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, a release time, and a state. 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, together with a field for the release time. The state indicates whether the correspondence is set to active or non-active. Note that, as long as the association can indicate the setting and state of the correspondence, the configuration of the association information D10 is not limited to the example of FIG. 3A, and may be appropriately changed according to the embodiment. In another example, the association information D10 may further include information indicating the type of the object (whether the object is a constant use object or a temporary use object). Note that the type of the object is not necessarily identified by separate information. For example, the type of the object may be identified by information such as an identifier. In yet another example, the association information D10 may further include information indicating the time of a change in state (from active to non-active, from non-active to active).

[0071] The data format of the linking information D10 is not particularly limited and may be appropriately selected depending on the embodiment. The linking information D10 may be stored in any database platform. In one example, the linking information D10 may be stored in a relational database such as a table format. In another example, the linking information D10 may be stored in a blockchain platform. In this case, each transaction of linking setting, status change, and release may be accumulated in the blockchain as linking information D10. For example, a linking setting transaction may include information indicating a first identifier I10, a second identifier I20, a setting time, and a type of status (active or non-active). A status change transaction may include information indicating a first identifier I10, a second identifier I20, a setting time, and a type of status (active or non-active). It may include the first identifier I10, the second identifier I20, and information indicating the change type (whether it is a change from active to non-active or from non-active to active). The information indicating the change type may be replaced with information indicating the type of state after the change (whether it is active or non-active). The transaction for unbinding may include the first identifier I10, the second identifier I20, and the unbinding time (or information indicating unbinding).

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

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

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

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

[0076] FIG. 3C is a schematic diagram showing an example of the mobile object information O20A according to the present embodiment. In the example of 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 type, and owner information. If the mobile object is a vehicle, the number may be a vehicle registration number. The type may be arbitrarily defined. 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 mobile object of a public transportation system. The mobile object type indicates, for example, a type such as a car model. If the mobile object type and the type (type of object) are the same, the mobile object type field may be omitted. The owner information may include any information related to the owner of the mobile object. The owner information may include, for example, personal information of the owner, such as a name, an address, an age, a sex, and a contact address. 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 appropriately changed according to the embodiment. For example, the mobile object information O20A (second target information O20) may further include information (e.g., registered unique information, etc.) used to authenticate the mobile object (second target WA). The configuration of the attribute information may also be changed as appropriate. For example, the mobile object information O20A (attribute information) may further include information related to the mobile object terminal, such as contact information for the mobile object terminal.

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

[0078] (Notification processing) When at least one of the processes of setting up a link, changing the status, and canceling the linkage 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).

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

[0080] (Status Information) The status information ST10 is used to select an active correspondence. As long as an active correspondence can be selected, the status information ST10 may not be particularly limited. The configuration of the status information ST10 may be appropriately determined according to the selection conditions, etc. Furthermore, the management server 1 may acquire the status information ST10 in real time from at least one of the relevant individual of the first target VA (e.g., the corresponding first terminal 4) for which two or more correspondence settings are established and each of the relevant individuals of two or more second target WAs (e.g., each of the corresponding second terminals 5) for which a correspondence relationship is set between the relevant individual of the first target VA and the relevant individual of the second target WA, at any timing before performing the arbitration process. This may activate the link setting between the relevant individuals of the first target VA and the second target WA in which a usage relationship is currently occurring. In this embodiment, at least one of the following three methods may be adopted as a method for selecting an active correspondence.

[0081] (1) First Method FIG. 4A is a schematic diagram showing an example of a process of selecting a pegging setting to be activated by the first method according to the present embodiment. In the example of FIG. 4A, the first object VA1 is an example of an individual of the first object VA in which two or more correspondence settings with two or more second objects WA (two or more individuals of the second object WA) are established. An individual of the first object VA in which two or more correspondence settings are established is also referred to as a "first individual of the first object". The second object WA2 and the second object WA3 are examples of other second objects WA (other individuals of the second object WA) in which a correspondence setting has already been established with the first object VA1 (the first individual of the first object VA). A situation is assumed in which a pegging request (a request to establish a new pegging setting) with the second object WA1 is accepted when the correspondence setting with the second object WA2 is active and the correspondence setting with the second object WA3 is non-active. Also, a situation is assumed in which a usage relationship between the first object VA1 and the second object WA1 among the second objects WA1 to WA3 is currently occurring.

[0082] In the first method, a first target VA (first target VA1) for which two or more correspondence relationships are established is In response to the selection by the first target VA (first target VA1), the binding setting to be activated may be selected. That is, the status information ST10 may include a selection by the first target VA (first target VA1). In response to this, activating one correspondence setting may be configured by activating the correspondence setting selected by the first target VA (first target VA1).

[0083] 4A, the first target VA1 selects the second target WA1 from among the second targets WA1 to WA3. In response to this, the binding setting of the first target VA1 may be updated such that an active binding setting is established between the first target VA1 and the second target WA1, and the state of the binding setting between the first target VA1 and the second target WA2 is changed from active to non-active.

[0084] In addition, selecting the binding setting to be activated may include directly selecting the binding setting to be activated, and indirectly selecting the binding setting to be activated by selecting the binding setting to be deactivated. Selecting the binding setting may include selecting the second target WA. The selection may be performed by automatic processing by a computer (terminal) or may be performed manually.

[0085] Furthermore, the selection of the binding setting to be activated may be accepted by at least one of the first terminal 4 of the first target VA (first target VA1) and the second terminal 5 of the second target WA. The second terminal 5 of the second target WA may be the second terminal 5 of the second target WA (second target WA1 in FIG. 4A) with which the usage relationship is currently occurring. The status information ST10 may be transmitted from at least one of the first terminal 4 and the second terminal 5 to the management server 1. In one example, the status information ST10 may be transmitted from one terminal that has accepted the selection of the first terminal 4 or the second terminal 5. In another example, the status information ST10 may be transmitted from another terminal different from the one terminal that has accepted the selection of the first terminal 4 or the second terminal 5 by data exchange of the selection result.

[0086] Moreover, the trigger for transmission may be any. In one example, at least one of the first terminal 4 and the second terminal 5 may transmit the status information ST10 to the management server 1 as spontaneous information processing accompanying a linking request. In another example, at least one of the first terminal 4 and the second terminal 5 may transmit the status information ST10 to the management server 1 as a reply to an inquiry from the management server 1. The transmitted status information ST10 may be appropriately configured to indicate the selection result of the first target VA. According to one example of this embodiment, an active linking setting can be selected by a simple process.

[0087] (2) Second Method Fig. 4B is a schematic diagram showing an example of a process of selecting a binding setting to be activated by a second method according to the present embodiment. The preconditions of Fig. 4B are the same as those of Fig. 4A, and the example of Fig. 4B also assumes a similar situation to that of Fig. 4A.

[0088] In the second method, a binding setting with a second target WA involved in the most recent authentication of the first target VA (first target VA1) may be selected as the binding setting to be activated. That is, the status information ST10 may include a report of the execution result of the authentication process for the first target VA (first target VA1) by the second terminal 5. In response to this, activating the setting of one target relationship may be configured by activating the setting of the correspondence relationship with the second target WA corresponding to the second terminal 5 that most recently reported the execution result of the authentication process for the first target VA (first target VA1).

[0089] In the example of FIG. 4B, among the second targets WA1 to WA3, the second terminal 5 of the second target WA1 is involved in the most recent authentication process of the first target VA1, and the status information ST10 includes information indicating that this authentication has been established. In response to this, the association setting of the first target VA1 is An active binding setup may be established with the second target WA1, and the state of the binding setup with the second target WA2 may be updated to change from active to non-active.

[0090] The authentication process of the first target VA (first target VA1) may be executed starting from at least one of the first terminal 4 and the second terminal 5. In the example of FIG. 2, the second terminal 5 of the mobile object (second target WA) may authenticate the user (first target VA) by performing face authentication using an image sensor provided on the mobile object, performing fingerprint authentication using a fingerprint reader attached to a steering wheel, having the user speak and performing voiceprint authentication using a microphone provided on the mobile object, or the like. However, the authentication method is not limited to these examples and may be appropriately selected depending on the embodiment. A known method may be adopted as the authentication method.

[0091] If the second terminal 5 is involved in the authentication process, the authentication process may be executed by at least one of the first terminal 4 and the second terminal 5. Also, at least a part of the authentication process may be executed by at least one of the management server 1 and an external server (e.g., the first server 2). The second terminal 5 being involved in the authentication process may include the second terminal 5 executing at least a part of the authentication process, and the second terminal 5 executing information processing related to the authentication process (e.g., executing data exchange with the first terminal 4) although the authentication process is executed by another computer (e.g., the first terminal 4, the management server 1, the first server 2). The authentication process may be triggered by the second terminal 5.

[0092] The status information ST10 may be transmitted from at least one of the first terminal 4 and the second terminal 5 to the management server 1. In one example, when at least one of the first terminal 4 and the second terminal 5 executes the authentication process, the status information ST10 may be transmitted from one of the first terminal 4 and the second terminal 5 that has completed the authentication process, or may be transmitted from another terminal different from the one terminal. When the status information ST10 is transmitted from another terminal, the completion of the authentication process may be notified from one terminal to the other terminal by any method. In another example, after the status information ST10 is transmitted from at least one of the first terminal 4 and the second terminal 5, at least one of the management server 1 and the external server may execute at least a part of the authentication process. In this case, the status information ST10 may be in an incomplete state at the stage when it is transmitted from at least one of the first terminal 4 and the second terminal 5. The status information ST10 may be configured to indicate the authentication result of the first target VA after the authentication process is completed by at least one of the management server 1 and the external server executing at least a part of the authentication process.

[0093] Also, as in the first method, the trigger of transmission may be arbitrary. In one example, at least one of the first terminal 4 and the second terminal 5 may execute information processing on the authentication process as spontaneous information processing accompanying the linking request, and transmit the status information ST10 to the management server 1. Executing the information processing on the authentication process may include at least one of the first terminal 4 and the second terminal 5 executing the authentication process by itself, and requesting the authentication process from an external computer (e.g., the management server 1, the first server 2). In another example, at least one of the first terminal 4 and the second terminal 5 may execute information processing on the authentication process in response to an inquiry from the management server 1, and transmit the status information ST10 to the management server 1 as a reply to the inquiry. According to one example of the present embodiment, by accompanying the authentication process of the first target VA, it is possible to appropriately identify the individual of the second target WA that is currently in a usage relationship with the individual of the first target VA. As a result, it is expected that an appropriate linking setting will be activated.

[0094] (3) The third method Fig. 4C is a schematic diagram showing an example of a process of selecting a binding setting to be activated by a third method according to the present embodiment. The prerequisites of Fig. 4C are the same as those of Fig. 4A, and the example of Fig. 4C also assumes a similar situation to that of Fig. 4A.

[0095] In the third method, the linking setting to be activated may be selected according to the positional relationship between the first individual (first terminal 4) of the first target VA and each individual (each second terminal 5) of the second target WA. That is, each first terminal 4 may include a positioning module 47. Each second terminal 5 may include a positioning module 57. The status information ST10 may include a first current position measured by the positioning module 47 of the first terminal 4 corresponding to the first target VA (first individual of the first target VA1 / first target VA) and a second current position measured by the positioning module 57 of the second terminal 5 corresponding to each of two or more second target WAs (each individual of the second target WA). In response to this, activating one correspondence setting may be configured by activating a correspondence setting with a second target WA where the second current position of the corresponding second terminal 5 satisfies a condition of a usage relationship between the first current position of the first terminal 4 and the second current position of the corresponding second terminal 5.

[0096] The condition of the usage relationship may be set as appropriate. In one example, the condition of the usage relationship may be defined by a range DR of a distance based on the first current location. In this case, whether or not the condition of the usage relationship is satisfied may be determined depending on whether or not it exists within the range DR. In one example of FIG. 4C, among the second targets WA1 to WA3, the second terminal 5 of the second target WA1 exists within the range DR based on the first terminal 4 (first current location) of the first target VA1. The status information ST10 may include at least the first current location of the first terminal 4 of the first target VA1 and the second current location of the second terminal 5 of the second target WA1, and it may be determined as appropriate that the second terminal 5 of the second target WA1 exists within the range DR. In response to this, the pegging setting of the first target VA1 may be updated so that an active pegging setting is established with the second target WA1, and the state of the pegging setting with the second target WA2 is changed from active to non-active.

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

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

[0099] Information on each current location (status information ST10) may be transmitted from each first terminal 4 and each second terminal 5 to the management server 1 at any timing. In one example, each terminal (4, 5) of each target (VA, WA) for which a linking setting has been established may report information on each current location to the management server 1 as a spontaneous information process such as periodic transmission. In this case, the management server 1 may determine a second target WA that satisfies the conditions of the usage relationship from the information on each most recently reported current location. In another example, the management server 1 may directly or indirectly transmit a request to each terminal (4, 5) at any timing before performing the arbitration process. In response to this request, each terminal (4, 5) may report information on the most recent current location to the management server 1 in real time. The management server 1 may determine a second target WA that satisfies the conditions of the usage relationship from the information on the most recent current location reported in real time. In either case, there may be a second terminal 5 that does not report (respond) its second current location due to the power of the second terminal 5 being off, etc. In this case, the second target WA corresponding to the second terminal 5 that has not reported its most recent second current location may be determined not to satisfy the conditions of the usage relationship, and accordingly, the correspondence relationship with the second target WA may be set to non-active.

[0100] Further, the destination of the report of the information of each current position may be appropriately selected depending on the embodiment. In one example, the destination of the report 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 report of the information of each current position may be The destination of the report 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 (status information ST10) 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, the NAS, etc.). Similarly, when the form of reporting indirectly 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. According to one example of this embodiment, by using the location information, it is possible to appropriately identify an individual of the second target WA that is currently in a usage relationship with the individual of the first target VA. This will hopefully ensure that the appropriate binding settings are activated.

[0101] (Lock active settings) For example, in the scene of FIG. 2, assume that an active correspondence relationship is set between the relevant individual (relevant user) of the first target VA and one individual of the second target WA, which is a moving body of a public transport facility. In this scene, even if the settlement of the moving body of the public transport facility has not been completed, it is not desirable for the relevant user (the relevant individual of the first target VA) to use another moving body (another individual of the second target WA) to cancel (deactivate or cancel) the active correspondence relationship with the relevant individual of the moving body (one individual of the second target WA) and establish a new active correspondence relationship setting with the other moving body. In this way, when the relevant individual of the second target WA is of a predetermined type, it may be desirable to refuse to establish an active correspondence relationship setting with another individual of the second target WA until a predetermined condition is satisfied (in the above example, settlement is completed).

[0102] Therefore, in one example of this embodiment, the management server 1 may be configured to further execute the following: after establishing an active correspondence setting with a second target WA (one individual of the second target WA) of a first predetermined type, the management server 1 may further lock the active correspondence setting until a predetermined condition is satisfied, thereby prohibiting the establishment of other active correspondence settings between the first target VA (corresponding individual of the first target VA) with which an active correspondence has been set and other second target WA (other individuals of the second target WA).

[0103] Establishing an active correspondence setting with the second target WA of the first predetermined type may include establishing a new link setting in an active state with the corresponding individual of the second target WA, and changing the state of the link setting with the corresponding individual of the second target WA from non-active to active. Prohibiting the establishment of other active correspondence setting may include prohibiting the establishment of a new link setting in an active state with other individuals of the second target WA, and prohibiting the change of the state of the link setting with other individuals of the second target WA from non-active to active. Establishing a new link setting with other individuals of the second target WA in an inactive state may or may not be permitted.

[0104] The predetermined condition may be set as appropriate depending on the embodiment. Furthermore, whether or not the predetermined condition is satisfied may be detected as appropriate. In a simple example, satisfaction of the predetermined condition may be detected by a notification from the second terminal 5 corresponding to the relevant individual of the second target WA of the first predetermined type. In the above example, when the settlement is completed, the second terminal 5 of the relevant individual of the mobile object may transmit a notification indicating the settlement completion (satisfaction of the predetermined condition) to the management server 1. By receiving this notification, the management server 1 may recognize that the predetermined condition is satisfied. Note that the management server 1 may also execute such a locking process for second target WAs of types other than the first predetermined type. However, for other types of second targets WA, the execution of the locking process may be omitted.

[0105] FIG. 5 is a schematic diagram showing an example of a scene in which an active association setting according to the present embodiment is locked. In the example shown in FIG. 5, the second object WA4 is an example of a second object WA of a first predetermined type. The first object VA1 is an example of a first object VA with which an active association setting has been established with one individual of the second object WA of the first predetermined type. The second object WA5 is an example of another second object WA (another individual of the second object WA) with which an active association setting is attempted to be established with the first object VA1.

[0106] In the example of Fig. 5, the management server 1 may lock the setting of the correspondence relationship between the first target VA1 and the second target WA4 until a predetermined condition is satisfied. If a linking request is received from at least one of the first terminal 4 of the first target VA1 and the second terminal 5 of the second target WA5 during this locking period, the management server 1 may ignore the linking request without permitting the establishment of an active correspondence relationship with the second target WA5 in response to the linking request. In this case, the management server 1 may directly or indirectly send a notification indicating that the setting of another active correspondence relationship is prohibited to at least one of the first terminal 4 of the first target VA1 and the second terminal 5 of the second target WA5.

[0107] The management server 1 may unlock the setting of the correspondence relationship with the second object WA in response to detecting the satisfaction of a predetermined condition. In this way, the management server 1 may permit the establishment of an active correspondence relationship setting with another individual of the second object WA. After unlocking, when a linking request is received from at least one of the first terminal 4 of the first object VA1 and the second terminal 5 of the second object WA5, the management server 1 may establish an active correspondence relationship setting with the second object WA5 in response to the linking request. According to an example of this embodiment, in a situation where it is inappropriate to establish another active correspondence relationship setting, the establishment of such another active correspondence relationship setting can be prohibited by locking the established active correspondence relationship setting.

[0108] The first predetermined type may be appropriately selected depending on the embodiment. In one example, the first object VA may be a user. The second object WA of the first predetermined type may be a public transportation vehicle. The predetermined condition may be that payment (settlement) for the use of the public transportation vehicle is completed. According to one example of the present embodiment, when the transportation vehicle vehicle fee is unpaid, transfer to another vehicle (establishment of an active correspondence setting with another vehicle) can be prohibited.

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

[0110] 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 servers (2, 3), or may be transmitted to an external computer such as the management server 1. The authentication result may be transmitted directly from the terminals (4, 5) to the management server 1, or indirectly via an external computer such as the servers (2, 3). When the management server 1 executes the authentication process, the data used for authentication may be transmitted directly from the terminals (4, 5) to the management server 1, or may be transmitted indirectly via an external computer such as the servers (2, 3). The management server 1 may acquire the authentication result as appropriate, and may determine that the correspondence relationship continues if the authentication of the target is established in the acquired authentication result, and may determine that the correspondence relationship does not continue if the authentication is not established.

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

[0112] 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. 4C. 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.

[0113] If it is determined that the correspondence relationship continues, the management server 1 may maintain the setting state of the correspondence relationship (for example, may maintain it in an active state). On the other hand, if it is determined that the correspondence relationship does not continue, the management server 1 may cancel the correspondence relationship or change the state of the correspondence relationship from active to non-active. After the correspondence relationship is set, the management server 1 may be configured to update the state of the correspondence relationship by repeatedly executing the confirmation process periodically or irregularly until the correspondence relationship is canceled.

[0114] (Unlink) In this embodiment, the management server 1 may be configured to cancel the correspondence (disable or change it to inactive) 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 specified cancellation condition.

[0115] (I) Request for cancellation In one example, the release request includes 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.

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

[0117] Similarly, when the second terminal 5 transmits an unlock request including the first identifier I10, the second terminal 5 may acquire the first identifier I10 at any timing. In one example, when making a linking request, the second terminal 5 may acquire the first identifier I10 and store the acquired first identifier I10 in the memory resource. In the case of an unlock request, the second terminal 5 may acquire the first identifier I10 from the memory resource. Also, when the second terminal 5 transmits an unlock request including the second identifier I20, the second terminal 5 may acquire the second identifier I20 at any timing. In one example, the second identifier I20 may be stored in advance in the memory resource. The second terminal 5 may acquire the second identifier I20 from the memory resource.

[0118] FIG. 6 is a schematic diagram showing an example of a process of untying according to the present embodiment. In the example of FIG. 6, as a first route, the first terminal 4 directly transmits an unbinding request to the management server 1 (step SZ10). As a second route, the first terminal 4 gives an instruction to the second terminal 5 (step SZ10A) to cause the second terminal 5 to directly transmit an unbinding request to the management server 1 (step SZ11A). However, the transmission route of the unbinding request is not limited to this example. The first terminal 4 may indirectly transmit the unbinding request to the management server 1 via an external computer such as the first server 2. In the second route, the second terminal 5 may indirectly transmit the unbinding request to the management server 1 via an external computer such as the second server 3. Note that the origin of the unbinding request is not limited to the first terminal 4. In another example, the second terminal 5 may directly or indirectly transmit the unbinding request to the management server 1. Furthermore, the second terminal 5 may 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 association information D10 and releases (deactivates or deactivates) the correspondence specified by the identifier included in the release request. After this release process, the management server 1 may transmit a notification indicating the result of the release process to at least one of the first terminal 4 and the second terminal 5, in the same manner as when the association was set.

[0119] 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, depending on the sensor device used for data exchange, a distinction may be made between data exchange at the time of linkage setting and data exchange at the time of linkage release. When the data exchange is executed by an application of the terminal, the application may be configured to be switchable between a binding setting mode and a binding release mode. In this case, a distinction may be made between binding setting and binding release depending on the mode of the application.

[0120] 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 (disable or deactivate) the correspondence relationship specified by the release request.

[0121] In addition, there may be cases where a non-active correspondence relationship between the individual of the first target VA and one or more other individuals of the second target WA is maintained. In this case, in response to the invalidation or non-activation of the correspondence relationship specified in the release request, the management server 1 may activate one of the non-active correspondence relationships between the individual of the first target VA and one or more other individuals of the second target WA maintained. The correspondence relationship to be activated may be determined according to the priority, type (e.g., whether it is a regular use object or a temporary use object) of each individual of the second target WA. As a specific example, in the example of FIG. 2, it is assumed that the first moving object is a regular use object (e.g., a personal car, etc.) and the second moving object is a temporary use object (e.g., a rental car, a shared car, a moving object of public transportation, etc.). In this case, the management server 1 may change the state of the previous correspondence relationship (the correspondence relationship with the first moving object) to non-active in response to receiving the setting of the correspondence relationship between the target user and the second moving object while the correspondence relationship between the target user and the first moving object is set. Then, in response to the invalidation or deactivation of the correspondence with the second mobile object (temporarily used object), the management server 1 may activate the correspondence between the first mobile object (regularly used object) and the target user. This makes it possible to quickly restore the setting of an active correspondence with the regular-usage object.

[0122] (I-1) Maintaining pegging settings When making a release request, it may be appropriately selected whether to release (invalidate) the corresponding linking setting or to change the state of the linking setting to inactive. However, in certain situations, it may be efficient to select to maintain the linking setting in an active or inactive state without selecting to release (invalidate) the linking setting. For example, in the situation of FIG. 2, if the corresponding individual of the second target WA is a private car, the corresponding individual of this second target WA is repeatedly used by the first target VA (user). Therefore, it may be possible to improve the efficiency of processing by switching between active and inactive rather than repeatedly creating and deleting the correspondence each time it is used.

[0123] Therefore, in one example of this embodiment, the management server 1 may be further configured to, when a predetermined relationship is established between a first target VA and a second target WA between which a corresponding relationship is set, not release (invalidate) the corresponding relationship until the predetermined relationship is dissolved, but to maintain the corresponding relationship in an active or non-active state, and release the corresponding relationship after the predetermined relationship is dissolved. Release (invalidate) the target relationship may include release of the target relationship in response to the dissolution of the predetermined relationship, and release of the target relationship in response to receiving a release request after the predetermined relationship is dissolved.

[0124] FIG. 7 is a schematic diagram showing an example of a situation where the association setting according to the present embodiment is maintained in an active or inactive state. The first object VA1 and the second object WA6 are an example of the first object VA and the second object WA in which a predetermined relationship is established. In the example of FIG. 7, the management server 1 may maintain the setting of the correspondence relationship between the first object VA1 and the second object WA6 in an active or inactive state while the predetermined relationship is established. On the other hand, after the predetermined relationship is dissolved, the management server 1 may cancel (invalidate) the correspondence relationship between the first object VA1 and the second object WA6.

[0125] According to an example of the present embodiment, in a situation where a predetermined relationship is established, it is expected that the processing for setting the correspondence relationship will be made more efficient. The predetermined relationship that specifies the targets for which the correspondence relationship is to be maintained may be set appropriately depending on the embodiment. From the viewpoint of improving the processing efficiency for the association setting, it is desirable that the predetermined relationship is a relationship that continues for a certain period of time, and during that period, the occurrence and disappearance of the usage relationship are repeated.

[0126] In one example, the predetermined relationship may be an ownership relationship. That is, while the ownership relationship between the first object VA and the second object WA is established, the setting of the correspondence relationship between the corresponding individuals of the first object VA and the second object WA may be maintained, and after the ownership relationship ends, the correspondence relationship may be canceled (invalidated). According to one example of the present embodiment, in a situation where the ownership relationship is established between the first object VA and the second object WA, the efficiency of the process related to the setting of the correspondence relationship can be expected.

[0127] The objects (VA, WA) between which the ownership relationship is established may not be particularly limited, and 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 a moving object (e.g., a personal car) owned by the user. According to one example of the present embodiment, in a scene in which a moving object owned by the user appears, it is expected that the processing for setting the correspondence relationship will be made more efficient.

[0128] In another example, the first object VA may be a user, and the second object WA may be a moving object that is rented (subject) by the user. The predetermined relationship may be that the user rents the moving object. That is, while the moving object is rented by the user, the setting of the correspondence relationship between the user and the moving object may be maintained, and the correspondence relationship may be released (invalidated) after the rental period ends. According to one example of the present embodiment, in a scene in which a rented moving object (e.g., a rental car) appears, it is expected that the processing for setting the correspondence relationship will become more efficient.

[0129] In addition, whether or not the predetermined relationship is established may be appropriately determined depending on the embodiment. For example, whether or not the moving body (second target WA) is an object with which the predetermined relationship is established, such as a personal car or a rental car, may be determined from attribute information. Therefore, in one example, whether or not the predetermined relationship is established may be determined from attribute information of at least one of the first target VA and the second target WA. The attribute information may be included in each object information (O10, O20). In another example, whether or not the predetermined relationship is established may be determined from information (ownership information, rental information, etc.) provided by an external system. The external system may be, for example, a terminal of a dealer, a terminal of a rental company, or the like, which is involved in the predetermined relationship. In yet another example, whether or not the predetermined relationship is established may be determined according to a notification from at least one of the first terminal 4 of the first target VA and the second terminal 5 of the second target WA.

[0130] Furthermore, the termination of a predetermined relationship may be detected as appropriate depending on the embodiment. In one example, the termination of a predetermined relationship may be detected from information provided by an external system (information on changes in ownership, information on lease termination, etc.). In another example, at least one of the first terminal 4 and the second terminal 5 of the first target VA and the second target WA with which a predetermined relationship was established sends a notification to the management server 1 or an external server (the third The management server 1 may detect that the predetermined relationship has been dissolved by receiving the notification or by referring to information in an external server.

[0131] (I-2) Cancellation of pegging settings For example, in the scene of Figure 2, depending on the types of the first target VA and the second target WA, the occurrence and disappearance of the usage relationship may be rare, such as when the second target WA is a moving object of public transportation. In such a case, by choosing to cancel (disable) the pegging setting rather than maintaining it, it may be possible to improve the efficiency of memory resources used to maintain the pegging setting.

[0132] Therefore, in one example of this embodiment, the management server 1 may be further configured to cancel (invalidate) the correspondence relationship in response to detecting the end of use of the second target WA after establishing the setting of the correspondence relationship with the second target WA of the second predetermined type. The end of use is an example of the disappearance of the usage relationship. The end of use may be detected appropriately depending on the embodiment. In one example, with the end of use, at least one of the first terminal 4 and the second terminal 5 may execute any information processing, and the execution of this information processing may be used as a trigger to transmit a cancellation request from at least one of the first terminal 4 and the second terminal 5. The end of use may be detected by this cancellation request.

[0133] FIG. 8 is a schematic diagram showing an example of a scene in which the linking is released (invalidated) according to the present embodiment. In the example of FIG. 8, the second target WA7 is an example of a second target WA of a second predetermined type. The first target VA1 is an example of a first target VA that has established a correspondence setting with the second target WA of a second predetermined type. In the example of FIG. 8, the first terminal 4 of the first target VA1 and the second terminal 5 of the second target WA7 may execute data exchange when use starts. This data exchange may be used as a trigger for at least one of the first terminal 4 and the second terminal 5 to transmit a linking request to the management server 1. In the example of FIG. 8, the management server 1 assumes a scene in which an active linking setting is established between the first target VA1 and the second target WA7 in response to this linking request. Thereafter, when use ends, the first terminal 4 of the first target VA1 and the second terminal 5 of the second target WA7 may execute data exchange. This data exchange may be used as a trigger for at least one of the first terminal 4 and the second terminal 5 to transmit a release request to the management server 1. In response to this cancellation request, the management server 1 may cancel (invalidate) the correspondence between the first object VA1 and the second object WA7.

[0134] According to an example of this embodiment, when the second object WA is a second predetermined type, it is expected that the memory resources used to maintain the association setting can be made more efficient. The second predetermined type may be appropriately selected depending on the embodiment. From the viewpoint of memory resource efficiency, it is desirable that the second predetermined type is one in which an active correspondence relationship is set (i.e., a usage relationship occurs) between the same individual of the second object WA and the same individual of the first object VA less frequently.

[0135] In one example, the first target VA may be a user, and the second target WA may be a moving object. The second target WA of the second predetermined type may be a moving object of public transportation. That is, when the user uses the moving object of public transportation, an active correspondence setting may be established between the moving object and the user. When the user finishes using the moving object of public transportation, the correspondence may be released (invalidated). According to one example of the present embodiment, in a scene where a moving object of public transportation (e.g., a taxi, etc.) appears, it is expected that the memory resources used to maintain the association setting can be made more efficient.

[0136] (II) Termination Conditions The release condition indicates the condition for releasing (invalidating or deactivating) the target correspondence relationship. The cancellation conditions may be defined appropriately depending on the embodiment.

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

[0138] In another example, the release condition may be defined such that, when multiple correspondence settings are overlapped for the same individual of the first target VA or the second target WA due to the interruption of the correspondence setting by at least one other individual of the first target VA and the second target WA, any of the overlapping correspondences is released. The number of active correspondences (linking) that can be set for the same individual of the second target WA is not limited to one, and may be two or more. In addition, the number of correspondences (linking) that can be maintained in a non-active state for the same individual of the first target VA may be infinite or finite. When the overlap of the correspondence settings exceeds a threshold (upper limit), the management server 1 may release any of the correspondences that have been previously set and maintained. The threshold may be given as appropriate. Which correspondences are to be released may be determined as appropriate according to the priority, order, type of target, and the like. The management server 1 may send an inquiry regarding the release to at least one of the first terminal 4 and the second terminal 5, and determine the correspondence to be released according to the response obtained.

[0139] 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 attributes of the use (e.g., the number of possible 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 (invalidate or deactivate) 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).

[0140] As a specific example, in the example of FIG. 2, it is assumed that the moving object is a private car, and 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 an active correspondence relationship between one of the first user and the second user and the target private car is 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 change the state of the previous correspondence relationship (the correspondence relationship between one user and the target private car) from active to non-active.

[0141] Furthermore, the number of uses that can maintain a link with the same user in an inactive state may be infinite or finite. If the number of uses that can maintain a link is finite, an upper limit on the number of uses may be appropriately set by a threshold. When the management server 1 receives a new correspondence setting for the target user, it may refer to the linking information D10 and extract the previous correspondence that has been set and maintained for the target user. If the newly received correspondence setting causes the overlap of the correspondence setting for the target user to exceed the threshold, the management server 1 may discard the request for the newly received correspondence setting, or may discard the extraction At least one of the previously established correspondence relationships may be cancelled (invalidated). When cancelling the previous correspondence relationships, the management server 1 may determine which correspondence relationships to cancel depending on the priority and type of the object (for example, whether it is a regular object or a temporary object) of the object.

[0142] Incidentally, even when the target correspondence relationship is cancelled in response to the establishment of a specified cancellation condition, the above-mentioned form may be adopted in which the correspondence relationship is not cancelled (invalidated) and is maintained in an active or inactive state until the specified relationship is resolved. In other words, when the specified relationship is established, the management server 1 may select a process of changing the state of the specified correspondence relationship to inactive as a cancellation process in response to the establishment of a specified cancellation condition until the specified relationship is resolved. After the specified relationship is resolved, the management server 1 may cancel the correspondence relationship.

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

[0144] In another example, the linking information D10 may be used to enable at least a part of the authority linked to either the first target VA or the second target WA to be exercised from the other while an active correspondence 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 the active correspondence setting, enabling the exercise of the authority associated with the corresponding first target VA (the corresponding individual of the first target VA) via the second target WA (the corresponding individual of the second target WA) with which the active correspondence is set. In addition, the management server 1 may be configured to further execute, in response to the establishment of the non-active correspondence setting, disabling the exercise of the authority associated with the corresponding first target VA via the second target WA with which the non-active correspondence is set. In the example of FIG. 2, the linking information D10 may be used to enable at least a part of the authority linked to the user to be exercised from the moving body while an active correspondence is set between the user and the moving body. According to one example of this embodiment, the state of the correspondence setting can be switched between active and non-active to control permission and prohibition of the exercise of the authority associated with the first target VA.

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

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

[0147] 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 an active correspondence relationship setting is maintained at the target date and time. In addition, the target date and time is basically 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 associated with the target moving object is extracted. On the other hand, if there is no valid correspondence relationship and a user associated with the target moving object is not extracted, this process may end.

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

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

[0150] 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 activating the correspondence relationship of one of the plurality of users who use the same individual moving body. In another example, the correspondence relationship of two or more users among the plurality of users who use the same individual moving body may be set to active. In this case, the method of exercising the authority may be appropriately adjusted among the two or more users for which the active correspondence relationship is set. 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 designated as appropriate.

[0151] 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 the priority may be set according to the relationship within the family. For example, the priority of parents may be set high, and the priority of children may be set low. The group and priority information 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, the correspondence relationship of two or more users in the same group may be set to active. 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 higher, the authority of the parent may be exercised. Exercising the authority according to the priority may include selecting a user who will exercise 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.).

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

[0153] (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 is performed using a method such as SSL (Secure Socket Layer) or TLS (Transport Layer Security). In one example, each of the terminals (4, 5) may include a Subscriber Identity Module (SIM), and data communication between each of the terminals (4, 5) and the servers (management server 1, first server 2, second server 3) may be performed by encrypted communication using the SIM.

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

[0155] The control unit 11 includes a CPU (Central Processing Unit) which is a hardware processor, The management server 1 includes a RAM, a ROM (Read Only Memory), etc., and is configured to execute any information processing based on programs and various data. The control unit 11 (CPU) is an example of a processor resource of the management server 1.

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

[0157] 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, or the like. The management server 1 is Through the interface 13, data communication may be performed with other computers (the first server 2, the second server 3, the first terminal 4, and the second terminal 5).

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

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

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

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

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

[0163] The control unit 41 (CPU) is an example of a processor resource of the first terminal 4, and the storage unit 42 (and RAM, ROM) is an example of a memory resource of the first terminal 4. In this embodiment, the storage unit 42 stores various information such as a program 84 and a first identifier I10. The program 84 is a program for causing the first terminal 4 to execute information processing related to the association (FIGS. 12 and 13 described later). The program 84 includes a series of instructions for the information processing. At least one of the program 84 and the first identifier I10 may be stored in a storage medium 94 instead of or together with the storage unit 42. The first terminal 4 may acquire at least one of the program 84 and the first identifier I10 from the storage medium 94. The first terminal 4 may 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 an input device 44 and an output device 45.

[0164] In addition, regarding the specific hardware configuration of the first terminal 4, components can be omitted, replaced, or added as appropriate depending on the embodiment. For example, the control unit 41 may include multiple hardware processors. The hardware processor is configured by a microprocessor, FPGA, DSP, GPU, ASIC, ECU (Electronic Control Unit), etc. At least one of the input device 44, the output device 45, the drive 46, and the positioning module 47 may be omitted. The first identifier I10 may not be stored in the storage unit 42. The first identifier I10 may be acquired each time. In order to acquire data such as the identifier and information used for authentication, the first terminal 4 may further include a data acquisition device such as a sensor or a reader. The communication interface 43 may be configured with multiple types of modules. For example, the communication interface 43 may include a short-range wireless communication module 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 (the management server 1, the first server 2, and the second server 3) via the wireless communication module. The first terminal 4 may be configured with multiple computers. In this case, the hardware configurations of the computers may or may not be the same. The first terminal 4 may be a general-purpose computer, a terminal device (e.g., a smartphone, a tablet PC, etc.), etc., in addition to an information processing device designed specifically for the service provided.

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

[0166] 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 the storage medium 95 instead of the storage unit 52 or together with the storage unit 52. The second terminal 5 may acquire at least one of the program 85 and the second identifier I20 from the storage medium 95. The second terminal 5 may 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 the input device 54 and the output device 55.

[0167] In addition, regarding the specific hardware configuration of the second terminal 5, components can be omitted, replaced, and added as appropriate depending on the embodiment. For example, the control unit 51 may include multiple hardware processors. The hardware processor may be configured with a microprocessor, FPGA, DSP, GPU, ASIC, ECU, etc. At least one of the input device 54, the output device 55, the drive 56, and the positioning module 57 may be omitted. The second identifier I20 may not be stored in the storage unit 52. 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 5 may further include a data acquisition device such as a sensor or a reading device. 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 be the same or different. The second terminal 5 may be a general-purpose computer, a terminal device, etc., in addition to an information processing device designed exclusively for the service provided.

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

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

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

[0171] The setting unit 112 is configured to execute a setting process of the received correspondence relationship. The setting process may include setting a new active 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, and changing the state of the correspondence relationship from non-active to active. In response to receiving a correspondence relationship setting by two or more linking requests related to the same individual of the first target VA, two or more correspondence relationship settings with two or more different individuals of the second target WA may be established for the same corresponding individual of the first target VA. In this case, the setting unit 112 is configured to make one of the two or more correspondence relationship settings active and the other correspondence relationship settings non-active according to the status information ST10 obtained from at least one of the corresponding individual of the first target VA and the two or more individuals of the second target WA.

[0172] The cancellation unit 113 is configured to execute a process of canceling the correspondence relationship upon receiving 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. The cancellation process may include canceling (invalidating) the setting of the correspondence relationship and changing the state of the correspondence relationship to non-active.

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

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

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

[0176] (others) In this embodiment, an example is described in which each software module of each device is realized by a general-purpose CPU. However, some or all of the above software modules may be realized by one or more dedicated processors. Each of the above modules may be realized as a hardware module. With respect to the software configuration of each device, modules may be omitted, replaced, 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.

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

[0178] In step S10, in response to the occurrence of a usage relationship between the corresponding individuals of the first object VA and the second object WA, at least one of the control unit 41 of the corresponding first terminal 4 and the control unit 51 of the corresponding second terminal 5 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 operates as a data exchange unit 411 and transmits a linking request to the corresponding second terminal 5. The control unit 51 of the second terminal 5 may operate as a data exchange unit 511 and may exchange data with the first terminal 4. Triggered by this data exchange, the control unit 41 of the first terminal 4 may operate as a setting request unit 412 and transmit a linking request to the management server 1. The control unit 51 of the second terminal 5 may operate as a setting request unit 512 and transmit a linking request to the management server 1. The linking request may be transmitted directly to the management server 1, or indirectly via an external computer (the first server 2, the second server 3, etc.).

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

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

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

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

[0183] In step S25, the control unit 11 of the management server 1 operates as the setting unit 112, and in response to receiving the setting of the correspondence relationship by two or more linking requests for the same individual of the first target VA, determines whether or not the setting of two or more correspondence relationships is established for the same corresponding individual of the first target VA with two or more different individuals of the second target WA. In one example, the control unit 11 determines whether or not an active existing linking setting exists for the corresponding individual of the first target VA specified in the received linking request with other individuals of the second target WA by referring to the linking information D10. If there is no active existing linking setting with other individuals of the second target WA, the control unit 11 proceeds to the process of step S301. On the other hand, if there is an active existing linking setting, the control unit 11 proceeds to the process of step S302.

[0184] In step S301, the control unit 11 operates as the setting unit 112, and updates the linking information D10 to establish a new active correspondence setting between the corresponding individuals of the first object VA and the second object WA specified by the linking request, or to change the state of the existing correspondence to active. The update of the linking information D10 in response to the establishment of a new correspondence setting may be configured by generating the corresponding new linking information D10. The update of the linking information D10 in response to the change of the correspondence state to active may be configured by recording information indicating the change to active. In one example, when the linking information D10 has the configuration of FIG. 3A, the control unit 11 may change the state of the correspondence to active by storing a value indicating active in the state field of the corresponding linking information D10. When the linking information D10 is configured on a blockchain platform, the control unit 11 may change the state of the correspondence to active by generating a transaction indicating the change of the correspondence to active and adding the generated transaction to the blockchain. After updating the linking information D10, the control unit 11 proceeds to the next step S40.

[0185] On the other hand, in step S302, the control unit 11 operates as the setting unit 112 and acquires the status information ST10. The control unit 11 updates the linking information D10 so that one of the correspondence settings is set to active and the other correspondence settings are set to non-active according to the status information ST10. In one example of the present embodiment, at least one of the above three methods may be adopted as a method for selecting an active correspondence. The update of the linking information D10 in response to the establishment of a new correspondence setting and the change of the state of an existing correspondence to active may be similar to the above. The update of the linking information D10 in response to the change of the state of the correspondence to non-active may be configured by recording information indicating the change to non-active. In one example, when the linking information D10 has the configuration of FIG. 3A, the control unit 11 may change the state of the correspondence to non-active by storing a value indicating non-active in the state field of the corresponding linking information D10. When the linking information D10 is configured on a blockchain platform, the control unit 11 may change the state of the correspondence to non-active by generating a transaction indicating a change to non-active and adding the generated transaction to the blockchain. After updating the linking information D10, the control unit 11 proceeds to the next step S40. The processes of steps S301 and S302 are an example of the process of setting the correspondence in response to the received linking request (step S30 above).

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

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

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

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

[0190] In step SZ20, the control unit 11 operates as the release unit 113 and releases (invalidates) the setting of the correspondence specified by the received release request or changes the state of the correspondence from active to non-active. The update of the linking information D10 in response to the change to non-active may be the same as described above. The update of the linking information D10 in response to the release (invalidation) of the correspondence may be configured by recording information indicating the release. In one example, when the linking 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 linking information D10 or setting a release flag. When the linking 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 link and adding the generated transaction to the blockchain.

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

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

[0193] [Features] In this embodiment, information indicating the setting of the correspondence relationship between the relevant 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 use relationship between the relevant individuals of the first target VA and the second target WA. In addition, in this embodiment, a link setting is permitted for one individual of the first target VA with each of multiple individuals of the second target WA. If multiple link settings are established and the link settings for the relevant individual of the first target VA collide, the collision is mediated by switching the state of the link setting by the processing of steps S25 and S302. This makes it possible to properly trace the use relationship regarding the relevant individual of the first target VA. Therefore, in at least some scenes, in this embodiment, it is possible to respond to the occurrence and disappearance of the use relationship by switching the state without repeatedly setting and releasing the link. Therefore, it is possible to easily trace the use relationship between the first target VA and the second target WA.

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

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

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

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

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

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

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

[0201] 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 the first identifier I10 and the first unique information CA1 from the first target VA as appropriate in the data exchange. At least one of CA1 may be obtained from the first terminal 4.

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

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

[0204] 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 target WA to the management server 1. In one example, the second server 3 may transmit the authentication result of the second target WA to the management server 1 with the second identifier I20 of the second target WA attached. 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.

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

[0206] The management server 1 receives the recognition of the individual of each target (VA, WA) from each server (2, 3). The management server 1 receives the authentication result. In order to identify the combination of the corresponding individual of the first target VA and the second target WA that is currently requesting the establishment of the correspondence relationship, the management server 1 may identify the correspondence of the authentication result data by a method such as using the above-mentioned shared information. If the authentication of both the first target VA and the second target WA is successful in the received authentication result of the first target VA and the second target WA, the management server 1 establishes a correspondence relationship between the corresponding individual of the first target VA and the second target WA. The correspondence relationship establishment 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 the association establishment may be executed in real time in response to the occurrence of the usage relationship.

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

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

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

[0210] First, when a usage relationship occurs between the corresponding individuals of the first object VA and the second object WA, data exchange is executed between the corresponding first terminal 4 and second terminal 5 (step SC110, step SD110). At least one of the first terminal 4 and the second terminal 5 transmits an authentication request including the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2 to the management server 1 as a linking request (step SC120, step SD120). In response to this, the management server 1 receives the authentication request including the first identifier I10, the first unique information CA1, the second identifier I20, and the second unique information CA2. The processes of steps SC120 and SD120 are an example of the process of step S10.

[0211] The allocation of data transmission may be appropriately determined depending on the embodiment. In one example, the second terminal 5 may be in charge of transmitting the first identifier I10 and the first unique information CA1, and the first terminal 4 may be in charge of transmitting the second identifier I20 and the second unique information CA2. That is, in step SC110, the 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 a linking request including the acquired second identifier I20 and second unique information CA2 to the management server 1. A linking request including the link may be transmitted to the management server 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0229] 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 unsuccessful, the authentication is unsuccessful. If the first time-limited certificate CB10 / second time-limited certificate CB20 have expired due to the expiration of their validity periods, the comparison of the first target VA / second target WA is unsuccessful. On the other hand, if the first time-limited certificate CB10 and If the two-time certificate CB20 is valid and each match is successful, authentication of both the first target VA and the second target WA is successful. If 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 individuals 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 the first authentication method, etc.

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

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

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

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

[0234] Furthermore, in the above authentication method 3-1, the matching process of each certificate (CB1, CB2) and each time-limited certificate (CB10, CB20), i.e., the authentication process of each target (VA, WA), is performed by the management server 1. However, the entity that performs 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 sending each certificate (CB1, CB2) to each server (2, 3). As a result, the matching process may be performed by each server (2, 3).

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

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

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

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

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

[0240] In response, 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 that of 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. Other configurations may be the same as those of the first authentication method, etc.

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

[0242] 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 the matching to the management server 1. For example, the above authentication request may further include the second identifier I20. If matching is established, the first server 2 may transmit the result of the matching, including the first identifier I10 and the second identifier I20, to the management server 1. As a result, the first server 2 may enable, to the management server 1, a linking request for the combination of the first identifier I10 and the second identifier I20 specified in the result of the matching. That is, in one example, the verification of the success of matching is constituted by receiving this result of the matching. The management server 1 may be configured to hold the result of the matching from the first server 2, accept a request for setting up a linkage for a combination of the first identifier I10 and the second identifier I20 specified by the result of the matching, and reject other requests for setting up a linkage.

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

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

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

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

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

[0248] Next, a first electronic certificate CC1 for the first public key is generated by a 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 depending on the embodiment. In one example, the first electronic certificate CC1 may be composed of an electronic signature by a 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 using a hash function, and encrypting the obtained hash value with the private key of the certification authority.

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

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

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

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

[0253] 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 a 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. Then, the second terminal 5 compares the obtained decrypted data with the remaining information (the possessed information and the first public key) included in the first electronic certificate CC1. If the data is encrypted after being converted into a hash value, the second terminal 5 converts the possessed information and the first public key into a hash value using a hash function and compares the obtained hash value with the decrypted data. If the two match, the second terminal 5 determines that the verification of the validity of the first electronic certificate CC1 is successful, and if the two do not match, it determines that the verification of the validity of the first electronic certificate CC1 is not successful.

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

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

[0256] Note that the processing procedure in FIG. 18A is merely an example, and each step may be modified as much as possible. Furthermore, steps of the above processing procedure may be omitted, replaced, or added as appropriate depending on the embodiment. For example, the processing order of verifying the validity of the first electronic certificate CC1 (steps SI130, SI135) and verifying the validity of the electronic signature CD1 (step SI140) may be modified 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.

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

[0258] FIG. 18B is another example of the process of linking settings when the fourth authentication method is adopted. 18B is a schematic diagram showing a case where the authentication process of the second target WA is executed instead of the authentication process of the first target VA. The process procedure and each data of FIG. 18B may be the same as the process procedure and each data of FIG. 18A, except that the first target VA and the second target WA are replaced. 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 to the second terminal 5 by the certification authority. In the use stage, when a use relationship occurs between the corresponding individuals of the first target VA and the second target WA, data exchange is executed between the corresponding first terminal 4 and the second terminal 5 (steps SJ110 and 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, a series of processes in FIG. 18A and FIG. 18B may be executed to perform authentication processing of the first target VA and the second target WA.

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

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

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

[0262] 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. The non-transitory computer-readable storage medium may be, for example, any type of disk, such as a magnetic disk (floppy (registered trademark) disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only medium, etc. This includes read only memory (ROM), random access memory (RAM), electronic programmable read only memory (EPROM), electronic data read only memory (EEPROM), magnetic cards, flash memory, optical cards, semiconductor drives (such as solid state drives), and any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0263] 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, ST10: Status information, VA: 1st target, WA: 2nd target, I10...first identifier, I20...second identifier, O10…First target information, O10A…User information, O20…second target information, O20A…mobile information, D10: Linking information, E10: Various information

Claims

1. Management server, A 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: Accepting a setting of a correspondence relationship between the first object and the second object by receiving the association request; and when two or more correspondence relationship settings with two or more different second objects are established for the same first object in response to receiving the setting of the correspondence relationship based on two or more of the linking requests related to the same first object, making one of the two or more correspondence relationship settings active and making the other correspondence relationship settings inactive in response to status information obtained from at least one of the first object and the two or more second objects for which the two or more correspondence relationship settings are established; configured to execute system.

2. The management server includes: In response to the establishment of an active correspondence, enabling the exercise of a privilege associated with the corresponding first object through the second object for which the active correspondence is established; and In response to the establishment of the inactive correspondence relationship, invalidating the exercise of a right associated with the corresponding first object through the second object with which the inactive correspondence relationship is established; and further configured to perform The system of claim 1 .

3. the status information includes a selection by the first subject; activating the one correspondence setting comprises activating a correspondence setting selected by the first object. The system of claim 1 .

4. the status information includes a report of a result of an authentication process performed by the second terminal on the first object; activating the setting of the one correspondence relationship is configured by activating a setting of a correspondence relationship with a second object corresponding to the second terminal that has most recently reported a result of the execution of the authentication process with the first object. The system of claim 1 .

5. Each of the first terminals comprises a positioning module; Each of the second terminals comprises a positioning module; the status information includes a first current location measured by a positioning module of a first terminal corresponding to the first object, and a second current location measured by a positioning module of a second terminal corresponding to each of the two or more second objects; Activating the setting of the one correspondence relationship includes: by activating a setting of a correspondence relationship between the first current location of the first terminal and a second object that satisfies the condition of the usage relationship. The system of claim 1 .

6. the management server is further configured to, after establishing an active correspondence setting with a second object of a first predetermined type, lock the active correspondence setting until a predetermined condition is satisfied, thereby prohibiting the establishment of another active correspondence setting between the first object with which the active correspondence is set and another second object; The system of claim 1 .

7. the first object is a user, the second object of the first 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 6.

8. the management server is further configured to, when a predetermined relationship is established between the first object and the second object between which the correspondence relationship is set, not release the correspondence relationship but maintain the correspondence relationship in an active or inactive state until the predetermined relationship is dissolved, and release the correspondence relationship after the predetermined relationship is dissolved. The system of claim 1 .

9. The predetermined relationship is an ownership relationship. The system of claim 8.

10. the first object is a user, The second object is a mobile object owned by the user. The system of claim 9.

11. the first object is a user, The second object is a mobile object rented by the user; The predetermined relationship is that the user is renting the mobile object. The system of claim 8.

12. The management server is further configured to, after establishing a correspondence relationship with a second object of a second predetermined type, cancel the correspondence relationship in response to detecting an end of use of the second object. The system of claim 1 .

13. the first object is a user, the second object is a moving object, The second target of the second predetermined type is a moving object of public transportation. The system of claim 12.

14. 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; Accepting a setting of a correspondence relationship between the first object and the second object by receiving the association request; and Accepting settings of the correspondence relationship by two or more of the linking requests regarding the same first object when two or more correspondence relationship settings are established for the same first object with two or more different second objects in response to the establishment of the two or more correspondence relationship settings, making one of the two or more correspondence relationship settings active and making the other correspondence relationship settings inactive in response to status information obtained from at least one of the first object and the two or more second objects for which the two or more correspondence relationship settings are established; A control unit configured to execute Management server.

15. The control unit is In response to the establishment of an active correspondence, enabling the exercise of a privilege associated with the corresponding first object through the second object for which the active correspondence is established; and In response to the establishment of the inactive correspondence relationship, invalidating the exercise of a right associated with the corresponding first object through the second object with which the inactive correspondence relationship is established; and further configured to perform The management server according to claim 14.

16. the status information includes a report of a result of an authentication process performed by the second terminal on the first object; activating the setting of the one correspondence relationship is configured by activating a setting of a correspondence relationship with a second object corresponding to the second terminal that has most recently reported a result of the execution of the authentication process with the first object. The management server according to claim 14.

17. the status information includes a first current location measured by a positioning module of a first terminal corresponding to the first object, and a second current location measured by a positioning module of a second terminal corresponding to each of the two or more second objects; Activating the setting of the one correspondence relationship is configured by activating the setting of a correspondence relationship with a second object, where a second current location of a corresponding second terminal satisfies a condition of the usage relationship between the second current location of the corresponding second terminal and the first current location of the first terminal. The management server according to claim 14.

18. the control unit is configured to further execute, after establishing an active correspondence setting with a second object of a first predetermined type, locking the active correspondence setting until a predetermined condition is satisfied, thereby prohibiting the establishment of another active correspondence setting between the first object with which the active correspondence is set and another second object; The management server according to claim 14.

19. The control unit is further configured to, when a predetermined relationship is established between the first object and the second object between which the corresponding relationship is set, not release the corresponding relationship but maintain the corresponding relationship in an active or inactive state until the predetermined relationship is released, and release the corresponding relationship after the predetermined relationship is released. The management server according to claim 14.

20. 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; Upon receiving the linking request, a correspondence relationship between the first object and the second object is set. Accepting the when two or more correspondence relationship settings with two or more different second objects are established for the same first object in response to receiving the setting of the correspondence relationship based on two or more of the linking requests related to the same first object, making one of the two or more correspondence relationship settings active and making the other correspondence relationship settings inactive in response to status information obtained from at least one of the first object and the two or more second objects for which the two or more correspondence relationship settings are established; Execute Management method.

Images