Inter-domain IP traceability alliance system and method based on hierarchical block chain

Through the hierarchical blockchain architecture and the third-party notary mechanism of the smallest public ancestor blockchain, the problem of low throughput and poor scalability in the IP traceability requirements of large-scale networks is solved, and efficient Accurate inter-domain IP traceability improves the trustworthiness and transparency of the system.

CN118984241APending Publication Date: 2024-11-19NORTHEASTERN UNIV AT QINHUANGDAO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411123146.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-15
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

The existing blockchains have low throughput, poor scalability, high false alarm rate and large storage overhead in the inter-domain IP traceability requirements under large-scale networks, which cannot meet the needs of efficient network security and management.

Method used

Adopting a hierarchical blockchain architecture, information synchronization and cross-chain message transmission are carried out through leaf blockchain, intermediate blockchain and root blockchain, to achieve inter-domain IP traceability with high throughput, high accuracy and low storage overhead. Use the smallest public ancestral blockchain as a third-party notary to ensure the atomicity and consistency of cross-affiliated transactions.

Benefits of technology

It improves the system throughput, accuracy and scalability, reduces storage overhead, enhances the system's credibility and transparency, and is suitable for IP traceability requirements under large-scale networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118984241A_ABST
    Figure CN118984241A_ABST
Patent Text Reader

Abstract

The invention provides an inter-domain IP traceability alliance system and method based on a hierarchical block chain, relates to the field of network security and network management, and realizes high throughput, high traceability precision, low storage overhead and expandability. The layered block chain system architecture provided by the invention not only better conforms to an actual network layered structure, but also realizes high throughput and high expandability so as to meet the IP traceability requirement under a large-scale network; a user information synchronization mechanism and a cross-chain message transmission mechanism are provided, so that the problem of non-intercommunication of information among the alliances is solved, and the credibility and transparency of the system are improved; the provided hierarchical inter-domain IP traceability scheme has the advantages of high precision, low storage overhead and expandability; according to the inter-domain IP traceability transaction processing flow based on the hierarchical block chain, the atomicity of cross-alliance traceability transaction is ensured, and the expandability of the system is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the fields of network security and network management, and in particular to an inter-domain IP tracing alliance system and method based on a layered blockchain. Background Art

[0002] With the development of network technology, the Internet has become increasingly complex. The statelessness and anonymity of the IP protocol have caused many problems in network security and network management, including attack source tracing, path verification, fault detection, traffic auditing, and network forensics. For example, attackers can forge the source address field of IP packets at will to conceal their true identity and launch network attacks; abnormal events such as route hijacking, route interruption, and equipment failure seriously affect network operation performance and service quality; traffic auditing can help network administrators analyze abnormal network traffic and respond to network threats and failures in a timely manner; network forensics can help to efficiently collect electronic evidence and hold network violations accountable. However, the statelessness of the Internet cannot meet the conditions for the normal operation of the above network security and network management applications, which brings inconvenience to network security and network management.

[0003] In the face of a huge number of network users, in order to ensure the safe operation of the network and efficient network management, the IP traceability technology at the network layer establishes a tracking mechanism in the network, records key fingerprint information on the forwarding path of IP data packets, and records network traffic fingerprints, thereby changing the stateless nature of the network. Among them, IP traceability based on data flow uses data flow as the carrier and autonomous domain as the traceability unit, which is suitable for autonomous domain-level networks.

[0004] Faced with the user traceability needs of autonomous domain-level networks, the efficient operation of network security and network management applications requires a large amount of collaboration between autonomous domains. The centralized collaboration method relies on trusted third-party nodes to achieve inter-domain IP traceability. However, this method has privacy leakage and single-point bottleneck problems within the autonomous domain, and the autonomous domain’s willingness to collaborate is low. In order to solve the trust problem between autonomous domains and improve the IP traceability collaboration willingness of autonomous domains, the Chinese patent "CN113553617: A cross-domain collaborative traceability system and method based on blockchain" proposes a cross-domain collaborative traceability system based on blockchain. Taking advantage of the decentralization, openness, transparency and trustworthiness of blockchain, it provides technical support for decentralized collaborative traceability of autonomous domains.

[0005] The cross-domain collaborative traceability system proposed by the Chinese patent "CN113553617: A cross-domain collaborative traceability system and method based on blockchain". Although the use of blockchain technology as a support has solved the problem of cross-domain collaborative traceability and improved the IP traceability collaboration willingness of autonomous domains. However, facing the demand for inter-domain IP traceability under large-scale networks, the low throughput and poor scalability of blockchain have become the main performance bottlenecks for large-scale autonomous domain collaborative traceability. It is urgent to improve the scalability of blockchain to meet the needs of inter-domain IP traceability under large-scale networks. In addition, due to design defects, the existing IP traceability solutions have a high false alarm rate and large storage overhead. Summary of the invention

[0006] In view of the deficiencies of the prior art, the purpose of the present invention is to propose an inter-domain IP traceability alliance system and method based on a layered blockchain, wherein the inter-domain IP traceability alliance system based on a layered blockchain consists of layer 0, layer 1 and layer 2;

[0007] The 0th layer includes a plurality of lower-level alliances, the lower-level alliance includes a plurality of autonomous domains of the access layer and an autonomous domain of the tandem layer, the autonomous domain of the tandem layer serves as a monitoring autonomous domain of the lower-level alliance, the autonomous domain of the access layer transmits data to the autonomous domain of the tandem layer, the access layer includes a plurality of autonomous domains at the edge of the network, and the tandem layer includes a plurality of autonomous domains between the edge of the network and the core of the network;

[0008] A low-level alliance also includes a leaf blockchain, which is used to store information about autonomous domains in the low-level alliance, including registration information about autonomous domains. For traceability transactions within the alliance where the sender and the receiver are in the same low-level alliance, the leaf blockchain is also used to reach a consensus on the traceability transactions within the alliance, where the sender is the autonomous domain of the initiator of the traceability transaction within the alliance, and the receiver is the autonomous domain of the receiver of the traceability transaction within the alliance. For cross-alliance traceability transactions where the sender and the receiver are not in the same low-level alliance, after the leaf blockchain reaches a consensus on the cross-alliance traceability transaction, the leaf blockchain in the low-level alliance where the leaf blockchain is located will be recorded. The monitoring autonomous domain of the higher-level alliance is used to send the cross-alliance traceability transactions, the proof of the cross-alliance traceability transactions and the block header of the block where the cross-alliance traceability transactions are located in the lower-level alliance in the form of cross-chain messages to the intermediate blockchain until the minimum common ancestor blockchain. The minimum common ancestor blockchain contains the information summary of the sender corresponding to the cross-alliance traceability transaction and the information summary of the receiver corresponding to the cross-alliance traceability transaction, and has the smallest distance from the blockchain where the sender is located and the blockchain where the receiver is located. The information summary of the autonomous domain includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number in the autonomous domain registration information;

[0009] The first layer includes multiple intermediate alliances, the intermediate alliance includes multiple autonomous domains of the convergence layer and one autonomous domain of the core layer, the multiple autonomous domains of the convergence layer include the monitoring autonomous domain in the low-level alliance, the core layer includes multiple autonomous domains in the core of the network, the autonomous domain of the core layer serves as the monitoring autonomous domain of the intermediate alliance, and the autonomous domain of the convergence layer transmits data to the autonomous domain of the core layer;

[0010] An intermediate alliance also includes an intermediate blockchain, which is used to store information of autonomous domains in the intermediate alliance and information summaries of autonomous domains of leaf blockchains; for traceability transactions within the alliance where the sender and the receiver are in the same intermediate alliance, the intermediate blockchain is also used to reach consensus on the traceability transactions within the alliance; for cross-alliance traceability transactions where the sender and the receiver are not in the same alliance, the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located is used to send the cross-alliance traceability transactions in the intermediate alliance, the proof of the cross-alliance traceability transactions, and the block header of the block where the cross-alliance traceability transactions are located to the root blockchain in the form of cross-chain messages; in the case of cross-alliance traceability transactions where the lower-level alliance where the sender is located and the lower-level alliance where the receiver is located are not the same lower-level alliance, and the intermediate blockchain contains the information summary of the sender and the information summary of the receiver corresponding to the cross-alliance traceability transaction, the intermediate blockchain is used as the minimum common ancestor blockchain, and the intermediate blockchain is used to verify and transmit cross-chain messages between the leaf blockchain where the sender of the cross-alliance traceability transaction is located and the leaf blockchain where the receiver is located;

[0011] The second layer includes a root alliance, which includes all autonomous domains of the core layer; a root alliance contains a root blockchain, which is used to store information of autonomous domains in the root alliance, and also stores information summaries of autonomous domains in lower-level alliances and information summaries of autonomous domains in intermediate alliances; for traceability transactions within the root alliance, the root blockchain is also used to reach consensus on traceability transactions within the root alliance; in the case of cross-alliance traceability transactions where the sender and receiver are not in the same alliance and there is no intermediate blockchain that meets the conditions for serving as the minimum common ancestor blockchain, the root blockchain is used as the minimum common ancestor blockchain, and the root blockchain is used to verify and transmit cross-chain messages between the blockchain where the sender and the blockchain where the receiver of the cross-alliance traceability transaction are located.

[0012] Optionally, the inter-domain IP traceability alliance system based on the hierarchical blockchain realizes the synchronization of autonomous domain information between the upper and lower level alliances in the following ways:

[0013] The monitoring autonomous domain in the lower-level alliance where the leaf blockchain is located obtains the information summary of the autonomous domain that needs to achieve information synchronization. The monitoring autonomous domain of the lower-level alliance where the leaf blockchain is located initiates a state summary transaction to the upper-level intermediate blockchain based on the obtained information summary of the autonomous domain. The state summary transaction contains the information summary of the autonomous domain obtained by the monitoring autonomous domain. The intermediate blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the intermediate blockchain to achieve information synchronization of the autonomous domains within the alliance; the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located obtains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance, and initiates a state summary transaction to the upper-level root blockchain. The state summary transaction contains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance. The root blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the root blockchain to achieve global synchronization of autonomous domain information;

[0014] For cross-alliance traceability transactions between two alliances, according to the third-party notary mechanism, the least common ancestor blockchain of the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located is determined as the third-party notary. Specifically, according to the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located, the least common ancestor blockchain is determined. The least common ancestor blockchain contains both the information summary of the sender and the information summary of the receiver, and has the smallest distance from the blockchain where the sender is located and the blockchain where the receiver is located, wherein the distance between the blockchain where the sender is located and the blockchain where the receiver is located is the number of layers of the blockchain where the sender is located and the blockchain where the receiver is located. The least common ancestor blockchain is used to verify and transmit cross-chain messages between the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located, and at the same time verify whether the cross-alliance traceability transaction actually exists in the blockchain where the sender is located or the blockchain where the receiver is located; the least common ancestor blockchain is also used to store the verification results of the cross-chain messages; for cross-alliance traceability transactions of the traceability transfer type, the least common ancestor blockchain is also used to ensure the atomicity of the cross-alliance traceability transaction and the state consistency of the blockchain where the sender of the traceability transaction is located and the blockchain where the receiver is located.

[0015] An inter-domain IP traceability alliance method based on a layered blockchain, according to an inter-domain IP traceability alliance system based on a layered blockchain, the inter-domain IP traceability alliance method based on a layered blockchain at least includes a hierarchical inter-domain IP traceability solution;

[0016] The traceability transaction is implemented based on a hierarchical inter-domain IP traceability solution. For the autonomous domain that deploys the hierarchical inter-domain IP traceability solution, the hierarchical inter-domain IP traceability solution includes: the autonomous domain through which the IP data stream i passes during transmission performs flow marking and flow fingerprint generation on the IP data stream i, and the autonomous domain with traceability requirements performs flow footprint acquisition or flow transmission path reconstruction on the IP data stream i. The IP data stream Said is the first data packet in IP data stream i, is the second data packet in IP data stream i, is the oth data packet in IP data stream i, and the routing paths of data packets in the same IP data stream are the same;

[0017] For IP data flow i from autonomous domain AS m-1 To the Autonomous Domain AS m The data transmission process, the flow marking and flow fingerprint generation strategy specifically includes:

[0018] Flow marking: In IP data flow First, the autonomous domain AS m-1 Sample the data packets and obtain one of the data packets of data stream i In the autonomous domain AS m-1 The query is made in the local flow fingerprint database of the autonomous domain AS. m-1 The fingerprint of data stream i is queried in the local stream fingerprint library Extract fingerprint Tags in If in the autonomous domain AS m-1 The fingerprint of data stream i is not found in the local stream fingerprint library The data packet obtained by sampling Assign new labels Autonomous Domain (AS) m-1 Autonomous Network Number ASN m-1 and tags Write The unused field of the packet is forwarded to the autonomous domain AS. m ;

