CN117194324A

CN117194324A - Snapshot-based service continuous operation method, device, medium and equipment

Info

Publication number: CN117194324A
Application number: CN202311153078.2A
Authority: CN
Inventors: 徐敬慈; 董琪; 贾琳; 王玉婷; 季铖; 雷蕾; 李婷姝; 岳茹霞; 吕婉晴; 张燕义; 郭旦萍; 魏文芳; 夏苗苗; 阮文静; 刘慧敏; 赵晓燕
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-09-07
Filing date: 2023-09-07
Publication date: 2023-12-08

Abstract

A business follow-up method, device, medium and equipment based on snapshot can be applied to the financial field or other fields. The method comprises the following steps: generating a service snapshot corresponding to the target service and generating an identifier corresponding to the service snapshot when the target service is interrupted, wherein the service snapshot stores service information of each service page of the target service; storing the service snapshot and the corresponding relation between the service snapshot and the identifier; when the user continues to operate the target service, checking whether the user has the authority to continue operating the target service, if so, calling the service snapshot corresponding to the first identifier, and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier, wherein the first identifier is the identifier selected by the user. By utilizing the method, the business handling efficiency can be improved, the waiting time of the client can be shortened, and the operation experience of the teller and the business handling experience of the user are improved.

Description

Snapshot-based service continuous operation method, device, medium and equipment

Technical Field

The present application relates to the field of computers, and in particular, to a snapshot-based service continuation method, apparatus, medium, and device.

Background

The special business of part of banks has the conditions that the information needs to be verified midway and the information is checked and returned to the front business page, the current business needs to be interrupted at the moment, and a plurality of systems do not carry out business follow-up processing.

Disclosure of Invention

In order to solve the technical problems in the prior art, the application provides a snapshot-based business follow-up method, a snapshot-based business follow-up device, a snapshot-based business follow-up medium and snapshot-based business follow-up equipment, which can improve business handling efficiency, facilitate shortening of waiting time of clients and further improve operation experience of teller and business handling experience of users.

In a first aspect, the present application provides a snapshot-based service continuous operation method, where the method includes generating a service snapshot corresponding to a target service each time a target service is interrupted, and generating an identifier corresponding to the service snapshot, where service information of each service page of the target service is stored in the service snapshot; storing the service snapshot and storing the corresponding relation between the service snapshot and the identifier; when a user continues to operate the target service, checking whether the user has the authority to continue operating the target service, if so, calling a service snapshot corresponding to a first identifier, and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier, wherein the first identifier is the identifier selected by the user.

By utilizing the method, when the teller interrupts the transacted target service, a service snapshot corresponding to the target service and an identifier corresponding to the service snapshot are generated. When multiple interruptions of the target service occur, multiple service snapshots may be stored. When the user continues to work on the target service, firstly checking whether the user has the authority to continue the work, and if so, calling the corresponding service snapshot according to the first identification selected by the user, thereby recovering and obtaining the service information of each service page. The first identifier is an identifier corresponding to one service snapshot in the generated one or more service snapshots, that is, the user can select which service snapshot to call, and the identifier is used as a basis for distinguishing different service snapshots by the user. With this method, even if the service is interrupted, the user can quickly restore the service information of each service page by selecting the service snapshot without restarting the operation. Therefore, the implementation method improves the operation experience of the teller, improves the business handling efficiency, shortens the waiting time of the clients handling the business, and improves the business handling experience of the clients.

In one possible implementation manner, the identifier includes a service state identifier and a snapshot version number identifier, and the generating an identifier corresponding to the service snapshot specifically includes:

determining a service state of the target service when the target service is interrupted, and generating a service state identifier, wherein the service state is used for indicating a processing stage of the target service when the target service is interrupted;

and generating a snapshot version number identification of the service snapshot corresponding to the current service.

In one possible implementation, the processing stage at which the target service is in when interrupted is one of the following:

waiting for verification data, waiting for third party auditing, returning to the preface business page for information confirmation, interrupting the business processing overtime or waiting for supplementary business information.

In one possible implementation manner, the checking whether the user has the authority to perform the continuous operation on the target service specifically includes:

determining a service class of the target service;

and when the user has the authority of the business category of the target business, determining that the user has the authority of continuing to work the target business.

In a possible implementation manner, after the service information of each service page of the target service is recovered through the service snapshot corresponding to the first identifier, the method further includes:

when the target service is determined to be processed currently, allowing the user to view all service pages of the target service only;

and allowing the user to edit each service page of the target service when the target service is determined to be not processed currently.

In one possible implementation, the method further includes:

when a deleting request of the user for the service snapshot of the target service is received, if the user is determined to have the authority to delete the service snapshot and the target service is determined to be processed currently, deleting the corresponding service snapshot of the target service according to the deleting request.

In a second aspect, the application also provides a business follow-up device based on the transaction snapshot, which comprises a generating unit, a storage unit and a business follow-up unit. And the generating unit is used for generating a service snapshot corresponding to the target service every time the target service is interrupted, and generating an identifier corresponding to the service snapshot, wherein the service snapshot stores service information of each service page of the target service. The storage unit is used for storing the service snapshot and storing the corresponding relation between the service snapshot and the identifier. And the service continuing unit is used for checking whether the user has the authority to continue the operation of the target service when the user continues the operation of the target service, if so, calling a service snapshot corresponding to a first identifier, and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier, wherein the first identifier is the identifier selected by the user.

By utilizing the device, the operation experience of a teller is improved, the business handling efficiency is improved, and the waiting time of a customer handling the business is shortened, so that the business handling experience of the customer is also improved.

In one possible implementation manner, a service continuation unit is specifically configured to determine a service class of the target service;

In a possible implementation manner, the service continuation unit is further configured to, when determining that the target service has been processed currently, allow only the user to view each service page of the target service; and allowing the user to edit each service page of the target service when the target service is determined to be not processed currently.

In a possible implementation manner, the device further comprises a deleting unit;

and the deleting unit is used for deleting the corresponding service snapshot of the target service according to the deleting request if the user is determined to have the authority to delete the service snapshot and the target service is determined to be processed currently when the deleting request of the user to the service snapshot of the target service is received.

In a possible implementation manner, the generating unit is specifically configured to determine a service state of the target service when the target service is interrupted, and generate the service state identifier, where the service state is used to indicate a processing stage in which the target service is in when the target service is interrupted;

In one possible implementation, the processing stage at which the target service is in at the time of interruption is one of the following:

In a third aspect, the present application further provides a storage medium, where a computer program is stored, where the computer program when executed by a processor implements a snapshot-based service continuation method.

In a fourth aspect, the present application further provides an electronic device, where the electronic device is configured to execute a program, and when the program is executed, the snapshot-based service continuation method is executed.

Drawings

FIG. 1 is a flowchart of a snapshot-based business continuation method according to an embodiment of the present application;

FIG. 2 is a flowchart of another snapshot-based business continuation method according to an embodiment of the present application;

FIG. 3 is a flowchart of another method for continuing a snapshot-based service according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a business follow-up device based on transaction snapshot according to an embodiment of the present application;

FIG. 5 is a schematic diagram of another business continuation device based on transaction snapshot according to an embodiment of the present application;

fig. 6 is a schematic diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the person skilled in the art more clearly understand the solution of the present application, the following first describes an application scenario of the solution of the present application.

When a teller in a bank, a hospital or other scenes handles a service for a user on electronic equipment, the situation that the user needs to verify data midway and wait for and return to a front-end service page to check information exists due to the service specificity, and the current service needs to be interrupted at the moment. When the service is interrupted, as many systems do not process the service, the information of the service page or even the preceding service page is lost, and the processing needs to be restarted when the service is continued again.

The process of restarting is not friendly to the operator operation experience, wastes manpower and time resources, causes low service handling efficiency, and on the other hand, prolongs the waiting time of the clients handling the service, and can require repeated information provision for cooperation with the re-handling of the service, so that the service handling experience of the clients is poor.

In order to solve the above problems, embodiments of the present application provide a snapshot-based service continuation method, apparatus, medium, and device, where each time a teller interrupts a target service being transacted, a service snapshot corresponding to the target service and an identifier corresponding to the service snapshot are generated. And correspondingly storing the identification and the business snapshot. The service snapshot stores service information of each service page of the target service. When multiple interruptions of the target service occur, multiple service snapshots may be stored. When the user continues to work on the target service, firstly checking whether the user has the authority to continue the work, and if so, calling the corresponding service snapshot according to the first identification selected by the user, thereby recovering and obtaining the service information of each service page. Even if the service is interrupted, the user can quickly restore the service information of each service page by selecting the service snapshot without restarting the operation. Therefore, the implementation method improves the operation experience of the teller, improves the business handling efficiency, shortens the waiting time of the clients handling the business, and improves the business handling experience of the clients.

