Patent Application
20240413901
Embodiments presented in this disclosure generally relate to optical fiber communication networks. More specifically, embodiments disclosed herein provide for detection of reversed fibers at an optical transceiver and implementing a crossover correction scheme to enable an optical connection at the optical transceiver.
Optical fiber networks provide increased communication speeds and throughput and are increasing used in a variety of applications. For example, optical fiber networks are used to provide both local network connections (e.g., small scale networks, onsite connections at data centers, etc.) and larger scale networks (e.g., enterprise networks, Internet service provider (ISP) networks, etc.). In each of these examples, communication is enabled over optical fibers which are connected between network devices. These network devices include optical transceivers which transmit and receive optical signals (i.e. light) over the optical fibers and transform the optical signals in order to be handled by the connected network device.
In many cases, these optical fiber networks are manually built and connected. For example, a person manually connects fibers between the network devices. Due to the scale of both the size of optical fiber networks and the potential distance between connected devices, various errors can occur during the manual phase of constructing and connecting the optical fiber networks. For example, swapped fibers which cause mismatches of polarity between receive (Rx) and transmit (Tx) fibers connected to optical transceivers is quite common. These mismatches are typically corrected via manual intervention from network technicians, such as swapping the Rx and Tx fibers to the correct polarity to establish network connectivity. While these manual interventions are seemingly small, these mismatches can cause significant overhead cost in establishing optical fiber networks.
For example, several steps may be involved including troubleshooting why the link is down, where the swapped fibers are one of many potential errors causing the lack of network connection. Additionally, since manual intervention is currently the only solution to a polarity mismatch, a technician may need to travel to the physical location of the swapped fibers to correct the error (increasing time and overhead costs to the network). Improved solutions for detecting and correcting a polarity mismatch remain a challenge.
So that the manner in which the above-recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate typical embodiments and are therefore not to be considered limiting; other equally effective embodiments are contemplated.
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one embodiment may be beneficially used in other embodiments without specific recitation.
A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions. One general aspect includes a method. The method includes determining receive (Rx) optical signals for an optical connection are not detected in a Rx path in an optical transceiver, determining whether crossover Rx optical signals are detected at a light sensor in a transmit (Tx) path in the optical transceiver, and upon detecting the crossover Rx optical signals in the Tx path: implementing a crossover correction scheme in the optical transceiver to enable the optical connection. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes an optical transceiver. The optical transceiver includes a processor, and a memory may include instructions which, when executed on the processor, performs an operation. The operation may include: determining receive (Rx) optical signals for an optical connection are not detected in a Rx path in the optical transceiver, determining whether crossover Rx optical signals are detected at a light sensor in a transmit (Tx) path in the optical transceiver, and upon detecting the crossover Rx optical signals in the Tx path: implementing a crossover correction scheme in the optical transceiver to enable the optical connection. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes an optical transceiver. The optical transceiver also includes a receive (Rx) path; a transmit (Tx) path; a light sensor in the Tx path; and control logic configured to perform an operation. The operation may include: determining Rx optical signals for an optical connection are not detected in the Rx path; determining whether crossover Rx optical signals are detected at the light sensor in the tx path, and upon detecting the crossover Rx optical signals in the Rx path: implementing a crossover correction scheme in the optical transceiver to enable the optical connection. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
As described above, optical fiber networks are utilized in many different types of communication networks including small and large scale implementations. A common error that these optical fiber networks experience is a polarity mismatch at optical transceivers in network devices. This type of error commonly occurs in several different type of network situations. For example, in new optical network installations, technicians may pull fiber optic cables and plug the pulled fiber optic cables into a port (e.g., an optical transceiver) without fully testing the pulled cable and port. For example, a port may be pre-wired and not immediately needed for network communications as the physical fiber network is built out or is not yet needed due to networking capacity being sufficient at the time of installation. Additionally, fiber infrastructure in older facilities may include a difference in wiring codes/standards among various optical connections, which may lead to a reversal of Tx and Rx fibers. In another example, lab or testing environments may use unpaired or single fibers to connect components together, which leads to frequent erroneous connections.
The optical transceivers and methods described herein provide for improved detection and correction of a polarity mismatch/swapped fiber without requiring manual intervention. This improved detection and correction includes determining receive (Rx) optical signals for an optical connection are not detected in a Rx path in an optical transceiver and, upon detecting the crossover Rx optical signals in the Tx path, implementing a crossover correction scheme in the optical transceiver to enable the optical connection, such as the optical connections shown in more detail in relation to
In some examples, as the optical fiber network 100 is constructed/installed, a technician connects the TRXs together by providing or pulling optical fibers between the TRXs. For example, a fiber optic cable 135, including fibers 136 and 137, is connected between the TRX 130 and TRX 140. A fiber optic cable 115, including fibers 116 and 117, is connected between the TRX 110 and TRX 120. While shown as paired cables, the fibers may be individual fibers or other combination fibers in a multi-fiber cable. In these case of a non-reversed installation, the optical transceivers transmit optical signals over the fibers to the respective peer transceivers via transmit Tx paths 112, 122, 132, and 142. The optical transceivers also receive optical signals via Rx paths 114, 124, 134, and 144.
For example, in the optical connection 145 between TRX 130 and TRX 140, the Tx path 132 is connected to the Rx path 144 via the fiber 136. The Tx path 142 is connected to the Rx path 134 via the fiber 137. In this example, the fibers 136 and 137 are not crossed/swapped and provide correct signal polarity between the TRX 130 and the TRX 140 such that the optical connection 145 is enabled as shown in
As described above, in some cases, the fibers between various transceivers may be erroneously reversed, switched, crossed, etc. during installation/connection. For example, an installer may reverse the fiber optic cable 115 such that the fibers 116 and 117 are connected to wrong signal channels or paths in the optical transceivers. For example, the fiber 117 is connected between the Tx path 112 and Tx path 122. The fiber 116 is connected between the Rx path 124 and the Rx path 114. In this example, optical connection 125 is not enabled since the TRX 110 and TRX 120 cannot communicate via normally transmitted optical signals. For example, neither transceiver receives signals via respective Rx paths 114 and 124. In some examples, the TRX 110 provides reversed fiber detection and correction as described in more detail in relation to
The TRX 110 also includes a coupling interface 230. In some examples, the coupling interface 230 is a general coupling interface between a fiber connection and internal components of the TRX 110. The coupling interface 230 may also include a 2×2 optical switch (or other type of optical switch) which performs the various crossover and other functions described herein. The TRX 110 also includes laser control module 220 and a light source 225 (e.g., a laser diode). In some examples, the functions of the TRX 110, including the operations of the transmitter 212, receiver 214, coupling interface 230, laser control module 220, light sensor, and photodiode 240, are controlled by a micro-controller 210. The reversed fiber detection and correction operations of the micro-controller 210 are described in more detail in relation to the methods of
Method 400 of
In another example, the photodiode 240 does not detect any optical signals in the Rx path 114. In this example, method 400 proceeds to block 410 where the TRX 110 waits for a given time to allow for boot up or other connection processes to be performed in the connection. For example, the wait at the block 410 allows for a peer device such as the TRX 120 to boot up and attempt to transmit Tx optical signals to the TRX 110 or implement a crossover correction if one is present in the network connection. The duration of the pause may be governed by various parameters on the TRX 110 to prevent a potential race condition or correction loop between the TRX 110 and the TRX 120.
At block 415, at a recheck time, the TRX 110 rechecks the Rx path for the Rx optical signals. For example, when the photodiode 240 detects RX optical signals at the recheck time, method 400 proceeds to block 420 and the TRX 110 proceeds with transceiver operations for the optical connection. This may indicate that the connection is normal and/or may indicate that the peer transceiver has provided crossover correction. In another example, where Rx signals are not detected at the recheck time, method 400 proceeds to block 425.
At block 425, the TRX 110 determines crossover capabilities of a coupling interface of the optical transceiver. For example, the TRX 110 determines whether the coupling interface 230 is capable of switching signals between the fibers 117 and 116 and the Tx path 112 and Rx path 114. For example, the coupling interface 230 may include a 2×2 optical switch, which enables the crossover switching. In an example where the interface 230 is crossover enabled, the method 400 proceeds to block 430. At block 430, the TRX 110 determines whether crossover Rx optical signals are detected at a light sensor in a Tx path in the optical transceiver. For example, the TRX 110 determines whether the light sensor 245 detects signals received from the interface 230. In some examples, the TRX 110 may stop transmission of Tx optical signals in the Tx path (e.g., block light from the light source 225) and check the light sensor for the crossover Rx optical signals once the light source 225 is blocked. In another example, the light source is not blocked and the light sensor 245 detects Rx signals while the transmitter 212 operates and emits Tx signals.
In one example, the TRX 110 may not detect any Rx signals in the Tx path. In some examples, the lack of Rx signals in the signal path may indicate both reversed/swapped fibers and a fiber connection issue as shown in
With reference to
In an example where the TRX 120 is crossover enabled, method 500 proceeds to block 510 where the TRX 110 determines whether a fallback condition is present in the optical connection. For example, if the fibers 116 and 117 are swapped and one of the fibers is not fully connected as shown in
Returning back to block 520, the TRX 110 implements the crossover correction scheme by negotiating an alternating transmission scheme for communication over a single fiber between the peer optical transceiver and the optical transceiver with the peer optical transceiver. At block 525, the TRX 110 alternates transmission of Tx optical signals and reception of Rx optical signals over the single fiber, according to the alternating transmission scheme at block 525. In this example, the coupling interface 230 switches (as needed) the Tx signals and Rx signals to transmit over the single fiber according to the alternating transmission scheme. In some examples, upon enabling the fallback crossover scheme according to method 500 the TRX 110 proceeds to block 455 of method 400.
Returning back to block 430 of
At block 440, the TRX 110 switches, at the coupling interface, first signals received from a peer optical transceiver via a first fiber connection to the Rx path in the optical transceiver. For example, the TRX 110 switches Rx signals received via the fiber 117 to the Rx path 114 at the coupling interface 230.
At block 445, the TRX 110 switches, at the coupling interface, Tx optical signals transmitted from the optical transceiver to the peer optical transceiver from the Tx path in the optical transceiver to a second fiber connection to the peer optical transceiver. For example, the TRX 110 switches Tx signals from the Tx path 112 to the fiber 116 at the coupling interface 230.
At block 450, the TRX 110, upon implementation of the crossover correction scheme at blocks 440 and 445, verifies Rx optical signals are detected in the Rx path. For example, determines whether the Rx signals are detected in the Rx path. For example, when the photodiode 240 detects Rx signals at block 450, the fibers are in the arrangement shown in
In an example where the photodiode 240 does not detect any Rx optical signals at block 450, the fibers may be in the arrangement shown in
Returning back to block 425, in an example where the interface 230 is not crossover capable, the TRX 110 functions as a crossover detection device or detection only device and method 400 proceeds to block 460. At block 460, the TRX 110 determines whether crossover Rx optical signals are detected at a light sensor in a Tx path in the optical transceiver. For example, the TRX 110 determines whether the light sensor 245 detects signals in the Tx path. In an example where the light sensor 245 does not detect Rx signals at block 460, the TRX 110 is not capable of providing a crossover correction and the method 400 proceeds to block 465. At block 465, the TRX generates a notification for the optical connection indicating the potential Tx/Rx mismatch and proceeds back to block 405. In some examples, multiple processions through the block 465 may signal a mismatch in the connection and that no connection is possible between the TRX 110 and a peer device without manual intervention.
In an example where the light sensor 245 detects Rx signals at block 460, method 400 proceeds to block 470. At block 470, the TRX 110 negotiates or otherwise determines an alternating transmission scheme with the peer optical transceiver and alternates, at the optical transceiver, transmission of Tx optical signals and reception of Rx optical signals according to the alternating transmission scheme at block 475. In some examples, during negotiation or determination of the scheme, the TRX 110 and TRX 120 communicate via a different network connection (e.g., the optical connection 145) in the optical fiber network 100 or other network connection outside of the optical fiber network 100 to determine an alternating transmission scheme in order to use the fiber 117 in a single fiber communication scheme.
In this example, the TRX 110 transmits Tx signals from the Tx path 112 during a Tx time according to the transmission scheme. The TRX 110 also receives Rx signals in the Tx path 112 during a Rx time according to the transmission scheme. In some examples, the light sensor 245 functions as a photodiode and the micro-controller 210 provides the Rx signals to component 214a (e.g., a TIA) as electric signals from the light sensor 245. The single fiber communication scheme allows for a network connection to be enabled over optical connection 125 at a lower throughput than if both fibers were connected properly. While the optical connection 125 is not optimized in this condition, enabling the connection in the non-optimized scheme allows for network connectivity during a time waiting for a technician to manually swap the reversed fibers or repair a broken or disconnected fiber in the optical connection.
From block 475, method 400 proceeds to block 455 where the TRX 110 generates a crossover notification indicating a crossover condition in the optical connection. In some examples, generating the crossover notification includes determining a physical correction type for the crossover correction scheme and providing the physical correction type on a user interface (UI) associated with the optical transceiver. For example,
In examples with reversed fibers or crossover conditions, the UI 600 will indicate additional information to aid a technician in manually fixing the problem. For example, when the TRX 110 is crossover enabled and successfully switches signals as described in relation to block 440-450, the UI 600 illuminates according to lighting pattern 620 shown in
In another example, the TRX 110 may utilize the single fiber scheme discussed in block 460-475 and/or the fallback scheme discussed in relation to
In another example, the TRX 110 may determine that the fibers are swapped and no connection is possible (e.g., as discussed in block 465). In this example, the U1600 illuminates according to lighting pattern 640 shown in
Bus 750 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Micro-controller 210 typically includes a variety of computer system readable media (e.g., a non-transitory computer-readable storage medium). Such media may be any available media that is accessible by micro-controller 210, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 710 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) and/or cache memory. Micro-controller 210 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example, storage system 720 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a Compact Disc Read-Only Memory (CD-ROM), digital versatile disc-read only memory (DVD-ROM) or other optical media can be provided. In such instances, each can be connected to bus 750 by one or more data media interfaces. As will be further depicted and described below, system memory 710 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments described herein.
Micro-controller 210 may further include other removable/non-removable, volatile/non-volatile computer system storage media. In some examples, storage system 720 may be included as part of system memory 710 and may typically provide a non-volatile memory for the networked computing devices, and may include one or more different storage elements such as Flash memory, a hard disk drive, a solid state drive, an optical storage device, and/or a magnetic storage device. For example, storage system 720 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 750 by one or more data media interfaces. Storage system 720 may include media for a crossover parameters 721, negotiation parameters 722, and other information 723 stored for access and use by the micro-controller 210.
System memory 710 may include a plurality of modules 715 for performing various functions described herein. The modules 715 generally include program code that is executable by one or more of the processors 705. As shown, modules 715 include the detection module 716 and crossover module 717. The modules 715 may also interact with each other and storage system 720 to perform certain functions as described herein.
In the current disclosure, reference is made to various embodiments. However, the scope of the present disclosure is not limited to specific described embodiments. Instead, any combination of the described features and elements, whether related to different embodiments or not, is contemplated to implement and practice contemplated embodiments. Additionally, when elements of the embodiments are described in the form of “at least one of A and B,” or “at least one of A or B,” it will be understood that embodiments including element A exclusively, including element B exclusively, and including element A and B are each contemplated. Furthermore, although some embodiments disclosed herein may achieve advantages over other possible solutions or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the scope of the present disclosure. Thus, the aspects, features, embodiments and advantages disclosed herein are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to “the invention” shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s).
As will be appreciated by one skilled in the art, the embodiments disclosed herein may be embodied as a system, method or computer program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments presented in this disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block(s) of the flowchart illustrations and/or block diagrams.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the block(s) of the flowchart illustrations and/or block diagrams.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer, other programmable data processing apparatus, or other device provide processes for implementing the functions/acts specified in the block(s) of the flowchart illustrations and/or block diagrams.
The flowchart illustrations and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in the flowchart illustrations or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In view of the foregoing, the scope of the present disclosure is determined by the claims that follow.
