Acquisition task configuration method and device, computer equipment and readable storage medium

Abstract

The invention relates to the technical field of intelligent configuration, and discloses a collection task configuration method and device, computer equipment and a readable storage medium. Firstly, in response to a trigger instruction, data acquisition omission information is determined based on historical acquisition data reported by an acquisition terminal device; and then, based on the data acquisition omission information, determining a first target acquisition task, reducing unnecessary acquisition task and junk task generation, and ensuring high efficiency and accuracy of task execution. Then, intelligent task configuration is performed based on the first target acquisition task, a first task instruction is generated, and the first task instruction is issued to the acquisition terminal equipment, so that the acquisition terminal equipment determines first target acquisition data based on the first task instruction; and finally, first target acquisition data reported by the acquisition terminal equipment is received, so that timely supplementary acquisition of the leakage point data is ensured, and data missing is prevented. According to the embodiment, the accuracy and integrity of the reported data are ensured, and the data quality is improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent configuration technology, and in particular to a collection task configuration method, device, computer equipment and readable storage medium. Background Art

[0002] Taking into account various business application scenarios and to better meet users' actual needs, we adopted a template-based, visual, and intelligent configuration strategy. By comparing and analyzing the effectiveness of intelligent configuration technologies and strategies, as well as optimization algorithms and frameworks, we further improved the overall system performance. At the same time, by rationally advancing the technology of the collection front-end system and implementing a task-intelligent configuration data collection strategy, we can effectively address the massive data access demands brought about by future business development, enhance the system's ability to process massive amounts of data, and provide favorable support for large-scale data collection. Summary of the Invention

[0003] The embodiments of this specification aim to solve at least one of the technical problems in the related art to a certain extent. To this end, the embodiments of this specification propose a collection task configuration method, apparatus, computer device and readable storage medium.

[0004] The present disclosure provides a method for configuring a collection task, the method comprising:

[0005] In response to a trigger instruction, determining data collection omission information based on historical collection data reported by the collection terminal device;

[0006] Determining a first target acquisition task based on the data acquisition omission information;

[0007] Performing task configuration based on the first target acquisition task, generating a first task instruction, and sending the first task instruction to the acquisition terminal device so that the acquisition terminal device determines the first target acquisition data based on the first task instruction;

[0008] Receive the first target acquisition data reported by the acquisition terminal device.

[0009] In one embodiment, determining data collection omission information based on historical collection data reported by the collection terminal device includes:

[0010] Acquiring historical collection data reported by the collection terminal device, wherein the historical collection data corresponds to an actual collection location;

[0011] The actual collection locations of the historically collected data are compared with the preset collection locations to determine missing data collection information.

[0012] In one embodiment, the first target acquisition task includes a plurality of sub-acquisition tasks, and the performing of task configuration based on the first target acquisition task to generate a first task instruction includes:

[0013] Combining the multiple sub-collection tasks based on configuration parameters to obtain at least one collection task group, wherein the configuration parameters include at least one of a protocol supported by the collection terminal device, a collection data type, a supplementary collection location, and a message length of the collection terminal device;

[0014] Perform task configuration based on the at least one acquisition task group and generate at least one task instruction.

[0015] In one embodiment, the task instruction includes execution sequence information, and the acquisition terminal device determines the first target acquisition data based on the first task instruction, including:

[0016] The acquisition terminal device sequentially executes the target task instructions corresponding to the execution sequence information based on the execution sequence information;

[0017] The acquisition terminal device determines first target acquisition data based on the target task instruction.

[0018] In one embodiment, obtaining the historical collection data reported by the collection terminal device includes:

[0019] Configuring the acquisition parameters based on the acquisition task template to obtain a second target acquisition task, wherein the newly added protocol corresponding to the second target acquisition task will be stored in the database;

[0020] Performing task configuration based on the second target acquisition task, generating a second task instruction, and sending the second task instruction to the acquisition terminal device so that the acquisition terminal device determines the second target acquisition data based on the second task instruction;

[0021] The second target collection data reported by the collection terminal device is received and analyzed to obtain the historical collection data.

[0022] In one embodiment, the trigger instruction includes any one of a timed trigger instruction and a manual trigger instruction, and the data collection omission information is stored in a cache.

[0023] In one embodiment, determining the first target acquisition task based on the data acquisition omission information includes:

[0024] The data collection omission information is configured based on the supplementary collection task template to obtain the first target collection task.

[0025] In one embodiment, the method further comprises:

[0026] After receiving the first target acquisition data reported by the acquisition terminal device, parsing the first target acquisition data to obtain target structured data;

[0027] The target structured data is stored in a database.

[0028] The embodiments of this specification provide a collection task configuration device, the device comprising:

[0029] a collection omission information determination module, configured to determine data collection omission information based on historical collection data reported by a collection terminal device in response to a trigger instruction;

[0030] a target acquisition task determination module, configured to determine a first target acquisition task based on the data acquisition omission information;

[0031] a task instruction generation and delivery module, configured to perform task configuration based on the first target acquisition task, generate a first task instruction, and deliver the first task instruction to the acquisition terminal device, so that the acquisition terminal device determines the first target acquisition data based on the first task instruction;

[0032] The target acquisition data receiving module is used to receive the first target acquisition data reported by the acquisition terminal device.

[0033] In one embodiment, the first target acquisition task includes multiple sub-acquisition tasks, and the task instruction generation and issuance module further includes: combining the multiple sub-acquisition tasks based on configuration parameters to obtain at least one acquisition task group, wherein the configuration parameters include at least one of the protocol supported by the acquisition terminal device, the acquisition data type, the supplementary acquisition location, and the message length of the acquisition terminal device; performing task configuration based on the at least one acquisition task group to generate at least one task instruction.

[0034] An embodiment of this specification provides a computer device, which includes: a memory, and one or more processors communicatively connected to the memory; the memory stores instructions that can be executed by the one or more processors, and the instructions are executed by the one or more processors to enable the one or more processors to implement the steps of the method described in any of the above embodiments.

[0035] The embodiments of this specification provide a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method described in any one of the above embodiments are implemented.

[0036] An embodiment of this specification provides a computer program product, which includes instructions. When the instructions are executed by a processor of a computer device, the computer device can perform the steps of the method described in any of the above embodiments.

[0037] In the implementation manner of the above specification, first, in response to a trigger instruction, data collection omission information is determined based on the historical collection data reported by the collection terminal device. Next, based on the data collection omission information, the first target collection task is determined to reduce the generation of unnecessary collection tasks and junk tasks, thereby ensuring the efficiency and accuracy of task execution. Then, intelligent task configuration is performed based on the first target collection task, a first task instruction is generated, and the first task instruction is sent to the collection terminal device so that the collection terminal device determines the first target collection data based on the first task instruction. Finally, the first target collection data reported by the collection terminal device is received to ensure that the missing data is collected in a timely manner to prevent data loss. The above implementation manner ensures the accuracy and completeness of the reported data, improves the quality of the data, and provides a more reliable basis for subsequent data analysis and decision-making. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 A flowchart of a collection task configuration method provided in an embodiment of this specification;

[0039] Figure 2 A schematic diagram of a process for determining missing information in data collection provided in an embodiment of this specification;

[0040] Figure 3 A schematic diagram of a process for generating task instructions provided in an embodiment of this specification;

[0041] Figure 4 A schematic diagram of a process for determining first target acquisition data provided in an embodiment of this specification;

[0042] Figure 5 A schematic diagram of the process of obtaining historical collection data reported by a collection terminal device provided in the embodiment of this specification;

[0043] Figure 6 A schematic diagram of a process for storing target structured data provided in an embodiment of this specification;

[0044] Figure 7 A schematic diagram of an intelligent task system for IoT collection provided in an embodiment of this specification;

[0045] Figure 8 A schematic diagram of a collection task configuration device provided in an embodiment of this specification;

[0046] Figure 9This is a diagram of the internal structure of a computer device provided in accordance with an embodiment of this specification. DETAILED DESCRIPTION

[0047] The following describes embodiments of the present invention in detail, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and are not to be construed as limiting the present invention.

[0048] The electricity consumption information collection system is positioned as the "general entrance for perception data and general exit for control instructions" and has core functions such as security authentication, full-scale collection, dispatching control, massive storage, real-time analysis, and global monitoring.

[0049] To meet the actual needs of users, the system's design comprehensively considers various business application scenarios and adopts a template-based, visual, and intelligent configuration strategy. Through continuous optimization of intelligent configuration technology, optimization algorithms, and frameworks, overall performance is improved. Furthermore, the advancement of front-end acquisition system technology and the rational application of intelligent task configuration strategies provide strong support for handling massive data inflows and enhance data processing capabilities.

