Data reporting method, device, equipment and medium

Abstract

The present disclosure provides a data reporting method, which can be applied to the financial field or other fields. The method includes: receiving transaction snapshots of at least one business scenario; storing the transaction snapshots of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information; extracting element information from the stored transaction snapshots and summarizing it into a transaction data summary table; splicing the data of the corresponding fields in the transaction data summary table according to the reporting interface specification of the target supervision system to form a target spliced message; and sending the target spliced message to the target supervision system. The present disclosure also provides a data reporting device, equipment, storage medium and program product.

Description

Technical Field

[0001] The present disclosure relates to the field of information security, and can be used in the financial field or other fields. More specifically, it relates to a data reporting method, apparatus, device, medium, and program product. Background Art

[0002] Currently, financial institutions such as banks need to report corresponding regulatory data to regulatory agencies according to regulatory requirements during business operations. The types of data involved are relatively numerous, and the data reporting sources often correspond to multiple business systems. In the prior art, the common solution for data reporting is to use an independent data reporting system as a bridge between financial institutions and regulatory agencies. On the one hand, it receives data files from each upstream business system of the financial institution and conducts unified processing. On the other hand, it reports the unified processed data to the monitoring agency according to the reporting requirements.

[0003] In the process of implementing the inventive concept of the present invention, the inventors found that the prior art has the following defects: Since the reported data involves multiple business systems, when developing the data reporting system, a large amount of negotiation, research, and testing of upstream and downstream file interfaces or online interfaces are often required. Moreover, when the data specification requirements reported by the regulatory agency change, the interfaces connected to the upstream business systems often need to be modified accordingly, and the modification workload is large. Summary of the Invention

[0004] In view of the above problems, the present disclosure provides a data reporting method, apparatus, device, medium, and program product that greatly facilitate the docking efficiency with upstream business systems.

[0005] According to a first aspect of the present disclosure, there is provided a data reporting method, including: receiving transaction snapshots of at least one business scenario; when any first business scenario in the at least one business scenario belongs to the business scenarios in the scenario configuration information, storing the transaction snapshots of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information; extracting element information from the stored transaction snapshots according to the element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario, and summarizing it into a transaction data summary table; and reporting data to at least one regulatory system based on the transaction data summary table.

[0006] According to an embodiment of the present disclosure, the scenario configuration information is obtained in the following manner: configuring the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data required to be reported by the at least one regulatory system, where the at least one regulatory system includes the target regulatory system.

[0007] According to an embodiment of the present disclosure, configuring the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data reported according to the requirements of the at least one supervision system further includes: when the business scenarios involved in the data reported according to the requirements of the at least one supervision system change, correspondingly changing the scenario configuration information, and after changing the scenario configuration information, correspondingly changing the element extraction methods of the changed business scenarios in the element extraction configuration information.

[0008] According to an embodiment of the present disclosure, the element extraction configuration information is obtained in the following manner: configuring the element information and its extraction method corresponding to the element fields in the element extraction configuration information according to the element fields involved in the data reported according to the requirements of the at least one supervision system. Wherein, when the element fields involve multiple business scenarios, the element information and its extraction method corresponding to the element fields are respectively configured in the multiple business scenarios in the element extraction configuration information.

[0009] According to an embodiment of the present disclosure, configuring the element information and its extraction method corresponding to the element fields in the element extraction configuration information according to the element fields involved in the data reported according to the requirements of the at least one supervision system further includes: when the element fields of the data reported according to the requirements of the at least one supervision system change, correspondingly changing the element extraction configuration information.

[0010] According to an embodiment of the present disclosure, extracting element information from the stored transaction snapshots according to the element extraction methods configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario includes: extracting element information from the transaction snapshots of the first business scenario according to the first element extraction method configured in the element extraction configuration information corresponding to the first business scenario. Specifically, it includes: obtaining at least one element position set in the first element extraction method; identifying the character information in the first element position in the transaction snapshot of the first business scenario, where the first element position is any one of the at least one element positions; obtaining the first field set in the first element extraction method corresponding to the first element position; and extracting the character information identified from the first element position to fill in the first field of the transaction data summary table.

[0011] According to an embodiment of the present disclosure, reporting data to at least one regulatory system based on the transaction data summary table includes: verifying the data of corresponding fields in the transaction data summary table according to a data verification rule set according to the data quality specification requirements of a target regulatory system, where the target regulatory system is any one of the at least one regulatory system; splicing the data of corresponding fields in the transaction data summary table according to the reporting interface specification of the target regulatory system to form a target spliced message in case of successful verification; and sending the target spliced message to the target regulatory system.

[0012] According to an embodiment of the present disclosure, the method further includes: archiving the transaction snapshots of each business scenario according to an archiving policy set for each business scenario.

[0013] In a second aspect of the embodiments of the present disclosure, a data reporting device is provided. The device includes: a transaction site receiving module, an automatic processing module for reporting data, and an external connection reporting module. Among them, the automatic processing module for reporting data includes a snapshot storage module and an element extraction module. The transaction site receiving module is configured to receive transaction snapshots of at least one business scenario. The snapshot storage module is configured to store the transaction snapshots of the first business scenario in the first file directory configured for the first business scenario in the scenario configuration information when any first business scenario among the at least one business scenario belongs to the business scenarios in the scenario configuration information. The element extraction module is configured to extract element information from the stored transaction snapshots according to an element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario, and summarize it into a transaction data summary table. The external connection reporting module is configured to report data to at least one regulatory system based on the transaction data summary table.

[0014] According to an embodiment of the present disclosure, the device further includes a rule library module. The rule library module is configured to configure the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data required to be reported by at least one regulatory system, where the at least one regulatory system includes the target regulatory system. According to an embodiment of the present disclosure, the rule library module is further configured to correspondingly change the scenario configuration information when the business scenarios involved in the data required to be reported by the at least one regulatory system change, and correspondingly change the element extraction method of the changed business scenario in the element extraction configuration information after changing the scenario configuration information.

[0015] According to an embodiment of the present disclosure, the rule base module is configured to configure the element information corresponding to the element field in the element extraction configuration information and its extraction method according to the element fields involved in the data reported according to the requirements of at least one supervision system; wherein, when the element field involves multiple business scenarios, the element information corresponding to the element field and its extraction method are respectively configured in the multiple business scenarios in the element extraction configuration information. According to another embodiment of the present disclosure, the rule base module is further configured to correspondingly change the element extraction configuration information when the element field of the data reported according to the requirements of the at least one supervision system changes.

[0016] According to an embodiment of the present disclosure, the device further includes a data verification module for reporting data. The data verification module for reporting data is configured to verify the data in the corresponding fields of the transaction data summary table according to the data verification rules set according to the data quality specification requirements of the target supervision system; the target supervision system is any one of the at least one supervision system. The external connection reporting module is configured to splice the data in the corresponding fields of the transaction data summary table according to the reporting interface specification of the target supervision system in the case of passing the verification, form a target spliced message and send the target spliced message to the target supervision system.

