Internet of Things identifier analysis-oriented block chain reputation management system

Abstract

The invention provides a block chain reputation management system for Internet of Things identification analysis, and the system comprises an IoT device which is used for requesting or providing an identifier; the IoT equipment comprises non-limited equipment and limited equipment; identifying server nodes which are used for representing nodes of a block chain consensus mechanism; the intelligent contract is used for defining a consensus threshold value thrc and a node threshold value thrn, and calculating a reputation value R; thrc cannot participate in block chain consensus, Rlt; and removing the alliance chain from the consensus threshold thrc and the node threshold thrn, analyzing the node identifiers conforming to the consensus threshold thrc and the node threshold thrn, and automatically executing an identifier analysis process. According to the method, the blockchain is utilized to ensure that the identifier cannot be tampered, the fairness and equivalence of the architecture are enhanced, a reputation model is introduced into the blockchain to provide a quantifiable and continuous trust mechanism for the system, the security and reliability of identifier analysis and the high efficiency of an identifier automatic allocation and registration mechanism are enhanced, and the system reliability is improved. And the method is suitable for a complex network environment.

Description

Technical Field

[0001] The present invention belongs to the technical field of blockchain, and in particular relates to a blockchain reputation management system for Internet of Things identity resolution. Background Art

[0002] The Internet of Things (IoT) connects people, machines and objects through embedded sensors, smart devices and software systems, providing a comprehensive solution for automated data collection, environmental monitoring and intelligent control. The correct identification and resolution of IoT devices is a prerequisite for interconnected communication between devices, client monitoring and control of devices, and connection to cloud servers for data processing and analysis. Therefore, the identification and resolution of IoT devices is a prerequisite for the development, deployment and operation of large-scale IoT applications and services.

[0003] Due to the particularity of IoT devices, higher requirements are placed on the security, stability and scalability of identity resolution services. Faced with a large-scale IoT environment, the IoT identity resolution system still faces many challenges in supporting the interconnection of massive objects.

[0004] At the architectural level, multiple standards and naming formats coexist in the Internet of Things, which brings huge challenges to the retrieval and understanding of objects. At the same time, the mainstream identity resolution system adopts a centralized hierarchical architecture with a single control point. The upper-level nodes in the architecture have control over their lower-level nodes and can even control the services of the entire lower-level node network. The unequal permissions of service nodes brought about by the architecture may cause the resolution service to be illegally controlled or even unable to be provided. Some mechanisms attempt to implement a multi-root structure at the top-level node to decentralize control, but they have not fundamentally solved the problems existing in the resolution architecture.

[0005] In terms of scalability, there are many types of objects in the Internet of Things. The identity resolution system should be able to meet the diverse and customized needs of identification and resolution results, and should have a certain degree of foresight, that is, it should have a large enough namespace to cope with the addition of massive devices in the future and meet the high concurrency registration and resolution of IoT devices. Most of the current identity resolution systems are not designed specifically for the Internet of Things, and their resource description capabilities are not strong. In addition, the identity resolution systems rely on the identity service platform established by a third party. The manual configuration of a large number of IoT device identifiers consumes time and labor costs, and it is difficult to meet the needs of large-scale deployment and management.

[0006] In terms of security, security is the cornerstone of building a reliable and sustainable Internet of Things. However, the current IoT identity resolution system does not fully consider the security risks involved. The security of the identity resolution system mainly includes terminal security, data security, and operational security [4]. Terminal security includes client security and server security. The identity resolution system should be able to ensure the authentication and privacy of the client, such as anonymous requests, and prevent cache poisoning, domain name hijacking, and DDoS attacks against the server; data security should ensure the transmission and storage security of identifiers; operational security means that participants perform operations within their rights. The power of the central node in the current centralized resolution system is overly concentrated, and there is a risk of improper control and review of data. The DDoS attacks faced by the central node have also become the core weak link in the tree structure. Therefore, the current identity resolution system cannot effectively ensure terminal security. At the same time, identity naming and resolution are at risk of being tampered with. Most of the current mainstream identity solutions do not set access control permissions, and cannot guarantee data security and operational security. Summary of the invention

[0007] The purpose of the present invention is to propose a blockchain reputation management system for Internet of Things identity resolution, which makes up for the defects of the current Internet of Things identity resolution system. The blockchain reputation management system for Internet of Things identity resolution has equal authority for each server node, meets the interconnection and interoperability of multi-source heterogeneous data, and realizes automatic and unique allocation and registration of identifiers. In addition, based on the inherent security of the blockchain, a reputation management mechanism is introduced, and the reputation value of the blockchain node is evaluated according to established rules, and the authority of the node in the mechanism is adjusted accordingly, and malicious nodes are effectively identified and isolated, further enhancing the security of the mechanism.

[0008] In order to achieve the above object, the present invention provides a blockchain reputation management system for IoT identity resolution, the system comprising:

[0009] IoT device, used to request or provide an identifier; the IoT device includes an unrestricted device and a restricted device, wherein the restricted device is represented by I w = {I w1 ,I w2 ,I w3 ..., I wi , I wn}, non-restricted devices are represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn};

[0010] The identification server node is used to represent the node of the blockchain consensus mechanism, and the identification server node includes an edge node and an unrestricted device node; wherein the edge node is used as a restricted device node. w The server performs identity resolution, and each edge node stores a copy of the blockchain, then the edge node is represented by Eg = {Eg1, Eg2, Eg3...Eg i ,Eg n}; The non-restricted device node is the non-restricted device, and the non-restricted device is represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn};

