The subject matter described herein relates to network taps. More particularly, the subject matter described herein relates to network tap with battery assisted and programmable failover.
Network taps are devices used to monitor traffic in live networks. A network tap receives a signal from the network, copies or diverts the signal to one or more monitoring processors, and transmits the original signal back to the network. In today's high speed networks, network taps tap optical and electrical signals.
Because a network tap is typically used as inline component, the network operator needs to account for the case when the network tap fails, for example, due to loss of external power. Network taps include pairs of ports that connect to the network. One port of a port pair may connect to a cable to receive a signal from the network, and another port of the pair may connect to a cable to provide the signal back to the network. If a failure of external power occurs, one type of network tap automatically fails open to allow traffic to pass through the network tap. Traffic flow continuity is provided by optical switches connected between ingress and egress port pairs that close when external power is disconnected. The optical switches do not require power to close and thus prevents an interruption in traffic flow to or from the network.
One problem with utilizing optical switches between network tap ports to provide automatic fail open capability is that an optical switch must be provided for each ingress/egress port pair in the network tap, and optical switches are expensive. For a network tap that includes multiple port pairs, providing an optical switch between every port pair can greatly increase the cost of the network tap.
Another feature of some network taps when external power is disconnected is temporary battery backup of all of the components of the network tap, including the components that perform network monitoring functions. For these taps, when external power fails, a backup battery allows the tap to function in the same mode as the tap functioned prior to the failure. That is, the battery powers the full network monitoring functionality of the network tap. One problem with such an approach is that a large battery may be required to fully power the tap for extended periods of time when external power is lost.
Another problem with existing network taps is that the taps either fail open or fail closed. “Fail open”, as used herein, means that the network tap allows network traffic between ingress and egress network port pairs. “Fail closed” means that the network tap blocks network traffic between ingress and egress port pairs. Such inflexibility in failover operation limits the utility of such network taps.
According to one aspect of the subject matter described herein a network tap includes a processing element. The network tap further includes at least one optical-electrical transceiver for receiving an optical signal from a network and for converting the optical signal into an electrical signal. The network tap further includes at least one multiplexer/demultiplexer module coupled to the at least one optical-electrical transceiver for operating in a first mode when the network tap is externally powered, wherein, when operating in the first mode, the at least one multiplexer/demultiplexer module provides the electrical signal to the processing element, which performs a network monitoring task for the electrical signal, wherein the at least one multiplexer/demultiplexer module is configured to operate in a second mode comprising a fail open mode when the network tap is not externally powered wherein, when operating in the second mode, the at least one multiplexer/demultiplexer module ceases providing the electrical signal to the processing element and implements a loopback operation for the electrical signal. The network tap further includes a power source internal to the network tap for providing temporary power to optical-electrical transceiver and the multiplexer/demultiplexer module for operating in the second mode.
According to another aspect of the subject matter described herein, a network tap includes a processing element. The network tap further includes at least one optical-electrical transceiver for receiving an optical signal from a network and for converting the optical signal into an electrical signal. The network tap further includes at least one multiplexer/demultiplexer module coupled to the at least one optical-electrical transceiver for operating in a first mode when the network tap is externally powered, wherein, when operating in the first mode, the at least one multiplexer/demultiplexer module provides the electrical signal to the processing element, which performs a network monitoring task for the electrical signal. The network tap further includes a multiplexer/demultiplexer controller coupled to the at least one multiplexer/demultiplexer module, wherein the multiplexer/demultiplexer controller is programmable to control the at least one multiplexer/demultiplexer module to operate in a second mode comprising a fail open mode or a third mode comprising a fail closed mode when the tap is not externally powered wherein, when operating in the second mode, the at least one multiplexer/demultiplexer module ceases providing the electrical signal to the processing element and implements a loopback operation for the electrical signal and wherein, when operating in the third mode, the at least one multiplexer/demultiplexer module blocks the providing of the optical signal to the network.
Although network tap functionality, battery-assisted bypass functionality, and programmable bypass functionality as described herein is primarily implemented in hardware, portions of the subject matter described herein can be implemented in software in combination with hardware and/or firmware. For example, a portion of the subject matter described herein can be implemented in software executed by a processor. The software-implemented portion may include network monitoring functionality implemented by the processing element of the network tap when the network tap is in its normal operating mode with access to external power. In one exemplary implementation, the software portion of subject matter described herein can be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the software portion of subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
The subject matter described herein will now be explained with reference to the accompanying drawings of which:
One problem with the architecture illustrated in
Similarly, in the first mode of operation, SFP+ transceiver 112A converts optical signals received from network 106 into electrical signals and provides the electrical signals to multiplexer/demultiplexer module 202A, as indicated by connection 212. Multiplexer/demultiplexer module 202A provides the electrical signal from SFP+ transceiver 112A to FPGA 114, as indicated by connection 214. FPGA 114 provides the electrical signal to multiplexer/demultiplexer module 202B, as indicated by connection 216. Multiplexer/demultiplexer module 202B provides the electrical signal from FPGA 114 to SFP+ transceiver 112B, as indicated by connection 218. SFP+ transceiver 218 converts the electrical signal into an optical signal provides the optical signal to the network via one of ports 104.
Thus, in the first mode of operation, the traffic flow is from the network, through one of the transceivers 112A or 112B, through one of the multiplexer/demultiplexer modules 202A or 202B, to the FPGA or other processing element for network monitoring processing, and back to the network. Rather than continuing the same traffic flow when external power to network tap 200 is lost, network tap 200 includes an internal power source, such as battery 220, that powers only multiplexer/demultiplexer modules 202A and 202B and transceivers 112A and 112B. Power is preferably not provided to FPGA 114, which reduces the required size of battery 220. In one example, when external power is lost, network tap 200 operates on a second node where electrical signals to and from network 106 pass through SFP+ transceivers 112A and 112B and through multiplexer/demultiplexer modules 202A and 202B but not through FPGA 114. For example, a signal received from network 106 through SFP+ transceiver 112B is provided to multiplexer/demultiplexer module 202B. Rather than passing the signal to FPGA 114 for network monitoring processing, the signal bypasses network monitoring processing by being provided from multiplexer/demultiplexer module 202B to multiplexer/demultiplexer module 202A through a bypass path between multiplexer/demultiplexer modules 202A and 202B. This bypass path is indicated by arrow 222. The signal is then provided to SFP+ transceiver 112A, which converts the signal to an optical signal and provides the signal to network 106.
A similar failover path is implemented for traffic from network 106 that enters network tap 100 via the port corresponding to SFP+ transceiver 112A when external power is lost. For example, an optical signal from network 106 will be received by SFP+ transceiver 112A. SFP+ transceiver 112A converts the received optical signal to an electrical signal and provides the signal to multiplexer/demultiplexer module 202A. Multiplexer/demultiplexer module 202A provides the electrical signal to multiplexer/demultiplexer module 202B via bypass path 222. Multiplexer/demultiplexer module 202B provides the electrical signal to SFP+ transceiver 112B which converts the electrical signal to an optical signal and provides the electrical signal to network 106 or another network through an external optical cable.
Thus, in the architecture illustrated in
Similarly, when external power is lost, for traffic received from the network via SFP+ transceiver 112B, internal demultiplexer 307 of multiplexer/demultiplexer module 202B provides the signal to outputs 308 and to multiplexer/demultiplexer module 202A via chip-to-chip loopback connection 310. Multiplexer/demultiplexer module 202A provides the signal from connection 310 to internal multiplexer 312 which, selects inputs 311 and provides the signal to SFP+ transceiver 112A via connection 314.
When network tap 200 is externally powered, SFP+ transceiver 112A receives an optical signal from the network, converts the optical signal into an electrical signal, and provides the electrical signal to multiplexer/demultiplexer module 202A vial connection 313. Demultiplexer 300 within multiplexer/demultiplexer module 202A receives the electrical signal from SFP+ transceiver 112A and provides the output signal to FPGA 114 via outputs 316 and connection 317.
FPGA 114 may perform a network monitoring task, such as copying packets from the signal received from demultiplexer 300. FPGA 114 also provides the signal from network A to multiplexer/demultiplexer module 202B via connection 319. Internal multiplexer 304 of multiplexer/demultiplexer module 202B provides the signal from network A to SFP+ transceiver 112B via connection 306. SFP+ transceiver 112B converts the signal from network A back into an optical signal and provides the signal to network B.
When external power is connected to network tap 200, SFP+ transceiver 112B receives an optical signal from network B, converts the optical signal into an electrical signal, and provides the electrical signal to multiplexer/demultiplexer module 202B via connection 321. Demultiplexer 307 within multiplexer/demultiplexer module 202B provides the electrical signal from network B to FPGA 114 via connection 323. FPGA 114 performs a network monitoring task, such as copying packets from network B to a network monitoring application, such as a network performance monitoring application, an intrusion detection application, an intrusion protection application, etc. FPGA 114 also provides the electrical signal from network B to multiplexer/demultiplexer module 202A via connection 324. Multiplexer 312 of multiplexer/demultiplexer module 202A provides the electrical signal from network B to SFP+ transceiver 112A via connection 314. SFP+ transceiver 112A converts the electrical signal from network B into an optical signal and provides the optical signal to network A.
In the examples illustrated in
When operating in failover mode, network A traffic received by SFP+ transceiver 112A is provided to multiplexer/demultiplexer module 402B via connection 404. Multiplexer/demultiplexer module 402B loops the traffic received at one of its input ports via connection 404 to one of its output ports connected to connection 406 and to SFP+ transceiver 112B. The internal loopback functionality of multiplexer/demultiplexer 402B is indicated by dashed arrow 408.
Network B traffic received by SFP+ transceiver 112B is provided to multiplexer/demultiplexer module 402A via connection 410. When external power is lost, the traffic received via connection 410 is looped to SFP+ transceiver 112A via internal loopback connection 412 and connection 414. SFP+ transceiver 112A converts the electrical signal to an optical signal and provides the optical signal to network A.
When external power is available to network tap 400, network A traffic received by SFP+ transceiver 112A is provided to multiplexer/demultiplexer module 402B via connection 404. The traffic is then forwarded to FPGA 114 via internal connection 415 and external connection 416. FPGA 114 performs network monitoring processing for the received network A traffic and provides the original traffic to multiplexer/demultiplexer module 402A via connection 420. Multiplexer/demultiplexer module 402A provides the traffic to SFP+ transceiver 112A via connection 406. SFP+ transceiver 112A converts the electrical signal to an optical signal and provides the optical signal to network A.
Network B traffic received from SFP+ transceiver 112B is provided to multiplexer/demultiplexer module 402A via connection 410. The traffic is then provided to FPGA 114 via internal connection 417 and external connection 418. FPGA 114 performs network monitoring processing of the received network B traffic and provides the traffic to multiplexer/demultiplexer module 402B via connection 421. Multiplexer/demultiplexer module 402B then provides the network B traffic to SFP transceiver 112B via connection 406. SFP+ transceiver 112B converts the electrical signal into an optical signal and provides the optical signal to network B.
Thus, the architecture illustrated in
As stated above, one problem with some network taps is that they only have a fail open capability or only a fail closed capability. According to one aspect of the subject matter described herein, any of the network taps described herein may be programmable to operate in a fail open or fail closed mode of operation. In a fail open mode of operation, network traffic is allowed to pass through the network tap when external power is lost, as described above with respect to
In fail open mode, traffic received on one of network ports proceeds through transceivers 112 to high speed mux/demux 202 or 402 and proceeds or is looped back to transceivers 112 and out another network port, as described above. In fail closed mode, traffic received on network ports is blocked by not activating the loopback functionality of high speed mux/demux 402. Thus, the subject matter described herein includes a network tap that is programmable to operate in fail open or fail closed mode in combination with the above-described advantages of providing high speed mux and demux to control the fail open mode and using battery 220 to only power portions of network tap 500 that are needed to operate in fail open mode.
In step 602, network traffic is received at the network tap, the traffic is copied to a monitoring processor, and directed to an output port. For example, in the normal or powered mode where the network tap is connected to external power, traffic may be monitored and redirected back to the network via an output port.
In step 604, it is determined whether a loss of external power has occurred. If a power loss has not occurred, control returns to step 602 where the receiving and monitoring of traffic is continued. If a loss of external power has occurred, control proceeds to step 606 where the battery is used to only power failover components. In the examples illustrated above, the failover components include the electrical to optical transceivers and the multiplexer and demultiplexer modules. For aspects in which the network tap is programmable, the failover components may also include the multiplexer/demultiplexer controller illustrated in
Thus, by providing a network tap with programmable and battery assisted failover, the subject matter described herein is advantageous over conventional network taps that require optical switches per interface pair. The subject matter described herein is also advantageous over network tap implementations where battery backup powers the entire device, including network monitoring functions during failover. The network tap described herein is also advantageous over non-programmable network taps where the failover mode is fixed.
It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/368,749, filed Jul. 29, 2016; the disclosure of which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4802161 | Byars et al. | Jan 1989 | A |
5173794 | Cheung et al. | Dec 1992 | A |
5550802 | Worsley et al. | Aug 1996 | A |
5648965 | Thadani et al. | Jul 1997 | A |
5710846 | Wayman et al. | Jan 1998 | A |
5774453 | Fukano et al. | Jun 1998 | A |
5781318 | Tremblay | Jul 1998 | A |
5898837 | Guttman et al. | Apr 1999 | A |
5983308 | Kerstein | Nov 1999 | A |
6041037 | Nishio et al. | Mar 2000 | A |
6047321 | Raab et al. | Apr 2000 | A |
6108310 | Wilkinson et al. | Aug 2000 | A |
6167025 | Hsing et al. | Dec 2000 | A |
6181677 | Valli et al. | Jan 2001 | B1 |
6239579 | Dunn et al. | May 2001 | B1 |
6272136 | Lin et al. | Aug 2001 | B1 |
6366557 | Hunter | Apr 2002 | B1 |
6424627 | Sorhaug et al. | Jul 2002 | B1 |
6449247 | Manzardo et al. | Sep 2002 | B1 |
6542145 | Reisinger et al. | Apr 2003 | B1 |
6650803 | Ramaswami et al. | Nov 2003 | B1 |
6658565 | Gupta et al. | Dec 2003 | B1 |
6687009 | Hui et al. | Feb 2004 | B2 |
6687847 | Aguilera et al. | Feb 2004 | B1 |
6714976 | Wilson et al. | Mar 2004 | B1 |
6798740 | Senevirathne et al. | Sep 2004 | B1 |
6801840 | Kodama et al. | Oct 2004 | B2 |
6801940 | Moran et al. | Oct 2004 | B1 |
6823383 | MacBride | Nov 2004 | B2 |
6836540 | Falcone et al. | Dec 2004 | B2 |
6841985 | Fetzer | Jan 2005 | B1 |
6850706 | Jager et al. | Feb 2005 | B2 |
6882654 | Nelson | Apr 2005 | B1 |
6898630 | Ueno et al. | May 2005 | B2 |
7027437 | Merchant et al. | Apr 2006 | B1 |
7061942 | Noronha, Jr. et al. | Jun 2006 | B2 |
7171504 | Ishii | Jan 2007 | B2 |
7277957 | Rowley et al. | Oct 2007 | B2 |
7284055 | Oehrke et al. | Oct 2007 | B1 |
7308705 | Gordy et al. | Dec 2007 | B2 |
7321565 | Todd et al. | Jan 2008 | B2 |
7324553 | Varier et al. | Jan 2008 | B1 |
7362765 | Chen | Apr 2008 | B1 |
7415013 | Lo | Aug 2008 | B1 |
7430354 | Williams | Sep 2008 | B2 |
7477611 | Huff | Jan 2009 | B2 |
7486624 | Shaw et al. | Feb 2009 | B2 |
7505416 | Gordy et al. | Mar 2009 | B2 |
7594095 | Nordquist | Sep 2009 | B1 |
7616587 | Lo et al. | Nov 2009 | B1 |
7788365 | Foster et al. | Aug 2010 | B1 |
8077049 | Yaney et al. | Dec 2011 | B2 |
8755293 | Matityahu et al. | Jun 2014 | B2 |
8902735 | Matityahu et al. | Dec 2014 | B2 |
9749261 | Matityahu et al. | Aug 2017 | B2 |
20010040870 | Ohmori et al. | Nov 2001 | A1 |
20020003592 | Hett et al. | Jan 2002 | A1 |
20020026374 | Moneymaker et al. | Feb 2002 | A1 |
20020032880 | Poletto et al. | Mar 2002 | A1 |
20020073199 | Levine et al. | Jun 2002 | A1 |
20020087710 | Aiken et al. | Jul 2002 | A1 |
20020146016 | Liu et al. | Oct 2002 | A1 |
20020176355 | Mimms et al. | Nov 2002 | A1 |
20020180592 | Gromov | Dec 2002 | A1 |
20030090995 | Illikkal et al. | May 2003 | A1 |
20030112760 | Puppa et al. | Jun 2003 | A1 |
20030142666 | Bonney et al. | Jul 2003 | A1 |
20030145039 | Bonney et al. | Jul 2003 | A1 |
20030215236 | Manifold | Nov 2003 | A1 |
20040008675 | Basso et al. | Jan 2004 | A1 |
20040023651 | Gollnick et al. | Feb 2004 | A1 |
20040046516 | Uekawa | Mar 2004 | A1 |
20040062556 | Kubo et al. | Apr 2004 | A1 |
20040096227 | Bulow | May 2004 | A1 |
20040109411 | Martin | Jun 2004 | A1 |
20040128380 | Chen et al. | Jul 2004 | A1 |
20040202164 | Hooper et al. | Oct 2004 | A1 |
20040215832 | Gordy et al. | Oct 2004 | A1 |
20040264494 | Kim | Dec 2004 | A1 |
20050060535 | Bartas | Mar 2005 | A1 |
20050071711 | Shaw | Mar 2005 | A1 |
20050108444 | Flauaus et al. | May 2005 | A1 |
20050122910 | Parupudi et al. | Jun 2005 | A1 |
20050129033 | Gordy et al. | Jun 2005 | A1 |
20050132051 | Hill et al. | Jun 2005 | A1 |
20050271065 | Gallatin et al. | Dec 2005 | A1 |
20050278565 | Frattura et al. | Dec 2005 | A1 |
20060083511 | Edmunds et al. | Apr 2006 | A1 |
20060200711 | Schondelmayer et al. | Sep 2006 | A1 |
20060215566 | Walsh | Sep 2006 | A1 |
20060282529 | Nordin | Dec 2006 | A1 |
20070064917 | Matityahu et al. | Mar 2007 | A1 |
20070081549 | Cicchetti et al. | Apr 2007 | A1 |
20070081553 | Cicchetti et al. | Apr 2007 | A1 |
20070121499 | Pal et al. | May 2007 | A1 |
20070140398 | Inoue et al. | Jun 2007 | A1 |
20070171966 | Light et al. | Jul 2007 | A1 |
20070211682 | Kim et al. | Sep 2007 | A1 |
20070218874 | Sinha et al. | Sep 2007 | A1 |
20080049627 | Nordin | Feb 2008 | A1 |
20080072291 | Carley | Mar 2008 | A1 |
20080168283 | Penning | Jul 2008 | A1 |
20080214108 | Beigne et al. | Sep 2008 | A1 |
20080296685 | Sonehara et al. | Dec 2008 | A1 |
20090041051 | Matityahu et al. | Feb 2009 | A1 |
20090162057 | Friedrich | Jun 2009 | A1 |
20090178144 | Redlich et al. | Jul 2009 | A1 |
20090210649 | Wan et al. | Aug 2009 | A1 |
20090303883 | Kucharczyk et al. | Dec 2009 | A1 |
20100014605 | Geile et al. | Jan 2010 | A1 |
20100167713 | Hoffman | Jul 2010 | A1 |
20100183298 | Biegert et al. | Jul 2010 | A1 |
20100195538 | Merkey et al. | Aug 2010 | A1 |
20100247068 | Howarter et al. | Sep 2010 | A1 |
20100254310 | Kats et al. | Oct 2010 | A1 |
20110161544 | Chengson et al. | Jun 2011 | A1 |
20110211446 | Matityahu et al. | Sep 2011 | A1 |
20110211473 | Matityahu et al. | Sep 2011 | A1 |
20110249968 | Ou | Oct 2011 | A1 |
20120176917 | Matityahu et al. | Jul 2012 | A1 |
20140341568 | Zhang | Nov 2014 | A1 |
20160182150 | Sprenger | Jun 2016 | A1 |
Number | Date | Country |
---|---|---|
2091199 | Aug 2009 | EP |
2001-197066 | Jul 2001 | JP |
2006-148686 | Jun 2006 | JP |
10-2004-0058415 | Jul 2004 | KR |
WO-2002019642 | Mar 2002 | WO |
WO-2004012163 | Feb 2004 | WO |
WO-2005043838 | May 2005 | WO |
Entry |
---|
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/944,801 (dated Apr. 21, 2017). |
“PeriScope Central Management System (CMS) 5.0 Administrator's Guide”, Peribit Networks, Inc. 13 pages total (2003-2004). |
“Sequence Reducer/Sequence Mirror Operator's Guide”, Peribit Networks, Inc. 13 pages total. (2005). |
“VSS Coppertap Literature”, VSS Monitoring Inc. 2 pages. (2003-2004). |
“VSS Easy Install Guide”, VSS Monitoring Inc. 8 pages total. 2003-2005. |
“VSS Linksafe”, VSS Monitoring Inc., 1 page. (2003-2005). |
Advisory Action for U.S. Appl. No. 13/034,730 (dated Sep. 12, 2013). |
Anonymous, “100Base-TX/100BBase-FX Media Converters E-100BTX-FX-04 User's Guide”, Transitions Networks, Minneapolis, MN, Copyright 1998-2000, 4 pages. |
Belkin International, Inc., “Belkin Quick Installation Guide”, N1 Vision Wireless Router, Belkin International, Inc., Compton, CA, Feb. 11, 2009, 3 pages total. (Feb. 11, 2009). |
Communication pursuant to Article 94(3) EPC for European Patent Application No. 12 760 718.2 (dated Jan. 17, 2017). |
Extended European Search Report for European Patent Application No. 11748109.3 (dated Jul. 20, 2016). |
“Fast Ethernet Fiber-to-Fiber Converters”, Canary Communications, Inc. 7 pages total, 2004. |
Final Office Action for U.S. Appl. No. 13/034,730 (dated Jun. 5, 2013). |
Final Office Action for U.S. Appl. No. 13/070,086 (dated Aug. 9, 2013). |
Gigamon Systems LLC, “GigaVUE—Product Brief”, Gigamon Systems LLC, http://web.archive.org/web/20070815021951/www.gigamon.com/pdf/GigamonSystems-OnePageProductBrief.pdf Aug. 15, 2007, 1 page. (Aug. 15, 2007). |
International Preliminary Report on Patentability, PCT Application No. PCT/US2011/026159, dated Sep. 13, 2012. (dated Sep. 13, 2012). |
International Search Report, PCT Application No. PCT/US2011/026159, dated Nov. 30, 2011. (dated Nov. 30, 2011). |
International Search Report, PCT Application No. PCT/US2012/030448, dated Oct. 19, 2012. (dated Oct. 19, 2012). |
Non-Final Office Action for U.S. Appl. No. 13/944,801 (dated Apr. 27, 2015). |
Non-Final Office Action for U.S. Appl. No. 13/034,730 (dated Mar. 13, 2014). |
Non-Final Office Action for U.S. Appl. No. 13/070,086 (dated Jan. 25, 2013). |
Non-Final Office Action for U.S. Appl. No. 13/034,730 (dated Dec. 6, 2012). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/944,801 (dated Nov. 23, 2016). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/944,801 (dated Jul. 1, 2016). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/944,801 (dated Jan. 21, 2016). |
Notice of Allowance for U.S. Appl. No. 13/034,730 (dated Jul. 30, 2014). |
Notice of Allowance for U.S. Appl. No. 13/070,086 (dated Feb. 4, 2014). |
Written Opinion, PCT Application No. PCT/US2011/026159, dated Nov. 30, 2011. (Nov. 30, 2011). |
Written Opinion, PCT Application No. PCT/US2012/030448, dated Oct. 19, 2012. (Oct. 19, 2012). |
Communication pursuant to Article 94(3) EPC for European Application No. 11 748 109.3 (dated Feb. 28, 2018). |
Number | Date | Country | |
---|---|---|---|
20180034542 A1 | Feb 2018 | US |
Number | Date | Country | |
---|---|---|---|
62368749 | Jul 2016 | US |