CN115114233A - Data transmission method, device, equipment and medium - Google Patents

Abstract

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

Description

Data transmission method, device, equipment and medium

Technical Field

The present disclosure relates to the field of information security, which may be used in the field of finance or other fields, and more particularly, to a method, apparatus, device, medium, and program product for data reporting.

Background

At present, financial institutions such as banks need to report corresponding supervision data to supervision institutions according to supervision requirements in the process of exhibition industry. The related data types are more, and the reported data source is usually corresponding to a plurality of service systems. In the prior art, a common scheme for data reporting is to use an independent data reporting system as a bridge between a financial institution and a supervisory institution, on one hand, receive data files of various upstream business systems of the financial institution and perform unified processing, and on the other hand, report the uniformly processed data to the supervisory institution according to reporting requirements.

In the process of implementing the inventive concept, the inventor finds that the prior art has the following defects: because the reporting data relates to a plurality of business systems, when the data reporting system is developed, a large number of upstream and downstream file interfaces or online interfaces are required to be negotiated, determined, developed and tested. Moreover, when the data specification required to be reported by the regulatory agency changes, the interfaces that interface with the upstream service system often need to be modified in a matching manner, and the modification workload is large.

Disclosure of Invention

In view of the foregoing, the present disclosure provides data delivery methods, apparatuses, devices, media and program products that greatly facilitate interfacing efficiency with upstream traffic systems.

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

According to an embodiment of the present disclosure, the scene configuration information is obtained by: and configuring the service scenes and file directories thereof in the scene configuration information according to the service scenes related to the data required to be reported by the at least one monitoring system, wherein the at least one monitoring system comprises the target monitoring system.

According to an embodiment of the present disclosure, configuring the service scenario and its file directory in the scenario configuration information according to the service scenario related to the data required to be reported by the at least one monitoring system further includes: when the business scene related to the data requested to be reported by the at least one monitoring system is changed, correspondingly changing the scene configuration information, and after the scene configuration information is changed, correspondingly changing the element extraction mode of the changed business scene in the element extraction configuration information.

According to an embodiment of the present disclosure, the element extraction configuration information is obtained by: and according to the element field related to the data required to be reported by the at least one supervision system, configuring the element information corresponding to the element field in the element extraction configuration information and the extraction mode thereof. When the element field relates to a plurality of business scenes, element information corresponding to the element field and an extraction mode thereof are respectively configured in the plurality of business scenes in the element extraction configuration information.

According to an embodiment of the present disclosure, the configuring, according to the element field related to the data requested to be submitted by the at least one monitoring system, the element information corresponding to the element field in the element extraction configuration information and the extraction manner thereof further include: when the element field of the data required to be reported by the at least one supervision system is changed, the element extraction configuration information is correspondingly changed.

According to an embodiment of the present disclosure, the extracting element information from the stored transaction snapshot according to an element extraction manner configured in the element extraction configuration information and used for extracting element information from the transaction snapshot of each service scenario includes: and extracting element information from the transaction snapshot of the first service scene according to a first element extraction mode corresponding to the first service scene and configured in the element extraction configuration information. The method specifically comprises the following steps: acquiring at least one element position set in the first element extraction mode; identifying character information in a first element position in a transaction snapshot of the first service scene, wherein the first element position is any one element position in the at least one element position; acquiring a first field corresponding to the position of the first element and arranged in the first element extraction mode; and extracting character information identified from the first component location for filling into the first field of the transaction data summary table.

According to an embodiment of the present disclosure, said reporting data to at least one regulatory system based on said transaction data summary table comprises: verifying data of corresponding fields in the transaction data summary table according to a data verification rule set according to the requirement of a target supervision system on data quality specifications, wherein the target supervision system is any one of the at least one supervision system; under the condition that the verification is passed, splicing data of corresponding fields in the transaction data summary table according to the submission interface specification of the target supervision system to form a target splicing message; and sending the target splicing message to the target supervision system.

According to an embodiment of the present disclosure, the method further comprises: and archiving the transaction snapshot of each business scene according to the archiving strategy set for each business scene.

In a second aspect of the disclosed embodiment, a data reporting apparatus is provided. The device comprises: the system comprises a transaction field receiving module, an automatic submitting data processing module and an external connection submitting module. The automatic submitting data processing module comprises a snapshot storage module and an element extraction module. The transaction scene receiving module is used for receiving transaction snapshots of at least one service scene. The snapshot storage module is configured to, when any first service scenario in the at least one service scenario belongs to a service scenario in scenario configuration information, store a transaction snapshot of the first service scenario according to a first file directory configured for the first service scenario in the scenario configuration information. The element extraction module is used for extracting element information from the stored transaction snapshots according to an element extraction mode which is configured in the element extraction configuration information and used for extracting the element information from the transaction snapshots of each service scene, and summarizing the element information to a transaction data summary table. And the external connection reporting module is used for reporting data to at least one supervision system based on the transaction data summary table.

According to an embodiment of the present disclosure, the apparatus further comprises a rule base module. The rule base module is used for configuring the service scene and the file directory thereof in the scene configuration information according to the service scene related to the data required to be reported by at least one monitoring system, wherein the at least one monitoring system comprises the target monitoring system. According to an embodiment of the present disclosure, the rule base module is further configured to correspondingly change the scene configuration information when a business scene related to data required to be reported by the at least one monitoring system is changed, and correspondingly change an element extraction manner of the changed business scene in the element extraction configuration information after the scene configuration information is changed.

According to the embodiment of the disclosure, the rule base module is used for configuring the element information corresponding to the element field in the element extraction configuration information and the extraction mode thereof according to the element field related to the data reported by at least one supervision system; wherein, when the element field relates to a plurality of service scenes, the element information corresponding to the element field and the extraction mode thereof are respectively configured in the plurality of service scenes in the element extraction configuration information. According to another embodiment of the disclosure, the rule base module is further configured to extract configuration information corresponding to an element when an element field of data required to be submitted by the at least one supervision system is changed.

According to an embodiment of the present disclosure, the apparatus further comprises a submission data verification module. The submission data checking module is used for checking data of corresponding fields in the transaction data summary table according to a data checking rule set according to the requirement of a target supervision system on data quality specifications; the target supervisory system is any one of the at least one supervisory system. And the external connection reporting module is used for splicing data of corresponding fields in the transaction data summary table according to the reporting interface specification of the target monitoring system under the condition that the verification is passed, forming a target splicing message and sending the target splicing message to the target monitoring system.

