US20070183322A1

US20070183322A1 - System and Method for Automated Network Element Database Population

Info

Publication number: US20070183322A1
Application number: US11/736,482
Authority: US
Inventors: Roberta O'Steen; Linda Reddick; Charles Hodges; Jon Walters; Leslie Huff
Original assignee: Individual
Current assignee: Individual
Priority date: 2002-03-26
Filing date: 2007-04-17
Publication date: 2007-08-09
Also published as: US7231448B1

Abstract

In an illustrative method for populating a database for use in automated administration of network elements, data that describes network elements in a telecommunication system is aggregated from existing systems. The aggregated network element data is validated and inserted into a database. Finally, a log is generated for each database entry.

Description

FIELD OF THE INVENTION

The present invention relates generally to telecommunications systems, and more particularly, to systems and methods for managing network elements.

BACKGROUND

Telecommunication systems comprise numerous network elements, such as switches, multiplexers, etc., which operate together to provide telephone service, digital subscriber lines, etc. Generally, the number of network elements in a telecommunication system is very large—on the order of tens of thousands. Accordingly, the companies that provide telecommunication services have developed systems to track information about the many network elements that have been deployed. Indeed, over the years, telecommunication service providers have installed numerous systems for tracking various aspects of the network elements in their systems.
Recently, systems have been developed that allow for automated remote control of network elements. Using these systems, administrators of telecommunication systems can quickly and easily perform system administrative tasks such as, for example, provisioning. However, before a system for remote control of network elements can be used, typically the system must be loaded with data regarding the network elements that are to be managed. Of course, the network element data that is needed for these systems is frequently located in the legacy systems that the telecommunication companies have previously installed. Unfortunately, there are not presently available systems and methods for populating new systems with the network element data from the installed legacy systems.

SUMMARY

Accordingly, Applicants have developed systems and methods for loading network element data into a database for use by a system for automated administration of network elements. In an illustrative method, data that describes network elements in a telecommunication system is aggregated from existing systems. The aggregated network data is validated and inserted into a database. Finally, a log is generated for each database entry.
Additional aspects of the invention are described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features of the invention will be further apparent from the following detailed description of presently preferred exemplary embodiments of the invention taken in conjunction with the accompanying drawings, of which:
FIG. 1 is a block diagram of systems used to administer a telecommunication system;
FIG. 2 is a diagram of a system for use in implementing a method for populating a database;
FIG. 3 is a flow chart of a method for populating a database;
FIG. 4 is a diagram of a display for retrieving a directory location; and
FIG. 5 is a diagram of a graphical user interface for populating a database.

DETAILED DESCRIPTION

