Methods, apparatus, computing devices, and storage media of determining a collection frequency

Abstract

Methods, apparatuses, computing devices, and storage media for determining a collection frequency. A method for determining a collection frequency of data, wherein the data is collected from a device and provided to an application for monitoring the device by the application, the method comprising: determining a collection frequency requirement of the data of the device by the application; determining state information of the device; and determining the collection frequency of the data according to a preset rule based on the determined collection frequency requirement of the data of the device by the application and the determined state information of the device.

Description

Technical Field

[0001] This disclosure generally relates to the field of Internet of Things (IoT) technology, and more specifically, to methods, apparatus, computing devices, and storage media for determining sampling frequencies. Background Technology

[0002] Digitalization is a trend in the manufacturing industry. Equipment-related digitalization is a crucial application in factories, especially cloud-based applications such as equipment condition monitoring, OEE (Overall Equipment Effectiveness), fault diagnosis, and predictive maintenance. Therefore, efficiently collecting effective field data from equipment is key to successful digital solutions; for example, at what frequency should data be collected from the equipment?

[0003] Currently, factories are using an increasing number of devices of various types. Even for the same type of equipment, the performance of the hardware and control systems can vary significantly due to different purchase dates and hardware and software versions. Therefore, determining the appropriate data acquisition frequency for a given device is a complex task that requires highly specialized technical personnel.

[0004] The situation worsens as cloud applications become more prevalent. This is because cloud application providers / developers have less information about the true state of field devices. If they apply a uniform data collection frequency to devices without considering factors such as device type, hardware and software versions, or workload, high-frequency data collection can lead to lower productivity, higher defect rates, and even device damage.

[0005] Currently, a fixed data acquisition frequency for a device is typically set based on application, field testing, or experience, which requires a significant amount of work and highly experienced engineers. Furthermore, a trial-and-error approach is needed, adjusting the acquisition frequency as the defect rate increases or the device becomes slower. Summary of the Invention

[0006] A brief overview of the invention is given below to provide a basic understanding of certain aspects of it. It should be understood that this overview is not an exhaustive summary of the invention. It is not intended to identify key or essential parts of the invention, nor is it intended to limit the scope of the invention. Its purpose is merely to present certain concepts in a simplified form as a prelude to the more detailed description that follows.

[0007] In view of the above, this disclosure provides an adaptive method for setting an appropriate data acquisition frequency for a device. In this method, the application requirements and the device's status are considered to determine the appropriate data acquisition frequency for the device. Furthermore, the acquisition frequency can be automatically adjusted based on the real-time situation of the device in the field.

[0008] According to one aspect of this disclosure, a method for determining the data acquisition frequency is provided, wherein the data is acquired from a device and provided to an application for the application to monitor the device, the method comprising: determining the application's data acquisition frequency requirement for the device; determining the device's status information; and determining the data acquisition frequency according to a preset rule based on the determined application's data acquisition frequency requirement for the device and the determined device status information.

[0009] Optionally, in one example of the above aspects, the application's data acquisition frequency requirement for the device includes at least one of the following: the application's own acquisition frequency requirement; the application's acquisition frequency requirement under different device states; and the application's acquisition frequency requirement at different times.

[0010] Optionally, in one example of the above aspects, the application itself requires the following sampling frequencies: a preferred sampling frequency, a minimum sampling frequency, and a zero frequency; different device states include: working state, idle state, fault state, repair state, and maintenance state, with corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency for each device state; and the time includes working hours, non-working hours, and all day, with corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency for each time period.

[0011] Optionally, in one example of the above aspects, the device status information includes at least one of the following: the device's operating status; the device's planned operating time and non-operating time; device performance indicators; and hardware information.

[0012] Optionally, in one example of the above aspects, the operating state of the device includes at least one of the following: operating state, idle state, fault state, repair state, and maintenance state; the device performance indicators include at least one of the following: CPU utilization, memory usage, input / output read time, and CPU temperature; and the hardware information includes at least one of the following: CPU version and memory version.

[0013] Optionally, in one example of the above aspects, the real-time performance parameters include at least one of the following: real-time CPU utilization, memory usage, network load, and device response time.

