JP2019028549A - Ledger management node, ledger management system, in-vehicle information providing device - Google Patents

Abstract

The present invention provides a technique capable of appropriately proving the occurrence of an event based on a distributed ledger. Each of a plurality of ledger management nodes provided in a ledger management system includes an information determining unit, a recording determining unit, an event determining unit, a ledger recording unit, and a distributed ledger. The distributed ledger records the ledger information including the unique information unique to the previous ledger information generated by any of the plural ledger management nodes and the record information recorded this time. The ledger recording unit records and agrees with the ledger information that is generated by one of a plurality of ledger management nodes and includes the occurrence information that indicates the occurrence of a predetermined event and the unique information unique to the previous ledger information. When the rule is satisfied and the occurrence information satisfies the event agreement rule, the ledger information including the occurrence information is recorded in the distributed ledger. [Selection] Figure 2

Description

  The present disclosure relates to a technique for managing vehicle information acquired from a vehicle using a distributed ledger.

  A technique for transmitting vehicle information acquired by a vehicle based on a predetermined condition from the vehicle to a center is known. In the technique described in Patent Document 1, an external terminal connected to the center inputs vehicle information acquisition conditions acquired by the vehicle to the center. Then, vehicle information acquired by the vehicle based on the acquisition conditions is transmitted from the vehicle to the center, and the vehicle information is transferred from the center to the external terminal that has input the corresponding acquisition conditions.

JP 2006-132368 A

  In some cases, the vehicle information acquired by the vehicle and transmitted to the center may be referred to not only by the external terminal that has input the acquisition conditions but also by other terminals. In this case, the vehicle information transmitted from the vehicle to the center may be recorded and managed by the center in a database, and a plurality of terminals may refer to the center database.

  Then, based on a vehicle information database managed by the center, it is conceivable to prove the occurrence of an event such as an accident. Probing the occurrence of an event is usually done at an authoritative third party or equivalent trusted center.

  However, if vehicle information is managed only by the center, it is difficult to suppress unauthorized rewriting of the vehicle information database managed by the center. If the vehicle information database managed by the center is illegally rewritten, the occurrence of an event such as an accident cannot be properly proved based on the vehicle information database managed by the center.

  In addition to external threats, there is also the possibility of data tampering due to unauthorized operations within the center. If there is a possibility that data will be tampered with in the center, there will remain challenges in terms of transparency and reliability in realizing official certification.

  The present disclosure provides a technique that can properly prove the occurrence of an event based on a distributed ledger.

  One aspect of the present disclosure includes a ledger management system (2, 4) including a plurality of ledger management nodes (10, 410) that are communicably connected to each other, and the plurality of ledger management nodes include the same distributed ledger (30). A ledger management node, which is a distributed ledger, an information determination unit (20, S14, S24), a recording determination unit (22, S14), an event determination unit (24, S24), and a ledger recording unit (26, S14). , S24).

  Another aspect of the present disclosure includes a ledger management system (2, 4) that includes a plurality of ledger management nodes (10, 410) that are communicably connected to each other, and the plurality of ledger management nodes include the same distributed ledger (30). Each of the plurality of ledger management nodes includes a distributed ledger, an information determination unit (20, S14, S24), a recording determination unit (22, S14), an event determination unit (24, S24), Ledger recording unit (26, S14, S24).

  The distributed ledger is generated by any of a plurality of ledger management nodes. The unique information (304) unique to the previous ledger information (300) and the vehicle information acquired from the vehicle as the current record information (306) or Ledger information including occurrence information indicating occurrence of a predetermined event is recorded.

The information determination unit determines whether the record information of the ledger information generated by any of the plurality of ledger management nodes is vehicle information or occurrence information.
When the information determination unit determines that the record information is vehicle information, the record determination unit satisfies the record agreement rule that allows the ledger information to record the ledger information set in the plurality of ledger management nodes in the distributed ledger. It is determined whether or not.

  When the information determination unit determines that the recorded information is occurrence information, the event determination unit determines whether or not the ledger information satisfies the recording agreement rule and whether the predetermined information set in the plurality of ledger management nodes is the occurrence information. It is determined whether or not an event agreement rule indicating that the event has occurred is satisfied.

  The ledger recording unit determines that the record judging unit determines that the ledger information satisfies the recording agreement rule, or if the ledger information satisfies the recording agreement rule and the occurrence information satisfies the event agreement rule. When the determination unit determines, the ledger information is recorded in the distributed ledger, and the record determination unit determines that the ledger information does not satisfy the recording agreement rule, or whether the ledger information does not satisfy the recording agreement rule, or occurrence information If the event determination unit determines that is not at least one of the event agreement rules, the ledger information is not recorded in the distributed ledger.

  According to the above ledger management node and ledger management system, each ledger information constituting the distributed ledger includes unique information unique to the previous ledger information and record information recorded this time. Therefore, when any of the ledger information in the distributed ledger is rewritten, the unique information recorded in the next ledger information is different from the unique information generated from the rewritten ledger information.

