Dynamic Hierarchical Address Resource Management Architecture, Method and Apparatus

Abstract

A Dynamic Hierarchical Address Resource Management Architecture (DHARMA) coordinates a logical hierarchy of address spaces with a virtual topology of network elements using a manageable database environment. Address spaces are apportioned into hierarchical levels in accordance with a network policy. Network elements may be represented as objects, coupled via the logical address space. Both address space hierarchy definition and virtual topology modelling may occur independent from actual network deployment. As a result, multiple address space hierarchy definitions and virtual topologies can be pre-generated and stored for selective use during network deployment. With such an arrangement, a flexible addressing architecture is provided which may advantageously be used in any network that desires dynamic network configuration. The connection between the logical address hierarchy and the virtual network topology may advantageously be implemented through the use of a logical tag that links a virtual network element to a logical address hierarchy level.

1 . A method of allocating an address space to a network routing element, the method comprising:
 the network routing element requesting allocation of an address space by generating a request comprising an identifier of the network routing element;   in response to the request, an address space allocated determining a respective tag based on the identifier of the network routing element;   in response to determination of the respective tag, the address space allocated determining an address prefix based on the respective tag;   the address space allocated providing the address prefix to the network routing element; and   the network routing element allocating respective addresses to network elements connected to the network routing element, the respective addresses comprising the address prefix.   
     
     
         2 . The method of  claim 1 , wherein the identifier of the network routing element is an address allocated to the network routing element. 
     
     
         3 . The method of  claim 2 , wherein the address allocated to the network routing element is a media access control (MAC) address. 
     
     
         4 . The method of  claim 1 , wherein the identifier of the network routing element comprises a media access control (MAC) address of the network routing element. 
     
     
         5 . The method of  claim 1 , wherein the request is a bootstrap request. 
     
     
         6 . The method of  claim 1 , wherein the address space allocated comprises:
 a translation table which maps network routing element identifiers onto tags; and   at least one virtual network topology model which maps tags onto address prefixes.   
     
     
         7 . The method of  claim 6 , wherein the address space allocated comprises multiple alternative virtual network topology models. 
     
     
         8 . The method of  claim 6 , wherein the at least one virtual network topology model is based, at least in part, on characteristics of network routing elements other than locations of the network routing elements in a physical network. 
     
     
         9 . The method of  claim 1 , wherein the tag is mapped onto the identifier of the network routing element based on at least one characteristic of the network element other than a location of the network routing element in a physical network. 
     
     
         10 . The method of  claim 1 , wherein the respective tag determined based on the identifier of the network routing element is associated with a respective level in an address hierarchy of the address space. 
     
     
         11 . The method of  claim 10 , wherein the respective level is other than a Top Level, a Next Level and a Site Level of an IPv6 address space. 
     
     
         12 . The method of  claim 1 , wherein the tag is neither a MAC address nor an IP address. 
     
     
         13 . The method of  claim 1 , wherein the address space allocated comprises:
 a policy broker which maps network routing element identifiers onto tags; and   a prefix server that maps tags onto address prefixes.   
     
     
         14 . The method of  claim 13 , wherein:
 the policy broker comprises a translation table which maps network routing element identifiers onto tags; and   the prefix server comprises at least one virtual network topology model which maps tags onto address prefixes.   
     
     
         15 . The method of  claim 13 , wherein the prefix server comprises multiple alternative virtual network topology models. 
     
     
         16 . The method of  claim 13 , wherein the at least one virtual network topology model is based, at least in part, on characteristics of network routing elements other than locations of the network routing elements in a physical network.