CN111476659B - Service data processing method, system, component, computing device and storage medium - Google Patents
Service data processing method, system, component, computing device and storage medium Download PDFInfo
- Publication number
- CN111476659B CN111476659B CN202010286149.6A CN202010286149A CN111476659B CN 111476659 B CN111476659 B CN 111476659B CN 202010286149 A CN202010286149 A CN 202010286149A CN 111476659 B CN111476659 B CN 111476659B
- Authority
- CN
- China
- Prior art keywords
- core
- point
- component
- check
- configuration information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
One or more embodiments of the present specification provide a business data processing method, a business data processing system, and a computing device and computer readable storage medium. Wherein the method is applied to a collation system which pre-configures a first component in a business system, the method comprising: generating the nuclear-to-point configuration information of the service system; sending the core-to-point configuration information to a first component; the first component determines a core point in the service system according to the core point configuration information. By implementing the scheme of the embodiment of the specification, the invasion to the service system is weakened, the influence on the service system is reduced, and the working stability and the original service correctness of the service system are improved; meanwhile, the checking points can be flexibly configured outside the service system through the checking system to carry out subsequent checking processing, so that the checking points can be flexibly arranged to check, and the checking flexibility is good.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a service data processing method. The present specification is also directed to a business data processing system, a first component, and a computing device and a computer readable storage medium.
Background
With the development of internet technology, financial institutions and third-party transaction platforms are becoming more and more diversified, so that transaction business data between financial institutions or between third-party transaction platforms and financial institutions needs to be checked in real time or periodically to ensure correctness of business flow and accounting details.
In the related art, the verification of service data is performed by adding a verification code in a transaction service system, and the verification code is released on line following the service system. However, existing implementations suffer from at least the following problems: checking that the code is coupled in the service system, so that the code is forced to invade; checking the code itself presents a certain risk, possibly affecting the business system; the check code is released on line along with the service system, cannot be dynamically adjusted, and has poor check flexibility.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a service data processing method. Embodiments of the present specification relate to a business data processing system, a first component, and a computing device and a computer readable storage medium, to solve the technical drawbacks of the prior art.
According to a first aspect of embodiments of the present specification, there is provided a service data processing method, the method being applied to a first system that pre-configures a first component in a second system; the method comprises the following steps:
The first system generates the core-to-point configuration information of the second system;
the first system sends the core-to-point configuration information to the first component;
the first component determines a core point in the second system according to the core point configuration information.
In one embodiment of the present specification, the step of generating, by the first system, the core-to-point configuration information of the second system includes:
and generating the core-point configuration information according to the core-requirement information of the second system, wherein the core-point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
In one embodiment of the present disclosure, the step of determining, by the first component, a core point in the second system according to the core point configuration information includes:
and the first component determines one or more corresponding core points in the second system according to the business scene information of the core points.
In one embodiment of the present specification, the service context information includes at least one core point location information;
the step of determining, by the first component, one or more corresponding core points in the second system according to the service scenario information to which the core points belong, includes:
And determining corresponding one or more core points in the second system according to the at least one core point position information.
In one embodiment of the present specification, further comprising:
the first system receiving a check data stream acquired by the first component from the point of verification;
the first system checks the check data stream to generate a check result.
In one embodiment of the present specification, further comprising:
the first system determines whether the collation result is abnormal;
in response to determining that the verification result is abnormal, throwing an abnormal notification to the second system so as to enable the second system to fuse current processing business; or alternatively
An alarm prompt is issued in response to determining that the collation result is abnormal.
In one embodiment of the present description, the first system includes a second component configured within the first system;
the step of the first system receiving a check data stream acquired by the first component from the point of verification comprises: the collation data stream is received by the second component.
In one embodiment of the present description, the check data stream of the check point contains a unique identification of the check point; the step of the first system collating the collation data stream to generate a collation result includes:
The second component queries and determines a checking module corresponding to the checking point according to the unique identifier of the checking point and a preset mapping table; the preset mapping table comprises a mapping relation between a unique identifier of at least one checking point and at least one corresponding checking module;
the second component forwards the collation data stream to the determined collation module so that the determined collation module performs real-time collation or delay collation on the collation data stream and outputs a collation result.
In one embodiment of the present specification, further comprising:
and when the second component does not inquire the checking module corresponding to the checking point according to the unique identification of the checking point and a preset mapping table, writing the checking module which is generated to be matched with the checking point, so that the checking data flow is checked through the generated checking module, and a checking result is output.
In one embodiment of the present specification, further comprising:
determining a service scene corresponding to the check point according to the unique identifier of the check point contained in the check data flow of the check point;
judging whether the service scene is in a preset service scene list or not;
Responding to the business scene in a preset business scene list, and checking the check data flow to generate a check result;
responding to the fact that the service scene is not in a preset service scene list, and sending a notification message to the first component through the second component; the notification message is used for indicating the first component to acquire a preset percentage of check data flow from a check point configured in the second system.
According to a second aspect of embodiments of the present specification, there is provided a service data processing system including a configuration information generating unit, a configuration information processing unit, and a first component; wherein:
the configuration information generating unit is used for generating the core-to-point configuration information of the second system;
the configuration information processing unit is used for sending the core-to-point configuration information to the first component;
the first component is pre-configured in the second system and is used for determining a core point in the second system according to the core point configuration information.
According to a third aspect of embodiments of the present specification, there is provided a service data processing method applied to a first component configured in advance in a second system via a first system; the method comprises the following steps:
Receiving the core-to-point configuration information of the second system generated by the first system;
and determining the core point in the second system according to the core point configuration information.
In one embodiment of the present specification, the check point configuration information is generated by check requirement information of the second system; the core point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
In one embodiment of the present disclosure, the step of determining the core point in the second system according to the core point configuration information includes:
and determining one or more corresponding core points in the second system according to the service scene information of the core points.
In one embodiment of the present specification, the service context information includes at least one core point location information; the step of determining one or more corresponding core points in the second system according to the service scene information of the core points comprises the following steps:
and determining corresponding one or more core points in the second system according to the at least one core point position information.
According to a fourth aspect of embodiments of the present specification, there is provided a first component pre-configured in a second system via a first system; the first assembly includes:
The receiving unit is used for receiving the core-to-point configuration information of the second system generated by the first system;
and the determining unit is used for determining the core point in the second system according to the core point configuration information.
According to a fifth aspect of embodiments of the present specification, there is provided a computing device comprising:
a memory and a processor;
the memory is configured to store computer executable instructions and the processor is configured to execute the computer executable instructions to implement the steps of the business data processing method of any of the embodiments described above.
According to a sixth aspect of embodiments of the present specification, there is provided a computer readable storage medium storing computer executable instructions which, when executed by a processor, implement the steps of the business data processing method of any of the embodiments described above.
According to the business data processing method, the system, the components and the like provided by one or more embodiments of the present disclosure, a first system generates core-to-point configuration information of a second system, the first system sends the core-to-point configuration information to a first component preset in the second system, and the first component determines a core-to-point in the second system according to the core-to-point configuration information. In this embodiment, the first component is set in the second system to determine the verification point, and the verification code is not added in the second system to directly perform verification, so as to reduce the amount of the verification code added in the second system, reduce or even completely avoid the intrusion of the verification code into the second system, reduce the influence on the second system, and improve the working stability and the service correctness of the second system. Meanwhile, the check points can be flexibly configured outside the second system through the first system to carry out subsequent check processing, so that the check points can be flexibly arranged to check, and the check flexibility is good.
Drawings
Fig. 1 is a flowchart of a service data processing method according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a business process verification system according to an embodiment of the present disclosure;
FIG. 3 is a flowchart of a method for processing service data according to an embodiment of the present disclosure;
FIG. 4 is a flowchart of a method for processing service data according to an embodiment of the present disclosure;
fig. 5 is a flowchart of a service data checking method according to an embodiment of the present disclosure;
FIG. 6 is a flowchart of a method for processing service data according to an embodiment of the present disclosure;
FIG. 7 is a schematic diagram of a business system data verification processing system according to an embodiment of the present disclosure;
FIG. 8 is a schematic diagram of a business data processing system according to an embodiment of the present disclosure;
FIG. 9 is a schematic view of a first component according to an embodiment of the present disclosure;
FIG. 10 is a schematic diagram of a computing device according to an embodiment of the present disclosure.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many other forms than described herein and similarly generalized by those skilled in the art to whom this disclosure pertains without departing from the spirit of the disclosure and, therefore, this disclosure is not limited by the specific implementations disclosed below.
The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that, although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first may also be referred to as a second, and similarly, a second may also be referred to as a first, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
First, terms related to one or more embodiments of the present invention will be explained.
And (3) assembly: the components are simple packages of data and methods, have relatively independent functions, can be independently deployed, and can be assembled.
In the present specification, a business data processing method is provided, and the present specification relates to a business data processing system, a first component, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.
Fig. 1 is a flowchart of a service data processing method according to an embodiment of the present disclosure, and in conjunction with a schematic diagram of a service processing verification system architecture shown in fig. 2, the method may be applied to the first system 10, that is, may be executed by the first system 10. The first system 10 pre-configures a first component 101 in the second system 20; the method may include steps S102 to S106.
Step S102: the first system generates the core-to-point configuration information of the second system.
Step S104: the first system sends the core-to-point configuration information to the first component.
Step S106: the first component determines a core point in the second system according to the core point configuration information.
In particular, in one embodiment of the present disclosure, the first system 10 may be a verification system for verifying business data, and the second system 20 may be a transaction business system, such as a third party paymate system. The first system 10 is configured to check service data of the second system 20. The point of interest may be, but is not limited to, a location between adjacent business process steps when the second system 20 performs business processing. The first component 101 is assigned to the first system 10 and has a relatively independent function for performing a corresponding independent function under control of the first system 10. This functionality in this embodiment may include, but is not limited to, determining a core point and subsequent replication of the traffic data stream from the core point.
In this embodiment, the check code is not added to the second system 20 to directly check, so as to reduce the amount of the check code added to the second system 20, reduce or even completely avoid the intrusion of the check code into the second system 20, reduce the influence on the second system 20, and improve the working stability and the service correctness of the second system 20. Meanwhile, the check points can be flexibly configured outside the second system 20 through the first system 10 to carry out subsequent check processing, so that the check points can be flexibly arranged for check, and the check flexibility is better.
In one embodiment of the present disclosure, the step of generating the core-to-point configuration information of the second system 20 by the first system 10 may specifically include: and generating the core-to-point configuration information according to the core-to-point requirement information of the second system 20, wherein the core-to-point configuration information at least comprises a unique identifier of the core-to-point and service scene information of the core-to-point associated with the unique identifier.
Illustratively, the collation demand information may be custom set in advance, but is not limited thereto. Specifically, the second system may be a third party payment platform system, which relates to more service scenarios, the service scenario information may be a scenario name, such as service scenario a, service scenario B, service scenario C, etc., and the verification requirement information of different service scenarios may be different. Therefore, the checking requirement information can be preset for the service scene a, the service scene B, the service scene C and the like, and the checking requirement information is used for representing the service scene to be checked and the corresponding checking point. Thus, the first system 10 may generate, during the verification, the verification request information, where the verification request information includes the unique identifier of the verification point and the service scenario information to which the verification point associated with the unique identifier belongs, for example, service scenario information such as service scenario a, service scenario B, service scenario C, and the unique identifier of the verification point under each associated service scenario, such as unique code, etc. The unique identifier of the core point can identify different service scenarios to which the core point belongs, and the unique identifier of the core point can be packaged in a subsequent verification data stream obtained from the core point, so that the first system 10, i.e. the verification system, can identify the service scenario to which the received verification data stream belongs.
Optionally, in an embodiment of the present disclosure, the step of determining, by the first component 101, a core point in the second system 20 according to the core point configuration information may specifically include: the first component 101 determines, in the second system 20, a corresponding one or more core points according to the service scenario information to which the core points belong.
In particular, in one embodiment of the present specification, the service scenario information may include at least one core point location information. The point location information is used to represent specific locations of the corresponding point in a plurality of business process steps when the business data is processed in the business scene. The step of determining, by the first component 101, the corresponding one or more core points in the second system 20 according to the service scenario information to which the core points belong may specifically include: corresponding one or more core points are determined in the second system 20 based on the at least one core point location information.
It will be appreciated that, in a business scenario, data of more than one point of verification may need to be verified in a business process during business data processing, so that when data of one or more points of verification need to be verified, a specific location of the corresponding one or more points of verification may be conveniently determined through the point of verification location information. Therefore, the verification data streams can be obtained from specific positions of a plurality of verification points, respectively, and the verification efficiency is improved.
Fig. 3 shows a flowchart of a service data processing method according to an embodiment of the present disclosure, where the processing method may include steps S302 to S310:
step S302: the first system generates the core-to-point configuration information of the second system.
Step S304: the first system sends the core-to-point configuration information to the first component.
Step S306: the first component determines a core point in the second system according to the core point configuration information.
Step S308: the first system receives a check data stream acquired by the first component from the point of verification.
Step S310: the first system checks the check data stream to generate a check result.
The steps S302 to S306 may refer to the corresponding descriptions of the steps S102 to S106 in the foregoing method embodiments, and are not repeated here.
In step S308, the first system 10 receives a check data stream acquired by the first component 101 from the check point. In this embodiment, as shown in fig. 7, the check data flow obtained by the first component 101 from the core point P is a service data flow copying a position between the service flow step 1 and the adjacent service flow step 2 in the service system 70, and has substantially no influence on the service system 70 which is the second system. The traffic data stream may for example contain transaction flow billing data or the like.
In step S310, the first system 10 checks the check data stream to generate a check result. I.e., data verification by second system 20, such as first system 10 outside of business system 70. It can be seen that, in this embodiment, the first component 101 is configured in the second system 20 to determine the checking point and obtain the checking data, and the checking is directly performed in the second system 20 without adding the checking code, but the first system 10 outside the second system 20 performs the checking after obtaining the checking data, so as to reduce the amount of the checking code added in the second system 20, reduce the intrusion of the checking code into the second system 20, thereby reducing the influence on the second system 20, improving the working stability and the original service correctness of the second system 20, and making the second system 20 such as the service system more compact. Meanwhile, the check points can be flexibly configured outside the second system 20 through the first system 10 to carry out subsequent check processing, so that the check points can be flexibly arranged for check, and the check flexibility is better.
Optionally, in an embodiment of the present disclosure, referring to fig. 4 in combination, after step S310, the processing method further includes the following steps S312 and S314:
Step S312: the first system determines whether the collation result is abnormal.
Specifically, the check data flow obtained by the first component 101 may include transaction flow bill data, for example, during check, balance data before and after consumption of a user account and consumption amount in the bill may be checked, whether transaction data calculation is wrong is determined, if wrong, the check result is determined to be abnormal, and if correct, the check result is determined to be normal.
Step S314: and in response to determining that the checking result is abnormal, throwing an abnormal notification to the second system so as to enable the second system to fuse the current processing service.
Specifically, when it is determined that the collation result is abnormal, the first system 10 throws an abnormality notification to the second system 20, for example, the abnormality notification may be fed back to the second system 20 by the second component 20 and the first component 10. In this way, the abnormality can be timely identified and thrown, and the second system 20, such as a service system, can sense the abnormality and immediately actively fuse the current service, where fusing indicates that the system prevents the service system from continuously executing the service flow through abnormal throwing, so as to facilitate implementation of subsequent remedial measures such as checking.
Optionally, in another embodiment of the present specification, the processing method further includes: an alarm prompt is issued in response to determining that the collation result is abnormal.
Specifically, when the checking result is abnormal, an alarm prompt message is sent out to remind relevant personnel of paying attention. The alarm prompt message is used for prompting when an acceptable abnormality occurs in some service scenarios, and only prompts but does not stop the continuous operation of the second system 20 such as a service system, so as to improve the fault tolerance of the system.
In one embodiment of the present description, the first system 10 includes a second component 102 disposed within the first system 10. Accordingly, in step S308, the step of receiving, by the first system 10, the check data stream obtained by the first component 101 from the core point may specifically include: the verification data stream is received by the second component 102. In this embodiment, the second component 102 may be a general-purpose collation component, which is used as an interface to uniformly manage and distribute the collation data flow from the first component 101, so as to improve the data processing efficiency of the first system 10.
In one embodiment of the present description, the check data stream of the check point contains a unique identification of the check point. Fig. 5 shows a flowchart of a service data collation method in one embodiment of the present specification, and step S310 is specifically described. Step S310, that is, the step of the first system 10 collating the collation data stream to generate a collation result, may specifically include the following steps S3101 to S3103:
Step S3101: the second component queries and determines a checking module corresponding to the checking point according to the unique identifier of the checking point and a preset mapping table; the preset mapping table comprises a mapping relation between a unique identifier of at least one checking point and at least one corresponding checking module.
Illustratively, as shown in table 1 below, the reconciliation data stream received by the second component 102, for example, contains the unique identification 001 of the point of verification, which can indicate that the reconciliation data stream is from a business scenario a in a second system 20, such as a business system, the corresponding reconciliation module being a first reconciliation module such as reconciliation module a shown in fig. 6.
TABLE 1
| Unique identification of a point of interest | Business scenario to which it belongs | Correspondence checking module |
| 001 | Service scenario A | First checking module |
| 002 | Service scenario B | Second checking module |
| 003 | Service scenario C | Third checking module |
| 004 | Service scenario D | Fourth checking module |
Step 3102: the second component forwards the collation data stream to the determined collation module so that the determined collation module performs real-time collation or delay collation on the collation data stream and outputs a collation result.
Specifically, after the verification module a is determined, the current verification data stream may be sent to the verification module a for verification processing. In the present embodiment, a plurality of collation modules may be provided, and fig. 7 exemplarily shows collation modules a, B, C, the number of which is not limited thereto. In one example, the processing logic of different collation modules may be different to correspondingly process data collation under different service scenarios, so that the data collation may be processed in a targeted manner, and the processing efficiency of collated data is improved. The collation system in this embodiment has a hot-deployed host application, carrying the collation module. The checking module is a place for really realizing checking capability and can be dynamically deployed in real time into a checking system. In addition, real-time checking or delay checking can be performed, and the dependence of the second system 20 such as a service system on the first system 10 such as the checking system can be avoided through asynchronization, so that the performance of the service system is not basically affected, and the correctness of the original service of the service system is ensured.
In one embodiment of the present specification, the processing method further includes the following step S3103:
step S3103: and when the second component does not inquire the checking module corresponding to the checking point according to the unique identification of the checking point and a preset mapping table, writing the checking module which is generated to be matched with the checking point, so that the checking data flow is checked through the generated checking module, and a checking result is output.
It can be understood that in this embodiment, the verification module may be customized, and after the specific content is edited, the verification module may issue to the verification system in real time, so as to implement flexible verification of service data.
In this exemplary embodiment, a checking system of a real-time heat-deployed checking module, i.e., the first system 10, may be implemented, and the first component 101 is embedded in the second system 20, such as the service system 70, to achieve flexible arrangement of checking capability, reduce strong intrusion of the service system, implement multiple flexible checking capabilities with as little sense of the original service system 70 as possible, and dynamically adjust the checking point and the checking module in real time.
Fig. 6 shows a flowchart of a service data processing method according to an embodiment of the present disclosure, including steps S601 to S604; wherein:
Step S601: and determining a service scene corresponding to the core point according to the unique identifier of the core point contained in the core point checking data stream.
Illustratively, step 601 may begin executing after the second component 102 receives a check data stream obtained by the first component 101 from the core point. For example, if the unique identifier of the point is 002, it can be determined that the point corresponds to the service scenario B, etc.
Step S602: and judging whether the service scene is in a preset service scene list or not.
Specifically, the preset service scenario list may be preset, for example, the service scenario list may include service scenario a, service scenario B, and service scenario C, but does not include service scenario D.
Step S603: and responding to the business scene in a preset business scene list, and checking the check data stream to generate a check result.
Specifically, for example, the service scenario B is currently determined, and after the judgment, the verification data stream is verified to generate a verification result after the verification is confirmed in the service scenario list.
Step S604: responding to the fact that the service scene is not in a preset service scene list, and sending a notification message to the first component through the second component; the notification message is used for indicating the first component to acquire a preset percentage of check data flow from a check point configured in the second system.
Specifically, for example, the unique identifier of the current core point is 004, it is determined that the service scenario D is determined, and after determining that the service scenario D is not in the service scenario list, a notification message is sent to the first component 101 through the second component 102, so as to instruct the first component 101 to obtain a preset percentage of check data flows from the core point configured in the second system 20. The preset percentage may be less than, for example, 60%. Therefore, the business scene blacklist/whitelist checking is realized, and more flexible checking capability can be realized by configuring the business scene blacklist/whitelist. Meanwhile, in this embodiment, the gray level cut-off can be implemented, and the smaller proportion of the check data stream is obtained by copying and splitting from the service flow check point in the second system 20 for subsequent check processing, so that the check capability is more diversified.
The service data processing method provided in the present specification is further described below with reference to fig. 7 by taking an application of the service data processing method in a service system as an example. Fig. 7 is a schematic diagram of a service system data checking and processing system according to an embodiment of the present disclosure, and based on the service system data checking and processing system shown in fig. 7, the method may include the following steps:
Step 1): the core-to-point configuration unit in first system 10 generates core-to-point configuration information for service system 70 based on the collation demand information for service system 70.
For example, if it is required to check the service data, such as the transfer transaction data, between the service flow step 1 and the service flow step 2 of a transaction under a service scenario of the service system 70, the core-to-core configuration information of the service system 70 may be generated according to the service flow data, where the core-to-core configuration information may include a unique identification ID of the core-to-core and the service scenario information associated therewith.
Step 2): the core-to-point configuration information is sent to the first component 101.
Step 3): the first component 101 determines a core point in the service system 70 based on the core point configuration information.
For example, the location determination between the step 1 and the step 2 may be regarded as the core point P. The first component 101 can determine from the core-to-point configuration information where the data stream should be obtained, i.e. in this embodiment from a position between step 1 and step 2.
Step 4): the second component 102 of the first system 10 receives the collation data stream acquired by the first component 101 from the core point.
Illustratively, the verification data stream is copied from the point of verification P upon determination of the point of verification P, such as from a location between step 1 and step 2 in the business process shown in fig. 7. The check data stream may carry a unique identification ID of the check point to identify from which service scenario in service system 70 the check data stream came.
Step 5): the first system 10 checks the check data stream to generate a check result.
Specifically, the second component 102 may receive the check data stream obtained from the location between step 1 and step 2 in the business process, and send the check data stream to the corresponding check module according to the unique identifier ID for check processing, where the specific check processing procedure may refer to the detailed description in the foregoing method embodiments.
In this embodiment, only the first component 101 is set in the service system 70 to determine the checking point P and obtain the checking data, and the checking is directly performed without adding a checking code in the service system 70, but the first system 10 outside the service system 70 performs the checking after obtaining the checking data, so as to reduce the amount of the checking code added in the service system 70, and reduce the intrusion of the checking code into the service system 70, thereby reducing the influence on the service system 70, improving the working stability and the original service correctness of the service system 70, and making the service system 70 more compact. Meanwhile, the check points can be flexibly configured outside the service system 70 through the first system 10 to carry out subsequent check processing, so that the check points can be flexibly arranged for check, and the check flexibility is better. Based on the embodiment, a more comprehensive monitoring means can be implemented on the verification system 10 side, so as to provide a more comprehensive service prevention and control capability for the main system, i.e. the service system 70.
The embodiment of the specification also provides a business data processing method which is applied to a first component which is pre-configured in a second system through a first system; the method comprises the following steps:
receiving the core-to-point configuration information of the second system generated by the first system;
and determining the core point in the second system according to the core point configuration information.
According to the service data processing method provided by the embodiment of the specification, a first component receives the core-to-point configuration information of the second system generated by a first system, and the first component determines a core-to-point in the second system according to the core-to-point configuration information. In this embodiment, the first component is set in the second system to determine the verification point, and the verification is directly performed without adding the verification code in the second system, so as to reduce the amount of the verification code added in the second system, and reduce the intrusion of the verification code into the second system, thereby reducing the influence on the second system and improving the working stability of the second system. Meanwhile, the check points can be flexibly configured outside the second system through the first system to carry out subsequent check processing, so that the check points can be flexibly arranged to check, and the check flexibility is good.
In one embodiment of the present specification, the check point configuration information is generated by check requirement information of the second system; the core point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
In one embodiment of the present disclosure, the step of determining the core point in the second system according to the core point configuration information includes:
and determining one or more corresponding core points in the second system according to the service scene information of the core points.
In one embodiment of the present specification, the service context information includes at least one core point location information; the step of determining one or more corresponding core points in the second system according to the service scene information of the core points comprises the following steps:
and determining corresponding one or more core points in the second system according to the at least one core point position information.
In this embodiment, the steps of the service data processing method are described by using the first component as an execution body, and specific details may refer to corresponding detailed descriptions in the foregoing embodiment of the service data processing method using the first system as an execution body, which are not repeated herein.
Corresponding to the above method embodiments, the present disclosure further provides an embodiment of a service data processing system, and fig. 8 shows a schematic structural diagram of a service data processing system according to an embodiment of the present disclosure. As shown in fig. 8, the system includes a configuration information generation unit 802, a configuration information processing unit 804, and a first component 101; wherein:
the configuration information generating unit 802 is configured to generate the core-to-point configuration information of the second system 20;
the configuration information processing unit 804 is configured to send the core-to-point configuration information to the first component 101;
the first component 101 is configured in advance in the second system, and is configured to determine a core point in the second system according to the core point configuration information.
The service data processing system provided in the embodiment of the present disclosure generates a core-to-core configuration information of the second system, and the first system sends the core-to-core configuration information to a first component preset in the second system, where the first component determines a core-to-core point in the second system according to the core-to-core configuration information. In this embodiment, the first component is set in the second system to determine the verification point, and the verification is directly performed without adding the verification code in the second system, so as to reduce the amount of the verification code added in the second system, and reduce the intrusion of the verification code into the second system, thereby reducing the influence on the second system and improving the working stability of the second system. Meanwhile, the check points can be flexibly configured outside the second system through the first system to carry out subsequent check processing, so that the check points can be flexibly arranged to check, and the check flexibility is good.
Optionally, in an embodiment of the present disclosure, the configuration information generating unit 802 is further configured to generate, according to the verification requirement information of the second system, core-to-core configuration information, where the core-to-core configuration information includes at least a unique identifier of a core-to-core point and service scenario information to which the core-to-core point associated with the unique identifier belongs.
Optionally, in an embodiment of the present specification, the first component is further configured to determine, in the second system, a corresponding one or more core points according to the traffic scenario information to which the core points belong.
Optionally, in one embodiment of the present specification, the service scenario information includes at least one core-to-point location information; the first component is further configured to determine a respective one or more core points in the second system based on the at least one core point location information.
Optionally, in an embodiment of the present specification, the data checking unit is further configured to receive a check data stream acquired by the first component from the check point, and check the check data stream to generate a check result.
Optionally, in one embodiment of the present specification, an abnormality processing unit is further included that is configured to determine whether the collation result is abnormal; in response to determining that the verification result is abnormal, throwing an abnormal notification to the second system so as to enable the second system to fuse current processing business; or, in response to determining that the collation result is abnormal, issuing an alarm prompt.
Optionally, in an embodiment of the present specification, the first system includes a second component configured within the first system. The data collation unit is further configured to receive the collation data stream through the second component.
Optionally, in an embodiment of the present specification, the check data stream of the core point includes a unique identifier of the core point. The second component is configured to determine a checking module corresponding to the checking point according to the unique identifier of the checking point and a preset mapping table; the preset mapping table comprises a mapping relation between a unique identifier of at least one checking point and at least one corresponding checking module;
the second component is further configured to forward the collation data stream to the determined collation module, so that the determined collation module performs real-time collation or delay collation on the collation data stream and outputs a collation result.
Optionally, in an embodiment of the present disclosure, the system further includes a writing module configured to write a verification module that generates a match with the core point when the second component does not query the verification module corresponding to the core point according to the unique identifier of the core point and a preset mapping table, so that the generated verification module verifies the verification data stream and outputs a verification result.
Optionally, in one embodiment of the present specification, the system further includes a gray level checking unit configured to determine a service scenario corresponding to the core point according to a unique identifier of the core point included in the core point checking data stream; judging whether the service scene is in a preset service scene list or not; responding to the business scene in a preset business scene list, and checking the check data flow to generate a check result; responding to the fact that the service scene is not in a preset service scene list, and sending a notification message to the first component through the second component; the notification message is used for indicating the first component to acquire a preset percentage of check data flow from a check point configured in the second system.
The foregoing is a schematic solution of a service data processing system of this embodiment. It should be noted that, the technical solution of the service data processing system and the technical solution of the service data processing method belong to the same conception, and details of the technical solution of the service data processing system, which are not described in detail, can be referred to the description of the technical solution of the service data processing method.
Corresponding to the method embodiments described above, the present embodiments also provide a first component that is preconfigured in the second system via the first system, that is, the first component belongs to the first system. As shown in fig. 9, the first assembly includes:
a receiving unit 902 configured to receive the first system generated core-to-core point configuration information of the second system;
a determining unit 904 configured to determine a core point in the second system according to the core point configuration information.
Optionally, in one embodiment of the present specification, the check point configuration information is generated by check requirement information of the second system; the core point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
Optionally, in an embodiment of the present specification, the determining unit 904 is further configured to determine, in the second system, a corresponding one or more core points according to the service scenario information to which the core point belongs.
Optionally, in an embodiment of the present specification, the service scenario information includes at least one core-to-point location information. Accordingly, the determining unit 904 is further configured to determine a corresponding one or more core points in the second system according to the at least one core point location information.
The above is a schematic version of a first component of the present embodiment. It should be noted that, the technical solution of the first component and the technical solution of the service data processing method applied to the first component belong to the same concept, and details of the technical solution of the first component, which are not described in detail, can be referred to the description of the technical solution of the service data processing method applied to the first component.
Fig. 10 illustrates a block diagram of a computing device 1000 provided in accordance with an embodiment of the present specification. The components of the computing device 1000 include, but are not limited to, a memory 1010 and a processor 1020. Processor 1020 is coupled to memory 1010 via bus 1030 and database 1050 is used to store data.
Computing device 1000 also includes access device 1040, which access device 1040 enables computing device 1000 to communicate via one or more networks 1060. Examples of such networks include the Public Switched Telephone Network (PSTN), a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The access device 1040 may include one or more of any type of network interface, wired or wireless (e.g., a Network Interface Card (NIC)), such as an IEEE802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 1000, as well as other components not shown in FIG. 10, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device illustrated in FIG. 10 is for exemplary purposes only and is not intended to limit the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 1000 may be any type of stationary or mobile computing device including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smart phone), wearable computing device (e.g., smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 1000 may also be a mobile or stationary server.
Wherein the processor 1020 is configured to execute computer-executable instructions to implement the steps of the business data processing method described in any of the embodiments above. Specific steps may refer to the descriptions in the foregoing method embodiments, and are not repeated here.
The foregoing is a schematic illustration of a computing device of this embodiment. It should be noted that, the technical solution of the computing device and the technical solution of the service data processing method belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the service data processing method.
An embodiment of the present disclosure also provides a computer readable storage medium storing computer instructions that, when executed by a processor, implement the steps of the business data processing method of any one of the above embodiments.
The above is an exemplary version of a computer-readable storage medium of the present embodiment. It should be noted that, the technical solution of the storage medium and the technical solution of the service data processing method belong to the same concept, and details of the technical solution of the storage medium which are not described in detail can be referred to the description of the technical solution of the service data processing method.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
It should be noted that, for the sake of simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the present description is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present description. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all necessary in the specification.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.
The preferred embodiments of the present specification disclosed above are merely used to help clarify the present specification. Alternative embodiments are not intended to be exhaustive or to limit the invention to the precise form disclosed. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the disclosure and the practical application, to thereby enable others skilled in the art to best understand and utilize the disclosure. This specification is to be limited only by the claims and the full scope and equivalents thereof.
Claims (17)
1. A business data processing method, the method is applied to a first system, and the first system is pre-configured with a first component in a second system; the method comprises the following steps:
the first system generates the core-to-point configuration information of the second system;
the first system sends the core-to-point configuration information to the first component;
the first component determines a core point in the second system according to the core point configuration information;
the first system receiving a check data stream acquired by the first component from the point of verification;
the first system checks the check data stream to generate a check result.
2. The method of claim 1, the step of the first system generating core-to-point configuration information for the second system comprising:
and generating the core-point configuration information according to the core-requirement information of the second system, wherein the core-point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
3. The method of claim 2, the first component determining a core point in the second system based on the core point configuration information, comprising:
And the first component determines one or more corresponding core points in the second system according to the business scene information of the core points.
4. The method of claim 3, the traffic scenario information comprising at least one core point location information;
the step of determining, by the first component, one or more corresponding core points in the second system according to the service scenario information to which the core points belong, includes:
and determining corresponding one or more core points in the second system according to the at least one core point position information.
5. The method of claim 1, further comprising:
the first system determines whether the collation result is abnormal;
in response to determining that the verification result is abnormal, throwing an abnormal notification to the second system so as to enable the second system to fuse current processing business; or alternatively
An alarm prompt is issued in response to determining that the collation result is abnormal.
6. The method of claim 1, the first system comprising a second component configured within the first system;
the step of the first system receiving a check data stream acquired by the first component from the point of verification comprises: the collation data stream is received by the second component.
7. The method of claim 6, wherein the check data stream of the point of interest comprises a unique identification of the point of interest;
the step of the first system collating the collation data stream to generate a collation result includes:
the second component queries and determines a checking module corresponding to the checking point according to the unique identifier of the checking point and a preset mapping table; the preset mapping table comprises a mapping relation between a unique identifier of at least one checking point and at least one corresponding checking module;
the second component forwards the collation data stream to the determined collation module so that the determined collation module performs real-time collation or delay collation on the collation data stream and outputs a collation result.
8. The method of claim 7, further comprising:
and when the second component does not inquire the checking module corresponding to the checking point according to the unique identification of the checking point and a preset mapping table, writing the checking module which is generated to be matched with the checking point, so that the checking data flow is checked through the generated checking module, and a checking result is output.
9. The method of claim 7, further comprising:
Determining a service scene corresponding to the check point according to the unique identifier of the check point contained in the check data flow of the check point;
judging whether the service scene is in a preset service scene list or not;
responding to the business scene in a preset business scene list, and checking the check data flow to generate a check result;
responding to the fact that the service scene is not in a preset service scene list, and sending a notification message to the first component through the second component; the notification message is used for indicating the first component to acquire a preset percentage of check data flow from a check point configured in the second system.
10. A business data processing system comprises a configuration information generating unit, a configuration information processing unit, a first component and a data checking unit; wherein:
the configuration information generating unit is used for generating the core-to-point configuration information of the second system;
the configuration information processing unit is used for sending the core-to-point configuration information to the first component;
the first component is pre-configured in the second system and is used for determining a core point in the second system according to the core point configuration information;
The data collation unit is configured to receive a collation data stream acquired by the first component from the collation point, and collate the collation data stream to generate a collation result.
11. A business data processing method applied to a first component pre-configured to a second system via a first system, the method comprising:
receiving the core-to-point configuration information of the second system generated by the first system;
determining a core point in the second system according to the core point configuration information;
and obtaining a check data stream from the check point and sending the check data stream to the first system for the first system to check to generate a check result.
12. The method of claim 11, the audit point configuration information generated by audit demand information of the second system; the core point configuration information at least comprises a unique identifier of the core point and service scene information of the core point associated with the unique identifier.
13. The method of claim 12, the step of determining a core point in the second system based on the core point configuration information, comprising:
and determining one or more corresponding core points in the second system according to the service scene information of the core points.
14. The method of claim 13, the traffic scenario information comprising at least one core point location information; the step of determining one or more corresponding core points in the second system according to the service scene information of the core points comprises the following steps:
and determining corresponding one or more core points in the second system according to the at least one core point position information.
15. A first component pre-configured in a second system via a first system; the first assembly includes:
the receiving unit is used for receiving the core-to-point configuration information of the second system generated by the first system;
a determining unit, configured to determine a core point in the second system according to the core point configuration information; and obtaining a check data stream from the check point and sending the check data stream to the first system for the first system to check to generate a check result.
16. A computing device, comprising:
a memory and a processor;
the memory is for storing computer executable instructions and the processor is for executing the computer executable instructions to implement the steps of the method of any one of claims 1 to 9 or any one of claims 10 to 14.
17. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 9 or any one of claims 10 to 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010286149.6A CN111476659B (en) | 2020-04-13 | 2020-04-13 | Service data processing method, system, component, computing device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010286149.6A CN111476659B (en) | 2020-04-13 | 2020-04-13 | Service data processing method, system, component, computing device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111476659A CN111476659A (en) | 2020-07-31 |
| CN111476659B true CN111476659B (en) | 2023-08-15 |
Family
ID=71751506
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010286149.6A Active CN111476659B (en) | 2020-04-13 | 2020-04-13 | Service data processing method, system, component, computing device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111476659B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004234257A (en) * | 2003-01-29 | 2004-08-19 | Hitachi Ltd | Detailed receipt transaction audit method, system and program, and recording medium |
| CN101075337A (en) * | 2007-07-20 | 2007-11-21 | 中国建设银行股份有限公司 | Method and system for verifying data |
| CN104573946A (en) * | 2014-12-26 | 2015-04-29 | 北京奇虎科技有限公司 | Processing method and system of business object data |
| CN108694664A (en) * | 2018-06-05 | 2018-10-23 | 阿里巴巴集团控股有限公司 | Checking method and device, the electronic equipment of operation system |
| CN110046153A (en) * | 2018-11-19 | 2019-07-23 | 阿里巴巴集团控股有限公司 | A kind of method, device and equipment of account fund verification |
| CN110213071A (en) * | 2018-04-16 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Verification of data method, apparatus, system, computer equipment and storage medium |
| CN110750530A (en) * | 2019-09-11 | 2020-02-04 | 口碑(上海)信息技术有限公司 | Service system and data checking method thereof |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3480771A1 (en) * | 2017-11-06 | 2019-05-08 | Tata Consultancy Services Limited | Method and system for managing exceptions during reconciliation of transactions |
-
2020
- 2020-04-13 CN CN202010286149.6A patent/CN111476659B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004234257A (en) * | 2003-01-29 | 2004-08-19 | Hitachi Ltd | Detailed receipt transaction audit method, system and program, and recording medium |
| CN101075337A (en) * | 2007-07-20 | 2007-11-21 | 中国建设银行股份有限公司 | Method and system for verifying data |
| CN104573946A (en) * | 2014-12-26 | 2015-04-29 | 北京奇虎科技有限公司 | Processing method and system of business object data |
| CN110213071A (en) * | 2018-04-16 | 2019-09-06 | 腾讯科技（深圳）有限公司 | Verification of data method, apparatus, system, computer equipment and storage medium |
| CN108694664A (en) * | 2018-06-05 | 2018-10-23 | 阿里巴巴集团控股有限公司 | Checking method and device, the electronic equipment of operation system |
| CN110046153A (en) * | 2018-11-19 | 2019-07-23 | 阿里巴巴集团控股有限公司 | A kind of method, device and equipment of account fund verification |
| CN110750530A (en) * | 2019-09-11 | 2020-02-04 | 口碑(上海)信息技术有限公司 | Service system and data checking method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111476659A (en) | 2020-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108764868B (en) | Block chain node proxy reconciliation method and block reconciliation proxy node | |
| EP3889870B1 (en) | Background architecture method and system for aggregation payment, computer device, and storage medium | |
| CN110730472B (en) | Communication certificate state detection method and server | |
| CN112351392B (en) | Cloud communication short message service platform | |
| JP2022517869A (en) | How to provide roaming service using blockchain and equipment for that | |
| KR102145578B1 (en) | Method and Apparatus for Providing Roaming Service using Block Chain | |
| CN108075911B (en) | Service testing method and device | |
| CN111476659B (en) | Service data processing method, system, component, computing device and storage medium | |
| US11349996B2 (en) | Offline charging of communications services | |
| CN100544505C (en) | The method that limits according to the flow of authorizing short-message system | |
| CN104539637B (en) | Sending method, server and the user terminal of information of check code | |
| CN101662731B (en) | Digital group system terminal and method for reporting GPS positioning information thereof | |
| CN103188084B (en) | Method, system and the broadcasting server of a kind of broadcasting user picture | |
| CN102316076B (en) | Method, device and system for recognizing cross-network system user | |
| CN110209556B (en) | Disaster tolerance testing method, payment method, device, medium and service equipment | |
| CN108848061B (en) | User information transmission method and terminal equipment | |
| KR102107454B1 (en) | System for multiplication of financial payment networks, method for financial services using the same and computer program for the same | |
| CN101860445B (en) | Value-added service charging method and system | |
| CN113850683A (en) | Car insurance inquiry request processing method and device, computer equipment and storage medium | |
| US20220253841A1 (en) | Method for providing neutral host network service by using blockchain, and system and device therefor | |
| CN112836479A (en) | Data report generation method, system and storage device | |
| CN106936602A (en) | Network charging method and device based on internet of things equipment | |
| CN111311395A (en) | Management system, method, equipment and storage medium for public accumulation fund repayment business | |
| CN113259879B (en) | Roaming payment method, system, terminal device and storage medium based on block chain | |
| CN112990903B (en) | Block chain-based telephone charge transfer method, transferable node and demand node |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |