Data processing method and apparatus, electronic device, medium, and product

Abstract

The present disclosure relates to a data processing method, device, electronic equipment, medium and product, the method comprising: in response to an execution request of a target event, constructing target event backup data, the target event backup data being used to describe a loading state of the target event; obtaining loading data of the target event, and updating the target event backup data based on the loading data; and according to a state of the updated target event backup data, reporting an execution result of the target event, so that the execution result of the event can be reported in time in the event execution process, and data in the event execution process can be accurately obtained.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to a data processing method, apparatus, electronic device, medium, and product. Background Technology

[0002] During event execution, such as during application startup, it is necessary to report the application startup process in a timely manner to facilitate the effective collection of data generated during startup.

[0003] In existing technologies, reporting is mainly processed through batch reporting. For example, a trigger time is set in advance, and when the trigger time is reached, an application startup reporting task is submitted.

[0004] However, using existing technologies makes it difficult to effectively handle execution events of some long processes (such as multiple loading tasks in a mini-game), reducing the accuracy of the data obtained during event execution. Summary of the Invention

[0005] To address the aforementioned technical problems, this disclosure provides a data processing method, apparatus, electronic device, medium, and product.

[0006] Firstly, this disclosure provides a data processing method, including:

[0007] In response to an execution request for a target event, backup data for the target event is constructed, which describes the loading state when the target event is executed.

[0008] Obtain the loading data when the target event is executed, and update the target event backup data based on the loading data;

[0009] When the target event finishes execution, the execution result of the target event is reported based on the status of the updated target event backup data.

[0010] In one possible design, the completion of the target event execution corresponds to the successful execution of the target event. The step of reporting the execution result of the target event based on the updated status of the target event backup data includes:

[0011] If the updated target event backup data exists, then delete the updated target event backup data;

[0012] The first execution result of the target event is determined to be successful, and the first execution result is reported.

[0013] In one possible design, reporting the execution result of the target event based on the updated status of the target event backup data includes:

[0014] If the updated status of the target event backup data is non-existent, then the first execution result is reported;

[0015] An early warning message is generated, which is used to indicate that the backup data construction for the target event is abnormal.

[0016] In one possible design, the completion of the target event execution corresponds to an execution exception of the target event. The step of reporting the execution result of the target event based on the updated status of the target event backup data includes:

[0017] If the execution exception of the target event is a first preset exception, and the status of the updated target event backup data is "existing", then the updated target event backup data is deleted; wherein, the first preset exception is used to describe the first end reporting event of the target event received;

[0018] The second execution result of the target event is determined to be execution failure, and the second execution result is reported.

[0019] In one possible design, reporting the execution result of the target event based on the updated status of the target event backup data includes:

[0020] If the execution exception of the target event is a second preset exception, and the status of the updated backup data of the target event is non-existent, then at least two end-reporting events of the target event received are blocked; wherein, the second preset exception is used to describe at least two end-reporting events of the target event received.

[0021] The third execution result of the target event is determined to be execution failure, and the third execution result is reported.

[0022] In one possible design, reporting the execution result of the target event based on the updated status of the target event backup data includes:

[0023] If the execution exception of the target event is a third preset exception, and the status of the updated target event backup data is "existing", then the updated target event backup data is deleted; wherein, the third preset exception is used to describe that the loading process of the target event has been canceled;

[0024] The fourth execution result corresponding to the target event and the preset reporting time is determined to be execution cancellation, and the fourth execution result is reported.

[0025] In one possible design, after the target event execution exception is a third preset exception, and the updated target event backup data is in the state of "before it existed", it also includes:

[0026] The target event is determined to be executed again, and the preset reporting time is reached.

[0027] Secondly, this disclosure provides a data processing apparatus, including:

[0028] A construction module is used to construct target event backup data in response to an execution request for a target event. The target event backup data is used to describe the loading status when the target event is executed.

[0029] The acquisition module is used to acquire the loading data when the target event is executed, and update the target event backup data based on the loading data;

[0030] The reporting module is used to report the execution result of the target event based on the status of the updated backup data of the target event when the execution of the target event ends.

[0031] In one possible design, the completion of the target event execution corresponds to the successful execution of the target event. The reporting module is specifically used for:

[0032] If the updated target event backup data exists, delete the updated target event backup data;

[0033] The first execution result of the target event is determined to be successful, and the first execution result is reported.

[0034] In one possible design, the reporting module is specifically used for:

[0035] If the updated target event backup data is found to be non-existent, report the first execution result.

[0036] An early warning message is generated, which is used to indicate that the backup data construction for the target event is abnormal.

[0037] In one possible design, the completion of the target event execution corresponds to an exception in the target event execution. The reporting module is specifically used for:

[0038] If the execution exception of the target event is a first preset exception, and the status of the updated target event backup data is "existing", then delete the updated target event backup data; wherein, the first preset exception is used to describe the first end reporting event of the target event received;

[0039] The second execution result of the target event is determined to be execution failure, and the second execution result is reported.

[0040] In one possible design, the reporting module is specifically used for:

[0041] If the execution exception of the target event is a second preset exception, and the status of the updated backup data of the target event is non-existent, at least two end-reporting events of the received target event are blocked; wherein, the second preset exception is used to describe at least two end-reporting events of the received target event;

[0042] The third execution result of the target event is determined to be execution failure, and the third execution result is reported.

[0043] In one possible design, the reporting module is specifically used for:

[0044] If the execution exception of the target event is a third preset exception, and the status of the updated target event backup data is "existing", then the updated target event backup data is deleted; wherein, the third preset exception is used to describe that the loading process of the target event has been canceled;

[0045] The fourth execution result corresponding to the target event and the preset reporting time is determined to be execution cancellation, and the fourth execution result is reported.

[0046] One possible design also includes: defining the module;

[0047] The determination module is used to determine when the target event is executed again and when a preset reporting time has been reached.

[0048] Thirdly, this disclosure provides an electronic device, including: a memory and a processor; the memory is used to store program instructions; the processor is used to invoke the program instructions in the memory to cause the electronic device to perform the data processing method in the first aspect and any possible design of the first aspect.

[0049] Fourthly, this disclosure provides a computer storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the data processing method of the first aspect and any possible design of the first aspect.

[0050] Fifthly, this disclosure provides a computer program product that, when run on a computer, causes the computer to perform the data processing method of the first aspect and any possible design of the first aspect.

[0051] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0052] The data processing method, apparatus, electronic device, medium, and product provided in this disclosure, in response to the execution request of a target event, construct a target event backup data as real-time recording data during the execution of the target event. The target event backup data can be used to describe the loading state of the target execution, obtain the loading data of the target event, update the target event backup data, and report the execution result of the target event based on the status of the updated target event backup data when the execution of the target event ends. Thus, the execution result of the event can be reported in a timely manner during the event execution process, which facilitates accurate knowledge of the data during the event execution process. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0054] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is a schematic flowchart of a data processing method provided in an embodiment of this disclosure;

[0056] Figure 2 This is a flowchart illustrating another data processing method provided in an embodiment of this disclosure;

[0057] Figure 3 This is an interactive schematic diagram of application startup provided in an embodiment of this disclosure;

[0058] Figure 4 This is a schematic diagram of the structure of a data processing device provided in an embodiment of the present disclosure. Detailed Implementation

[0059] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0060] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.

[0061] For example, this disclosure provides a data processing method, apparatus, electronic device, medium, and product that, in response to an execution request for a target event, constructs a target event backup data as real-time recording data during the execution of the target event. The target event backup data can be used to describe the loading state of the target execution, acquire the loading data of the target event, update the target event backup data, and, at the end of the target event execution, report the execution result of the target event based on the updated state of the target event backup data. Thus, the execution result of the event can be reported in a timely manner during the event execution process, facilitating accurate knowledge of the data during the event execution process.

[0062] The data processing method disclosed herein is executed by a client installed in an electronic device. The electronic device may be a tablet computer, mobile phone, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), smart TV, smart screen, high-definition TV, 4K TV, smart speaker, smart projector, etc. This disclosure does not impose any restrictions on the specific type of electronic device.

[0063] This disclosure does not limit the type of operating system used in electronic devices. Examples include Android, Linux, Windows, and iOS.

[0064] Please see Figure 1 , Figure 1 This is a flowchart illustrating a data processing method provided in an embodiment of this disclosure. Figure 1 As shown, the data processing method provided in this disclosure may include:

[0065] S110. In response to the execution request of the target event, construct backup data for the target event.

[0066] The target event backup data can be used to describe the loading status when the target event is executed. The loading status of the target event can include: loading successful, loading failed, and loading canceled.

[0067] Among them, the target event backup data can serve as a backup of the target event if the process terminates abnormally during the execution and loading process.

[0068] Specifically, target events may include target applications and target files, where target files may be a type of file with a large amount of data.

[0069] Accordingly, the execution of the target event may include: launching the target application and downloading the target file; the execution request of the target event may include: a launch request for the target application and a download request for the target file.

[0070] The target application can be a type of program with a long-running process.

[0071] For example, the target application could be a mini-game program. Specifically, the loading process of a mini-game program could include: requesting mini-game entity data, downloading mini-game resource packages, and preparing the engine rendering environment.

[0072] It should be noted that the loading process of the target application may include multiple processes loading in parallel.

[0073] Based on the above examples, when a mini-game starts, the download of the mini-game resource package and the preparation of the engine rendering environment can be loaded in parallel. For example, the first thread can be used to load the download of the mini-game resource package, while the second thread can be used to load the preparation of the engine rendering environment.

[0074] S120. Obtain the loading data when the target event is executed, and update the target event backup data based on the loading data.

[0075] Among them, the loaded data can be the runtime data generated during the execution of the target event. For example, when the target event is application startup, the loaded data can be the data required to load the startup process when the application starts. When the target event is file download, the loaded data can be the data obtained / generated during the file download process, which can be used to indicate the file download progress.

[0076] During the loading and execution of the target event, a loading and execution progress can be displayed, such as by loading a progress bar. The loading progress bar can include multiple loading progress nodes, and the loading data of the target event can be the sum of the data of the loaded progress nodes.

[0077] For example, if the loading progress bar includes 100 loading progress nodes, and the loading is currently completed at the 50th loading progress node, then the loading data of the target event can correspond to the sum of the data from the 1st loading progress node to the 50th loading progress node.

[0078] S130. When the target event execution ends, report the execution result of the target event based on the status of the updated target event backup data.

[0079] Among them, the completion of the target event execution can correspond to the target event execution success, target event execution failure, target event execution exception, etc.

[0080] Specifically, it can be determined whether the loading and execution of the target event is abnormal based on the target event backup data, or it can be determined whether the loading and execution of the target event is completed / ended based on the target event backup data.

[0081] Based on the above examples, if the loading progress bar includes 100 loading progress nodes, and the program exits when the target event reaches the 90th loading progress node, or if the 90th loading progress node is not completed for a long time, then the execution of the target event can be considered abnormal.

[0082] The status of the updated target event backup data can include: existence or non-existence.

[0083] Specifically, after constructing the target event backup data, the constructed target event backup data can be stored in the cache area for target event backup data update processing. After determining whether the target event loading is abnormal / loading execution is complete, check whether there is still target event backup data in the cache area.

[0084] The execution result of the target event may include, but is not limited to: execution success, execution failure, and execution cancellation.

[0085] Accordingly, when the execution of the target event is to start the target application, the execution result of the target event may include, but is not limited to: successful startup, failed startup, and canceled startup; when the execution of the target event is to download the target file, the execution result of the target event may include, but is not limited to: successful download, failed download, and canceled download.

[0086] Based on the examples above, successful execution means loading all progress nodes, failure means loading some progress nodes but some progress nodes are still not loaded successfully, and cancellation means exiting the target application during the loading process.

[0087] The data processing method provided in this disclosure constructs a target event backup data in response to the execution request of the target event, which serves as real-time recording data during the execution of the target event. The target event backup data can be used to describe the loading status of the target execution, obtain the loading data of the target event, update the target event backup data, and report the execution result of the target event based on the status of the updated target event backup data when the execution of the target event ends. Thus, the execution result of the event can be reported in a timely manner during the event execution process, making it easier to accurately obtain the data during the event execution process.

