CA3134295C - Data queue pushing method and device, computer equipment and storage medium - Google Patents

Data queue pushing method and device, computer equipment and storage medium Download PDF

Info

Publication number
CA3134295C
CA3134295C CA3134295A CA3134295A CA3134295C CA 3134295 C CA3134295 C CA 3134295C CA 3134295 A CA3134295 A CA 3134295A CA 3134295 A CA3134295 A CA 3134295A CA 3134295 C CA3134295 C CA 3134295C
Authority
CA
Canada
Prior art keywords
pushed data
timer
data
pushed
current
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CA3134295A
Other languages
French (fr)
Other versions
CA3134295A1 (en
Inventor
Yang Wang
Gang Wang
Heng Xu
Wei Qian
Fan XIAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
10353744 Canada Ltd
Original Assignee
10353744 Canada Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 10353744 Canada Ltd filed Critical 10353744 Canada Ltd
Publication of CA3134295A1 publication Critical patent/CA3134295A1/en
Application granted granted Critical
Publication of CA3134295C publication Critical patent/CA3134295C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/548Queue

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Electronic Switches (AREA)

Abstract

The present invention discloses to a data queue pushing method, an apparatus, a computer device, and a storage medium. The method comprises: obtaining a to-be-pushed data queue; determining a current to- be-pushed data from the data queue; obtaining a first current pushing status by pushing the data through a regular timer; closing regular timer and starting supplementary timer when the status is abnormal network status, obtaining a second current pushing status by pushing the data through supplementary timer; closing supplementary timer and starting regular timer when the status is normal network status, obtaining a next to-be-pushed data from the data queue and treating the data as the current to- be-pushed data, returning to step of pushing the current to-be-pushed data through regular timer until at least one data completes data pushing. By adopting the present method to ensure data submission efficiency.

Description

DATA QUEUE PUSHING METHOD AND DEVICE, COMPUTER EQUIPMENT AND STORAGE
MEDIUM
Field [0001] The present disclosure relates to the field of computer technology, particularly to a data queue pushing method, an apparatus, a computer device and a storage medium.
Background
[0002] As well known, submission and storage of terminal information rely on network, in the case of excluding program's intervention, the network speed determines the communication quality and speed, therefore, the network speed directly affects the quality and the result of information submission. However, the terminal network status is always changeable and uncontrollable.
Therefore, how to protect data from loss and submit data in time in a weak network or without network in a short time becomes unavoidable.
At present, if under a status with weak network or without network in a short time, generally caching the data in local until the network comes back to normal, and then submitting the data, however, this mentioned method can not ensure the real-time performance of data submission and lead to low data submission efficiency.
Invention Content
[0003] Based on this, it is necessary to provide a data queue pushing method, an apparatus, a computer device and a storage medium to tackle the above-mentioned technical problems, in any network status, flexibly and intervalley enabling two timers, setting to try to connect to the Internet once in a while through the two timers, and if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.

Date Recue/Date Received 2021-10-14
[0004] A data queue pushing method, the method includes:
[0005] Obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data;
[0006] Determining current to-be-pushed data from the to-be-pushed data queue;
[0007] Obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer;
[0008] Closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period;
[0009] Closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0010] In one of the implementations, the data queue pushing method also includes: where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status;
where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed Date Recue/Date Received 2021-10-14 data queue completes data pushing; and where if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
[0011] In one of the implementations, the data queue pushing method also includes: where if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0012] In one of the implementations, obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprising: obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule, processing at least one initial to-be-pushed data according to the preset data processing rule, obtaining correspondingly to-be-pushed data, obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0013] In one of the implementations, determining the current to-be-pushed data according to the to-be-pushed data queue, comprising: obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
[0014] In one of the implementations, closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period, comprising: where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according Date Recue/Date Received 2021-10-14 to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0015] In one of the implementations, closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, comprising:
where if the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0016] In one of the implementations, the data queue pushing method also includes: where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
[0017] A data queue pushing apparatus includes:
[0018] A to-be-pushed data obtaining module for obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data;

Date Recue/Date Received 2021-10-14
[0019] A cm-rent to-be-pushed data determination module for determining the current to-be-pushed data from the to-be-pushed data queue;
[0020] A regular timer processing module for pushing the current to-be-pushed data through the regular timer, obtaining the first current pushing status corresponding to the current to-be-pushed data;
[0021]
A supplementary timer processing module for closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period;
[0022] A regular timer loop processing module for closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0023] A computer device, including a memory, a processor and a computer program stored in the memory and ran on the processor configured to achieve the following steps when the processor executes the computer program:
[0024] Obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data;
[0025] Determining current to-be-pushed data from the to-be-pushed data queue;
[0026] Obtaining first current pushing status corresponding to the current to-be-pushed data by pushing Date Recue/Date Received 2021-10-14 the current to-be-pushed data through a regular timer;
[0027] Closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period;
[0028] Closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0029] A computer readable storage medium stored with a computer program configured to achieve the following steps when the processor executes the computer program:
[0030] Obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data;
[0031] Determining current to-be-pushed data from the to-be-pushed data queue;
[0032] Obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer;
[0033] Closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset Date Recue/Date Received 2021-10-14 period;
[0034] Closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0035] The above-mentioned data queue pushing method, the apparatus, the computer device, and the storage medium, obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data; determining current to-be-pushed data from the to-be-pushed data queue; obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer; closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period; and closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0036] Wherein, the regular timer is always connected to network under a normal network situation and performing data pushing, where if the network status is changed to abnormal, closing the regular timer and starting the supplementary timer, the supplementary timer keeps connecting to network to perform data pushing, flexibly and intervalley enabling two timers, setting to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency. Additionally, intermittent control of the two Date Recue/Date Received 2021-10-14 timers at the same time also avoids the performance loss of multiple timers.
Drawing Description
[0037] Figure 1 is an application environment diagram of a data queue pushing method in an implementation;
[0038] Figure 2 is a process diagram of a data queue pushing method in an implementation;
[0039] Figure 3 is a process diagram of a data queue pushing method in an implementation;
[0040] Figure 4 is a process diagram of a to-be-pushed data queue's obtaining steps in an implementation;
[0041] Figure 5 is a process diagram of a to-be-pushed data queue's determination steps in an implementation;
[0042] Figure 6 is a process diagram of a data queue pushing method in an implementation;
[0043] Figure 7 is a structural diagram of a data queue pushing apparatus in an implementation;
[0044] Figure 8 is an internal structure of a computer device in an implementation.
Specific implementation methods
[0045] In order to make application purposes, technical solutions, and advantages clearer, the present disclosure is further explained in detail with a particular embodiment thereof, and with reference to the drawings. It shall be appreciated that these descriptions are only intended to be illustrative, but not to limit the scope of the disclosure thereto.

