Data reporting method and apparatus, electronic device, and storage medium

Abstract

The present disclosure relates to a data reporting method and device, electronic equipment and storage medium, belonging to the field of financial technology, information technology and data processing technology. The method comprises: abstracting a reporting action to obtain a candidate code, and binding the reporting action with the candidate code, so that the user does not need to write reporting code when arranging the reporting workflow, simplifying the user operation, reducing the arrangement difficulty of the reporting workflow, improving the arrangement efficiency of the reporting workflow. In addition, based on the type of arrangement operation and the operation information of the arrangement operation, the reporting action contained in the candidate workflow is determined to generate the candidate workflow, the target workflow is determined from the workflow library, and the target workflow is configured based on the configuration information of the target reporting event to generate a reporting instance. The automatic generation of the reporting workflow and the reporting instance is realized, and the reporting instance is executed through the scheduling application program to process the target reporting event, thereby improving the data reporting efficiency.

Description

Technical Field

[0001] This disclosure relates to the fields of financial technology, information technology industry, and data processing technology, and in particular to a data reporting method, apparatus, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] Currently, with the continuous development of internet technology, workflow has been widely used due to its advantages such as high degree of office automation and high efficiency. However, most related technologies still rely on manual data reporting, which is problematic, especially in scenarios with large amounts of data, resulting in repetitive operations, long processing times, and low data reporting efficiency. Summary of the Invention

[0003] This disclosure provides a data reporting method, apparatus, electronic device, computer-readable storage medium, and computer program product to at least solve the problem of low data reporting efficiency in related technologies. The technical solution of this disclosure is as follows:

[0004] According to a first aspect of the present disclosure, a data reporting method is provided, comprising: abstracting a reporting action to obtain candidate code, and binding the reporting action to the candidate code; in response to detecting an orchestration operation for a candidate workflow, determining the reporting action contained in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation, generating the candidate workflow, and adding the candidate workflow to a workflow library; determining a target workflow for a target reporting event from the workflow library, configuring the target workflow based on the configuration information of the target reporting event, and generating a reporting instance of the target reporting event; importing the reporting instance into a scheduling application, and parsing the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, as target code to be executed; and executing the target code through the scheduling application to execute the reporting instance to process the target reporting event.

[0005] According to a second aspect of the present disclosure, a data reporting apparatus is provided, comprising: an abstraction module configured to abstract reporting actions to obtain candidate codes, and bind the reporting actions to the candidate codes; an orchestration module configured to, in response to detecting an orchestration operation for a candidate workflow, determine the reporting actions included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation, generate the candidate workflow, and add the candidate workflow to a workflow library; a configuration module configured to determine a target workflow for a target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event; a parsing module configured to import the reporting instance into a scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate codes bound to the reporting actions included in the reporting instance, as target codes to be executed; and an execution module configured to execute the target codes through the scheduling application to execute the reporting instance and process the target reporting event.

[0006] According to a third aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the data reporting method as described in the first aspect above.

[0007] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided that, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the data reporting method as described in the first aspect above.

[0008] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the data reporting method as described in the first aspect above.

[0009] The technical solutions provided by the embodiments of this disclosure offer at least the following advantages: By abstracting reporting actions to obtain candidate codes and binding reporting actions with candidate codes, users do not need to write reporting code when orchestrating reporting workflows, simplifying user operations, reducing the difficulty of orchestrating reporting workflows, and improving the orchestration efficiency of reporting workflows. Furthermore, by considering the type and operation information of orchestration operations, the reporting actions included in the candidate workflows can be determined to generate candidate workflows, which are then added to the workflow library, enabling automatic reporting workflow execution. In addition, the target workflow for the target reporting event is determined from the workflow library, and the target workflow is automatically configured taking into account the configuration information of the target reporting event. This generates a reporting instance for the target reporting event, enabling automatic generation of the reporting instance. The reporting instance is then imported into the scheduling application, which parses the reporting instance to obtain the candidate code bound to the reporting action contained in the reporting instance. This candidate code is then used as the target code to be executed. The scheduling application executes the target code to execute the reporting instance, thus automating data reporting and improving data reporting efficiency.

[0010] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0012] Figure 1 This is a flowchart illustrating the data reporting method according to the first embodiment of this disclosure.

[0013] Figure 2 This is a flowchart illustrating the data reporting method according to the second embodiment of this disclosure.

[0014] Figure 3 This is a flowchart illustrating the data reporting method according to the third embodiment of this disclosure.

[0015] Figure 4 This is a schematic flowchart of a data reporting method according to the fourth embodiment of this disclosure.

[0016] Figure 5 This is a block diagram of a data reporting apparatus according to a first embodiment of the present disclosure.

[0017] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0018] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0019] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0020] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, data stored, data displayed, etc.) and signals involved in this disclosure are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0021] It should be noted that the acquisition, transmission, storage, use, and processing of data in this disclosure comply with the relevant provisions of laws and regulations. In the embodiments of this disclosure, certain software, components, models, and other existing solutions in the industry may be mentioned. These should be considered as exemplary and are intended only to illustrate the feasibility of implementing the technical solution of this disclosure. However, they do not mean that the applicant has used or necessarily used the solution.

[0022] Figure 1 This is a flowchart illustrating the data reporting method according to the first embodiment of this disclosure.

[0023] like Figure 1 As shown, the data reporting method of the first embodiment of this disclosure includes the following steps:

[0024] S101, abstract the reporting action to obtain candidate code, and bind the reporting action to the candidate code.