[0019] According to the different scales of alliances at different levels, an autonomous domain number with a length of a first threshold is configured for the autonomous domain of the root alliance, an autonomous domain number with a length of a second threshold is configured for the autonomous domain of the intermediate alliance, and an autonomous domain number with a length of a third threshold is configured for the autonomous domain of the low-level alliance, wherein the first threshold is smaller than the second threshold, and the second threshold is smaller than the third threshold;

[0020] Flow fingerprint generation: AS m Receive AS m-1Marked Packets After that, the ASN m-1 and of Extract information and obtain flow footprint Among them, the dst i Indicates data packet Destination IP address, according to the flow footprint In the autonomous domain AS m The local flow fingerprint database is searched to determine the autonomous domain AS m Whether the flow fingerprint of IP data flow i already exists in the local flow fingerprint database in the autonomous domain AS m If the flow fingerprint of IP data flow i exists in the local flow fingerprint library of the autonomous domain AS m Only the flow marking policy needs to be implemented. m If the flow fingerprint of IP data flow i does not exist in the local flow fingerprint database of the autonomous domain AS m Generate a flow fingerprint for IP data flow i. Specifically, assign a label to data flow i According to the flow footprint and tags Generate flow fingerprint The flow fingerprint is stored. The specific flow fingerprint generation process is expressed by the following formula:

[0021]

[0022] Among them, function f(·) is the function of generating flow fingerprint, SampleFlow() represents the sampling operation, i represents the IP data flow, Indicates an autonomous domain AS m Flow fingerprint Stored in the local flow fingerprint library;

[0023] For autonomous domains with traceability requirements m The process of obtaining the flow footprint or reconstructing the flow transmission path of IP data flow i adopts the flow footprint acquisition or flow path reconstruction strategy, which specifically includes: Autonomous domain AS m According to the sampled data packets Extracting Data Packets Destination IP address dst i and tags Read the stream fingerprint in the local stream fingerprint library Based on flow fingerprint Get flow footprint and the previous hop ASN of IP data flow i m-1 , specifically, the one-hop routing path of IP data flow i The flow footprint acquisition or flow path reconstruction strategy is expressed by the following formula:

[0024]

[0025] Among them, the function f -1 (·) is a function for obtaining flow footprint or reconstructing flow path, LoadFP() is a function for reading flow fingerprint, and UpAS represents the previous hop autonomous domain number of IP data flow i.

[0026] Optionally, the inter-domain IP traceability alliance method based on the layered blockchain also includes an inter-domain IP traceability transaction processing flow based on the layered blockchain; wherein the inter-domain IP traceability transaction processing flow based on the layered blockchain at least includes autonomous domain registration, and the autonomous domain registration includes the following steps:

[0027] Step A1: Newly joined autonomous domain AS k Submit a registration transaction to the blockchain of the current alliance. The registration transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the autonomous domain AS k The autonomous domain number, autonomous domain prefix, public key, account address and service fee. The autonomous domain prefix refers to the usable IP address range allocated by the Internet management agency to the autonomous domain. The public key and account address of the autonomous domain are generated by the autonomous domain itself. The service fee of the autonomous domain refers to the fee for the autonomous domain to provide a traceability service once. The sender address refers to the account address of the newly added autonomous domain. The receiver address refers to the account addresses of all other autonomous domains in the current alliance.

[0028] Step A2: After receiving the registration transaction, the blockchain of the current alliance executes the consensus algorithm within the chain to verify the mapping relationship between the autonomous domain number and the autonomous domain prefix in the registration transaction. If the verification is successful, the registration transaction is stored on the blockchain of the current alliance and step A3 is executed. If the verification is not successful, the registration transaction is canceled.

[0029] Step A3: If the current alliance is at level 0, execute steps A4 to A8; if the current alliance is at level 1, execute steps A5 to A8; if the current alliance is at level 2, execute steps A7 to A8;

[0030] Step A4: The monitoring autonomous domain of the current alliance summarizes the information of all newly registered autonomous domains within a preset time period. k Information summary S k The information summary includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number of the autonomous domain, and generates a state summary transaction TX BS =(S1,S2,...,Sk ), the state summary transaction includes the information summary of all newly registered autonomous domains within a preset time period, and then the state summary transaction TX BS =(S1,S2,...,S k ) is sent to the intermediate blockchain of the first layer alliance that has data transmission with the current alliance;

[0031] Step A5: The intermediate blockchain receives the state summary transaction TX sent by the monitoring autonomous domain of the 0th layer alliance BS =(S1,S2,...,S k ) and summarize the status transaction TX BS =(S1,S2,...,S k ) executes the consensus algorithm to TX BS Consensus is reached. If the consensus is passed, the intermediate blockchain will BS To store;

[0032] Step A6: The monitoring autonomous domain of the alliance where the intermediate blockchain is located summarizes the information summary of all newly registered autonomous domains and the status summary transaction TX of the leaf blockchain BS , and generate a new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ), and then the new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) is sent to the root blockchain;

[0033] Step A7: The root blockchain receives the new state summary transaction TX' sent by the listening autonomous domain of the layer 1 alliance BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r );and summarize the new state transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) executes the consensus algorithm and performs BS Consensus is reached. If the consensus is passed, TX' BS To store;

[0034] Step A8: The root blockchain stores information of all newly registered autonomous domains.

[0035] Optionally, the inter-domain IP tracing transaction processing process based on the layered blockchain further includes a tracing request, and the tracing request includes the following steps:

[0036] Step 1.1: Initiate a traceability request transaction to the blockchain of the alliance to which the traceability requester of the IP data stream belongs. The traceability request transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the destination IP address and label of the IP data stream. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder.

[0037] Step 1.2: The blockchain of the alliance where the traceability requester belongs receives the traceability request transaction, reaches a consensus on the traceability request transaction, and stores the traceability request transaction on the blockchain;

[0038] Step 1.3: The monitoring autonomous domain of the alliance where the tracing requester is located detects that the recipient of the tracing request transaction is not in the current alliance, and generates a first cross-chain message, which includes the tracing request transaction, the proof of the tracing request transaction, the block header of the block where the tracing request transaction is located, and the numbers of the blockchains where the sender and receiver of the tracing request transaction are located; then, the monitoring autonomous domain sends the first cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchains where the sender and receiver of the tracing request transaction are located;

[0039] Step 1.4: The least common ancestor blockchain parses the first cross-chain message, verifies the traceability request transaction and its proof, stores the verification result on the least common ancestor blockchain, and encapsulates the first cross-chain message and the verification result into a second cross-chain message and sends it to the blockchain where the recipient of the traceability request transaction is located;

[0040] Step 1.5: The blockchain where the recipient of the traceability request transaction is located receives the second cross-chain message, parses the second cross-chain message, obtains the first cross-chain message and the verification result, and when the verification result indicates that the verification is passed, sends the traceability request transaction in the first cross-chain message to the traceability responder.

[0041] Optionally, the inter-domain IP traceability transaction processing flow based on the layered blockchain further includes a traceability response, and the traceability response includes the following steps:

[0042] Step 2.1: After receiving the tracing request transaction, the tracing responder extracts the flow tag, queries the local flow fingerprint library, generates the flow footprint and the previous hop autonomous domain number in the flow path, and then initiates a tracing response transaction to the blockchain of the alliance. The tracing response transaction includes: transaction content, the sender address and the receiver address of the transaction. The transaction content includes the flow footprint and the previous hop autonomous domain number in the flow path. The sender address refers to the account address of the tracing responder, and the receiver address refers to the account address of the tracing requester.

[0043] Step 2.2: The blockchain of the alliance to which the traceability responder belongs receives the traceability response transaction, reaches a consensus on the traceability response transaction, and stores the traceability response transaction on the blockchain;

[0044] Step 2.3: The monitoring autonomous domain of the alliance where the tracing response party is located detects that the recipient of the tracing response transaction is not in the current alliance, and generates a third cross-chain message, wherein the third cross-chain message includes the tracing response transaction, the proof of the tracing response transaction, the block header of the block where the tracing response transaction is located, the number of the blockchain where the sender of the tracing response transaction is located, and the number of the blockchain where the recipient is located; then, the monitoring autonomous domain sends the third cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchain where the sender and the recipient of the tracing response transaction are located;

[0045] Step 2.4: The least common ancestor blockchain parses the third cross-chain message, verifies the provenance response transaction and the proof of the provenance response transaction, stores the verification result on the least common ancestor blockchain, and encapsulates the third cross-chain message and the verification result into a fourth cross-chain message and sends it to the blockchain where the recipient of the provenance response transaction is located;

[0046] Step 2.5: The blockchain where the recipient of the traceability response transaction is located receives the fourth cross-chain message, parses the fourth cross-chain message, obtains the third cross-chain message and the verification result, and sends the traceability response transaction to the traceability requester when the verification result indicates that the verification is passed.

[0047] Optionally, the inter-domain IP traceability transaction processing flow based on the layered blockchain also includes traceability transfer, and the traceability transfer includes the following steps:

[0048] Step B1: Withdrawal consensus

[0049] Step B1.1: The tracing requester initiates a tracing transfer transaction to the blockchain of the alliance to which it belongs. The tracing transfer transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the service fee of the tracing responder. The sender address refers to the account address of the tracing requester, and the receiver address refers to the account address of the tracing responder.

[0050] Step B1.2: The blockchain of the alliance to which the tracing requester belongs reaches a consensus on the tracing transfer transaction and checks whether the account balance of the tracing requester satisfies the service fee of the tracing responder. If the account balance of the tracing requester does not meet the service fee requirement of the tracing responder, the tracing transfer transaction is canceled. If the account balance of the tracing requester meets the service fee requirement of the tracing responder, the account balance of the tracing requester is withdrawn, and the amount withdrawn is the service fee of the tracing responder.

[0051] Step B2. Withdrawal transaction proof delivery

[0052] Step B2.1: The monitoring autonomous domain of the alliance where the traceability requester is located detects that the recipient of the traceability transfer transaction is not in the current alliance, and encapsulates the traceability transfer transaction, the proof of the traceability transfer transaction, the block header of the block where the traceability transfer transaction is located, and the numbers of the blockchains where the sender and receiver of the traceability transfer transaction are located into a fifth cross-chain message. The monitoring autonomous domain sends the fifth cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchains where the sender and receiver of the traceability transfer transaction are located;

[0053] Step B2.2: The least common ancestor blockchain parses the fifth cross-chain message, verifies the traceability transfer transaction and its proof, and stores the verification result on this blockchain. If the verification fails, a rollback message is sent to the blockchain where the sender of the traceability transfer transaction is located, including the proof of verification failure, and the processing flow of the traceability transfer transaction is terminated; if the verification passes, it is searched whether there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted. If not, the least common ancestor blockchain encapsulates the fifth cross-chain message and the verification result into a sixth cross-chain message and sends it to the blockchain where the recipient of the traceability transfer transaction is located; if there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted, the least common ancestor blockchain needs to wait for the other cross-alliance traceability transfer transactions to be successfully submitted or terminated before the sixth cross-chain message can be sent to the blockchain where the recipient of the traceability transfer transaction is located;

[0054] Step B3. Deposit Transaction Consensus

[0055] Step B3.2: The blockchain where the recipient of the traceability transfer transaction is located parses the sixth cross-chain message to obtain the fifth cross-chain message and the verification result. If the verification result indicates that the verification is passed, it indicates that the traceability transfer transaction is correctly submitted on the blockchain where the sender is located. The traceability responder initiates a deposit transaction to the blockchain of the alliance where it is located. The deposit transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the proof of the traceability transfer transaction and the service fee of the traceability responder. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder. The blockchain of the alliance where the traceability responder is located reaches a consensus on the deposit transaction to realize the account deposit of the traceability responder. The amount of the deposit is the service fee.

[0056] Step B3.3: The monitoring autonomous domain of the alliance where the traceability responder is located encapsulates the deposit transaction, the proof of the deposit transaction, the block header of the block where the deposit transaction is located, and the numbers of the blockchains where the sender and receiver of the deposit transaction are located into the seventh cross-chain message, and sends the seventh cross-chain message to the least common ancestor blockchain of the blockchains where the sender and receiver of the deposit transaction are located;

[0057] Step B4.4. Submit

[0058] The least common ancestor blockchain parses the seventh cross-chain message, verifies the deposit transaction and its proof, and stores the verification result on the least common ancestor blockchain. If the verification result indicates that the verification is passed, a submission message is sent to the blockchains where the sender and receiver of the traceability transfer transaction are located respectively. The submission message indicates that the traceability transfer transaction is successfully submitted, and the process ends; if the verification result indicates that the verification is not passed or the least common ancestor blockchain does not receive the seventh cross-chain message within a preset time period, step B5 is executed;