[0011] Smart contract to define the consensus threshold thr c and node threshold thr n , calculate the reputation value R, when R <thr c Then it cannot participate in the blockchain consensus, R <thr n The alliance chain is removed, and the consensus threshold thr c and node threshold thr n The node identifier is parsed and the identifier parsing process is automatically executed; wherein the identifier is used to automatically allocate and register the contract sc1, the reputation management contract sc2 and the priority management contract sc3, respectively using the smart contract sc i ={sc1,sc2,sc3} represents.

[0012] Furthermore, the restricted device I w According to the geographical location, the nearest edge node Eg is selected for identity resolution. w Communication with the edge node Eg is also based on the IP address.

[0013] Furthermore, the reputation value is calculated as follows:

[0014] The reputation management contract sc2 extracts the edge node reputation information and calculates the reputation value R (Eg i ,t) value, R(Eg i ,t) represents the edge node Eg i The reputation value at time t is expressed as follows:

[0015]

[0016] The reputation management contract sc2 extracts the edge node reputation information and calculates the reputation value R (Eg i ,t) value, R(Eg i,t) represents the edge node Eg i The reputation value at time t is expressed as follows:

[0017]

[0018] Among them, k represents a fixed value, which is 1; e -0.01t represents the decay function; Indicates the consensus success rate, cs t represents the number of times the consensus of node i succeeds at time t, c t represents the total number of consensuses at time t, c represents the total number of consensuses,; Indicates the registration success rate, rs t Indicates the number of successful registrations, r t represents the total number of registrations at time t, and r represents the total number of registrations; Indicates that the node consensus time is less than the average consensus time T of all nodes at a certain time e The number of times, Indicates that the node consensus time T is greater than the average consensus time T of all nodes at a certain time e The number of times; represents the malicious formula behavior impact factor, M c Indicates the influence factor of malicious behavior during consensus, represents the impact weight when the a-th consensus is malicious, n represents the total weight of the impact when the consensus is malicious, M represents the impact factor of the total malicious behavior, and a represents the impact weight when the a-th consensus is malicious; represents the malicious registration impact factor, M r Indicates malicious behavior when registering a logo, Represents the impact weight of malicious registration at the bth time.

[0019] Furthermore, the reputation value calculation also includes the non-restricted device identification I s The reputation value is calculated as follows:

[0020]

[0021] Among them, R(Is i ,t) indicates non-restricted device Is i The reputation value at time t, α and β represent optimization factors, cs t represents the number of times the consensus of node i succeeds at time t, c t Represents the total number of consensuses at time t.

[0022] Furthermore, since the calculation formulas for the reputation values ​​of the two nodes are different, the reputation values ​​are normalized as follows:

[0023]

[0024] Among them, R(Eg i ,Is i ,t) norm represents the normalized reputation value of the edge node or non-restricted device node at time t, and R represents the reputation value;

[0025] The behavior of all nodes is managed by the reputation management contract sc2, which regularly calculates the node reputation value within t time intervals. when , the node will be removed from the blockchain network and will not be able to participate in identity resolution or exchange data with other devices. When consensus begins, the reputation management contract sc2 will compare the node's most recently updated reputation value with the preset threshold. , the current node cannot participate in the consensus.

[0026] Furthermore, the automatic allocation and registration contract includes transaction initialization implemented by three smart contracts and consensus completed by the blockchain network.

[0027] Furthermore, the transaction initialization specifically includes:

[0028] The node first submits a request containing<Device information,SensitiveInformation,Public key,Others> Request package, and mark it as Device information registered as internal identification and Others registered as external identification, then automatically assign and register contract sc1 to process the request information, conduct a preliminary compliance review, and after confirming that the request information is compliant, automatically assign and register contract sc1 to generate an internal identification for uniquely identifying the device according to the established rules. The format is<Device information> *<unique_id> , where unique_id is composed of node ID and timestamp. The contract checks whether there is any marked sensitive information in the user registration request. If there is such information, the requester's public key signature generates a sign (sensitiveinformation) Then the system assigns an IPv6 address to it and sets IPv6, others, and sign (sensitiveinformation) Aggregated into an external identifier, the external identifier is bound to the corresponding internal identifier as a transaction, ready to enter the transaction sorting stage;

[0029] The reputation management smart contract sc2 monitors and records node transactions, including consensus success rate, registration success rate, consensus time, and compliance verification results. When a node submits a registration request, the reputation management smart contract sc2 calculates the node's reputation value at the current moment;

[0030] The transaction priority management contract sc3 obtains the node reputation value from the reputation management smart contract sc2, and then prioritizes the transactions within a certain time window according to the size of the node reputation value, and finally adds them to the transaction pool in an orderly manner to wait for processing.

[0031] Furthermore, the consensus specifically includes: the PBFT packaging thread is responsible for taking out transactions from the transaction pool, encapsulating the transactions into PBFTPrepare packages and handing them over to the consensus thread for processing; PBFT Engine receives PBFT consensus message packages through PBFTSealer or P2P network, starts the consensus process, and finally writes the consensus blocks into the blockchain, and deletes the transactions that have been on the chain from the transaction pool.

[0032] Furthermore, the identification resolution specifically includes: non-restricted device node I s By initiating a resolution request to the nearby edge node Eg, the IP address of the target device is obtained. w The local account book can be directly queried to obtain the edge node Eg, which maintains a managed restricted device node I s list, and avoid a restricted device node I by detecting the data traffic frequency s Request overload.

[0033] Furthermore, the four trends of the reputation value include gradually increasing, first increasing and then decreasing, gradually decreasing, and first decreasing and then increasing.

[0034] The beneficial technical effects of the present invention are at least as follows:

[0035] The blockchain of the present invention realizes a multi-center, tamper-proof data storage solution by synchronizing, sharing and copying data at multiple points. This fair and equal service solves the challenges of the current identity resolution system architecture level; its hash chain structure prevents the identifier naming and resolution data from being illegally tampered with, ensuring data security; the distributed architecture effectively resists DDoS attacks and enhances terminal security. However, the establishment of an identity resolution system directly based on the blockchain cannot completely guarantee terminal security. This is because the nodes participating in the blockchain are driven by reason and interests, and may show selfish or malicious behavior. It is difficult for the blockchain to effectively constrain the malicious behavior of illegal nodes. Therefore, in order to motivate the nodes in the blockchain to actively and honestly participate in the system, this paper proposes an identity resolution system based on the reputation of the blockchain through a quantitative evaluation of the behavior of the blockchain nodes in the identity resolution cycle. The smart contract written dynamically calculates the reputation value according to the behavior of the node in consensus and registration, and uses the reputation value to identify and confirm malicious nodes in the mechanism. The reputation value not only determines the resolution and consensus authority of the node, but also affects the verification priority of the node submitting the registration request, thereby enhancing the controllability of the mechanism to the node and ensuring operational safety. In summary, this paper proposes a peer-to-peer, scalable, and secure IoT identity resolution system based on reputation-based blockchain, which provides a new perspective for device identification and network service lookup. The main contributions include:

[0036] 1. At the architectural level, the identification management and central organization are decoupled, and an equal and autonomous distributed resolution system is designed. The identifier extension in the proposed general architecture enables a variety of naming formats to be easily and seamlessly migrated to the system, achieving compatibility with current heterogeneous identifier formats, thereby realizing data interoperability and unified resource scheduling.

[0037] 2. In terms of scalability, the proposed identifier naming scheme supports multiple types of identifier subjects, automated identifier allocation and registration, and identifier resolution realizes privacy and customization requirements.

[0038] 3. In terms of security, a reputation model that is compatible with IoT identity resolution has been developed. By quantifying node behavior and dynamically monitoring devices, malicious nodes can be effectively identified. Node request priorities and node consensus, resolution and other permissions are managed based on reputation values, further enhancing terminal security and operational security. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The present invention is further described using the accompanying drawings, but the embodiments in the accompanying drawings do not constitute any limitation to the present invention. A person skilled in the art can obtain other drawings based on the following drawings without creative work.

[0040] Figure 1 This is a framework diagram of a blockchain reputation management system for IoT identity resolution according to the present invention.

[0041] Figure 2 The figure is a schematic diagram of the identification allocation and registration process according to an embodiment of the present invention.

[0042] Figure 3 The figure is a schematic diagram of the identification resolution process according to an embodiment of the present invention.

[0043] Figure 4 Four trend diagrams of the comprehensive reputation scores of consensus and registered instances within 100 time units are simulated for the embodiments of the present invention.

[0044] Figure 5 Schematic diagram of the reaction of the embodiment of the present invention and RTChain to malicious node behavior.

[0045] Figure 6 The diagram is a schematic diagram of the node's recovery capability after experiencing a long period of malicious behavior according to an embodiment of the present invention.

[0046] Figure 7 This is a schematic diagram of the effect of the consensus efficiency factor on network performance in the reputation model tested in an embodiment of the present invention.

[0047] Figure 8 This is a schematic diagram of the impact of the incentive node consensus efficiency on the system efficiency according to an embodiment of the present invention.

[0048] Fig. 9 A schematic diagram of a single allocation registration and resolution time according to an embodiment of the present invention.

[0049] Fig.10 A schematic diagram of concurrently allocating registration and parsing time in an embodiment of the present invention. DETAILED DESCRIPTION

[0050] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0051] Embodiment 1

[0052] like Figure 1 As shown, the present invention provides a blockchain reputation management system for IoT identity resolution, the system comprising:

[0053] IoT device, used to request or provide an identifier; the IoT device includes an unrestricted device and a restricted device, wherein the restricted device is represented by I w = {I w1 ,I w2 ,I w3 ..., Iwi , I wn}, non-restricted devices are represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn};

[0054] The identification server node is used to represent the node of the blockchain consensus mechanism, and the identification server node includes an edge node and an unrestricted device node; wherein the edge node is used as a restricted device node. w The server performs identity resolution, and each edge node stores a copy of the blockchain, then the edge node is represented by Eg = {Eg1, Eg2, Eg3...Eg i ,Eg n}; The non-restricted device node is the non-restricted device, and the non-restricted device is represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn}; The present invention selects the alliance chain with the highest throughput as the underlying infrastructure. The blockchain node is the server node for identity resolution, which is divided into edge nodes and unrestricted device nodes. w They cannot directly assume the role of blockchain nodes, store copies of blockchain data, or participate in computationally intensive consensus mechanisms, so edge nodes are used as I w The server performs identity resolution;

[0055] Smart contract to define the consensus threshold thr c and node threshold thr n , calculate the reputation value R, when R <thr c Then it cannot participate in the blockchain consensus, R <thr n The alliance chain is removed, and the consensus threshold thr c and node threshold thr n The node identifier is parsed and the identifier parsing process is automatically executed; wherein the identifier is used to automatically allocate and register the contract sc1, the reputation management contract sc2 and the priority management contract sc3, respectively using the smart contract sc i ={sc1,sc2,sc3} represents; the present invention utilizes smart contracts for identity resolution. Smart contracts, as scripts embedded in the blockchain, have ACID properties (Atomicity, Consistency, Isolation, Durability) and are used to automatically execute multi-step processes.

[0056] Furthermore, if Figure 1 As shown, the restricted device I w According to the geographical location, the nearest edge node Eg is selected for identity resolution. w Communication with the edge node Eg is also based on the IP address.

