Industrial Internet of Things platform management method and system based on digital twin drive

Abstract

The invention discloses an industrial Internet of Things platform management method and system based on digital twin drive, and relates to the technical field of new-generation communication technology and industrial digital platform, and the method comprises the steps: obtaining the basic information and operation information of all equipment in a factory; defining a hierarchical industrial Internet of Things element component; carrying out digital coding on the elements, and carrying out digital mapping; carrying out association matching on different elements, and carrying out scene-based configuration; global driving information is added, and global information interaction and bidirectional digital twinning are carried out. By designing hierarchical and modular element components and an identification coding technology, mapping of various entities in a digital space in an industrial Internet of Things scene is realized, a new scene is quickly adapted, the digital twin construction cost of an enterprise is reduced, and the informatization and intelligence levels of links such as design, operation and management of the industrial Internet of Things are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of new generation communication technology and industrial digital platform, and specifically to an industrial Internet of Things platform management method and system driven by digital twins. Background Art

[0002] In response to the diversified business needs of the industrial Internet, especially digital factories, and the construction requirements of new information infrastructure for large-scale human-machine-object interconnection, digital twin technology can be used to empower the intelligent management and control, collaborative operation and maintenance decision-making capabilities of the industrial Internet platform. Industrial production mainly focuses on the efficiency and reliability of the five factors of "people, machines, materials, methods, and environment" in the production, manufacturing and circulation links, and the communication system aims to form a channel for information exchange. How to organically integrate industrial production and new communication technologies to realize new digital twin technologies that are real-time dynamic, flexible, and highly reusable in scenarios such as digital factories.

[0003] The present invention aims to break the traditional digital twin implementation path: select a fixed twin scene - build a static 3D model - add dynamic information. Explore a new element-based digital twin implementation path: build a dynamic element component that includes a communication interface and internal information processing capabilities - perform scenario-based matching and assembly according to different industrial design, production, manufacturing and circulation links - add model rendering and global drive information to achieve global interaction.

[0004] The present invention proposes a new element-based digital twin implementation path. First, a dynamic element component including a communication interface and internal information processing capabilities is established. Then, scenario-based matching and assembly are performed according to different industrial design, production, manufacturing and circulation links. Finally, global interaction and virtual-reality mapping are achieved by adding global driving information. Summary of the invention

[0005] In view of the above existing problems, the present invention mainly focuses on the smart factory scenario, and forms the industrial Internet of Things referred to in the present invention by integrating the factory operating environment and the Internet of Things technology. The digital twin mapping and matching method proposed in the present invention refers to the specific digital twin algorithm and system design problems under the industrial Internet of Things.

[0006] In order to solve the above technical problems, an industrial Internet of Things platform management method based on digital twin drive is proposed, including:

[0007] Obtain basic information and operation information of all equipment in the factory; define hierarchical industrial Internet of Things element components; digitally encode elements and perform digital mapping; associate and match different elements and perform scenario-based configuration; add global drive information, conduct global information interaction and two-way digital twins.

[0008] As a preferred solution of the industrial Internet of Things platform management method driven by digital twins described in the present invention, the hierarchical industrial Internet of Things element components include factory facility definition, communication equipment definition, network definition, and scenario definition in a hierarchical definition manner.

[0009] The factory facility definition includes assembly lines, robotic arms, lathes, AGV carts, shelves, testing instruments, and other custom facility types.

[0010] The communication device definition includes sensors, mobile terminals, base stations, gateways, edge servers, cloud servers, and other custom device types.

[0011] The network definitions include Bluetooth, Lora, ZigBee, WiFi, StarFlash, NBIoT, 5G, and other custom network types.

[0012] The scene definitions include production and manufacturing workshops, quality inspection workshops, warehousing and logistics workshops, energy stations, offices, and other custom scene types.

[0013] The external interfaces of the element components are defined in a software-defined manner, including the Init port, Control port, Display port, and Feedback port. The software defines the interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters.

[0014] Connect to another facility component through n E ports, with bidirectional data flow. Connect to a communication device component through n D ports, with bidirectional data flow. Connect to a scene component through n S ports, with bidirectional data flow.

[0015] As a preferred solution of the industrial Internet of Things platform management method driven by digital twins described in the present invention, the digital code includes using suffix coding to uniquely identify the element components, and the suffix coding is expressed as: "element hierarchy code-element entity type identification-unique serial number".

[0016] The element hierarchy code indicates the hierarchy to which the element entity belongs, including the factory facility layer E, the communication equipment layer D, the network layer N, and the scene layer S.

[0017] The element entity type identifier indicates the specific type of the entity, mode M, digital heat exchanger DH, gateway G, heat exchanger HT, thermal sensor TS.

[0018] The unique serial number distinguishes different entities in the same level and type, model 1-001, digital heat exchanger 5-005, Lora network 1-001, heat exchanger 3-003, thermal sensor 1-002.

[0019] Add attribute information to the element components to map from the physical world to the digital world. Each attribute information is represented by a six-tuple, namely { <index> , <name> , <data>, <permission> , <timestamp> , <remark>}, an element contains multiple attribute information, through <index>to index.

[0020] in, <index>Is a 3-digit decimal integer that serves as the index of the entry. <name>Indicates the name of the attribute, <data>The first 4 bytes of the current data specify the length of the data, followed by the actual bytecode of the data. permission> is the permission mask including read-only, modify, delete, and invalid permission settings. <timestamp>To record the time when the data was last updated, in microseconds. <remark>Reserved for comments. The default value is null.

[0021] As a preferred solution of the industrial Internet of Things platform management method driven by digital twins described in the present invention, the association matching includes establishing initialization associations for different element components, superimposing prefix codes, and performing dynamic matching associations between element components based on the dynamic scope of the elements.

