Multi-device centralized management method, device, system, electronic device and storage medium

Abstract

The present application discloses a method, apparatus, system, electronic device, and readable storage medium for centralized management of multiple devices. The method includes pre-configuring unique device identification information and data category identification information for each device; upon receiving a data collection request, parsing the data collection request to obtain information to be collected; the data collection request is a request generated in response to a user collection instruction and carries the device identification information to be collected and the data category identification information to be collected; based on the information to be collected, matching a target device with the same device identification information to be collected, and collecting data with the same data category identification information to be collected from the target device to obtain collected data carrying the device identification information of the target device, thereby achieving centralized management of multiple devices.

Description

Technical Field

[0001] The present application relates to the field of industrial automation technology, and in particular to a method, apparatus, system, electronic device, and readable storage medium for centralized management of multiple devices. Background Art

[0002] With the rapid development of computers, the internet, and information technology, industrial automation has become widely used in daily work and life, and the demand for centralized control and monitoring of multiple devices is increasing. Related technologies typically deploy one or more devices in different regions or areas, each of which is independently controlled. This makes centralized management of multiple devices impossible, and it also prevents timely access to the operating status of each device. For example, in the field of purification monitoring devices, pharmaceutical factories often deploy air particle monitoring devices, such as laser particle counters, within each production station. Purification monitoring devices, such as particle counters, are often independently controlled and carried to each monitoring point for monitoring. However, in production environments, equipment monitoring points often have multiple monitoring points within the same process environment. The environmental requirements may change as the next process proceeds. This leads to discontinuity in environmental monitoring and the need for continuous adjustment of monitoring standards. Even if a sufficient number of purification monitoring devices are matched to the monitoring points in different production environments, if the devices are deployed over a large area without remote terminal control, centralized management of multiple devices is impossible. In order to obtain timely information on the operating status of each monitoring device and remotely manage the monitoring devices, centralized management and control of multiple devices is necessary.

[0003] In view of this, how to achieve centralized management and control of multiple devices is a technical problem that technical personnel in the relevant field need to solve. Summary of the Invention

[0004] The present application provides a method, apparatus, system, electronic device and readable storage medium for centralized management of multiple devices, which can realize centralized management and control of multiple devices.

[0005] To solve the above technical problems, the embodiments of the present invention provide the following technical solutions:

[0006] An embodiment of the present invention provides a method for centralized management of multiple devices, including:

[0007] Pre-configure unique device identification information and data category identification information for each device;

[0008] When a data collection request is received, the information to be collected is obtained by parsing the data collection request; the data collection request is a request generated in response to a user collection instruction and carries identification information of the device to be collected and identification information of the category of data to be collected;

[0009] Based on the information to be collected, a target device with the same identification information as the device to be collected is matched, and data with the same category identification information as the data to be collected is collected from the target device to obtain collected data carrying the device identification information of the target device.

[0010] Optionally, after obtaining the information to be collected by parsing the data collection request, the method further includes:

[0011] If the target device cannot be matched based on the information to be collected, a device offline notification message is generated, and a device identification error instruction is sent to the client to add the device identification information of the target device to the client or correct the device identification information of the target device.

[0012] Optionally, matching a target device having the same identification information as the device to be collected based on the information to be collected, and collecting data having the same category identification information as the data to be collected from the target device to obtain the collected data of the target device includes:

[0013] Based on the first device identification information to be collected and the second device identification information to be collected, calling the first thread and the second thread to simultaneously match the first target device and the second target device that are identical to the first device identification information to be collected and the second device identification information to be collected; the first thread and the second thread are in a working state at the same time;

[0014] Based on a first preset interval automatic collection time of the first target device, whenever a corresponding collection time is detected, automatically calling the first thread to collect first data having the same category identification information as the first data to be collected from the first target device;

[0015] Based on the second preset interval automatic collection time of the second target device, whenever the corresponding collection time is detected, the second thread is automatically called to collect second data with the same category identification information as the second data to be collected from the second target device; the first data and the second data are used as the collected data.

[0016] Optionally, after receiving the data collection request, the method further includes:

[0017] Reading a collection operation execution identification code from the data collection request;

[0018] Execute the identification code according to the acquisition operation to determine whether there is a matching target data collector;

[0019] If the target data collector is matched, the step of parsing the data collection request to obtain the information to be collected is performed by the target data collector;

[0020] If the target data collector cannot be matched, a device offline notification message is generated, and a collection error instruction is sent to the client to add or modify the collection operation execution identification code of the target data collector in the client.

[0021] Optionally, after obtaining the collected data carrying the device identification information of the target device, the method further includes:

[0022] Converting the collected data into storage data in a data server platform;

[0023] The data server platform receives an operation command from the client, where the operation command is generated by the client based on the identification information of the device to be collected and the identification information of the type of data to be collected;

[0024] If the device identification information that is the same as the device identification information to be collected is matched, generating an initial operation result according to the target storage data corresponding to the acquired data category identification information to be collected;

[0025] If the initial operation result meets the data analysis requirements of the client, the operation result will be fed back to the client as operation result information; if the initial operation result does not meet the data analysis requirements, the initial operation result will be calculated and analyzed based on the operation command to obtain operation result information, and the operation result information will be sent to the client; after responding to the user's operation result requirement instruction, the client will perform a secondary operation on the operation result information according to the operation result requirement instruction.

[0026] Optionally, after obtaining the information to be collected by parsing the data collection request, the method further includes:

[0027] Pre-generate a user rights database, which includes authorized users of each device, data collection categories of each authorized user, and stored data call range;

[0028] Obtaining user identification information by parsing the data collection request;

[0029] By calling the user authority database, judging whether the accessing user is an authorized user of the target device corresponding to the device identification information to be collected based on the user identification information;

[0030] If the user is an authorized user of the target device, determining whether the user has collected data of the same category as the category identification information of the data to be collected from the target device;

[0031] If the user has collected data of the same category as the category identification information of the data to be collected from the target device, the operation of matching the target device with the same identification information as the device to be collected based on the information to be collected is performed.

[0032] Another embodiment of the present invention provides a multi-device centralized management apparatus, including:

[0033] A pre-deployment module is used to pre-configure unique device identification information and data category identification information for each device;

[0034] A request parsing module is configured to, upon receiving a data collection request, parse the data collection request to obtain the information to be collected; the data collection request is a request generated in response to a user collection instruction and carries identification information of the device to be collected and identification information of the category of data to be collected;

[0035] The acquisition module is used to match the target device with the same identification information as the device to be collected based on the information to be collected, and collect data with the same category identification information as the data to be collected from the target device to obtain the collected data carrying the device identification information of the target device.

[0036] An embodiment of the present invention further provides an electronic device, comprising a processor, wherein the processor is configured to implement the steps of the multi-device centralized management method as described in any of the preceding items when executing a computer program stored in a memory.

[0037] An embodiment of the present invention further provides a readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method for centralized management of multiple devices as described in any of the preceding items are implemented.

[0038] Finally, the embodiment of the present invention further provides a multi-device centralized management system, including a data collector, a data server platform, a communication module, a client, and a plurality of devices to be collected;

[0039] The data collector is used to implement the steps of the multi-device centralized management method described in any of the preceding items when executing the computer program stored in the memory;

[0040] The communication module is used to realize the communication connection between at least two of the devices to be collected, the data collector, the data server platform, and the client;

[0041] The data server platform is used to respond to the collection instruction issued by the client, generate a data collection request carrying the identification information of the device to be collected and the identification information of the type of data to be collected, and send the data collection request to the data collector;

[0042] The client is used to send a collection instruction to the data server platform in response to a user collection instruction, and to configure unique device identification information and data category identification information for each device to be collected in response to a user configuration instruction.

[0043] The advantage of the technical solution provided by the present application is that, by setting unique identification information for each device and uniquely identifying the data category of the data that can be collected by each device, the user can issue a collection instruction carrying the relevant identification information of the device to be collected and the data to be collected to the device that performs data collection. Based on the collection instruction, the device to be collected can be located and the required data can be collected from the device to be collected. Based on the collected data, the operating status of each device can be known in a timely manner, and each device can be remotely managed, so that one or more devices can be arranged in different locations without being restricted by terrain and region, thereby realizing centralized management of these multiple devices.

[0044] In addition, the embodiment of the present invention also provides corresponding implementation devices, electronic devices and readable storage media for the multi-device centralized management method, further making the method more practical, and the devices, electronic devices and readable storage media have corresponding advantages.

[0045] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0047] Figure 1 A flowchart of a method for centralized management of multiple devices provided by an embodiment of the present invention;

[0048] Figure 2 A schematic diagram of a framework of an exemplary application scenario provided by an embodiment of the present invention;

[0049] Figure 3 A structural diagram of a specific implementation of the multi-device centralized management apparatus provided by an embodiment of the present invention;

[0050] Figure 4 A structural diagram of a specific implementation of an electronic device provided by an embodiment of the present invention;

[0051] Figure 5 This is a structural diagram of a specific implementation of the multi-device centralized management system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0052] In order to enable those skilled in the art to better understand the present invention, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0053] In the specification, claims, and drawings of this application, the terms "first," "second," "third," "fourth," and so on are used to distinguish between different items, not to describe a specific order. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements and may include steps or elements that are not listed.

[0054] After introducing the technical solutions of the embodiments of the present invention, various non-limiting implementation methods of the present application are described in detail below.

[0055] See first Figure 1 , Figure 1 A flowchart of a method for centralized management of multiple devices provided in an embodiment of the present invention may include the following:

[0056] S101: Pre-configure unique device identification information and data category identification information for each device.

[0057] In this embodiment, the devices are devices to be centrally managed. Each device can be multiple devices deployed in the same area, multiple devices deployed in different areas, or multiple devices deployed in both the same area and different areas. The type and number of devices can be flexibly selected based on actual needs and do not affect the implementation of this application. Device identification information is unique, non-repetitive information that can be used to identify and locate the device. The device identification information can be the device's IP address, a pre-set device identification code, or a combination thereof to achieve a unique correspondence between devices and device identifiers. Data categories are the types of data that a device can collect. These data can be data collected by the device, data operated by the device, or other types of data. Different types of data can be uniquely identified by data category identification information. By identifying the device and data, the device performing the data collection operation can locate the device and collect data based on the identification information. The device identification information and data category identification information can be configured by the user through a client running on a desktop computer or mobile smart terminal, such as a webpage or app. The client includes a configuration module that configures the device and data, generates configuration information, and sends the configuration information to a server, such as a data server platform. S102: When a data collection request is received, the information to be collected is obtained by parsing the data collection request.