[0050] However, the configuration and execution of pre-collection tasks in related technologies have the following major problems:

[0051] Simple and inefficient task configuration: Pre-collection tasks can only be configured and scheduled using cron expressions. This configuration method not only increases system memory consumption, but also leads to poor task execution accuracy and real-time performance due to inaccurate collection times and task intervals.

[0052] Task execution backlog and delay: Because collection tasks are processed based on task configuration and type, this often leads to execution backlogs when the task volume is large. This affects the success rate of page collection instructions and, under high load, can easily lead to task timeouts or loss, further compromising data integrity and reliability.

[0053] Lack of real-time monitoring and precise data collection mechanisms: Data collection can only be performed through polling, without real-time monitoring and feedback of data collection status. This method not only leads to high terminal traffic consumption, but also fails to accurately collect data point by point, resulting in a waste of resources.

[0054] Data collection lags: Data collection tasks primarily process data from the T-1 day, which means there's a time delay in data collection. This means the calculation results for the current task lack real-time performance, leading to insufficient data support for indicator forecasting and statistics, impacting the timeliness and accuracy of decision-making.

[0055] Based on the above analysis, the embodiment of this specification provides a method for configuring a collection task. First, in response to a trigger instruction, data collection omission information is determined based on the historical collection data reported by the collection terminal device. Then, based on the data collection omission information, the first target collection task is determined to reduce the generation of unnecessary collection tasks and junk tasks, thereby ensuring the efficiency and accuracy of task execution. Then, intelligent task configuration is performed based on the first target collection task, a first task instruction is generated, and the first task instruction is sent to the collection terminal device so that the collection terminal device determines the first target collection data based on the first task instruction. Finally, the first target collection data reported by the collection terminal device is received to ensure that the missing data is collected in a timely manner to prevent data loss. The above embodiment ensures the accuracy and completeness of the reported data, improves the quality of the data, and provides a more reliable basis for subsequent data analysis and decision-making.

[0056] This specification provides a method for configuring a collection task. Figure 1 , the method may include the following steps:

[0057] S110 . In response to a trigger instruction, determine data collection omission information based on historical collection data reported by the collection terminal device.

[0058] S120: Determine a first target collection task based on data collection omission information.

[0059] S130 , performing task configuration based on the first target acquisition task, generating a first task instruction, and sending the first task instruction to the acquisition terminal device so that the acquisition terminal device determines the first target acquisition data based on the first task instruction.

[0060] S140: Receive first target acquisition data reported by the acquisition terminal device.

[0061] Specifically, historically collected data can be data proactively reported by a collection terminal device with an active reporting function, or data reported by a collection terminal device without such a function in accordance with periodic task instructions. The historically collected data is associated with time information, identifying the specific time at which these data records were collected. In response to a trigger instruction, the system determines which data were not successfully reported or which collection locations were successfully reported based on the historically collected data reported by the collection terminal device, thereby determining missing data collection information. Parameters included in the missing data collection information are then configured to generate a specific supplementary collection task, resulting in a first target collection task. The system then configures the first target collection task and generates a corresponding first task instruction. The first task instruction includes at least one task instruction, which generally includes information such as the read data, execution priority, and meter ID. The system issues the first task instruction to the collection terminal device, so that upon receiving the first task instruction, the collection terminal device executes the collection according to the execution order of each task instruction, determines the target collected data corresponding to each task instruction, and reports it to the system. The target collected data corresponding to all task instructions constitute the first target collected data. The system receives primary target data reported by acquisition terminals and further normalizes it for storage in the database. This primary target data also includes time information, identifying the specific moment the data record was collected. By adding this data to the database in chronological order, it ensures that all data is accurately mapped to the corresponding time point, guaranteeing data integrity and timeliness.

[0062] It should be noted that after acquiring the first target acquisition data, it is necessary to re-compare the first target acquisition data with the data acquisition omission information to determine whether any new data acquisition omission information exists. If any new data acquisition omission information exists, a new target acquisition task is determined based on the new data acquisition omission information. Task configuration is then performed based on the new target acquisition task, and new task instructions are generated. These new task instructions are then sent to the acquisition terminal device, which then determines new target acquisition data based on the new task instructions until all the data required to be acquired within the preset time period is complete.

