# US 2014/0153626 A1 · Automated Line Test Action and Monitoring System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0153626 A1
- Document ID: US20140153626A1
- Status: Published application
- Kind: A1
- Application number: 13/705,791
- Filed: 2012-12-05
- Published: 2014-06-05
- Earliest claimed: 2012-12-05
- Assignees: AT&T Intellectual Property I, L.P.
- Applicants: At&T Intellectual Property I, L.P.
- Inventors: Christopher Wilson; Keith Bertelsen; Bruce Losee; Kavitha Shankar
- Web page: https://patentgrep.com/patent/US20140153626A1

## CPC

- H04B 3/46: Monitoring; Testing
- G06F 11/006: {Identification (G06F11/2289 takes precedence)}
- G06F 11/2252: {using fault dictionaries}
- G06F 11/2257: {using expert systems}
- H04L 43/50: Testing arrangements
- H04M 3/28: Automatic routine testing {; Fault testing; Installation testing; Test methods, test equipment or test arrangements therefor}
- H04M 3/30: for subscriber's lines {, for the local loop}
- H04B: TRANSMISSION
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

A method includes identifying, at a computing system executing a line test engine, a line to be tested by comparing a test entry of a test configuration database to a first database. The first database includes line data descriptive of multiple lines of a network. The method includes determining, at the computing system, a test to be performed on the line based on the test entry and sending a message from the computing system to a line test controller. The message indicates the line and the test to be performed on the line. The line test controller causes a test device to perform the test on the line. The method includes receiving a result message from the line test controller, wherein the result message indicates a result of the test.

## Claims

### Claim 1

A method comprising:
identifying, at a computing system executing a line test engine, a line to be tested by comparing a test entry of a test configuration database to a first database, wherein the first database includes line data descriptive of multiple lines of a network;
determining, at the computing system, a test to be performed on the line based on the test entry;
sending a message from the computing system to a line test controller, wherein message indicates the line and the test to be performed on the line, wherein the line test controller causes a test device to perform the test on the line; and
receiving a result message from the line test controller, wherein the result message indicates a result of the test.

### Claim 2 (depends on 1)

The method of claim 1, wherein the result is indicated as a numeric value, and further comprising:
performing a comparison of the numeric value to one or more threshold values indicated in the test entry, wherein the one or more threshold values correspond to acceptable values for the results of the test; and
determining whether the line passed the test based on the comparison.

### Claim 3 (depends on 2)

The method of claim 2, further comprising storing a result entry in a result database, wherein the result entry indicates whether the line passed the test.

### Claim 4 (depends on 2)

The method of claim 2, further comprising, in response to determining that the line did not pass the test, initiating a corrective action, wherein the corrective action is selected based on the test entry.

### Claim 5 (depends on 2)

The method of claim 2, further comprising, in response to determining that the line did not pass the test, sending a notification message to a designated recipient or a designated group of recipients, wherein the designated recipient or the designated group of recipients is indicated in the test entry.

### Claim 6 (depends on 2)

The method of claim 2, further comprising, in response to determining that the line passed the test, determining a subsequent test to be performed on the line based on the test entry.

### Claim 7 (depends on 2)

The method of claim 2, further comprising, in response to determining that the line did not pass the test, determining a subsequent test to be performed on the line based on the test entry.

### Claim 8 (depends on 7)

The method of claim 7, wherein the test is configured to identify a problem related to the line and the subsequent test is configured to determine a source or location of the problem.

### Claim 9 (depends on 7)

The method of claim 7, wherein the test and the subsequent test relate to a common characteristic of the line.

### Claim 10 (depends on 7)

The method of claim 7, wherein the test and the subsequent test relate to distinct characteristic of the line.

### Claim 11 (depends on 1)

The method of claim 1, wherein the result is indicated as a numeric value, and further comprising:
performing a comparison of the numeric value to a first threshold value and a second threshold value indicated in the test entry;
when the numeric value satisfies the first threshold value and does not satisfy the second threshold value, selecting a first subsequent test to be performed on the line based on the test entry; and
when the numeric value satisfies the first threshold value and satisfies the second threshold value, selecting a second subsequent test to be performed on the line based on the test entry, wherein the first subsequent test is distinct from the second subsequent test.

### Claim 12 (depends on 1)

The method of claim 1, wherein identifying the line to be tested includes determining whether a triggering event associated with a particular line has occurred, wherein determining whether the triggering event has occurred includes determining whether event data stored at the first database satisfies one or more criteria associated with the triggering event, wherein the one or more criteria are indicated by the test entry.

### Claim 13 (depends on 12)

The method of claim 12, wherein the triggering event corresponds to a particular date, a particular time, a modification to a network, an addition to a network, or a combination thereof.

### Claim 14 (depends on 12)

The method of claim 12, wherein the triggering event corresponds to an indication that a particular action has been performed.

### Claim 15 (depends on 14)

The method of claim 14, wherein determining whether the triggering event has occurred includes searching a second database for information related to the particular action.

### Claim 16

A system comprising:
a processor; and
a memory comprising instructions executable by a processor to cause the processor to perform operations comprising:
identifying, at a computing system executing a line test engine, a line to be tested by comparing a test entry of a test configuration database to a first database, wherein the first database includes line data descriptive of multiple lines of a network;
determining, at the computing system, a test to be performed on the line based on the test entry;
sending a message from the computing system to a line test controller, wherein message indicates the line and the test to be performed on the line, and wherein the line test controller causes a test device to perform the test on the line; and
receiving a result message from the line test controller, wherein the result message indicates a result of the test.

### Claim 17 (depends on 16)

The system of claim 16, wherein identifying the line to be tested includes searching the first database using a criterion specified in the test entry and selecting a database record of the first database that satisfies the criterion, wherein the selected database record includes a line identifier of the line.

### Claim 18 (depends on 17)

The system of claim 17, wherein the criterion includes a project identifier.

### Claim 19 (depends on 17)

The system of claim 17, wherein the criterion includes a line status identifier.

### Claim 20

A computer-readable storage device storing instructions executable by a processor to cause the processor to perform operations comprising:
identifying, at a computing system executing a line test engine, a line to be tested by comparing a test entry of a test configuration database to a first database, wherein the first database includes line data descriptive of multiple lines of a network;
determining, at the computing system, a test to be performed on the line based on the test entry;
sending a message from the computing system to a line test controller, wherein the message indicates the line and the test to be performed on the line, and wherein the line test controller causes a test device to perform the test on the line; and
receiving a result message from the line test controller, wherein the result message indicates a result of the test.