CN107153646B - Data processing method and equipment - Google Patents
Data processing method and equipment Download PDFInfo
- Publication number
- CN107153646B CN107153646B CN201610118569.7A CN201610118569A CN107153646B CN 107153646 B CN107153646 B CN 107153646B CN 201610118569 A CN201610118569 A CN 201610118569A CN 107153646 B CN107153646 B CN 107153646B
- Authority
- CN
- China
- Prior art keywords
- event
- service
- message
- contained
- business
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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
Abstract
The application discloses a data processing method and equipment, which comprise the following steps: receiving service event messages sent by different service systems; selecting an event checking model matched with the business event contained in the business event message and the calling relationship among different business systems according to the business event contained in the business event message and the calling relationship among different business systems, and checking the business event contained in the business event message by using the event checking model, wherein the event checking model is used for checking whether a business event chain is complete; when the completeness of an event chain formed by the service events contained in the service event message is determined, the data associated with the event chain is synchronized, and the data is checked, so that the problem that the data generated when complex services are processed cannot be checked in real time in the prior art is effectively solved, the time delay of data checking is shortened, and inaccurate data appearing in a system can be found in time.
Description
Technical Field
The present application relates to the field of internet information processing technologies, and in particular, to a data processing method and device.
Background
With the development of science and technology, more and more complex services are loaded on a computer, and the complex services are processed by utilizing the characteristics of high operation speed, convenience in operation and the like of the computer. Meanwhile, in order to ensure the accuracy of complex business processing, data maintenance needs to be performed on data generated in the complex business processing process, that is, the generated data is stored in different databases.
When a data checking time period is up, data stored in different databases are synchronized to a data warehouse, and data generated from the previous data checking time period to the current data checking time period are checked to judge whether errors occur in the process of processing complex services.
However, in practical applications, if a homogeneous system is formed between a data warehouse and different databases, the data checking time has a large delay relative to the data generating time, which means that errors occurring in the processing process of complex services cannot be found in time; if a heterogeneous system is formed between the data warehouse and different databases, under the condition that the problems cannot be avoided, when the data stored in the different databases are synchronized to the data warehouse, the data formats in the different databases need to be uniformly converted, the workload of the data checking process is increased, a large amount of system resources are occupied, and the data checking efficiency is reduced.
Disclosure of Invention
In view of this, embodiments of the present application provide a data processing method and device, which are used to solve the problem that real-time checking of data generated when a complex service is processed cannot be implemented in the prior art.
A method of data processing, comprising:
receiving service event messages sent by different service systems, wherein each service event message is used for representing that data in the service system generating the service event message changes;
selecting an event checking model matched with the business event contained in the business event message and the calling relationship among different business systems according to the business event contained in the business event message and the calling relationship among different business systems, and checking the business event contained in the business event message by using the event checking model, wherein the event checking model is used for checking whether a business event chain is complete;
and when the event chain formed by the service events contained in the service event message is determined to be complete, synchronizing the data associated with the event chain and checking the data.
A data processing apparatus comprising:
a receiving unit, configured to receive service event messages sent by different service systems, where each of the service event messages is used to represent a change in data in a service system that generates the service event message;
a checking unit, configured to select an event checking model matching the service event included in the service event message and the call relationship between different service systems according to the service event included in the service event message and the call relationship between different service systems, and check the service event included in the service event message by using the event checking model, where the event checking model is used to check whether a service event chain is complete;
and the processing unit is used for synchronizing data associated with the event chain and checking the data when the event chain formed by the service events contained in the service event message is determined to be complete.
The beneficial effect of this application is as follows:
the method comprises the steps that service event messages sent by different service systems are received, and each service event message is used for representing that data in the service system generating the service event message are changed; selecting an event checking model matched with the business event contained in the business event message and the calling relationship among different business systems according to the business event contained in the business event message and the calling relationship among different business systems, and checking the business event contained in the business event message by using the event checking model, wherein the event checking model is used for checking whether a business event chain is complete; and when the event chain formed by the service events contained in the service event message is determined to be complete, synchronizing the data associated with the event chain and checking the data. The method comprises the steps that when a business system processes business, not only are business events used for representing business processing progress generated, but also data used for representing a business processing process are generated.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a data processing method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an event collation model;
fig. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a business system;
FIG. 5 is a diagram illustrating an event reconciliation model corresponding to the business system shown in FIG. 4;
fig. 6 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
Detailed Description
In order to achieve the purpose of the present application, embodiments of the present application provide a data processing method and device, which receive service event messages sent by different service systems, where each of the service event messages is used to represent a change in data in a service system that generates the service event message; selecting an event checking model matched with the business event contained in the business event message and the calling relationship among different business systems according to the business event contained in the business event message and the calling relationship among different business systems, and checking the business event contained in the business event message by using the event checking model, wherein the event checking model is used for checking whether a business event chain is complete; and when the event chain formed by the service events contained in the service event message is determined to be complete, synchronizing the data associated with the event chain and checking the data.
The method comprises the steps that when a business system processes business, not only are business events used for representing business processing progress generated, but also data used for representing a business processing process are generated.
Various embodiments of the present application are described in further detail below with reference to the figures of the specification. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a schematic flowchart of a data processing method according to an embodiment of the present application. The method may be as follows.
Step 101: and receiving service event messages sent by different service systems.
Wherein each of the service event messages is used for representing the data change in the service system generating the service event message.
In step 101, assume that there is a complex service processing system, where the service processing system includes a plurality of different service systems, and each service system can process a service independently, or can establish a call relationship with other service systems to assist the other service systems in completing processing of the complex service.
Each service system generates not only service event messages but also service processing data when processing services. The service event message contains a service event, and the service event is used for recording an event that the service function is changed when the service system processes the service. For example: a funds exchange system in a financial system, upon the occurrence of an exchange of funds, will accordingly generate an exchange event message characterizing the funds exchange event, the exchange event message including the event of the funds exchange.
When a service event occurs in the service system, it means that service data related to the service event will be generated in the service system, and the generated service data will cause a change in data in the service system, either increasing the data volume in the service system or updating the data in the service system, which is not limited herein.
It should be noted that, in step 101, the service event messages sent by different service systems may be received in real time, or the service event messages sent by different service systems may be received periodically; and may also receive service event messages sent by multiple service systems at the same time, which is not limited herein.
Step 102: and selecting an event checking model matched with the service event contained in the service event message and the calling relationship among different service systems according to the service event contained in the service event message and the calling relationship among different service systems, and checking the service event contained in the service event message by using the event checking model.
Wherein the event checking model is used for checking whether a business event chain is complete.
In step 102, for a complex service processing system, for different services, a call relationship between different service systems used by each service in the execution process may be determined, and an event checking model for the service may be established using the call relationship.
Thus, for different services, an event checking model matched with the service can be established. Each event checking model comprises business events which need to occur when the business is executed and logic relations among the business events. And judging whether an event chain constructed by the service events generated in the service execution process is complete or not by using the event checking model.
For example: a complex service processing system comprises a service system A, a service system B, a service system C, a service system D, a service system E and a service system F, wherein a calling relationship exists among the service system A, the service system B, the service system C, the service system D, the service system E and the service system F. If a service event occurs in the service system A, the service system B can be triggered to generate a new service event, the new service event generated by the service system B affects the service system C and the service system D, the service event of the service system C affects the service system E, and the service event of the service system D affects the service system F. Then a schematic diagram of the event reconciliation model shown in fig. 2 can be obtained according to the above-mentioned calling relationship (or influence relationship) between the business systems. As can be seen from fig. 2, the obtained event checking model may be represented by a tree structure, where the tree structure includes a plurality of nodes, each node (which may be referred to as an event node) may correspond to a service event, and a relationship between the nodes satisfies a call relationship between service systems. Therefore, after the event checking model is obtained, the logical relationship between each node in the event checking model can be used to judge whether the received service event constitutes a complete event chain.
In this embodiment of the present application, when receiving a service event message sent by different service systems in step 101, determining a call relationship between the service systems that send the service event message, and selecting an event collation model that matches the service event contained in the service event message and the call relationship between the different service systems from a pre-established event collation model library according to the service event contained in the service event message and the call relationship between the different service systems.
The event collation model included in the pre-established event collation model library may be determined based on the service type, or may be determined based on the call relationship between different service systems, which is not specifically limited herein.
After determining the event checking model, the method for checking the service event contained in the service event message by using the event checking model includes, but is not limited to, the following methods:
the first mode is as follows:
determining the occurrence time of the service event contained in each received service event message; and determining the calling relationship among the business events contained in different business event messages according to the occurrence time, and comparing the calling relationship with the logic relationship among the event nodes contained in the event checking model.
The second mode is as follows:
determining the occurrence time of the service event contained in each received service event message; according to the logic relation between the occurrence time and the event nodes contained in the event checking model, sequentially establishing the corresponding relation between the business event and the event nodes contained in the event checking model; and scanning the event checking model at fixed time, and determining whether the event node contained in the event checking model corresponds to the service event.
Based on the two modes, for a service with strong real-time performance, a first mode can be adopted, namely, aiming at one service, the occurrence time difference of service events generated by different service systems is not large, namely, service event messages sent by different service systems can be received within a short time, and then the operation of checking the service events contained in the service event messages can be rapidly completed according to the first mode;
for the service with poor real-time performance, a second mode can be adopted, due to some reasons, some service systems are abnormal, and the service cannot be correctly processed, so that the occurrence time of the service events generated by different service systems is relatively large, at this time, the corresponding relation between the service events and the event nodes contained in the event check model can be established according to the received service event messages containing the service events, and the event check model is scanned at regular time, so that the operation of checking the service events contained in the service event messages is completed. It should be noted that, if the time period of the timing scan is too long (greater than the set time length), the process is performed according to a situation that the event chain formed by the service events included in the service event message is determined to be incomplete.
Step 103: judging whether an event chain formed by the service events contained in the service event message is complete or not according to the check result, and if so, executing the step 104; otherwise, step 105 is performed.
Step 104: and when the event chain formed by the service events contained in the service event message is determined to be complete, synchronizing the data associated with the event chain and checking the data.
In step 104, if the service event included in the service event message is checked in the first manner in step 102, it is determined that an event chain formed by the service event included in the service event message is complete if the comparison result is that the calling relationship is consistent with the logical relationship between the event nodes included in the event checking model.
If the service event included in the service event message is checked in the step 102 in the second manner, when it is determined that each event node included in the event checking model has established a corresponding relationship with the service event included in the service event message, it is determined that an event chain formed by the service event included in the service event message is complete.
In step 103, it is determined that the event chain formed by the service events included in the service event message completely indicates that the service processing flow is correct, and at this time, the data associated with the event chain is synchronized and checked, so that the checking operation on the data associated with the event chain can be realized, and the real-time checking on the data can be effectively realized.
That is to say, in the embodiment of the present application, the data synchronization is completed by real-time synchronization of real-time service event messages, and since the real-time synchronization of the service event messages can achieve second-level synchronization in some application scenarios, it also means that the data can also achieve second-level synchronization and check, thereby effectively solving the problem that the real-time check of data generated when complex services are processed cannot be achieved in the prior art, shortening the time delay of data check, and being capable of timely finding inaccurate data appearing in the system.
Step 105: and sending out an alarm message when the event chain formed by the service events contained in the service event message is determined to be incomplete.
Wherein the alarm message is used to remind the data associated with the event chain of an error.
In step 105, once it is determined that the event chain formed by the service events included in the service event message is incomplete, which indicates that an abnormality occurs in the service execution process, the system generates inaccurate data, and at this time, an alarm message needs to be sent to remind a manager or a system maintainer of the system to notice so as to discover the inaccurate data (or referred to as difference data) occurring in the system in time.
According to the technical scheme provided by the embodiment of the application, when the business system processes the business, the business event used for representing the business processing progress is generated, and the data used for representing the business processing process is also generated.
Fig. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application. The data processing illustrated in fig. 3 may be implemented based on a financial system.
Assume that a financial system includes a credit business system (reference numeral 1), an asset exchange system (reference numeral 2), a deposit core system (reference numeral 3), a loan core system (reference numeral 4), a debit accounting system (reference numeral 5), and a credit accounting system (reference numeral 6), as shown in fig. 4, which is a schematic view of the structure of the business system. Then, according to the calling relationship between the business systems in the financial system, an event checking model for the financial system may be determined, as shown in fig. 5, which is a structural diagram of the event checking model corresponding to the business system shown in fig. 4.
The message center shown in fig. 4 is configured to receive the service event messages sent by the service systems, and the main fields included in the service event message and the meaning of each field are as shown in table 1 below:
TABLE 1
The following describes in detail the detailed application of the technical solutions described in the embodiments of the present application in an assumed scenario.
Step 301: and receiving the service event message sent by each service system.
For example: business event information sent by a credit business system; an exchange event message sent by the asset exchange system; deposit event information sent by a deposit core system; a loan event message sent by the loan core system; a debit event message sent by the debit accounting system; a credit event message sent by the credit accounting system.
Step 302: the service event included in the received service event message is checked using the event checking model shown in fig. 5.
In step 302, for the credit business system to send a repayment event message a to the message center, some key information, such as business order number and amount of money, is recorded in the data field in the repayment event message in the credit business system platform; and calling the asset exchange system, wherein at the same time, a data field in a service event message B of a platform of the asset exchange system also records some key information, such as debit amount (debit _ amount) and credit amount (credit _ amount), and at this time, a repayment event contained in a repayment event message sent by the credit service system can be checked by using sum ({ a }. amount) ═ sum ({ B }. debit _ amount) } sum ({ B }. credit _ amount).
For a current expenditure event message C and a repayment event message D sent by an asset exchange system, the asset exchange system calls a deposit core system to execute a current expenditure event, and key field information such as an expenditure amount is recorded in a data field of a deposit core system platform for the current expenditure event; meanwhile, the property exchange system also calls a loan core system to execute a repayment event, and key fields of principal amount (prin _ account) and interest amount (int _ account) are recorded in a data field of the record of the repayment event in the loan core system platform. At this time, the checking may be performed by using the live expense event message C and the repayment event message D transmitted by the asset exchange system, where the asset exchange system is capable of checking the live expense event message C and the repayment event message D.
For the current expenditure event message sent by the deposit core system, the loan core system calls the credit accounting system to repay the balance expenditure of the user, and key field information such as the expenditure amount and the like is recorded in a data field in the credit accounting event message E generated by the loan core system. At this time, the demand-expenditure event message transmitted by the deposit core system may be checked using sum ({ C }. account) ═ sum ({ E }. account).
For a repayment event D sent by the loan core system, the loan core system calls the credit accounting system to execute a repayment operation and an interest reduction operation, the credit accounting system generates a repayment event message F and an interest reduction event message G, and key field information such as the amount is recorded in a data field in the repayment event message F/the interest reduction event message G. At this time, the repayment event D transmitted by the loan core system may be checked using sum ({ D }. print _ account) ═ sum ({ F }. account) & & sum ({ D }. int _ account) ═ sum ({ G }. account).
Debiting a demand expense event message sent by the accounting system; the credit accounting system also receives principal event messages and interest event messages.
Step 303: and when the event chain formed by the service events contained in the service event message is determined to be complete, synchronizing the data associated with the event chain and checking the data.
Fig. 6 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application. The data processing apparatus includes: a receiving unit 61, a collating unit 62, and a processing unit 63, wherein:
a receiving unit 61, configured to receive service event messages sent by different service systems, where each of the service event messages is used to represent a change in data in the service system that generates the service event message;
a checking unit 62, configured to select an event checking model matching the service event included in the service event message and the call relationship between different service systems according to the service event included in the service event message and the call relationship between different service systems, and check the service event included in the service event message by using the event checking model, where the event checking model is used to check whether a service event chain is complete;
and the processing unit 63 is configured to, when it is determined that an event chain formed by the service events included in the service event message is complete, synchronize data associated with the event chain, and check the data.
In another embodiment of the present application, the processing unit 63 is further configured to issue an alarm message when it is determined that an event chain formed by the business events included in the business event message is incomplete, where the alarm message is used to remind a data associated with the event chain of an error.
In another embodiment of the present application, the checking unit 62 checks the service event included in the service event message by using the event checking model, including:
determining the occurrence time of the service event contained in each received service event message;
and determining the calling relationship among the business events contained in different business event messages according to the occurrence time, and comparing the calling relationship with the logic relationship among the event nodes contained in the event checking model.
In another embodiment of the present application, the determining, by the processing unit 63, that an event chain formed by the service events included in the service event message is complete includes:
and when the comparison result is that the calling relation is consistent with the logic relation between the event nodes contained in the event checking model, determining that an event chain formed by the service events contained in the service event message is complete.
In another embodiment of the present application, the checking unit 62 checks the service event included in the service event message by using the event checking model, including:
determining the occurrence time of the service event contained in each received service event message;
according to the logic relation between the occurrence time and the event nodes contained in the event checking model, sequentially establishing the corresponding relation between the business event and the event nodes contained in the event checking model;
and scanning the event checking model at fixed time, and determining whether the event node contained in the event checking model corresponds to the service event.
In another embodiment of the present application, the determining, by the processing unit 63, that an event chain formed by the service events included in the service event message is complete includes:
and when determining that each event node contained in the event checking model establishes a corresponding relation with the service event contained in the service event message, determining that an event chain formed by the service event contained in the service event message is complete.
It should be noted that the data processing device described in the embodiment of the present application may be implemented in a software manner or a hardware manner, which is not limited herein, and may check data associated with a generated service event in time by means of real-time performance generated by the service event, so as to effectively solve the problem that real-time checking of data generated when a complex service cannot be processed in the prior art, shorten a time delay of data checking, and find inaccurate data occurring in a system in time.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus (device), or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A data processing method, comprising:
receiving service event messages sent by different service systems, wherein each service event message is used for representing that data in the service system generating the service event message changes;
selecting an event checking model matched with the business events contained in the business event message and the calling relations among different business systems according to the business events contained in the business event message and the calling relations among different business systems, and checking the business events contained in the business event message by using the event checking model, wherein the event checking model is used for checking whether a business event chain is complete, and the event checking model comprises the business events required to be generated for executing the business and the logic relations among all the business events;
when determining that an event chain formed by the service events contained in the service event message is complete, synchronizing data associated with the event chain and checking the data;
the checking the service event included in the service event message by using the event checking model includes:
determining the occurrence time of the service event contained in each received service event message;
and determining the calling relationship among the business events contained in different business event messages according to the occurrence time, and comparing the calling relationship with the logic relationship among the event nodes contained in the event checking model.
2. The data processing method of claim 1, wherein the method further comprises:
and sending an alarm message when the event chain formed by the business events contained in the business event message is determined to be incomplete, wherein the alarm message is used for reminding that data associated with the event chain has errors.
3. The data processing method of claim 1, wherein determining that an event chain formed by the service events included in the service event message is complete comprises:
and when the comparison result is that the calling relation is consistent with the logic relation between the event nodes contained in the event checking model, determining that an event chain formed by the service events contained in the service event message is complete.
4. The data processing method of claim 1, wherein checking the service event included in the service event message using the event checking model comprises:
determining the occurrence time of the service event contained in each received service event message;
according to the logic relation between the occurrence time and the event nodes contained in the event checking model, sequentially establishing the corresponding relation between the business event and the event nodes contained in the event checking model;
and scanning the event checking model at fixed time, and determining whether the event node contained in the event checking model corresponds to the service event.
5. The data processing method of claim 4, wherein determining that an event chain formed by the service events included in the service event message is complete comprises:
and when determining that each event node contained in the event checking model establishes a corresponding relation with the service event contained in the service event message, determining that an event chain formed by the service event contained in the service event message is complete.
6. A data processing apparatus, characterized by comprising:
a receiving unit, configured to receive service event messages sent by different service systems, where each of the service event messages is used to represent a change in data in a service system that generates the service event message;
a checking unit, configured to select an event checking model matching the service event included in the service event message and the call relationship between different service systems according to the service event included in the service event message and the call relationship between different service systems, and check the service event included in the service event message by using the event checking model, where the event checking model is used to check whether a service event chain is complete, and the event checking model includes service events that need to occur to execute a service and a logical relationship between the service events;
the processing unit is used for synchronizing data associated with the event chain and checking the data when determining that the event chain formed by the service events contained in the service event message is complete;
the checking unit checks the service event included in the service event message by using the event checking model, and includes:
determining the occurrence time of the service event contained in each received service event message;
and determining the calling relationship among the business events contained in different business event messages according to the occurrence time, and comparing the calling relationship with the logic relationship among the event nodes contained in the event checking model.
7. The data processing device of claim 6,
the processing unit is further configured to send an alarm message when it is determined that an event chain formed by the service events included in the service event message is incomplete, where the alarm message is used to remind that data associated with the event chain is incorrect.
8. The data processing device of claim 6, wherein the processing unit determines that an event chain formed by the service events included in the service event message is complete, comprising:
and when the comparison result is that the calling relation is consistent with the logic relation between the event nodes contained in the event checking model, determining that an event chain formed by the service events contained in the service event message is complete.
9. The data processing apparatus according to claim 6, wherein the collation unit collates the service event included in the service event message using the event collation model, comprising:
determining the occurrence time of the service event contained in each received service event message;
according to the logic relation between the occurrence time and the event nodes contained in the event checking model, sequentially establishing the corresponding relation between the business event and the event nodes contained in the event checking model;
and scanning the event checking model at fixed time, and determining whether the event node contained in the event checking model corresponds to the service event.
10. The data processing device of claim 9, wherein the processing unit determines that an event chain formed by the service events included in the service event message is complete, comprising:
and when determining that each event node contained in the event checking model establishes a corresponding relation with the service event contained in the service event message, determining that an event chain formed by the service event contained in the service event message is complete.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610118569.7A CN107153646B (en) | 2016-03-02 | 2016-03-02 | Data processing method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610118569.7A CN107153646B (en) | 2016-03-02 | 2016-03-02 | Data processing method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107153646A CN107153646A (en) | 2017-09-12 |
| CN107153646B true CN107153646B (en) | 2020-10-09 |
Family
ID=59791996
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610118569.7A Active CN107153646B (en) | 2016-03-02 | 2016-03-02 | Data processing method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107153646B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106060928A (en) * | 2016-04-20 | 2016-10-26 | 上海斐讯数据通信技术有限公司 | Thin AP (Access Point) event notification message processing method and thin AP device |
| CN108694664A (en) * | 2018-06-05 | 2018-10-23 | 阿里巴巴集团控股有限公司 | Checking method and device, the electronic equipment of operation system |
| CN109325055A (en) * | 2018-08-02 | 2019-02-12 | 阿里巴巴集团控股有限公司 | The screening of business association tables of data and checking method, device, electronic equipment |
| CN111899016A (en) * | 2018-10-31 | 2020-11-06 | 创新先进技术有限公司 | Quality data processing method and device based on block chain |
| CN110750530B (en) * | 2019-09-11 | 2022-08-02 | 口碑(上海)信息技术有限公司 | Service system and data checking method thereof |
| CN112419094B (en) * | 2020-08-12 | 2024-03-29 | 国网江西省电力有限公司信息通信分公司 | Power distribution Internet of things data product construction method and device and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1835014A (en) * | 2006-03-28 | 2006-09-20 | 阿里巴巴公司 | Method and system of monitoring on-line service risk |
| CN103577940A (en) * | 2013-11-21 | 2014-02-12 | 华迪计算机集团有限公司 | Method and device for diagnosing service model |
| CN103714479A (en) * | 2012-10-09 | 2014-04-09 | 四川欧润特软件科技有限公司 | Intelligent centralized monitor method and system for bank personal business fraudulent conducts |
| CN104239052A (en) * | 2014-09-12 | 2014-12-24 | 浙江宇视科技有限公司 | Business flow generation method and business flow generation device |
-
2016
- 2016-03-02 CN CN201610118569.7A patent/CN107153646B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1835014A (en) * | 2006-03-28 | 2006-09-20 | 阿里巴巴公司 | Method and system of monitoring on-line service risk |
| CN103714479A (en) * | 2012-10-09 | 2014-04-09 | 四川欧润特软件科技有限公司 | Intelligent centralized monitor method and system for bank personal business fraudulent conducts |
| CN103577940A (en) * | 2013-11-21 | 2014-02-12 | 华迪计算机集团有限公司 | Method and device for diagnosing service model |
| CN104239052A (en) * | 2014-09-12 | 2014-12-24 | 浙江宇视科技有限公司 | Business flow generation method and business flow generation device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107153646A (en) | 2017-09-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107153646B (en) | Data processing method and equipment | |
| EP3859644B1 (en) | Block chain-based data check system and method, computing device, and storage medium | |
| CN112073269B (en) | Block chain network testing method, device, server and storage medium | |
| CN108509392B (en) | Multi-mechanism account checking method, system, computer equipment and storage medium | |
| CN105389256A (en) | Unit testing method and system | |
| CN110740356B (en) | Live broadcast data monitoring method and system based on block chain | |
| CN104346365A (en) | Device and method for determining specific service associated logs | |
| CN116155771A (en) | Network anomaly test method, device, equipment, storage medium and program | |
| CN112446786A (en) | Abnormal transaction processing method and device, electronic equipment and readable storage medium | |
| CN111553652B (en) | Service processing method and device | |
| CN110363663A (en) | Batch data processing method, device, equipment and storage medium based on block chain | |
| CN110222323A (en) | A kind of voucher generation method, device, readable storage medium storing program for executing and terminal device | |
| CN108075911B (en) | Service testing method and device | |
| CN114282011A (en) | Knowledge graph construction method and device, and graph calculation method and device | |
| CN111651522A (en) | Data synchronization method and device | |
| CN108710658B (en) | Data record storage method and device | |
| CN109389271B (en) | Application performance management method and system | |
| CN116258309A (en) | Business object life cycle management and tracing method and device based on block chain | |
| CN110046172A (en) | In line computation data processing method and system | |
| CN114491662A (en) | Block chain-based data asset auditing method, system and equipment | |
| CN114677138A (en) | Data processing method, data processing equipment and computer readable storage medium | |
| CN110990278A (en) | Test method and device | |
| CN113342795B (en) | Data checking method and device in application program, electronic equipment and storage medium | |
| CN116560722B (en) | Operation and maintenance flow processing method and device, electronic equipment and storage medium | |
| CN116506333B (en) | Transaction system production inversion detection method and equipment |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200918 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |