Data tracing method and device, equipment and storage medium

Abstract

The invention provides a data tracing method and device, equipment and a storage medium, and is applied to a handle client, and the method comprises the steps: obtaining a handle identifier of to-be-traced data; the handle identifier comprises an identifier prefix and an identifier suffix; the identification prefix is determined according to a handle server site configuration file; the identification suffix is determined according to the position number of the block chain to which the handle client belongs, the transaction sequence number and the generation time of the handle client; an identification prefix analysis request is sent to a global handle registration server, so that the global handle registration server determines a local handle server associated with the identification prefix based on the identification prefix, and the identification prefix analysis request comprises a handle identifier; and an identification suffix analysis request is sent to a local handle server, so that the local handle server determines related information of the to-be-traced data based on the identification suffix, and the identification suffix analysis request comprises the handle identification. According to the method, the Handle identifier and the block chain technology are combined, so that comprehensive and accurate data tracing is realized.

Description

Technical Field

[0001] This application relates to the field of information management technology, and in particular to a data traceability method, device, equipment and storage medium. Background Art

[0002] With the continuous in-depth application of new technologies such as big data, cloud computing, Internet of Things, mobile Internet and artificial intelligence, the power industry, as a pillar industry of the national economy, has developed rapidly in recent years. The scale of the power grid has been continuously expanding, and the types of equipment have become increasingly rich. The application of these new technologies not only improves the operation efficiency and reliability of the power system, but also brings new challenges and opportunities to the construction and operation and maintenance of power equipment. The power industry has accumulated a vast amount of data, which comes from a wide range of sources, including various links such as power generation, transmission, transformation, distribution, power consumption and dispatching, covering multiple aspects such as power grid operation and equipment detection, power enterprise marketing, and enterprise management. However, in the face of such a huge amount of data, traditional data processing mechanisms seem powerless and are unable to effectively cope with the diversity and complexity of the data.

[0003] The collection and aggregation of power equipment quality data face many problems. First, the data collection cost is high. The sources of equipment quality data are extensive and the formats are diverse, making it difficult to accurately and completely collect the data. For example, in complex production lines with multiple models and batches of equipment, data confusion and omission often occur. Second, the data transfer chain is long. Equipment quality data is often scattered in different systems and databases, and it is difficult to guarantee data relevance and consistency. In addition, the data heterogeneity is strong, and complex conversion and integration are required for different types of data. Finally, the availability of power quality data elements in the upstream and downstream of the supply chain is poor. Traditional data traceability methods are inefficient and unreliable, and it is difficult to meet the requirements of modern power systems for data quality and management. These problems not only affect the construction and operation and maintenance efficiency of power equipment, but also pose potential risks to the safe and stable operation of the power grid. Summary of the Invention

[0004] In view of this, the purpose of this application is to propose a data traceability method, device, equipment and storage medium.

[0005] As one aspect of this application, a data traceability method is provided, which is applied to a handle client and includes:

[0006] Obtain the handle identifier of the data to be traced; the handle identifier includes an identifier prefix and an identifier suffix; the identifier prefix is determined according to the handle server site configuration file; the identifier suffix is determined according to the position number, transaction sequence number of the blockchain to which the handle client belongs, and the generation time of the handle client;

[0007] Send an identification prefix resolution request to the global handle registration server, so that the global handle registration server determines the local handle server associated with the identification prefix based on the identification prefix; the identification prefix resolution request includes the handle identification;

[0008] Send an identification suffix resolution request to the local handle server, so that the local handle server determines the relevant information of the data to be traced based on the identification suffix; the identification suffix resolution request includes the handle identification.

[0009] Optionally, obtaining the handle identification of the data to be traced includes:

[0010] Send the transaction information corresponding to the data to be traced to the private chain;

[0011] In response to the completion of the transaction corresponding to the transaction information, monitor the transaction status of the transaction;

[0012] In response to the transaction being packaged and written to the blockchain, obtain the encoded information corresponding to the transaction;

[0013] Generate the identification suffix of the data to be traced based on the encoded information.

[0014] Optionally, obtaining the handle identification of the data to be traced includes:

[0015] Generate Ethereum virtual machine bytecode based on the smart contract corresponding to the obtained data to be traced, and deploy the Ethereum virtual machine bytecode to the blockchain;

[0016] Call the contract function in the blockchain based on the address of the smart contract;

[0017] Generate the identification suffix of the data to be traced based on the return value of the contract function, and the return value of the contract function includes: the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

[0018] Optionally, obtaining the handle identification of the data to be traced includes:

[0019] Deploy the local handle server and obtain the local handle server site configuration file;

[0020] Send the local handle server site configuration file and the data to be traced to the prefix identification management device, so that the prefix identification management device assigns the identification prefix to the data to be traced based on the local handle server site configuration file.

[0021] Optionally, the local handle server determines the relevant information of the data to be traced based on the identification suffix, including:

[0022] The local handle server sends the handle identifier to the Node.js server based on the identification information query module, so that the Node.js server retrieves the identification data corresponding to the handle identifier from the document-type database according to the handle identifier, and sends the retrieved identification data to the identification information query module;

[0023] The identification information query module generates relevant information of the data to be traced based on the identification data, and sends the relevant information of the data to be traced to the local handle server.

[0024] Optionally, the identification information query module generates relevant information of the data to be traced based on the identification data, including:

[0025] The identification information query module decrypts the encrypted ciphertext in the identification data based on the obtained secret key to obtain the hash value of the relevant information of the data to be traced;

[0026] The identification information query module determines the relevant information corresponding to the hash value of the relevant information of the data to be traced from the InterPlanetary File System as the relevant information of the data to be traced.

[0027] Optionally, the identification information storage module binds the handle identifier to the corresponding identification object, and uploads the relevant information of the identification object to the InterPlanetary File System;

[0028] The identification information storage module receives the content identifier returned by the InterPlanetary File System, and encrypts the content identifier based on the encryption algorithm;

[0029] The identification information storage module writes the encrypted content identifier into the blockchain, so that the handle identifier is bound to the local handle server, and the registration of the handle identifier is completed.

[0030] As a second aspect of the present application, a data traceability device is provided, which is applied to a handle client and includes: an acquisition module and a determination module;

[0031] The acquisition module is used to acquire the handle identifier of the data to be traced; the handle identifier includes an identifier prefix and an identifier suffix; the identifier prefix is determined according to the handle server site configuration file; the identifier suffix is determined according to the position number, transaction sequence number of the blockchain to which the handle client belongs, and the generation time of the handle client;

[0032] The determining module is configured to send a prefix resolution request of an identifier to a global handle registration server, so that the global handle registration server determines a local handle server associated with the identifier prefix based on the identifier prefix; the prefix resolution request of the identifier includes the handle identifier.

[0033] The determining module is further configured to send a suffix resolution request of an identifier to the local handle server, so that the local handle server determines relevant information of the data to be traced based on the identifier suffix; the suffix resolution request of the identifier includes the handle identifier.

[0034] Optionally, the obtaining module is specifically configured to send transaction information corresponding to the data to be traced to a private chain.

[0035] In response to completion of the transaction corresponding to the transaction information, monitor the transaction status of the transaction.

[0036] In response to the transaction being packaged and written to the blockchain, obtain encoded information corresponding to the transaction.

[0037] Generate an identifier suffix of the data to be traced based on the encoded information.

[0038] Optionally, the obtaining module is further specifically configured to generate Ethereum virtual machine bytecode based on the smart contract corresponding to the data to be traced, and deploy the Ethereum virtual machine bytecode to the blockchain.

[0039] Call a contract function in the blockchain based on the address of the smart contract.

