WO2001088697A2

WO2001088697A2 - Methods for modularizing network software

Info

Publication number: WO2001088697A2
Application number: PCT/IB2001/000840
Authority: WO
Inventors: Shlomo Rabinovitch
Original assignee: Adc Telecommunications Israel Ltd.
Priority date: 2000-05-17
Filing date: 2001-05-16
Publication date: 2001-11-22
Also published as: AU2001258671A1; WO2001088697A3; CA2409362A1

Abstract

Methods and structures are discussed that modularize network software so as to reduce or eliminate a large amount of time allocated for testing. The embodiments of the present invention discuss a method for modularizing network software. The method includes an act for forming a first part of the network software. The first part is adapted to be used for providing distributed application management. The method includes an act for forming a second part of the network software. The second part is adapted to be used for providing network element functionality. The method includes an act for forming a third part of the network software. The third part is adpated to be used for providing management functionality.

Description

METHODS FOR MODULARIZING NETWORK SOFTWARE

Technical Field The technical field relates generally to network software. More particularly, it pertains to the modularizing of network software so as to reduce or eliminate time allocated to retest the network software after changes or additions.

Copyright Notice - Permission A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings attached hereto: Copyright © 1999, 2000, ADC Telecommunications, Inc., All Rights Reserved.

Background The information technology of today has grown at an unprecedented rate as a result of the synergistic marriage of communication networks and the computer. Milestones in the development of these communication networks have included the telephone networks, radio, television, cable, and communication satellites. Computers have made tremendous progress from being hulking machines with human operators to today's postage-stamp-size integrated circuits. The merging of the communication networks and the computer has replaced the model of forcing workers to bring their work to the machine with a model of allowing anyone to access information on any computers at diverse locations and times.

One major contributor to this synergy is software. With each succeeding generation of technology, however, software has become more complicated. One reason for the increased complexity is due to the evolution of software. Such an evolution occurs rapidly in response to the demands of the marketplace. The evolution of software includes changes to existing software as well as new additions. Because a probability exists that software may not perform as expected after the changes and additions, software may benefit from analyses that may be used to improve it. One type of analysis includes testing. But testing complicated network software thoroughly requires a large amount of time. Current testing practices provide insufficiently time to gain confidence that the software will perform as expected. As the size of network software has increased with each generation of technology, such inferior practices may slow the improvement of network software and lead to the eventual lack of acceptance of such network software in the marketplace. Thus, what is needed are methods and structures to enhance the modularizing of network software so as to minimize the amount of time for testing.

Summary

Methods and structures for enhancing the modularizing of element management system of network software are discussed. An illustrative aspect includes a method for modularizing element management system of the network software. The method includes an act for forming a first part of the network software; the first part of the network software is adapted to be used for providing distributed application management. The method includes an act for forming a second part of the network software; the second part of the network software is adapted to be used for providing network element functionality. The method includes an act for forming a third part of the network software; the third part is adapted to be used for providing management functionality.

Another illustrative aspect includes a business method for packaging network software. The method includes an act for forming a plurality of software parts; each software part includes a plurality of components; each software part is adapted to be functionally independent from another software part. The method includes an act for packaging the network software for a network management system; the network software for the network management system includes at least one desired software part from the plurality of software parts. The method further includes an act for pricing the at least one desired software part at a desired pricing level.

Another illustrative aspect includes a data structure for packaging network software. The data structure includes a data member part to represent a feature of the network software and a data member components to represent the components of the feature.

Brief Description of the Drawings Figure 1 is a block diagram of a system according to one aspect of the present invention.

Figures 2A-2C illustrate a depository of network software according to one aspect of the present invention.

Figure 3 illustrates a portion of the network software according to one aspect of the present invention. Figure 4 illustrates a portion of the network software according to one aspect of the present invention.

Figure 5 illustrates a portion of the network software according to one aspect of the present invention.