Therefore, if the unique information generated from the rewritten ledger information is compared with the unique information recorded in the next ledger information, it can be detected that the ledger information has been rewritten.
In addition, since the ledger information that does not satisfy the recording agreement rule set in the plurality of ledger management nodes is not recorded in the distributed ledger, it is possible to suppress the illegal ledger information that does not satisfy the recording agreement rule from being recorded in the distributed ledger. .

  Furthermore, if the occurrence information of a predetermined event as record information does not satisfy the event agreement rule set in a plurality of ledger management nodes, the ledger information including the occurrence information is not recorded in the distributed ledger. Therefore, it is possible to suppress the ledger information including unauthorized occurrence information that does not satisfy the event agreement rule from being recorded in the distributed ledger.

  In this way, a plurality of ledger management nodes can manage the distributed ledger, detect that the ledger information recorded in the distributed ledger has been illegally rewritten, and suppress the illegal ledger information from being recorded. That is, the occurrence information included in the ledger information recorded in the distributed ledger is reliable information. Further, the plurality of ledger management nodes have the same distributed ledger.

  Therefore, any ledger management node does not require a central organization that manages vehicle information collectively, and a predetermined event occurs based on the occurrence information of a credible event included in the ledger information of the distributed ledger. This can be proved early and appropriately.

  Another aspect of the present disclosure includes a ledger management system (2, 4) that includes a plurality of ledger management nodes (10, 410) that are communicably connected to each other, and the plurality of ledger management nodes include the same distributed ledger (30). In-vehicle information providing apparatus (200) that provides vehicle information to the information management unit (204, S10, S11, S20, S21) and a communication unit (202, S12, S22).

  The distributed ledger includes vehicle information (306) provided by the information providing device and unique information (304) specific to the previous ledger information (300), which is generated by any of a plurality of ledger management nodes, Provided by the information provider that generates the ledger information that satisfies the record agreement rule that allows the ledger information set in the multiple ledger management nodes to be recorded in the distributed ledger, and one of the multiple ledger management nodes The ledger information that includes the occurrence information (306) of the predetermined event generated based on the vehicle information to be performed and the unique information unique to the previous ledger information and satisfies the recording agreement rule, The ledger information satisfying the event agreement rule indicating that a predetermined event set in the ledger management node has occurred is recorded.

The information management unit acquires appropriate vehicle information from the in-vehicle electronic control device (110). The communication unit transmits appropriate vehicle information acquired by the information management unit to the ledger management system.
According to this configuration, since appropriate vehicle information is transmitted from the in-vehicle electronic control device to the ledger management system, appropriate vehicle information is recorded in the distributed ledger.

  Note that the reference numerals in parentheses described in this column and in the claims indicate the correspondence with the specific means described in the embodiment described later as one aspect, and the technical scope of the present disclosure. It is not limited.

The block diagram which shows the ledger management system by 1st Embodiment. The block diagram which shows the structure of a ledger management node. The schematic diagram which shows the structure of a distributed ledger. The block diagram which shows a vehicle-mounted information provision apparatus. The sequence diagram which shows the vehicle initial registration process. The sequence diagram which shows the recording process of vehicle information. The sequence diagram which shows the recording process of the occurrence information of an event. The block diagram which shows the ledger management system by 2nd Embodiment. The block diagram which shows the ledger management node mounted in a vehicle.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[1. First Embodiment]
[1-1. Constitution]
The ledger management system 2 shown in FIG. 1 includes a plurality of ledger management nodes 10 and an electronic certificate authority 40. The ledger management system 2 records and manages vehicle information provided by communication from a plurality of vehicles 100 and event occurrence information generated by any of the plurality of ledger management nodes 10 based on the vehicle information in a distributed ledger. . The plurality of ledger management nodes 10 and the electronic certification authority 40 constitute a peer-to-peer network that is communicably connected to each other.

  Each ledger management node 10 stores a node list in which appropriate ledger management nodes of the ledger management system 2 are registered in a rewritable nonvolatile storage device. In the node list, the IP address and electronic certificate of each ledger management node 10 are registered. In the electronic certificate, the public key and electronic signature of each ledger management node 10 are registered. Registration in the node list is performed offline by a trusted registrant in response to a registration request, or online in the same procedure as the initial vehicle registration described later.

  Further, when the ledger management node 10 does not communicate for a predetermined time or longer in the ledger management system 2 due to a communication failure, a failure of the ledger management node 10, etc., the corresponding ledger management node 10 may be deleted from the node list. Good. When the ledger management node 10 deleted from the node list recovers from a communication failure, a failure of the ledger management node 10, etc., it requests registration to the node list again.