[0088] Figure 2This is a flowchart illustrating another data processing method provided in this embodiment. This embodiment is based on the above embodiment, wherein the completion of the target event execution corresponds to a target event execution exception, and the target event execution exception can be accurately determined. When the target event execution exception is determined to be a first preset exception, the first preset exception can be used to describe the first completion reporting event of the received target event; a possible implementation of S130 is as follows:

[0089] S1301. If the updated target event backup data exists, delete the updated target event backup data.

[0090] The updated target event backup data can record the loading progress of the target event in real time. After receiving the first end report of the target event, the execution result of the target event can be reported by checking whether there is updated target event backup data.

[0091] S1302. Determine that the second execution result of the target event is execution failure, and report the second execution result.

[0092] After determining that the target event execution is abnormal based on the loaded data, the second execution result of the target event can be determined to be execution failure, that is, the loading was not successful. After deleting the updated target event backup data, the reporting result of the target event can be reported.

[0093] Therefore, when an error occurs during the execution of the target event, the execution and loading status of the target event can be understood in a timely manner.

[0094] Based on the description of the above embodiments, optionally, the target event execution exception may also include the following types.

[0095] In some embodiments, the target event execution exception may be a second preset exception, wherein the second preset exception may be used to describe at least two end-reporting events received from the target event.

[0096] For example, if a pause occurs during the execution of a target event, and at least two execution loading processes of the target event are loaded in parallel, a reporting event will be executed once when the first execution loading process pauses, and a reporting event will also be executed once when the second execution loading process pauses.

[0097] Based on the above examples, the execution of the target event is that when the mini-game starts, the download of the mini-game resource package and the preparation of the engine rendering environment can be carried out in parallel. For example, the first thread loads the download of the mini-game resource package, while the second thread loads the engine rendering environment preparation. If the download of the mini-game resource package fails, the first reporting event is executed. If the engine rendering environment preparation fails, the second reporting event is executed.

[0098] Based on the status of the updated target event backup data, report the execution results of the target event, including:

[0099] If the updated target event backup data is not found, then at least two end-reporting events for the received target event will be blocked.

[0100] The third execution result of the target event is determined to be execution failure, and the third execution result is reported.

[0101] If at least two end-reporting events are received for the target event, it indicates that there is a parallel execution loading process for the target event. If the first execution loading process has failed and the reporting event has been executed, then after the first execution loading fails, there is no need to execute the reporting event again.

[0102] This avoids multiple loading failures when the same part of the event fails to load, preventing redundant error reports from ending the task in the data warehouse.

[0103] Based on the above examples, when a mini-game starts, the download of the mini-game resource package and the preparation of the engine rendering environment can be loaded in parallel. For example, the first thread can be used to load the download of the mini-game resource package, while the second thread can be used to load the engine rendering environment preparation. If the download of the mini-game resource package fails, the first reporting event is executed, and the updated target application loading data (the backup data of the target event when the target event is the target application) is deleted. If the engine rendering environment preparation fails to load, the second reporting event is executed. At this time, the second reporting event is determined to be an abnormal reporting event and can be blocked.

[0104] In other embodiments, the target event loading exception may be a third preset exception, which is used to describe that the execution process of the target event has been canceled.

[0105] In this context, "the execution process of the target event has been cancelled" means that the execution task is cancelled while the target event is in progress and before it is completed.

[0106] Taking the execution of the target event as the startup of the target application as an example, during the normal loading process of the target application, if the user manually cancels the application loading process in the task list, the process is terminated and the relevant code will not be executed.

[0107] Based on the above example, when a mini-game starts, the loading requirements are: loading mini-game entity data requests, downloading mini-game resource packages, and preparing the engine rendering environment. After loading the mini-game entity data requests, the download of mini-game resource packages and the preparation of the engine rendering environment continue. However, before the download of mini-game resource packages and the preparation of the engine rendering environment are completed, the user cancels the loading process of the target application in the task list.

[0108] The preset reporting time can be the period during which the target event is re-executed but the relevant loading process has not yet been executed.