[0059] Step B5. Rollback

[0060] The least common ancestor blockchain sends a rollback message to the blockchains of the sender and receiver of the traceability transfer transaction respectively. If the verification fails, the rollback message includes the verification result and proof of the deposit transaction; if it is a timeout, the rollback message includes the proof of timeout of the traceability transfer transaction, the blockchain where the sender is located executes the reverse operation of the traceability transfer transaction, and the blockchain where the receiver is located executes the reverse operation of the deposit transaction.

[0061] The beneficial effects of adopting the above technical solution are:

[0062] Compared with the prior art, the inter-domain IP traceability alliance system and method based on layered blockchain proposed in the present invention achieves high throughput, high traceability accuracy, low storage overhead and scalability. The proposed layered blockchain system architecture not only better fits the actual network layered structure, but also achieves high throughput and high scalability to meet the IP traceability requirements under large-scale networks; the proposed user information synchronization mechanism and cross-chain message transmission mechanism solve the problem of information non-intercommunication between alliances and improve the credibility and transparency of the system; the proposed hierarchical inter-domain IP traceability scheme has the advantages of high precision, low storage overhead and scalability; the proposed inter-domain IP traceability transaction processing flow based on layered blockchain ensures the atomicity of cross-alliance traceability transactions and improves the scalability of the system. The application of the present invention does not require upgrading the existing network infrastructure, has low deployment cost and high scalability, and meets the application requirements. In addition, the layered blockchain system architecture and method proposed in the present invention are not only applicable to the fields of network security and network management, but also applicable to other large-scale hierarchical application scenarios, and have good application prospects. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 A network hierarchical structure diagram according to an embodiment of the present invention;

[0064] Figure 2 This is an architecture diagram of an inter-domain IP traceability alliance system based on a layered blockchain in an embodiment of the present invention;

[0065] Figure 3 This is a schematic diagram of alliance user information synchronization in an embodiment of the present invention;

[0066] Figure 4 A schematic diagram of a different alliance autonomous domain number allocation mechanism in an embodiment of the present invention;

[0067] Figure 5 A model diagram of a hierarchical inter-domain IP tracing system in an embodiment of the present invention;

[0068] Figure 6 A flowchart of a user registration transaction process in an embodiment of the present invention;

[0069] Figure 7 A flowchart of a cross-alliance traceability request and response transaction processing in an embodiment of the present invention;

[0070] Figure 8 The present invention provides a flowchart of a cross-alliance traceability transfer transaction process in an embodiment of the present invention. DETAILED DESCRIPTION

[0071] The specific implementation of the present invention is further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0072] In view of the problems existing in the prior art, in order to solve the challenge that the blockchain has poor scalability and cannot meet the IP traceability requirements under large-scale networks, the present invention proposes an inter-domain IP traceability alliance system architecture based on a layered blockchain. The layered characteristics of the network structure are used to divide IP traceability alliances at different levels, each alliance maintains a blockchain, and different alliances execute traceability transactions within the alliance in parallel, achieving high concurrency of transactions. In addition, in order to reduce the low storage load of the blockchain full node, a state sharding mechanism is adopted, and each blockchain only records IP traceability transactions within the alliance. In order to solve the blockchain consistency problem caused by the state sharding mechanism, an autonomous domain information synchronization mechanism and a cross-chain message transmission mechanism under a layered blockchain system are proposed. In order to solve the problems of low precision and large storage overhead of the IP traceability solution, a high-precision, low-overhead and scalable hierarchical inter-domain IP traceability solution is proposed, including flow marking, flow fingerprint generation and flow footprint acquisition / flow path reconstruction strategy.

[0073] In order to realize the efficient processing of IP traceability transactions under the layered blockchain system, the present invention proposes an inter-domain IP traceability transaction processing flow based on the layered blockchain. IP traceability transactions include autonomous domain registration, traceability requests, traceability responses and traceability transfer transactions. The present invention only considers the cross-alliance traceability transaction processing flow based on the layered blockchain, and proposes to use the minimum common ancestor blockchain of the blockchain related to the cross-alliance traceability transaction as the third-party notary of the cross-alliance traceability transaction, responsible for the verification and transmission of cross-chain messages. This will ensure that the verification process of all cross-alliance traceability transactions can be audited and traced, and improve the credibility and transparency of the system. For cross-alliance traceability transfer transactions involving cross-chain asset transfers, a cross-alliance traceability transfer transaction processing flow based on a coordinator is proposed, which realizes the atomicity of the transaction and the consistency of the blockchain state. Among them, the minimum common ancestor blockchain with the role of a third-party notary can serve as a coordinator, which improves the degree of decentralization and solves the performance bottleneck of a single coordinator.

[0074] The present invention is designed for large-scale real network architecture, such as Figure 1As shown in the figure, the network structure is divided into three layers, namely the access layer, the aggregation layer and the core layer from bottom to top. The access layer is composed of some autonomous systems (AS) at the edge of the network, among which Stub AS accounts for a large proportion, and the autonomous domains usually form a C2P (Customer-to-Provider, C2P) relationship. The aggregation layer is composed of some forwarding autonomous domains, which are responsible for aggregating and forwarding the traffic of the access layer autonomous domains. The core layer is composed of some large backbone autonomous domains at the core of the network, which are responsible for forwarding large-scale network traffic, and the autonomous domains form a P2P (Peer-to-Peer, P2P) relationship.

[0075] Figure 1 Medium, AS1, AS2, AS3, AS4, AS5, AS6, AS7, AS8, AS9, AS 10 ,AS 11 ,AS 12 and AS 13 Both represent autonomous domains. The access layer aggregates the data streams that need to be forwarded through the access layer aggregation device and sends them to the aggregation layer. The aggregation layer aggregates the data streams that need to be forwarded through the aggregation layer aggregation device and sends them to the core layer.

[0076] Based on this, a hierarchical blockchain-based inter-domain IP traceability alliance system is developed, combining Figure 2 , the inter-domain IP traceability alliance system based on layered blockchain consists of layer 0, layer 1 and layer 2.

[0077] The 0th layer includes multiple low-alliances (LAs for short), the low-alliance includes multiple autonomous domains of the access layer and one autonomous domain of the tandem layer, the autonomous domain of the tandem layer serves as a monitoring autonomous domain of the low-alliance, the autonomous domain of the access layer transmits data to the autonomous domain of the tandem layer, the access layer includes multiple autonomous domains at the edge of the network, and the tandem layer includes multiple autonomous domains between the edge of the network and the core of the network.

[0078] like Figure 2 LA#1 is the first low-level alliance, AS1 and AS2 are two autonomous domains of the access layer, and AS3 is an autonomous domain of the tandem layer, that is, the monitoring autonomous domain. Figure 2 LA#2 is the leader of LA#1; LA#2 is the second lowest level alliance, AS4 and AS5 are two autonomous domains of the access layer, and AS6 is an autonomous domain of the tandem layer, that is, the monitoring autonomous domain. Figure 2 LA#n is the leader of LA#2; LA#n is the nth lower-level alliance, AS7 and AS8 are two autonomous domains of the access layer, and AS9 is an autonomous domain of the tandem layer, that is, the monitoring autonomous domain. Figure 2 Leader in LA#n.

[0079] A low-level alliance also contains a leaf blockchain (Leaf-BlockChain, referred to as L-BC), Figure 2 Each rectangular block in represents a block that is combined together to obtain a blockchain, L-BC#1 is the first leaf blockchain, L-BC#2 is the second leaf blockchain, and L-BC#n is the nth leaf blockchain; the leaf blockchain is used to store information about autonomous domains in low-level alliances, and the information about autonomous domains includes registration information about autonomous domains; for traceability transactions within an alliance where the sender and the receiver are in the same low-level alliance, the leaf blockchain is also used to reach a consensus on the traceability transactions within the alliance, where the sender is the autonomous domain of the initiator of the traceability transaction within the alliance, and the receiver is the autonomous domain of the receiver of the traceability transaction within the alliance; for cross-alliance traceability transactions where the sender and the receiver are not in the same low-level alliance, the leaf blockchain After consensus is reached on the cross-alliance traceability transaction, the monitoring autonomous domain of the lower-level alliance where the leaf blockchain is located is used to send the cross-alliance traceability transaction in the lower-level alliance, the proof of the cross-alliance traceability transaction and the block header of the block where the cross-alliance traceability transaction is located in the form of a cross-chain message to the intermediate blockchain until the minimum common ancestor blockchain. The minimum common ancestor blockchain contains the information summary of the sender corresponding to the cross-alliance traceability transaction and the information summary of the receiver corresponding to the cross-alliance traceability transaction, and has the smallest distance from the blockchain where the sender is located and the blockchain where the receiver is located; the information summary of the autonomous domain includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number in the autonomous domain registration information.

[0080] Among them, the proof of cross-alliance traceability transactions can be a Merkle proof; in the specific implementation, the Leader autonomous domain of the leaf blockchain also needs to send the transaction, the Merkle proof of the transaction, the block header of the transaction and other information to the intermediate blockchain (Inter-BlockChain, abbreviated as I-BC) in the form of a cross-chain message until the minimum common ancestor blockchain.

[0081] The first layer includes multiple intermediate alliances (IA), the intermediate alliance includes multiple autonomous domains of the aggregation layer and one autonomous domain of the core layer, the multiple autonomous domains of the aggregation layer include the monitoring autonomous domain in the low-level alliance, the core layer includes multiple autonomous domains in the core of the network, the autonomous domain of the core layer serves as the monitoring autonomous domain of the intermediate alliance, and the autonomous domain of the aggregation layer transmits data to the autonomous domain of the core layer.

[0082] like Figure 2 IA#1 is the first intermediate alliance, AS3 and AS6 are two autonomous domains at the aggregation layer, and AS 10It is an autonomous domain of the core layer, that is, the monitoring autonomous domain. Figure 2 The leader of IA#1; IA#m is the mth intermediate alliance, AS9 and AS 11 There are two autonomous domains in the aggregation layer, AS 12 It is an autonomous domain of the core layer, that is, the monitoring autonomous domain. Figure 2 Leader in IA#m.

[0083] An intermediate alliance also includes an intermediate blockchain. Figure 2 Each rectangular block in represents a block that is combined together to obtain a blockchain, I-BC#1 is the first intermediate blockchain, and I-BC#m is the mth intermediate blockchain; the intermediate blockchain is used to store the information of the autonomous domain in the intermediate alliance and the information summary of the autonomous domain of the leaf blockchain; for the traceability transaction within the alliance of the sender and the receiver in the same intermediate alliance, the intermediate blockchain is also used to reach a consensus on the traceability transaction within the alliance.

[0084] For cross-alliance traceability transactions where the sender and receiver are not in the same alliance, the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located is used to send the cross-alliance traceability transactions in the intermediate alliance, the proof of the cross-alliance traceability transactions, and the block header of the block where the cross-alliance traceability transactions are located to the root blockchain in the form of cross-chain messages; among them, for cross-alliance traceability transactions where the sender and receiver are not in the same alliance, the sender can be in a lower-level alliance and the receiver can be in a lower-level alliance, but the sender's information digest and the receiver's information digest are not stored in the same intermediate blockchain, for example, Figure 2 In the example, the sender can be AS1 and the receiver can be AS8; or the sender and receiver can be one in the middle alliance and one in the lower alliance, and the sender's message digest and the receiver's message digest are not stored in the same middle blockchain, for example, Figure 2 In the example, the sender can be AS1 and the receiver can be AS 11 ; It is also possible that the sender is in the intermediate alliance and the receiver is in the intermediate alliance, but the sender's information digest and the receiver's information digest are not stored in the same intermediate blockchain, such as Figure 2 , the sender can be AS3 and the receiver can be AS9.

[0085] In the case of a cross-alliance traceability transaction where the sender's lower-level alliance and the receiver's lower-level alliance are not the same lower-level alliance, and the intermediate blockchain contains the sender's information digest and the receiver's information digest corresponding to the cross-alliance traceability transaction, such as Figure 2In the example, the sender can be AS1 and the receiver can be AS4. The intermediate blockchain is used as the minimum common ancestor blockchain. The intermediate blockchain is used to verify and transmit cross-chain messages between the leaf blockchain where the sender of the cross-alliance traceability transaction is located and the leaf blockchain where the receiver is located.

