Discovery of physically adjacent neighbor devices using a unidirectional in-band process coupled with an out-of-band follow-up process

FIELD OF THE INVENTION

0001The present invention relates generally to the telecommunications and optical networking fields. More specifically, the present invention relates to the discovery of physically adjacent neighbor devices using a unidirectional in-band (in-fiber) process coupled with an out-of-band follow-up process.

BACKGROUND OF THE INVENTION

0002Discovery is the process whereby neighboring nodes on either side of a link automatically determine each others' identity and verify the connectivity between them. There can be “layer adjacency discovery” between nodes that have interfaces or switching capabilities at the same layer, and “physical adjacency discovery” between nodes that have interfaces or switching capabilities at different layers. Current International Telecommunications Union—Telecommunications Division (ITU-T) standards and Optical Internetworking Forum (OIF) implementation agreements define methods for layer adjacency discovery, wherein there is a bidirectional link available between neighboring nodes, using the control overhead bytes present in Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) and Optical Transport Network (OTN) formatted links (see, for example, ITU-T Recommendations G.7714 and G.7714.1, and OIF User Network Interface (UNI) 1.0 Signaling Specification). Likewise, the Internet Engineering Task Force (IETF) defines a “link management protocol” that does not perform automatic discovery, as the Internet Protocol (IP) addresses of neighboring nodes must first be configured into the system, but that can be used after discovery, or with configured information, to exchange link capabilities and verify connectivity (see Internet Draft).

0003Thus, layer adjacency discovery is logically performed at a specific layer (i.e., discovery can be at the fiber wavelength or SONET path/line/section (OTN ODU/OTU) layers). While the provisioning of such information is not difficult, the provisioning process is typically a manual process with several steps that may lead to errors being incorporated into a topology database. Any method that increases the accuracy of the topology database is helpful to carriers, and an automated or partially-automated method is most useful.

0004ITU-T and OIF layer adjacency discovery methods rely on the existence of a bidirectional link between neighboring nodes at a specific layer and the availability of an in-band channel at that specific layer over which a discovery message can be sent, unimpeded by any equipment placed in between the neighboring nodes that operates at a different layer. SONET/SDH and OTN control overhead bytes are designed to be passed transparently by equipment at a lower layer (e.g., path overhead is passed transparently by line and section terminating equipment, line overhead is passed transparently by section terminating equipment, etc.). Certain fields, such as bit error monitoring bytes (BIP-8), are created based on the bit values in a frame, and if any information in the control overhead bytes is changed by intervening equipment, this either invalidates the bit error monitoring bytes (potentially causing an error indication) or requires that the intervening equipment modify the bit error monitoring bytes to correct for the change in the control overhead bytes.

0005If either a bidirectional link is not available or a peer relationship does not exist, standard discovery methods do not work. If neighboring nodes are not peers (i.e., do not operate at the same layer), then one endpoint may be able to write information into the control overhead bytes, but the other endpoint may not, as its role is normally to pass the control overhead bytes transparently. In particular, if a node which normally passes the control overhead bytes transparently is called upon to write information into the control overhead bytes, this disrupts the parity bits used for performance monitoring on the frame and an intervening node may have to recalculate the parity bits. This may also result in a false performance monitoring reading at the node terminating the frame. If only a unidirectional link is available, only one node will receive its neighbor's identity.

0006This makes it complex and costly for equipment to use standard discovery methods if the equipment is not operating at a peer layer, since equipment operating at a lower layer cannot modify overhead by inserting its own address and information without correspondingly recalculating the bit error monitoring bytes. Moreover, equipment operating at a lower layer cannot be designed to insert information into overhead, since this is not a standard function. Monitoring the contents of overhead, however, is a useful function and can be used to determine, for example, the performance of a transported signal.

0007Thus, what is needed in the art is an automated discovery method for equipment that does not operate at a peer layer and, as a result, cannot perform bidirectional interaction using control overhead bytes to detect the address/identity of a physically adjacent node. What is also needed in the art is a method for using out-of-band protocol messages, such as Link Management Protocol (LMP) messages (or other protocol messages as defined in the ITU-T standards for link capability exchange), to allow equipment to carry its own address/node identification (ID) and link information back to the physically adjacent node. A method for the authentication of the received out-of-band message is desirable in order to ensure that the received out-of-band message was generated by an actual neighboring node, since out-of-band messages can presumably be received from any node connected to the same control network.

