Device management method and system, computer device, storage medium and program product

Abstract

The application provides a device management method and system, a computer device, a storage medium and a program product, and relates to the technical fields of cloud technology, cloud storage and the like. A configuration page of at least one production device is displayed to facilitate a user to configure complex and multi-type production devices in an industrial production scene by using the configuration page. When data categories configured in the configuration page of the at least one production device are acquired, a reporting instruction is respectively sent to each production device, and an analysis server is sent an analysis instruction. Each production device reports data to the analysis server based on the respective data categories, and the analysis server automatically returns attribute data obtained by analysis. Automatic data collection of complex and multi-type production devices in an industrial production scene is realized. Furthermore, attribute data of each production device can be displayed to facilitate device management based on the displayed data, and the efficiency, flexibility and reliability of device management are improved.

Description

Technical Field

[0001] This application relates to the technical fields of cloud technology and cloud storage, and specifically to a device management method, system, computer equipment, storage medium, and program product. Background Technology

[0002] In industrial production processes, it is typically necessary to collect data from equipment in the production workshop for management purposes. In this field, each piece of equipment in the production workshop uniformly reports its data to a server for management purposes.

[0003] In related technologies, the equipment management process includes: staff need to write different program codes for different devices to enable each device to report data. For example, staff encode a corresponding reporting program code for each device, and each device executes its corresponding reporting program code to report its own data to the server. The server then manages the equipment based on the data reported by each device.

[0004] The above process requires coding different devices separately. However, there are many different types of devices, and even the same type of devices have different models. The above method is costly and time-consuming when reporting data, resulting in low actual management efficiency of device management. Summary of the Invention

[0005] This application provides a device management method, system, computer device, storage medium, and program product, which can solve the problem of low actual management efficiency in related technologies. The technical solution is as follows:

[0006] On the one hand, a device management method is provided, the method comprising:

[0007] Displays the configuration page for at least one production device;

[0008] In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device and a parsing instruction is sent to the parsing server. The reporting instruction instructs to report data to the parsing server based on the data category of the corresponding production device, and the parsing instruction instructs to return the attribute data obtained by parsing the reported data of each production device.

[0009] In response to receiving attribute data of each production device returned by the parsing server, the attribute data of each production device is displayed on the device management page, and each production device is managed based on the attribute data.

[0010] On the other hand, a device management method is provided, the method comprising:

[0011] In response to a parsing instruction triggered by the configuration page of at least one production device, the data parsing protocol corresponding to each of the at least one production device is stored, and the parsing instruction indicates the return of attribute data obtained by parsing the reported data of each production device;

[0012] In response to receiving data reported by any production equipment, the reported data is parsed based on the data parsing protocol corresponding to the production equipment to obtain the attribute data of the production equipment.

[0013] Return the attribute data of any of the production equipment to the management device.

[0014] On the other hand, a device management method is provided, the method comprising:

[0015] For any one of the at least one production equipment, initiate the data reporting program for that production equipment, wherein the at least one production equipment is a device that has established a connection with the management equipment and is managed by the management equipment based on the attribute data displayed on the equipment management page;

[0016] In response to a reporting instruction triggered by a configuration page of any production device displayed by the management device, the attribute class file of the production device sent by the management device is stored in the parameter loading path. The attribute class file includes the data category of the production device. The reporting instruction instructs to report data to the parsing server based on the data category of the production device.

[0017] Based on the data reporting program, the attribute class file is loaded from the parameter loading path, and the reported data is sent to the parsing server based on the data categories included in the attribute class file.

[0018] On the other hand, an equipment management system is provided, characterized in that the equipment management system includes a management device, a parsing server, and at least one production device; the management device is used for:

[0019] Displays the configuration page for at least one production device;

[0020] In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device and a parsing instruction is sent to the parsing server. The reporting instruction instructs to report data to the parsing server based on the data category of the corresponding production device, and the parsing instruction instructs to return the attribute data obtained by parsing the reported data of each production device.

[0021] In response to receiving attribute data of each production device returned by the parsing server, the attribute data of each production device is displayed on the device management page, and each production device is managed based on the attribute data.

[0022] On the other hand, a computer device is provided, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the device management method described above.

[0023] On the other hand, a computer-readable storage medium is provided that stores a computer program thereon, which, when executed by a processor, implements the device management method described above.

[0024] On the other hand, a computer program product is provided, including a computer program that, when executed by a processor, implements the above-described device management method.

[0025] The beneficial effects of the technical solutions provided in this application are:

[0026] The equipment management method provided in this application displays a configuration page for at least one type of production equipment, facilitating user configuration of complex and diverse production equipment in industrial production scenarios. When the data category configured on the configuration page of at least one type of production equipment is obtained, a reporting command can be sent to each production equipment, and a parsing command can be sent to the parsing server. This enables each production equipment to report data to the parsing server based on its respective data category, and the parsing server automatically returns the parsed attribute data. This achieves automated data collection for complex and diverse production equipment in industrial production scenarios. Furthermore, the attribute data of each production equipment can be displayed to facilitate equipment management based on the displayed data. By flexibly configuring data categories through the configuration page and automatically triggering device reporting and parsing server automatic parsing, a reliable equipment management process is formed by managing equipment, production equipment, and the parsing server, improving the efficiency, flexibility, and reliability of equipment management. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0028] Figure 1 This application provides a schematic diagram of an equipment management system architecture for implementing an equipment management method.

[0029] Figure 2 A flowchart illustrating a device management method provided in an embodiment of this application;

[0030] Figure 3 A schematic diagram of a device management page provided in an embodiment of this application;

[0031] Figure 4A schematic diagram of a configuration page provided in an embodiment of this application;

[0032] Figure 5 A schematic diagram of a configuration page provided in an embodiment of this application;

[0033] Figure 6 This is a schematic diagram of the structure of an equipment management system provided in an embodiment of this application;

[0034] Figure 7 A flowchart illustrating a device management method provided in an embodiment of this application;

[0035] Figure 8 This is a schematic diagram illustrating the execution process of a parsing server, provided in an embodiment of this application.

[0036] Figure 9 A flowchart illustrating a device management method provided in an embodiment of this application;

[0037] Figure 10 This application provides a schematic diagram of the execution process of a production equipment.

[0038] Figure 11 This application provides a schematic diagram of a data category update process.

[0039] Figure 12 A flowchart illustrating a device management method provided in an embodiment of this application;

[0040] Figure 13 This is a schematic diagram of the structure of an equipment management system provided in an embodiment of this application;

[0041] Figure 14 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0042] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0043] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. The terms “comprising” and “including” as used in the embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, or operation, but do not exclude implementation as other features, information, data, steps, or operations supported by this art.

[0044] It is understood that in the specific implementation of this application, any user-related data, such as user permission information, data categories of user's production equipment, and attribute data, is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0045] Figure 1 This is a schematic diagram of the architecture of an equipment management system provided in this application. This equipment management system can manage production equipment using the equipment management method of this application. Figure 1 As shown, the equipment management system includes: a management device 11, a parsing server 12, and at least one production device 13. The management device 11 is equipped with a management application, such as a management client or a management platform; the management device 11 can interact with at least one production device 13 and the parsing server 12 through the management application to manage the at least one production device 13.