[0022] The initialization association includes determining the initialization association relationship of the element components in the factory facility layer E, the communication equipment layer D, the network layer N, and the scene layer S, superimposing the code before the suffix code, and representing the association relationship in the form of a prefix code. Based on the prefix code, each element component constructs and maintains an association rule table. In any scenario, the initialization association of the element component is:

[0023] Establish the association between the E-layer factory facilities and the D-layer communication equipment. Based on the prefix code of the association rule table, initialize the association logic in a software-defined manner, create a Link_ED type object named mylink, and initialize the connection relationship to true.

[0024]

[0025] Among them, preCode indicates the prefix code, and flowDr indicates the data flow direction.

[0026] Establish the association between D-layer communication equipment and N-layer network mode:

[0027]

[0028] Establish associations between the components of the E layer and the S layer, the D layer and the S layer, and the N layer and the S layer respectively:

[0029]

[0030] The dynamic matching association includes that the relationship between elements is constantly changing, and the dynamic association rules based on the element spatiotemporal scope matching algorithm are used to dynamically match the relationship between elements, and update the association rule table. For any element component M, its dynamic scope D is defined. M for:

[0031] D M ={<x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M ,

[0032] <list-necessary> M ,

[0033] <list-rejective> M }

[0034] Among them, <x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M Indicates the spatiotemporal scope of an element, abbreviated as <D-ST> M <list-necessary> M Indicates a required list, that is, an element that is prioritized for association. <list-rejective> M Represents a deny list, which are features that are never associated.

[0035] For two element components M and N, a matching calculation is performed to calculate whether element M falls within the scope of element N:

[0036]

[0037] When the operation result is R ＜M,N＞ When =1, it means that element M falls within the scope of element N, otherwise, element M does not fall within the scope of element N.

[0038] Then calculate whether element N falls within the scope of element M:

[0039]

[0040] When R ＜M,N＞ =1 and R ＜N,M＞ =1, then element M and element N are associated, otherwise they are not associated. If there is an association before this calculation, the association is cancelled and the association rule tables of the two are updated at the same time.

[0041] As a preferred solution of the industrial Internet of Things platform management method driven by digital twins described in the present invention, the association matching also includes an agreed method for establishing a message transmission channel between element components in the digital space.

[0042] When element M and element N are associated, a two-way data flow interaction of message transmission between the physical space and the digital space is performed. The message transmission methods include method 1, method 2 and method 3:

[0043] The method 1 is active periodic uploading, where element M periodically transmits messages to element N, and the message carrier is in the form of a four-tuple, defined as {<prefix code>, <name> , <data>, <timestamp>},in, <name> 、 <data>、 <timestamp>Obtained from the local attribute information list of feature N respectively.

[0044] The method 2 is the query-aggregation method. When element M needs to aggregate messages from multiple elements N, P, and Q, element M broadcasts a "query-aggregation" request to multiple elements in the form of a four-tuple. The elements that receive the request send information extracted from the local attribute information list to M and transmit it in the form of a four-tuple.

[0045] The method 3 is the query-measurement method. Element M hopes to obtain the result of measurement calculation from element N. Element M first sends the data involved in the calculation and the variables expected to be measured to N in the form of a quadruple. After element N obtains the data, it completes the calculation in combination with local data and passes the calculation result to M in the form of a quadruple.

[0046] As a preferred solution of the industrial Internet of Things platform management method based on digital twin drive described in the present invention, the global information interaction includes establishing an interactive path from the platform hub to each element component in the digital space, and defining four virtual buses, namely, Init bus, Control bus, Display bus, and Feedback bus:

[0047] The Init bus includes the platform hub writing to the Init port of the element component through the Init bus, configuring the initialization parameters of different element components, creating an initialization bus type object named myInitBus, and postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Init bus:

[0048] InitBus myInitBus=new InitBus(postCode1,...,postCodeN)

[0049] The Control bus includes the platform hub performing a write operation on the Control port of the element component through the Control bus, modifying the attribute information list of the element component, and creating a control bus type object named myContBus. postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Control bus:

[0050] ContBus myContBus=new ContBus(postCode1,...,postCodeN)

[0051] The Display bus includes the element components uploading information that needs to be visualized from the Display port to the platform hub through the Display bus. The platform hub calls the digital twin visualization engine to create a "display bus" type object named myDispBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Display bus:

[0052] DispBus myDispBus=new DispBus(postCode1,...,postCodeN)

[0053] The Feedback bus includes the information that the element components upload from the Feedback port to the platform hub through the Feedback bus, which does not need to be visualized but needs to be aggregated and analyzed by the platform hub. The platform hub can call the numerical calculation engine to create a "feedback bus" type object named myFeedBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Feedback bus:

[0054] FeedBus myFeedBus=new FeedBus(postCode1,...,postCodeN)

[0055] The platform hub and all components perform message transmission. The platform hub or component initiates a message transmission task Task and sends the Task to one of the four queues. The four queues correspond to four buses respectively. When the Task is at the head of the current queue, it monitors whether the current bus is occupied. When the bus status is "busy", it continues to wait. When the bus status is "free", the Task monopolizes the bus and executes one of the following message transmission processes:

[0056] myInitBus.Transmitter(postCode,Task)

[0057] myContBus.Transmitter(postCode,Task)

[0058] myDispBus.Receiver(postCode,Task)

[0059] myFeedBus.Receiver(postCode,Task)

[0060] Among them, Task is a structure containing multiple parameter names and values, Transmitter(·) means sending messages from the platform hub, and Receiver(·) means receiving messages from the platform hub.