[0025] It should be noted that the data reporting method of this disclosure is executed by an electronic device, which may include mobile phones, laptops, in-vehicle devices, smart home appliances, etc. The data reporting method of this disclosure can be executed by the data reporting device of this disclosure, which can be configured in any electronic device to execute the data reporting method of this disclosure.

[0026] It should be noted that there are no strict limitations on the reporting actions. These actions can include data collection, data parsing, data processing, data encryption, data review, data packaging, data compression, and data transmission. Data parsing can include parsing data using delimiters, extracting tags or key-value pairs, text parsing based on NLP (Natural Language Processing), and structured processing. Data processing can include data cleaning, data transformation, feature engineering, data aggregation, data fragmentation, and quality checks.

[0027] It should be noted that abstracting the reporting action to obtain candidate code refers to converting the reporting action into an executable script. This can be achieved using any abstraction method from related technologies, without much limitation here. For example, the name, execution method, formal parameters, and code type of the candidate code can be configured.

[0028] It's understandable that binding a reporting action to a candidate code means binding a specific reporting action to a candidate code abstracted from that action. Different reporting actions may be bound to different candidate codes.

[0029] In one implementation, after obtaining the candidate code, the method further includes deploying the candidate code to local storage space.

[0030] For example, the reporting action 1 can be abstracted to obtain candidate code 1, and the reporting action 1 can be bound to candidate code 1, and candidate code 1 can be deployed to the local storage space.

[0031] For example, the reporting action 2 can be abstracted to obtain candidate code 2, and the reporting action 2 can be bound to candidate code 2, and candidate code 2 can be deployed to the local storage space.

[0032] S102, in response to detecting an orchestration operation for a candidate workflow, based on the type of the orchestration operation and the operation information of the orchestration operation, determine the reporting actions contained in the candidate workflow to generate a candidate workflow and add the candidate workflow to the workflow library.

[0033] It should be noted that candidate workflows are workflows used for data reporting (hereinafter referred to as reporting workflows). The terms workflow, process flow, etc., are interchangeable. A candidate workflow contains at least one reporting action. There are no strict restrictions on the type of orchestration operation; it may include selection operations, data entry operations, etc. Selection operations may include click operations, drag-and-drop operations, etc. The workflow library includes multiple candidate workflows.

[0034] In one implementation, the method further includes controlling the display of multiple candidate options on an interactive page during the orchestration of candidate workflows, wherein the candidate options are used to characterize reporting actions.

[0035] Based on the type and operation information of the orchestration operation, the reporting actions included in the candidate workflow are determined. This includes actions responding to the orchestration operation type as selection operations, where the candidate selections chosen by the selection operation are taken as target selections, and the reporting actions corresponding to the target selections are added to the reporting actions included in the candidate workflow. Thus, user-selected reporting actions can be added to the reporting actions included in the reporting workflow, enabling visualized and personalized orchestration of reporting workflows.

[0036] Understandably, users can select from candidate options on the interactive page, without much restriction on the shape or other information of the candidate options. For example, different types of reporting actions may correspond to different shapes of the candidate options. There are also no strict restrictions on how the candidate options are displayed; they can include pop-ups, notification bars, floating windows, etc. Multiple candidate options include the target selection.

[0037] For example, the interactive page can be controlled to display start action component, end action component, and arrow component, etc. The start action component is used to indicate that the candidate workflow has started execution, the end action component is used to indicate that the candidate workflow has ended execution, and the arrow component is used to indicate whether the reporting action has been executed successfully. The start action component and the end action component are both elliptical, the candidate selection is a rectangle, the arrow component used to indicate that the reporting action has been executed successfully is a solid arrow, and the arrow component used to indicate that the reporting action has failed is a dashed arrow.

[0038] For example, during the orchestration of candidate workflow A, candidate options 1 to 10 can be displayed on the interactive interface. Candidate option k is used to represent the reporting action k, where k is a positive integer not greater than 10.

[0039] In response to the detection of a selection operation for candidate workflow A, candidate selection items 1 and 3 selected by the selection operation are taken as target selection items, and reporting action 1 corresponding to candidate selection item 1 and reporting action 3 corresponding to candidate selection item 3 are added to the reporting actions contained in candidate workflow A.

[0040] In one implementation, the method further includes generating a candidate workflow based on the reporting actions contained in the candidate workflow, the dependencies between the reporting actions contained in the candidate workflow, and the name of the candidate workflow. The dependencies may include serial relationships, parallel relationships, etc.

[0041] S103, determine the target workflow of the target reporting event from the workflow library, configure the target workflow based on the configuration information of the target reporting event, and generate a reporting instance of the target reporting event.

[0042] It should be noted that the workflow library includes the target workflow.

[0043] In one implementation, determining the target workflow for a target reporting event from a workflow library includes, in response to detecting a selection operation for a candidate workflow, selecting the candidate workflow chosen by the selection operation as the target workflow. Thus, a user-selected candidate workflow can be used as the target workflow for a given reporting event, enabling personalized selection of reporting workflows.

[0044] In one implementation, determining the target workflow for a target reporting event from a workflow library includes obtaining the target reporting scenario for the target reporting event and the candidate reporting scenarios for each of multiple candidate workflows in the workflow library. The similarity between the target reporting scenario and the candidate reporting scenarios is then calculated, and based on this similarity, the target workflow is determined from the workflow library. Therefore, considering the similarity between the target reporting scenario and the candidate reporting scenarios when determining the target workflow from the workflow library helps to obtain a target workflow that matches the target reporting scenario, thus improving the success rate of data reporting.

[0045] It should be noted that there are no strict limitations on the reporting scenario. For example, it may include the content to be reported, the field to which the data to be reported belongs, and the type of reporting organization (such as the initiator and the responder). The terms "initiator" and "sender" are interchangeable, as are "responder" and "receiver".