In a third aspect of the disclosed embodiments, 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 which, when executed by the one or more processors, cause the one or more processors to perform the above-described method.

In a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon executable instructions, which when executed by a processor, cause the processor to perform the above-mentioned method.

In a fifth aspect of the embodiments of the present disclosure, there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the above method.

One or more of the embodiments described above have the following advantages or benefits: the configuration information is extracted through the scene configuration information and the elements, so that only transaction snapshots can be transmitted when the system is in butt joint with various upstream business systems, specific file types, data types and the like do not need to be distinguished, interfaces do not need to be designed for different upstream business systems according to business scenes, and the design and development of the interfaces with the upstream business systems are simplified in the mode.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

fig. 1 schematically illustrates a system architecture diagram of a data transmission method and apparatus according to an embodiment of the present disclosure;

fig. 2 schematically illustrates a system architecture diagram of a data transmission method and apparatus according to another embodiment of the present disclosure;

fig. 3 schematically illustrates a flow chart of a data transmission method according to an embodiment of the present disclosure;

fig. 4 schematically shows a flowchart for configuring scene configuration information in a data transmission method according to an embodiment of the present disclosure;

fig. 5 schematically shows a flowchart of configuration element extraction configuration information in a data transmission method according to an embodiment of the present disclosure;

fig. 6 schematically illustrates a flow chart of a method of extracting element information from a transaction snapshot in a data reporting method according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a flow diagram for automatically processing a transaction snapshot for posting data in a data posting method according to an embodiment of the present disclosure;

fig. 8 schematically shows a flow chart of a data transmission method according to another embodiment of the present disclosure;

FIG. 9 schematically illustrates a block diagram of a datagram device according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a datagram device according to another embodiment of the present disclosure; and

fig. 11 schematically shows a block diagram of an electronic device adapted to implement a data transmission method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more features.

In view of the problems that in the prior art, when data is sent, various data interaction interfaces need to be negotiated and determined with each upstream service system, which causes a complicated development process, and the amount of interface modification is large after the monitored data is changed, the embodiments of the present disclosure provide a data sending method, apparatus, device, medium, and program product that can improve the efficiency of interfacing with each service system.

The key points of the embodiments of the present disclosure mainly include two aspects: firstly, by pre-configuring file directories of various service scenes in scene configuration information, transaction snapshots for recording transaction field information from various service systems can be stored in corresponding directories according to the service scenes to which the transaction snapshots belong; and secondly, element information such as characters and the like required to be reported can be extracted from the transaction snapshots of each service scene by pre-configuring the element extraction mode of the transaction snapshots in each service scene in the element extraction configuration information, so that the original data required to be reported can be extracted from the transaction snapshots, and subsequent data processing (such as data gathering and integration, verification, message formation and sending and the like) is facilitated.

Therefore, the configuration information is extracted through the scene configuration information and the elements, so that only transaction snapshots can be transmitted when the upstream business systems are in butt joint, specific file types, data types and the like do not need to be distinguished, interfaces do not need to be designed for different upstream business systems according to business scenes and file types, and the design and development of the interfaces with the upstream business systems are simplified.

Meanwhile, according to the embodiment of the disclosure, when the data specification required to be reported by the supervision agency changes, the purpose of changing the available transaction snapshot and/or the element information in the transaction snapshot can be achieved by changing the service scene related to the scene configuration information and/or changing the element extraction mode related to the element extraction configuration information. Thus, according to the embodiment of the disclosure, when the data specification required to be submitted by a supervision organization changes, the data submission can be quickly realized only by changing corresponding scene configuration information and/or elements to extract the configuration information without carrying out a large amount of interface modification, so that the efficiency of the data submission is greatly improved, and the workload of developers is reduced.

Moreover, according to the embodiment of the disclosure, transaction snapshots of each business scenario can be archived, so that subsequent tracing and confirmation are facilitated. The trouble that in the prior art, once the reported data is in problem, the data is required to be logged in the original service system again for inquiry and confirmation is avoided.

In the technical scheme of the disclosure, the processes of collecting, storing, using, processing, transmitting, providing, disclosing and applying the personal information (for example, existing in the transaction snapshot) of the related user are all in accordance with the regulations of related laws and regulations, and necessary security measures are taken without violating the customs of the public order.

It should be noted that the data transmission method and apparatus determined by the embodiment of the present disclosure may be used in the financial field, and may also be used in any field other than the financial field, and the application field is not limited by the present disclosure.

Fig. 1 schematically shows a system architecture diagram of a data transmission method and apparatus according to an embodiment of the present disclosure.

As shown in fig. 1, in the system architecture 100, a datagram device 101 according to an embodiment of the present disclosure may be connected in series with an original datagram system 102, and together serve as a bridge for interfacing between at least one service system and at least one monitoring system. Wherein the at least one business system is illustrated in system architecture 100 as including a plurality of business systems, e.g., business system 1, business system 2, business system 3, business system 4. The at least one regulatory system is exemplified in the system architecture 100 as including a plurality of regulatory systems, e.g., a system of regulatory agency 1, a system of regulatory agency 2. The system architecture 100 may be obtained by modifying the original distribution system flow of a financial institution such as a bank.

The data reporting device 101 may execute the data reporting method according to the embodiment of the present disclosure, store the transaction snapshot from the upstream service system according to the file directory in the scene configuration information, extract the element information according to the element extraction manner configured in the element extraction configuration information, summarize the extracted element information to the transaction data summary table, and then perform subsequent data reporting according to the data in the transaction data summary table.

The original data reporting system 102 can only serve as an information exchange channel with the system of the external monitoring authority, and does not take over the function of data processing.

In one embodiment, the data processing flow of the data delivery device 101 may include: firstly, a transaction snapshot sent by an upstream service system is received, configuration information is extracted according to scene configuration information and elements, data information needing to be reported is automatically extracted from the transaction snapshot through, for example, Optical Character Recognition (OCR), then, according to the requirement of a supervisory organization to report the data, the data is checked and a message is formed, and the message is sent to an original data reporting system 102 for data reporting.