[0063] In the above implementation, first, in response to a trigger instruction, data collection omission information is determined based on the historical collection data reported by the collection terminal device. Next, based on the data collection omission information, the first target collection task is determined to reduce the generation of unnecessary collection tasks and junk tasks, thereby ensuring the efficiency and accuracy of task execution. Then, intelligent task configuration is performed based on the first target collection task, a first task instruction is generated, and the first task instruction is sent to the collection terminal device so that the collection terminal device determines the first target collection data based on the first task instruction. Finally, the first target collection data reported by the collection terminal device is received to ensure that the missing data is collected in a timely manner to prevent data loss. The above implementation ensures the accuracy and completeness of the reported data, improves the quality of the data, and provides a more reliable basis for subsequent data analysis and decision-making.

[0064] In some embodiments, see Figure 2 , determining data collection omission information based on historical collection data reported by the collection terminal device may include the following steps:

[0065] S210: Acquire historical collection data reported by the collection terminal device.

[0066] S220: Compare the actual collection sites based on historical data collection with the preset collection sites to determine missing information in data collection.

[0067] Among them, the historical collection data corresponds to the actual collection sites.

[0068] Specifically, historical data collected by the acquisition terminal device is extracted from the database. This historical data includes the actual acquisition location. Next, based on the historical data, the actual acquisition location and all corresponding acquisition data (e.g., voltage and current) are extracted. The actual acquisition location is then compared with the pre-defined acquisition locations in the system. The pre-defined acquisition locations are a set of locations defined in advance based on the system design and data acquisition requirements. During this comparison, if a pre-defined acquisition location does not appear among the actual acquisition locations, it is identified as a missed acquisition location. A missed acquisition location means that all acquired data at that location is missed. All acquired data (e.g., voltage and current) corresponding to the actual acquisition location is compared with the acquisition data required by the pre-defined acquisition location to determine whether any acquired data (e.g., voltage) is missed at a particular acquisition location. Data acquisition missed information is determined based on the missed acquisition location and the missed acquired data at that location.

[0069] In the above implementation, historical collection data reported by the collection terminal device is obtained, and the actual collection locations of the historical collection data are compared with the preset collection locations to determine the missing information in the data collection so as to perform the subsequent supplementary collection task and realize the integrity of the reported data, so as to ensure the accuracy of the subsequent corresponding analysis.

[0070] In some embodiments, see Figure 3 The first target acquisition task includes multiple sub-acquisition tasks. Task configuration based on the first target acquisition task and generating a first task instruction may include the following steps:

[0071] S310: Combine multiple collection subtasks based on configuration parameters to obtain at least one collection task group.

[0072] S320: Perform task configuration based on at least one acquisition task group and generate at least one task instruction.

[0073] The configuration parameters include at least one of the protocol supported by the acquisition terminal device, the acquisition data type, the supplementary acquisition location, and the message length of the acquisition terminal device.

[0074] Specifically, the first target collection task consists of multiple sub-collection tasks. Each sub-collection task represents an independent data collection operation, typically executed for a specific meter, specific data item, or using a specific protocol. Multiple sub-collection tasks are combined using configuration parameters to form at least one collection task group. During the sub-task combination process, the system automatically adjusts the sub-task combinations based on the configuration parameters to optimize resource utilization and improve data collection efficiency. Task configuration is then performed for each collection task group, generating a varying number of task instructions based on the different combinations.

[0075] For example, if the message length of the terminal device is the total length of the current of three meters, the collection task group is configured to generate one task instruction. If the message length of the terminal device is the total length of the current of one meter, the collection task group is configured to generate three task instructions.

[0076] In some implementations, multiple sub-collection tasks are grouped according to the protocols supported by the collection terminal device, and sub-collection tasks supporting the same protocol are grouped into a collection task group.

[0077] In some implementations, multiple sub-collection tasks are grouped according to the type of data being collected, and sub-collection tasks that collect the same type of data are grouped into a collection task group. For example, sub-collection tasks that collect the current of meter A, meter B, and meter C are grouped into a collection task group.

[0078] In some implementations, multiple sub-collection tasks are grouped based on the supplementary sampling location and the type of data collected. Sub-collection tasks that collect the same supplementary sampling location and the same type of data are grouped into a collection task group. For example, sub-collection tasks that collect the current at supplementary sampling location T1 of meter A, the current at supplementary sampling location T1 of meter B, and the current at supplementary sampling location T1 of meter C are grouped into a collection task group.

