Information sharing among mobile apparatus

• US 10,276,039 B2
• Filed: 11/15/2017
• Issued: 04/30/2019
• Est. Priority Date: 01/24/2017
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Furuichi, Sanehiro, Iwasaki, Norie, Tada, Masami, Tashiro, Takahito
• Primary Examiner(s): Aziz, Adnan
• Application Number:
  US15/813,517
• Publication Number:
  US 20180211524A1
• Time in Patent Office: 531 Days
• Field of Search: 340435, 340903, 340905, 701117-119, 701300, 701301
• CPC Class Codes: G01C 21/20 Instruments for performing navigational calculations G01C21/24, G01C21/26 take precedence
• CPC Class Codes: G01C 21/3415 Dynamic re-routing, e.g. recalculating the route when the user deviates from calculated route or after detecting real-time traffic data or accidents
• CPC Class Codes: G01C 21/3691 Retrieval, searching and output of information related to real-time traffic, weather, or environmental conditions arrangements for giving variable traffic instructions G08G1/09
• CPC Class Codes: G08G 1/0112 from the vehicle, e.g. floating car data [FCD]
• CPC Class Codes: G08G 1/0133 for classifying traffic situation
• CPC Class Codes: G08G 1/0141 for traffic information dissemination
• CPC Class Codes: G08G 1/096716 where the received information does not generate an automatic action on the vehicle control
• CPC Class Codes: G08G 1/096775 where the origin of the information is a central station
• CPC Class Codes: G08G 1/096791 where the origin of the information is another vehicle
• CPC Class Codes: G08G 1/162 event-triggered
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Verifying shared event information is provided. Communication with a nearby mobile or immobile apparatus is established to generate an event existence proof in response to encountering the nearby mobile or immobile apparatus. Existence of an incident event is verified in response to arriving at a geographic location of the incident event. A verified incident event is published to add to an incident event distributed ledger for managing incident event information corresponding to the incident event.

Claims

1. A computer-implemented method executed by a mobile apparatus for verifying shared event information, the computer-implemented method comprising:

communicating, by the mobile apparatus, with a nearby mobile or immobile apparatus to generate an event existence proof in response to encountering the nearby mobile or immobile apparatus;

verifying, by the mobile apparatus, existence of an incident event in response to arriving at a geographic location of the incident event; and

publishing, by the mobile apparatus, a verified incident event to add to an incident event distributed ledger for managing incident event information corresponding to the incident event.

2. The computer-implemented method of claim 1, further comprising:

obtaining, by the mobile apparatus, an unverified incident event reported by other mobile apparatus as the incident event, the unverified incident event including information associated with the geographic location of the unverified incident event.

3. The computer-implemented method of claim 2, wherein the event existence proof is added into an event existence proof block of an existence proof distributed ledger after being verified in terms of geographic location consistency with other event existence proofs.

4. The computer-implemented method of claim 2, wherein the verified incident event is added into the incident event distributed ledger after being validated in terms of geographic locations of the mobile apparatus at a time around the verifying of the existence of the incident event.

5. The computer-implemented method of claim 2, further comprising:

initiating, by the mobile apparatus, communication for generating the event existence proof in response to the mobile apparatus obtaining the unverified incident event, the verified incident event including a list of event existence proofs generated during a time period from the obtaining of the unverified incident event to the publishing of the verified incident event.

6. The computer-implemented method of claim 2, wherein the unverified incident event includes event content of the unverified incident event, and wherein the verifying of the existence of the incident event further comprises:

detecting, by the mobile apparatus, a local incident event around the geographic location of the unverified incident event; and

determining, by the mobile apparatus, whether event content of the local incident event matches the event content of the unverified incident event.

7. The computer-implemented method of claim 6, wherein the publishing of the verified incident event is performed in response to determining that the event content of the local incident event matches the event content of the unverified incident event, and further comprising:

reporting, by the mobile apparatus, a state change relating to the incident event as a new unverified incident event via a network in response to determining that the event content of the local incident event does not match the event content reported by the other mobile apparatus or the local incident event failed to be detected around the geographic location.

8. The computer-implemented method of claim 2, wherein the obtaining of the unverified incident report comprises:

subscribing, by the mobile apparatus, a validated incident event relating to a nearby geographic location; and

retrieving, by the mobile apparatus, an unverified event similar to the validated incident event as the unverified incident event.

9. The computer-implemented method of claim 2, wherein the publishing of the verified incident event comprises:

validating, by the mobile apparatus, whether the incident event distributed ledger records valid event existence proofs by referring to an event existence proof distributed ledger; and

adding, by the mobile apparatus, the verified incident event into the incident event distributed ledger in response to determining that the incident event distributed ledger records valid event existence proofs.

10. The computer-implemented method of claim 1, wherein the verifying of the existence of the incident event comprises detecting, by the mobile apparatus, the incident event by using a sensor included in or connected to the mobile apparatus;

and wherein the publishing of the verified incident event comprises;

validating, by the mobile apparatus, whether the incident event distributed ledger records valid event existence proofs by referring to an event existence proof distributed ledger; and

adding, by the mobile apparatus, the verified incident event to the incident event distributed ledger in response to determining that the incident event distributed ledger records valid event existence proofs.