Blockchain-based bridge informationization anti-collision method and system

Abstract

The application discloses a bridge informatization anti-collision method based on a blockchain, and comprises the following steps: establishing a unified identity code for a bridge that joins the blockchain in advance; and constructing a bridge blockchain Chain1, a ship blockchain Chain2 and a bridge-ship passing information blockchain Chain3; acquiring the identity code of a ship that enters a monitoring area, sensing real-time information of the ship, writing the acquired ship information and bridge information into the bridge-ship passing information blockchain Chain3, and signing the written information by using a private key corresponding to the bridge identity code acquired in advance; comparing the sensed real-time information of the ship with corresponding bridge information, judging whether the ship has a collision risk, and if yes, issuing a collision warning to the corresponding ship; if a collision still occurs after the warning, deducting a certain amount of pre-stored ship deposit and writing the information into the bridge-ship passing information blockchain Chain3. The application can realize sharing of bridge data and improve the credibility of the bridge data.

Description

Technical Field

[0001] This invention relates to the field of bridge information technology, and in particular to a bridge information-based collision avoidance method and system based on blockchain. Background Technology

[0002] Current methods for bridge collision avoidance primarily utilize lidar, electronic fences, and infrared image recognition. These methods generate a large amount of sensing data, but because this data is owned by individual bridges and is not currently shared between upstream and downstream bridges, a secure data recording medium is needed. Establishing a new shared database would require a new server, and centralized server management would increase costs. Furthermore, the lack of a sharing mechanism leads to redundant deployment of information-based detection methods (such as lidar height measurement), resulting in high engineering and maintenance costs.

[0003] While blockchain technology offers convenience for sharing to some extent, its application in bridge information systems presents several challenges: 1) How many chains are needed? 2) What information should be uploaded to the chain? 3) How should information be uploaded? 4) How can the economic mechanisms of blockchain be used to prevent bridge collisions? Existing technologies do not provide corresponding solutions. Summary of the Invention

[0004] The main objective of this invention is to provide a blockchain-based bridge information-based collision avoidance method and system that enables bridge data sharing and improves the credibility of bridge data.

[0005] The technical solution adopted in this invention is:

[0006] This invention provides a blockchain-based information-based bridge collision avoidance method, comprising the following steps:

[0007] A unified identity code is pre-established for the bridges joining the blockchain; and a bridge blockchain Chain1 for storing bridge information, a ship blockchain Chain2 for storing ship information, and a bridge-ship passage information blockchain Chain3 for storing passage information are constructed.

[0008] The system acquires the identification code of the vessel entering the monitoring area and senses the real-time information of the vessel. Together with the vessel information in the acquired vessel blockchain Chain2, the current bridge information, or the bridge information in the bridge blockchain Chain1, the information is written into the bridge vessel passage information blockchain Chain3. The information written into the bridge vessel passage information blockchain Chain3 is signed with the private key corresponding to the pre-acquired bridge identification code.

[0009] The system compares the real-time information of the sensed ships with the corresponding bridge information to determine whether there is a risk of collision. If so, a collision warning is issued to the corresponding ship. If a collision still occurs after the warning, a certain amount of the pre-deposited ship deposit is deducted and written into the bridge ship passage information blockchain Chain3.

[0010] Following the above technical solution, the data structure of the bridge blockchain Chain1 includes a block header (Blockhead1) and a block body (Blockbody1). The Block header (Blockhead1) includes the hash value of the previous block header, the hash value of the current block, and the signature of the bridge registration client. The Block body (Blockbody1) stores the bridge information corresponding to the bridge identity code, including the bridge identity code, bridge name, construction time, bridge construction unit, bridge management unit, bridge ownership unit, bridge height, and bridge width.

[0011] Following the above technical solution, the data structure of the ship blockchain Chain2 includes a block header (Blockhead2) and a block body (Blockbody2). The block header (Blockhead2) includes the hash value of the previous block header, the hash value of the current block, and the ship registration client signature. The block body (Blockbody2) stores the ship information corresponding to the ship's identity code, including the ship's identity code, ship name, construction time, ship owner's unit, ship height, ship width, and maximum speed.

