Identification resolution method, apparatus, system, device, and readable storage medium

Abstract

This application provides an identifier resolution method, apparatus, system, device, and readable storage medium. The method deploys a next-level node to the enterprise nodes in the existing industrial internet identifier resolution system. This next-level node has edge identification capabilities. Using this next-level node, the target data to be encoded generated by the unit in the industrial site is generated according to preset encoding rules to generate an identifier code that conforms to a unified encoding standard. The identification code and the target data transmission process are made secure and reliable by using encrypted transmission. This realizes the edge identifier resolution capability and the sinking of the identifier resolution system in the industrial site, bringing it closer to the data source. Based on the identifier resolution system, the accuracy, reliability, and timeliness of industrial site identifiers are guaranteed.

Description

Technical Field

[0001] This application relates to the field of industrial internet technology, and in particular to an identifier resolution method, apparatus, system, device, and readable storage medium. Background Technology

[0002] The identifier resolution system is considered the "foundation of the foundation" of the Industrial Internet, serving as the nerve center supporting its connectivity and enabling the interconnection of people, machines, and things. The Industrial Internet identifier resolution system assigns a unique identity code to each entity or virtual object through barcodes, QR codes, and RFID tags, while simultaneously carrying relevant data information, thus creating a new type of infrastructure for the location, connection, and communication of physical and virtual objects.

[0003] The existing identifier resolution system consists of node elements such as international root nodes, national top-level nodes, second-level nodes, enterprise nodes, and recursive nodes. Under the existing industrial internet identifier resolution system, enterprises can use the enterprise nodes already built in the system to generate identifier codes and associate the identifier codes with the second-level nodes or even the top-level nodes. However, many enterprises use these enterprise nodes to generate codes according to their own identifier coding rules. During circulation, these proprietary codes need to be converted into new identifier codes that conform to the unified identifier coding standard, which affects work efficiency and can easily lead to the failure of information association between proprietary codes and new identifier codes, making it impossible to obtain relevant information by identifying the new identifier codes. At the same time, most enterprise nodes are located on the cloud side, which cannot respond to complex and ever-changing industrial site conditions in a timely manner. Using enterprise nodes to generate enterprise-level identifier codes may not be able to update the identifier coding rules in a timely manner, and there are problems such as poor timeliness and stability of identifier codes. Summary of the Invention

[0004] In view of this, in order to solve the above-mentioned technical problems, this application provides an identifier resolution method, apparatus, system, device and readable storage medium.

[0005] Specifically, this application is implemented through the following technical solution:

[0006] According to a first aspect of the embodiments of this application, an identifier resolution method is provided, the method comprising:

[0007] In a specified industrial application scenario, a next-level node is determined. This next-level node is at least one newly added node under the enterprise node already defined in the existing Industrial Internet Identifier Resolution System, through improvements to the existing system. Each node in this next-level node corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using this rule conforms to the identifier encoding specification required by the second-level node. The second-level node is the next-level node defined in the existing Industrial Internet Identifier Resolution System as the parent node of the enterprise node.

[0008] Each node in the next level collects target data to be encoded from its corresponding designated industrial site unit, encodes the target data using pre-set identification encoding rules to generate encoded data that conforms to the identification encoding specifications required by the second-level node, encrypts the encoded data and the target data, and transmits them to the second-level node for storage.

[0009] Optionally, the next-level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario.

[0010] Optionally, the target data is the product produced by the designated industrial site unit, or the data during the product production process of the designated industrial site unit;

[0011] When the target data is data from the production process of the designated industrial site unit, the step of encrypting the coded data and the target data and transmitting them to the secondary node includes:

[0012] Following the principle that the order of data sent to the secondary node is consistent with the order of data collected, the production data at different time points during the production process of the set industrial site unit and the encoded data of the production data are encrypted and transmitted to the secondary node.

[0013] Optionally, the industrial site unit is at least one production workshop or at least one production line.

[0014] Optionally, encrypting the encoded data and the target data and transmitting them to the secondary node includes:

[0015] The encoded data and the target data are signed using the target private key to obtain a digital signature;

[0016] The digital signature is sent to the secondary node, so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and store the encoded data and the target data after the verification is successful.

[0017] According to a second aspect of the embodiments of this application, an identifier resolution system is provided. This system includes at least enterprise nodes already defined in the existing industrial internet identifier resolution system, and second-level nodes, which are the upper-level nodes of the enterprise nodes. The system also includes lower-level nodes determined in a specified industrial application scenario. These lower-level nodes are at least one newly added node under the enterprise nodes already defined in the existing industrial internet identifier resolution system, achieved through improvements to the existing system. Each node in the lower-level system corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using the identifier encoding rule conforms to the identifier encoding specification required by the second-level node.