Date Recue/Date Received 2021-10-14
[0046] The data queue pushing method provided in the present application can be applied in the application environment as shown in Figure 1. Wherein, terminal 102 communicates with server 104 through the network. And terminal 102 can be used but not limited to a variety of personal computers, laptop computers, smart phones, tablets, portable and wearable devices, the server 104 can be achieved by an independent server or a server cluster composed of multiple servers.
[0047] Specifically, the terminal 102 obtaining the to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, determining current to-be-pushed data from the to-be-pushed data queue, obtaining the returned first current pushing status corresponding to the current to-be-pushed data from server 104 by pushing the current to-be-pushed data to server 104 through regular timer. Wherein, closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining the returned second current pushing status corresponding to the current to-be-pushed data from the server 104 by pushing the current to-be-pushed data to the server 104 through the supplementary timer within a preset period. Wherein, closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0048] In an implementation, as shown in Figure 2, a data queue pushing method is provided and applied in the terminal of Figure 1, which includes following steps:
[0049] Step 202, obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data.
[0050] Wherein, to-be-pushed data is the data waiting for pushing in a terminal, and to-be-pushed data Date Recue/Date Received 2021-10-14 queue is data function used for achieving first in first out queuing function, the to-be-pushed data queue includes at least one to-be-pushed data, and for each to-be-pushed data, whether sorting the data by time stack, whether sorting the data by the other preset rules, or whether sorting the data by first in first out rule, which can be determined according to business requirements, application scenarios or product requirements.
[0051] In another implementation, the correspondingly data structure of to-be-pushed data in the to-be-pushed data queue remains consistent. Therefore, after obtaining the initial to-be-pushed data corresponding to each to-be-pushed data, the data structure corresponding to each initial to-be-pushed data can be different, in order to maintain the same data format of the to-be-pushed data queue, obtaining preset data processing rules and each initial to-be-pushed data is processed according to the preset data processing rules, after obtaining the processed to-be-pushed data, composing the to-be-pushed data queue with the processed to-be-pushed data. For example, the preset data processing rules can be used to perform processing on initial to-be-pushed data's operation types, variables, or incremental information.
Wherein, the preset data processing rules can be obtained according to the business requirements, product requirements or actual application scenarios.
[0052] Step 204, determining the current to-be-pushed data according to the to-be-pushed data queue.
[0053] Wherein, the current to-be-pushed data refers to the data currently in processing, the current to-be-pushed data is determined and obtained from the to-be-pushed data queue, wherein, the determination way can be customized, the customized way can be randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue, the customized way can also be obtaining the to-be-pushed data's priority corresponding to each to-be-pushed data from the to-be-pushed data queue, and determining the current to-be-pushed data according to the to-be-pushed data's priority from the to-be-pushed data queue, for example, determining the to-be-pushed data with higher priority as the current to-be-pushed data. In another implementation, the current to-be-pushed data's customized determination way Date Recue/Date Received 2021-10-14 can also be sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order, for example, determining the first out to-be-pushed data in the to-be-pushed data queue as the current to-be-pushed data.
[0054] Step 206, obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer.
[0055] Wherein, the timer here is an apparatus for time control, and by setting the time, the timer can start to work after reaching the set time. The regular timer refers to the timer that is often used, the time setting in the regular timer is very short, which means the regular timer works more frequently, and the regular time will work normally under the normal network status, but once the network is abnormal, the regular timer will stop working. Wherein, a regular timer is preset inside the terminal which can be used for pushing the current to-be-pushed data, pushing the current to-be-pushed data by the regular timer can specifically be obtaining the preset period by the regular timer, pushing the current to-be-pushed data by the regular timer when reaching the preset period. The preset period can be determined and obtained according to the business requirements, product requirements or actual application scenarios.
[0056] When the regular timer pushes the current to-be-pushed data to a server, where if the network is a under normal status, the regular timer will successfully push the current to-be-pushed data to the server, the server will return the regular timer's correspondingly first current pushing status after receives the current to-be-pushed data from the regular timer, and this time, the first current pushing status is normal network status. In another implementation, where if the network is abnormal, then the regular time will stop working, which means the regular timer fails to push the current to-be-pushed data to the server, then obtaining the current to-be-pushed data's response time corresponding to the current to-be-pushed data, when reaching the current to-be-pushed data's response time, if still having not received any pushing status returned from the server, then determining the first current pushing status corresponding to the current to-be-pushed data as abnormal network status.

Date Recue/Date Received 2021-10-14
[0057] Step 208, closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period.
[0058] Wherein, if the first current pushing status is abnormal network status after obtaining the first current pushing status corresponding to the current to-be-pushed data, which means the current to-be-pushed data's network is abnormal status and can not complete the pushing work of the current to-be-pushed data. Moreover, the current to-be-pushed data's network is under abnormal status, then the regular timer stops working, and in order to avoid the pushing delayed of the current to-be-pushed data and ensure the pushing efficiency of the current to-be-pushed data, at this time, closing the regular timer and starting the supplementary timer, pushing the current to-be-pushed data through the supplementary timer within a preset period.
[0059] Wherein, the supplementary timer is also an apparatus for time control, unlike regular timer, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer will not get started, which means the supplementary timer here is specifically starting to work and obtaining preset period under abnormal network status, when reaching the preset period, the supplementary timer pushes the current to-be-pushed data. The preset period here can be determined and obtained according to business requirements, product requirements and actual application scenarios, the preset period corresponding to the supplementary timer can be greater than the preset period corresponding to the regular timer, which means supplementary does not need to push the to-be-pushed data frequently, the pushing frequency of the supplementary timer can be smaller than frequency of the regular timer.
[0060] Similarly, when the supplementary timer pushes the current to-be-pushed data to the server, where Date Recue/Date Received 2021-10-14 if the network is under normal status, the supplementary timer will successfully push the current to-be-pushed data to the server, the server will return the supplementary timer's correspondingly second current pushing status after receives the current to-be-pushed data from the supplementary timer, and this time, the second current pushing status is normal network status.
[0061] In another implementation, if the network is under abnormal status, keeping running the supplementary timer, which means the supplementary timer continues to work, the supplementary timer re-obtains the next preset period, and when reaching the next preset period, re-pushing the current to-be-pushed data until the supplementary timer pushes the current to-be-pushed data successfully.
[0062] Step 210, closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0063] Wherein, after obtaining the second current pushing status corresponding to the current to-be-pushed data, where if the second current pushing status is normal network status, which means the current to-be-pushed data's pushing network is already back to normal status, and the regular timer can start to complete the pushing work of the other to-be-pushed data in the to-be-pushed data queue. Specifically, when the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.

Date Recue/Date Received 2021-10-14
[0064] In the above-mentioned data queue pushing method, obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data; determining current to-be-pushed data from the to-be-pushed data queue; obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer;
closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period; and closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0065] Wherein, the regular timer is always connected to network under a normal network situation and performing data pushing, where if the network status is changed to abnormal, closing the regular timer and starting the supplementary timer, the supplementary timer keeps connecting to network to perform data pushing, flexibly and intervalley enabling two timers, setting to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency. Additionally, intermittent control of the two timers at the same time also avoids the performance loss of multiple timers.
[0066] In an implementation, as shown in Figure 3, the data queue pushing method also includes:
[0067] Step 302, where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status;

Date Recue/Date Received 2021-10-14
[0068] Step 304, where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing;
[0069] Step 306, where if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
[0070] Wherein, if the first current pushing status is not abnormal network status, the first current pushing status can be first current pushing succeed status, or the other reasons unrelated to network which lead the regular timer cannot be able to work normally to push the current to-be-pushed data and lead the failure of pushing current to-be-pushed data. Therefore, if the first current pushing status is not abnormal network status, judging whether the current to-be-pushed data is successfully pushed, specifically, determining if the current to-be-pushed data is successfully pushed according to the first current pushing status, for example, receiving the response returned from the server, which means the current to-be-pushed data is successfully pushed, otherwise, if there is no response received from the server, which means the current to-be-pushed data is failure pushed.
[0071] Furthermore, when determining the current to-be-pushed data is successfully pushed, which means the cm-rent network status is normal and also there is no other reason unrelated to network, the regular timer can continue to push the to-be-pushed data, specifically, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0072] In another implementation, where if the current to-be-pushed data is unsuccessfully pushed, which Date Recue/Date Received 2021-10-14 means the cm-rent to-be-pushed data at this time is failure pushed, but the failure reason is not the abnormal network status and is the other abnormal reason unrelated to network, and for this abnormal reason unrelated to network which leads to the failure pushing of the current to-be-pushed data, the regular timer needs to keep running, obtaining the next preset period set by the regular timer, when reaching the preset period, the current to-be-pushed data will be pushed again by the regular timer until the current to-be-pushed data is successfully pushed.
[0073] In an implementation, where if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0074] Wherein, after obtaining the second current pushing status corresponding to the current to-be-pushed data, where if the second current pushing status is abnormal network status, which means the current to-be-pushed data's pushing network is not back to normal status, and the supplementary timer continues to work, which means keeping running the he supplementary timer, then obtaining the next preset period set by the supplementary timer, re-pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
Furthermore, if the current to-be-pushed data is successfully pushed, which means the network is back to normal, therefore, starting the regular timer to complete the other to-be-pushed data's pushing in the to-be-pushed data queue.
[0075] In an implementation, as shown in Figure 4, obtaining the to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprising:
[0076] Step 402, obtaining at least one initial to-be-pushed data.
[0077] Step 404, obtaining preset data processing rule, processing at least one initial to-be-pushed data Date Recue/Date Received 2021-10-14 according to the preset data processing rule, obtaining correspondingly to-be-pushed data.
[0078] Step 406, composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0079] Wherein, the initial to-be-pushed data refers to the data before the to-be-pushed data, the data structure and the data format of each initial to-be-pushed data can be different, in order to maintain the same data format in the to-be-pushed data queue, obtaining the preset data processing rule, and processing each initial to-be-pushed data according to the preset data processing rule, then obtaining the processed to-be-pushed data, composing the to-be-pushed data queue according to each to-be-pushed data.
[0080] For example, the preset data processing rule can be used to perform processing on initial to-be-pushed data's operation type, variable, or incremental information. Wherein, the preset data processing rule can be determined and obtained according to the business requirements, product requirements or actual application scenarios.
[0081] Wherein, composing the to-be-pushed data queue according to at least one to-be-pushed data, for each to-be-pushed data, whether sorting the data by time stack, whether sorting the data by the other preset rules, or whether sorting the data by first in first out rule, which can be determined according to business requirements, application scenarios or product requirements.
[0082] In an implementation, as shown in Figure 5, obtaining the current to-be-pushed data according to the to-be-pushed data queue, comprising:
[0083] Step 502, obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue;
[0084] Step 504, determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.