[0058] In this embodiment, a data collection request is a request generated in response to a user collection instruction and carries the device identification information to be collected and the data category identification information to be collected. The user collection instruction is an instruction issued by a user to a server through a client, such as an app or a webpage. The server, such as a data server platform, generates a data collection request based on the collection instruction and configuration information, carrying the device identification information to be collected and the data category identification information to be collected. The server then issues the data collection request to the device performing the data collection. After receiving the data collection request, the device performing the data collection, i.e., the subject of execution in this embodiment, parses the data collection request to obtain the device identification information to be collected and the data category identification information to be collected. Furthermore, to facilitate traceability, the data collection request may also carry time information, indicating when to collect certain data from a specific device. This time information can be configured in S101 or set by the server based on actual needs after receiving the collection instruction. S103: Based on the information to be collected, a target device with the same identification information as the device to be collected is matched, and data with the same identification information as the data category identification information to be collected is collected from the target device to obtain collected data carrying the device identification information of the target device.

[0059] After obtaining the device identification information and the data category identification information to be collected in the previous step, the device identification information to be collected can be used to locate whether there is a device that needs to perform data collection from each device. If so, the device is located and data with the same data category identification information as the data to be collected is collected from the target device, thereby obtaining collected data carrying the device identification information of the target device. If the target device cannot be matched based on the information to be collected, a device offline notification message is generated, and a device identification error instruction is sent to the client to add the device identification information of the target device to the client or correct the device identification information of the target device. In the technical solution provided by the embodiment of the present invention, by setting unique identification information for each device and uniquely identifying the data category of the data that can be collected by each device, the user can issue a collection instruction carrying the relevant identification information of the device to be collected and the data to be collected to the device performing data collection. Based on the collection instruction, the device to be collected can be located and the required data can be collected from the device to be collected. Based on the collected data, the operating status of each device can be timely understood and each device can be remotely managed. Therefore, one or more devices can be deployed in different locations without being restricted by terrain or region, realizing centralized management of these multiple devices.

[0060] It should be noted that there is no strict order in which the steps in this application are performed. As long as they comply with the logical order, these steps can be performed simultaneously or in a predetermined order. Figure 1 This is just a schematic and does not mean that this is the only execution order.

[0061] It is understandable that users will inevitably collect multiple categories of data information from multiple devices. The above embodiment does not limit this implementation scenario. In order to improve the overall data collection efficiency, in this embodiment, based on the information to be collected, matching the target device with the same identification information as the device to be collected, and collecting data with the same category identification information as the data to be collected from the target device to obtain the collected data of the target device. An optional implementation method may include:

[0062] Based on the first to-be-collected device identification information and the second to-be-collected device identification information of the information to be collected, calling the first thread and the second thread to simultaneously match the first target device and the second target device that are identical to the first to-be-collected device identification information and the second to-be-collected device identification information;

[0063] Based on a first preset interval automatic collection time of the first target device, whenever a corresponding collection time is detected, the first thread is automatically called to collect first data having the same category identification information as the first data to be collected from the first target device;

[0064] Based on a second preset interval automatic collection time of the second target device, whenever a corresponding collection moment is detected, automatically calling a second thread to collect second data having the same category identification information as the second data to be collected from the second target device;

[0065] The first data and the second data are used as collected data.

[0066] In this embodiment, the first device identification information to be collected is the same as the device identification information of the first target device, and the second device identification information to be collected is the same as the device identification information of the second target device. The first and second target devices can be devices in the same region or in different regions, and the first data and second data can be data of the same category or different categories, without affecting the implementation of the present application. The first thread and the second thread are in operation simultaneously, that is, the present application can collect data from multiple target devices simultaneously. The data collection request also includes a preset interval automatic collection time. To distinguish the automatic collection times of the first and second target devices, the preset interval automatic collection time of the first target device may be referred to as the first preset interval automatic collection time, and the preset interval automatic collection time of the second target device may be referred to as the second preset interval automatic collection time. The data collector can automatically collect raw data from each target device according to the preset interval automatic collection time and transmit it to the server. The preset interval automatic collection time can be configured through the client's configuration module or can be a fixed setting on the server. The value of the preset interval automatic collection time can be flexibly set according to actual needs. When it is 0, it is equivalent to not setting an interval.

[0067] The above embodiment does not impose any restrictions on the device that performs the data collection operation. For multiple devices that perform data collection operations, for ease of description, the device that performs the data collection operation can be referred to as a data collector. When generating a data collection request, the server can specify a data collector to perform the data collection operation and then directly send the data collection request to the data collector. The server can also send the data collection request to a random data collector instead of the specified data collector. After receiving the data collection request, the data collector reads the collection operation execution identification code from the data collection request; based on the collection operation execution identification code, it determines whether there is a matching target data collector among multiple data collectors; if a match is found, the target data collector executes the step of parsing the data collection request to obtain the information to be collected. Of course, the server can also not specify which data collector to perform the data collection operation, and randomly send the data collection request to a data collector to perform the operation. If the data collector does not feedback any information within a certain period of time, the server will re-forward the data collection request to other data collectors. If the target data collector cannot be matched, a device offline notification message is generated, and a collection error instruction is sent to the client to add or modify the collection operation execution identification code of the target data collector in the client.