[0018] The next-level node is used to collect target data to be encoded from its corresponding set industrial field units, encode the target data using a pre-set identification encoding rule to generate encoded data that conforms to the identification encoding specification required by the second-level node, encrypt the encoded data and the target data and transmit them to the second-level node for storage.

[0019] According to a third aspect of the embodiments of this application, an identifier resolution device is provided, applied to a next-level node, wherein the next-level node is a node determined in a specified industrial application scenario, and the next-level node is at least one newly added node under the enterprise node already defined in the existing industrial internet identifier resolution system by improving the existing industrial internet identifier resolution system; each node in the next-level node corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained by encoding using the identifier encoding rule conforms to the identifier encoding specification required by the second-level node; the second-level node is the next-level node defined in the existing industrial internet identifier resolution system as the enterprise node; the device includes:

[0020] The data acquisition module is used to collect target data to be encoded from the corresponding set industrial field units through each node in the next layer node;

[0021] The encoded data generation module is used to encode the target data using pre-set identifier encoding rules to generate encoded data that conforms to the identifier encoding specifications required by the secondary node.

[0022] An encrypted transmission module is used to encrypt the encoded data and the target data and transmit them to the secondary node for storage.

[0023] Optionally, the next-level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario.

[0024] Optionally, the target data is the product produced by the designated industrial site unit, or the data during the product production process of the designated industrial site unit;

[0025] When the target data is data from the production process of the designated industrial site unit, the encryption transmission module is specifically used to: encrypt and transmit the production data at different time points during the production process of the designated industrial site unit and the encoded data after encoding the production data to the secondary node, in accordance with the principle that the order of data sent to the secondary node is consistent with the order of data collected.

[0026] Optionally, the industrial site unit is at least one production workshop or at least one production line.

[0027] Optionally, the encrypted transmission module is specifically used to: sign the encoded data and the target data using the target private key to obtain a digital signature; send the digital signature to the secondary node so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and store the encoded data and the target data after successful verification.

[0028] According to a fourth aspect of the embodiments of this application, an electronic device is provided, the electronic device comprising: a memory and a processor; the memory being used to store a computer program; the processor being used to execute the above-described identifier resolution method by invoking the computer program.

[0029] According to a fifth aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, wherein the program, when executed by a processor, implements the above-described identifier resolution method.

[0030] The technical solutions provided in this application embodiment may include the following beneficial effects:

[0031] In the technical solution provided in this application, a next-level node is deployed to the enterprise node in the existing identifier resolution system. This next-level node has edge identification capabilities and is used to generate coded data conforming to a unified coding standard for the target data to be encoded generated by the unit in the industrial site according to the preset coding rules. This achieves the unification of identifier coding data in the circulation process. The identification coding and target data transmission process are made secure and reliable by using encrypted transmission. This realizes the edge identifier resolution capability and the sinking of the identifier resolution system in the industrial site, bringing it closer to the data source. Based on the identifier resolution system, the accuracy, reliability and timeliness of industrial site identifiers are guaranteed.

[0032] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this application. Furthermore, no embodiment in this application needs to achieve all the effects described above. Attached Figure Description

[0033] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0034] Figure 1 This is a schematic diagram of the hierarchical deployment model of the existing industrial internet identifier resolution system;

[0035] Figure 2 This application illustrates a schematic flowchart of an identifier resolution method in an exemplary embodiment.

[0036] Figure 3 This is a schematic diagram illustrating the deployment of the next-level node in an industrial internet identifier resolution system, as shown in an exemplary embodiment of this application.

[0037] Figure 4 A schematic diagram of another identifier resolution method is shown in an exemplary embodiment of this application;

[0038] Figure 5 This is a schematic diagram illustrating the structure of an identifier resolution device according to an exemplary embodiment of this application;

[0039] Figure 6 This is a hardware schematic diagram of an electronic device illustrated in an exemplary embodiment of this application. Detailed Implementation

[0040] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0041] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0042] The existing industrial internet identifier resolution system architecture in my country adopts a layered and hierarchical deployment model, consisting of root nodes, national top-level nodes, second-level nodes, enterprise nodes, and recursive nodes. The corresponding deployment methods are as follows: Figure 1 As shown, the lowest-level node in the identifier resolution system, or the final node, is the enterprise node. Identifier encoding is generated by the enterprise node and can be synchronized to second-level nodes and even associated with the top-level node. That is, the next level down from the second-level node is the enterprise node; there are no other levels of nodes below the enterprise nodes in the current identifier resolution system. Second-level nodes are public nodes that provide identifier services to specific or multiple industries. They must connect upwards to the national top-level node and downwards to allocate identifier codes to industrial enterprises and provide identifier registration, identifier resolution, and identifier data services. Enterprise nodes are identifier service nodes within a single enterprise, capable of providing identifier registration, identifier resolution, and identifier data services to specific enterprises. They are the final resolution nodes in the identifier encoding and resolution process. Identifier resolution requests from second-level nodes are resolved by the enterprise nodes according to the encoding rules, and the resolution results are returned to the recursive nodes.