In some embodiments, the data reporting device 101 may fall into the entry-complementing status for the data that fails to pass the verification, and the data is modified after being confirmed by the service personnel. The business personnel in the confirmation link can directly call the transaction snapshot for tracing without logging in an upstream business system (such as the business system 1, the business system 2, the business system 3, the business system 4, the business system n).

In some embodiments, the data submission device 101 may further receive a submission data processing result fed back by at least one supervision system (e.g., a system of the supervision organization 1, a system of the supervision organization 2, and/or a system of the supervision organization m), and update the status to submission success for data successfully processed by the supervision system; and for the data which are returned by the supervision system and fail to be processed, updating the state into reporting failure, and rectifying and correcting the data after being confirmed by service personnel. And service personnel in the confirmation link can directly call a transaction site to trace the source without logging in an upstream service system.

Fig. 2 schematically illustrates a system architecture diagram of a data transmission method and apparatus according to another embodiment of the present disclosure.

It should be apparent that the data reporting apparatus 201 according to the embodiment of the present disclosure may also report data to at least one monitoring system (e.g., the system of the monitoring authority 1, the system of the monitoring authority 2,. and/or the system of the monitoring authority m) by using the connection manner in the system architecture 200 shown in fig. 2 as a bridge between at least one business system and at least one monitoring system. Among them, the data transmission device 201 may execute the data transmission method of the embodiment of the present disclosure.

According to the embodiment of the present disclosure, no matter the system architecture 100 or 200 is, the business system only needs to save the picture snapshot of the transaction site to obtain the transaction snapshot, and then transmit the transaction snapshot to the data reporting device 101 or 201, and the data reporting device 101 or 201 can automatically extract the element information in the transaction snapshot by using, for example, an OCR image recognition technology according to the pre-configured scene configuration information and the snapshot processing manner in the business scene configured in the element extraction configuration information. Then, the extracted element information can be used for data reporting, for example, the messages are spliced according to the reporting interface specification and are reported to the outside after the data to be reported passes the verification.

According to an embodiment of the present disclosure, the datagram apparatus 101 or 201 may be embodied as at least one of the datagram apparatus 900, the datagram apparatus 10, the electronic device 1100, the readable storage medium and the computer program product described below, for performing the reporting method described below with fig. 3 to 8. Reference is made in detail to the following description.

Fig. 3 schematically shows a flow chart of a data transmission method according to an embodiment of the present disclosure.

As shown in fig. 3, the data transmission method according to the embodiment may include operations S310 to S340.

First, in operation S310, a transaction snapshot of at least one business scenario is received.

A transaction snapshot is image information formed by a business system by screenshot or photographing a transaction site of one transaction.

The transaction snapshot is mainly used for recording transaction original information and recording transaction sites which are not changed after the transaction is successful. For example, a bank remittance system submits a remittance application form according to application information of a client, and after receiving a remittance success notification, a transaction snapshot of a remittance service can be obtained by screen capturing or photographing transaction record information of remittance transaction. The screen capturing or photographing process can be realized through a background program in the service system. For example, a program may be written, and after the business system receives a trigger signal indicating that the transaction is successful, a page for recording the information of the transaction scene is automatically captured or photographed.

Then, in operation S320, when any first service scenario in the at least one service scenario belongs to a service scenario in the scenario configuration information, a transaction snapshot of the first service scenario is stored according to a first file directory configured for the first service scenario in the scenario configuration information.

The scene configuration information is used for defining the business scenes of data report of the upstream business system and information such as a transaction snapshot file directory in each business scene.

Table 1 illustrates the contents of part of scene configuration information. For example, a service scenario with a scenario ID of 000001 is defined as: and international reimbursement data needing to be submitted in service transaction generated by the AAA service system, wherein the submission type is BOP.

TABLE 1

Scene ID

Scene description

Upstream service system

Type of submission

Transaction snapshot file directory

Name of transaction snapshot

Effective mark

000001

International reimbursement data declaration

AAA

BOP

\AAA\

AAA_00001

0

000002

International reimbursement data declaration

BBB

BOP

\BBB\

AAB__00001

0

000003

External debt data declaration

CCC

XXX

\XXX\

APL988XXX

0

......

In one embodiment, the data distribution device 101 or 201 may provide the scene configuration information to the business systems (such as business system 1, business system 2, business system 3, business system 4, business system n) connected to the business systems, and each business system may transmit the transaction snapshot to the data distribution device 101 or 201 according to the file directory corresponding to the business scene in its business, so that the data distribution device 101 or 201 may store the transaction snapshot in the file directory. For example, according to the scenario configuration information in table 1, the AAA service system may name the transaction snapshot generated therein in the form of "AAA _ (file sequence number)" (e.g., AAA _00001), and transmit the transaction snapshot to the file directory \ AAA \ of the data delivery apparatus 101 or 201.

In another embodiment, the datagram device 101 or 201 may provide a uniform snapshot receiving interface for all service systems connected thereto, then determine the service system that sends the transaction snapshot and the service scenario to which the transaction snapshot belongs according to the attribute (for example, naming information, source system, source port or protocol, etc.) of the received transaction snapshot, and further store the transaction snapshot in the file directory corresponding to the service scenario to which the transaction snapshot belongs according to the scenario configuration information.

Therefore, the embodiment of the present disclosure effectively solves the problem of interfacing between the data reporting device 101 or 201 and the upstream service system through the scene configuration information, and can automatically store the transaction snapshot from the upstream service system in a specific location.

Next, in operation S330, the element information is extracted from the stored transaction snapshots according to the element extraction manner configured in the element extraction configuration information for extracting the element information from the transaction snapshot of each service scenario, and is summarized into a transaction data summary table.

In one embodiment, the service scenario in the element extraction configuration information coincides with the service scenario in the scenario configuration information. Therefore, the corresponding element extraction mode can be provided for the transaction snapshot of each service scene.

According to the embodiment of the present disclosure, in the element extraction configuration information, a set of element extraction methods may be configured for each service scenario.

The extracted element information may be specifically character information recognized from the transaction snapshot, and may be character data recognized by an OCR character recognition technology, for example.

The extracted element information is summarized to the transaction data summary table, for example, after character data of a certain element position or field is identified in the transaction snapshot, the identified character data is correspondingly filled in the transaction data summary table according to a predefined mapping relation between the identified element position or field and the field in the transaction data summary table. The information elements from the same transaction snapshot form a record in the transaction data summary table, namely, the record corresponds to a transaction. As exemplified below in connection with table 2.

Table 2 illustrates a part of the contents of the element extraction configuration information. In this element extraction method, a plurality of information extraction rules are arranged for a scene 000001. Specifically, the fact that multiple rows of records are corresponding to the scene ID000001 in table 2 means that element information can be identified from multiple element positions for each transaction snapshot in the scene 000001, and the identified element information is filled in corresponding fields of the data table according to the table name and the field name corresponding to each element position.

For example, the implementation process of element extraction according to the rule with rule number 1 in table 2 is as follows: the data to be transmitted from the transaction context file AAA _00001 is represented by x: 1, 10& & y: 2, 12, the information in the element position determined is automatically identified and extracted and stored in the MAIN table (i.e., transaction data summary table) DATE1 field as the element value of FILE1 of the submission type BOP. As for a specific process of extracting the factor information according to the manner shown in table 2, the detailed description in fig. 6 below may be referred to.

TABLE 2

Note that, in the element extraction method in table 2, it is only one possible embodiment to recognize and extract the element information from the image range defined by the element position. In other embodiments, the element extraction mode may also be to perform OCR recognition on the whole transaction snapshot, and then extract information of some fields from the recognition result and fill the information in corresponding fields of the transaction summary table.

Thereafter, in operation S340, data is reported to at least one regulatory system based on the transaction data summary table.

In an embodiment, information of corresponding fields may be extracted from a transaction data summary table and spliced into a message according to a message receiving specification of a monitoring system (hereinafter referred to as a target monitoring system) that receives reported data, then, data in the message is checked (for example, whether the data is compliant, whether a data format of each field is correct, and the like), and after all the checks are passed, the spliced message is sent to the target monitoring system.

In another embodiment, the data of the corresponding field in the transaction data summary table requiring reporting in the time period may be checked according to the standard requirement of the target monitoring system on the reported data, and after all the check requirements are checked, the data are spliced according to the message receiving standard of the target monitoring system to form a message, and then the message is sent to the target monitoring system.

And for the data or the message which is not verified, sending a notification that the verification is not passed, manually confirming or rectifying the information that the verification is not passed, and verifying again after the rectification is finished.

Further, in some embodiments, a processing result of the target monitoring system on the report data may also be received. And when the processing result represents that the delivery is successful, updating the state of the delivery data to be the successful delivery. When the processing result represents that the delivery fails, the state of the delivery data can be updated to be the delivery failure, and then the service personnel can correct and modify the delivery data after confirming the delivery failure. According to the embodiment of the disclosure, in the confirmation link, the service personnel can directly call the transaction snapshot stored in the data reporting device 101 or 201 to trace the source without logging in the upstream service system.

It can be seen that, in the embodiment of the present disclosure, the scene configuration information may be used to instruct, on one hand, the upstream service system or the data reporting device 101 or 201 to store the transaction snapshot according to the file directory corresponding to the service scene, and on the other hand, may also be used to instruct the data reporting device 101 or 201 to read the transaction snapshot from the corresponding directory according to the service scene and extract the element information from the transaction snapshot according to the element extraction manner of the service scene.

In this way, by extracting configuration information through the scene configuration information and the elements, only a transaction snapshot may be transmitted when the datagram device 101 or 201 interfaces with various upstream business systems, without distinguishing a specific file type, a data type, and the like, or designing interfaces for different upstream business systems according to business requirements, in this way, fig. 4, which implements datagram, schematically shows a flowchart of configuring scene configuration information in the data datagram method according to the embodiment of the present disclosure.

Specifically, as shown in fig. 4, the process of configuring the scene configuration information according to this embodiment may include operations S410 to S440. Wherein the scene configuration information may be configured before operation S310.

In operation S410, according to the service scenario related to the data requested to be reported by the at least one monitoring system, the service scenario and its file directory in the scenario configuration information are configured. As shown in table 1.

In operation S420, it is detected whether a notification of a change in a service scenario related to data requested to be posted by at least one supervisory system is received. If the notification is received, operation S430 is performed; if the notification is not received, the scene configuration information configured in S410 is used. The service scene change may include deletion, addition, or replacement of the service scene.

In operation S430, when a service scenario related to the reported data is required to be changed by at least one monitoring system, the configuration information of the corresponding changed scenario is generated.

Next, in operation S440, an element extraction method of the service scene changed in the configuration information is extracted corresponding to the changed element.

For example, assume that regulatory requirements now require class a services to add a BOP class of data feeds from upstream service system B1 (e.g., one of service system 1, service system 2, service system 3, service system 4,. and service system n).

According to the embodiment of the present disclosure, the reporting of this type of data may be supported only by adding a BOP class service scenario to the scenario configuration information without changing the upstream service system B1. The specific configuration steps are as follows.

First, the service scenario information shown in table 3 below is newly added to the scenario configuration information.

TABLE 3

The second step is that: information of the element extraction method is arranged for the service scenario, as shown in table 4.

TABLE 4

After the first step and the second step, the data reporting device 101 or 201 can summarize the transaction data of the BOP class performed in the business system B1 into a transaction data summary table (i.e., Main table).

Then, according to an embodiment of the present disclosure, the setting of the entire delivery flow can also be completed by, for example, the following third and fourth steps.

The third step: and setting a data verification rule aiming at the data in the service scene, wherein the data verification rule is used for ensuring the quality of the externally reported data.

The fourth step: and setting and configuring the filing strategy aiming at the transaction field of the service scene.

In this way, according to the embodiment of the present disclosure, the upstream business system B1 only needs to save the transaction site to form a transaction snapshot through snapshot saving, and transmit the transaction snapshot to the data distribution device 101 or 201, and the data distribution device can automatically save the transaction snapshot in the corresponding file directory according to the scene configuration information. After that, the data reporting device 101 or 201 can automatically complete the processing of extracting, processing, verifying and reporting the reporting information according to the transaction snapshot, thereby saving the research and development cost.