[0046] In some cases, the target workflow is determined from the workflow library based on similarity, including selecting the candidate workflow with the highest similarity as the target workflow.

[0047] In some cases, the target workflow is determined from the workflow library based on similarity, including obtaining the target score of the candidate workflows based on similarity, and taking the candidate workflow with the highest target score as the target workflow.

[0048] For example, a target score for a candidate workflow is obtained based on similarity, including obtaining the target score based on both similarity and the initial score of the candidate workflow. For instance, candidate workflows can be pre-scored to obtain initial scores for each of the multiple candidate workflows. Alternatively, the target score can be obtained by weighted summation of the similarity and the initial scores.

[0049] It should be noted that the configuration information for reporting events is not subject to many restrictions. For example, it may include the reporting content, the reporting organization (e.g., the initiator and responder), the reporting node, the strategy for identifying whether to re-report, and the strategy for identifying whether the reporting action was successfully executed. The configuration information may differ for different reporting events.

[0050] For example, the reporting content may include the type, format, reporting method, and data source of the data to be reported.

[0051] For example, a strategy for identifying whether to retransmit may include determining to retransmit in response to receiving a first indication message (such as a retransmission flag) indicating retransmission, and determining not to retransmit in response to not receiving the first indication message.

[0052] For example, a strategy for identifying whether a reporting action has been successfully executed may include determining that the reporting action has been successfully executed in response to receiving a second indication message (such as a success return code) indicating that the reporting action has been successfully executed, and determining that the reporting action has failed in response to not receiving the second indication message.

[0053] For example, a strategy for identifying whether a reporting action was executed successfully may include determining that the reporting action failed in response to receiving a third indication message (such as a failure return code) indicating that the reporting action failed, and determining that the reporting action was executed successfully in response to not receiving the third indication message.

[0054] In the embodiments of this disclosure, the target workflow is configured based on the configuration information of the target reporting event, and a reporting instance of the target reporting event is generated, including the following possible implementation methods:

[0055] Method 1: Identify whether there is any overlap in the configuration information of each of the N target reporting events, where N is a positive integer greater than 1. In response to the overlap in the configuration information of each of the N target reporting events, perform batch configuration on the target workflow of each of the N target reporting events based on the overlap information, and generate reporting instances of each of the N target reporting events.

[0056] Therefore, when there is overlap in the configuration information of multiple reporting events, the reporting workflow of each reporting event can be configured in batches based on the overlap information to generate multiple reporting instances, thereby improving the configuration efficiency of the reporting workflow and thus improving the generation efficiency of the reporting instances.

[0057] For example, identify whether there is any overlap in the configuration information of each of the target reporting events 1 to 10. In response to the consistency of the reporting content and reporting agency of each of the target reporting events 1 to 10, perform batch configuration of the target workflow of each of the target reporting events 1 to 10 based on the above reporting content and reporting agency, and generate reporting instances of each of the target reporting events 1 to 10.

[0058] Method 2: Determine the reporting content and reporting agency of the target reporting event from the configuration information of the target reporting event, bind the target workflow to the reporting content and reporting agency of the target reporting event respectively, and generate a reporting instance.

[0059] Therefore, the reporting workflow can be bound to the reporting content and the reporting organization of the reporting event to generate reporting instances.

[0060] It is understandable that different reporting workflows may be associated with different reporting content and reporting agencies.

[0061] Method 3: Obtain the candidate code bound to the reporting action contained in the target workflow as the target code to be executed. Based on the configuration information of the target reporting event, configure the actual parameters of the target code and generate a reporting instance.

[0062] Therefore, the actual parameters of the reporting code can be configured by taking into account the configuration information of the reporting event in order to generate a reporting instance.

[0063] S104. Import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed.

[0064] S105, by scheduling the application to execute target code to execute reporting instances to process target reporting events.

[0065] It should be noted that multiple candidate codes include target code, and the number of target codes must be at least one. The scheduling application refers to the application used to schedule workflows; there are no strict limitations on the scheduling application, which may include batch processing programs, for example.

[0066] For example, there is a binding relationship between the reporting action p and the candidate code p, where p is a positive integer not greater than 10.

[0067] The target workflow for target reporting event 1 is determined from the workflow library as candidate workflow A. Based on the configuration information of target reporting event 1, candidate workflow A is configured to generate reporting instance B for target reporting event 1.

[0068] Import reporting instance B into the scheduling application, and parse reporting instance B through the scheduling application to obtain reporting actions 1 and 3 contained in reporting instance B. Obtain candidate code 1 bound to reporting action 1 and candidate code 3 bound to reporting action 3 as target code to be executed.

[0069] The application is scheduled to execute candidate codes 1 and 3 to execute reporting instance B in order to process target reporting event 1.

[0070] In summary, according to the data reporting method provided in this disclosure, reporting actions are abstracted to obtain candidate codes, and the reporting actions are bound to the candidate codes. This eliminates the need for users to write reporting code when orchestrating reporting workflows, simplifying user operations, reducing the difficulty of orchestrating reporting workflows, and improving the orchestration efficiency. Furthermore, by considering the type and operation information of the orchestration operation, the reporting actions included in the candidate workflow can be determined to generate a candidate workflow, which is then added to the workflow library, enabling automatic generation of reporting workflows. Furthermore, by identifying the target workflow for the target reporting event from the workflow library and taking into account the configuration information of the target reporting event, the target workflow is automatically configured to generate a reporting instance for the target reporting event. This enables the automatic generation of reporting instances. The reporting instance is then imported into the scheduling application, which parses the reporting instance to obtain the candidate code bound to the reporting action contained in the reporting instance. This candidate code serves as the target code to be executed. The scheduling application executes the target code to execute the reporting instance, thereby automating data reporting and improving data reporting efficiency.