Figure 6 is a process diagram of a method according to one aspect of the present invention.

Figure 7 is a process diagram of a method according to one aspect of the present invention.

Figure 8 is a structure diagram of a data structure according to one aspect of the present invention. Detailed Description

In the following detailed description of exemplary embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown, by way of illustration, specific exemplary embodiments in which the invention may be practiced. In the drawings, like numerals describe substantially similar components throughout the several views. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and structural, logical, electrical, and other changes maybe made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims. Figure 1 is a block diagram of a system according to one aspect of the present invention. A system 100 includes a plurality of clients, such as clients 102₀, 102_l5 and 102₂. These clients 102₀, 102_l5 and 102₂ may be used to control network elements. In one embodiment, these clients 102₀, 102_l5 and 102₂ are used to provide a user interface so as to allow an operator to control network elements. In another embodiment, these clients 102₀, 102_l5 and 102₂ are computers running different user interfaces.

The system 100 includes an internetwork layer 104 for allowing the computers 102₀, 102,, and 102₂ to communicate with network elements. In one embodiment, the internetwork layer 102 may include an Internet Protocol that governs the breakup of data messages into packets, the routing of the packets from sender to destination network and station, and the reassembly of the packets into the original data messages at the destination.

The system 100 includes a plurality of network domains, such as domains 106₀ and 106^ The network domain 106₀ includes a plurality of network elements, such as network elements 108₀, 108_l5 and 108₂. The plurality of network elements includes pieces of telecom equipment, such as switches, multiplexers, etc. The network domain 106_x includes a plurality of network elements, such as network elements 108₃ and 108₄.

The system 100 includes a server 110. The server 110 includes a database 112. In one embodiment, the server 110 serves a plurality of applications to the plurality of clients 102₀, 102_l5 and 102₂. The plurality of applications is adapted to be stored in the database 112.

Because the system 100 is modularized according to the embodiments of the present invention, there is confidence that the system 100 may perform as expected whenever the network software (not shown) of the system 100 is changed or new functionality added. Without such modularization techniques offered by the embodiments of the present invention, a prohibitive amount of time may be required to thoroughly test the system 100 to gain confidence in the performance of the system 100. Previous techniques separate the network software of the system 100 into traditional software libraries or dynamic link libraries. However, such previous techniques suffer from interdependency and foster the prohibitive amount of time needed to test the system 100.

Figures 2A-2C illustrate a depository of network software according to one aspect of the present invention. In Figure 2 A, a depository matrix 200₀ includes a collection of network software 204. The collection of network software components 204 can be referenced by column 202 that lists a plurality of software parts. For example, software part 206₀ is used to manage a network element. Software part 206j is used to manage an Asynchronous Transfer Mode (ATM) network element. Software part 206₂ is used to manage an Asymmetric Digital Subscriber Line (ADSL). Software part 206₃ is used to manage a Synchronous Optical Network (SONET). Software part 206₄ is used to manage a GR-303 network standard. Software part 206₅ is used to manage a TR-008 network standard. Software part 206₆ is used to manage a TI line. Software part 206₇ is used to manage an Integrated Services Digital Network (ISDN). Software part 206₈ is used to manage Plain Old Telephone Service (POTS). Hereinafter, for clarity purposes, many of the reference numbers are eliminated from subsequent drawings so as to focus on the portion of interest of the depository. In Figure 2B, a depository matrix 200, includes a collection of network software that has now been modularized into three components: a user interface component 204₀, an application component 204,, and a communication component 204₂. The user interface component 204₀ and the application component 204_! are further modularized into various management functionalities, such as Fault (F), Configuration (C), Account (A), Performance (P), and Security (S).

