In particular embodiments, a computing device may receive device data from a client device. The computing device may encode the data for transmission to a remote desktop client. The re-encoding may be performed according to a pre-defined import/export protocol.
Legal claims defining the scope of protection, as filed with the USPTO.
1. A method comprising: attaching a transcoding service to a hypertext markup language (HTML) client device; and by the transcoding service, interfacing a web browser of the client device with a remote desktop extension protocol; allowing the client device to connect to a remote desktop protocol (RDP) server; importing and exporting at least one of a graphical device interface, one or more virtual channels, and one or more input/output devices to the client device; provisioning and serializing one or more operating system function calls to allow for end-to-end communication between the client device and the RDP server when the client device and the RDP server utilize incompatible communication protocols; providing an interface to and from the client device by a hypertext markup language (HTML) compatible stream service of the transcoding service; reconstructing or unpacking, by the HTML compatible stream service, one or more remote client tasks to and from a remote desktop protocol; receiving device data from the client device; and encoding the device data for transmission to a transcoding remote desktop client with a particular port, the encoding being performed according to a pre-defined import/export protocol.
2. The method of claim 1 , wherein the device data comprises input/output data from the client device.
3. The method of claim 1 , wherein the client device comprises one or more of: a mouse; a touch device; a keyboard; a display; a speaker; or a microphone.
4. The method of claim 1 , wherein the import/export protocol is HTML5-compatible.
5. The method of claim 1 , wherein the device data comprises a rendering associated with the client device.
6. The method of claim 1 , wherein the client device is a remote desktop protocol client.
7. The method of claim 6 , wherein the remote desktop protocol client is launched by a generic client engine.
8. One or more computer-readable non-transitory storage media embodying software that is operable when executed to: by a transcoding service attached to a hypertext markup language (HTML) client device, interface a web browser of the client device with a remote desktop extension protocol; allow the client device to connect to a remote desktop protocol (RDP) server; import and export at least one of a graphical device interface, one or more virtual channels, and one or more input/output devices to the client device; provision and serialize one or more operating system function calls to allow for end-to-end communication between the client device and the RDP server when the client device and the RDP server utilize incompatible communication protocols; provide an interface to and from the client device by a hypertext markup language (HTML) compatible stream service of the transcoding service; reconstruct or unpack, by the HTML compatible stream service, one or more remote client tasks to and from a remote desktop protocol; receive device data from the client device; and encode the device data for transmission to a transcoding remote desktop client with a particular port, the encoding being performed according to a pre-defined import/export protocol.
9. The media of claim 8 , wherein the device data comprises input/output data from the client device.
10. The media of claim 8 , wherein the client device comprises one or more of: a mouse; a touch device; a keyboard; a display; a speaker; or a microphone.
11. The media of claim 8 , wherein the import/export protocol is HTML5-compatible.
12. The media of claim 8 , wherein the data comprises a rendering associated with the client device.
13. The media of claim 8 , wherein the client device is a remote desktop protocol client.
14. The media of claim 13 , wherein the remote desktop protocol client is launched by a generic client engine.
15. A system comprising: a hypertext markup language (HTML) client device comprising one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to: by a transcoding service attached to the client device, interface a web browser of the client device with a remote desktop extension protocol; allow the client device to connect to a remote desktop protocol (RDP) server; import and exporting at least one of a graphical device interface, one or more virtual channels, and one or more input/output devices to the client device; provision and serialize one or more operating system function calls to allow for end-to-end communication between the client device and the RDP server when the client device and the RDP server utilize incompatible communication protocols; provide an interface to and from the client device by a hypertext markup language (HTML) compatible stream service of the transcoding service; reconstruct or unpack, by the HTML compatible stream service, one or more remote client tasks to and from a remote desktop protocol; receive device data from the client device; and encode the device data for transmission to a transcoding remote desktop client with a particular port, the encoding being performed according to a pre-defined import/export protocol.
16. The system of claim 15 , wherein the device data comprises input/output data from the client device.
17. The system of claim 15 , wherein the client device comprises one or more of: a mouse; a touch device; a keyboard; a display; a speaker; or a microphone.
18. The system of claim 15 , wherein the import/export protocol is HTML5-compatible.
19. The system of claim 15 , wherein the data comprises a rendering associated with the client device.
20. The system of claim 15 , wherein the client device is a remote desktop protocol client.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 14, 2013
August 2, 2016
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.