[0043] In the Industrial Internet, users can access servers storing information about machines, materials, parts, and products through identifiers. These identifiers enable intelligent information association, providing crucial tools and support for information sharing and full lifecycle management within the industries served. With the development of the Industrial Internet, upstream and downstream collaboration among enterprises is becoming increasingly close, creating a stronger demand for the use of public identifiers to achieve automatic information association and retrieval. Therefore, there is an urgent need to accelerate the construction of an Industrial Internet identifier resolution system.

[0044] Under the existing industrial internet identifier resolution system, enterprises can use their existing enterprise nodes to generate identifier codes and associate them with secondary nodes and other nodes. However, many enterprises mainly use their own codes. During the circulation of materials, parts, and products, these proprietary codes need to be converted into new identifier codes that conform to the unified identifier coding standard. This reduces work efficiency and makes it difficult to achieve accurate information association. At the same time, due to the large number of nodes involved in the identifier transmission process and insufficient security protection, identifiers are easily tampered with and forged, which seriously affects the reliability of identifier resolution applications. In addition, most enterprise-level nodes are located on the cloud side, which is insufficient for the complex and ever-changing industrial site. This leads to untimely updates of identifier resolution rules, or poor stability and timeliness of identifier codes due to problems such as "slow network and fast cloud".

[0045] To address the aforementioned issues, this application provides an identifier resolution method based on the Industrial Internet identifier resolution system. Specifically, see [link to relevant documentation]. Figure 2 As shown, the method may include:

[0046] S101, determine the next-level node in the specified industrial application scenario; the next-level node is at least one newly added node under the enterprise node already defined in the existing industrial internet identifier resolution system by improving the existing industrial internet identifier resolution system; each node in the next-level node corresponds to at least one set industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained by encoding using the identifier encoding rule conforms to the identifier encoding specification required by the second-level node; the second-level node is the upper-level node defined in the existing industrial internet identifier resolution system as the enterprise node;

[0047] The designated industrial application scenario refers to a scenario such as an enterprise with an enterprise node or an industrial site connected to that enterprise. For example, an air conditioning company has an enterprise node, and the entire interaction scenario between the enterprise node and the industrial site where the air conditioner is manufactured can be used as the designated industrial application scenario. The interaction includes the collection, acquisition, and transmission of information such as process data and product data of the industrial site where the air conditioner is manufactured, as well as the generation and parsing of identification codes.

[0048] In the existing industrial internet identifier resolution system, nodes are only built up to the enterprise node. There are no other level nodes under the enterprise node. The enterprise node is responsible for generating the identifier codes for all products or materials of the entire enterprise. The enterprise node obtains data from the industrial site of the enterprise and processes the data to generate the identifier codes for all products or materials of the entire enterprise.

[0049] This application improves upon the existing Industrial Internet Identifier Resolution System by redeploying a new type of node, the next-level node, under the existing enterprise nodes. This next-level node replaces the existing enterprise nodes for encoding. Specifically, in this application, the next-level node generates the identifier code, while the enterprise node connects to it, receiving the identifier code generated and sent by the next-level node, which is then synchronized to the second-level nodes. This next-level node is located in the industrial field, possesses edge identification capabilities, connects upwards to enterprise nodes for information exchange, and connects downwards to designated industrial field units to obtain data information from each of the next-level nodes connected to the designated industrial field units.

[0050] Each node in this next-level node is positioned facing a designated industrial site unit. By setting up each node on the industrial site side, it can support the access of various types of equipment in the industrial site. For example, a node in this next-level node can be a gateway on the industrial site side, which can exchange information between industrial site data and existing enterprise nodes; or a newly added edge server in the industrial site can be used as a next-level node. At the device access layer, industrial gateway technology is used for protocol conversion and data collection, and the industrial site data is uploaded to the edge server so that the edge server can perform identification encoding.

[0051] The term "set industrial site unit" refers to at least one production workshop or at least one production line of physical or virtual objects such as products, materials, and processes. The set industrial site unit corresponds to a node in the next level node. Multiple set industrial site units may correspond to the same node in the next level node, or each set industrial site unit may correspond to a different node in the next level node. The correspondence between nodes in the next level node and set industrial site units can be set according to the actual situation.

