Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

EFFICIENT RESOURCE IDENTIFICATION MANAGEMENT SCHEME ACROSS INDEPENDENT BUT RELATED RESOURCE POOLS IN A HIERARCHICAL RESOURCE SCENARIO OF A SWITCH ASSEMBLY SYSTEM

IP.com Disclosure Number: IPCOM000245533D
Publication Date: 2016-Mar-15

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure relates to managing a set of resources as a tree with nodes and leaves. Each node of the tree typical represents a logical unit (Chassis, Line-Blades, Ports, hardware-chips, etc.). At the lowest level, each leaf represents the base unit at which the resources are being managed (e.g. hardware-chip). The expectation is resources are allocated and deallocated relative to a set of leaves at the lowest level as determined by the singular node-level at which the allocation/deallocation is being requested. Allocation/Deallocation requests propagate down through all child nodes and up through singular parent nodes of the resource tree. This disclosure introduces the ability to maintain unique maskable resource ID pools at non-root levels of the resource tree coupled with the ability to manage the IDs as an atomic unique ID unit across multiple leaves at the same level of the hierarchy in an efficient manner.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 5% of the total text.

EFFICIENT RESOURCE IDENTIFICATION MANAGEMENT SCHEME ACROSS INDEPENDENT BUT RELATED RESOURCE POOLS IN A HIERARCHICAL RESOURCE SCENARIO OF A SWITCH ASSEMBLY SYSTEM

ABSTRACT

[0001]               This disclosure relates to managing a set of resources as a tree with nodes and leaves. Each node of the tree typical represents a logical unit (Chassis, Line-Blades, Ports, hardware-chips, etc.). At the lowest level, each leaf represents the base unit at which the resources are being managed (e.g. hardware-chip). The expectation is resources are allocated and deallocated relative to a set of leaves at the lowest level as determined by the singular node-level at which the allocation/deallocation is being requested. Allocation/Deallocation requests propagate down through all child nodes and up through singular parent nodes of the resource tree.  This disclosure introduces the ability to maintain unique maskable resource ID pools at non-root levels of the resource tree coupled with the ability to manage the IDs as an atomic unique ID unit across multiple leaves at the same level of the hierarchy in an efficient manner.

BACKGROUND

[0002]               There is an ever increasing need for high speed and high-performance computer networks which can support high bandwidths. Ethernet is a commonly used technology for such high speed and high-performance computer networks. Ethernet systems can be based on IEEE 802 standards, and typically employ several layers of hardware resources to enable network switching and routing functions. The well-known open systems interconnect (OSI) 7-layer reference model specifies inter alia, a physical layer which defines electrical and physical specifications for devices connected to a network and a data link layer which specifies functional and procedural means for transferring data between network devices and entities. Ethernet technology can span both of these layers, and generally include hardware devices such as routers, repeaters, bridges, switches, blades, ports, etc.

[0003]               In general, the devices in an Ethernet switch assembly system tend to follow a hierarchical structure. For example, a chassis is a frame or box which can support mounting of components of a device. The chassis can have multiple blades or “line blades.” Ports may be connected to the line blades. Hardware devices, such as end user network devices like personal computers, can be connected to the ports.

[0004]               Representatively, the one or more chassis may make up a root level in a network fabric, one or more levels of blades may be branches, and one or more ports and devices connected thereto may comprise leaves. However, conventional management of resources tends to be compartmentalized. For example, each component such as a chassis, line blade, port, etc., is allocated a predefined amount of resources in terms of, for example, number of ports, bandwidth, etc. This leads to an overly restrictive provisioning of resources, as each component needs to draw from a static pool of re...