In order to make the solution of the present application more clearly understood by those skilled in the art, the following description will describe the solution of the present application in connection with the accompanying drawings in the embodiments of the present application.

The words "first," "second," and the like in the description of the application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

The embodiment of the application provides a snapshot-based business follow-up method, which is specifically described below with reference to the accompanying drawings.

Referring to fig. 1, a flowchart of a snapshot-based business continuation method according to an embodiment of the present application is shown.

The method comprises the following steps:

s11: and generating a service snapshot corresponding to the target service and generating an identifier corresponding to the service snapshot when the target service is interrupted.

Multiple service interruptions may occur during the processing of the service by the user. And each time the service is interrupted, a service snapshot corresponding to the target service can be generated. The generation of the service snapshot may be triggered automatically when the service is interrupted or initiated by the user, which is not particularly limited by the embodiments of the present application.

It can be understood that the service snapshot in the embodiment of the application corresponds to a specific target service, different target services and different generated service snapshots. The service snapshot stores service information of each service page of the target service.

For example, for a target service, the service processing process includes a plurality of service pages, and each service page needs to fill in corresponding service information. Taking the example that the service page comprises three pages, when the user interrupts the service while processing the second page, the first part of the second page is processed, and the second part is unprocessed. The generated service snapshot comprises service information of a first processed page and service information of a first part in a second page, and for the second part and a third page in the second page, the corresponding service information is null.

The identification of the service snapshot is used for uniquely identifying the service snapshot, so that a user can be directly matched with the corresponding service snapshot according to the identification.

In some embodiments, the identification of the service snapshot includes a service status identification and a snapshot version number identification.

The service state identifier is used for representing the service state, and the service state is used for indicating the processing stage of the target service when the target service is interrupted. The processing stage of the target service when interrupted is one of the following: waiting for verification data, waiting for third party auditing, returning to the preface business page for information confirmation, interrupting the business processing overtime or waiting for supplementary business information, and the like. So that the user can intuitively determine the service snapshot which is expected to be selected according to the processing stage. The above processing stages are merely illustrative. In practical application, the corresponding processing stage can be set according to the specific service class.

The snapshot version number is identified as the version sequence number of the service snapshot, and is generally numbered from small to large according to the generation time sequence of the service snapshot. For example: the snapshot version number of the service snapshot generated at the first moment is 1.0; the snapshot version number of the service snapshot generated at the second time after the first time is 2.0, and so on.

And generating the corresponding identifier of the service snapshot, namely generating a service state identifier and a snapshot version number identifier.

S12: storing the service snapshot and storing the corresponding relation between the service snapshot and the identification.

The storing of the service snapshot and the corresponding relation can be triggered by a user or automatically stored after the service snapshot and the identifier corresponding to the service snapshot are generated, which is not limited by the embodiment of the application.

S13: when the user continues to operate the target service, checking whether the user has the authority to continue to operate the target service.

If yes, execution is S14, otherwise execution is S16.

In the embodiment of the application, after the user initiates the request for continuing the operation to the interrupted target service, the user is not directly allowed to call the transaction snapshot through the operation request of the user, but is checked whether the user has the authority for continuing the target service.

This is because it is necessary to determine whether or not the job user before and after the interruption is the same person, or whether or not the right to handle the service is provided similarly, because the interruption process is performed on the target service. Through permission verification, the user who does not have permission to continue operation can be prevented from acquiring the service information of each service page of the operation before service interruption, so that information leakage is avoided. Therefore, the verification authority can improve the safety of the operation.

S14: and calling the business snapshot corresponding to the first identifier.

When the verification is passed, the user is allowed to proceed. One or more snapshots of the service may be currently saved because of one or more interruptions of the previous service.

At this time, the user can determine the node for re-operation according to the actual situation requirement, that is, determine which service snapshot is selected from one or more service snapshots.

The first identifier is an identifier selected by a user, and the service snapshot corresponding to the first identifier is the service snapshot which is generated and stored.