[0071] Figure 2 This is a flowchart illustrating the data reporting method according to the second embodiment of this disclosure.

[0072] like Figure 2 As shown, the data reporting method of the second embodiment of this disclosure includes the following steps:

[0073] S201, abstract the reporting action to obtain candidate codes, and bind the reporting action to the candidate codes.

[0074] For details regarding step S201, please refer to the above embodiments, which will not be repeated here.

[0075] S202, in response to detecting an orchestration operation for a candidate workflow, and in response to the type of orchestration operation being a first entry operation for a reporting action, the reporting action entered by the first entry operation is obtained.

[0076] S203: Add the entered reporting action to the reporting actions included in the candidate workflow to generate a candidate workflow, and add the candidate workflow to the workflow library.

[0077] S204 abstracts the entered reporting action to obtain the new candidate code, and binds the entered reporting action to the new candidate code.

[0078] The relevant content of step S204 can be referred to the relevant content of step S101, and will not be repeated here.

[0079] S205, obtain the candidate code entered in the first input operation, and bind the input reporting action to the entered candidate code.

[0080] Understandably, users can perform the initial input for the reporting action on the interactive page. For example, users can also enter candidate codes when entering the reporting action.

[0081] For example, during the orchestration of candidate workflow A, an input box can be displayed on the interactive interface. In response to the detection of the first input operation for the reporting action, the reporting actions 11 and 12 entered by the first input operation can be obtained, and the reporting actions 11 and 12 can be added to the reporting actions contained in candidate workflow A.

[0082] The reporting action 11 can be abstracted to obtain candidate code 11, and the reporting action 11 can be bound to the candidate code 11, and the candidate code 11 can be deployed to the local storage space.

[0083] The candidate code 12 entered in the first input operation can be obtained, and the candidate code 12 can be bound to the candidate code 12 and deployed to the local storage space.

[0084] S206. Determine the target workflow for the target reporting event from the workflow library, configure the target workflow based on the configuration information of the target reporting event, and generate a reporting instance for the target reporting event.

[0085] S207, import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed.

[0086] S208, by scheduling the application to execute target code to execute reporting instances to process target reporting events.

[0087] For details regarding steps S206-S208, please refer to the above embodiments; they will not be repeated here.

[0088] In summary, according to the data reporting method provided in the embodiments of this disclosure, in response to a first input operation of the type of orchestration operation being a reporting action, the reporting action entered in the first input operation is obtained, and the entered reporting action is added to the reporting actions included in the candidate workflow. This allows user-entered reporting actions to be added to the reporting actions included in the reporting workflow, enabling personalized orchestration of the reporting workflow. In addition, the entered reporting action is abstracted to obtain a new candidate code, and the entered reporting action is bound to the new candidate code. And / or, the candidate code entered in the first input operation is obtained, and the entered reporting action is bound to the entered candidate code. This allows the candidate code bound to the entered reporting action to be automatically obtained through step abstraction. And / or, the candidate code entered by the user can be used as the candidate code bound to the entered reporting action, enabling personalized configuration of the candidate code.

[0089] Figure 3 This is a flowchart illustrating the data reporting method according to the third embodiment of this disclosure.

[0090] like Figure 3 As shown, the data reporting method of the third embodiment of this disclosure includes the following steps:

[0091] S301 abstracts the reporting action to obtain candidate codes and binds the reporting action to the candidate codes.

[0092] For details regarding step S301, please refer to the above embodiments, which will not be repeated here.

[0093] S302, in response to detecting an orchestration operation for a candidate workflow, and in response to the type of orchestration operation being a second entry operation for orchestration requirements, the orchestration requirements of the candidate workflow entered by the second entry operation are obtained.

[0094] Understandably, users can perform a second entry operation on the interactive page to specify their orchestration needs. There are no strict limitations on these orchestration needs; they can include, for example, the content to be submitted, the frequency of submission, scheduled submission, the domain of the data to be submitted, and the type of submitting organization (e.g., the initiator and responder). The orchestration needs may differ for different candidate workflows.

[0095] S303: Input the orchestration requirements into the target model, and the target model outputs text description information of the candidate workflows.

[0096] S304. Determine the reporting actions included in the candidate workflow from the text description information, generate the candidate workflow, and add the candidate workflow to the workflow library.

[0097] It should be noted that the target model is not overly limited; it may include language models, large models (such as large language models), etc. The text description information includes the reporting actions contained in the candidate workflow. For example, the text description information may also include the dependencies between the reporting actions contained in the candidate workflow, the name of the candidate workflow, etc. The training content of the target model can be found in the following embodiments, and will not be repeated here.

[0098] S305: Determine the target workflow for the target reporting event from the workflow library, configure the target workflow based on the configuration information of the target reporting event, and generate a reporting instance for the target reporting event.

[0099] S306, import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed.

[0100] S307 executes target code by scheduling the application to execute reporting instances in order to process target reporting events.

[0101] For details regarding steps S305-S307, please refer to the above embodiments; they will not be repeated here.

[0102] In summary, according to the data reporting method provided in this embodiment, in response to a second input operation of type 'arrangement operation' (for arrangement requirements), the arrangement requirements of the candidate workflow entered in the second input operation are obtained. These arrangement requirements are then input into a target model, which outputs text description information of the candidate workflow. The reporting actions included in the candidate workflow are determined from the text description information. Therefore, the arrangement requirements of the reporting workflow entered by the user can be input into the target model. The target model processes the arrangement requirements to obtain the text description information of the reporting workflow, thereby determining the reporting actions included in the reporting workflow. Thus, the user only needs to enter the arrangement requirements of the reporting workflow, without needing to arrange the reporting actions. Automatic arrangement of the reporting workflow is achieved through the target model, simplifying user operations, reducing the difficulty of reporting workflow arrangement, and improving the efficiency of reporting workflow arrangement.