[0040] Generate an identifier suffix of the data to be traced based on the return value of the contract function, and the return value of the contract function includes: the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

[0041] Optionally, the obtaining module is further specifically configured to deploy the local handle server and obtain a local handle server site configuration file.

[0042] Send the local handle server site configuration file and the data to be traced to a prefix identifier management device, so that the prefix identifier management device assigns the identifier prefix to the data to be traced based on the local handle server site configuration file.

[0043] Optionally, the determining module is specifically configured to send the handle identifier to a Node.js server by the local handle server based on an identifier information query module, so that the Node.js server retrieves identifier data corresponding to the handle identifier from a document-type database retrieved from the handle identifier, and sends the retrieved identifier data to the identifier information query module.

[0044] The identification information query module generates relevant information of the data to be traced based on the identification data, and sends the relevant information of the data to be traced to the local handle server.

[0045] Optionally, the determination module is further specifically configured to: the identification information query module decrypts the encrypted ciphertext in the identification data based on the obtained secret key to obtain the hash value of the relevant information of the data to be traced;

[0046] The identification information query module determines, from the InterPlanetary File System, the relevant information corresponding to the hash value of the relevant information of the data to be traced as the relevant information of the data to be traced.

[0047] Optionally, the data tracing device further includes a processing module, an encryption module, and a registration module;

[0048] The processing module is configured to: the identification information storage module binds the handle identifier with the corresponding identification object, and uploads the relevant information of the identification object to the InterPlanetary File System;

[0049] The encryption module is configured to: the identification information storage module receives the content identifier returned by the InterPlanetary File System, and encrypts the content identifier based on the encryption algorithm;

[0050] The registration module is configured to: the identification information storage module writes the encrypted content identifier into the blockchain, so that the handle identifier is bound to the local handle server, and the registration of the handle identifier is completed.

[0051] As a third aspect of the present application, an electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program, the data tracing method as described above is implemented.

[0052] As a fourth aspect of the present application, a non-transitory computer-readable storage medium is provided, and the non-transitory computer-readable storage medium stores computer instructions for causing the computer to execute the data tracing method provided by the present application as described above.

[0053] As can be seen from the above, the data traceability method, apparatus, device, and storage medium provided in this application assign a Handle identifier to power equipment. The Handle identifier consists of an identifier prefix and an identifier suffix. The identifier prefix is determined according to the Handle server site configuration file, ensuring the uniqueness of the identifier. The identifier suffix combines the location number of the blockchain, the transaction sequence number, and the generation time of the Handle client, further enhancing the traceability and security of the data. During the data traceability process, the method first sends an identifier prefix resolution request to the global handle registration server, and uses the global perspective of the global handle registration server to quickly locate the relevant local handle server. Subsequently, an identifier suffix resolution request is sent to the local handle server to obtain relevant information about the data to be traced. This ensures that all relevant data during the life cycle of the power equipment can be comprehensively obtained during the traceability process, avoiding information omission, achieving comprehensive and accurate quality traceability. At the same time, it improves the efficiency and accuracy of data traceability, simplifies the traceability process, enabling users to quickly obtain the required data by simply providing the Handle identifier, providing strong support for data management and application in the power industry. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solutions in this application or related technologies, the following will briefly introduce the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings in the following descriptions are only embodiments of this application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0055] Figure 1 Schematic diagram of an application scenario of a data traceability method provided in an embodiment of this application;

[0056] Figure 2 Schematic diagram of a process flow of a data traceability method provided in an embodiment of this application;

[0057] Figure 3 Schematic diagram of an architecture of a handle resolution service system provided in an embodiment of this application;

[0058] Figure 4 Schematic diagram of a basic identification code structure provided in an embodiment of this application;

[0059] Figure 5 Schematic diagram of a process flow of another data traceability method provided in an embodiment of this application;

[0060] Figure 6 Schematic diagram of a process flow of yet another data traceability method provided in an embodiment of this application;

[0061] Figure 7Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0062] Figure 8 Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0063] Figure 9 Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0064] Figure 10 Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0065] Figure 11 Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0066] Figure 12 Schematic flowchart of another data traceability method provided by an embodiment of this application;

[0067] Figure 13 Schematic diagram of the composition of a data traceability device provided by an embodiment of this application;

[0068] Figure 14 Schematic diagram of the composition of an electronic device provided by an embodiment of this application. Detailed implementation manners

[0069] To make the objectives, technical solutions and advantages of this application clearer and more understandable, the following further elaborates on this application in detail with reference to specific embodiments and the accompanying drawings. Obviously, the described embodiments are only a part rather than all of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0070] It should be noted that in the embodiments of this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplarily" or "for example" is intended to present relevant concepts in a specific manner. Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this application should have the ordinary meanings understood by those of ordinary skill in the art to which this application belongs. Summary of the Invention

[0072] In related technologies, weak data association often leads to incomplete quality traceability. Data in different links are often stored relatively independently and lack an effective association mechanism. For example, data in the production link is stored in the manufacturer's production management system, data in the transportation link is stored in the logistics system, and operation and maintenance data is stored in the operation and maintenance system of the power company. The data formats and identifiers between these systems are inconsistent, and there is no unified coding to closely connect them. This makes it difficult to fully integrate data from the entire life cycle of the equipment from production to operation during traceability, and it is impossible to fully trace quality problems, and information from key links may be missed. In addition, some existing traceability technologies use centralized data storage methods, and the data security and reliability are low. For example, traditional database storage is easily affected by human factors, and data may be misoperated, maliciously modified or deleted, resulting in the inability to guarantee the authenticity of the traceability data, which in turn affects the accurate judgment of quality problems of power equipment. At the same time, in the process of data collection and transmission, existing technologies often lack strict data verification and audit mechanisms, and are unable to detect and correct data errors in a timely manner. This makes it possible for erroneous or inaccurate data to spread in the traceability system, misleading the quality traceability results and increasing the difficulty of determining the root cause of quality problems.

[0073] The inventors of this application have discovered that most existing traceability technologies can only achieve simple linear traceability, that is, tracing the source of data in a fixed process sequence, and it is difficult to explore deep-seated causal relationships. Quality problems of power equipment are usually the result of the interaction of multiple factors, involving design defects, raw material quality, production processes, operating environment and other aspects. Existing technologies are unable to effectively analyze the complex relationships between these factors, resulting in insufficient traceability depth and the inability to accurately find the root cause of quality problems. At the same time, existing technologies have difficulties in processing multi-source heterogeneous data and cannot fully integrate data of different types and sources for comprehensive analysis. Lack of dynamism and real-time performance, data updates are not timely, and data updates of existing traceability technologies often lag and cannot reflect the latest status and changes of power equipment in a timely manner.

[0074] To solve the above problems, the present application provides a data traceability method. By assigning a Handle identifier to power equipment, the Handle identifier consists of an identifier prefix and an identifier suffix. The identifier prefix is determined according to the Handle server site configuration file, ensuring the uniqueness of the identifier. The identifier suffix combines the location number of the blockchain, the transaction sequence number, and the generation time of the Handle client, further enhancing the traceability and security of the data. During the data traceability process, the method first sends an identifier prefix resolution request to the global Handle registration server, and uses the global perspective of the global Handle registration server to quickly locate the relevant local Handle server. Subsequently, an identifier suffix resolution request is sent to the local Handle server to obtain relevant information about the data to be traced. This ensures that all relevant data during the life cycle of the power equipment can be comprehensively obtained during the traceability process, avoiding information omission, achieving comprehensive and accurate quality traceability. At the same time, it improves the efficiency and accuracy of data traceability, simplifies the traceability process, enabling users to quickly obtain the required data by only providing the Handle identifier, providing strong support for data management and application in the power industry.