Date Recue/Date Received 2021-10-14
[0085] Wherein, the current to-be-pushed data refers to the data currently in processing, the current to-be-pushed data is determined and obtained from the to-be-pushed data queue, wherein, the determination way can be customized, the customized way can be randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue, the customized way can also be obtaining the to-be-pushed data's priority corresponding to each to-be-pushed data from the to-be-pushed data queue, and determining the current to-be-pushed data according to the to-be-pushed data's priority from the to-be-pushed data queue, for example, determining the to-be-pushed data with higher priority as the current to-be-pushed data.
[0086] Wherein, the to-be-pushed data's priority corresponding to each to-be-pushed data can be obtained in advance by determining the business requirements, product requirements or actual application scenarios, the to-be-pushed data with higher priority can rank before the to-be-pushed data with lower priority, the to-be-pushed data with higher priority can be pushed first, therefore, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
[0087] Furthermore, determining the current to-be-pushed data according to the to-be-pushed data's priority from the to-be-pushed data queue, which can determine the to-be-pushed data with higher priority as current to-be-pushed data, after the current to-be-pushed data completes data pushing, determining the to-be-pushed data with second higher priority as the current to-be-pushed data.
[0088] In an implementation, closing a regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period, comprising: where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the Date Recue/Date Received 2021-10-14 supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0089] Wherein, if the first current pushing status is abnormal network status after obtaining the first current pushing status corresponding to the current to-be-pushed data, which means the current to-be-pushed data's network is abnormal status and cannot complete the pushing work of the current to-be-pushed data. Moreover, the current to-be-pushed data's network is under abnormal status, then the regular timer stops working, and in order to avoid the pushing delayed of the current to-be-pushed data and ensure the pushing efficiency of the current to-be-pushed data, at this time, closing the regular timer and starting the supplementary timer, pushing the current to-be-pushed data through the supplementary timer within a preset period. Specifically, where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, meanwhile sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0090] Wherein, the supplementary timer here is also an apparatus for time control, unlike regular timer, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer will not get started, which means the supplementary timer here is specifically starting to work and obtaining preset period under abnormal network status, when reaching the preset period, the supplementary timer pushes the current to-be-pushed data. The preset period here can be determined and obtained according to business requirements, product requirements and actual application scenarios, the preset period corresponding to the supplementary timer can be greater than the preset period corresponding to the regular timer, which means supplementary does not need to push the to-be-pushed data frequently, the pushing frequency of the supplementary timer can Date Recue/Date Received 2021-10-14 be smaller than frequency of the regular timer.
[0091] Similarly, when the supplementary timer pushes the current to-be-pushed data to the server, where if the network is under normal status, the supplementary timer will successfully push the current to-be-pushed data to the server, the server will return the supplementary timer's correspondingly second current pushing status after receives the current to-be-pushed data from the supplementary timer, and this time, the second current pushing status is normal network status.
[0092] In another implementation, if the network is under abnormal status, keeping running the supplementary timer, which means the supplementary timer continues to work, the supplementary timer re-obtains the next preset period, and when reaching the next preset period, re-pushing the current to-be-pushed data until the supplementary timer pushes the current to-be-pushed data successfully.
[0093] In an implementation, closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, comprising:
where if the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0094] Wherein, after obtaining the second current pushing status corresponding to the current to-be-Date Recue/Date Received 2021-10-14 pushed data, where if the second current pushing status is normal network status, which means the current to-be-pushed data's pushing network is already back to normal status, and the regular timer can start to complete the pushing work of the other to-be-pushed data in the to-be-pushed data queue. Specifically, when the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0095] In an implementation, as shown in Figure 6, the data queue pushing method also includes:
[0096] Step 602, where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, obtaining timer clear up command.
[0097] Step 604, clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
[0098] Wherein, the timer clear up command here is used to clear up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, specifically, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, where if there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command, in case of leaving any trace when running the regular timer and the supplementary timer next time, therefore, when completing the data pushing, clearing up the regular Date Recue/Date Received 2021-10-14 timer and the supplementary timer, then obtaining a cleared regular timer and a cleared supplementary timer. Wherein, the cleared regular timer and supplementary timer can be used for processing next to-be-pushed data queue and clearing up the regular timer and the supplementary timer every time after completing the pushing work of a data queue which can ensure the data security.
[0099] In a specific implementation, a data queue pushing method is provided, specially includes following steps:
[0100] 1, obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data.
[0101] 1-1, obtaining at least one initial to-be-pushed data.
[0102]
1-2, obtaining preset data processing rule, processing at least one initial to-be-pushed data according to the preset data processing rule, obtaining correspondingly to-be-pushed data.
[0103] 1-3, composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0104] 2, obtaining the current to-be-pushed data from the to-be-pushed data queue.
[0105] 2-1, obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue.
[0106] 2-2, determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
[0107] 3, obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer.

Date Recue/Date Received 2021-10-14
[0108] 4, closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period.
[0109] 4-1, where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0110] 5, closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0111] 5-1, where if the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.