[0012] Following the above technical solution, the data structure of the bridge and vessel passage information blockchain Chain3 includes a block header (Blockhead3) and a block body (Blockbody3). The block header (Blockhead3) includes the hash value of the previous block header, the hash value of the current block, and the bridge client signature. The block body (Blockbody3) includes three types of information: 1) Vessel information for this bridge passage: bridge identification code, vessel identification code, and the time the vessel passed through the bridge; 2) Current bridge monitoring data: hydrological data, meteorological data, and photographic data; 3) Current vessel monitoring data: current deposit amount and number of collisions.

[0013] Based on the above technical solution, the methods for determining whether a ship has a collision risk include:

[0014] By acquiring collision information, bridge information, and ship information from three blockchains, the risk assessment value is calculated based on a pre-built collision risk assessment model.

[0015] Determine if the risk assessment value exceeds the preset value. If so, there is a collision risk, and an alarm message will be generated.

[0016] Following the above technical solution, each time a ship safely passes through the bridge or collides with it, a new record is generated. If it is a collision, the collision count is incremented by 1, the deposit is reduced by a certain amount, and the information is written into the bridge ship passage information blockchain Chain3. If there is no collision, the count remains unchanged, and the deposit amount remains unchanged. The deposit is in the form of central bank digital currency.

[0017] This invention also provides a blockchain-based bridge information-based collision avoidance system, comprising:

[0018] The blockchain construction module is used to pre-establish a unified identity code for bridges joining the blockchain; and to construct the bridge blockchain Chain1, the ship blockchain Chain2, and the bridge ship passage information blockchain Chain3 for storing ship information.

[0019] The bridge crossing monitoring module is used to obtain the identity code of the vessel entering the monitoring area and sense the real-time information of the vessel. Together with the vessel information in the bridge blockchain Chain1, the current bridge information, or the bridge information in the vessel blockchain Chain2, it is written into the bridge vessel crossing information blockchain Chain3. The information written into the bridge vessel crossing information blockchain Chain3 is signed with the private key corresponding to the pre-obtained bridge identity code.

[0020] The collision analysis module is used to compare the real-time information of the sensed ships with the corresponding bridge information to determine whether there is a collision risk. If so, a collision warning is issued to the corresponding ship. If a collision still occurs after the warning, a certain amount of the pre-deposited ship deposit is deducted and written into the bridge ship passage information blockchain Chain3.

[0021] This invention also provides a blockchain-based bridge information-based collision avoidance system, comprising:

[0022] The bridge client, installed on the bridge server, is used to generate the bridge identity code and its public and private keys, and to read and write the pre-built bridge blockchain Chain1 for storing bridge information and the pre-built bridge and ship passage information blockchain Chain3 for storing passage information.

[0023] The ship registration client is used to generate ship identification codes and their public and private keys, and to read and write the pre-built ship blockchain Chain2 used to store ship information;

[0024] The bridge client is also used to: obtain the identity code of the vessel entering its monitoring area, sense the real-time information of the vessel, and write it together with the vessel information in the vessel blockchain Chain2 obtained from the blockchain server, the current bridge information, or the bridge information in the bridge blockchain Chain1 into the bridge vessel passage information blockchain Chain3; sign the information written into the bridge vessel passage information blockchain Chain3 with the private key corresponding to the pre-obtained bridge identity code; compare the sensed real-time information of the vessel with the corresponding bridge information to determine whether there is a collision risk; if so, issue a collision warning to the corresponding vessel; if a collision still occurs after the warning, deduct a certain amount of the pre-deposited vessel deposit and write it into the bridge vessel passage information blockchain Chain3.

[0025] Following the above technical solution, the data structure of the bridge blockchain Chain1 includes a block header (Blockhead1) and a block body (Blockbody1). The block header (Blockhead1) includes the hash value of the previous block header, the hash value of the current block, and the signature of the bridge registration client. The block body (Blockbody1) stores the bridge information corresponding to the bridge identity code, including the bridge identity code, bridge name, construction time, bridge construction unit, bridge management unit, bridge ownership unit, bridge height, and bridge width.

[0026] The data structure of the ship blockchain Chain2 includes a block header (Blockhead2) and a block body (Blockbody2). The block header (Blockhead2) contains the hash value of the previous block header, the hash value of the current block, and the ship registration client signature. The block body (Blockbody2) stores the ship information corresponding to the ship's identity code, including the ship's identity code, ship name, construction time, ship owner's unit, ship height, ship width, and maximum speed.

