WO2019056736A1 - 断点数据获取方法、装置、终端设备及介质 - Google Patents

断点数据获取方法、装置、终端设备及介质 Download PDF

Info

Publication number
WO2019056736A1
WO2019056736A1 PCT/CN2018/082495 CN2018082495W WO2019056736A1 WO 2019056736 A1 WO2019056736 A1 WO 2019056736A1 CN 2018082495 W CN2018082495 W CN 2018082495W WO 2019056736 A1 WO2019056736 A1 WO 2019056736A1
Authority
WO
WIPO (PCT)
Prior art keywords
list
tracked
organization
organizations
needs
Prior art date
Application number
PCT/CN2018/082495
Other languages
English (en)
French (fr)
Inventor
田正伟
薛艳
张领
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019056736A1 publication Critical patent/WO2019056736A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793—Remedial or corrective actions

Definitions

  • the present application belongs to the field of data transmission technologies, and in particular, to a method, an apparatus, a terminal device, and a medium for acquiring a breakpoint data.
  • the system is abnormal, and there is more or less data loss.
  • the system data is incomplete and the data needs to be rolled back.
  • Rollback refers to data processing errors that restore data to the last correct state. Take the system pull data as an example. If an exception occurs in the system, all data needs to be rolled back. The workload is large and error-prone.
  • the embodiment of the present application provides a method, an apparatus, a terminal device, and a medium for acquiring a breakpoint data, so as to solve the problem that an existing system needs to roll back all the data, and the workload is large and error-prone.
  • a first aspect of the embodiments of the present application provides a method for acquiring breakpoint data, including:
  • the organization update list that needs to be tracked is used as a new list of organizations to be tracked, and the step of sending a data processing progress query request to the organization in the list of organizations to be tracked is returned;
  • an organization update list that needs to be tracked closest to the abnormal time of the system is acquired, and a prompt for re-processing the data of the system abnormality is sent to the institution in the latest organization update list that needs to be tracked.
  • a second aspect of the embodiment of the present application provides a device for acquiring breakpoint data, including:
  • a list determining unit for determining a list of institutions that need to be tracked
  • Processing progress query unit configured to send a data processing progress query request to an organization in the list of organizations that need to be tracked
  • a processing progress receiving unit configured to receive a data processing progress returned by the mechanism in the organization list that needs to be tracked, and record the data processing progress and the receiving time;
  • a list updating unit configured to generate an organization update list that needs to be tracked according to the data processing progress and a list of organizations that need to be tracked;
  • the processing progress query unit is further configured to: after the first preset time interval, use the organization update list that needs to be tracked as a new list of organizations to be tracked, and return to execute to send a data processing progress to the organization in the list of organizations that need to be tracked.
  • the system abnormality processing unit is configured to: when an abnormality occurs in the system, acquire an organization update list that needs to be tracked closest to the abnormal time of the system, and send a system abnormality to the institution in the latest organization list that needs to be tracked to reprocess the data. Tips.
  • a third aspect of the embodiments of the present application provides a breakpoint data acquisition terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processing The following steps are implemented when the computer readable instructions are executed:
  • the organization update list that needs to be tracked is used as a new list of organizations to be tracked, and the step of sending a data processing progress query request to the organization in the list of organizations to be tracked is returned;
  • an organization update list that needs to be tracked closest to the abnormal time of the system is acquired, and a prompt for re-processing the data of the system abnormality is sent to the institution in the latest organization update list that needs to be tracked.
  • a fourth aspect of the embodiments of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by at least one processor, implement the following steps:
  • the organization update list that needs to be tracked is used as a new list of organizations to be tracked, and the step of sending a data processing progress query request to the organization in the list of organizations to be tracked is returned;
  • an organization update list that needs to be tracked closest to the abnormal time of the system is acquired, and a prompt for re-processing the data of the system abnormality is sent to the institution in the latest organization update list that needs to be tracked.
  • a data processing progress query request is sent to the organization in the list of organizations that need to be tracked, and the data processing progress returned by the organization in the list of organizations to be tracked is received, and the data processing progress is recorded.
  • receiving time according to the data processing progress and the list of organizations that need to be tracked, generating an organization update list that needs to be tracked; after the first preset time interval, the organization update list that needs to be tracked is used as a new list of organizations to be tracked, and the execution is returned.
  • the mechanism in the system sends a system exception to re-process the data prompt, complete the breakpoint data acquisition quickly and easily, without rolling back all the data, saving a lot of time, improving the data processing accuracy, and solving the abnormality of the existing system requires all the data. Carry back Heavy workload and error-prone issues, thus reducing operation and improve the user experience to meet practical needs.
  • FIG. 1 is a schematic flowchart of a method for acquiring breakpoint data according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for acquiring breakpoint data according to another embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for acquiring breakpoint data according to still another embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for acquiring breakpoint data according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for acquiring breakpoint data according to another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a breakpoint data obtaining program provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a device for acquiring a breakpoint data according to an embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a method for acquiring a breakpoint data according to an embodiment of the present disclosure.
  • an angle trigger of a terminal is used as an example.
  • the terminal may be a smart phone.
  • Mobile terminals such as tablets.
  • the processing of the terminal may include the following steps:
  • S101 Determine a list of organizations that need to be tracked.
  • the identity acquisition request may be sent to the organization that needs to be tracked, the identity of the organization that needs to be tracked is obtained, and a list of organizations that need to be tracked is generated.
  • the institutions that need to be tracked can have one or more, depending on the actual situation.
  • S102 Send a data processing progress query request to an organization in the list of organizations that need to be tracked.
  • a data processing progress query request may be sent to the organization in the list of organizations that need to be tracked at a preset time, for example, at 8:00 am every day, to know the data processing progress of the organization that needs to be tracked in time. If there are multiple organizations that need to be tracked, a data processing progress query request may be sent to these organizations at the same time, or a data processing progress query request may be sent to these organizations in turn according to the order of the institutions in the list of organizations to be tracked.
  • S103 Receive data processing progress returned by the mechanism in the organization list that needs to be tracked, and record the data processing progress and the receiving time.
  • the data processing progress returned by the mechanism A is recorded under the name of the organization A, and the time at which the data processing progress is received is recorded.
  • the processing progress check request may be sent to the organization in the list of organizations that need to be tracked, or the organization A is sent as an example to send a processing progress check request to the organization A, and the request carries the data processing progress of the organization A. If the information indicating that the processing progress returned by each mechanism is correct, step S104 is performed, otherwise, step S102 is re-executed.
  • S104 Generate an organization update list that needs to be tracked according to the data processing progress and the list of organizations that need to be tracked.
  • the organization list that needs to be tracked is adjusted according to the received data processing progress, and the organization update list that needs to be tracked is obtained, and the organization update list that needs to be tracked may be sent to the organization in the list of organizations to be tracked for review, and when the need to track is received
  • step S105 is performed, otherwise, step S104 is re-executed.
  • the organization update list that needs to be tracked is used as a new list of organizations to be tracked, and the step of sending a data processing progress query request to the organization in the list of organizations to be tracked is returned.
  • the first preset time interval is set according to an actual situation.
  • a data processing progress query request is sent to the organization in the organization update list that needs to be tracked, and the mechanism in the organization update list that needs to be tracked is returned.
  • the data processing progress is further updated based on the data processing progress update list that needs to be tracked.
  • S106 When an abnormality occurs in the system, obtain an organization update list that needs to be tracked closest to the abnormal time of the system, and send a prompt to the institution in the latest organization list that needs to be tracked to reprocess the data.
  • an abnormality occurs at a point of 5 o'clock in the system, and a list of mechanism updates required to be tracked is generated by 4:50 closest to 5 points, and a mechanism for resampling data is sent to a mechanism in the organization update list that needs to be tracked.
  • a mechanism for resampling data is sent to a mechanism in the organization update list that needs to be tracked.
  • the method for acquiring breakpoint data in the embodiment of the present application quickly and simply completes the acquisition of the breakpoint data, without rolling back all the data, saving a lot of time, improving the accuracy of data processing, and solving the abnormality of the existing system. All data is rolled back, the workload is large and error-prone, reducing user operations, improving user experience, and meeting actual application needs.
  • FIG. 2 is a schematic flowchart of a method for acquiring breakpoint data according to another embodiment of the present application.
  • generating an organization update list that needs to be tracked may include S204 according to the data processing progress and the list of organizations that need to be tracked.
  • S201 ⁇ S203 are the same as S101 ⁇ S103 in the previous embodiment
  • S205 ⁇ S206 are the same as S105 ⁇ S106 in the previous embodiment.
  • S204 may include S2041 ⁇ S2042.
  • S2041 Determine, according to the data processing progress, whether there is a mechanism for completing data processing.
  • the list is deleted, and a new list of organizations to be tracked is generated, that is, an organization update list that needs to be tracked, and the organization's data processing progress can be recorded in the organization update list that needs to be tracked.
  • the above-mentioned list of organizations that need to be tracked according to the received data processing progress can reduce the number of organizations that need to be tracked, reduce subsequent tracking work, save resources, and be suitable for applications.
  • FIG. 3 is a schematic flowchart of a method for acquiring breakpoint data according to still another embodiment of the present application.
  • the list of institutions determining the need to track may include S301.
  • S302 ⁇ S306 are the same as S102 ⁇ S106 in the previous embodiment.
  • S301 may include S3011 ⁇ S3012.
  • S3011 Send a prompt to the organization in the pre-stored organization list whether the data needs to be processed.
  • a list of the total institutions of each institution may be pre-stored, for example, a total of 10 organizations, and each organization is sent a prompt for processing data to determine which institution needs to process data.
  • S3012 Receive information returned by the organization in the pre-stored organization list, and determine, according to the information and the pre-stored organization list, a list of organizations that need to be tracked, and the information is information for confirming that data needs to be processed or information that does not need to be processed.
  • each institution receives the above-mentioned prompt whether or not the data needs to be processed, returns corresponding information according to its own situation, and if it needs to process the data, returns information confirming that the data needs to be processed, otherwise, returns information confirming that the data is not required to be processed.
  • the mechanism A is taken as an example. If the information returned by the mechanism A needs to be processed, the determination mechanism A is a mechanism that needs to be tracked. If the confirmation returned by the organization A does not need to process the data, it is determined. Organization A is an organization that does not require tracking. Finally, according to the information returned by each organization, the list of organizations to be tracked is obtained, and only the organizations that need to be tracked are tracked by the data, and the organizations that do not need to be tracked do not perform data tracking, thereby reducing user operations and improving user experience.
  • FIG. 4 is a schematic flowchart of a method for acquiring breakpoint data according to still another embodiment of the present application.
  • the difference between the foregoing embodiment and the embodiment is S401 ⁇ S404, wherein S405 ⁇ S408 are the same as S103 ⁇ S106 in the previous embodiment.
  • S405 ⁇ S408 are the same as S103 ⁇ S106 in the previous embodiment.
  • the method for acquiring the breakpoint data in this embodiment may further include:
  • S401 Determine a list of organizations that need to be tracked.
  • S402 Send a prompt to the organization in the list of organizations that need to be tracked whether the list is correct.
  • each organization in the list of organizations that need to be tracked is sent a prompt indicating whether the list is correct, and the prompt carries a list of institutions that need to be tracked.
  • a data processing progress query request is sent to the organization in the organization list to be tracked to ensure that the subsequent processing is normally performed.
  • S404 If receiving the information that the confirmation list returned by the first institution is incorrect, and receiving the list change request sent by the first institution, reviewing whether the list change request meets the preset list change rule, if the list is reviewed
  • the change request conforms to the preset list change rule, and according to the list change request, the list of organizations that need to be tracked is changed, and the changed list of organizations to be tracked is used as a new list of organizations to be tracked, and the list of organizations to be tracked is executed.
  • the institution in the middle sends a data processing progress query request, and the first institution is any one of the institutions list that needs to be tracked.
  • the list change request is reviewed according to the preset list change rule, and if the review is passed, the change request is tracked according to the list change request.
  • the organization list sends a data processing progress query request to the organization in the changed organization list to be tracked. If the audit fails, the list change failure information is returned to the first institution, and the information carries the preset list change rule.
  • the preset list change rule can be set according to actual conditions.
  • the list of organizations that need to be tracked is sent to the corresponding organization for confirmation. If there is an error, the list of organizations to be tracked may be further changed to avoid subsequent breakpoint data acquisition errors.
  • FIG. 5 is a schematic flowchart of a method for acquiring breakpoint data according to still another embodiment of the present application.
  • the difference between the foregoing embodiment and the embodiment is S507 ⁇ S509, wherein S501 ⁇ S506 are the same as S101 ⁇ S106 in the previous embodiment.
  • S501 ⁇ S506 are the same as S101 ⁇ S106 in the previous embodiment.
  • the method for acquiring the breakpoint data in this embodiment may further include:
  • S507 Send a prompt for returning the receipt to the institution in the latest institution update list that needs to be tracked.
  • S508 Determine whether a receipt returned by the second institution is received after the second preset time interval, and the second institution is any one of the latest institutions that need to track the update list.
  • a prompt for returning the receipt may be sent to the institutions at the same time, if the institutions are at the preset time.
  • the interval returns the receipt, indicating that these organizations have received a reminder that the system needs to reprocess the data. If only some organizations return the receipt at the preset time interval, it indicates that some organizations have not received the system exception and need to reprocess the data. In order to notify these organizations to obtain breakpoint data as soon as possible, the organization that has not received the receipt can be re-sent to send a reminder that the system needs to reprocess the data to meet the actual application needs.
  • the preset time interval is set as needed, and may be 5 seconds, 10 seconds, or the like.
  • FIG. 6 is a schematic diagram showing the operating environment of the breakpoint data acquisition program provided by the embodiment of the present application. For the convenience of explanation, only the parts related to the present embodiment are shown.
  • the breakpoint data acquisition program 600 is installed and runs in the terminal device 60.
  • the terminal device 60 can be a mobile terminal, a palmtop computer, a server, or the like.
  • the terminal device 60 can include, but is not limited to, a memory 601, a processor 602, and a display 603.
  • Figure 6 shows only terminal device 60 having components 601-603, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the memory 601 may be an internal storage unit of the terminal device 60, such as a hard disk or memory of the terminal device 60, in some embodiments.
  • the memory 601 may also be an external storage device of the terminal device 60 in other embodiments, such as a plug-in hard disk equipped on the terminal device 60, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, flash card, etc.
  • SMC smart memory card
  • secure digital device Secure Digital, SD
  • the memory 601 may also include both an internal storage unit of the terminal device 60 and an external storage device.
  • the memory 601 is configured to store application software and various types of data installed in the terminal device 60, such as program codes of the breakpoint data acquisition program 600.
  • the memory 601 can also be used to temporarily store data that has been output or is about to be output.
  • the processor 602 can be a central processor (Central) in some embodiments A processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 601, such as executing the breakpoint data acquisition program 600 and the like.
  • Central central processor
  • CPU central processing unit
  • microprocessor microprocessor or other data processing chip for running program code or processing data stored in the memory 601, such as executing the breakpoint data acquisition program 600 and the like.
  • the display 603 may be an LED display, a liquid crystal display, a touch liquid crystal display, and an OLED (Organic) in some embodiments. Light-Emitting Diode, organic light-emitting diodes, etc.
  • the display 603 is used to display information processed in the terminal device 60 and a user interface for displaying visualizations, such as an application menu interface, an application icon interface, and the like.
  • the components 601-603 of the terminal device 60 communicate with one another via a system bus.
  • FIG. 7 is a functional block diagram of the breakpoint data obtaining program 600 provided by the embodiment of the present application.
  • the breakpoint data acquisition program 600 may be divided into one or more modules, the one or more modules being stored in the memory 601 and being processed by one or more processors ( This embodiment is performed by the processor 602) to complete the application.
  • the breakpoint data acquisition program 600 may be divided into a list determination unit 701, a process progress inquiry unit 702, a process progress reception unit 703, a list update unit 704, and a system exception processing unit 705.
  • a module referred to in the present application refers to a series of computer readable instruction instruction segments capable of performing a specific function, and is more suitable than the program to describe the execution process of the breakpoint data acquisition program 600 in the terminal device 60. The following description will specifically describe the functions of the modules 701-705.
  • the list determining unit 701 is configured to determine a list of organizations that need to be tracked.
  • the processing progress query unit 702 is configured to send a data processing progress query request to the organization in the organization list that needs to be tracked.
  • the processing progress receiving unit 703 is configured to receive a data processing progress returned by the mechanism in the organization list that needs to be tracked, and record the data processing progress and the receiving time.
  • the list updating unit 704 is configured to generate an organization update list that needs to be tracked according to the data processing progress and the organization list that needs to be tracked.
  • the processing progress query unit 702 is configured to: after the first preset time interval, use the organization update list that needs to be tracked as a new list of organizations to be tracked, and return to execute to send a data processing progress to the organization in the list of organizations that need to be tracked.
  • the system abnormality processing unit 705 is configured to: when an abnormality occurs in the system, acquire an organization update list that needs to be tracked closest to an abnormal time of the system, and send a system abnormality to the institution in the latest organization update list that needs to be tracked, and needs to be reprocessed. Tips for the data.
  • the list updating unit 704 may be divided into a processing progress determining unit 7041 and an update list generating unit 7042.
  • the processing progress determining unit 7041 is configured to determine, according to the data processing progress, whether there is a mechanism for completing data processing.
  • the update list generating unit 7042 is configured to delete the mechanism that completes the data processing from the list of institutions that need to be tracked, and generate an organization update list that needs to be tracked.
  • the list determining unit 701 may be divided into a first prompt sending unit 7011 and an information processing unit 7012.
  • the first prompt sending unit 7011 is configured to send a prompt to the organization in the pre-stored organization list whether the data needs to be processed.
  • the information processing unit 7012 is configured to receive information returned by the mechanism in the pre-stored organization list, and determine, according to the information and the pre-stored organization list, a list of organizations that need to be tracked, where the information is to confirm that information needs to be processed or is not required to be confirmed. Processing data information.
  • the breakpoint data obtaining program 600 may also be divided into a second prompt sending unit 706 and a list changing unit 707.
  • the second prompt sending unit 706 is configured to send a prompt to the organization in the list of organizations that need to be tracked whether the list is correct.
  • the processing progress query unit 702 is configured to: if receiving the correct information of the confirmation list returned by the organization in the organization list that needs to be tracked, execute the data processing progress query request to the organization in the organization list that needs to be tracked.
  • the list changing unit 707 is configured to: if receiving the information of the confirmation list error returned by the first institution, and receiving the list change request sent by the first institution, reviewing whether the list change request meets the preset list change rule, If the review of the list change request conforms to the preset list change rule, the list of organizations that need to be tracked is changed according to the list change request.
  • the processing progress query unit 702 is configured to use the changed organization list that needs to be tracked as a new organization list that needs to be tracked, and execute the data processing progress query request to the organization in the organization list that needs to be tracked, where the first The organization is any institution in the list of institutions that need to be tracked.
  • the breakpoint data obtaining program 600 may also be divided into a third prompt sending unit 708 and a receipt determining unit 709.
  • the third prompt sending unit 708 is configured to send a prompt for returning the receipt to the institution in the latest organization update list that needs to be tracked.
  • the receipt determining unit 709 is configured to determine whether the receipt returned by the second mechanism is received after the second preset time interval, and the second mechanism is any one of the latest institutions that need to be tracked to update the list.
  • the system abnormality processing unit 705 is configured to: if it is determined that the receipt returned by the second mechanism is not received after the second preset time interval, send a prompt to the second organization that the system abnormality needs to reprocess the data.
  • each functional unit and module in the foregoing system may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be implemented by hardware.
  • Formal implementation can also be implemented in the form of software functional units.
  • the specific names of the respective functional units and modules are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application.
  • the disclosed device/terminal device and method may be implemented in other manners.
  • the device/terminal device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units.
  • components may be combined or integrated into another system, or some features may be omitted or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium.
  • the computer readable instructions when executed by a processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like.
  • the computer readable medium can include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard drive, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read-Only) Memory), random access memory (RAM, Random) Access Memory), electrical carrier signals, telecommunications signals, and software distribution media.
  • ROM Read Only memory
  • RAM Random Access Memory
  • electrical carrier signals telecommunications signals
  • telecommunications signals and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media Does not include electrical carrier signals and telecommunication signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种断点数据获取方法、装置、终端设备及介质。该方法包括：确定需要跟踪机构列表（S101）；向列表中的机构发送一个数据处理进度查询请求（S102）；接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻（S103）；根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表（S104）；经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求（S105）；当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构列表中的机构发送系统异常需重新处理数据的提示（S105），该方法可以快速、简单地获取断点数据，无需回滚所有数据，节省大量时间，提高数据处理准确性。

