Equipment task pushing method and device and computer readable storage medium
By obtaining the push conditions, time and file collection in the push task, determining and pushing device tasks, the problem of inefficient push in the existing technology is solved, and the function of pushing multiple files at one time is realized, which improves the push efficiency and accuracy .
Patent Information
- Application Number
- CN202411344042.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-25
- Publication Date
- 2025-02-07
AI Technical Summary
In the prior art, device task push efficiency is low, especially when multiple file types need to be pushed, multiple tasks need to be created, resulting in low push efficiency.
By obtaining the push conditions, push time and push file collection in the push task, determining the push object, and pushing all files in the push file collection to the push object within a specified time, the function of pushing multiple files in the push task is realized.
It improves the efficiency of device task push, reduces the number and time of task creation, and improves the accuracy and timeliness of information transmission.
Smart Images
Figure CN119402547A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the technical field of information push, and in particular, to a method, apparatus, and computer-readable storage medium for device task push. Background Art
[0002] Information push is a process in which the server actively sends predetermined information to users. It is usually done through an automated system that selects target users and pushes corresponding content according to specific conditions and schedules. This process includes task acquisition, parsing, object screening, file packaging, timely connection, and real-time transmission, etc., aiming to ensure that information is delivered to target users in a timely, accurate, and complete manner, thereby improving user experience and the efficiency of information delivery.
[0003] The updates of firmware, applications, parameters, files, and configurations are mainly created through the web background push tasks. The device terminal periodically requests the background to obtain, download, and install the task files. In the prior art, multiple tasks need to be created to push different task files to the same device. For example, when a device is started for the first time, it is necessary to obtain the latest firmware, applications, parameters, configuration information, etc. However, in this case, four different tasks need to be created according to different file types, and the push efficiency is very low. Summary of the invention
[0004] The embodiments of the present application provide a method, an apparatus, and a computer-readable storage medium for pushing device tasks, which can improve push efficiency.
[0005] A first aspect of an embodiment of the present application provides a method for pushing a device task, including:
[0006] Obtain a push task, wherein the push task includes a push condition, a push time, and a push file set;
[0007] Determine a push object according to the push condition;
[0008] Push the push files in the push file set to the push object within the push time.
[0009] Optionally, determining the push object according to the push condition includes:
[0010] Obtaining the screening index in the push condition;
[0011] Devices in the device pool that meet the screening criteria are determined as push objects.
[0012] Optionally, the screening index includes at least one of a device model, a device label, and an associated merchant.
[0013] Optionally, after determining the devices in the device pool that meet the screening criteria as push objects, the method further includes:
[0014] When a new device is added to the device pool, determining whether the new device meets the screening criteria;
[0015] If yes, the new device is added to the push object.
[0016] Optionally, the pushing of the pushed files in the pushed file set to the pushed object within the push time includes:
[0017] Packing the push files in the push file set into a task package;
[0018] The task package is pushed to the push object within the push time.
[0019] Optionally, after pushing the push file in the push file set to the push object within the push time, the method further includes:
[0020] Receiving a periodic push request of the push object;
[0021] The push object is responded to according to the push request.
[0022] Optionally, after pushing the push file in the push file set to the push object within the push time, the method further includes:
[0023] Obtaining change information for the push task;
[0024] At least one of the push condition, the push time, and the push file set is updated according to the change information.
[0025] A second aspect of an embodiment of the present application provides an apparatus for pushing a device task, including:
[0026] An acquisition unit, used to acquire a push task, wherein the push task includes a push condition, a push time, and a push file set;
[0027] A determination unit, configured to determine a push object according to the push condition;
[0028] The pushing unit is used to push the push files in the push file set to the push object within the push time.
[0029] Optionally, the determining unit includes:
[0030] An acquisition module, used to acquire the screening index in the push condition;
[0031] The determination module is used to determine the devices in the device pool that meet the screening index as push objects.
[0032] Optionally, the determining unit further includes:
[0033] A judgment module, used for judging whether a new device meets the screening index after the new device is added to the device pool;
[0034] The adding module is used to add the new device to the push object when the judging module determines that the new device meets the screening index.
[0035] Optionally, the pushing unit is specifically used for:
[0036] Packing the push files in the push file set into a task package;
[0037] The task package is pushed to the push object within the push time.
[0038] Optionally, the device further comprises a heartbeat connection unit, wherein the heartbeat connection unit is used to:
[0039] Receiving a periodic push request of the push object;
[0040] The push object is responded to according to the push request.
[0041] Optionally, the device further includes a changing unit, wherein the changing unit is configured to:
[0042] Obtaining change information for the push task;
[0043] At least one of the push condition, the push time, and the push file set is updated according to the change information.
[0044] A third aspect of an embodiment of the present application provides an apparatus for pushing a device task, including:
[0045] Processor, memory, input-output unit, and bus;
[0046] The processor is connected to the memory, the input and output unit, and the bus;
[0047] A program is stored in the memory, and the processor calls the program to execute the method in the first aspect and any possible implementation manner of the first aspect.
[0048] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, on which a program is stored. When the program is executed on a computer, the computer executes the method in the first aspect and any possible implementation of the first aspect.
[0049] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:
[0050] In the embodiment of the present application, after the push task is acquired, and the push conditions, push time and push file set are obtained, the push object is determined using the push conditions, and the push files in the push file set are pushed to the push object within the push time. The push file set can include one or more push files, so multiple push files can be pushed to the push object at one time in one push task, which improves the push efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] Figure 1 A flowchart of an embodiment of a method for pushing device tasks in an embodiment of the present application;
[0052] Figure 2 A schematic diagram of an embodiment of packaging the push files in the push file set into a task package in an embodiment of the present application;
[0053] Figure 3 A flowchart of an embodiment of determining a push object in an embodiment of the present application;
[0054] Figure 4 A schematic diagram of a process for receiving a periodic push request according to an embodiment of the present application;
[0055] Figure 5 A schematic diagram of an embodiment of receiving a periodic push request in an embodiment of the present application;
[0056] Figure 6 A schematic diagram of a process for obtaining change information in an embodiment of the present application;
[0057] Figure 7 A schematic diagram of an embodiment of a method for pushing device tasks in an embodiment of the present application;
[0058] Figure 8 A schematic diagram of the structure of an embodiment of an apparatus for pushing device tasks in an embodiment of the present application;
[0059] Fig. 9 This is a structural diagram of another embodiment of the apparatus for pushing device tasks in the embodiments of the present application. DETAILED DESCRIPTION
[0060] The embodiments of the present application provide a method, an apparatus, and a computer-readable storage medium for pushing device tasks, which are used to improve push efficiency.
[0061] The method of the present application can be applied to a server, a terminal or other devices with logic processing capabilities, and the present application does not limit this. For the convenience of description, the following description is made by taking the execution subject as a server as an example.
[0062] The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0063] See also Figure 1 , an embodiment of the method for pushing device tasks in the embodiment of the present application includes:
[0064] 101. Get a push task, which includes push conditions, push time, and push file set;
[0065] In actual applications, administrators will set push tasks according to actual needs. Push tasks include push conditions, push time, and push file collection. Among them, the push file collection may include one or more push files. After the administrator sets the push task on the server, the server can obtain the push task. After obtaining the push task, the server parses the content of the push task in detail and extracts the push conditions, push time, and push file collection. The parsing process enables the server to accurately understand and distinguish the specific requirements and execution conditions of the push task, laying the foundation for subsequent precise push, thereby improving the effectiveness of task execution. It should be noted that push files can include firmware, applications, parameters, configuration information, animations and other files or parameters.
[0066] 102. Determine the push object according to the push conditions;
[0067] Based on the push conditions obtained through analysis, the server searches and selects devices that meet the push conditions in the database. These devices are the push targets. Through this precise object identification method, the server can ensure that the information is conveyed to the target device, avoid the spread of invalid information, and improve the hit rate of the push task.
[0068] 103. Push the push file in the push file set to the push object within the push time.
[0069] When the scheduled push time comes, the server automatically establishes a connection with the selected push object and prepares to transmit the push file set. Through timely connection management, the server ensures that the information can be delivered to the recipient at the scheduled time, which is particularly suitable for time-sensitive notifications and improves the accuracy and timeliness of information delivery.
[0070] After successfully establishing a connection with the push target, the server starts to transfer the push files in the push file set to the push target and monitors the transmission status in real time to handle possible abnormal situations. Through this stable and reliable transmission process, the server ensures that the push files can reach the target user intact and safely, effectively reducing the risk of push failure and improving the success rate of push tasks.
[0071] In this embodiment, after acquiring the push task, the server first analyzes the push task to obtain the push condition, push time and push file set, and then determines the push object using the push condition, and pushes the push files in the push file set to the push object within the push time. The push file set can include one or more push files, so multiple push files can be pushed to the push object at one time in one push task, which is conducive to improving the push efficiency.
[0072] For further information, see Figure 2 In some embodiments of the present application, step 103 in the above embodiment may include the following steps 1031 to 1032:
[0073] 1031. Pack the push files in the push file set into a task package;
[0074] The server packages all or part of the push files in the push file set to generate a complete task package. The push files may include firmware, applications, parameters, configuration information, animations and other files or parameters.
[0075] 1032. Push the task package to the push object within the push time.
[0076] After packaging the task package, the server can push the task package to the push object within the push time.
[0077] File packaging is conducive to the orderly transmission and management of data, ensures the consistency and integrity of data, optimizes transmission efficiency, and thus greatly improves the execution effect of push tasks.
[0078] See also Figure 3 In some embodiments of the present application, step 102 in the above embodiment determines the push object according to the push condition, and may include the following steps 201 to 202:
[0079] 201. Get the filtering index in the push condition;
[0080] The push conditions include multiple screening indicators, which may include device models, device tags, associated merchants, etc. Any number of them may be included and at least one of them may be included. In order to use these screening indicators to filter out push objects, the server needs to first obtain the screening indicators in the push conditions.
[0081] 202. Determine the devices in the device pool that meet the screening criteria as push objects.
[0082] After obtaining all the screening indicators, the server can use these screening indicators to screen the devices in the device pool, screen out the devices that meet all the screening indicators at the same time, and use these devices as push objects.
[0083] In this embodiment, by screening the push objects through multiple screening indicators, the push objects can be accurately found, thus reducing the possibility of push errors.
[0084] Furthermore, in some embodiments of the present application, after step 202 in the above embodiment determines the devices in the device pool that meet the screening index as push targets, the following steps 203 to 204 may be further included:
[0085] 203. When a new device is added to the device pool, it is determined whether the new device meets the screening criteria. If so, step 204 is executed;
[0086] In actual applications, new equipment is often installed. When installing new equipment, the server needs to add the information of the new equipment to the equipment pool for management. After adding the information of the new equipment to the equipment pool, the server can determine whether the new equipment meets the above-mentioned screening indicators. If the new equipment meets all the screening indicators, step 205 can be executed. If the new equipment only meets some of the screening indicators or does not meet any of the screening indicators, it can be determined that the new equipment does not need to be pushed for this push task.
[0087] 204. Add the new device to the push object.
[0088] After the server determines that the new device meets all the screening criteria, the new device can also be added to the push object.
[0089] In this embodiment, the new device can be added to the push task in a timely manner, and there is no need to create a new push task for the new device, which can reduce the user's repeated operations and is conducive to improving efficiency and user experience.
[0090] See also Figure 4 as well as Figure 5In some embodiments of the present application, after step 103 in the above embodiment pushes the push file in the push file set to the push object within the push time, the following steps 301 to 302 may be further included:
[0091] 301. Receive a periodic push request of a push object;
[0092] After the server (backend service) connects with the push object and pushes the task package to the push object, the push object will periodically send push requests to the task center of the server. The push requests include information about the push task from the push object, such as configuration information, system parameters, parameters of each application, system version number, version number of each application, etc. The server receives the push request within the preset push time of the push task.
[0093] 302. Respond to the push object according to the push request.
[0094] After the server receives the push request, it can use the information about the push task of the push object included in the push request to make a judgment, and compare the information with the information of each push file in the task package. If the two are consistent, it can be determined that no push is required. At this time, the server can send a notification to prompt that the contents of the push object are already up to date and the push object does not need to be updated; if the two are inconsistent, it can be determined that push is required, and the server can send the task package to the push object.
[0095] In this embodiment, the push object periodically sends a push request so that the connection between the server and the push object is not disconnected, and the server can perform persistent push of the push object.
[0096] See also Figure 6 In some embodiments of the present application, after step 103 in the above embodiment pushes the push file in the push file set to the push object within the push time, the following steps 401 to 402 may be further included:
[0097] 401. Get the change information for the push task;
[0098] In actual applications, there is often a need to change the push task. When this need arises, the administrator can edit the change information for the push task according to the actual situation and pass the change information to the server, and the server can obtain the change information.
[0099] 402. Update at least one of the push condition, the push time, and the push file set according to the change information.
[0100] After the server obtains the change information, it can parse the change information to obtain at least one of the push conditions, push time and push file set, and then use the push condition, the push time and at least one of the push file set to update the push condition, push time and at least one of the push file set in the push task, which can be a specific overwrite update. It should be noted that in actual applications, the change information includes at least one of the push conditions, push time and push file set, but not necessarily all three. After the server parses the change information, it only needs to use the content included in the change information to update the corresponding content in the push task. After the update, the server needs to re-determine the push object, reconnect the updated push object, and re-push the updated push file set to the updated push object according to the updated push time.
[0101] In this embodiment, the user can update the push task according to actual needs without having to create a new push task, which is conducive to improving efficiency and user experience.
[0102] See also Figure 7 , Figure 7 This is a schematic diagram of an embodiment of a method for pushing device tasks in an embodiment of the present application.
[0103] exist Figure 7 In the illustrated embodiment, the business end supports operations such as administrators adding devices and labeling devices, and also supports operations such as merchants adding labels, thereby improving convenience; the monitoring module monitors in real time whether the newly added devices meet the push conditions, and adds the devices that meet the push conditions to the push task. Specifically, the SN code of the device (other identifiers that can represent a unique identity can also be used, which is not limited here) is added to the push task, and the task package is continuously pushed to all push objects (i.e., devices that meet the push conditions).
[0104] See also Figure 8 In one embodiment of the present application, an apparatus for pushing device tasks includes:
[0105] The acquisition unit 501 is used to acquire a push task, which includes a push condition, a push time, and a push file set;
[0106] A determination unit 502, configured to determine a push object according to a push condition;
[0107] The pushing unit 503 is used to push the push files in the push file set to the push object within the push time.
[0108] In this embodiment, after the acquisition unit 501 acquires the push task and thus obtains the push condition, the push time and the push file set, the determination unit 502 determines the push object using the push condition, and the push unit 503 pushes the push files in the push file set to the push object within the push time. The push file set can include one or more push files, so multiple push files can be pushed to the push object at one time in one push task, thereby improving the push efficiency.
[0109] Optionally, the determining unit 502 includes:
[0110] The acquisition module is used to obtain the filtering indicators in the push conditions;
[0111] The determination module is used to determine the devices that meet the screening index in the device pool as push objects.
[0112] Optionally, the determining unit 502 further includes:
[0113] A judgment module, used for judging whether a new device meets the screening index after a new device is added to the device pool;
[0114] The adding module is used to add the new device to the push object when the judging module determines that the new device meets the screening criteria.
[0115] Optionally, the push unit 503 is specifically used for:
[0116] Pack the push files in the push file collection into a task package;
[0117] Push the task package to the push object within the push time.
[0118] Optionally, the device further includes a heartbeat connection unit, and the heartbeat connection unit is used to:
[0119] Receive periodic push requests of push objects;
[0120] Respond to the push request and push the object.
[0121] Optionally, the device further includes a changing unit, and the changing unit is used to:
[0122] Get the change information for the push task;
[0123] At least one of the push condition, the push time, and the push file set is updated according to the change information.
[0124] In this implementation, the functions of each unit and module are the same as those described above. Figures 1 to 7 The steps in the illustrated embodiments correspond to each other and will not be described again here.
[0125] See also Fig. 9Another embodiment of the device task push apparatus in the embodiment of the present application includes:
[0126] Processor 601, memory 602, input and output unit 603 and bus 604;
[0127] The processor 601 is connected to the memory 602, the input and output unit 603 and the bus 604;
[0128] The memory 602 stores a program, and the processor 601 calls the program to execute Figures 1 to 7 Steps in the illustrated embodiment.
[0129] In this embodiment, the function of the processor 601 is the same as that of the aforementioned Figures 1 to 7 The steps in the illustrated embodiments correspond to each other and will not be described again here.
[0130] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0131] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
[0132] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0133] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0134] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.
Claims
1. A method for pushing device tasks, characterized in that: include: Obtain a push task, wherein the push task includes a push condition, a push time, and a push file set; Determine a push object according to the push condition; Push the push files in the push file set to the push object within the push time.
2. The method according to claim 1, characterized in that Determining the push object according to the push condition includes: Obtaining the screening index in the push condition; Devices in the device pool that meet the screening criteria are determined as push objects.
3. The method according to claim 2, characterized in that The screening index includes at least one of a device model, a device label, and an associated merchant.
4. The method according to claim 2, characterized in that: After determining the devices in the device pool that meet the screening criteria as push targets, the method further includes: When a new device is added to the device pool, determining whether the new device meets the screening criteria; If yes, the new device is added to the push object.
5. The method according to claim 1, characterized in that The pushing of the push file in the push file set to the push object within the push time includes: Packing the push files in the push file set into a task package; The task package is pushed to the push object within the push time.
6. The method according to any one of claims 1 to 5, characterized in that After pushing the push file in the push file set to the push object within the push time, the method further includes: Receiving a periodic push request of the push object; The push object is responded to according to the push request.
7. The method according to any one of claims 1 to 5, characterized in that After pushing the push file in the push file set to the push object within the push time, the method further includes: Obtaining change information for the push task; At least one of the push condition, the push time, and the push file set is updated according to the change information.
8. A device for pushing device tasks, characterized in that: include: An acquisition unit, used to acquire a push task, wherein the push task includes a push condition, a push time, and a push file set; A determination unit, configured to determine a push object according to the push condition; The pushing unit is used to push the push files in the push file set to the push object within the push time.
9. A device for pushing device tasks, characterized in that: include: Processor, memory, input-output unit, and bus; The processor is connected to the memory, the input and output unit, and the bus; A program is stored in the memory, and the processor calls the program to execute the method according to any one of claims 1 to 7. 10 . A computer-readable storage medium having a program stored thereon, wherein when the program is executed on a computer, the computer is caused to execute the method according to claim 1 .