A shore-based data exchange and relay enhancement system based on ship networking blockchain architecture

By introducing shore-based data exchange and relay enhancement systems into the ship networking system, using relay nodes and blockchain technology, the problem of instability between ships is solved, the stability and security of data transmission is improved, and the stability and security of data transmission are ensured. Timely transmission and reliability of information.

CN118590851BActive Publication Date: 2024-11-26SANYA SCI & EDUCATION INNOVATION PARK WUHAN UNIV OF TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411067150.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-06
Publication Date
2024-11-26
Estimated Expiration
2044-08-06

AI Technical Summary

Technical Problem

The lack of stable data transfer in the ship networking system causes the ship to be unable to obtain information about the surrounding ships and environment in a timely manner, affecting the data transmission performance and reliability.

Method used

Design a shore-based data exchange and relay enhancement system with a ship networking blockchain architecture. By deploying relay enhancement nodes on shore-based and islands, using digital certificates and encryption technology to ensure the security and stability of data transmission, and through the zone Blockchain technology maintains the trustworthiness and verifiability of data. The system includes Type-I nodes (ship terminals) and Type-II nodes (relay nodes). Type-II nodes are responsible for receiving and forwarding data, establishing a stable P2P network, and making up for weak connections in the ship network.

Benefits of technology

It improves the stability and security of data transmission in the ship networking system, ensures the timeliness and reliability of data, and avoids the forking and trust problems caused by data delays in blockchain applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118590851B_ABST
    Figure CN118590851B_ABST
Patent Text Reader

Abstract

The present invention relates to a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, the system is established on the basis of the ship networking, the ship networking is used to support data to form point-to-point data exchange between ship / shore-based nodes; the nodes are mainly divided into two types, one is a natural communication node, called Type-I node; the other is a relay node for communication enhancement, called Type-II node; Type-II node is used to make up for weak connections in the ship networking; both types of nodes must apply for digital certificates from the maritime trust center MTA, the public key carried on the certificate and the matching private key are generated by the node according to the requirements of the MTA, and the identity information and identification of the node in the P2P network are statically bound to the digital certificate. The use of the method of adding relay enhancement nodes to transfer data ensures that each node in the entire ship networking can continuously obtain and update data, and the present invention also ensures the stability, efficiency, security and reliability of data transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of ship networking data exchange and blockchain technology, and in particular to a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture. Background Art

[0002] Ship networking is a network system formed by connecting a series of digital entities in ships and shore-based facilities. It is usually composed of ship-borne equipment, navigation environment, and sensing or data transmission nodes in shore-based facilities. It is combined into a heterogeneous network through multiple communication methods based on space or on the water surface to provide real-time exchange of dynamic information for ship navigation and other services. Blockchain program applications can be executed on the ship networking terminal, including credit points between ships, carbon footprint records, carbon trading, ship navigation event notifications, etc.

[0003] There are two ways of communication between ships and ships, and between ships and shores. One is short-range opportunistic communication between ships and other surface targets (ships, navigation marks, etc.). Candidate communication technologies include VHF / VDES, etc.; the other is a stable connection communication method based on long-distance digital communication and static shore-based stations, usually satellite communication. The communication link formed by these two types of communication methods establishes a physical layer channel for data exchange between the two entities, and then forms a ship network through a wider interconnection. Since ships need to frequently exchange data with the outside world during normal navigation, this information exchange with the outside world needs to be maintained in a continuous, stable and reliable state for a long time. However, most of the nodes in each entity of the ship network are composed of mobile ships. The frequent changes in the network topology result in the data transmission performance quality on the ship network being far inferior to the Internet, which is based on optical fiber, 4G / 5G to form a stable and continuous data interaction.

[0004] Therefore, in order to improve the stability and security of the blockchain system in the ship network, it is urgent to study a method for data enhancement transmission for blockchain applications on the ship network. Summary of the invention

[0005] The present invention provides a shore-based data exchange and enhancement system for maritime regulatory agencies, sailing ships, etc., which serves the blockchain architecture of ship networking. The present invention designs and adds a type of relay enhancement node to the existing water / marine transportation system. The node only serves as the forwarding and transmission function of data, and the ship terminal performs blockchain calculations. Digital certificates and encryption technology are used throughout the system operation to ensure the security and stability of data forwarding. At the same time, blockchain technology is used to maintain the credibility and traceability of data, so as to solve the problems existing in the existing water / marine transportation system and ensure the real-time, reliability and auditability of data exchange between various physical nodes.

[0006] The main technical problem solved by the present invention is as follows: the current alternative communication technologies between ships mainly include AIS, VDES, satellite communication, etc., and such communications are only temporary information exchanges with nearby ships or shore-based systems. Such data exchanges lack stable data transfer in the current ship networking system, resulting in the inability of ships to obtain information about surrounding ships and the environment in a timely manner.