[0046] In one possible implementation environment, the management device 11 can use the management application to send reporting instructions to each production device 13 and parsing instructions to the parsing server 12. Each production device 13 can report its own data to the parsing server 12 based on the reporting instructions. The parsing server 12 can parse the reported data from each production device 13 based on the parsing instructions to obtain attribute data, and then send the attribute data of each production device 13 to the management device 11.

[0047] In another possible implementation environment, the equipment management system may further include a backend server 14, which may be the backend server 14 of the management application. The management device 11 interacts with the backend server 14 based on the management application to manage each production device. The management application provides configuration pages for each production device 13. The management device 11 can send a data acquisition command to the backend server 14 based on the data category configured by the user in the configuration page of any production device 13. The data acquisition command instructs the collection of attribute data of the production device 13 in the configured data category. The backend server 14 can send a reporting command to the production device 13 and a parsing command to the parsing server 12 based on the data acquisition command. This allows the management device 11 to obtain the attribute data of the production device returned by the parsing server 12. The parsing server 12 may be an intermediate parsing platform located between the backend server 14 and each production device 13. The parsing server 12 parses the data reported by each production device 13 and returns the parsed attribute data of each production device to the backend server 14.

[0048] In industrial production scenarios, various types of production equipment 12 typically operate in the industrial production environment, such as cleaning machines and cutting machines. The factory's management equipment 11 can be equipped with an equipment management platform. Users can configure the data categories that need to be collected by the cleaning machines and cutting machines on the equipment management platform, and obtain the attribute data of the cleaning machines and cutting machines in their respective data categories through the equipment management platform. The equipment management platform can display to users the production volume and yield rate of each cleaning machine that are automatically collected, as well as the production volume and cutting success rate of each cutting machine.

[0049] It should be noted that the at least one production device 13 may include, but is not limited to, a cleaning machine, a cutting machine, a slicing machine, a packaging machine, a scanning machine, etc. The management device 11 may be a management server, a terminal, or a computer device providing a large operating interface. The server may be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server or server cluster providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, and big data and artificial intelligence platforms. The terminal may be a smartphone, tablet, laptop, digital radio receiver, desktop computer, vehicle terminal (e.g., vehicle navigation terminal, vehicle computer), smart speaker, smartwatch, etc. The terminal and server may be directly or indirectly connected via wired or wireless communication, or determined based on the actual application scenario requirements, and are not limited here.

[0050] Figure 2 This is a flowchart illustrating a device management method provided in an embodiment of this application. The subject executing this method can be a device management system. Figure 2 As shown, the method includes the following steps.

[0051] Step 201: The management device displays the configuration page for at least one production device.

[0052] The management device can display category operation controls on the configuration page. These controls are used to trigger configuration operations for the data categories to be collected from the production device. These configuration operations include at least one of adding, deleting, or editing categories. Users can configure the data categories to be collected from each production device by triggering the category operation controls. The management device responds to the configuration operations triggered by the category operation controls by obtaining the data categories configured for each production device on the configuration page.

[0053] In one possible implementation, each production device may have its own configuration page; the management application provides a device management page, through which users can access the configuration pages of each production device. For example, step 201 may include: the management device displaying a configuration entry for at least one production device on the device management page; and, in response to a triggering operation on the configuration entry of any production device, the management device displaying the configuration page for that production device. Correspondingly, the process by which the management device obtains the data category of each production device may include: in response to a configuration operation on the configuration page of that production device, the management device obtaining the data category of that production device.

[0054] In one possible implementation, the user can also configure the data storage format corresponding to each data category on the configuration page. This configuration operation may further include configuring the data storage format for each data category; correspondingly, the management device, in response to the configuration operation triggered by the category operation control, obtains the data categories of each production device configured on the configuration page and the data storage format for each data category. For example, the various data storage formats corresponding to different data categories may include, but are not limited to: integer data (e.g., byte, short, int, long), floating-point types (e.g., float, double), character types (e.g., char), boolean types (e.g., boolean), etc. In one possible example, the configuration operation may further include configuring at least one of the following for each data category: unit, calculation rules, calculation parameters, remarks, etc.; correspondingly, the management device, in response to the configuration operation triggered by the category operation control, obtains the data categories of each production device configured on the configuration page and the pre-configuration information for each data category. The pre-configuration information for each data category may include, but is not limited to, at least one of the following: data storage format, unit, calculation rules, calculation parameters, remarks, and reporting cycle for each data category. The reporting cycle can be the period during which production equipment reports attribute data belonging to the corresponding data category. For example, the reporting cycle can be the first cycle.

[0055] Figure 3 This is a schematic diagram of a device management page provided in this application. (For example...) Figure 3 As shown, the equipment management page can include the following information for each production device: device name or serial number, device ID, whether the data acquisition process for the corresponding production device is open, whether each production device is online, number of points, last online time of each production device, and data synchronization status. The equipment management page also provides entry points for management operations of each production device, such as management controls and more operation type controls corresponding to each production device in the operation column.

[0056] It should be noted that the management equipment can manage the production equipment that is connected to it. Figure 3 The device management page provides controls for adding devices and batch importing devices. Users can trigger these controls on the device management page to add or import production devices that need to be managed. The device management page can display various information about each connected production device.

[0057] in, Figure 3 The "points" in the data collection column refer to the data categories to be collected. One point represents one data category, and the number of points represents the number of data categories. The numbers in the "point count" column for each production device link to its configuration page. Users can access the configuration page for a specific production device by triggering the corresponding number in the "point count" column. For example, if production device A has 0 points, a user can trigger the number 0 to access device A's configuration page and add the necessary points.

[0058] Figure 4 This is a schematic diagram of a configuration page provided in this application. For example... Figure 4 As shown, this configuration page can be the configuration page for production equipment B. This page contains the configuration information for each point on equipment B. The point name and point alias are used to distinguish different points. The data type represents the data storage format for the corresponding point, such as double or float. This configuration page displays multiple information columns for each point, including unit, calculation rule, calculation parameters, remarks, and operations. The operation column can include edit, copy, and delete operations to facilitate users in editing, copying, or deleting existing points. The calculation rule can be a statistical algorithm for the collected point data, and the calculation parameters can be the parameters required for calculations according to this calculation rule.

[0059] Figure 5 This application provides a dynamically configured page that is being configured. For example, if a user triggers... Figure 4 Adding point controls in the configuration page will take you to... Figure 5 The dynamic configuration status is shown. Figure 5 The dynamic configuration page shows a blank line above each point, with an empty input box in each information column to allow users to configure information such as the name, alias, unit, calculation rules, calculation parameters, and remarks for newly added points. Save and cancel controls are provided in the operation column for easy saving or cancellation at any time.

[0060] like Figure 4 or Figure 5As shown, the configuration page also includes a point data preview control. This point data refers to the attribute data of each data category of the production equipment. If the point data preview control is triggered, the equipment management platform can display the point data of equipment B, which is the attribute data of equipment B in each data category.

[0061] Step 202: In response to obtaining the data category configured in the configuration page of at least one production device, the management device sends a reporting instruction to each production device and a parsing instruction to the parsing server.

[0062] The reporting instruction instructs the reporting of data to the parsing server based on the data category of the corresponding production equipment. The parsing instruction instructs the return of attribute data obtained from parsing the reported data from each production equipment. In this step, the management device can send reporting instructions to each production equipment based on the acquired data category, with each reporting instruction carrying the corresponding data category. It can also send a parsing instruction to the parsing server, carrying the data parsing protocol corresponding to each production equipment. This data parsing protocol defines the data category of the corresponding production equipment and can also define pre-configuration information for each data category, such as data storage format and unit.