Date Recue/Date Received 2021-10-14
[0112] 6, where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status.
[0113] 7, where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0114] 8, where if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
[0115] 9, where if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0116] 10, where if at least one of the to-be-pushed data in the to-be-pushed data queue completes data pushing, obtaining timer clear up command.
[0117] 11, clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
[0118] Although the above-mentioned steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly instruction in this article, there is no strict order in which these steps can be performed, and Date Recue/Date Received 2021-10-14 they can be performed in any other orders. In addition, at least parts of the appended drawings in the steps can include more sub steps or multiple stages, these sub steps or stages are not necessarily completed at the same time but can be executed in different time, the execution order of these sub steps or stages is also not necessarily in sequence order but can be performed alternately with the other steps or sub steps of other steps or at least one part of the other stages.
[0119] In an implementation, as shown in Figure 7, a data queue pushing apparatus 700 is provided, including: to-be-pushed data obtaining module 702, current to-be-pushed data determination module 704, regular timer processing module 706, supplementary timer processing module 708 and regular timer loop processing module 710, wherein:
[0120] A to-be-pushed data obtaining module 702 for obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data.
[0121] A cm-rent to-be-pushed data determination module 704 for determining the current to-be-pushed data from the to-be-pushed data queue.
[0122] A regular timer processing module 706 for pushing the current to-be-pushed data through the regular timer, obtaining the first current pushing status corresponding to the current to-be-pushed data.
[0123] A supplementary timer processing module 708 for closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period.
[0124] A regular timer loop processing module 710 for closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed Date Recue/Date Received 2021-10-14 data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0125] In an implementation, the data queue pushing apparatus 700 is also used when the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status; if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing; if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
[0126] In an implementation, the data queue pushing apparatus 700 is also used when the second current pushing status is abnormal network status, if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0127] In an implementation, the to-be-pushed data obtaining module 702 is also used when obtaining at least one initial to-be-pushed data, obtaining preset data processing rule, processing at least one initial to-be-pushed data according to the preset data processing rule, obtaining correspondingly to-be-pushed data;
composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0128] In an implementation, the current to-be-pushed data determination module 704 is also used when obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; determining the Date Recue/Date Received 2021-10-14 current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
[0129] In an implementation, the supplementary timer processing module 708 is also used when the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0130] In an implementation, the regular timer processing module 710 is also used when the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0131] In an implementation, the data queue pushing apparatus 700 is also used when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, obtaining timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue. For the specific limitation of the data queue pushing apparatus can refer to the above-mentioned the data queue pushing method, which will not be repeated here.
Each module of the above-mentioned data queue pushing apparatus can be achieved fully or partly by Date Recue/Date Received 2021-10-14 software, hardware, and their combinations. The above modules can be embedded in the processor or independent of the processor in computer device and can store in the memory of computer device in form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0132] In an implementation, a computer device is provided to be a server and whose internal structure diagram is shown in Figure 8. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. The processor of the computer device is configured to provide calculation and control capabilities. The memory of computer device includes non-volatile storage medium and internal memory. The memory of non-volatile storage medium has operation system, computer programs and database. The internal memory provides an environment for the operation system and computer program running in a non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection.
The computer program is executed by the processor to implement a data queue pushing method. The computer device's display monitor can be LCD monitor or electronic ink display monitor, the input apparatus of the computer device can be the touch layer on the display monitor, also can be button, trackball, or touchpad, and can be the external keyboard, touchpad, or mouse.
[0133] The skilled in the art can understand that the structure shown in Figure 8 is only partial structural diagram related this application solution and not constitute limitation to the computer device applied on the current application solution, the specific computer device can include more or less components than what is shown in the figure, or combinations of some components or different components to what is shown in the figure.
[0134] In an implementation, a computer device is provided which includes a memory, a processor, and a computer program stored on the memory and running on the processor. The processor performs the following steps when executing the computer program: obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data; determining current to-be-pushed data from the Date Recue/Date Received 2021-10-14 to-be-pushed data queue; obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer; closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period; and closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0135] In an implementation, the processor performs the following steps when executing the computer program: where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status; if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing; and if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
[0136] In an implementation, the processor performs the following steps when executing the computer program: where if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0137] In an implementation, the processor performs the following steps when executing the computer Date Recue/Date Received 2021-10-14 program: obtaining at least one initial to-be-pushed data; obtaining preset data processing rule, processing at least one initial to-be-pushed data according to the preset data processing rule, obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0138] In an implementation, the processor performs the following steps when executing the computer program: obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
[0139] In an implementation, the processor performs the following steps when executing the computer program: where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0140] In an implementation, the processor performs the following steps when executing the computer program: where if the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0141] In an implementation, the processor performs the following steps when executing the computer Date Recue/Date Received 2021-10-14 program: where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, obtaining timer clear up command; clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
[0142] In an implementation, a computer readable storage medium is provided, wherein the medium stored with a computer program, the following steps are performed when executing the computer program:
obtaining a to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data;
determining current to-be-pushed data from the to-be-pushed data queue;
obtaining first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer; closing the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period; and closing the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0143] In an implementation, the processor performs the following steps when executing the computer program: where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status; if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing; and if the current to-be-pushed data is unsuccessfully pushed, restarting the step of pushing the current to-be-pushed data through the regular timer Date Recue/Date Received 2021-10-14 until the current to-be-pushed data is successfully pushed.
[0144] In an implementation, the processor performs the following steps when executing the computer program: where if the second current pushing status is abnormal network status, keeping running the supplementary timer, restarting to obtain the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed.
[0145] In an implementation, the processor performs the following steps when executing the computer program: obtaining at least one initial to-be-pushed data; obtaining preset data processing rule, processing at least one initial to-be-pushed data according to the preset data processing rule, obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
[0146] In an implementation, the processor performs the following steps when executing the computer program: obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
[0147] In an implementation, the processor performs the following steps when executing the computer program: where if the first current pushing status is abnormal network status, sending a regular timer's closing command to the regular timer, the regular timer stops working according to the regular timer's closing command, sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command, pushing the current to-be-pushed data and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
[0148] In an implementation, the processor performs the following steps when executing the computer Date Recue/Date Received 2021-10-14 program: where if the second current pushing status is normal network status, sending a supplementary timer's closing command to the supplementary timer, the supplementary timer stops working according to the supplementary timer's closing command, sending a regular timer's starting command to the regular timer, to make the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command, treating the next to-be-pushed data as the current to-be-pushed data, returning to the step of pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
[0149] In an implementation, the processor performs the following steps when executing the computer program: where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, obtaining timer clear up command; clearing up the regular timer and the supplementary timer according to the timer clear up command, obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
[0150] The skilled in the art can understand that all or partial of procedures from the above-mentioned methods can be performed by computer program instructions through related hardware, the mentioned computer program can be stored in a non-volatile material computer readable storage medium, this computer can include various implementation procedures from the abovementioned methods when execution. Any reference to the memory, the storage, the database, or the other media used in each implementation provided in current application can include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programable RON (PROM), electrically programmable ROM (EPRPMD), electrically erasable programmable ROM(EEPROM) or flash memory.
Volatile memory can include random access memory (RAM) or external cache memory. As an instruction but not limited to, RAM is available in many forms such as static RAM (SRAM), dynamic RAM
(DRAMD), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SRAM
(ESDRAM), synchronal link (Synchlink) DRAM (SLDRAM), memory bus (Rambus), direct RAM
(RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM
(RDRAM), Date Recue/Date Received 2021-10-14 etc.
[0151] The technical features of the above-mentioned implementations can be randomly combined, for concisely statement, not all possible combinations of technical features in the abovementioned implementations are described. However, if there are no conflicts in the combinations of these technical features, it shall be within the scope of this descriptions.
[0152] The above-mentioned implementations are only several implementations in this disclosure and the description is more specific and detailed but cannot be understood as the limitation of the scope of the invention patent. Evidently those ordinary skilled in the art can make various modifications and variations to the disclosure without departing from the spirit and scope of the disclosure. Therefore, the appended claims are intended to be construed as encompassing the described embodiment and all the modifications and variations coming into the scope of the disclosure.

Date Recue/Date Received 2021-10-14

Claims (274)

Claims:
1. An apparatus comprises:
a to-be-pushed data obtaining module configured to obtain a to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
a current to-be-pushed data determination module configured to determine a current to-be-pushed data from the to-be-pushed data queue;
a regular timer processing module configured to:
push the current to-be-pushed data through a regular timer to a server;
obtain a first current pushing status corresponding to the current to-be-pushed data;
a supplementary timer processing module configured to:
stop the regular timer and start a supplementary timer when the first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtain a second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;
wherein if the second current pushing status is abnormal network status, keep ninning the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
Date Recue/Date Received 2023-09-15 a regular timer loop processing module configured to:
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status;
obtain next to-be-pushed data from the to-be-pushed data queue;
treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
2. The apparatus of claim 1, further comprises:
if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and if the current to-be-pushed data is unsuccessfully pushed, pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
3. The apparatus of claim 1, wherein the to-be-pushed data obtaining module further configured to:
obtain at least one initial to-be-pushed data obtain preset data processing rule;

Date Recue/Date Received 2023-09-15 processing at least one initial to-be-pushed data according to the preset data processing rule;
obtain correspondingly to-be-pushed data; and compose the to-be-pushed data queue according to at least one to-be-pushed data.
4. The apparatus of claim 1, wherein the current to-be-pushed data determination module is configured to:
obtain at least one to-be-pushed data's priority from the to-be-pushed data queue; and determine the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
5. The apparatus of claim 1, wherein the supplementary timer processing module is further configured to:
when the first current pushing status is abnormal network status includes:
sending a regular timer's stopping command to the regular timer, wherein the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
6. The apparatus of claim 1, wherein the regular timer processing module is further configured to:

Date Recue/Date Received 2023-09-15 when the second current pushing status is nomal network status includes:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtains the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and retuniing to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
7. The apparatus of claim 1, wherein the data queue pushing apparatus is further configured to:
when all the to-be-pushed data in the to-be-pushed data queue complete data pushing includes:
obtahung timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command;
obtaining a cleared regular timer and a cleared supplementary timer, wherein the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
8. The apparatus of any one of claims 1 to 7, wherein each module is achieved fully or partly by software, hardware, and their combinations.

Date Recue/Date Received 2023-09-15
9. The apparatus of any one of claims 1 to 8, wherein the modules are embedded in the processor or independent of the processor in computer device and are stored in the memory of computer device in foiin of software.
10. The apparatus of any one of claims 1 to 9, communicates with the server through the network.
11. The apparatus of any one of claims 1 to 10, includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
12. The apparatus of any one of claims 1 to 11, wherein the server includes an independent server or a server cluster composed of multiple servers.
13. The apparatus of any one of claims 1 to 12, wherein the to-be-pushed data is data waiting for pushing.
14. The apparatus of any one of claims 1 to 13, wherein the to-be-pushed data queue is data function used for achieving first in, first out queuing function.
15. The apparatus of any one of claims 1 to 14, wherein for each to-be-pushed data includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
16. The apparatus of any one of claims 1 to 15, wherein the data structure corresponding to each initial to-be-pushed data is different.
17. The apparatus of any one of claims 1 to 16, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
18. The apparatus of any one of claims 1 to 17, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.

Date Recue/Date Received 2023-09-15
19. The apparatus of any one of claims 1 to 18, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
20. The apparatus of any one of claims 1 to 19, wherein the current to-be-pushed data refers to the data currently in processing.
21. The apparatus of any one of claims 1 to 20, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
22. The apparatus of any one of claims 1 to 21, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in, first out queuing function, then determining the current to-be-pushed data by the first in, first out order.
23. The apparatus of any one of claims 1 to 22, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
24. The apparatus of any one of claims 1 to 23, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
25. The apparatus of any one of claims 1 to 24, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
26. The apparatus of any one of claims 1 to 25, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
27. The apparatus of any one of claims 1 to 26, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
Date Recue/Date Received 2023-09-15
28. The apparatus of any one of claims 1 to 27, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein the supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
29. The apparatus of any one of claims 1 to 28, wherein the regular timer is always connected to network under the noimal network status and performing data pushing.
30. The apparatus of any one of claims 1 to 29, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
31. The apparatus of any one of claims 1 to 30, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
32. The apparatus of any one of claims 1 to 31, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
33. The apparatus of any one of claims 1 to 32, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
34. The apparatus of any one of claims 1 to 33, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.

Date Recue/Date Received 2023-09-15
35. The apparatus of any one of claims 1 to 34, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
36. A device comprising:
a memory includes non-volatile storage medium and internal memory wherein the memory of non-volatile storage medium has an operation system, computer programs and a database wherein the internal memory provides an environment for the operation system and computer program running in a non-volatile storage medium;
a processor configured to provide calculation and control capabilities;
a network interface to communicate with an external terminal through a network connection;
the database connected through a system bus; and program instructions stored in the memory and executed by the processor configured to:
obtain a to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determine current to-be-pushed data from the to-be-pushed data queue;
obtain first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer to a server;
stop the regular timer and start a supplementary timer when the first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;

Date Recue/Date Received 2023-09-15 obtain a second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;
wherein if the second current pushing status is abnormal network status, keep running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status;
obtain next to-be-pushed data from the to-be-pushed data queue;
treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
37. The device of claim 36, further comprises:
where if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
where if the current to-be-pushed data is successfully pushed obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and Date Recue/Date Received 2023-09-15 where if the current to-be-pushed data is unsuccessfully pushed, pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
38. The device of claim 36, wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
39. The device of claim 36, wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
40. The device of claim 36, wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is the abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period, where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;

Date Recue/Date Received 2023-09-15 sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
41. The device of claim 36, wherein stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, where if the second current pushing status is noimal network status comprises:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtains the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data throue) the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
42. The device of claim 36, wherein if all the to-be-pushed data in the to-be-pushed data queue complete data pushing comprises:
Date Recue/Date Received 2023-09-15 obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
43. The device of any one of claims 36 to 42, communicates with the server through the network.
44. The device of any one of claims 36 to 43, includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
45. The device of any one of claims 36 to 44, wherein the server includes an independent server or a server cluster composed of multiple servers.
46. The device of any one of claims 36 to 45, wherein to-be-pushed data is data waiting for pushing in a terminal.
47. The device of any one of claims 36 to 46, wherein the to-be-pushed data queue is data function used for achieving first in, first out queuing function.
48. The device of any one of claims 36 to 47, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
49. The device of any one of claims 36 to 48, wherein the data structure corresponding to each initial to-be-pushed data is different.
50. The device of any one of claims 36 to 49, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.

