Patent Grant
11012174
The present disclosure relates generally to telecommunication network operations, e.g., in a wavelength division multiplexing (WDM) network, and more particularly to devices, computer-readable media, and methods for verifying that an optical transmit/receive device is correctly installed.
Reconfigurable optical add/drop multiplexers (ROADMs) are increasingly being used in dense-wavelength-division-multiplexed (DWDM) networks. However, tail installation (e.g., installation of transponders and switches) remains subject to manual error. For instance, network personnel or an installation vendor may physically install a transponder and Ethernet switch by connecting these devices to each other, and by connecting the transponder to a ROADM using fiber optic patch cords. In one example, the installer may install the device(s) and fiber(s), and then walk away and assume the physical connectivity is correct. In other cases, the installer may call a network provisioning center to advise that the device(s) and fiber(s) have been installed, and then wait on-site until the network provisioning center verifies connectivity by turning up a circuit, e.g., a wavelength connection, that utilizes the tail. When the circuit is verified, the installation is then deemed to be correct. In turn, the installer may be informed that the installation is complete and is allowed to depart from the installation site. Such verification approach may incur a certain amount of potential down time for the installer.
In one example, the present disclosure describes a device, computer-readable medium, and method for verifying that an optical transmit/receive device is correctly installed. For example, a processing system including at least one processor may activate a first light source of an optical transmit/receive device of a telecommunication network and detect a receiving of a light from the first light source at a port of an optical add/drop multiplexer of the telecommunication network. The processing system may then verify the optical transmit/receive device and the port of the optical add/drop multiplexer match a network provisioning order, when the receiving of the light from the first light source is detected, and generate an indication that the optical transmit/receive device is correctly installed, when the optical transmit/receive device and the port of the optical add/drop multiplexer match the network provisioning order.
In another example, the present disclosure describes a device, computer-readable medium, and method for verifying that an optical transmit/receive device (e.g., a transponder) is correctly installed. For example, a processing system including at least one processor may activate a first light source of a first one of: an optical transponder of a telecommunication network or a network switch of the telecommunication network, and detect a receiving of a light from the first light source at a different one of: the optical transponder or the network switch. The processing system may then verify the optical transponder and the network switch match a network provisioning order, when the receiving of the light from the first light source is detected, and generate an indication that the optical transponder is correctly installed, when the optical transponder and the network switch match the network provisioning order.
The teaching of the present disclosure can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
The present disclosure broadly discloses devices, computer-readable media and methods for verifying that an optical transmit/receive device is correctly installed. Upgrading a telecommunication network to a software defined network (SDN) architecture implies replacing or augmenting existing network elements that may be integrated to perform a single function with new network elements. The replacement technology may comprise a substrate of networking capability, often called network function virtualization infrastructure (NFVI) that is capable of being directed with software and SDN protocols to perform a broad variety of network functions and services.
Advancing SDN architectures also extend to the physical layer, with the introduction of devices such as reconfigurable optical add/drop multiplexers (ROADM) to the optical network, e.g., a wavelength division multiplexing (WDM) network, such as a dense wavelength division multiplexing (DWDM) network. Software-controlled ROADMs manage data traveling over high-capacity fiber optic lines and can automatically detect and adjust bandwidth, move traffic to different lanes, turn off wavelengths for a variety of different reasons, and so forth. SDN components relating to the physical layer (e.g., optical components) may additionally include transceivers, transponders, muxponders, or the like, as well as optical or electro/optical components of switches (e.g., Ethernet switches), layer 3 switches/multi-layer switches, routers (e.g., routers which may also include switching functions), or the like. Similar to other SDN components (e.g., virtual network functions (VNFs) for layer 3 services, application layer services, etc.), these optical components may be turned on and off, and configured and reconfigured at any time. In addition, such components may be installed but remain inactive until an SDN controller determine that the components should be activated for one or more wavelength connections.
A work order to install a new transponder or switch may be generated in response to a customer or network need. For instance, network planning personnel may determine that a new wavelength connection beginning at one location and ending in another may be required. An installer may therefore install the transponder and/or the switch in response to the work order, and notify a network provisioning center. The network provisioning center personnel may then activate the circuit associated with the new transponder and/or switch and determine if end to end traffic is supported. When the circuit is verified, the installation is deemed to be correct and the installer may be informed that the installation is complete. This may provide a verification when the physical installation is performed correctly. However, if there is an error in exchanging high speed bits at the transport layer, the error would not necessarily indicate there is a physical connectivity problem. The issue could be with higher layers or in different geographic/physical portions of the network. For example, there could be a problem at a repeater in the optical network, while the new components may have a correct physical installation. This can lead to wasted efforts in troubleshooting the physical connectivity, which may already be correct, or may fail to isolate an error to a physical connectivity problem relating to the new components, which can lead to wasted troubleshooting efforts elsewhere.
In addition, as stated above, it may no longer be the case that newly installed transponders and/or switches will be immediately activated into a functioning circuit/wavelength connection. For instance, an Ethernet switch and transponder may be “pre-cabled” to each other and/or to a ROADM. Therefore, end-to-end verification may not even be able to provide a positive indication when new transponders and/or switches are correctly installed. In contrast, examples of the present disclosure verify correct physical connections at installation time, regardless of whether and when new transponders and/or switches may be activated.
In one example, once a transponder is physically connected to a ROADM, a light source may be activated via the transponder on the ROADM side. Incoming light may then be detected at one of the ROADM add/drop (shared resource group (SRG)) ports to identify that the transponder is connected to the particular ROADM add/drop port. In one example, when the light is detected, the light source may be turned off from the transponder, and then no light may be detected at the same one of the ROADM add/drop ports. In one example, the activation and deactivation may be repeated at least two times to verify the pairing of the transponder light source and the ROADM add/drop port.
It should be noted that in some examples, a network switch may include an integrated optical transceiver that is connected to an optical transponder with a connection to a ROADM add/drop port. For instance, the network switch may include a small form factor pluggable (SFP) transceiver or the like (e.g., a 4.5 Gb/s transceiver, a 10 Gb/s optical transceiver, etc.). The transceiver may be a “gray light” transceiver or “colored light” transceiver. The external optical transponder may also include the same quality optics on the network switch side. However, on the ROADM/line side, the external optical transponder may have higher quality optics such as a C-form factor pluggable (CFP) optical transceiver or the like (e.g., a 100 Gb/s optical transceiver, and 200 Gb/s optical transceiver, etc.) for metro or long-haul transport network applications. In these types of deployments, examples of the present disclosure may include a turning on (and off) of a light source at either or both of the network switch optical transceiver and the external optical transponder, and then detecting a received light (and/or no light) at the receiver side to identify the connection between the external optical transponder and the integrated optical transceiver of the network switch (e.g., the particular integrated optical transponder and/or a particular slot of the network switch containing the integrated optical transponder).
In one example, the process of light source activation and light detection of the present disclosure may be initiated by an optical transponder (and/or a network switch containing an optical transceiver) when such a device is powered on according to a pre-configuration. In another example, the light source activation and light detection of the present disclosure may be initiated and/or performed remotely, e.g., by an SDN controller via one or more application programming interfaces (APIs) providing management access to and control of the respective device(s).
In one example, the present disclosure relates to a ROADM-based network according to an open standard, such as the Open ROADM Multi-Source Agreement. Unlike ROADMs that are vendor specific and highly proprietary, and which may require custom and static configuration and provisioning, open standard ROADMs and optical plug-ins allow multi-vendor interoperability where various equipment support standardized APIs. Examples of the present disclosure also enable automatic network topology updating by automatic, systematic, and accurate determination of tail connectivity (e.g., between an Ethernet switch and a transponder, and/or between a transponder and a ROADM port) in a ROADM-based network. In one example, network topology changes are automatically discovered and fed to a machine learning-based optical Path Computation Engine (PCE) for provisioning of new service(s), re-optimizing existing one(s), and so forth. For instance, the integrated, self-initiated, and automated connectivity discovery processes of the present disclosure confirm the connection, capture relevant network connectivity and resource information, and verify the readiness and proper operation of the optical resources. These and other aspects of the present disclosure are discussed in greater detail below in connection with the examples of
To aid in understanding the present disclosure,
In one example, the network 105 may be in communication with networks 160 and networks 170. Networks 160 and 170 may comprise wireless networks (e.g., an Institute of Electrical and Electronics Engineers (IEEE) 802.11/Wi-Fi network and the like), a cellular access network (e.g., a Universal Terrestrial Radio Access Network (UTRAN) or an evolved UTRAN (eUTRAN), and the like), a circuit switched network (e.g., a public switched telephone network (PSTN)), a cable network, a digital subscriber line (DSL) network, a metropolitan area network (MAN), an Internet service provider (ISP) network, a peer network, and the like. In one example, the networks 160 and 170 may include different types of networks. In another example, the networks 160 and 170 may be the same type of network. The networks 160 and 170 may be controlled or operated by a same entity as that of network 105 or may be controlled or operated by one or more different entities. In one example, the networks 160 and 170 may comprise separate domains, e.g., separate routing domains as compared to the network 105. In one example, networks 160 and/or networks 170 may represent the Internet in general.
In one example, network 105 may transport traffic to and from user devices 141 and 142. For instance, the traffic may relate to communications such as voice telephone calls, video and other multimedia, text messaging, emails, and so forth between the user devices 141 and 142, or between the user devices 141 and/or 142 and other devices that may be accessible via networks 160 and 170. User devices 141 and 142 may comprise, for example, cellular telephones, smart phones, personal computers, other wireless and wired computing devices, private branch exchanges, customer edge (CE) routers, media terminal adapters, cable boxes, home gateways and/or routers, and so forth.
As stated above, network 105 comprises a WDM network (e.g., a dense wavelength division multiplexing (DWDM) network). Accordingly, in one example, the nodes 131-137 may include optical components, such as ROADMs, and the links between nodes 131-137 may comprise fiber optic cables. For ease of illustration, a portion of the links is specifically labeled as links 120-129. Inset 101 illustrates a portion of the network 105 comprising nodes 136 and 137, and links 125-129. As shown in inset 101, node 136 includes a ROADM 191 coupled to links 125, 126, and 128, a plurality of add/drop ports 194, and a network switch 193 coupled to the ROADM 191 via one of the plurality of add/drop ports 194 and a transponder 192. It should be noted that the network switch 193 may include a transceiver 199 which is coupled to the transponder 192 via a fiber optic patch cord 171. The transponder 192 may include a client side transceiver 174 (which in one example may comprise the same or similar quality optics as the transceiver 199, e.g., an SFP transceiver, a 10 Gb small form factor pluggable (XFP) transceiver, or the like) and a ROADM side/line side transceiver 175 (which may comprise higher quality optics for transmitting and receiving signals over longer distances between nodes of the network 105, e.g., hundreds of kilometers up to 2,000 or more kilometers) coupled to one of the add/drop ports 194 via a fiber optic patch cord 172. In one example, the transceiver 192 may comprise a muxponder that may aggregate several lower bandwidth signals from network switch 193 and/or from one or more other network switches, routers, or other client devices at node 136 into a combined signal for transmission over one of the network links 125, 126, or 128.
Similarly, node 137 includes a ROADM 195 coupled to links 126, 127, and 129, a plurality of add/drop ports 198, and a network switch 197 coupled to ROADM 195 via a patch cord 173 between one of the plurality of add/drop ports 198 and a transponder 196. It should be noted that as illustrated in
It should be noted that in each of nodes 136 and 137, any number of routers, switches, application servers, and the like may be connected to one of the plurality of add/drop ports 194 or plurality of add/drop ports 198, e.g., via additional transponders and/or transceivers. In addition, in other examples, additional components, such as additional ROADMs, may be connected to one of the plurality of add/drop ports 194 or plurality of add/drop ports 198. For instance, in another example, node 137 may include a number of ROADMs, WSSs, and other components that are interconnected to provide a higher degree node. In addition, as referred to herein the terms “switch” and “network switch” may refer to any of a number of similar devices, e.g., including: a layer 2 switch (e.g., an Ethernet switch), a layer 3 switch/multi-layer switch, a router (e.g., a router which may also include switching functions), or the like. It should also be noted that nodes 131-135 may have a same or similar setup as nodes 136 and 137. In addition, in one example, any one or more of components 181-184 may also comprise an optical node with a same or similar setup as nodes 136 and 137.
As further illustrated in
In one example, nodes 131-137 and components 181-184 (and/or the devices therein) may be controlled and managed by SDN controller 155. For instance, in one example, SDN controller 155 is responsible for such functions as provisioning and releasing instantiations of VNFs to perform the functions of routers, switches, and other devices, provisioning routing tables and other operating parameters for the VNFs, and so forth. Thus, various components of network 105 may comprise virtual network functions (VNFs) which may physically comprise hardware executing computer-readable/computer-executable instructions, code, and/or programs to perform various functions. For example, the functions of SDN controller 155 may include the selection of a network function virtualization infrastructure (NFVI) from among various NFVIs available at nodes 131-137 in network 105 to host various devices, such as routers, gateways, switches, route reflectors, firewalls, media servers, and so forth. To illustrate, network switches 193 and 197 may physically reside on host devices that may be configured to be a firewall, a media server, a network switch, a router, and so forth.
In addition, SDN controller 155 may also manage the operations of optical components of the network 105. For instance, SDN controller 155 may configure paths for wavelength connections via the network 105 by configuring and reconfiguring ROADMs at nodes 131-137 and components 181-184. For example, SDN controller 155 may provide instructions to control wavelength selective switches (WSSs) within the ROADMs, as well as transceivers and/or transponders connected to the ROADM add/drop ports. In one example, SDN controller 155 may maintain communications with nodes 131-137 and components 181-184 (and/or the devices therein) via a number of control links 151 which may comprise secure tunnels for signaling communications over an underling IP infrastructure of network 105, e.g., including fibers/links 120-129, etc. In other words, the control links 151 may comprise virtual links multiplexed with transmission traffic and other data traversing network 105 and carried over a shared set of physical links. Alternatively, or in addition, the control links 151 may comprise out-of-band links, e.g., optical or non-optical connections that are different from fibers/links 120-129. In one example, SDN controller 155 may be in communication with node controllers at each node 131-137 (and in one example at components 181-184). For example, node controllers 178 and 179 may be responsible for instantiating and releasing instances of virtual machines at nodes 136 and 137 respectively, and for configuring and reconfiguring operations of associated ROADMs, such as ROADMs 191 and 195, transponders 192 and 196, transceiver 199, network switches 193 and 197, and so on. Thus, in one example, node controllers 178 and 179 may receive instructions for configuring and reconfiguring ROADMs 191 and 195 from SDN controller 155, e.g., via control links 151. Alternatively, or in addition, control links 151 may provide connections between SDN controller 155 and ROADMs 191 and 195, transponders 192 and 196, transceiver 199, and network switches 193 and 197 without the involvement of separate node controllers 178 and 179. In one example, the SDN controller 155 may also comprise a virtual machine operating on one or more NFVI/host devices, or may comprise one or more dedicated devices. For instance, SDN controller 155 may be collocated with one or more VNFs, may be deployed in one or more different host devices, or at a different physical location or locations, and so forth.
In addition, in one example, SDN controller 155 may represent a processing system comprising a plurality of controllers, e.g., a multi-layer SDN controller, one or more federated layer 0/physical layer SDN controllers, and so forth. For instance, a multi-layer SDN controller may be responsible for instantiating, tearing down, configuring, reconfiguring, and/or managing layer 2 and/or layer 3 VNFs (e.g., a network switch, a layer 3 switch and/or a router, etc.), whereas one or more layer 0 SDN controllers may be responsible for activating and deactivating optical networking components, for configuring and reconfiguring the optical networking components (e.g., to provide circuits/wavelength connections between various nodes or to be placed in idle mode), for receiving management and configuration information from such devices, for instructing optical devices at various nodes to engage in testing operations in accordance with the present disclosure, and so forth. In one example, the layer 0 SDN controller(s) may in turn be controlled by the multi-layer SDN controller. For instance, each layer 0 SDN controller may be assigned to nodes/optical components within a portion of the network 105. In addition, these various components may be co-located or distributed among a plurality of different dedicated computing devices or shared computing devices (e.g., NFVI) as described herein.
As mentioned above, examples of the present disclosure may provide operations for verifying that an optical transponder is correctly installed. In the example of
In one example, the SDN controller 155 may access a network provisioning order to identify the correct installation of the network switch 193 and/or transponder 192. In particular, the SDN controller 155 may activate a light source (e.g., a laser) of the transponder 192 facing the ROADM 191 (e.g., transceiver 175) and detect a light at one of the ROADM add/drop ports 194 to identify that the transponder 192 is connected to the particular one of the ROADM add/drop ports 194. In one example, when the light is detected, the light source may be turned off from the transponder 192, and then no light may be detected at the same one of the ROADM add/drop ports 194. In one example, the activation and deactivation may be repeated at least two times to verify the pairing between the transponder 192 and the particular one of the ROADM add/drop ports 194.
In one example, SDN controller 155 may further verify the correct installation of a transponder using a network-based light source (e.g., another laser). For instance, SDN controller 155 may verify the correct installation of transponder 192 by activating (and deactivating) a light source at a different node in the network 105 (e.g., using a test set or a transponder that is not in use), configuring WSS(s) at ROADM(s) in the network node(s) to route the light from the network-based light source to node 136, and configuring ROADM 191 of node 136 to direct the light from the network-based light source to the particular one of the ROADM add/drop ports 194. The transponder 192 may then detect the light (or light/no-light signal) from the one of the ROADM add/drop ports 194 to further verify the pairing between the transponder 192 and the particular one of the ROADM add/drop ports 194.
SDN controller 155 may similarly activate a light source of the transponder 192 facing the network switch 193 (e.g., transceiver 174, which may comprise a laser or light emitting diode (LED) transmitter) and detect a light at the transceiver 199, which may be installed in a particular slot of the network switch 193. In one example, when the light is detected, the light source may be turned off from the transponder 192, and then no light may be detected at the transceiver 199. In one example, the activation and deactivation may be repeated at least two times to verify the pairing between the transponder 192 and the network switch 193 (e.g., the pairing of the transponder 192 with the particular transceiver 199, or the slot in which the transceiver 199 is installed). In one example, the SDN controller 155 may also activate a light source of the network switch 193 (e.g., transceiver 199, which may comprise a laser or LED transmitter) and detect a light at the transponder 192 (e.g., at client-side transceiver 174). When the light is detected, the light source may be turned off from the network switch 193, and then no light may be detected at the transponder 192. In addition, the activation and deactivation may be repeated at least two times to further verify the pairing between the transponder 192 and the network switch 193 (e.g., the pairing of the transponder 192 with the particular transceiver 199, or the slot in which the transceiver 199 is installed).
It should be noted that the foregoing example describes the verification of the connection between transponder 192 and the one of the add/drop ports 194 of ROADM 191 followed by the verification of the connection between the transponder 192 and the network switch 193. However, in another example, the order of these operations may be reversed. Similarly, the foregoing example describes the activation of a light source of transponder 192 and detection at network switch 193, followed by activation of a light source of network switch 193 and detection at transponder 192. However, in another example, the order of these operations may also be reversed. In addition, it should be noted that the correct installation of both the transponder 192 and network switch 193 may be verified at the same time or in connection with the same set of operations, or may be verified at entirely different times and in different circumstances. For instance, the transponder 192 may be installed and connected to the one of the ROADM add/drop ports 194 during a first installation session, while the network switch 193 may be installed and connected to the transponder 192 at another time, which could be hours, days, or weeks later. Thus, in connection with the example methods 200 and 300 below, the verification of correct installation of the transponder 192 may be with respect to the connection to ROADM 191 via patch cord 172, with respect to the connection to network switch 193 via patch cord 171, or both.
It should again be noted that in one example, the activation and deactivation of light sources may be directed by SDN controller 155 via instructions to the respective optical devices, e.g., via control links 151. However, in another example, one or more of the involved optical components (e.g., transponder 192 and/or network switch 193) may be pre-configured to engage in light activation and deactivation and/or light detection operations. For instance, transponder 192 and/or network switch 193 may be pre-configured to activate and deactivate light sources via the respective transceivers in response to being powered on. In addition, either or both of these devices, and/or ROADM 191 may be configured to detect the on/off light pattern (e.g., a simple two cycle on/off pattern, or other low bitrate pattern) and to report the detection to SDN controller 155. Such an example may provide for tail device installation self-discovery where the control links 151 are not separate from links 125-129 and where there is no access of SDN controller 155 to the transponder 192 and network switch 193 except via the ROADM 191.
A similar process may be followed with respect to the installation of additional tail components at other network locations. For example, referring to node 137 that is illustrated in the inset 101 of
In one example, the SDN controller 155 may access a network provisioning order to identify the correct installation of the network switch 197 and/or transponder 196. In particular, the SDN controller 155 may activate a light source of the transponder 196 and detect a light at one of the ROADM add/drop ports 198 to identify that the transponder 196 is connected to the particular one of the ROADM add/drop ports 198. In one example, when the light is detected, the light source may be turned off from the transponder 196, and then no light is detected at the same one of the ROADM add/drop ports 198. In one example, the activation and deactivation may be repeated at least two times to verify the pairing between the transponder 196 and the particular one of the ROADM add/drop ports 198.
In one example, SDN controller 155 may further verify the correct installation of network switch 197 and/or transponder 196 by activating (and deactivating) a light source at a different node in the network 105 (e.g., using a test set or a transponder that is not in use), configuring WSS(s) at ROADM(s) in the network node(s) to route the light from the network-based light source to node 137, and configuring ROADM 195 of node 137 to direct the light from the network-based light source to the particular one of the ROADM add/drop ports 198. The network switch 197 may then detect the light (or light/no-light signal) at transponder 196 from the particular one of the ROADM add/drop ports 198 to further verify the pairing between the transponder 196 and the particular one of the ROADM add/drop ports 198.
As further illustrated in
As illustrated in
In this regard, PCE 150 may store various data in connection with managing path utilizations for telecommunication network tunnels. For instance, PCE 150 may maintain a topology information block (TIB) that includes records for various links/fibers between the nodes 131-137 and components 181-184 in network 105, such as the available wavelengths, the wavelengths assigned/in-use and/or the available/free wavelengths, the paths assigned to respective wavelengths, the fiber lengths, capacities, and ages, the availability of transponders, switches, and/or other infrastructure at various nodes, transponder and/or transceiver performance capabilities of the various nodes, information regarding any protection scheme involving a fiber, and/or any particular wavelengths that may be utilized over the fiber, and so forth. In this regard, the SDN controller 155 may provide information to PCE 150 regarding the statuses of transponders, network switches, and/or ROADMs, and regarding the connections between such devices that the SDN controller 155 may obtain in the course of the performance of operations for verifying that an optical transmit/receive device is correctly installed, as described herein. For instance, example methods 200 and 300 for verifying that an optical transmit/receive device is correctly installed are described in greater detail below.
It should be noted that the system 100 has been simplified. In other words, the system 100 may be implemented in a different form than that illustrated in
In addition, the foregoing includes examples where operations for verifying that an optical transmit/receive device is correctly installed are performed by SDN controller 155, and/or by SDN controller 155 in conjunction with other devices under the control and instruction of SDN controller 155. However, in other, further, and different examples, aspects of verifying that an optical transmit/receive device is correctly installed may include transponders and/or network switches performing one or more operations autonomously, such as a transponder and/or a transceiver activating and deactivating a light source upon being powered on, a ROADM detecting light at a previously inactive add/drop port and reporting the detection of the light to SDN controller 155, and so forth. Thus, these and other modifications of the system 100 are all contemplated within the scope of the present disclosure.
At step 210, the processing system activates a first light source of an optical transmit/receive device of a telecommunication network. In one example, the optical transmit/receive device is coupled to an optical add/drop multiplexer (e.g., a ROADM) of the telecommunication network via a fiber optic patch cord. In one example, the optical transmit/receive device comprises a transceiver integrated into a network switch. In another example, the optical transmit/receive device comprises a transponder coupled to the port of the optical add/drop multiplexer and to a network switch (e.g., via a second fiber optic patch cord). In one example, the processing system includes the optical transmit/receive device and the first light source is activated by the optical transmit/receive device in response to the optical transmit/receive device (and/or a network switch containing the optical transmit/receive device) being powered on. In another example, the first light source is activated by the processing system via a remote command in response to a notification that the optical transmit/receive device (e.g., a transponder, or a transceiver and/or a network switch containing the transceiver) is installed. For instance, the processing system may comprise an SDN controller of the telecommunication network. The remote command may be in accordance with a remote access API, e.g., using YANG (Yet Another Next Generation) data modeling language via the NETCONF network configuration protocol.
At step 215, the processing system detects a receiving of light from the first light source at a port of the optical add/drop multiplexer (e.g., a ROADM) of the telecommunication network. For instance, the optical add/drop multiplexer may be configured to detect the presence or absence of light at particular add/drop ports, and may further be configured to report the detection of the presence or absence of light to the processing system via a remote API. For example, the processing system may comprise an SDN controller with one or more control links to the optical add/drop multiplexer. In one example, the optical add/drop multiplexer may report the detecting of the receiving of light from the first light source automatically, or may report in response to a query from the processing system.
At optional step 220, the processing system may activate a second light source at a first one of the optical transmit/receive device or the network switch, e.g., in an example where the optical transmit/receive device comprises a transponder. In one example, the second light source may also be activated via a remote command. In another example, the second light source may be part of a client side transceiver of the optical transmit/receive device and the second light source may be activated by the optical transmit/receive device in response to the optical transmit/receive device being powered on. It should be noted that the various light sources described in the method 200 may comprise lasers or LEDs. For instance, between an optical transceiver and the optical add/drop multiplexer the light source may comprise a laser for generating light signals for WDM aggregation in metro or transport network applications. However, in one example, a light source of a transceiver for intra-office communications between a transponder and network switch could be either a laser or LED.
At optional step 225, the processing system may detect a receiving of light from the second light source at a different one of the optical transmit/receive device or the network switch. For instance, the optical transmit/receive device or the network switch may be configured to detect the presence or absence of light at a receive component of a transceiver, and may also be configured to report the detection of the presence or absence of light to the processing system via a remote API. For example, the processing system may comprise an SDN controller with one or more control links to the optical transmit/receive device or the network switch. In one example, the optical transmit/receive device or the network switch may report the detecting of the receiving of light from the second light source automatically, or may report in response to a query from the processing system.
At optional step 230, the processing system may activate a third light source at the different one of the optical transmit/receive device or the network switch. Activation of the third light source at optional step 230 may be automatic (e.g., when the optical transmit/receive device comprises a transponder and the third light source is a component of the transponder), or may be via a remote command (when third light source is of either the optical transmit/receive device or the network switch).
At optional step 235, the processing system may detect a receiving of a light from the third light source at the first one of the optical transmit/receive device or the network switch. For example, as mentioned above, the optical transmit/receive device or the network switch may report the detecting of the receiving of a light from the second light source automatically, or may report in response to a query from the processing system.
At optional step 240, the processing system may route light from a fourth light source of the telecommunication network to the port of the optical add/drop multiplexer. For instance, the fourth light source may comprise a network test set or an unassigned transponder at another node of the telecommunication network that may also be activated via a remote command. In one example, step 240 may include the processing system activating (and deactivating) the fourth light source at a different node in the telecommunication network, configuring WSS(s) at optical add/drop multiplexers in the network node(s) to route the light from the fourth light source to the node containing the optical transmit/receive device, and configuring the optical add/drop multiplexer at the node to direct the light from the fourth light source to the particular one of the add/drop ports.
At optional step 245, the processing system may detect a receiving of a light from the fourth light source at the optical transmit/receive device. In one example, the optical transmit/receive device may report the detecting of the receiving of the light from the fourth light source automatically, or may report in response to a query from the processing system.
At step 250, the processing system verifies that the optical transmit/receive device and the port of the optical add/drop multiplexer match a network provisioning order, in response to detecting the receiving of the light from the first light source. In one example, the processing system verifies that the optical transmit/receive device and the port of the optical add/drop multiplexer match the network provisioning order, when both the receiving of the light from the first light source is detected and the receiving of the light from the fourth light source is detected (e.g., when optional steps 240 and 245 are performed). In one example, the verifying further comprises: verifying the optical transmit/receive device and the network switch match the network provisioning order, when the receiving of the light from the second light source is detected (e.g., when optional steps 220 and 225 are performed). In one example, the verifying further comprises verifying that the optical transmit/receive device and the network switch match the network provisioning order, when both the receiving of the light from the second light source is detected and the receiving of the light from the third light source is detected (e.g., when optional steps 220-235 are performed).
The network provisioning order may specify a particular transceiver or transceiver slot of a network switch to connect to the add/drop port, or may more broadly indicate that it is acceptable to connect any free transceiver in any slot to the add/drop port (e.g., where the network switch may comprise a plurality of the same type of transceivers). In another example, the network provisioning order may specify a particular transponder to connect to the add/drop port. In addition, the network provisioning order may specify a particular add/drop port, or may more broadly indicate that it is acceptable to connect the transceiver and/or transponder to any free add/drop port. For instance, the processing system may determine the connectivity based upon the reporting from the respective devices of the receiving of the light from the first light source, the light from the second light source, etc.
At step 255, the processing system generates an indication that the optical transmit/receive device is correctly installed, when the optical transmit/receive device and the port of the optical add/drop multiplexer match the network provisioning order. The indication may comprise at least one of: an entry in a network provisioning system, a visual indication or an audio indication via at least one of the optical transmit/receive device, the optical add/drop multiplexer, a network switch associated with the optical transmit/receive device, or a device of a network technician. In one example, the generating of the indication comprises generating the indication that the optical transmit/receive device is correctly installed when both (1) the optical transmit/receive device and the port of the optical add/drop multiplexer match the network provisioning order and (2) the optical transmit/receive device and the network switch match the network provisioning order (e.g., when steps 220 and 225, and/or steps 220-235 are performed).
Following step 255 the method 200 proceeds to step 295. At step 295, the method 200 ends.
It should be noted that the method 200 may be expanded to include additional steps or may be modified to include additional operations with respect to the steps outlined above. For instance, in one example, the method 200 may be repeated for the installation of various additional optical transmit/receive devices at the same or different nodes in the telecommunication network. In one example, the method 200 may further include establishing a wavelength connection through the telecommunication network that includes the optical transmit/receive device. In addition, in one example, the method 200 may further include provisioning or reconfiguring VNFs and/or NFVI within the network to utilize the wavelength connection. Thus, these and other modifications are all contemplated within the scope of the present disclosure.
At step 310, the processing system activates a first light source of a first one of an optical transponder of a telecommunication network or a network switch of the telecommunication network. In one example, the optical transponder is coupled to the network switch via a fiber optic patch cord. In one example, the first light source is activated by the processing system via a remote command in response to a notification that the optical transponder is installed. For instance, the processing system may comprise an SDN controller of the telecommunication network. The remote command may be in accordance with a remote access API, e.g., using YANG via NETCONF. In an example where the light source comprises a light source of the optical transponder, the processing system may include the optical transponder, and the first light source may be activated by the optical transponder in response to the optical transponder being powered on. In one example, step 310 may comprise the same or similar operations as described above in connection with step 220 and/or step 230 of the example method 200.
At step 315, the processing system detects a receiving of a light from the first light source at a different one of the optical transponder or the network switch. For instance, the optical transponder or the network switch may be configured to detect the presence or absence of a light at a receive component of a transceiver and may further be configured to report the detection of the presence or absence of light to the processing system via a remote API. For example, the processing system may comprise an SDN controller with one or more control links to the optical transponder or the network switch. In one example, the optical transponder or the network switch may report the detecting of the receiving of a light from the first light source automatically, or may report in response to a query from the processing system. In one example, step 315 may comprise the same or similar operations as described above in connection with step 225 and/or step 235 of the example method 200.
At optional step 320, the processing system may activate a second light source at the different one of the optical transponder or the network switch. In one example, the second light source may also be activated via a remote command. In another example, the second light source may be activated by the optical transponder or the network switch in response to the optical transponder or the network switch being powered on. In one example, step 320 may comprise the same or similar operations as described above in connection with step 220 and/or step 230 of the example method 200.
At optional step 325, the processing system may detect a receiving of a light from the second light source at the first one of the optical transponder or the network switch. For instance, the optical transponder or the network switch may be configured to detect the presence or absence of a light at a receive component of a transceiver and may further be configured to report the detection of the presence or absence of light to the processing system via a remote API. For example, the processing system may comprise an SDN controller with one or more control links to the optical transponder or the network switch. In one example, the optical transponder or the network switch may report the detecting of the receiving of a light from the first light source automatically, or may report in response to a query from the processing system. In one example, step 325 may comprise the same or similar operations as described above in connection with step 225 and/or step 235 of the example method 200.
At optional step 330, the processing system may activate a third light source at the optical transponder. For instance, the third light source may be facing an optical add/drop multiplexer (e.g., a ROADM) of the telecommunication network. In one example, the third light source may also be activated via a remote command. In another example, the third light source may be activated by the optical transponder in response to the optical transponder being powered on. It should be noted that the various light sources described in the method 300 may comprise lasers or LEDs. For instance, between the optical transceiver and the optical add/drop multiplexer, the third light source may comprise a laser for generating light signals for WDM aggregation in metro or transport network applications. However, in one example, the first and second light sources for intra-office communications between the transponder and the network switch could be either lasers or LEDs. In one example, step 330 may comprise the same or similar operations as described above in connection with step 210 of the example method 200.
At optional step 335, the processing system may detect a receiving of a light from the third light source at a port of an optical add/drop multiplexer of the telecommunication network. For instance, the optical add/drop multiplexer may be configured to detect the presence or absence of a light at particular add/drop ports, and may further be configured to report the detection of the presence or absence of light to the processing system via a remote API. For example, the processing system may comprise an SDN controller with one or more control links to the optical add/drop multiplexer. In one example, the optical add/drop multiplexer may report the detecting of the receiving of a light from the third light source automatically, or may report in response to a query from the processing system. In one example, step 335 may comprise similar operations as described above in connection with step 215 of the example method 200.
At optional step 340, the processing system may route a light from a fourth light source of the telecommunication network to the port of the optical add/drop multiplexer. For instance, the fourth light source may comprise a network test set or an unassigned transponder at another node of the telecommunication network that may also be activated via a remote command. In one example, step 340 may comprise similar operations as described above in connection with step 240 of the example method 200.
At optional step 345, the processing system may detect a receiving of a light from the fourth light source at the optical transponder. In one example, the optical transponder may report the detecting of the receiving of a light from the fourth light source automatically, or may report in response to a query from the processing system. In one example, step 345 may comprise similar operations as described above in connection with step 245 of the example method 200.
At step 350, the processing system verifies that the optical transponder and the network switch match a network provisioning order, in response to detecting the receiving of the light from the first light source. In one example, the verifying comprises verifying that the optical transponder and the network switch match the network provisioning order, when both the receiving of the light from the first light source is detected and the receiving of the light from the second light source is detected (e.g., when optional steps 320 and 325 are performed). In one example, the verifying further comprises verifying the optical transponder and the port of the optical add/drop multiplexer match the network provisioning order, when the receiving of the light from the third light source is detected (e.g., when optional steps 330 and 335 are performed). In one example, the verifying comprises verifying that the optical transponder and the port of the optical add/drop multiplexer match the network provisioning order, when both the receiving of the light from the third light source is detected and the receiving of the light from the fourth light source is detected (e.g., when optional steps 330-345 are performed). In one example, step 350 may comprise similar operations as described above in connection with step 255 of the example method 200.
At step 355, the processing system generates an indication that the optical transponder is correctly installed, when the optical transponder and the network switch match the network provisioning order. The indication may comprise at least one of: an entry in a network provisioning system, a visual indication or an audio indication via at least one of the optical transceiver, the network switch, an optical add/drop multiplexer associated with the optical transceiver, or a device of a network technician. In one example, the processing system generates the indication that the optical transponder is correctly installed when both (1) the optical transponder and the network switch match the network provisioning order and (2) the optical transponder and the port of the optical add/drop multiplexer match the network provisioning order (e.g., when steps 320 and 325, and/or steps 320-335 are performed). In one example, step 355 may comprise similar operations as described above in connection with step 255 of the example method 200.
Following step 355 the method 300 proceeds to step 395. At step 395, the method 300 ends.
It should be noted that the method 300 may be expanded to include additional steps or may be modified to include additional operations with respect to the steps outlined above. For instance, in one example, the method 300 may be repeated for the installation of various additional optical transponders at the same or different nodes in the telecommunication network. In one example, the method 300 may further include establishing a wavelength connection through the telecommunication network that includes the optical transponder. In addition, in one example, the method 300 may further include provisioning or reconfiguring VNFs and/or NFVI within the network to utilize the wavelength connection. Thus, these and other modifications are all contemplated within the scope of the present disclosure.
In addition, although not specifically specified, one or more steps, functions or operations of the method 200 or the method 300 may include a storing, displaying, and/or outputting step as required for a particular application. In other words, any data, records, fields, and/or intermediate results discussed in the example method 200 or method 300 can be stored, displayed, and/or outputted to another device as required for a particular application. Furthermore, steps or blocks in
Furthermore, one or more hardware processors can be utilized in supporting a virtualized or shared computing environment. The virtualized computing environment may support one or more virtual machines representing computers, servers, or other computing devices. In such virtualized virtual machines, hardware components such as hardware processors and computer-readable storage devices may be virtualized or logically represented. The hardware processor 402 can also be configured or programmed to cause other devices to perform one or more operations as discussed above. In other words, the hardware processor 402 may serve the function of a central controller directing other devices to perform the one or more operations as discussed above.
It should be noted that the present disclosure can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a programmable gate array (PGA) including a Field PGA, or a state machine deployed on a hardware device, a computing device or any other hardware equivalents, e.g., computer readable instructions pertaining to the methods discussed above can be used to configure a hardware processor to perform the steps, functions and/or operations of the above disclosed method 200 and/or method 300. In one example, instructions and data for the present module or process 405 for verifying that an optical transmit/receive device is correctly installed (e.g., a software program comprising computer-executable instructions) can be loaded into memory 404 and executed by hardware processor element 402 to implement the steps, functions, or operations as discussed above in connection with the illustrative method 200 and/or method 300. Furthermore, when a hardware processor executes instructions to perform “operations,” this could include the hardware processor performing the operations directly and/or facilitating, directing, or cooperating with another hardware device or component (e.g., a co-processor and the like) to perform the operations.
The processor executing the computer readable or software instructions relating to the above described method(s) can be perceived as a programmed processor or a specialized processor. As such, the present module 405 for verifying that an optical transmit/receive device is correctly installed (including associated data structures) of the present disclosure can be stored on a tangible or physical (broadly non-transitory) computer-readable storage device or medium, e.g., volatile memory, non-volatile memory, ROM memory, RAM memory, magnetic or optical drive, device or diskette, and the like. Furthermore, a “tangible” computer-readable storage device or medium comprises a physical device, a hardware device, or a device that is discernible by the touch. More specifically, the computer-readable storage device may comprise any physical devices that provide the ability to store information such as data and/or instructions to be accessed by a processor or a computing device such as a computer or an application server.
While various examples have been described above, it should be understood that they have been presented by way of illustration only, and not a limitation. Thus, the breadth and scope of any aspect of the present disclosure should not be limited by any of the above-described examples, but should be defined only in accordance with the following claims and their equivalents.
This application is a continuation of U.S. patent application Ser. No. 16/047,798, filed on Jul. 27, 2018, now U.S. Pat. No. 10,608,774, which is herein incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5353339 | Scobee | Oct 1994 | A |
| 6005696 | Joline et al. | Dec 1999 | A |
| 6108113 | Fee | Aug 2000 | A |
| 6862380 | Chaudhuri | Mar 2005 | B2 |
| 6980736 | Fee | Dec 2005 | B1 |
| 7603033 | Lumetta et al. | Oct 2009 | B1 |
| 7711267 | Wellbrock et al. | May 2010 | B2 |
| 8180216 | Xia et al. | May 2012 | B2 |
| 8509621 | Boertjes et al. | Aug 2013 | B2 |
| 8619246 | Hisamoto | Dec 2013 | B2 |
| 9432113 | Oi et al. | Aug 2016 | B2 |
| 9628340 | Blair | Apr 2017 | B2 |
| 9680569 | Archambault et al. | Jun 2017 | B2 |
| 9692544 | Wellbrock et al. | Jun 2017 | B2 |
| 9698902 | Nakamura et al. | Jul 2017 | B2 |
| 9742500 | Kachita et al. | Aug 2017 | B2 |
| 9800472 | Spock et al. | Oct 2017 | B2 |
| 9806973 | Htay et al. | Oct 2017 | B2 |
| 9882634 | Al Sayeed et al. | Jan 2018 | B1 |
| 9887774 | Huang et al. | Feb 2018 | B2 |
| 9900089 | Yuki et al. | Feb 2018 | B2 |
| 10009671 | Younce et al. | Jun 2018 | B2 |
| 10015057 | Djukie et al. | Jul 2018 | B2 |
| 10097303 | Papakos et al. | Oct 2018 | B2 |
| 20020003639 | Arecco et al. | Jan 2002 | A1 |
| 20020041409 | Laham | Apr 2002 | A1 |
| 20020149812 | Hong et al. | Oct 2002 | A1 |
| 20020159113 | Tokunaga | Oct 2002 | A1 |
| 20040096216 | Ito | May 2004 | A1 |
| 20040165888 | Gerstel | Aug 2004 | A1 |
| 20040175171 | Kokkinos | Sep 2004 | A1 |
| 20040223759 | Fee | Nov 2004 | A1 |
| 20060153070 | DelRegno et al. | Jul 2006 | A1 |
| 20080232760 | Xia | Sep 2008 | A1 |
| 20090067836 | Liu | Mar 2009 | A1 |
| 20090154918 | Hinderthuer et al. | Jun 2009 | A1 |
| 20090324240 | Ishiguro | Dec 2009 | A1 |
| 20100253936 | Xia et al. | Oct 2010 | A1 |
| 20100266275 | Xia et al. | Oct 2010 | A1 |
| 20100272431 | Chen | Oct 2010 | A1 |
| 20100290785 | Hinderthur et al. | Nov 2010 | A1 |
| 20110085801 | Palacharia | Apr 2011 | A1 |
| 20110142439 | Chen et al. | Jun 2011 | A1 |
| 20110142440 | Xia et al. | Jun 2011 | A1 |
| 20110200324 | Boertjes et al. | Aug 2011 | A1 |
| 20110243558 | Iizawa et al. | Oct 2011 | A1 |
| 20120042213 | Zimmerman | Feb 2012 | A1 |
| 20120224170 | Hisamoto | Sep 2012 | A1 |
| 20120294613 | Hood | Nov 2012 | A1 |
| 20120301134 | Davari et al. | Nov 2012 | A1 |
| 20120301137 | Sakamoto | Nov 2012 | A1 |
| 20120321296 | Wellbrock et al. | Dec 2012 | A1 |
| 20130195462 | Ghioni et al. | Aug 2013 | A1 |
| 20130259474 | Ji et al. | Oct 2013 | A1 |
| 20130294770 | Hino et al. | Nov 2013 | A1 |
| 20130315579 | Xia et al. | Nov 2013 | A1 |
| 20140112658 | Hurley et al. | Apr 2014 | A1 |
| 20140355981 | Miyazaki | Dec 2014 | A1 |
| 20150086192 | Sakamoto | Mar 2015 | A1 |
| 20150104170 | Xia | Apr 2015 | A1 |
| 20150208146 | Younce et al. | Jul 2015 | A1 |
| 20160315701 | Yuki et al. | Oct 2016 | A1 |
| 20170054508 | Kobayashi et al. | Feb 2017 | A1 |
| 20170104530 | Nagata et al. | Apr 2017 | A1 |
| 20170222747 | Ban et al. | Aug 2017 | A1 |
| 20180175962 | Magri et al. | Jun 2018 | A1 |
| 20180295130 | Younce et al. | Oct 2018 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20200228226 A1 | Jul 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16047798 | Jul 2018 | US |
| Child | 16834352 | US |