[0027] The data structure of the bridge and vessel passage information blockchain Chain3 includes a block header (Blockhead3) and a block body (Blockbody3). The block header (Blockhead3) includes the hash value of the previous block header, the hash value of the current block, and the bridge client signature. The block body (Blockbody3) includes three types of information: 1) Vessel information for this bridge passage: bridge identification code, vessel identification code, and the time the vessel passed through the bridge; 2) Current bridge monitoring data: hydrological data, meteorological data, and photographic data; 3) Current vessel monitoring data: current deposit amount and number of collisions.

[0028] The present invention also provides a computer storage medium storing a computer program executable by a processor, the computer program executing the blockchain-based bridge information-based collision avoidance method described in the above technical solution.

[0029] The beneficial effects of this invention are as follows: This invention primarily establishes a blockchain-based data and information sharing mechanism between upstream and downstream bridges, thereby reducing the procurement and deployment of inspection equipment. This invention treats blockchain data as a shared database, which has the advantages of being small-scale, shared, and tamper-proof. By designing a bridge blockchain (Chain1) for storing bridge information, a ship blockchain (Chain2) for storing ship information, and a bridge-ship passage information blockchain (Chain3) for storing passage information, a data sharing mechanism is formed, and the issue of bridge data trustworthiness is solved using blockchain technology.

[0030] Furthermore, the amount of data on the blockchain should not be too large, as this will lead to a heavy load on the blockchain client. Therefore, this invention forms a blockchain data structure that includes a block header and a block body by carefully selecting the on-chain data and designing the block data structure. The block header is mainly used to store the hash value of the previous block header and the current block, while the block body is used to store the corresponding information data.

[0031] Furthermore, the use of central bank digital currency (CBDC) has addressed the difficulty of enforcing laws against illegal activities by ships. With the application of CBDC, especially the legal digital yuan, using digital yuan to monitor and urge compliance with past violations by ships will help prevent such incidents from occurring. The digital yuan has official status, making it subject to regulation, and also possesses digital characteristics, offering convenient payment options.

[0032] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a schematic diagram of the structure of an embodiment of the present invention;

[0035] Figure 2 This is a schematic diagram of the data structure of the bridge blockchain Chain1 according to an embodiment of the present invention;

[0036] Figure 3 This is a schematic diagram of the data structure of Ship Blockchain Chain2 according to an embodiment of the present invention;

[0037] Figure 4 This is a schematic diagram of the data structure of the blockchain Chain3 for bridge and ship passage information in an embodiment of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0039] It should be noted that the illustrations provided in the embodiments of the present invention are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the number, shape and size of the components in actual implementation. In actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0040] In this invention, it should also be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Furthermore, the terms "first" and "second" are used only for descriptive and distinguishing purposes and should not be construed as indicating or implying relative importance.

[0041] like Figure 1 As shown, the blockchain-based bridge information-based collision avoidance method of this invention includes the following steps:

[0042] S1. Establish a unified identity code for the bridges to be added to the blockchain in advance; and construct a bridge blockchain Chain1 for storing bridge information, a ship blockchain Chain2 for storing ship information, and a bridge-ship passage information blockchain Chain3 for storing passage information.

[0043] S2. Obtain the identity code of the vessel entering the monitoring area and sense the real-time information of the vessel. Together with the vessel information in the vessel blockchain Chain2, the current bridge information or the bridge information in the bridge blockchain Chain1, write it into the bridge vessel passage information blockchain Chain3. Sign the information written into the bridge vessel passage information blockchain Chain3 using the private key corresponding to the pre-obtained bridge identity code.

[0044] S3. Compare the real-time information of the sensed ships with the corresponding bridge information to determine whether there is a risk of collision. If so, issue a collision warning to the corresponding ship. If a collision still occurs after the warning, deduct a certain amount of the pre-deposited ship deposit and write it into the bridge ship passage information blockchain Chain3.

[0045] In step S2, the methods for obtaining ship information include:

[0046] (1) Direct acquisition. That is, the bridge monitoring system collects relevant data of the ship, including: radar height measurement, infrared image, speed, beam and other information.

[0047] (2) Indirect acquisition. If the equipment required to collect information has not yet been deployed, then query the bridge information blockchain.

