Equipment management method and device, equipment, medium and program product

Abstract

The invention relates to the technical field of Internet of Things, and discloses an equipment management method and device, equipment, a medium and a program product. The method comprises the following steps: acquiring object model data corresponding to target equipment through a coal mine unified data transmission protocol (MDTP) service; the method comprises the following steps: acquiring equipment data corresponding to target equipment through a modular communication protocol MODBUS service, and carrying out standardization processing on the equipment data by converting MODBUS address information into a triple form to obtain standard equipment data; and updating the object model data based on the standard equipment data through the MDTP service, and obtaining updated object model data corresponding to the target equipment. According to the scheme of the embodiment, the MDTP service and the MODBUS service are set, and the equipment data acquired by the MODBUS service is subjected to standardized processing, so that the unification of an equipment data format and a reporting mechanism is realized, the efficient acquisition and management of the equipment data are realized, and the equipment management efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things, and in particular to a device management method, apparatus, equipment, medium and program product. Background Art

[0002] The coal mining industry utilizes a wide variety of equipment, encompassing everything from ventilation, hoisting, and transportation to drilling and production, each with its own unique functions and requirements. Furthermore, operating systems are complex and diverse. Traditional coal mine automation systems are often provided by different manufacturers, each with its own independent system architecture and user interface, making coordination and management of the entire system extremely difficult. Furthermore, the protocols used by each device vary, lacking a unified standard. This leads to serious compatibility issues with data exchange and control command transmission between devices from different manufacturers and models. This lack of protocol uniformity not only increases the complexity of device access but also poses significant challenges to the coal mining industry in terms of equipment monitoring, data sharing, and remote control, impacting production efficiency and safety management in coal mines. Summary of the Invention

[0003] The present invention provides a device management method, apparatus, device, medium and program product, which can unify the device data format and reporting mechanism, realize efficient collection and management of device data, and improve device management efficiency.

[0004] According to one aspect of the present invention, there is provided a device management method, comprising:

[0005] Obtain the physical model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service;

[0006] The device data corresponding to the target device is collected through the modular communication protocol MODBUS service, and the device data is standardized by converting the MODBUS address information into a triplet form to obtain standard device data;

[0007] The object model data is updated based on the standard device data through the MDTP service to obtain updated object model data corresponding to the target device.

[0008] According to another aspect of the present invention, there is provided a device management apparatus, comprising:

[0009] The physical model data acquisition module is used to obtain the physical model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service;

[0010] A data standardization processing module is used to collect device data corresponding to the target device through the modular communication protocol MODBUS service, and to standardize the device data by converting the MODBUS address information into a triplet form to obtain standard device data;

[0011] The data updating module is configured to update the object model data based on the standard device data through the MDTP service, and obtain the updated object model data corresponding to the target device.

[0012] According to another aspect of the present invention, an electronic device is provided, comprising:

[0013] at least one processor; and

[0014] a memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores a computer program executable by the at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the device management method according to any embodiment of the present invention.

[0016] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and the computer program is configured to enable a processor to implement the device management method according to any embodiment of the present invention when executed.

[0017] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the device management method according to any embodiment of the present invention is implemented.

[0018] The technical solution of the embodiment of the present invention obtains the object model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service; collects the device data corresponding to the target device through the modular communication protocol MODBUS service, and standardizes the device data by converting the MODBUS address information into a triplet form to obtain standard device data; updates the object model data based on the standard device data through the MDTP service to obtain the updated object model data corresponding to the target device; and by setting the MDTP service and the MODBUS service and standardizing the device data collected by the MODBUS service, the unification of the device data format and the reporting mechanism is achieved, the efficient collection and management of the device data is achieved, and the equipment management efficiency is improved.

[0019] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 This is a flow chart of a device management method provided according to the first embodiment of the present invention;

[0022] Figure 2 This is a schematic diagram of the physical model definition provided in the first embodiment of the present invention;

[0023] Figure 3 This is a schematic diagram of the MODBUS definition provided according to the first embodiment of the present invention;

[0024] Figure 4 This is a flow chart of a device management method provided according to the second embodiment of the present invention;

[0025] Figure 5 is a flowchart of another device management method provided according to embodiment 2 of the present invention;

[0026] Figure 6 This is a schematic diagram of the structure of a device management apparatus provided according to a third embodiment of the present invention;

[0027] Figure 7 It is a structural diagram of an electronic device for implementing the device management method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," "target," etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or that are inherent to these processes, methods, products, or apparatus.

[0030] Example 1

[0031] Figure 1 A flow chart of a device management method is provided for the first embodiment of the present invention. This embodiment is applicable to the coal mining industry for data collection and management of electromechanical equipment. The method can be executed by a device management device, which can be implemented in the form of hardware and / or software. Typically, the device management device can be configured in an electronic device, such as a computer device or a server. Figure 1 As shown, the method includes:

[0032] S110. Obtain object model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service.

[0033] Among them, the Mine Data Transfer Protocol (MDTP) is a network transmission and interoperability protocol standard that can be used for data collection and transmission between various types of equipment or between platforms and equipment, such as communication between inspection equipment and industrial machines, data synchronization or remote control between equipment and servers, etc. The MDTP service is a set of Harmony Services (Service Ability, SA) included in the Mine Hong system specifically for object model parsing, attribute registration, attribute reading, attribute writing and data processing. In the Mine Hong system, the services provided based on the framework layer are implemented using SA, and there will be only one SA instance in each device.

[0034] A thing model is a set of digital models defined by the IoT platform for the same type of device or product. It digitally describes the product through three functional types: attributes, events, and behaviors. It serves as a key interface for standardization, defining product functionality and abstracting and summarizing product functions across brands and categories, making it easier for all parties to describe, control, and understand product functions using a unified language.

[0035] This embodiment provides a new object model definition, which includes model information, device information, network information, and function information. Based on the object model definition, users can pre-configure the object model file corresponding to the target device. The MDTP service can then parse the object model file to obtain the object model data. The target device can be electromechanical equipment in the coal mining industry, such as a low-voltage protection switch.

[0036] Optionally, the object model data corresponding to the target device can be obtained through the coal mine unified data transmission protocol MDTP service, which can include:

[0037] Obtaining a physical model file corresponding to the target device through the MDTP service, and parsing the physical model file to obtain model information, device information, network information, and function information corresponding to the target device;

[0038] Obtain object model data corresponding to the target device according to the model information, device information, network information and function information.

[0039] The object model file may be in the format of Extensible Markup Language (XML), may be pre-written by a user, or may be converted from a modular communication protocol file.

[0040] Taking the target device as a low voltage protection switch as an example, the object model definition can be as follows: Figure 2 As shown in the figure, it includes model information, device information, network information and function information, and each information contains multiple device attributes. Among them, the id (Identity) in the ccipDeviceAttrSet field represents the device id, the id in the ccipDeviceAttrSetInstance field represents the instance id, the attrId in the ccipAttr field represents the attribute id, the type field represents the attribute data type, the access field represents the attribute read and write type (R represents read, W represents write), the mask field represents the attribute mask, the readstatus field represents the attribute read status, the setstatus field represents the attribute setting status, the value field represents the attribute default value, and the desc field represents the attribute description information. It is worth noting that model information, device information and network information are common parts of the object model. Each device will contain this information, while the function information needs to be adapted according to the specific device.

[0041] Specifically, in the MDTP service, the object model file in XML format can be parsed to extract the model information, device information, network information and function information corresponding to the target device, and the various pieces of information can be combined to obtain the object model data.

[0042] Optionally, obtaining the object model file corresponding to the target device through the MDTP service may include:

[0043] Get the conversion rules between MODBUS definition and object model definition;

[0044] The MODBUS definition file corresponding to the target device is obtained through the MDTP service, and the MODBUS definition file is converted according to the conversion rule between the MODBUS definition and the object model definition to obtain the object model file corresponding to the target device.

[0045] Among them, still taking the low voltage protection switch as an example, the definition of the modular communication protocol (Modbus protocol, MODBUS) can be as follows Figure 3 As shown, it includes detailed information such as MODBUS address, name, data type, unit, etc. In this embodiment, the conversion rules between MODBUS definition and object model definition can be predefined to achieve the unification of data format. For example, the conversion rules may include: (1) converting the MODBUS address information into a triplet to represent the device attributes. For example, the MODBUS address of the phase A voltage is 40001. After conversion to the physical model information, the device id is 4 (1-3 has been occupied by the model, device, and network information, and starts from 4 by default), the instance id is 1 (counting starts from 1 by default), and the attribute attrId is 1 (counting starts from 1 by default). Therefore, the triplet 4.1.1 is used to represent the phase A voltage in the future; (2) the data type of the phase A voltage is uint16, and the type data type in the physical model is also set to uint16, which is consistent with the data type of the MODBUS protocol; (3) since there is no default value for the phase A voltage in the MODBUS protocol, the default value of the value attribute in the physical model is set to 1; (4) the desc description information in the physical model is consistent with the name of the phase A voltage in the MODBUS protocol, so the phase A voltage is represented by the triplet 4.1.1 in the future, and other device attributes are also processed in this way.