[0063] In one possible approach, the management device can transmit individual attribute class files to each production device, whereby the attribute class files may include the data categories corresponding to the production device. Step 202 can then be implemented through the following steps 2021-2022:

[0064] Step 2021: Based on the data categories of each production device, the management equipment determines the corresponding attribute class file and data parsing protocol for each production device.

[0065] This data parsing protocol indicates the method for parsing attribute data obtained from the reported data of the corresponding production equipment. The management device can generate attribute class files and corresponding data parsing protocols for each production equipment based on its data categories. For example, for each production equipment, its attribute class file includes the equipment's data category; for instance, for equipment A, its attribute class file includes the names of points such as point 1 and point 2.

[0066] In one possible example, the data parsing protocol includes at least one data category corresponding to the production equipment and a data storage format for each data category. For example, for equipment A, the data parsing protocol defines point 1, point 2, and the data storage format for point 1 as float and point 2 as double.

[0067] In another possible example, the data parsing protocol may also include the data categories corresponding to the production equipment and pre-configured information for each data category. For example, for equipment A, in addition to including the location and data storage format, its data parsing protocol may also define the units, calculation rules, calculation parameters, etc., corresponding to location 1 and location 2.

[0068] Step 2022: The management device sends a reporting instruction to each production device and a parsing instruction to the parsing server.

[0069] Each production device's reporting instruction carries its corresponding attribute class file. The parsing instruction carries the data parsing protocol for each production device. The management device can generate its own attribute class file and data parsing protocol based on the data categories of each production device. For example, the data parsing protocol can be a parsing function, which can define data categories to extract attribute data under various data categories from the reported data. For instance, if the data category for the cutting machine includes yield rate, the parsing function can be used to parse from the reported data to determine that the hourly yield rate of the cutting machine over the past 3 hours is 80%, 90%, and 88%.

[0070] In one possible example, a protocol type can be defined for each production device, allowing the parsing server to select the corresponding data parsing protocol for parsing. For instance, for each production device, its attribute class file includes the data category and the corresponding protocol type. Accordingly, the parsing instruction also carries the correspondence between the protocol types and data parsing protocols for each production device. For example, device A's attribute class file includes type1, and device B's attribute class file includes type2. The parsing instruction can carry this correspondence: device A corresponds to protocol type1, and device B corresponds to protocol type2. Based on this, the parsing server can select the data parsing protocol matching the corresponding protocol type to parse the data reported by each production device.

[0071] In one possible implementation, the management device can not only send attribute class files to the production devices, but also specify the storage path of the attribute class files on the production devices; and it can also specify the storage path of the data parsing protocol on the parsing server. For example, in step 202, the implementation of the management device sending reporting instructions to each production device includes: the management device sending reporting instructions to each production device based on the parameter loading path and the corresponding attribute class files of each production device. The reporting instruction further instructs the reporting of data to the parsing server based on the data category in the parameter loading path. The parameter loading path is the path where the category parameters are loaded in the data reporting program of each production device.

[0072] In this application, each production unit can be pre-configured with a data reporting program, which includes execution logic for reporting data of the corresponding data category to the parsing server. Each production device can start and run the data reporting program to complete the data reporting process. The execution logic of this data reporting program may include category loading logic, which refers to loading the required data categories from the parameter loading path. Based on this, the management device can store attribute class files in the parameter loading path; so that after the production device starts the data reporting program, it can execute the category loading logic to load the data categories from the parameter loading path and complete the data reporting process.

[0073] For example, in step 202, the implementation of the management device sending a parsing instruction to the parsing server includes: the management device sending a parsing instruction to the parsing server based on the protocol storage path and the data parsing protocol corresponding to each production device. The parsing instruction further instructs the parsing of the reported data of the corresponding production device based on the various data parsing protocols in the protocol storage path.

[0074] In this application, the parsing server can parse the data reported by each production device by calling an interface. The interface is pre-configured with the data parsing protocol corresponding to each production device. The parsing server can update this interface in real time; for example, it can periodically scan the protocol storage path to update the configured data parsing protocol in the interface. Based on this, the management device can store the data parsing protocol in the periodically scanned path, i.e., the protocol storage path.

[0075] In one possible example, the steps for the management device to obtain the parameter loading path and protocol storage path include: the management device obtaining the parameter loading path of each production device and obtaining the protocol storage path of the parsing server. For example, users can define the parameter loading path in the category loading logic. After each production device is connected to the management device, each production device can send its own parameter loading path to the management device. The parsing server can be pre-configured with a periodically scanned protocol storage path. After the parsing server is connected to the management device, it can send the protocol storage path to the management device.

[0076] In one possible implementation, the management device can also send update prompts to the production devices and the parsing server in real time based on update operations in the configuration page. This update process may include: in response to an update operation in the configuration page of any production device, the management device sends a first update instruction to that production device and a second update instruction to the parsing server, based on the update category and update protocol, respectively. The first update instruction instructs the updating of data categories located in the parameter loading path, such as attribute files, based on the update category. The second update instruction instructs the updating of the data parsing protocol located in the protocol storage path based on the update protocol.

[0077] In one possible implementation, the device management system of this application further includes a server, which may be a backend server for a management application. The management device can use this server to complete the process of sending reporting instructions and parsing instructions. For example, step 202 may include: for any production device, in response to a target operation triggered on the configuration page of that production device, the management device sends a data collection instruction to a cloud server based on the data category configured on the configuration page of that production device; the management device then sends a reporting instruction to the production device and a parsing instruction to the parsing server via the cloud server. The target operation may be a data viewing operation, a configuration operation, or a submission operation following a configuration operation, etc.

[0078] For example, such as Figure 5 As shown, if detected Figure 5 When the location data preview control on the configuration page is triggered, the management device can send a data acquisition command to the server based on the data category of the production equipment. This data acquisition command instructs the collection of attribute data for the production equipment within the configured data category. For example, the data acquisition command can carry the configured data category. Alternatively, the data acquisition category can also carry pre-configured information for each data category, such as data storage format and unit.

[0079] Step 203: Upon receiving the attribute data of each production device returned by the parsing server, the management device displays the attribute data of each production device on the device management page and manages each production device based on the attribute data.

[0080] The management device receives and parses attribute data for each production device sent by the server. In response to a data viewing operation triggered on a target page of the management application, the attribute data for each production device is displayed on the device management page. This target page can be any page, including the device management page, the configuration page, or the data viewing entry point. For example, a point data preview button can be triggered on the configuration page to access the device management page and display the attribute data there.

[0081] For example, the management device can execute a matching management process on the production equipment based on attribute data. For instance, for any production equipment among the various production devices, if the attribute data of that production equipment in each data category meets a pre-configured first condition, the management device can perform a first management operation on that production equipment. The first condition includes, but is not limited to: being within the normal range, and the attribute data being within the normal range for a consecutive first number of reporting cycles. The first management operation includes, but is not limited to: controlling the production equipment to continue reporting data according to the first cycle, increasing the first cycle to a second cycle, and controlling the production equipment to report data in the second cycle. It should be noted that the first cycle is the cycle in which the production equipment reports attribute data. In step 201, the user can configure the first cycle corresponding to each data category for the production equipment on the configuration page, so that the production equipment reports data according to the first cycle corresponding to each data category. If the attribute data is normal, the management device can control the production equipment to increase the reporting cycle, thereby saving traffic, saving storage costs, and reducing the data processing pressure on the parsing server.