For example, for a service, it is interrupted twice. The first interruption generates a service snapshot A, the corresponding mark is a, the second interruption generates a service snapshot B, and the corresponding mark is B.

Because the mark comprises the processing stage of the target service when the target service is interrupted, after the user determines the starting stage of the continuous operation according to the actual situation, the selected first mark is B, and the service snapshot B corresponding to the first mark B is called.

S15: and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier.

And after the service snapshot corresponding to the first identifier is called, recovering and obtaining the service information of each service page of the target service according to the service snapshot so as to facilitate the user to continue operation.

S16: the user is not allowed to invoke the service snapshot.

Because the user does not have the authority to continue the operation, the user is not allowed to call the service snapshot, and the service information leakage of the service page is avoided.

In summary, by using the technical scheme provided by the embodiment of the application, when the transacted target service is interrupted, a service snapshot corresponding to the target service and an identifier corresponding to the service snapshot are generated. When multiple interruptions of the target service occur, multiple service snapshots may be stored. When the user continues to work on the target service, firstly checking whether the user has the authority to continue the work, and if so, calling the corresponding service snapshot according to the first identification selected by the user, thereby quickly recovering the service information of each service page. With this method, even if the service is interrupted, the user can quickly restore the service information of each service page by selecting the service snapshot without restarting the operation. Therefore, the implementation method improves the operation experience of the teller, improves the business handling efficiency, shortens the waiting time of the clients handling the business, and improves the business handling experience of the clients.

The following description is made in connection with specific implementations.

Referring to fig. 2, a flowchart of another snapshot-based business continuation method according to an embodiment of the present application is shown.

The method comprises the following steps:

s201: and when the target service is interrupted, generating a service snapshot corresponding to the target service.

S202: and determining the service state of the target service when the target service is interrupted, and generating a service state identifier.

The service snapshot identification comprises a service state identification and a snapshot version number identification. The service state identifier is used for representing a service state, and the service state is used for indicating a processing stage of the target service when the target service is interrupted. The processing stage of the target service when interrupted is one of the following: waiting for verification data, waiting for third party auditing, returning to the preface business page for information confirmation, interrupting the business processing overtime or waiting for supplementary business information, and the like.

The user can intuitively determine the service snapshot which is expected to be selected according to the processing stage.

S203: and generating a snapshot version number identification of the service snapshot corresponding to the current service.

S204: storing the service snapshot and storing the corresponding relation between the service snapshot and the identification.

S205: and when the user continues to operate the target service, determining the service class of the target service.

The embodiment of the application does not limit the specific service category of the target service, and a person skilled in the art can set the service category according to the actual situation and divide various services into various service categories.

For example, the business category may be an account application category, an account cancellation category, a product subscription information registration category, or the like.

S206: it is determined whether the user has the job right to the service class of the target service.

If yes, then execute S207; otherwise, S210 is performed.

When a request of a user for continuing the operation is generated on the interrupted target service, the user is not directly requested by the operation of the user and allowed to call the transaction snapshot, but the user is checked whether the user has the authority of continuing the target service. Through permission verification, the user who does not have permission to continue operation can be prevented from acquiring the service information of each service page of the operation before service interruption, so that information leakage is avoided. Therefore, the verification authority can improve the safety of the operation.

S207: it is determined whether the target traffic has currently been processed.

If yes, executing S208; otherwise, S209 is performed.

S208: only allowing the user to view each service page of the target service.

Since the business has completed processing, editing of the information of the business page is not allowed at this time, and viewing of the information is allowed.

S209: allowing the user to edit each service page of the target service.

S210: the user is not allowed to invoke the service snapshot.

The above steps are merely for convenience of description, and are not limited to the technical solution of the present application, and in practical application, the above steps may be adjusted, for example, the order of S202 and S203 may be exchanged.

In the above embodiment, when the user continues to work on the target service, it is first checked whether the user has the authority to continue to work, then it is determined whether the target service has been processed currently, and after the target service is completed, the information of the service page is not allowed to be edited but only can be checked, and only when the allowed service is not completed, the service page can be edited. With this method, even if the service is interrupted, the user can quickly restore the service information of each service page by selecting the service snapshot without restarting the operation. And after the business is completed, even if the page is restored through the business snapshot, editing cannot be performed, so that the user is prevented from tampering with the business result, and the business handling safety is ensured.