Date Recue/Date Received 2023-09-15
51. The device of any one of claims 36 to 50, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
52. The device of any one of claims 36 to 51, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
53. The device of any one of claims 36 to 52, wherein the current to-be-pushed data refers to the data currently in processing.
54. The device of any one of claims 36 to 53, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
55. The device of any one of claims 36 to 54, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
56. The device of any one of claims 36 to 55, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
57. The device of any one of claims 36 to 56, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
58. The device of any one of claims 36 to 57, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
59. The device of any one of claims 36 to 58, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.

Date Recue/Date Received 2023-09-15
60. The device of any one of claims 36 to 59, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
61. The device of any one of claims 36 to 60, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein the supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
62. The device of any one of claims 36 to 61, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
63. The device of any one of claims 36 to 62, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
64. The device of any one of claims 36 to 63, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
65. The device of any one of claims 36 to 64, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
66. The device of any one of claims 36 to 65, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.

Date Recue/Date Received 2023-09-15
67. The device of any one of claims 36 to 66, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
68. The device of any one of claims 36 to 67, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
69. A method comprising:
obtaining a to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determining a current to-be-pushed data from the to-be-pushed data queue;
obtaining first current pushing status conesponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer to a server;
stopping the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtaining a second cunent pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to a server;
wherein if the second current pushing status is abnormal network status, keeping running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;

Date Recue/Date Received 2023-09-15 stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status;
obtaining next to-be-pushed data from the to-be-pushed data queue;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
70. The method of claim 69, further comprises:
where if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
where if the current to-be-pushed data is successfully pushed obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and where if the current to-be-pushed data is unsuccessfully pushed, restarting pushing the current to-be-pushed data through the regular timer until the cunent to-be-pushed data is successfully pushed.
71. The method of claim 69 wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
Date Recue/Date Received 2023-09-15 obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
72. The method of claim 69 wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
73. The method of claim 69 wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is the abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.

Date Recue/Date Received 2023-09-15
74. The method of claim 69 wherein, stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing where if the second current pushing status is normal network status comprises:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
75. The method of claim 69, where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing comprises obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.

Date Recue/Date Received 2023-09-15
76. The method of any one of claims 69 to 75, wherein a terminal communicates with the server through the network.
77. The method of any one of claims 69 to 76, wherein the terminal includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
78. The method of any one of claims 69 to 77, wherein the server includes an independent server or a server cluster composed of multiple servers.
79. The method of any one of claims 69 to 78, wherein to-be-pushed data is data waiting for pushing in the terminal.
80. The method of any one of claims 69 to 79, wherein the to-be-pushed data queue is data function used for achieving first in, first out queuing function.
81. The method of any one of claims 69 to 80, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
82. The method of any one of claims 69 to 81, wherein the data structure corresponding to each initial to-be-pushed data is different.
83. The method of any one of claims 69 to 82, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
84. The method of any one of claims 69 to 83, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
85. The method of any one of claims 69 to 84, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.

Date Recue/Date Received 2023-09-15
86. The method of any one of claims 69 to 85, wherein the current to-be-pushed data refers to the data currently in processing.
87. The method of any one of claims 69 to 86, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
88. The method of any one of claims 69 to 87, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
89. The method of any one of claims 69 to 88, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
90. The method of any one of claims 69 to 89, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
91. The method of any one of claims 69 to 90, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
92. The method of any one of claims 69 to 91, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
93. The method of any one of claims 69 to 92, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.

Date Recue/Date Received 2023-09-15
94. The method of any one of claims 69 to 93, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
95. The method of any one of claims 69 to 94, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
96. The method of any one of claims 69 to 95, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
97. The method of any one of claims 69 to 96, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
98. The method of any one of claims 69 to 97, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
99. The method of any one of claims 69 to 98, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
100. The method of any one of claims 69 to 99, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
Date Recue/Date Received 2023-09-15
101. The method of any one of claims 69 to 100, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
102.A computer readable medium having stored thereon program instructions executed by a processor configured to:
obtain a to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determine current to-be-pushed data from the to-be-pushed data queue;
obtain first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer to a server;
stop the regular timer and starting a supplementary timer when the first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtain second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;
wherein if the second current pushing status is abnormal network status, keep running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status;

Date Recue/Date Received 2023-09-15 obtain next to-be-pushed data from the to-be-pushed data queue;
treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
103. The readable medium of claim 102, further comprises:
where if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and where if the current to-be-pushed data is unsuccessfully pushed, pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
104. The readable medium of claim 102, wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
obtaining correspondingly to-be-pushed data; and Date Recue/Date Received 2023-09-15 composing the to-be-pushed data queue according to at least one to-be-pushed data.
105. The readable medium of claim 102, wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
106. The readable medium of claim 102, wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is the abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period, where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.

Date Recue/Date Received 2023-09-15
107. The readable medium of claim 102, wherein stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, where if the second current pushing status is normal network status comprises:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtains the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
108. The readable medium of claim 102, wherein if all the to-be-pushed data in the to-be-pushed data queue complete data pushing comprises:
obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.