[0061] As a preferred solution of the industrial Internet of Things platform management method driven by digital twins described in the present invention, the bidirectional digital twin includes establishing a bidirectional interactive path from the platform hub to each element entity in the physical space, performing global bidirectional digital twins, and defining a bus structure. Then, the platform hub and the element components communicate and establish an interactive path:

[0062] Industrial facilities at the facility layer use the communication equipment bound to them to communicate with the platform through standard wired and wireless communication protocols. When the industrial facilities are not bound to any communication equipment, the platform only performs static modeling of the facilities and does not consider interactive operations.

[0063] The communication device layer platform communicates with the communication device through standard wired or wireless communication protocols.

[0064] The network layer communicates with the gateway or network management node through standard wired or wireless communication protocols.

[0065] The scene layer monitors the scene through cameras, and the scene changes captured by the cameras will cause changes in the scene elements in the digital space.

[0066] When the state of an element entity in the physical space changes, the state change information is represented as state real (postCode,t+1), the original state is represented by state real (postCode,t), where t represents the timestamp.

[0067] The state (postCode, t+1) is transmitted to the platform hub through the standard communication protocol.

[0068] The platform hub then drives the corresponding element component status changes through the corresponding virtual bus, namely:

[0069] state cyber (postCode,t+1)=myContBus.Transmitter(postCode,Task(state real ))

[0070] Among them, state cyber Indicates the state of the feature component, Task(state real ) represents a message passing task triggered by a feature entity state change.

[0071] When the state of any element component changes in the virtual digital space, the state change is represented by state cyber (postCode,t+1), the original state is represented by state cyber (postCode,t).

[0072] In the system, the state is transmitted through the Feedback port cyber (postCode, t+1) is fed back to the platform hub, that is:

[0073]

[0074] in, Indicates the status of the element component received by the platform hub, Task(state cyber ) represents a message passing task triggered by a state change of a feature component.

[0075] Based on standard communication protocols, the platform hub will Sent to the corresponding feature entity, the feature entity changes its state to state according to its own conditions real (postCode, t+1), to control the real with the virtual. The platform hub drives the physical entity to change its state through standard wired or wireless communication protocols.

[0076] Another object of the present invention is to provide an industrial Internet of Things platform management system driven by digital twins. The present invention uses digital twin technology and industrial Internet of Things platform to realize the intelligence, efficiency and safety of factory production processes, thereby enhancing the competitiveness and sustainable development capabilities of enterprises.

[0077] As a preferred solution of the industrial Internet of Things platform management system driven by digital twins described in the present invention, it is characterized by including a device management module, a scene management module, and a data control module.

[0078] The equipment management module is responsible for acquiring, storing and managing the basic information and operation information of all equipment in the factory, and performing association and dynamic matching between equipment.

[0079] The scenario management module is responsible for defining and managing industrial scenarios, including production and manufacturing workshops and quality inspection workshops, to ensure that equipment and operations can be coordinated in appropriate scenarios.

[0080] The data control module provides a channel for global information interaction and two-way control to ensure the real-time and accuracy of the digital twin system.

[0081] A computer device includes a memory and a processor, wherein the memory stores a computer program, and is characterized in that when the processor executes the computer program, the steps of the industrial Internet of Things platform management method based on digital twin drive are implemented.

[0082] A computer-readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the steps of the industrial Internet of Things platform management method based on digital twin drive are implemented.

[0083] Beneficial effects of the invention: The invention realizes improved production efficiency, reduced maintenance costs, enhanced product quality, improved safety, optimized resource utilization, strengthened decision support, improved automation level, enhanced system flexibility and promoted information sharing through real-time data collection, digital twin model construction and active monitoring feedback, thereby comprehensively improving the operational efficiency and market competitiveness of the enterprise.

[0084] By designing hierarchical and modular element components and identification coding technologies, we can achieve the mapping of various entities in the digital space under the Industrial Internet of Things scenarios, quickly adapt to new scenarios, reduce the cost of enterprise digital twin construction, and improve the level of informatization and intelligence in the design, operation, management and other aspects of the Industrial Internet of Things. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0086] Figure 1 An overall flow chart of an industrial Internet of Things platform management method driven by digital twins provided for one embodiment of the present invention.

[0087] Figure 2 A schematic diagram of the association and connection of element components in a certain scenario of an industrial Internet of Things platform management method driven by digital twins provided by an embodiment of the present invention.

[0088] Figure 3 A system module diagram of an industrial Internet of Things platform management system driven by digital twins provided for one embodiment of the present invention. DETAILED DESCRIPTION

[0089] In order to make the above-mentioned purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are described in detail below in conjunction with the drawings of the specification. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary persons in the art without creative work should fall within the scope of protection of the present invention.

[0090] In the following description, many specific details are set forth to facilitate a full understanding of the present invention, but the present invention may also be implemented in other ways different from those described herein, and those skilled in the art may make similar generalizations without violating the connotation of the present invention. Therefore, the present invention is not limited to the specific embodiments disclosed below.

[0091] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The term "in one embodiment" that appears in different places in this specification does not necessarily refer to the same embodiment, nor is it an embodiment that is mutually exclusive with other embodiments, either individually or selectively.

[0092] The present invention is described in detail with reference to schematic diagrams. When describing the embodiments of the present invention, for the sake of convenience, the cross-sectional diagrams showing the device structure will not be partially enlarged according to the general scale, and the schematic diagrams are only examples, which should not limit the scope of protection of the present invention. In addition, in actual production, the three-dimensional dimensions of length, width and depth should be included.