The ledger management node 10 is an apparatus installed in, for example, a vehicle insurance company, a vehicle leasing company, a delivery company, a road management company, a navigation company, a vehicle manufacturing company, and the like.
The ledger management node 10 is configured around a known computer having a CPU and a semiconductor memory such as a RAM, a ROM, and a flash memory. Various functions of the ledger management node 10 are realized by the CPU executing a program stored in a non-transitional physical recording medium. The semiconductor memory corresponds to a non-transitional tangible recording medium that stores a program.

  When the CPU executes the program, a method corresponding to the program is executed. The ledger management node 10 may be composed of one computer or a plurality of computers.

  As illustrated in FIG. 2, the ledger management node 10 includes a communication unit 12, a registration determination unit 14, an occurrence determination unit 16, and an information generation unit 18 as functions configured by the CPU executing a program. , An information determination unit 20, a recording determination unit 22, an event determination unit 24, a ledger recording unit 26, an information reference unit 28, and a distributed ledger 30.

  The method of realizing these functions constituting the ledger management node 10 is not limited to software, and some or all of the elements may be realized using one or a plurality of hardware. For example, when the above function is realized by an electronic circuit that is hardware, the electronic circuit may be realized by a digital circuit including a large number of logic circuits, an analog circuit, or a combination thereof.

  The communication unit 12 communicates with the other ledger management node 10, the electronic certificate authority 40, and the vehicle 100. The registration determination unit 14 transmits a source such as the VIN number transmitted from the vehicle 100 and the telephone number of the vehicle owner when the vehicle 100 that transmits and provides vehicle information to the ledger management system 2 makes an initial registration request. Based on the information, it is determined whether or not it is an initial registration request from the appropriate vehicle 100.

  The occurrence determination unit 16 determines whether or not a predetermined event has occurred based on at least one of vehicle information acquired from the vehicle 100 and record information of the ledger information recorded in the distributed ledger 30. The ledger information, the record information, and the predetermined event will be described later.

  The information generation unit 18 generates ledger information to be recorded in the distributed ledger 30. As shown in FIG. 3, in the ledger information 300, a time stamp 302 when the ledger information is generated, a hash value 304 generated from the previous ledger information 300, and current recording information 306 are recorded. Is done. That is, the database configured by the ledger information 300 shown in FIG. 3 forms a block chain.

  When the occurrence determination unit 16 determines that the predetermined event has not occurred, the information generation unit 18 generates the ledger information 300 using the vehicle information transmitted from the vehicle 100 as the record information 306. When the occurrence determination unit 16 determines that the predetermined event has occurred, the information generation unit 18 includes the vehicle information acquired from the vehicle 100 and the record information 306 of the ledger information 300 recorded in the distributed ledger 30. Based on at least one of them, the ledger information 300 is generated with the occurrence information indicating that a predetermined event has occurred as the record information 306.

  The information determination unit 20 determines whether the record information 306 of the ledger information 300 generated by any of the plurality of ledger management nodes 10 is vehicle information or occurrence information based on the contents of the record information 306.

  In the record determination unit 22, the ledger information that uses the vehicle information generated by the other ledger management node 10 as the record information satisfies the record agreement rule set in advance in the plurality of ledger management nodes 10 constituting the ledger management system 2. It is determined whether or not. POW, PBFT, and the like are known as recording agreement rules. POW is an abbreviation for Proof of Work, and PBFT is an abbreviation for Practical Byzantine Fault Tolerance.

  When the record information included in the ledger information generated by another ledger management node 10 is the above-described occurrence information, the event determination unit 24 determines whether the ledger information satisfies the above-described recording agreement rule. Furthermore, the event determination unit 24 determines whether or not the occurrence information satisfies an event agreement rule indicating that a predetermined event that has been set in advance in the plurality of ledger management nodes 10 has occurred. As an event agreement rule, for example, a rule indicating that an accident or traffic jam has occurred is set.

  The ledger recording unit 26 records the ledger information in the distributed ledger 30 when the record judging unit 22 determines that the ledger information having the vehicle information as the record information satisfies the recording agreement rule. Further, the ledger recording unit 26 determines that the ledger information that uses the generated information generated by the other ledger management node 10 as the record information satisfies the recording agreement rule, and that the generated information satisfies the event agreement rule. If 24 determines, the ledger information is recorded in the distributed ledger 30.

  The information reference unit 28 refers to the ledger information 300 to be used from the distributed ledger 30. When referring to the ledger information 300, the information reference unit 28 compares the hash value generated from the ledger information 300 that is referred to this time with the hash value 304 recorded in the next ledger information 300, and the ledger information that is referred to this time. It is determined whether or not 300 recorded information 306 is appropriate.

  When the electronic certificate authority 40 receives an application for registration of a public key from an appropriate applicant, the electronic certificate authority 40 creates and publishes an electronic certificate for the public key. The electronic certification authority 40 may be a dedicated electronic certification authority 40, or any of the ledger management nodes 10 may also serve as the electronic certification authority 40. A plurality of electronic certificate authorities 40 may exist.

  As shown in FIG. 4, the vehicle 100 includes a plurality of electronic control devices 110 and an information providing device 200. The electronic control device is also referred to as an ECU. Each ECU 110 controls steering, braking, travel torque generation, in-vehicle audio, display, drive recorder, airbag, and the like.

  Each ECU 110 communicates with the information providing apparatus 200 using, for example, a CAN or Ethernet protocol. CAN is an abbreviation for Controller Area Network, and CAN and Ethernet are registered trademarks.

  For communication between each ECU 110 and the information providing apparatus 200, security measures such as encryption of a communication message using a key are taken. Since the security measures as described above are applied to the communication in the vehicle 100, even if an unauthorized ECU is connected to the network of the vehicle 100 and the vehicle information is transmitted, it can be detected that the vehicle information is unauthorized.

  In addition, when the vehicle communicates with the outside such as a smartphone or an Internet line, unauthorized communication from the outside to the vehicle 100 can be suppressed by providing the information management unit 204 described later with a gateway security function.

The information providing apparatus 200 includes a communication unit 202 and an information management unit 204. The communication unit 202 communicates with the ledger management node 10 of the ledger management system 2.
The information management unit 204 acquires from the ECU 110 as vehicle information at least one of environmental information around the vehicle and travel information of the vehicle. The environmental information around the vehicle includes image data captured by a vehicle-mounted camera, image data captured by a drive recorder, detection results by laser radar and millimeter wave radar, and the like.

  The traveling information represents how the vehicle 100 has traveled obtained from detection signals of sensors such as the operation amount of an accelerator pedal, a brake pedal, a steering wheel, and the like operated by the driver, the vehicle speed, and the acceleration. It is a history.

  Further, the information management unit 204 may acquire from the ECU 110 vehicle information such as a usage history indicating how the vehicle 100 has been used and a configuration of software installed in each ECU 110.

  The usage history of the vehicle 100 is, for example, a history indicating that the traveling mode of the vehicle 100 is switched to the automatic operation mode or the manual operation mode, an oil replacement history, a vehicle maintenance inspection history, and the vehicle 100 shared by a plurality of owners. If it is, the information represents the number of owners, the travel distance, and the like.

  The software configuration in the vehicle 100 is, for example, information indicating that in addition to software installed in the vehicle 100, software installed in the vehicle 100 has been updated, new software such as a travel function has been purchased, etc. It is.

  The information management unit 204 generates an electronic signature by encrypting appropriate vehicle information acquired from the ECU 110 with a secret key by the security measures described above, and transmits the electronic signature from the communication unit 202 to the ledger management system 2 together with the vehicle information.

[1-2. processing]
(1) Initial Registration Processing Processing when the vehicle 100 performs initial registration for providing vehicle information to the ledger management system 2 will be described based on the sequence diagram of FIG. Before the first registration, a public key and a secret key for communicating with the ledger management system 2 are set in advance in the information management unit 204 of the vehicle 100.

  In S <b> 1 and S <b> 2, the information management unit 204 transmits the initial registration request, the own vehicle VIN number, and the public key from the communication unit 202 to the specific ledger management node 10. The specific ledger management node 10 is installed, for example, in the information center of the company that manufactured the vehicle 100.

  The line used when the vehicle 100 transmits to the specific ledger management node 10 for the initial registration request is preferably a dedicated line or a line capable of maintaining secrecy such as VPN. VPN is an abbreviation for Virtual Private Network.

  The ledger management node 10 that has received the initial registration request, the VIN number, and the public key from the vehicle 100 becomes an agreement requester that requests other ledger management nodes 10 to agree on the initial registration request. The ledger management node 10, which is the agreement requester, determines whether the initial registration request from the vehicle 100 is appropriate based on the transmission source information such as the VIN number transmitted from the vehicle 100 and the telephone number of the vehicle owner. Determine. In the case of an initial registration request from an inappropriate vehicle 100, the current initial registration request is ignored.

  In the case of an initial registration request from an appropriate vehicle 100, the ledger management node 10 that is an agreement requester generates a hash value from the previous ledger information, and uses this hash value and time stamp as vehicle information for the first time. The registration request, the VIN number, and the public key are added to generate the current ledger information.

  In S3, the ledger management node 10 that is the agreement requester transmits the generated ledger information to the other ledger management node 10 and requests to agree to the initial registration request for the vehicle. The other ledger management node 10 that receives the ledger information becomes an agreement responder to the agreement requester.

  The ledger management node 10 that is the agreement responder that has received the agreement request for the initial registration request determines whether or not the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10. This determination is made based on, for example, whether or not the ledger management node 10 that is the agreement requester is registered in the node list.

  If the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10, the ledger management node 10 that is the agreement responder in S <b> 4 sends the ledger management node 10 that is the agreement requester and the electronic certification authority 40. Responds to an agreement request.

  In S5, when the predetermined number or more of the ledger management nodes 10 agree to the agreement request, the electronic certification authority 40 has completed the creation of the electronic certificate in which the public key and the electronic signature of the vehicle 100 that requested the initial registration are registered. To all the ledger management nodes 10. The electronic certificate authority 40 notifies the URL of the created electronic certificate in the completion notification of the creation of the electronic certificate. URL is an abbreviation for Uniform Resource Locator.

  The ledger management node 10 notified from the electronic certification authority 40 that the creation of the electronic certificate has been completed adds and records the ledger information received from the ledger management node 10 as the agreement requester in S3 to the distributed ledger 30. To do. As a result, the distributed ledger 30 provided in each of the plurality of ledger management nodes 10 is updated synchronously, so that the distributed ledger 30 provided in the plurality of ledger management nodes 10 has the same contents.

  In S6 and S7, the electronic certification authority 40 reports to the vehicle 100 that has requested the initial registration that the public key registration has been completed. The vehicle 100 to which registration of the public key is reported determines that the initial registration for providing vehicle information to the ledger management system 2 has been completed.

In S8, the ledger management node 10 obtains the electronic certificate of the vehicle 100 registered for the first time from the URL notified from the electronic certificate authority 40.
(2) Vehicle Information Recording Process The vehicle information recording process provided to the ledger management system 2 by the vehicle 100 that has completed initial registration will be described based on the sequence diagram of FIG.

  For example, when the vehicle 100 starts traveling, in S10, the information management unit 204 uses the vehicle-mounted ECU 110 as the vehicle information as environment information around the vehicle 100, the traveling information of the vehicle 100, the usage history of the vehicle 100, the usage history of the vehicle 100, and so on. Get software configuration etc.

  If the vehicle 100 that is transmitting vehicle information to the ledger management system 2 is traveling in an underground parking lot, a tunnel, a mountainous area, or the like, and communication with the ledger management system 2 is interrupted, the information management unit 204 temporarily stores vehicle information while communication is interrupted. Then, when communication with the ledger management system 2 is restored, the temporarily stored vehicle information is transmitted to the ledger management system 2.

  In S11 and S12, the information management unit 204 sends an agreement request from the communication unit 202 to the ledger management system 2 for the acquired vehicle information, an electronic signature obtained by encrypting a hash value generated from the vehicle information with a secret key, time, and the like. To a specific ledger management node 10 such as a vehicle insurance company. The line used in S11 and S12 may be a general-purpose line such as an Internet line instead of a dedicated line or VPN as in the above-described initial registration request.

  The ledger management node 10 that is the consensus requester who has received the vehicle information from the vehicle 100 matches the hash value generated from the vehicle information by the hash function and the hash value that is decrypted from the electronic signature by the public key of the corresponding vehicle 100. If so, it is determined that the request is an appropriate vehicle information recording request from the vehicle 100.

  In the case of a vehicle information recording request from an appropriate vehicle 100, the ledger management node 10 that is an agreement requester records the vehicle information acquired from the vehicle 100 this time or the vehicle information acquired this time from the vehicle 100 and the distributed ledger 30. Based on the recorded record information of the ledger information, it is determined based on the event agreement rule whether, for example, an accident or traffic jam has occurred as a predetermined event.

