WO2020116894A1

WO2020116894A1 - Vehicle information management system using blockchain

Info

Publication number: WO2020116894A1
Application number: PCT/KR2019/016918
Authority: WO
Inventors: 윤여표
Original assignee: 윤여표
Priority date: 2018-12-06
Filing date: 2019-12-03
Publication date: 2020-06-11
Also published as: KR102086684B1

Abstract

The present invention relates to a vehicle information management system using a blockchain, wherein information delivered from an information supplier that supplies information for state determination is generated and delivered through a blockchain, and thus the information for state determination may be prevented from being maliciously manipulated. The vehicle information management system using a blockchain according to the present invention includes: a company server which collects vehicle-related information that is information about an event that has occurred in relation to a vehicle, a vehicle owner, or a vehicle driver, and writes the collected vehicle-related information as a transaction of the blockchain to generate a block; a user terminal which generates vehicle-related information that is different from information generated in the company server from among the vehicle-related information, and writes the generated information to the block; and a management server which receives the block from the company server, applies the vehicle-related information recorded in the block to a reference value and an algorithm to generate an index for each piece of vehicle information, uses the index to calculate a score representing the state of the vehicle as a number, and writes the calculated index or score to an index/score block.

Description

Vehicle information management system using blockchain

The present invention relates to a vehicle information management system using a blockchain, and in particular, by generating and delivering information transmitted from an information provider providing information for state determination through a blockchain, information for state determination is maliciously manipulated It relates to a vehicle information management system using a blockchain so as to prevent it.

Cars are convenient for the general public to use, but the manufacturing technology is complicated, so it is difficult to make them without an expert, and it is almost impossible to repair them in the event of a breakdown or accident. In the process of manufacturing automobiles, managers with the best inspection systems and engineering capabilities can monitor the operation of inspection systems, minimizing the shipping of problematic products.

However, while the car is being delivered and operated by the user, the user must check the vehicle's condition and take action when a problem occurs. When a vehicle needs to be repaired due to a malfunction or accident occurring while the vehicle is running, the general driver does not need to worry about the vehicle being repaired. There are numerous vehicle repair shops in the vicinity and vehicle repair specialists in the vehicle repair shop. This is because repairs can be made simply by asking the customer.

There are various types of ownership of automobiles, and they can be classified into ownership types for the purpose of passenger use, passenger transportation, and goods transportation in ordinary homes. Cars owned by individuals and used as a means of transportation for themselves and their families are generally shorter in driving distance and driving time than cars used in transportation, and driving roads are more often paved roads than unpaved roads. will be. It can be easily predicted that driving on unpaved roads is one of the factors that shorten the life of the vehicle compared to those on pavement.

It is common for ordinary people who do not have expertise in automobiles to base the life of the vehicle on the mileage, but there is no problem in determining the life of the vehicle based on the mileage of the vehicle. However, even in the case of a vehicle of the same type, the life of the vehicle will be different depending on the driving time, driving conditions, and the propensity of the driver. It will be easy to predict what will be reduced.

Although the aging of taxi drivers, which is a recent problem, can be adjusted by law, in order to prevent accidents due to vehicle aging and deterioration of vehicle functions, it is necessary to be able to check the status of vehicles currently driving on the road.

In addition, the information confirming the state of the vehicle may be related to the profits generated by the vehicle, such as a vehicle owner or a manufacturing company, and if it is discriminated against them, a malicious change may occur.

Accordingly, the present invention is to solve the above problems, and collects and processes vehicle manufacturing information at the time of manufacture, fluctuation information of a running vehicle, and driving information of a vehicle to determine the overall condition of the vehicle in use and determines it. It is to provide a vehicle information management system using a blockchain for self-identification.

In addition, another object of the present invention is to create information that determines the overall condition of the vehicle as a block in the blockchain, so that it can be shared with others, and accumulates and manages issues generated in the vehicle through blocks to ensure accurate and reliable operation. It is to provide a vehicle information management system using a blockchain that can manage vehicle information.

In addition, another object of the present invention is to create and transmit information transmitted from an information provider that provides information for state determination through a blockchain, so that one block can be prevented from malicious manipulation of information for state determination It is to provide a vehicle information management system using a chain.