In the prior art, when reporting data of a service scene needs to be added, the service data of the newly added service scene needs to be transmitted to the original data reporting system 102 by means of a newly added batch or an online interface. The original data distribution system 102 also needs to be modified to receive the distribution file of the upstream service system B1, perform the relevant verification processing, and then distribute the file to the outside. That is, the upstream business system B1 and the original messaging system 102 need to be modified at the same time. It can be seen from comparison that, according to the method of the embodiment of the present disclosure, the configuration information can be extracted by changing the scene configuration information and the elements, so that the change of the data transmission interface of the upstream service system B1 and the datagram device 101 or 201 is avoided, the development cost is saved, and the reporting efficiency is improved.

Fig. 5 schematically shows a flowchart of configuration element extraction configuration information in a data transmission method according to an embodiment of the present disclosure.

As shown in fig. 5, the process of extracting configuration information by a configuration element according to this embodiment may include operations S510 to S530. In some embodiments, the configuration element may extract the configuration information before operation S310. In other embodiments, the configuration element may extract the configuration information after the scene configuration information is configured in operation S410.

Specifically, in operation S510, according to the element field related to the data requested to be reported by at least one monitoring system, the configuration element extracts the element information corresponding to the element field in the configuration information and the extraction manner thereof, as shown in table 2.

It is understood that table 2 only illustrates the extraction manner of different element fields in one scenario. When a certain element field (for example, a transaction amount) to be reported by the monitoring organization relates to a plurality of business scenarios, element information corresponding to the element field and an extraction method thereof are respectively arranged in the plurality of business scenarios in the element extraction configuration information.

In operation S520, it is detected whether a notification that at least one element field of the data requested to be reported by the monitoring system is changed is received. If so, perform operation S530; if not, the configuration information is extracted using the elements configured in S510.

In operation S530, when an element field of data requested to be submitted by at least one supervisory system is changed, configuration information is extracted corresponding to the changed element.

For example, assuming that regulatory requirements change, a delivery field C needs to be added to the delivery data already in the EXD category of the delivery. And the EXD class of data is derived from N business processing systems (e.g., business system 1, business system 2, business system 3, business system 4,. and N of business systems N, N being an integer greater than or equal to 1 and less than or equal to N).

According to the embodiment of the present disclosure, it is possible to support only by adding the extraction manner of the element information corresponding to the field C to the element extraction configuration information. Specific configuration steps may be exemplified as follows.

In the first step, the scene configuration information table does not need to be adjusted, because this example does not involve the addition or modification of the service scene.

The second step is that: the OCR image recognition extraction method in which the new delivery field C is arranged in the element extraction arrangement information is shown in table 5 below.

Specifically, since the field C is derived from the EXD category in the N service processing systems, the element extraction manner of the service scene related to the EXD category in the N service processing systems needs to be changed.

TABLE 5

After the second step, the data reporting device 101 or 201 may aggregate the data for field C in the EXD category of transactions into the Main Table.

The settings of the overall delivery process can thereafter be refined, for example, by the following third and fourth steps.

The third step: and setting a data verification rule aiming at the newly added field C under each service scene, wherein the data verification rule is used for ensuring the quality of the externally reported data.

The fourth step: the trading floor archive policy settings for this scenario need not be adjusted, as this example does not involve the addition or modification of a submission scenario.

Therefore, according to the embodiment of the disclosure, when the service scene in the data requested to be reported by the monitoring system is not changed, but the reported element field is changed, N upstream service systems related to the element field do not need to be modified, and only an element extraction mode of a newly added report field C is configured in the element extraction configuration information, so that the modification workload of the system is greatly reduced.

However, in the prior art, when the element fields of the data required to be reported by the monitoring system are changed, the batch interfaces or the online interfaces of the N service systems and the original data reporting system 102 need to be modified, so that the modification workload is large. Compared with the prior art, the embodiment of the disclosure can rapidly extract the corresponding elements by configuring and/or changing the element information to extract the configuration information when a certain field is added for supervision, thereby reducing the workload of system modification and being beneficial to improving the timeliness and efficiency of data delivery.

Fig. 6 schematically shows a flowchart of a method for extracting element information from a transaction snapshot in operation S330 in a data transmission method according to an embodiment of the present disclosure.

As shown in fig. 6, in the data transmission method according to an embodiment of the present disclosure, when element information is extracted from stored transaction snapshots in operation S330, for a transaction snapshot in an arbitrary first service scenario, element information is extracted in a first element extraction manner corresponding to the first service scenario. The first element extraction method may include a plurality of rules or a plurality of element field extraction methods, and a specific process of extracting element information may include operations S331 to S334, as shown in table 2.

First, in operation S331, at least one element position set in the first element extraction manner is acquired.

As exemplified in connection with table 2. In one embodiment, the element position is a coordinate axis established by taking the lower bottom edge of the transaction snapshot as the x-axis, the left side edge as the y-axis and the lower left end point as the origin (0, 0). At this time, each information area in the transaction snapshot can be automatically mapped to an area position. X of the rule configuration such as rule number 1: 1, 10& & y: the 2, 12 region is represented as a rectangular region having 4 vertices (1, 2), (10, 2), (1, 12), (10, 12) in the coordinate axis plane.

Then, in operation S332, character information in a first element position in the transaction snapshot of the first service scenario is identified, wherein the first element position is any one element position in at least one element position, for example, an element position corresponding to rule number 1.

Next, in operation S333, a first field corresponding to the first element position set in the first element extraction manner is acquired. The field name as set under rule number 1 in table 2 is DATE 1.

Thereafter, in operation S334, character information recognized from the first element position is extracted to be filled in a first field of the transaction data summary table. For example, character information in a rectangular area having 4 vertices (1, 2), (10, 2), (1, 12), (10, 12) is recognized using an OCR recognition technique, and the recognized character information is filled in the DATE1 field of the transaction data summary table (i.e., MAIN table).

Compared with a mode of extracting corresponding information by identifying keywords or fields in the transaction snapshot in some embodiments, the embodiment of the disclosure can decouple the extracted information from the keywords or the fields, and the extraction mode is more stable.

Specifically, the corresponding information may be extracted based on the keyword recognition, for example, by recognizing a continuous character string following "the collection line name" to obtain the collection line name. However, there are certain disadvantages to this extraction method by keyword recognition: for example, if the upstream business system modifies the "collection line name" to "collection line chinese name", the modification element must be synchronized to extract the information of the keyword in the configuration information.

