Operating a Network Using Relational Database Methodology

• US 20120005243A1
• Filed: 07/02/2010
• Published: 01/05/2012
• Est. Priority Date: 07/02/2010
• Status: Active Grant

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.), Board of Regents of the University of Michigan (University of Michigan)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Van der Merwe, Jacobus E., Chen, Xu, Mao, Yun, Mao, Zhuoqing M.
• Granted Patent: US 8,682,940 B2
• Time in Patent Office: Days
• US Class Current: 707/812
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2393 Updating materialised views
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network

Abstract

The disclosed technology involves the use of relational databases in conjunction with declarative language and network-wide, database abstractions to manage and operate networks. The data model creates a logically centralized database abstraction and access point for managing data relevant to network management. Exemplary managed data includes router configurations, network status and provisioning data. This information resides in a single database system which is tightly integrated with the operational network. Transactional write operations are used to change network configurations, and enforce constraints to detect and prevent policy violations during operation. In accordance with one aspect of the disclosed technology, a network operation is implemented by means of a series of database commands—read and/or write—from and to database view tables.

Claims

1. A method, comprising:

populating a relational database with data representing characteristics associated with components of a network;

implementing a database query to define a view table; and

writing data to the view table, the data representative of a change in a characteristic associated with a component of the network.

2. The method of claim 1 wherein the data is written at an address of a memory device that is associated with a cell of the view table.

3. The method of claim 1 wherein the data is written to recursive views.

4. The method of claim 2 wherein the data is written to recursive views.

5. The method of claim 1 further comprising:

transmitting the change to the component.

6. The method of claim 4 further comprising:

transmitting the change to the component.

7. The method of claim 1 further comprising:

implementing a database query to define network constraints; and

determining from the database that the change is consistent with the constraints.

8. The method of claim 6 further comprising:

implementing a database query to define network constraints; and

determining from the database that the change is consistent with the constraints.

9. The method of claim 1 wherein the database comprises regular tables, config tables and status tables.

10. The method of claim 1 wherein the view table is selected from the group consisting of a) a view of enabled interfaces, b) a view of the routing tables of routers, c)a view of enabled BGP sessions, and d) a view of established MPLS label switching paths.

11. The method of claim 9 wherein the view table is selected from the group consisting of a) a view of enabled interfaces, b) a view of the routing tables of routers, c)a view of enabled BGP sessions, and d) a view of established MPLS label switching paths.

12. The method of claim 1 wherein the component of the network to which the information is communicated is the same component that has a characteristic represented by the data, and further comprising changing the characteristic of the component to which the information is communicated, based on the communicated information.

13. The method of claim 11 wherein the component of the network to which the information is communicated is the same component that has a characteristic represented by the data, and further comprising changing the characteristic of the component to which the information is communicated, based on the communicated information.

14. The method of claim 1 wherein the database is a centralized database.

15. The method of claim 1 wherein the database is distributed over a plurality of network components.

16. The method of claim 1 wherein the one component is selected from the group consisting of a switch, a router and a communications link.

17. The method of claim 1 wherein a declarative, rule-based language is used to interact with the database.

20. The computer readable storage medium of claim 17 which implements further steps, comprising:

implementing a database query to define network constraints;

determining from the database that the change is consistent with the constraints; and

transmitting the change to the component.

18. A network comprising:

at least two network devices;

a memory device with a memory position associated with a cell of at least one view table of a relational database, and with data in the memory position associated with at least one characteristic of at least one network device;

a data entry device for entering data into the memory position;

a communication device for communicating information associated with a change in the data in a memory position associated with the at least one characteristic of the at least one network device, and

the at least one network device adapted to change a characteristic of the at least one network device based on the communicated information.

19. A computer readable storage medium encoded with computer executable instructions which, when executed by a computer, implements the steps of:

populating a relational database with data representing characteristics associated with components of the network;

implementing a database query to define a view table; and

writing data to the view table, the data representative of a change in a characteristic associated with a component of the network.