[0109] Based on the status of the updated target event backup data, report the startup result of the target application, including:

[0110] If the target event execution exception is the third preset exception, and the status of the updated target event backup data is "existing", then delete the updated target event backup data; where the third preset exception is used to describe that the loading process of the target event has been canceled.

[0111] The fourth execution result corresponding to the target event and the preset reporting time is determined to be execution cancellation, and the fourth execution result is reported.

[0112] If the updated target event backup data is the target event backup data corresponding to the first execution of the target event and is unrelated to the current execution of the target event, then the updated target event backup data needs to be deleted and the execution canceled, thereby making up for the problem of missing data after the execution loading is completed.

[0113] Additionally, in this embodiment, after the target event execution exception is the third preset exception, and before the updated target event backup data is in a state of "existence", it may also include:

[0114] Determine if the target event is executed again and a preset reporting time has been reached; wherein, the target event is executed again means that the execution event of the target event triggered by the user is received again, and the preset reporting time can be a preset period of time after the user executes the target event again.

[0115] Based on the above example, when a mini-game starts, the loading requirements are: loading mini-game entity data requests, downloading mini-game resource packages, and preparing the engine rendering environment. After loading the mini-game entity data requests, the download of mini-game resource packages and the preparation of the engine rendering environment continue. However, if the user cancels the loading process of the target application in the task list before the download of mini-game resource packages and the preparation of the engine rendering environment are completed, and then the user restarts the target application, the time / process after the completion of the mini-game entity data requests can be used as the preset reporting time.

[0116] Optionally, after determining that the target event has been successfully executed based on the loaded data, the execution result of the target event can be reported according to the status of the updated target event backup data.

[0117] It should be noted that after determining that the target event was successfully executed based on the loaded data, the status of the updated target event backup data can be either present or absent.

[0118] Specifically, based on the status of the updated target event backup data, the execution results of the target event are reported, including:

[0119] If the updated target event backup data exists, then delete the updated target event backup data;

[0120] The first execution result of the target event is determined to be successful, and the first execution result is reported.

[0121] Once the successful execution of the target event is confirmed based on the loaded data, it indicates that the execution task of the target event has been completed normally.

[0122] When the execution of the target event is used as the start of the mini-game (start of the target application), the loading requirements are as follows: loading mini-game entity data requests, downloading mini-game resource packages, and preparing the engine rendering environment. After loading the mini-game entity data requests, the loading of mini-game resource packages and engine rendering environment preparation continues. After loading the mini-game resource packages and engine rendering environment preparation, the loading of engine rendering environment preparation continues. Once the engine rendering environment preparation is completed, it means that the target application has been successfully loaded.

[0123] Specifically, based on the status of the updated target event backup data, the startup result of the target application is reported, including:

[0124] If the updated target event backup data is found to be non-existent, then the first execution result is reported.

[0125] Generate an early warning message, which is used to indicate an anomaly in the construction of backup data for the target event.

[0126] If, after determining that the target event has been successfully executed based on the loaded data, the updated target event backup data is found to be non-existent, it can be considered that the construction / update of the target event backup data is abnormal, and an alarm should be issued to facilitate administrators to be aware of the event execution status in a timely manner.

[0127] Based on the description of the above embodiments, the data processing method of this disclosure, taking the execution of a target event as an example of the startup of a target application, is as follows: Figure 3 As exemplified, specifically, this can be achieved through an application startup module, a data calibration module, and a data reporting module, wherein:

[0128] The application launch module can detect the loading of the target application (such as a mini-game). When the loading of the mini-game is detected, the data calibration module will be used.

[0129] Upon receiving the notification and confirming that loading has begun, the data calibration module constructs a backup of the loading cancellation data (such as the target event backup data mentioned above) and reports the loading start event to the data reporting module. During the loading process of the mini-game, the loading progress bar will be continuously updated, and the testers will also notify the data calibration module to update the created backup data.

[0130] The data reporting module is used to report loading result events, such as loading success, loading failure, loading cancellation, etc.

[0131] Specifically, when the loading process is detected to be finished (loading successful or loading failed), the data calibration module is notified so that it can check whether there is corresponding backup data. If so, the backup data is deleted and the received loading completion notification is sent to the data reporting module for data reporting.