[0068] Based on the above embodiment, in order to facilitate user use and centralized management of devices, the server can be a data server platform, and can also analyze and process the collected data, which may include the following:

[0069] After acquiring the collected data, the collected data can be converted into storage data in the data server platform; the data server platform receives the operation command of the client, and the operation command is generated by the client based on the identification information of the device to be collected and the identification information of the category of the data to be collected; if the device identification information that is the same as the identification information of the device to be collected is matched, the initial operation result is generated according to the target storage data corresponding to the obtained identification information of the category of the data to be collected; if the initial operation result meets the data analysis requirements of the client, the operation result is fed back to the client as the operation result information; if the initial operation result does not meet the data analysis requirements, the initial operation result is calculated and analyzed based on the operation command to obtain the operation result information, and the operation result information is sent to the client; after responding to the user's operation result requirement instruction, the client performs a secondary operation on the operation result information according to the operation result requirement instruction.

[0070] The device that performs data collection operations in this application can form collected data through the original data collected by the interfaces of each device, and transmit it to the server, that is, the data storage module of the data server platform of this embodiment through the device that performs data transmission to form stored data. The stored data may include collected data and / or data formed by collected data calculations. The collected data includes original data and / or data formed by original data calculations. Optionally, at least the data starting from the formation of one of the original data, collected data, and stored data includes time data for realizing the time traceability and identifiability of the data. Exemplarily, the time data starting from the original data can be the time when the original data is formed, the time data starting from the collected data can be the time when the data is collected, and the time data starting from the stored data can be the time when the data is stored. The client can access the data server platform and call the data of its storage module according to the data category that needs to be presented. The storage module directly calls the data according to the client's requirements, or inputs the data that can be calculated to obtain the data category into the data analysis module and sends it to the client after calculation. The client displays the received data or converts it twice, and compares it with the client's preset standards. It can be a comparison of a single device, or it can associate the device data under the same production process and compare it with the standard. It will be judged when the data exceeding the predetermined proportion exceeds the standard value, and then access and control the start and stop of the on-site instruments to achieve effective management of each device.

[0071] To further improve the security of device management, the user's device monitoring authority, data collection authority, and data reading authority may be further limited. Based on the above embodiment, after parsing the data collection request and obtaining the information to be collected, the following may also be included:

[0072] Generate a user rights database in advance, which includes the authorized users of each device, the data collection category of each authorized user, and the scope of stored data call;

[0073] Obtain user identification information by parsing the data collection request;

[0074] By calling the user authority database, based on the user identification information, it is determined whether the accessing user is an authorized user of the target device corresponding to the device identification information to be collected;

[0075] If the user is an authorized user of the target device, determining whether the user has the ability to collect data of the same category as the category identification information of the data to be collected from the target device;

[0076] If the user has collected data of the same category as the category identification information of the data to be collected from the target device, an operation of matching the target device with the same identification information as the device to be collected based on the information to be collected is performed.

[0077] In order to make the technical personnel in the related field more clearly understand the technical solution of this application, Figure 2 Taking the clean monitoring equipment as an example, this application also provides an illustrative embodiment, which may include the following contents:

[0078] A centralized management system for clean monitoring equipment is used to support data collection and management of at least one clean monitoring equipment, comprising at least one clean monitoring equipment, at least one data collection module, a transmission module, a data server platform and a client.

[0079] Clean monitoring equipment is used to monitor the cleanliness of its surrounding environment and generate raw data. The sensors in these clean monitoring equipment measure the environment and generate measurement signals, which are then output to the sensor processor to obtain raw data such as particle size, concentration, and quantity. Each clean monitoring device has a corresponding device identifier. The data acquisition module can be software and is used to collect raw data from a specific clean monitoring device as required. The transmission module can be any type of communication module, such as a data cable, Bluetooth, or network, and can be configured by a person skilled in the art as needed. It is used to enable communication between at least two of the clean monitoring equipment, the data acquisition module, the data server platform, and the client, as well as internal communication between the data acquisition module and the data server platform. The data server platform is software installed on a cloud server or a local server. The data server platform is used to acquire and store raw data from the clean monitoring equipment, generate stored data, and analyze and manage this stored data. It includes a data storage module and a data analysis module. The client, which can be an app or webpage running on a smart terminal device, can include a configuration module, an operation module, and a display module. The output of the operation module and the settings of the configuration module are visualized. The configuration module is used to configure the clean monitoring devices connected to the management system. The raw data generated by the clean monitoring equipment when identifying the monitoring environment may include data such as the particle size, quantity, and concentration of particles in the air. The data acquisition module can collect raw data through the clean monitoring equipment interface to form collected data and transmit it to the data storage module of the data server platform through the transmission module to form stored data. Alternatively, the data acquisition module can be integrated into the data server platform, and the raw data collected through the transmission module to form collected data, which is then input into the data storage module to form stored data. In other words, the data acquisition module collects the raw data of the clean monitoring equipment corresponding to the device identification information and data category identification in the data server platform collection request to form collected information, and sends the collected information to the data storage module to form stored information. The output content of the data server platform includes the display and export of data and data analysis results. Specifically, a collection request is issued through the client operation data server platform, and the collection request includes the device identification of the device to be collected and the data category identification of the data to be collected. The data collection module receives the collection request and reads the device identification in the collection request. According to the read device identification, the data collection module matches the clean monitoring device with the device identification. When a clean monitoring device with a consistent device identification is matched, the data collection module collects the original data of the corresponding clean monitoring device according to the data category identification in the collection request and forms the collected data. The collected data is input into the data storage module to form the stored data. When the data collection module cannot match the clean monitoring device with the same device identification, the data collection module cannot execute the collection request normally and displays on the client that the device is offline and cannot obtain data. The technician can give up the collection according to the offline identification or add the device identification to the device list or modify the device identification through the configuration module.