[0086] The second layer includes a root alliance (RA), which includes all autonomous domains of the core layer, such as Figure 2 In, A.S. 10 ,AS 12 ,AS 13 For all autonomous domains of the core layer; a root alliance contains a root blockchain (Root-BlockChain, referred to as R-BC), such as Figure 2 In the R-BC, the root blockchain is used to store the information of the autonomous domain in the root alliance, and also stores the information digest of the autonomous domain in the lower-level alliance and the information digest of the autonomous domain in the intermediate alliance; for the traceability transaction in the root alliance, the root blockchain is also used to reach a consensus on the traceability transaction in the root alliance; in the case of a cross-alliance traceability transaction where the sender and the receiver are not in the same alliance, and there is no intermediate blockchain that meets the conditions for serving as the minimum common ancestor blockchain, the root blockchain is used as the minimum common ancestor blockchain, and the root blockchain is used to verify and transmit the cross-chain messages between the blockchain where the sender and the blockchain where the receiver of the cross-alliance traceability transaction are located. Among them, the condition for serving as the minimum common ancestor blockchain is that the intermediate blockchain contains both the information digest of the sender and the information digest of the receiver, that is, the intermediate blockchain only contains the information digest of the sender or the information digest of the receiver does not meet the condition for serving as the minimum common ancestor blockchain, and the intermediate blockchain does not contain the information digest of the sender and the information digest of the receiver, and does not meet the condition for serving as the minimum common ancestor blockchain.

[0087] The inter-domain IP traceability alliance system based on layered blockchain proposed in the present invention adopts a layered multi-chain architecture to improve the throughput and scalability of the system. Each blockchain only maintains the transaction information within the blockchain, which can achieve high concurrency of large-scale traceability transactions. However, the layered multi-chain architecture has the problem of non-intercommunication of messages between blockchains. In a licensed blockchain, independent blockchains cannot communicate effectively. In this system, this will lead to difficulties in the transmission of cross-alliance traceability transactions. In order to solve the problem of non-intercommunication of messages between blockchains, the present invention proposes to sink the upper layer of the autonomous domain with a connection relationship in the network architecture to the next layer, so that the autonomous domain (Leader autonomous domain) will be in both the upper and lower alliances, and maintain the ledgers of the two blockchains at the same time. Although this method sacrifices a certain storage space of the Leader autonomous domain, it improves the message transmission efficiency between blockchains and is also in line with the actual network hierarchical structure characteristics. The Leader autonomous domain can be selected in a large Transit AS, or by designing a certain incentive mechanism. The present invention only considers selecting a Transit AS with a gateway role.

[0088] In addition, the system architecture is based on state sharding, so that each layer of blockchain only stores the autonomous domain information within the alliance, reducing the storage overhead of the blockchain and enhancing the privacy protection of each alliance. However, this advantage has caused the problem that cross-alliance traceability transactions cannot be initiated. For example, Figure 2 As shown, autonomous domain AS1 needs to request traceability from autonomous domain AS4. However, AS1 cannot obtain information such as AS4's account address and service fee from L-BC#1, and thus cannot initiate a cross-alliance traceability transaction to AS4. In order to achieve autonomous domain information acquisition, the present invention proposes an autonomous domain information synchronization mechanism under a layered blockchain system.

[0089] The inter-domain IP traceability alliance system based on the hierarchical blockchain realizes the synchronization of autonomous domain information between the upper and lower level alliances in the following ways:

[0090] The monitoring autonomous domain in the lower-level alliance where the leaf blockchain is located obtains the information summary of the autonomous domain that needs to achieve information synchronization. The monitoring autonomous domain of the lower-level alliance where the leaf blockchain is located initiates a state summary transaction to the upper-level intermediate blockchain based on the obtained information summary of the autonomous domain. The state summary transaction contains the information summary of the autonomous domain obtained by the monitoring autonomous domain. The intermediate blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the intermediate blockchain to achieve information synchronization of the autonomous domains within the alliance; the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located obtains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance, and initiates a state summary transaction to the upper-level root blockchain. The state summary transaction contains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance. The root blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the root blockchain to achieve global synchronization of autonomous domain information;

[0091] like Figure 3 As shown in the figure, the left side is the autonomous domain information table maintained by different layers of blockchain, and the right side is the autonomous domain information synchronization process. Newly added autonomous domains in the alliance need to register with the alliance blockchain to participate in the traceability system. After the blockchain reaches a consensus, it will maintain the information of the autonomous domain on the chain, including the autonomous domain number ASN, autonomous domain prefix Pre, public key PK, account address Addr, account balance Bal, service fee C and blockchain number T. This information also constitutes Figure 3 The autonomous domain information table shown on the left. In the inter-domain IP traceability alliance system, each layer of blockchain needs to synchronize the autonomous domain information summary within the alliance from the bottom up, including the autonomous domain number ASN, public key PK, account address Addr, service fee C and the blockchain number T to which it belongs. As for the autonomous domain prefix Pre and account balance Bal, on the one hand, this information is private information; on the other hand, in order to avoid inconsistent account balances, it is only maintained by the alliance and does not need to be synchronized. The autonomous domain information synchronization operation is the responsibility of the Leader node of each blockchain. The specific process is as follows: For example, Figure 3 As shown in the figure, it includes registration transactions, status summary transactions and other transactions. Specifically, within a certain period, the Leader node of L-BC#1 queries the registration transactions on this chain, extracts the summary of the autonomous domain information that needs to be synchronized, and then initiates a new transaction to the upper blockchain (I-BC#1), which is called the status summary transaction. The upper blockchain reaches an in-chain consensus, and after passing it, it updates the autonomous domain information table of this alliance. This synchronization operation continues until the root blockchain ends.

[0092] After the autonomous domain information synchronization process is completed, the root alliance will record all the information of the autonomous domains within the alliance and the information summaries of all other autonomous domains. The intermediate alliance will record all the information of the autonomous domains within the alliance and the information summaries of all autonomous domains of the subordinate lower-level alliances. Figure 2 As shown in the figure, when AS1 cannot obtain information such as AS4's account address and service fee from L-BC#1, AS1 can entrust the Leader autonomous domain of the blockchain of this layer to query the autonomous domain information of AS4 from the upper blockchain (I-BC#1). In the IP traceability solution, AS1 can obtain the upstream autonomous domain number ASN4 that needs to be traced in advance, so AS1 can use the autonomous domain number ASN4 as the query condition. The autonomous domain information query process only needs to be executed twice at most to complete.

[0093] In order to ensure the validity and consistency of cross-alliance traceability transactions, the present invention proposes a trusted and transparent cross-chain message transmission mechanism. In addition to ensuring the basic atomicity requirements of cross-alliance traceability transactions, in order to improve the reliability and transparency of the system, the present invention introduces a third-party notary mechanism to verify the validity and authenticity of cross-chain messages; for cross-alliance traceability transactions between two alliances, according to the third-party notary mechanism, the least common ancestor blockchain of the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located is determined as the third-party notary. Specifically, according to the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located, the least common ancestor blockchain is determined, and the least common ancestor blockchain contains both the sender's information summary and the receiver's information summary, and is consistent with the blockchain where the sender is located and the block where the receiver is located. The distance between the chains is the smallest, wherein the distance between the sender's blockchain and the receiver's blockchain is the number of layers of the sender's blockchain and the receiver's blockchain; the least common ancestor blockchain is used to verify and transmit cross-chain messages between the sender's blockchain and the receiver's blockchain of the cross-alliance traceability transaction, and at the same time verify whether the cross-alliance traceability transaction actually exists in the sender's blockchain or the receiver's blockchain; the least common ancestor blockchain is also used to store the verification results of the cross-chain message; for cross-alliance traceability transactions of the traceability transfer type, the least common ancestor blockchain is also used to ensure the atomicity of the cross-alliance traceability transaction and the state consistency of the sender's blockchain and the receiver's blockchain of the traceability transaction.

[0094] For example, Figure 2 As shown in the figure, when the autonomous domain AS1 of alliance LA#1 initiates a cross-alliance traceability transaction TX to the autonomous domain AS4 of alliance LA#2 14 When, first, TX 14 A consensus will be reached in the blockchain L-BC#1 to which AS1 belongs. If the consensus is reached, it will be packaged into a new block.14 TX 14 The Merkle proof and the block header information are encapsulated into a cross-chain message Msg 14 , sent to TX 14 The minimum common ancestor blockchain I-BC#1. Again, I-BC#1 parses the cross-chain message Msg 14 , for transaction TX 14 Verify the authenticity and integrity of Stored on this blockchain, verification results Mainly includes cross-chain message Msg 14 The ID, verification status (verification passed or failed), proof data, timestamp and verifier signature. Finally, I-BC#1 sends the cross-chain message Msg 14 And verification results Encapsulate into a new cross-chain message Msg1'4 and send to TX 14 The recipient blockchain L-BC#2 processes it and feeds the result back to the autonomous domain AS4.

[0095] In the inter-domain IP traceability alliance system, the autonomous domains can be divided into ordinary autonomous domains and traceability autonomous domains according to whether the IP traceability solution is deployed. Ordinary autonomous domains do not deploy IP traceability solutions and do not provide traceability services. The traceability autonomous domain deploys an IP traceability solution and can provide traceability services to other autonomous domains to make profits. The present invention proposes a scalable and low-overhead hierarchical inter-domain IP traceability solution. It mainly includes flow marking, flow fingerprint generation, and flow footprint acquisition / path reconstruction strategies, which not only supports network attack tracing applications, but also supports network management applications such as network monitoring and traffic auditing.

[0096] In the inter-domain IP tracing solution, the present invention defines an IP flow This means all IP packets with the same routing path. These packets have the following common characteristics: in, express The source IP address, represents the source autonomous domain IP address prefix of flow i, express The destination IP address of these packets is the same, so we use dst i Therefore, an ideal IP flow identifier should be However, when facing a source IP address spoofing attack, for example, a packet p with a source IP address spoofing attack s ∈PFX1, its source IP address src s Forgery Source IP address During the data packet propagation process, s and At the AS where aggregation occurs, the current flow identifier will identify the two as the same flow i, that is, the current flow identifier has inherent traceability misreporting. Therefore, the ideal IP flow identifier Not feasible, a new flow identifier needs to be defined.

[0097] Inspired by the Multi-Protocol Label Switching protocol, this invention introduces a new dynamic label Indicates AS m The label assigned to flow i is unique within the domain and is only available in AS m Internally valid, used to distinguish different flows that are aggregated. m At, flow i can be used The only indication. Indicates AS m The captured flow i’s footprint information reflects the forwarding traces of flow i in the autonomous domain-level network. m-1 Indicates the upstream autonomous domain AS m-1 Autonomous domain number, Indicates AS m-1 The label assigned to flow i. If the autonomous domain number uses the 32-bit public autonomous domain number assigned by the Internet Assigned Numbers Authority (IANA), the storage overhead for autonomous domains in the root alliance and the intermediate alliance is huge; secondly, the public autonomous domain number can be used as a data flow label by malicious network attackers to analyze the routing path, which has the risk of privacy leakage. Referring to the principle of hierarchical reuse of IP addresses, the hierarchical autonomous AS proposed in the present invention m The domain number allocation mechanism allocates scalable private autonomous domain numbers to alliances at different levels, and does not use public autonomous domain numbers. Alliances can independently allocate private autonomous domain numbers to autonomous domains, as long as they are unique within the alliance.

[0098] In view of the different scales of alliances at different levels, the autonomous domain number with a length of a first threshold is configured for the autonomous domain of the root alliance, the autonomous domain number with a length of a second threshold is configured for the autonomous domain of the intermediate alliance, and the autonomous domain number with a length of a third threshold is configured for the autonomous domain of the low-level alliance, wherein the first threshold is less than the second threshold, and the second threshold is less than the third threshold. Figure 4 As shown, according to the different scales of alliances at different levels, the present invention allocates a 4-bit autonomous domain number to the root alliance, a 16-bit autonomous domain number (including the 4-bit root alliance autonomous domain number) to the intermediate alliance, and a 32-bit autonomous domain number (including the 16-bit intermediate alliance autonomous domain number) to the lower-level alliance. 10 Assign a 4-digit Autonomous Network Number (ASN) 10= 0xA, and the 16-bit autonomous domain numbers ASN3 = 0xA111 and ASN6 = 0xA112 are allocated to AS3 in the middle alliance IA#1 and AS6 in IA#2 respectively; and the 32-bit autonomous domain numbers ASN1 = 0xA1110001 and ASN4 = 0xA1120001 are allocated to AS1 in the lower alliance LA#1 and AS4 in LA#2 respectively. For autonomous domains in both the upper and lower alliances, the autonomous domain number allocated by the upper alliance shall prevail.