[0017] In a third aspect of the embodiments of the present disclosure, an electronic device is provided. The electronic device includes one or more processors and one or more memories. The memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the above method.

[0018] In a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which executable instructions are stored, and when the instructions are executed by a processor, the processor is caused to execute the above method.

[0019] In a fifth aspect of the embodiments of the present disclosure, a computer program product is further provided, including a computer program, and when the computer program is executed by a processor, the above method is implemented.

[0020] The above one or more embodiments have the following advantages or beneficial effects: Through the scenario configuration information and the element extraction configuration information, when docking with various upstream business systems, only the transaction snapshot can be transmitted, without distinguishing specific file types, data types, etc., and without designing interfaces for different upstream business systems according to business scenarios. In this way, the interface design and development with each upstream business system are simplified. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, the above content and other objects, features and advantages of the present disclosure will become clearer. In the drawings:

[0022] Figure 1 Schematically shows the system architecture diagram of a data reporting method and apparatus according to an embodiment of the present disclosure;

[0023] Figure 2 Schematically shows the system architecture diagram of a data reporting method and apparatus according to another embodiment of the present disclosure;

[0024] Figure 3 Schematically shows the flowchart of a data reporting method according to an embodiment of the present disclosure;

[0025] Figure 4 Schematically shows the flowchart of configuring scenario configuration information in the data reporting method according to an embodiment of the present disclosure;

[0026] Figure 5 Schematically shows the flowchart of extracting configuration information of configuration elements in the data reporting method according to an embodiment of the present disclosure;

[0027] Figure 6 Schematically shows the method flowchart of extracting element information from a transaction snapshot in the data reporting method according to an embodiment of the present disclosure;

[0028] Figure 7 Schematically shows the flowchart of automatically processing a transaction snapshot for data reporting in the data reporting method according to an embodiment of the present disclosure;

[0029] Figure 8 Schematically shows the flowchart of a data reporting method according to another embodiment of the present disclosure;

[0030] Figure 9 Schematically shows the block diagram of a data reporting apparatus according to an embodiment of the present disclosure;

[0031] Figure 10 Schematically shows the block diagram of a data reporting apparatus according to another embodiment of the present disclosure; and

[0032] Figure 11 Schematically shows the block diagram of an electronic device suitable for implementing the data reporting method according to an embodiment of the present disclosure. Detailed implementation manners

[0033] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the following detailed description, for the sake of explanation, numerous specific details are set forth in order to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is obvious that one or more embodiments can be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

[0034] The terms used herein are merely for the purpose of describing specific embodiments and are not intended to limit the present disclosure. The terms "including", "comprising", etc. used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0035] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0036] In the case of using expressions such as "at least one of A, B, and C", generally, it should be interpreted according to the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include, but is not limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C). The terms "first" and "second" are used only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features.

[0037] In view of the fact that when reporting data in the prior art, it is necessary to separately negotiate with each upstream business system to determine various data interaction interfaces, which causes the development process to be cumbersome, and when the regulatory reporting data changes, it leads to a large amount of interface modification. Embodiments of the present disclosure provide a data reporting method, apparatus, device, medium, and program product that can improve the docking efficiency with each business system.

[0038] The key points of the embodiments of the present disclosure mainly include two aspects: First, by pre-configuring the file directories of various business scenarios in the scenario configuration information, the transaction snapshots used to record the transaction site information from each business system can be stored in the corresponding directories according to the belonging business scenarios; Second, by pre-configuring the element extraction methods of the transaction snapshots in each business scenario in the element extraction configuration information, the element information such as characters to be reported can be extracted from the transaction snapshots of each business scenario, so that the original data to be reported can be extracted from the transaction snapshots for subsequent data processing (for example, data aggregation and integration, verification, forming a message for sending, etc.).

[0039] It can be seen that through the scenario configuration information and the element extraction configuration information, the embodiments of the present disclosure enable only the transaction snapshots to be transmitted when docking with various upstream business systems, without the need to distinguish specific file types, data types, etc., so that there is no need to design interfaces specifically for different upstream business systems according to business scenarios and file types, simplifying the interface design and development with each upstream business system.

[0040] At the same time, according to the embodiments of the present disclosure, when the data specification requirements by the regulatory agency change, by changing the business scenarios involved in the scenario configuration information and / or the element extraction methods involved in the element extraction configuration information, the purpose of changing the available transaction snapshots and / or the element information in the transaction snapshots can be achieved. In this way, according to the embodiments of the present disclosure, when the data specification requirements by the regulatory agency change, a large number of interface modifications do not need to be carried out. Only by changing the corresponding scenario configuration information and / or element extraction configuration information, the data reporting can be quickly realized, greatly improving the data reporting efficiency and reducing the workload of developers.

[0041] Furthermore, according to the embodiments of the present disclosure, the transaction snapshots of each business scenario can also be archived for subsequent traceability and confirmation, avoiding the trouble of having to log in to the original business system again for query and confirmation when there are problems with the reported data in the prior art.

[0042] In the technical solution of the present disclosure, the processing of the collection, storage, use, processing, transmission, provision, disclosure and application of the user's personal information involved (for example, existing in the transaction snapshot) complies with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and public order and good customs are not violated.

[0043] It should be noted that the data reporting method and device determined by the embodiments of the present disclosure can be used in the financial field and can also be used in any field other than the financial field. The present disclosure does not limit the application field.

[0044] Figure 1A system architecture diagram of a data reporting method and apparatus according to an embodiment of the present disclosure is schematically shown.

[0045] As Figure 1 shown, in the system architecture 100, a data reporting apparatus 101 according to an embodiment of the present disclosure can be connected in series with an original data reporting system 102 to jointly serve as a bridge for docking between at least one business system and at least one monitoring system. Among them, in the system architecture 100, the at least one business system is shown as including a plurality of business systems. For example, business system 1, business system 2, business system 3, business system 4,..., and business system n. In the system architecture 100, the at least one supervision system is exemplified as including a plurality of supervision systems. For example, the system of supervision agency 1, the system of supervision agency 2,..., and the system of supervision agency m. The system architecture 100 can be obtained by transforming the original reporting system process in financial institutions such as banks.

[0046] Among them, the data reporting apparatus 101 can execute the data reporting method according to an embodiment of the present disclosure, store the transaction snapshots from the upstream business system according to the file directory in the scenario configuration information, extract element information according to the element extraction method configured in the element extraction configuration information, and then summarize the extracted element information into a transaction data summary table, and then subsequent data reporting can be performed according to the data in the transaction data summary table.

[0047] The original data reporting system 102 can only serve as an information interaction channel with the systems of external supervision agencies and no longer undertake the function of data processing and processing.

[0048] In one embodiment, the data processing process of the data reporting apparatus 101 may include: first receiving the transaction snapshots sent from the upstream business system, and automatically extracting the data information to be reported from the transaction snapshots according to the scenario configuration information and the element extraction configuration information, for example, by using optical character recognition technology (OCR). Then, according to the requirements of the supervision agency for the reported data, the data can be verified and formed into a message, and sent to the original data reporting system 102 for external data reporting.