[0014] According to another aspect of this disclosure, an apparatus for determining the data acquisition frequency is provided, wherein the data is acquired from a device and provided to an application for the application to monitor the device. The apparatus includes: an acquisition frequency requirement determination unit configured to determine the data acquisition frequency requirement of the application for the device; a device status determination unit configured to determine the status information of the device; and an acquisition frequency determination unit configured to determine the data acquisition frequency based on the determined data acquisition frequency requirement of the application for the device and the determined status information of the device, according to a preset rule.

[0015] Optionally, in one example of the above aspects, the apparatus for determining the data acquisition frequency further includes: an acquisition frequency adjustment unit configured to receive real-time performance parameters of the device and determine whether the acquisition frequency needs to be adjusted based on the real-time performance parameters.

[0016] Optionally, in one example of the above aspects, the application's data acquisition frequency requirement for the device includes at least one of the following: the application's own acquisition frequency requirement; the application's acquisition frequency requirement under different device states; and the application's acquisition frequency requirement at different times.

[0017] Optionally, in one example of the above aspects, the application itself requires the following sampling frequencies: a preferred sampling frequency, a minimum sampling frequency, and a zero frequency; different device states include: working state, idle state, fault state, repair state, and maintenance state, with corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency for each device state; and the time includes working hours, non-working hours, and all day, with corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency for each time period.

[0018] Optionally, in one example of the above aspects, the device status information includes at least one of the following: the device's operating status; the device's planned operating time and non-operating time; device performance indicators; and hardware information.

[0019] Optionally, in one example of the above aspects, the operating state of the device includes at least one of the following: operating state, idle state, fault state, repair state, and maintenance state; the device performance indicators include at least one of the following: CPU utilization, memory usage, input / output read time, and CPU temperature; and the hardware information includes at least one of the following: CPU version and memory version.

[0020] Optionally, in one example of the above aspects, the real-time performance parameters include at least one of the following: real-time CPU utilization, memory usage, network load, and device response time.

[0021] According to another aspect of this disclosure, a computing device is provided, comprising: at least one processor; and a memory coupled to said at least one processor, said memory for storing instructions that, when executed by said at least one processor, cause the processor to perform the method as described above.

[0022] According to another aspect of this disclosure, a non-transitory machine-readable storage medium is provided that stores executable instructions, which, when executed, cause the machine to perform the method described above.

[0023] According to another aspect of this disclosure, a computer program is provided, including computer-executable instructions that, when executed, cause at least one processor to perform the method described above.

[0024] According to another aspect of this disclosure, a computer program product is provided, which is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause at least one processor to perform the method as described above.

[0025] The method for determining the data acquisition frequency according to this disclosure can meet the requirements of the application as much as possible while ensuring the normal operation of the device, and avoid interference with the normal operation of the device due to data acquisition.

[0026] The method and apparatus for determining the data acquisition frequency according to this disclosure can avoid high requirements for configuration personnel and reduce the workload and complexity of setting an appropriate data acquisition frequency, especially when there are hundreds or thousands of different types of equipment.

[0027] The method for determining the data acquisition frequency according to this disclosure can avoid collecting invalid data, thereby reducing the amount of data collected and saving costs for data communication, storage and processing. Attached Figure Description

[0028] The above and other objects, features, and advantages of the present invention will be more readily understood by referring to the following description of embodiments of the invention in conjunction with the accompanying drawings. The components in the drawings are merely for illustrating the principles of the invention. In the drawings, the same or similar technical features or components will be represented by the same or similar reference numerals.

[0029] Figure 1 This is a flowchart illustrating an exemplary process of a method for determining the data acquisition frequency according to an embodiment of the present disclosure;

[0030] Figure 2 This is a block diagram illustrating an exemplary configuration of an apparatus for determining the data acquisition frequency according to an embodiment of the present disclosure;

[0031] Figure 3 This is a block diagram illustrating an exemplary configuration of an information processing system according to an embodiment of the present disclosure; and

[0032] Figure 4 A block diagram of a computing device for configuring data priority according to an embodiment of the present disclosure is shown.

[0033] Figure Labels

[0034] 100: Methods for determining the data acquisition frequency; S102, S104, S106, S108: Steps