[0007] The present invention adopts a technical solution to solve the above-mentioned technical problems: a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, whose main features include: data packet encryption process, data packet forwarding and verification process, and blockchain operation calculation.

[0008] The system mainly includes trading entities: ships, Maritime Trust Authority (MTA), Maritime Supervision Authority (MSA), Shore Control Center (SCC), Maritime Certificate Authority (MCA), Maritime Registration Authority (MRA). These entities need to apply for digital certificates from the Maritime Trust Authority (MTA) and bind the obtained digital certificates to their own identities as credentials for subsequent data forwarding and authentication.

[0009] The digital certificate of each entity contains the following contents: the version number of the certificate, usually the X.509 version, the serial number of the certificate, the unique identifier of the certificate, the identifier of the MTA signature algorithm, the name of the issuing certificate authority MTA, and the identity information of the entity, that is, the unique identifier IMO i , the entity's public key information PubKey i , the version of the hash algorithm, encryption algorithm and signature algorithm used in the certificate, the validity period of the certificate, and the MTA uses its own private key to sign the summary obtained by hashing the entire digital certificate. i Represents an entity i ;

[0010] Digital certificate application process:

[0011] 1. Each entity needs to generate its own key pair (PubKey i , PriKey i ), that is, each entity needs to generate a public-private key pair before applying for a certificate;

[0012] 2. Each entity sends the Maritime Certificate Signing Request (MCSR) and public key generated by itself to the Maritime Certificate Registration Authority (MRA), and retains the private key;

[0013] 3. MRA reviews the application documents of each entity certificate request. After the review is passed, the user information and MCSR file will be sent to the Maritime Certificate Authority (MCA). MCA will digitally sign according to the user's public key and user information content, and finally generate a digital certificate;

[0014] 4. MCA issues the digital certificate to the entity that applied. For the Maritime Trust Center MTA, their digital certificate is a self-signed certificate, representing the highest trust authority.

[0015] The system is established on the basis of ship networking, and provides enhanced data transmission facilities for the application of blockchain on ship networking; wherein, the ship networking is used to support point-to-point data exchange between ship / shore-based nodes, and the data exchange forms a data coverage network on the ship networking; the nodes are mainly divided into two types, one is a natural communication node, including a ship-borne terminal and a shore-based station, and running a blockchain program, called a Type-I node; the other is a relay node for communication enhancement, which is set on land or islands and provides stable data exchange assistance for natural communication nodes, called a Type-II node; the Type-I node is also called a blockchain terminal, and the applications based on blockchain include navigation event notifications, ship reputation value updates, and ship carbon trading accounting, etc., and the Type-II node is used to make up for the weak connection in the ship networking; both types of nodes must apply for a digital certificate from the Maritime Trust Center MTA, and the public key carried on the certificate and the matching private key are generated by the node according to the requirements of the MTA, and the identity information and identification of the node in the P2P network are statically bound to the digital certificate, while the location of the node in the physical space and the network layer address are not required to be fixed.

[0016] As a further technical solution of the present invention, MTA manages Type-I and Type-II node certificates, including application, issuance and revocation of certificates; the public and private key pairs of Type-I and Type-II nodes are generated locally by the nodes themselves; the digital certificate of each node contains: the version number of the certificate, usually the X.509 version, the serial number of the certificate, the unique identifier of the certificate, the identifier of the MTA signature algorithm, the name of the issuing certificate authority MTA, and the identity information of the entity, that is, the unique identifier IMO i , the entity's public key information PubKeyi , the versions of the hash algorithm, encryption algorithm and signature algorithm used in the certificate, the validity period of the certificate, and the MTA uses its own private key to sign the summary obtained by hashing the entire digital certificate.

[0017] As a further technical solution of the present invention, in this system, the communication system of the ship is a vital part in the field of navigation, which can realize information exchange and data transmission between ships and between ships and shore facilities. The communication means of the system are divided into short-range opportunistic communication and a stable connection communication method based on long-range digital communication and static shore-based sites; the short-range opportunistic communication refers to a random self-organizing (Ad-hoc) communication link that can be supported by the physical proximity between communication terminal devices, that is, when two terminal devices are within a sufficiently close distance, data transmission and information exchange are carried out through short-range wireless communication technology, which is mainly used for data transmission and information exchange between ships or between ships and targets such as navigation marks. Candidate communication technologies include VHF / VDES, etc.; the long-range digital communication refers to a long-distance communication method established via satellite links between ships on the water and between ships and shore facilities. Its communication links mainly include satellite communications such as VDES-SAT and Inmarsat, etc. The establishment of this communication method is agreed upon in advance and clearly by all participating parties;

[0018] Type-II nodes are responsible for receiving and forwarding data from Type-I nodes, and forwarding data to other Type-I or Type-II nodes through a dedicated network or the Internet, thereby enhancing communication. The Type-II nodes establish a P2P network on land or islands to achieve data forwarding between nodes. The communication link between Type-II nodes is generally based on a fiber optic backbone network. The P2P network between Type-II nodes enables data between ships to not only be transmitted through surface communication equipment, but also to be assisted in forwarding through relays between stations, thereby achieving more efficient and reliable data transmission and communication.