[0103] Figure 4 This is a schematic flowchart of a data reporting method according to the fourth embodiment of this disclosure.

[0104] like Figure 4 As shown, the data reporting method of the fourth embodiment of this disclosure includes the following steps:

[0105] S401 abstracts the reporting action to obtain candidate codes and binds the reporting action to the candidate codes.

[0106] S402, in response to detecting an orchestration operation for a candidate workflow, and in response to the type of orchestration operation being a second entry operation for orchestration requirements, the orchestration requirements of the candidate workflow entered in the second entry operation are obtained.

[0107] For details regarding steps S401-S402, please refer to the above embodiments, which will not be repeated here.

[0108] S403, based on orchestration requirements, orchestration knowledge base and orchestration rule base, determines the reporting actions included in the candidate workflow, generates candidate workflows, and adds the candidate workflows to the workflow library.

[0109] It should be noted that the orchestration knowledge base includes multiple orchestration knowledge sets for submitting workflows, while the orchestration rule base includes multiple orchestration rules for submitting workflows. There are no strict limitations on the orchestration knowledge sets; for example, they can include modularity (decomposing the workflow into multiple independent modules), reusability (each module can be reused by multiple workflows), dependencies between submitted actions, conditional branching (such as conditional checks and branch merging), and exception handling. Similarly, there are no strict limitations on the orchestration rules; for example, they can include standardization (such as adopting unified naming and coding standards), scalability (such as designing a plug-in architecture and using configuration files to manage parameters), and security (such as data encryption, authentication, and access control).

[0110] In one implementation, based on orchestration requirements, an orchestration knowledge base, and an orchestration rule base, the submission actions included in a candidate workflow are determined. This includes retrieving orchestration knowledge matching the orchestration requirements from the orchestration knowledge base, retrieving orchestration rules matching the orchestration requirements from the orchestration rule base, and determining the submission actions included in the candidate workflow based on the matching orchestration knowledge and matching orchestration rules. Therefore, by considering the orchestration knowledge and orchestration rules matching the orchestration requirements of the submission workflow, the submission actions included in the submission workflow can be determined, enabling automatic orchestration of submission actions.

[0111] In some examples, the method also includes obtaining a first relevance parameter between the orchestration requirement and the orchestration knowledge, and based on the first relevance parameter, obtaining orchestration knowledge from the orchestration knowledge base that matches the orchestration requirement.

[0112] For example, based on the first relevance parameter, the orchestration knowledge matching the orchestration requirements is obtained from the orchestration knowledge base. This includes sorting multiple orchestration knowledge in descending order according to the first relevance parameter, taking the top Q orchestration knowledge as the matching orchestration knowledge, where Q is a positive integer, and / or taking the orchestration knowledge corresponding to the first relevance parameter that is greater than a set threshold as the matching orchestration knowledge.

[0113] In some examples, the method also includes obtaining a second correlation parameter between the orchestration requirement and the orchestration rule, and based on the second correlation parameter, obtaining an orchestration rule from the orchestration rule base that matches the orchestration requirement.

[0114] For example, based on the second relevance parameter, an orchestration rule matching the orchestration requirement is obtained from the orchestration rule base. This includes sorting multiple orchestration rules from largest to smallest according to the second relevance parameter, taking the top Q orchestration rules as the matching orchestration rules, where Q is a positive integer, and / or taking the orchestration rules corresponding to the second relevance parameter that is greater than a set threshold as the matching orchestration rules.

[0115] It should be noted that the first relevance parameter characterizes the correlation (also called the relationship) between layout requirements and layout knowledge, while the second relevance parameter characterizes the correlation between layout requirements and layout rules. Relevance can include the degree of correlation, positive correlation, negative correlation, or no correlation. There are no strict limitations on the relevance parameters; for example, they can include the F-value of linear regression, the correlation coefficient, the nonlinear correlation coefficient, and the multiple correlation coefficient. Obtaining the relevant content of the relevance parameters can be achieved using any correlation analysis method in the field of relevant techniques; no further limitations are imposed here.

[0116] S404: Determine the target workflow for the target reporting event from the workflow library, configure the target workflow based on the configuration information of the target reporting event, and generate a reporting instance for the target reporting event.

[0117] S405, import the reporting instance into the scheduling application, and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed.

[0118] S406 executes target code by scheduling the application to execute reporting instances in order to process target reporting events.

[0119] For details regarding steps S404-S406, please refer to the above embodiments; they will not be repeated here.

[0120] In summary, according to the data reporting method provided in this disclosure, in response to a second entry operation whose type of orchestration operation is for orchestration requirements, the orchestration requirements of the candidate workflow entered in the second entry operation are obtained. Based on the orchestration requirements, the orchestration knowledge base, and the orchestration rule base, the reporting actions included in the candidate workflow are determined. Therefore, the orchestration requirements of the reporting workflow entered by the user, the orchestration knowledge base, and the orchestration rule base can be comprehensively considered to determine the reporting actions included in the reporting workflow. Thus, the user only needs to enter the orchestration requirements of the reporting workflow, without needing to orchestrate the reporting actions, simplifying user operations, reducing the orchestration difficulty of the reporting workflow, and improving the orchestration efficiency of the reporting workflow.