BRIEF SUMMARY OF THE INVENTION

0008In accordance with the methods and systems of the present invention, equipment generates a discovery message containing its address/node ID and/or other information, such as link information. Adjacent equipment (e.g., physically adjacent equipment) monitors control overhead bytes (section trace (J0) bytes, Data Communication Channel (DCC) control overhead, General Communication Channel (GCC) control overhead, etc.) for this message, but does not generate a corresponding response message as called for in the standards/implementation agreements. Rather, it records the address/node ID and/or other information in order to identify its neighbor, and uses an alternative mechanism to either record the adjacency separately (e.g., at a Network Management System (NMS) in order to populate or verify its topology database) or communicate an out-of-band control message to the neighbor (e.g., using the received address/node ID as the destination address for the out-of-band control message, which carries its own address/node ID and link information). Such automated population and/or verification of node and/or NMS topology databases improves the speed and accuracy of network resource allocation.

0009In this manner, automated discovery is possible for equipment that does not operate at a peer layer and, as a result, cannot perform bidirectional interaction using control overhead bytes. Advantageously, automated discovery is possible with minimal complexity and cost. The methods and systems of the present invention also provide an out-of-band follow-up method using LMP messages (or other protocol messages as defined in the ITU-T standards for link capability exchange) as the format for carrying address/node ID and link information back to a physically adjacent node. As described above, a method for the authentication of the received out-of-band control message is desirable in order to ensure that the received out-of-band control message was generated by an actual neighboring node, since out-of-band control messages can presumably be received from any node connected to the same control network.

0010In one exemplary embodiment of the present invention, a unidirectional in-band and out-of-band follow-up method for discovering physically adjacent neighbor devices in a telecommunications network includes, at a first device, generating an in-band discovery message including identification information related to the first device; at a second device, receiving the in-band discovery message including the identification information related to the first device and recognizing the first device as a neighbor device; and, from the second device, communicating the identification information related to the first device to a network management system via an out-of-band communication. The method also includes, from the second device, communicating identification information related to the second device to the network management system via an out-of-band communication. The method further includes, from the network management system, communicating the identification information related to the second device to the first device via an out-of-band communication. The in-band discovery message including the identification information related to the first device consists of one of section trace (J0) bytes, Data Communication Channel (DCC) control overhead, and General Communication Channel (GCC) control overhead. Optionally, the second device includes a tunable filter and a receiver collectively operable for selectively receiving the in-band discovery message including the identification information related to the first device. The method still further includes, at the network management system, populating a topology database with the information related to the first device. The method still further includes, from the network management system, communicating one or more of the identification information related to the first device and identification information related to the second device to one or more other devices via one or more out-of-band communications. The identification information related to the first device includes one or more of a contact address, node identification information, node capability information, and link connectivity information. The identification information related to the second device includes one or more of a contact address, node identification information, node capability information, link connectivity information, and an out-of-band discovery message. The method still further includes, at the first device, receiving the identification information related to the second device and recognizing the second device as a neighbor device. Finally, the method includes, at the network management system, populating a topology database with the information related to the second device.

0011In another exemplary embodiment of the present invention, a unidirectional in-band and out-of-band follow-up method for discovering physically adjacent neighbor devices in a telecommunications network includes, at a first device, generating an in-band discovery message including identification information related to the first device; at a second device, receiving the in-band discovery message including the identification information related to the first device and recognizing the first device as a neighbor device; from the second device, communicating the identification information related to the first device to a network management system via an out-of-band communication; from the second device, communicating identification information related to the second device to the network management system via an out-of-band communication; from the network management system, communicating the identification information related to the second device to the first device via an out-of-band communication; and, at the first device, receiving the identification information related to the second device and recognizing the second device as a neighbor device. The in-band discovery message including the identification information related to the first device consists of one of section trace (J0) bytes, Data Communication Channel (DCC) control overhead, and General Communication Channel (GCC) control overhead. Optionally, the second device includes a tunable filter and a receiver collectively operable for selectively receiving the in-band discovery message including the identification information related to the first device. The method also includes, at the network management system, populating a topology database with the information related to the first device. The method further includes, from the network management system, communicating one or more of the identification information related to the first device and identification information related to the second device to one or more other devices via one or more out-of-band communications. The identification information related to the first device includes one or more of a contact address, node identification information, node capability information, and link connectivity information. The identification information related to the second device includes one or more of a contact address, node identification information, node capability information, link connectivity information, and an out-of-band discovery message. The method still further includes, at the network management system, populating a topology database with the information related to the second device.

