Data Consistency Validation

• US 20070276970A1
• Filed: 03/17/2004
• Published: 11/29/2007
• Est. Priority Date: 03/17/2004
• Status: Abandoned Application

• Current Assignee: ABB Research Ltd. (ABB Ltd.)
• Original Assignee: ABB Research Ltd. (ABB Ltd.)
• Inventors: Werner, Thomas, Svensson, Erik, Vetter, Claus, Koch, Thomas
• Application Number:
  US10/593,095
• Publication Number:
  US 20070276970A1
• Time in Patent Office: Days
• US Class Current: 710/55
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element

Abstract

Attribute consistency works on the comparison of a reference value against the online value of the attributes, which are retrieved from the corresponding system. In order to know which attributes need to be considered for consistency, a list of relevant attributes of each entity type in each application is stored together with the reference value of the entity. This attribute list is used by the consistency service. Therefore several attribute values of one entity in one system can be included in a combined “hash” value. At start-up or in the engineering phase, this reference value is computed out of the defined attribute list. At the time of a consistency check, the values of the attributes are read and a “hash” value is calculated with the same algorithm as the reference value. If those two values differ, an inconsistency occurred. The inventive method allows validating consistency of attributes of an entity in one of the participating applications. Any inconsistency can be propagated to all other participating applications which then may trigger functionality accordingly.

Claims

1. Method for validating consistency of attributes of entities stored in data sets of a multitude of different IT systems,

whereas entities are assigned to entity types, said entity types holding a list of available attributes,

whereas a consistency service comprises

an input buffer in which an entity to be validated for consistency of its attributes can be placed,

output means in which the result of the consistency validation can be stored and

communication means to communicate with the different IT systems,

whereas an adapter for each of the IT systems allows communication between the consistency service and the IT systems, such that a signal sent by the consistency service to verify the existence of a specific data set of an IT system can be sent back to the consistency service if that specific data set exists, and

whereas a storage device holds references to the entity in the data sets of the various IT systems such that the entity in a specific IT system can be addressed, said method comprising the following steps:

loading the entity to be validated for consistency of its attributes into the buffer of the consistency service,

reading the values of the attributes of the entity from the adapter,

comparing the values of the attributes to values of reference attributes stored in the consistency service, and

storing consistency validating information in the output means, said consistency validating information depending on the results of the comparison of the values of the attributes to the values of the reference attributes.

2. Method as in claim 1, whereas a hash code is computed from the values of the attributes read from the adapter and compared to a reference hash code computed from the values of the reference attributes, and the values of the attributes are compared to the values of the reference attributes by comparing the computed hash codes.

3. Method as in claim 1, further comprising the following step:

the consistency service sending a signal to verify the existence of a specific data set of an IT system to the IT system holding the entity to be validated for consistency of its attributes prior to reading the values from the attributes of the entity from the adapter, and

aborting the consistency validating of the entity if the signal is not being sent back to the consistency service.

4. Method as in claim 3, further comprising the following step:

logging failure of consistency validation if the signal is not being sent back to the consistency service by adding entity, which was to be validated for consistency, and the IT system, which was not replying to the signal, to a log file.

5. Method as in claim 3, further comprising the following step:

the consistency service checking communication to the IT system holding the data set to be verified prior to sending signal to verify the existence of the specific data set of that IT system.

6. Method as in claim 1, further comprising the following step:

a multitude of entities to be validated for consistency being loaded into the buffer of the consistency service,

the consistency service successively processing the entities to be validated for consistency, sending out signals and storing consistency validating information in the output means.

7. A computer program product loadable into an internal memory of a digital computer, comprising computer program code means to make, when said program is loaded in the computer, the computer execute the method of any of claim 1.

8. Consistency validating System for validating consistency of entities stored in data sets of a multitude of different IT systems, said system comprising a consistency service with

an input buffer in which an entity to be validated for consistency can be placed,

output means in which the result of the consistency validation can be stored and

communication means to communicate with the different IT systems, whereas an adapter for each of the IT systems allows communication between the consistency service and the IT systems, such that a signal sent by the consistency service to verify the existence of a specific data set of an IT system can be sent back to the consistency service if that specific data set exists, and

whereas a reference storage device holds references to the entities in the data sets of the various IT systems such that a specific entity in a specific IT system can be addressed based on such a reference stored in the reference storage.

9. Consistency validating System as in claim 8, wherein the reference storage further holds entity types, to which each entity can be assigned, said entity types defining a list of available attributes of the entities.

10. Consistency validating System as in claim 9, wherein the reference storage further holds a reference hash code for each entity type computed from the values of the attributes of a reference entity.