The present disclosure relates generally to intelligent systems that map optical fiber communication paths of one port density to optical fiber communication paths of a different port density while providing human perceivable indications to represent attached devices port status, to provide guidance for fiber moves, adds or changes, or for other end user intentions. Other intelligent functions of the system may include an ability to detect cable presence, logging of moves, adds and changes such as counters for cable insertions and extractions, and to identify and log cable characteristics such as color, length, ID, fiber type and such.
The Intelligent Fiber Port Management System according to the present disclosure maps optical fiber communication paths of one density to optical fiber communication paths of a different density, for either breakout or aggregation functionality. For example, devices with one or more Quad Small Form-factor Pluggable (QSFP+) multi-fiber transceivers that interface with multi-fiber connectors can be mapped to devices with a plurality of small form factor (SFF) transceivers that interface with single fiber optic connectors. Examples of multi-fiber connectors may include but are not limited to Multi-fiber Push On (“MPO”) connectors, and examples of single fiber optic connectors may include but are not limited to Lucent Connectors (“LC”).
In an example where 20 QSFP+ MPO multi-fiber connections are to be mapped to LC single duplex fiber connections, each QSFP+ transceiver has 4 transmit (Tx) and 4 receive (Rx) fiber paths housed inside a 12 fiber MPO connector that are accessible from, for example, a rear panel of the Intelligent Fiber Port Management System. It should be noted that in this example, the remaining 4 fibers are inactive. The Fiber Port Management System internally provides the required breakout connectivity from the multi-fiber connections to the single fiber connectors. The result in this example is that 20 MPO connectors on a rear panel of the Fiber Port Management System can be mapped to 160 LC connectors on the front panel of the Fiber Port Management System with 80 paired ports.
In another example, a high density multifiber connection such as a 24 fiber MPO connector may break out the individual fibers to single fiber connectors such as bidirectional LC connections or into duplex LC connections supporting a Transmit fiber and a Receive fiber.
In another example, a high density multifiber connection such as a 24 fiber MPO connector may break out the individual fibers to multifiber connectors such as 12 fiber MPO connectors or 8 fiber MPO connectors which may connect to downstream devices with multifiber port connectors such as 12 fiber MPO connectors or other transceiver interfaces such as QSFP transceivers.
In addition, each multi-fiber connector on the Fiber Port Management System, e.g., each MPO connector, has one or more associated LEDs on either the front panel or the rear panel that is in close proximity to the relevant multi-fiber connector and that provides a visual indication programmable by an externally attached device, by an external Management System, or by any other criteria defined by an internal CPU. In the configuration shown, the one or more LEDs can be positioned above the multi-fiber connector. Each single fiber connector on the Fiber Port Management System, e.g., each quad LC connector, has one or more (e.g., two) LEDs on either the front panel or the rear panel that is in close proximity to the relevant single-fiber connector and that provides a visual indication programmable by an externally attached device, by an external Management System, or by any other criteria defined by the internal CPU. The one or more LEDs can have different colors to indicate defined conditions. The colors for the multi-fiber LEDs may be the same as the colors for the single-fiber LEDs or the colors for the multi-fiber LEDs may be different than the colors for the single-fiber LEDs.
A more complete appreciation of the present disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:
The Fiber Port Management System 10 according to the present disclosure can be used to map optical fiber paths of one or more ports of, for example, a network device 50 having one fiber density to optical fiber paths having a different fiber density that can be used by one or more network appliances 60 or other network devices. For the purpose of the present disclosure, a network device can include network switches, patch panels, and other types of devices facilitating data center or network communications. The phrase network appliance can include, for example, data storage devices, servers and other computing devices that facilitate user interaction.
For example, and referring to
As another example, and referring to
As another example, and referring to
Referring to
For the high density side of the Fiber Port Management System 10, the one or more multi-fiber connectors 20 can be connected to, for example, the front or rear panel of the housing 11, and for the low density side of the Fiber Port Management System 10, one or more single-fiber connectors 22 can be connected to, for example, the front or rear panel of the housing 11. An exemplary MPO to LC hydra cable 24, seen in
The Multi-fiber Termination Push-on (“MTP”) connectors, which are also called MPO connectors 20, and LC connectors 22 are mounted to openings in the PCB on the front and/or rear panels 14 and 15. Other embodiments may include higher density MPO connectors on the rear panel and lower density MPO connectors on the front panel. The LC connectors or adapters pass through openings on the PCB and mount to, for example, the front panel 14 of the housing 11, and may or may not be operatively connected to the PCB. As shown in
In the exemplary configuration shown in
Within the housing 11 is a CPU 80, seen in
Fiber Port Management System CPU Operation
The Fiber Port Management System 10 frontends a network device (e.g., network device 50) and extends the aggregated interfaces to low density or lower density pairs of ports, e.g., simplex pairs of ports. A function of the Fiber Port Management System 10 is to split or breakout the aggregated data to individual ports. The Fiber Port Management System 10 has a core processor environment (CPE) with LED indicators 26 for each port. The CPE can reside on the Fiber Port Management System 10 or remotely on a different platform. The CPE manages an application program interface.
1. Network Device Controlling Fiber Port Management System
A network device that includes any platform with software or hardware able to communicate to Fiber Port Management System 10 via a defined application program interface (API) can be used with the Fiber Port Management System of the present disclosure. In this exemplary embodiment, the API can include any method of communicating to the Fiber Port Management System. For example, a Restful API, JSON format can be used to communicate with the Fiber Port Management System 10. In this exemplary embodiment, the network device 50 is the master and controls and/or provides information to the Fiber Port Management System 10 acting as a slave device. An example of the communication protocol may include:
A network device 50 that includes any platform with software or hardware able to communicate to the Fiber Port Management System via defined Application Program Interface (API) can be used with the Fiber Port Management System 10 of the present disclosure. In this exemplary embodiment, the API can include any method of communicating between the Fiber Port Management System 10 and the network device 50. In this exemplary embodiment, the Fiber Port Management System 10 is the master and polls the network device 50 for information to determine the state of the port status of the LEDs 26. The information is then parsed by the Fiber Port Management System 10 to set the state, e.g., the color, mode, etc., of each LED 26 associated with the high density connectors 20 and/or the low density connectors 22. Two processes would be used to parse the information; configuration and interface polling. An example of the communication protocol may include:
A network device that includes any platform with software or hardware able to communicate to Fiber Port Management System via defined Application Program Interface (API) can be used with the Fiber Port Management System of the present disclosure. In this exemplary embodiment, the API can be any method of communicating between the Fiber Port Management System 10 and the network device 50. The Fiber Port Management System 10 can be either a slave device or a master device such that information used to set the state of the LEDs 26 is set by a network device 50 or polled/received by the Fiber Port Management System. This embodiment uses methods for receiving request/information about interface, as described in sections 1 or 2 above. In this exemplary embodiment, the Fiber Port Management System's CPE is in another platform, i.e. an appliance or virtual machine. The CPE shows a virtual display of the Fiber Port Management System and its LEDs. The virtual display can be on any network device 50 or appliance 60, local to CPE or on a mobile device.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or computer program. Accordingly, aspects of the present invention 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 system. Furthermore, aspects of the present disclosure 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.
Computer program code for carrying out operations for aspects of the present invention 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 computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices 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 flowchart and/or block diagram block or blocks.
It will be understood that various modifications can be made to the embodiments of the present disclosure without departing from the spirit and scope thereof. Therefore, the above description should not be construed as limiting the disclosure, but merely as embodiments thereof. Those skilled in the art will envision other modifications within the scope and spirit of the invention as defined by the claims appended hereto.
This application is a continuation application of co-pending and allowed U.S. application Ser. No. 16/288,389 filed Feb. 28, 2019, which is a continuation application of U.S. application Ser. No. 15/705,084 filed Sep. 14, 2017, now U.S. Pat. No. 10,255,628, which is based on and claims benefit from U.S. Provisional Application No. 62/394,544, filed on Sep. 14, 2016, entitled “Intelligent Fiber Port Management,” the entire contents of all are incorporated herein in their entirety by reference.
Number | Name | Date | Kind |
---|---|---|---|
5101151 | Beaufils et al. | Mar 1992 | A |
5457556 | Shiragaki | Oct 1995 | A |
5493565 | Hanson et al. | Feb 1996 | A |
5838681 | Bonomi et al. | Nov 1998 | A |
5892770 | Wolf et al. | Apr 1999 | A |
6188702 | Tornetta et al. | Feb 2001 | B1 |
6243510 | Rauch | Jun 2001 | B1 |
6765877 | Foschiano | Jul 2004 | B1 |
6747878 | Hipp et al. | Aug 2004 | B1 |
6980725 | Swieconek | Dec 2005 | B1 |
7226217 | Benton et al. | Jun 2007 | B1 |
7277425 | Sikdar | Oct 2007 | B1 |
7492714 | Liao et al. | Feb 2009 | B1 |
7606494 | Weston-Dawkes | Oct 2009 | B1 |
7653057 | Fromm | Feb 2010 | B1 |
7772975 | Downie et al. | Aug 2010 | B2 |
7782202 | Downie et al. | Aug 2010 | B2 |
7831733 | Sultan | Nov 2010 | B2 |
7965186 | Downie et al. | Jun 2011 | B2 |
8138925 | Downie et al. | Mar 2012 | B2 |
8264366 | Chamarti et al. | Sep 2012 | B2 |
8421626 | Downie et al. | Apr 2013 | B2 |
8576839 | Beshai | Nov 2013 | B2 |
8873967 | Bames | Oct 2014 | B2 |
8994547 | German | Mar 2015 | B2 |
9002170 | Neitge et al. | Apr 2015 | B2 |
9030947 | Xu | May 2015 | B2 |
9100313 | Mazzola | Aug 2015 | B1 |
9159012 | Downie et al. | Oct 2015 | B2 |
9172465 | Wu | Oct 2015 | B2 |
9277302 | Beshai | Mar 2016 | B2 |
9715795 | Butterbaugh | Jul 2017 | B2 |
9865976 | Warren | Jan 2018 | B2 |
10225628 | Raza et al. | Mar 2019 | B2 |
10674235 | Raza | Jun 2020 | B2 |
20010015839 | Koh et al. | Aug 2001 | A1 |
20030026205 | Mullendore et al. | Feb 2003 | A1 |
20030030866 | Yoo | Feb 2003 | A1 |
20040029417 | Engel et al. | Feb 2004 | A1 |
20040160917 | Eliznd | Aug 2004 | A1 |
20060018329 | Nielsen et al. | Jan 2006 | A1 |
20060148279 | German et al. | Jul 2006 | A1 |
20060165366 | Feustel et al. | Jul 2006 | A1 |
20060186926 | Yager et al. | Aug 2006 | A1 |
20060251419 | Zadikian et al. | Nov 2006 | A1 |
20070291535 | Eberle et al. | Dec 2007 | A1 |
20080101229 | Meleis et al. | May 2008 | A1 |
20090051558 | Dorval | Feb 2009 | A1 |
20090074414 | Miles et al. | Mar 2009 | A1 |
20090226181 | Fingler et al. | Sep 2009 | A1 |
20100098412 | Boyd et al. | Apr 2010 | A1 |
20100211664 | Raza et al. | Apr 2010 | A1 |
20100129078 | Weston-Dawkes et al. | May 2010 | A1 |
20100142544 | Chapel et al. | Jun 2010 | A1 |
20100211665 | Raza et al. | Aug 2010 | A1 |
20100211697 | Raza et al. | Aug 2010 | A1 |
20100215049 | Raza et al. | Aug 2010 | A1 |
20100266117 | Enge et al. | Oct 2010 | A1 |
20110092100 | Coffrey et al. | Apr 2011 | A1 |
20110116748 | Smrha et al. | May 2011 | A1 |
20110188383 | Koziy et al. | Aug 2011 | A1 |
20110228473 | Anderson et al. | Sep 2011 | A1 |
20110255829 | Anderson et al. | Oct 2011 | A1 |
20110274437 | Jones et al. | Nov 2011 | A1 |
20110292788 | Tsuchiya | Dec 2011 | A1 |
20120008945 | Single et al. | Jan 2012 | A1 |
20120069839 | Kunz et al. | Mar 2012 | A1 |
20120102217 | Carona | Apr 2012 | A1 |
20120219005 | Durve et al. | Aug 2012 | A1 |
20120243554 | Sybesma et al. | Sep 2012 | A1 |
20120246362 | Anne et al. | Sep 2012 | A1 |
20120287939 | Leu | Nov 2012 | A1 |
20130148976 | Patel et al. | Jun 2013 | A1 |
20130171042 | Plotnikov et al. | Jul 2013 | A1 |
20130177309 | El-Ahmadi et al. | Jul 2013 | A1 |
20130179622 | Pratt et al. | Jul 2013 | A1 |
20130194005 | Vouilainen et al. | Aug 2013 | A1 |
20140019662 | Coffey | Jan 2014 | A1 |
20140036920 | McCormick et al. | Feb 2014 | A1 |
20140270634 | Miller | Sep 2014 | A1 |
20140270762 | Li et al. | Sep 2014 | A1 |
20140317249 | Janakiraman et al. | Oct 2014 | A1 |
20160192044 | Raza | Jun 2016 | A1 |
20180059326 | Makrides-Saravanos | Mar 2018 | A1 |
Number | Date | Country |
---|---|---|
2468008 | Jun 2012 | EP |
2414347 | Nov 2005 | GB |
2013171042 | Nov 2013 | WO |
2016054028 | Jun 2016 | WO |
Entry |
---|
LHCB Online System Data Acquisition & Experiment Control. 2001. (retrieved on Sep. 4, 2015). Retrieved from the internet: <URL:http://lhcb-comp.web.cem.ch/ilcb-comp/General/Publicaitons/onlinetdr.pdf>. |
International Search Report and Written Opinion mailed in PCT/US2015/039045 by ISA/US dated Oct. 2, 2015. |
International Search Report and Written Opinion mailed in PCT/US2015/23077 by ISA/US dated Jul. 7, 2015. |
International Search Report and Written Opinion mailed in PCT/US2015/12795 by ISA/US dated May 18, 2015. |
International Search Report and Written Opinion mailed in PCT/US2016/026714 by ISA/US dated Jul. 12, 2016. |
International Search Report and Written Opinion mailed in PCT/US2015/052924 by ISA/US dated Feb. 2, 2016. |
International Search Report and Written Opinion mailed in PCT/US2015/052847 by ISA/US dated Jun. 30, 2016. |
International Search Report and Written Opinion mailed in PCT/US2017/051635 by ISA/US dated Nov. 28, 2017. |
International Preliminary Report on Patentability mailed in PCT/US2017/051635 by ISA/US dated Mar. 28, 2019. |
Examination Report No. 1 in corresponding AU 2017325838 dated Dec. 9, 2019. |
Examination Report No. 2 in corresponding AU 2017325838 dated Jun. 15, 2020. |
Extended European Search Report in corresponding EU 17851554.0 dated Mar. 20, 2020. |
Number | Date | Country | |
---|---|---|---|
20200296482 A1 | Sep 2020 | US |
Number | Date | Country | |
---|---|---|---|
62394544 | Sep 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16288389 | Feb 2019 | US |
Child | 16889616 | US | |
Parent | 15705084 | Sep 2017 | US |
Child | 16288389 | US |