[0035] 200: Device for determining data acquisition frequency; 202: Unit for determining acquisition frequency requirements.

[0036] 204: Equipment Status Determination Unit; 206: Acquisition Frequency Determination Unit

[0037] 208: Acquisition frequency adjustment unit; 300: Information processing system

[0038] 302: Equipment; 304: Cloud Platform

[0039] 306: Gateway; 400: Computing Device

[0040] 402: Processor; 404: Memory Detailed Implementation

[0041] The subject matter described herein will now be discussed with reference to exemplary embodiments. It should be understood that these embodiments are discussed merely to enable those skilled in the art to better understand and implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. The function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as needed in the various examples. For example, the described methods may be performed in a different order than described, and steps may be added, omitted, or combined. Furthermore, features described in some examples may be combined in other examples.

[0042] As used herein, the term "comprising" and its variations are open terms meaning "including but not limited to". The term "based on" means "at least partially based on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other definitions, whether explicit or implicit, may be included below. Unless explicitly indicated by the context, the definition of a term shall remain consistent throughout the specification.

[0043] As mentioned above, various devices in a factory can be monitored using applications, such as for equipment status monitoring, determining OEE (Overall Equipment Effectiveness), fault diagnosis, and predictive maintenance. All these functions rely on data collected from the devices. This disclosure provides an adaptive method for setting an appropriate data acquisition frequency for the devices.

[0044] According to the method disclosed herein, the appropriate data acquisition frequency for the device is determined by considering the application's requirements and the device's status. Furthermore, the acquisition frequency can be automatically adjusted based on the device's real-time on-site conditions.

[0045] The method disclosed herein can meet application requirements as much as possible while ensuring normal device operation. This method significantly reduces the workload and complexity of configuring data acquisition solutions for thousands of devices, reduces invalid data, and simultaneously ensures normal production activities.

[0046] First, Table 1 below lists some basic rules related to the data acquisition frequency to be considered in the method for determining the data acquisition frequency according to this disclosure.

[0047]

[0048]

[0049] Table 1

[0050] Based on the above basic rules, a method for determining the data collection frequency according to this disclosure is proposed. Figure 1 This is a flowchart illustrating an exemplary process of a method 100 for determining the data acquisition frequency according to an embodiment of the present disclosure.

[0051] exist Figure 1 First, in box S102, the application's data collection frequency requirements for the device are determined.

[0052] It's understandable that different applications have different data collection frequency requirements. Some applications need to collect data several times a day, some need to collect data several times an hour, and some may need to collect data thousands of times per second.

[0053] Furthermore, the frequency of data collection required by the application varies depending on the device's state or the time of day.

[0054] Therefore, in the method according to this disclosure, the determined application's data acquisition frequency requirements may include the following specific situations.

[0055] First, the application's requirements for the acquisition frequency are determined by the application's functionality.

[0056] In the method according to this disclosure, the application's requirements for the acquisition frequency may include a preferred acquisition frequency, a minimum acquisition frequency, and a zero frequency.

[0057] The preferred acquisition frequency is the optimal frequency for the application. Use the preferred acquisition frequency as long as the device's control system can handle it.

[0058] The minimum acquisition frequency is used when the equipment's control system is busy with normal operations and cannot share resources with the data acquisition function. If the equipment's control system cannot even handle the minimum acquisition frequency, the acquisition frequency should be further reduced to ensure normal production operations.

[0059] Zero frequency means that no data collection is required.

[0060] For example, in preventive maintenance applications, vibration data, current data, etc., require high sampling frequencies to meet the needs of subsequent data analysis. In scenarios where equipment status is transparent, high-frequency sampling is not required; usually, 1Hz sampling is sufficient to meet the needs of transparent equipment status on site. In energy consumption acquisition scenarios, acquiring the current energy consumption every hour, or even longer sampling periods, can meet the needs of energy consumption management. Data like energy consumption can be collected when the equipment is not in production, so as not to affect the normal operation of the equipment.

[0061] Secondly, the different states of a device can include: operating state, idle state, fault state, repair state, and maintenance state. For each different state of the device, the application may have different data acquisition frequency requirements.