[0046] Specifically, the MODBUS definition file may be first obtained through the MDTP service, and then the MODBUS definition file may be automatically converted based on a predefined conversion rule between the MODBUS definition and the object model definition, thereby obtaining the object model file.

[0047] In this embodiment, by setting a standard object model definition, object models with different definitions can be converted into a unified format, supporting data collection services for connecting to devices with different protocols.

[0048] S120 , collecting device data corresponding to the target device through the modular communication protocol MODBUS service, and converting the MODBUS address information into a triplet form to standardize the device data to obtain standard device data.

[0049] Among them, the MODBUS service can be an SA service included in the Kuanghong system that specifically handles the MODBUS protocol, which is used to connect to specific electromechanical equipment in order to collect equipment attribute information, etc. MODBUS adopts a client-server communication model, which constitutes the backbone of data communication in the MODBUS transmission control protocol / Internet protocol network. In this model, the client sends a request to the server (or multiple servers), and the server then processes the request and returns a response. The client is typically a human-machine interface, a programmable logic controller, or any device that requires data or control equipment. On the other hand, the server is typically a sensor, actuator, or other device that provides data or performs operations, and in this embodiment, the server can be an electromechanical device that requires data collection and management.

[0050] In this embodiment, after the MODBUS service is started, the client can be started according to the pre-configured port, connected to the server (target device) and listen for data. Afterwards, the client in the MODBUS service collects device data once every set time interval to obtain the device data corresponding to the target device. Furthermore, the MODBUS service can convert the MODBUS address information in the device data into a triple form based on the conversion rules between the pre-set MODBUS definition and the object model definition, and set other properties to convert the device data into a standardized JS key-value pair data (JavaScript Object Notation, JSON) string, thereby obtaining standard device data. For example, the standard device data is {"4.1.4":"36"}, which means that the rated voltage is 36.

[0051] S130: Update the object model data based on the standard device data through the MDTP service, and obtain updated object model data corresponding to the target device.

[0052] In this embodiment, after the standard device data is acquired, the original object model data can be updated using the standard device data through the MDTP service to obtain updated object model data. The update can be a full update or an incremental update.

[0053] The technical solution of the embodiment of the present invention obtains the object model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service; collects the device data corresponding to the target device through the modular communication protocol MODBUS service, and standardizes the device data by converting the MODBUS address information into a triplet form to obtain standard device data; updates the object model data based on the standard device data through the MDTP service to obtain the updated object model data corresponding to the target device; and by setting the MDTP service and the MODBUS service and standardizing the device data collected by the MODBUS service, the unification of the device data format and the reporting mechanism is achieved, the efficient collection and management of the device data is achieved, and the equipment management efficiency is improved.

[0054] Example 2

[0055] Figure 4 This is a flow chart of a device management method provided in Example 2 of the present invention. This embodiment is a further refinement of the above technical solution. The technical solution in this embodiment can be combined with one or more of the above implementation methods. Figure 4 As shown, the method includes:

[0056] S210: Acquire conversion rules between MODBUS definition and object model definition.

[0057] S220 . Obtain a MODBUS definition file corresponding to the target device through the MDTP service, and convert the MODBUS definition file according to a conversion rule between the MODBUS definition and the object model definition to obtain a object model file corresponding to the target device.

[0058] S230. Parse the object model file to obtain model information, device information, network information, and function information corresponding to the target device, and obtain object model data corresponding to the target device based on the model information, device information, network information, and function information.

[0059] S240: Store the object model data into a dynamic array container.

[0060] Specifically, after acquiring the object model data, key device parameters and attributes can be extracted from the object model data and stored in a dynamic array container std::vector, with each device node as an independent data object. Dynamic array containers automatically resize, expanding their capacity as elements are added, and support random access like arrays.

[0061] S250 , collecting device data corresponding to the target device through the modular communication protocol MODBUS service, and converting the MODBUS address information into a triplet form to standardize the device data and obtain standard device data.

[0062] Optionally, before acquiring the device data corresponding to the target device through the modular communication protocol MODBUS service, the following steps may also be included:

[0063] Registering a callback function to the MODBUS service through the MDTP service to establish a communication link between the MDTP service and the MODBUS service;