0012In a further exemplary embodiment of the present invention, a unidirectional in-band and out-of-band follow-up system for discovering physically adjacent neighbor devices in a telecommunications network includes a first device operable for generating an in-band discovery message including identification information related to the first device; and a second device operable for receiving the in-band discovery message including the identification information related to the first device and recognizing the first device as a neighbor device, wherein the second device is further operable for communicating the identification information related to the first device to a network management system via an out-of-band communication. The second device is further operable for communicating identification information related to the second device to the network management system via an out-of-band communication. The network management system is operable for communicating the identification information related to the second device to the first device via an out-of-band communication. The in-band discovery message including the identification information related to the first device consists of one of section trace (J0) bytes, Data Communication Channel (DCC) control overhead, and General Communication Channel (GCC) control overhead. Optionally, the second device includes a tunable filter and a receiver collectively operable for selectively receiving the in-band discovery message including the identification information related to the first device. The network management system is also operable for populating a topology database with the information related to the first device. The network management system is further operable for communicating one or more of the identification information related to the first device and identification information related to the second device to one or more other devices via one or more out-of-band communications. The identification information related to the first device includes one or more of a contact address, node identification information, node capability information, and link connectivity information. The identification information related to the second device includes one or more of a contact address, node identification information, node capability information, link connectivity information, and an out-of-band discovery message. The first device is further operable for receiving the identification information related to the second device and recognizing the second device as a neighbor device. The network management system is still further operable for populating a topology database with the information related to the second device.

BRIEF DESCRIPTION OF THE DRAWINGS

0013The present invention is illustrated and described herein with reference to the various drawings, in which like reference numbers denote like method steps and/or system components, respectively, and in which:

0014<figref idref="DRAWINGS">FIG. 1</figref> is a schematic diagram illustrating a conventional in-band discovery process that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements;

0015<figref idref="DRAWINGS">FIG. 2</figref> is another schematic diagram illustrating the conventional in-band discovery process that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements;

0016<figref idref="DRAWINGS">FIG. 3</figref> is a further schematic diagram illustrating the conventional in-band discovery process that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements;

0017<figref idref="DRAWINGS">FIG. 4</figref> is a schematic diagram illustrating a conventional out-of-band discovery or verification process, as defined in the IETF specifications;

0018<figref idref="DRAWINGS">FIG. 5</figref> is another schematic diagram illustrating the conventional out-of-band discovery or verification process, as defined in the IETF specifications;

0019<figref idref="DRAWINGS">FIG. 6</figref> is a schematic diagram illustrating one exemplary embodiment of the unidirectional in-band discovery process of the present invention, and specifically a SONET/SDH embodiment;

0020<figref idref="DRAWINGS">FIG. 7</figref> is a schematic diagram illustrating one exemplary embodiment of a filter/receiver assembly that is optionally utilized by the unidirectional in-band discovery process of the present invention;

0021<figref idref="DRAWINGS">FIG. 8</figref> is a schematic diagram illustrating one exemplary embodiment of the out-of-band follow-up process of the present invention, and specifically a SONET/SDH embodiment;

0022<figref idref="DRAWINGS">FIG. 9</figref> is another schematic diagram illustrating the out-of-band follow-up process of the present invention, and specifically the SONET/SDH embodiment; and

0023<figref idref="DRAWINGS">FIG. 10</figref> is a flowchart illustrating one exemplary embodiment of the unidirectional in-band discovery and out-of-band follow-up processes of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

