GB2542562A - Private access to HID - Google Patents
Private access to HID Download PDFInfo
- Publication number
- GB2542562A GB2542562A GB1516692.9A GB201516692A GB2542562A GB 2542562 A GB2542562 A GB 2542562A GB 201516692 A GB201516692 A GB 201516692A GB 2542562 A GB2542562 A GB 2542562A
- Authority
- GB
- United Kingdom
- Prior art keywords
- user application
- mobile device
- communication interface
- display device
- hids
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004891 communication Methods 0.000 claims abstract description 52
- 238000000034 method Methods 0.000 claims abstract description 27
- 238000000115 helium ionisation detection Methods 0.000 claims abstract description 18
- 238000003032 molecular docking Methods 0.000 claims abstract description 15
- 230000003993 interaction Effects 0.000 claims abstract description 7
- 238000012545 processing Methods 0.000 claims description 14
- 239000000872 buffer Substances 0.000 claims description 7
- 241000699666 Mus <mouse, genus> Species 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 4
- 238000009434 installation Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000002156 mixing Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
- G06F3/038—Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/16—Constructional details or arrangements
- G06F1/1613—Constructional details or arrangements for portable computers
- G06F1/1632—External expansion units, e.g. docking stations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/10—Program control for peripheral devices
- G06F13/102—Program control for peripheral devices where the programme performs an interfacing function, e.g. device driver
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4063—Device-to-bus coupling
- G06F13/4068—Electrical coupling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
- G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
- G06F3/0416—Control or interface arrangements specially adapted for digitisers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0489—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using dedicated keyboard keys or combinations thereof
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
Abstract
A method of communication between a human interface device (HID) and a mobile device 11 (e.g. tablet, smart phone or smart watch) comprises: operating, on a mobile device, an operating system 21 providing an execution space for applications and a user application 22 in the execution space. The user application detects a connection of an external display device 12 to the mobile device via a communication interface 23 (e.g. a hub or docking station) of the mobile device, controls the communication interface of the mobile device, sends image data for display on the external display device, detects a connection of one or more HIDs to the mobile device via the communication interface, communicates with the one or more HIDs using the communication interface; and shows any visible results of interaction with the one or more HIDs in the image data to be sent to the external display device. The user application can operate independently of the operating system and can control the communication interface via a private interface 27, not accessible by the operating system. Other HIDs can also be connected to the mobile device by the communications interface.
Description
Private Access to HID
Background
As mobile devices such as smartphones, tablet computers and even wearable devices such as smart watches become more powerful, it is becoming increasingly common for users to wish to use such devices in place of conventional computing devices such as PCs, especially in a hotdesking environment. However, most mobile devices only have small integral displays and are not provided with keyboards, mice or other human interface (input) devices (“HIDs”) associated with desktop computers. It is therefore desirable to connect such devices to a mobile device that is being used as a computer in order to increase ease of use.
In order to connect a human interface device to a mobile device, the mobile device needs to provide various drivers to be able to connect to the various interface devices. Conventionally, such drivers, when present, must be incorporated into the code of the mobile device’s operating system. This requires co-operation between multiple manufacturers and possibly designers of operating systems and is difficult due to the wide variety of human interface devices for which drivers would need to be provided. Alternatively, if it is required to add a driver later, it usually requires an upgrade of the full operating system into which the driver is incorporated. This means that it is difficult to add suitable drivers to mobile devices to allow HIDs to be connected.
The invention attempts to solve or at least mitigate this problem.
Brief Summary of the Invention
According to a first aspect of the invention, there is provided a method of communication between a human interface device, HID, and a mobile device, the method comprising: operating, on a mobile device, an operating system providing an execution space for applications; operating, on the mobile device, a user application in the execution space; detecting, by the user application, a connection of an external display device to the mobile device via a communication interface of the mobile device; controlling, by the user application, the communication interface of the mobile device; sending, by the user application, image data for display on the external display device; detecting, by the user application, a connection of one or more HIDs to the mobile device via the communication interface; communicating, by the user application, with the one or more HIDs using the communication interface; and showing, by the user application, any visible results of interaction with the one or more HIDs in the image data to be sent to the external display device.
Thus, by installing an application on the mobile device, no drivers for the HID need be specifically incorporated into the operating system. This is beneficial because it allows the user application to control other devices alongside the external display device without having to set up a second connection. Furthermore, the communication interface with the connected HID - for example, a mouse - will be entirely within the user application and the operating system will not be aware of the nature or origins of the input data from the mouse and will not interact with it, removing the need for drivers, which are effectively provided within the user application itself.
In a preferred embodiment, the method further comprises: granting, by the operating system, memory space to the user application when the user application is executed in the execution space; and creating, by the user application, a frame buffer within the memory space and storing the image data to be sent to the external display device therein.
Preferably, the user application is able to send image data to the display device without any interaction with the operating system of the mobile device. This minimises interaction with the operating system and therefore necessary changes to the operating system. However, the user application may pass completed image data to the operating system to be output to the display device. Each of a number of applications within a family of applications seeking to take advantage of this invention could have its own interface with the connected HIDs. This is not problematic as most mobile devices only run one application at a time in any case and it may therefore be beneficial as it ensures clarity as to which application has control of the HID at any time.
According to a second aspect of the invention, there is provided a mobile device arranged to carry out the first aspect of the invention.
Advantageously, there may be provided only one connection port for external devices, which can be connected to a hub which in turn may be connected to multiple external devices. This is advantageous because it is desirable to have as few connection ports in a mobile device as possible in order to minimise size and maximise the strength of the device’s case. The hub may be embodied as part of a desktop docking station.
The connection port or ports may be embodied as a capability for a wireless data connection and, accordingly, all connections may be either wired or wireless.
Short Description of the Drawings
An embodiment of the invention will now be more fully described, by way of example, with reference to the drawings, of which:
Figure 1 shows a basic schematic of an embodiment of the whole system;
Figure 2 shows a more detailed schematic of the mobile device and hub shown in Figure 1, together with software components, especially those responsible for the production of image data;
Figure 3 shows a similar schematic of the mobile device and hub to Figure 2, together with software components responsible for receiving user input; and
Figure 4 shows a flow chart of the process followed by the application.
Detailed Description of the Drawings
Figure 1 shows a mobile device [11] connected to a docking station [12], The connection may be wired or wireless and may be over a network, including the internet, as long as it is capable of carrying general-purpose data. For the purpose of the embodiment shown in these diagrams, the connection is wireless via Wi-Fi.
The docking station [12] is in turn connected to a display device [13], keyboard [14], and mouse [15], In this example, the connections between the docking station [12] and the human interface devices [14, 15] are all one-way: the keyboard [14] and mouse [15] provide input data only. The connection with the display device [13] could be one-way, or, where the display device [13] incorporates a touchscreen, the connection to the display device [13] could be two-way. However, since the data would be travelling along different lanes within the same connection, these lanes could be treated as two one-way connections and the principle is the same.
The intention is for the mobile device [11] to be able to supply display data to the display device [13] while receiving user input from the mouse [14] and keyboard [15] and also incorporating this into the display data transmitted to the display device [13], Although it is known to transmit display data from a mobile device [11] to a display device [13], it is not known to receive external input through the same communication interface connection.
Figure 2 shows a detail of the same mobile device [11], connected to the same docking station [12], The human interface devices [14, 15] and the display device [13] are still present as shown in Figure 1, but they are not shown here for clarity.
Two software components [21, 22] are shown running on the mobile device. In practice these are likely to be running simultaneously on the same processor and using the same main memory space, but they are shown separately for clarity. The first software component [21] is the main operating system of the mobile device [11], Conventionally, this would need to be amended either at manufacture and original installation or by the installation of a driver in order to allow the user to connect any particular HID, and to connect to a display device. However, according to particular embodiments of the invention, the operating system [21] is not involved in interaction with the HIDs or the display device as this is handled within an application. This is shown as the second software component [22] in Figure 2.
Figure 2 shows only the elements of the application [22] used in the production and transmission of display data. These elements [24, 25, 26] are shown as three parts within the application [22], although in practice they will be running together and using the same memory allocated by the operating system [21] for the use of the application [22], in the same way as the application [22] and operating system [21] are not in fact stored and run separately but are here shown separately as described above. There may be other components in the application [22], depending on its functionality, but these are not here shown.
The first [24] of the three elements is a software component that generates display data (a “display component”). It then passes this data to the second component [25], which processes the data to make it suitable for display (the “processing component”). This may include blending different types of display data or display data from different sources, colour correction and processing, scaling according to the resolution of the display device [13], and other functions. The aim of this component is to produce a frame, which may be stored in a frame buffer in memory space allocated to the application [22], or may be passed directly to the third element [26] (the “output component”): a component that transmits the finished data to the communication interface [23] of the mobile device [11],
The application [21] is able to communicate with the communication interface [23] through a private interface [27], On most mobile devices only one application will be active at a time, so the active application [21] may be able to entirely monopolise the communication interface [23] so that not even the operating system [21] is able to communicate with it. In other cases, the application [22] may only monopolise some part of the communication interface’s [23] functionality. In any case, the private interface [27] may be inaccessible to the operating system [21] or any other application.
In this embodiment, the output component [26] streams display data directly to the communication interface [23], although in other embodiments there may be an intervening area of memory that acts as a flow buffer. The communication interface [23] then converts the flow of display data to Wi-Fi packets and transmits them to the docking station [12], which is able to perform any further processing and transmit them on to the display device [13]·
The communication interface [23] is capable of both transmitting and receiving data and, as previously mentioned, the application [22] has a private interface [27] with it. This means that the communication interface [23] can be used for data transmission in both directions.
Figure 3 once again shows the same mobile device [11] and docking station [12], the mobile device [11] including the same operating system [21], application [22], and communication interface [23], In Figure 3, only one component [31] of the application [22] is shown: the input component [31], This is in communication with the communication interface [23] via the private interface [17], but, as is shown by the arrows, the communication interface [23] receives data from the two input devices [14, 15] and sends it to the input component [31],
The input component [31] is in communication with both the application’s [22] local memory and the processing component [25], This means that data received through the private interface [27] can be placed in memory if appropriate - for example, words being typed into a document - and the changes to the display data such as movement of a cursor can be immediately reflected in the display data output by the application [22], For this reason, these methods and adaptations to the mobile device [11] are most suitable for input data that causes a visible change in the display output.
Figure 4 shows the overall process starting from the launch of the application [22], The application [22] will have been previously installed and will be aware of the existence of the communication interface [23] and how to communicate with it - this is information that could be requested from the communication interface [23] itself or read from the operating system [21] upon installation.
At Step S41, the application [22] is launched. This may be by user choice or as the result of an automatic process. It then creates the private interface [27] with the communication interface [23] at Step S42. As part of this, or separately, it will query the capabilities of any connected display device or, as in this case, docking station [12], in which case it will send querying messages on through the docking station [12] to the display device [13], It will use the results of these queries, such as resolution, number of display devices, refresh rate, etc., to inform the behaviour of the components [24, 25, 26] within the application [22], especially the processing component [25] and the output component [26],
It will also query for any other peripherals [14, 15] connected either to a docking station [12] or, in some cases, directly to the communication interface [23], If there are such peripherals [14, 15], as here, it will configure itself to receive input from them through the private interface [27], which otherwise would only be configured to transmit data. In all cases, the communication interface [23] is unaware of the nature of the data being transmitted; it is just packaging it as a general-purpose format and transmitting it across a general-purpose connection: in this case, Wi-Fi.
At Step S43, the display component [24] begins generating display data.
At this stage, the user may use the keyboard [14] or mouse [15] to input data. This is unlikely to occur on every frame, so this is not handled as part of the main process, although the application [22] will be constantly listening for such input. It will also listen for the connection of a new HID and, upon receiving a signal indicating that a device has been connected to the docking station [12], it will query that device as described at Step S42. If there was originally only a display device [13], the application [22] will then return to Step S42 and re-configure the private interface [27] to be able to receive data as well as transmitting it.
If, at Step S43, the user inputs data, the process will follow the branch labelled ‘A’ and indicated as optional by the dotted boxes and arrows. Otherwise, the process will move directly to Step S44.
At Step S4A1, the user has input data by, for example, typing on the keyboard [14], This data is transmitted from the keyboard [14] to the interface engine [23] of the mobile device [11], via the docking station [12] to which they are both connected as aforementioned. The interface engine [23] is not aware of the nature of the data but just removes the Wi-Fi packaging and directs it to the application [22] to which it is addressed, along the private interface [27], at Step S4A2.
When the application [22] receives the user input, it is aware of the source and type of the input - this may be contained in internal packet headings, for example. There may also be specific packets containing an indication of an expected reaction. For example, a mouse movement and click may be transmitted in a signal that contains the new location and the fact that the mouse was clicked at that location. The application [22] then reacts to that input at Step S4A3. This may mean, for example, placing a piece of data in memory, or altering the display data generated by the display component [24],
In either case, the processing component [25] of the application [22] produces a complete frame of display data at Step S44. If there is no user input, the processing component [25] will produce a frame entirely comprising the output from the display component [24], If there is user input, the processing component [25] will amend the output from the display component [24] appropriately, for example by adding a letter at the appropriate location in response to a key-press on the keyboard [14], When the frame is complete, the processing component [24] stores it in a frame buffer in the memory space and passes it to the output component [26], which will in turn pass it to the communication interface [23],
At Step S45, the frame is then transmitted to the communication interface [23] as previously described. The communication interface [23] is not aware that it is display data, but will package it as general-purpose Wi-Fi data and may also compress and encrypt it. It then transmits it to the docking station [12], where it may be decompressed and decrypted if appropriate and may also undergo further processing; for example, it may require rescaling prior to transmission to the display device [13], When this is complete, it is transmitted to the display device [13] in the appropriate format and displayed.
As long as the application [22] is running, the steps between Step S43 and S45 inclusive, including Steps S4A1 to S4A3 as appropriate, will repeat. They may be pipelined such that the processing component [25] is producing a frame simultaneously with the interface engine [23] transmitting the previous frame, for example, and if one or more frame buffers are provided in memory then one or more frames may be stored prior to transmission, resulting in the communication interface [23] transmitting a frame multiple frames ahead of the frame currently being produced by the processing component [25],
At Step S46, the application [22] ends. This may be automatically or due to user input, and will result in the removal of resources dedicated to the application [22], This includes the return of memory to a central pool under the control of the operating system [21], but will also include the removal of the private interface [27], This means that the application [22] will no longer be monopolising the use of the communication interface [23] and this can be used by the operating system [21] or another application. It also means that the display device [13], mouse [15], and keyboard [14] will cease to function until the application is launched again.
An application can use this process to use appropriate peripherals without any modification to the operating system running on the mobile device. This makes deployment of such functionality more straightforward.
Claims (13)
1. A method of communication between a human interface device, HID, and a mobile device, the method comprising: operating, on a mobile device, an operating system providing an execution space for applications; operating, on the mobile device, a user application in the execution space; detecting, by the user application, a connection of an external display device to the mobile device via a communication interface of the mobile device; controlling, by the user application, the communication interface of the mobile device; sending, by the user application, image data for display on the external display device; detecting, by the user application, a connection of one or more HIDs to the mobile device via the communication interface; communicating, by the user application, with the one or more HIDs using the communication interface; and showing, by the user application, any visible results of interaction with the one or more HIDs in the image data to be sent to the external display device.
2. A method according to claim 1, wherein the communication interface comprises one or more ports on the mobile device for connection directly to the external device and the one or more HIDs.
3. A method according to claim 1, wherein the communication interface comprises a port on the mobile device for connection to the external device and the one or more HIDs via a hub.
4. A method according to claim 3, wherein the hub comprises a docking station.
5. A method according to claim 1, wherein the communication interface comprises a wireless interface for wireless communication with the external display device and the one or more HIDs.
6. A method according to any preceding claim, further comprising: granting, by the operating system, memory space to the user application when the user application is executed in the execution space; and creating, by the user application, a frame buffer within the memory space and storing the image data to be sent to the external display device therein.
7. A method according to any preceding claim, further comprising: closing operation of the user application in the execution space; operating, on the mobile device, a second user application in the execution space; detecting, by the second user application, a connection of the external display device to the mobile device via the communication interface of the mobile device; controlling, by the second user application, the communication interface of the mobile device; sending, by the second user application, the image data for display on the external display device; detecting, by the second user application, a connection of a second HID to the mobile device via the communication interface; communicating, by the second user application, with the second HID using the communication interface; and showing, by the second user application, any visible results of interaction with the second HID in the image data to be sent to the external display device.
8. A method according to any preceding claim, further comprising: granting, by the operating system, second memory space to the second user application when the second user application is executed in the execution space; and creating, by the second user application, a second frame buffer within the memory space and storing the image data to be sent to the external display device therein.
9. A method according to any preceding claim, wherein the image data is sent by the user application to the external display device via the communication interface.
10. A method according to any preceding claim, wherein the one or more HIDs comprises one or more of a mouse and a keyboard.
11. A method of communication substantially as hereinbefore described with reference to the drawings.
12. A mobile device configured to perform all the steps of a method according to any one of the preceding claims.
13. A computer readable medium including executable instructions which, when executed in a processing system, cause the processing system to perform all the steps of a method according to any one of claims 1 to 11.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB1516692.9A GB2542562B (en) | 2015-09-21 | 2015-09-21 | Private access to HID |
| US15/761,806 US20180253155A1 (en) | 2015-09-21 | 2016-09-21 | Private access to human interface devices |
| PCT/GB2016/052937 WO2017051171A1 (en) | 2015-09-21 | 2016-09-21 | Private access to human interface devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB1516692.9A GB2542562B (en) | 2015-09-21 | 2015-09-21 | Private access to HID |
Publications (3)
| Publication Number | Publication Date |
|---|---|
| GB201516692D0 GB201516692D0 (en) | 2015-11-04 |
| GB2542562A true GB2542562A (en) | 2017-03-29 |
| GB2542562B GB2542562B (en) | 2018-06-27 |
Family
ID=54544558
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB1516692.9A Active GB2542562B (en) | 2015-09-21 | 2015-09-21 | Private access to HID |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US20180253155A1 (en) |
| GB (1) | GB2542562B (en) |
| WO (1) | WO2017051171A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3472806A4 (en) | 2016-06-17 | 2020-02-26 | Immersive Robotics Pty Ltd | Image compression method and apparatus |
| AU2018217434C1 (en) | 2017-02-08 | 2023-04-27 | Immersive Robotics Pty Ltd | Displaying content to users in a multiplayer venue |
| AU2018372561B2 (en) | 2017-11-21 | 2023-01-05 | Immersive Robotics Pty Ltd | Image compression for digital reality |
| AU2018373495B2 (en) | 2017-11-21 | 2023-01-05 | Immersive Robotics Pty Ltd | Frequency component selection for image compression |
| IT201900023646A1 (en) * | 2019-12-11 | 2021-06-11 | Alessandrino Alessandra Ditta Individuale | INTERFACE SYSTEM FOR MOBILE DEVICES AND COLUMN STATION INCLUDING SAID INTERFACE SYSTEM |
| TWI760006B (en) * | 2020-12-14 | 2022-04-01 | 華碩電腦股份有限公司 | Electronic device, control method, and computer program product thereof |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070080934A1 (en) * | 2005-10-11 | 2007-04-12 | Elaine Chen | Human interface input acceleration system |
| US20120264413A1 (en) * | 2009-12-07 | 2012-10-18 | Francois Olivier | Office system comprising a telephony application |
| US20140019866A1 (en) * | 2012-07-16 | 2014-01-16 | Oracle International Corporation | Human interface device input handling through user-space application |
| WO2014073825A1 (en) * | 2012-11-09 | 2014-05-15 | Lg Electronics Inc. | Portable device and control method thereof |
| US20140337748A1 (en) * | 2013-05-09 | 2014-11-13 | Samsung Electronics Co., Ltd. | Method and apparatus for displaying user interface through sub device that is connectable with portable electronic device |
| US20140340309A1 (en) * | 2013-05-20 | 2014-11-20 | Samsung Electronics Co., Ltd. | Method and apparatus for processing touch input in mobile terminal |
| US20150109262A1 (en) * | 2012-04-05 | 2015-04-23 | Pioneer Corporation | Terminal device, display device, calibration method and calibration program |
| EP2891959A2 (en) * | 2014-01-02 | 2015-07-08 | Samsung Electronics Co., Ltd | Method and apparatus for controlling electronic devices in proximity |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH08180001A (en) * | 1994-04-12 | 1996-07-12 | Mitsubishi Electric Corp | Communication system, communication method and network interface |
| US20040085290A1 (en) * | 2002-11-06 | 2004-05-06 | Bryan Scott | Manipulating the position of a horizontal-vertical visual indicator on a PDA display via a one-hand manual screen horizontal-vertical visual indicator device |
| US20050099395A1 (en) * | 2003-11-06 | 2005-05-12 | Marsden Randal J. | Assistive technology interface |
| US20050219210A1 (en) * | 2004-03-31 | 2005-10-06 | The Neil Squire Society | Pointer interface for handheld devices |
| US7660939B2 (en) * | 2004-07-30 | 2010-02-09 | Virinci Technologies, Inc. | Operating system arrangement for flexible computer system design |
| US8165633B2 (en) * | 2007-07-16 | 2012-04-24 | Microsoft Corporation | Passive interface and software configuration for portable devices |
| US9241062B2 (en) * | 2009-05-20 | 2016-01-19 | Citrix Systems, Inc. | Methods and systems for using external display devices with a mobile computing device |
| WO2011132652A1 (en) * | 2010-04-19 | 2011-10-27 | 株式会社Ｄａｐリアライズ | Portable information processing device equipped with touch panel means and program for said portable information processing device |
| US9383772B2 (en) * | 2013-05-16 | 2016-07-05 | I/O Interconnect, Ltd. | Docking station with KVM switch |
| US9596319B2 (en) * | 2013-11-13 | 2017-03-14 | T1V, Inc. | Simultaneous input system for web browsers and other applications |
-
2015
- 2015-09-21 GB GB1516692.9A patent/GB2542562B/en active Active
-
2016
- 2016-09-21 US US15/761,806 patent/US20180253155A1/en not_active Abandoned
- 2016-09-21 WO PCT/GB2016/052937 patent/WO2017051171A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070080934A1 (en) * | 2005-10-11 | 2007-04-12 | Elaine Chen | Human interface input acceleration system |
| US20120264413A1 (en) * | 2009-12-07 | 2012-10-18 | Francois Olivier | Office system comprising a telephony application |
| US20150109262A1 (en) * | 2012-04-05 | 2015-04-23 | Pioneer Corporation | Terminal device, display device, calibration method and calibration program |
| US20140019866A1 (en) * | 2012-07-16 | 2014-01-16 | Oracle International Corporation | Human interface device input handling through user-space application |
| WO2014073825A1 (en) * | 2012-11-09 | 2014-05-15 | Lg Electronics Inc. | Portable device and control method thereof |
| US20140337748A1 (en) * | 2013-05-09 | 2014-11-13 | Samsung Electronics Co., Ltd. | Method and apparatus for displaying user interface through sub device that is connectable with portable electronic device |
| US20140340309A1 (en) * | 2013-05-20 | 2014-11-20 | Samsung Electronics Co., Ltd. | Method and apparatus for processing touch input in mobile terminal |
| EP2891959A2 (en) * | 2014-01-02 | 2015-07-08 | Samsung Electronics Co., Ltd | Method and apparatus for controlling electronic devices in proximity |
Also Published As
| Publication number | Publication date |
|---|---|
| GB201516692D0 (en) | 2015-11-04 |
| GB2542562B (en) | 2018-06-27 |
| WO2017051171A1 (en) | 2017-03-30 |
| US20180253155A1 (en) | 2018-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180253155A1 (en) | Private access to human interface devices | |
| US7752633B1 (en) | Cross-platform event engine | |
| US10353718B2 (en) | Providing access to a remote application via a web client | |
| WO2020238425A1 (en) | Application starting method and apparatus | |
| US8681811B2 (en) | System and method for obtaining cross compatibility with a plurality of thin-client platforms | |
| US9201814B2 (en) | Electronic devices and methods for sharing peripheral devices in dual operating systems | |
| KR20130096059A (en) | Displaying method of remote sink device, source device and system for the same | |
| US10223302B2 (en) | Systems and methods for implementing a user mode virtual serial communications port emulator | |
| EP2854038A1 (en) | System and method for interconnecting user terminal and external device | |
| US20170031680A1 (en) | Computer-implemented method and system for executing android apps natively on any environment | |
| WO2019161691A1 (en) | Method and apparatus for self-adaptively parsing touch data, and device and storage medium | |
| US20120166585A1 (en) | Apparatus and method for accelerating virtual desktop | |
| WO2019072213A1 (en) | Wireless access point information processing method, device and computer readable storage medium | |
| US10637827B2 (en) | Security network system and data processing method therefor | |
| US9411760B2 (en) | System and method for a thin-client terminal system with a local screen buffer using a serial bus | |
| KR20130062078A (en) | Method for providing image adapted to resolution of external display apparatus in mobile device | |
| US20170142245A1 (en) | Electronic apparatus with shareable input devices and input device sharing method thereof | |
| CN114116263A (en) | System, method, apparatus, and medium for multi-page tag communication in a browser | |
| KR20110069443A (en) | Application service system based on user interface virtualization and method thereof | |
| WO2019127475A1 (en) | Method and apparatus for implementing virtual sim card, storage medium, and electronic device | |
| KR101284791B1 (en) | Method and apparatus for implementing computer operating system using mobile terminal | |
| JP4007452B2 (en) | System and program for displaying device information using browser | |
| EP3872630A2 (en) | Request processing method and apparatus, electronic device, and computer storage medium | |
| US20230034475A1 (en) | System service sharing between endpoint devices for increased endpoint device capability | |
| WO2021005978A1 (en) | Arithmetic device and data transmission method |