CN101582790B - Method, device and system for dynamic data audit and service entity fault detection - Google Patents
Method, device and system for dynamic data audit and service entity fault detection Download PDFInfo
- Publication number
- CN101582790B CN101582790B CN2008101116442A CN200810111644A CN101582790B CN 101582790 B CN101582790 B CN 101582790B CN 2008101116442 A CN2008101116442 A CN 2008101116442A CN 200810111644 A CN200810111644 A CN 200810111644A CN 101582790 B CN101582790 B CN 101582790B
- Authority
- CN
- China
- Prior art keywords
- data
- time
- data elements
- business
- entity
- 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.)
- Expired - Fee Related
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 46
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012550 audit Methods 0.000 title abstract description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention relates to a method, a device and a system for dynamic data audit and service entity fault detection. The method for dynamic data audit comprises the following steps: receiving data and the time of the latest update of the data elements in the data uploaded by at least two service entities; and comparing the data elements in the service entities, and if the data elements in the service entities are different, judging whether or not the data elements in service entities have data element differences by determining whether or not the time difference between the time of the latest update of the data elements in each service entity and a preset time for loading the snapshots of the data exceeds a preset threshold. When finding out that the data elements in the service entities are different through comparison, the audit device of the embodiment of the invention further judges whether the data elements have data element differences according to the time of the latest update of data elements, thereby avoiding determining reasonable metadata dynamic change as metadata difference, preventing the faults in the service entities, and improving the accuracy of the data audit and the service entity fault detection.
Description
Technical Field
The invention relates to the field of communication, in particular to a method, a device and a system for auditing dynamic data and detecting faults of a business entity.
Background
In current telecommunication networks, operational data, such as: user profiles, product order records, etc. are often stored in multiple systems, i.e. business entities, and are in dynamic change as the business operates. When data between business entities are different, business transaction failure can be caused. Therefore, data auditing between business entities is necessary.
In the prior art, each business entity downloads the whole data of the system at a preset time point and sends the data to an independent auditing system. The auditing system checks whether the same data element is the same among the systems according to an equal matching mode. However, due to small differences in the clocks between the various business entities, data updates may occur within the time differences. When data updates are synchronized by one business entity to another, the data must be differentiated if the snapshot is occurring during the synchronization process, since synchronization is time consuming. Therefore, if the data difference is checked, it is not necessarily determined as a data error.
Disclosure of Invention
The embodiment of the invention provides a method, a device and a system for dynamic data auditing and service entity fault detection, which are used for avoiding judging reasonable dynamic change of metadata as metadata difference and service entity fault and improving the accuracy of data auditing and service entity fault detection.
The embodiment of the invention provides a method for auditing dynamic data, which comprises the following steps:
receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
and comparing whether the data elements in the service entity are the same or not, and if not, judging whether the data elements have data element differences or not according to whether the time difference between the latest updating time of the data elements and the preset snapshot time for downloading the data is smaller than a preset threshold value or not.
The embodiment of the invention also provides a device for auditing the dynamic data, which comprises:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first auditing module is used for comparing whether the data elements in the business entity are the same or not;
and the second auditing module is used for judging whether the data elements have data element differences or not according to whether a time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not when the first auditing module compares the data elements in the service entities to be different.
The embodiment of the invention also provides a system for auditing dynamic data, which comprises:
the system comprises at least two business entities, a snapshot module and a server, wherein the business entities are used for recording the updating time when a data element is updated, downloading data at the preset snapshot time and uploading the data and the latest updating time of the data element;
and the auditing device is used for receiving the data uploaded by the business entity and the latest updating time of the data elements in the data, comparing whether the data elements in the business entity are the same or not, and if not, judging whether the data elements have data element difference or not according to whether the time difference between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not.
The embodiment of the invention provides a method for detecting a fault of a service entity, which comprises the following steps:
receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
and comparing whether the data elements in the service entity are the same or not, and if not, judging whether the service entity fails or not according to whether the time difference between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not.
The embodiment of the invention also provides a device for detecting the fault of the service entity, which comprises the following steps:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first detection module is used for comparing whether the data elements in the business entity are the same or not;
and the second detection module is used for judging whether the business entity fails or not according to whether a time difference value between the latest updating moment of the data element and the preset snapshot moment of downloading the data is smaller than a preset threshold value or not when the first detection module compares that the data elements in the business entity are different.
The embodiment of the present invention further provides a system for detecting a fault of a service entity, including:
the system comprises at least two business entities, a snapshot module and a server, wherein the business entities are used for recording the updating time when a data element is updated, downloading data at the preset snapshot time and uploading the data and the latest updating time of the data element;
the detection device is used for receiving the data uploaded by the business entity and the latest updating time of the data elements in the data, comparing whether the data elements in the business entity are the same or not, and if not, judging whether the business entity fails or not according to whether the time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is smaller than a preset threshold value or not.
According to the technical scheme, when the data elements of the system are updated by each service entity, the updating time of each data element is recorded, the data are downloaded at the preset snapshot time, the data and the latest updating time of the data elements are uploaded to the auditing device, and when the auditing device or the detection device compares that the data elements in the service entities are different, whether the data elements have data element difference or not and whether the service entities have faults or not are further judged according to the latest updating time of the data elements, so that the reasonable dynamic change of the metadata is judged to be the metadata difference and the service entities have faults, and the accuracy of data auditing and the fault detection of the service entities is improved.
The following describes in further detail specific embodiments of the present invention with reference to the accompanying drawings.
Drawings
FIG. 1 is a flowchart illustrating a method for dynamic data auditing according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating an embodiment of a dynamic data auditing apparatus according to the present invention;
FIG. 3 is a block diagram illustrating a system for dynamic data auditing according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a method for detecting a fault of a service entity according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an embodiment of a device for detecting a service entity failure according to the present invention;
fig. 6 is a schematic structural diagram of a system for detecting a service entity failure according to an embodiment of the present invention.
Detailed Description
Fig. 1 is a schematic flow chart of an embodiment of a method for auditing dynamic data according to the present invention, and as shown in fig. 1, the embodiment includes the following steps:
The business entity in the process of completing the relevant business operation process includes, for example: storing and maintaining related service data, namely data elements, and updating the maintained data elements. The updating herein may specifically include two cases: one updates self-maintained service data for one service entity and sends data synchronization operation request to other related service entities; and the other is to receive data synchronization operation requests sent by other related business entities and update the business data maintained by the other business entities. In any of the above updating cases, the service entity can record the latest updating time of each data element therein. The business entity also needs to download data at a preset snapshot time and upload the data and the latest updating time of the data elements to the auditing device.
102, comparing whether the data elements in the business entity are the same by the auditing device, and if so, ending the process; if not, go to step 103;
and 104, judging that the data elements have data element differences by the auditing device.
The auditing principle is as follows:
firstly, assume that the preset snapshot time is L, the clock difference range of each service entity is M, and the maximum reasonable completion time of a certain data element from one service entity to another service entity is N. Then, if the latest update time T > -.
Taking the example of a user product ordering a color ring service, the related service entities may be a Business Operation Support System (BOSS), an Online Charging System (OCS), and a color ring platform, and the following Operations are required to be completed:
01) BOSS business accepts user order requests;
02) BOSS business completes business side order operation;
03) the BOSS business sends the product order operation to the OCS in a forward simplex manner;
04) the OCS completes OCS side order operation;
05) BOSS business sends product ordering operation to the color ring platform;
06) the color ring back tone platform completes the color ring back tone side ordering operation.
02), 04), and 06), the BOSS business, the OCS, and the polyphonic ring platform all record the latest update time of the respective product order record data elements.
When the auditing device audits, the auditing device starts the following auditing process according to each data element in the data uploaded by BOSS business and OCS one by one: judging whether the data elements are the same in the two service entities, and skipping if the data elements are the same in the two service entities; if the data element is different in the two service entities, comparing the latest updating time of the data element in the two service entities, and if the distance between a certain latest updating time and the snapshot time is less than a threshold value, judging that the data element is not different; otherwise, the data difference is determined.
Assuming that the complete processing time of a normal color ring back tone ordering process is two hours at most, the snapshot time of the downloaded data is 0 a.m. every morning, and the audit day is 20080401. As shown in the following table, the audit object is the color ring back tone ordering mark on each platform.
As can be seen from the above table, the data in the scene 2 are inconsistent, but since the latest update time recorded by the BOSS business system is less than two hours from the snapshot time, the scene 2 is not determined as a data element difference; the data in scene 3 are inconsistent, and the latest update time recorded by each system is more than two hours away from the snapshot time, so that scene 3 is determined as a data element difference.
In this embodiment, when each data element in each service entity is changed, the service entity can record the latest update time of the data element, regardless of the change caused by the service logic of the service entity or the change caused by the data synchronization of other service entities. The auditing device does not use the latest update time of the data elements as the auditing object, but needs to use the latest update time as the judgment basis when the difference of the data elements is checked. And when the distance between the latest updating time of the data element among the business entities and the preset snapshot time is less than a preset threshold value, judging that the data element difference is reasonable, otherwise, judging that the data element difference is the data element difference.
In the embodiment of the invention, the latest updating time of the data element in the maintained data is accurately identified through the business entity, and the data and the latest updating time of the data element are uploaded to the auditing device after the data is downloaded when the snapshot time arrives. When the auditing device detects that the data elements are different, whether the data elements are the data differences or not is judged according to the latest updating time of the data elements in each business entity, so that the reasonable dynamic change of the metadata is avoided being judged as the metadata differences, and the accuracy of data auditing is improved.
Fig. 2 is a schematic structural diagram of an embodiment of the apparatus for auditing dynamic data according to the present invention, and as shown in fig. 2, the embodiment includes a receiving module 21, a first auditing module 22 and a second auditing module 23. The receiving module 21 is configured to receive data uploaded by at least two service entities and a latest update time of a data element in the data; the first auditing module 22 is used for comparing whether the data elements in the business entities are the same; the second auditing module 23 is configured to, when the first auditing module 22 compares that the data elements in the business entities are different, determine whether the data elements have data element differences according to whether a time difference between a latest update time of the data elements and a preset snapshot time is less than a preset threshold.
In the embodiment of the invention, after the auditing device receives the data downloaded by the business entity when the snapshot time arrives and the latest updating time of the data elements in the maintained data recorded by the business entity, the auditing device audits the data elements in each business entity. When the auditing device detects that the data elements are different, whether the data elements are the data differences or not is judged according to the latest updating time of the data elements in each business entity, so that the reasonable dynamic change of the metadata is avoided being judged as the metadata differences, and the accuracy of data auditing is improved.
FIG. 3 is a schematic structural diagram of a system for dynamic data auditing according to an embodiment of the present invention, as shown in FIG. 3, the system includes at least two business entities 10 and an auditing device 20. The service entity 10 is configured to store and maintain data elements related to a service, record an update time when the data elements are updated, download data at a preset snapshot time, and upload the data and the latest update time of the data elements to the auditing device 20; the auditing device 20 is configured to receive data uploaded by the service entity 10 and a latest update time of a data element in the data, compare whether the data element in the service entity 10 is the same, and determine whether the data element has a data element difference according to whether a time difference between the latest update time of the data element and a preset snapshot time is smaller than a preset threshold if the data element in the service entity 10 is not the same.
In this embodiment, when each data element in each service entity is changed, the service entity can record the latest update time of the data element, regardless of the change caused by the service logic of the service entity or the change caused by the data synchronization of other service entities. The auditing device does not use the latest update time of the data elements as the auditing object, but needs to use the latest update time as the judgment basis when the difference of the data elements is checked. And when the distance between the latest updating time of the data element among the business entities and the preset snapshot time is less than a preset threshold value, judging that the data element difference is reasonable, otherwise, judging that the data element difference is the data element difference.
Further, the auditing apparatus 20 may further include a receiving module 21, a first auditing module 22 and a second auditing module 23. The receiving module 21 is configured to receive data uploaded by at least two service entities 10 and a latest update time of a data element in the data; the first auditing module 22 is used for comparing whether the data elements in the business entity 10 are the same; the second auditing module 23 is configured to, when the data elements in the business entity 10 compared by the first auditing module 22 are different, determine whether the data elements have data element difference according to whether a time difference between a latest updating time of the data elements and a preset snapshot time is less than a preset threshold.
In the embodiment of the invention, the latest updating time of the data element in the maintained data is accurately identified through the business entity, and the data and the latest updating time of the data element are uploaded to the auditing device after the data is downloaded when the snapshot time arrives. When the auditing device detects that the data elements are different, whether the data elements are the data differences or not is judged according to the latest updating time of the data elements in each business entity, so that the reasonable dynamic change of the metadata is avoided being judged as the metadata differences, and the accuracy of data auditing is improved.
Fig. 4 is a flowchart illustrating an embodiment of a method for detecting a service entity failure according to the present invention, as shown in fig. 4, the embodiment includes the following steps:
The business entity in the process of completing the relevant business operation process includes, for example: storing and maintaining related service data, namely data elements, and updating the maintained data elements. The updating herein may specifically include two cases: one updates self-maintained service data for one service entity and sends data synchronization operation request to other related service entities; and the other is to receive data synchronization operation requests sent by other related business entities and update the business data maintained by the other business entities. In any of the above updating cases, the service entity can record the latest updating time of each data element therein. The service entity also needs to download data at a preset snapshot time and upload the data and the latest update time of the data element to the detection device.
The detection principle is as follows:
firstly, assume that the preset snapshot time is L, the clock difference range of each service entity is M, and the maximum reasonable completion time of a certain data element from one service entity to another service entity is N. Then, if the latest update time T > -.
In this embodiment, when each data element in each service entity is changed, the service entity can record the latest update time of the data element, regardless of the change caused by the service logic of the service entity or the change caused by the data synchronization of other service entities. The detection device does not set the latest update time of the data element as a detection target, but when the difference of the data element is detected, the latest update time is required to be used as a judgment basis. When the latest updating time of the data element between the business entities is less than a preset threshold value from the preset snapshot time of the downloaded data, the data element difference is judged to be reasonable, otherwise, the business entity is judged to have a fault.
In the embodiment of the invention, the latest updating time of the data element in the maintained data is accurately identified through the service entity, and the data and the latest updating time of the data element are uploaded to the detection device after the data is downloaded when the snapshot time arrives. When the detection device detects that the data elements are different, whether the service entity fails or not is judged according to the latest updating time of the data elements in each service entity, so that the situation that reasonable dynamic change of metadata is judged to be that the service entity fails is avoided, and the accuracy of detecting the service entity failure is improved.
Fig. 5 is a schematic structural diagram of an embodiment of a device for detecting a service entity failure, as shown in fig. 5, the embodiment includes a receiving module 41, a first detecting module 42, and a second detecting module 43. The receiving module 41 is configured to receive data uploaded by at least two service entities and a latest update time of a data element in the data; the first detection module 42 is configured to compare whether the data elements in the business entities are the same; the second detecting module 43 is configured to, when the first detecting module 42 compares that the data elements in the service entity are different, determine whether the service entity fails according to whether a time difference between a latest update time of the data elements and a preset snapshot time of downloaded data is smaller than a preset threshold.
In the embodiment of the invention, the detection device detects the data elements in each service entity after receiving the data downloaded by the service entity when the snapshot time arrives and the latest updating time of the data elements in the maintained data recorded by the service entity. When the detection device detects that the data elements are different, whether the service entity fails or not is judged according to the latest updating time of the data elements in each service entity, so that the situation that reasonable dynamic change of metadata is judged to be that the service entity fails is avoided, and the accuracy of detecting the service entity failure is improved.
Fig. 6 is a schematic structural diagram of a system embodiment of service entity fault detection according to the present invention, and as shown in fig. 6, the present embodiment includes at least two service entities 30 and a detection device 40. The service entity 30 is configured to store and maintain data elements related to a service, record an update time when the data elements are updated, download data at a preset snapshot time, and upload the data and the latest update time of the data elements to the detection device 40; the detecting device 40 is configured to receive the data uploaded by the service entity 30 and the latest update time of the data element in the data, compare whether the data elements in the service entity 30 are the same, and if not, determine whether the service entity 30 fails according to whether a time difference between the latest update time of the data element and a preset snapshot time is smaller than a preset threshold.
In this embodiment, when each data element in each service entity is changed, the service entity can record the latest update time of the data element, regardless of the change caused by the service logic of the service entity or the change caused by the data synchronization of other service entities. The detection device does not set the latest update time of the data element as a detection target, but when the difference of the data element is detected, the latest update time is required to be used as a judgment basis. When the distance between the latest updating time of the data element among the business entities and the preset snapshot time is less than a preset threshold value, the data element difference is judged to be reasonable, otherwise, the business entity is judged to have a fault.
Further, the detection device 40 may further include a receiving module 41, a first detection module 42, and a second detection module 43. The receiving module 41 is configured to receive data uploaded by at least two service entities 30 and a latest update time of a data element in the data; the first detection module 42 is used to compare whether the data elements in the business entity 30 are the same; the second detecting module 43 is configured to, when the data elements in the service entity 30 compared by the first detecting module 42 are different, determine whether the service entity 30 fails according to whether a time difference between a latest update time of the data elements and a preset snapshot time is smaller than a preset threshold.
In the embodiment of the invention, the latest updating time of the data element in the maintained data is accurately identified through the service entity, and the data and the latest updating time of the data element are uploaded to the detection device after the data is downloaded when the snapshot time arrives. When the detection device detects that the data elements are different, whether the service entity fails or not is judged according to the latest updating time of the data elements in each service entity, so that the situation that reasonable dynamic change of metadata is judged to be that the service entity fails is avoided, and the accuracy of detecting the service entity failure is improved.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for dynamic data auditing, comprising:
receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
and comparing whether the data elements in the service entity are the same or not, and if not, judging whether the data elements have data element differences or not according to whether the time difference between the latest updating time of the data elements and the preset snapshot time for downloading the data is smaller than a preset threshold value or not.
2. The method of dynamic data auditing of claim 1 where the threshold is the sum of the difference range of the business entity's clocks and the maximum reasonable completion time for the data elements to synchronize from one business entity to another.
3. The method of claim 1, wherein the latest update time of the data element is the time when the business entity updates the maintained data element in the business operation process, and sends a data synchronization operation request to another business entity or when the business entity receives a data synchronization operation request from another business entity and updates the time corresponding to the maintained data element.
4. An apparatus for dynamic data auditing, comprising:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first auditing module is used for comparing whether the data elements in the business entity are the same or not;
and the second auditing module is used for judging whether the data elements have data element differences or not according to whether a time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not when the first auditing module compares the data elements in the service entities to be different.
5. A system for dynamic data auditing, comprising:
the system comprises at least two business entities, a snapshot module and a server, wherein the business entities are used for recording the updating time when a data element is updated, downloading data at the preset snapshot time and uploading the data and the latest updating time of the data element;
the auditing device is used for receiving the data uploaded by the business entity and the latest updating time of the data elements in the data, comparing whether the data elements in the business entity are the same or not, and if not, judging whether the data elements have data element differences or not according to whether the time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is smaller than a preset threshold value or not; wherein,
the auditing device comprises:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first auditing module is used for comparing whether the data elements in the business entity are the same or not;
and the second auditing module is used for judging whether the data elements have data element differences or not according to whether a time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not when the first auditing module compares the data elements in the service entities to be different.
6. A method for service entity fault detection, comprising:
receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
and comparing whether the data elements in the service entity are the same or not, and if not, judging whether the service entity fails or not according to whether the time difference between the latest updating time of the data elements and the preset snapshot time for downloading the data is less than a preset threshold value or not.
7. The method of service entity fault detection according to claim 6, wherein said threshold is a sum of a difference range of clocks of said service entities and a maximum reasonable completion time of synchronization of said data elements from one service entity to another service entity.
8. The method according to claim 6, wherein the latest update time of the data element is the time when the service entity updates the maintained data element in the service operation process the latest time, and sends a data synchronization operation request to another service entity or the service entity receives a data synchronization operation request sent by another service entity and updates the time corresponding to the maintained data element.
9. An apparatus for service entity fault detection, comprising:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first detection module is used for comparing whether the data elements in the business entity are the same or not;
and the second detection module is used for judging whether the business entity fails or not according to whether a time difference value between the latest updating moment of the data element and the preset snapshot moment of downloading the data is smaller than a preset threshold value or not when the first detection module compares that the data elements in the business entity are different.
10. A system for service entity fault detection, comprising:
the system comprises at least two business entities, a snapshot module and a server, wherein the business entities are used for recording the updating time when a data element is updated, downloading data at the preset snapshot time and uploading the data and the latest updating time of the data element;
the detection device is used for receiving the data uploaded by the business entity and the latest updating time of the data elements in the data, comparing whether the data elements in the business entity are the same or not, and if not, judging whether the business entity fails or not according to whether the time difference value between the latest updating time of the data elements and the preset snapshot time for downloading the data is smaller than a preset threshold value or not; wherein,
the detection device includes:
the receiving module is used for receiving data uploaded by at least two business entities and the latest updating time of data elements in the data;
the first detection module is used for comparing whether the data elements in the business entity are the same or not;
and the second detection module is used for judging whether the business entity fails or not according to whether a time difference value between the latest updating moment of the data element and the preset snapshot moment of downloading the data is smaller than a preset threshold value or not when the first detection module compares that the data elements in the business entity are different.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101116442A CN101582790B (en) | 2008-05-15 | 2008-05-15 | Method, device and system for dynamic data audit and service entity fault detection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101116442A CN101582790B (en) | 2008-05-15 | 2008-05-15 | Method, device and system for dynamic data audit and service entity fault detection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101582790A CN101582790A (en) | 2009-11-18 |
| CN101582790B true CN101582790B (en) | 2011-12-07 |
Family
ID=41364765
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101116442A Expired - Fee Related CN101582790B (en) | 2008-05-15 | 2008-05-15 | Method, device and system for dynamic data audit and service entity fault detection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101582790B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108243046A (en) * | 2016-12-27 | 2018-07-03 | 中国移动通信集团浙江有限公司 | A kind of evaluation the quality method and device based on data auditing |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103473672A (en) * | 2013-09-30 | 2013-12-25 | 国家电网公司 | System, method and platform for auditing metadata quality of enterprise-level data center |
| CN110620632B (en) * | 2019-09-12 | 2021-02-23 | 华为技术有限公司 | Time synchronization method and device |
| CN113110362A (en) * | 2021-05-24 | 2021-07-13 | 深创高新产业研究中心(深圳)有限公司 | Injection molding equipment state monitoring system based on industry 4.0 |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1794227A (en) * | 2004-12-20 | 2006-06-28 | 微软公司 | Systems and methods for synchronization of items without snapshots |
| CN101046761A (en) * | 2007-04-29 | 2007-10-03 | 华为技术有限公司 | Device and method for fetching snapshot data |
-
2008
- 2008-05-15 CN CN2008101116442A patent/CN101582790B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1794227A (en) * | 2004-12-20 | 2006-06-28 | 微软公司 | Systems and methods for synchronization of items without snapshots |
| CN101046761A (en) * | 2007-04-29 | 2007-10-03 | 华为技术有限公司 | Device and method for fetching snapshot data |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108243046A (en) * | 2016-12-27 | 2018-07-03 | 中国移动通信集团浙江有限公司 | A kind of evaluation the quality method and device based on data auditing |
| CN108243046B (en) * | 2016-12-27 | 2020-12-22 | 中国移动通信集团浙江有限公司 | Service quality assessment method and device based on data audit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101582790A (en) | 2009-11-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11086825B2 (en) | Telemetry system for a cloud synchronization system | |
| CN101436138B (en) | Control device and control method for software upgrade and dynamic rolling back | |
| US20110258160A1 (en) | Data synchronization methods for synchronizing data in communication system and communication systems | |
| CN108319617B (en) | Method and device for determining master-slave difference of database and switching control method and device | |
| CN101582790B (en) | Method, device and system for dynamic data audit and service entity fault detection | |
| CN106327191B (en) | Method and device for recording transaction information | |
| CN111797060B (en) | Offline video recording method, device and equipment and computer readable storage medium | |
| CN111367994A (en) | Method and system for synchronously backing up incremental data of database | |
| CN109086065A (en) | A kind of method for upgrading software, system and terminal device | |
| CN107016075A (en) | Company-data synchronous method and device | |
| CN109450977B (en) | Cache data pushing and updating method and device | |
| WO2018014881A1 (en) | Interactive authentication method, device and system for internet protocol television (iptv) platform | |
| CN111223245A (en) | Solar equipment leasing method, device and system and mobile terminal | |
| CN113783649B (en) | Terminal timing method, system, electronic equipment and storage medium | |
| CN102970159B (en) | Data auditing and repair process method and apparatus | |
| CN115269917A (en) | Goods receiving system and goods receiving method | |
| US10922301B1 (en) | Apparatus, computer program, and method for trigger-based tracking of database modifications | |
| US20240256563A1 (en) | Mechanism for backfilling records dropped during transfer from distributed node system | |
| CN105574020B (en) | Database operation method and device | |
| CN109992215A (en) | A kind of upgrade method, upgrade-system and the relevant apparatus of ICFS system | |
| CN112711599B (en) | Data increment updating method | |
| CN112860284B (en) | SP upgrade package generation method and device for equipment remote upgrade and computer equipment | |
| CN115134213B (en) | Disaster recovery method, device, equipment and storage medium | |
| CN108874416B (en) | Policy processing method and device, storage medium and processor | |
| CN117033345A (en) | Database migration verification method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111207 |