The following is an example of an event agreement rule that indicates the occurrence of an accident.
-The vehicle airbag has been activated.
・ It was determined that an accident occurred by analyzing the images captured by the drive recorder.

・ The acceleration sensor value exceeds the specified value.
・ Multiple vehicles are stopped at the same point on the road at the same time.
The following is an example of an event agreement rule that indicates the occurrence of traffic congestion.

When the vehicle speed of a plurality of vehicles traveling in the same direction on a road in the same direction is a low speed of, for example, 10 km / h or less within a predetermined time.
・ Accidents and road construction have occurred due to analysis of image data captured by the drive recorder.

The event recording process when a preset event occurs will be described later with reference to FIG.
If a preset event has not occurred, the ledger management node 10 as the agreement requester generates a hash value from the previous ledger information, and sets this hash value, time stamp, and ledger information. Vehicle information received from the vehicle 100 as record information and a record request for vehicle information are generated as ledger information. In S13, the ledger management node 10 that is the agreement requester transmits the generated ledger information to the other ledger management node 10 and requests an agreement for recording the vehicle information in the distributed ledger 30.

  The ledger management node 10 that is the consensus responder who has received the agreement request for vehicle information recording determines whether or not the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10. This determination is made based on, for example, whether or not the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10 registered in the node list.

  If the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10 registered in the node list, the ledger management node 10 that is the agreement responder in S14 is connected to the ledger management node 10 that is the agreement requester. It responds to the ledger management node 10, which is another consensus responder, to agree on a consensus request for vehicle information recording.

  If the ledger management node 10 that is the agreement requester is not the appropriate ledger management node 10 registered in the node list, the ledger management node 10 that is the agreement responder in S14 is connected to the ledger management node 10 that is the agreement requester. It responds to the ledger management node 10 which is another agreement responder that it does not agree with the agreement request | requirement of vehicle information recording.

  In S14, each ledger management node 10 is an agreement requester this time when a predetermined number or more of the ledger management nodes 10 agree to a vehicle information record agreement request as a record agreement rule set in the plurality of ledger management nodes 10. The ledger information generated by the ledger management node 10 is added to the distributed ledger 30 and recorded. As a result, the distributed ledger 30 provided in each of the plurality of ledger management nodes 10 is updated synchronously, so that the distributed ledger 30 provided in the plurality of ledger management nodes 10 has the same contents.

  In S14, each ledger management node 10 does not record the ledger information generated by the ledger management node 10 that is the requester of the agreement in the distributed ledger 30 when only a less than a predetermined number of the ledger management nodes 10 agree with the agreement request for vehicle information recording. . In this case, the distributed ledger 30 is not updated.

(3) Event recording process The event recording process for recording the event occurrence information generated by the ledger management node 10 in the distributed ledger based on the vehicle information provided by the vehicle 100 to the ledger management system 2 is shown in the sequence diagram of FIG. This will be explained based on.

The processes in S20 to S22 in FIG. 7 are substantially the same as the processes in S10 to S12 in FIG.
The ledger management node 10 that is the consensus requester who has received the vehicle information from the vehicle 100 in S22 has the hash value generated from the vehicle information by the hash function and the hash value decrypted from the electronic signature by the public key of the corresponding vehicle 100. If they match, it is determined that the request is a proper vehicle information recording request from the vehicle 100.

  In the case of a request for recording vehicle information from an appropriate vehicle 100, the ledger management node 10 that is an agreement requester, for example, an accident or traffic jam occurs as a preset event based on the vehicle information received from the vehicle. Is determined based on the event agreement rule described in FIG.

  The ledger management node 10 that is the agreement requester determines whether or not a preset event has occurred based on the vehicle information received from the vehicle 100 and the record information already recorded in the distributed ledger 30 this time. You may determine based on an agreement rule.

The vehicle information recording process when a preset event has not occurred has been described above with reference to FIG.
When a preset event has occurred, the ledger management node 10 as the agreement requester generates a hash value from the previous ledger information, and the hash value, time stamp, and recorded event information Generate occurrence information and event record consensus request.

  In S23, the ledger management node 10 that is the agreement requester transmits the generated ledger information to the other ledger management node 10 and requests an agreement for recording the occurrence information of the event in the distributed ledger 30.

  In the event occurrence information, for example, the occurrence of a predetermined event and vehicle information indicating that the predetermined event has occurred are set. The vehicle information set in the occurrence information may be vehicle information provided by one vehicle 100, or may be vehicle information provided by a plurality of vehicles 100.

  The ledger management node 10 that is an agreement responder that has received the event record agreement request determines whether or not the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10. This determination is made based on, for example, whether or not the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10 registered in the node list.

  If the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10 registered in the node list, the ledger management node 10 that is the agreement responder further determines that the occurrence information included in the ledger information is the event described above. Determine whether agreement rules are met.

  When the ledger management node 10 that is the agreement requester is an appropriate ledger management node 10 and the occurrence information included in the ledger information satisfies the event agreement rule described above, the ledger management node 10 that is the agreement responder in S24 Then, the ledger management node 10 that is the agreement requester and the ledger management node 10 that is the other agreement responder respond that they agree to the event record agreement request.

  If at least one of the ledger management node 10 that is the agreement requester is not an appropriate ledger management node 10 registered in the node list or the occurrence information included in the ledger information does not satisfy the event agreement rule, In S24, the ledger management node 10 that is the agreement responder responds to the ledger management node 10 that is the agreement requester and the ledger management node 10 that is the other agreement responder that it does not agree to the event record agreement request.

  In S24, each of the ledger management nodes 10 generates, as a record agreement rule set in advance, when a predetermined number or more of the ledger management nodes 10 agree to an event record agreement request, the ledger management node 10 that is the agreement requester generates this time. The ledger information is added to the distributed ledger 30 and recorded. As a result, the distributed ledger 30 provided in each of the plurality of ledger management nodes 10 is updated synchronously, so that the distributed ledger 30 provided in the plurality of ledger management nodes 10 has the same contents.

  In S24, each ledger management node 10 does not record the ledger information generated by the ledger management node 10 that is the requester of the agreement in the distributed ledger 30 when less than a predetermined number of ledger management nodes 10 agree to the event record agreement request. In this case, the distributed ledger 30 is not updated.