[0099] Based on this, the present invention proposes an inter-domain IP traceability alliance method based on a layered blockchain based on a provided inter-domain IP traceability alliance system, wherein the inter-domain IP traceability alliance method based on a layered blockchain includes a hierarchical inter-domain IP traceability scheme and an inter-domain IP traceability transaction processing flow based on a layered blockchain, wherein the traceability transaction is implemented based on the hierarchical inter-domain IP traceability scheme, and for the autonomous domain that deploys the hierarchical inter-domain IP traceability scheme, the hierarchical inter-domain IP traceability scheme includes: a process in which the autonomous domain through which the IP data stream i passes during transmission performs flow marking and flow fingerprint generation on the IP data stream i, and a process in which the autonomous domain with traceability requirements obtains flow footprints or reconstructs flow transmission paths for the IP data stream i, wherein the IP data stream Said is the first data packet in IP data stream i, is the second data packet in IP data stream i, It is the oth data packet in IP data stream i. The routing paths of data packets in the same IP data stream are the same.

[0100] For IP data flow i from autonomous domain AS m-1 To the Autonomous Domain AS m The data transmission process, the flow marking and flow fingerprint generation strategy specifically includes:

[0101] Flow marking: In IP data flow First, the autonomous domain AS m-1 Sample the data packets and obtain one of the data packets of data stream i In the autonomous domain AS m-1 The query is made in the local flow fingerprint database of the autonomous domain AS. m-1 The fingerprint of data stream i is queried in the local stream fingerprint library Extract fingerprint Tags in If in the autonomous domain AS m-1 The fingerprint of data stream i is not found in the local stream fingerprint library The data packet obtained by sampling Assign new labels Autonomous Domain (AS) m-1 Autonomous Network Number ASN m-1 and tags Write The unused field of the packet is forwarded to the autonomous domain AS. m ;

[0102] Flow fingerprint generation: AS m Receive AS m-1 Marked Packets After that, the ASN m-1 and of Extract information and obtain flow footprint Among them, the dst i Indicates data packet Destination IP address, according to the flow footprint In the autonomous domain AS m The local flow fingerprint database is searched to determine the autonomous domain AS m Whether the flow fingerprint of IP data flow i already exists in the local flow fingerprint database in the autonomous domain AS m If the flow fingerprint of IP data flow i exists in the local flow fingerprint library of the autonomous domain AS m Only the flow marking policy needs to be implemented. m If the flow fingerprint of IP data flow i does not exist in the local flow fingerprint database of the autonomous domain AS m Generate a flow fingerprint for IP data flow i. Specifically, assign a label to data flow i According to the flow footprint and tags Generate flow fingerprint The flow fingerprint is stored. The specific flow fingerprint generation process is expressed by the following formula:

[0103]

[0104] Among them, function f(·) is the function of generating flow fingerprint, SampleFlow() represents the sampling operation, i represents the IP data flow, Indicates an autonomous domain AS m Flow fingerprint Stored in the local flow fingerprint library.

[0105] For autonomous domains with traceability requirements m The process of obtaining the flow footprint or reconstructing the flow transmission path of IP data flow i adopts the flow footprint acquisition or flow path reconstruction strategy, which specifically includes: Autonomous domain AS m According to the sampled data packets Extracting Data Packets Destination IP address dsti and tags Read the stream fingerprint in the local stream fingerprint library Based on flow fingerprint Get flow footprint and the previous hop ASN of IP data flow i m-1 , specifically, the one-hop routing path of IP data flow i The flow footprint acquisition or flow path reconstruction strategy is expressed by the following formula:

[0106]

[0107] Among them, the function f -1 (·) is a function for obtaining flow footprint or reconstructing flow path, LoadFP() is a function for reading flow fingerprint, and UpAS represents the previous hop autonomous domain number of IP data flow i.

[0108] Figure 5 The overall example of the hierarchical inter-domain IP tracing solution is shown. The fields of the flow fingerprint table established by the tracing autonomous domain include the upstream autonomous domain number UpAS of flow i, the label InL allocated by the upstream autonomous domain, the identifier FID of flow i, and the label OutL allocated by the autonomous domain. Figure 5 As shown, Transit AS 10 、Transit AS 13 AS4 and AS1 do not deploy IP tracing solutions, so they do not perform flow marking and flow fingerprint generation operations on the passing flows. Assuming that device D4 in AS4 is a legitimate device and communicates normally with device D2 in AS1, its traffic is recorded as L-F2. At the same time, the zombie machine in AS5 forges the source IP address of device D4 and launches an attack on device D2, and its attack flow is recorded as A-F2. n When flow A-F2 is detected, the autonomous domain number ASN5 and the assigned label L5 are written into any data packet belonging to flow A-F2 according to the flow marking strategy. Then a flow fingerprint entry is created for it. Among them, * represents null, which means that the current autonomous domain is the source autonomous domain of flow A-F2. Since the "autonomous domain number + label" proposed in the present invention is globally unique, in order to reduce the storage overhead of the autonomous domain's flow fingerprints to store more flow fingerprints, without affecting the traceability accuracy, the present invention uses fewer flow feature fields and only uses the destination IP address to represent a flow. Therefore, the FID item in the figure uses the destination IP address. When AS6 first detects the legitimate flow L-F2, it extracts Then use the autonomous domain number ASN6 and the assigned label L 6-1 Re-mark and forward; finally create flow fingerprint When AS6 detects attack flow A-F2, it extracts Although the current attack flow uses a forged source IP address, the label it carries is completely different from L-F2. Therefore, A-F2 is considered a different flow. AS6 then uses its own autonomous domain number ASN6 and the new label L 6-2 Re-mark and forward; finally create flow fingerprint The operation of AS3 is the same. When device D2 detects attack flow A-F2 and needs to trace the source, it first extracts the footprint information of A-F2. Confirm that the previous hop traceability AS is AS3 and the assigned label is L 3-2 ; Then, AS1 will As the traceability request information, a traceability request is initiated to AS3. Finally, AS3 receives the traceability request information and executes the query local stream fingerprint library function Returns the flow fingerprint And generate flow footprint As the traceability response information. So far, the two-hop routing paths AS6|AS3 and AS3|AS1 have been reconstructed. If D2 needs to reconstruct the complete routing path, continue to iterate the above process until the traceability is completed.

[0109] Finally, based on the above-mentioned inter-domain IP traceability alliance system based on layered blockchain and hierarchical inter-domain IP traceability solution, the present invention introduces the inter-domain IP traceability transaction processing flow based on layered blockchain.

[0110] Among them, the inter-domain IP traceability transaction processing flow based on layered blockchain includes four stages, namely autonomous domain registration, traceability request, traceability response and traceability transfer. According to whether the two parties involved in the traceability transaction are in the same alliance, the traceability transaction can also be divided into intra-alliance traceability transaction and cross-alliance traceability transaction. Both intra-alliance and cross-alliance transactions include the above four stages. Intra-alliance traceability transactions only involve the operation of one blockchain and are processed by the consensus algorithm within the blockchain (such as the PBFT consensus algorithm).

[0111] The present invention only considers the cross-alliance traceability transaction processing flow based on the layered blockchain. The Leader node of each layer of the blockchain is responsible for encapsulating the cross-alliance traceability transaction and its proof into a cross-chain message and forwarding it. The least common ancestor blockchain of the blockchain related to the cross-alliance traceability transaction serves as a third-party notary to verify the validity and authenticity of the cross-chain message and ensure the atomicity of the transaction and the consistency of the blockchain state. In addition, for cross-alliance traceability transfer transactions involving cross-chain asset transfers, the present invention proposes a cross-alliance traceability transfer transaction processing flow based on a coordinator. Using the least common ancestor blockchain that serves as a third-party notary as a coordinator, in addition to verifying the cross-chain message, it is also responsible for maintaining the atomicity of the cross-alliance traceability transfer transaction and the consistency of the blockchain where the two parties to the transaction are located, and promptly handling abnormal situations. The multi-coordinator feature under the layered blockchain system architecture solves the single-point bottleneck problem faced by the traditional single coordinator and improves the scalability of the system.

[0112] The process of autonomous domain registration includes the following steps:

[0113] Step A1: Newly joined autonomous domain AS k Submit a registration transaction to the blockchain of the current alliance. The registration transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the autonomous domain AS k The autonomous domain number, autonomous domain prefix, public key, account address and service fee are as follows: the autonomous domain prefix refers to the usable IP address range allocated by the Internet management agency to the autonomous domain; the public key and account address of the autonomous domain are generated by the autonomous domain itself; the service fee of the autonomous domain refers to the fee for the autonomous domain to provide a traceability service once; the sender address refers to the account address of the newly joined autonomous domain; and the receiver address refers to the account addresses of all other autonomous domains in the current alliance.

[0114] Step A2: After receiving the registration transaction, the blockchain of the current alliance executes the consensus algorithm within the chain and calculates the autonomous domain number ASN in the registration transaction. k , Autonomous Domain Number ASN k With the autonomous domain prefix Pre k The mapping relationship is verified. If the verification is passed, the registration transaction is stored on the blockchain of the current alliance and step A3 is executed. If the verification is not passed, the registration transaction is cancelled.

[0115] Step A3: If the current alliance is at the 0th level, execute steps A4 to A8; if the current alliance is at the 1st level, execute steps A5 to A8; if the current alliance is at the 2nd level, execute steps A7 to A8.

[0116] Step A4: The monitoring autonomous domain of the current alliance summarizes the information of all newly registered autonomous domains within a preset time period. k Information summary S k The information summary includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number of the autonomous domain, and generates a state summary transaction TX BS =(S1,S2,...,S k ), the state summary transaction includes the information summary of all newly registered autonomous domains within a preset time period, and then the state summary transaction TX BS =(S1,S2,...,S k ) is sent to the intermediate blockchain of the Layer 1 alliance with which the current alliance has data transmission.

[0117] The information summary of the newly registered autonomous domain can be expressed as S k ={ASN k |PK k ,Addr k ,C k ,T k}, where ASN k Indicates an autonomous domain AS k Autonomous domain number, Pre k Indicates the autonomous domain prefix, Addr k Indicates the account address, PK k represents the public key, C k Indicates service fee, T k Indicates the blockchain number to which it belongs; and generates a status summary transaction TX BS =(S1,S2,...,S k ), the state summary transaction includes the information summary of all newly registered autonomous domains within a preset time period, and then the state summary transaction TX BS =(S1,S2,...,S k ) is sent to the intermediate blockchain of the first layer alliance that has the first connection network with the current alliance.

[0118] Step A5: The intermediate blockchain receives the state summary transaction TX sent by the monitoring autonomous domain of the 0th layer alliance BS =(S1,S2,...,S k ) and summarize the status transaction TX BS =(S1,S2,...,S k ) executes the consensus algorithm to TX BS Consensus is reached. If the consensus is passed, the intermediate blockchain will BS for storage.

[0119] Step A6: The monitoring autonomous domain of the alliance where the intermediate blockchain is located summarizes the information summary of all newly registered autonomous domains and the status summary transaction TX of the leaf blockchain BS , and generate a new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ), and then the new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) is sent to the root blockchain.

[0120] Step A7: The root blockchain receives the new state summary transaction TX' sent by the listening autonomous domain of the layer 1 alliance BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r );and summarize the new state transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) executes the consensus algorithm and performs BS Consensus is reached. If the consensus is passed, TX' BS for storage.

[0121] Step A8: The root blockchain stores information of all newly registered autonomous domains.

[0122] Combination Figure 6 For example, the registration process may include the following steps:

[0123] (1) Newly joined autonomous domains need to register with the blockchain of the alliance to which they belong before they can participate in the traceability system. Figure 6 As shown, AS k Submit registration transaction TX to blockchain L-BC#1 reg =(ASN k ,Pre k ,PK k ,Addr k ,C k ), including the Autonomous Network Number (ASN) k , Autonomous domain prefix Pre k , Public Key PK k 、Account addressAddr kand service charge C k .

[0124] (2) L-BC#1 receives AS k After the registration transaction, the consensus algorithm in the chain is executed to ASN k and ASN k With Pre k The legitimacy of the mapping relationship is verified. If it passes the verification, it will be stored on L-BC#1 to realize the information disclosure within the alliance.

[0125] (3) L-BC#1 performs the autonomous domain information synchronization operation, and the leader node summarizes the recently added autonomous domain information, that is, Figure 6 The user information summary in the , and then initiates a new state summary transaction TX to the upper blockchain (I-BC#1). BS =(S1,S2,...,S k ). k Autonomous domain information summary S k ={ASN k |PK k ,Addr k ,C k ,T k}, where T k Indicates AS k The blockchain ID to which it belongs.

[0126] (4) I-BC#1 executes the consensus algorithm within the chain and BS Reach consensus, then store on the chain to complete the synchronization of autonomous domain information at this layer.

[0127] (5) The Leader of I-BC#1 also summarizes the information summary of the newly registered autonomous domains in the alliance and the status summary transaction TX of the leaf blockchain BS , and execute step (3) in the same way, and finally initiate a new state summary transaction TX' to R-BC BS =(S1,S2,...,S k ,S k+1 ,...).

[0128] (6) R-BC executes the consensus algorithm within the chain, and BS Reach consensus, then store on the chain to achieve global autonomous domain information synchronization.