Description

断点数据获取方法、装置、终端设备及介质
本申请申明享有2017年9月22日递交的申请号为201710865431.8、名称为“断点数据获取方法及终端设备”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请属于数据传输技术领域，尤其涉及断点数据获取方法、装置、终端设备及介质。
 背景技术
目前系统出现异常，或多或少存在数据丢失的情况，直接导致系统数据不完整，需要对数据进行回滚。回滚（Rollback）指的是数据处理错误，将数据恢复到上一次正确状态的行为。以系统拉取报表数据为例，如果系统出现异常，需要对所有数据进行回滚，工作量大且容易出错。
 技术问题
有鉴于此，本申请实施例提供了断点数据获取方法、装置、终端设备及介质，以解决现有系统出现异常需要对所有数据进行回滚，工作量大且容易出错的问题。
 技术解决方案
本申请实施例的第一方面提供了一种断点数据获取方法，包括：
确定需要跟踪的机构列表；
向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
本申请实施例的第二方面提供了一种断点数据获取装置，包括：
列表确定单元，用于确定需要跟踪的机构列表；
处理进度查询单元，用于向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
处理进度接收单元，用于接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
列表更新单元，用于根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
所述处理进度查询单元，还用于经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
系统异常处理单元，用于当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
本申请实施例的第三方面，提供了一种断点数据获取终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
确定需要跟踪的机构列表；
向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
本申请实施例的第四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
确定需要跟踪的机构列表；
向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
 有益效果