[0049] In some embodiments, for the data that fails the verification, the data reporting apparatus 101 can enter the supplementary recording state, and after being confirmed by the business personnel, rectification can be carried out. During the confirmation process, the business personnel can directly call the transaction snapshots for traceability without logging in to the upstream business systems (such as business system 1, business system 2, business system 3, business system 4,..., and business system n).

[0050] In some embodiments, the data reporting device 101 may also receive the processing results of the reported data feedback by at least one supervision system (for example, the system of supervision agency 1, the system of supervision agency 2,..., and / or the system of supervision agency m). For the data successfully processed by the supervision system, the status is updated to reported successfully; for the data with failed processing returned by the supervision system, the status is updated to reported failed, and after being confirmed by the business personnel, rectification is carried out. In the confirmation process, the business personnel can also directly call the transaction site for traceability without logging in to the upstream business system.

[0051] Figure 2 Schematically shows a system architecture diagram of a data reporting method and device according to another embodiment of the present disclosure.

[0052] Obviously, it can also be in Figure 2 the connection mode shown in the system architecture 200, and the data reporting device 201 according to the embodiment of the present disclosure is separately used as a bridge between at least one business system and at least one monitoring system to report data to at least one supervision system (for example, the system of supervision agency 1, the system of supervision agency 2,..., and / or the system of supervision agency m). Among them, the data reporting device 201 can execute the data reporting method of the embodiment of the present disclosure.

[0053] According to the embodiment of the present disclosure, whether it is the system architecture 100 or 200, the business system only needs to save a picture snapshot of the transaction site to obtain a transaction snapshot, and then transmit the transaction snapshot to the data reporting device 101 or 201. The data reporting device 101 or 201 will automatically extract the element information in the transaction snapshot by using, such as OCR image recognition technology, according to the snapshot processing method in the business scenario configured in the pre-configured scenario configuration information and element extraction configuration information. Then, the extracted element information can be used for data reporting. For example, after the message is spliced according to the reporting interface specification and the data to be reported passes the verification, it is reported externally.

[0054] According to the embodiment of the present disclosure, the data reporting device 101 or 201 can specifically be implemented as at least one of the data reporting device 900, the data reporting device 10, the electronic device 1100, the readable storage medium, and the computer program product described below, and is used to execute the Figures 3 - 8 reporting method described below. Specifically, refer to the detailed introduction below.

[0055] Figure 3 Schematically shows a flowchart of a data reporting method according to an embodiment of the present disclosure.

[0056] As Figure 3 shown, the data reporting method according to this embodiment may include operation S310 to operation S340.

[0057] First, in operation S310, receive transaction snapshots of at least one business scenario.

[0058] A transaction snapshot is an image information formed by the business system taking a screenshot or a photo of the transaction site of a transaction.

[0059] The main function of the transaction snapshot is to record the original transaction information, which is an information snapshot of the transaction site after the transaction is successful and will not change. For example, when the bank remittance system submits a remittance application form according to the customer's application information, after receiving the remittance success notice, taking a screenshot or a photo of the transaction record information of the remittance transaction can obtain a transaction snapshot of the remittance business. Among them, the process of taking a screenshot or a photo can be implemented by a background program in the business system. For example, a program can be written to automatically take a screenshot or a photo of the page recording the transaction site information after the business system receives a trigger signal indicating the success of the transaction.

[0060] Then, in operation S320, when any first business scenario in at least one business scenario belongs to the business scenarios in the scenario configuration information, store the transaction snapshot of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information.

[0061] The scenario configuration information is used to define the business scenarios for data submission by the upstream business system and information such as the transaction snapshot file directory in each business scenario.

[0062] Table 1 exemplifies the content of part of the scenario configuration information. For example, the business scenario with scenario ID 000001 is defined as: the balance of payments data that needs to be submitted in the business transactions occurring in the AAA business system, where the submission category is BOP.

[0063] Table 1

[0064] Scenario ID Scenario Description Upstream Business System Reporting Category Transaction Snapshot File Directory Transaction Snapshot Name Effective Flag 000001 Balance of Payments Data Declaration AAA BOP \AAA\ AAA_00001 0 000002 Balance of Payments Data Declaration BBB BOP \BBB\ AAB__00001 0 000003 External Debt Data Declaration CCC XXX \XXX\ APL988XXX 0 ......

[0065] In one embodiment, the data submission device 101 or 201 can provide the scenario configuration information to the connected business systems (such as business system 1, business system 2, business system 3, business system 4,..., and business system n). Each business system can transmit the transaction snapshot to the data submission device 101 or 201 according to the file directory corresponding to the business scenario in its own business, along the path defined in the file directory, so that the data submission device 101 or 201 can store the transaction snapshot under the file directory. For example, according to the scenario configuration information in Table 1, the AAA business system can name the generated transaction snapshot in the way of "AAA_(file serial number)" (for example, AAA_00001) and transmit it to the file directory \AAA\ of the data submission device 101 or 201.

[0066] In another embodiment, the data reporting device 101 or 201 may provide a unified snapshot receiving interface for all business systems connected thereto, and then determine the business system that sends the transaction snapshot and the corresponding business scenario according to the attributes of the received transaction snapshot (for example, naming information, source system, source port, or protocol, etc.). Furthermore, according to the scenario configuration information, the transaction snapshot is stored in the file directory corresponding to the business scenario to which it belongs.

[0067] It can be seen that the embodiments of the present disclosure effectively solve the docking between the data reporting device 101 or 201 and the upstream business system through the scenario configuration information, and can automatically store the transaction snapshots from the upstream business system in a specific location.

[0068] Next, in operation S330, according to the element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario, extract the element information from the stored transaction snapshots and summarize it into the transaction data summary table.

[0069] In one embodiment, the business scenarios in the element extraction configuration information are the same as those in the scenario configuration information. Thus, there can be corresponding element extraction methods for the transaction snapshots of each business scenario.

[0070] According to the embodiments of the present disclosure, in the element extraction configuration information, a set of element extraction methods can be configured for each business scenario.

[0071] The extracted element information can specifically be character information identified from the transaction snapshot. For example, it can be character data identified through OCR text recognition technology.

[0072] Summarize the extracted element information into the transaction data summary table. For example, after identifying the character data at a certain element position or field in the transaction snapshot, according to the predefined mapping relationship between the identified element position or field and the fields in the transaction data summary table, fill the identified character data into the corresponding fields of the transaction data summary table. Among them, the information elements from the same transaction snapshot form a record in the transaction data summary table, that is, corresponding to one transaction. An exemplary description is as follows with reference to Table 2.

[0073] Table 2 exemplifies part of the content of the element extraction configuration information. Multiple information extraction rules are configured for scenario 000001 in this element extraction method. Specifically, there are multiple rows of records corresponding to scenario ID 000001 in Table 2, which means that for each transaction snapshot in scenario 000001, element information can be identified from multiple element positions respectively, and according to the table name and field name corresponding to each element position, fill the identified element information into the corresponding fields of the data table.