[0057] Specifically, nodes will maximize profits through selfish behaviors, which will pose a threat to the system. Therefore, a reputation model is constructed in the present invention, and continuous reputation management is performed to dynamically monitor the behavior of devices and timely discover potential malicious activities. The core of the reputation model is to quantify node behavior, which is used as a standard for calculating and updating reputation scores, and is transparently managed by smart contracts. Nodes that follow established rules will increase their own reputation, while violating these rules will result in a deduction of reputation. The reputation score not only affects whether it can join the system and its ability to make decisions within the system, but also affects the priority of its registration request. Establishing a consensus threshold thr in the system c and node threshold thr n , when R <thr c Then it cannot participate in the blockchain consensus, R <thr n The reputation value calculation rules drive the consensus efficiency of blockchain nodes. For Eg, since it is responsible for multiple I w The higher the R value is, the higher the priority of the submitted registration request will be, and the faster it will be registered, thereby encouraging nodes to actively and honestly participate in the system.

[0058] Furthermore, the reputation value is calculated as follows:

[0059] The reputation management contract sc2 extracts the edge node reputation information and calculates the reputation value R (Eg i ,t) value, R(Eg i ,t) represents the edge node Eg i The reputation value at time t is expressed as follows:

[0060]

[0061] Among them, k represents a fixed value, which is 1; e -0.01t represents the decay function; Indicates the consensus success rate, cs t represents the number of times the consensus of node i succeeds at time t, c t represents the total number of consensuses at time t, c represents the total number of consensuses,; Indicates the registration success rate, rs t Indicates the number of successful registrations, r trepresents the total number of registrations at time t, and r represents the total number of registrations; Indicates that the node consensus time is less than the average consensus time T of all nodes at a certain time e The number of times, Indicates that the node consensus time T is greater than the average consensus time T of all nodes at a certain time e The number of times; represents the malicious formula behavior impact factor, M c Indicates the influence factor of malicious behavior during consensus, represents the impact weight when the a-th consensus is malicious, n represents the total weight of the impact when the consensus is malicious, M represents the impact factor of the total malicious behavior, and a represents the impact weight when the a-th consensus is malicious; represents the malicious registration impact factor, M r Indicates malicious behavior when registering a logo, Represents the impact weight of malicious registration at the bth time.

[0062] Specifically, for I s Since it only needs one registration, the impact of registration success rate and malicious registration on reputation value is eliminated, because each I s When applying to become a blockchain node, an identifier must be assigned to it and registered with the present invention. After successful registration, the registration request of the node will be ignored by the system. The rest is the same as Eg.

[0063] Furthermore, the reputation value calculation also includes the non-restricted device identification I s The reputation value is calculated as follows:

[0064]

[0065] Among them, R(Is i ,t) indicates non-restricted device Is i The reputation value at time t, α and β represent optimization factors, which are 1.5 and cs respectively. t represents the number of times the consensus of node i succeeds at time t, c t Represents the total number of consensuses at time t.

[0066] Furthermore, since the calculation formulas for the reputation values ​​of the two nodes are different, the reputation values ​​are normalized as follows:

[0067]

[0068] Among them, R(Eg i ,Is i ,t) norm represents the normalized reputation value of the edge node or non-restricted device node at time t, and R represents the reputation value;

[0069] The behavior of all nodes is managed by the reputation management contract sc2, which regularly calculates the node reputation value within t time intervals. when , the node will be removed from the blockchain network and will not be able to participate in identity resolution or exchange data with other devices. When consensus begins, the reputation management contract sc2 will compare the node's most recently updated reputation value with the preset threshold. , the current node cannot participate in the consensus.

[0070] In addition, the reputation model gives IoT devices the ability to determine the credibility of the received data based on the reputation value of the communicating party, thereby introducing a quantitative and continuous trust mechanism in internal interactions.

[0071] Furthermore, it also includes the rules for naming identifiers, which can easily migrate existing identifiers to the system. Identifiers are divided into internal identifiers and external identifiers. Internal identifiers are used to uniquely identify and manage devices within the system, and external identifiers are used by external systems to identify and access IoT devices. Most of the information in the identifier can be defined by the device owner.

[0072] The internal identifier uses a two-level hierarchical structure, and the basic format is<Device information> *<unique_id> .

[0073] Device information: The prefix information is defined by the device owner, including but not limited to the device type, device manufacturer, device owner, and other information.

[0074] unique_id: The suffix serves as a unique identifier to ensure the uniqueness of the device identification.

[0075] When registering an identifier, the prefix is ​​automatically submitted by the client based on the actual situation. If the client submits maliciously, it will be detected by the blockchain and its reputation will be reduced. The unique_id in the suffix is ​​globally uniquely generated and allocated by the smart contract.

[0076] The core problem of decentralized distributed identifier registration is how to achieve secure identifier generation without a central node and avoid identifier conflicts. Therefore, in the present invention, unique_id consists of a node ID and a UNIX timestamp of the current generation moment. This method ensures the uniqueness of each identifier, because the timestamp provides a continuously changing value, and the node ID ensures that even at the same timestamp, the identifiers generated by different nodes will be unique. Such a design not only solves the uniqueness problem of the identifier, but also, because it is based on the timestamp, it is easy to track and manage the generation time of the identifier, providing a certain traceability for the system.

[0077] In order to meet the diverse and differentiated needs of the Internet of Things, the analysis results are converted from the IP address in the Internet to multiple types of data, and support user-defined analysis results. Therefore, the external identifier includes some specific information of the device, and the specific format is: <IPv6,Others,sign (sensitiveinformation) >

[0078] IPv6 address: used for network communication between devices.

[0079] Others: Indicates custom information, such as item description, manufacturer information, etc.

