Method and system for auditing a test database against a reference database

• US 6,195,658 B1
• Filed: 07/15/1999
• Issued: 02/27/2001
• Est. Priority Date: 07/15/1999
• Status: Expired due to Term

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Bell Atlantic Network Services, Inc. (Verizon Communications Inc.)
• Inventors: DiRocco, Philip, St. Martin, Wilfred, Spence, George, Comito, Richard, Boorom, Paul, Carlan, Dennis
• Primary Examiner(s): Alam, Hosaint T.
• Assistant Examiner(s): Corrielus, Jean M.
• Application Number:
  US09/354,449
• Time in Patent Office: 593 Days
• Field of Search: 379/201, 379/45, 379/37, 379/49, 379/388, 379/40, 707/6, 707/2, 707/202, 455/402, 455/404
• US Class Current: 1/1
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems
• CPC Class Codes: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: H04M 7/06 using auxiliary connections for control or supervision , e.g. where the auxiliary connection is a signalling system number 7 link
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A method for auditing databases containing records of varied record formats verifies records from a test database against records from a reference database. Records from the test database are converted to test tokens, and records from the reference database are converted to reference tokens. The tokens summarize select fields of data from the records. Thereafter, pattern recognition techniques are used to analyze the tokens to determine Whether the data in the test tokens matches to data in the reference tokens. When an erroneous test token is discovered, an update token is generated to correct a corresponding record in the test database. This method is particularly well suited for auditing enhanced 911 emergency telephone service selective router databases.

Claims

1. A method for auditing a test database against a reference database, said reference database having a reference record designed to correspond to a test record in said test database, said reference record represented by a reference token containing select data from said reference record, and said test record being in any one of a plurality of formats, said method comprising:

determining whether said test record format conforms to a recognizable record format by;

determining whether said test record has a data pattern that conforms to a currently recognized data pattern;

determining whether said test record has a data pattern that conforms to a pre-established data pattern, when said test record does not have said data pattern that conforms to said currently recognized data pattern; and

saving said pre-established data pattern as said currently recognized data pattern, when said test record has said data pattern that conforms to said pre-established data pattern;

copying select data from said test record into a test token when said test record format conforms to said recognizable record format; and

determining whether data in said reference token matches data in said test token in accord with a comparison parameter,

wherein said reference token and said test token have a common token format.

2. The method recited in claim 1, further comprising:

generating an update token that contains data to correct said test record when said data in said reference token does not match said data in said test token.

3. The method recited in claim 1, wherein determining whether said test record format conforms to a recognizable record format further comprises:

determining whether said test record has a data pattern that conforms to a new data pattern; and

saving said new data pattern as said currently recognized data pattern, when said test record has said data pattern that conforms to said new data pattern.

4. The method recited in claim 3, further comprising saving said new data pattern as said pre-established data pattern, when said test record has said data pattern that conforms to said new data pattern.

5. The method recited in claim 3, wherein determining whether said test record has a data pattern that conforms to a new data pattern comprises parsing a data stream in said test record and searching for a valid data pattern.

6. The method recited in claim 1, wherein determining whether data in said reference token matches data in said test token in accord with a comparison parameter comprises:

determining whether data in said test token is identical to data in said reference token;

determining whether said test token is a wildcard token, when data in said test token is not identical to data in said reference token;

saving said test token as a currently recognized wildcard token, when said test token is said wildcard token; and

determining whether data in said reference token matches data in said currently recognized wildcard token, when said test token is not said wildcard token,

wherein said wildcard token contains a field that affirmatively matches any value to which said field is compared.

7. A memory media that stores a program for controlling a processor for auditing a test database against a reference database, said reference database having a reference record designed to correspond to a test record in said test database, said reference record represented by a reference token containing select data from said reference record, and said test record being in any one of a plurality of formats, said memory media comprising:

means for controlling said processor to determine whether said test record format conforms to a recognizable record format by;

determining whether said test record has a data pattern that conforms to a currently recognized data pattern;

determining whether said test record has a data pattern that conforms to a pre-established data pattern, when said test record does not have said data pattern that conforms to said currently recognized data pattern; and