[0075] After introducing the basic principle of the present application, the various non-limiting implementation manners of the present application will be specifically introduced below.

[0076] Overview of Application Scenarios

[0077] Figure 1 It is a schematic diagram of the application scenario of a data traceability method provided by an embodiment of the present application. As Figure 1 shown, the application scenario provides a Handle distributed management architecture, including a Global Handle Registry (GHR) 101, a Local Handle Service (LHS) 102, a prefix generation system 103, a blockchain network 104, and a Handle client 105. Among them, the connection method is through a wired or wireless communication network.

[0078] Among them, the GHR101 and LHS102 mentioned here can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. Optionally, the server can also be implemented on a cloud platform. For example, the cloud platform can include private clouds, public clouds, hybrid clouds, community clouds, distributed clouds, inter-clouds, and multi-clouds, etc., or any combination thereof. The embodiments of the present application do not limit this.

[0079] In some embodiments, GHR101 serves as the top layer of the Handle distributed management architecture and is responsible for the application and management of identification prefixes. It is uniformly managed by the global root node to ensure the uniqueness of each identification prefix globally. GHR101 consists of several parallel global Handle registries, and data between these registries is synchronized in real time and communicated equally to ensure data consistency and reliability. When the Handle client 105 needs to apply for a new Handle identifier, it will first send a request to GHR101. After passing the review, GHR will allocate a unique identification prefix for the client and associate the prefix with LHS102 to lay the foundation for subsequent Handle resolution.

[0080] In some embodiments, LHS102 is located under GHR101 and is responsible for storing and managing the specific information related to the Handle identifier. LHS102 also consists of multiple parallel service sites, and each site is a replica of other sites in the service to ensure high availability and fault tolerance of data. Each service site is composed of multiple Handle servers to handle requests from the Handle client 105. After the Handle client 105 completes the application for the identification prefix, it will use the prefix generation system 103 to generate the identification suffix of the Handle. Then, the applied Handle identification prefix and the generated identification suffix are spliced, and the network service (web service) identification registration interface in the LHS102 system is called to input the content that complies with the Handle identifier protocol specification into the LHS to complete the registration of the identifier.

[0081] In some embodiments, the prefix generation system 103 includes a Handle prefix application module and a front-end module. Through interaction with the blockchain network 104, the generation function of the Handle suffix identifier is implemented using a smart contract. The prefix generation system 103 ensures the uniqueness and security of the Handle identifier, providing a solid foundation for the registration and resolution of Handles.

[0082] In some embodiments, the blockchain network 104 plays a role of information storage and verification in the system. When the LHS 102 needs to resolve a Handle identifier and find the resource address it is bound to, it sends a suffix resolution request to the blockchain network 104. The blockchain network 104, according to its specific coding rules, finds the information bound to the identifier in a specific block and returns the data information to the LHS 102.

[0083] In some embodiments, the Handle client 105 is the interface for users to interact with the system. It is responsible for sending requests for applying, registering, and resolving Handle identifiers, and receiving responses from the GHR 101, LHS 102, and blockchain network 104. The Handle client 105 enables users to conveniently manage and use Handle identifiers, realizing the rapid location and access of digital resources.

[0084] It should be understood that Figure 1 is an exemplary structural diagram, Figure 1 the number of devices included in the application scenario shown is not limited. For example, the number of GHR 101s is not limited and the number of LHS 102s is not limited. And, in addition to Figure 1 the devices shown, Figure 1 the application scenario shown may also include other devices, which are not limited herein.

[0085] Next, in combination with Figure 1 the application scenario, the device control method according to the exemplary embodiments of the present application will be described. It should be noted that the above application scenario is only shown for the convenience of understanding the spirit and principle of the present application, and the embodiments of the present application are not limited in this regard. On the contrary, the embodiments of the present application can be applied to any applicable scenario.

[0086] Figure 2 is a schematic flowchart of a data traceability method provided by an embodiment of the present application. As Figure 2 shown, the data traceability method provided by the present application can be implemented through the above-mentioned Handle client 105, and specifically includes the following steps:

[0087] S201. Obtain the handle identifier of the data to be traced.

[0088] Among them, the handle identifier includes an identifier prefix (Prefix) and an identifier suffix (Suffix).

[0089] In some embodiments, the identifier prefix is determined according to the handle server site configuration file, which points to a specific handle server or a group of handle servers responsible for managing and resolving handles with the same prefix. The identifier suffix is determined according to the position number of the blockchain where the handle client belongs, the transaction sequence number, and the generation time of the handle client, which ensure the uniqueness of each handle identifier.

[0090] It should be noted that the Prefix is applied for registration by the user to the GHR, and a corresponding prefix management fee needs to be provided to the GHR during this process. The Suffix is completely defined by the enterprise itself and ensures the uniqueness of the Handle suffix identifier and a sufficiently large namespace. At the same time, the generated Suffix is stored in the blockchain network. Since the cost of storing data in the blockchain is expensive, the data to be stored needs to be as small as possible, which requires ensuring that the Suffix is not too long.

[0091] Exemplarily, the Handle identifier is 20.500.12875 / 9809093.8.1615345248, where the identifier prefix of the Handle is 20.500.12875, which is obtained by applying for registration to the GHR, and a certain fee needs to be paid for the management of this identifier prefix. The identifier suffix of the Handle is 9809093.8.210310, indicating that the data information of the identified object is stored in chainblockID 980.

[0092] In some embodiments, the Handle adopts a hierarchical identifier scheme. Each Handle consists of two parts: a prefix and a suffix. The prefix is its naming agency, and the suffix is the unique local name under the naming agency. The two are separated by " / ", for example: <handle>:: = "<Handle Naming Authority>" / "<Handle Local Name>", where the naming authority is the creator and manager of the Handle identifier, consisting of multiple non - empty sub - naming authorities separated by ".", forming a tree - like hierarchical structure together; the suffix is defined by the naming authority itself, and as long as it is unique within its local namespace, it can ensure its global uniqueness in the system. The Handle global namespace can be considered as a superset of multiple local namespaces, each local namespace has a unique prefix, and any local namespace can join the global namespace by applying for a prefix. And the binding relationship between its local identifier and value remains unchanged after joining the Handle system. Just by combining the local name with the prefix as the global identifier, global reference can be carried out, which helps to break information silos, facilitates enterprises to join their respective information systems, and is compatible with other identifier schemes. The Handle system provides a binding service from identifier to value. Each Handle can be resolved into a set of values, and each value can be an item introduction, information summary, URL, or other custom information. The Handle system adopts an iterative resolution method and a hierarchical resolution architecture, which is divided into two layers: GHR and LHS. Its complete resolution architecture consists of three parts: the Handle client, GHR, and LHS. As Figure 3 shown, it is the architecture of the Handle resolution service system.

[0093] The construction of device quality characteristic information is to identify and code the devices with shared requirements by each domain (Domain), bind the identifiers of these devices with the quality characteristics, and form the corresponding relationship of device - identifier - quality characteristic. After completing the construction of device quality characteristic information, keyword - attribute matching is provided to obtain the corresponding identifier search results. This subsection of research will use the Handle identifier technology as a support to design a unified and standardized identifier coding generation scheme for the objects with management requirements within the enterprise. The scheme design is divided into three parts: the formulation of the basic identification code standard for the identification object, the formulation of the Handle identifier coding generation rule, and the association between the coding and the fixed - asset information of the identification object.

