Some standalone computing devices may serve as a peripheral device for another computing device. For examples, the built-in display of an All-in-One (AiO) computer may serve as an additional display for another computer.
Some examples of the present application are described with respect to the following figures:
When a built-in display of an All-in-One (AiO) computer serves as an additional display for another computer, such as a notebook computer, peripheral device(s) connected to the AiO computer may not be shared by the other computer. Thus, reducing the usefulness of the peripheral device(s).
Examples described herein provide an input data switch to selectively route input data received at a first computing device (e.g., the AiO computer) between the first computing device and a second computing device (e.g., the notebook computer). Thus, the input data can be used to control the second computing device when the two computing devices are connected.
For example, a method may include establishing, via a first data communication interface of a first computing device, a physical connection to between the first computing device and a second computing device. The method may also include receiving, at the first computing device, input data via a second data communication interface of the first computing device. The method may further include controlling an operation at the first computing device based on the input data when the input data is received prior to establishing the connection. The method may further include routing the input data to the second computing device via an input data switch of the first computing device when the input data is received after establishing the connection.
In another example, a first computing device may include a controller. The first computing device may also include a first data communication interface to establish a connection between the first computing device and a second computing device. The first computing device may further include a second data communication interface to receive input data. The first computing device may further include an input data switch. The input data switch may, based on a detection of the connection, remove a data path between the controller and the second data communication interface. The input data switch may also, based on the detection, route the input data to the second communication device via the first communication interface. In this manner, examples described herein may reduce difficulty associated with sharing an input device between two connected computing devices.
First computing device 100 may include input data switch 102, a first data communication interface 104, a second data communication interface 106, and a controller 108. Input data switch 102 may selectively route input data received at first computing device 100 to controller 108 or to a second computing device. Input data switch 102 may selectively route the input data based on whether the second computing device is connected or docked to first computing device 100. Input data switch 102 may be connected to first data communication interface 104, second data communication interface 106, controller 108, or a combination thereof.
Data communication interfaces 104 and 106 may be any type of physical port that enables electronic communication between first computing device and other devices. Controller 108 may be, for example, a central processing unit (CPU), a semiconductor-based microprocessor, and/or other hardware devices suitable for retrieval and execution of instructions stored in a computer-readable storage medium.
During operation, first computing device 100 may not be connected to another computing device via first data communication interface 104. Input data switch 102 may establish a data path between second data communication interface 106 and controller 108. Data communication interfaces 104 and 106 may be logically isolated from each other. First computing device 100 may receive input data 110 at second data communication interface 106. For example, first computing device 100 may receive input data 110 from an input device (not shown in
Second computing device 112 may be connected to first computing device 100 via first data communication interface 104. In some examples, second computing device 112 may be docked to a docking station (not shown in
In response to detecting signal 114 at input data switch 102, input data switch 102 may disable the data path between second data communication interface 106 and controller 108. Input data switch 102 may also establish a second data path between data communication interfaces 104 and 106. Thus, first data communication interface 104 may be logically bridged to second data communication interface 106 via input data switch 102. When first computing device receives input data 116 at second data communication interface 106, input data switch 102 may route input data 116 from second data communication interface 106 to second computing device 112 via first data communication interface 104. Second computing device 112 may process input data 116 to control operations of second computing device 112 and/or first computing device 100.
When input data switch 102 does not detect enable signal 204, input data switch 102 may only route input data (e.g., input data 110, input data 116) from second data communication interface 106 to controller 108. When input data switch 102 detects enable signal 204, input data switch 102 may change how input data received at second data communication interface 106 is routed based on the presence of signal 114.
In some examples, first computing device 100 may also include a display 206. When second computing device 112 is connected to first computing device 100, display 206 may serve as a display for second computing device 112.
First data communication interface 104 may be connected to a data port 306 of first multiplexer 302. First data communication interface 104 may also be connected to a selector port 308 of first multiplexer 302. Controller 108 may be connected to first multiplexer 302 via a data port 310 of first multiplexer 302. Second multiplexer 304 may be connected to first multiplexer 302 via a data port 312 of first multiplexer 302.
Second data communication interface 106 may be connected to a data port 314 of second multiplexer 304. First data communication interface 104 may also be connected to a selector port 316 of first multiplexer 302. Controller 108 may be connected to second multiplexer 304 via a data port 318 of second multiplexer 304. Second multiplexer 304 may be connected to first multiplexer 302 via a data port 320 of second multiplexer 304. Connections between first data communication interface 104 and selector ports 308 and 316 may be unidirectional. Connections to data ports of each multiplexer 302 and 304 may be bidirectional.
During operation, multiplexers 302 and 304 may detect the presence of signal 114 via selector ports 308 and 316, respectively. When signal 114 is absent, first multiplexer 302 may connect data port 306 to data port 310 so that a data path is established between first data communication interface 104 and controller 108. Thus, first multiplexer 302 may route input data received at first data communication interface 104 to controller 108 for processing. When signal 114 is absent, second multiplexer 304 may connect data port 314 to data port 318 to establish a data path between second data communication interface 106 and controller 108. Thus, second multiplexer 304 may route input data received at second data communication interface 106 to controller 108 for processing.
In response to detecting signal 114 at selector port 308, first multiplexer 302 may connect data port 306 to data port 312. Thus, the data path between first data communication interface 104 and controller 108 may be removed. In response to detecting signal 114 at selector port 316, second multiplexer 304 may connect data port 314 to data port 320. Thus, the data path between second data communication interface 106 and controller 108 may be removed. Also, by connecting data port 306 to data port 312 and connecting data port 314 to data port 320, a data path between first data communication interface 104 and second data communication interface 106 may be established. Thus, input data (e.g., input data 110, input data 116) received at second data communication interface 106 may be routed to second computing device 112.
Operations of third multiplexer 504 may be similar to operations of multiplexers 302 and 304. Thus, when signal 114 is detected by multiplexers 302, 304, and 504, multiplexers 304 and 504 may route input data received at data communication interfaces 106 and 502, respectively, to second computing device 112 via first data communication interface 104.
Method 600 also includes receiving, at the first computing device, input data via a second data communication interface of the first computing device, at 604. For example, referring to
Method 600 further includes controlling an operation at the first computing device based on the input data when the input data is received prior to establishing the connection, at 606. For example, referring to
Method 600 further includes routing the input data to the second computing device via the first data communication interface when the input data is received after establishing the connection, at 608. For example, referring to
The use of “comprising”, “including” or “having” are synonymous and variations thereof herein are meant to be inclusive or open-ended and do not exclude additional unrecited elements or method steps.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2017/030340 | 5/1/2017 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2018/203869 | 11/8/2018 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5831447 | Chaw | Nov 1998 | A |
6073188 | Fleming | Jun 2000 | A |
6098120 | Yaotani | Aug 2000 | A |
6125417 | Bailis | Sep 2000 | A |
6363452 | Lach | Mar 2002 | B1 |
6377082 | Loinaz et al. | Apr 2002 | B1 |
6765543 | Masuda | Jul 2004 | B1 |
7133938 | Nagao | Nov 2006 | B2 |
8190785 | Hill | May 2012 | B2 |
8484403 | Wu et al. | Jul 2013 | B2 |
8769172 | Softer | Jul 2014 | B2 |
9053250 | Halim | Jun 2015 | B2 |
9477437 | Ferry et al. | Oct 2016 | B2 |
20030115395 | Karcher | Jun 2003 | A1 |
20030167367 | Kaushik | Sep 2003 | A1 |
20040044822 | Chen | Mar 2004 | A1 |
20070065157 | Katagiri et al. | Mar 2007 | A1 |
20070116038 | Holt | May 2007 | A1 |
20090234983 | Golden et al. | Sep 2009 | A1 |
20100257380 | Huang | Oct 2010 | A1 |
20110113166 | Hung et al. | May 2011 | A1 |
20110153871 | Ferragut, II | Jun 2011 | A1 |
20130166629 | Ivashin et al. | Jun 2013 | A1 |
20140019652 | Soffer | Jan 2014 | A1 |
20140289431 | Chien | Sep 2014 | A1 |
20150227485 | Maung | Aug 2015 | A1 |
20150234764 | Kline | Aug 2015 | A1 |
Number | Date | Country |
---|---|---|
1313701 | Sep 2001 | CN |
103116386 | May 2013 | CN |
105378692 | Mar 2016 | CN |
105871586 | Aug 2016 | CN |
2518206 | Mar 2015 | GB |
Entry |
---|
Hirofuchi et al., “USB/IP—A Peripheral Bus Extension for Device Sharing Over IP Network”, USENIX, Retrieved from Internet—http://static.usenix.org/legacy/events/usenix05/tech/freenix/hirofuchi/hirofuchi_html/, 2005, 16 Pages. |
Number | Date | Country | |
---|---|---|---|
20200379940 A1 | Dec 2020 | US |