To build a desired network software from the collection of network software components 204, a customer would pick among software parts listed in column 202 and select a group of desired software parts. For example, suppose a customer wants to build network software to support ATM and ISDN. The customer would proceed to select the software part 206₀ to provide general management support for network elements, the software part 206, to support ATM, and the software part 206₇ to support ISDN. The software part 206₀ includes a particular software version of each component 204 that lies along the same row in the depository matrix 200,. Similarly, software parts 206_j and 206₇ include a particular software version of each component 204 that lies along the respective rows in the depository matrix 200,. Because the depository matrix 200, has undergone a modularizing process by the embodiments of the invention, there is no need for the customer to test the newly selected network software. There is confidence that the network software would perform as expected.

Figure 2C shows another view of Figure 2B. Figure 2C shows the software versions that are available for a customer to select for each of the components 204₀, 204,, and 204₂ for each software part as listed in column 202. Figure 3 illustrates a portion of the network software according to one aspect of the present invention. Network software 300 modularizes into three components: a user interface component 302, an application component 304, and a communication component 306. The user interface component 302 includes aspects of the network software that allow an operator to control a network element. The application component 304 includes aspects of the network software that provide the functionality that allows an operator to control a network element through the user interface component 302. The communication component 306 includes aspects of the network software to service a particular network standard, such as ATM or ISDN.

All three components are coupled together through a software bus 308. In various embodiments, the software bus includes Distributed Component Object Model (DCOM), Common Object Request Broker Architecture (CORBA), the Remote Method Invocation (RMI) of the Java programming language, and the extensible Markup Language (XML), etc.

Figure 4 illustrates a portion of the network software according to one aspect of the present invention. Network software 400 has been modularized according to the various embodiments of the present invention. Network software 400 modularizes into three main components: a user interface component 402, an application component 404, and a communication component 406. The network software 400 further modularizes by the functionality that manages the network element. The following offers a few types of network elements that can be modularized according to the various embodiments of the present invention: a general network element is represented by a user interface 412₀, an application 412_l3 and a communication medium 412₂. A SONET network element is represented by a user interface 414₀, an application 414,, and a communication medium 414₂. An ATM network element is represented by a user interface 416₀, an application 416,, and a communication medium 416₂. An ADSL network element is represented by a user interface 418₀, 418,, and 418₂.

In one embodiment, the plurality of applications 412,, 414_l5 416_l5 and 418j is stored in the database 408. In another embodiment, information to manage the plurality of communication mediums 412₂. 414₂, 416₂, and 418₂ is stored in a Management Information Base 410. There are lines in the network 400 connecting the various components of the network elements together. These lines represent the software bus that may be used by the components to transmit and receive control information and data.

Figure 5 illustrates a portion of the network software according to one aspect of the present invention. The portion of the network software 500 includes a user interface component 502 and an application component 504. The application component includes a database 506 to store a plurality of applications for the portion of the network software 500.

The portion of the network software 500 has been further modularized by management functionality. Management functionality has both a user interface component and an application component. The management functionality includes the following functions: Fault (F), Configuration (C), Account (A), Performance (P), and Security (S). The function Fault has a user interface component 508₀ and an application component 508₁. The function Configuration has a user interface component 510₀ and an application component 510,. The function Account has a user interface component 512₀ and an application component 512,. The function Performance has a user interface component 514₀ and an application component 514,. The function Security has a user interface component 516₀ and an application component 516,. Figure 5 shows lines connecting each of the user interface components to each of the application components. These lines represent a software bus that couples each of the user interface components to each of the application components, respectively.

Figure 6 is a process diagram of a method according to one aspect of the present invention. A process 600 for modularizing network software includes an act 602 for forming a first part of the network software. The first part is adapted to be used for providing distributed application management. The first part includes a plurality of components. The plurality of components includes a user interface component, an application component, and a communication component. Each of the components is adapted to communicate among each other by a software bus. The software bus is selected from a group consisting of Distributed Component Object Model (DCOM), Common Object Request Broker Architecture (CORB A), the Remote Method Invocation (RMI) of the Java programming language, and the extensible Markup Language (XML), etc.