[0129] The process of the traceability request includes the following steps:

[0130] Step 1.1: Initiate a traceability request transaction in the blockchain of the alliance to which the traceability requester of the IP data stream belongs. The traceability request transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the destination IP address and label of the IP data stream. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder.

[0131] Step 1.2: The blockchain of the alliance to which the traceability requester belongs receives the traceability request transaction, reaches consensus on the traceability request transaction, and stores the traceability request transaction on the blockchain.

[0132] Step 1.3: The monitoring autonomous domain of the alliance where the tracing requester is located detects that the recipient of the tracing request transaction is not in the current alliance, and generates a first cross-chain message, which includes the tracing request transaction, the proof of the tracing request transaction, the block header of the block where the tracing request transaction is located, and the number of the blockchain where the sender and recipient of the tracing request transaction are located; then, the monitoring autonomous domain sends the first cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchain where the sender and recipient of the tracing request transaction are located.

[0133] Step 1.4: The least common ancestor blockchain parses the first cross-chain message, verifies the traceability request transaction and its proof, stores the verification result on the least common ancestor blockchain, and encapsulates the first cross-chain message and the verification result into a second cross-chain message and sends it to the blockchain where the recipient of the traceability request transaction is located.

[0134] Step 1.5: The blockchain where the recipient of the traceability request transaction is located receives the second cross-chain message, parses the second cross-chain message, obtains the first cross-chain message and the verification result, and when the verification result indicates that the verification is passed, sends the traceability request transaction in the first cross-chain message to the traceability responder.

[0135] Combination Figure 7 For example, the traceability request process may include the following steps:

[0136] (1) Figure 7 As shown in the figure, autonomous domain AS1 needs to use the traceability service of autonomous domain AS5, and expects AS5 to respond to the previous autonomous domain of flow A-F2. Therefore, AS1 initiates a traceability request transaction to its blockchain. in, Indicates the traceability request information of AS1. Addr1 and Addr5 represent TX rst The sender and receiver addresses.

[0137] (2) L-BC#1 pair transaction TX rst The consensus is reached and stored on the blockchain.

[0138] (3) The leader node of L-BC#1 detects TX rst The recipient of TX is not located in this alliance. rst Request a transaction for cross-alliance traceability, so collect TX rst The relevant information is encapsulated as a cross-chain message in, Indicates TX rst Merkle proof of H(Blk rst ) indicates TX rst The block header where T1 and T5 are located respectively indicates the blockchain number of the sender and receiver of the transaction. Then, the Leader sends Msg rst Sent to the upper blockchain I-BC#1 until TX rst The Lowest Common Ancestor blockchain (LCA). Figure 2 In the example, I-BC#1 happens to be TX rst LCA.

[0139] (4) LCA parses cross-chain message Msg rst , for transaction TX rst Verify the authenticity and integrity of Stored on this blockchain, verification results Mainly includes cross-chain message Msg rst The ID, verification status (verification passed or failed), proof data, timestamp and verifier signature. Finally, LCA sends the cross-chain message Msg rst And verification results Encapsulate into a new cross-chain message Msg' rst Send to TX rst The recipient blockchain L-BC#2.

[0140] (5) L-BC#2 parses Msg' rst , view the verification results If the verification is successful, it indirectly indicates that TX rst It has been submitted correctly on L-BC#1.

[0141] (6) L-BC#2 sends TX rst Sent to the receiver AS5.

[0142] The traceability response process includes the following steps:

[0143] Step 2.1: After receiving the tracing request transaction, the tracing responder extracts the flow tag, queries the local flow fingerprint library, and generates the flow footprint and the previous hop autonomous domain number in the flow path, and then initiates a tracing response transaction to the blockchain of the alliance. The tracing response transaction includes: transaction content, sender address and receiver address of the transaction. The transaction content includes the flow footprint and the previous hop autonomous domain number in the flow path. The sender address refers to the account address of the tracing responder, and the receiver address refers to the account address of the tracing requester.

[0144] Step 2.2: The blockchain of the alliance to which the traceability responder belongs receives the traceability response transaction, reaches consensus on the traceability response transaction, and stores the traceability response transaction on the blockchain.

[0145] Step 2.3: The monitoring autonomous domain of the alliance where the tracing response party is located detects that the recipient of the tracing response transaction is not in the current alliance, and generates a third cross-chain message, wherein the third cross-chain message includes the tracing response transaction, the proof of the tracing response transaction, the block header of the block where the tracing response transaction is located, the number of the blockchain where the sender of the tracing response transaction is located, and the number of the blockchain where the recipient is located; then, the monitoring autonomous domain sends the third cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchain where the sender and recipient of the tracing response transaction are located.

[0146] Step 2.4: The least common ancestor blockchain parses the third cross-chain message, verifies the provenance response transaction and the proof of the provenance response transaction, stores the verification result on the least common ancestor blockchain, and encapsulates the third cross-chain message and the verification result into a fourth cross-chain message and sends it to the blockchain where the recipient of the provenance response transaction is located.

[0147] Step 2.5: The blockchain where the recipient of the traceability response transaction is located receives the fourth cross-chain message, parses the fourth cross-chain message, obtains the third cross-chain message and the verification result, and sends the traceability response transaction to the traceability requester when the verification result indicates that the verification is passed.

[0148] Combination Figure 7 For example, the traceability response may include the following steps:

[0149] (1) Figure 7 As shown in the figure, after AS5 receives the traceability request from AS1, it executes the query local flow fingerprint library function And generate flow footprint AS5 initiates a traceability response transaction to its blockchain L-BC#2

[0150] (2) L-BC#2 transaction TX rsp The consensus is reached and stored on the blockchain.

[0151] (3) The leader node of L-BC#2 detects TX rsp The recipient of TX is not located in this alliance. rsp For a cross-alliance traceability response transaction, TX is collected rsp The relevant information is encapsulated as a cross-chain message in, Indicates TX rsp Merkle proof of H(Blk rsp ) indicates TX rsp Then, the Leader sends Msg rsp Sent to the upper blockchain I-BC#1 until TX rsp The least common ancestor blockchain LCA.

[0152] (4) LCA parses cross-chain message Msg rsp , for transaction TX rsp Verify the authenticity and integrity of Stored on this blockchain, verification results Mainly includes cross-chain message Msg rsp The ID, verification status (verification passed or failed), proof data, timestamp and verifier signature. Finally, LCA sends the cross-chain message Msg rsp And verification results Encapsulate into a new cross-chain message Msg' rsp Send to TX rsp The recipient blockchain L-BC#1.

[0153] (5) L-BC#1 parses Msg' rsp , view the verification results If the verification is successful, it indirectly indicates that TX rsp It has been submitted correctly on L-BC#2.

[0154] (6) L-BC#1 sends TX rsp Sent to the receiver AS1, and AS1 obtains the expected response information.

[0155] The process of tracing the source of the transfer includes the following steps:

[0156] Step B1: Withdrawal consensus

[0157] Step B1.1: The tracing requester initiates a tracing transfer transaction to the blockchain of the alliance to which it belongs. The tracing transfer transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the service fee of the tracing responder. The sender address refers to the account address of the tracing requester, and the receiver address refers to the account address of the tracing responder.

[0158] Step B1.2: The blockchain of the alliance to which the tracing requester belongs reaches a consensus on the tracing transfer transaction and checks whether the account balance of the tracing requester satisfies the service fee of the tracing responder. If the account balance of the tracing requester does not meet the service fee requirement of the tracing responder, the tracing transfer transaction is canceled. If the account balance of the tracing requester meets the service fee of the tracing responder, the account balance of the tracing requester is withdrawn, and the amount of the withdrawal is the service fee of the tracing responder.

[0159] Step B2. Withdrawal transaction proof delivery

[0160] Step B2.1: The monitoring autonomous domain of the alliance where the traceability requester is located detects that the recipient of the traceability transfer transaction is not in the current alliance, and encapsulates the traceability transfer transaction, the proof of the traceability transfer transaction, the block header of the block where the traceability transfer transaction is located, and the numbers of the blockchains where the sender and receiver of the traceability transfer transaction are located into a fifth cross-chain message. The monitoring autonomous domain sends the fifth cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchains where the sender and receiver of the traceability transfer transaction are located.

[0161] Step B2.2: The least common ancestor blockchain parses the fifth cross-chain message, verifies the traceability transfer transaction and its proof, and stores the verification result on this blockchain. If the verification fails, a rollback message is sent to the blockchain where the sender of the traceability transfer transaction is located, including the proof of verification failure, and the processing flow of the traceability transfer transaction is terminated; if the verification passes, it is searched whether there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted. If not, the least common ancestor blockchain encapsulates the fifth cross-chain message and the verification result into a sixth cross-chain message and sends it to the blockchain where the recipient of the traceability transfer transaction is located; if there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted, the least common ancestor blockchain needs to wait for the other cross-alliance traceability transfer transactions to be successfully submitted or terminated before the sixth cross-chain message can be sent to the blockchain where the recipient of the traceability transfer transaction is located.

[0162] Step B3. Deposit Transaction Consensus

[0163] Step B3.2: The blockchain where the recipient of the traceability transfer transaction is located parses the sixth cross-chain message to obtain the fifth cross-chain message and the verification result. If the verification result indicates that the verification is successful, it indicates that the traceability transfer transaction is correctly submitted on the blockchain where the sender is located. The traceability responder initiates a deposit transaction to the blockchain of the alliance where it is located. The deposit transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the proof of the traceability transfer transaction and the service fee of the traceability responder. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder. The blockchain of the alliance where the traceability responder is located reaches a consensus on the deposit transaction to realize the account deposit of the traceability responder, and the amount of the deposit is the service fee.

[0164] Step B3.3: The monitoring autonomous domain of the alliance where the traceability responder is located encapsulates the deposit transaction, the proof of the deposit transaction, the block header of the block where the deposit transaction is located, and the number of the blockchain where the sender and receiver of the deposit transaction are located into the seventh cross-chain message, and sends the seventh cross-chain message to the least common ancestor blockchain of the blockchain where the sender and receiver of the deposit transaction are located.

[0165] Step B4.4. Submit

[0166] The least common ancestor blockchain parses the seventh cross-chain message, verifies the deposit transaction and its proof, and stores the verification result on the least common ancestor blockchain. If the verification result indicates that the verification is successful, a submission message is sent to the blockchains where the sender and receiver of the traceability transfer transaction are located respectively. The submission message indicates that the traceability transfer transaction is successfully submitted, and the process ends; if the verification result indicates that the verification is not successful or the least common ancestor blockchain does not receive the seventh cross-chain message within a preset time period, step B5 is executed.

[0167] Step B5. Rollback

[0168] The least common ancestor blockchain sends a rollback message to the blockchains of the sender and receiver of the traceability transfer transaction respectively. If the verification fails, the rollback message includes the verification result and proof of the deposit transaction; if it is a timeout, the rollback message includes the proof of timeout of the traceability transfer transaction, the blockchain where the sender is located executes the reverse operation of the traceability transfer transaction, and the blockchain where the receiver is located executes the reverse operation of the deposit transaction.

[0169] Combination Figure 8 For example, a traceable transfer may include the following steps:

[0170] like Figure 8 As shown in the figure, the coordinator-based cross-alliance traceability transfer transaction processing process includes the following five steps: withdrawal consensus, withdrawal proof transmission, deposit consensus, submission and rollback.

[0171] Step A. Withdrawal consensus

[0172] (1) AS1 initiates a traceability transfer transaction TX to its blockchain L-BC#1 tsf =(C5):Addr1→Addr5. C5 represents the service fee of AS5 and also represents the transfer amount of AS1.

[0173] (2) L-BC#1 pair transaction TX tsf Conduct in-chain consensus, first check whether the account balance of AS1 meets the service fee requirements of AS5, if not, cancel TX tsf ; Secondly, withdraw the account balance of AS1, and the withdrawal amount is the service fee of AS5.

[0174] Step B. Withdrawal Proof Delivery

[0175] (3) The leader node of L-BC#1 detects TX tsf The recipient of TX is not located in this alliance. tsf For a cross-alliance traceability transfer transaction, TX is collected tsf The relevant information is encapsulated as a cross-chain message in, Indicates TX tsf Merkle proof of H(Blk tsf ) indicates TX tsf The block header where T1 and T5 are located respectively indicates the blockchain number of the sender and receiver of the transaction. Then, the Leader sends Msg tsf Sent to the upper blockchain I-BC#1 until TX tsf The least common ancestor blockchain LCA.