0024Referring to <figref idref="DRAWINGS">FIG. 1</figref>, illustrating a conventional in-band discovery process <b>10</b> that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements, originating point A <b>12</b> and terminating point Z <b>14</b> generate discovery messages <b>16</b>,<b>18</b>, respectively, that are sent over the J0 byte, DCC, GCC, or other control overhead in the connecting link. Intermediate nodes <b>20</b>,<b>22</b>,<b>24</b> that are transparent to this control overhead (i.e., that transport the discovery messages <b>16</b>,<b>18</b> to/from the originating point A <b>12</b> and terminating point Z <b>14</b> transparently) do not participate in the discovery process <b>10</b> and are not automatically discovered by originating point A <b>12</b> and terminating point Z <b>14</b>, nor do they automatically discover that originating point A <b>12</b> and terminating point Z <b>14</b> are neighbors. They may, however, through IP identification, be capable of identifying neighbors at their own layer.

0025Referring to <figref idref="DRAWINGS">FIG. 2</figref>, also illustrating the conventional in-band discovery process that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements, originating point A <b>12</b> and terminating point Z <b>14</b> receive the discovery messages <b>16</b>,<b>18</b> and are thus able to determine that they are neighbors, as well as to ascertain the others' identity and contact address.

0026Referring to <figref idref="DRAWINGS">FIG. 3</figref>, further illustrating the conventional in-band discovery process that is designed to work between peer entities, as defined in the ITU-T standards and OIF implementation agreements, originating point A <b>12</b> and terminating point Z <b>14</b> subsequently exchange messages supporting link capability exchange, still to be defined in the standards and implementation agreements. A bidirectional control path is assumed, either via in-band control overhead or an out-of-band network <b>26</b>,<b>28</b>.

0027Referring to <figref idref="DRAWINGS">FIG. 4</figref>, illustrating a conventional out-of-band discovery or verification process, as defined in the IETF specifications, neighboring devices do not “discover” each others' identity and contact address, but, rather, are pre-provisioned with each others' identity and contact address. They subsequently use this information to exchange messages about each others' link capabilities. For example, originating point A <b>12</b> and terminating point Z <b>14</b> are pre-provisioned with each others' identity and contact address via a network interface <b>30</b> with a network management system <b>32</b>.

0028Referring to <figref idref="DRAWINGS">FIG. 5</figref>, also illustrating the conventional out-of-band discovery or verification process, as defined in the IETF specifications, originating point A <b>12</b> and terminating point Z <b>14</b> subsequently exchange messages supporting link capability exchange, which are designed with the assumption that neighbor identity has already been configured into the end systems. A bidirectional control path is assumed, via an out-of-band network <b>26</b>,<b>28</b>.

0029Referring to <figref idref="DRAWINGS">FIG. 6</figref>, illustrating one exemplary embodiment of the unidirectional in-band discovery process <b>40</b> of the present invention, and specifically a SONET/SDH embodiment, it is assumed that only a one-way in-fiber path is available between device A <b>12</b> and device B <b>20</b>. This renders the discovery process described above (<figref idref="DRAWINGS">FIGS. 1-3</figref>) unusable, as this process requires a two-way in-fiber path for the exchange of discovery messages. However, a combination of a one-way in-fiber discovery message and subsequent out-of-band interaction can be used to perform neighbor discovery. Accordingly, device A <b>12</b> generates a J0 discovery message <b>42</b> containing its identity and device B <b>20</b> (an intermediate Dense Wavelength Division Multiplexing (DWDM) device, for example) monitors J0, thereby identifying device A <b>12</b> and recognizing it as its neighbor.

0030An exemplary discovery message consists of the following format: a 4 byte flag indicating that the message is a discovery message, an address/node ID for the source equipment, and a link or port identifier corresponding to the link endpoint at the source equipment. This is illustrated in Table 1.