[0048] Furthermore, the design of the blockchain data structure for bridges and ships and its data composition include:

[0049] (3) Bridges joining the blockchain alliance establish a unified identity code (BID), such as province / city code-river code-bridge code. Ships joining the blockchain alliance establish a unified ship identity code (SID).

[0050] (4) Constructing the bridge blockchain Chain1.

[0051] (5) Construct the ship blockchain Chain2.

[0052] (6) Construct a blockchain for information on bridge and ship passage: Chain3.

[0053] Among them, the data structure of the bridge blockchain Chain1 is as follows: Figure 2 As shown, it includes:

[0054] (1) Blockchain Chain1 includes Blockhead1 and Blockbody1.

[0055] (2) The Blockhead1 information of Blockchain Chain1 includes: PreviousBlockHeadHash, current block hash - BlockHash, and bridge registration client signature SIG. PreviousBlockHeadHash refers to the hash value of the previous block header, generated by the SM3 algorithm. BlockHash is the hash value of the current block, generated by the SM3 algorithm.

[0056] (3) Blockbody1 stores the bridge information corresponding to the bridge identification code, including: bridge identification code BID, bridge name BNAME, construction time BTIME, bridge construction unit BCC, bridge management unit BMC, bridge ownership unit BOC, bridge height BH, and bridge width BW.

[0057] like Figure 3 As shown, the data structure of the ship blockchain Chain2 includes:

[0058] (1) The blockchain Chain2 includes the block header Blockhead2 and the block body Blockbody2.

[0059] (2) The Blockhead2 information of the Chain2 blockchain includes: the previous block header hash value (PreviousBlockHeadHash), the current block hash (BlockHash), and the ship registration client signature (SIG). PreviousBlockHeadHash refers to the hash value of the previous block header, generated using the SM3 algorithm. BlockHash is the hash value of the current block, generated using the SM3 algorithm.

[0060] (3) Blockbody2 stores the ship information corresponding to the ship identification code, including: ship identification code SID, ship name SNAME, construction time STIME, ship owner unit SOC, ship height SH, ship width SW, and maximum speed SP.

[0061] like Figure 4 As shown, the data structure of the Chain3 blockchain for bridge and vessel passage information includes:

[0062] (1) The blockchain Chain3 includes the block header 3 and the block body 3.

[0063] (2) The Blockhead3 information of the Bridge & Ship Blockchain includes: PreviousBlockHeadHash, current block hash - BlockHash, and bridge client signature SIG. PreviousBlockHeadHash is the hash value of the previous block header, generated using the SM3 algorithm. BlockHash is the hash value of the current block, generated using the SM3 algorithm.

[0064] (3) Blockbody3 includes three types of information: 1) Information about the vessel's crossing of the bridge: bridge identification code BID, vessel identification code SID, and the time T when the vessel crossed the bridge. 2) Current bridge monitoring data, including: hydrological data, meteorological data, and photographic data. 3) Current vessel monitoring data, including: current deposit amount and number of collisions.

[0065] Furthermore, the data on-chain method for the bridge blockchain Chain1 includes: when the bridge registration and management party joins the blockchain consortium, after downloading the blockchain software client, the client will generate the bridge BID and its public and private keys. The bridge management party then enters the information of the bridge to be registered.

[0066] The data on-chain method of the ship blockchain Chain2 includes: when the ship registration manager joins the blockchain consortium, after downloading the blockchain software client, the client will generate the ship's SID and its public and private keys. The ship management manager will then enter the ship information.

[0067] The methods for uploading bridge and vessel passage information to the Chain3 blockchain and the methods for using on-chain data include:

[0068] (1) When a ship enters the monitoring area, initiate an AIS ship identification dialogue to obtain the ship's identity information SID.

[0069] (2) The bridge obtains real-time information on the perception and monitoring of passing ships based on the currently deployed shoreline or bridge equipment.

[0070] (3) If there is no real-time monitoring information for the bridge, the relevant information of the vessel (e.g., vessel height) is read from the blockchain Chain2. The bridge information is read from the blockchain Chain1, and the relevant data of the vessel is compared with the current bridge data (e.g., bridge height) to determine whether there is a safety risk, such as the risk of colliding with the bridge, and corresponding early warning measures are taken.