Compared with the extraction method based on the keyword, when the element information is extracted based on the element position, even if the name of the keyword is changed, the element extraction configuration information does not need to be changed as long as the position of the element information in the transaction snapshot is not changed. Furthermore, the transaction site data of an organization such as a financial institution is usually in a standardized table form, and is usually aligned left or right, and the maximum character length, the character height, and the like are usually set in each table entry. Therefore, when element information extraction is performed based on the element position in the manner shown in fig. 6, as long as the distribution of table items in a table or a document in which field data of a transaction is recorded in an upstream business system is not changed, the element extraction configuration information is not changed.

Fig. 7 schematically illustrates a flow chart for automatically processing a transaction snapshot for posting data in a data posting method according to an embodiment of the present disclosure.

As shown in fig. 7, the flow of the automatic processing of the transaction snapshot by the data reporting device 101 or 201 according to the embodiment of the disclosure may include operations S701 to S706.

First, in operation S701, scene configuration information (e.g., table 1) is read, and a record (e.g., a scene ID) of a service scene to be processed is obtained.

In operation S702, whether a transaction snapshot to be processed exists in the path is scanned according to the file directory and the transaction snapshot filename set in the scene ID rule. If not, the process is finished. If so, execution continues.

In operation S703, the element extraction method set for the scene ID in the element extraction configuration information (see table 2) is read, and if the element extraction method includes a plurality of extraction rules, each extraction rule is cyclically processed through operations S704 to S706.

In operation S704, an extraction rule is read.

In operation S705, the element position is acquired, and the element information in the position area is automatically extracted and saved to the corresponding field in the table of the rule setting by OCR image recognition.

In operation S706, it is determined whether the currently processed extraction rule is the last extraction rule under the current scene ID. If yes, the process is ended. If not, return is made to operation S704.

Fig. 8 schematically shows a flow chart of a data transmission method according to another embodiment of the present disclosure.

As shown in fig. 8, the data transmission method according to the embodiment may include operations S310 to S330, S341 to S343, and S850.

First, through operations S310 to S330, element data is extracted from a transaction snapshot recording a transaction field and summarized in a transaction data summary table. The specific implementation of operations S310 to S330 refers to the foregoing description, and is not described herein again.

And then reporting the data to the supervision authority through operations S341 to S343, where operations S341 to S343 are specific embodiments of the foregoing operation S340.

Specifically, according to an embodiment of the present disclosure, first, in operation S341, the data of the corresponding field in the transaction data summary table is verified according to the data verification rule set according to the requirement of the target supervisory system on the data quality specification.

And the data verification rule is set according to the data quality specification requirement of the target supervision system. Different supervision systems may require different reported data fields and different data accuracy degrees, so different data verification rules may be set for different supervision systems. The data verification rule may include the length, the necessity of inputting, the dictionary validity, etc. of each element information, and is used to ensure the quality of the externally reported data.

Table 6 is an example of a partial data check rule. During verification, the corresponding rule records can be read from the table 6 by combining with the transaction data summary table, judgment is carried out in a circulating mode, and only after the rules of all fields in the data verification rules are verified, subsequent external reporting operation can be carried out so as to ensure the quality of reported data. The key fields involved in the validation rules in table 6 are described below:

TABLE 6

Rule states: 1-effective; 0-failure. By which it is controlled whether the rule needs to be executed by submission data verification module 950 or submission data verification module 15.

The effective condition is as follows: an additional validation condition may be set via this field, provided that the rule is validated, such as the above-mentioned rule with serial number 1, AVALCON set to $ ACTIONYPE $! D' indicates that the rule only needs to be executed by the data check engine when the operation type (action) is not delete (D).

Checking element fields: for specifying the target field for verification by the data verification engine.

Field length: and the data checking engine checks the length of the target field according to the configuration value of the field, and if the length of the target field is not matched with the configuration value of the target field, the output check is failed.

And (3) checking type: s is a simple rule; f is a complex rule (which can be extended by writing the check function separately).

A check function: when the CHKTYPE is configured as an F-complex rule, a check function corresponding to the rule needs to be set through the field. And when the data verification engine formulates a complex rule, calling the verification function set by the field, and returning a verification result according to the execution result of the verification function.

Whether the dictionary is: and if the dictionary value is checked, Y-is, and N-is. Used to specify whether the rule requires checking the dictionary value validity of the target field.

Associated dictionary values: this field needs to be configured when ISDICT sets Y-YES. For example, rule relict ═ dic with sequence number 1: count, the data verification engine may verify a value of the target field with a dictionary value range of count, pass if the target field value is within the dictionary value range of count, and fail otherwise.

Next, in operation S342, the data of the corresponding field in the transaction data summary table is spliced according to the reporting interface specification of the target monitoring system when the verification passes, so as to form a target spliced message.

Then, in operation S343, a target splicing message is sent to the target monitoring system.

Although the data verification rules of different monitoring systems may be different, the data verification of different monitoring systems is based on transaction fact, so that the same field data theory in the transaction data summary table does not have conflict on the verification rules. Therefore, according to the embodiment of the disclosure, the data in the transaction data summary table can be verified according to the data verification rule, and then the template splicing message is spliced and reported when all the rules in the data verification rule are verified to pass. Compared with the mode of splicing messages first and then verifying, the mode of splicing messages first and then verifying of the embodiment of the disclosure saves efficiency.

After the data is posted, the transaction snapshot of each business scenario may also be archived according to the archiving policy set for each business scenario in operation S850. Archive policy settings may be set for each business scenario as shown in table 7.

The archive policy exemplified in table 7 may include 1: archiving online; 2: archiving offline; 3: and (6) clearing data. Where online archiving may be archiving in a storage device of the data submission device 101 or 201, or a storage device of a business system where the transaction occurs. Offline archiving may be storage on disk, tape. Data cleaning may specify the number of archive cycle days, with transaction snapshots exceeding the specified number of archive cycle days cleaned.

According to the embodiments of the present disclosure, after the data is reported to the monitoring authority, the transaction snapshot can be filed, which is convenient for tracing.

TABLE 7

Based on the data reporting method of each embodiment, the embodiment of the disclosure further provides a data reporting device. The apparatus will be described in detail below with reference to fig. 9 and 10.

Fig. 9 schematically illustrates a block diagram of a datagram device 900 according to an embodiment of the present disclosure.