[0082] For example, for any production equipment among the various generating devices, if the attribute data of that production equipment in any data category meets the pre-configured second condition, the management device can perform a second management operation on that production equipment. The second condition includes, but is not limited to: being within the abnormal range, or the attribute data being within the abnormal range for a second consecutive number of reporting cycles; the second management operation includes, but is not limited to: displaying an anomaly prompt message, reducing the first cycle corresponding to that data category to a third cycle and controlling the production equipment to report the attribute data of that data category in the third cycle, controlling the production equipment to suspend operation, controlling the production equipment to report equipment environmental data, and controlling the production equipment to issue an anomaly prompt voice signal. For example, equipment environmental data may include equipment temperature, wear rate of some mechanical parts in the equipment, and service life.

[0083] In one possible implementation, the management device can also provide statistical results on the attribute data to enable device management using these results. For example, step 203 can be replaced by step 204:

[0084] Step 204: The management device responds to the receipt of attribute data of each production device returned by the parsing server, performs statistics based on the attribute data of each production device, displays the attribute data of each production device and the statistical results on the device management page, and manages the corresponding production device based on the attribute data and statistical results of each production device.

[0085] For example, after receiving attribute data of various production devices sent by the parsing server, the management device can display attribute data and statistical data based on the triggering of a data viewing operation. Alternatively, it can first display attribute data based on the triggering of a data viewing operation; then, when a statistical operation is detected, it can read attribute data from the database, perform statistical analysis, and display the resulting statistical results.

[0086] In one possible implementation, the management device can also store the data reported by each production device, for example, by storing it in a time-series database according to timestamps, to facilitate subsequent statistics or time-based data queries. This process may include: for any production device, the management device stores the attribute data in a time-series database within a cloud-native service based on the timestamp of each data entry in the attribute data of that production device. Correspondingly, the process of reading, statistically analyzing, and displaying data from the time-series database may include: in response to a data display request for any production device, the management device verifies the data display request based on the device permission information configured in the cloud-native service; if the permission verification is successful, the management device reads each data entry from the time-series database for that production device and performs statistical analysis on each data entry based on its timestamp, obtaining at least one statistical result; the management device then displays this at least one statistical result on the device management page.

[0087] like Figure 6As shown, the device management system can include a web interface, cloud platform, edge platform, device platform, and cloud-native Pass. The web interface refers to the management device providing the management application; the cloud platform can be the backend server for this management application; the edge platform can be a parsing server providing parsing services; and the device platforms can be various production devices connected to the management application. The cloud platform provides a protocol service, which can be used to obtain the data categories input from the web interface and automatically generate attribute class files for each production device, as well as the data parsing protocol (such as parsing functions) for the parsing server. The edge platform provides an Analysis service, which can be used to parse data based on the parsing functions generated by the cloud platform. Device platforms can initiate a data reporting service, dynamically loading attribute class files through the SDK (Software Development Kit) provided by the cloud. These attribute class files can be in JSON (JavaScript Object Notation) format. The production devices then obtain the corresponding attribute data based on the data categories in the attribute class files and report the obtained attribute data to the edge platform's parsing service. The parsing service then parses the data using the parsing functions and reports the parsed attribute data to the cloud platform. Attribute data can be directly displayed in the cloud, and it can also be stored in a time-series database provided by CloudNative Pass, categorized by timestamps. CloudNative Pass can store attribute data in time-series databases such as InfluxDB (an open-source time-series database) and ClickHouse. For example, calculated data can also be stored in the database, from which both the web application and the compute service can retrieve data. Statistical analysis can be performed on demand, providing data for configuration and display; the statistical results can be stored in the database provided by CloudNative Pass.

[0088] The equipment management method provided in this application displays a configuration page for at least one type of production equipment, facilitating user configuration of complex and diverse production equipment in industrial production scenarios. When the data category configured on the configuration page of at least one type of production equipment is obtained, a reporting command can be sent to each production equipment, and a parsing command can be sent to the parsing server. This enables each production equipment to report data to the parsing server based on its respective data category, and the parsing server automatically returns the parsed attribute data. This achieves automated data collection for complex and diverse production equipment in industrial production scenarios. Furthermore, the attribute data of each production equipment can be displayed to facilitate equipment management based on the displayed data. By flexibly configuring data categories through the configuration page and automatically triggering device reporting and parsing server automatic parsing, a reliable equipment management process is formed by managing equipment, production equipment, and the parsing server, improving the efficiency, flexibility, and reliability of equipment management.

[0089] Figure 7 This application provides a device management method, in which the execution entity is a parsing server. For example... Figure 7 As shown, the method includes:

[0090] Step 701: In response to a parsing instruction triggered by the configuration page of at least one production device, the parsing server stores the data parsing protocol corresponding to each of the at least one production device.

[0091] The parsing instruction specifies the return of attribute data obtained by parsing the reported data from each production device. For example, the parsing instruction may carry the data parsing protocol corresponding to each production device; alternatively, it may carry the correspondence between protocol types and data parsing protocols. In one possible implementation, the parsing instruction further instructs the parsing of the reported data from the corresponding production device based on the various data parsing protocols in the protocol storage path. For example, the parsing instruction may also carry the protocol storage path. Therefore, the process by which the parsing server stores the data parsing protocols corresponding to each production device includes: the parsing server storing the correspondence between the protocol types and data parsing protocols of each production device in the protocol storage path.

[0092] In one possible example, the parsing server can perform the parsing process of reported data from various production devices by calling a generic interface. The parsing server can periodically scan the protocol storage path to update the data parsing protocols included in the generic interface in real time. This process may include: the parsing server periodically scanning each data parsing protocol in the protocol storage path; and the parsing server adding the new data parsing protocol and its corresponding new protocol type to its generic interface in response to detecting a new data parsing protocol in the protocol storage path.

[0093] Step 702: In response to receiving the reported data from any production device, the parsing server parses the reported data based on the data parsing protocol corresponding to that production device to obtain the attribute data of that production device.

[0094] In one possible implementation, for data reported by any production device, the parsing server can parse the reported data based on the protocol type corresponding to that production device by calling a generic interface to obtain the attribute data of that device. The generic interface includes at least one protocol type for the production device and its corresponding data parsing protocol. The data parsing protocol includes at least one data category for that production device and a data storage format for each data category. For example, if any production device sends a reporting data packet to the parsing server, the reporting data packet includes the reported data and the protocol type of the production device. The parsing server can extract the protocol type from the reporting data packet. For example, the parsing server can extract the attribute data for each data category from the reported data and store the attribute data for each data category according to the corresponding data storage format.

[0095] Step 703: Parse the attribute data of any production device returned by the server to the management device.

[0096] The parsing server can return data packets from each production device to the management device. For any given production device, the data packet includes attribute data encapsulated according to the data storage format of each data category for that production device.

[0097] like Figure 8 As shown, by obtaining the data category entered on the web and sending the data category to the Protocol service in the cloud, the Protocol service generates a data parsing protocol and stores the data parsing protocol in the protocol storage path, such as the root path where the Analysis service on the edge is located. The edge starts a scheduled task through the Analysis service to periodically scan the files under the root path. If a new data parsing protocol is stored in this path, the new data parsing protocol will be added to the generic interface of the Analysis service. When the production device reports data, it calls the reflection interface through the Analysis service to automatically parse the reported data to obtain attribute data, and reports it to the statistics service and configuration display service in the cloud for subsequent statistics and display.