[0071] (4) Information about ships passing over the bridge, along with ship and bridge information, forms the corresponding block and block header. The current block information is the information in Blockbody3. The information written into the block needs to be signed using the private key corresponding to the bridge identity code (installed on the bridge server blockchain client). The signature includes: the current block hash, and the block header field information (i.e., the hash value of the previous block header, PreviousBlockHeadHash, and the current block hash minus BlockHash). Finally, the block header is written.

[0072] (5) Block writing is handled by the bridge server of the bridge. Each bridge server has a client installed on the bridge blockchain. The client is configured with the bridge's identity information (SID) and the corresponding public and private keys. Client functions include: writing to the blockchain, viewing the blockchain, and viewing the current deposit balance of the vessel. A copy of the blockchain is maintained on each bridge server. The correctness of the signature signed with the bridge's private key can be verified by other bridge servers and their blockchain clients. Public key certificates can be issued when necessary, containing the bridge's identity code, public key, and CA's signature.

[0073] If a vessel with safety hazards is involved in a collision despite being notified by phone or radio, a certain amount will be deducted from the vessel's deposit. This deducted portion will be transferred to a public account and recorded on the blockchain. The digital RMB in the public account will be used for bridge maintenance, etc.

[0074] Furthermore, methods for determining whether a vessel is at risk of collision include:

[0075] By acquiring collision information, bridge information, and ship information from three blockchains, the risk assessment value is calculated based on a pre-built collision risk assessment model.

[0076] Determine if the risk assessment value exceeds the preset value. If so, there is a collision risk, and an alarm message will be generated.

[0077] Each time a ship safely passes under the bridge or collides with it, a new record is generated. If it is a collision, the collision count is incremented by 1, the deposit is reduced by a certain amount, and the information is written into the bridge ship passage information blockchain Chain3. If there is no collision, the count remains unchanged, and the deposit amount remains unchanged. The deposit is in the form of central bank digital currency.

[0078] In another embodiment of the present invention, the collision avoidance analysis method in step S3 specifically includes:

[0079] By acquiring on-chain collision information, bridge information, and ship information, a collision risk assessment index I is constructed. Chain3's Blockbody3 contains hydrological data A and meteorological data B; Chain2's Blockbody2 contains ship width C, height D, and maximum speed information E; and Chain1's Blockbody1 contains bridge height F and width information G. Performing common logistic regression analysis on this collision data yields the assessment index I. G represents the factors, and collision risk represents the logistic regression result. Through sample learning, a model for index I is obtained.

[0080] Each time a ship passes under the bridge, a blockchain record is created on Chain3, and this record is immutable. Pointers on Chain3 are used to retrieve relevant information from Chain1 and Chain2, forming the basis for subsequent factor analysis. This process ultimately leads to a contract algorithm, which can be continuously improved with the addition of data.

[0081] Furthermore, in one embodiment of the present invention, the deduction of deposit (token) on the blockchain is as follows: each successful pass and collision will inevitably generate a new record. If there is a collision, the collision count is incremented by 1, and the deposit is reduced by an amount K. If there is no collision, the count remains unchanged, and the deposit amount remains unchanged. The initial collision count is 0. The initial deposit amount is 5K.

[0082] To implement the above method embodiments, the present invention also provides a blockchain-based bridge information-based collision avoidance system, comprising:

[0083] The bridge client, installed on the bridge server, is used to generate the bridge identity code and its public and private keys, and to read and write the pre-built bridge blockchain Chain1 for storing bridge information and the pre-built bridge and ship passage information blockchain Chain3 for storing passage information.

[0084] The ship registration client is used to generate ship identification codes and their public and private keys, and to read and write the pre-built ship blockchain Chain2 used to store ship information;

[0085] The bridge client is also used to: obtain the identity code of the vessel entering its monitoring area, sense the real-time information of the vessel, and write it together with the vessel information in the vessel blockchain Chain2 obtained from the blockchain server, the current bridge information, or the bridge information in the bridge blockchain Chain1 into the bridge vessel passage information blockchain Chain3; sign the information written into the bridge vessel passage information blockchain Chain3 with the private key corresponding to the pre-obtained bridge identity code; compare the sensed real-time information of the vessel with the corresponding bridge information to determine whether there is a collision risk; if so, issue a collision warning to the corresponding vessel; if a collision still occurs after the warning, deduct a certain amount of the pre-deposited vessel deposit and write it into the bridge vessel passage information blockchain Chain3.