[0094] First, to comply with a series of standards issued by the National Standardization Administration Committee, a combination of the line classification method and the hierarchical coding method is used to formulate the identification code standard. The identification objects within the enterprise are classified according to the attribute type and divided into two major parts and four minor parts. Among them, the two major parts are the category code segment and the classification code segment, and the four minor parts are the subdivisions of the category code segment and the classification code segment. The classification code segment is further divided into three code segments: the major category, the middle category, and the minor category. As Figure 4 The basic identification code structure shown has an object identification code composed of 8 digits in 4 layers. Among them, the 1st and 2nd digits represent the category code of the identified object; the last 6 digits represent the classification code of the identified object, where the 3rd and 4th digits represent the major category code of the object, the 5th and 6th digits represent the middle category code of the object, and the 7th and 8th digits represent the minor category code of the object. The finally formed numerical code is the basic identification code of the identified object.

[0095] Secondly, according to the registration rules of industrial Internet identification, a valid Handle identification code should consist of a prefix part and a suffix part. The prefix part is the prefix assigned by the identification and resolution secondary node platform to the enterprise, which is composed of three parts: country code, secondary node code, and enterprise code. Before formulating the generation rule of the Handle identification code for the identified object of the enterprise, first apply to the identification and resolution secondary node platform to register a unique enterprise identification prefix, which mainly involves information such as enterprise institution name, legal person information, and the industry to which the enterprise / institution belongs.

[0096] The total length of a valid Handle identification code can reach up to 256 bytes at most, so the scalability of the Handle identification code is extremely strong. The above Figure 4 has already formulated the basic identification code standard for the enterprise identified object, and divided the object code into two parts: category code segment and classification code segment. Next, define the suffix part of the Handle identification code, and conduct a preliminary expansion on the basis of the two parts of the category code segment and the classification code segment. Taking the equipment object as an example, define the suffix of the identification by taking the specific usage situation of the equipment as an extended attribute, and add four parts: manufacturer code, department code, input date, and product serial number. Finally, the suffix of the Handle identification code consists of six code segments: the category, classification, manufacturer, department, input date, and product serial number to which the equipment object belongs. The suffix data structure table of the identified object is shown in Table 1 below.

[0097] Table 1

[0098] Code Segment Character Length Remarks Category Code 2 digits Identify the category to which the object belongs Classification Code 6 digits Identify the detailed sub-type to which the object belongs Manufacturer Code 2 digits Identify the manufacturer number to which the object belongs Department Code 2 digits Identify the department number to which the object belongs Input Date 8 digits Identify the date when the object is put into use Product Serial Number 4 digits Identify the product number of the object

[0099] Finally, after the generation rule of the identification code is set up, it is also necessary to associate the generated code with the fixed asset information of the identified object to achieve "one object, one code; one number, one source". By parsing the code, the asset information associated with the code can be obtained. Identified objects of the same type have the same attributes in terms of name, specification, model, parameters, etc. Therefore, it is necessary to establish a corresponding metadata template for each type of object to store its asset information. Here, taking a certain piece of equipment as an example, establish its metadata template, and the specific content defined in the template is shown in Table 2.

[0100] Table 2

[0101] Name Data Type Content Example Metadata Template Model Character Type V1.0 Product Code Character Type 86.117.2 / 020101010304202112230001 Product Name Character Type Intelligent Terminal

[0102] When registering an identifier, it is necessary to select a data template and enter data. After the data entry is completed and passes the verification, the identifier registration is successful. After that, by querying the identifier, the specific information corresponding to the identifier can be obtained. After the coding information is associated, the coding information is carried by an active carrier and embedded in the production equipment or key components through the device identification code that matches the information, so as to realize the effective identification and unified management of the fixed assets within the enterprise.

[0103] In some embodiments, the present application provides a Handle suffix identification coding based on blockchain (BlockChain-based Identification Coding, abbreviated as BCIC), as Figure 5 shown, S201 can be specifically implemented as follows S2011-S2014:

[0104] S2011. Send the transaction information corresponding to the data to be traced to the private chain.

[0105] In some embodiments, first, a private chain environment is built through an Ethereum client (geth or ganache-cli), and at the same time, multiple accounts are generated and a certain amount of Ether is allocated. Then, determine the object to be identified and its related information. Furthermore, interact with the private chain network through the Ethereum client or the web.js library, send a transfer transaction to the private chain, and then record the returned transaction hash value for subsequent query of the transaction status. Finally, according to the returned transaction hash value, obtain the transaction information corresponding to the data to be traced.

[0106] It should be understood that if the identifier needs to carry additional information, these information can be encoded into a format suitable for blockchain storage (such as strings, hash values, etc.), and these information are attached to the transaction through the data fields of smart contracts or transactions, and these information are written into the block together with the transaction when sending the transaction.

[0107] S2012. In response to the completion of the transaction corresponding to the transaction information, monitor the transaction status of the transaction.

[0108] In some embodiments, use the event listening function of the web.js library to subscribe to the event corresponding to the transaction hash value. After the transaction is confirmed, the eth.getTransactionReceipt method can be used to obtain the transaction receipt, and the transaction ID (transactionID) and block information (including block hash value or block number) can be extracted from the transaction receipt.

[0109] S2013. In response to the transaction being packaged and written to the blockchain, obtain the coding information corresponding to the transaction.

[0110] In some embodiments, once it is monitored that a transaction is packaged and written into the blockchain, encoded information is returned in the form of [chainblockID].[transactionID].[timestampID], where chainblockID is the position number of the current block in the blockchain. When a new block is generated in the blockchain, chainblockID is incremented by one; transactionID is the specific position of the transaction in the current block body, and different transactions have different numbers according to the order of writing into the block; timestampID is the total number of seconds elapsed from 00:00:00 on January 1, 1970, Greenwich Mean Time, to the time when the block is generated. In this application, BCIC is bound to the storage location of the transaction in the blockchain. Due to the design of the blockchain, transactions are stored in the blockchain in the form of transaction hashes, and the hash value of a transaction is unique.

[0111] Exemplarily, for a transaction with a transaction hash of: "0x48c08449eade082f8fffa1b6f2062b2d5456a036f7b45505a27dad726a7d3a2b", it is stored in the transaction array transactions, the trans actionID is 1, the chainblockID of the block it is in is 10054003, and the timestampID of this block is 1618624522. Therefore, the BCIC corresponding to this transaction is 10054003.1.1618624522. It can be seen that each transaction stored in the blockchain will have a specific number. For any two transactions stored in the blockchain, assume: the chainblockIDs are BN1 and BN2 respectively; the transactionIDs are TN 1 and TN2 respectively; the timestampIDs are TT1 and TT2 respectively. Then according to this encoding standard, their corresponding BCICs are BN1.TN1.TT1 and BN2.TN2.TT2 respectively. And there are only two cases for the position forms of the two transactions in the blockchain:

[0112] (1) The two transactions are stored in the same block: At this time, there is:

[0113] BN1 = BN2, TN1 ≠ TN2, TT1 = TT2;

[0114] Then for the BCICs corresponding to the two transactions, there is:

[0115] BN1.TN1.TT1 ≠ BN2.TN2.TT2.

[0116] (2) The two transactions are stored in different blocks: At this time, there is:

[0117] BN1 ≠ BN2, TN1 = TN2, TT1 ≠ TT2;

[0118] Then, for the BCICs corresponding to the two transactions, there is: BN1.TN1.TT1 ≠ BN2.TN2.TT2.

[0119] In summary, for any two transactions stored in the blockchain, their BCICs both have BN1.TN1.TT1 ≠ BN2.TN2.TT2. Therefore, the identifier in the form of [chainblockID].[transactionID].[timestampID] is unique locally according to the encoding rule. At the same time, due to the scalability of the blockchain, it can meet the requirement that the identifier coding namespace is large enough to meet the needs of future marine data.