[0064] In an optional example, the MDTP service can establish a communication link with the MODBUS service by registering the EventCallback callback function to the MODBUS service and wait for data to be reported. The EventCallback callback function is defined as using EventCallback = std::function<void(const std::string&)> , indicating reporting a string for registering a callback function in the MODBUS service.

[0065] After converting the MODBUS address information into a triplet form and performing standardization processing on the device data to obtain the standard device data, the following steps may also be included:

[0066] The standard device data is sent to the MDTP service via the MODBUS service based on the communication link between the MDTP service and the MODBUS service.

[0067] Correspondingly, after obtaining the standard device data, the MODBUS service can upload the standard device data to the MDTP service based on the communication link between the MODBUS service and the MDTP service.

[0068] In this embodiment, by using a registration callback function to report device data, the efficiency of collecting device data can be improved.

[0069] S260: Update the object model data in the dynamic array container based on the standard device data through the MDTP service, and obtain updated object model data corresponding to the target device.

[0070] In this embodiment, after the MDTP service obtains the standard device data reported by the MODBUS service, it can update the existing object model data in the std::vector based on the triplet information to obtain the updated object model data. Specifically, matching information can be searched in the std::vector based on the triplet information, and the current attribute value can be compared with the original attribute value found. If it is determined that they are not equal, the current attribute value is used to replace the original attribute value to achieve the update of the object model data. For example, the standard device data is {"4.1.4":"36"}, the object model data in the std::vector is {"4.1.4":"35"}, and the current rated voltage is not equal to the original rated voltage, then the object model data in the std::vector is updated to {"4.1.4":"36"}.

[0071] S270: When a user's request to view target properties of a target device is detected through the target application, a property acquisition request is sent to the MDTP service through the host control protocol component.

[0072] The target application can communicate with the MDTP service through the Host Controller Protocol (HCP) component. Specifically, when the user needs to view the properties or parameters of the target device, he can send a request to view the target properties of the target device to the target application. At this time, the target application can call the interface HcpReadRemoteAttrValue and send a property acquisition request to the MDTP service through the HCP component of Kuanghong. The target properties can be rated voltage, rated current, active power, etc.

[0073] S280: Read the attribute value corresponding to the target attribute from the dynamic array container according to the attribute acquisition request through the MDTP service, and send the attribute value to the target application through the host control protocol component.

[0074] Specifically, after receiving the attribute acquisition request, the MDTP service can trigger the OnReadCallback read attribute callback function through the HCP component of Kuanghong, read the latest attribute value corresponding to the target attribute from the std::vector, and return the attribute value to the target application.

[0075] S290: Visually display the target attributes and corresponding attribute values ​​through the target application.

[0076] Specifically, after receiving the attribute value, the target application may display the target attribute and the corresponding attribute value on the interface, completing an attribute reading process.

[0077] In a specific implementation of this embodiment, the process of the device management method can be as follows: Figure 5 As shown in the figure. First, the MDTP service parses the XML object model file of the electromechanical device, extracts model information, device information, network information, and function information, and stores the extracted information in std::vector memory for subsequent use. After that, the extracted information is registered through the MDTP protocol stack interface HcpRegister AttributeSet, waiting for subsequent application calls. Then, after the MODBUS service is started, the client is started according to the configured port 502, connected to the server, and listens for data. Furthermore, the MDTP service registers the EventCallback callback function with the MODBUS service, waiting for data reporting. Secondly, the client in the MODBUS service collects device data once a second, parses and formats it into a standardized JSON string, and uploads it to the MDTP service. The MDTP service receives and processes the uploaded JSON data, and updates the corresponding data in std::vector based on the triple information.

[0078] The APP application discovers and connects to the MDTP service through the HCP component. When it needs to obtain the rated voltage, it calls the interface HcpReadRemoteAttrValue and sends a request to obtain the rated voltage attribute through the corresponding HCP component. After receiving the request, the MDTP service triggers the OnReadCallback read attribute callback function through the corresponding HCP component and returns the latest rated voltage data in the std::vector to the APP application. The APP application displays the rated voltage on the interface to complete the attribute reading. Secondly, the user can also perform fault data operations through the APP application. Correspondingly, the MDTP service triggers the method callback function to obtain the fault data operation results and returns the results to the APP application, which then reports the fault data results.

[0079] In this embodiment, a set of standard electromechanical equipment physical models is proposed. At the same time, a set of data standardization processing and reporting mechanisms are proposed for protocol collection data, which can realize the efficient collection and management of electromechanical equipment data and improve the production efficiency and safety management level of coal mines.

[0080] The technical solution of an embodiment of the present invention is as follows: after obtaining the object model data corresponding to the target device, the object model data is stored in a dynamic array container; through the MDTP service, the object model data in the dynamic array container is updated based on the standard device data to obtain the updated object model data corresponding to the target device; by using the dynamic array container for device data storage, the data update efficiency can be improved; secondly, when the user's request to view the target attribute of the target device is detected through the target application, the host control protocol component sends a property acquisition request to the MDTP service; through the MDTP service, according to the property acquisition request, the property value corresponding to the target attribute is read from the dynamic array container, and the property value is sent to the target application through the host control protocol component; through the target application, the target attribute and the corresponding property value are visualized, providing a set of standard device data reporting mechanisms, which can improve the efficiency of device data collection and management, and improve device management efficiency.

[0081] Example 3

[0082] Figure 6 This is a schematic diagram of the structure of a device management device provided by the third embodiment of the present invention. Figure 6 As shown, the device includes: a physical model data acquisition module 310, a data standardization processing module 320 and a data update module 330; wherein,

[0083] The physical model data acquisition module 310 is used to obtain the physical model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service;

[0084] The data standardization processing module 320 is used to collect the device data corresponding to the target device through the modular communication protocol MODBUS service, and to standardize the device data by converting the MODBUS address information into a triplet form to obtain standard device data;

[0085] The data updating module 330 is configured to update the object model data based on the standard device data through the MDTP service, and obtain the updated object model data corresponding to the target device.

[0086] The technical solution of the embodiment of the present invention obtains the object model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service; collects the device data corresponding to the target device through the modular communication protocol MODBUS service, and standardizes the device data by converting the MODBUS address information into a triplet form to obtain standard device data; updates the object model data based on the standard device data through the MDTP service to obtain the updated object model data corresponding to the target device; and by setting the MDTP service and the MODBUS service and standardizing the device data collected by the MODBUS service, the unification of the device data format and the reporting mechanism is achieved, the efficient collection and management of the device data is achieved, and the equipment management efficiency is improved.

[0087] Optionally, the physical model data acquisition module 310 includes:

[0088] a file parsing unit, configured to obtain a physical model file corresponding to the target device through the MDTP service, and parse the physical model file to obtain model information, device information, network information, and function information corresponding to the target device;

[0089] The object model data acquisition unit is used to acquire the object model data corresponding to the target device according to the model information, device information, network information and function information.

[0090] Optionally, a file parsing unit is used to obtain the conversion rules between MODBUS definition and object model definition;

[0091] The MODBUS definition file corresponding to the target device is obtained through the MDTP service, and the MODBUS definition file is converted according to the conversion rule between the MODBUS definition and the object model definition to obtain the object model file corresponding to the target device.

[0092] Optionally, the device management device further includes:

[0093] A data storage module, configured to store the object model data in a dynamic array container;

[0094] The data updating module 330 is specifically configured to update the object model data in the dynamic array container based on the standard device data through the MDTP service, and obtain the updated object model data corresponding to the target device.

[0095] Optionally, the device management device further includes:

[0096] a request sending module, configured to send a property acquisition request to the MDTP service through a host control protocol component when a user's request to view a target property of a target device is detected through a target application;

[0097] an attribute value reading module, configured to read the attribute value corresponding to the target attribute from the dynamic array container according to the attribute acquisition request through the MDTP service, and send the attribute value to the target application through the host control protocol component;

[0098] The attribute value display module is used to visually display the target attribute and the corresponding attribute value through the target application.

[0099] Optionally, the device management device further includes:

[0100] A communication link establishing module, configured to register a callback function to the MODBUS service through the MDTP service to establish a communication link between the MDTP service and the MODBUS service;

[0101] The data sending module is used to send the standard device data to the MDTP service through the MODBUS service based on the communication link between the MDTP service and the MODBUS service.

[0102] The equipment management apparatus provided in the embodiment of the present invention can execute the equipment management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0103] In the technical solutions disclosed herein, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0104] Example 4

[0105] Figure 7 A schematic diagram of the structure of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device 40 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 40 can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0106] like Figure 7As shown, the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by the at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory 42 or the computer program loaded from the storage unit 48 to the random access memory 43. Various programs and data required for the operation of the electronic device 40 can also be stored in the RAM 43. The processor 41, ROM 42 and RAM 43 are connected to each other via a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0107] Multiple components in the electronic device 40 are connected to the I / O interface 45, including an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a magnetic disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0108] Processor 41 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of processor 41 include, but are not limited to, a central processing unit, a graphics processing unit, various specialized artificial intelligence computing chips, various processors running machine learning model algorithms, a digital signal processor, and any suitable processor, controller, microcontroller, etc. Processor 41 executes the various methods and processes described above, such as the device management method.

