Vehicle payment support device
US-2020160335-A1 · May 21, 2020 · US
US12580913B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12580913-B2 |
| Application number | US-202418782237-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 24, 2024 |
| Priority date | Sep 22, 2023 |
| Publication date | Mar 17, 2026 |
| Grant date | Mar 17, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A management system according to one aspect of the present disclosure includes a first server, a second server, and a management server. When a use relationship occurs between a first target and a second target, the first server authenticates the first target in response to a request from a second terminal of the second target, and the second server authenticates the second target in response to a request from a first terminal of the first target. The management server receives results of the authentication from the servers, and sets a correspondence between a first identifier of the first target and a second identifier of the second target when both the first target and the second target have successfully been authenticated.
Opening claim text (preview).
What is claimed is: 1 . A management system comprising: a first server; a second server; and a management server, wherein the first server is configured to execute: receiving a first request for authentication of a first target from a second terminal of a second target in response to occurrence of a use relationship between the first target and the second target; authenticating the first target in response to reception of the first request; and transmitting a result of the authentication of the first target to the management server, wherein the second server is configured to execute: receiving a second request for authentication of the second target from a first terminal of the first target in response to the occurrence of the use relationship between the first target and the second target; authenticating the second target in response to reception of the second request; and transmitting a result of the authentication of the second target to the management server, and wherein the management server is configured to execute: receiving the results of the authentication of the first target and the second target from the first server and the second server; and when the received results of the authentication of the first target and the second target show that both the first target and the second target have successfully been authenticated, setting a correspondence between a first identifier of the first target and a second identifier of the second target. 2 . The management system according to claim 1 , wherein the management server is configured to further execute terminating the correspondence in response to reception of a termination request from at least one of the first terminal and the second terminal or satisfaction of a predetermined termination condition. 3 . The management system according to claim 1 , wherein: the first server is connected in an accessible manner to a first storage device configured to store first registered unique information for the authentication of the first target, the first registered unique information being associated with the first identifier; the second server is connected in an accessible manner to a second storage device configured to store second registered unique information for the authentication of the second target, the second registered unique information being associated with the second identifier; the first request includes the first identifier and first unique information; the second request includes the second identifier and second unique information; the authenticating the first target includes checking the first unique information in the received first request against the first registered unique information associated with the first identifier; and the authenticating the second target includes checking the second unique information in the received second request against the second registered unique information associated with the second identifier. 4 . The management system according to claim 1 , wherein: the first request includes the first identifier and the second identifier; the second request includes the first identifier and the second identifier; the transmitting the result of the authentication of the first target includes transmitting the result of the authentication of the first target with the first identifier and the second identifier in the first request attached to the result; the transmitting the result of the authentication of the second target includes transmitting the result of the authentication of the second target with the first identifier and the second identifier in the second request attached to the result; the management server is configured to further execute associating the received results of the authentication of the first target and the second target in response to agreement between the first identifier and the second identifier attached to the result of the authentication of the first target that has been received from the first server and the first identifier and the second identifier attached to the result of the authentication of the second target that has been received from the second server; and the setting the correspondence between the first identifier and the second identifier includes setting a correspondence between the first identifier and the second identifier corresponding to the associated results of the authentication of the first target and the second target. 5 . The management system according to claim 1 , wherein: the transmitting the result of the authentication of the first target includes transmitting the result of the authentication of the first target with first supplementary information attached to the result; the transmitting the result of the authentication of the second target includes transmitting the result of the authentication of the second target with second supplementary information attached to the result; the management server is configured to further execute associating the received results of the authentication of the first target and the second target in response to successful checking between the first supplementary information and the second supplementary information; and the setting the correspondence between the first identifier and the second identifier includes setting a correspondence between the first identifier and the second identifier corresponding to the associated results of the authentication of the first target and the second target. 6 . The management system according to claim 5 , wherein the first supplementary information and the second supplementary information each include temporary information. 7 . The management system according to claim 6 , wherein: the use relationship between the first target and the second target occurs by data communication between the first terminal and the second terminal; shared temporary information is generated in the data communication between the first terminal and the second terminal; the first request and the second request each include the generated shared temporary information; the first supplementary information is acquired from the shared temporary information in the first request; and the second supplementary information is acquired from the shared temporary information in the second request. 8 . The management system according to claim 1 , wherein: one of the first target and the second target is a user; one terminal corresponding to the user out of the first terminal and the second terminal is a user terminal associated with the user; another of the first target and the second target is a use item to be used by the user; and one terminal corresponding to the use item out of the first terminal and the second terminal is a load terminal to be loaded on the use item. 9 . The management system according to claim 8 , wherein the use item is a mobile body. 10 . The management system according to claim 8 , wherein the user terminal associated with the user is a proxy user terminal possessed by a proxy user who acts as proxy for the user. 11 . The management system according to claim 10 , wherein the use relationship between the first target and the second target occurs through data communication between a target user terminal possessed by the user and the proxy user terminal and data communication between the proxy user terminal and the load terminal. 12 . The management system according to claim 8 , wherein: the user terminal associated with the user is a target user terminal possessed by the user; and the use relationship between the first target and the second target occurs by data communication between the target user terminal an
by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.