[1-3. effect]
In the first embodiment described above, the following effects can be obtained.
(1a) The vehicle information provided from the vehicle 100 to the ledger management system 2 is recorded in the distributed ledger by the agreement of a plurality of ledger management nodes 10 as ledger information including a hash value of the previous ledger information. As a result, even if an unauthorized vehicle impersonating a registered vehicle providing vehicle information provides vehicle information to the ledger management system 2, no agreement can be obtained, so that unauthorized vehicle information is prevented from being recorded in the distributed ledger. it can.

  Even if an unauthorized third party tries to rewrite the ledger information of the distributed ledger, it is necessary to calculate hash values set in all the ledger information that follows the ledger information to be rewritten. In order for a person to rewrite the ledger information of the distributed ledger, a large processing load is required. Therefore, it is virtually impossible for an unauthorized third party to rewrite the ledger information of the distributed ledger.

  (1b) Since it is ensured that the ledger information recorded in the distributed ledger is appropriate and trustworthy, for example, if it is a vehicle insurance company, using the ledger information, a vehicle that tends to drive dangerously. Appropriate premiums can be set, such as raising premiums and lowering premiums for vehicles that tend to drive safely.

Furthermore, since the driving characteristics for each vehicle can be acquired from the ledger information as vehicle information, the insurance premium for each vehicle can be calculated in more detail in addition to the accident history and the vehicle year.
Further, if the company distributes software to vehicles, it can charge the vehicle using the software by confirming that the distributed software is used from the ledger information recorded in the distributed ledger.

Further, since a used car sales company can determine how a vehicle has been used from a distributed ledger without unauthorized rewriting, an appropriate selling price can be set for a used car.
(1c) Since occurrence information such as an accident or a traffic jam that satisfies both the record agreement rule and the event agreement rule is recorded as record information in the distributed ledger 30 as a predetermined event, the occurrence recorded in the distributed ledger 30 Based on the information, any ledger management node 10 can prove early and appropriately that an accident or traffic jam has occurred without requiring a central organization that collectively manages vehicle information.

  For example, if the event that occurred is an accident, the vehicle insurance company that is the ledger management node 10 refers to the distributed ledger 30 to generate the accident occurrence time and the position, vehicle speed, acceleration, etc. of each vehicle 100 immediately before that. It is acquired as information, and the driving behavior of the vehicle 100 traveling at the accident occurrence point can be grasped. Then, by reproducing the travel of each vehicle 100 at the time of the occurrence of the accident from the driving behavior of each vehicle 100, it is possible to calculate the negligence ratio of each vehicle 100 as compared with the case at the past accident occurrence point.

  In addition, if the event that has occurred is a traffic jam, the courier company that is the ledger management node 10 refers to the occurrence location of the traffic jam that occurs by referring to the distributed ledger 30 that the delivery vehicle is delayed due to the traffic jam. You can sign and contact the delivery address based on the time.

  Further, if the event that occurred is a traffic jam, the company that is the ledger management node 10 refers to the distributed ledger 30 to acquire that the reason that the employee of the car commute was late was due to an unexpected traffic jam. It can be determined based on the occurrence point and the occurrence time.

  Also, if the event that occurred is a traffic jam, the road management company and the navigation company that are the ledger management node 10 refer to the distributed ledger 30 even in road sections where there are no roadside devices that detect the traffic volume. The traffic jam information can be provided to the vehicle based on the traffic jam occurrence point and the occurrence time.

In the first embodiment described above, the hash value 304 of the previous ledger information 300 generated by the information generating unit 18 corresponds to unique information unique to the ledger information.
S10, S11, S20, and S21 correspond to processing of the information management unit, S12 and S22 correspond to processing of the communication unit, S13 and S23 correspond to processing of the occurrence determination unit and the information generation unit, and S14, S24 corresponds to the processing of the information determination unit and the ledger recording unit, S14 corresponds to the processing of the recording determination unit, and S24 corresponds to the processing of the event determination unit.