The vehicle information management system using the blockchain according to the present invention collects vehicle-related information, which is information on an event related to a vehicle, a vehicle owner, and a vehicle operator, and writes the defensive vehicle-related information as a transaction of the blockchain A company server generating blocks; A user terminal that generates vehicle-related information different from information generated by the company server among the vehicle-related information and writes it in the block; And receiving the block from the company server, applying the vehicle-related information recorded in the block to a reference value and an algorithm to generate an index for each vehicle information, and using the index to calculate a score representing the state of the vehicle as a numerical value. , A management server that records the calculated index or score in the index/score block.

Therefore, the vehicle information management system using the blockchain according to the present invention collects and processes vehicle manufacturing information at the time of manufacture, fluctuation information of a running vehicle, and driving information of a vehicle to determine a comprehensive state of a vehicle in use and provides it. It is possible to make it possible for three parties to confirm.

In addition, the vehicle information management system using the block chain according to the present invention enables information to be judged as a block of the blockchain to be shared with others by generating information that determines the overall condition of the vehicle, and accumulates issues generated in the vehicle through blocks. This enables accurate and reliable vehicle information management.

In addition, the vehicle information management system using the blockchain according to the present invention generates and transmits information transmitted from an information provider that provides information for state determination through the blockchain, so that information for state determination is maliciously manipulated It is possible to prevent.

1 is an exemplary view showing the configuration of a vehicle information management system using a blockchain according to the present invention.

Figure 2 is an exemplary view for explaining the company server of the vehicle information management system using a blockchain.

Figure 3 is an exemplary view for explaining a vehicle information management method using a blockchain.

Hereinafter, with reference to the accompanying drawings, an embodiment of the present invention will be described so that those skilled in the art can easily carry out. It should be noted that, in the accompanying drawings, the same reference number is used when the same number is indicated in the other drawings. In addition, in the description of the present invention, when it is determined that a detailed description of a related known function or known configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, certain features shown in the drawings are enlarged or reduced or simplified for ease of description, and the drawings and their components are not necessarily drawn to scale. However, those skilled in the art will readily understand these details.

1, a vehicle information management system using a blockchain according to the present invention includes a management server 110, a company server 111, and a user terminal 160, and the user terminal 160 is a vehicle terminal It may be divided into (160a) RHK third-party terminal (160b).

The management server 110 serves to receive various information related to a vehicle from the company server 111 and to index and score the received information. In particular, the management server 110 serves to generate information such as scores, indices, part (or all) of collected information, and rules used in calculating scores/indexes as blocks, and to propagate the generated blocks to nodes. do. Here, the nodes of the blockchain are basically the management server 110, the user terminal 160, and the vendor server 111, and may include any devices existing in the network separately. However, the management server 110 may configure a private blockchain including only the company server 111 and the user terminal 160, in which case, the management server 110 may approve the device or server participating in the private blockchain. You can do In particular, the management server 110 of the present invention, in addition to the private blockchain, in which only members are involved, may also allow a node for arbitrary verification to be made, and the description will be further described below.

The management server 110 receives and collects vehicle-related information from the company server 111 or the user terminal 160, indexes the collected vehicle-related information, and synthesizes and indexes the indexed information. To this end, the management server 110 stores information such as algorithms, reference values, and depreciation for index calculation and score calculation of collected vehicle-related information.

As an example, the index may be set to 100 points when the parts are shipped out of the vehicle, and the rate at which these parts are reflected in the vehicle score may be set at 10%. In addition, depreciation due to aging may be selected as 0.01%/1000km for each mileage and used for index and score calculation. These examples are used for convenience of description and do not limit the present invention.

The management server 110 may generate blocks and propagate the collected information used for calculating the index, the score information and the algorithm or judgment criteria used for calculating the index and the score, the index or the score as a block. In addition, it is possible to configure the blockchain by adding collected information or calculated information to the block whenever the information needs to be updated. Verification of this information has been released through blockchain technology, and detailed description thereof will be omitted. In this process, the management server 110 may request each node to preferentially propagate the block to member nodes among the nodes of the blockchain.

In order to receive this information from the company server 111 or the user terminal 160, the management server 110 receives the information generated by the block of the blockchain from the company server 111 or the user terminal 160.