Date Recue/Date Received 2023-09-15
109. The readable medium of any one of claims 102 to 108, wherein a terminal communicates with the server through the network.
110. The readable medium of any one of claims 102 to 109, wherein the terminal includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
111. The readable medium of any one of claims 102 to 110, wherein the server includes an independent server or a server cluster composed of multiple servers.
112. The readable medium of any one of claims 102 to 111, wherein to-be-pushed data is data waiting for pushing in the terminal.
113. The readable medium of any one of claims 102 to 112, wherein the to-be-pushed data queue is data function used for achieving first in first out queuing function.
114. The readable medium of any one of claims 102 to 113, wherein for each to-be-pushed data includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
115. The readable medium of any one of claims 102 to 114, wherein the data structure corresponding to each initial to-be-pushed data is different.
116. The readable medium of any one of claims 102 to 115, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
117. The readable medium of any one of claims 102 to 116, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
118. The readable medium of any one of claims 102 to 117, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
Date Recue/Date Received 2023-09-15
119. The readable medium of any one of claims 102 to 118, wherein the current to-be-pushed data refers to the data currently in processing.
120. The readable medium of any one of claims 102 to 119, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
121. The readable medium of any one of claims 102 to 120, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
122. The readable medium of any one of claims 102 to 121, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
123. The readable medium of any one of claims 102 to 122, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
124. The readable medium of any one of claims 102 to 123, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
125. The readable medium of any one of claims 102 to 124, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
126. The readable medium of any one of claims 102 to 125, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.

Date Recue/Date Received 2023-09-15
127. The readable medium of any one of claims 102 to 126, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein the supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
128. The readable medium of any one of claims 102 to 127, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
129. The readable medium of any one of claims 102 to 128, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
130. The readable medium of any one of claims 102 to 129, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
131. The readable medium of any one of claims 102 to 130, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
132. The readable medium of any one of claims 102 to 131, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
133. The readable medium of any one of claims 102 to 132, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.

Date Recue/Date Received 2023-09-15
134. The readable medium of any one of claims 102 to 133, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
135. An apparatus comprising:
a supplementary timer processing module confivred to:
stop a regular timer and start the supplementary timer when a first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to a server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtain a second current pushing status corresponding to a current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;
wherein if the second current pushing status is abnormal network status, keep running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;

and a regular timer loop processing module configured to:
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status.
136. The apparatus of claim 135, wherein the regular timer loop processing module is further configured to::
obtain next to-be-pushed data from to-be-pushed data queue;

Date Recue/Date Received 2023-09-15 treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue completes data pushing.
137. The apparatus of claim 135, further comprises:
a to-be-pushed data obtaining module for obtaining to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
a current to-be-pushed data determination module for determining the current to-be-pushed data from the to-be-pushed data queue;
138. The apparatus of claim 135, further comprises:
a regular timer processing module configured to:
push the current to-be-pushed data through the regular timer;
obtain the first current pushing status corresponding to the current to-be-pushed data;
139. The apparatus of claim 135, further comprises:
if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and Date Recue/Date Received 2023-09-15 if the current to-be-pushed data is unsuccessfully pushed, restarting pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
140. The apparatus of claim 135, wherein the to-be-pushed data obtaining module further configured to:
obtain at least one initial to-be-pushed data;
obtain preset data processing rule;
process at least one initial to-be-pushed data according to the preset data processing rule;
obtain correspondingly to-be-pushed data; and compose the to-be-pushed data queue according to at least one to-be-pushed data.
141. The apparatus of claim 135, wherein the current to-be-pushed data determination module is configured to:
obtain at least one to-be-pushed data's priority from the to-be-pushed data queue; and determine the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
142. The apparatus of claim 135, wherein the supplementary timer processing module is further configured to:
when the first current pushing status is abnormal network status, includes:
sending a regular timer's stopping command to the regular timer, wherein the regular timer stops working according to the regular timer's stopping command;
Date Recue/Date Received 2023-09-15 sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
143. The apparatus of claim 135, wherein the regular timer processing module is further configured to:
when the second current pushing status is normal network status includes:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtains the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
144. The apparatus of claim 135, wherein the data queue pushing apparatus is further configured to:
when all the to-be-pushed data in the to-be-pushed data queue complete data pushing includes:
obtaining timer clear up command;

Date Recue/Date Received 2023-09-15 clearing up the regular timer and the supplementary timer according to the timer clear up command;
obtaining a cleared regular timer and a cleared supplementary timer, wherein the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
145. The apparatus of any one of claims 135 to 144, wherein each module is achieved fully or partly by software, hardware, and their combinations.
146. The apparatus of any one of claims 135 to 145, wherein the modules are embedded in the processor or independent of the processor in computer device and are stored in the readable medium of computer device in form of software.
147. The apparatus of any one of claims 135 to 146, communicates with the server through the network.
148. The apparatus of any one of claims 135 to 147, includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
149. The apparatus of any one of claims 135 to 148, wherein the server includes an independent server or a server cluster composed of multiple servers.
150. The apparatus of any one of claims 135 to 149, wherein the to-be-pushed data is data waiting for pushing in a terminal.
151. The apparatus of any one of claims 135 to 150, wherein the to-be-pushed data queue is data function used for achieving first in first out queuing function.
152. The apparatus of any one of claims 135 to 151, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.

Date Recue/Date Received 2023-09-15
153. The apparatus of any one of claims 135 to 152, wherein the data structure corresponding to each initial to-be-pushed data is different.
154. The apparatus of any one of claims 135 to 153, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
155. The apparatus of any one of claims 135 to 154, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
156. The apparatus of any one of claims 135 to 155, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
157. The apparatus of any one of claims 135 to 156, wherein the current to-be-pushed data refers to the data currently in processing.
158. The apparatus of any one of claims 135 to 157, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
159. The apparatus of any one of claims 135 to 158, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in, first out queuing function, then determining the current to-be-pushed data by the first in, first out order.
160. The apparatus of any one of claims 135 to 159, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
161. The apparatus of any one of claims 135 to 160, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.

Date Recue/Date Received 2023-09-15
162. The apparatus of any one of claims 135 to 161, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
163. The apparatus of any one of claims 135 to 162, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
164. The apparatus of any one of claims 135 to 163, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
165. The apparatus of any one of claims 135 to 164, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein the supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
166. The apparatus of any one of claims 135 to 165, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
167. The apparatus of any one of claims 135 to 166, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
168. The apparatus of any one of claims 135 to 167, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.

Date Recue/Date Received 2023-09-15
169. The apparatus of any one of claims 135 to 168, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
170. The apparatus of any one of claims 135 to 169, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
171. The apparatus of any one of claims 135 to 170, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
172. The apparatus of any one of claims 135 to 171, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
173.A device comprising:
a memory includes non-volatile storage medium and internal memory wherein the memory of non-volatile storage medium has an operation system, computer programs and a database wherein the internal memory provides an environment for the operation system and computer program running in a non-volatile storage medium;
a processor configured to provide calculafion and control capabilities;
a network interface to communicate with an external terminal through a network connection;
the database connected through a system bus; and progam instructions stored in the memory and executed by the processor configured to:
Date Recue/Date Received 2023-09-15 stop a regular timer and start a supplementary timer when a first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to a server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtain second current pushing status corresponding to a current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;
wherein if the second current pushing status is abnormal network status, keep running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status;
obtain next to-be-pushed data from a to-be-pushed data queue;
treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
174. The device of claim 173, further comprises:
obtaining the to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determining the current to-be-pushed data from the to-be-pushed data queue;

Date Recue/Date Received 2023-09-15 obtaining the first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the regular timer to a server;
175. The device of claim 173, further comprises:
where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status;
where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and where if the current to-be-pushed data is unsuccessfully pushed, restarting pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
176. The device of claim 173, wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.

Date Recue/Date Received 2023-09-15
177. The device of claim 173, wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
178. The device of claim 173, wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is the abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period, where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
179. The device of claim 173, wherein stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, where if the second current pushing status is normal network status comprises:

Date Recue/Date Received 2023-09-15 sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data throug)i the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
180. The device of claim 173, wherein if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, comprises:
obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
181. The device of any one of claims 173 to 180, communicates with the server through the network.
182. The device of any one of claims 173 to 181, includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
183. The device of any one of claims 173 to 182, wherein the server includes an independent server or a server cluster composed of multiple servers.