[0093] Meanwhile, in the description of the present invention, it should be noted that the directions or positional relationships indicated by the terms "upper, lower, inner and outer" are based on the directions or positional relationships shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific direction, be constructed and operated in a specific direction, and therefore cannot be understood as limiting the present invention. In addition, the terms "first, second or third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance.

[0094] In the present invention, unless otherwise specified and limited, the terms "install, connect, connect" should be understood in a broad sense, for example: it can be a fixed connection, a detachable connection or an integral connection. It can also be a mechanical connection, an electrical connection or a direct connection, or it can be an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0095] Example 1, reference Figure 1-Figure 2 , which is the first embodiment of the present invention, and provides an industrial Internet of Things platform management method based on digital twin drive, including:

[0096] S1: Obtain basic information and operation information of all equipment in the factory.

[0097] S2: Define hierarchical industrial IoT elements and components.

[0098] Furthermore, a hierarchical definition approach is adopted including factory facility definition, communication equipment definition, network definition, and scenario definition.

[0099] The factory facility definition includes assembly lines, robotic arms, lathes, AGV carts, shelves, testing instruments, and other custom facility types.

[0100] The external interfaces of the element components are defined in a software-defined manner, including the Init port, Control port, Display port, and Feedback port. The software defines the interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters.

[0101] Connect to another facility component through n E ports, with bidirectional data flow. Connect to a communication device component through n D ports, with bidirectional data flow. Connect to a scene component through n S ports, with bidirectional data flow.

[0102] The communication device definition includes sensors, mobile terminals, base stations, gateways, edge servers, cloud servers, and other custom device types.

[0103] The external interface of the element component is defined in a software-defined manner. The software defines the interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters.

[0104] The basic external interfaces of the communication equipment element components include Init port, Control port, Display port, and Feedback port: the definitions of these ports are the same as those of the factory facility element components.

[0105] Connect to a facility-type component through n E ports, with bidirectional data flow; connect to another communication equipment-type component through n D ports, with bidirectional data flow; connect to a network-type component through n N ports, with bidirectional data flow; connect to a scene-type component through n S ports, with bidirectional data flow.

[0106] The network definitions include Bluetooth, Lora, ZigBee, WiFi, StarFlash, NBIoT, 5G, and other custom network types.

[0107] The external interfaces of the element components are defined in a software-defined manner, including the Init port, Control port, Display port, and Feedback port. The software defines the interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters.

[0108] Connect to another facility component through n E ports, with bidirectional data flow. Connect to a communication device component through n D ports, with bidirectional data flow. Connect to a scene component through n S ports, with bidirectional data flow.

[0109] The scene definitions include production and manufacturing workshops, quality inspection workshops, warehousing and logistics workshops, energy stations, offices, and other custom scene types.

[0110] The external interfaces of the element components are defined in a software-defined manner, including the Init port, Control port, Display port, and Feedback port. The software defines the interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters.

[0111] Connect to another facility component through n E ports, with bidirectional data flow. Connect to a communication device component through n D ports, with bidirectional data flow. Connect to a scene component through n S ports, with bidirectional data flow.

[0112] S3: Digitally encode the elements and perform digital mapping.

[0113] Furthermore, the element component is uniquely identified by using a suffix code, which is represented by: "element level code-element entity type identifier-unique serial number". The following table is an example of suffix coding:

[0114] Table 1 Example of element suffix coding

[0115] Hierarchy Prefix Entity Type Identifier unique serial number Coding Example S M 001 OM-001(Mode 1) E DH 005 E-DH-001 (Digital Heat Exchanger 5) N LR 001 N-LR-001(Lora network 1) E HT 003 E-HT-001(Heat exchanger 3) D TS 002 D-TS-001 (Thermal sensor 2)

[0116] The element hierarchy code indicates the hierarchy to which the element entity belongs, including the factory facility layer E, the communication equipment layer D, the network layer N, and the scene layer S.

[0117] The element entity type identifier indicates the specific type of the entity, mode M, digital heat exchanger DH, gateway G, heat exchanger HT, thermal sensor TS.

[0118] The unique serial number distinguishes different entities in the same level and type, model 1-001, digital heat exchanger 5-005, Lora network 1-001, heat exchanger 3-003, thermal sensor 1-002.

[0119] Add attribute information to the element components to map from the physical world to the digital world. Each attribute information is represented by a six-tuple, namely { <index> , <name> , <data>, <permission> , <timestamp> , <remark>}, an element contains multiple attribute information, through <index>to index.

[0120] in, <index>Is a 3-digit decimal integer that serves as the index of the entry. <name>Indicates the name of the attribute, <data>The first 4 bytes of the current data specify the length of the data, followed by the actual bytecode of the data. permission> is the permission mask including read-only, modify, delete, and invalid permission settings. <timestamp>To record the time when the data was last updated, in microseconds. <remark>Reserved for comments. The default value is null.

[0121] S4: Associate and match different elements and perform scenario-based configuration.

[0122] It should be noted that initialization associations are established for different element components, prefix codes are superimposed, and dynamic matching associations are performed between element components based on the dynamic scope of the elements.

[0123] The initialization association includes determining the initialization association relationship of the element components in the factory facility layer E, communication equipment layer D, network layer N, and scene layer S based on prior knowledge such as construction drawings, user manuals, knowledge graphs, or building information management systems (BIM), superimposing the code before the suffix code, and representing the association relationship in the form of a prefix code.

[0124] For some static elements, their association relationship does not change from beginning to end. For example, a robot arm (E-MA-025) is bound to a sensor (D-TS-012). The association relationship can be represented in the form of a prefix code (preCode) by superimposing the code before the suffix code.