[0120] S2014. Generate the identifier suffix of the data to be traced based on the encoding information.

[0121] In some embodiments, the obtained encoding information [chainblockID].[transactionID].[timestampID] is used as the identifier suffix of the data to be traced. Then, the generated Handle identifier suffix of the data to be traced is returned as the identifier information conforming to the encoding rule.

[0122] In some embodiments, as Figure 6 shown, S201 can be specifically implemented as S2015 - S2017 as follows:

[0123] S2015. Generate Ethereum Virtual Machine bytecode based on the smart contract corresponding to the data to be traced, and deploy the Ethereum Virtual Machine bytecode to the blockchain.

[0124] In some embodiments, use the Solidity language to write the smart contract corresponding to the data to be traced. After writing, compile the smart contract into Ethereum Virtual Machine (EVM) bytecode and deploy it in the blockchain network. Then, record the returned smart contract address, and through this address, the contract functions deployed in the blockchain can be called.

[0125] S2016. Call the contract functions in the blockchain based on the address of the smart contract.

[0126] In some embodiments, through the recorded smart contract address, call the contract functions deployed in the blockchain. These functions can be used to generate and manage the identifier suffix to ensure the uniqueness and traceability of the identifier.

[0127] S2017. Generate the identifier suffix of the data to be traced based on the return value of the contract function.

[0128] Among them, the return values of the contract function include: the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

[0129] In some embodiments, when the EVM finishes executing the contract function and is packaged and written into the blockchain, the transaction is completed. Extract the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client from the transaction return value, and combine the extracted values into the identification suffix of the data to be traced according to the defined format, so as to obtain the Handle suffix identification that conforms to the identification coding rule.

[0130] In some embodiments, as Figure 7 shown, S201 can be specifically implemented as S2018 - S2019 as follows:

[0131] S2018. Deploy a local handle server and obtain the site configuration file of the local handle server.

[0132] In some embodiments, deploy a local handle server. For example, configure the software parameters of the local handle server, such as the location of the log file, database connection information, etc. Set the network parameters of the server, such as the IP address, port number, etc. Configure the security settings, such as SSL / TLS certificates, user authentication mechanisms, etc. Then, after the deployment is completed, obtain the site configuration file of the local handle server. This configuration file contains the basic information of the local handle server, such as the server address, port, management permissions, etc., ensuring that the server can correctly process handle resolution requests and interact with the prefix identification management device.

[0133] S2019. Send the site configuration file of the local handle server and the data to be traced to the prefix identification management device, so that the prefix identification management device assigns an identification prefix to the data to be traced based on the site configuration file of the local handle server.

[0134] In some embodiments, the prefix identification management device includes the above-mentioned prefix generation system. After the local handle server is deployed and the site configuration file is generated, it is necessary to send this configuration file and the data to be traced to the prefix identification management device. After receiving the handle server site configuration file, the prefix identification management device will parse the relevant information in the configuration file, such as the address of the server, resource access policies, etc. According to this information, the prefix identification management device will assign one or more unique prefixes to the data to be traced according to the information in the configuration file and the internal allocation policies and rules of the GHR, so as to uniquely identify resources in the network. Once the prefix is assigned, the prefix identification management device will send the Prefix information to the local handle server, and after receiving the prefix information, the local handle server will store it in the local database.

[0135] S202. Send an identification prefix resolution request to the global handle registration server, so that the global handle registration server determines the local handle server associated with the identification prefix based on the identification prefix.

[0136] Wherein, the identification prefix resolution request includes a handle identifier.

[0137] In some embodiments, the GHR is used to resolve the Handle identification prefix. By sending an identification prefix resolution request to the GHR, the purpose of this request is to find the LHS associated with the identification prefix. Furthermore, the GHR determines the address or network location of the LHS associated with the identification prefix based on the identification prefix, and returns the site information of the LHS. After receiving the returned LHS site information, the Handle client finds the corresponding LHS server according to this information.

[0138] S203. Send an identification suffix resolution request to the local handle server, so that the local handle server determines the relevant information of the data to be traced based on the identification suffix.

[0139] Wherein, the identification suffix resolution request includes a handle identifier.

[0140] In some embodiments, after determining the location of the LHS, the Handle identifier is sent to the LHS for resolution. After receiving the identification suffix resolution request, the LHS obtains the resource address bound to the identifier according to its resolution result. Further, after locating the resource address, the LHS sends a suffix resolution request to the corresponding blockchain network node. According to the suffix-specific encoding rule, the relevant information of the data to be traced bound to the identifier is found in a specific block, and at the same time, the relevant information is returned to the LHS. After receiving the relevant information of the data to be traced, the LHS returns it to the Handle client.

[0141] In some embodiments, as Figure 8 shown, S203 can be specifically implemented as S2031 - S2032 as follows:

[0142] S2031. The local handle server sends a handle identifier to the Node.js server based on the identification information query module, so that the Node.js server retrieves the identification data corresponding to the handle identifier from the document-type database retrieved from the handle identifier, and sends the retrieved identification data to the identification information query module.

[0143] In some embodiments, the LHS has one or more Handle identifiers that are used to uniquely identify specific data stored in a document-based database (MongoDB). The LHS sends the Handle identifiers to the Node.js server based on the identifier information query module, requesting to retrieve the corresponding data. After receiving the Handle identifiers, the Node.js server uses these identifiers as query conditions to access the MongoDB database and perform a query operation in MongoDB to retrieve the data records that match the Handle identifiers. Then, the Node.js server encapsulates the retrieved identifier data into an appropriate response format and sends it back to the identifier information query module.

[0144] S2032. The identifier information query module generates information related to the data to be traced based on the identifier data and sends the information related to the data to be traced to the local handle server.

[0145] In some embodiments, based on the received identifier data, the identifier information query module generates information related to the data to be traced. These information may include the source of the data, the timestamp, the data content summary, etc., for subsequent data tracing. Furthermore, the identifier information query module sends the generated information related to the data to be traced to the LHS. The LHS receives the information related to the data to be traced and stores it in the local database for subsequent query and management.

[0146] In some embodiments, as Figure 9 shown, S2032 can be specifically implemented as S2032a - S2032b as follows:

[0147] S2032a. The identifier information query module decrypts the encrypted ciphertext in the identifier data based on the obtained secret key to obtain the hash value of the information related to the data to be traced.

[0148] In some embodiments, the identifier information query module receives the identifier data returned from the Node.js server, which contains ciphertext encrypted by the Advanced Encryption Standard (AES) algorithm. The identifier information query module uses the pre-obtained secret key to decrypt the received ciphertext. Among them, AES is a symmetric encryption algorithm. The decrypted data contains the hash value of the information related to the data to be traced. This hash value is a fixed-length string used to uniquely identify the original data.

[0149] S2032b. The identifier information query module determines the information corresponding to the hash value of the information related to the data to be traced from the InterPlanetary File System as the information related to the data to be traced.

[0150] In some embodiments, the identification information query module uses the extracted hash value to query in the InterPlanetary File System (IPFS) network. IPFS is a distributed file system that allows users to store and retrieve the content of files, not just the names of files. In IPFS, each file has a unique hash value used to locate and retrieve the file. The IPFS network returns the file content that matches the query hash value according to the query request. Furthermore, relevant information of the data to be traced is extracted from the files or data obtained from the IPFS network.