[0080] sign (sensitiveinformation) : Considering that some information often involves privacy and security issues, such as location and status information, if the registration request submitted by the device owner contains such sensitive information, the system will sign it with the registrant's public key, and the relevant content can only be viewed after decryption.

[0081] To be compatible with the current multi-type identifier management rules, the device can use the current identifier as a prefix, and then the blockchain will assign a suffix<unique_id> This method does not rely on a central agency, and can easily connect various current identifier formats to the system to achieve unified management. For example, if a device marked with the handle identifier 20.1000 / abc123xyz wants to join this system, it can apply to the blockchain to allocate a unique_id composed of <20.1000 / abc123xyz>*<unique_id> , and then register to the present invention to realize data retrieval and data exchange functions.

[0082] Furthermore, the automatic allocation and registration contract includes transaction initialization implemented by three smart contracts and consensus completed by the blockchain network.

[0083] Specifically, the traditional centralized identifier generation method means that when obtaining an identifier, it is necessary to apply to a public authoritative server. The concentration of power in a third party is prone to single point failure, and centralized data storage increases the risk of privacy leakage. The decentralized identifier generation method enhances the transparency of the system and the autonomy of users through decentralized control and processing. It not only solves the complexity of manual configuration, but also effectively avoids the risk of single point failure by abandoning the reliance on trusted third parties. In this method, the identifier is not allocated by an authoritative service node, but is obtained through consensus. The flowchart of identifier allocation and registration is shown in the figure below. Figure 2 As shown in the figure, the process is mainly divided into two stages. The first stage is transaction initialization, which is implemented by three smart contracts; the second stage is consensus, which is completed by the blockchain network.

[0084] Furthermore, the transaction initialization specifically includes:

[0085] The node first submits a request containing<Device information,SensitiveInformation,Public key,Others> Request package, and mark it as Device information registered as internal identification and Others registered as external identification, then automatically assign and register contract sc1 to process the request information, conduct a preliminary compliance review, and after confirming that the request information is compliant, automatically assign and register contract sc1 to generate an internal identification for uniquely identifying the device according to the established rules. The format is<Device information> *<unique_id> , where unique_id is composed of node ID and timestamp. The contract checks whether there is any marked sensitive information in the user registration request. If there is such information, the requester's public key signature generates a sign (sensitiveinformation) Then the system assigns an IPv6 address to it and sets IPv6, others, and sign (sensitiveinformation) Aggregated into an external identifier, the external identifier is bound to the corresponding internal identifier as a transaction, ready to enter the transaction sorting stage;

[0086] The reputation management smart contract sc2 monitors and records node transactions, including consensus success rate, registration success rate, consensus time, and compliance verification results. When a node submits a registration request, the reputation management smart contract sc2 calculates the node's reputation value at the current moment;

[0087] The transaction priority management contract sc3 obtains the node reputation value from the reputation management smart contract sc2, and then prioritizes the transactions within a certain time window according to the size of the node reputation value, and finally adds them to the transaction pool in an orderly manner to wait for processing.

[0088] Furthermore, the consensus specifically includes: the PBFT packaging thread is responsible for taking out transactions from the transaction pool, encapsulating the transactions into PBFTPrepare packages and handing them over to the consensus thread for processing; PBFT Engine receives PBFT consensus message packages through PBFTSealer or P2P network, starts the consensus process, and finally writes the consensus blocks into the blockchain, and deletes the transactions that have been on the chain from the transaction pool.

[0089] Furthermore, the identification resolution, such as Figure 3 As shown, it specifically includes: non-restricted device node I s By initiating a resolution request to the nearby edge node Eg, the IP address of the target device is obtained. w The local account book can be directly queried to obtain the edge node Eg, which maintains a managed restricted device node I s list, and avoid a restricted device node I by detecting the data traffic frequency s Request overload.

[0090] Specifically, the process of identity resolution is the process of mapping the internal and external identities of the Internet of Things. The present invention can not only store the identification information of the Internet of Things devices, but also record the necessary DNS information, thereby allowing the Internet of Things devices to be seamlessly integrated into cloud services, data centers and other network infrastructures, and more conveniently interoperate with existing Internet infrastructure and other online services. Through this system, basic device information can be easily retrieved, and the device owner can obtain data about the current location and status of the device. When an Internet of Things device needs to exchange data with a remote service on the Internet, or when devices in the Internet of Things communicate with each other, a communication connection is established through the other party's IP address to ensure the correct reception and transmission of information.

[0091] The architecture of the system will affect the security, robustness and latency of the resolution service. The hierarchical tree structure of the current identifier may not be resolved due to denial of service attacks and node hijacking. The identifier resolution process of the present invention breaks the hierarchical structure of the current IoT resolution and transforms it into distributed point-to-point resolution. In this new mode, the resolution action no longer relies on complex hierarchical relationships, but directly obtains external identification information quickly by querying internal identifiers between blockchain nodes. In point-to-point resolution, each resolution node has the same resolution authority, and each resolution node has no right to tamper with or discard the resolution requests of other nodes, avoiding illegal control of the resolution service and facilitating the construction of a decentralized and equal resolution ecosystem.

[0092] The heterogeneity of IoT identifiers is one of the bottlenecks faced by IoT. The universal identifier format of the present invention can easily migrate the existing identifier format to the mechanism, breaking through the information island of identifier resolution and achieving compatibility and interoperability. By integrating blockchain and edge nodes, the communication problem between restricted devices is solved. By distributing the resolution tasks to various blockchain nodes, the burden of a single central node is reduced. And through direct or indirect P2P search, the communication efficiency is improved. The present invention can provide a complete, secure and robust resolution mechanism for IoT devices.