saving said pre-established data pattern as said currently recognized data pattern, when said test record has said data pattern that conforms to said pre-established data pattern;

means for controlling said processor to copy select data from said test record into a test token when said test record format conforms to said recognizable record format; and

means for determining whether data in said reference token matches data in said test token in accord with a comparison parameter,

wherein said reference token and said test token have a common token format.

8. The memory media recited in claim 7, further comprising:

means for generating an update token that contains data to correct said test record when said data in said reference token does not match said data in said test token.

9. The memory media recited in claim 7, wherein said means for controlling said processor to determine whether said test record format conforms to a recognizable record format further comprises:

means for determining whether said test record has a data pattern that conforms to a new data pattern; and

means for saving said new data pattern as said currently recognized data pattern, when said test record has said data pattern that conforms to said new data pattern.

10. The memory media recited in claim 9, further comprising means for saving said new data pattern as said pre-established data pattern, when said test record has said data pattern that conforms to said new data pattern.

11. The memory media recited in claim 9, wherein said means for determining whether said test record has a data pattern that conforms to a new data pattern comprises means for parsing a data stream in said test record and searching for a valid data pattern, wherein determining whether said test record has a data pattern that conforms to a new data pattern comprises parsing a data stream in said test record and searching for a valid data pattern.

12. The memory media recited in claim 7, wherein said means for determining whether data in said reference token matches data in said test token in accord with a comparison parameter comprises:

means for determining whether data in said test token is identical to data in said reference token;

means for determining whether said test token is a wildcard token, when data in said test token is not identical to data in said reference token;

means for saving said test token as a currently recognized wildcard token, when said test token is said wildcard token; and

means for determining whether data in said reference token matches data in said currently recognized wildcard token, when said test token is not said wildcard token,

wherein said wildcard token contains a field that affirmatively matches any value to which said field is compared.

13. A method for auditing a 911 telephone service router database against a reference database, said reference database having a reference record designed to correspond to a router record in said router database, said reference record represented by a reference token containing select data from said reference record, and said router record being in any one of a plurality of formats, said method comprising:

determining whether said router record format conforms to a recognizable record format;

copying select data from said router record into a router token, when said router record format conforms to said recognizable record format; and

determining whether data in said reference token imatches data in said router token, when said router record format conforms to said recognizable record format,

wherein said reference token and said router token have a common token format.

14. The method recited in claim 13, further comprising:

generating an update token that contains data to correct said router record when said data in said reference token does not match said data in said router token.

15. The method recited in claim 13, wherein determining whether said router record format conforms to a recognizable record format comprises:

determining whether said router record has a data pattern that conforms to a currently recognized data pattern;

determining whether said router record has a data pattern that conforms to a pre-established data pattern, when said router record does not have said data pattern that conforms to said currently recognized data pattern; and

saving said pre-established data pattern as said currently recognized data pattern, when said router record has said data pattern that conforms to said pre-established data pattern.

16. The method recited in claim 13, wherein determining whether said router record format conforms to a recognizable record format comprises:

determining whether said router record has a data pattern that conforms to a new data pattern; and

saving said new data pattern as a currently recognized data pattern, when said router record has said data pattern that conforms to said new data pattern.

17. The method recited in claim 16, wherein determining whether said router record has a data pattern that conforms to a new data pattern comprises parsing a data string in said router record to locate a 3-character area code, a 7-character telephone number and a 3-character emergency service number.

18. The method recited in claim 16, further comprising saving said new data pattern as a pre-established data pattern, when said router record has said data pattern that conforms to said new data pattern.

19. The method recited in claim 13, wherein determining whether data in said reference token matches data in said router token in accord with a comparison parameter comprises:

determining whether data in said router token is identical to data in said reference token;

determining whether said router token is a predominant token, when data in said router token is not identical to data in said reference token;

saving said router token as a currently recognized predominant token, when said rouzer token is said predominant token; and

determining whether data in said reference token matches data in said currently recognized predominant token, when said router token is not said predominant token,

wherein said predominant token contains a field that affirmatively matches any value to which said field is compared.

20. The method recited in claim 13, wherein said common token format comprises a field representing a 3-character area code, a field representing a 7-character telephone number and a field representing a 3-character emergency service number.