[0019] As a further technical solution of the present invention, the link relationships between Type-I and Type-II nodes include the following four types, and these bidirectional connection relationships constitute a mixed P2P network in the entire system:

[0020] Type-I short-range links between nodes: opportunistic, temporary connections between nodes that occur in close proximity, including links temporarily established when two ships meet or follow each other. The short-range links provide temporary data exchange and serve the message forwarding in the blockchain during the life cycle of the links. However, their life cycle is short and they only exist during brief contact between nodes.

[0021] Long-distance links between Type-I nodes: temporary communication connections established by satellite links, mainly serving ordinary maritime services. Typical applications include information transmission between Type-I shore-based and ship-borne nodes, including navigation notices and climate information. The long-distance links carry messages in the blockchain during their life cycle. When the ordinary maritime service session is completed, the long-distance links will be closed and cannot bear the P2P connection of the blockchain.

[0022] Stable link between Type-I node and Type-II node: Type-II node has a relatively static network address, and the connection between the two is stable and continuous; in the stable link between Type-I node and Type-II node, Type-I node maintains a stable communication link with certain known Type-II nodes based on the principle of proximity and trust, relying on satellite network or shore-based optical fiber network, fully serving blockchain applications;

[0023] Stable links between Type-II nodes: Type-II nodes are all built on shore, land or islands. Type-II nodes establish fast connections through the fiber optic backbone network, fully serving blockchain applications and providing support for fast data exchange between nodes.

[0024] As a further technical solution of the present invention, all blockchain-related calculations are completed on Type-I nodes, including transaction verification, consensus algorithms and smart contracts. If it is difficult for a Type-I node to find a good P2P neighbor node in the surrounding area (such as the only ship in a vast sea area), the node selects a Type-II node and maintains a stable connection with it, even if this Type-II node may not be a node adjacent to it in space, to perform two-way data forwarding and join the P2P network. A stable connection is often established with a Type-II node through a satellite link, and the Type-I node can use the node as a relay to perform two-way data forwarding and join the entire P2P network. In this way, even if there are not enough good P2P neighbor nodes around the Type-I node, its activity and participation in the blockchain network can be maintained.

[0025] It is worth noting that a Type-I node can also always maintain a connection with a Type-II node, regardless of whether it has other Type-I neighbor nodes with good links. This connection relationship is established to ensure that the Type-I node can maintain contact with the blockchain network under any circumstances and complete its tasks in a timely manner.

[0026] As a further technical solution of the present invention, conventional blockchain node programs are run between Type-I nodes, and the supported application functions include navigation event notification, ship reputation value update and ship carbon trading accounting, etc. The blockchain program on each Type-I node performs inter-node communication according to the built-in protocol, including neighbor node discovery, block message broadcasting and message rumors;

[0027] Type-II provides enhanced transmission services for data messages for Type-I nodes. There are two types of blockchain messages sent by Type-I: one with a clear destination Type-I node network address, and the other is a flooding type without a specific Type-I network address.

[0028] Each Type-I node has its own message forwarding table. For the first type of single-hop forwarding table, the Type-I node queries the corresponding network address in the forwarding table through the next-hop ID. This node can be a Type-I node or a Type-II node, and then queries the network address of the destination node Type-I through this transit node and forwards it to this address.

[0029] For flooding, for data packets transmitted between Type-I nodes according to the blockchain's own protocol, if the Type-I node cannot transmit the packet to the destination Type-I node directly connected to itself in one hop, the packet will be transmitted to the Type-II node that maintains a high-quality connection with itself, and the Type-II node will perform enhanced forwarding. That is, the Type-II node receives data packets from the Type-I node, and uses its high-quality connection capabilities to forward these packets to the destination Type-I node. This mechanism ensures that even if the direct connection between Type-I nodes is unavailable or insufficient to transmit certain packets, the entire network can still efficiently transmit and exchange data.

[0030] As a further technical solution of the present invention, the link established between the Type-II node and other nodes (Type-I, Type-II) adopts two working modes; ordinary mode and VPN pipeline mode; ordinary mode means that the data forwarding between the two nodes follows the usual direct message sending and receiving, such as through TCP or UDP protocol; VPN pipeline mode means maintaining a stable and long-term link between the two nodes and establishing a VPN protocol on it, typically through IPSec, the blockchain message to be forwarded is transmitted in the VPN pipeline, and the key negotiation for establishing VPN is calculated and updated by the public and private keys of the nodes at both ends of the link, and the public and private keys of the nodes are specified by the digital certificate issued by the MTA to the node. Specifically, the key negotiation process for establishing VPN is the responsibility of the nodes at both ends of the link. The nodes will use their own public and private keys to exchange keys with each other to ensure the security and privacy protection of communication. The validity and legitimacy of these public and private keys are usually specified by the digital certificates issued by the MTA. Through the VPN pipeline mode, nodes can transmit data in a more secure and reliable communication environment to protect the data security and integrity of the blockchain network.