[0052] S102, each node in the next level collects target data to be encoded from its corresponding set industrial field unit, encodes the target data using a pre-set identification encoding rule to generate encoded data that conforms to the identification encoding specification required by the second-level node, encrypts the encoded data and the target data and transmits them to the second-level node for storage.

[0053] The target data to be encoded refers to product or material data information retrieved during the identification and resolution process in the circulation of the product or material. For example, for a packaged food, the target data to be encoded may include the producer's address, ingredient list, production date, quality inspector, etc.

[0054] In terms of object type, the target data to be encoded can be attribute data information of physical objects in the set industrial site unit. The physical object refers to a machine or product with a physical structure, such as automobiles, ships, instrument parts, etc.; or, the target data to be encoded can be attribute data information of virtual objects in the set industrial site unit, such as virtual resources such as product manufacturing processes and algorithms.

[0055] From a production process perspective, the target data to be encoded can be the relevant attribute information of an industrial finished product, or the relevant attribute information of the constituent elements of the finished product during the manufacturing process. For example, a computer includes components such as a motherboard, monitor, optical drive, hard drive, and peripherals. The target data to be encoded includes the attribute information of each of these components and / or the attribute information of the final assembled computer.

[0056] Each node in the next level can obtain the target data to be encoded through wired data communication with its corresponding industrial site unit, such as through a serial port or Ethernet port, or through wireless data communication, such as Bluetooth or Wi-Fi.

[0057] In one embodiment, for each designated industrial site unit, each node in the next-level node establishes communication with the data acquisition device of the corresponding designated industrial site unit. This data acquisition device is used to collect the target data to be encoded for the designated industrial site unit and identify the corresponding entity or virtual object. For example, it collects attribute information such as voltage, color, model, and production date, and identifies that this attribute information belongs to a computer motherboard.

[0058] Each node in the next-level node is pre-configured with the encoding rules required by the corresponding industrial site unit. These pre-set encoding rules conform to the unified identifier encoding standard required by the second-level nodes defined in the Industrial Internet Identifier Resolution System, and are used to encode coded data that conforms to the unified identifier encoding standard, so that the second-level nodes can parse the coded data generated by the next-level nodes according to the encoding rules. Users can define unified coded data formats and rules according to their own needs.

[0059] For example, a secondary node requires the encoded data to include an identifier prefix and an identifier suffix. The identifier prefix is ​​used to uniquely identify the enterprise entity, and the identifier suffix is ​​used to uniquely identify the object to which the target data to be encoded belongs. Users can customize which fields in the identifier suffix are used to uniquely identify the object. The overall rules of the user-defined fields, the identifier suffix, and the identifier prefix can be used as preset encoding rules.

[0060] The encrypted transmission refers to providing a trusted identity authentication technology based on national cryptographic algorithms to ensure the security and reliability of the identifier resolution process. Specifically, the next-level node uses public-private key encryption to verify the encoded data and the target data before transmitting the data to the enterprise node. This allows the enterprise node to upload the data to the secondary node, where it will store the data after secure verification.

[0061] In the above embodiments, compared with the related technologies that concentrate the coding of specified industrial application scenarios such as enterprises at the enterprise node, the existing identifier resolution system is improved to deploy new next-level nodes under the enterprise nodes already built in the system. Each node in the next-level node is set to face the set industrial site unit, and the data is distributed to encode the data in each set industrial site unit. This enables each node in the next-level node to generate codes that conform to the second-level node coding specifications for products or materials in each set industrial site unit according to preset coding rules on the industrial site side. This solves the problems caused by centralized coding at the enterprise node, such as inability to respond to industrial site conditions in a timely manner, untimely updates of identifier coding rules, and poor stability and timeliness of identifier coding.

[0062] Furthermore, compared to existing enterprise nodes, which are mostly located on the cloud and acquire data on all products or materials of the entire enterprise, the nodes in the next-layer nodes described in the above embodiment are located on the industrial site side. They are equivalent to edge nodes, possessing edge identification capabilities and supporting the access of multiple types of equipment in the industrial site. They can collect a wider variety of data resources from the industrial site units targeted by each node, realizing the sinking of the identification resolution system and bringing it closer to the industrial site data source. This solves the problem of poor stability in the application of the identification resolution system by enterprises. At the same time, encryption technology ensures that the data is transparent, reliable, and tamper-proof throughout the process from collection to storage, guaranteeing the accuracy, reliability, and timeliness of industrial site identification based on the identification resolution system.

[0063] In one embodiment, the next-level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario, wherein the edge gateway can support the access of multiple types of devices in the industrial site.

