Method and apparatus supporting network communications

• US 7,447,728 B1
• Filed: 02/02/2004
• Issued: 11/04/2008
• Est. Priority Date: 10/31/1996
• Status: Expired due to Fees

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Arunkumar, Nagaraj, Nilakantan, Chandrasekharan, Loi, Ly
• Primary Examiner(s): Vu; Thong H
• Application Number:
  US10/770,065
• Time in Patent Office: 1,737 Days
• Field of Search: 709/202, 709/217, 709226-228, 709/237, 709/249, 709/250, 709/232, 370/249, 370/431, 713/151
• US Class Current: 709/200
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

One embodiment of the invention includes a method of managing network communications in a network device. The network device includes software components and modules. Some of the components control the interaction between modules, while other components perform specific functions for associated modules. A module manager component controls the creation and destruction of modules as well as their interactions. A communications manager component manages network communications in the network device. The network communications is supported by creating a number of modules that are associated with components that implement different parts of a network protocol. As a result of the use of the modules, a component need not know which other component(s) it depends upon, nor need it know which other component(s) depend upon it. This allows components to be used together very easily in many different configurations. The modules also allow the same component to be used by multiple modules.

Claims

1. A network device comprising:

a first software component that provides an interface to a first network protocol layer in a stack of network protocol layers, the first software component being a device driver and the first network protocol layer provides an interface to a physical media;

a second software component that provides an interface to a second network protocol layer in the stack of network protocol layers, the second software component being a device driver and the second network protocol layer provides an interface to a physical media;

a first module associated with the first software component, wherein the first module facilitates communication between the first software component and other software components that provide interfaces to other network protocol layers in the stack of network protocol layers;

a second module associated with the second software component, wherein the second module facilitates communication between the second software component and other software components that provide interfaces to other network protocol layers in the stack of network protocol layers;

a module manager for controlling creation and destruction of the first and second modules as required to control the first and second software components to service data packets that require a particular protocol and for managing interaction between the first and second modules;

a configuration file that defines which software components to use to establish a port for a particular path, wherein the first and second modules correspond to different software components that support different parts of the communications protocol used to create the port for the particular path; and

a communications manager for accessing the configuration file to determine the components used to establish the port and for sending requests to the module manager to create modules associated with the software components used to establish the port.

2. The network device of claim 1, wherein the module manager assigns dependencies of modules on each other and thereby creates the module stack.

3. The network device of claim 2, wherein the module manager includes an application program interface (“

API”

) that further includes insertModuleAfter(uniqueModuleID) and linkModuleAbove(uniqueModuleID) functions for building the module stack.

4. The network device of claim 1, wherein the first module includes:

an Owner ID that identifies the first software component associated with the first module;

a Module ID that defines an identifier used by the first software component to refer to the first module; and

upstream and downstream links that point to modules above and below the first module in a module stack.

5. The network device of claim 1, wherein the first and second software components are processes, and wherein the first and second modules are data structures.

6. The network device of claim 1, wherein the first network protocol layer is a point-to-point protocol (“

PPP”

) layer, a frame relay layer, a high speed serial interface driver (“

HSSID”

) layer or a integrated services digital network (“

ISDN”

) driver layer.

7. The network device of claim 1, wherein the network device is a router or a network interface card.

8. A method for communication between network protocol layers in a network device, wherein the network device includes a first software component that provides an interface to a first network protocol layer, a first module that provides an interface between the first software component and a module manager, the method comprising:

accessing a configuration file that defines using the first software component, an upstream software component and a downstream software component, at least in part, to establish a port for a particular path;

the module manager responsively creating the first module, an upstream module and a downstream module;

the first software component generating an event and sending the event to the first module;

reporting the event to the upstream module, wherein the upstream module provides an interface to the upstream software component that in turn provides an interface to a network protocol layer above the first network protocol layer in a network protocol layer stack;

reporting the event to the downstream module, wherein the downstream module provides an interface to the downstream software component that in turn provides an interface to a network protocol layer below the first network protocol layer in the network protocol layer stack; and

notifying the module manager of the event,

wherein the first software component registers references to functions with the first module, wherein the upstream and downstream software components can call the functions through information stored in the first module.

9. The method of claim 8, further comprising:

the upstream module notifying the upstream software component of the event; and

the downstream module notifying the downstream software component of the event.

10. The method of claim 8, wherein responsively creating the first, upstream and downstream modules comprises the module manager using an application program interface to define a specific order of the modules in a module stack.

11. The method of claim 10, wherein the application program interface includes insertModuleAfter(uniqueModuleID) and linkModuleAbove(uniqueModuleID) functions used to define the specific order of the modules in the module stack.

12. The method of claim 8, wherein the first, upstream and downstream software components cooperatively provide services to a device interfaced with the network device, the method further comprising:

detecting that the device has become available on the network device; and

responsively creating the first, upstream and downstream modules.

13. The method of claim 12, wherein detecting that the device has become available on the network device comprises detecting that the device has been hot-swapped into the network device.

14. The method of claim 8, wherein the first, upstream and downstream software components cooperatively provide services to a device interfaced with the network device, the method further comprising:

detecting that the device is no longer available; and

responsively destroying the first, upstream and downstream modules.

15. The method of claim 8, wherein the first, upstream and downstream software components are processes, and wherein the first, upstream and downstream modules are data structures.

16. The method of claim 8, wherein the first software component can only communicate with the upstream and downstream software components through functionality provided by the first, upstream and downstream modules.

17. The method of claim 8, wherein downstream first network protocol layer is a point-to-point protocol (“

PPP”

) layer, an Internet Protocol layer or a frame relay layer.

18. A network device comprising:

a processor;

memory;

a first module stored in the memory and executable on the processor to i) receive an event from a first software component, wherein the first software component provides an interface to a first network protocol layer, ii) determine upstream modules that are dependent on the first module, wherein each upstream module provides an interface to respective upstream software components that in turn provide interfaces to a network protocol layer above the first network protocol layer in a network protocol layer stack, iii) notify the upstream modules of the event, iv) determine downstream modules that are dependent on the first module, wherein each downstream module provides an interface to respective downstream software components that in turn provide interfaces to a network protocol layer below the first network protocol layer in the stack of network protocol layers, v) notify the downstream modules of the event;

a module manager stored in the memory and executable on the processor to i) create the first, upstream and downstream modules, ii) define an order of the first, upstream and downstream modules thereby creating a module stack, iii) receive a notification of the event, and iv) destroy the first, upstream and downstream modules; and

instructions stored in the memory and executable on the processor to i) determine that a device interfaced with the network device has become available, ii) determine that the first, upstream and downstream software components provide services to the device, and iii) responsively create the first, upstream and downstream modules providing interfaces to the first, upstream and downstream software components.

19. The network device of claim 18, further comprising a configuration file defining that the first, upstream and downstream components are used to establish a port for a path.

20. The network device of claim 18, further comprising instructions stored in the memory and executable on the processor to i) determine that the device interfaced with the network device has become unavailable, and ii) responsively destroy the first, upstream and downstream modules.

21. The network device of claim 18, wherein the first module includes references to functions implemented in the first software component that can be called by the upstream and downstream software components.

22. The network device of claim 18, wherein the module manager includes a finite state machine that can be used by the first, upstream and downstream modules.

23. The network device of claim 18, wherein the first, upstream and downstream modules each include a finite state machine.

24. The network device of claim 18, wherein the network device is a router or a network interface card.