[0086] Furthermore, a blockchain server can be designed to store bridge information (Bridge Blockchain Chain1), ship information (Ship Blockchain Chain2), and bridge-ship passage information (Bridge Blockchain Chain3). Simultaneously, specific ship measurement data can be packaged into files, stored on a shared server, and then the file summary can be uploaded to the blockchain. This can establish common trust, ensure the credibility of measurement data, and establish a shared trust database.

[0087] The specific functions of each module are the same as those in the method implementation, and will not be repeated here.

[0088] This application also provides a computer-readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, server, App application store, etc., which stores a computer program, and the program implements corresponding functions when executed by a processor. This embodiment describes a blockchain-based bridge information collision avoidance method implemented when the computer-readable storage medium is executed by a processor.

[0089] It should be noted that, depending on the implementation needs, the various steps / components described in this application can be broken down into more steps / components, or two or more steps / components or parts of the operation of steps / components can be combined into new steps / components to achieve the purpose of this invention.

[0090] The order of the steps in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0091] It should be understood that those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A blockchain-based information-based bridge collision avoidance method, characterized in that, Includes the following steps: Establish a unified identity code in advance for bridges joining the blockchain; And construct a bridge blockchain Chain1 for storing bridge information, a ship blockchain Chain2 for storing ship information, and a bridge-ship passage information blockchain Chain3 for storing passage information; The system acquires the identification code of the vessel entering the monitoring area and senses the real-time information of the vessel. Together with the vessel information in the acquired vessel blockchain Chain2, the current bridge information, or the bridge information in the bridge blockchain Chain1, the information is written into the bridge vessel passage information blockchain Chain3. The information written into the bridge vessel passage information blockchain Chain3 is signed with the private key corresponding to the pre-acquired bridge identification code. The system compares the real-time information of the sensed ships with the corresponding bridge information to determine whether there is a risk of collision. If so, a collision warning is issued to the corresponding ship. If a collision still occurs after the warning, a certain amount of the pre-deposited ship deposit is deducted and written into the bridge ship passage information blockchain Chain3.

2. The blockchain-based bridge information-based collision avoidance method according to claim 1, characterized in that, The data structure of the bridge blockchain Chain1 includes a block header (Blockhead1) and a block body (Blockbody1). The block header (Blockhead1) contains the hash value of the previous block header, the hash value of the current block, and the signature of the bridge registration client. The block body (Blockbody1) stores the bridge information corresponding to the bridge identity code, including the bridge identity code, bridge name, construction time, bridge construction unit, bridge management unit, bridge ownership unit, bridge height, and bridge width.

3. The blockchain-based bridge information-based collision avoidance method according to claim 1, characterized in that, The data structure of the ship blockchain Chain2 includes a block header (Blockhead2) and a block body (Blockbody2). The information in the block header (Blockhead2) includes the hash value of the previous block header, the hash value of the current block, and the ship registration client signature. Blockbody2 stores the ship information corresponding to the ship identification code, including the ship identification code, ship name, construction time, ship owner unit, ship height, ship width, and maximum speed.

4. The blockchain-based bridge information-based collision avoidance method according to claim 1, characterized in that, The data structure of the blockchain Chain3 for bridge and vessel passage information includes a block header (Blockhead3) and a block body (Blockbody3). The information in the block header (Blockhead3) includes the hash value of the previous block header, the hash value of the current block, and the bridge client signature. Blockbody3 includes three types of information: 1) Information about the vessel crossing the bridge: bridge identification code, vessel identification code, and the time the vessel passed through the bridge; 2) Current bridge monitoring data: hydrological data, meteorological data, and photographic data; 3) Current vessel monitoring data: current deposit amount and number of collisions.

5. The blockchain-based bridge information-based collision avoidance method according to claim 1, characterized in that, Methods for determining whether a vessel is at risk of collision include: By acquiring collision information, bridge information, and ship information from three blockchains, the risk assessment value is calculated based on a pre-built collision risk assessment model. Determine if the risk assessment value exceeds the preset value. If so, there is a collision risk, and an alarm message will be generated.