[0064] In this embodiment of the disclosure, by using an edge gateway that connects to at least one designated industrial site unit as the next-level node of the enterprise node, the problem of high application cost and poor stability of enterprises in the process of applying the identifier resolution system can be solved by leveraging edge computing technology and the integration of multiple access methods.

[0065] In some embodiments, the target data is product data produced by the designated industrial site unit, or data generated during the product production process of the designated industrial site unit.

[0066] When the target data is data from the production process of the designated industrial site unit, encrypting the encoded data and the target data and transmitting them to the secondary node may include the following steps:

[0067] Following the principle that the order of data sent to the secondary node is consistent with the order of data collected, the production data at different time points during the production process of the set industrial site unit and the encoded data of the production data are encrypted and transmitted to the secondary node.

[0068] That is, when the designated industrial site unit corresponding to at least one node in the next-level node is used for finished product production, the target data collected is the attribute information of the produced finished product; when the designated industrial site unit corresponding to at least one node in the next-level node is used for producing components or elements or production operation steps of the finished product, the target data collected is the attribute information or operation step information of each component or element in the finished product production process. In one example, based on the above types of the collected target data, product code data and / or product process code data can be generated, and the association between each product code data and the product process code data can be established, that is, through the product code data, the product process code data of the product can be traced.

[0069] When the encoded data and the target data are encrypted and transmitted to the secondary node, the encoded data of the entity or virtual object and the target data associated with the encoded data are uploaded to the secondary node after the corresponding encoded data of the product data and / or production process data of an entity or virtual object have been obtained.

[0070] For data information during the product manufacturing process, the target data corresponding to the collected product process can be maintained with an incrementing operation sequence number according to the preset product manufacturing process sequence. Timestamp synchronization can be added to ensure that the uploaded target data sequence is consistent with the product manufacturing process sequence, and the product manufacturing process sequence is consistent with the sequence of collected product manufacturing process data.

[0071] In this embodiment of the disclosure, product information traceability is achieved by generating corresponding coded data for the collected product data information or product production process data information, and the target data corresponding to the product process maintains an incremental operation sequence number according to the process sequence, so that the uploaded target data order is consistent with the collection order.

[0072] In one embodiment, after the encoded data is generated, a one-to-one correspondence between the encoded data and the identification carrier can be established so that the product's encoded data and the product attribute information associated with the encoded data can be located through the identification carrier.

[0073] The identification carrier is a tag or storage device capable of carrying identification coding resources. It is divided into active identification carriers and passive identification carriers. The active identification carriers include SIM cards, communication modules, UICCs, terminals, etc., while the passive identification carriers include barcodes, QR codes, RFID, etc.

[0074] In some embodiments, encrypting the encoded data and the target data and transmitting them to the secondary node can be achieved by: signing the encoded data and the target data using the target private key to obtain a digital signature; sending the digital signature to the secondary node so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and storing the encoded data and the target data after successful verification.

[0075] In this embodiment, the security of encoded data transmission and storage is guaranteed by using private key signing and public key verification, so that the encoded data cannot be tampered with. This encryption method can be implemented by national cryptographic algorithms such as SM9. The private key can be at least one of the device manufacturer's name, device model and device SN number, or the private key can be a random number.

[0076] This application provides another identifier resolution method based on the Industrial Internet identifier resolution system, which is executed by the next-level node. The next-level node is a layer node with edge identifier resolution and encryption capabilities set up under the existing enterprise nodes of the identifier resolution system before executing this identifier resolution method. Figure 3 As shown, under the existing identifier resolution system's enterprise node, an edge gateway on the industrial site side is set up as the next level node of the enterprise node. It is used to connect the industrial production site and the enterprise node to realize information interaction between the two. The edge gateway can support the access of multiple types of devices in the production site to collect rich target data.

[0077] Based on this edge gateway, an identifier resolution module can be embedded within it. This embedded identifier resolution module can be used to implement the identifier resolution method. Specifically, as... Figure 4 As shown, the identifier resolution method may include the following steps:

[0078] S201, Collect and access target data to be encoded from the set industrial field units;

[0079] The target data to be encoded refers to the attribute information of products, equipment or other virtual resources in the Industrial Internet that need to be assigned identification or identification coding data. The attribute information refers to the basic information that can characterize or describe the product, equipment or other virtual resource, such as production date, color, model, category, material, quality inspector, etc.

[0080] Each designated industrial unit corresponds to one edge gateway. Data acquisition rules for the designated industrial unit can be pre-configured in the edge gateway so that the edge gateway can acquire target data according to the data acquisition rules. Automatic product identification function can also be configured in the edge gateway so that the gateway can confirm the ownership of the acquired target data.