[0080] Taking the clean monitoring equipment as a particle counter as an example, as an illustrative example, multiple particle counters can be connected to the data acquisition software through a bus. Each particle counter has a corresponding device identification. The processor contained in the particle counter analyzes and processes the data monitored by the particle counter's sensor to obtain various categories of data, such as particle size D, concentration C, the number of each particle size N, etc. The device identification is configured and input from the client's configuration module. For example, the bus, device address, and register information of the device can be set on the client, and the data category that the device needs to obtain can be configured and input. The data category can be direct data consistent with the category of data obtained by the particle counter, or it can be indirect data obtained through calculation of particle counting sensor data, such as particle size, concentration, and the number of each particle size. After the device identification and data category are configured and input from the client's configuration module, the client sends the device identification information to the data server platform. The data server platform sends a collection request for the data category to be collected by the device identification to the data collection module based on the received device identification information. After receiving the collection request, the data collection module matches the particle counter to which it is connected based on the device identification information. When the device with the device identification can be matched, the data of the register corresponding to the device identification is collected, and the collected data is input into the storage module of the data server platform. When it is necessary to analyze the monitoring data of the device identification, the client selects the data category, time and other options and then requests the corresponding data to be called from the data server platform. The data server platform judges the call request. For the passed call request, the data corresponding to the device identification is screened in the data storage module. According to the data category, it is determined whether it is the stored data in the data storage module or the data that can be obtained after calculation of the stored data. According to the judgment result, the data that can be directly output by the data storage module is sent to the client. If the data requires further calculation to obtain, the data is sent to the data analysis module for calculation and then sent to the client. The client presents the received data and can perform secondary statistical analysis. The client can input the warning value of the device data category corresponding to each device identification. When the data received by the client exceeds the warning value, the client presents a warning state, and the stop instruction of the field instrument is output through the client.

[0081] This embodiment configures the device identification information of each clean monitoring device on the client and transmits this information to the data server platform. The data server platform then sends a collection request to the data acquisition module based on the device identification information, thereby continuously collecting monitoring information from the device and inputting the collected data into the data server platform. This allows one or more clean monitoring devices to be deployed in different locations without being restricted by terrain or region, and the client can control the management of the corresponding clean monitoring device by entering the device identification information.

[0082] The embodiments of the present invention also provide a corresponding apparatus for the multi-device centralized management method, further enhancing the practicality of the method. The apparatus can be described from the perspective of functional modules and hardware. The following describes the multi-device centralized management apparatus provided by the embodiments of the present invention. The multi-device centralized management apparatus described below can be used in conjunction with the multi-device centralized management method described above.

[0083] From the perspective of functional modules, see Figure 3 , Figure 3 A structural diagram of a multi-device centralized management apparatus provided in an embodiment of the present invention in a specific implementation manner, the apparatus may include:

[0084] A pre-deployment module 301 is used to pre-configure unique device identification information and data category identification information for each device;

[0085] The request parsing module 302 is used to parse the data collection request upon receiving it to obtain the information to be collected. The data collection request is a request generated in response to a user collection instruction and carries the identification information of the device to be collected and the identification information of the type of data to be collected.

[0086] The collection module 303 is used to match the target device with the same identification information as the device to be collected based on the information to be collected, and collect data with the same category identification information as the data to be collected from the target device to obtain collected data carrying the device identification information of the target device.

[0087] Optionally, in some implementations of this embodiment, the above-mentioned device may also include an identification information update module, which is used to generate device offline notification information if the target device cannot be matched based on the information to be collected, and send a device identification error instruction to the client, so as to add the device identification information of the target device to the client or correct the device identification information of the target device.

[0088] As an optional implementation, the request parsing module 302 may also be used to: match a first target device with the same identification information as the device to be collected based on the first identification information of the information to be collected, and collect first data with the same identification information as the first data category to be collected from the first target device; when the preset interval automatic collection time in the information to be collected is detected, match a second target device with the same identification information as the device to be collected based on the second identification information of the information to be collected, and collect second data with the same identification information as the second data category to be collected from the second target device; and use the first data and the second data as the collected data.