[0074] For example, the implementation process of extracting elements according to the rule No. 1 in Table 2 is as follows: Automatically identify and extract the information from the element positions determined by x: 1, 10 && y: 2, 12 in the transaction site document AAA_00001, and save it in the DATE1 field of the MAIN table (i.e., the transaction data summary table) as the element value of FILE1 of the reporting type BOP. For the specific process of extracting element information according to the method shown in Table 2, please refer to the detailed introduction below Figure 6 in the following text

[0075] Table 2

[0076]

[0077] It should be noted that in the element extraction method in Table 2, identifying and extracting element information from the image range defined by the element position is only a feasible embodiment. In some other embodiments, the element extraction method may also be to first perform OCR recognition on the entire transaction snapshot, and then extract the information of certain fields from the recognition result and fill it into the corresponding fields of the transaction summary table

[0078] Thereafter, in operation S340, based on the transaction data summary table, data is reported to at least one supervision system

[0079] In one embodiment, first, according to the message receiving specification of the supervision system (hereinafter referred to as the target supervision system) that receives the reported data, extract the information of the corresponding fields from the transaction data summary table and splice them into a message, and then verify the data in the message (for example, whether the data is compliant, whether the data format of each field is correct, etc.). After all verifications pass, send the spliced message to the target supervision system

[0080] In another embodiment, first, verify the data of the corresponding fields within the required reporting time period in the transaction data summary table according to the specification requirements of the target supervision system for the reported data. After all verification requirements pass, splice and form a message according to the message receiving specification of the target supervision system, and then send it to the target supervision system

[0081] For the data or message that fails the verification, a notice of failed verification can be issued, and it is transferred to manual confirmation or rectification of the information that fails the verification. After the rectification is completed, re-verification is performed

[0082] Further, in some embodiments, the processing result of the reported data by the target monitoring system may also be received. When the processing result indicates successful reporting, the status of the reported data is updated to successful reporting. When the processing result indicates reporting failure, the status of the reported data may be updated to reporting failure, and then it may be transferred to the business personnel for confirmation and rectification. According to the embodiments of the present disclosure, in the confirmation link, the business personnel may directly call the transaction snapshot stored in the data reporting device 101 or 201 for traceability without logging in to the upstream business system.

[0083] It can be seen that in the embodiments of the present disclosure, on the one hand, the scenario configuration information can be used to instruct the upstream business system or the data reporting device 101 or 201 to store the transaction snapshot according to the file directory corresponding to the business scenario, and on the other hand, it can also be used to instruct the data reporting device 101 or 201 to read the transaction snapshot from the corresponding directory according to the business scenario and extract the element information from the transaction snapshot according to the element extraction method of the business scenario.

[0084] In this way, through the scenario configuration information and the element extraction configuration information, when the data reporting device 101 or 201 is docked with various upstream business systems, only the transaction snapshot can be transmitted, and it is not necessary to distinguish specific file types, data types, etc., nor to design interfaces for different upstream business systems according to business requirements. In this way, when realizing data reporting Figure 4 Schematically shows a flowchart of configuring scenario configuration information in the data reporting method according to an embodiment of the present disclosure.

[0085] Specifically, as Figure 4 shown, the process of configuring scenario configuration information according to this embodiment may include operation S410 to operation S440. Among them, the scenario configuration information may be configured before operation S310.

[0086] In operation S410, according to the business scenarios involved in the data reported according to the requirements of at least one regulatory system, configure the business scenarios and their file directories in the scenario configuration information. As shown in Table 1.

[0087] In operation S420, detect whether a notice of change in the business scenarios involved in the data reported according to the requirements of at least one regulatory system is received. Among them, if a notice is received, operation S430 is executed; if no notice is received, the scenario configuration information configured in S410 is used. The change in the business scenario may include deletion, addition, replacement, etc. of the business scenario.

[0088] In operation S430, when the business scenarios involved in the data reported according to the requirements of at least one regulatory system change, the scenario configuration information is correspondingly changed.

[0089] Next, in operation S440, the element extraction method of the business scenario that has been changed in the corresponding change element extraction configuration information is changed.

[0090] For example, assume that currently regulatory requirements state that Category A business needs to add data reporting of BOP category, and the data of this BOP category comes from the upstream business system B1 (for example, one of business systems 1, 2, 3, 4,..., and business system n).

[0091] According to the embodiments of the present disclosure, without changing the upstream business system B1, it is possible to support the reporting of this type of data only by adding a business scenario of BOP category in the scenario configuration information. The specific configuration steps are as follows.

[0092] First step, add the business scenario information shown in Table 3 below in the scenario configuration information.

[0093] Table 3

[0094]

[0095] Second step: For this business scenario, configure the information of the element extraction method, as shown in Table 4.

[0096] Table 4

[0097]

[0098] After the first step and the second step, the data reporting device 101 or 201 can summarize the transaction data of the BOP category carried out in the business system B1 into the transaction data summary table (i.e., the Main table).

[0099] Then, according to the embodiments of the present disclosure, the entire reporting process settings can also be improved through, for example, the following third step and fourth step.

[0100] Third step: Set data verification rules for the data in this business scenario to ensure the quality of the externally reported data.

[0101] Fourth step: Configure the archiving policy settings for the transaction site of this business scenario.

[0102] In this way, according to the embodiments of the present disclosure, the upstream business system B1 only needs to save the transaction site through a snapshot to form a transaction snapshot, and transmit it to the data reporting device 101 or 201. The data reporting device can automatically save the transaction snapshot in the corresponding file directory according to the scenario configuration information. Thereafter, transmitting to the data reporting device 101 or 201 can achieve automatic extraction, processing, verification, and reporting of the reporting information based on the transaction snapshot, saving R & D costs.

[0103] In the prior art, when it is necessary to increase the reported data of a business scenario, it is necessary to transmit the business data of the new business scenario to the original data reporting system 102 by adding a batch or an online interface. The original data reporting system 102 also needs to be modified to receive the reporting file of the upstream business system B1, perform relevant verification processing, and then report it externally. That is, both the upstream business system B1 and the original data reporting system 102 need to be modified simultaneously. By comparison, it can be seen that according to the method of the embodiments of the present disclosure, by changing the scenario configuration information and the element extraction configuration information, it is possible to avoid modifying the data transmission interfaces of the upstream business system B1 and the data reporting device 101 or 201, saving development costs and improving the reporting efficiency.

[0104] Figure 5 Schematically shows a flowchart of configuring element extraction configuration information in the data reporting method according to an embodiment of the present disclosure.

[0105] As Figure 5 shown, the process of configuring the element extraction configuration information according to this embodiment may include operation S510 to operation S530. In some embodiments, the element extraction configuration information may be configured before operation S310. In other embodiments, the element extraction configuration information may be configured after the scenario configuration information is configured in operation S410.