[0081] S202, the target data is encoded using a pre-set identifier encoding rule to generate an identifier encoding that conforms to the identifier encoding specification required by the secondary node;

[0082] The pre-set identification coding rules can be flexibly configured according to the coding rules of the upper-level nodes. For example, according to the unified identification coding standard of the second-level nodes, users can set the fields in the identification used to uniquely identify products or devices. The identification code (same as the coding data) generated according to the identification coding rules is a unique serial number that conforms to the identification coding standard. After the identification code is generated, the identification code can be stored in barcode, QR code, RFID tag, etc.

[0083] In one example, the logical structure of the identifier code required by the secondary node includes a prefix field, a suffix field, and optional fields. The identifier prefix uniquely identifies the enterprise entity, while the identifier suffix uniquely identifies the object requiring the identifier, such as physical resources like materials, machines, and products within the enterprise, as well as virtual resources like algorithms, processes, and models. For example, the identifier prefix may include three fields: country code, industry code, and enterprise code, which can uniquely identify the enterprise entity. For products under the same enterprise, the product identifier code prefix is ​​the same. Users can set the suffix field and optional fields according to product attributes and their own enterprise needs.

[0084] For example, the prefix field sequence corresponding to a certain enterprise is 86.111.10086. The user sets the suffix field to consist of the production date, serial number, and product category code. If the suffix of a certain product of this enterprise is 2023042005A, then the identification code of the product obtained according to this coding rule is 86.111.10086 / 2023042005A.

[0085] By identifying this identifier code, the attribute information of the object represented by the identifier code can be uniquely located. For example, the code in the above example is the code of an air conditioner. By identifying the above code, information such as the brand, color, model, power, production time, and component models of the air conditioner can be viewed.

[0086] S203, the identifier code and the target data are encrypted and transmitted to the enterprise node using a private key signing and public key verification method, so that they can be sent to the secondary node through the enterprise node, and the identifier code and the target data associated with the identifier code are stored after the secondary node verifies the signature.

[0087] Each entity or virtual product object within an enterprise is assigned a unique identifier. This identifier uniquely identifies the product object, and its specific attribute information can be obtained by recognizing the identifier. Therefore, there is a correlation between the identifier and the target data of the product object it represents, allowing the acquisition of the corresponding product's target data through the identifier.

[0088] In one example, during the process of sending the identifier code and the target data associated with that code to the secondary node, the identifier code and the target data can first be hashed to obtain a hash value. This hash value is then encrypted using the product object's private key to obtain the corresponding digital signature value. After encryption, the digital signature value and public key certificate are sent to the enterprise node, which then forwards them to the secondary node. Upon receiving the information, the secondary node verifies the validity of the public key certificate and uses the public key to decrypt and sign the digital signature value. After successful verification, the identifier code and the target data are stored, and there is a unique association between the two.

[0089] like Figure 3 As shown, after the identifier code and the target data associated with the code are stored in the secondary node, there is a communication interface between the industrial internet platform and the identifier resolution system. When an identifier resolution request is received, the platform can call the target data associated with the code stored in the secondary node of the identifier resolution system.

[0090] In the above embodiments, by using the edge gateways in industrial sites as new edge nodes (i.e., next-level nodes) under the existing enterprise nodes of the identifier resolution system, and embedding an identifier resolution module within the edge gateways, edge computing technology and multi-access methods for field devices are employed to generate coded data conforming to the identifier encoding specifications of the second-level nodes for products in the designated industrial site units corresponding to each edge gateway. Furthermore, the embedded identifier resolution module allows users to flexibly configure it according to the encoding rules of the upper-level nodes, which is more conducive to the promotion of the identifier resolution system and reduces the difficulty and cost for users. The secure and reliable transmission and storage of identifier encoding data and associated target data are achieved through encryption methods using private key signatures and public key verification. This identifier resolution method realizes the sinking of the identifier resolution system, bringing it closer to the data source in the industrial site, addressing the complex and ever-changing situations in industrial sites, solving the problem of poor stability in the application of identifier resolution systems by enterprises, and ensuring the accuracy, reliability, and timeliness of industrial site identifiers based on the identifier resolution system.

[0091] Corresponding to the embodiments of the aforementioned identifier resolution method, see [link to relevant documentation]. Figure 5 As shown, this application also provides an embodiment of an identifier resolution device, wherein the identifier resolution device is located at the next-level node, which is a node determined based on the Industrial Internet Identifier Resolution System and is the next-level node of an enterprise node in the Industrial Internet Identifier Resolution System in a specified industrial application scenario; the next-level node of the enterprise node in the Industrial Internet Identifier Resolution System is a second-level node; the next-level node includes at least one node, and each node corresponds to at least one designated industrial site unit; the device may include:

[0092] Data acquisition module 501 is used to collect target data to be encoded from the corresponding set industrial field units through each node in the next layer node;

[0093] The encoding data generation module 502 is used to encode the target data using a pre-set identifier encoding rule to generate encoded data that conforms to the identifier encoding specification required by the secondary node.

[0094] The encrypted transmission module 503 is used to encrypt the encoded data and the target data and transmit them to the secondary node for storage.

[0095] In some embodiments, the next-level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario.

[0096] In some embodiments, the target data is the product produced by the designated industrial site unit, or data generated during the product production process of the designated industrial site unit.

[0097] When the target data is data from the production process of the designated industrial site unit, the encryption transmission module is specifically used to: encrypt and transmit the production data at different time points during the production process of the designated industrial site unit and the encoded data after encoding the production data to the secondary node, in accordance with the principle that the order of data sent to the secondary node is consistent with the order of data collected.

[0098] In some embodiments, the industrial site unit is at least one production workshop or at least one production line.

[0099] In some embodiments, the encrypted transmission module is specifically used to: sign the encoded data and the target data using the target private key to obtain a digital signature; send the digital signature to the secondary node so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and store the encoded data and the target data after successful verification.

[0100] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0101] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0102] This application embodiment also provides an identifier resolution system based on the Industrial Internet Identifier Resolution System. The system includes at least enterprise nodes already defined in the existing Industrial Internet Identifier Resolution System, and upper-level nodes (second-level nodes) of these enterprise nodes. The system also includes lower-level nodes determined in a specified industrial application scenario. These lower-level nodes are at least one newly added node under the enterprise nodes already defined in the existing Industrial Internet Identifier Resolution System through improvements to the existing system. Each lower-level node corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using this rule conforms to the identifier encoding specification required by the second-level node.

[0103] The next-level node is used to collect target data to be encoded from its corresponding set industrial field units, encode the target data using a pre-set identification encoding rule to generate encoded data that conforms to the identification encoding specification required by the second-level node, encrypt the encoded data and the target data and transmit them to the second-level node for storage.

[0104] This application also provides an electronic device, the structural schematic diagram of which is shown below. Figure 6 As shown, the electronic device 600 includes at least one processor 601, a memory 602, and a bus 603. At least one processor 601 is electrically connected to the memory 602. The memory 602 is configured to store at least one computer-executable instruction, and the processor 601 is configured to execute the at least one computer-executable instruction to perform the steps of any identifier resolution method provided in any embodiment or optional implementation of this application.

[0105] Furthermore, the processor 601 can be an FPGA (Field-Programmable Gate Array) or other devices with logic processing capabilities, such as an MCU (Microcontroller Unit) or a CPU (Central Processing Unit).

[0106] In the above embodiments, by deploying a next-level node to the enterprise nodes in the existing identifier resolution system, this next-level node has edge identification capabilities. Using this next-level node, the target data to be encoded generated by the unit in the industrial site is generated according to the preset encoding rules to generate coded data that conforms to the unified encoding standard. This realizes the unification of identifier encoding data in the circulation process. The identification encoding and target data transmission process are made secure and reliable by using encrypted transmission. This realizes the edge identifier resolution capability and the sinking of the identifier resolution system in the industrial site, bringing it closer to the data source. Based on the identifier resolution system, the accuracy, reliability and timeliness of industrial site identifiers are guaranteed.

[0107] This application also provides another readable storage medium storing a computer program that, when executed by a processor, implements the steps of any identifier resolution method provided in any embodiment or optional implementation of this application.

[0108] The readable storage media provided in this application include, but are not limited to, any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic cards, or optical cards. In other words, the readable storage media includes any medium by which a device (e.g., a computer) stores or transmits information in a readable form.

[0109] In the above embodiments, by deploying a next-level node with edge identification capabilities to the enterprise nodes in the existing identifier resolution system, and using this next-level node to generate coded data conforming to a unified coding standard for the target data to be encoded generated by the unit in the industrial site according to the preset coding rules, the uniformity of the identifier coding data in the circulation process is realized. The identification coding and the transmission of the target data are made secure and reliable by using encrypted transmission. This realizes the sinking of the edge identifier resolution capability and the identifier resolution system in the industrial site, bringing it closer to the data source, and ensuring the accuracy, reliability and timeliness of industrial site identifiers on the basis of the identifier resolution system.

[0110] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0111] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of protection claimed, but rather are primarily used to describe the features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in the various embodiments or in any suitable sub-combination.