More specifically, the company server 111 is a server of a maintenance company that performs maintenance of a specific vehicle, and there may be a case in which it is desired to transmit a maintenance performance history. In order to deliver this, the server of the maintenance company may generate a block that deals with items such as a maintenance performance history, cost required for maintenance, and a maintenance date as a transaction and deliver it to the supplier server 111. In addition, the management server 110 can generate an index and a score based on the information contained in the block, and generate a new block to generate a block in which the index and score changed by the maintenance history and the maintenance history are calculated. In this case, for one vehicle, one blockchain is formed to record the index and score. Here, this one blockchain is a base block, and when vehicle-related information is transmitted through a separate blockchain, one or more family blockchains for recording and transmitting vehicle-related information may be formed. This will be described in more detail below.

Alternatively, the management server 110 may be in charge of transaction delivery so that the contents of the blockchain delivered by the vendor server 111 are included in the blocks of other blockchains. That is, the company server 111 may generate a block related to the maintenance history of the vehicle or record maintenance information to be recorded in a block of the existing maintenance history blockchain and transmit it to the management server 110. The management server queries the block in which this maintenance information is recorded, and reads the maintenance history recorded in the transaction of the block, and records it in the comprehensive information of the vehicle, that is, the block in which the index and score are recorded. In particular, at this time, the maintenance information obtained from the maintenance history block may be recorded together, or only a score reflecting the index and the index calculated by the maintenance history may be written in the block representing the overall information of the vehicle to generate a new block. In other words, in this case, various blockchains such as maintenance and accidents are formed for one vehicle, and among them, the blockchain corresponding to the overall vehicle information is a score/index blockchain created based on information contained in another blockchain. Is formed.

Here, the delivery of the public key and the private key is exchanged between the transaction parties of the blockchain, that is, the sender and the receiver who transmit the information, and is based on the technology disclosed by the blockchain technology, and detailed description thereof will be omitted. . In addition, detailed description of verification by the nodes of the blockchain will be omitted.

In particular, the management server 110 stores the transaction ID (TXID) or public key used in the generation of the block to match the user's information or vehicle information for management of such information, block generation and update. For example, when the user participates in the management system 100 through the user terminal 160, and a block for this user's vehicle is generated, an ID for a block transaction is generated. The transaction ID (TXID) or public key is stored in correspondence with the information of the user registered in the management server 110, and is managed by matching the user and the member who generated the transaction or block. Then, when the user wants to access the block information through the user terminal 160, or to update the contents of the block, the information is authenticated and searched using only one of the user information or the transaction ID (TXID) or public key matched thereto. To enable access and use.

To this end, the management server 110 may be connected to the TXID management server 185 to perform transaction ID management.

Through this, users who want to check the information of the vehicle can obtain the information by checking the transaction of the block through their respective user terminal 110, and the management server 110 can use this as data for determining the stability of the vehicle. It becomes possible.

The company server 111 serves to generate and transmit vehicle-related information. The company server 111 is composed of servers provided in various companies or public institutions related to vehicles such as maintenance, repair, and insurance.

The company server 111 serves to generate information about actions applied to a vehicle by a company or an agency and to transmit it to the management server 110. This will be described in more detail with reference to other drawings below.

The information generated in the company server 111 is described in the block and transmitted to the management server 110. That is, it is possible to prevent intentional manipulation or change of information by a block at the time of occurrence of the information, and transmit it to the management server 110. At this time, the block in which information is written by the vendor server 111 may be a block recorded only for a specific action as described above, or a block in which comprehensive information of a vehicle is recorded.

These blocks may be requested separately from other nodes or may not need to be generated because the vendor server 111 participates as a node. That is, after the company server 111 participates as a node for verification of the previously generated block, it records new information in the retained block and generates it as a block connected to the existing blockchain, and can transmit it to the management server 110 have.

The user terminal 160 serves to collect or generate and transmit vehicle-related information similar to the company server 111, and a vehicle-related information block of a blockchain including vehicle-related information or a block chain generated by scoring and indexing it. Refers to an object that identifies and collects information needed by the comprehensive information block. Here, as described above, the vehicle-related information and the scored blockchain may consist of one blockchain and be described as divided into each block, or by configuring them as separate chains, the information of one blockchain in the management server may be different. It can also be written in the block of the blockchain, and in the following description, it is assumed that it applies to all of them when there is no distinction.