[0089] As another optional implementation, the above-mentioned device may also include a collector determination module, which is used to read the collection operation execution identification code from the data collection request; based on the collection operation execution identification code, determine whether there is a matching target data collector; if the target data collector is matched, the target data collector executes the step of parsing the data collection request to obtain the information to be collected; if the target data collector cannot be matched, a device offline notification message is generated, and a collection error instruction is sent to the client to add or correct the collection operation execution identification code of the target data collector in the client.

[0090] Optionally, in some other implementations of this embodiment, the above-mentioned device may also include a data storage and analysis module for converting the collected data into storage data in the data server platform; the data server platform receives the operation command of the client, and the operation command is generated by the client based on the device identification information to be collected and the category identification information of the data to be collected; if the device identification information that is the same as the device identification information to be collected is matched, the initial operation result is generated according to the target storage data corresponding to the obtained category identification information of the data to be collected; if the initial operation result meets the data analysis requirements of the client, the operation result is fed back to the client as operation result information; if the initial operation result does not meet the data analysis requirements, the initial operation result is calculated and analyzed based on the operation command to obtain operation result information, and the operation result information is sent to the client; after responding to the user's operation result requirement instruction, the client performs a secondary operation on the operation result information according to the operation result requirement instruction.

[0091] Optionally, in some other implementations of this embodiment, the above-mentioned device may also include, for example: pre-generating a user authority database, the user authority database including authorized users of each device, the data collection category of each authorized user, and the storage data call range; obtaining user identification information by parsing the data collection request; judging whether the accessing user is an authorized user of the target device corresponding to the device identification information to be collected based on the user identification information by calling the user authority database; if the user is an authorized user of the target device, judging whether the user has the ability to collect data of the same category as the data category identification information to be collected from the target device; if the user has the ability to collect data of the same category as the data category identification information to be collected from the target device, performing an operation based on the information to be collected to match the target device with the same identification information as the device to be collected.

[0092] The functions of the functional modules of the multi-device centralized management apparatus according to the embodiment of the present invention can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment and will not be repeated here.

[0093] As can be seen from the above, the embodiments of the present invention can achieve centralized management and control of multiple devices.

[0094] The multi-device centralized management device mentioned above is described from the perspective of functional modules. Furthermore, the present application also provides an electronic device, which is described from the perspective of hardware. Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application in one embodiment. Figure 4 As shown, the electronic device includes a memory 40 for storing computer programs; a processor 41 for implementing the steps of the multi-device centralized management method mentioned in any of the above embodiments when executing the computer program.

[0095] The processor 41 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 41 may also be a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 41 may be implemented in at least one hardware form selected from the group consisting of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 41 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 41 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 41 may also include an AI (Artificial Intelligence) processor, which is used to handle computing operations related to machine learning.

[0096] The memory 40 may include one or more computer-readable storage media, which may be non-transitory. The memory 40 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash memory storage devices. In some embodiments, the memory 40 may be an internal storage unit of an electronic device, such as a hard disk of a server. In other embodiments, the memory 40 may also be an external storage device of an electronic device, such as a plug-in hard disk equipped on a server, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Furthermore, the memory 40 may also include both an internal storage unit of an electronic device and an external storage device. The memory 40 can not only be used to store application software and various types of data installed on the electronic device, such as the code of the program that executes the vulnerability handling method, but can also be used to temporarily store data that has been output or is to be output. In this embodiment, the memory 40 is used to store at least the following computer program 401, wherein, after the computer program is loaded and executed by the processor 41, it can implement the relevant steps of the multi-device centralized management method disclosed in any of the aforementioned embodiments. In addition, the resources stored in memory 40 may also include an operating system 402 and data 403, and the storage method may be temporary or permanent. Among them, operating system 402 may include Windows, Unix, Linux, etc. Data 403 may include, but is not limited to, data corresponding to the results of centralized management of multiple devices.

[0097] In some embodiments, the electronic device may further include a display screen 42, an input / output interface 43, a communication interface 44 or a network interface, a power supply 45 and a communication bus 46. Among them, the display screen 42 and the input / output interface 43, such as a keyboard, are user interfaces, and the optional user interface may also include a standard wired interface, a wireless interface, etc. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode) touch device, etc. The display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device and to display a visual user interface. The communication interface 44 may optionally include a wired interface and / or a wireless interface, such as a WI-FI interface, a Bluetooth interface, etc., which is generally used to establish a communication connection between the electronic device and other electronic devices. The communication bus 46 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0098] Those skilled in the art will understand that Figure 4 The structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, for example, it may also include a sensor 47 to realize various functions.

[0099] The functions of the functional modules of the electronic device in the embodiment of the present invention can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment, which will not be repeated here.

[0100] As can be seen from the above, the embodiments of the present invention can achieve centralized management and control of multiple devices.

[0101] It is understandable that if the multi-device centralized management method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), electrically erasable programmable ROM, register, hard disk, multimedia card, card-type memory (such as SD or DX memory, etc.), magnetic memory, removable disk, CD-ROM, magnetic disk or optical disk, etc. Various media that can store program code.

[0102] Based on this, an embodiment of the present invention further provides a readable storage medium storing a computer program. When the computer program is executed by a processor, the steps of the multi-device centralized management method in any of the above embodiments are performed.