[0062] For example, in energy monitoring applications, the data collection frequency should be lower when the device is in idle mode and higher when it switches to operating mode. Conversely, in predictive maintenance applications, data collection may not be necessary when the device is in idle or maintenance mode. In such cases, the data collection frequency can be significantly reduced to save on data communication, storage, and processing costs. Therefore, for each state of the device, a preferred collection frequency, minimum collection frequency, and zero frequency can be set separately. For instance, when the device is in "operating mode," data collection can be performed using one of the preferred, minimum, or zero frequencies set for that "operating mode," depending on the specific operating conditions of the device.

[0063] Furthermore, factories may have different working hours, including working hours, non-working hours, and 24-hour periods (e.g., morning shift, afternoon shift, and night shift). Different data collection frequencies can be set for different times; for example, the collection frequency during non-working hours should be set lower. In addition, each time period can also have corresponding preferred collection frequency, minimum collection frequency, and zero frequency.

[0064] Furthermore, there may be multiple applications for the same device, meaning that multiple applications may require the same data from the same device. In this case, the needs of multiple applications can be combined so that the collected data can meet the needs of all applications.

[0065] Thus, through the operations in block S102, the data acquisition frequency requirements of an application for a particular device under various circumstances can be determined. It is understood that the application's data acquisition frequency requirements for the device are not limited to those described above. Those skilled in the art, when determining the data acquisition frequency using the method according to this disclosure, may also consider other factors related to the application that may affect the data acquisition frequency, which will not be detailed here.

[0066] Next, in box S104, the status information of the device is determined.

[0067] The status information of the equipment comes from, for example, equipment on the factory site, or is obtained from a third-party system.

[0068] Equipment information may include, for example, the following: the equipment's operating status; the equipment's operating and non-operating hours; the equipment's performance indicators; and hardware information.

[0069] The operating status of the equipment can be, for example, operating status, idle status, fault status, maintenance status, and upkeep status.

[0070] Device performance metrics include, for example, CPU utilization, RAM usage, I / O read time, and CPU temperature.

[0071] For each equipment performance indicator, experienced engineers can pre-set thresholds for evaluating that performance indicator, or automated evaluation methods can be used, such as measuring the response time of the equipment's control system to assess its performance.

[0072] Hardware information can include CPU version, memory version, etc. Using this hardware information, the sampling frequency of one device can be used as a reference for other similar devices.

[0073] It is understood that the status information of the device is not limited to that described above. When using the method according to this disclosure to determine the data acquisition frequency, those skilled in the art may also consider other device status information that affects the data acquisition frequency, which will not be described in detail here.

[0074] Then, in block S106, based on the determined application's data collection frequency requirements for the device and the determined device status information, the data collection frequency is determined according to preset rules.

[0075] The preset rules here may include, for example, that the sampling frequency should at least meet the minimum requirements for implementing the application's functions; the sampling frequency should not be too frequent to avoid excessive costs in data transmission, storage, processing, and visualization; the sampling frequency should avoid affecting the device's performance; different sampling frequencies can be generated for different device states; and corresponding sampling frequencies can be customized for devices with different hardware and software, etc.

[0076] In the method according to this disclosure, appropriate rules can be preset by those skilled in the art based on experience, not limited to the preset rules described above, and then the appropriate data acquisition frequency for the device can be automatically calculated based on the determined application's data acquisition frequency requirements for the device and the determined device status information.

[0077] In one example, the method 100 for determining the data acquisition frequency may further include the operation in block S108, acquiring real-time performance parameters of the acquisition device, and determining whether the acquisition frequency needs to be adjusted based on the real-time performance parameters.

[0078] Specifically, it can collect real-time performance parameters of the device, such as CPU utilization, RAM usage, network load, and device response speed. For each performance parameter, a threshold can be preset. By comparing the data with the threshold, the device's performance status can be determined, thus determining whether the data collection frequency needs to be adjusted.

[0079] In one example, a test command can be periodically sent to the device, and the response time can be used to determine if the device's response speed is slow. This approach allows for the automation of numerous tests, and the test data can then be analyzed using a self-learning method to determine thresholds.

[0080] In this way, changes in equipment status or the impact of data collection on normal production can be determined based on real-time performance parameters, allowing for timely adjustments to the data collection frequency.