[0125] For example, in the above relationship, for the sensor, the prefix representation is E-MA-025 / D-TS-012; for the robot arm, the prefix code representation is D-TS-012 / E-MA-025.

[0126] Based on the prefix code, each element component builds and maintains an association rule table. In any scenario, the initial association of the element component is:

[0127] Establish the association between the E-layer factory facilities and the D-layer communication equipment. Based on the prefix code of the association rule table, initialize the association logic in a software-defined manner, create a Link_ED type object named mylink, and initialize the connection relationship to true.

[0128]

[0129] Among them, preCode indicates the prefix code, and flowDr indicates the data flow direction.

[0130] Establish the association between D-layer communication equipment and N-layer network mode:

[0131]

[0132] Establish associations between the components of the E layer and the S layer, the D layer and the S layer, and the N layer and the S layer respectively:

[0133]

[0134] The dynamic matching association includes that the relationship between elements is constantly changing, and the dynamic association rules based on the element spatiotemporal scope matching algorithm are used to dynamically match the relationship between elements, and update the association rule table. For any element component M, its dynamic scope D is defined. M for:

[0135] D M ={<x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M ,

[0136] <list-necessary> M ,

[0137] <list-rejective> M }

[0138] Among them, <x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M Indicates the spatiotemporal scope of an element, abbreviated as <D-ST> M <list-necessary> M Indicates a required list, that is, an element that is prioritized for association. <list-rejective> M Represents a deny list, which are features that are never associated.

[0139] For two element components M and N, a matching calculation is performed to calculate whether element M falls within the scope of element N:

[0140]

[0141] When the operation result is R ＜M,N＞ When =1, it means that element M falls within the scope of element N, otherwise, element M does not fall within the scope of element N.

[0142] Then calculate whether element N falls within the scope of element M:

[0143]

[0144] When R ＜M,N＞ =1 and R ＜N,M＞ =1, then element M and element N are associated, otherwise they are not associated. If there is an association before this calculation, the association is cancelled and the association rule tables of the two are updated at the same time.

[0145] It should also be explained how to establish agreed ways of communicating messages between components in the digital space.

[0146] When element M and element N are associated, a two-way data flow interaction of message transmission between the physical space and the digital space is performed. The message transmission methods include method 1, method 2 and method 3:

[0147] The method 1 is active periodic uploading, where element M periodically transmits messages to element N, and the message carrier is in the form of a four-tuple, defined as {<prefix code>, <name> , <data>, <timestamp>},in, <name> 、 <data>、 <timestamp>Obtained from the local attribute information list of feature N respectively.

[0148] The method 2 is the query-aggregation method. When element M needs to aggregate messages from multiple elements N, P, and Q, element M broadcasts a "query-aggregation" request to multiple elements in the form of a four-tuple. The elements that receive the request send information extracted from the local attribute information list to M and transmit it in the form of a four-tuple.

[0149] The method 3 is the query-measurement method. Element M hopes to obtain the result of measurement calculation from element N. Element M first sends the data involved in the calculation and the variables expected to be measured to N in the form of a quadruple. After element N obtains the data, it completes the calculation in combination with local data and passes the calculation result to M in the form of a quadruple.

[0150] S5: Add global driving information to conduct global information interaction and two-way digital twins.

[0151] Furthermore, in the digital space, an interactive channel is established from the platform hub to each element component, and four virtual buses are defined, namely Init bus, Control bus, Display bus, and Feedback bus:

[0152] The Init bus includes the platform hub writing to the Init port of the element component through the Init bus, configuring the initialization parameters of different element components, creating an initialization bus type object named myInitBus, and postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Init bus:

[0153] InitBus myInitBus=new InitBus(postCode1,...,postCodeN)

[0154] The Control bus includes the platform hub performing a write operation on the Control port of the element component through the Control bus, modifying the attribute information list of the element component, and creating a control bus type object named myContBus. postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Control bus:

[0155] ContBus myContBus=new ContBus(postCode1,...,postCodeN)

[0156] The Display bus includes the element components uploading information that needs to be visualized from the Display port to the platform hub through the Display bus. The platform hub calls the digital twin visualization engine to create a "display bus" type object named myDispBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Display bus:

[0157] DispBus myDispBus=new DispBus(postCode1,...,postCodeN)

[0158] The Feedback bus includes the information that the element components upload from the Feedback port to the platform hub through the Feedback bus, which does not need to be visualized but needs to be aggregated and analyzed by the platform hub. The platform hub can call the numerical calculation engine to create a "feedback bus" type object named myFeedBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Feedback bus:

[0159] FeedBus myFeedBus=new FeedBus(postCode1,...,postCodeN)

[0160] The platform hub and all components perform message transmission. The platform hub or component initiates a message transmission task Task and sends the Task to one of the four queues. The four queues correspond to four buses respectively. When the Task is at the head of the current queue, it monitors whether the current bus is occupied. When the bus status is "busy", it continues to wait. When the bus status is "free", the Task monopolizes the bus and executes one of the following message transmission processes:

[0161] myInitBus.Transmitter(postCode,Task)

[0162] myContBus.Transmitter(postCode,Task)

[0163] myDispBus.Receiver(postCode,Task)

[0164] myFeedBus.Receiver(postCode,Task)

[0165] Among them, Task is a structure containing multiple parameter names and values, Transmitter(·) means sending messages from the platform hub, and Receiver(·) means receiving messages from the platform hub.

[0166] It should be noted that there is a distinction between feature components and feature entities: feature components are the projection of a feature in the digital space, and feature entities are the entity of a feature in the physical space.