FIG. 1 is a block diagram representing systems for use in managing network elements in a telecommunications system. Loop Equipment Inventory Module System (LEIMs) 110 comprises a database of the network elements that are employed to provide service between central offices (CO's) and customer locations. Telemetry Assignment System (TAS) 112 comprises a database of numbers that have been assigned to network elements to uniquely identify each network element. The Trunk Integrated Record Keeping System (TIRKS)/Network and Services Database (NSDB) 114 has two functions. It is used to assign and maintain records of facilities and equipment associated with services requiring design transmission conditioning. It also stores customer and circuit data for special services, message carrier, and enhanced non-design services.
Generally, LEIMs 110, TAS 112, and TIRKS/NSDB 114 are data tracking and management systems. While they provide for managing information relevant to the network elements, they are not operable to interact with the network elements to implement administrative functions. Conversely, Transport 120 and ELCOM 122, which are software systems produced by Telcordia, may be employed to automatically implement administrative functions such as updating network element provisioning. However, before these systems can be used to administer a system, they must be loaded with data regarding the network elements. A method for loading network element data from systems such as for example, LEIMs 110, TAS 112, and TIRKS/NSDB 114 into an automated administration system such as for example, Transport is described below in connection with FIG. 3.
FIG. 2 is a diagram of a generic computing system in which an illustrative method for loading data may be implemented. As shown in FIG. 2, computing device 220 includes processor 222, system memory 224, and system bus 226 that couples various system components including system memory 224 to processor 222. System memory 224 may include read-only memory (ROM) and/or random access memory (RAM). Computing device 220 may further include hard-drive 228, which provides storage for computer readable instructions, data structures, program modules, data, and the like. A user (not shown) may enter commands and information into the computing device 220 through input devices such as a keyboard 240, a mouse 242, and a bar code scanner 246. Display device 244 may also include other devices such as a touch screen, a light pen, a grid of light beams, or the like for inputting information into processor 222. A display device 244, such as a monitor, a flat panel display, or the like is also connected to the computing device 220 or output. Communications device 243, which may be a modem, network interface card, or the like, provides for communications over network 250. Processor 222 can be programmed with instructions to interact with other computing systems so as to perform the methods described below. The instructions may be received from network 250 or stored in memory 224 and/or hard drive 228. Processor 222 may be loaded with any one of several computer operating systems such as WINDOWS NT operating system, WINDOWS 2000 operating system, LINUX operating system, and the like.
As shown in FIG. 2, computing device 220 may be connected to computer network 250. Server 264 is likewise operable to communicate with other computing devices over network 250. Network 250 may be the Internet, a local area network, a wide area network, or the like. Server 264 may communicate e-mails, web pages, and other data. Server 264 may be operated by an ISP, a corporate computer department, or any other organization or person with a server connected to network 250. Server 264 is accessible by client stations 268 from which users may send and receive data and browse web pages. Client stations 268 may connect to servers via a local area network (not shown) or using a remote connection device 272 such as, for example, a modem or network interface card.
The illustrative computing system described above may be used to implement an illustrative method for preparing data for use in a system for automatically performing administrative tasks such as is described in FIG. 3. As shown, at step 310, a request is made for the directory location of the network element related data that is to be loaded into the administrative system. For example, a screen such as disclosed in FIG. 4 may be displayed to the user on display device 244 whereby the user may input a directory location. At step 312, the directory location of the network element data is received. For example, a user input identifying a directory location and made using keyboard 240 or mouse 242 may be received into device 220.
At step 314, the network element data is requested, and at step 316 is received. For example, a command may be issued by processor 222 to read data from memory 224 or hard drive 228. The network element data corresponds to attributes of the network elements such as, for example, the network element location, the network element vendor, the network element model, and the network element type.
At step 318, the network element data received at step 316 is validated. To be validated, the data network element data may be required to be both recognizable and/or consistent. For example, the received network element type may be required to be data included in a predetermined set of recognized data. Additionally, the received network element vendor may be required to be data included in a predetermined set of recognized data based on the received network element type.
At step 320, the network element data is inserted into a database such as, for example, the transport database. The data may be inserted into the database using a graphical user interface such as, for example, the graphical user interface for the Transport software system shown in FIG. 5. At step 322, a log file of each database entry is generated. The log file may indicate whether each entry was successful, was skipped or left incomplete, or was erroneous. An erroneous entry may be accompanied by an error message indicating the source of the error such as, for example, an invalid data entry or a record that already exists in the database.
Thus, illustrative systems and methods for populating a database for use by a system for automatically performing network element administrative tasks have been disclosed. Systems and methods in accordance with the invention facilitate the loading of data that otherwise might need to be loaded manually at great effort and expense. Thus, systems and methods in accordance with the invention mark an advance in the administration of telecommunication networks.
Those skilled in the art understand that computer readable instructions for implementing the above-described processes, such as those described with reference to FIG. 3 can be generated and stored on one of a plurality of computer readable media such as a magnetic disk or CD-ROM. Further, a general purpose computer such as that described with reference to FIG. 2 may be arranged with other similarly equipped computers in a network, and may be loaded with computer readable instructions for performing the above described processes. Specifically, referring to FIG. 2, microprocessor 222 may be programmed to operate in accordance with the above-described processes.
While the invention has been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles of the invention as described above and set forth in the following claims. For example, while the invention has been described in connection with transport element databases, the systems and methods may be employed to populate databases for use with other systems as well. Accordingly, reference should be made to the appended claims as indicating the scope of the invention.

Claims

1. A method for automated loading of network element data, comprising:

receiving network element data, the network element data corresponding to attributes of network elements in a telecommunication system;

validating the network element data;

inserting the valid network element data into a database; and

generating a log file of each database entry.

2. The method of claim 1, wherein said step of validating the network element data comprises validating that the received data corresponding to a network element attribute comprises data included in a predetermined set of recognized data.

3. The method of claim 2, wherein said step of validating the network element data comprises validating that the received data corresponding to a network element attribute comprises data included in a predetermined set of recognized data based on the received data corresponding to another network element attribute.

4. The method of claim 1, wherein said step of generating a log file comprises generating a log file comprising at least one of a log of successful data entries, skipped or incomplete data entries, and erroneous data entries.

5. The method of claim 4, further comprising generating an error message for each entry in the log of erroneous data entries.

6. The method of claim 5, wherein the error message consists of an invalid data entry message.

7. The method of claim 5, wherein the error message consists of a previously existing data entry message.

8. The method of claim 1, further comprising requesting a directory location of the network element data to be loaded.

9. The method of claim 1, further comprising retrieving the network element data from the directory location.

10. A system for automated loading of network element data, comprising:

a processor operative to execute computer executable instructions; and

a memory having stored therein computer executable instructions for performing the following steps:

validating the network element data;

inserting the valid network element data into a database; and

generating a log file of each database entry.

11. A computer readable medium having computer executable instructions recorded thereon for performing the method recited in claim 1.