[0176] (4) LCA first parses the cross-chain message Msg tsf , for transaction TX tsf Verify the authenticity and integrity of Stored on this blockchain, verification results Mainly includes cross-chain message Msg tsf ID, verification status (verification passed or failed), proof data, timestamp and verifier signature. If the verification fails, a rollback message is sent to L-BC#1 with a proof of failure. If the verification is successful, LCA checks whether there are other cross-alliance traceability transfer transactions with the same autonomous domain that have not been submitted. If not, LCA will send the cross-chain message Msg tsf And verification results Encapsulated into a new cross-chain message Msg′ tsf Send to TXtsf The recipient blockchain L-BC#2. If it exists, it needs to wait for other transactions to terminate successfully before it can be delivered.

[0177] Step C. Deposit Consensus

[0178] (5) L-BC#2 first parses Msg t ' sf , view the verification results If the verification is successful, it indirectly indicates that TX tsf It has been submitted correctly on L-BC#1. Secondly, AS5 initiates the deposit transaction L-BC#2 to TX t ' sf Conduct in-chain consensus and complete AS5 account deposit.

[0179] (6) The Leader node of L-BC#2 collects TX t ' sf The relevant information is encapsulated as a cross-chain message Then, Leader will send Msg t ' sf Send to LCA.

[0180] Step D. Submit

[0181] (7) LCA analysis Msg t ' sf , for transaction TX t ' sf Verify the authenticity and integrity of Stored on this blockchain. Then send TX tsf The related blockchains L-BC#1 and L-BC#2 send a submission message, indicating that TX tsf Successfully submitted. Otherwise, if LCA is on the transaction TX t ' sf Verification failed or no Msg was received within the specified time t ' sf , then handle it according to the abnormal situation and go to step E.

[0182] Step E. Rollback

[0183] If LCA deposit transaction TX t ' sf If the verification result is failed or timed out, a rollback message is sent to L-BC#1 and L-BC#2 respectively, with the verification result of failed. Or proof of timeout. L-BC#1 and L-BC#2 need to complete TX tsf and TX t 'sf The reverse operation.

[0184] The key point of the present invention is that the inter-domain IP traceability alliance system and method based on layered blockchain proposed in the present invention mainly include an inter-domain IP traceability alliance system architecture based on layered blockchain, a hierarchical inter-domain IP traceability solution and an inter-domain IP traceability transaction processing flow based on layered blockchain.

[0185] First, the proposed inter-domain IP traceability alliance system architecture based on layered blockchain enables different alliances to execute traceability transactions within the alliance in parallel, achieving high throughput and high scalability; utilizing the state sharding mechanism, each blockchain only records IP traceability transactions within the alliance, achieving low storage load on the blockchain; a proposed user information synchronization mechanism and cross-chain message passing mechanism solve the consistency problem of the layered blockchain system under state sharding.

[0186] Secondly, the proposed hierarchical inter-domain IP tracing solution adopts hierarchical autonomous domain number allocation, which reduces the storage overhead of the core autonomous domain; the proposed flow labeling and flow fingerprint generation strategy reduces the false alarm rate of tracing.

[0187] Finally, the proposed inter-domain IP traceability transaction processing flow based on layered blockchain proposes to use the least common ancestor blockchain of the blockchain related to the cross-alliance traceability transaction as the third-party notary of the cross-alliance traceability transaction, responsible for the verification and transmission of cross-chain messages. This will ensure that the verification process of all cross-alliance traceability transactions can be audited and traced, improving the credibility and transparency of the system. For cross-alliance traceability transfer transactions involving cross-chain asset transfers, a cross-alliance traceability transfer transaction processing flow based on a coordinator is proposed to achieve the atomicity of the transaction and the consistency of the blockchain state. Among them, the least common ancestor blockchain with the role of a third-party notary can serve as a coordinator, which improves the degree of decentralization and solves the performance bottleneck of a single coordinator.

[0188] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) to form a technical solution.

Claims

1. An inter-domain IP traceability alliance system based on hierarchical blockchain, characterized in that: The inter-domain IP traceability alliance system based on layered blockchain consists of layer 0, layer 1 and layer 2; The 0th layer includes a plurality of lower-level alliances, the lower-level alliance includes a plurality of autonomous domains of the access layer and an autonomous domain of the tandem layer, the autonomous domain of the tandem layer serves as a monitoring autonomous domain of the lower-level alliance, the autonomous domain of the access layer transmits data to the autonomous domain of the tandem layer, the access layer includes a plurality of autonomous domains at the edge of the network, and the tandem layer includes a plurality of autonomous domains between the edge of the network and the core of the network; A low-level alliance also includes a leaf blockchain, which is used to store information about autonomous domains in the low-level alliance, including registration information about autonomous domains. For traceability transactions within the alliance where the sender and the receiver are in the same low-level alliance, the leaf blockchain is also used to reach a consensus on the traceability transactions within the alliance, where the sender is the autonomous domain of the initiator of the traceability transaction within the alliance, and the receiver is the autonomous domain of the receiver of the traceability transaction within the alliance. For cross-alliance traceability transactions where the sender and the receiver are not in the same low-level alliance, after the leaf blockchain reaches a consensus on the cross-alliance traceability transaction, the leaf blockchain in the low-level alliance where the leaf blockchain is located will be recorded. The monitoring autonomous domain of the higher-level alliance is used to send the cross-alliance traceability transactions, the proof of the cross-alliance traceability transactions and the block header of the block where the cross-alliance traceability transactions are located in the lower-level alliance in the form of cross-chain messages to the intermediate blockchain until the minimum common ancestor blockchain. The minimum common ancestor blockchain contains the information summary of the sender corresponding to the cross-alliance traceability transaction and the information summary of the receiver corresponding to the cross-alliance traceability transaction, and has the smallest distance from the blockchain where the sender is located and the blockchain where the receiver is located. The information summary of the autonomous domain includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number in the autonomous domain registration information; The first layer includes multiple intermediate alliances, the intermediate alliance includes multiple autonomous domains of the convergence layer and one autonomous domain of the core layer, the multiple autonomous domains of the convergence layer include the monitoring autonomous domain in the low-level alliance, the core layer includes multiple autonomous domains in the core of the network, the autonomous domain of the core layer serves as the monitoring autonomous domain of the intermediate alliance, and the autonomous domain of the convergence layer transmits data to the autonomous domain of the core layer; An intermediate alliance also includes an intermediate blockchain, which is used to store information of autonomous domains in the intermediate alliance and information summaries of autonomous domains of leaf blockchains; for traceability transactions within the alliance where the sender and the receiver are in the same intermediate alliance, the intermediate blockchain is also used to reach consensus on the traceability transactions within the alliance; for cross-alliance traceability transactions where the sender and the receiver are not in the same alliance, the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located is used to send the cross-alliance traceability transactions in the intermediate alliance, the proof of the cross-alliance traceability transactions, and the block header of the block where the cross-alliance traceability transactions are located to the root blockchain in the form of cross-chain messages; in the case of cross-alliance traceability transactions where the lower-level alliance where the sender is located and the lower-level alliance where the receiver is located are not the same lower-level alliance, and the intermediate blockchain contains the information summary of the sender and the information summary of the receiver corresponding to the cross-alliance traceability transaction, the intermediate blockchain is used as the minimum common ancestor blockchain, and the intermediate blockchain is used to verify and transmit cross-chain messages between the leaf blockchain where the sender of the cross-alliance traceability transaction is located and the leaf blockchain where the receiver is located; The second layer includes a root alliance, which includes all autonomous domains of the core layer; a root alliance contains a root blockchain, which is used to store information of autonomous domains in the root alliance, and also stores information summaries of autonomous domains in lower-level alliances and information summaries of autonomous domains in intermediate alliances; for traceability transactions within the root alliance, the root blockchain is also used to reach consensus on traceability transactions within the root alliance; in the case of cross-alliance traceability transactions where the sender and receiver are not in the same alliance and there is no intermediate blockchain that meets the conditions for serving as the minimum common ancestor blockchain, the root blockchain is used as the minimum common ancestor blockchain, and the root blockchain is used to verify and transmit cross-chain messages between the blockchain where the sender and the blockchain where the receiver of the cross-alliance traceability transaction are located.

2. The inter-domain IP traceability alliance system based on layered blockchain according to claim 1 is characterized in that: The inter-domain IP traceability alliance system based on the hierarchical blockchain realizes the synchronization of autonomous domain information between the upper and lower level alliances in the following ways: The monitoring autonomous domain in the lower-level alliance where the leaf blockchain is located obtains the information summary of the autonomous domain that needs to achieve information synchronization. The monitoring autonomous domain of the lower-level alliance where the leaf blockchain is located initiates a state summary transaction to the upper-level intermediate blockchain based on the obtained information summary of the autonomous domain. The state summary transaction contains the information summary of the autonomous domain obtained by the monitoring autonomous domain. The intermediate blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the intermediate blockchain to achieve information synchronization of the autonomous domains within the alliance; the monitoring autonomous domain of the intermediate alliance where the intermediate blockchain is located obtains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance, and initiates a state summary transaction to the upper-level root blockchain. The state summary transaction contains the information summary of the autonomous domain within the alliance and the information summary of the autonomous domain from the lower-level alliance. The root blockchain reaches a consensus on the state summary transaction. After the consensus is passed, the information summary of the autonomous domain in the state summary transaction is stored in the root blockchain to achieve global synchronization of autonomous domain information; For cross-alliance traceability transactions between two alliances, according to the third-party notary mechanism, the least common ancestor blockchain of the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located is determined as the third-party notary. Specifically, according to the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located, the least common ancestor blockchain is determined. The least common ancestor blockchain contains both the information summary of the sender and the information summary of the receiver, and has the smallest distance from the blockchain where the sender is located and the blockchain where the receiver is located, wherein the distance between the blockchain where the sender is located and the blockchain where the receiver is located is the number of layers of the blockchain where the sender is located and the blockchain where the receiver is located. The least common ancestor blockchain is used to verify and transmit cross-chain messages between the blockchain where the sender of the cross-alliance traceability transaction is located and the blockchain where the receiver is located, and at the same time verify whether the cross-alliance traceability transaction actually exists in the blockchain where the sender is located or the blockchain where the receiver is located; the least common ancestor blockchain is also used to store the verification results of the cross-chain messages; for cross-alliance traceability transactions of the traceability transfer type, the least common ancestor blockchain is also used to ensure the atomicity of the cross-alliance traceability transaction and the state consistency of the blockchain where the sender of the traceability transaction is located and the blockchain where the receiver is located.

3. A method for inter-domain IP traceability alliance based on hierarchical blockchain, characterized in that: According to the inter-domain IP traceability alliance system based on layered blockchain according to claim 1, the inter-domain IP traceability alliance method based on layered blockchain at least includes a hierarchical inter-domain IP traceability solution; The traceability transaction is implemented based on a hierarchical inter-domain IP traceability solution. For the autonomous domain that deploys the hierarchical inter-domain IP traceability solution, the hierarchical inter-domain IP traceability solution includes: the autonomous domain through which the IP data stream i passes during transmission performs flow marking and flow fingerprint generation on the IP data stream i, and the autonomous domain with traceability requirements performs flow footprint acquisition or flow transmission path reconstruction on the IP data stream i. The IP data stream Said is the first data packet in IP data stream i, is the second data packet in IP data stream i, is the oth data packet in IP data stream i, and the routing paths of data packets in the same IP data stream are the same; For IP data flow i from autonomous domain AS m-1 To the Autonomous Domain AS m The data transmission process, the flow marking and flow fingerprint generation strategy specifically includes: Flow marking: In IP data flow First, the autonomous domain AS m-1 Sample the data packets and obtain one of the data packets of data stream i In the autonomous domain AS m-1 The query is made in the local flow fingerprint database of the autonomous domain AS. m-1 The fingerprint of data stream i is queried in the local stream fingerprint library Extract fingerprint Tags in If in the autonomous domain AS m-1 The fingerprint of data stream i is not found in the local stream fingerprint library The data packet obtained by sampling Assign new labels Autonomous Domain (AS) m-1 Autonomous Network Number ASN m-1 and tags Write The unused field of the packet is forwarded to the autonomous domain AS. m ; According to the different scales of alliances at different levels, an autonomous domain number with a length of a first threshold is configured for the autonomous domain of the root alliance, an autonomous domain number with a length of a second threshold is configured for the autonomous domain of the intermediate alliance, and an autonomous domain number with a length of a third threshold is configured for the autonomous domain of the low-level alliance, wherein the first threshold is smaller than the second threshold, and the second threshold is smaller than the third threshold; Flow fingerprint generation: AS m Receive AS m-1 Marked Packets After that, the ASN m-1 and of Extract information and obtain flow footprint Among them, the dst i Indicates data packet Destination IP address, according to the flow footprint In the autonomous domain AS m The local flow fingerprint database is searched to determine the autonomous domain AS m Whether the flow fingerprint of IP data flow i already exists in the local flow fingerprint database in the autonomous domain AS m If the flow fingerprint of IP data flow i exists in the local flow fingerprint library of the autonomous domain AS m Only the flow marking policy needs to be implemented. m If the flow fingerprint of IP data flow i does not exist in the local flow fingerprint database of the autonomous domain AS m Generate a flow fingerprint for IP data flow i. Specifically, assign a label to data flow i According to the flow footprint and tags Generate flow fingerprint The flow fingerprint is stored. The specific flow fingerprint generation process is expressed by the following formula: Among them, function f(·) is the function of generating flow fingerprint, SampleFlow() represents the sampling operation, i represents the IP data flow, Indicates an autonomous domain AS m Flow fingerprint Stored in the local flow fingerprint library; For autonomous domains with traceability requirements m The process of obtaining the flow footprint or reconstructing the flow transmission path of IP data flow i adopts the flow footprint acquisition or flow path reconstruction strategy, which specifically includes: Autonomous domain AS m According to the sampled data packets Extracting Data Packets Destination IP address dst i and tags Read the stream fingerprint in the local stream fingerprint library Based on flow fingerprint Get flow footprint and the previous hop ASN of IP data flow i m-1 , specifically, the one-hop routing path of IP data flow i The flow footprint acquisition or flow path reconstruction strategy is expressed by the following formula: Among them, the function f -1 (·) is a function for obtaining flow footprint or reconstructing flow path, LoadFP() is a function for reading flow fingerprint, and UpAS represents the previous hop autonomous domain number of IP data flow i.