[0167] In the physical space, a two-way interactive channel is established from the platform hub to each element entity to perform global two-way digital twinning. After the bus structure is defined, the platform hub and element components communicate with each other to establish an interactive channel:

[0168] Industrial facilities at the facility layer use the communication equipment bound to them to communicate with the platform through standard wired and wireless communication protocols. When the industrial facilities are not bound to any communication equipment, the platform only performs static modeling of the facilities and does not consider interactive operations.

[0169] The communication device layer platform communicates with the communication device through standard wired or wireless communication protocols.

[0170] The network layer communicates with the gateway or network management node through standard wired or wireless communication protocols.

[0171] The scene layer monitors the scene through cameras, and the scene changes captured by the cameras will cause changes in the scene elements in the digital space.

[0172] Mapping from real to virtual:

[0173] When the state of an element entity in the physical space changes, the state change information is represented as state real (postCode,t+1), the original state is represented by state real (postCode,t), where t represents the timestamp.

[0174] The state (postCode, t+1) is transmitted to the platform hub through the standard communication protocol.

[0175] The platform hub then drives the corresponding element component status changes through the corresponding virtual bus, namely:

[0176] state cyber (postCode,t+1)=myContBus.Transmitter(postCode,Task(state real ))

[0177] Among them, state cyber Indicates the state of the feature component, Task(state real ) represents a message passing task triggered by a feature entity state change.

[0178] Control the real with the virtual:

[0179] When the state of any element component changes in the virtual digital space, the state change is represented by state cyber (postCode,t+1), the original state is represented by state cyber (postCode,t).

[0180] In the system, the state is transmitted through the Feedback port cyber (postCode, t+1) is fed back to the platform hub, that is:

[0181]

[0182] in, Indicates the status of the element component received by the platform hub, Task(state cyber ) represents a message passing task triggered by a state change of a feature component.

[0183] Based on standard communication protocols, the platform hub will Sent to the corresponding feature entity, the feature entity changes its state to state according to its own conditions real (postCode, t+1), to control the real with the virtual. The platform hub drives the physical entity to change its state through standard wired or wireless communication protocols.

[0184] The above process reflects that: Different from the traditional digital twin method, the present invention focuses on the particularity of the industrial Internet. In addition to paying attention to the factory facility layer and the communication equipment layer, it also condenses the network layer and the scene layer to construct these relatively abstract elements; the present invention further clarifies the relationship between element entities and element components, and establishes dynamic information interaction channels within the digital space and between the digital space and the physical space; the present invention adopts an element-based approach to build digital twin scenarios, and the elements can be defined in advance outside the industrial environment, which is more efficient than the traditional "one-issue-one-discussion" method; the present invention considers the particularity of the industrial Internet of Things, especially the twinning of industrial processes and network communications at the same time, which has not yet been involved in traditional digital twin methods.

[0185] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention, which should all be included in the scope of the claims of the present invention.

[0186] Embodiment 2, the third embodiment of the present invention, is different from the first two embodiments in that:

[0187] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program codes.

[0188] The logic and / or steps represented in the flowchart or otherwise described herein, for example, may be considered as an ordered list of executable instructions for implementing logical functions, and may be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, apparatus or device and execute the instructions), or in conjunction with such instruction execution system, apparatus or device. For purposes of this specification, "computer-readable medium" may be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, apparatus or device, or in conjunction with such instruction execution system, apparatus or device.

[0189] More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk case (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be a paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a computer memory.

[0190] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0191] Example 3, reference Figure 2 , which is the fourth embodiment of the present invention, provides an industrial Internet of Things platform management system driven by digital twins, including a device management module, a scene management module, and a data control module.

[0192] The equipment management module is responsible for acquiring, storing and managing the basic information and operation information of all equipment in the factory, and for associating and dynamically matching equipment.

[0193] Through sensors and communication equipment, the status, operation data and other relevant information of the equipment are obtained in real time, and the equipment information is digitally encoded, including the mapping of suffix coding and attribute information, and the conversion from the physical world to the digital world is carried out. The initial association between devices is established, and the association relationship is continuously updated according to the dynamic scope to ensure effective linkage between devices.

[0194] The scenario management module is responsible for defining and managing industrial scenarios, including production and manufacturing workshops and quality inspection workshops, to ensure that equipment and operations can be coordinated in appropriate scenarios.

[0195] Establish different scenario models according to factory needs, including the definition and property setting of scenario components; interact with the equipment management module to dynamically establish the relationship between equipment and scenarios to ensure the effective operation of equipment in specific scenarios; capture scene changes in real time through monitoring devices such as cameras, update relevant scene elements in the digital space, and feed back changes to the equipment management module.

[0196] The data control module provides a channel for global information interaction and two-way control to ensure the real-time and accuracy of the digital twin system.

[0197] Four virtual buses (Init bus, Control bus, Display bus, and Feedback bus) are established for the transmission of various types of information and the issuance of control instructions. When the status of equipment in the physical space changes, the change information is transmitted to the platform hub through data interaction to update the system status. Data analysis is performed through the collected feedback information to support industrial management decisions and timely adjust equipment and scene configurations to improve overall production efficiency and safety.

[0198] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention, which should all be included in the scope of the claims of the present invention.< / timestamp> < / data> < / name> < / timestamp> < / data> < / name> < / remark> < / timestamp> < / data> < / name> < / index> < / index> < / remark> < / timestamp> < / permission> < / data> < / name> < / index> < / timestamp> < / data> < / name> < / timestamp> < / data> < / name> < / remark> < / timestamp> < / data> < / name> < / index> < / index> < / remark> < / timestamp> < / permission> < / data> < / name> < / index>

Claims