[0079] In some implementations, multiple sub-collection tasks are grouped based on the message length and data type of the data collected by the collection terminal device. Sub-collection tasks that collect the same type of data and whose collected data type length can meet the message length are grouped into a collection task group to reduce the length of the frame. For example, if the message length of the collection terminal device is the total length of the current of three electricity meters (type M), then the current collected at the T1 collection point of meter A (type M), the current collected at the T1 collection point of meter B (type M), and the current collected at the T1 collection point of meter C (type M) can be grouped into a sub-collection task group.

[0080] In the above implementation, multiple sub-collection tasks are combined based on configuration parameters to obtain at least one collection task group, and task configuration is performed based on at least one collection task group to generate at least one task instruction. The composition of the collection task is flexibly adjusted according to actual needs, thereby improving the flexibility of task combination.

[0081] In some embodiments, see Figure 4 The task instruction includes execution sequence information, and the acquisition terminal device determines the first target acquisition data based on the first task instruction, which may include the following steps:

[0082] S410. The acquisition terminal device sequentially executes target task instructions corresponding to the execution sequence information based on the execution sequence information.

[0083] S420: The collection terminal device determines first target collection data based on the target task instruction.

[0084] Specifically, the task instruction includes execution sequence information, which specifies the order that the acquisition terminal device should follow during the execution of the task instruction. During the execution process, the acquisition terminal device executes each task instruction in sequence according to the execution sequence information in the task instruction. The task instruction that the acquisition terminal device determines to be executed currently based on the execution sequence information is used as the target task instruction. Each target task instruction has clear guidelines. For example, the target task instruction may include the type of data to be collected, the source of the data, the collection location, etc. The acquisition terminal device executes the target task instruction to determine the corresponding target collection data to ensure the timely reporting of key data. Each task instruction is executed in sequence according to the execution sequence information, and the target collection data corresponding to all target task instructions constitute the first target collection data.

[0085] In the above implementation, the terminal device sequentially executes the target task instructions corresponding to the execution sequence information based on the execution sequence information, and the acquisition terminal device determines the first target acquisition data based on the target task instructions to ensure timely reporting of key data.

[0086] In some embodiments, see Figure 5 , obtaining the historical collection data reported by the collection terminal device, may include the following steps:

[0087] S510: Configure acquisition parameters based on the acquisition task template to obtain a second target acquisition task.

[0088] S520: Perform task configuration based on the second target acquisition task, generate a second task instruction, and send the second task instruction to the acquisition terminal device so that the acquisition terminal device determines the second target acquisition data based on the second task instruction.

[0089] S530: Receive the second target collection data reported by the collection terminal device and parse it to obtain historical collection data.

[0090] Among them, the newly added protocol corresponding to the second target acquisition task will be stored in the database.

[0091] Specifically, the collection task template includes multiple key configuration items, which are core elements that define the execution method of the collection task and the data collected. For example, configuration items may include information such as data collection type, adaptation protocol, data length, and meter ID. When some collection terminal devices do not support active reporting, the system must rely on periodic task instructions to trigger the collection terminal devices to report data. To ensure the smooth execution of the collection task, the system configures the collection parameters using the collection task template to generate a specific collection task, resulting in a second target collection task. The second target collection task consists of multiple subtasks, each of which contains specific collection rules (such as the collection cycle, collection duration, specific data items to be collected, meter ID, etc.). The system configures the second target collection task and generates a corresponding second task instruction. The second task instruction includes at least one task instruction, which generally includes information such as the data to be read, execution priority, and meter ID. The system issues the second task instruction to the collection terminal device, so that after receiving the second task instruction, the collection terminal device executes the collection according to the execution order of each task instruction, determines the target collection data corresponding to the task instruction, and reports it to the system. The target collection data corresponding to all task instructions constitute the second target collection data. The system parses the second target collection data reported by the terminal device and stores the parsed structured data as historical collection data in the database to facilitate the subsequent determination of missing information in data collection.

[0092] In some implementations, the system can group subtasks based on factors such as the protocols supported by the collection terminal devices, the type of data being collected, and the message length of the collection terminal devices. It can also intelligently prioritize different subtasks based on the timeliness and importance of the collection tasks, ensuring that the task instructions corresponding to high-priority subtasks are executed first when resources are in contention, ensuring the timely collection of critical data.