[0081] The data acquisition frequency determined by the method of this disclosure can, for example, be provided to a gateway responsible for data acquisition, which then acquires data according to the determined data acquisition frequency and provides it to the corresponding application.

[0082] The method disclosed herein allows for real-time monitoring of device usage. For example, if a device slows down, the data collection frequency can be automatically reduced, and an updated collection frequency can be sent to the gateway. No different processing is required for different devices.

[0083] The method for determining the data acquisition frequency according to this disclosure can strike a balance between demand and actual conditions based on the application's requirements and the operating status of field equipment.

[0084] The method for determining the data acquisition frequency according to this disclosure can meet the requirements of the application as much as possible while ensuring the normal operation of the device, and avoid interference with the normal operation of the device due to data acquisition.

[0085] The method for determining the data acquisition frequency according to this disclosure can avoid high requirements for configuration personnel and reduce the workload and complexity of setting an appropriate data acquisition frequency, especially when there are hundreds or thousands of different types of equipment.

[0086] The method for determining the data acquisition frequency according to this disclosure can avoid collecting invalid data, thereby reducing the amount of data collected and saving costs for data communication, storage and processing.

[0087] Figure 2 This is a block diagram illustrating an exemplary configuration of an apparatus 200 for determining the data acquisition frequency according to an embodiment of the present disclosure.

[0088] The device 200 for determining the data acquisition frequency includes: an acquisition frequency requirement determination unit 202, a device status determination unit 204, and an acquisition frequency determination unit 206.

[0089] The frequency acquisition requirement determination unit 202 is configured to determine the frequency acquisition requirements of the application for data from the device.

[0090] The device status determination unit 204 is configured to determine the status information of the device.

[0091] The sampling frequency determination unit 206 is configured to determine the data sampling frequency based on the determined application's data sampling frequency requirements for the device and the determined device status information, according to preset rules.

[0092] The device 200 for determining the data acquisition frequency may further include: an acquisition frequency adjustment unit 208, which is configured to receive real-time performance parameters of the device and determine whether the acquisition frequency needs to be adjusted based on the real-time performance parameters.

[0093] The application's data collection frequency requirements for the device include at least one of the following: the application's own collection frequency requirements; the application's collection frequency requirements under different device states; and the application's collection frequency requirements at different times.

[0094] The application itself has the following requirements for the acquisition frequency: preferred acquisition frequency, minimum acquisition frequency, and zero frequency; different device states include: working state, idle state, fault state, repair state, and maintenance state, and each device state has a corresponding preferred acquisition frequency, minimum acquisition frequency, and zero frequency; and the time includes working time, non-working time, and all day, and each time has a corresponding preferred acquisition frequency, minimum acquisition frequency, and zero frequency.

[0095] The status information of the device includes at least one of the following: the device's working status; the device's planned working time and non-working time; the device's performance indicators; and hardware information.

[0096] The operating status of the device includes at least one of the following: operating status, idle status, fault status, repair status, and maintenance status; the device performance indicators include at least one of the following: CPU utilization, memory usage, input / output read time, and CPU temperature; and the hardware information includes at least one of the following: CPU version and memory version.

[0097] The real-time performance parameters include at least one of the following: real-time CPU utilization, memory usage, network load, and device response time.

[0098] It should be noted that the above-mentioned application's requirements for the frequency of device data collection and the device status information are merely illustrative examples, and this disclosure is not limited thereto.

[0099] It should also be noted that, Figure 2 The structure of the device 200 for determining the data acquisition frequency and its constituent units shown is merely exemplary. Those skilled in the art can modify it as needed. Figure 2 The structural diagram shown is modified.

[0100] Details of the operation and function of each part of the device 200 for determining the data acquisition frequency can be found in conjunction with references. Figure 1 The relevant parts of the embodiments of the method 100 for determining the data collection frequency described herein are the same as or similar, and will not be described in detail here.

[0101] Figure 3 This is a block diagram illustrating an exemplary configuration of an information processing system 300 according to an embodiment of the present disclosure.

[0102] The information processing system 300 includes field devices 302, a cloud platform 304, a device 200 set on the cloud platform 304 to determine the data acquisition frequency, and a gateway 306.