In practical application, in order to avoid that excessive or expired service snapshots are stored to cause that the storage space of the electronic device is occupied in a large amount, the embodiment of the application further provides a mode for deleting the service snapshots, which is specifically described below with reference to the accompanying drawings.

Referring to fig. 3, a flowchart of another snapshot-based business continuation method according to an embodiment of the present application is shown.

S301: and receiving a deleting request of the user to the service snapshot of the target service.

S302: and determining whether the user has the authority to delete the business snapshot.

If yes, then execute S303; otherwise, S305 is performed.

S303: it is determined whether the target traffic has currently been processed.

If yes, executing S304; otherwise, S305 is performed.

S304: and deleting the service snapshot of the corresponding target service according to the deleting request.

The deletion request indicates that the deletion may be all or part of the service snapshot corresponding to the target service, which is not specifically limited in the embodiment of the present application.

S305: the service snapshot of the corresponding target service is not allowed to be deleted.

In summary, by using the method, when deleting the service snapshot, the user is not directly required to delete the service snapshot, but is checked to determine whether the user has the authority to delete the service snapshot, and then the target service is checked to be processed currently, so that the condition that the service snapshot generated when the target service is interrupted is maliciously deleted or accidentally deleted, and the unfinished target service cannot be recovered is avoided. The technical means can ensure the security of the service snapshot of the target service.

Based on the snapshot-based service follow-up method provided by the embodiment, the embodiment of the application also provides a snapshot-based service follow-up device, and the method is specifically described below with reference to the accompanying drawings.

Referring to fig. 4, a schematic diagram of a service continuation apparatus based on snapshot according to an embodiment of the present application is shown.

The apparatus 400 includes: a generating unit 401, a storing unit 402, and a service continuation unit 403.

The generating unit 401 is configured to generate a service snapshot corresponding to the target service and generate an identifier corresponding to the service snapshot, where service information of each service page of the target service is stored in the service snapshot every time the target service is interrupted.

The storage unit 402 is configured to store the service snapshot, and store a correspondence between the service snapshot and the identifier.

The service continuation unit 403 is configured to check, when the user continues to work on the target service, whether the user has permission to continue to work on the target service, and if so, invoke a service snapshot corresponding to the first identifier, and restore service information of each service page of the target service through the service snapshot corresponding to the first identifier, where the first identifier is an identifier selected by the user.

In a possible implementation manner, the forming unit 401 is specifically configured to determine a service state of the target service when the target service is interrupted, generate the service state identifier, and generate a snapshot version number identifier of a service snapshot corresponding to the current service. The service status is used to indicate the processing stage of the target service when the target service is interrupted.

The processing stage of the target service when interrupted is one of the following:

In one possible implementation, the service continuation unit 403 is specifically configured to determine a service class of the target service; and when the user has the authority of the business category of the target business, determining that the user has the authority of continuing to work the target business.

In a possible implementation manner, the service continuation unit 403 is further configured to, when determining that the target service has been processed currently, only allow the user to view each service page of the target service; and allowing the user to edit each service page of the target service when the target service is determined to be not processed currently.

Referring to fig. 5, a schematic diagram of another snapshot-based service continuation apparatus according to an embodiment of the present application is shown.

The device shown in fig. 5 differs from that shown in fig. 4 in that it further comprises: the unit 404 is deleted.

The deleting unit 404 is configured to, when receiving a deletion request of the user for the service snapshot of the target service, delete the corresponding service snapshot of the target service according to the deletion request if it is determined that the user has the authority to delete the service snapshot and it is determined that the target service has been processed currently.

In summary, by using the device provided by the embodiment of the application, even if the service is interrupted, the user can quickly recover the service information of each service page by selecting the service snapshot without restarting the operation. Therefore, the implementation method improves the operation experience of the teller, improves the business handling efficiency, shortens the waiting time of the clients handling the business, and improves the business handling experience of the clients. And the device improves the safety of the operation by checking whether the user has the authority to continue the operation on the target service.

The processor includes a kernel, and the kernel fetches the corresponding program unit from the memory. The kernel can be provided with one or more than one, and the snapshot-based business follow-up method is realized by adjusting kernel parameters.

The embodiment of the application provides a storage medium, wherein a program is stored on the storage medium, and the program realizes the snapshot-based business follow-up method when being executed by a processor.

The embodiment of the application provides a processor which is used for running a program, wherein the program runs to execute the snapshot-based business follow-up method.