The process 600 includes an act 604 for forming a second part of the network software. The second part is adapted to be used for providing network element functionality. The second part includes a plurality of network element function sets. Each network element function set has a representation in each component of the first part of the network software. Each network element function set is functionally independent from other network element function sets. Each network element function set includes configuration, security, alarms, and a networking standard. Examples of the network standard include Synchronous Optical Network (SONET), Asynchronous Transfer Mode (ATM), and Asymmetric Digital Subscriber Line (ADSL).

The process 600 includes an act 606 for forming a third part of the network software. The third part is adapted to be used for providing management functionality. The third part includes a plurality of management function sets. Each management function set has a representation for each network element function set. Each management function set includes fault, configuration, account, performance, and security functions. Figure 7 is a process diagram of a method according to one aspect of the present invention. A business process 700 for packaging network software is presented so as to allow such network software to be sold to customers. The business process 700 modularizes the network software into parts. Each part can be independently developed, independently tested, and independently supplied to customers. Because of such modularization, a customer may choose to purchase only a partial system. This allows a scaling of the network system so that a customer may add parts over time without having to purchase the entire system at once. The business process 700 includes an act 702 for forming a plurality of software parts. Each software part includes a plurality of components. Each software part is adapted to be functionally independent from another software part. The plurality of software parts is selected from a group consisting of network element functionality and network management functionality. Network element (NE) functionality is selected from a group consisting of network element management functionality, Asynchronous Transfer Mode (ATM) functionality, Asymmetric Digital Subscriber Line (ADSL) functionality, Synchronous Optical Network (SONET) functionality, GR-303 functionality, TR-008 functionality, TI functionality, Integrated Services Digital Network (ISDN) functionality, and Plain Old Telephone Service (POTS) functionality. The plurality of components of each software part includes a user interface component, an application component, and a communication component. Each component includes a plurality of versions that can be selected by a customer. The business process 700 includes an act 704 for packaging the network software for a network management system. The network software for the network management system includes at least one desired software part from the plurality of software parts. The act 704 for packaging includes an act for selecting a desired version of each component of each software part.

The business process 700 further includes an act for pricing the at least one desired software at a desired pricing level. The business process 700 further includes an act for pricing the network software at a desired pricing level. Figure 8 is a structure diagram of a data structure according to one aspect of the present invention. A structure 800 is presented for packaging network software so as to reduce or eliminate testing when the network software is changed or new functions added. The structure 800 includes a data member part 802 to represent a feature of the network software and a data member components 804 to represent the components of the feature of the network software.

The data components 804 includes a data member user interface 806. The data member user interface 806 includes a data member version 808 and a data member management functionality 810. The data member management functionality 810 includes a data member fault 812, a data member configuration 814, a data member account 816, a data member performance 818, and a data member security 820.

The data member components 804 further includes a data member application 822. The data member application 822 includes a data member version 824 and a data member management functionality 826. The data member management functionality 826 includes a data member fault 828, a data member configuration 830, a data member account 832, a data member performance 834, and a data member security 836. The data member components 838 further includes a data member communication 838. The data member communication 838 includes a data member version 840.

Conclusion Methods and structures have been discussed to modularize network software. Such modularization reduces or eliminates the need to retest the network software after changes or new functions are added. Additional benefits of the modularization provided by the embodiments of the present invention include software stability, reduction of performance risk, and a reduction of the time needed to place the network software in the marketplace. Although the specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention. It is to be understood that the above description is intended to be illustrative, and not restrictive. Combinations of the above embodiments and other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention includes any other applications in which the above structures and fabrication methods are used. Accordingly, the scope of the invention should only be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

1 claim:

1. A method for modularizing element management system of the network software, comprising: forming a first part of the network software, wherein the first part is adapted to be used for providing distributed application management; forming a second part of the network software, wherein the second part is adapted to be used for providing network element functionality; and forming a third part of the network software, wherein the third part is adapted to be used for providing management functionality.