[0103] The present invention also provides a multi-device centralized management system. Figure 5 , which may include the following:

[0104] The multi-device centralized management system may include a data collector 51 , a data server platform 52 , a communication module 53 , a client 54 and a plurality of devices to be collected 55 .

[0105] The data collector 51 can be used to execute the multi-device centralized management method described in any of the above embodiments. The data collector 51 can be embedded in the data server platform 52 or installed in another device. The communication module 53 is used to establish a communication connection between at least two of the devices 55 to be collected, the data collector 51, the data server platform 52, and the client 54. The data server platform 52 is used to respond to collection instructions issued by the client 54, generate a data collection request containing the identification information of the device to be collected and the identification information of the category of the data to be collected, and send the data collection request to the data collector 51. The data server platform 52 can be installed locally to form a local area network server or on a cloud platform to form a cloud server, and the specific configuration and installation can be based on needs. The data server platform 52 includes a data storage module and a data analysis module. Accordingly, its output content includes the display and export of data and data analysis results. The client 54 is used to issue collection instructions to the data server platform 52 in response to user collection instructions, and to configure unique device identification information and data category identification information for each device to be collected in response to user configuration instructions.

[0106] In this embodiment, the client 54 may include a configuration module, an operation module, a display module, and a client analysis module. The output content of the operation module and the setting content of the configuration module are visualized. The configuration module is used to configure the clean monitoring equipment connected to the management system. The configuration module includes a device list, a data category identification list, and a collector list. The device identification information enters the device list after configuration. The data category identification is selected from the data category of the original data monitored by the clean monitoring equipment, the data category of the collected data, the data category of the stored data, and the data category obtained by calculating the original data / collected data / stored data. The data category enters the data category identification list after configuration. When the data acquisition module exceeds a preset time, the identification code of the data acquisition module is entered into the collector list through the configuration module of the client. At this time, the acquisition request contains the identification code of the data acquisition module. After receiving the acquisition request, the acquisition module matches the corresponding data acquisition module according to the identification code of the data acquisition module in the acquisition request to collect the original data of the clean monitoring equipment with the corresponding device identification to form the collected data. After a specific data acquisition module receives a collection request, if the data acquisition module identifier in the collection request matches a data acquisition module with a consistent identifier, the data acquisition module executes the collection request. If the collection module identifier in the collection request does not match a data acquisition module with a consistent identifier, the data acquisition module cannot execute the collection request normally and displays on the client that the device is offline and unable to obtain data. The technician abandons the collection based on the offline identifier or adds the identification code of the data acquisition module to the collector list through the configuration module. The operation module may include an operation command list, an execution block, and an operation result list. The operation module calls the device identifier of the device to be analyzed and the data category identifier to be analyzed from the device list and the data category identifier list to generate an operation command, and the generated operation command is stored in the operation command list. When the execution block executes a run command, it sends the run command to the data storage module and / or the data analysis module. The data storage module matches the device identifier in the run command with the data storage module. When the corresponding device identifier is matched in the data storage module, the data storage module generates a run result based on the data category identifier in the run command and sends it to the run result directory and / or to the data analysis module. The data analysis module calculates and analyzes the received stored data according to the run command to obtain a run result and sends it to the run result directory. The run result is displayed by the display module. The client analysis module performs secondary operations on the run result according to preset requirements to achieve personalized analysis for the client.

[0107] As an optional implementation, the aforementioned multi-device centralized management system may also include a user module. The user module is a list of users who can access the data server platform through a client to collect and analyze data. The user list limits the range of device identifications of clean monitoring equipment that users can control and collect data, as well as the range of stored data that can be called, to achieve secure data storage and retrieval. When an exemplary configuration module accesses the data server platform to request the execution of a run command, the user module identifies the visitor requesting the run command. For visitors listed in the user module's user list, the module determines whether the device identification in the run command is within the visitor's authority range. For device identifications within the authority range, access is granted and the run command is executed.

[0108] The functions of each functional module of the multi-device centralized management system in the embodiment of the present invention can be specifically implemented according to the method in the above method embodiment. The specific implementation process can refer to the relevant description of the above method embodiment and will not be repeated here.

[0109] As can be seen from the above, the embodiments of the present invention can achieve centralized management and control of multiple devices.

[0110] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. References to the same or similar parts between the various embodiments are sufficient. The hardware disclosed in the embodiments, including devices and electronic devices, is described briefly because it corresponds to the methods disclosed in the embodiments. For relevant details, refer to the method description.

[0111] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0112] The above is a detailed introduction to a multi-device centralized management method, apparatus, system, electronic device and readable storage medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of this application.

Claims

1. A method for centralized management of multiple devices, characterized in that: include: Pre-configure unique device identification information and data category identification information for each device; When a data collection request is received, the information to be collected is obtained by parsing the data collection request; the data collection request is a request generated in response to a user collection instruction and carries identification information of the device to be collected and identification information of the category of data to be collected; Based on the information to be collected, matching a target device with the same identification information as the device to be collected, and collecting data with the same identification information as the data category to be collected from the target device to obtain collected data carrying the device identification information of the target device; Converting the collected data into storage data in a data server platform; The data server platform receives an operation command from the client, where the operation command is generated by the client based on the identification information of the device to be collected and the identification information of the type of data to be collected; If the device identification information that is the same as the device identification information to be collected is matched, generating an initial operation result according to the target storage data corresponding to the acquired data category identification information to be collected; If the initial operation result meets the data analysis requirements of the client, the operation result is fed back to the client as operation result information; If the initial operation result does not meet the data analysis requirement, performing calculation and analysis on the initial operation result based on the operation command to obtain operation result information, and sending the operation result information to the client; After responding to the user's operation result request instruction, the client performs a secondary operation on the operation result information according to the operation result request instruction.