[0093] Embodiment 2

[0094] The system configuration and tools used in the experimental test are shown in Table 1. The performance test is mainly carried out from two aspects. First, the changing trend of the reputation formula under different conditions and the ability to identify malicious nodes are tested, and then the time overhead and parallel execution capability of automatic allocation and registration are tested.

[0095] Table 1 Test environment

[0096]

[0097]

[0098] In order to test the effect of the blockchain reputation management system for IoT identity resolution, the reputation value is updated according to the formula in Section 3.2, and four typical trends of the comprehensive reputation score of consensus and registration instances within 100 time units are simulated: gradually rising, rising first and then falling, gradually falling, and falling first and then rising. The results are shown in Figure 2. Figure 4 shown.

[0099] a. Nodes have no malicious behavior - reputation value gradually increases: This situation simulates the changing trend of reputation value when there is no malicious consensus or malicious registration of nodes. The fluctuations in the curve are caused by the number of times the consensus time is less than the average consensus time at each moment. The behavior of rapid growth and gradual slowdown of reputation value simulates the natural development process of trust in the real world. The rapid rise of reputation value when a new node joins the network reflects the system's initial trust incentive for the newly joined node, and can prevent it from being identified as a malicious node due to a too small reputation value. However, as time goes by, it becomes more difficult to increase trust, and nodes need to continue to have positive behavior to maintain and improve their reputation.

[0100] b. Malicious behavior occurs in the node midway - the reputation value rises first and then falls: This situation simulates that there is no malicious behavior in the first 35 time units, and registration failure and consensus failure occur randomly in the following time. Considering that in the real world, node registration failure or consensus failure may be caused by sporadic failure or malicious behavior, the blockchain reputation management system for IoT identity resolution allows problematic nodes to regain trust by proving their reliability and normal behavior within a period of time. However, as can be seen from the slope, the recovery process is relatively slow, which can ensure that the system can observe the behavior of the node for a longer period of time, thereby maintaining the overall trust of the network environment.

[0101] C. The node exhibits malicious behavior from the beginning - the reputation value gradually decreases: This situation simulates that the node starts to behave maliciously from the beginning. The rapid decrease in the reputation value at the beginning can ensure that the system responds quickly to potential threats, showing the system's high sensitivity to abnormal behavior.

[0102] d. The node starts to do evil and then stops - the reputation value first decreases and then increases: This situation simulates that the node performs malicious behavior in the first 35 time units and then stops the malicious behavior. It is designed to test the recovery ability of the reputation value. As can be seen from the figure, once the node has obvious and continuous malicious behavior, the system will continue to be alert to it and remember it for a long time. The difference between Figure d and Figure b is that the failure behavior of the node in Figure b is accidental, while in the case of Figure d, the node's continuous failure behavior will be judged as intentional malicious behavior, so the reputation value can no longer be restored.

[0103] like Figure 5 The figure shows the reactions of the blockchain reputation management system for IoT identity resolution and RTChain to malicious node behavior. As can be seen from the figure, after the reputation value rises to the same value, the node randomly performs malicious behavior. The decrease in the reputation value in the blockchain reputation management system for IoT identity resolution, that is, the reaction ability, is higher than that of RTChain. This shows that the blockchain reputation management system for IoT identity resolution has a higher sensitivity to malicious node identification and can identify and isolate malicious nodes faster.

[0104] like Figure 6As shown in the figure, the node's recovery ability after experiencing a long period of malicious behavior. The figure tests that the node has been experiencing malicious behavior in the first 35 time units, and then recovers to normal behavior. From the figure, it can be seen that the blockchain reputation management system for IoT identity resolution cannot significantly increase the reputation value even if the node continuously remedies after experiencing continuous malicious behavior. Because malicious behavior will bring long-term memory to the reputation value, this method is to reduce the means by which nodes manipulate reputation through periodic malicious behavior and superficial good behavior, ensuring that only nodes that truly perform well continuously can maintain high reputation, thereby enhancing the authenticity and reliability of the entire system. In RTChain, previous malicious behavior will not affect the subsequent increase in reputation value, so the constraint ability on nodes is weak.

[0105] like Figure 7 As shown in Figure 2, the impact of consensus efficiency on reputation value was tested under the same conditions (consensus success rate, registration success rate). Figure 7 As shown in the figure, when other conditions are equal, the more times a node's consensus time is below the average level, the higher the reputation value will be. This mechanism ensures that more efficient nodes receive corresponding incentives, that is, in the absence of malicious behavior, the difference in reputation value mainly reflects the pros and cons of node consensus efficiency. In order to obtain a higher priority for registration requests and maintain an active position in the blockchain network, nodes must continuously optimize their consensus efficiency to ensure that their processing speed is faster than the average consensus time. This design can motivate participants to invest resources to increase the speed of consensus. Figure 8 It further shows the impact of different numbers of nodes improving consensus efficiency to different degrees on the overall average consensus time. Here, it is assumed that the initial average consensus time is 100 and the number of nodes is 1000. It can be seen that with the increase in the number of nodes whose consensus time is less than the average consensus time and the increase in the time improvement, the overall consensus efficiency is also constantly improving.

[0106] Furthermore, the performance of the blockchain reputation management system for IoT identity resolution is tested during automatic identity allocation, registration, and identity resolution in single and high-concurrency situations.

[0107] Specifically, we first conducted 100 single-time performance tests, such as Fig. 9 As shown, the logo registration time is between 143ms-651ms, and the logo resolution time is between 103ms-123ms.