[2. Second Embodiment]
[2-1. Difference from the first embodiment]
As shown in FIG. 8, the second embodiment is different from the first embodiment in that a plurality of vehicles 400 are registered in the node list as a ledger management node of the ledger management system 4. Note that the same reference numerals as those in the first embodiment indicate the same configuration, and the preceding description is referred to.

  As shown in FIG. 9, the vehicle 400 is equipped with a ledger management node 410 that combines the configurations of the ledger management node 10 of the first embodiment and the information providing device 200 of the vehicle 100. The ledger management node 410 includes a registration determination unit 14, an occurrence determination unit 16, an information generation unit 18, an information determination unit 20, a record determination unit 22, an event determination unit 24, a ledger recording unit 26, and an information reference unit. 28, a distributed ledger 30, an information management unit 204, and a communication unit 412.

  The communication unit 412 communicates with the ledger management node 10, the ledger management node 410 of the other vehicle 400 registered as the ledger management node of the ledger management system 4, and the other vehicles 100 not registered as the ledger management node. .

[2-2. processing]
The vehicle 400 includes a node registration request for registering as a ledger management node in the node list of the ledger management system 4, and an initial registration request described in the first embodiment for providing vehicle information to the ledger management system 4. Do it yourself. When the node registration and the initial registration are completed, an agreement request for vehicle information recording and an agreement request for event recording when providing vehicle information are executed as an agreement requester.

[2-3. effect]
In the second embodiment, in addition to the effects (1a), (1b), and (1C) of the first embodiment, the following effects can be obtained.

  (2a) By registering a plurality of vehicles as a ledger management node of the ledger management system 4, each vehicle can realize an appropriate travel while exchanging vehicle information that can be used safely with other vehicles.

  For example, when the in-vehicle ledger management node 410 determines from the vehicle information provided by the vehicle 100 that an accident or traffic jam has occurred, the in-vehicle travel route setting device that sets the travel route of the vehicle has an accident or traffic jam. It is possible to set a travel route that avoids the point where it occurs.

[3. Other Embodiments]
(1) In the above embodiment, the ledger management node 10 is based on the vehicle information acquired this time from the vehicle 100 or the vehicle information acquired this time from the vehicle 100 and the record information of the ledger information recorded in the distributed ledger 30. Whether or not a predetermined event occurred was determined based on the event agreement rule.

  On the other hand, the ledger management node 10 that is the agreement requester searches the distributed ledger 30 at predetermined time intervals, for example, and a predetermined event occurs based on the vehicle information recorded as recorded information in the distributed ledger 30. It may be determined based on the event agreement rule.

  (2) In the above embodiment, an accident and a traffic jam are taken as examples of the predetermined event. In addition to this, based on the vehicle information indicating that the wiper of the vehicle is operating continuously, it is raining as an event and the point, the weather forecasting company that is the ledger management node 10, etc. May report.

  (3) In the above embodiment, the information generation unit 18 generates the hash value 304 from the previous ledger information 300 as unique information unique to the previous ledger information 300. On the other hand, the unique information unique to the previous ledger information is not limited to the hash value, but is unique to the previous ledger information. Any value may be generated.

  (4) The distributed ledger 30 described in the above embodiment is not limited to the block chain. The distributed ledger includes, as ledger information, specific information unique to the previous ledger information generated from the previous ledger information by any of the plural ledger management nodes and the current vehicle information provided from the vehicle. If the ledger information generated by any of the multiple ledger management nodes satisfies the agreement rule set in the multiple ledger management nodes and is recorded in the distributed ledger, what kind of agreement rule The distributed ledger managed based on may be sufficient.

  (5) A plurality of functions of one constituent element in the above embodiment may be realized by a plurality of constituent elements, or a single function of one constituent element may be realized by a plurality of constituent elements. In addition, a plurality of functions possessed by a plurality of constituent elements may be realized by one constituent element, or a single function realized by a plurality of constituent elements may be realized by one constituent element. Moreover, you may abbreviate | omit a part of structure of the said embodiment. In addition, at least a part of the configuration of the above embodiment may be added to or replaced with the configuration of the other embodiment. In addition, all the aspects contained in the technical thought specified only by the wording described in the claim are embodiment of this indication.

  (6) In addition to the ledger management nodes 10 and 410 described above, a ledger management system 2 and 4 having the ledger management nodes 10 and 410 as constituent elements, and a ledger management program for causing a computer to function as the ledger management nodes 10 and 410 The present disclosure can also be realized in various forms such as a recording medium recording the ledger management program and a ledger management method.

  In addition to the information providing apparatus 200 described above, the present disclosure is realized in various forms such as an information providing program for causing a computer to function as the information providing apparatus 200, a recording medium on which the information providing program is recorded, and an information providing method. You can also

2, 4: Ledger management system, 10, 410: Ledger management node, 12: Communication unit, 14: Registration determination unit, 16: Occurrence determination unit, 18: Information generation unit, 20: Information determination unit, 22: Recording determination unit 24: event determination unit, 26: ledger recording unit, 28: information reference unit, 30: distributed ledger, 100, 400: vehicle, 200: information providing device, 202, 412: communication unit, 204: information management unit, 300 : Ledger information 304: Hash value (unique information) 306: Record information

Claims (9)