6. The blockchain-based bridge information-based collision avoidance method according to claim 1, characterized in that, Each time a ship safely passes under a bridge or collides with it, a new record is generated. If it is a collision, the collision count is incremented by 1, the deposit is reduced by a certain amount, and the information is written into the bridge ship passage information blockchain Chain3. If there is no collision, the count remains unchanged, and the deposit amount remains unchanged. The deposit is in the form of central bank digital currency.

7. A blockchain-based bridge information-based collision avoidance system, characterized in that, include: Blockchain building blocks are used to pre-establish a unified identity code for bridges joining the blockchain; And construct a bridge blockchain Chain1, a ship blockchain Chain2, and a bridge ship passage information blockchain Chain3 to store ship information; The bridge crossing monitoring module is used to obtain the identity code of the vessel entering the monitoring area and sense the real-time information of the vessel. Together with the vessel information in the vessel blockchain Chain2, the current bridge information or the bridge information in the bridge blockchain Chain1, it is written into the bridge vessel crossing information blockchain Chain3. The information written into the bridge vessel crossing information blockchain Chain3 is signed with the private key corresponding to the pre-obtained bridge identity code. The collision analysis module is used to compare the real-time information of the sensed ships with the corresponding bridge information to determine whether there is a collision risk. If so, a collision warning is issued to the corresponding ship. If a collision still occurs after the warning, a certain amount of the pre-deposited ship deposit is deducted and written into the bridge ship passage information blockchain Chain3.

8. A blockchain-based bridge information-based collision avoidance system, characterized in that, include: The bridge client, installed on the bridge server, is used to generate the bridge identity code and its public and private keys, and to read and write the pre-built bridge blockchain Chain1 for storing bridge information and the pre-built bridge and ship passage information blockchain Chain3 for storing passage information. The ship registration client is used to generate ship identification codes and their public and private keys, and to read and write the pre-built ship blockchain Chain2 used to store ship information; The bridge client is also used to: obtain the identity code of the vessel entering its monitoring area, sense the real-time information of the vessel, and write it together with the vessel information in the vessel blockchain Chain2, the current bridge information, or the bridge information in the bridge blockchain Chain1 into the bridge vessel passage information blockchain Chain3; sign the information written into the bridge vessel passage information blockchain Chain3 with the private key corresponding to the pre-obtained bridge identity code; compare the sensed real-time information of the vessel with the corresponding bridge information to determine whether there is a collision risk; if so, issue a collision warning to the corresponding vessel; if a collision still occurs after the warning, deduct a certain amount of the pre-deposited vessel deposit and write it into the bridge vessel passage information blockchain Chain3.

9. The blockchain-based bridge information-based collision avoidance system according to claim 8, characterized in that, in, The data structure of the bridge blockchain Chain1 includes a block header (Blockhead1) and a block body (Blockbody1). The block header (Blockhead1) includes the hash value of the previous block header, the hash value of the current block, and the signature of the bridge registration client. The block body (Blockbody1) stores the bridge information corresponding to the bridge identity code, including the bridge identity code, bridge name, construction time, bridge construction unit, bridge management unit, bridge ownership unit, bridge height, and bridge width. The data structure of the ship blockchain Chain2 includes a block header (Blockhead2) and a block body (Blockbody2). The information in the block header (Blockhead2) includes the hash value of the previous block header, the hash value of the current block, and the ship registration client signature. Blockbody2 stores the ship information corresponding to the ship identification code, including the ship identification code, ship name, construction time, ship owner unit, ship height, ship width, and maximum speed. The data structure of the blockchain Chain3 for bridge and vessel passage information includes a block header (Blockhead3) and a block body (Blockbody3). The information in the block header (Blockhead3) includes the hash value of the previous block header, the hash value of the current block, and the bridge client signature. Blockbody3 includes three types of information: 1) Information about the vessel crossing the bridge: bridge identification code, vessel identification code, and the time the vessel passed through the bridge; 2) Current bridge monitoring data: hydrological data, meteorological data, and photographic data; 3) Current vessel monitoring data: current deposit amount and number of collisions.

10. A computer storage medium, characterized in that, It contains a computer program that can be executed by a processor, which performs the blockchain-based bridge information-based collision avoidance method as described in any one of claims 1-6.

Images