More specifically, the user terminal 160 may include a vehicle terminal 160a installed in the vehicle and a third party terminal 160b that generates other information using vehicle-related information. Here, the terminal device of the user who owns the vehicle may be included in the third party terminal 160b. In the case of the owner, the profit according to the score of the vehicle may be distorted when the information is recorded by the owner due to the increase or decrease. Therefore, the terminal that can reflect the will of the owner is included in the third-party terminal 160b that can be reprocessed by receiving the score and the index, and the vehicle-related information is associated with the vehicle terminal 160a installed in the vehicle, that is, the trip computer. It can be the same device. However, the terminal used by the owner may be used as a role of providing a communication path for the vehicle terminal 160a having no communication means with the outside.

Here, the vehicle terminal 160a may be a device that is installed in a vehicle and collects driving information and sensing information of the vehicle, and is a device capable of converting such information into an external device. For example, the vehicle terminal 160a may be a trip computer or an electronic control unit installed in the vehicle, but may be configured as a terminal device installed separately.

Here, the vehicle terminal 160a serves to generate the genesis block or to transmit the vehicle-related information generated by the vehicle state change according to the operation of the vehicle to the management server 110. The vehicle terminal 160a does not limit the present invention only by suggesting that the generation block generated together with the vehicle when the vehicle is generated may be generated by the management server 110.

In addition, the vehicle terminal 160a and the third party terminal 160b operate as a node of the blockchain. The vehicle terminal 160a and the third party terminal 160b serve to verify if a new block is propagated and require verification, and to return the verification result to the block forwarder.

In addition, the third party terminal 160b may include an information terminal arbitrarily present in the network to increase the reliability of verification without participating in the vehicle information management system. Whether such a third party terminal 160b includes a random information terminal is configured such that the configuration of the blockchain is open, private blockchain, or any node for verification can be added to the private blockchain. It is subject to change depending on whether it works.

2 is an exemplary diagram for explaining a company server of a vehicle information management system using a blockchain.

The vehicle information management system 100 using the blockchain includes a management server 110, a vehicle manufacturer server 120, a vehicle regular inspection server 130, a vehicle maintenance company server 140, a parts manufacturer server 150, and a user It may be configured to include a terminal 160, a police station server 170, a TXID management server 185, an insurance company server 180, and a traffic management agency server 190.

The vehicle manufacturer server 120 is a server provided in a company that manufactures a vehicle and provides basic information (hereinafter, basic vehicle information) at the time of manufacturing the vehicle to the management server 110. Basic vehicle information includes the vehicle's unique number (meaning the main serial number assigned to the vehicle, such as the vehicle identification number and engine number), the vehicle's release date, the specifics of the vehicle's manufacture, and information about options added to the vehicle at the time of shipment. Includes. When manufacturing a vehicle, specific items may include, for example, matters such as whether to stop the manufacturing line at the time of manufacturing the vehicle, whether to change parts suppliers, history of changing parts, and whether to change the manufacturing line. As an option to be added to a vehicle, for example, a component that is basically mounted on a vehicle that is shipped at the request of an orderer may be replaced with another part, or an example that is not included in the basic specification may be added at the factory.

The vehicle regular inspection server 130 means a server installed in a company that performs regular inspection of a vehicle according to the law, and provides a regular inspection result (hereinafter referred to as a vehicle regular inspection result) of the vehicle that has undergone regular inspection to the management server 110 do. Here, the information provided by the vehicle regular inspection server 130 may be transmitted to the traffic management industrial complex server 190 and may be transmitted to the management server 110 also by the traffic management industrial complex server 190. In the present invention, in this case, the information is received from both sides, and the management server 110 compares the contents transmitted through the two

servers

130 and 190 to ensure data reliability. However, the present invention is not limited by the suggestion that data can be received from only one

server

130 or 190.