[0106] Specifically, in operation S510, according to the element fields involved in the data reported according to the requirements of at least one regulatory system, configure the element information corresponding to the element fields and its extraction method in the element extraction configuration information, as shown in Table 2.

[0107] It can be understood that Table 2 only shows the extraction methods of different element fields in one scenario. When a certain element field (for example, transaction amount) that needs to be reported by the regulatory agency involves multiple business scenarios, configure the element information corresponding to the element field and its extraction method in multiple business scenarios in the element extraction configuration information.

[0108] In operation S520, detect whether a notification of a change in the element fields of the data required to be reported by at least one regulatory system is received. If received, perform operation S530; if not received, continue to use the element extraction configuration information configured in S510.

[0109] In operation S530, when the element fields of the data required to be reported by at least one regulatory system change, correspondingly change the element extraction configuration information.

[0110] For example, assume that regulatory requirements change, and for the reporting data of the EXD category that is already being reported, it is necessary to add the reporting field C. The data of the EXD category comes from N business processing systems (for example, N systems among business system 1, business system 2, business system 3, business system 4,..., and business system n, where N is an integer greater than or equal to 1 and less than or equal to n).

[0111] According to the embodiments of the present disclosure, it can be supported only by adding the extraction method of the element information corresponding to the field C in the element extraction configuration information. The specific configuration steps can be exemplified as follows.

[0112] First step, the scenario configuration information table does not need to be adjusted because this example does not involve the addition or modification of business scenarios.

[0113] Second step: Configure the OCR image recognition extraction method for the newly added reporting field C in the element extraction configuration information, as shown in Table 5 below.

[0114] Specifically, since the field C comes from the EXD category in the N business processing systems, the extraction methods of the elements in the business scenarios related to the EXD category in the N business processing systems all need to be changed.

[0115] Table 5

[0116]

[0117] After the second step, the data reporting device 101 or 201 can summarize the data of the field C in the transactions of the EXD category into the Main table.

[0118] After that, the settings of the entire reporting process can be further improved through, for example, the following third step and fourth step.

[0119] Third step: Set data verification rules for the newly added field C in each business scenario to ensure the quality of the externally reported data.

[0120] Fourth step: The setting of the transaction site archiving strategy for this scenario does not need to be adjusted because this example does not involve the addition or modification of reporting scenarios.

[0121] It can be seen that according to the embodiments of the present disclosure, when the business scenarios in the data required to be reported by the regulatory system remain unchanged, but the reported element fields change, it is not necessary to modify the N upstream business systems related to the element fields. It can be achieved only by configuring the extraction method of the newly added reporting field C in the element extraction configuration information, greatly reducing the system transformation workload.

[0122] In the prior art, when an element field of the data to be reported required by the supervision system changes, it is necessary to separately modify the batch interfaces or online interfaces of N business systems and the original data reporting system 102, resulting in a large amount of modification work. By comparison, in the embodiments of the present disclosure, by configuring and / or changing the element information extraction configuration information, when the supervision needs to add a certain field, the corresponding element extraction can be quickly realized, reducing the system modification work, which is beneficial to the timeliness and efficiency improvement of data reporting.

[0123] Figure 6 Schematically shows a method flowchart for extracting element information in operation S330 in the data reporting method according to an embodiment of the present disclosure from a transaction snapshot.

[0124] As Figure 6 shown, in the data reporting method of an embodiment of the present disclosure, when extracting element information from the stored transaction snapshot in operation S330, for the transaction snapshot in any first business scenario, the element information is extracted according to the first element extraction method corresponding to the first business scenario. The first element extraction method can be, for example, as shown in Table 2, and can include multiple rules or extraction methods for multiple element fields. The specific process of extracting element information can include operations S331 to S334.

[0125] First, in operation S331, at least one element position set in the first element extraction method is obtained.

[0126] Exemplarily described in combination with Table 2. In one embodiment, the element position is an axis established with the lower bottom edge of the transaction snapshot as the x-axis, the left side edge as the y-axis, and the left lower endpoint as the origin (0, 0). At this time, each information area in the transaction snapshot can be automatically mapped to a block area position. For example, the area configured by rule serial number 1 with x: 1, 10 && y: 2, 12 represents a rectangular area in the above coordinate axis plane with (1, 2), (10, 2), (1, 12), and (10, 12) as the four vertices.

[0127] Then, in operation S332, the character information in the first element position in the transaction snapshot of the first business scenario is recognized, where the first element position is any one of the at least one element position, such as the element position corresponding to rule serial number 1.

[0128] Next, in operation S333, the first field corresponding to the first element position set in the first element extraction method is obtained. As shown in Table 2, the field name set under rule serial number 1 is DATE1.

[0129] Subsequently, in operation S334, the character information identified from the first element position is extracted and filled into the first field of the transaction data summary table. For example, the OCR recognition technology is used to recognize the character information in the rectangular area with (1, 2), (10, 2), (1, 12), and (10, 12) as the four vertices, and the recognized character information is filled into the DATE1 field of the transaction data summary table (i.e., the MAIN table).

[0130] By extracting the element information at the predefined element positions in the transaction snapshot, the embodiments of the present disclosure can decouple the extracted information from the keywords or fields compared with the method of extracting the corresponding information by recognizing the keywords or fields in the transaction snapshot in some embodiments, and the extraction method is more stable.

[0131] Specifically, the method of extracting the corresponding information based on keyword recognition, for example, can be to recognize the continuous string after the "name of receiving bank" to obtain the name of the receiving bank. However, there are certain drawbacks to this extraction method based on keyword recognition: for example, if the upstream business system changes the "name of receiving bank" to the "Chinese name of receiving bank", then the information of the keyword in the element extraction configuration information must be modified synchronously.

[0132] Compared with the extraction method based on keywords, when extracting element information based on element positions, even if the name of the keyword changes, as long as the position of the element information in the transaction snapshot remains unchanged, there is no need to modify the element extraction configuration information. Moreover, the transaction site data of organizations such as financial institutions usually has a standardized table form, etc., and is generally left-aligned or right-aligned. The maximum character length and character height, etc., are usually set in each table item. Therefore, when extracting element information based on element positions in the manner Figure 6 shown, as long as the distribution of the table items in the table or file recording the transaction site data in the upstream business system does not change, then there is no need to modify the element extraction configuration information.

[0133] Figure 7 Schematically shows a flowchart of automatically processing a transaction snapshot for data reporting in a data reporting method according to an embodiment of the present disclosure.

[0134] As Figure 7 shown, the process of automatically processing the transaction snapshot by the data reporting device 101 or 201 according to the embodiments of the present disclosure may include operation S701 to operation S706.

[0135] First, in operation S701, the scenario configuration information (such as Table 1) is read, and a record of the business scenario to be processed (for example, the scenario ID) is obtained.

[0136] However, in operation S702, according to the file directory set according to the scenario ID rule and the transaction snapshot file name, scan whether there is a pending transaction snapshot in this path. If not, end. If so, continue to execute.