[0121] Based on any of the above embodiments, the method further includes acquiring a sample workflow, sample orchestration requirements of the sample workflow, and sample execution information of the sample reporting instances corresponding to the sample workflow; training the target model based on the sample workflow, sample orchestration requirements, and sample execution information; and / or updating the orchestration knowledge base and orchestration rule base. Thus, during training, the target model can learn the relationship between sample orchestration requirements, sample workflow, and sample execution information. The trained target model can then obtain textual description information of the reporting workflow based on its orchestration requirements. Furthermore, it can update the orchestration knowledge base and orchestration rule base based on the sample workflow, sample orchestration requirements, and sample execution information, thereby improving the accuracy of the orchestration knowledge base and orchestration rule base.

[0122] It should be noted that there are no excessive restrictions on the execution information. For example, it may include the execution result (e.g., execution successful, execution failed) of the candidate code bound to the reporting action contained in the sample instance, the processing status (e.g., unprocessed, processing, processing completed) and processing result (e.g., processing successful, processing failed) of the sample reporting event corresponding to the sample instance.

[0123] It should be noted that, based on the sample workflow, sample orchestration requirements, and sample execution information, the target model can be trained using any model training method from the relevant technologies, without further restrictions here.

[0124] For example, the target model is trained based on sample workflows, sample orchestration requirements, and sample execution information. This includes determining the labels for the sample workflows based on the sample execution information, where the labels include positive or negative samples; inputting the sample orchestration requirements into the target model; outputting predicted text descriptions of the sample workflows from the target model; obtaining the loss function for the target model based on the predicted text descriptions, the actual text descriptions of the sample workflows, and the labels of the sample workflows; and training the target model based on the loss function. It should be noted that the loss function is not overly limited; for example, it can include Cross Entropy (CE), Mean-Square Error (MSE), Kullback-Leibler divergence (KL), contrastive loss functions, etc.

[0125] For example, determining the label of a sample workflow based on sample execution information includes determining the label of the sample workflow as a positive sample in response to the sample execution information indicating that the sample reporting event corresponding to the sample workflow was successfully processed, and determining the label of the sample workflow as a negative sample in response to the sample execution information indicating that the sample reporting event corresponding to the sample workflow was unsuccessfully processed.

[0126] Based on any of the above embodiments, the method further includes, in response to the consistency of the target workflows and reporting content of the M target reporting events, grouping the reporting agencies bound to the M target reporting events into the same reporting group, where M is a positive integer greater than 1, and generating statistical reports based on the execution information of the reporting instances of the multiple reporting agencies within the same reporting group. Thus, when the target workflows and reporting content of the multiple reporting events are consistent, the reporting agencies bound to the multiple reporting events can be grouped into the same reporting group, and by considering the execution information of the reporting instances of the multiple reporting agencies within the same reporting group, statistical reports can be generated. This enables collaborative statistics of the execution information of the reporting instances of different reporting agencies, improving the statistical efficiency of the execution information of reporting instances.

[0127] It is understandable that different reporting events may be associated with different reporting agencies.

[0128] Figure 5 This is a block diagram of a data reporting apparatus according to a first embodiment of the present disclosure.

[0129] like Figure 5 As shown, the data reporting device 100 of this embodiment includes: an abstraction module 110, an arrangement module 120, a configuration module 130, a parsing module 140, and an execution module 150.

[0130] Abstraction module 110 is configured to abstract the reporting action, obtain candidate code, and bind the reporting action to the candidate code;

[0131] The orchestration module 120 is configured to, in response to detecting an orchestration operation for a candidate workflow, determine the reporting actions contained in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation, generate the candidate workflow, and add the candidate workflow to the workflow library;

[0132] The configuration module 130 is configured to determine the target workflow of the target reporting event from the workflow library, and configure the target workflow based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event;

[0133] The parsing module 140 is configured to import the reporting instance into the scheduling application and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed.

[0134] Execution module 150 is configured to execute the target code through the scheduling application to execute the reporting instance to process the target reporting event.

[0135] In one embodiment of this disclosure, the orchestration module 120 is further configured to: control the display of multiple candidate selection items on an interactive page during the orchestration process of the candidate workflow, wherein the candidate selection items are used to represent reporting actions; in response to the type of the orchestration operation being a selection operation, take the candidate selection item selected by the selection operation as the target selection item; and add the reporting action corresponding to the target selection item to the reporting actions included in the candidate workflow.

[0136] In one embodiment of this disclosure, the orchestration module 120 is further configured to: in response to the orchestration operation being a first entry operation for a reporting action, obtain the reporting action entered by the first entry operation; and add the entered reporting action to the reporting actions included in the candidate workflow.

[0137] In one embodiment of this disclosure, the orchestration module 120 is further configured to: abstract the input reporting action to obtain new candidate codes, and bind the input reporting action to the new candidate codes; and / or, obtain the candidate codes input by the first input operation, and bind the input reporting action to the input candidate codes.

[0138] In one embodiment of this disclosure, the orchestration module 120 is further configured to: in response to a second input operation of type 2 for orchestration requirements, obtain the orchestration requirements of the candidate workflow entered by the second input operation; input the orchestration requirements into a target model, and have the target model output text description information of the candidate workflow; and determine the reporting action included in the candidate workflow from the text description information.

[0139] In one embodiment of this disclosure, the orchestration module 120 is further configured to: in response to a second input operation of type 2 for orchestration requirements, obtain the orchestration requirements of the candidate workflow entered by the second input operation; and determine the reporting actions included in the candidate workflow based on the orchestration requirements, the orchestration knowledge base, and the orchestration rule base.