The vehicle maintenance company server 140 is a server installed in a maintenance company that repairs or repairs a vehicle. After the vehicle is repaired, the maintenance information (hereinafter, vehicle maintenance information) of the corresponding vehicle entered by the vehicle maintenance company is managed by the management server 110. ). Here, the vehicle maintenance information includes information about attachments (optional) that are not attached by the vehicle manufacturer among vehicle attachments, maintenance date of the vehicle, driving distance of the vehicle, vehicle maintenance contents, parts used for replacement, and accident contents do. Attachments added to the outgoing vehicle may be convenient from the standpoint of the driver operating the vehicle, but may also be a disadvantage in terms of the vehicle's aging speed, vehicle life or safety, so these parts also determine the vehicle's aging and safety. Can be included. In addition, if the parts used for replacement are genuine, parts beyond the expiration date are used, parts recommended by the manufacturer are used, or vice versa, parts other than those recommended are used. It can be reflected in determining vehicle aging and safety.

The parts manufacturer server 150 is a server of a parts manufacturer that supplies parts of a vehicle to a vehicle maintenance company, and provides information to a management server 110 about which parts and when a vehicle maintenance company supplies parts (hereinafter, parts information). to provide. Here, the parts information includes the date of manufacture of the parts, production time, service life, delivery maintenance company, and recommended replacement time. The parts information can be checked to which vehicle maintenance company server 140, when, what parts, and how much parts are provided, and the running vehicle management server 110 provides parts information and parts information input by the vehicle maintenance company. By comparing, you can check the accuracy or error of the parts used by the vehicle maintenance company.

When the safety evaluation of a specific part manufactured in a specific period changes after the sale, the evaluation score assigned to the safety of the part changes. For example, it could not be confirmed during the manufacture and sale of the part, but it was the case that the defect of the part was found while analyzing the vehicle in the accident.

Also, assuming that the higher the evaluation score is, the higher the safety score is compared to when the evaluation score is low, when the inspection by the police or the relevant authorities determines that there is a defect in a specific product produced by a specific company for a specific period of time. The evaluation score applied to the parts should be reduced, and then, when a specific vehicle replaces the corresponding part with a normal part, the evaluation score for the safety of the corresponding vehicle can be modified.

The user terminal 160 includes an input/output device owned by the owner of the vehicle or a transportation company operating a plurality of vehicles, and an input/output device owned by a user of another vehicle participating in the management system 100. The user terminal 160 transmits the driving information of the vehicle to the management server 110. Here, the use of the personal vehicle, for example, one of the use mode of the vehicle owned by the individual, such as commuting, traveling, and personal business, will be an example, and the operating information of the operating vehicle is the operational purpose of the vehicle (passenger, cargo transportation), service route , Driving distance, and history of driving drivers. The operating route is a route on which business vehicles move, and includes specific features of the route, such as unpaved roads and construction.

The user terminal 160 collects information and transmits it to the management server 110 like other servers in order to generate a vehicle information block of the blockchain, and verifies the block generated by the management server 110 And propagates the node. The role of the node is also performed by the servers. This will be described in more detail while describing the management server 110 below.

The police station server 170 transmits vehicle accident information and enforcement information to the management server 110. Here, the crackdown information will include speeding or signal violation.

The insurance company server 180 transmits the accident of the vehicle that sees the agreement to the management server 110 without reporting to the police station during the vehicle accident. Vehicle accidents are generally filed with the police, but minor accidents other than personnel accidents may result in agreement between the abuser and the victim and not be reported to the police. However, even in this case, when the settlement amount is now through the insurance company, the record is transmitted to the management server 110, so that such a situation can also be used as data for determining the safety of the vehicle. In addition, since an insurance process of a vehicle or an accident not reported to the police can be viewed or analyzed through the repair history of the maintenance company server 140, actual accident occurrence information can be used as judgment data in various ways.

The management server 110 includes a vehicle manufacturer server 120, a vehicle regular inspection server 130, a vehicle maintenance company server 140, a parts manufacturing company server 150, a user terminal 160, a police station server 170, insurance It receives and receives various information from the company server 180 and the traffic management industrial complex server 190, and uses the received information to evaluate and take measures to aging and safety of the vehicle.

The management server 110 indexes the collected information for the evaluation of aging and safety, and calculates it as a score indicating the state of the vehicle.