[0108] In order to test whether the blockchain reputation management system for IoT identity resolution can meet the needs of large-scale deployment of IoT, this experiment simulates a large number of devices in IoT to issue registration requests and resolution requests at the same time, and tests the performance under high concurrency. The test results are as follows: Fig.10As shown in the figure. Each concurrency is tested 10 times and the average value is taken. For identifier resolution, since it does not involve consensus, the time fluctuation in each group of 10 tests is very small and can be basically ignored. However, consensus is required for identifier allocation and registration, and the time will fluctuate due to network conditions, etc. The fluctuation is as follows Fig.10 As shown in the waves. When faced with concurrent requests ranging from 10,000 to 100,000 times, the time required for both increases with the increase in the number of concurrent requests. When parsing with 100,000 times of high concurrency, the time did not exceed 1 minute, and the allocation and registration of 100,000 times of high concurrency identifiers did not exceed 10 minutes, and the error rate of both in the test was 0%, proving the efficiency and effectiveness of the automatic allocation registration and distributed parsing of the blockchain reputation management system for IoT identity parsing. In actual application deployment, when used on higher-performance servers and more optimized network environments, the processing time is expected to be much lower than the current test results.

[0109] In the blockchain reputation management system for IoT identity resolution, by combining alliance chain, edge computing and the reputation management mechanism involved in the characteristics of IoT identity resolution, a more secure and reliable management service model is obtained than the current IoT identity management. Table 2 shows the security performance comparison between the blockchain reputation management system for IoT identity resolution and different solutions.

[0110] Table 2 Comparison of safety performance of different solutions

[0111]

[0112] Furthermore, it will protect terminal security:

[0113] Specifically, (1) Client security. The blockchain identifies users through anonymous wallet addresses, making it difficult for potential attackers to associate resolution records with the user's identity, thus achieving anonymous requests. In addition, the customizable resolution results encrypt sensitive information, protecting the privacy of the client's resolution results.

[0114] (2) Server security. Although there are currently a variety of IoT identity resolution systems, the identities in these technologies mainly rely on the allocation of trusted institutions. When dealing with large-scale and rapidly growing IoT device registration requests, centralized systems face tremendous pressure on resources and time, and the centralized storage of registration information may become a high-value target for attackers. Once the system is attacked, technically failed, or interrupted in any form, it may cause the entire service to be paralyzed and user information to be leaked. The blockchain reputation management system for IoT identity resolution automates the allocation and registration of identities through smart contracts, distributing the control of identifiers to participants. Blockchain nodes serve as identity resolution servers, and each node saves a complete copy. Even if some nodes are attacked, the entire network can still operate normally. In addition, if a node frequently and maliciously initiates registration requests, it will be identified as a malicious registration behavior by the system, thereby reducing its reputation value. As shown in the above test, the node will be quickly identified and processed, thereby ensuring server security.

[0115] The blockchain reputation management system for IoT identity resolution uses the infrastructure of blockchain to record the identification information of IoT devices in blocks. Each block not only contains data, but also stores the hash value of the previous block, thereby building a secure and irreversible data chain. If an attacker wants to change a block, he not only needs to recalculate the hash value of the block, but also needs to recalculate all subsequent blocks on the entire chain and quickly update the information of the entire blockchain before other nodes in the network verify the tampered content. This attack method is almost impossible in actual operation due to the resources and time required. In addition to the inherent security features of blockchain, the reputation model in the blockchain reputation management system for IoT identity resolution can identify malicious nodes based on their behavior, making up for the problem that the alliance chain cannot prevent nodes between chains from doing evil, and providing the credibility of identity resolution from the source.

[0116] In the blockchain reputation management system for IoT identity resolution, in order to ensure the legitimacy of the participants, the system adopts a certificate-based identity authentication mechanism to ensure that the participants are authorized nodes. The node certificate is the key credential of the legal participant and is issued by the certification authority (CA). When a node applies to join the blockchain network, it needs to submit its detailed information (hardware information, MAC address, etc.) to the CA. The CA verifies the authenticity of the applicant's information through various means online and offline. After the review is passed, the CA will issue a certificate to the node. In order to strengthen the security of the system, the blockchain reputation management system for IoT identity resolution regulates the node behavior through the reputation value to ensure the honest cooperation of the nodes. When the node is removed from the blockchain network due to malicious behavior and the reputation value is too low, in order to prevent the node from rejoining the network, the blockchain reputation management system for IoT identity resolution will maintain a blacklist of nodes that have been removed from the network, which stores the certificate information of these nodes. When the node removed due to malicious behavior reapplies for a certificate from the CA, the CA detects whether the node is an illegal node by comparing the information in the blacklist and further verification, and thus refuses to rejoin. In addition, the reputation value can also refine the authority allocation of nodes, and nodes can also use the reputation value to judge each other's trust level, providing an accurate trust reference for the interaction between nodes and ensuring the trusted interaction of the entire blockchain reputation management system for IoT identity resolution.

[0117] Although embodiments of the present invention have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A blockchain reputation management system for IoT identity resolution, characterized in that: The system comprises: IoT device, used to request or provide an identifier; the IoT device includes an unrestricted device and a restricted device, wherein the restricted device is represented by I w = {I w1 ,I w2 ,I w3 ..., I wi , I wn }, non-restricted devices are represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn }; The identification server node is used to represent the node of the blockchain consensus mechanism, and the identification server node includes an edge node and an unrestricted device node; wherein the edge node is used as a restricted device node. w The server performs identity resolution, and each edge node stores a copy of the blockchain, then the edge node is represented by Eg = {Eg1, Eg2, Eg3...Eg i ,Eg n }; The non-restricted device node is the non-restricted device, and the non-restricted device is represented by I s = {I s1 ,I s2 ,I s3 ...Is i , I sn }; Smart contract, used to define the consensus threshold thr c and node threshold thr n , calculate the reputation value R, when R <thr c Then it cannot participate in the blockchain consensus, R <thr n The alliance chain is removed, and the consensus threshold thr c and node threshold thr n The node identifier is parsed and the identifier parsing process is automatically executed; wherein the identifier is used to automatically allocate and register the contract sc1, the reputation management contract sc2 and the priority management contract sc3, respectively using the smart contract sc i ={sc1,sc2,sc3} represents.