[0103] The device 200, which determines the data collection frequency and is set on the cloud platform 304, can utilize the above reference. Figure 1 The method for determining the data acquisition frequency determines the acquisition frequency at which data is acquired from device 302. Device 200 can provide the determined data acquisition frequency to gateway 306, and then gateway 306 acquires data from device 302 according to the determined data acquisition frequency and provides it to the required application.

[0104] In addition, the gateway 306 can collect the real-time performance parameters of the device and provide them to the device 200 that determines the data collection frequency, so that the device 200 can determine whether the collection frequency needs to be adjusted based on the real-time performance parameters.

[0105] Those skilled in the art will understand that Figure 3 The information processing system 300 shown is merely a specific application example of the method for determining the data acquisition frequency according to this disclosure. It is understood that the device 200 for determining the data acquisition frequency according to this disclosure is not necessarily located on the cloud platform 304, but can be located in any suitable location, such as a local server. Furthermore, the determined data acquisition frequency does not necessarily need to be provided to the gateway, but can also be provided to other third-party applications.

[0106] As per the above reference Figures 1 to 3 Embodiments of a method, apparatus, and information processing system for determining the data acquisition frequency according to embodiments of this disclosure have been described. The apparatus for determining the data acquisition frequency described above can be implemented in hardware, software, or a combination of hardware and software.

[0107] Figure 4 A block diagram of a computing device 400 for determining the data acquisition frequency according to an embodiment of the present disclosure is shown. According to one embodiment, the computing device 400 may include at least one processor 402 that executes at least one computer-readable instruction (i.e., the elements implemented in software above) stored or encoded in a computer-readable storage medium (i.e., memory 404).

[0108] In one embodiment, computer-executable instructions are stored in memory 404, which, when executed, cause at least one processor 402 to perform the following actions: determine the frequency requirement for data collection from the application to the device; determine the status information of the device; and determine the data collection frequency according to a preset rule based on the determined frequency requirement for data collection from the application to the device and the determined status information of the device.

[0109] It should be understood that the computer-executable instructions stored in memory 404, when executed, cause at least one processor 402 to perform the above-described combinations in the various embodiments of this disclosure. Figure 1-3 The description includes various operations and functions.

[0110] According to one embodiment, a non-transitory machine-readable medium is provided. This non-transitory machine-readable medium may have machine-executable instructions (i.e., the elements implemented in software as described above), which, when executed by a machine, cause the machine to perform the above-described combinations in the various embodiments of this disclosure. Figure 1-3 The description includes various operations and functions.

[0111] According to one embodiment, a computer program is provided, including computer-executable instructions that, when executed, cause at least one processor to perform the above-described embodiments of the present disclosure. Figure 1-3 The description includes various operations and functions.

[0112] According to one embodiment, a computer program product is provided, including computer-executable instructions that, when executed, cause at least one processor to perform the above-described embodiments of the present disclosure. Figure 1-3 The description includes various operations and functions.

[0113] The specific embodiments described above with reference to the accompanying drawings are exemplary embodiments, but do not represent all embodiments that can be implemented or fall within the scope of the claims. The term "exemplary" as used throughout this specification means "serving as an example, instance, or illustration" and does not imply that it is "preferred" or "advantageous" compared to other embodiments. Specific details are included to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concepts of the described embodiments.

[0114] The foregoing description of this disclosure is provided to enable any person skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is consistent with the widest scope of the principles and novel features disclosed herein.

Claims

1. A method for determining the data acquisition frequency, wherein, The data is collected from the device and provided to the application for the application to monitor the device, which is equipment in a factory; the method includes: Determine the frequency of data collection requirements of the application from the device; Determine the status information of the device, wherein the status information includes the device's operating status, and the device's planned operating time and non-operating time; and Based on the application's data collection frequency requirements, the device's operating status, and the planned working time, the collection frequency is determined according to preset rules. When the device is not in operation, the sampling frequency is reduced; Obtain the hardware information of the device, and adjust the sampling frequency based on the hardware information; The system collects real-time performance parameters of the device and determines whether the acquisition frequency needs to be adjusted based on these parameters. A threshold is pre-set for each real-time performance parameter, and the device's performance status is determined by comparing it with the threshold. This determines whether the acquisition frequency needs to be adjusted to avoid interference with the normal operation of the device due to data acquisition.