1. An industrial Internet of Things platform management method driven by digital twins, characterized by: include, Obtain basic information and operation information of all equipment in the factory; Define hierarchical industrial IoT elements and components; Digitally encode and digitally map the elements; Correlate and match different elements and perform scenario-based configuration; Add global driving information to conduct global information interaction and two-way digital twins.

2. The industrial Internet of Things platform management method based on digital twin drive according to claim 1, characterized in that: The hierarchical industrial Internet of Things element components include, in a hierarchical definition manner, factory facility definition, communication equipment definition, network definition, and scenario definition; The factory facility definition includes assembly lines, robotic arms, lathes, AGVs, shelves, testing instruments, and other custom facility types; The communication device definition includes sensors, mobile terminals, base stations, gateways, edge servers, cloud servers, and other custom device types; The network definitions include Bluetooth, Lora, ZigBee, WiFi, Star Flash, NBIoT, 5G, and other custom network types; The scene definitions include manufacturing workshops, quality inspection workshops, warehousing and logistics workshops, energy stations, offices, and other custom scene types; The external interfaces of the element components are defined in a software-defined manner, including the Init port, Control port, Display port, and Feedback port, the software-defined interface name, the sender and receiver of data transmission, whether the message transmission is unidirectional or bidirectional, the data structure, and the class used to process the received input parameters; Connect to another facility-type component through n E ports, with bidirectional data flow; connect to a communication equipment-type component through n D ports, with bidirectional data flow; connect to a scene-type component through n S ports, with bidirectional data flow.

3. The industrial Internet of Things platform management method based on digital twin drive according to claim 2, characterized in that: The digital coding includes using suffix coding to uniquely identify the element component, and the suffix coding is expressed as: "element level code-element entity type identifier-unique serial number"; The element level code indicates the level to which the element entity belongs, including the factory facility level E, the communication equipment level D, the network level N, and the scene level S; The element entity type identifier indicates the specific type of the entity, mode M, digital heat exchanger DH, gateway G, heat exchanger HT, thermal sensor TS; The unique serial number distinguishes different entities in the same level and type, model 1-001, digital heat exchanger 5-005, Lora network 1-001, heat exchanger 3-003, thermal sensor 1-002; Add attribute information to the element components to map from the physical world to the digital world. Each attribute information is represented by a six-tuple, namely { <index> , <name> , <data>, <permission> , <timestamp> , <remark>}, an element contains multiple attribute information, through <index> To index;< / index> < / remark> < / timestamp> < / permission> < / data> < / name> < / index> in, <index>is a 3-digit decimal integer, serving as the index of the entry; <name>Indicates the name of the attribute, <data>The first 4 bytes of the current data specify the length of the data, followed by the actual bytecode of the data; permission> is the permission mask including read-only, modify, delete, and invalid permission settings. <timestamp>To record the time when the data was last updated, in microseconds; <remark> Reserved for comments. The default value is null.< / remark> < / timestamp> < / data> < / name> < / index> 4. The industrial Internet of Things platform management method based on digital twin drive according to claim 3 is characterized in that: The association matching includes establishing initial associations for different element components, superimposing prefix codes, and performing dynamic matching associations between element components based on the dynamic scope of the elements; The initialization association includes determining the initialization association relationship of the element components in the factory facility layer E, the communication equipment layer D, the network layer N, and the scene layer S, superimposing the code before the suffix code, and representing the association relationship in the form of a prefix code. Based on the prefix code, each element component constructs and maintains an association rule table. In any scenario, the initialization association of the element component is: Establish the association between the E-layer factory facilities and the D-layer communication equipment. Based on the prefix code of the association rule table, initialize the association logic in a software-defined manner, create a Link_ED type object named mylink, and initialize the connection relationship to true. Among them, preCode represents the prefix code, and flowDr represents the data flow direction; Establish the association between D-layer communication equipment and N-layer network mode: Establish associations between the components of the E layer and the S layer, the D layer and the S layer, and the N layer and the S layer respectively: The dynamic matching association includes that the relationship between elements is constantly changing, and the dynamic association rules based on the element spatiotemporal scope matching algorithm are used to dynamically match the relationship between elements, and update the association rule table. For any element component M, its dynamic scope D is defined. M for: D M ={<x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M , <list-necessary> M , <list-rejective> M } Among them, <x l ,x u ,y l ,y u ,z l ,z u ,t s ,t e > M Indicates the spatiotemporal scope of an element, abbreviated as <D-ST> M ; <list-necessary> M Indicates a required list, that is, the elements that are associated first; <list-rejective> M Represents a reject list, i.e., elements that are never associated; For two element components M and N, a matching calculation is performed to calculate whether element M falls within the scope of element N: When the operation result is R ＜M,N＞ =1, it means that the element M falls within the scope of the element N, otherwise the element M does not fall within the scope of the element N; Then calculate whether element N falls within the scope of element M: When R ＜M,N＞ =1 and R ＜N,M＞ =1, then element M and element N are associated, otherwise they are not associated. If there is an association before this calculation, the association is cancelled and the association rule tables of the two are updated at the same time.