[0031] How to quickly find the network address of nodes between nodes, each Type-II node maintains the application layer message forwarding table, which is used to enhance the forwarding of blockchain messages to Type-I nodes. The application layer forwarding table contains the following contents: It is usually used to guide the routing selection of data packets at the application layer. It contains a series of entries, each of which describes a path or forwarding rule from the source node to the destination node.

[0032] As a further technical solution of the present invention, each Type-II node needs to maintain an application layer message forwarding table to enhance the forwarding of blockchain messages to Type-I nodes, with the following features:

[0033] 1. If the blockchain protocol message received by this Type-II node has a clear destination Type-I node, and the destination Type-I node is directly connected to itself, the blockchain protocol message is directly forwarded to the destination Type-I node;

[0034] 2. The entries in the Type-II node forwarding table are a series of destination addresses that are Type-I node identifiers and their network addresses, and the next-hop forwarding nodes are other Type-II nodes directly connected to this Type-II node; when the blockchain protocol message received by this Type-II node, if there is a clear destination Type-I node and it can be found in the forwarding table, it is forwarded according to the known forwarding table. If it cannot be found, it is randomly flooded to a maximum of WIDTH neighboring Type-II nodes directly connected to this Type-II node; if the blockchain protocol message itself is a flooding message, there is no clear destination Type-I node and its address, and it is randomly forwarded to a maximum of WIDTH neighboring Type-I and Type-II nodes directly connected to this Type-II node; the number of known neighbors selected in the flood forwarding, WIDTH, is called the flood width, which is a preset constant of the system;

[0035] 3. If a blockchain protocol message with a specific destination Type-I node still cannot be forwarded to the destination node after DEPTH flooding forwarding in a Type-II node, it will be discarded; if a flooding message without a specific destination Type-I node is forwarded DEPTH times in a Type-I or Type-II node, it will also stop forwarding; DEPTH is a preset constant of the system;

[0036] 4. Adjacent Type-II nodes regularly exchange and update their application layer message forwarding tables; in order to avoid message forwarding loops, no two nodes can forward messages in the reverse direction, that is, when node A forwards a message to node B, node B is not allowed to forward the message in the reverse direction to node A; if, due to some accident, any node receives multiple copies of a blockchain protocol message, the second and subsequent messages will be discarded immediately, that is, any blockchain protocol message can only be processed by one node once (including single forwarding and flooding forwarding), and the message identity is determined by the hash value of the message;

[0037] 5. The blockchain protocol message forwarding method adopts the normal mode or VPN pipeline mode, both of which include the several processes described above to ensure the security and reliability of the network.

[0038] As a further technical solution of the present invention, the blockchain program is run between Type-I nodes. If a Type-I node is a ship, the blockchain protocol message it sends has a reserved public information field, including IMO i |MMSI i |LOC i |TimeStamp, which IMO i Indicates ship iIMO number; MMSI i Indicates ship i MMSI number; dynamic information: LOC i =(Lat i, Lon i ) means ship i The real-time location information of the ship can be obtained by using the TimeStamp, which is the current timestamp. The dynamic information can be forwarded by the Type-II node's forwarding table. For example, when performing flood forwarding, the Type-II node can select certain neighbors for flood forwarding based on the geographic information carried on the blockchain protocol. In this way, the ship node can provide its current location information to other nodes through the blockchain network, helping network nodes to transmit information and select routes more efficiently.

[0039] Compared with the prior art, the present invention has the following beneficial effects:

[0040] 1. Improved the stability of data transmission in the ship networking system. By deploying relay enhancement nodes Type-II on shore and islands, and using relay nodes to transfer data, the stability of data transmission of Type-I nodes (mainly ship nodes) in the ship networking system is ensured, which makes up for the current situation of insufficient opportunistic communication faced by ships during ocean voyages. Relay enhancement nodes can also be used to obtain surrounding information in a timely manner. At the same time, it provides the timeliness and stability of data for the application of blockchain in ship networking, avoiding the lack of consensus and trust problems caused by the bifurcation phenomenon caused by data delay in blockchain applications.

[0041] 2. Improve the security of data in the ship networking system. By combining blockchain technology and digital encryption technology, it is ensured that there is an encryption verification process when data is transferred between Type-I and Type-II nodes, avoiding the shortcomings of encryption technology in existing maritime technology, and ensuring the security of data during transfer and the identity verification process between nodes. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A structural schematic diagram of a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture provided by the present invention.

[0043] Figure 2 It is the message forwarding table of the system in the embodiment of the present invention. DETAILED DESCRIPTION

[0044] The technical solution of the present invention is further described in detail below in conjunction with specific implementation methods.