[0112] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for resolving identifiers, characterized in that, The method includes: In a specified industrial application scenario, a next-level node is determined. This next-level node is at least one newly added node under the enterprise node already defined in the existing Industrial Internet Identifier Resolution System, through improvements to the existing system. The enterprise node is used to connect to the next-level node. Each node in the next-level node corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using this rule conforms to the identifier encoding specification required by the second-level node. The second-level node is the next-level node defined in the existing Industrial Internet Identifier Resolution System as the parent node of the enterprise node. Each node in the next level collects target data to be encoded from its corresponding designated industrial site unit, encodes the target data using pre-set identification and encoding rules to generate encoded data that conforms to the identification and encoding specifications required by the second-level node, encrypts the encoded data and the target data and transmits them to the enterprise node, which then synchronizes them to the storage of the second-level node.

2. The method according to claim 1, characterized in that, The next level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario.

3. The method according to claim 1, characterized in that, The target data refers to the products produced by the designated industrial site unit, or the data generated during the production process of the products by the designated industrial site unit. When the target data is data from the production process of the designated industrial site unit, the step of encrypting the coded data and the target data and transmitting them to the secondary node includes: Following the principle that the order of data sent to the secondary node is consistent with the order of data collected, the production data at different time points during the production process of the industrial site unit and the encoded data of the production data are encrypted and transmitted to the secondary node.

4. The method according to any one of claims 1 to 3, characterized in that, The industrial site unit is defined as at least one production workshop or at least one production line.

5. The method according to any one of claims 1 to 3, characterized in that, The step of encrypting the encoded data and the target data and transmitting them to the secondary node includes: The encoded data and the target data are signed using the target private key to obtain a digital signature; The digital signature is sent to the secondary node, so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and store the encoded data and the target data after the verification is successful.

6. An identifier resolution system, characterized in that, The system includes at least enterprise nodes already defined in the existing Industrial Internet Identifier Resolution System, and second-level nodes, which are the upper-level nodes of the enterprise nodes. The system also includes lower-level nodes determined in a specified industrial application scenario. These lower-level nodes are at least one new node added under the enterprise nodes already defined in the existing Industrial Internet Identifier Resolution System through improvements to the existing system. The enterprise nodes are used to connect to the lower-level nodes. Each node in the lower-level nodes corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using this rule conforms to the identifier encoding specifications required by the second-level nodes. The next-level node is used to collect target data to be encoded from its corresponding set industrial field units, encode the target data using pre-set identification encoding rules to generate encoded data that conforms to the identification encoding specifications required by the second-level node, encrypt the encoded data and the target data and transmit them to the enterprise node, which then synchronizes them to the second-level node for storage.

7. An identifier resolution device, characterized in that, This is applied to the next-level node, which is a node determined in a specific industrial application scenario. The next-level node is at least one newly added node under the enterprise nodes already defined in the existing Industrial Internet Identifier Resolution System, through improvements to the existing system. The enterprise node is used to connect to the next-level node. Each node in the next-level node corresponds to at least one designated industrial site unit, and each node is configured with a corresponding identifier encoding rule so that the encoded data obtained using this rule conforms to the identifier encoding specifications required by the second-level node. The secondary node is the next-level node defined in the existing industrial internet identifier resolution system as the enterprise node; the device includes: The data acquisition module is used to collect target data to be encoded from the corresponding set industrial field units through each node in the next level node; The encoded data generation module is used to encode the target data using pre-set identifier encoding rules to generate encoded data that conforms to the identifier encoding specifications required by the secondary node. An encrypted transmission module is used to encrypt the encoded data and the target data and transmit them to the enterprise node, which then synchronizes them to the secondary node for storage.

8. The apparatus according to claim 7, characterized in that, The next-level node is an edge gateway that connects to at least one designated industrial site unit in the specified industrial application scenario; or... The target data refers to the products produced by the designated industrial site unit, or the data generated during the production process of the products by the designated industrial site unit. When the target data is data from the production process of the designated industrial site unit, the encrypted transmission module is specifically used to: encrypt and transmit to the secondary node the production data at different time points during the production process of the designated industrial site unit and the encoded data of the production data, following the principle that the order of data sent to the secondary node is consistent with the order of data collected; or... The industrial site unit is defined as at least one production workshop or at least one production line; or... The encrypted transmission module is specifically used to: sign the encoded data and the target data using the target private key to obtain a digital signature; send the digital signature to the secondary node so that the secondary node can verify the digital signature using the target public key corresponding to the target private key, and store the encoded data and the target data after the verification is successful.

9. An electronic device, characterized in that, include: Memory, processor; The memory is used to store computer programs; The processor is configured to invoke the computer program to implement the identifier resolution method as described in any one of claims 1-5.

10. A readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the identifier resolution method as described in any one of claims 1-5.

Images