[0093] It should be noted that since data reporting from collection terminal devices is typically periodic, each task instruction issued will trigger multiple data collection requests. Frequent database access can significantly impact system performance, especially when there are a large number of devices and frequent tasks. Therefore, to improve system efficiency and reduce database burden, secondary collection tasks can be cached to reduce database access. Furthermore, the execution time, execution priority, execution strategy, and collection information of secondary collection tasks can be dynamically monitored and modified within the cache, making the execution of secondary collection tasks more targeted.

[0094] In some implementations, as data collection equipment continues to expand and update, new meters or data collection terminals may appear. These new devices may use different protocols. Therefore, to support these new devices, the system must have dynamic expansion capabilities that can identify and adapt to new protocols that are not yet stored and store them in the database. This protocol expansion mechanism ensures stable operation in an environment with constantly updated devices.

[0095] In the above implementation, the collection parameters are configured based on the collection task template to obtain the second target collection task, the task configuration is performed based on the second target collection task, the second task instruction is generated, and the second task instruction is sent to the collection terminal device, so that the collection terminal device determines the second target collection data based on the second task instruction, receives the second target collection data reported by the collection terminal device and parses it to obtain historical collection data, thereby ensuring the traceability of the data and providing a basis for subsequent supplementary collection tasks.

[0096] In some implementations, the trigger instruction may include any one of a timed trigger instruction and a manual trigger instruction.

[0097] Specifically, a scheduled trigger automatically triggers execution at preset intervals or specified time points. For example, a scheduled trigger can schedule regular full data collection tasks or supplement missed data. Scheduled triggers can be set to run hourly, daily, weekly, or monthly intervals, depending on your needs. Scheduled triggers ensure timely and automatic execution of tasks, reducing manual intervention.

[0098] Manual triggers are initiated by operators and are typically used for temporary or emergency tasks. For example, if the system detects that certain critical data is not being reported properly, operators can manually trigger a data recollection task to ensure data integrity. Manual triggers provide flexibility, allowing tasks to be initiated instantly based on specific needs.

[0099] In the above implementation, the trigger instruction includes any one of a timed trigger instruction and a manual trigger instruction, which improves flexibility and schedulability, and the two complement each other, helping to improve the stability and adaptability of the system.

[0100] In some embodiments, data collection omission information is stored in a cache.

[0101] Specifically, due to network problems between the data collection terminal device and the electricity meter, communication delays or interruptions between the data collection terminal device and the system, equipment failures or other external factors, some data may not be reported to the system in a timely manner. In order to ensure the integrity of the data and avoid data missing or loss, the system will determine the missing information of data collection based on the system that has been reported and temporarily store it in the cache. The cache usually uses an efficient memory storage mechanism (such as Redis) for fast access and processing. The missing information of data collection is usually stored in the cache using an appropriate data structure. It should be noted that the cache is not used for long-term storage, but as a temporary storage area.

[0102] In the above implementation, the data collection omission information is stored in the cache, which reduces the number of database accesses and improves the system response speed.

[0103] In some implementations, determining the first target acquisition task based on the data acquisition omission information may further include: configuring the data acquisition omission information based on a supplementary acquisition task template to obtain the first target acquisition task.

[0104] In some cases, data reporting may not be completed in real time due to factors such as processing delays or network transmission. Therefore, to ensure that data from all time periods is reported, a preset time period is used. At the end of the preset time period, a recollection task is performed based on the missed data. The preset time period can be used to generate a timer trigger instruction. For example, the preset time period can be one day, with the recollection task for day T-1 being executed at dawn on day T.

[0105] Specifically, the supplementary acquisition task template includes multiple key configuration items, such as data collection type, adaptation protocol, data length, collection location and other information. During the data reporting process, there will be some missing data. In order to solve these omission problems, at the end of the preset time period, the system will use the supplementary acquisition task template to configure the data collection missing information in detail. The information of each missing data (for example, the device ID of the missing data, the time interval of the missing data, etc.) is matched with the configuration items in the supplementary acquisition task template to generate a specific supplementary acquisition task and obtain the first target acquisition task.

[0106] It should be noted that since there are typically multiple missing data collection information, each piece of missing data collection information corresponds to an independent sub-collection task. The information of each missing data collection information (e.g., the meter ID of the missing data, the collection location of the missing data, etc.) is matched with the configuration items in the supplementary collection task template to generate a specific supplementary collection task, resulting in a sub-collection task. All sub-collection tasks constitute the first target collection task.