[0098] Figure 9 This application provides an equipment management method, the subject of which is production equipment, which can be any one of various production equipment. For example... Figure 9 As shown, the method includes:

[0099] Step 901: Any production equipment starts its data reporting program.

[0100] It should be noted that the at least one production device is a device that is connected to the management device and managed by the management device based on the attribute data displayed on the device management page. For example, the at least one production device can access the management application of the management device, and the management device can display information about each connected production device on the device management page.

[0101] Step 902: In response to a reporting instruction triggered by the configuration page of any production device displayed by the management device, any production device stores the attribute class file of that production device sent by the management device in the parameter loading path.

[0102] This attribute class file includes the data category for any of the production devices. The reporting instruction directs data to be reported to the parsing server based on the data category of any of the production devices.

[0103] Step 903: Any production equipment loads the attribute class file from the parameter loading path based on the data reporting program, and sends the reported data to the parsing server based on the data categories included in the attribute class file.

[0104] For example, production equipment can use MQTT (Message Queuing Telemetry Transport) for reporting. MQTT is a client-server message publish / subscribe protocol. It is lightweight, simple, open, and easy to implement, making it widely applicable.

[0105] In this application, IoT (Internet of Things) technology can be used to connect various production equipment to management equipment so that the production equipment can report data. IoT technology uses various information sensors, laser scanners and other devices and technologies to collect data in real time from any equipment or process that needs to be connected and interacted with.

[0106] The device management method of this application can adopt PaaS (Platform as a Service) technology to provide the platform for developing and running the device management method as a service to users.

[0107] like Figure 10As shown, the cloud automatically generates attribute class files based on data categories and distributes the corresponding attribute class files to the production equipment side using the equipment information of each production equipment, such as equipment ID and TCP / IP port. For example, the attribute class files can be stored in the specified parameter loading path of the production equipment. When the production equipment needs to report data, it can load the required data category from the parameter loading path, obtain the attribute data according to the loaded data category, and then call the sending interface to send it to the Analysis service of the parsing server.

[0108] like Figure 11 As shown, when a user needs to update the data categories for production equipment, such as adding, modifying, or deleting data categories, the user only needs to perform the corresponding add, modify, or delete operations on the visual configuration page. After the operation, the updated data categories will be sent to the production equipment side, and the corresponding updated data parsing protocol will also be sent to the parsing server. The parsing server will periodically scan the data parsing protocol to update the generic interface. After the production equipment reports data, the Analysis service parses and reports the data according to the data parsing protocol in the latest generic interface.

[0109] The following is based on Figure 12 The flowchart shown illustrates the process of equipment management. For example... Figure 12 As shown, the equipment management method includes the following process:

[0110] 1. Device attributes are entered via web service. These device attributes refer to the data categories for which attribute data needs to be collected.

[0111] 2.1. Generate a data parsing protocol through the Protocol service and send the data parsing protocol to the parsing server.

[0112] 2.2. Generate attribute class files through the Protocol service and distribute the attribute class files to the production equipment.

[0113] 3. The parsing server loads the corresponding data parsing protocol from the protocol storage path and adds the data parsing protocol to the generic interface.

[0114] 4. Production equipment loads data categories from the parameter loading path.

[0115] 5. Production equipment reports data to the parsing server based on data category.

[0116] 6. The parsing server uses the Analysis service to call the generic interface to parse the data and sends the parsed attribute data to the server.

[0117] 7. The server stores attribute data in a cloud-native time-series database, such as InfluxDB, and performs configuration rendering on the web interface, such as previewing the collected attribute data. The statistics service can read data from the time-series database and perform statistics. The statistical results can be stored in a database, such as MySQL, for display on the web interface.

[0118] This application's equipment management method, including cloud-native cloud-edge-device data acquisition and parsing processes, can handle more complex production scenarios, such as automatically collecting attribute data from various types of production equipment, achieving rapid and flexible data collection from industrial equipment. For example, through cloud-native cloud-edge-device data acquisition and parsing, the entire data acquisition process can be completed by entering data categories once in the cloud, achieving the goal of one-time entry and automatic collection, making production equipment data acquisition more efficient and flexible. Furthermore, through cloud-native cloud-edge-device data acquisition and parsing processes, it can also adapt to complex and ever-changing scenarios, such as constantly updated data categories and the addition of new production equipment. For data category updates, only the data category needs to be modified in the cloud, which will be synchronized to the production equipment side and the parsing server side, achieving the effect of one-time modification and automatic synchronization, improving equipment management efficiency, flexibility, and convenience. In addition, the cloud-native Pass component supports privatization, verifying user permissions before providing data access, facilitating user-defined deployment based on needs, ensuring the secure and efficient storage of production equipment attribute data, and improving the reliability of equipment management.

[0119] The device management method provided in this application involves technical fields such as cloud technology and cloud storage, such as using cloud technology to call services on the cloud and edge; and using cloud storage technology to store attribute data and statistical results.

[0120] As we can understand, cloud computing is a computing model that distributes computing tasks across a resource pool composed of a large number of computers, enabling various application systems to obtain computing power, storage space, and information services as needed. The network providing these resources is called the "cloud." From the user's perspective, the resources in the "cloud" are infinitely scalable, readily available, on-demand, expandable, and pay-as-you-go.

[0121] As a provider of fundamental cloud computing capabilities, a cloud resource pool (referred to as a cloud platform, generally called an IaaS (Infrastructure as a Service) platform) is established. Various types of virtual resources are deployed in the resource pool for external customers to choose from. The cloud resource pool mainly includes: computing devices (virtualized machines containing operating systems), storage devices, and network devices.

[0122] Based on logical function, a PaaS (Platform as a Service) layer can be deployed on top of the IaaS (Infrastructure as a Service) layer, and a SaaS (Software as a Service) layer can be deployed on top of the PaaS layer. Alternatively, SaaS can be deployed directly on top of IaaS. PaaS is a platform for running software, such as databases and web containers. SaaS refers to various types of business software, such as web portals and bulk SMS senders. Generally speaking, SaaS and PaaS are upper layers compared to IaaS.

[0123] It is understandable that cloud storage is a new concept that has been extended and developed from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as a storage system) refers to a storage system that uses cluster applications, grid technology and distributed storage file systems to bring together a large number of storage devices of various types in the network (storage devices are also called storage nodes) to work together through application software or application interfaces to provide data storage and business access functions to the outside world.

[0124] Currently, the storage method of storage systems is as follows: Logical volumes are created. During the creation of a logical volume, physical storage space is allocated to each logical volume. This physical storage space may consist of a single storage device or the disks of several storage devices. Clients store data on a logical volume, which means storing the data on the file system. The file system divides the data into many parts, each part being an object. Each object contains not only the data but also additional information such as a data identifier (ID, ID entity). The file system writes each object to the physical storage space of that logical volume and records the storage location information of each object. Therefore, when a client requests access to data, the file system can allow the client to access the data based on the storage location information of each object.

[0125] The process by which a storage system allocates physical storage space to a logical volume is as follows: the physical storage space is pre-divided into strips according to the capacity estimate of the objects stored in the logical volume (this estimate often has a large margin relative to the actual capacity of the objects to be stored) and the grouping of Redundant Array of Independent Disks (RAID). A logical volume can be understood as a strip, thus allocating physical storage space to the logical volume.