2. The method as described in claim 1, wherein, The application's data collection frequency requirements for the device include at least one of the following: The application itself has specific requirements regarding the sampling frequency; The application's requirements for sampling frequency under different device states; and The application's requirements for acquisition frequency vary at different times.

3. The method as described in claim 2, wherein, The application itself has the following requirements for the acquisition frequency: preferred acquisition frequency, minimum acquisition frequency, and zero frequency; The different states of the equipment include: operating state, idle state, fault state, maintenance state, and upkeep state. For each state, there are corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency. The time includes working hours, non-working hours, and the whole day, and there are corresponding preferred sampling frequencies, minimum sampling frequencies, and zero frequencies for different times.

4. The method of claim 1, wherein, The status information also includes device performance metrics, which include at least one of the following: CPU utilization, memory usage, input / output read / write time, and CPU temperature; and The hardware information includes at least one of the following: the version of the central processing unit and the version of the memory.

5. The method as described in claim 1, wherein, The real-time performance parameters include at least one of the following: Real-time CPU utilization, memory usage, network load, and device response time.

6. A device (200) for determining the data acquisition frequency, wherein, The data is collected from the device and provided to the application so that the application can monitor the device, which is a device in a factory. The device (200) includes: The frequency acquisition requirement determination unit (202) is configured to determine the frequency acquisition requirement of the application for data from the device. The device status determination unit (204) is configured to determine device status information, wherein the status information includes the device's operating status, and the device's planned operating time and non-operating time; and The sampling frequency determination unit (206) is configured to determine the sampling frequency based on the application's sampling frequency requirements for device data, the device's working status, and the planned working time, according to a preset rule; reduce the sampling frequency when the device is not in working time; acquire the device's hardware information, and adjust the sampling frequency based on the hardware information; The acquisition frequency adjustment unit (208) is configured to acquire the real-time performance parameters of the device and determine whether the acquisition frequency needs to be adjusted based on the real-time performance parameters. A threshold is preset for each real-time performance parameter, and the performance status of the device is determined by comparing it with the threshold, thereby determining whether the acquisition frequency needs to be adjusted to avoid interference with the normal operation of the device due to data acquisition.

7. The apparatus (200) as claimed in claim 6, wherein, The application's data collection frequency requirements for the device include at least one of the following: The application itself has specific requirements regarding the sampling frequency; The application's requirements for sampling frequency under different device states; and The application's requirements for acquisition frequency vary at different times.

8. The apparatus (200) as claimed in claim 7, wherein, The application itself has the following requirements for the acquisition frequency: preferred acquisition frequency, minimum acquisition frequency, and zero frequency; The different states of the equipment include: operating state, idle state, fault state, maintenance state, and upkeep state. For each state, there are corresponding preferred sampling frequency, minimum sampling frequency, and zero frequency. The time includes working hours, non-working hours, and the whole day, and there are corresponding preferred sampling frequencies, minimum sampling frequencies, and zero frequencies for different times.

9. The apparatus (200) as claimed in claim 6, wherein, The operating status of the device includes at least one of the following: operating status, idle status, fault status, maintenance status, and upkeep status; The status information also includes device performance metrics, which include at least one of the following: CPU utilization, memory usage, input / output read / write time, and CPU temperature; and The hardware information includes at least one of the following: the version of the central processing unit and the version of the memory.

10. The apparatus (200) as claimed in claim 6, wherein, The real-time performance parameters include at least one of the following: Real-time CPU utilization, memory usage, network load, and device response time.

11. A computing device (400), comprising: At least one processor (402); as well as A memory (404) coupled to the at least one processor (402), the memory being used to store instructions that, when executed by the at least one processor (402), cause the processor (402) to perform the method as described in any one of claims 1 to 5.

12. A non-transitory machine-readable storage medium storing executable instructions that, when executed, cause the machine to perform the method as described in any one of claims 1 to 5.

13. A computer program product tangibly stored on a computer-readable medium and comprising computer-executable instructions that, when executed, cause at least one processor to perform the method according to any one of claims 1 to 5.

Images