[0137] In operation S703, read the feature extraction method set for this scenario ID in the feature extraction configuration information (as shown in Table 2). If this feature extraction method includes multiple extraction rules, loop through each extraction rule through operations S704 - S706.

[0138] In operation S704, read an extraction rule.

[0139] In operation S705, obtain the feature location. Through OCR image recognition, automatically extract and save the feature information in this location area to the corresponding field in the table set by the rule.

[0140] In operation S706, determine whether the currently processed extraction rule is the last extraction rule under the current scenario ID. If so, end. If not, return to operation S704.

[0141] Figure 8 Schematically shows a flowchart of a data reporting method according to another embodiment of the present disclosure.

[0142] As Figure 8 shown, the data reporting method according to this embodiment may include operations S310 - S330, operations S341 - S343, and operation S850.

[0143] First, through operations S310 - S330, extract the feature data from the transaction snapshot recording the transaction site and summarize it into the transaction data summary table. Among them, the specific implementation of operations S310 - S330 refers to the previous description and will not be elaborated here.

[0144] Next, perform data reporting to the regulatory agency through operations S341 - S343. Among them, operations S341 - S343 are specific embodiments of the aforementioned operation S340.

[0145] Specifically, according to the embodiment of the present disclosure, first in operation S341, verify the data in the corresponding fields of the transaction data summary table according to the data verification rules set according to the data quality specification requirements of the target regulatory system.

[0146] The data verification rules are set according to the data quality specification requirements of the target supervision system. Different supervision systems may have different requirements for the reported data fields and data accuracy, so different data verification rules can be set for different supervision systems. The data verification rules can include the length of each element information, whether it is mandatory, dictionary validity, etc., to ensure the quality of the externally reported data.

[0147] Table 6 shows examples of some data verification rules. When performing verification, the corresponding rule records can be read from Table 6 in combination with the transaction data summary table and looped for judgment. Only after all the rules of all fields in the data verification rules pass the verification can the subsequent external reporting operation be carried out to ensure the quality of the reported data. The description of the key fields involved in the verification rules in Table 6 is as follows:

[0148] Table 6

[0149]

[0150] Rule status: 1 - effective; 0 - ineffective. Through this field, it controls whether this rule needs to be verified by the data reporting verification module 950 or the data reporting verification module 15.

[0151] Effective condition: On the premise that the rule is effective, additional effective conditions can be set through this field. For example, for the rule numbered 1 above, AVALCON is set to $ACTIONTYPE$! = ′D′, indicating that this rule only needs to be executed by the data verification engine when the operation type (ACTIONTYPE) is not delete (D).

[0152] Verification element field: Used to specify the target field for the data verification engine to verify.

[0153] Field length: The data verification engine verifies the length of the target field according to the configured value of this field. If it does not match, the verification fails.

[0154] Verification type: S is a simple rule; F is a complex rule (which can be extended by writing a separate verification function).

[0155] Verification function: When CHKTYPE is configured as F - complex rule, the corresponding verification function of the rule needs to be set through this field. When the data verification engine encounters a complex rule, it invokes the verification function set in this field and returns the verification result according to the execution result of the verification function.

[0156] Is dictionary: Whether to perform dictionary value verification, Y - yes, N - no. Used to specify whether this rule needs to verify the dictionary value validity of the target field.

[0157] Related dictionary value: When ISDICT is set to Y - Yes, this field needs to be configured. For example, for the rule with serial number 1, RELDICT = dic:[T_CPRI_NTHPADIC.COUNTRY], the data verification engine will verify the value of the target field against the dictionary value range of COUNTRY. If the target field value is within the dictionary value range of COUNTRY, the verification passes; otherwise, it fails.

[0158] Next, in operation S342, when the verification passes, the data of the corresponding fields in the transaction data summary table is spliced according to the reporting interface specification of the target supervision system to form the target spliced message.

[0159] Then, in operation S343, the target spliced message is sent to the target supervision system.

[0160] Although the data verification rules of different supervision systems may be different, since data verification in different supervision systems is based on transaction facts, there will theoretically be no conflict in verification rules for the data of the same field in the transaction data summary table. Thus, according to the embodiments of the present disclosure, the data in the transaction data summary table can be verified according to the data verification rules first, and then, when all the rules in the data verification rules pass, it is spliced into a template spliced message for reporting. Compared with the method of splicing the message first and then verifying, the method of verifying first and then splicing the message in the embodiments of the present disclosure is more efficient.

[0161] After reporting the data, in operation S850, the transaction snapshots of each business scenario can be archived according to the archiving policy set for each business scenario. The archiving policy settings can be set for each business scenario, as shown in Table 7.

[0162] The archiving policies exemplified in Table 7 may include 1: Online archiving; 2: Offline archiving; 3: Data cleaning. Among them, online archiving can be archiving in the storage device of the data reporting device 101 or 201, or in the storage device of the business system where the transaction occurs. Offline archiving can be stored on disks or tapes. Data cleaning can specify the number of days of the archiving period, and the transaction snapshots exceeding the specified archiving period days are cleared.

[0163] According to some embodiments of the present disclosure, after reporting data to the regulatory agency, the transaction snapshots can also be archived for easy traceability.

[0164] Table 7

[0165]

[0166] Based on the data reporting methods of the above various embodiments, the embodiments of the present disclosure also provide a data reporting device. The following will be combined with Figure 9 andFigure 10 Describe the device in detail.

[0167] Figure 9 FIG. schematically shows a block diagram of a data reporting device 900 according to an embodiment of the present disclosure.

[0168] As Figure 9 shown, the data reporting device 900 according to this embodiment may include a transaction site receiving module 910, a reporting data automatic processing module 920, and an external connection reporting module 930. Among them, the reporting data automatic processing module 920 may include a snapshot storage module 921 and a feature extraction module 922. According to some other embodiments of the present disclosure, the data reporting device 900 may further include at least one of a rule library module 940, a reporting data verification module 950, and a transaction site archiving module 960. The data reporting device 900 may execute the method described in reference Figures 3 - 8 .

[0169] Specifically, the transaction site receiving module 910 is configured to receive transaction snapshots of at least one business scenario. In one embodiment, the transaction site receiving module 910 may perform the operation S310 described above.

[0170] The snapshot storage module 921 is configured to store the transaction snapshot of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information when any first business scenario in at least one business scenario belongs to the business scenarios in the scenario configuration information. In one embodiment, the snapshot storage module 921 may perform the operation S320 described above.

[0171] The feature extraction module 922 is configured to extract feature information from the stored transaction snapshots according to the requirement extraction method configured in the feature extraction configuration information for extracting feature information from the transaction snapshots of each business scenario, and summarize it into a transaction data summary table. In one embodiment, the feature extraction module 922 may perform the operation S330 described above.

[0172] The external connection reporting module 930 is configured to report data to at least one regulatory system based on the transaction data summary table. In one embodiment, the external connection reporting module 930 may perform the operation S340 described above.