[0107] In the above implementation, the data collection omission information is configured based on the supplementary collection task template, and the first target collection task is obtained through a standardized and normalized supplementary collection process, providing support for subsequent combination.

[0108] In some embodiments, see Figure 6 , the method may include the following steps:

[0109] S610: After receiving first target collection data reported by a collection terminal device, the first target collection data is parsed to obtain target structured data.

[0110] S620: Store the target structured data in a database.

[0111] Specifically, the data collection terminal device supports a variety of meter types, including but not limited to single-phase, three-phase, and smart meters. Different types of meters have different data structures. For example, the data structure of a single-phase meter is relatively simple, including basic information such as power consumption (e.g., kilowatt-hours) and power. The data structure of a smart meter is more complex, recording not only traditional power consumption and power data, such as three-phase current, but also information such as load curves and frequency, which reflect the detailed dynamic changes in power consumption. Furthermore, the data generated by different meters typically uses different formats and protocols. Therefore, after the meter transmits data to the data collection terminal device, the terminal device selects the required data items based on the task instructions corresponding to the target task, determines the first target data to be reported, and reports it. The system receives the first target data reported by the data collection terminal device and parses it accordingly, identifying the data format and protocol type. Then, based on pre-set conversion rules, it converts the first target data into unified, standardized structured data, resulting in the target structured data. Finally, the target structured data is stored in the corresponding table in the database based on information such as timestamp and device ID, ensuring efficient data access and query performance.

[0112] In the above implementation, after receiving the first target acquisition data reported by the acquisition terminal device, the first target acquisition data is parsed to obtain target structured data, and the target structured data is stored in a database to achieve standardized management and efficient access of data.

[0113] The embodiment of this specification also provides an intelligent task system for IoT collection that is used to implement the collection task configuration method. Figure 7The system includes a front-end, a presentation layer, a business layer, a data layer, a communication layer, and a database. The front-end includes a user interface for interacting with the user to determine whether it is a scheduled task or a manually triggered task. If it is a scheduled task, the presentation layer triggers the scheduled task according to the task instructions in the cache. If it is a manually triggered task, the presentation layer sends down a communication connection via TCP to implement the task. The business layer is the core logic processing layer, including intelligent task template configuration, task delivery monitoring, intelligent leakage point maintenance, data item and protocol combination, and real-time combination of task supplementary sampling. The data layer is the data processing and storage layer, including Kafka message processing and transaction processing, Redis data cache, and read-write database and stored procedures (Zookeeper). The communication layer is a communication framework, including Netty, TIO, and Curator. The database is the data persistence layer, using Oracle and MySQL databases. Among them, the Oracle database can store target structured data, and the MySQL database can store protocols.

[0114] This specification provides a collection task configuration device 800, see Figure 8 The collection task configuration device 800 includes: a collection omission information determination module 810, a target collection task determination module 820, a task instruction generation and issuance module 830, and a target collection data receiving module 840.

[0115] A collection omission information determination module 810 is configured to determine data collection omission information based on historical collection data reported by a collection terminal device in response to a trigger instruction;

[0116] a target acquisition task determination module 820, configured to determine a first target acquisition task based on the data acquisition omission information;

[0117] A task instruction generation and delivery module 830 is configured to perform task configuration based on the first target acquisition task, generate a first task instruction, and deliver the first task instruction to the acquisition terminal device so that the acquisition terminal device determines the first target acquisition data based on the first task instruction;

[0118] The target acquisition data receiving module 840 is configured to receive the first target acquisition data reported by the acquisition terminal device.

[0119] In some embodiments, the first target acquisition task includes multiple sub-acquisition tasks, and the task instruction generation and issuance module 830 further includes: combining the multiple sub-acquisition tasks based on configuration parameters to obtain at least one acquisition task group, wherein the configuration parameters include at least one of the protocol supported by the acquisition terminal device, the acquisition data type, the supplementary acquisition location, and the message length of the acquisition terminal device; performing task configuration based on the at least one acquisition task group to generate at least one task instruction.

[0120] For a detailed description of the acquisition task configuration device, please refer to the description of the acquisition task configuration method above, which will not be repeated here.

[0121] An embodiment of this specification provides a computer device including a memory and a processor. The memory stores a computer program, and the processor implements the method steps in the above embodiment when executing the computer program.

[0122] An embodiment of this specification provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method in any of the above embodiments are implemented.