[0045] With reference to the accompanying drawings- Figure 1 to Figure 2The present invention further describes the process of the present invention. It is particularly noted that unless otherwise specifically described, the operation flow, presentation form and numerical calculation of the nodes and implementation steps described in the embodiments of the present invention do not limit the scope of the present invention. The specific embodiments described in the present invention are only used to explain the present invention and are not used to limit the present invention.

[0046] Figure 1 As shown, the present invention is a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, and the system mainly includes trading entities: ships, Maritime Trust Authority (MTA), Maritime Supervision Authority (MSA), Shore-based Remote Control Center (SCC), Maritime Certificate Authority (MCA), Maritime Registration Authority (MRA). These entities need to apply for digital certificates from the Maritime Trust Center MTA, and bind the obtained digital certificates to their own identities as credentials for subsequent data forwarding and authentication.

[0047] The system is established on the basis of ship networking, and provides enhanced data transmission facilities for the application of blockchain on ship networking; wherein, the ship networking is used to support point-to-point data exchange between ships / shore-based nodes, and the data exchange forms a data coverage network on the ship networking; the nodes are mainly divided into two types, one is a natural communication node, including a ship-borne terminal and a shore-based station, and running a blockchain program, called a Type-I node; the other is a relay node for communication enhancement, which is set on land or islands and provides stable data exchange assistance for natural communication nodes, called a Type-II node; the Type-I node is also called a blockchain terminal, and the applications based on blockchain include navigation event notifications, ship reputation value updates and ship carbon trading accounting, and the Type-II node is used to make up for the weak connection in the ship networking; both types of nodes must apply for a digital certificate from the Maritime Trust Center MTA, and the public key carried on the certificate and the matching private key are generated by the node according to the requirements of the MTA, and the identity information and identification of the node in the P2P network are statically bound to the digital certificate, while the location of the node in the physical space and the network layer address are not required to be fixed. In this example, unless otherwise specified, the Type-I node refers to a ship by default.

[0048] All nodes need to submit their identity information including their public key information to the Maritime Trust Center MTA. The entire process is an offline operation. It is divided into 4 steps: ① Transaction entity i You need to generate your own key pair locally on the client (PubKey i , PriKey i ) ; ② Each entity sends the maritime certificate signature application file MCSR and public key generated by itself to the Maritime Certificate Registration Center MRA, and retains the private key; ③ MRA reviews the application documents of each entity certificate request, and after the review is passed, the user information and MCSR file are sent to the Maritime Certificate Authority MCA. MCA digitally signs according to the user public key and user information content, and finally generates a digital certificate; ④ MCA issues the digital certificate to the entity that applied i For the Maritime Trust Authority (MTA), their digital certificates are self-signed certificates, representing the highest trust authority.

[0049] In the present invention, MTA manages Type-I and Type-II node certificates, including certificate application, issuance and revocation; the public and private key pairs of Type-I and Type-II nodes are generated locally by the nodes themselves; the digital certificate of each node contains: the version number of the certificate, usually the X.509 version, the serial number of the certificate, the unique identifier of the certificate, the identifier of the MTA signature algorithm, the name of the issuing certificate authority MTA, and the identity information of the entity, that is, the unique identifier IMO i , the entity's public key information PubKey i , the versions of the hash algorithm, encryption algorithm and signature algorithm used in the certificate, the validity period of the certificate, and the MTA uses its own private key to sign the summary obtained by hashing the entire digital certificate.

[0050] In order to facilitate those skilled in the art to better understand the technical solution of the present invention, specific embodiments of the present invention are given as follows:

[0051] like Figure 1 Divided into near-shore ships and ocean-going ships, there are three types of weak connections, which only serve ordinary maritime business, that is, short-term data exchange.

[0052] 1) A nearshore ship A can establish a temporary P2P network with its neighboring ships B and C within the opportunistic communication range. During this opportunistic network process, the ship can participate in the data exchange process. However, this opportunistic communication is unstable and is only possible in waters where ships are concentrated and the communication radius is within a certain range. This exchange is temporary, so the connection between them is a weak connection.

[0053] 2) For ship D, it is in nearshore waters and does not have opportunistic communication with neighboring ships, but it remains within the communication range with the shore-based center and can exchange data. However, this data exchange is also temporary, that is, a weak connection.

[0054] 3) For ships E and F far away from the shore (or island) waters, since the distance between them exceeds the communication radius of the opportunistic network, if temporary data interaction is required, they can establish a temporary communication link through satellite N.

[0055] The above three situations can only solve the temporary data exchange process between ships. For the blockchain application serving the ship network, in order to maintain the stability and integrity of data exchange, the present invention innovatively proposes a type of relay enhancement node Type-II. Figure 1 , discusses in detail the different scenarios corresponding to the process operation of the shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, so as to adapt to the timely exchange of information by ships at different locations at sea:

[0056] All data exchanges in this system are subject to digital certificate verification and data packet verification. Taking ship A and ship B as an example, the verification process of other subsequent nodes is the same as this example. The following is a detailed explanation:

[0057] (1) Digital certificate verification process

[0058] 1. The sender ship A has its own public-private key pair (PubKey A , PriKey A );

[0059] 2. The receiving ship B obtains the digital certificate of the sending ship A (Cert A ), which contains the public key PubKey of the sender ship A A And the digital signature SIG issued by the Maritime Trust Center MTA MTA ;

[0060] 3. The receiving ship B uses the public key PubKey of the maritime trust center MTA MTA To verify the digital signature and ensure the authenticity and integrity of the certificate.

[0061] (2) Data packet verification process

[0062] 1. The sender ship A uses its own private key (PriKey A ) to sign the data packet and generate a digital signature (SIG A );

[0063] 2. After receiving the data packet and digital signature, the receiving ship B uses the public key (PubKey A ) Verify the digital signature to ensure the integrity and authenticity of the data packet.

[0064] All information will be hashed during the verification process. The verification of the digital certificate ensures the authenticity and integrity of the sender A's public key to prevent man-in-the-middle attacks. The digital signature verification of the data packet ensures that the data has not been tampered with during transmission, preventing data forgery and tampering attacks.

[0065] Figure 1 The relay enhancement node Type-II in the system plays the role of stable data forwarding in the system. According to factors such as communication range and geographical environment, it is mainly deployed on the shore or island. A stable and fast P2P network is established between the relay enhancement nodes through optical fiber or submarine optical cable to receive and transfer data from Type-I and Type-II nodes. Generally, the connection will not be disconnected. At the same time, the relay enhancement node Type-II needs to maintain and update a message forwarding table to facilitate the search for the target address and forwarding address.

[0066] Type-I is a natural communication node, which is the terminal of blockchain operation, usually a ship. Supported application functions include navigation event notification, ship reputation value update, ship carbon trading accounting, etc. The blockchain program on the ship nodes A, B, C, D, E, and F in the figure communicates between nodes according to the built-in protocol, including neighbor node discovery, blockchain message broadcast, message rumors, etc.

[0067] Figure 1 Ship nodes A, B, C, D, E, and F can send two types of blockchain messages: 1. One is based on a forwarding path with a clear node network address; 2. A flooding type, forwarding without a specific node network address. For data messages transmitted between Type-I nodes according to the blockchain's own protocol, if the Type-I node cannot transmit a message to the destination Type-I node directly connected to it in one hop, it can transmit these messages to the Type-II node that maintains a high-quality connection with itself, and this Type-II node will perform enhanced forwarding.

[0068] Scenario 1: Ship C and Ship F perform stable single-hop data exchange

[0069] There is a one-hop connection between ship C and ship F. Ship C finds the unique identifier IMO of the next-hop Type-II node L closest to itself through its own single-hop destination forwarding table. Land network address 192.168.100.120; then, Type-II node L finds the unique identity of ship F, IMO, according to its own global message forwarding table F and network address 192.168.100.131; finally, the data exchange process is completed. This process includes the entity identity verification process and data verification process.

[0070] Scenario 2: Ship C and Ship E perform stable flooding data exchange

[0071] For ship C, when it is difficult for ship C to find a good P2P neighbor node in the surrounding area (such as the only ship in a vast sea area), ship C uses its own message forwarding table to find the unique identity of the next-hop Type-II node L closest to itself. L and network address 172.17.101.121; then, Type-II node L finds the unique identity IMO of the next-hop Type-II node K, J, H, G according to the flooding destination forwarding table K 、IMO J 、IMO H 、IMO G And network addresses 172.18.102.132, 172.25.104.127, 192.168.31.111, 192.168.63.133; then, a stable communication link is established through the satellite M to complete the data exchange process with the ship E. This process includes the entity identity verification process and the data verification process.

[0072] There are two working modes for the links established between Type-II nodes and ships, and between Type-II and Type-II nodes, one is the normal mode and the other is the VPN pipeline mode. The normal mode is to directly forward data between two nodes through TCP or UDP protocol; the VPN pipeline mode means to maintain a stable and long-term link between two nodes, and the blockchain messages to be forwarded are transmitted in the VPN's proprietary pipeline. The key negotiation for establishing VPN is calculated and updated by the public and private keys of the nodes at both ends of the link, and the public and private keys of the nodes are specified by the digital certificates issued by the MTA to the nodes.

[0073] Any ship i All blockchain protocol messages sent contain public information fields: IMO i |MMSI i |LOC i |TimeStamp, IMO i (Unique Identifier), MMSI i Indicates ship i Identity information; LOC i= (Lat i, Lon i ) means ship i The current longitude and latitude information plays a key role in the subsequent blockchain services. It is for Type-II nodes to select certain neighbors for flood forwarding based on the geographic information carried in the blockchain protocol. In addition, there are some data packet information Data i , mainly providing some maritime services: event notification, credit value, carbon trading accounting, etc.