本申请实施例，通过确定需要跟踪的机构列表，向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，接收需要跟踪的机构列表中的机构返回的数据处理进度，记录该数据处理进度和接收时刻，根据该数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向该最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示，快速、简单地完成断点数据获取，无需回滚所有数据，节省大量时间，提高数据处理准确性，解决现有系统出现异常需要对所有数据进行回滚，工作量大且容易出错的问题，减少用户操作，提高用户体验，满足实际应用需要。
 附图说明
图 1是本申请实施例提供的一种断点数据获取方法的示意流程图；
图2是本申请另一实施例提供的一种断点数据获取方法的示意流程图；
图3是本申请再一实施例提供的一种断点数据获取方法的示意流程图；
图4是本申请又一实施例提供的一种断点数据获取方法的示意流程图；
图5是本申请又一实施例提供的一种断点数据获取方法的示意流程图；
图6是本申请实施例提供的一种断点数据获取程序的示意性框图；
图7是本申请实施例提供的一种断点数据获取终端设备的示意性框图。
 本发明的实施方式
为了说明本申请所述的技术方案，下面通过具体实施例来进行说明。
参见图1，图1是本申请实施例提供的一种断点数据获取方法的示意流程图，在该实施例中，是以终端的角度触发为例进行说明，这里，终端可以为智能手机、平板电脑等移动终端。如图1所示，在该实施例中，终端的处理过程可以包括以下步骤：
S101：确定需要跟踪的机构列表。
这里，可以向需要跟踪的机构发送身份标识获取请求，获取需要跟踪的机构的身份标识，生成需要跟踪的机构列表。需要跟踪的机构可以有一个或多，根据实际情况确定。
S102：向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求。
具体地，可以在预设时间向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，例如每天上午八点，及时了解需要跟踪的机构的数据处理进度。如果需要跟踪的机构有多个，可以同时向这些机构发送一个数据处理进度查询请求，或者，按照需要跟踪的机构列表中的机构排序，依次向这些机构发送一个数据处理进度查询请求。
S103：接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻。
这里，以机构A为例，将机构A返回的数据处理进度记录在机构A名下，并记录接收该数据处理进度的时刻。为了保证后续处理正常进行，可以向需要跟踪的机构列表中的机构发送处理进度核对请求，还是以机构A为例，向机构A发送一个处理进度核对请求，该请求携带机构A的数据处理进度，若接收到各个机构返回的处理进度正确的信息，执行步骤S104，否则，重新执行步骤S102。
S104：根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表。
具体地，根据接收的数据处理进度调整需要跟踪的机构列表，得到需要跟踪的机构更新列表，可以将需要跟踪的机构更新列表发送给需要跟踪的机构列表中的机构进行审核，当接收到需要跟踪的机构列表中的机构返回的审核通过信息时，执行步骤S105，否则，重新执行步骤S104。
S105：经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤。
这里，第一预设时间间隔根据实际情况设置，经过第一预设时间间隔，向需要跟踪的机构更新列表中的机构发送一个数据处理进度查询请求，接收需要跟踪的机构更新列表中的机构返回的数据处理进度，进一步根据该数据处理进度更新需要跟踪的机构更新列表。
S106：当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
具体地，例如系统5点出现异常，距离5点最近的有4点50生成的需要跟踪的机构更新列表，向该需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示，还是以机构A为例，若机构A接收到系统异常需重新处理数据的提示，机构A根据该提示重新处理数据，获取断点数据。
从以上描述可知，本申请实施例的断点数据获取方法，快速、简单地完成断点数据获取，无需回滚所有数据，节省大量时间，提高数据处理准确性，解决现有系统出现异常需要对所有数据进行回滚，工作量大且容易出错的问题，减少用户操作，提高用户体验，满足实际应用需要。
请参阅图2，图2是本申请另一实施例提供的一种断点数据获取方法的示意流程图。与图1对应的实施例的区别在于：根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表可以包括S204。其中S201~S203与上一实施例中的S101~S103相同，S205~S206与上一实施例中的S105~S106相同，具体请参阅上述实施例中S101~S103、S105~S106的相关描述，此处不赘述。具体地，S204可以包括S2041~S2042。
S2041：根据所述数据处理进度判断是否有完成数据处理的机构。
S2042：若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
这里，根据各个机构的数据处理进度判断是否有完成数据处理的机构，若有，停止对完成数据处理的机构发送数据处理进度查询请求，即停止跟踪，将完成数据处理的机构从需要跟踪的机构列表中删除，生成新的需要跟踪的机构列表，即需要跟踪的机构更新列表，可以在需要跟踪的机构更新列表中记录机构的数据处理进度。
上述根据接收的数据处理进度不断更新需要跟踪的机构列表，可以减少需要跟踪的机构数目，降低后续跟踪工作，节省资源，适合应用。
请参阅图3，图3是本申请再一实施例提供的一种断点数据获取方法的示意流程图。与图1对应的实施例的区别在于：所述确定需要跟踪的机构列表可以包括S301。其中S302~S306与上一实施例中的S102~S106相同，具体请参阅上述实施例中S102~S106的相关描述，此处不赘述。具体地，S301可以包括S3011~S3012。
S3011：向预存的机构列表中的机构发送一个是否需要处理数据的提示。
具体地，可以预先存储各个机构总的机构列表，例如一共有10家机构，向各个机构发送一个是否需要处理数据的提示，确定哪家机构需要处理数据。
S3012：接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
这里，各个机构接收到上述是否需要处理数据的提示，根据自身情况返回相应的信息，如果需要处理数据，返回确认需要处理数据的信息，否则，返回确认不需要处理数据的信息。
还以机构A为例进行说明，若接收到机构A返回的确认需要处理数据的信息后，确定机构A为需要跟踪的机构，若接收到机构A返回的确认不需要处理数据的信息后，确定机构A为不需要跟踪的机构。最后根据各个机构返回的信息得到需要跟踪的机构列表，后续只对需要跟踪的机构进行数据跟踪，不需要需要跟踪的机构不进行数据跟踪，减少用户操作，提高用户体验。
请参阅图4，图4为本申请再一实施例提供的一种断点数据获取方法的示意流程图。本实施例上述实施例的区别在于S401~S404，其中S405~S408与上一实施例中的S103~S106相同，具体请参阅上述实施例中S103~S106的相关描述，此处不赘述。本实施例中的断点数据获取方法还可以包括：
S401：确定需要跟踪的机构列表。
S402：向需要跟踪的机构列表中的机构发送一个列表是否正确的提示。
这里，向需要跟踪的机构列表中每个机构发送一个列表是否正确的提示，该提示携带需要跟踪的机构列表。
S403：若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求。
具体地，在接收到各个机构返回的确认列表正确的信息后，向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，保证后续处理正常进行。
S404：若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表，将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
这里，若第一机构返回的确认列表错误的信息，且接收到第一机构发送的列表更改请求，根据预设列表更改规则审核该列表更改请求，若审核通过，根据该列表更改请求更改需要跟踪的机构列表，向更改后的需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，若审核不通过，向第一机构返回列表更改失败信息，该信息携带预设列表更改规则。具体地，预设列表更改规则可以根据实际情况设置。
这里，在确定需要跟踪的机构列表后，将需要跟踪的机构列表发送给相应的机构进行确认，如果有误，可以进一步更改需要跟踪的机构列表，避免后续断点数据获取出错。
请参阅图5，图5为本申请再一实施例提供的一种断点数据获取方法的示意流程图。本实施例上述实施例的区别在于S507~S509，其中S501~S506与上一实施例中的S101~S106相同，具体请参阅上述实施例中S103~S106的相关描述，此处不赘述。本实施例中的断点数据获取方法还可以包括：
S507：向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示。
S508：判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构。
S509：若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
具体地，在向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示后，可以同时向这些机构发送一个返回收条的提示，如果这些机构在预设时间间隔都返回了收条，说明这些机构都收到了系统异常需重新处理数据的提示，如果只有部分机构在预设时间间隔返回了收条，说明还有一些机构没有收到系统异常需重新处理数据的提示，为了尽快通知这些机构获取断点数据，可以重新向没有收到收条的机构发送一个系统异常需重新处理数据的提示，满足实际应用需要。这里，预设时间间隔根据需要设置，可以为5秒、10秒等。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
对应于上文实施例所述的断点数据获取方法，图6示出了本申请实施例提供的断点数据获取程序的运行环境示意图。为了便于说明，仅示出了与本实施例相关的部分。
在本实施例中，所述的断点数据获取程序600安装并运行于终端设备60中。该终端设备60可以是移动终端、掌上电脑、服务器等。该终端设备60可包括，但不仅限于，存储器601、处理器602及显示器603。图6仅示出了具有组件601-603的终端设备60，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
所述存储器601在一些实施例中可以是所述终端设备60的内部存储单元，例如该终端设备60的硬盘或内存。所述存储器601在另一些实施例中也可以是所述终端设备60的外部存储设备，例如所述终端设备60上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器601还可以既包括所述终端设备60的内部存储单元也包括外部存储设备。所述存储器601用于存储安装于所述终端设备60的应用软件及各类数据，例如所述断点数据获取程序600的程序代码等。所述存储器601还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器602在一些实施例中可以是一中央处理器（Central Processing Unit，CPU），微处理器或其他数据处理芯片，用于运行所述存储器601中存储的程序代码或处理数据，例如执行所述断点数据获取程序600等。
所述显示器603在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED（Organic Light-Emitting Diode，有机发光二极管）触摸器等。所述显示器603用于显示在所述终端设备60中处理的信息以及用于显示可视化的用户界面，例如应用菜单界面、应用图标界面等。所述终端设备60的部件601-603通过系统总线相互通信。
请参阅图7，是本申请实施例提供的断点数据获取程序600的功能模块图。在本实施例中，所述的断点数据获取程序600可以被分割成一个或多个模块，所述一个或者多个模块被存储于所述存储器601中，并由一个或多个处理器（本实施例为所述处理器602）所执行，以完成本申请。例如，在图7中，所述的断点数据获取程序600可以被分割成列表确定单元701、处理进度查询单元702、处理进度接收单元703、列表更新单元704和系统异常处理单元705。本申请所称的模块是指能够完成特定功能的一系列计算机可读指令指令段，比程序更适合于描述所述断点数据获取程序600在所述终端设备60中的执行过程。以下描述将具体介绍所述模块701-705的功能。
其中，列表确定单元701，用于确定需要跟踪的机构列表。处理进度查询单元702，用于向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求。处理进度接收单元703，用于接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻。列表更新单元704，用于根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表。所述处理进度查询单元702，用于经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤。系统异常处理单元705，用于当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
可选的，所述列表更新单元704可以被分割为处理进度判断单元7041和更新列表生成单元7042。
其中，处理进度判断单元7041，用于根据所述数据处理进度判断是否有完成数据处理的机构。更新列表生成单元7042，用于若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
可选的，所述列表确定单元701可以被分割为第一提示发送单元7011和信息处理单元7012。其中，第一提示发送单元7011，用于向预存的机构列表中的机构发送一个是否需要处理数据的提示。信息处理单元7012，用于接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
可选的，所述的断点数据获取程序600还可以被分割成第二提示发送单元706和列表更改单元707。其中，第二提示发送单元706，用于向需要跟踪的机构列表中的机构发送一个列表是否正确的提示。处理进度查询单元702，用于若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求。列表更改单元707，用于若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表。处理进度查询单元702，用于将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
可选的，所述的断点数据获取程序600还可以被分割成第三提示发送单元708和收条判断单元709。其中，第三提示发送单元708，用于向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示。收条判断单元709，用于判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构。系统异常处理单元705，用于若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。实施例中的各功能单元、模块可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中，上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。另外，各功能单元、模块的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。上述系统中单元、模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的实施例中，应该理解到，所揭露的装置/终端设备和方法，可以通过其它的方式实现。例如，以上所描述的装置/终端设备实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通讯连接可以是通过一些接口，装置或单元的间接耦合或通讯连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一计算机可读存储介质中，该计算机可读指令在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令包括计算机可读指令代码，所述计算机可读指令代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器（ROM，Read-Only Memory）、随机存取存储器（RAM，Random Access Memory）、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可读介质不包括电载波信号和电信信号。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种断点数据获取方法，其特征在于，包括：
    确定需要跟踪的机构列表；
    向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
    根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
    经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
    当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
  2. 如权利要求1所述的断点数据获取方法，其特征在于，根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表包括：
    根据所述数据处理进度判断是否有完成数据处理的机构；
    若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
  3. 如权利要求1所述的断点数据获取方法，其特征在于，所述确定需要跟踪的机构列表包括：
    向预存的机构列表中的机构发送一个是否需要处理数据的提示；
    接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
  4. 如权利要求1所述的断点数据获取方法，其特征在于，还包括：
    向需要跟踪的机构列表中的机构发送一个列表是否正确的提示；
    若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表，将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
  5. 如权利要求1所述的断点数据获取方法，其特征在于，还包括：
    向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示；
    判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构；
    若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
  6. 一种断点数据获取装置，其特征在于，包括：
    列表确定单元，用于确定需要跟踪的机构列表；
    处理进度查询单元，用于向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    处理进度接收单元，用于接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
    列表更新单元，用于根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
    所述处理进度查询单元，还用于经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
    系统异常处理单元，用于当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
  7. 根据权利要求6所述的断点数据获取装置，其特征在于，所述列表更新单元包括：
    处理进度判断单元，用于根据所述数据处理进度判断是否有完成数据处理的机构；
    更新列表生成单元，用于若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
  8. 根据权利要求6所述的断点数据获取装置，其特征在于，所述列表确定单元包括：
    第一提示发送单元，用于向预存的机构列表中的机构发送一个是否需要处理数据的提示；
    信息处理单元，用于接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
  9. 根据权利要求6所述的断点数据获取装置，其特征在于，还包括：
    第二提示发送单元，用于向需要跟踪的机构列表中的机构发送一个列表是否正确的提示；
    处理进度查询单元，用于若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    列表更改单元，用于若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表；
    处理进度查询单元，用于将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
  10. 根据权利要求6所述的断点数据获取装置，其特征在于，还包括：
    第三提示发送单元，用于向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示；
    收条判断单元，用于判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构；
    系统异常处理单元，用于若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
  11. 一种断点数据获取终端设备，其特征在于，包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
    确定需要跟踪的机构列表；
    向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
    根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
    经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
    当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
  12. 根据权利要求11所述的断点数据获取终端设备，其特征在于，根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表包括：
    根据所述数据处理进度判断是否有完成数据处理的机构；
    若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
  13. 根据权利要求11所述的断点数据获取终端设备，其特征在于，所述确定需要跟踪的机构列表包括：
    向预存的机构列表中的机构发送一个是否需要处理数据的提示；
    接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
  14. 根据权利要求11所述的断点数据获取终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    向需要跟踪的机构列表中的机构发送一个列表是否正确的提示；
    若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表，将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
  15. 根据权利要求11所述的断点数据获取终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示；
    判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构；
    若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被至少一个处理器执行时实现如下步骤：
    确定需要跟踪的机构列表；
    向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    接收需要跟踪的机构列表中的机构返回的数据处理进度，记录所述数据处理进度和接收时刻；
    根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表；
    经过第一预设时间间隔，将需要跟踪的机构更新列表作为新的需要跟踪的机构列表，返回执行向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求的步骤；
    当系统出现异常时，获取距离系统出现异常时刻最近的需要跟踪的机构更新列表，向所述最近的需要跟踪的机构更新列表中的机构发送一个系统异常需重新处理数据的提示。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，根据所述数据处理进度和需要跟踪的机构列表，生成需要跟踪的机构更新列表包括：
    根据所述数据处理进度判断是否有完成数据处理的机构；
    若判定有完成数据处理的机构，则将完成数据处理的机构从需要跟踪的机构列表中删除，生成需要跟踪的机构更新列表。
  18. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述确定需要跟踪的机构列表包括：
    向预存的机构列表中的机构发送一个是否需要处理数据的提示；
    接收预存的机构列表中的机构返回的信息，根据所述信息和预存的机构列表，确定需要跟踪的机构列表，所述信息为确认需要处理数据的信息或者确认不需要处理数据的信息。
  19. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    向需要跟踪的机构列表中的机构发送一个列表是否正确的提示；
    若接收到需要跟踪的机构列表中的机构返回的确认列表正确的信息，则执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求；
    若接收到第一机构返回的确认列表错误的信息，且接收到所述第一机构发送的列表更改请求，则审核所述列表更改请求是否符合预设列表更改规则，若审核所述列表更改请求符合预设列表更改规则，则根据所述列表更改请求更改需要跟踪的机构列表，将更改后的需要跟踪的机构列表作为新的需要跟踪的机构列表，执行所述向需要跟踪的机构列表中的机构发送一个数据处理进度查询请求，所述第一机构为需要跟踪的机构列表中的任意一个机构。
  20. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被至少一个处理器执行时还实现如下步骤：
    向所述最近的需要跟踪的机构更新列表中的机构发送一个返回收条的提示；
    判断经过第二预设时间间隔是否收到第二机构返回的收条，所述第二机构为所述最近的需要跟踪的机构更新列表中的任意一个机构；
    若判定经过第二预设时间间隔没有收到所述第二机构返回的收条，则重新向所述第二机构发送一个系统异常需重新处理数据的提示。