[0109] In some embodiments, the device management method may be implemented as a computer program that is tangibly contained in a computer-readable storage medium, such as storage unit 48. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 40 via ROM 42 and / or communication unit 49. When the computer program is loaded into RAM 43 and executed by processor 41, one or more steps of the device management method described above may be performed. Alternatively, in other embodiments, processor 41 may be configured to perform the device management method in any other suitable manner (e.g., by means of firmware).

[0110] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays, application specific integrated circuits, application specific standard products, system-on-a-chip systems, on-load programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0111] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0112] In the context of the present invention, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. A computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical fiber, a portable compact disk read-only memory, an optical storage device, a magnetic storage device or any suitable combination of the foregoing.

[0113] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device 40 having: a display device (e.g., a cathode ray tube or a liquid crystal display) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or a trackball) through which the user can provide input to the electronic device 40. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0114] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include local area networks, wide area networks, blockchain networks, and the Internet.

[0115] A computing system may include clients and servers. The client and server are generally remote from each other and typically interact through a communication network. The client and server relationship arises through computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server.

[0116] This embodiment may also include a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the device management method provided by any embodiment of the present invention.

[0117] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0118] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A device management method, characterized in that: include: Obtain the physical model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service; The device data corresponding to the target device is collected through the modular communication protocol MODBUS service, and the device data is standardized by converting the MODBUS address information into a triplet form to obtain standard device data; The object model data is updated based on the standard device data through the MDTP service to obtain updated object model data corresponding to the target device.

2. The method according to claim 1, characterized in that Obtain the object model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service, including: Obtaining a physical model file corresponding to the target device through the MDTP service, and parsing the physical model file to obtain model information, device information, network information, and function information corresponding to the target device; Obtain object model data corresponding to the target device according to the model information, device information, network information and function information.

3. The method according to claim 2, characterized in that Obtaining a physical model file corresponding to the target device through the MDTP service includes: Get the conversion rules between MODBUS definition and object model definition; The MODBUS definition file corresponding to the target device is obtained through the MDTP service, and the MODBUS definition file is converted according to the conversion rule between the MODBUS definition and the object model definition to obtain the object model file corresponding to the target device.

4. The method according to claim 2, characterized in that After acquiring object model data corresponding to the target device according to the model information, device information, network information, and function information, the method further includes: storing the physical model data in a dynamic array container; Updating the object model data based on the standard device data through the MDTP service to obtain updated object model data corresponding to the target device includes: The object model data in the dynamic array container is updated based on the standard device data through the MDTP service to obtain updated object model data corresponding to the target device.

5. The method according to claim 4, characterized in that Also includes: When a user's request to view target properties of a target device is detected through the target application, a property acquisition request is sent to the MDTP service through the host control protocol component; Reading, by the MDTP service, an attribute value corresponding to the target attribute from the dynamic array container according to the attribute acquisition request, and sending the attribute value to the target application through a host control protocol component; The target attributes and corresponding attribute values ​​are visualized through the target application.

6. The method according to claim 1, characterized in that Before acquiring the device data corresponding to the target device through the modular communication protocol MODBUS service, the method further includes: Registering a callback function to the MODBUS service through the MDTP service to establish a communication link between the MDTP service and the MODBUS service; After converting the MODBUS address information into a triplet form and performing standard processing on the device data to obtain the standard device data, the following steps are further included: The standard device data is sent to the MDTP service via the MODBUS service based on the communication link between the MDTP service and the MODBUS service.

7. A device management device, characterized in that: include: The physical model data acquisition module is used to obtain the physical model data corresponding to the target device through the coal mine unified data transmission protocol MDTP service; A data standardization processing module is used to collect device data corresponding to the target device through the modular communication protocol MODBUS service, and to standardize the device data by converting the MODBUS address information into a triplet form to obtain standard device data; The data updating module is configured to update the object model data based on the standard device data through the MDTP service, and obtain the updated object model data corresponding to the target device.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor, and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor. The computer program is executed by the at least one processor to enable the at least one processor to perform the device management method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is configured to enable a processor to implement the device management method according to any one of claims 1 to 6 when the computer program is executed.

10. A computer program product, characterized in that The device comprises a computer program, which implements the device management method according to any one of claims 1 to 6 when executed by a processor.

Images