In particular, the management server 110 generates a part (or all) of these scores, indices, and collected information as blocks, and propagates the generated blocks to nodes. Here, the nodes include a device that connects to the management server 110 and provides information, devices that access to use the information, and arbitrary devices that exist on the network separately. However, the management server 110 may configure a private blockchain by limiting only nodes that connect to the management server 110 to provide information and devices that access to use the information as nodes, in this case management The server 110 may perform authorization of devices participating in the private blockchain. However, the present invention is not limited by the suggestions.

The management server 110 indexes the collected information and scores the indexed information. To this end, the management server 110 includes information such as algorithms, reference values, and depreciation for indexing the collected information and scoring each index of the vehicle.

As an example, the index may be set to 100 points when the parts are shipped out of the vehicle, and the rate at which these parts are reflected in the vehicle score may be set at 10%. In addition, it can be selected as 0.01%/1000km for each mileage and mileage due to aging, and used for index and score calculation. These examples are used for convenience of description, and the present invention is not specifically limited thereto.

The management server 110 may generate blocks and propagate the collected information used for calculating the index, the score information and the algorithm or judgment criteria used for calculating the index and the score, the index or the score in a block. In addition, it is possible to configure the blockchain by adding the collected information to the block whenever the information needs to be updated. The propagation and verification of such information has been disclosed through blockchain technology, and detailed description thereof will be omitted.

In particular, the management server 110 stores the transaction ID (TXID) used in the generation of the block to match the user's information or vehicle information for the management of such information, block generation and update. For example, when the user participates in the management system 100 through the user terminal 160, and a block for this user's vehicle is generated, an ID for a block transaction is generated. While the transaction ID (TXID) user participates in the system, it is stored corresponding to the information of the user registered in the management server 110. Subsequently, when the user wants to access the block information through the user terminal 160 or update the contents of the block, access and use of the information is authenticated by using only one of the user information or the transaction ID (TXID) matched thereto. It can be enabled.

In addition, the management server 110 may store and manage the public key that can distinguish the blockchain by matching the member information. As described above, the transaction ID may be matched with the member information or the public key may be matched and stored, or both may be matched with the member information and stored. In particular, the management server 110 may convert and store the public key or transaction ID into information that is easy for general members to check, such as a vehicle number. That is, the member information and the public key (or transaction ID) are matched and stored. At this time, the public key (or transaction ID) is matched and stored with the vehicle number to store the block chain through the member's name or vehicle number. You can have access to information. To this end, when the member's name and vehicle number are entered by a third party, the management server 110 can check the blockchain through the corresponding public key (or transaction ID) and provide it to the user who has the request. have. Through this, in the present invention, when information about a specific vehicle or a plurality of vehicles is to be collected and regenerated with other information, information already known to users (for example, when management of a vehicle that is an information subject of a blockchain is required) You can access the blockchain through information such as the owner of the vehicle or the number of the vehicle) and use the information by confirming the transaction described in the block.

In particular, the management server 110 may convert and store the public key into information that is easy for general members to check, such as a vehicle number. That is, the member information and the public key are matched and stored, and at this time, the public key is matched and stored with the vehicle number so that users can access the information on the blockchain through the member's name or vehicle number. To this end, when the member's name and vehicle number are input by a third party, the management server 110 may check the blockchain through a corresponding public key and provide it to a user who has a request.

To this end, nodes participating in the management system 100, that is, when members store information of a neighbor node, check the information of the node in the management system 100 to check whether the node participates in the vehicle information management system. It can be rough. In addition, through this, each server or terminals of the management system 100 can modify the order of neighboring nodes so that block sharing and verification among members of the management system 100 can be preferentially performed, but this is only provided as an example. It is not intended to limit the present invention.

Here, it is possible to change the verification order of the verification list in addition to the delivery order. That is, for member nodes participating in the management system, verification of blocks generated by members among blocks transmitted by the blockchain may be given priority, and for this, the management server 110 is generated by members. For example, the member IDs can adjust the verification order of the verification list by transmitting the information of the block, for example, the transaction ID and the public key.

3 is an exemplary diagram for describing a vehicle information management method using a blockchain.