2. According to claim 1, a blockchain reputation management system for IoT identity resolution is characterized in that: The restricted device I w According to the geographical location, the nearest edge node Eg is selected for identity resolution. w Communication with the edge node Eg is also based on the IP address.

3. According to a blockchain reputation management system for IoT identity resolution according to claim 1, it is characterized in that: The reputation value is calculated as follows: The reputation management contract sc2 extracts the edge node reputation information and calculates the reputation value R (Eg i ,t) value, R(Eg i ,t) represents the edge node Eg i The reputation value at time t is expressed as follows: Among them, k represents a fixed value, which is 1; e -0.01t represents the decay function; Indicates the consensus success rate, cs t represents the number of times the consensus of node i succeeds at time t, c t represents the total number of consensuses at time t, c represents the total number of consensuses,; Indicates the registration success rate, rs t Indicates the number of successful registrations, r t represents the total number of registrations at time t, and r represents the total number of registrations; Indicates that the node consensus time is less than the average consensus time T of all nodes at a certain time e The number of times Indicates that the node consensus time T is greater than the average consensus time T of all nodes at a certain time e The number of times; represents the malicious formula behavior impact factor, M c Indicates the influence factor of malicious behavior during consensus, represents the impact weight when the a-th consensus is malicious, n represents the total weight of the impact when the consensus is malicious, M represents the impact factor of the total malicious behavior, and a represents the impact weight when the a-th consensus is malicious; represents the malicious registration impact factor, M r Indicates malicious behavior when registering a logo, Represents the impact weight of malicious registration at the bth time.

4. According to claim 3, a blockchain reputation management system for IoT identity resolution is characterized in that: The reputation value calculation also includes the non-restricted device identification I s The reputation value is calculated as follows: Among them, R(Is i ,t) indicates non-restricted device Is i The reputation value at time t, α and β represent optimization factors, cs t represents the number of times the consensus of node i succeeds at time t, c t Represents the total number of consensuses at time t.

5. A blockchain reputation management system for IoT identity resolution according to any one of claims 3 or 4, characterized in that: Since the two node reputation calculation formulas are different, the reputation values ​​are normalized as follows: in, represents the normalized reputation value of the edge node or non-restricted device node at time t, and R represents the reputation value; The behavior of all nodes is managed by the reputation management contract sc2, which regularly calculates the node reputation value within t time intervals. when , the node will be removed from the blockchain network and will not be able to participate in identity resolution or exchange data with other devices. When consensus begins, the reputation management contract sc2 will compare the node's most recently updated reputation value with the preset threshold. , the current node cannot participate in the consensus.

6. A blockchain reputation management system for IoT identity resolution according to claim 1, characterized in that: The automatic allocation and registration contract includes transaction initialization implemented by three smart contracts and consensus completed by the blockchain network.

7. A blockchain reputation management system for IoT identity resolution according to claim 6, characterized in that: The transaction initialization specifically includes: The node first submits a request containing<Device information,Sensitive Information,Public key,Others> Request package, and mark it as Device information registered as internal identification and Others registered as external identification, then automatically assign and register contract sc1 to process the request information, conduct a preliminary compliance review, and after confirming that the request information is compliant, automatically assign and register contract sc1 to generate an internal identification for uniquely identifying the device according to the established rules. The format is<Device information> *<unique_id> , where unique_id is composed of node ID and timestamp. The contract checks whether there is any marked sensitive information in the user registration request. If there is such information, the requester's public key signature generates a sign (sensitiveinformation) Then the system assigns an IPv6 address to it and sets IPv6, others, and sign (sensitiveinformation) Aggregated into an external identifier, the external identifier is bound to the corresponding internal identifier as a transaction, ready to enter the transaction sorting stage; The reputation management smart contract sc2 monitors and records node transactions, including consensus success rate, registration success rate, consensus time, and compliance verification results. When a node submits a registration request, the reputation management smart contract sc2 calculates the node's reputation value at the current moment; The transaction priority management contract sc3 obtains the node reputation value from the reputation management smart contract sc2, and then prioritizes the transactions within a certain time window according to the size of the node reputation value, and finally adds them to the transaction pool in an orderly manner to wait for processing.

8. According to claim 7, a blockchain reputation management system for IoT identity resolution is characterized in that: The consensus specifically includes: the PBFT packaging thread is responsible for taking transactions from the transaction pool, encapsulating the transactions into PBFTPrepare packages and handing them over to the consensus thread for processing; PBFT Engine receives PBFT consensus message packages through PBFTSealer or P2P network, starts the consensus process, and finally writes the consensus blocks into the blockchain, and deletes the transactions that have been on the chain from the transaction pool.

9. A blockchain reputation management system for IoT identity resolution according to claim 1, characterized in that: The identification resolution specifically includes: non-restricted device node I s By initiating a resolution request to the nearby edge node Eg, the IP address of the target device is obtained. w The local account book can be directly queried to obtain the edge node Eg, which maintains a managed restricted device node I s list, and avoid a restricted device node I by detecting the data traffic frequency s Request overload.

10. A blockchain reputation management system for IoT identity resolution according to claim 1, characterized in that: The four trends of the reputation value include gradually increasing, first increasing and then decreasing, gradually decreasing, and first decreasing and then increasing.

Images