PCT/CN2018/082495 2017-09-22 2018-04-10 断点数据获取方法、装置、终端设备及介质 WO2019056736A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710865431.8A CN108255629B (zh) 2017-09-22 2017-09-22 断点数据获取方法及终端设备
CN201710865431.8 2017-09-22

Publications (1)

Publication Number Publication Date
WO2019056736A1 true WO2019056736A1 (zh) 2019-03-28

Family

ID=62721286

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/082495 WO2019056736A1 (zh) 2017-09-22 2018-04-10 断点数据获取方法、装置、终端设备及介质

Country Status (2)

Country Link
CN (1) CN108255629B (zh)
WO (1) WO2019056736A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111478751B (zh) * 2020-03-30 2023-03-24 百富计算机技术（深圳）有限公司 一种数据断点续传方法、装置及终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101286127A (zh) * 2008-05-08 2008-10-15 华中科技大学 一种多叉日志存储的连续数据保护和恢复方法
CN103198159A (zh) * 2013-04-27 2013-07-10 国家计算机网络与信息安全管理中心 一种基于事务重做的异构集群多副本一致性维护方法
CN104424162A (zh) * 2013-08-21 2015-03-18 鸿合科技有限公司 一种生成最近使用的文档记录的方法及装置
CN106682017A (zh) * 2015-11-09 2017-05-17 高德软件有限公司 一种数据库更新方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201013550A (en) * 2008-09-17 2010-04-01 Chunghwa Telecom Co Ltd Operating flow control and management system and the method thereof
CN104794138B (zh) * 2014-01-22 2018-08-24 深圳市沃信科技有限公司 一种数据库交易结果确认方法、装置及系统
CN106611364B (zh) * 2015-10-22 2020-07-24 中国电信股份有限公司 存储碎片整理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101286127A (zh) * 2008-05-08 2008-10-15 华中科技大学 一种多叉日志存储的连续数据保护和恢复方法
CN103198159A (zh) * 2013-04-27 2013-07-10 国家计算机网络与信息安全管理中心 一种基于事务重做的异构集群多副本一致性维护方法
CN104424162A (zh) * 2013-08-21 2015-03-18 鸿合科技有限公司 一种生成最近使用的文档记录的方法及装置
CN106682017A (zh) * 2015-11-09 2017-05-17 高德软件有限公司 一种数据库更新方法及装置

