International Business Machines Corporation

Broadcom Corporation

Alejandro Emilio Vásquez

Andrey L Tsigler

Hassan Elmosallamy Ibrahim Hassan

Katherine Marie McDowell

Steven Howard Johnson

Peter D Beal

Gregory Francis Paussa

Wynona Persephone Jacobs

Colin Michael Winegarden

Steven Edward Ledford

James Steele Gaillard

Embodiments of this invention comprise a modular, scalable architecture for building a variety of Layer 2/3/4+ Ethernet products and devices. Such devices or units can be attached to form an homogenous systems called stack. The invention provides a set of rules to handle such stack. The rules are controlled by the architectural component named Unit Manager. The Unit Manager uses a protocol to discover the units that are entering or leaving the system/stack. The protocol's data provides a unique way of identifying the units that belong to the system stack.

Component identification and transmission system

Embodiments of this invention comprise a modular, scalable architecture for building a variety of Layer 2/3/4+ Ethernet products and devices. Such devices comprise of a set modules. The invention provides a set of rules to handle such modules. The rules are controlled by the architectural component named card manager. The card manager uses a protocol to discover the modules that are entering or leaving the system/device. The protocol's data provides a unique way of identifying the modules that belong to the system.

Counters are implemented within an 802.1Q VLAN (Virtual Local Area Network) bridge model to assist a network administrator in diagnosing network problems associated with the dynamic registration of VLANs. Such counters are able to count the number of dynamic VLANs propagated through a bridging device, and for monitoring the maximum number of VLANs ever simultaneously configured on a bridge device.

Counting of GVRP protocol data units within a network bridge

An alterable device driver development system for supporting various operating systems, network protocols, and adapter hardware interfaces. Each device driver comprises a System, Network and Adapter software component, each component providing services to the other through its associated programming interfaces and being alterable or replaceable according to the requirements of an associated adapter hardware product. The System component supports a set of services defined by the device driver and which can be used by the Network and Adapter components. The Network component manages all interactions of the Adapter component with a network operating system or protocol stack and ensures its applicability and correctness in the context of the device driver operation. The Adapter component provides the functions for operating and managing all interactions with the adapter hardware. A Transformation Path in the Adapter component improves device driver performance by mapping network packet descriptors against adapter packet descriptors in data transferring processes.

Design methodology for device drivers supporting various operating

Growing community of inventors

Raleigh, NC, United States of America

Alejandro Emilio Vásquez