[0140] In one embodiment of this disclosure, the orchestration module 120 is further configured to: obtain orchestration knowledge matching the orchestration requirements from the orchestration knowledge base; obtain orchestration rules matching the orchestration requirements from the orchestration rule base; and determine the reporting actions included in the candidate workflow based on the matching orchestration knowledge and the matching orchestration rules.

[0141] In one embodiment of this disclosure, the orchestration module 120 is further configured to: acquire a sample workflow, sample orchestration requirements of the sample workflow, and sample execution information of the sample reporting instance corresponding to the sample workflow; train the target model based on the sample workflow, the sample orchestration requirements, and the sample execution information; and / or update the orchestration knowledge base and the orchestration rule base.

[0142] In one embodiment of this disclosure, the configuration module 130 is further configured to: identify whether there is overlap information among the configuration information of each of the N target reporting events, where N is a positive integer greater than 1; in response to the existence of overlap information among the configuration information of each of the N target reporting events, perform batch configuration on the target workflow of each of the N target reporting events based on the overlap information, and generate reporting instances of each of the N target reporting events.

[0143] In one embodiment of this disclosure, the apparatus 100 further includes: a statistics module configured to: in response to the consistency of the target workflows of the M target reporting events and the consistency of the reporting content of the M target reporting events, divide the reporting agencies bound to the M target reporting events into the same reporting group, where M is a positive integer greater than 1; and generate a statistical report based on the execution information of the reporting instances of the multiple reporting agencies within the same reporting group.

[0144] In one embodiment of this disclosure, the configuration module 130 is further configured to: obtain the target reporting scenario of the target reporting event, and the candidate reporting scenarios of each of the multiple candidate workflows in the workflow library; obtain the similarity between the target reporting scenario and the candidate reporting scenarios; and determine the target workflow from the workflow library based on the similarity.

[0145] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0146] In summary, the data reporting device provided in this embodiment abstracts reporting actions to obtain candidate codes and binds the reporting actions to the candidate codes. This eliminates the need for users to write reporting code when orchestrating reporting workflows, simplifying user operations, reducing the difficulty of workflow orchestration, and improving workflow orchestration efficiency. Furthermore, by considering the type and operation information of the orchestration operation, the device determines the reporting actions included in the candidate workflow to generate a candidate workflow, which is then added to the workflow library, enabling automatic generation of reporting workflows. In addition, by identifying the target workflow for the target reporting event from the workflow library and taking into account the configuration information of the target reporting event, the target workflow is automatically configured to generate a reporting instance for the target reporting event. This enables the automatic generation of reporting instances. The reporting instances are then imported into the scheduling application, which parses them to obtain the candidate code bound to the reporting actions contained within the reporting instance. This candidate code serves as the target code to be executed. The scheduling application then executes the target code to execute the reporting instance, thus automating data reporting and improving data reporting efficiency.

[0147] Figure 6 This is a block diagram illustrating an electronic device according to an exemplary embodiment.

[0148] like Figure 6 As shown, the above-mentioned electronic device 200 includes:

[0149] The memory 210 and the processor 220 are connected by a bus 230, which connects different components (including the memory 210 and the processor 220). The memory 210 stores a computer program, and when the processor 220 executes the program, it implements the data reporting method described in the embodiments of this disclosure.

[0150] Bus 230 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0151] Electronic device 200 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by electronic device 200, including volatile and non-volatile media, removable and non-removable media.

[0152] Memory 210 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 240 and / or cache memory 250. Electronic device 200 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 260 may be used to read and write non-removable, non-volatile magnetic media (… Figure 6 Not shown; usually referred to as a "hard drive"). Although Figure 6 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 230 via one or more data media interfaces. Memory 210 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this disclosure.

[0153] A program / utility 280 having a set (at least one) of program modules 270 may be stored, for example, in memory 210. Such program modules 270 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 270 typically perform the functions and / or methods described in the embodiments of this disclosure.

[0154] Electronic device 200 can also communicate with one or more external devices 290 (e.g., keyboard, pointing device, display 291, etc.), and with one or more devices that enable a user to interact with the electronic device 200, and / or with any device that enables the electronic device 200 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 292. Furthermore, electronic device 200 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 293. Figure 6 As shown, network adapter 293 communicates with other modules of electronic device 200 via bus 230. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0155] The processor 220 performs various functional applications and data processing by running programs stored in the memory 210.

[0156] It should be noted that the implementation process and technical principles of the electronic device in this embodiment are explained in the foregoing description of the data reporting method of the present disclosure embodiment, and will not be repeated here.

[0157] In summary, the electronic device provided in this embodiment can execute the data reporting method described above, abstract the reporting action to obtain candidate code, and bind the reporting action to the candidate code. This eliminates the need for users to write reporting code when orchestrating reporting workflows, simplifying user operations, reducing the difficulty of orchestrating reporting workflows, and improving the orchestration efficiency. Furthermore, considering the type and operation information of the orchestration operation, the reporting actions included in the candidate workflow can be determined to generate a candidate workflow, which is then added to the workflow library, thus realizing the reporting workflow... The automatic generation of data streams, in addition, involves identifying the target workflow for the target reporting event from the workflow library and automatically configuring the target workflow based on the configuration information of the target reporting event. This generates a reporting instance for the target reporting event, which is then automatically generated. The reporting instance is imported into the scheduling application, which parses the reporting instance to obtain the candidate code bound to the reporting action contained in the reporting instance. This candidate code serves as the target code to be executed, and the scheduling application executes the target code to execute the reporting instance. This process automates data reporting and improves data reporting efficiency.

[0158] To implement the above embodiments, this disclosure also proposes a computer-readable storage medium.

[0159] When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the aforementioned actions or the aforementioned data reporting method. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, or optical data storage device, etc.