2. The method for centralized management of multiple devices according to claim 1, characterized in that: After obtaining the information to be collected by parsing the data collection request, the method further includes: If the target device cannot be matched based on the information to be collected, a device offline notification message is generated, and a device identification error instruction is sent to the client to add the device identification information of the target device to the client or correct the device identification information of the target device.

3. The method for centralized management of multiple devices according to claim 2, wherein: The step of matching a target device with the same identification information as the device to be collected based on the information to be collected, and collecting data with the same category identification information as the data to be collected from the target device to obtain the collected data of the target device includes: Based on the first device identification information to be collected and the second device identification information to be collected, calling the first thread and the second thread to simultaneously match the first target device and the second target device that are identical to the first device identification information to be collected and the second device identification information to be collected; the first thread and the second thread are in a working state at the same time; Based on a first preset interval automatic collection time of the first target device, whenever a corresponding collection time is detected, automatically calling the first thread to collect first data having the same category identification information as the first data to be collected from the first target device; Based on a second preset interval automatic collection time of the second target device, whenever a corresponding collection moment is detected, automatically calling the second thread to collect second data having the same category identification information as the second data to be collected from the second target device; The first data and the second data are used as collected data.

4. The method for centralized management of multiple devices according to claim 1, wherein: After receiving the data collection request, the method further includes: Reading a collection operation execution identification code from the data collection request; Execute the identification code according to the acquisition operation to determine whether there is a matching target data collector; If the target data collector is matched, the step of parsing the data collection request to obtain the information to be collected is performed by the target data collector; If the target data collector cannot be matched, a device offline notification message is generated, and a collection error instruction is sent to the client to add or modify the collection operation execution identification code of the target data collector in the client.

5. The method for centralized management of multiple devices according to any one of claims 1 to 4, characterized in that: After obtaining the information to be collected by parsing the data collection request, the method further includes: Pre-generate a user rights database, which includes authorized users of each device, data collection categories of each authorized user, and stored data call range; Obtaining user identification information by parsing the data collection request; By calling the user authority database, judging whether the accessing user is an authorized user of the target device corresponding to the device identification information to be collected based on the user identification information; If the user is an authorized user of the target device, determining whether the user has collected data of the same category as the category identification information of the data to be collected from the target device; If the user has collected data of the same category as the category identification information of the data to be collected from the target device, the operation of matching the target device with the same identification information as the device to be collected based on the information to be collected is performed.

6. A multi-device centralized management device, characterized in that: include: A pre-deployment module is used to pre-configure unique device identification information and data category identification information for each device; A request parsing module is configured to, upon receiving a data collection request, parse the data collection request to obtain the information to be collected; the data collection request is a request generated in response to a user collection instruction and carries identification information of the device to be collected and identification information of the category of data to be collected; a collection module configured to match a target device having the same identification information as the device to be collected based on the information to be collected, and collect data having the same category identification information as the data to be collected from the target device, so as to obtain collected data carrying the device identification information of the target device; A data storage and analysis module, configured to convert the collected data into storage data in a data server platform; The data server platform receives an operation command from the client, where the operation command is generated by the client based on the identification information of the device to be collected and the identification information of the type of data to be collected; If the device identification information that is the same as the device identification information to be collected is matched, generating an initial operation result according to the target storage data corresponding to the acquired data category identification information to be collected; If the initial operation result meets the data analysis requirements of the client, the operation result is fed back to the client as operation result information; If the initial operation result does not meet the data analysis requirement, performing calculation and analysis on the initial operation result based on the operation command to obtain operation result information, and sending the operation result information to the client; After responding to the user's operation result request instruction, the client performs a secondary operation on the operation result information according to the operation result request instruction.

7. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the processor is configured to implement the steps of the multi-device centralized management method according to any one of claims 1 to 5 when executing a computer program stored in the memory.

8. A readable storage medium, characterized in that: The readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the multi-device centralized management method according to any one of claims 1 to 5.

9. A multi-device centralized management system, characterized in that: It includes data collector, data server platform, communication module, client and multiple devices to be collected; The data collector is used to implement the steps of the multi-device centralized management method according to any one of claims 1 to 5 when executing the computer program stored in the memory; The communication module is used to realize the communication connection between at least two of the devices to be collected, the data collector, the data server platform, and the client; The data server platform is used to respond to the collection instruction issued by the client, generate a data collection request carrying the identification information of the device to be collected and the identification information of the type of data to be collected, and send the data collection request to the data collector; The client is used to send a collection instruction to the data server platform in response to a user collection instruction, and to configure unique device identification information and data category identification information for each device to be collected in response to a user configuration instruction.

Images