5. The industrial Internet of Things platform management method based on digital twin drive according to claim 4, characterized in that: The association matching also includes an agreed method for establishing a message transmission channel between element components in the digital space; When element M and element N are associated, a two-way data flow interaction of message transmission between the physical space and the digital space is performed. The message transmission methods include method 1, method 2 and method 3: The method 1 is active periodic uploading, where element M periodically transmits messages to element N, and the message carrier is in the form of a four-tuple, defined as {<prefix code>, <name> , <data>, <timestamp>},in, <name> 、 <data>、 <timestamp> Obtained from the local attribute information list of feature N respectively;< / timestamp> < / data> < / name> < / timestamp> < / data> < / name> Mode 2 is a query-aggregation mode. When element M needs to aggregate messages from multiple elements N, P, and Q, element M broadcasts a "query-aggregation" request to multiple elements in the form of a four-tuple. The elements that receive the request send information extracted from the local attribute information list to M and transmit it in the form of a four-tuple. The method 3 is the query-measurement method. Element M hopes to obtain the result of measurement calculation from element N. Element M first sends the data involved in the calculation and the variables expected to be measured to N in the form of a quadruple. After element N obtains the data, it completes the calculation in combination with local data and passes the calculation result to M in the form of a quadruple.

6. The industrial Internet of Things platform management method based on digital twin drive according to claim 5 is characterized in that: The global information interaction includes establishing an interactive path from the platform hub to each element component in the digital space, and defining four virtual buses, namely, the Init bus, the Control bus, the Display bus, and the Feedback bus: The Init bus includes the platform hub writing to the Init port of the element component through the Init bus, configuring the initialization parameters of different element components, creating an initialization bus type object named myInitBus, and postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Init bus: InitBus myInitBus=new InitBus(postCode1,...,postCodeN) The Control bus includes the platform hub performing a write operation on the Control port of the element component through the Control bus, modifying the attribute information list of the element component, and creating a control bus type object named myContBus. postCode1, ..., postCodeN represent the suffix codes of all element components driven by the Control bus: ContBus myContBus=new ContBus(postCode1,...,postCodeN) The Display bus includes the element components uploading information that needs to be visualized from the Display port to the platform hub through the Display bus. The platform hub calls the digital twin visualization engine to create a "display bus" type object named myDispBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Display bus: DispBus myDispBus=new DispBus(postCode1,...,postCodeN) The Feedback bus includes the information that the element components upload from the Feedback port to the platform hub through the Feedback bus, which does not need to be visualized but needs to be aggregated and analyzed by the platform hub. The platform hub can call the numerical calculation engine to create a "feedback bus" type object named myFeedBus. postCode1,...,postCodeN represent the suffix codes of all element components driven by the Feedback bus: FeedBus myFeedBus=new FeedBus(postCode1,...,postCodeN) The platform hub and all components perform message transmission. The platform hub or component initiates a message transmission task Task and sends the Task to one of the four queues. The four queues correspond to four buses respectively. When the Task is at the head of the current queue, it monitors whether the current bus is occupied. When the bus status is "busy", it continues to wait. When the bus status is "free", the Task monopolizes the bus and executes one of the following message transmission processes: myInitBus.Transmitter(postCode,Task) myContBus.Transmitter(postCode,Task) myDispBus.Receiver(postCode,Task) myFeedBus.Receiver(postCode,Task) Among them, Task is a structure containing multiple parameter names and values, Transmitter(·) means sending messages from the platform hub, and Receiver(·) means receiving messages from the platform hub.

7. The method for managing an industrial Internet of Things platform based on digital twin drive according to claim 6, characterized in that: The bidirectional digital twin includes establishing a bidirectional interactive path from the platform hub to each element entity in the physical space, performing global bidirectional digital twin, and after the bus structure is defined, the platform hub and the element components communicate and establish an interactive path: Industrial facilities at the facility layer use the communication equipment bound to them to communicate with the platform through standard wired and wireless communication protocols. When the industrial facilities are not bound to any communication equipment, the platform only performs static modeling on the facilities and does not consider interactive operations; The communication device layer platform communicates with the communication device through standard wired or wireless communication protocols; The network layer uses standard wired or wireless communication protocols to allow the platform to communicate with gateways or network management nodes; The scene layer monitors the scene through the camera. The scene changes captured by the camera will cause changes in the scene elements in the digital space. When the state of an element entity in the physical space changes, the state change information is represented as state real (postCode,t+1), the original state is represented by state real (postCode, t), where t represents the timestamp; The state (postCode, t+1) is transmitted to the platform hub through the standard communication protocol; The platform hub then drives the corresponding element component status changes through the corresponding virtual bus, namely: state cyber (postCode,t+1)=myContBus.Transmitter(postCode,Task(state real )) Among them, state cyber Indicates the state of the feature component, Task(state real ) represents the message passing task triggered by the state change of the feature entity; When the state of any element component changes in the virtual digital space, the state change is represented by state cyber (postCode,t+1), the original state is represented by state cyber (postCode,t); In the system, the state is transmitted through the Feedback port cyber (postCode, t+1) is fed back to the platform hub, that is: in, Indicates the status of the element component received by the platform hub, Task(state cyber ) represents a message passing task triggered by a state change of an element component; Based on standard communication protocols, the platform hub will Sent to the corresponding feature entity, the feature entity changes its state to state according to its own conditions real (postCode,t+1), to control the real with the virtual; the platform hub drives the physical entity to change its state through standard wired or wireless communication protocols.

8. A system using the industrial Internet of Things platform management method based on digital twin drive as described in any one of claims 1 to 7, characterized in that: Including equipment management module, scene management module and data control module; The equipment management module is responsible for acquiring, storing and managing the basic information and operation information of all equipment in the factory, and performing association and dynamic matching between equipment; The scenario management module is responsible for defining and managing industrial scenarios, including manufacturing workshops and quality inspection workshops, to ensure that equipment and operations can be coordinated in appropriate scenarios; The data control module provides a channel for global information interaction and two-way control to ensure the real-time and accuracy of the digital twin system.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the industrial Internet of Things platform management method based on digital twin drive described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the industrial Internet of Things platform management method based on digital twin drive described in any one of claims 1 to 7 are implemented.

Images