[0074] If the ships are close to the concentrated waters, non-blockchain related services, such as the forwarding and verification of temporary maritime information data, can be carried out directly through the opportunistic network without the help of satellites or relay enhancement nodes Type-II.

[0075] When there is information about blockchain business, in order to ensure that the blockchain message has a public blockchain ledger for each ship node in the entire maritime system, all data needs to be transferred through the Type-II node and forwarded to the Type-I node (ship). For blockchain business, each Type-II node needs to maintain the application layer message forwarding table to enhance the forwarding of blockchain messages to the Type-I node (ship). The main methods are as follows:

[0076] 1. When a Type-II node receives a blockchain protocol message, if the message explicitly specifies the target Type-I node and is directly connected to the Type-II node, then the node will directly transmit the message to the target Type-I node.

[0077] 2. The forwarding table of the Type-II node includes a series of entries whose target address is the Type-I node identifier and its network address, as well as the next node to be forwarded to, which is another Type-II node directly connected to this Type-II node. When a Type-II node receives a blockchain protocol message and it can find a clear target Type-I node in the forwarding table, it will forward it based on the known forwarding table information. If the target cannot be found, up to WIDTH directly connected neighbor Type-II nodes will be selected for broadcast forwarding. In the case of flooding, if the message itself does not contain a clear target Type-I node and address, up to WIDTH directly connected neighbor Type-I and Type-II nodes will be randomly selected for forwarding.

[0078] 3. For blockchain protocol messages with specific target Type-I nodes, if they still fail to reach the target node after DEPTH flooding propagation, they will be discarded. For flooding messages with non-specific targets, they will also stop propagating after DEPTH flooding propagation. DEPTH is a system preset constant.

[0079] 4. Adjacent Type-II nodes regularly exchange and update their application layer message forwarding tables. In order to prevent message forwarding from forming loops, reverse forwarding is not allowed between nodes. If a node receives multiple copies of the same blockchain protocol message, all subsequent copies except the first will be discarded. Blockchain protocol messages are only allowed to be processed once, including single forwarding and flooding propagation, and their uniqueness is determined by the hash value of the message.

[0080] 5. Message forwarding can adopt normal mode or VPN pipe mode.

[0081] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0082] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A shore-based data exchange and relay enhancement system based on the blockchain architecture of ship networking, It is characterized in that The system is built on the basis of the ship networking, and provides enhanced data transmission facilities for the application of blockchain on the ship networking; wherein, the ship networking is used to support point-to-point data exchange between ships / shore-based nodes, and the data exchange forms a data coverage network on the ship networking; the ship / shore-based nodes are mainly divided into two types, one is a natural communication node, including a ship-borne terminal and a shore-based station, and running a blockchain program, called a Type-I node; the other is a relay node for communication enhancement, which is set on land or islands and provides stable data exchange assistance for natural communication nodes, called a Type-II node; the Type-I node is also called a blockchain terminal, and the applications based on blockchain include navigation event notifications, ship reputation value updates and ship carbon trading accounting, and the Type-II node is used to make up for the weak connection in the ship networking; both types of nodes must apply for a digital certificate from the Maritime Trust Center MTA, and the public key carried on the certificate and the matching private key are generated by the node according to the requirements of the MTA, and the identity information and identification of the ship / shore-based node in the P2P network are statically bound to the digital certificate, while the location of the node in the physical space and the network layer address are not required to be fixed; The communication means of the system are divided into short-range opportunistic communication and long-range digital communication; the short-range opportunistic communication refers to a random self-organizing communication link that can be supported by the physical proximity between communication terminal devices, that is, when two terminal devices are within a sufficiently close distance, data transmission and information exchange are carried out through short-range wireless communication technology; the long-range digital communication refers to a long-distance communication method established via satellite links between ships on the water and between ships and shore facilities, and its communication links include satellite communications, and the satellite communications include VDES-SAT and Inmarsat; Type-II nodes are responsible for receiving and forwarding data from Type-I nodes, and forwarding data to other Type-I or Type-II nodes through a dedicated network or the Internet, thereby enhancing communication. The Type-II nodes establish a P2P network on land or islands to achieve data forwarding between nodes, and the communication link between Type-II nodes is based on a fiber optic backbone network.

2. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that MTA manages Type-I and Type-II node certificates, including certificate application, issuance and revocation. The public and private key pairs of Type-I and Type-II nodes are generated locally by the nodes themselves. The digital certificate of each node contains the following contents: certificate version number, certificate serial number, certificate unique identifier, MTA signature algorithm identifier, MTA name of the issuing certificate authority, entity identity information, entity public key information PubKey, hash algorithm used in the certificate, encryption algorithm and signature algorithm versions, certificate validity period, and MTA's signature of the summary obtained by hashing the entire digital certificate using its own private key.

3. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that The link relationships between Type-I and Type-II nodes include the following four types. The bidirectional connection relationship constitutes a mixed P2P network in the entire system: Type-I short-range links between nodes: opportunistic, temporary connections between nodes that occur in close proximity. The short-range links provide temporary data exchange and serve the message forwarding in the blockchain during the life cycle of the links. Long-distance links between Type-I nodes: temporary communication connections established by satellite links, mainly serving ordinary maritime services. The long-distance links carry messages in the blockchain during their life cycle. When the ordinary maritime service session is completed, the long-distance links will be closed and cannot bear the P2P connection of the blockchain. Stable links between Type-I nodes and Type-II: Type-II nodes have relatively static network addresses; In the stable link between Type-I nodes and Type-II, Type-I nodes maintain stable communication links with certain known Type-II nodes based on the principles of proximity and trust, relying on satellite networks or shore-based optical fiber networks to fully serve blockchain applications; Stable links between Type-II nodes: Type-II nodes are all built on shore, land or islands. Type-II nodes establish fast connections through the fiber optic backbone network, which fully serves blockchain applications.

4. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that All blockchain-related calculations are completed on Type-I nodes: If a Type-I node has difficulty finding a good P2P neighbor node in the surrounding area, the Type-I node selects a Type-II node and maintains a stable connection with it, performs two-way data forwarding and joins the P2P network.

5. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that A Type-I node always maintains a connection with a Type-II node, regardless of whether it has other Type-I neighbors with good links.

6. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that The Type-I nodes run conventional blockchain node programs, supporting application functions including navigation event notification, ship reputation value update and ship carbon trading accounting; the blockchain program on each Type-I node communicates between nodes according to the built-in protocol, including neighbor node discovery, block message broadcast and message rumors; Type-II provides enhanced transmission services for data messages for Type-I nodes. There are two types of blockchain messages sent by Type-I, one with a clear destination Type-I node network address, and the other is a flooding type without a specific Type-I network address. For data message transmission between Type-I nodes according to the blockchain's own protocol, if the Type-I node cannot transmit the message to the destination Type-I node directly connected to itself in one hop, it will transmit the message to the Type-II node that maintains a high-quality connection with itself, and the Type-II node will perform enhanced forwarding.

7. According to claim 4, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that The link established between the Type-II node and other nodes adopts two working modes: normal mode and VPN pipe mode. Normal mode means that the data forwarding between the two nodes follows the usual direct message sending and receiving; VPN pipe mode means maintaining a stable and long-term link between the two nodes and establishing a VPN protocol on it. The blockchain messages that need to be forwarded are transmitted in the VPN pipe. The key negotiation for establishing VPN is calculated and updated by the public and private keys of the nodes at both ends of the link, and the public and private keys of the nodes are specified by the digital certificate issued by the MTA to the node.

8. According to claim 5, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that Each Type-II node needs to maintain an application layer message forwarding table to enhance the forwarding of blockchain messages to Type-I nodes. The features are as follows: If the blockchain protocol message received by this Type-II node has a clear destination Type-I node, and the destination Type-I node is directly connected to itself, the blockchain protocol message is directly forwarded to the destination Type-I node; The entries of the Type-II node message forwarding table are a series of destination addresses that are Type-I node identifiers and their network addresses, and the next-hop forwarding nodes are other Type-II nodes directly connected to this Type-II node; When the blockchain protocol message received by this Type-II node has a clear destination Type-I node and can be found in the forwarding table, it will be forwarded according to the known forwarding table. If it cannot be found, it will be randomly flooded to up to WIDTH neighboring Type-II nodes directly connected to this Type-II node; if the blockchain protocol message itself is a flooding message and there is no clear destination Type-I node and its address, it will be randomly forwarded to up to WIDTH neighboring Type-I and Type-II nodes directly connected to this Type-II node; The number of known neighbors selected in the flood forwarding, WIDTH, is called the flood width, which is a preset constant of the system; If a blockchain protocol message with a specific destination Type-I node still cannot be forwarded to the destination node after DEPTH flood forwarding in a Type-II node, it will be discarded; if a flood message without a specific destination Type-I node is forwarded DEPTH times in a Type-I or Type-II node, forwarding will also stop; DEPTH is a preset constant of the system; Adjacent Type-II nodes regularly exchange and update their application layer message forwarding tables. To avoid message forwarding loops, no two nodes can forward messages in the reverse direction, and any blockchain protocol message can only be processed once by one node. The blockchain protocol message forwarding method adopts normal mode or VPN pipeline mode.

9. According to claim 1, a shore-based data exchange and relay enhancement system of a ship networking blockchain architecture, It is characterized in that The blockchain program runs between Type-I nodes. If a Type-I node is a ship, the blockchain protocol message it sends has a reserved public information field, including IMO i |MMSI i |LOC i |TimeStamp, which IMO i Indicates ship i IMO number; MMSI i Indicates ship i MMSI number; dynamic information: LOC i = (Lat i ,Lon i ) means ship i Real-time location information; TimeStamp is the current timestamp; The dynamic information can serve the routing forwarding of Type-II nodes.