0031<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="441pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Exemplary Discovery Message</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="31"><colspec colname="1" colwidth="14pt" align="center" /><colspec colname="2" colwidth="21pt" align="center" /><colspec colname="3" colwidth="14pt" align="center" /><colspec colname="4" colwidth="14pt" align="center" /><colspec colname="5" colwidth="14pt" align="center" /><colspec colname="6" colwidth="14pt" align="center" /><colspec colname="7" colwidth="14pt" align="center" /><colspec colname="8" colwidth="14pt" align="center" /><colspec colname="9" colwidth="14pt" align="center" /><colspec colname="10" colwidth="14pt" align="center" /><colspec colname="11" colwidth="14pt" align="center" /><colspec colname="12" colwidth="14pt" align="center" /><colspec colname="13" colwidth="14pt" align="center" /><colspec colname="14" colwidth="14pt" align="center" /><colspec colname="15" colwidth="14pt" align="center" /><colspec colname="16" colwidth="14pt" align="center" /><colspec colname="17" colwidth="14pt" align="center" /><colspec colname="18" colwidth="14pt" align="center" /><colspec colname="19" colwidth="14pt" align="center" /><colspec colname="20" colwidth="14pt" align="center" /><colspec colname="21" colwidth="14pt" align="center" /><colspec colname="22" colwidth="14pt" align="center" /><colspec colname="23" colwidth="14pt" align="center" /><colspec colname="24" colwidth="14pt" align="center" /><colspec colname="25" colwidth="14pt" align="center" /><colspec colname="26" colwidth="14pt" align="center" /><colspec colname="27" colwidth="14pt" align="center" /><colspec colname="28" colwidth="14pt" align="center" /><colspec colname="29" colwidth="14pt" align="center" /><colspec colname="30" colwidth="14pt" align="center" /><colspec colname="31" colwidth="14pt" align="center" /><tbody valign="top"><row><entry>0</entry><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry>1</entry><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry>2</entry><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry /><entry>3</entry><entry /></row><row><entry>0</entry><entry>1  2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry><entry>2</entry><entry>3</entry><entry>4</entry><entry>5</entry><entry>6</entry><entry>7</entry><entry>8</entry><entry>9</entry><entry>0</entry><entry>1</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49pt" align="center" /><colspec colname="2" colwidth="392pt" align="center" /><tbody valign="top"><row><entry>Flag</entry><entry>Address/Node ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="273pt" align="center" /><colspec colname="2" colwidth="168pt" align="center" /><tbody valign="top"><row><entry>Address/Node ID cont'd</entry><entry>Local Link/Port ID</entry></row><row><entry>Local Link/Port ID cont'd</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0032Referring to <figref idref="DRAWINGS">FIG. 7</figref>, illustrating one exemplary embodiment of a filter/receiver assembly <b>44</b> that is optionally utilized by the unidirectional in-band discovery process of the present invention, the monitoring of J0 or other overhead bytes is only possible if device B <b>20</b> has access to these bytes. This is typically not true of Select Optical Add/Drop Multiplexers (S-OADMs) and Reconfigurable Optical Add/Drop Multiplexers (R-OADMs), which treat received input as a transparent photonic signal. However, it is possible to equip such devices with the ability to “snoop” on an input port, using a receiver <b>46</b> preceded by a tunable filter <b>48</b>. The tunable filter <b>48</b> is used to scan the input port, lock on any signal present, and snoop on the J0 or other overhead bytes that are present in the signal. Because a tunable filter <b>48</b> is used, this can be done for one or multiple signals in a multi-wavelength photonic link between domains. In order to perform such snooping without affecting the transmission of the received signal requires splitting the signal, sending one copy through the filter/receiver assembly <b>44</b>, and adding the other copy to the DWDM signal, as per the normal operation of the S-OADM or R-OADM.

0033Referring to <figref idref="DRAWINGS">FIG. 8</figref>, illustrating one exemplary embodiment of the out-of-band follow-up process <b>50</b> of the present invention, and specifically a SONET/SDH embodiment, the neighbor identity of device A <b>12</b> is passed to the network management system <b>32</b> via a network interface <b>52</b>. At this point, it is possible to stop the discovery process and use the information mined for network management purposes (i.e., to populate the topology database of the network management systems <b>32</b>, etc.). Subsequently, if needed, the network management system <b>32</b> can notify device A <b>12</b> of its neighbor's identity. However, it may also be desirable to continue a distributed process to notify device A <b>12</b> of its neighbor's identity via out-of-band control messaging, thus enabling interactions to, for example, exchange link information and verify link connectivity.