[0151] The data tracing method provided by this application assigns a Handle identifier to the power equipment. The Handle identifier consists of an identification prefix and an identification suffix. The identification prefix is determined according to the Handle server site configuration file, ensuring the uniqueness of the identifier; while the identification suffix combines the location number of the blockchain, the transaction sequence number, and the generation time of the Handle client, further enhancing the traceability and security of the data. During the data tracing process, the method first sends an identification prefix resolution request to the global handle registration server, and uses the global perspective of the global handle registration server to quickly locate the relevant local handle server; subsequently, it sends an identification suffix resolution request to the local handle server to obtain relevant information of the data to be traced. This ensures that all relevant data during the life cycle of the power equipment can be comprehensively obtained during the tracing process, avoiding information omission, achieving comprehensive and accurate quality tracing. At the same time, it improves the efficiency and accuracy of data tracing, simplifies the tracing process, enabling users to quickly obtain the required data by only providing the Handle identifier, providing strong support for data management and application in the power industry.

[0152] In some embodiments, as Figure 10 shown, after S203, the data tracing method provided by the embodiments of this application further includes the following S301 - S303:

[0153] S301. The identification information storage module binds the handle identifier with the corresponding identification object, and uploads the relevant information of the identification object to the InterPlanetary File System.

[0154] In some embodiments, the identification information storage module first creates a binding relationship to associate the handle identifier with the corresponding identification object. Then, the identification information storage module uploads the relevant information of the identification object to the IPFS network. The IPFS network receives and stores these data, and then returns the content identifier (CID) of the corresponding information for subsequent retrieval of these data.

[0155] S302. The identification information storage module receives the content identifier returned by the InterPlanetary File System and encrypts the content identifier based on the encryption algorithm.

[0156] In some embodiments, the identification information storage module receives the returned CID from the IPFS network and encrypts the CID using a predefined encryption algorithm, such as the AES algorithm. The key used in the encryption process is securely stored to ensure that only authorized objects can access it, thereby ensuring the security and reliability of the encrypted data.

[0157] S303. The identification information storage module writes the encrypted content identifier into the blockchain so that the handle identifier is bound to the local handle server, completing the registration of the handle identifier.

[0158] In some embodiments, the identification information storage module calls the storage function interface in the smart contract and writes the encrypted CID and the generated Suffix into the blockchain in the form of key-value pairs. The smart contract is responsible for processing data storage and management to ensure the immutability and traceability of the data. After the data is written into the blockchain, the smart contract triggers a data storage event to notify relevant modules that the data has been successfully stored, and the relevant modules can listen for these events for subsequent processing and verification.

[0159] In some embodiments, the Node.Js server enables an event listening service to listen for specified data storage events in the blockchain. The Node.Js server writes the listened data into the MongoDB database to complete data backup to speed up data query. The suffix identifier generation module concatenates the Prefix and the BCIC obtained from S2011 - S2014 with " / " and creates a Handle identifier through the Handle client, binding the identifier to the LHS for subsequent query of identification information, thus completing a process of registering a Handle identifier.

[0160] The data traceability method provided by this application completes the registration process of the Handle identifier by binding the Handle identifier to the corresponding identification object. Furthermore, the identification information storage module can securely store the information of the identification object in IPFS and record the encrypted CID on the blockchain, thereby providing a reliable and decentralized way to manage and verify identification information.

[0161] In some embodiments, a two-dimensional code nameplate is selected as the coding label for the power equipment to identify the power equipment. The middle part of the two-dimensional code label style is the two-dimensional code body. The size of the two-dimensional code label preferably selects a large label, and medium and small labels can also be selected according to the actual situation of the equipment. In special cases, if none of the three sizes meet the requirements, the label size can be determined by oneself. The specific size-related parameters are shown in Table 3 below. The two-dimensional code nameplate style adopts an integrated design of the two-dimensional code label and the nameplate, and is divided into three forms: upper-lower design type, left-right design type, and inclusion design type.

[0162] Table 3

[0163]

[0164] It should be understood that in the process of the whole life cycle management of power equipment, two-dimensional codes are associated with the above identification and parsing codes and pasted on the equipment. Users can assign codes during the procurement and warehousing stages of the equipment. On-site employees can establish their basic account books by scanning the codes for warehousing, and scan the codes in the links of installation, use, transfer, scrapping, etc. to record the quality data and store it in the system. Users can scan the codes to trace its historical information and processing records.

[0165] In some embodiments, such as Figure 11 As shown in the figure, the embodiment of the present application provides a schematic flow diagram of a data traceability method. The traceability of the quality information of the entire life cycle of power equipment is an operation that tracks and records the entire process of the equipment from procurement, installation, maintenance to scrapping. Through traceability, detailed information about the equipment, operation history, maintenance records, data on replaced parts, and any repairs or changes the equipment has undergone can be obtained. The construction of the power equipment quality data traceability model includes: Equipment basic information layer: Equipment identifier (H), that is, the Handle code, which serves as the unique identifier of the equipment and is used to associate all data related to this equipment. Equipment type (T), such as transformer (T1), circuit breaker (T2), switchgear (T3), etc. Different types of equipment have different quality parameters and structural characteristics. Manufacturer (M), in string form, representing the manufacturer of the equipment. Production date (D), in the format of "YYYY-MM-DD", recording the date when the equipment production is completed. Production link data layer: Raw material information (R), including the type of raw material (R_type), supplier (R_supplier), batch (R_batch), etc. For example, for a transformer, the raw materials may include core materials (such as silicon steel sheets), winding materials (such as copper wires), etc. Production process parameters (P), which is a set of data related to the production process. For different types of equipment, the production process parameters are different. Taking a transformer as an example, the winding tension when winding the winding, the pressure of the core laminations, etc. are all important process parameters. Quality inspection data (Q_prod), the results of various quality inspections carried out during the production process. Installation link data layer: Installation (L), the detailed installation geographical location, such as longitude and latitude coordinates (L_lat, L_lon). Installation time (t_inst), the time point when the equipment installation is completed, in the format of "YYYY-MM-DD HH:MM:SS". Installation and commissioning data (D_inst), including the initial test results after installation, such as wiring inspection of the equipment (D_inst-wire), parameter setting (D_inst-param), etc. For example, for a circuit breaker, it is necessary to check whether its opening and closing times (t_open, t_close) are within the specified range, and the calculation formula is the same as the opening and closing time measurement method in the equipment quality parameter layer. Operation link data layer: Operation time (t_run), the cumulative duration since the equipment was put into operation, with the unit of hour (h). Operation status data (S_run), including real-time electrical parameters (such as voltage V_run, current I_run, etc.), temperature data (T_run), alarm information of the equipment (A_run), etc. Maintenance record (M_run), information such as the time of each maintenance (t_maintain), maintenance content (M_content), replaced parts (P_replace), etc. Quality problem feedback layer: Problem discovery time (t_find), the time point when the equipment quality problem is discovered.Problem description (D_prob), a detailed description of quality problems, such as fault phenomena (D_prob - fault), performance anomalies (D_prob - abn), etc. The severity level of the problem (S_prob) can be divided into levels such as minor, medium, and severe, and is classified according to the impact of the problem on the operation of the equipment and the power system. The Handle code, as the core hub of the entire traceability model, is the key to realizing the correlation and integration of data throughout the life cycle of power equipment. By assigning a unique Handle code to each power equipment and establishing a complete set of coding management and parsing mechanisms, the data generated in various links such as production, transportation, installation, operation, and maintenance of the equipment can be effectively correlated without error, breaking the traditional data island phenomenon and providing a solid foundation for comprehensive and accurate quality traceability. In addition, a multi-level data model is constructed, including the basic information layer of the equipment, the production link data layer, the transportation link data layer, the installation link data layer, the operation link data layer, and the quality problem feedback layer, comprehensively covering various types of information related to the quality of power equipment. The data between each level is closely correlated through the Handle code, and corresponding data structures and storage methods are designed according to the characteristics of different levels, which can not only ensure the integrity of the data, but also facilitate data query, analysis, and traceability, thus realizing in-depth mining and refined management of power equipment quality data.