[0132] If a task loading failure occurs (occurring during the parallel loading of multiple processes), and the data calibration module is notified again that the task has ended, the data calibration module will check and find that there is no corresponding backup data. In this case, it will ignore the completion of the loading and not report it to the data reporting module, so as to ensure that there are no redundant erroneous data reports of the task completion in the data warehouse.

[0133] If a user swipes off a mini-game from the recent tasks list while it is loading, the process will be killed and the code will not be executed, resulting in missing loading completion data. However, since the backup data has been written to the storage space, it will be reported the next time the user launches the mini-game to make up for the missing loading completion data.

[0134] Figure 4 This is a schematic diagram of the structure of a data processing device provided in this disclosure, such as... Figure 4 As shown, the data processing device 400 of this embodiment includes: a construction module 410, an acquisition module 420, and a reporting module 430, wherein:

[0135] The construction module 410 is used to construct target event backup data in response to the execution request of the target event, wherein the target event backup data is used to describe the loading state when the target event is executed;

[0136] The acquisition module 420 is used to acquire the loading data when the target event is executed, and update the target event backup data based on the loading data;

[0137] The reporting module 430 is used to report the execution result of the target event based on the status of the updated target event backup data when the target event execution ends.

[0138] In this embodiment, the completion of the target event execution corresponds to the successful execution of the target event. The reporting module 430 is specifically used for:

[0139] If the updated target event backup data exists, delete the updated target event backup data;

[0140] The first execution result of the target event is determined to be successful, and the first execution result is reported.

[0141] In this embodiment, the reporting module 430 is specifically used for:

[0142] If the updated target event backup data is found to be non-existent, report the first execution result.

[0143] An early warning message is generated, which is used to indicate that the backup data construction for the target event is abnormal.

[0144] In this embodiment, the completion of the target event execution corresponds to an exception in the target event execution. The reporting module 430 is specifically used for:

[0145] If the execution exception of the target event is a first preset exception, and the status of the updated target event backup data is "existing", then delete the updated target event backup data; wherein, the first preset exception is used to describe the first end reporting event of the target event received;

[0146] The second execution result of the target event is determined to be execution failure, and the second execution result is reported.

[0147] In this embodiment, the reporting module 430 is specifically used for:

[0148] If the execution exception of the target event is a second preset exception, and the status of the updated backup data of the target event is non-existent, at least two end-reporting events of the received target event are blocked; wherein, the second preset exception is used to describe at least two end-reporting events of the received target event;

[0149] The third execution result of the target event is determined to be execution failure, and the third execution result is reported.

[0150] In this embodiment, the reporting module 430 is specifically used for:

[0151] If the execution exception of the target event is a third preset exception, and the status of the updated target event backup data is "existing", then the updated target event backup data is deleted; wherein, the third preset exception is used to describe that the loading process of the target event has been canceled;

[0152] The fourth execution result corresponding to the target event and the preset reporting time is determined to be execution cancellation, and the fourth execution result is reported.

[0153] In this embodiment, the device further includes: a determining module;

[0154] The determination module is used to determine when the target event is executed again and when a preset reporting time has been reached.

[0155] The data processing apparatus provided in this disclosure can execute the above-described method embodiments. For its specific implementation principles and technical effects, please refer to the above-described method embodiments. This disclosure will not repeat them here.

[0156] For example, this disclosure provides an electronic device including: one or more processors; a memory; and one or more computer programs; wherein the one or more computer programs are stored in the memory; and when the one or more processors execute the one or more computer programs, the electronic device causes the electronic device to implement the data processing method of the foregoing embodiments.

[0157] For example, this disclosure provides a chip system applied to an electronic device including a memory and a sensor; the chip system includes: a processor; when the processor executes the data processing method of the preceding embodiments.

[0158] For example, this disclosure provides a computer-readable storage medium having a computer program stored thereon, the computer program being processed by a processor to cause an electronic device to implement the data processing method of the preceding embodiments.

[0159] For example, this disclosure provides a computer program product that, when run on a computer, causes the computer to execute the data processing method described in the preceding embodiments.