4. The inter-domain IP traceability alliance method based on layered blockchain according to claim 3 is characterized in that: The inter-domain IP traceability alliance method based on the layered blockchain also includes an inter-domain IP traceability transaction processing flow based on the layered blockchain, wherein the inter-domain IP traceability transaction processing flow based on the layered blockchain at least includes autonomous domain registration, and the autonomous domain registration includes the following steps: Step A1: Newly joined autonomous domain AS k Submit a registration transaction to the blockchain of the current alliance. The registration transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the autonomous domain AS k The autonomous domain number, autonomous domain prefix, public key, account address and service fee. The autonomous domain prefix refers to the usable IP address range allocated by the Internet management agency to the autonomous domain. The public key and account address of the autonomous domain are generated by the autonomous domain itself. The service fee of the autonomous domain refers to the fee for the autonomous domain to provide a traceability service once. The sender address refers to the account address of the newly added autonomous domain. The receiver address refers to the account addresses of all other autonomous domains in the current alliance. Step A2: After receiving the registration transaction, the blockchain of the current alliance executes the consensus algorithm within the chain to verify the mapping relationship between the autonomous domain number and the autonomous domain prefix in the registration transaction. If the verification is successful, the registration transaction is stored on the blockchain of the current alliance and step A3 is executed. If the verification is not successful, the registration transaction is canceled. Step A3: If the current alliance is at level 0, execute steps A4 to A8; if the current alliance is at level 1, execute steps A5 to A8; if the current alliance is at level 2, execute steps A7 to A8; Step A4: The monitoring autonomous domain of the current alliance summarizes the information of all newly registered autonomous domains within a preset time period. k Information summary S k The information summary includes the autonomous domain number, autonomous domain prefix, account address, public key, service fee and blockchain number of the autonomous domain, and generates a state summary transaction TX BS =(S1,S2,...,S k ), the state summary transaction includes the information summary of all newly registered autonomous domains within a preset time period, and then the state summary transaction TX BS =(S1,S2,...,S k ) is sent to the intermediate blockchain of the first layer alliance that has data transmission with the current alliance; Step A5: The intermediate blockchain receives the state summary transaction TX sent by the monitoring autonomous domain of the 0th layer alliance BS =(S1,S2,...,S k ) and summarize the state transaction TX BS =(S1,S2,...,S k ) executes the consensus algorithm to TX BS Consensus is reached. If the consensus is passed, the intermediate blockchain will BS To store; Step A6: The monitoring autonomous domain of the alliance where the intermediate blockchain is located summarizes the information summary of all newly registered autonomous domains and the status summary transaction TX of the leaf blockchain BS , and generate a new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ), and then the new state summary transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) is sent to the root blockchain; Step A7: The root blockchain receives the new state summary transaction TX' sent by the listening autonomous domain of the layer 1 alliance BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r );and summarize the new state transaction TX' BS =(S1,S2,...,S k ,S k+1 ,S k+2 ,...,S k+r ) executes the consensus algorithm and performs BS Consensus is reached. If the consensus is passed, TX' BS To store; Step A8: The root blockchain stores information of all newly registered autonomous domains.

5. The inter-domain IP traceability alliance method based on layered blockchain according to claim 4 is characterized in that: The inter-domain IP traceability transaction processing flow based on the layered blockchain also includes a traceability request, and the traceability request includes the following steps: Step 1.1: Initiate a traceability request transaction to the blockchain of the alliance to which the traceability requester of the IP data stream belongs. The traceability request transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the destination IP address and label of the IP data stream. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder. Step 1.2: The blockchain of the alliance where the traceability requester belongs receives the traceability request transaction, reaches a consensus on the traceability request transaction, and stores the traceability request transaction on the blockchain; Step 1.3: The monitoring autonomous domain of the alliance where the tracing requester is located detects that the recipient of the tracing request transaction is not in the current alliance, and generates a first cross-chain message, which includes the tracing request transaction, the proof of the tracing request transaction, the block header of the block where the tracing request transaction is located, and the numbers of the blockchains where the sender and receiver of the tracing request transaction are located; then, the monitoring autonomous domain sends the first cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchains where the sender and receiver of the tracing request transaction are located; Step 1.4: The least common ancestor blockchain parses the first cross-chain message, verifies the traceability request transaction and its proof, stores the verification result on the least common ancestor blockchain, and encapsulates the first cross-chain message and the verification result into a second cross-chain message and sends it to the blockchain where the recipient of the traceability request transaction is located; Step 1.5: The blockchain where the recipient of the traceability request transaction is located receives the second cross-chain message, parses the second cross-chain message, obtains the first cross-chain message and the verification result, and when the verification result indicates that the verification is passed, sends the traceability request transaction in the first cross-chain message to the traceability responder.

6. The inter-domain IP traceability alliance method based on layered blockchain according to claim 5 is characterized in that: The inter-domain IP traceability transaction processing flow based on the layered blockchain also includes a traceability response, and the traceability response includes the following steps: Step 2.1: After receiving the tracing request transaction, the tracing responder extracts the flow tag, queries the local flow fingerprint library, generates the flow footprint and the previous hop autonomous domain number in the flow path, and then initiates a tracing response transaction to the blockchain of the alliance. The tracing response transaction includes: transaction content, the sender address and the receiver address of the transaction. The transaction content includes the flow footprint and the previous hop autonomous domain number in the flow path. The sender address refers to the account address of the tracing responder, and the receiver address refers to the account address of the tracing requester. Step 2.2: The blockchain of the alliance to which the traceability responder belongs receives the traceability response transaction, reaches a consensus on the traceability response transaction, and stores the traceability response transaction on the blockchain; Step 2.3: The monitoring autonomous domain of the alliance where the tracing response party is located detects that the recipient of the tracing response transaction is not in the current alliance, and generates a third cross-chain message, wherein the third cross-chain message includes the tracing response transaction, the proof of the tracing response transaction, the block header of the block where the tracing response transaction is located, the number of the blockchain where the sender of the tracing response transaction is located, and the number of the blockchain where the recipient is located; then, the monitoring autonomous domain sends the third cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchain where the sender and the recipient of the tracing response transaction are located; Step 2.4: The least common ancestor blockchain parses the third cross-chain message, verifies the provenance response transaction and the proof of the provenance response transaction, stores the verification result on the least common ancestor blockchain, and encapsulates the third cross-chain message and the verification result into a fourth cross-chain message and sends it to the blockchain where the recipient of the provenance response transaction is located; Step 2.5: The blockchain where the recipient of the traceability response transaction is located receives the fourth cross-chain message, parses the fourth cross-chain message, obtains the third cross-chain message and the verification result, and sends the traceability response transaction to the traceability requester when the verification result indicates that the verification is passed.

7. The inter-domain IP traceability alliance method based on layered blockchain according to claim 4 is characterized in that: The inter-domain IP traceability transaction processing flow based on the layered blockchain also includes traceability transfer, and the traceability transfer includes the following steps: Step B1: Withdrawal consensus Step B1.1: The tracing requester initiates a tracing transfer transaction to the blockchain of the alliance to which it belongs. The tracing transfer transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the service fee of the tracing responder. The sender address refers to the account address of the tracing requester, and the receiver address refers to the account address of the tracing responder. Step B1.2: The blockchain of the alliance to which the tracing requester belongs reaches a consensus on the tracing transfer transaction and checks whether the account balance of the tracing requester satisfies the service fee of the tracing responder. If the account balance of the tracing requester does not meet the service fee requirement of the tracing responder, the tracing transfer transaction is canceled. If the account balance of the tracing requester meets the service fee requirement of the tracing responder, the account balance of the tracing requester is withdrawn, and the amount withdrawn is the service fee of the tracing responder. Step B2. Withdrawal transaction proof delivery Step B2.1: The monitoring autonomous domain of the alliance where the traceability requester is located detects that the recipient of the traceability transfer transaction is not in the current alliance, and encapsulates the traceability transfer transaction, the proof of the traceability transfer transaction, the block header of the block where the traceability transfer transaction is located, and the numbers of the blockchains where the sender and receiver of the traceability transfer transaction are located into a fifth cross-chain message. The monitoring autonomous domain sends the fifth cross-chain message to the upper-level blockchain until the minimum common ancestor blockchain of the blockchains where the sender and receiver of the traceability transfer transaction are located; Step B2.2: The least common ancestor blockchain parses the fifth cross-chain message, verifies the traceability transfer transaction and its proof, and stores the verification result on this blockchain. If the verification fails, a rollback message is sent to the blockchain where the sender of the traceability transfer transaction is located, including the proof of verification failure, and the processing flow of the traceability transfer transaction is terminated; if the verification passes, it is searched whether there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted. If not, the least common ancestor blockchain encapsulates the fifth cross-chain message and the verification result into a sixth cross-chain message and sends it to the blockchain where the recipient of the traceability transfer transaction is located; if there are other cross-alliance traceability transfer transactions with the same sender or receiver that have not been submitted, the least common ancestor blockchain needs to wait for the other cross-alliance traceability transfer transactions to be successfully submitted or terminated before the sixth cross-chain message can be sent to the blockchain where the recipient of the traceability transfer transaction is located; Step B3. Deposit Transaction Consensus Step B3.2: The blockchain where the recipient of the traceability transfer transaction is located parses the sixth cross-chain message to obtain the fifth cross-chain message and the verification result. If the verification result indicates that the verification is passed, it indicates that the traceability transfer transaction is correctly submitted on the blockchain where the sender is located. The traceability responder initiates a deposit transaction to the blockchain of the alliance where it is located. The deposit transaction includes the transaction content, the sender address and the receiver address of the transaction. The transaction content includes the proof of the traceability transfer transaction and the service fee of the traceability responder. The sender address refers to the account address of the traceability requester, and the receiver address refers to the account address of the traceability responder. The blockchain of the alliance where the traceability responder is located reaches a consensus on the deposit transaction to realize the account deposit of the traceability responder. The amount of the deposit is the service fee. Step B3.3: The monitoring autonomous domain of the alliance where the traceability responder is located encapsulates the deposit transaction, the proof of the deposit transaction, the block header of the block where the deposit transaction is located, and the numbers of the blockchains where the sender and receiver of the deposit transaction are located into the seventh cross-chain message, and sends the seventh cross-chain message to the least common ancestor blockchain of the blockchains where the sender and receiver of the deposit transaction are located; Step B4.

4. Submit The least common ancestor blockchain parses the seventh cross-chain message, verifies the deposit transaction and its proof, and stores the verification result on the least common ancestor blockchain. If the verification result indicates that the verification is passed, a submission message is sent to the blockchains where the sender and receiver of the traceability transfer transaction are located respectively. The submission message indicates that the traceability transfer transaction is successfully submitted, and the process ends; if the verification result indicates that the verification is not passed or the least common ancestor blockchain does not receive the seventh cross-chain message within a preset time period, step B5 is executed; Step B5. Rollback The least common ancestor blockchain sends a rollback message to the blockchains of the sender and receiver of the traceability transfer transaction respectively. If the verification fails, the rollback message includes the verification result and proof of the deposit transaction; if it is a timeout, the rollback message includes the proof of timeout of the traceability transfer transaction, the blockchain where the sender is located executes the reverse operation of the traceability transfer transaction, and the blockchain where the receiver is located executes the reverse operation of the deposit transaction.