0034Referring to <figref idref="DRAWINGS">FIG. 9</figref>, also illustrating the out-of-band follow-up process <b>50</b> of the present invention, and specifically the SONET/SDH embodiment, an out-of-band discovery message <b>54</b> is sent from device B <b>20</b> to device A <b>12</b> through the control/management network <b>28</b>, given that device B <b>20</b> determines the network address of device A <b>12</b> from the J0 discovery message <b>42</b> (<figref idref="DRAWINGS">FIG. 6</figref>). At this point, originating device A <b>12</b> determines that its physically adjacent neighbor is DWDM device B <b>20</b>. Device A <b>12</b> and device B <b>20</b> can then exchange information about the link that connects them, as well as information about their respective capabilities, using out-of-band messaging.

0035A typical set of control/management network processes operates as follows: both device A <b>12</b> and device B <b>20</b> are connected to the same control/management network <b>28</b>, or to different control/management networks through a router; device A <b>12</b> and device B <b>20</b> each support limited control/management network capabilities, including the knowledge of where to send messages for a given network address (e.g., to a default router for the control/management network <b>28</b>); until device A <b>12</b> and device B <b>20</b> are known to be physically adjacent neighbors, there may be no communication between them using the control/management network <b>28</b>; once device B <b>20</b> detects that device A <b>12</b> is its physically adjacent neighbor, it initiates a control session with device A <b>12</b>, which consists of an initial HELLO message informing device A <b>12</b> of its neighbor B <b>20</b> and subsequent session configuration messages providing details of the control session, such as the frequency of keep-alive messages and alternate addresses that may be used; and device B <b>20</b> and device A <b>12</b> exchange link information, such as the link ID used locally to identify the link in question, the type of switching supported by the sending node (e.g., device A <b>12</b> may indicate SONET/SDH, while device B <b>20</b> may indicate DWDM or wavelength granularity), and any other link characteristics, such as protection mechanisms, supported by the link.

0036Thus, in accordance with the methods and systems of the present invention, equipment generates a discovery message containing its address/node ID and/or other information. Adjacent equipment (e.g., physically adjacent equipment) monitors control overhead bytes (J0 bytes, DCC control overhead, GCC control overhead, etc.) for this message, but does not generate a corresponding response message as called for in the standards/implementation agreements. Rather, it records the address/node ID and/or other information in order to identify its neighbor, and uses an alternative mechanism to either record the adjacency separately (e.g., at a NMS in order to populate or verify its topology database) or communicate an out-of-band control message to the neighbor (e.g., using the received address/node ID as the destination address for the out-of-band control message, which carries its own address/node ID and link information). Such automated population and/or verification of node and/or NMS topology databases improves the speed and accuracy of network resource allocation.

0037This process <b>60</b> is illustrated in the flowchart of <figref idref="DRAWINGS">FIG. 10</figref>. First, J0 monitoring is initiated <b>62</b>. Second, if a J0 discovery message is detected <b>64</b>, the neighbor's node ID and control address are stored <b>66</b>. If not, J0 monitoring continues <b>62</b>. Third, the neighbor's node ID and control address are forwarded to the management system <b>68</b>. Fourth, an out-of-fiber message is either initiated or not 70. If so, the message is formatted using the neighbor's control address <b>72</b>. If not, J0 monitoring continues <b>62</b>. Finally, the message is sent and the process is exited to a new protocol machine <b>74</b>.

0038In this manner, automated discovery is possible for equipment that does not operate at a peer layer and, as a result, cannot perform bidirectional interaction using control overhead bytes. Advantageously, automated discovery is possible with minimal complexity and cost. The methods and systems of the present invention also provide an out-of-band follow-up method using LMP messages (or other protocol messages as defined in the ITU-T standards for link capability exchange) as the format for carrying address/node ID and link information. As described above, a method for the authentication of the received out-of-band control message is desirable in order to ensure that the received out-of-band control message was generated by an actual neighboring node, since out-of-band control messages can presumably be received from any node connected to the same control network.

0039Although the present invention has been illustrated and described herein with reference to preferred embodiments and specific examples thereof, it will be readily apparent to those of ordinary skill in the art that other embodiments and examples may perform similar functions and/or achieve like results. All such equivalent embodiments and examples are within the spirit and scope of the present invention and are intended to be covered by the following claims.