[0173] The rule library module 940 is used to configure the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data reported according to the requirements of at least one regulatory system, where the at least one regulatory system includes the target regulatory system. In some embodiments, the rule library module 940 is further used to, when the business scenarios involved in the data reported according to the requirements of at least one regulatory system change, correspondingly change the scenario configuration information, and after changing the scenario configuration information, correspondingly change the element extraction method of the business scenarios changed in the element extraction configuration information. In one embodiment, the rule library module 940 may perform with reference to the operation process described above Figure 4 in the foregoing text.

[0174] In some other embodiments, the rule library module 940 is used to configure the element information corresponding to the element fields and their extraction methods in the element extraction configuration information according to the element fields involved in the data reported according to the requirements of at least one regulatory system; where, when the element fields involve multiple business scenarios, the element information corresponding to the element fields and their extraction methods are respectively configured in the multiple business scenarios in the element extraction configuration information. In some other embodiments, the rule library module 940 is further used to, when the element fields of the data reported according to the requirements of at least one regulatory system change, correspondingly change the element extraction configuration information. In one embodiment, the rule library module 940 may perform with reference to the operation process described above Figure 5 in the foregoing text.

[0175] The data submission verification module 950 is used to verify the data of the corresponding fields in the transaction data summary table according to the data verification rules set according to the data quality specification requirements of the target regulatory system before the external connection submission module 930 submits data to at least one regulatory system, and the target regulatory system is any one of the at least one regulatory system. Correspondingly, the external connection submission module 930 is used to splice the data of the corresponding fields in the transaction data summary table according to the submission interface specification of the target regulatory system in the case of passing the verification, form the target spliced message and send the target spliced message to the target regulatory system. In one embodiment, the data submission verification module 950 may perform the operation S341 described above, and the external connection submission module 930 may perform the operations S342 to S343 described above.

[0176] The transaction site archiving module 960 is used to archive the transaction snapshots of each business scenario according to the archiving policy set for each business scenario. In one embodiment, the transaction site archiving module 960 may perform the operation S850 described above.

[0177] According to an embodiment of the present disclosure, any plurality of modules among the transaction site receiving module 910, the reported data automatic processing module 920, the external connection reporting module 930, the rule library module 940, the reported data verification module 950, and the transaction site archiving module 960 can be combined and implemented in one module, or any one of them can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the transaction site receiving module 910, the reported data automatic processing module 920, the external connection reporting module 930, the rule library module 940, the reported data verification module 950, and the transaction site archiving module 960 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on chip, a system on substrate, a system on package, an application specific integrated circuit (ASIC), or can be implemented by any other reasonable means such as integrating or packaging circuits, etc., in hardware or firmware, or implemented in any one of the three implementation manners of software, hardware, and firmware, or in an appropriate combination of any several of them. Alternatively, at least one of the transaction site receiving module 910, the reported data automatic processing module 920, the external connection reporting module 930, the rule library module 940, the reported data verification module 950, and the transaction site archiving module 960 can be at least partially implemented as a computer program module, and when the computer program module is run, it can execute the corresponding functions.

[0178] Figure 10 Schematically shows a block diagram of a data reporting device 10 according to another embodiment of the present disclosure.

[0179] As Figure 10 shown, the data reporting device 10 may include a parameter configuration module 11, a rule library module 12, a transaction site receiving module 13, a reported data automatic processing module 14, a reported data verification module 15, an external connection reporting module 16, a transaction site archiving module 17, a traceability confirmation module 18, and a data storage module 19. The data reporting device 10 is a specific embodiment of the data reporting device 900. Correspondingly, the modules with the same name in the data reporting device 10 are embodiments of the data reporting device 900. The functions of each module of the data reporting device 10 are described in detail as follows.

[0180] Parameter configuration module 11: Responsible for configuring the parameters required by this device, such as network connection parameters, transaction site archiving directory path, external connection reporting path, device operation start and stop time, etc.

[0181] Rule library module 12: Responsible for configuring various information required by this device, including the scenario configuration information elements mentioned above (as shown in Table 1), element extraction configuration information (as shown in Table 2), data verification rules (as shown in Table 6), and archiving strategies (as shown in Table 7).

[0182] Transaction site receiving module 13: Responsible for receiving transaction snapshots transmitted by each business system, and creating different file directories according to the business scenarios to which different upstream product systems belong, so as to facilitate the storage and / or naming of transaction snapshots according to the scenario configuration information for use by the reported data automatic processing module 14.

[0183] Reported data automatic processing module 14: According to the scenario configuration information and element extraction configuration information configured by the rule library module 12, read the transaction snapshots in the file directory of the transaction site receiving module 13, and automatically extract element information from the transaction snapshots according to the element extraction method of the business scenario and save it to the reported information table (as Figure 6 shown). The processing flow of the reported data automatic processing module 14 can refer to the schematic diagram in Figure 7 .

[0184] Reported data verification module 15: Verify the reported data generated from the element information extracted by the reported data automatic processing module 14, obtain each rule from the data verification rule library shown in, for example, Table 6, and perform verification one by one. If all verifications pass, the data is set to the to-be-reported status; otherwise, it is updated to the to-be-confirmed status.

[0185] External connection reporting module 16: Responsible for interacting with the external supervision system, including reporting the to-be-reported data that has passed verification to the supervision system; receiving the processing result returned by the supervision system. Update the data status to reported successfully or reported failed according to the returned result.

[0186] Transaction site archiving module 17: Read the archiving strategy in the rule library module 12, and upload the transaction snapshots that have completed the automatic processing of reported information to the archiving path for archiving and future reference.

[0187] Traceability confirmation module 18: Provide traceability confirmation operations for data in the to-be-confirmed and reported failed statuses, retrieve the transaction snapshots from the archiving path according to this piece of data, so that business personnel can confirm, improving the operation convenience without having to query information by logging in to the upstream business system again.

[0188] Data storage module 19: Responsible for storing transaction snapshots, spliced messages, and parameter rules during the device processing process.

[0189] The data reporting device 10 automatically reports data based on transaction snapshots, which can well solve the problem of large workload of relevant system adaptation and transformation brought about by the adjustment of the regulatory reporting data interface. At the same time, it can quickly support business personnel to trace and confirm the reported data, reduce the management cost of regulatory reporting data, and improve the data reporting efficiency.

[0190] Figure 11 A block diagram of an electronic device 1100 suitable for implementing the data reporting method according to an embodiment of the present disclosure is schematically shown.

[0191] As Figure 11 shown, the electronic device 1100 according to an embodiment of the present disclosure includes a processor 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage section 1108 into a random access memory (RAM) 1103. The processor 1101 may include, for example, a general microprocessor (e.g., CPU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (e.g., an application specific integrated circuit (ASIC)), etc. The processor 1101 may also include on-board memory for caching purposes. The processor 1101 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0192] In the RAM 1103, various programs and data required for the operation of the electronic device 1100 are stored. The processor 1101, the ROM 1102, and the RAM 1103 are connected to each other through a bus 1104. The processor 1101 performs various operations of the method flow according to an embodiment of the present disclosure by executing the programs in the ROM 1102 and / or the RAM 1103. It should be noted that the program may also be stored in one or more memories other than the ROM 1102 and the RAM 1103. The processor 1101 may also perform various operations of the method flow according to an embodiment of the present disclosure by executing the programs stored in one or more memories.

