Computing environments are becoming increasingly complex. One reason is that computing tasks are becoming more complicated. Another is that extremely high-quality, specialized computing devices are becoming popular.
These ever increasingly complicated tasks have driven a recent evolutionary change to many people's computer systems, specifically, the inclusion of multiple display screens. For example, an electronic engineer may use one display to show a schematic of a portion of an electronic device and another display to show a layout of that portion of the electronic device. Also, these complicated tasks have led to increases in the amount of data that needs to be stored. In particular, video applications may be capable of generating huge amounts of data. In response, external hard drives have become a popular way to store this data.
The availability of specialized devices has also acted to increase many user's computing environments. For example, laptop computers have become so powerful that for many, they are not only a portable computing device, but have taken over duties as a desktop computer as well. But often times, perhaps at work or at home, users may want a bigger screen than a laptop may provide. In such a case, a larger, external display may be used. Also, a laptop may have a limited storage capacity. This, and a desire to perform backup tasks, may prompt a user to add an external storage drive.
To share data, these devices need to connect to each other, either through cables, wirelessly, or by using other means. When connecting these devices through these cables, it may be useful to be able to optimally utilize the bandwidth available at these connections.
Thus, what is needed are circuits, methods, and apparatus that may improve networking techniques for transferring data among various electronic devices.
Accordingly, embodiments of the present invention may provide circuits, methods, and apparatus that may improve networking techniques for transferring data among various electronic devices.
An illustrative embodiment of the present invention may provide sharing data among various devices by daisy-chaining devices together. That is, several devices may be connected to each other through a series of cables to form a chain of devices. For example, a host device, such as a laptop, may connect to an external display through a first cable, while an external storage drive may connect to the display through a second cable. Data on these cables may be received by, and transmitted by, router chips or other appropriate devices. This configuration allows the host device, the laptop, to display graphics images on the display and to store data in the external drive.
With this physical connection, data may be shared among these devices in a number of ways. That is, various virtual connections may be configured given a set physical connection. Each virtual connection from one device to another may be referred to as a hop. A tunnel may be used to convey data from one device to one or more other devices, which may be referred to as destination devices. A tunnel may be one hop in length, or it may be multiple hops in length. A device where a tunnel terminates may be referred to as a target device.
In a specific embodiment of the present invention, data may be shared among multiple devices using a series of single-hop tunnels. This technique may provide for potentially very long daisy chains of devices at the cost of an increase in latency through the chain.
In another specific embodiment of the present invention, a number of tunnels may be formed by a host device. These tunnels may each have a target device in the daisy chain. Some of these tunnels may be multiple hops in length. Each tunnel may originate at the host device and terminate at their target device. Each tunnel may bypass devices, if any, between the host device and the tunnel's target device. This technique may reduce latency, but the length of a resulting daisy chain may be limited by the number of tunnels that may be formed by the host. In various embodiments of the present invention, the number of tunnels that may be formed by a host device may be limited by a number of available hardware resources. For example, a number of adapters for a particular protocol in the host device may limit the number of tunnels that may be formed.
In another specific embodiment of the present invention, these two techniques may be combined. For example, a number of tunnels may be formed by a host device, where each tunnel carries data for multiple destination devices. Each tunnel may originate in the host device and terminate in a target device. Each tunnel may bypass intermediate devices between the host device and their target device. A series of single-hop tunnels may then convey data from the target device to the tunnel's other destination devices.
Another illustrative embodiment of the present invention may provide a method of simplifying the routing of high-speed data signals through a network topology. In one example, a device may include two router devices. These router devices may be cross-coupled to connectors that may be connected to other electronic devices further down the daisy chain. By cross coupling these connectors, it does not matter which connector a downstream device connects to, the same data may appear on the same connector pins. Also, by cross-coupling these connectors, data may pass through a device having two router devices without that data having to be passed from one of the router devices to the other.
Various embodiments of the present invention may incorporate one or more of these and the other features described herein. A better understanding of the nature and advantages of the present invention may be gained by reference to the following detailed description and the accompanying drawings.
This figure includes host device 110, first electronic device 120, and second electronic device 130. In this example host device 110 is a laptop computer, while the first electronic device 120 and the second electronic device 130 are an external display and a hard drive. In other embodiments of the present invention, other types of devices may be connected together. Host device 110 may communicate with first electronic device 120 over cable 140. First electronic device 120 may communicate with second electronic device 130 over cable 150. In various embodiments of the present invention, cables 140 and 150 may be various types of cables. In a specific embodiment of the present invention, cables 140 and 150 may be Thunderbolt cables, though in other embodiments of the present invention, cables 140 and 150 may be DisplayPort cables, or other types of cables.
In various embodiments of the present invention, data may be transmitted and received over cables 140 and 150 using various types of circuitry. For example, router device or chips may be used to transmit and receive data over cables 140 and 150. A specific example of such a router device or chip may be the “Light Peak” developed at least in part by Intel Corp. of Santa Clara, Calif., though in other embodiments of the present invention, other types of router devices or chips may be used.
In a specific embodiment of the present invention, various types of data may be transmitted over cables 140 and 150. For example, DisplayPort or PCIe data may be transmitted using Thunderbolt packets over cables 140 and 150. In other embodiments of the present invention, other types of data formatted in other ways may be transmitted over cables 140 and 150.
In this example, cable 140 may carry data transmitted from host device 110 to first electronic device 120 and second electronic device 130. Cable 150 may carry data from first electronic device 120 to second electronic device 130. Similarly, cable 150 may carry data transmitted from second electronic device 130 to first electronic device 120. Cable 140 may carry data transmitted from first electronic device 120 to host device 110.
Once these physical connections are set, the virtual communication channels used to convey this data may be configured in various ways. For example, data may be transmitted over cables 140 and 150 using a series of one hop tunnels. This may provide an advantage in that very long daisy chained may be achieved. This long or large fanout, however, may come at the expense of increased latency. An example is shown in the following figure.
This figure illustrates a host device 210 connected to first device 220 over first cable 240, and second device 230 connected to first device 220 over second cable 250.
In this example, host device 210 may transmit data A to first device 220 and data B to second device 230. Accordingly, host device 210 may form a first tunnel (A,B) to carry data A to first device 220. The first tunnel (A,B) may be formed at a PCIe adapter associated with the PCIe switch in host device 210. The first tunnel (A,B) may terminate at a Thunderbolt switch in first device 220. Data A,B may be provided to its corresponding PCIe switch. The PCI switch may provide data A to circuitry coupled to the router chip in first device 220. An adapter associated with the PCIe switch may form a second tunnel (B). Second tunnel (B) may be conveyed using second cable 250 to second device 230. Data B may be provided through a corresponding PCIe switch to other circuitry in second device 230.
In a specific embodiment of the present invention, each Thunderbolt switch may be able to route data received from a first cable directly to a second cable. In this way, a data path may bypass a PCIe switch in a router device and avoid its attendant format changes. This may reduce the overall latency through a chain of devices. An example is shown in the following figure.
As before, host device 310 may transmit data A to first device 320, and data B to second device 330. Accordingly, data A and B may be received by the PCIe switch in host device 310. Adapters associated with this PCIe switch may form separate tunnels for data A and data B. These two tunnels may convey data using first cable 340 to first device 320. Tunnel (A) may terminate and data A may be provided by the PCIe switch to associated circuitry in first device 320. Tunnel (B) may bypass the PCIe switch and exit the Thunderbolt switch on second cable 350. In this configuration, tunnel (A) may be one hop long and tunnel (B) may be two hops long. Tunnel (B) may terminate at the Thunderbolt switch in second device 330, and data B may be provided by the associated PCIe switch to circuitry in second device 330.
In this way, the latency of data B may be reduced by bypassing the PCIe switch in first device 320. However, the number of tunnels may be limited by hardware resources in host device 310. For example, if a number of PCIe adapters that can tunnel PCIe data is limited to four, the maximum fanout from host device 310 is also four. Accordingly, embodiments of the present invention may provide a mix of the above to techniques. In this way, latency may be reduced, while maintaining long or large fanouts. An example is shown in the following figure.
In this example, host 410 may transmit data A to first device 420, data B to second device 430, and data C to third device 460. A first adapter in host device 410 may form a first tunnel for data A, and a second adapter may form a second tunnel for data B and C. Tunnels (A) and (B,C) may be conveyed using first cable 440. Tunnel (A) may terminate in first device 420 and data A may be provided through its PCIe switch to associated circuitry.
Tunnel (B,C) may bypass the PCIe switch in first device 420 and exit the Thunderbolt switch on second cable 450. This may allow data B and C to avoid the latency incurred with the PCIe switch in first device 420. Tunnel (B,C) may terminate in second device 430. In this way, tunnel (B,C) may be two hops long. Data B may be provided by the PCIe switch in second device 430 to circuitry in second device 430. Tunnel (C) may be formed and provided on third cable 470, where it may be received by third device 460. The PCIe switch in third device 460 may provide this data to associated circuitry.
Again, in this example, data B and C may avoid the latency of a PCIE switch. Also, only the resources of two adapters in host device 410 are used transmit data to these three external devices. This tradeoff may help reduce latency while providing good fanout.
Devices consistent with various embodiments of the present invention may utilize multiple router devices. For example, some electronic devices may include two router chips or devices, though other devices may include more than two router chips or devices. When two or more devices are included, a first router device may be used to receive and provide data for the electronic device housing the routers, while a second router device may be used to send data to other electronic devices coupled downstream. To facilitate this, connector receptacles connected to the router devices may be cross coupled. This arrangement may allow multiple, high-bandwidth signal paths to use separate lanes, which may avoid bandwidth limitations that may otherwise result from sharing a single lane. An example is shown in the following figure.
Again, in this example, host device 510 may be connected to first electronic device 520 through tethered cable 540. This tethered cable may carry two lanes of data. A first lane of data may carry data A and X from connector 512 to a first router chip or device 524 in first electronic device 520, while a second lane may carry data B from connector 512 to second router chip or device 526 in first electronic device 520. Physically, these lanes may be specific wires in tethered cable 540. They may terminate at one end at specific pins or contacts in connector 512. In practical applications, connector 512 may be a composite of a connector insert attached to an end of tethered cable 540 and a connector receptacle in host device 510. The lanes may be assigned to specific pins or contacts in the connectors.
Again, in this example, host 510 may transmit PCIe data A and DisplayPort data X to first electronic device 520, and PCIe data B to second electronic device 530. Accordingly, host device 510 may provide data A and X to a first lane defined by pins of connector 512 and data B to a second lane of connector 512. First router chip 524 may provide PCIe data A and DisplayPort data X to associated circuitry in first electronic device 520. (It should be noted that in these examples, associated circuitry is connected to the top router device or chip, such as router device 524, and is not directly connected to the lower router device or chip, such as router chip 526.) Second router chip or device 526 may provide data B to connector 522. Second electronic device 530 may receive data B through cable 550 and connector 532. In this example, data B may pass through electronic device 520. That is, data B may not need to be passed from router device 524 to router device 526. This may help reduce the latency of data B and saves power. It should also be noted that it does not matter which connector of second electronic device 530 that cable 550 is connected to. If cable 550 is connected to the lower connector receptacle, routing device 526 could be configured to deliver data B to that connector.
This arrangement may also be useful in load-balancing where two DisplayPort or other high-bandwidth signals are received by an electronic device, since each signal may be assigned to a separate lane and each routing device may handle one of these high-bandwidth signals. An example is shown in the following figure.
In this example, host device 610 may transmit PCIe data A and DisplayPort data X to first electronic device 620, DisplayPort data Y to second electronic device 630, and PCIe data B to third electronic device 660. Accordingly, host device 610 may provide data A, B, and X to a first lane on connector 612, and data Y on a second lane of connector 612. First routing device 624 in first electronic device 620 may provide PCIe data A and DisplayPort data X to internal circuitry. First routing device 624 may further provide data B to a second lane of connector 622. Second routing device 626 may provide data Y to a first lane on connector 622.
Second electronic device 630 may receive data Y and provides it to internal circuitry. Second routing chip 636 may provide data B to a first lane on connector 632. Third electronic device 660 may receive data B.
In this example, host device 610 may provide two high-speed data signals X and Y. In this configuration, these high-speed signals may use separate lanes and separate routing chips. Again, this may help reduce latency, and may also help balance the bandwidth load among the various circuits.
More specifically, in this example, data X and Y may be DisplayPort signals, though in other configurations, they may be other types of data. These signals may consume a great deal of bandwidth, so much so that in some embodiments of the present invention, data X and Y may not be able to share a data lane. That is, the bandwidth requirements of data X and Y may exceed the bandwidth capacity of a single lane. Accordingly, this configuration allows data X to share a lane with data A and B, which may be lower bandwidth signals, while providing a separate lane for data Y. By allowing data X to have its own lane separate from data Y, host device 610 may provide DisplayPort data to first electronic device 620 and second electronic device 630.
As can be seen in this example, the cross coupling router chip outputs at the connectors of first electronic device 620 and second electronic device 630 may allow the high-bandwidth data signals X and Y to be routed using separate lanes. For example, since data Y is not used by first electronic device 620, it may be provided by host device 610 on a second lane that is received over tethered cable 640 by routing chip 626. Routing device or chip 626 may then provide data Y on a first lane to either connector 622 or 623, depending on where cable 650 is inserted. By providing data Y on this first lane, data Y may be received by router chip or device 634 in second electronic device 630, which may provide it to associated circuitry, as shown.
It should be noted that without cross coupling, router chip 626 in first electronic device 620 may provide data Y on the second lane with data B, such that data Y would be received by routing device or chip 636. In this case, routing chip 636 would have to provide data Y over connection 635 to routing chip or device 634, which would then provide data Y to the associated circuitry. This extra jump over path 635 may add latency to data Y, consume extra power, and also slow the transmission of data B.
It should also be noted that the benefit of this configuration arises independently of the connector on the first electronic device that the tethered cable 650 is connected to. Specifically, if tethered cable 650 is connected to connector receptacle 623, then routing device 626 in first electronic device 620 may provide data Y to routing device 634 in second electronic device 630 via connector receptacle 623.
In various embodiments of the present invention, various connections may be made among routing chips or devices and connectors. In this example, a first input/output port on a first routing device may be connected to pins of a second lane on a first connector and a second input/output port on the first routing device may be connected to pins of a second lane on a second connector. Similarly, a first input/output port on a second routing device may be connected to pins of a first lane on a first connector and a second input/output port on the second routing device may be connected to pins of a first lane on a second connector.
The above description of embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form described, and many modifications and variations are possible in light of the teaching above. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. Thus, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims.
This application is a divisional of U.S. patent application Ser. No. 13/403,182, filed Feb. 23, 2012, which claims the benefit of U.S. provisional patent application No. 61/446,027, filed Feb. 23, 2011, which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3581143 | Dornfeld | May 1971 | A |
4628151 | Cardas | Dec 1986 | A |
5228035 | Hirato et al. | Jul 1993 | A |
5313465 | Perlman et al. | May 1994 | A |
5711686 | O'Sullivan et al. | Jan 1998 | A |
6029137 | Cordery et al. | Feb 2000 | A |
6169251 | Grant et al. | Jan 2001 | B1 |
6485335 | Dewdney | Nov 2002 | B1 |
6495763 | Eichmann et al. | Dec 2002 | B1 |
6653813 | Khatri | Nov 2003 | B2 |
6677534 | Yamamoto et al. | Jan 2004 | B2 |
6792474 | Hopprich et al. | Sep 2004 | B1 |
6798790 | Enssle et al. | Sep 2004 | B1 |
6998538 | Fetterolf, Sr. et al. | Feb 2006 | B1 |
7033219 | Gordon et al. | Apr 2006 | B2 |
7174413 | Pettey et al. | Feb 2007 | B2 |
7188209 | Pettey et al. | Mar 2007 | B2 |
7197549 | Salama et al. | Mar 2007 | B1 |
7219183 | Pettey et al. | May 2007 | B2 |
7255602 | Driessen et al. | Aug 2007 | B1 |
7323640 | Takahashi et al. | Jan 2008 | B2 |
7366182 | O'Neill | Apr 2008 | B2 |
7369388 | Cheung et al. | May 2008 | B2 |
7422471 | Wu | Sep 2008 | B1 |
7447922 | Asbury et al. | Nov 2008 | B1 |
7466712 | Makishima et al. | Dec 2008 | B2 |
7480303 | Ngai | Jan 2009 | B1 |
7561855 | Hofmeister et al. | Jul 2009 | B2 |
7562176 | Kloeppner et al. | Jul 2009 | B2 |
7587575 | Moertl et al. | Sep 2009 | B2 |
7689755 | Balasubramanian et al. | Mar 2010 | B2 |
7743197 | Chavan et al. | Jun 2010 | B2 |
7830882 | Johnson | Nov 2010 | B2 |
7860205 | Aweya et al. | Dec 2010 | B1 |
7944200 | Endo et al. | May 2011 | B2 |
8267718 | Straka et al. | Sep 2012 | B2 |
8312302 | Baker et al. | Nov 2012 | B2 |
8327536 | Kim et al. | Dec 2012 | B2 |
8380912 | Jaramillo | Feb 2013 | B2 |
8463881 | Baker et al. | Jun 2013 | B1 |
8516238 | Cornelius et al. | Aug 2013 | B2 |
8683190 | Cornelius et al. | Mar 2014 | B2 |
8696378 | Behziz et al. | Apr 2014 | B2 |
8801461 | Kim et al. | Aug 2014 | B2 |
8862912 | Baker et al. | Oct 2014 | B2 |
8966134 | Anderson | Feb 2015 | B2 |
8976799 | Baker et al. | Mar 2015 | B1 |
20020010799 | Kubota et al. | Jan 2002 | A1 |
20020093935 | Denney et al. | Jul 2002 | A1 |
20030030720 | Hutchings | Feb 2003 | A1 |
20030137997 | Keating | Jul 2003 | A1 |
20040023645 | Olsen et al. | Feb 2004 | A1 |
20040080544 | Stripling | Apr 2004 | A1 |
20040115988 | Wu | Jun 2004 | A1 |
20040196682 | Funaba et al. | Oct 2004 | A1 |
20050025119 | Pettey et al. | Feb 2005 | A1 |
20050044236 | Stafford | Feb 2005 | A1 |
20050060470 | Main et al. | Mar 2005 | A1 |
20050060480 | Solomon | Mar 2005 | A1 |
20050111362 | Freytsis et al. | May 2005 | A1 |
20050147119 | Tofano | Jul 2005 | A1 |
20050182876 | Kim et al. | Aug 2005 | A1 |
20050238035 | Riley | Oct 2005 | A1 |
20050262269 | Pike | Nov 2005 | A1 |
20050281193 | Hofmeister et al. | Dec 2005 | A1 |
20060023386 | Palinkas et al. | Feb 2006 | A1 |
20060029038 | Jungck | Feb 2006 | A1 |
20060083518 | Lee et al. | Apr 2006 | A1 |
20060092928 | Pike et al. | May 2006 | A1 |
20060168387 | Gan et al. | Jul 2006 | A1 |
20060200600 | Groso | Sep 2006 | A1 |
20060206655 | Chappell et al. | Sep 2006 | A1 |
20060288098 | Singh et al. | Dec 2006 | A1 |
20070011536 | Khanna et al. | Jan 2007 | A1 |
20070025481 | Ryu et al. | Feb 2007 | A1 |
20070067654 | Adachi | Mar 2007 | A1 |
20070074891 | Burke | Apr 2007 | A1 |
20070086487 | Yasuda et al. | Apr 2007 | A1 |
20070111597 | Kondou et al. | May 2007 | A1 |
20070174733 | Boyd et al. | Jul 2007 | A1 |
20070208899 | Freking et al. | Sep 2007 | A1 |
20070266179 | Chavan et al. | Nov 2007 | A1 |
20080065738 | Landers et al. | Mar 2008 | A1 |
20080079462 | Chiu et al. | Apr 2008 | A1 |
20080091857 | McDaniel | Apr 2008 | A1 |
20080117909 | Johnson | May 2008 | A1 |
20080123672 | Wilkinson | May 2008 | A1 |
20080147898 | Freimuth et al. | Jun 2008 | A1 |
20080172501 | Goodart et al. | Jul 2008 | A1 |
20080195747 | Elmaliah | Aug 2008 | A1 |
20080222338 | Balasubramanian | Sep 2008 | A1 |
20080250175 | Sheafor | Oct 2008 | A1 |
20080256445 | Olch et al. | Oct 2008 | A1 |
20080266730 | Viborg et al. | Oct 2008 | A1 |
20080279186 | Winter et al. | Nov 2008 | A1 |
20080318348 | Grupen-Shemansky | Dec 2008 | A1 |
20090003335 | Biran et al. | Jan 2009 | A1 |
20090003361 | Bakthavathsalam | Jan 2009 | A1 |
20090006710 | Daniel et al. | Jan 2009 | A1 |
20090016348 | Norden et al. | Jan 2009 | A1 |
20090022176 | Nguyen | Jan 2009 | A1 |
20090037606 | Diab | Feb 2009 | A1 |
20090063701 | Bagepalli et al. | Mar 2009 | A1 |
20090070775 | Riley | Mar 2009 | A1 |
20090117754 | Fields et al. | May 2009 | A1 |
20090182917 | Kim | Jul 2009 | A1 |
20090222924 | Droz et al. | Sep 2009 | A1 |
20090279473 | Lu et al. | Nov 2009 | A1 |
20090301755 | Shintani | Dec 2009 | A1 |
20100014598 | Pfeifer | Jan 2010 | A1 |
20100046590 | Harper et al. | Feb 2010 | A1 |
20100085091 | Strazzieri et al. | Apr 2010 | A1 |
20100185792 | Yao et al. | Jul 2010 | A1 |
20100303442 | Newton et al. | Dec 2010 | A1 |
20110019383 | Aoyama et al. | Jan 2011 | A1 |
20110167187 | Crumlin et al. | Jul 2011 | A1 |
20110256756 | Lu et al. | Oct 2011 | A1 |
20110278043 | Ueda et al. | Nov 2011 | A1 |
20120005394 | Goodart et al. | Jan 2012 | A1 |
20120103651 | Kim | May 2012 | A1 |
20120104543 | Shahoian | May 2012 | A1 |
20120106018 | Shahoian et al. | May 2012 | A1 |
20120152613 | Kim et al. | Jun 2012 | A1 |
20120182223 | Zeng et al. | Jul 2012 | A1 |
20120226774 | Hochsprung | Sep 2012 | A1 |
20140220822 | Keyser et al. | Aug 2014 | A1 |
20140344615 | Cornelius et al. | Nov 2014 | A1 |
20140359319 | Baker et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
1168549 | Dec 1997 | CN |
1351356 | May 2002 | CN |
101010833 | Aug 2007 | CN |
101248559 | Aug 2008 | CN |
201215850 | Apr 2009 | CN |
201285827 | Aug 2009 | CN |
101803121 | Aug 2010 | CN |
202678638 | Jan 2013 | CN |
202797544 | Mar 2013 | CN |
1202419 | May 2002 | EP |
2090955 | Aug 2009 | EP |
57-064083 | Apr 1982 | JP |
H05-41255 | Feb 1993 | JP |
H08-265600 | Oct 1996 | JP |
H11-273790 | Oct 1999 | JP |
2000-077141 | Mar 2000 | JP |
2001-109697 | Apr 2001 | JP |
2003-189263 | Jul 2003 | JP |
2004-095518 | Mar 2004 | JP |
2004-126885 | Apr 2004 | JP |
2004-193090 | Jul 2004 | JP |
2005-521368 | Jul 2005 | JP |
2005-243446 | Sep 2005 | JP |
2005-309744 | Nov 2005 | JP |
2006-048594 | Feb 2006 | JP |
2007-086876 | Apr 2007 | JP |
2007-251779 | Sep 2007 | JP |
2007-535235 | Nov 2007 | JP |
2008-252310 | Oct 2008 | JP |
2009-076375 | Apr 2009 | JP |
2009-123561 | Jun 2009 | JP |
20090079879 | Jul 2009 | KR |
200303126 | Aug 2003 | TW |
589563 | Jun 2004 | TW |
I239127 | Sep 2005 | TW |
200627322 | Aug 2006 | TW |
200838085 | Sep 2008 | TW |
200909825 | Mar 2009 | TW |
2006102606 | Sep 2006 | WO |
2006102606 | Sep 2006 | WO |
2007099507 | Sep 2007 | WO |
2009039287 | Mar 2009 | WO |
2009039287 | Mar 2009 | WO |
2009046617 | Apr 2009 | WO |
20090866566 | Jul 2009 | WO |
2010051281 | May 2010 | WO |
2010051281 | May 2010 | WO |
2012003347 | Jan 2012 | WO |
2012003381 | Jan 2012 | WO |
2012003385 | Jan 2012 | WO |
Entry |
---|
Non-Final Office Action for U.S. Appl. No. 13/480,345, dated Apr. 1, 2013, 6 pages. |
Notice of Allowance for U.S. Appl. No. 12/239,743, dated Feb. 19, 2013, 18 pages. |
Notice of Allowance for U.S. Appl. No. 13/173,739, dated May 13, 2013, 11 pages. |
Notice of Allowance for U.S. Appl. No. 13/173,979, dated Jul. 11, 2012, 5 pages. |
Non-Final Office Action for U.S. Appl. No. 13/615,642, dated Apr. 12, 2013, 8 pages. |
Display Port, Wikipedia, the free encyclopedia, 4 pages; printed on Aug. 29, 2008 from http://en.wikipedia.org/wiki/Displayport; page states it was last modified on Aug. 25, 2008. |
Dopplinger, A., et al. “Using IEEE 1588 for synchronization of network-connected devices”, Mar. 29, 2007, from www.embedded.com/columns/technicalinsights/, 7 pages. |
Ethernet, Wikipedia, the free encyclopedia, 9 pages; printed on Aug. 17, 2008, from http://en.wikipedia.org/wiki/Ethernet; page states it was last modified on Aug. 17, 2008. |
Final Office Action for U.S. Appl. No. 12/239,742, dated Oct. 15, 2010, 14 pages. |
Final Office Action for U.S. Appl. No. 12/239,743, dated Nov. 12, 2010, 15 pages. |
IDT 24-Lane 3-Port PCI Express, 89HPES24N3 Data Sheet, Jul. 18, 2006, 30 pages. |
IEEE 1394 interface, Wikipedia, the free encyclopedia, 7 pages; printed on Jul. 24, 2008 from http://en.wikipedia.org/wiki/Firewire; page states it was last modified on Jul. 23, 2008. |
International Preliminary Report on Patentability for PCT Application No. PCT/US2011/042684, dated Jan. 17, 2013, 12 pages. |
International Preliminary Report on Patentability for PCT Application No. PCT/US2011/042634, dated Jan. 17, 2013, 13 pages. |
International Preliminary Report on Patentability for PCT Application No. PCT/US2011/042689, dated Jan. 17, 2013, 7 pages. |
International Search Report and Written Opinion, dated Jan. 31, 2012 for PCT Patent Application No. PCT/US2011/042684, 18 pages. |
International Search Report and Written Opinion, dated Nov. 30, 2011 for PCT Patent Application No. PCT/US2011/042634, 20 pages. |
International Search Report and Written Opinion, dated Sep. 28, 2011 for PCT Patent Application No. PCT/US2011/042689, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 12/239,742, dated Apr. 28, 2010, 14 pages. |
Non-Final Office Action for U.S. Appl. No. 12/239,742, dated Dec. 7, 2012, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 12/239,743 dated Jun. 21, 2012, 15 pages. |
Non-Final Office Action for U.S. Appl. No. 12/239,743, dated May 25, 2010, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 13/173,979, dated Mar. 15, 2012, 8 pages. |
Notice of Allowance for U.S. Appl. No. 13/033,562, dated Aug. 8, 2012, 6 pages. |
Office Action for European Patent Application No. 11743164.3, dated Mar. 5, 2013, 2 pages. |
Office Action for Japanese Patent Application No. 2012-543350, dated Nov. 19, 2012, in 4 pages. |
PCI Express Architecture, Chapter 3, Address Spaces & Transaction Routing, from PCIEX.book, pp. 105-152, Aug. 5, 2003. |
PCI Express Base Specification Revision 1.0a, Apr. 15, 2003, pp. 1-426. |
PCI Express, Wikipedia, the free encyclopedia, 11 pages; printed on Jul. 24, 2008 from http://en.wikipedia.org/wiki/PCI-Express; page states it was last modified on Jul. 16, 2008. |
PCI-X, Wikipedia, the free encyclopedia, 4 pages; printed on Sep. 9, 2008, from http://en.wikipedia.org/wiki/PCI-X; page states it was last modified on Sep. 4, 2008. |
Peer-to-peer, Wikipedia, the free encyclopedia, 11 pages; printed on Jul. 24, 2008, from http://en.wikipedia.org/wiki/Peer-to-peer; page states it was last modified on Jul. 24, 2008. |
Peripheral Component Interconnect, Wikipedia, the free encyclopedia, 7 pages; printed on Jul. 24, 2008, from http://en.wikipedia.org/wiki/PCI_%28bus%29; page states it was last modified on Jul. 23, 2008. |
Universal Serial Bus, Wikipedia, the free encyclopedia, 17 pages; printed on Jul. 24, 2008, from http://en.wikipedia.org/wiki/USB; page states it was last modified on Jul. 23, 2008. |
VESA DisplayPort Standard, Version 1, Revision 1a, Jan. 11, 2008, 238 pages. |
Notice of Allowance for Japanese Patent Application No. 2012-543350, dated Mar. 12, 2013, in 3 pages. |
Office Action for Japanese Patent Application No. 2012-541240, dated Oct. 26, 2012, 3 pages. |
Notice of Allowance for Japanese Patent Application No. 2012-541240, dated Apr. 30, 2013, 3 pages. |
Office Action for Chinese Patent Application No. 201120235164.4, dated May 4, 2012, with English translation, 2 pages. |
Notice of Allowance for Chinese Patent Application No. 201120235164.4, dated Sep. 17, 2012, with English translation, 4 pages. |
Notice of Allowance for Chinese Patent Application No. 201120235144.7, dated Mar. 1, 2012, with English Translation, 4 pages. |
Final Office Action dated Jul. 8, 2013 for U.S. Appl. No. 12/239,742, 14 pages. |
Non-Final Office Action dated Jul. 9, 2013 for U.S. Appl. No. 13/033,542, 16 pages. |
Non-Final Office Action dated Jul. 9, 2013 for U.S. Appl. No. 13/033,553, 17 pages. |
Office Action for Chinese Patent Application No. 201110189140.4, dated Aug. 19, 2013, 11 pages. |
Japanese Notice of Allowance dated Aug. 5, 2013 for JP Patent Application No. 2012-547345, 3 pages. |
Non-Final Office Action dated Sep. 9, 2013 for U.S. Appl. No. 13/249,260, 21 pages. |
Chinese Office Action dated Sep. 18, 2013 for CN Patent Application No. 201110189137.2, with English Translation, 14 pages. |
Chinese Office Action dated Sep. 24, 2013 for CN Patent Application No. 201110189138.7, with English Translation, 10 pages. |
Non-Final Office Action dated Oct. 3, 2013 for U.S. Appl. No. 13/403,209, 18 pages. |
Salvator, Dave; “Business Wire on Intel Announces Thunderbolt Technology,”; Feb. 24, 2013, 3 pages. |
Pang, Tiffany; TI Introduces High-Performance, Dual-Mode DisplayPort Switches and DHMI/DVI Level Translations; Connects new PC Video Standard to Monitors and TVs,; Mar. 11, 2008, 3 pages. |
Texas Instruments; “DisplayPort Switch,”; Feb. 2008, 25 pages. |
Texas Instruments; “DisplayPort Switch,”; Jan. 2008, revised Mar. 2008, 56 pages. |
Final Office Action for U.S. Appl. No. 13/615,642, dated Oct. 23, 2013, 11 pages. |
Notice of Allowance for U.S. Appl. No. 13/480,345, dated Oct. 30, 2013, 7 pages. |
Office Action for Korean Patent Application No. 10-2012-7032488, dated Oct. 31, 2013, with English translation, 6 pages. |
Non-Final Office Action for U.S. Appl. No. 12/239,742, dated Nov. 22, 2013, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 13/403,182, dated Dec. 20, 2013, 14 pages. |
Office Action for Taiwanese Patent Application No. 100123236, dated Feb. 19, 2014, with English translation, 4 pages. |
Office Action for Taiwanese Patent Application No. 100123233, dated Feb. 19, 2014, with English translation, 7 pages. |
Office Action for Taiwanese Patent Application No. 100123170, dated Feb. 20, 2014, with English translation, 13 pages. |
Office Action for Korean Patent Application No. 10-2012-7032475, dated Feb. 25, 2014, with English translation, 6 pages. |
Final Office Action for U.S. Appl. No. 13/033,553, dated Mar. 10, 2014, 16 pages. |
Office Action for Chinese Patent Application No. 201110189140.4, dated Mar. 28, 2014, 3 pages. |
Office Action for Korean Patent Application No. 10-2012-7032848, dated Apr. 30, 2014, with English translation, 5 pages. |
Notice of Allowance for U.S. Appl. No. 13/615,642, dated Apr. 30, 2014, 5 pages. |
Final Office Action dated May 23, 2014 for U.S. Appl. No. 13/403,209, 28 pages. |
Chinese Office Action dated May 26, 2014 for CN Patent Application No. 201110189137.2, with English Translation, 10 pages. |
Final Office Action for U.S. Appl. No. 13/403,182, dated Jun. 11, 2014, 13 pages. |
Chinese Office Action dated Jun. 12, 2014 for CN Patent Application No. 201110189138.7, with English Translation, 7 pages. |
Final Office Action for U.S. Appl. No. 12/239,742, dated Jul. 8, 2014, 19 pages. |
Office Action for EP Application No. 11743164.3, dated Aug. 1, 2014, 6 pages. |
Final Office Action dated Oct. 16, 2014 for U.S. Appl. No. 13/033,542, 20 pages. |
Notice of Allowance dated Oct. 17, 2014, for U.S. Appl. No. 13/403,182, 7 pages. |
Non-Final Office Action dated Nov. 5, 2014 for U.S. Appl. No. 14/218,877, 4 pages. |
Notice of Allowance dated Jan. 13, 2015 for U.S. Appl. No. 12/239,742, 12 pages. |
Non-Final Office Action dated Mar. 16, 2015 for U.S. Appl. No. 13/403,209, 35 pages. |
Taiwan Office Action dated Mar. 23, 2015 for TW Patent Application No. 100123170, with English translation, 9 pages. |
Notice of Allowance dated Apr. 13, 2015 for U.S. Appl. No. 13/033,542, 15 pages. |
Japanese Office Action dated Jul. 27, 2015 for JP Patent Application No. 2013-110372, with English summary, 6 pages. |
Non-Final Office Action dated Aug. 13, 2015 for U.S. Appl. No. 14/448,862, 10 pages. |
Final Office Action dated Jun. 3, 2015 for U.S. Appl. No. 14/218,877, 7 pages. |
Final Office Action dated Nov. 3, 2015 for U.S. Appl. No. 13/403,209, 35 pages. |
Notice of Allowance dated Oct. 22, 2015 for U.S. Appl. No. 14/218,877, 10 pages. |
Taiwan Office Action dated Dec. 2, 2015 for TW Patent Application No. 100123170, with English translation, 3 pages. |
Notice of Allowance dated Mar. 1, 2016, for U.S. Appl. No. 13/404,949, 9 pages. |
Final Office Action dated Mar. 31, 2016, for U.S. Appl. No. 14/448,862, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20150212966 A1 | Jul 2015 | US |
Number | Date | Country | |
---|---|---|---|
61446027 | Feb 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13403182 | Feb 2012 | US |
Child | 14629358 | US |