2. The method of claim 1 , wherein forming includes forming a first part, wherein the first part includes a plurality of components, wherein the plurality of components includes a user interface component, an application component, and a communication component.

3. The method of claim 2, wherein forming includes forming a first part, wherein the plurality of components is adapted to communicate among each other by a software bus.

4. The method of claim 3, wherein forming includes forming a first part, wherein the software bus is selected from a group consisting of Distributed Component Object Model, Common Object Request Broker Architecture, and Remote Method Invocation, extensible Markup Language.

5. The method of claim 2, wherein forming includes forming a second part, wherein the second part includes a plurality of network element function sets.

6. The method of claim 5, wherein forming includes forming a second part, wherein each network element function set has a representation in each component of the first part of the network software.

7. The method of claim 6, wherein forming includes forming a second part, wherein each network element function set is functionality independent from other network element function set.

8. The method of claim 5, wherein forming includes forming a second part, wherein each network element function set includes configuration, security, alarms, and a networking standard.

9. The method of claim 8, wherein forming includes forming a second part, wherein the networking standard is selected from a group consisting of

Synchronous Optical Network, Asynchronous Transfer Mode, and Asymmetric Digital Subscriber Line.

10. The method of claim 6, wherein forming includes forming a third part, wherein the third part includes a plurality of management function sets, wherein each management function set has a representation for each network element function set.

11. The method of claim 10, wherein forming includes forming a third part, wherein each management function set includes fault, configuration, account, performance, and security.

12. A business method for packaging network software, comprising: forming a plurality of software parts, wherein each software part includes a plurality of components, wherein each software part is adapted to be functionally independent from another software part; and packaging the network software for a network management system, wherein the network software for the network management system includes at least one desired software part from the plurality of software parts.

13. The business method of claim 12, further comprising pricing the at least one desired software part at a desired pricing level.

14. The business method of claim 12, further comprising pricing the network software at a desired pricing level.

15. The business method of claim 12, wherein forming includes forming a plurality of network software parts, wherein the plurality of software parts is selected from a group consisting of network element functionality and network management functionality.

16. The business method of claim 15, wherein forming includes forming a plurality of network software parts, wherein network element functionality are selected from a group consisting of network element management functionality, Asynchronous Transfer Mode functionality, Asymmetric Digital Subscriber Line functionality, Synchronous Optical Network functionality, GR-303 functionality, TR-008 functionality, TI functionality, Integrated Services Digital Network functionality, and Plain Old Telephone Service functionality.

17. The business method of claim 12, wherein the plurality of components includes a user interface component, an application component, and a communication component.

18. The business method of claim 17, wherein forming includes forming a plurality of software parts, wherein each component includes a plurality of versions.

19. The business method of claim 18, wherein packaging includes selecting a desired version of each component.

20. A computer readable medium having instructions stored thereon for causing a computer to perform a business method for packaging network software, the method comprising: forming a plurality of software parts, wherein each software part includes a plurality of components, wherein each software part is adapted to be functionally independent from another software part; and packaging the network software for a network management system, wherein the network software for the network management system includes at least one desired software part from the plurality of software parts.

21. A data structure for packaging network software, comprising: a data member part to represent a feature of the network software; and a data member components to represent the components of the feature.

22. The data structure of claim 21 , wherein the data member components includes a data member user interface, a data member application, and a data member communication medium.

23. The data structure of claim 22, wherein the data member user interface includes a data member version and a data member management functionality.

24. The data structure of claim 23, wherein the data member management functionality of the data member user interface, includes a data member fault, a data member configuration, a data member account, a data member performance, and a data member security.

25. The data structure of claim 22, wherein the data member application includes a data member version and a data member management functionality.

26. The data structure of claim 25, wherein the data member management functionality of the data member application includes a data member fault, a data member configuration, a data member account, a data member performance, and a data member security.

27. The data structure of claim 22, wherein the data member communication medium includes a data member version.