[0126] Figure 13 This is a schematic diagram of a device management system provided in an embodiment of this application. Figure 13As shown, the equipment management system includes a management device 1301, a parsing server 1302, and at least one production device 1303;

[0127] The management device 1301 is used for:

[0128] Displays the configuration page for at least one production device;

[0129] In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device and a parsing instruction is sent to the parsing server. The reporting instruction instructs to report data to the parsing server based on the data category of the corresponding production device, and the parsing instruction instructs to return the attribute data obtained by parsing the reported data of each production device.

[0130] In response to receiving the attribute data of each production device returned by the parsing server, the attribute data of each production device is displayed on the device management page, and each production device is managed based on the attribute data.

[0131] The DNS server 1302 is used for:

[0132] In response to a parsing instruction triggered by the configuration page of at least one production device, the data parsing protocol corresponding to each of the at least one production device is stored, and the parsing instruction indicates the return of attribute data obtained by parsing the reported data of each production device;

[0133] In response to receiving data reported by any production equipment, the reported data is parsed based on the data parsing protocol corresponding to that production equipment to obtain the attribute data of that production equipment;

[0134] Return the attribute data of any production equipment to the management device.

[0135] Wherein, for any one of the at least one production equipment 1303, the any one production equipment 1303 is used for:

[0136] Initiate the data reporting program for any production equipment, wherein the at least one production equipment is connected to the management equipment and managed by the management equipment based on the attribute data displayed on the equipment management page;

[0137] In response to a reporting instruction triggered by the configuration page of any production device displayed by the management device, the attribute class file of any production device sent by the management device is stored in the parameter loading path. The attribute class file includes the data category of any production device. The reporting instruction instructs to report data to the parsing server based on the data category of any production device.

[0138] Based on this data reporting program, the attribute class file is loaded from the parameter loading path, and the reported data is sent to the parsing server based on the data categories included in the attribute class file.

[0139] In one possible implementation, when the management device 1301 receives data categories configured in the configuration page of at least one production device, sends reporting instructions to each production device, and sends parsing instructions to the parsing server, it is specifically used for:

[0140] Based on the data categories of each production equipment, the corresponding attribute class file and data parsing protocol for each production equipment are determined. The data parsing protocol indicates the parsing method for parsing attribute data from the reported data of the corresponding production equipment.

[0141] Each production device sends a reporting instruction, and each production device's reporting instruction carries the attribute class file corresponding to that production device.

[0142] Send a parsing command to the parsing server. This parsing command carries the data parsing protocol corresponding to each production device.

[0143] In one possible implementation, the attribute class file for each production device includes the data category of the production device and the protocol type corresponding to the production device;

[0144] The parsing instruction also carries the correspondence between the protocol type of each production device and the data parsing protocol;

[0145] The data parsing protocol includes at least one data category corresponding to the production equipment and the data storage format for each data category.

[0146] In one possible implementation, the management device 1301 is also used for:

[0147] Obtain the parameter loading path for each production device. This parameter loading path is the path for loading category parameters in the data reporting program of each production device.

[0148] Obtain the protocol storage path of the parsing server;

[0149] When the management device 1301 sends reporting instructions to each production device, it is specifically used for:

[0150] Based on the parameter loading path of each production device and its corresponding attribute class file, a reporting instruction is sent to each production device. The reporting instruction also instructs the data to be reported to the parsing server based on the data category in the parameter loading path.

[0151] When the management device 1301 sends a parsing command to the parsing server, it is specifically used for:

[0152] Based on the protocol storage path and the data parsing protocol corresponding to each production device, a parsing instruction is sent to the parsing server. The parsing instruction also instructs the parsing of the reported data of the corresponding production device based on the data parsing protocol in the protocol storage path.

[0153] In one possible implementation, the management device 1301 is also used for:

[0154] In response to an update operation on the configuration page of any production device, a first update command is sent to that production device and a second update command is sent to the parsing server, based on the update category and update protocol.

[0155] The first update instruction indicates that the data category located in the parameter loading path be updated based on the update category, and the second update instruction indicates that the data parsing protocol located in the protocol storage path be updated based on the update protocol.

[0156] In one possible implementation, the management device 1301 displays a configuration page for at least one production device, specifically for:

[0157] Display the configuration entry for at least one production device on the equipment management page;

[0158] In response to a trigger operation on the configuration entry of any production device, the configuration page of that production device is displayed;

[0159] In response to a configuration operation on the configuration page of any production device, the data category of any production device is obtained, the configuration operation including at least one of adding a category, deleting a category, or editing a category.

[0160] In one possible implementation, when the management device 1301 receives data categories configured in the configuration page of at least one production device, sends reporting instructions to each production device, and sends parsing instructions to the parsing server, it is specifically used for:

[0161] For any production equipment, in response to a data viewing operation triggered on the configuration page of that production equipment, a data collection command is sent to the cloud server based on the data category configured on the configuration page of that production equipment.

[0162] The cloud server sends reporting instructions to any of the production devices and parsing instructions to the parsing server.

[0163] In one possible implementation, the management device 1301 is also used for:

[0164] For any production equipment, based on the timestamp of each data item in the attribute data of that production equipment, the attribute data is stored in the time-series database in the cloud-native service;

[0165] In response to a data display request for any production device, the permission of the data display request is verified based on the device permission information configured in the cloud-native service.

[0166] If the permission verification is successful, read each data entry of any production device from the time-series database, and perform statistics on each data entry based on its timestamp to obtain at least one statistical result;

[0167] This device management page displays at least one statistical result.

[0168] In one possible implementation, when the parsing server 1302 parses the reported data based on the data parsing protocol corresponding to any production device to obtain the attribute data of that production device, it is specifically used for:

[0169] Based on the protocol type corresponding to any production equipment, a generic interface is called to parse the reported data and obtain the attribute data of any equipment. The generic interface includes at least one protocol type of the production equipment and its corresponding data parsing protocol. The data parsing protocol includes at least one data category of the production equipment and the data storage format of each data category.

[0170] In one possible implementation, the parsing instruction also instructs the parsing protocol in the storage path of the protocol to parse the reported data of the corresponding production equipment;

[0171] When storing the data parsing protocols corresponding to each production device, the parsing server 1302 is specifically used for:

[0172] The protocol storage path stores the correspondence between the protocol types of each production device and the data parsing protocol;

[0173] Periodically scan the various data parsing protocols in the protocol's storage path;

[0174] In response to the detection of a new data parsing protocol in the protocol storage path, the new data parsing protocol and its corresponding new protocol type are added to the generic interface of the parsing server.

[0175] This application displays a configuration page for at least one type of production equipment, facilitating user configuration of complex and diverse production equipment in industrial production scenarios. When the data category configured on the configuration page of at least one type of production equipment is obtained, reporting instructions can be sent to each production equipment, and parsing instructions can be sent to the parsing server. This allows each production equipment to report data to the parsing server based on its respective data category, and the parsing server to automatically return the parsed attribute data. This achieves automated data collection for complex and diverse production equipment in industrial production scenarios. Furthermore, the attribute data of each production equipment can be displayed to facilitate equipment management based on the displayed data. By flexibly configuring data categories through the configuration page and automatically triggering device reporting and parsing server automatic parsing, a reliable equipment management process is formed by managing equipment, production equipment, and the parsing server, improving the efficiency, flexibility, and reliability of equipment management.