Date Recue/Date Received 2023-09-15
184. The device of any one of claims 173 to 183, wherein to-be-pushed data is data waiting for pushing in a terminal.
185. The device of any one of claims 173 to 184, wherein the to-be-pushed data queue is data function used for achieving first in, first out queuing function.
186. The device of any one of claims 173 to 185, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
187. The device of any one of claims 173 to 186, wherein the data structure corresponding to each initial to-be-pushed data is different.
188. The device of any one of claims 173 to 187, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
189. The device of any one of claims 173 to 188, wherein the preset data processing performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
190. The device of any one of claims 173 to 189, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
191. The device of any one of claims 173 to 190, wherein the current to-be-pushed data refers to the data currently in processing.
192. The device of any one of claims 173 to 191, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
Date Recue/Date Received 2023-09-15
193. The device of any one of claims 173 to 192, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
194. The device of any one of claims 173 to 193, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.
195. The device of any one of claims 173 to 194, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
196. The device of any one of claims 173 to 195, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
197. The device of any one of claims 173 to 196, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
198. The device of any one of claims 173 to 197, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
199. The device of any one of claims 173 to 198, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein the supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
200. The device of any one of claims 173 to 199, wherein the regular timer is always connected to network under the normal network status and performing data pushing.

Date Recue/Date Received 2023-09-15
201. The device of any one of claims 173 to 200, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
202. The device of any one of claims 173 to 201, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
203. The device of any one of claims 173 to 202, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
204. The device of any one of claims 173 to 203, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
205. The device of any one of claims 173 to 204, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
206. The device of any one of claims 173 to 205, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
207.A method comprising:

Date Recue/Date Received 2023-09-15 stopping a regular timer and starting a supplementary timer when a first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtaining a second current pushing status corresponding to a current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to a server;
wherein if the second current pushing status is abnormal network status, keeping running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status;
obtaining next to-be-pushed data from the to-be-pushed data queue;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
208. The method of claim 207, further comprises:
obtaining the to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determining the current to-be-pushed data from the to-be-pushed data queue;
obtaining the first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through a regular timer;

Date Recue/Date Received 2023-09-15
209. The method of claim 207, further comprises:
where if the first current pushing status is not abnormal network status, determining whether the current to-be-pushed data is successfully pushed according to the first current to-be-pushed status;
where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and where if the current to-be-pushed data is unsuccessfully pushed, restarting pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
210. The method of claim 207 wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
211. The method of claim 207 wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and Date Recue/Date Received 2023-09-15 determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.
212. The method of claim 207 wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period, where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
213. The method of claim 207 wherein, stopping the supplementary timer and starting the regular timer when the second current pushing status is noimal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, where if the second current pushing status is normal network status comprises:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
Date Recue/Date Received 2023-09-15 sending a regular timer's starting command to the regular timer, wherein the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;
treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
214. The method of claim 207, where if all the to-be-pushed data in the to-be-pushed data queue complete data pushing comprises:
obtaining timer clear up command;
clearing up the regular timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
215. The method of any one of claims 207 to 214, wherein a terminal communicates with the server through the network.
216. The method of any one of claims 207 to 215, wherein the terminal includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
217. The method of any one of claims 207 to 216, wherein the server includes an independent server or a server cluster composed of multiple servers.
218. The method of any one of claims 207 to 217, wherein to-be-pushed data is data waiting for pushing in the terminal.
219. The method of any one of claims 207 to 218, wherein the to-be-pushed data queue is data function used for achieving first in first out queuing function.

Date Recue/Date Received 2023-09-15
220. The method of any one of claims 207 to 219, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, which is determined according to business requirements, application scenarios or product requirements.
221. The method of any one of claims 207 to 220, wherein the data structure corresponding to each initial to-be-pushed data is different.
222. The method of any one of claims 207 to 221, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
223. The method of any one of claims 207 to 222, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
224. The method of any one of claims 207 to 223, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
225. The method of any one of claims 207 to 224, wherein the current to-be-pushed data refers to the data currently in processing.
226. The method of any one of claims 207 to 225, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
227. The method of any one of claims 207 to 226, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
228. The method of any one of claims 207 to 227, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.

Date Recue/Date Received 2023-09-15
229. The method of any one of claims 207 to 228, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
230. The method of any one of claims 207 to 229, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
231. The method of any one of claims 207 to 230, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
232. The method of any one of claims 207 to 231, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
233. The method of any one of claims 207 to 232, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein supplementary timer does not push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
234. The method of any one of claims 207 to 233, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
235. The method of any one of claims 207 to 234, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to try to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
236. The method of any one of claims 207 to 235, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.

Date Recue/Date Received 2023-09-15
237. The method of any one of claims 207 to 236, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
238. The method of any one of claims 207 to 237, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
239. The method of any one of claims 207 to 238, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
240. The method of any one of claims 207 to 239, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.
241.A computer readable medium having stored thereon a program instructions executed by a processor configured to:
stop a regular timer and start a supplementary timer when a first current pushing status is abnormal network status, wherein where a network is abnormal, the regular timer stops working, and the regular timer fails to push the current to-be-pushed data to the server, wherein intermittent control of the two timers avoids performance loss of multiple timers;
obtain second current pushing status corresponding to a current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within a preset period to the server;

Date Recue/Date Received 2023-09-15 wherein if the second current pushing status is abnormal network status, keep running the supplementary timer, obtaining the next preset period through the supplementary timer, pushing the current to-be-pushed data when reaching the next preset period until the current to-be-pushed data is successfully pushed;
stop the supplementary timer and start the regular timer when the second current pushing status is normal network status;
obtain next to-be-pushed data from a to-be-pushed data queue;
treat the next to-be-pushed data as the current to-be-pushed data; and return to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed.
242. The readable medium of claim 241, further comprises:
obtaining the to-be-pushed data queue, wherein the to-be-pushed data queue includes at least one to-be-pushed data;
determining the current to-be-pushed data from the to-be-pushed data queue;
and obtaining the first current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the regular timer to a server.
243. The readable medium of claim 241, further comprises:
where if the first current pushing status is not the abnormal network status, determining the current to-be-pushed data is successfully pushed according to the first current pushing status;
Date Recue/Date Received 2023-09-15 where if the current to-be-pushed data is successfully pushed, obtaining the next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue is successfully pushed; and where if the current to-be-pushed data is unsuccessfully pushed, pushing the current to-be-pushed data through the regular timer until the current to-be-pushed data is successfully pushed.
244. The readable medium of claim 241, wherein obtaining to-be-pushed data queue, the to-be-pushed data queue includes at least one to-be-pushed data, comprises:
obtaining at least one initial to-be-pushed data;
obtaining preset data processing rule;
processing at least one initial to-be-pushed data according to the preset data processing rule;
obtaining correspondingly to-be-pushed data; and composing the to-be-pushed data queue according to at least one to-be-pushed data.
245. The readable medium of claim 241, wherein determining the current to-be-pushed data according to the to-be-pushed data queue, comprises:
obtaining at least one to-be-pushed data's priority from the to-be-pushed data queue; and determining the current to-be-pushed data from the to-be-pushed data queue according to the priority of the to-be-pushed data.

Date Recue/Date Received 2023-09-15
246. The readable medium of claim 241, wherein stopping the regular timer and starting the supplementary timer wherein the first current pushing status is the abnormal network status, obtaining second current pushing status corresponding to the current to-be-pushed data by pushing the current to-be-pushed data through the supplementary timer within the preset period, where if the first current pushing status is abnormal network status comprises:
sending a regular timer's stopping command to the regular timer, the regular timer stops working according to the regular timer's stopping command;
sending a supplementary timer's starting command to the supplementary timer, to make the supplementary timer obtain the preset period according to the supplementary timer's starting command;
pushing the current to-be-pushed data; and obtaining the second current pushing status corresponding to the to-be-pushed data when reaching the preset period.
247. The readable medium of claim 241, wherein stopping the supplementary timer and starting the regular timer when the second current pushing status is normal network status, obtaining next to-be-pushed data from the to-be-pushed data queue, treating the next to-be-pushed data as the current to-be-pushed data, returning to pushing the current to-be-pushed data through the regular timer until at least one of the to-be-pushed data from the to-be-pushed data queue completes data pushing, where if the second current pushing status is normal network status comprises:
sending a supplementary timer's stopping command to the supplementary timer, wherein the supplementary timer stops working according to the supplementary timer's stopping command;
sending a regular timer's starting command to the regular timer, wherein the regular timer obtain the next to-be-pushed data from the next to-be-pushed data queue according to the regular timer's starting command;