[0166] In some embodiments, such as Figure 12 shown, the embodiment of the present application provides a schematic flow chart of a data traceability method, which correlates the data of each link through the Handle code. When a quality problem occurs, starting from the problem feedback layer, along Figure 12 Path tracing: First, based on the Handle code (H) of the problem device, search for the operating status data (S_run) and maintenance records (M_run) in the operation link data layer to analyze whether the problem is related to the operating environment or improper maintenance. Then, through the installation information in the installation link data layer (such as installation location L, installer P_inst, installation and commissioning data D_inst), check whether there are problems in the installation process. Finally, in the production link data layer, review the raw material information (R), production process parameters (P), and quality inspection data (Q_prod) to determine whether the quality problem originates from the production link. Different from the traditional forward or simple linear tracing method, this algorithm can start from the quality problem feedback, based on the Handle code of the device, and intelligently trace back in the multi-level data model, comprehensively considering the complex relationships and mutual influences between the data of each link, and quickly and accurately locate the root cause of the quality problem. By introducing technologies such as data mining and machine learning, analyze and learn a large amount of historical data, continuously optimize the tracing path and judgment rules, and improve the accuracy and efficiency of tracing. Moreover, by establishing a data dynamic update and real-time monitoring mechanism, ensure that the data in the tracing model can timely reflect the latest status and changes of power equipment. Through real-time data interaction with the operation monitoring system, maintenance management system, etc. of power equipment, once the device undergoes a status change or a maintenance operation, the relevant data can be automatically updated to the tracing model. At the same time, real-time monitor the operating parameters and quality indicators of the device, and when an anomaly occurs, the tracing process can be triggered in a timely manner, providing strong support for the quality control and fault prevention of the device.

[0167] It should be noted that the method of the embodiment of the present application can be executed by a single device, such as a computer or a server, etc. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In this case of a distributed scenario, one of the multiple devices can only execute one or more steps of the method of the embodiment of the present application, and these multiple devices will interact with each other to complete the described method.

[0168] It should be noted that some embodiments of the present application have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be executed in a different order from that in the above embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or consecutive order shown to achieve the desired results. In certain embodiments, multi-tasking and parallel processing are also possible or may be advantageous.

[0169] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present application also provides a data tracing device.

[0170] Reference Figure 13 The data traceability device includes an acquisition module 1301 and a determination module 1302;

[0171] The acquisition module 1301 is configured to acquire a handle identifier of the data to be traced; the handle identifier includes an identifier prefix and an identifier suffix; the identifier prefix is determined according to a handle server site configuration file; the identifier suffix is determined according to the position number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client;

[0172] The determination module 1302 is configured to send an identifier prefix resolution request to a global handle registration server, so that the global handle registration server determines a local handle server associated with the identifier prefix based on the identifier prefix; the identifier prefix resolution request includes the handle identifier;

[0173] The determination module 1302 is further configured to send an identifier suffix resolution request to the local handle server, so that the local handle server determines relevant information of the data to be traced based on the identifier suffix; the identifier suffix resolution request includes the handle identifier.

[0174] In some embodiments, the acquisition module 1301 is specifically configured to send transaction information corresponding to the data to be traced to a private chain;

[0175] In response to the completion of the transaction corresponding to the transaction information, monitor the transaction status of the transaction;

[0176] In response to the transaction being packaged and written to the blockchain, acquire the encoded information corresponding to the transaction;

[0177] Generate an identifier suffix of the data to be traced based on the encoded information.

[0178] In some embodiments, the acquisition module 1301 is further specifically configured to generate Ethereum virtual machine bytecode based on the smart contract corresponding to the acquired data to be traced, and deploy the Ethereum virtual machine bytecode to the blockchain;

[0179] Call a contract function in the blockchain based on the address of the smart contract;

[0180] Generate an identifier suffix of the data to be traced based on the return value of the contract function, and the return value of the contract function includes: the position number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

[0181] In some embodiments, the acquisition module 1301 is further specifically configured to deploy the local handle server and acquire a local handle server site configuration file;

[0182] Send the local handle server site configuration file and the data to be traced to the prefix identification management device, so that the prefix identification management device allocates the identification prefix for the data to be traced based on the local handle server site configuration file.

[0183] In some embodiments, the determining module 1302 is specifically configured to: the local handle server sends the handle identifier to the Node.js server based on the identification information query module, so that the Node.js server retrieves the identification data corresponding to the handle identifier from the document-type database according to the handle identifier, and sends the retrieved identification data to the identification information query module;

[0184] The identification information query module generates the relevant information of the data to be traced based on the identification data, and sends the relevant information of the data to be traced to the local handle server.

[0185] In some embodiments, the determining module 1302 is further specifically configured to: the identification information query module decrypts the encrypted ciphertext in the identification data based on the obtained secret key to obtain the hash value of the relevant information of the data to be traced;

[0186] The identification information query module determines the relevant information corresponding to the hash value of the relevant information of the data to be traced from the InterPlanetary File System as the relevant information of the data to be traced.

[0187] In some embodiments, the data traceability device further includes a processing module 1303, an encryption module 1304, and a registration module 1305;

[0188] The processing module 1303 is configured to: the identification information storage module binds the handle identifier with the corresponding identification object, and uploads the relevant information of the identification object to the InterPlanetary File System;

[0189] The encryption module 1304 is configured to: the identification information storage module receives the content identifier returned by the InterPlanetary File System, and encrypts the content identifier based on the encryption algorithm;

[0190] The registration module 1305 is configured to: the identification information storage module writes the encrypted content identifier into the blockchain, so that the handle identifier is bound to the local handle server, and the registration of the handle identifier is completed.

[0191] For the convenience of description, when describing the above device, various modules are described separately according to their functions. Of course, when implementing the present application, the functions of each module can be implemented in one or more software and / or hardware.

[0192] The device of the above embodiment is used to implement the corresponding data traceability method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0193] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the data traceability method described in any of the above embodiments.

[0194] Figure 14 FIG. shows a more specific schematic diagram of the hardware structure of the electronic device provided in this embodiment. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1060. Among them, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are communicatively connected to each other inside the device through the bus 1060.

[0195] The processor 1010 may be implemented in a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0196] The memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0197] The input / output interface 1030 is used to connect to an input / output module to implement information input and output. The input / output module may be configured as a component in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Among them, the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0198] The communication interface 1040 is used to connect a communication module (not shown in the figure) to achieve communication and interaction between this device and other devices. The communication module can communicate through a wired method (such as USB, network cable, etc.) or through a wireless method (such as mobile network, WIFI, Bluetooth, etc.).

[0199] The bus 1050 includes a path for transmitting information between various components of the device (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0200] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device may also only include the components necessary to implement the solution of the embodiments of this specification, and does not necessarily include all the components shown in the figure.

[0201] The electronic device in the above embodiment is used to implement the corresponding data traceability method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0202] Based on the same inventive concept, corresponding to the method in any of the above embodiments, the present application also provides a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause the computer to execute the data traceability method described in any of the foregoing embodiments.

[0203] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0204] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the data traceability method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0205] Based on the same inventive concept, corresponding to the data traceability method described in any of the above embodiments, the present disclosure also provides a computer program product, which includes a computer program. In some embodiments, the computer program is executable by one or more processors to cause the processors to execute the data traceability method. Corresponding to the execution subjects corresponding to the steps in the various embodiments of the data traceability method, the processors executing the corresponding steps may belong to the corresponding execution subjects.