[0176] The system in this application embodiment can execute the method provided in this application embodiment, and the implementation principle is similar. The actions performed by each module in the system of each embodiment of this application correspond to the steps in the method of each embodiment of this application. For detailed functional descriptions of each device in the system, please refer to the descriptions in the corresponding methods shown above, which will not be repeated here.

[0177] Figure 14 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. For example... Figure 14 As shown, the computer device includes: a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of the device management method, which, compared with related technologies, can achieve:

[0178] The equipment management method provided in this application displays a configuration page for at least one type of production equipment, facilitating user configuration of complex and diverse production equipment in industrial production scenarios. When the data category configured on the configuration page of at least one type of production equipment is obtained, a reporting command can be sent to each production equipment, and a parsing command can be sent to the parsing server. This enables each production equipment to report data to the parsing server based on its respective data category, and the parsing server automatically returns the parsed attribute data. This achieves automated data collection for complex and diverse production equipment in industrial production scenarios. Furthermore, the attribute data of each production equipment can be displayed to facilitate equipment management based on the displayed data. By flexibly configuring data categories through the configuration page and automatically triggering device reporting and parsing server automatic parsing, a reliable equipment management process is formed by managing equipment, production equipment, and the parsing server, improving the efficiency, flexibility, and reliability of equipment management.

[0179] In one alternative embodiment, a computer device is provided, such as Figure 14 As shown, Figure 14 The computer device 1400 shown includes a processor 1401 and a memory 1403. The processor 1401 and the memory 1403 are connected, for example, via a bus 1402. Optionally, the computer device 1400 may further include a transceiver 1404, which can be used for data interaction between the computer device and other computer devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 1404 is not limited to one type, and the structure of the computer device 1400 does not constitute a limitation on the embodiments of this application.

[0180] Processor 1401 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 1401 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0181] Bus 1402 may include a pathway for transmitting information between the aforementioned components. Bus 1402 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 1402 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0182] The memory 1403 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0183] The memory 1403 is used to store computer programs that execute the embodiments of this application, and the execution is controlled by the processor 1401. The processor 1401 is used to execute the computer programs stored in the memory 1403 to implement the steps shown in the foregoing method embodiments.

[0184] Electronic devices include, but are not limited to, servers, terminals, or cloud computing center equipment.

[0185] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments.

[0186] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.

[0187] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. The terms “comprising” and “including” as used in the embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, or operation, but do not exclude implementation as other features, information, data, steps, or operations supported by this art.

[0188] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.

[0189] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0190] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A method for managing equipment, characterized in that, The method includes: Displays the configuration page for at least one production device; In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device and a parsing instruction is sent to the parsing server. The reporting instruction instructs to report data to the parsing server based on the data category of the corresponding production device, and the parsing instruction instructs to return the attribute data obtained by parsing the reported data of each production device. In response to receiving attribute data of each production device returned by the parsing server, the attribute data of each production device is displayed on the device management page, and each production device is managed based on the attribute data.

2. The method according to claim 1, characterized in that, In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device, and a parsing instruction is sent to the parsing server, including: Based on the data categories of each production equipment, the corresponding attribute class file and data parsing protocol for each production equipment are determined. The data parsing protocol indicates the parsing method for parsing attribute data from the reported data of the corresponding production equipment. Each production device sends a reporting instruction, and each production device's reporting instruction carries the attribute class file corresponding to that production device. A parsing instruction is sent to the parsing server, the parsing instruction carrying the data parsing protocol corresponding to each production device.

3. The method according to claim 2, characterized in that, The attribute class file for each production device includes the data category of the production device and the corresponding protocol type of the production device; The parsing instructions also carry the correspondence between the protocol types of each production device and the data parsing protocol; The data parsing protocol includes at least one data category corresponding to the production equipment and the data storage format for each data category.

4. The method according to claim 2 or 3, characterized in that, The method further includes: Obtain the parameter loading path for each production device, where the parameter loading path is the path for loading category parameters in the data reporting program of each production device; Obtain the protocol storage path of the parsing server; The step of sending reporting instructions to each production device includes: Based on the parameter loading path of each production device and its corresponding attribute class file, a reporting instruction is sent to each production device. The reporting instruction also instructs to report data to the parsing server based on the data category in the parameter loading path. Sending the parsing instruction to the parsing server includes: Based on the protocol storage path and the data parsing protocol corresponding to each production device, a parsing instruction is sent to the parsing server. The parsing instruction also instructs the parsing of the reported data of the corresponding production device based on the data parsing protocol in the protocol storage path.

5. The method according to claim 4, characterized in that, The method further includes: In response to an update operation on the configuration page of any production device, a first update instruction is sent to the production device and a second update instruction is sent to the parsing server, based on the update category and update protocol, respectively. The first update instruction indicates that the data category located in the parameter loading path is updated based on the update category, and the second update instruction indicates that the data parsing protocol located in the protocol storage path is updated based on the update protocol.

6. The method according to claim 1, characterized in that, The configuration page for displaying at least one production device includes: Display the configuration entry for at least one production device on the equipment management page; In response to a trigger operation on the configuration entry of any production equipment, the configuration page of that production equipment is displayed; The method further includes: In response to a configuration operation on the configuration page of any production device, the data category of the production device is obtained, wherein the configuration operation includes at least one of adding a category, deleting a category, or editing a category.

7. The method according to claim 1 or 6, characterized in that, In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device, and a parsing instruction is sent to the parsing server, including: For any production equipment, in response to a data viewing operation triggered on the configuration page of the production equipment, a data collection command is sent to the cloud server based on the data category configured on the configuration page of the production equipment. The cloud server sends a reporting command to any of the production devices and a parsing command to the parsing server.

8. The method according to claim 1, characterized in that, The method further includes: For any production equipment, based on the timestamp of each data item in the attribute data of the production equipment, the attribute data is stored in the time-series database in the cloud-native service; In response to a data display request for any of the production devices, the data display request is verified based on the device permission information configured in the cloud-native service. If the permission verification is successful, read each piece of data from the time-series database for any of the production devices, and perform statistics on each piece of data based on the timestamp of each piece of data to obtain at least one statistical result; The device management page displays at least one of the statistical results.

9. A method for managing equipment, characterized in that, The method includes: In response to a parsing instruction triggered by the configuration page of at least one production device, the data parsing protocol corresponding to each of the at least one production device is stored, and the parsing instruction indicates the return of attribute data obtained by parsing the reported data of each production device; In response to receiving data reported by any production equipment, the reported data is parsed based on the data parsing protocol corresponding to the production equipment to obtain the attribute data of the production equipment. Return the attribute data of any of the production equipment to the management device.

10. The method according to claim 9, characterized in that, The reported data is parsed based on the data parsing protocol corresponding to any of the production equipment to obtain the attribute data of any of the production equipment, including: Based on the protocol type corresponding to any of the production devices, a generic interface is invoked to parse the reported data to obtain the attribute data of any of the production devices. The generic interface includes at least one protocol type of the production device and its corresponding data parsing protocol. The data parsing protocol includes at least one data category of the production device and the data storage format of each data category.

11. The method according to claim 9 or 10, characterized in that, The parsing instruction also instructs each data parsing protocol in the protocol storage path of the parsing server to parse the reported data of the corresponding production equipment. The data parsing protocol for storing each of the at least one production device includes: The protocol storage path stores the correspondence between the protocol types of each production device and the data parsing protocol. The method further includes: Periodically scan each data parsing protocol in the protocol storage path; In response to the detection of a new data parsing protocol in the protocol storage path, the new data parsing protocol and its corresponding new protocol type are added to the generic interface of the parsing server.