As shown in fig. 9, the datagram device 900 according to this embodiment may include a trading floor reception module 910, a datagram data automatic processing module 920 and an out-link datagram module 930. The automatic submission data processing module 920 may include a snapshot storage module 921 and an element extraction module 922. According to other embodiments of the present disclosure, the data delivery device 900 may further include at least one of a rule base module 940, a delivery data verification module 950, and a trading floor filing module 960. The apparatus 900 may perform the methods described with reference to fig. 3-8.

Specifically, the trading scene receiving module 910 is configured to receive a trading snapshot of at least one business scenario. In one embodiment, the trading floor reception module 910 may perform operation S310 described above.

The snapshot storing module 921 is configured to, when any first service scenario in the at least one service scenario belongs to a service scenario in the scenario configuration information, store a transaction snapshot of the first service scenario according to a first file directory configured for the first service scenario in the scenario configuration information. In one embodiment, the snapshot storage module 921 may perform operation S320 described previously.

The element extraction module 922 is used for extracting element information from the stored transaction snapshots according to a request extraction mode configured in the element extraction configuration information and used for extracting the element information from the transaction snapshots of each service scene, and summarizing the element information to a transaction data summary table. In one embodiment, the element extraction module 922 may perform operation S330 described above.

The outbound 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 export submission module 930 may perform operation S340 described above.

The rule base module 940 is configured to configure the service scenario and its file directory in the scenario configuration information according to the service scenario related to the data requested by at least one monitoring system, where the at least one monitoring system includes a target monitoring system. In some embodiments, the rule base module 940 is further configured to, when a change occurs in a service scenario related to data requested to be submitted by at least one monitoring system, correspond to the change scenario configuration information, and, after the change scenario configuration information is changed, extract an element extraction manner of the service scenario changed in the configuration information corresponding to the changed element. In one embodiment, the rule base module 940 may perform the operational flow described in FIG. 4, supra.

In other embodiments, the rule base module 940 is configured to, according to the element fields related to the data reported by at least one monitoring system, configure the element to extract the element information corresponding to the element fields in the configuration information and the extraction manner thereof; when the element field relates to a plurality of business scenes, element information corresponding to the element field and an extraction mode thereof are respectively configured in the plurality of business scenes in the element extraction configuration information. In other embodiments, the rule base module 940 is further configured to extract configuration information corresponding to changed elements when the element fields of the data requested to be submitted by at least one of the monitoring systems are changed. In one embodiment, the rule base module 940 may perform the operational flow described in FIG. 5, supra.

The submission data checking module 950 is configured to check data of a corresponding field in the transaction data summary table according to a data checking rule set according to a requirement of a target supervision system on a data quality specification before the external submission module 930 submits the data to at least one supervision system, where the target supervision system is any one of the at least one supervision system. Accordingly, the external connection reporting module 930 is configured to, in the case that the verification passes, splice data of corresponding fields in the transaction data summary table according to the reporting interface specification of the target monitoring system, form a target splicing message, and send the target splicing message to the target monitoring system. In one embodiment, the submission data checking module 950 may perform operation S341 and the external submission module 930 may perform operations S342-S343.

The trading scene archiving module 960 is configured to archive the trading snapshot of each business scenario according to an archiving policy set for each business scenario. In one embodiment, the trading floor archiving module 960 may perform operation S850 described above.

According to the embodiment of the present disclosure, any plurality of the transaction field receiving module 910, the submission data automatic processing module 920, the external connection submission module 930, the rule base module 940, the submission data verification module 950 and the transaction field filing module 960 may be combined and implemented in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the transaction field reception module 910, the submission data automatic processing module 920, the external connection submission module 930, the rule base module 940, the submission data verification module 950, and the transaction field filing module 960 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented in any one of three manners of software, hardware, and firmware, or in any suitable combination of any of them. Alternatively, at least one of the trading floor receipt module 910, the submission data automatic processing module 920, the extranet submission module 930, the rule base module 940, the submission data verification module 950 and the trading floor filing module 960 may be at least partially implemented as a computer program module that, when executed, may perform corresponding functions.

Fig. 10 schematically illustrates a block diagram of a datagram device 10 according to another embodiment of the present disclosure.

As shown in fig. 10, the data delivery device 10 may include a parameter configuration module 11, a rule base module 12, a transaction field receiving module 13, a delivery data automatic processing module 14, a delivery data verification module 15, an external connection delivery module 16, a transaction field archiving module 17, a traceability confirmation module 18 and a data storage module 19. The datagram device 10 is an embodiment of the datagram device 900, and accordingly, the modules with the same name in the datagram device 10 are embodiments of the datagram device 900. The functions of the various modules of the data delivery device 10 are described in detail below.

The parameter configuration module 11: the device is responsible for the configuration of parameters required by the device, such as network connection parameters, transaction field filing directory paths, external connection reporting paths, device operation start-stop time and the like.

Rule base module 12: the various information required for configuring the present device includes the aforementioned scene configuration information elements (e.g., table 1), element extraction configuration information (e.g., table 2), data verification rules (e.g., table 6), and archive policies (e.g., table 7).

The transaction field receiving module 13: the system is responsible for receiving the transaction snapshots transmitted by the service systems, and different file directories are established according to the service scenes to which different upstream product systems belong, so that the transaction snapshots can store and/or name files according to scene configuration information for the automatic reporting data processing module 14 to use.

The submission data automatic processing module 14: according to the scene configuration information configured by the rule base module 12 and the element extraction configuration information, the transaction snapshot under the file directory of the transaction field receiving module 13 is read, and the element information is automatically extracted from the transaction snapshot according to the element extraction mode of the service scene and stored in the reporting information table (as shown in fig. 6). The processing flow of the delivery data automatic processing module 14 can refer to the schematic of fig. 7.

The report data verification module 15: the delivery data generated from the factor information extracted by the delivery data automatic processing module 14 is verified, and each rule is acquired from, for example, a data verification rule base shown in table 6, and is verified one by one. And setting the data to be in a to-be-reported state when all the checks are passed, and otherwise, updating the data to be in a to-be-confirmed state.

The external connection reporting module 16: the monitoring system is responsible for interaction with an external monitoring system, and the interaction comprises the step of reporting the data to be reported which passes the verification to the monitoring system; and receiving a processing result return of the supervision system. And updating the data state into successful delivery or failed delivery according to the returned result.