A ledger management node of a ledger management system (2, 4) comprising a plurality of ledger management nodes (10, 410) connected to be communicable with each other, wherein the plurality of ledger management nodes comprise the same distributed ledger (30). ,
Specific information (304) unique to the previous ledger information (300) generated by one of the plurality of ledger management nodes and vehicle information or predetermined event acquired from the vehicle as the current record information (306) A distributed ledger configured to record the ledger information including:
An information determination unit (20, S14, S24) configured to determine whether the record information of the ledger information generated by any of the plurality of ledger management nodes is the vehicle information or the generated information. When,
When the information determination unit determines that the record information is the vehicle information, a record agreement rule that permits the ledger information to record the ledger information set in the plurality of ledger management nodes in the distributed ledger. A record determination unit (22, S14) configured to determine whether or not the condition is satisfied;
When the information determination unit determines that the recorded information is the generated information, whether or not the ledger information satisfies the recording agreement rule, and the generated information is set in the plurality of ledger management nodes. An event determination unit (24, S24) configured to determine whether or not an event agreement rule indicating that an event has occurred is satisfied,
The record determination unit determines that the ledger information satisfies the recording agreement rule, or the ledger information satisfies the recording agreement rule, and the occurrence information satisfies the event agreement rule If the event determining unit determines that the record information is recorded in the distributed ledger, the record determining unit determines that the ledger information does not satisfy the recording agreement rule, or the ledger information is If the event determination unit determines that the recording agreement rule is not satisfied or the occurrence information does not satisfy the event agreement rule, the ledger information is not recorded in the distributed ledger. A ledger recording unit (26, S14, S24) configured as described above,
Comprising
Ledger management node. The ledger management node according to claim 1,
The predetermined event is at least one of an accident and a traffic jam.
Ledger management node. The ledger management node according to claim 1 or 2,
The vehicle information is configured to include at least one of environmental information around the vehicle acquired from the vehicle and travel information of the vehicle.
Ledger management node. The ledger management node according to any one of claims 1 to 3,
Whether the predetermined event satisfying the event agreement rule has occurred based on at least one of the vehicle information acquired from the vehicle and the recorded information of the ledger information recorded in the distributed ledger An occurrence determination unit (16, S13, S23) configured to determine
When the generation unit determines that the predetermined event has occurred, the ledger information including the generation information is generated, and when the generation unit determines that the predetermined event has not occurred, the vehicle information is An information generation unit (18, S13, S23) configured to generate the ledger information including;
A ledger management node further comprising: The ledger management node according to any one of claims 1 to 4,
When referring to the ledger information recorded in the distributed ledger, whether or not the ledger information to be referred to this time is appropriate based on the ledger information to be referred to this time and the unique information of the next ledger information. Further comprising an information reference (28) configured to determine
Ledger management node. The ledger management node according to any one of claims 1 to 5,
The ledger management node is mounted on the vehicle,
An information management unit (204, S10, S11, S20, S21) configured to acquire appropriate vehicle information from an electronic control device (110) mounted on the vehicle;
A communication unit (202, S12, S22) configured to transmit the appropriate vehicle information acquired by the information management unit to the ledger management system;
A ledger management node further comprising: A ledger management system (2, 4) comprising a plurality of ledger management nodes (10, 410) connected to be communicable with each other, wherein the plurality of ledger management nodes comprise the same distributed ledger (30);
Each of the plurality of ledger management nodes is
Specific information (304) unique to the previous ledger information (300) generated by one of the plurality of ledger management nodes and vehicle information or predetermined event acquired from the vehicle as the current record information (306) A distributed ledger configured to record the ledger information including:
An information determination unit (20, S14, S24) configured to determine whether the record information of the ledger information generated by any of the plurality of ledger management nodes is the vehicle information or the generated information. When,
When the information determination unit determines that the record information is the vehicle information, a record agreement rule that permits the ledger information to record the ledger information set in the plurality of ledger management nodes in the distributed ledger. A record determination unit (22, S14) configured to determine whether or not the condition is satisfied;
When the information determination unit determines that the recorded information is the generated information, whether or not the ledger information satisfies the recording agreement rule, and the generated information is set in the plurality of ledger management nodes. An event determination unit (24, S24) configured to determine whether or not an event agreement rule indicating that an event has occurred is satisfied,
The record determination unit determines that the ledger information satisfies the recording agreement rule, or the ledger information satisfies the recording agreement rule, and the occurrence information satisfies the event agreement rule If the event determining unit determines that the record information is recorded in the distributed ledger, the record determining unit determines that the ledger information does not satisfy the recording agreement rule, or the ledger information is If the event determination unit determines that the recording agreement rule is not satisfied or the occurrence information does not satisfy the event agreement rule, the ledger information is not recorded in the distributed ledger. A ledger recording unit (26, S14, S24) configured as described above,
Comprising
Ledger management system. An in-vehicle system that includes a plurality of ledger management nodes (10, 410) that are communicably connected to each other, and that provides the vehicle information to a ledger management system (2, 4) that includes the same distributed ledger (30). Information providing device (200),
In the distributed ledger, vehicle information (306) provided by the information providing device and unique information (304) specific to the previous ledger information (300) generated by any of the plurality of ledger management nodes Any of the ledger information satisfying a record agreement rule that allows the ledger information set in the plurality of ledger management nodes to be recorded in the distributed ledger, and any of the plurality of ledger management nodes And generating the predetermined event occurrence information (306) generated based on the vehicle information provided by the information providing device and the unique information specific to the previous ledger information, and satisfying the recording agreement rule The ledger information, wherein the occurrence information satisfies an event agreement rule indicating that the predetermined event set in the plurality of ledger management nodes has occurred Ledger information is recorded,
An information management unit (204, S10, S11, S20, S21) configured to acquire appropriate vehicle information from the on-vehicle electronic control device (110);
A communication unit (202, S12, S22) configured to transmit the appropriate vehicle information acquired by the information management unit to the ledger management system;
An on-vehicle information providing apparatus comprising: The in-vehicle information providing apparatus according to claim 8,
The information management unit is configured to acquire the vehicle information including at least one of environmental information around the vehicle acquired from the vehicle and travel information of the vehicle.
In-vehicle information providing device.

Images