Also Published As

Publication number Publication date
CN108255629A (zh) 2018-07-06
CN108255629B (zh) 2020-09-22

Similar Documents

Publication Publication Date Title
CN108139958B (zh) 用于处理事件流的事件的系统和方法
CN110489313B (zh) 基于区块链的操作日志记录方法、装置及存储介质
US20090112939A1 (en) Linking framework for information technology management
WO2020000720A1 (zh) 服务器、报文处理方法、程序和计算机可读存储介质
US20150309889A1 (en) Recovery of a transaction after xa end
CN114925084B (zh) 分布式事务处理方法、系统、设备及可读存储介质
CN111225073B (zh) 业务编码分配方法及装置、存储介质、计算机系统
CN110555150B (zh) 一种数据监控方法、装置、设备和存储介质
JP2022550408A (ja) 在庫データを取得するための方法、装置、端末機器及び記憶媒体
CN110895472A (zh) 一种识别业务变更的方法和装置
WO2023240830A1 (zh) 一种信息管理方法、装置、设备及介质
US20240095726A1 (en) Systems for reimbursing and reconciling pharamacy-related transactions
US20190303360A1 (en) Database lock
US9292345B2 (en) Systems, methods, and computer program products for processing sets of instructions for mobile devices
CN111444199B (zh) 数据处理方法及装置、存储介质和处理器
WO2019056736A1 (zh) 断点数据获取方法、装置、终端设备及介质
CN112950191A (zh) 基于退费业务的业务数据处理方法、装置及计算机设备
CN109597819B (zh) 用于更新数据库的方法和装置
CN115147031B (zh) 清算工作流执行方法、装置、设备及介质
US8285775B2 (en) Expedited transaction failure handling by leveraging a reliable message transport protocol to assist detection of discarded processing
CN110765148B (zh) 一种业务数据处理方法及装置
CN113419718A (zh) 数据报送方法、装置、设备及介质
KR20060059040A (ko) 데이터 백업 시스템 및 그 방법
US20140046691A1 (en) Method, apparatus, and computer program product for versioning electronic health records
CN111584084A (zh) 用户信息处理的方法、装置、电子设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18859436

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 24.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18859436

Country of ref document: EP

Kind code of ref document: A1