Transaction field archive module 17: and reading the filing strategy in the rule base module 12, and uploading the transaction snapshot which is finished with the automatic processing of the report information to a filing path for filing and future reference.

The tracing confirmation module 18: and providing a tracing confirmation operation for the data to be confirmed and in the reporting failure state, and retrieving the transaction snapshot from the filing path according to the data so as to facilitate the confirmation of business personnel, improve the convenience of operation and avoid the need of logging in an upstream business system for information query.

The data storage module 19: and the device is responsible for storing transaction snapshots, spliced messages and parameter rules in the device processing process.

The data reporting device 10 can well solve the problem of large workload of adaptation and transformation of related systems caused by adjustment of a supervision reporting data interface based on transaction snapshot automatic reporting data, and can quickly support service personnel to trace source and confirm the reporting data, reduce the management cost of supervision reporting data and improve the data reporting efficiency.

Fig. 11 schematically shows a block diagram of an electronic device 1100 adapted to implement a data transmission method according to an embodiment of the present disclosure.

As shown in fig. 11, an 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 comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1101 may also include on-board memory for caching purposes. The processor 1101 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to the embodiments of the present disclosure.

In the RAM 1103, various programs and data necessary 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 by a bus 1104. The processor 1101 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1102 and/or the RAM 1103. It is to be noted that the programs 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 method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1100 may also include input/output (I/O) interface 1105, input/output (I/O) interface 1105 also connected to bus 1104, according to an embodiment of the present disclosure. Electronic device 1100 may also include one or more of the following components connected to I/O interface 1105: an input portion 1106 including a keyboard, mouse, and the like; an output portion 1107 including a signal output unit such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 1108 including a hard disk and the like; and a communication section 1109 including a network interface card such as a LAN card, a modem, or the like. The communication section 1109 performs communication processing via a network such as the internet. A driver 1110 is also connected to the I/O interface 1105 as necessary. A removable medium 1111 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1110 as necessary, so that a computer program read out therefrom is mounted into the storage section 1108 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1102 and/or the RAM 1103 described above and/or one or more memories other than the ROM 1102 and the RAM 1103.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 1101. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication part 1109, and/or installed from the removable medium 1111. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 1109 and/or installed from the removable medium 1111. The computer program, when executed by the processor 1101, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures 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 diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be appreciated by a person skilled in the art that various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made, even if such combinations and/or combinations are not explicitly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (12)

1. A method of data reporting, comprising:

receiving a transaction snapshot of at least one business scenario;

when any first service scene in the at least one service scene belongs to a service scene in scene configuration information, storing a transaction snapshot of the first service scene according to a first file directory configured for the first service scene in the scene configuration information;

extracting element information from the stored transaction snapshots according to an element extraction mode which is configured in the element extraction configuration information and used for extracting the element information from the transaction snapshot of each service scene, and summarizing the element information to a transaction data summary table; and

reporting data to at least one regulatory system based on the transaction data summary sheet.

2. The method of claim 1, wherein the scene configuration information is obtained by:

and configuring the service scenes and file directories thereof in the scene configuration information according to the service scenes related to the data required to be reported by the at least one monitoring system.

3. The method according to claim 2, wherein the configuring the service scenario and its file directory in the scenario configuration information according to the service scenario to which the data reported by the at least one monitoring system relates further comprises:

when the service scene related to the data required to be reported by the at least one monitoring system is changed, correspondingly changing the scene configuration information; and

and after changing the scene configuration information, correspondingly changing the element extraction mode of the changed service scene in the element extraction configuration information.

4. The method of claim 1, wherein the element extraction configuration information is obtained by:

according to the element field related to the data requested to be reported by the at least one supervisory system, element information corresponding to the element field in the element extraction configuration information and an extraction mode of the element information are configured;

wherein the content of the first and second substances,

and when the element field relates to a plurality of business scenes, respectively arranging element information corresponding to the element field and an extraction mode thereof in the plurality of business scenes in the element extraction configuration information.

5. The method according to claim 4, wherein the configuring of the element information corresponding to the element field in the element extraction configuration information and the extraction manner thereof according to the element field related to the data required to be reported by the at least one monitoring system further comprises:

when the element field of the data required to be reported by the at least one supervision system is changed, the element extraction configuration information is correspondingly changed.

6. The method of claim 1, wherein the extracting element information from the stored transaction snapshot according to an element extraction manner configured in the element extraction configuration information for extracting element information from the transaction snapshot of each service scenario comprises:

extracting element information from the transaction snapshot of the first service scenario according to a first element extraction manner corresponding to the first service scenario and configured in the element extraction configuration information, wherein the method comprises the following steps:

acquiring at least one element position set in the first element extraction mode;

identifying character information in a first element position in a transaction snapshot of the first service scene, wherein the first element position is any one element position in the at least one element position;

acquiring a first field corresponding to the position of the first element and arranged in the first element extraction mode; and

extracting character information identified from the first component location for filling into the first field of the transaction data summary table.

7. The method of claim 1, wherein said reporting data to at least one regulatory system based on said transaction data summary table comprises:

verifying data of corresponding fields in the transaction data summary table according to a data verification rule set according to the requirement of a target supervision system on data quality specifications; the target supervisory system is any one of the at least one supervisory system;

under the condition that the verification is passed, splicing data of corresponding fields in the transaction data summary table according to the reporting interface specification of the target monitoring system to form a target splicing message; and

and sending the target splicing message to the target supervision system.

8. The method of claim 1, wherein the method further comprises:

and archiving the transaction snapshot of each business scene according to the archiving strategy set for each business scene.

9. A datagram device comprising:

the transaction scene receiving module is used for receiving a transaction snapshot of at least one service scene;

a snapshot storage module, configured to, when any first service scenario in the at least one service scenario belongs to a service scenario in scenario configuration information, store a transaction snapshot of the first service scenario according to a first file directory configured for the first service scenario in the scenario configuration information;

the element extraction module is used for extracting element information from the stored transaction snapshots according to an element extraction mode which is configured in the element extraction configuration information and used for extracting the element information from the transaction snapshots of each service scene, and summarizing the element information to a transaction data summary table; and

and the external connection reporting module is used for reporting data to at least one monitoring system based on the transaction data summary table.

10. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.

11. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the method of any one of claims 1 to 8.

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

Images