Date Recue/Date Received 2023-09-15 treating the next to-be-pushed data as the current to-be-pushed data; and returning to pushing the current to-be-pushed data through the regular timer until one of the to-be-pushed data from the to-be-pushed data queue queue is successfully pushed.
248. The readable medium of claim 241, wherein if all the to-be-pushed data in the to-be-pushed data queue complete data pushing, comprises:
obtaining timer clear up command;
clearing up the revlar timer and the supplementary timer according to the timer clear up command; and obtaining a cleared regular timer and a cleared supplementary timer, the cleared regular timer and the cleared supplementary timer are used for next to-be-pushed data queue.
249. The readable medium of any one of claims 241 to 248, wherein a terminal communicates with the server through the network.
250. The readable medium of any one of claims 241 to 249, wherein the terminal includes personal computers, laptop computers, smart phones, tablets, portable and wearable devices.
251. The readable medium of any one of claims 241 to 250, wherein the server includes an independent server or a server cluster composed of multiple servers.
252. The readable medium of any one of claims 241 to 251, wherein to-be-pushed data is data waiting for pushing in the terminal.
253. The readable medium of any one of claims 241 to 252, wherein the to-be-pushed data queue is data function used for achieving first in first out queuing function.

Date Recue/Date Received 2023-09-15
254. The readable medium of any one of claims 241 to 253, wherein for each to-be-pushed data, includes sorting the data by time stack, sorting the data by the other preset rules, or sorting the data by first in first out rule, determined according to business requirements, application scenarios or product requirements.
255. The readable medium of any one of claims 241 to 254, wherein the data structure corresponding to each initial to-be-pushed data is different.
256. The readable medium of any one of claims 241 to 255, wherein in order to maintain same data format of the to-be-pushed data queue, obtaining preset data processing rules.
257. The readable medium of any one of claims 241 to 256, wherein the preset data processing rules performs processing on initial to-be-pushed data's operation types, variables, or incremental information.
258. The readable medium of any one of claims 241 to 257, wherein the preset data processing rules are obtained according to the business requirements, product requirements or actual application scenarios.
259. The readable medium of any one of claims 241 to 258, wherein the current to-be-pushed data refers to the data currently in processing.
260. The readable medium of any one of claims 241 to 259, wherein determining the to-be pushed data queue is customized, including randomly choosing one of the to-be-pushed data to be the current to-be-pushed data from the to-be-pushed data queue.
261. The readable medium of any one of claims 241 to 260, wherein the current to-be-pushed data's is determined with sorting the to-be-pushed data in the to-be-pushed data queue by first in first out queuing function, then determining the current to-be-pushed data by the first in first out order.
262. The readable medium of any one of claims 241 to 261, wherein a timer is for time control, and by setting the time, the timer starts to work after reaching the set time.

Date Recue/Date Received 2023-09-15
263. The readable medium of any one of claims 241 to 262, wherein the regular timer refers to the timer that is often used, wherein the time setting in the regular timer is very short.
264. The readable medium of any one of claims 241 to 263, wherein the preset period is determined and obtained according to the business requirements, product requirements or actual application scenarios.
265. The readable medium of any one of claims 241 to 264, wherein when the network is a under normal status, the regular timer successfully push the current to-be-pushed data to the server.
266. The readable medium of any one of claims 241 to 265, wherein the supplementary timer is an apparatus for time control, where if there is no abnormal network status or the other reasons unrelated to network which cause the failure pushing of the current to-be-pushed data, the supplementary timer does not get started, wherein the supplementary timer is specifically starting to work and obtaining preset period under abnormal network status.
267. The readable medium of any one of claims 241 to 266, wherein the preset period corresponding to the supplementary timer is greater than the preset period corresponding to the regular timer, wherein supplementary timer does not need to push the to-be-pushed data frequently, wherein the pushing frequency of the supplementary timer is smaller than frequency of the regular timer.
268. The readable medium of any one of claims 241 to 267, wherein the regular timer is always connected to network under the normal network status and performing data pushing.
269. The readable medium of any one of claims 241 to 268, wherein the supplementary timer is connecting to network to perform data pushing, flexibly and intervalley enabling two timers, to tiy to connect to the Internet once in a while through the two timers, and where if once connecting successfully, starting one of the timers for pushing the stored offline data and ensuring the submission efficiency.
Date Recue/Date Received 2023-09-15
270. The readable medium of any one of claims 241 to 269, wherein the initial to-be-pushed data refers to the data before the to-be-pushed data.
271. The readable medium of any one of claims 241 to 270, wherein the to-be-pushed data's priority corresponding to each to-be-pushed data is obtained in advance by determining the business requirements, product requirements or actual application scenarios.
272. The readable medium of any one of claims 241 to 271, wherein the to-be-pushed data with higher priority is pushed first, sorting the to-be-pushed data by the higher priority to lower priority, and composing a current to-be-pushed data queue.
273. The readable medium of any one of claims 241 to 272, wherein the timer clear up command clears up the regular timer and the supplementary timer, when all the to-be-pushed data in the to-be-pushed data queue complete data pushing, detecting if existing any incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue.
274. The readable medium of any one of claims 241 to 273, wherein there is no incomplete data pushing of the to-be-pushed data in the to-be-pushed data queue, obtaining the timer clear up command, clearing up the regular timer and the supplementary timer according to the timer clear up command.

Date Recue/Date Received 2023-09-15
CA3134295A 2020-10-14 2021-10-14 Data queue pushing method and device, computer equipment and storage medium Active CA3134295C (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011097363.3 2020-10-14
CN202011097363.3A CN112214336B (en) 2020-10-14 2020-10-14 Data queue pushing method and device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CA3134295A1 CA3134295A1 (en) 2022-04-14
CA3134295C true CA3134295C (en) 2024-01-02

Family

ID=74054141

Family Applications (1)

Application Number Title Priority Date Filing Date
CA3134295A Active CA3134295C (en) 2020-10-14 2021-10-14 Data queue pushing method and device, computer equipment and storage medium

Country Status (2)

Country Link
CN (1) CN112214336B (en)
CA (1) CA3134295C (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114374747B (en) * 2022-01-11 2023-09-15 高拓讯达(北京)微电子股份有限公司 Method and device for starting timer, electronic equipment and readable storage medium

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9247023B2 (en) * 2011-07-27 2016-01-26 Qualcomm Incorporated System and method for prioritizing requests to a SIM
CN107172182B (en) * 2017-06-06 2021-02-02 深圳市金立通信设备有限公司 Message pushing method, message pushing server and terminal
CN107748695B (en) * 2017-10-24 2020-11-24 平安科技(深圳)有限公司 Timed task processing method and device, storage medium and computer equipment

Also Published As

Publication number Publication date
CA3134295A1 (en) 2022-04-14
CN112214336A (en) 2021-01-12
CN112214336B (en) 2022-11-22

Similar Documents

Publication Publication Date Title
CA3134295C (en) Data queue pushing method and device, computer equipment and storage medium
CN110955508B (en) Asynchronous task scheduling method and device based on distributed architecture and computer equipment
CN105045708A (en) Method and system for processing running errors of software
US11513493B2 (en) Control system driven by real time and non-real time data
CN112379993A (en) Robot process automation processing system, method and device
CN110708197A (en) Monitoring device, method for setting monitoring policy of monitoring device, and storage medium
CN114416284A (en) Distributed operating system control method, apparatus, device, medium, and program product
CN114189559A (en) Interface repeat request processing method and system based on Axios
CN114006891A (en) Information reporting method, device, equipment and storage medium
CA3184895A1 (en) User behavior data writing method and device, computer equipment and storage medium
CN114513468B (en) Method, device, equipment, storage medium and product for protecting flow in Sentinel
CA3138768A1 (en) Data processing method, equipment, and device based on a timed task
CN110543349B (en) Application starting acceleration method and device and computer readable storage medium
CN110879757B (en) Restarting method and device for abnormal operation of client and computer equipment
CN115525415B (en) Data processing method, device, equipment and medium
CN110647526B (en) Batch data processing method, device, computer equipment and storage medium
CA3191232A1 (en) Data monitoring method and device, computer equipment and storage medium
CN115187332A (en) Order information processing method, device, system, electronic device and storage medium
CN113342548A (en) Message notification method, device, equipment and storage medium based on Toast
CN118069294A (en) Inter-core interrupt injection method and device, electronic equipment and storage medium
CN117742919A (en) Task scheduling method and device
CN116185695A (en) Log processing method and device, electronic equipment and storage medium
CN110888815A (en) Application program testing method, device, equipment and storage medium
CN116860394A (en) Batch restarting method, equipment and storage medium of CKE nodes
CN115062249A (en) Page exporting method, page exporting device, electronic equipment and page exporting system

Legal Events

Date Code Title Description
EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506

EEER Examination request

Effective date: 20220506