[0123] One embodiment of the present specification provides a computer program product, which includes instructions. When the instructions are executed by a processor of a computer device, the computer device is enabled to perform the steps of the method of any of the above embodiments.

[0124] In some embodiments, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 9 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a method for configuring an acquisition task is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse.

[0125] Those skilled in the art will understand that Figure 9The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution disclosed in this specification, and does not constitute a limitation on the computer device to which the solution disclosed in this specification is applied. Specifically, the computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0126] It should be noted that the logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic device), a portable computer disk cartridge (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable compact disc read-only memory (CDROM). Furthermore, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing it in a suitable manner if necessary, and then storing it in a computer memory.

Claims

1. A collection task configuration method, characterized in that: The method comprises: In response to a trigger instruction, determining data collection omission information based on historical collection data reported by the collection terminal device; Determining a first target acquisition task based on the data acquisition omission information; Performing task configuration based on the first target acquisition task, generating a first task instruction, and sending the first task instruction to the acquisition terminal device so that the acquisition terminal device determines the first target acquisition data based on the first task instruction; Receive the first target acquisition data reported by the acquisition terminal device.

2. The method according to claim 1, characterized in that The determining of data collection omission information based on historical collection data reported by the collection terminal device includes: Acquiring historical collection data reported by the collection terminal device, wherein the historical collection data corresponds to an actual collection location; The actual collection locations of the historically collected data are compared with the preset collection locations to determine missing data collection information.

3. The method according to claim 1, characterized in that The first target acquisition task includes a plurality of sub-acquisition tasks, and the step of performing task configuration based on the first target acquisition task and generating a first task instruction includes: Combining the multiple sub-collection tasks based on configuration parameters to obtain at least one collection task group, wherein the configuration parameters include at least one of a protocol supported by the collection terminal device, a collection data type, a supplementary collection location, and a message length of the collection terminal device; Perform task configuration based on the at least one acquisition task group and generate at least one task instruction.

4. The method according to claim 3, characterized in that The task instruction includes execution sequence information, and the acquisition terminal device determines first target acquisition data based on the first task instruction, including: The acquisition terminal device sequentially executes the target task instructions corresponding to the execution sequence information based on the execution sequence information; The acquisition terminal device determines first target acquisition data based on the target task instruction.

5. The method according to claim 2, characterized in that The acquiring of the historical collected data reported by the collection terminal device includes: Configuring the acquisition parameters based on the acquisition task template to obtain a second target acquisition task, wherein the newly added protocol corresponding to the second target acquisition task will be stored in the database; Performing task configuration based on the second target acquisition task, generating a second task instruction, and sending the second task instruction to the acquisition terminal device so that the acquisition terminal device determines the second target acquisition data based on the second task instruction; The second target collection data reported by the collection terminal device is received and analyzed to obtain the historical collection data.

6. The method according to claim 1, characterized in that The trigger instruction includes any one of a timing trigger instruction and a manual trigger instruction, and the data collection omission information is stored in a cache.

7. The method according to claim 1, characterized in that The determining of the first target acquisition task based on the data acquisition omission information includes: The data collection omission information is configured based on the supplementary collection task template to obtain the first target collection task.

8. The method according to claim 1, characterized in that The method further comprises: After receiving the first target acquisition data reported by the acquisition terminal device, parsing the first target acquisition data to obtain target structured data; The target structured data is stored in a database.

9. A collection task configuration device, characterized in that: The device comprises: a collection omission information determination module, configured to determine data collection omission information based on historical collection data reported by a collection terminal device in response to a trigger instruction; a target acquisition task determination module, configured to determine a first target acquisition task based on the data acquisition omission information; a task instruction generation and delivery module, configured to perform task configuration based on the first target acquisition task, generate a first task instruction, and deliver the first task instruction to the acquisition terminal device, so that the acquisition terminal device determines the first target acquisition data based on the first task instruction; The target acquisition data receiving module is used to receive the first target acquisition data reported by the acquisition terminal device.

10. The device according to claim 9, characterized in that The first target acquisition task includes multiple sub-acquisition tasks, and the task instruction generation and issuance module also includes: combining the multiple sub-acquisition tasks based on configuration parameters to obtain at least one acquisition task group, wherein the configuration parameters include at least one of the protocol supported by the acquisition terminal device, the acquisition data type, the supplementary acquisition location, and the message length of the acquisition terminal device; performing task configuration based on the at least one acquisition task group to generate at least one task instruction.

11. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

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

Images