12. A method for managing equipment, characterized in that, The method includes: For any one of the at least one production equipment, initiate the data reporting program for that production equipment, wherein the at least one production equipment is a device that has established a connection with the management equipment and is managed by the management equipment based on the attribute data displayed on the equipment management page; In response to a reporting instruction triggered by a configuration page of any production device displayed by the management device, the attribute class file of the production device sent by the management device is stored in the parameter loading path. The attribute class file includes the data category of the production device. The reporting instruction instructs to report data to the parsing server based on the data category of the production device. Based on the data reporting program, the attribute class file is loaded from the parameter loading path, and the reported data is sent to the parsing server based on the data categories included in the attribute class file.

13. An equipment management system, characterized in that, The equipment management system includes management equipment, a parsing server, and at least one production device; the management equipment is used for: Displays the configuration page for at least one production device; In response to obtaining the data category configured in the configuration page of at least one production device, a reporting instruction is sent to each production device and a parsing instruction is sent to the parsing server. The reporting instruction instructs to report data to the parsing server based on the data category of the corresponding production device, and the parsing instruction instructs to return the attribute data obtained by parsing the reported data of each production device. In response to receiving attribute data of each production device returned by the parsing server, the attribute data of each production device is displayed on the device management page, and each production device is managed based on the attribute data.

14. The equipment management system according to claim 13, characterized in that, The parsing server is used for: In response to a parsing instruction triggered by the configuration page of at least one production device, the data parsing protocol corresponding to each of the at least one production device is stored, and the parsing instruction indicates the return of attribute data obtained by parsing the reported data of each production device; In response to receiving data reported by any production equipment, the reported data is parsed based on the data parsing protocol corresponding to the production equipment to obtain the attribute data of the production equipment. Return the attribute data of any of the production equipment to the management device.

15. The equipment management system according to claim 14, characterized in that, For any one of the at least one production equipment, the any one production equipment is used for: Initiate the data reporting program of any production equipment, wherein the at least one production equipment is a device that is connected to the management equipment and managed by the management equipment based on the attribute data displayed in the equipment management page; In response to a reporting instruction triggered by a configuration page of any production device displayed by the management device, the attribute class file of the production device sent by the management device is stored in the parameter loading path. The attribute class file includes the data category of the production device. The reporting instruction instructs to report data to the parsing server based on the data category of the production device. Based on the data reporting program, the attribute class file is loaded from the parameter loading path, and the reported data is sent to the parsing server based on the data categories included in the attribute class file.

16. The equipment management system according to claim 13, characterized in that, When the management device, in response to obtaining the data category configured in the configuration page of at least one production device, sends a reporting instruction to each production device and a parsing instruction to the parsing server, it is specifically used for: Based on the data categories of each production equipment, the corresponding attribute class file and data parsing protocol for each production equipment are determined. The data parsing protocol indicates the parsing method for parsing attribute data from the reported data of the corresponding production equipment. Each production device sends a reporting instruction, and each production device's reporting instruction carries the attribute class file corresponding to that production device. A parsing instruction is sent to the parsing server, the parsing instruction carrying the data parsing protocol corresponding to each production device.

17. The equipment management system according to claim 16, characterized in that, The attribute class file for each production device includes the data category of the production device and the corresponding protocol type of the production device; The parsing instructions also carry the correspondence between the protocol types of each production device and the data parsing protocol; The data parsing protocol includes at least one data category corresponding to the production equipment and the data storage format for each data category.

18. The equipment management system according to claim 16 or 17, characterized in that, The management device is also used for: Obtain the parameter loading path for each production device, where the parameter loading path is the path for loading category parameters in the data reporting program of each production device; Obtain the protocol storage path of the parsing server; When the management device sends reporting instructions to each production device, it is specifically used for: Based on the parameter loading path of each production device and its corresponding attribute class file, a reporting instruction is sent to each production device. The reporting instruction also instructs to report data to the parsing server based on the data category in the parameter loading path. When the management device sends a parsing command to the parsing server, it is specifically used for: Based on the protocol storage path and the data parsing protocol corresponding to each production device, a parsing instruction is sent to the parsing server. The parsing instruction also instructs the parsing of the reported data of the corresponding production device based on the data parsing protocol in the protocol storage path.

19. The equipment management system according to claim 18, characterized in that, The management device is also used for: In response to an update operation on the configuration page of any production device, a first update instruction is sent to the production device and a second update instruction is sent to the parsing server, based on the update category and update protocol, respectively. The first update instruction indicates that the data category located in the parameter loading path is updated based on the update category, and the second update instruction indicates that the data parsing protocol located in the protocol storage path is updated based on the update protocol.

20. The equipment management system according to claim 13, characterized in that, The management device displays a configuration page for at least one production device, specifically for: Display the configuration entry for at least one production device on the equipment management page; In response to a trigger operation on the configuration entry of any production equipment, the configuration page of that production equipment is displayed; In response to a configuration operation on the configuration page of any production device, the data category of the production device is obtained, wherein the configuration operation includes at least one of adding a category, deleting a category, or editing a category.

21. The equipment management system according to claim 13 or 20, characterized in that, When the management device, in response to obtaining the data category configured in the configuration page of at least one production device, sends a reporting instruction to each production device and a parsing instruction to the parsing server, it is specifically used for: For any production equipment, in response to a data viewing operation triggered on the configuration page of the production equipment, a data collection command is sent to the cloud server based on the data category configured on the configuration page of the production equipment. The cloud server sends a reporting command to any of the production devices and a parsing command to the parsing server.

22. The equipment management system according to claim 13, characterized in that, The management device is also used for: For any production equipment, based on the timestamp of each data item in the attribute data of the production equipment, the attribute data is stored in the time-series database in the cloud-native service; In response to a data display request for any of the production devices, the data display request is verified based on the device permission information configured in the cloud-native service. If the permission verification is successful, read each piece of data from the time-series database for any of the production devices, and perform statistics on each piece of data based on the timestamp of each piece of data to obtain at least one statistical result; The device management page displays at least one of the statistical results.

23. The equipment management system according to claim 14, characterized in that, When the parsing server parses the reported data based on the data parsing protocol corresponding to any of the production devices to obtain the attribute data of any of the production devices, it is specifically used for: Based on the protocol type corresponding to any of the production devices, a generic interface is invoked to parse the reported data to obtain the attribute data of any of the production devices. The generic interface includes at least one protocol type of the production device and its corresponding data parsing protocol. The data parsing protocol includes at least one data category of the production device and the data storage format of each data category.

24. The equipment management system according to claim 14 or 23, characterized in that, The parsing instruction also instructs each data parsing protocol in the protocol storage path of the parsing server to parse the reported data of the corresponding production equipment. When storing the data parsing protocols corresponding to each of the at least one production device, the parsing server is specifically used for: The protocol storage path stores the correspondence between the protocol types of each production device and the data parsing protocol. The parsing server is also used for: Periodically scan each data parsing protocol in the protocol storage path; In response to the detection of a new data parsing protocol in the protocol storage path, the new data parsing protocol and its corresponding new protocol type are added to the generic interface of the parsing server.

25. A computer device, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 12.

26. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 12.

27. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 12.

Images