[0160] In the above embodiments, all or part of the functionality can be implemented by software, hardware, or a combination of software and hardware. When implemented using software, it can be implemented wholly or partially in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this disclosure is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0161] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0162] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data processing method, characterized by, The method comprises the following steps: in response to an execution request of a target event, constructing target event backup data used to describe a loading state when the target event is executed; obtaining loading data when the target event is executed, and updating the target event backup data based on the loading data; when the target event execution ends, reporting an execution result of the target event based on a state of the updated target event backup data; the target event execution end corresponds to target event execution exception, and the reporting of the execution result of the target event based on the state of the updated target event backup data comprises: if the target event execution exception is a first preset exception, and the state of the updated target event backup data is existing, the updated target event backup data is deleted; wherein the first preset exception is used to describe that a first end reporting event of the target event is received; determining that a second execution result of the target event is an execution failure, and reporting the second execution result; the reporting of the execution result of the target event based on the state of the updated target event backup data comprises: if the target event execution exception is a second preset exception, and the state of the updated target event backup data is non-existing, at least two end reporting events of the target event received are shielded; wherein the second preset exception is used to describe that at least two end reporting events of the target event are received; determining that a third execution result of the target event is an execution failure, and reporting the third execution result; the reporting of the execution result of the target event based on the state of the updated target event backup data comprises: if the target event execution exception is a third preset exception, and the state of the updated target event backup data is existing, the updated target event backup data is deleted; wherein the third preset exception is used to describe that a loading process of the target event has been cancelled; determining that a fourth execution result of the target event corresponding to a preset reporting time is an execution cancellation, and reporting the fourth execution result.

2. The method of claim 1, wherein, the target event execution end corresponds to target event execution success, and the reporting of the execution result of the target event based on the state of the updated target event backup data comprises: if the state of the updated target event backup data is existing, the updated target event backup data is deleted; determining that a first execution result of the target event is an execution success, and reporting the first execution result.

3. The method of claim 2, wherein, the reporting of the execution result of the target event based on the state of the updated target event backup data comprises: if the state of the updated target event backup data is non-existing, the first execution result is reported; generating a warning information, the warning information is used to prompt a target event backup data construction exception.

4. The method of claim 1, wherein, after the target event execution exception is the third preset exception, and before the state of the updated target event backup data is existing, the method further comprises the following steps: determining that the target event is executed again, and reaches a preset reporting time.

5. A data processing apparatus, characterized by, The method comprises the following steps: The constructing module is configured to construct target event backup data in response to an execution request of a target event, the target event backup data being used to describe a loading state when the target event is executed; The obtaining module is configured to obtain loading data when the target event is executed, and update the target event backup data based on the loading data; The reporting module is configured to report an execution result of the target event based on a state of the updated target event backup data when execution of the target event ends; The target event execution end corresponds to target event execution exception, and the reporting module is specifically configured to: if the target event execution exception is a first preset exception and the state of the updated target event backup data is existence, delete the updated target event backup data; wherein the first preset exception is used to describe that a first end reporting event of the target event is received; determine a second execution result of the target event as execution failure, and report the second execution result; If the target event execution exception is a second preset exception and the state of the updated target event backup data is nonexistence, shield at least two end reporting events of the target event that are received; wherein the second preset exception is used to describe that at least two end reporting events of the target event are received; determine a third execution result of the target event as execution failure, and report the third execution result; If the target event execution exception is a third preset exception and the state of the updated target event backup data is existence, delete the updated target event backup data; wherein the third preset exception is used to describe that a loading process of the target event is cancelled; determine a fourth execution result of the target event corresponding to a preset reporting time as execution cancellation, and report the fourth execution result.

6. An electronic device, comprising: One or more processors; Memory; And one or more computer programs; wherein the one or more computer programs are stored in the memory; characterized in that the one or more processors, when executing the one or more computer programs, cause the electronic device to implement the data processing method of any one of claims 1-4.

7. A computer storage medium, characterized in that Computer instructions are included, when the computer instructions run on an electronic device, cause the electronic device to execute the data processing method of any one of claims 1-4.

Images