[0206] The computer program product of the above embodiments is used to cause the processor to execute the data traceability method described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0207] Those of ordinary skill in the art should understand that: the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope of the present application (including the claims) is limited to these examples; under the concept of the present application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of the embodiments of the present application as described above, and they are not provided in detail for the sake of brevity.

[0208] In addition, for simplicity of explanation and discussion, and in order not to make the embodiments of the present application difficult to understand, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. In addition, the devices may be shown in block diagram form to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present application are to be implemented (i.e., these details should be completely within the understanding of those skilled in the art). In the case where specific details (such as circuits) are set forth to describe the exemplary embodiments of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be implemented without these specific details or with variations of these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0209] Although the present application has been described in connection with specific embodiments of the present application, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art based on the foregoing description. For example, other memory architectures (such as dynamic RAM (DRAM)) can be used with the embodiments discussed.

[0210] Embodiments of the present application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application shall be included within the protection scope of the present application.< / handle>

Claims

1. A data traceability method, characterized in that, Applied to a handle client, the method includes: Obtaining a handle identifier of the data to be traced; the handle identifier includes an identifier prefix and an identifier suffix; the identifier prefix is determined according to the handle server site configuration file; the identifier suffix is determined according to the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client; Sending an identifier prefix resolution request to the global handle registration server, so that the global handle registration server determines the local handle server associated with the identifier prefix based on the identifier prefix; the identifier prefix resolution request includes the handle identifier; Sending an identifier suffix resolution request to the local handle server, so that the local handle server determines the relevant information of the data to be traced based on the identifier suffix; the identifier suffix resolution request includes the handle identifier.

2. The data traceability method according to claim 1, wherein The obtaining of the handle identifier of the data to be traced includes: Sending the transaction information corresponding to the data to be traced to the private chain; In response to the completion of the transaction corresponding to the transaction information, monitoring the transaction status of the transaction; In response to the transaction being packaged and written to the blockchain, obtaining the encoded information corresponding to the transaction; Generating the identifier suffix of the data to be traced based on the encoded information.

3. The data traceability method according to claim 1, wherein The obtaining of the handle identifier of the data to be traced includes: Generating Ethereum virtual machine bytecode based on the smart contract corresponding to the obtained data to be traced, and deploying the Ethereum virtual machine bytecode to the blockchain; Invoking a contract function in the blockchain based on the address of the smart contract; Generating the identifier suffix of the data to be traced based on the return value of the contract function, and the return value of the contract function includes: the location number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

4. The data traceability method according to claim 1, characterized in that The obtaining of the handle identifier of the data to be traced includes: Deploying the local handle server and obtaining the local handle server site configuration file; Sending the local handle server site configuration file and the data to be traced to the prefix identifier management device, so that the prefix identifier management device assigns the identifier prefix to the data to be traced based on the local handle server site configuration file.

5. The data traceability method according to claim 1, wherein The local handle server determining the relevant information of the data to be traced based on the identifier suffix includes: The local handle server sends the handle identifier to the Node.js server through the identifier information query module, so that the Node.js server retrieves the identifier data corresponding to the handle identifier from the document type database according to the handle identifier, and sends the retrieved identifier data to the identifier information query module; The identifier information query module generates the relevant information of the data to be traced based on the identifier data, and sends the relevant information of the data to be traced to the local handle server.

6. The data traceability method according to claim 5, wherein The identifier information query module generating the relevant information of the data to be traced based on the identifier data includes: The identifier information query module decrypts the encrypted ciphertext in the identifier data based on the obtained secret key to obtain the hash value of the relevant information of the data to be traced; The identification information query module determines, from the InterPlanetary File System, the relevant information corresponding to the hash value of the relevant information of the data to be traced as the relevant information of the data to be traced.

7. The data traceability method according to claim 1, wherein The method further includes: The identification information storage module binds the handle identifier to the corresponding identification object and uploads the relevant information of the identification object to the InterPlanetary File System; The identification information storage module receives the content identifier returned by the InterPlanetary File System and encrypts the content identifier based on an encryption algorithm; The identification information storage module writes the encrypted content identifier into the blockchain so that the handle identifier is bound to the local handle server, completing the registration of the handle identifier.

8. A data traceability device, characterized in that, Applied to a handle client, the device includes: an acquisition module and a determination module; The acquisition module is configured to acquire a handle identifier of the data to be traced; the handle identifier includes an identification prefix and an identification suffix; the identification prefix is determined according to the handle server site configuration file; the identification suffix is determined according to the position number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client; The determination module is configured to send an identification prefix resolution request to the global handle registration server so that the global handle registration server determines the local handle server associated with the identification prefix based on the identification prefix; the identification prefix resolution request includes the handle identifier; The determination module is further configured to send an identification suffix resolution request to the local handle server so that the local handle server determines the relevant information of the data to be traced based on the identification suffix; the identification suffix resolution request includes the handle identifier.

9. The device according to claim 8, characterized in that, The acquisition module is specifically configured to: Send the transaction information corresponding to the data to be traced to the private chain; In response to the completion of the transaction corresponding to the transaction information, monitor the transaction status of the transaction; In response to the transaction being packaged and written into the blockchain, obtain the coding information corresponding to the transaction; Generate the identification suffix of the data to be traced based on the coding information.

10. The device according to claim 8, characterized in that, The acquisition module is specifically configured to: Generate Ethereum virtual machine bytecode based on the obtained smart contract corresponding to the data to be traced and deploy the Ethereum virtual machine bytecode to the blockchain; Call the contract function in the blockchain based on the address of the smart contract; Generate the identification suffix of the data to be traced based on the return value of the contract function, and the return value of the contract function includes: the position number of the blockchain to which the handle client belongs, the transaction sequence number, and the generation time of the handle client.

11. The device according to claim 8, characterized in that, The acquisition module is specifically configured to: Deploy the local handle server and obtain the local handle server site configuration file; Send the local handle server site configuration file and the data to be traced to the prefix identification management device so that the prefix identification management device allocates the identification prefix for the data to be traced based on the local handle server site configuration file.

12. The device according to claim 8, characterized in that The determination module is specifically configured to: The local handle server sends the handle identifier to the Node.js server based on the identifier information query module, so that the Node.js server retrieves the identifier data corresponding to the handle identifier from the document-type database according to the handle identifier, and sends the retrieved identifier data to the identifier information query module; The identifier information query module generates the relevant information of the data to be traced based on the identifier data, and sends the relevant information of the data to be traced to the local handle server.

13. The device according to claim 12, wherein The determination module is further specifically configured to: The identifier information query module decrypts the encrypted ciphertext in the identifier data based on the obtained secret key to obtain the hash value of the relevant information of the data to be traced; The identifier information query module determines the relevant information corresponding to the hash value of the relevant information of the data to be traced from the InterPlanetary File System as the relevant information of the data to be traced.

14. The device according to claim 8, characterized in that, The device further includes a processing module, an encryption module, and a registration module; The processing module is configured to bind the handle identifier with the corresponding identifier object by the identifier information storage module, and upload the relevant information of the identifier object to the InterPlanetary File System; The encryption module is configured to receive the content identifier returned by the InterPlanetary File System by the identifier information storage module, and encrypt the content identifier based on the encryption algorithm; The registration module is configured to write the encrypted content identifier into the blockchain by the identifier information storage module, so that the handle identifier is bound to the local handle server, and the registration of the handle identifier is completed.

15. An electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the method according to any one of claims 1 to 7 when executing the program.

16. A non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores computer instructions for causing a computer to execute the method according to any one of claims 1 to 7.

Images