Format for automatic generation of unique ATM addresses used for PNNI

[00002] 1. Field of the Invention

[00003] The invention relates to a format for automatic generation of unique ATM addresses used for PNNI.

[00004] 2. Related Art

[00005] In known ATM systems, each node performing the PNNI protocol must be assigned a unique 20-byte ATM address in a standard format specified by the ATM Forum User-Network Interface Specification (Presently version 3.1). The “PNNI protocol” refers to the protocol specified by the ATM Forum Private Network-Network Interface Specification (presently version 1.0).

[00006] One technique for assigning unique addresses for nodes in an ATM network is to assign them manually, thus assuring that each address is unique and also that the nodes form peer groups as desired by the operator configuring the ATM network. However, this technique can be tedious, particularly for ATM networks which include a relatively large number of nodes.

[00007] Accordingly, it would be advantageous to provide a method and system for assigning ATM addresses automatically, which by default causes similar devices (such as those from the same manufacturer) to be configured in the same peer group for PNNI protocol purposes. This advantage is achieved in an embodiment of the invention in which a first portion of an ATM address is set to a value unique to the manufacturer (or otherwise unique to a selected class of devices), while a second portion of the ATM address is set to a value unique to the specific device.

[00008] The invention provides a method and system for providing unique ATM End System Addresses, in which each new device is assigned a unique address in an ATM network while allowing all new devices performing the PNNI protocol in a selected set (such as all those from a single manufacturer) to be assigned by default to the same peer group. In the invention, a first portion of the ATM address (from which the default peer group ID is determined) is by default configured to equal a selected value unique to the manufacturer (or another selected class of devices), which, assures that all devices from the same manufacturer (or in that selected class) are by default configured in the same peer group for PNNI protocol purposes, while a second portion of the ATM address (comprising a switch number ID) and a third portion of the ATM address (comprising a device number ID) are by default both configured to equal a unique value for the device (such as a MAC address), which assures that each device is configured with a unique ATM address. In alternative embodiments, the third portion of the ATM address may be determined using a different method, so long as selection of the third portion causes each device to be assigned a unique ATM address by default.

[00010] In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. Those skilled in the art would recognize after perusal of this application that embodiments of the invention can be implemented using general purpose switching processors or special purpose switching processors or other circuits adapted to particular process steps and data structures described herein, and that implementation of the process steps and data structures described herein would not require undue experimentation or further invention.

[00011] Inventions described herein can be used in conjunction with inventions described in the following applications:

[00012] Application Ser. No. 08/862,915, filed May 23, 1997, Express Mail Mailing No. EM302071674US, in the same inventors, titled “Next Hop Selection In ATM Networks, and

[00013] Application Ser. No. 08/863,031, filed May 23, 1997, Express Mail Mailing No. EM302071665US, in the same of the same inventor(s), titled “Call size Feedback on PNNI Operation”.

[heading-00014] Autoconfigured ATM Address

[00015] FIG. 1 shows a data structure diagram of an autoconfigured address in an ATM network.

[00016] An autoconfigured ATM address 100 comprises a 20-byte AIM address value, including an API field 110, a manufacturer ID field 120, a manufacturer-specific field 130, a switch number ID field 140, a device number ID field 150, and a selector field 160. The ATM address 100 is an ATM End System Address as defined in Section 5.1.3.1 of the ATM Forum User-Network Interface Specification (version 3.1)”.

[00017] The AFI field 110 comprises a single byte (each byte comprises one octet) and has the value hexadecimal 47. This value indicates that ATM addresses are assigned in conformity with the ICD (International Code Designator) format. In alternative embodiments, ATM addresses may be assigned in conformity with other formats, such as the DCC (Data Country Code) or E.164 formats.

[00018] The manufacturer ID field 120 comprises two bytes and has a value which is specific to a manufacturer of the specific device, as specified by the ATM address authority associated with the selected value on the AFI field 110; for the ICD format that authority is the British Standards Institute. In a preferred embodiment, the value hexadecimal 00 91 is reserved for products manufactured by Cisco Systems, Inc. of San Jose, Calif. There is no special significance to this specific value; it is simply the value which is assigned to the manufacturer by the ATM address authority associated with the value hexadecimal 47 in the AFI field 110.

[00019] The manufacturer-specific field 130 comprises four bytes and has a value assigned by the manufacturer. In a preferred embodiment, when the manufacturer is Cisco Systems, Inc., of San Jose, Calif., this value is uniformly selected to be hexadecimal 81 00 00 00. There is no special significance to the special value, which could be any selected value so long as maintained consistent across devices manufactured by the same manufacturer.

[00020] Collectively, the first seven bytes of the ATM address 100 (the AFI field 110, the manufacturer ID field 120, and the manufacturer-specific field 130) comprise a peer group ID field 171 used in PNNI protocols for ATM routing. This peer group ID field 171 is only seven bytes, not the 14 bytes which are used for PNNI routing in known ATM networks to determine the default peer group ID. The level value is set accordingly to 56 bits to indicate only a seven byte peer group ID field 171. Those devices which have the same value in the peer group ID field 171 are treated as members of the same peer group for PNNI protocol purposes. Because those devices manufactured by the same manufacturer have the same value in the peer group ID field 171, they are thus configured by default all in the same peer group for protocol purposes.

[00021] In alternative embodiments, a single manufacturer may provide devices which are autoconfigured to have differing values for the manufacturer-specific field 130, such as for example hexadecimal 81 00 00 00 for a first set of devices and hexadecimal 81 00 00 01 for a second set of devices. The first set of devices would thus be configured by default in a first peer group, while the second set of devices would thus be configured by default in a second peer group distinct from the first peer group. There is no special significance to these specific values, which could be any selected values so long as maintained consistent across sets of devices manufactured by the same manufacturer.

[00022] The switch number ID field 140 comprises six bytes and has a value equal to a MAC address for the device. In alternative embodiments, the switch number ID field 140 may be configured to equal a different unique value for the device.

[00023] Although in a preferred embodiment, a switch is typically a single device, a switch may also comprise a plurality of devices comprising a switching system, such as a set of one or more physical devices acting together as a single PNNI network management entity. A switching system generally includes one or more lowest-level nodes and, when acting as a PGL (peer group leader) in the PNNI protocol, also includes one or more LGNs (logical group node). A switching system can include a plurality of lowest-level PNNI nodes, and in such cases, each node could have a different ATM address.

[00024] Collectively, the first 13 bytes of the ATM address 100 (the AFI field 110, the manufacturer ID field 120, the manufacturer-specific field 130, and the switch number ID field 140) comprise a switch ID 172 used in PNNI protocols for ATM routing. Because the MAC address (or other selected unique value) for the device is unique, the switch ID 172 is therefore unique to the switch. An end system which is coupled to the device, and thus to the ATM network, uses the switch ID 172 supplied by the switch, together with a unique ESI (End System Identifier) assigned to the end system, plus a selector byte, to determine a unique ATM address for the end system.

[00025] The device number ID field 150 comprises six bytes and also has a value equal to a MAC address for the device. In alternative embodiments, the device number ID field 150 may be configured to equal a different unique value for the device. Because the MAC address (or other selected unique value) for the device is unique, the ATM address 100 is therefore unique to the device.

[00026] The selector field 160 comprises one byte and has the value hexadecimal 00. There is no special significance to this specific value, which could be any selected value.

[00027] When the device is coupled to an ATM network, the ATM address 100 is autoconfigured to the values shown herein. The ATM address 100 can be modified by an operator to take on a different value if the autoconfigured value is not advantageous.

[00028] Alternative Embodiments

[00029] Although preferred embodiments are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.