Vehicle information management method using the blockchain according to the present invention is a Genesis block generation step (S10), vehicle-related information generation step (S20), vehicle-related information block generation and delivery step (S30), index and score calculation step (S40) , Index and score block generation and delivery step (S50), a score using step (S60) and information update determination step (S70).

In the Genesis block generation step (S10), the Genesis block corresponding to the vehicle to be managed is generated by the management server 110 or the vehicle terminal 160a. The Genesis block creation step (S10) is a step in which management is started by an owner participating in the management system 100 as a member, or a vehicle requiring management for the owner who is a member.

At this time, in the Genesis block, information that can be disclosed among basic information and member information of the vehicle may be stored as a transaction. Here, the basic information is information obtained from the vehicle manufacturer's server 120, such as the vehicle's number, vehicle identification number, engine number, model number, first owner of the vehicle, date of manufacture of the vehicle, manufacturing plant, and applied options, insurance company server (180 ) May be included. To this end, the management server 110 may request and receive such information from the manufacturer server 120 and the insurance company server 180, but the present invention is not limited thereto. In addition, the information that can be input by the vehicle terminal 160a or the management server 110 is generated as a genesis block, except for information that the management server 110 needs to request and receive from other servers, and basic information of the vehicle is generated. The present invention is not limited by the suggestion that the second block may be connected to the Genesis block to form a block group of the initial blockchain. That is, in the generation block of the Genesis block (S10), the vehicle terminal 160a or the management server 110 records the most basic information in the Genesis block, and transmits it to the other side to record additional information, so that the block of the initial blockchain Although it is possible to record the information related to the vehicle and the owner in the group so that the initial information is connected and transmitted by subsequent blocks, the present invention is not limited thereto.

In addition, the member information stored in the block generated in the Genesis block creation step (S10) may store information that can be exposed to a third party, such as a vehicle number, a vehicle owner's name, and an ID registered as a member in the management system 100. have.

The block generated in the Genesis block generation step (S10) can be propagated to the member nodes as it is, but verification can be performed, but a chain is formed by generating a block connected through the transfer between the management server 110 and the vehicle terminal 160a. After that, other information may be written in the block.

The vehicle-related information generation step (S20) is a step in which vehicle-related information is generated by the company server 111 or the user terminal 160 when a vehicle-related issue occurs. This vehicle-related information means information corresponding to an index and a score for evaluating a vehicle. For example, it means various information such as mileage, maintenance history, accident history, and violation of laws and regulations, and when any one of them occurs, it can be generated by a device that handles the issue.

In the vehicle-related information block generation and delivery step (S30), when vehicle-related information that needs to be updated or added is generated, a vehicle that processes the vehicle-related information, that is, a vehicle by a company server 111, a vehicle terminal 160a, or a management server 110 This is a step in which a transaction with related information and a block recording it are generated and propagated to members.

Here, the vehicle-related information block may be a block connected to the above-mentioned Genesis block and a block connecting the initial block (referred to as "base block chain"), and the vehicle-related information may be managed by the management server 111 and the user terminal 160. It may be a block included in a separate blockchain (hereinafter referred to as "family block chain") for delivery to. These family blockchains can be created individually for items that frequently occur in issues such as maintenance, accidents, and violations of laws, such as items related to vehicle-related information, but it is also possible to have all of this information listed in one family blockchain. have. This is according to the amount of information and processing efficiency described in the block, and can be adjusted in actual implementation.

In the index and score calculation step (S40), when vehicle-related information is delivered to the management server 110 by the blockchain, the information included in the blockchain of the management server vehicle-related information is checked to calculate the index, and the score is calculated by the index. Will yield This index and scores have been described in detail above, and thus detailed descriptions thereof will be omitted. Here, the management server 110 checks the final index and score of the base blockchain of the vehicle when it is confirmed that the vehicle-related information is vehicle information for a specific vehicle regardless of being transmitted to the base blockchain or family blockchain. , The updated index and score are calculated by applying the added vehicle-related information.