[0193] According to an embodiment of the present disclosure, the electronic device 1100 may further include an input / output (I / O) interface 1105, and the input / output (I / O) interface 1105 is also connected to the bus 1104. The electronic device 1100 may further include one or more of the following components connected to the I / O interface 1105: an input portion 1106 including a keyboard, a mouse, etc.; an output portion 1107 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage portion 1108 including a hard disk, etc.; and a communication portion 1109 including a network interface card such as a LAN card, a modem, etc. The communication portion 1109 performs communication processing via a network such as the Internet. The drive 1110 is also connected to the I / O interface 1105 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed so that a computer program read therefrom can be installed into the storage portion 1108 as needed.

[0194] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist separately without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to the embodiments of the present disclosure is implemented.

[0195] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program can be used by or combined with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the above-described ROM 1102 and / or RAM 1103 and / or one or more memories other than ROM 1102 and RAM 1103.

[0196] An embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes program codes for executing the method shown in the flowchart. When the computer program product runs in a computer system, the program codes are used to cause the computer system to implement the method provided by the embodiments of the present disclosure.

[0197] When the computer program is executed by the processor 1101, the above functions defined in the system / apparatus of the embodiments of the present disclosure are performed. According to the embodiments of the present disclosure, the above-described systems, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0198] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and be downloaded and installed through the communication part 1109, and / or be installed from the removable medium 1111. The program code included in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0199] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1109, and / or be installed from the removable medium 1111. When the computer program is executed by the processor 1101, the above functions defined in the system of the embodiments of the present disclosure are performed. According to the embodiments of the present disclosure, the above-described systems, devices, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0200] According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level procedures and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include but are not limited to, such as Java, C++, python, the "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, by using an Internet service provider to connect through the Internet).

[0201] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur in a different order than that noted in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0202] Those skilled in the art will appreciate that the features recited in the various embodiments and / or claims of the present disclosure can be combined and / or combined in various ways, even if such combinations and / or combinations are not explicitly recited in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features recited in the various embodiments and / or claims of the present disclosure can be combined and / or combined in various ways. All such combinations and / or combinations fall within the scope of the present disclosure.

[0203] The embodiments of the present disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments have been described separately above, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and all such substitutions and modifications should fall within the scope of the present disclosure.

Claims

1. A data reporting method, comprising: Receiving transaction snapshots of at least one business scenario; wherein each transaction snapshot is an image information formed by a business system taking a screenshot or a photo of the transaction site of a transaction therein; When any first business scenario in the at least one business scenario belongs to the business scenarios in the scenario configuration information, storing the transaction snapshots of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information; wherein the file directories of various business scenarios are pre-configured in the scenario configuration information; Extracting element information from the stored transaction snapshots of each business scenario according to the element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario, and summarizing it into a transaction data summary table; wherein the element extraction methods of the transaction snapshots of each business scenario are pre-configured in the element extraction configuration information; the element information includes character information; wherein the element information from the same transaction snapshot forms a record in the transaction data summary table; and Reporting data to at least one supervision system based on the transaction data summary table.

2. The method according to claim 1, wherein, The scenario configuration information is obtained through the following method: Configuring the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data required to be reported by the at least one supervision system.

3. The method according to claim 2, wherein The configuring the business scenarios and their file directories in the scenario configuration information according to the business scenarios involved in the data required to be reported by the at least one supervision system further includes: When the business scenarios involved in the data required to be reported by the at least one supervision system change, correspondingly changing the scenario configuration information; and After changing the scenario configuration information, correspondingly changing the element extraction method of the business scenario changed in the element extraction configuration information.

4. The method according to claim 1, wherein, The element extraction configuration information is obtained through the following method: Configuring the element information corresponding to the element field and its extraction method in the element extraction configuration information according to the element field involved in the data required to be reported by the at least one supervision system; Wherein, When the element field involves multiple business scenarios, configuring the element information corresponding to the element field and its extraction method respectively in the multiple business scenarios in the element extraction configuration information.

5. The method according to claim 4, wherein The configuring the element information corresponding to the element field and its extraction method in the element extraction configuration information according to the element field involved in the data required to be reported by the at least one supervision system further includes: When the element field of the data required to be reported by the at least one supervision system changes, correspondingly changing the element extraction configuration information.

6. The method according to claim 1, wherein The extracting element information from the stored transaction snapshots according to the element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario includes: Extracting element information from the transaction snapshots of the first business scenario according to the first element extraction method configured in the element extraction configuration information corresponding to the first business scenario, including: Obtain at least one element position set in the first element extraction method; Identify the character information in the first element position in the transaction snapshot of the first business scenario, where the first element position is any one of the at least one element position; Obtain the first field corresponding to the first element position set in the first element extraction method; and Extract the character information identified from the first element position and fill it into the first field of the transaction data summary table.

7. The method according to claim 1, wherein The data reporting based on the transaction data summary table to at least one supervision system includes: Verify the data of the corresponding field in the transaction data summary table according to the data verification rules set according to the data quality specification requirements of the target supervision system; the target supervision system is any one of the at least one supervision system; When the verification passes, splice the data of the corresponding field in the transaction data summary table according to the reporting interface specification of the target supervision system to form a target spliced message; and Send the target spliced message to the target supervision system.

8. The method according to claim 1, wherein The method further includes: Archive the transaction snapshots of each business scenario according to the archiving policy set for each business scenario.

9. A data reporting device, comprising: A transaction site receiving module, configured to receive transaction snapshots of at least one business scenario, where each transaction snapshot is an image information formed by a business system taking a screenshot or a photo of the transaction site of a transaction therein; A snapshot storage module, configured to store the transaction snapshot of the first business scenario according to the first file directory configured for the first business scenario in the scenario configuration information when any first business scenario in the at least one business scenario belongs to the business scenarios in the scenario configuration information; wherein, the file directories of various business scenarios are pre-configured in the scenario configuration information; An element extraction module, configured to extract element information from the stored transaction snapshots of each business scenario according to the element extraction method configured in the element extraction configuration information for extracting element information from the transaction snapshots of each business scenario, and summarize it into a transaction data summary table; wherein, the element extraction methods of the transaction snapshots of each business scenario are pre-configured in the element extraction configuration information; the element information includes character information; wherein, the element information from the same transaction snapshot forms a record in the transaction data summary table; and An external connection reporting module, configured to report data to at least one supervision system based on the transaction data summary table.

10. An electronic device, comprising: One or more processors; A memory, configured to store one or more programs, wherein, when the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.

12. A computer program product comprising computer program instructions which, when executed by a processor, implement the method according to any one of claims 1 to 8.

Images