The embodiment of the application provides an electronic device, and the electronic device is specifically described below with reference to the accompanying drawings.

Referring to fig. 6, the schematic diagram of an electronic device according to an embodiment of the present application is shown.

The electronic device 60 comprises at least one processor 601, at least one memory 602 connected to the processor 601, and a bus 603.

The processor 601 and the memory 602 perform communication with each other through the bus 603.

The processor 601 is configured to invoke the program instructions in the memory 602 to perform the method of information recommendation based on speech described above. The electronic device of the application may be a server, a PC, a PAD, a mobile phone, etc.

The present application also provides a computer program product adapted to perform a computer program initialized with the above snapshot-based business continuation method when executed on a data processing device.

The snapshot-based business follow-up method, device, medium and equipment provided by the application can be used in the financial field or other fields, for example, can be used in an application scene of continuing operation after business interruption in the financial field. Other fields are any field other than the financial field, for example, the computer technology field. The foregoing is merely an example, and the snapshot-based service continuation method, apparatus, medium and device provided by the present application are not limited.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, the device includes one or more processors (CPUs), memory, and a bus. The device may also include input/output interfaces, network interfaces, and the like.

The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), among other forms in computer readable media, the memory including at least one memory chip. Memory is an example of a computer-readable medium.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. The apparatus embodiments described above are merely illustrative, wherein the units and modules illustrated as separate components may or may not be physically separate. In addition, some or all of the units and modules can be selected according to actual needs to achieve the purpose of the embodiment scheme. Those of ordinary skill in the art will understand and implement the present application without undue burden.

The foregoing is merely illustrative of the embodiments of this application and it will be appreciated by those skilled in the art that variations and modifications may be made without departing from the principles of the application, and it is intended to cover all modifications and variations as fall within the scope of the application.

Claims

1. A snapshot-based business continuation method, the method comprising:

generating a service snapshot corresponding to a target service when the target service is interrupted, and generating an identifier corresponding to the service snapshot, wherein the service snapshot stores service information of each service page of the target service;

storing the service snapshot and storing the corresponding relation between the service snapshot and the identifier;

when a user continues to operate the target service, checking whether the user has the authority to continue operating the target service, if so, calling a service snapshot corresponding to a first identifier, and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier, wherein the first identifier is the identifier selected by the user.

2. The method according to claim 1, wherein the identifiers include a service status identifier and a snapshot version number identifier, and the generating the identifier corresponding to the service snapshot specifically includes:

3. The method of claim 1, wherein the processing stage at which the target traffic is at the time of interruption is one of:

4. The method according to claim 1, wherein the checking whether the user has the right to continue the operation on the target service specifically comprises:

determining a service class of the target service;

5. The method according to any one of claims 1-4, wherein after the service information of each service page of the target service is recovered by the service snapshot corresponding to the first identifier, the method further includes:

6. The method according to claim 1, wherein the method further comprises:

7. A snapshot-based business continuance apparatus, the apparatus comprising: the system comprises a generating unit, a storage unit and a service continuous unit;

the generating unit is used for generating a service snapshot corresponding to the target service every time the target service is interrupted, and generating an identifier corresponding to the service snapshot, wherein the service snapshot stores service information of each service page of the target service;

the storage unit is used for storing the service snapshot and storing the corresponding relation between the service snapshot and the identifier;

and the service continuing unit is used for checking whether the user has the authority to continue the operation of the target service when the user continues the operation of the target service, if so, calling a service snapshot corresponding to a first identifier, and recovering the service information of each service page of the target service through the service snapshot corresponding to the first identifier, wherein the first identifier is the identifier selected by the user.

8. The apparatus according to claim 7, wherein the service continuation unit is configured to determine a service class of the target service;

9. The apparatus of claim 7, wherein the service continuation unit is further configured to allow only the user to view each service page of the target service when it is determined that the target service has been currently processed; and allowing the user to edit each service page of the target service when the target service is determined to be not processed currently.

10. The apparatus of claim 7, wherein the apparatus further comprises a deletion unit;

11. A storage medium having stored thereon a computer program which, when executed by a processor, implements the snapshot-based business continuation method of any one of claims 1-6.

12. An electronic device for running a program, wherein the program when run performs the snapshot-based business continuation method of any one of claims 1-6.