In the index and score block generation and delivery step (S50), the management server 110 generates a block describing the calculated index and score, and creates a block to connect to the previously created blockchain, that is, member nodes (ie, companies). This is the step of delivering to the server 111 and the user terminal 160. In this index and score block generation and delivery step (S50), when vehicle-related information is transmitted by a block of the base blockchain, the base block chain is connected so that the newly created block is connected to the block of the base blockchain. Create a block based on it. Even when vehicle-related information is transmitted through the family blockchain, the index and score information will be written on the block connected to the base blockchain. However, in this case, in the block connected to the family blockchain, a block that records that the index and score information has changed according to the update of vehicle-related information may be generated and described in the family blockchain, but the present invention is not limited thereto.

The score use step (S60) is a step in which the information written in the base blockchain is received by the user terminal 160 or the company server 111 and used as indicators for various evaluations and uses such as vehicle evaluation and safety check. In such a score use step (S60), the user terminal 160 or the company server 111 checks or outputs information transmitted through the block through a program for processing the blockchain, so that the user can use the information to perform a predetermined action. It is provided so that it can be performed.

The information update determination step (S70) is a step of checking whether a new issue requiring updating or changing of vehicle-related information has occurred after the above-described steps S20 to S60. This information update determination step (S70) can be determined by both the management server 110, the company server 111, and the user terminal 160, and if it is necessary to update or add a block through the above steps S20 to S60 Chains are formed and used.

In the above, although illustrated and described as a specific example to illustrate the technical spirit of the present invention, the present invention is not limited to the same configuration and operation as the specific embodiments as described above, and various modifications are within the limits of the scope of the present invention. Can be practiced. Therefore, such modifications should also be regarded as belonging to the scope of the present invention, and the scope of the present invention should be determined by the claims below.

The present invention can improve the reliability of the calculated value for the vehicle by improving the reliability in the management of vehicle information, thereby enabling the activation and market activation of transactions such as used transactions. In addition, since malicious information manipulation of the vehicle state information can be prevented, the state information itself can be used as one big data.

Claims

A company server that collects vehicle-related information that is information on an event related to a vehicle, a vehicle owner, and a vehicle operator, and writes the collected vehicle-related information as a transaction in a blockchain to generate a block;

Upon receiving the block, the vehicle-related information recorded in the block is applied to a reference value and an algorithm to generate an index for each vehicle information, and the index is used to calculate a score indicating the state of the vehicle as a numerical value, and the calculated index or Vehicle information management system using a block chain, characterized in that comprises a; management server for recording the score in the index / score block.
According to claim 1,

The management server is a vehicle information management system using a blockchain, characterized in that the index/score block is connected to a base block chain having a block in which basic information about the vehicle is recorded as a Genesis block.
According to claim 2,

The base blockchain

The management server, and the Genesis block generated by any one of the vehicle terminal and

Vehicle information management system using a blockchain, characterized in that it comprises an initial block chain that is generated by the management server and the other of the vehicle terminal, and includes a second block connected to the genesis block.
According to claim 2,

The block is generated separately from the base block, the vehicle information management system using a block chain, characterized in that the block of the family block chain generated to describe the vehicle-related information of the vehicle.
The method of claim 4,

The management server records indexes and scores calculated using the vehicle-related information transmitted and written in the blocks of the family blockchain in both blocks connected to the base blockchain and blocks connected to the family blockchain, respectively Vehicle information management system using a blockchain, characterized by connecting to the blockchain.
The method of claim 3,

A vehicle information management system using a blockchain, characterized in that the management server, the company server, and the user terminal including the vehicle terminal constitute a private blockchain.
The method of claim 6,

The management server, the company server and the user terminal

A vehicle information management system using a blockchain, characterized in that a block generated from a member who has joined the vehicle information management system is preferentially verified in preference to a block transmitted from the outside.
The method of claim 6,

The management server, the company server and the user terminal

A vehicle information management system using a blockchain, characterized in that the block is first delivered to a member node subscribed to the vehicle information management system.
According to claim 1,

The management server

Vehicle information management system using a blockchain, characterized in that the algorithm or reference value used for calculating the index or the score is described in the block.
According to claim 1,

The management server

Vehicle information management system using a blockchain, characterized by matching and managing any one or more of the member information of the user who owns the vehicle, the vehicle information of the vehicle, the public key of the blockchain, and the transaction ID of the block.