[0160] To implement the above embodiments, this disclosure also provides a computer program product, including a computer program, characterized in that the computer program, when executed by a processor, implements the data reporting method as described above.

[0161] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0162] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data reporting method, characterized in that, include: The reporting action is abstracted to obtain candidate codes, and the reporting action is bound to the candidate codes; In response to detecting an orchestration operation for a candidate workflow, based on the type of the orchestration operation and the operation information of the orchestration operation, the reporting action contained in the candidate workflow is determined to generate the candidate workflow and add the candidate workflow to the workflow library; The target workflow for the target reporting event is determined from the workflow library, and the target workflow is configured based on the configuration information of the target reporting event to generate a reporting instance of the target reporting event. The reporting instance is imported into the scheduling application, and the reporting instance is parsed by the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed. The target code is executed through the scheduling application to execute the reporting instance and process the target reporting event.

2. The method according to claim 1, characterized in that, The method further includes: During the orchestration of the candidate workflow, multiple candidate options are displayed on the interactive page, wherein the candidate options are used to represent the reporting action; The step of determining the reporting actions included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation includes: In response to the arrangement operation being a selection operation, the candidate selections selected by the selection operation are taken as the target selections. Add the reporting action corresponding to the target selection item to the reporting actions included in the candidate workflow.

3. The method according to claim 1, characterized in that, The step of determining the reporting actions included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation includes: In response to the arrangement operation being a first input operation for a reporting action, the reporting action entered by the first input operation is obtained; The entered reporting action is added to the reporting actions included in the candidate workflow.

4. The method according to claim 3, characterized in that, The method further includes: The entered reporting action is abstracted to obtain new candidate codes, and the entered reporting action is bound to the new candidate codes; and / or, Obtain the candidate code entered in the first input operation, and bind the input reporting action to the entered candidate code.

5. The method according to claim 1, characterized in that, The step of determining the reporting actions included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation includes: In response to the orchestration operation being a second entry operation for orchestration requirements, the orchestration requirements of the candidate workflow entered in the second entry operation are obtained; The orchestration requirements are input into the target model, and the target model outputs the text description information of the candidate workflow; The reporting actions included in the candidate workflow are determined from the text description information.

6. The method according to claim 1, characterized in that, The step of determining the reporting actions included in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation includes: In response to the orchestration operation being a second entry operation for orchestration requirements, the orchestration requirements of the candidate workflow entered in the second entry operation are obtained; Based on the orchestration requirements, orchestration knowledge base, and orchestration rule base, the reporting actions included in the candidate workflow are determined.

7. The method according to claim 6, characterized in that, The step of determining the reporting actions included in the candidate workflow based on the orchestration requirements, orchestration knowledge base, and orchestration rule base includes: Retrieve orchestration knowledge that matches the orchestration requirements from the orchestration knowledge base; Obtain orchestration rules that match the orchestration requirements from the orchestration rule base; Based on the matching orchestration knowledge and the matching orchestration rules, the reporting actions included in the candidate workflow are determined.

8. The method according to any one of claims 5-7, characterized in that, The method further includes: Obtain the sample workflow, the sample orchestration requirements of the sample workflow, and the sample execution information of the sample reporting instance corresponding to the sample workflow; Based on the sample workflow, the sample orchestration requirements, and the sample execution information, the target model is trained, and / or the orchestration knowledge base and orchestration rule base are updated.

9. The method according to any one of claims 1-7, characterized in that, The step of configuring the target workflow based on the configuration information of the target reporting event and generating a reporting instance of the target reporting event includes: Identify whether there is overlap in the configuration information of each of the N target reporting events, where N is a positive integer greater than 1; In response to the existence of overlapping information between the configuration information of the N target reporting events, the target workflow of the N target reporting events is configured in batches based on the overlapping information, and a reporting instance of the N target reporting events is generated.

10. The method according to any one of claims 1-7, characterized in that, The method further includes: In response to the consistency of the target workflows of the M target reporting events and the consistency of the reporting content of the M target reporting events, the reporting agencies bound to the M target reporting events are divided into the same reporting group, where M is a positive integer greater than 1; Statistical reports are generated based on the execution information of each reporting instance from multiple reporting agencies within the same reporting group.

11. The method according to any one of claims 1-7, characterized in that, The step of determining the target workflow for the target reporting event from the workflow library includes: Obtain the target reporting scenario of the target reporting event, and the candidate reporting scenarios of each of the multiple candidate workflows in the workflow library; Obtain the similarity between the target reporting scenario and the candidate reporting scenario; Based on the similarity, the target workflow is determined from the workflow library.

12. A data reporting device, characterized in that, include: The abstract module is configured to abstract the reporting action, obtain candidate code, and bind the reporting action to the candidate code; The orchestration module is configured to, in response to detecting an orchestration operation for a candidate workflow, determine the reporting actions contained in the candidate workflow based on the type of the orchestration operation and the operation information of the orchestration operation, generate the candidate workflow, and add the candidate workflow to the workflow library; The configuration module is configured to determine the target workflow of the target reporting event from the workflow library, configure the target workflow based on the configuration information of the target reporting event, and generate a reporting instance of the target reporting event. The parsing module is configured to import the reporting instance into the scheduling application and parse the reporting instance through the scheduling application to obtain the candidate code bound to the reporting action contained in the reporting instance, which is used as the target code to be executed. The execution module is configured to execute the target code through the scheduling application to execute the reporting instance to process the target reporting event.

13. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the data reporting method as described in any one of claims 1-11.

14. A computer-readable storage medium, wherein when instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the data reporting method as described in any one of claims 1-11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the data reporting method as described in any one of claims 1-11.

Images