Generic transcoding service for client-server communication

• US 10,044,825 B2
• Filed: 05/11/2016
• Issued: 08/07/2018
• Est. Priority Date: 06/14/2013
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Fausak, Andrew T., Rombakh, Oleg
• Primary Examiner(s): Mundur, Padma
• Application Number:
  US15/152,140
• Publication Number:
  US 20160255168A1
• Time in Patent Office: 818 Days
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

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.

Claims

1. A method comprising:

establishing a remote desktop protocol (RDP) connection between a client device and a connection engine, wherein the client device is an RDP client device;

providing, from a data source, a client-side protocol front-end (CFE) input converted data to the client device via the connection engine;

communicating the CFE converted data to a remote computing device through a client-side protocol back-end (CBE) via an RDP server;

receiving, by a data sink, CFE output converted data from the client device, wherein the client device receives the CFE output converted data from communication with at least one of the RDP server and the remote computing device, and wherein the connection engine connects the data source and the data sink with the client device;

invoking, by the connection engine, at least one application, wherein invoking at least one application that is remote from the client device further comprises passing a parameter from the client device to the connection engine;

binding, by the connection engine, the data sink of the connection engine to an output translation block;

binding, by the connection engine, the data source of the connection engine to an input translation block; and

binding, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to the at least one application.

2. The method of claim 1, wherein the parameter is a name of the at least one application.

3. The method of claim 1, further comprising, binding, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to an operating system associated with the at least one application.

4. The method of claim 1, further comprising:

receiving an indication of the data sink, wherein the indication comprises at least one of a pointer to the data sink, a link to the data sink or a network address of the data sink.

5. The method of claim 1, further comprising:

receiving an indication of the data source, wherein the indication of the data source comprises at least one of a pointer to the data source, a link to the data source or a network address of the data source.

6. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

establish a remote desktop protocol (RDP) connection between a client device and a connection engine, wherein the client device is an RDP client device;

provide, from a data source, a client-side protocol front-end (CFE) input converted data to the client device via the connection engine;

communicating the CFE converted data to a remote computing device through a client-side protocol back-end (CBE) via and RDP server;

receive, by a data sink, CFE output converted data from the client device, wherein the client device receives the CFE output converted data from communication with at least one of the RDP server and the remote computing device, wherein the connection engine connects the data source and the data sink with the client device;

invoke, by the connection engine, at least one application, wherein invoking at least one application that is remote from the client device further comprises passing a parameter from the client device to the connection engine;

bind, by the connection engine, the data sink of the connection engine to an output translation block; and

bind, by the connection engine, the data source of the connection engine to an input translation block; and

bind, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to the at least one application.

7. The media of claim 6, wherein the parameter is a name of the at least one application.

8. The media of claim 6, wherein the software is further operable when executed to:

bind, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to an operating system associated with the at least one application.

9. The media of claim 6, wherein the software is further operable when executed to:

receive an indication of the data sink, wherein the indication comprises at least one of a pointer to the data sink, a link to the data sink or a network address of the data sink.

10. The media of claim 6, wherein the software is further operable when executed to:

receive an indication of the data source, wherein the indication comprises at least one of a pointer to the data source, a link to the data source or a network address of the data source.

11. A system comprising:

a memory;

a processor coupled to the memory, wherein the memory comprises one or more instructions executable by the processor, the processor executing a connection engine, a data sink and a data source to;

establish a remote desktop protocol (RDP) connection between a client device and the connection engine, wherein the client device is an RDP client device;

provide, from the data source, a client-side protocol front-end (CFE) input converted data to the client device via the connection engine;

communicating the CFE converted data to a remote computing device through a client-side protocol back-end (CBE) via an RDP server;

receive, by the data sink, CFE output converted data from the client device, wherein the client device receives the CFE output converted data from communication with at least one of the RDP server and the remote computing device, and wherein the connection engine connects the data source and the data sink with the client device;

invoke, by the connection engine, at least one application, wherein invoking at least one application that is remote from the client device further comprises passing a parameter from the client device to the connection engine;

bind, by the connection engine, the data sink of the connection engine to an output translation block;

bind, by the connection engine, the data source of the connection engine to an input translation block;

bind, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to the at least one application.

12. The system of claim 11, wherein the parameter is a name of the at least one application.

13. The system of claim 11, wherein the processor is further operable when executing the one or more instructions to:

bind, by the connection engine and prior to binding the data sink of the connection engine or the data source of the connection engine, at least one of the output translation block and the input translation block to an operating system associated with the at least one application.

14. The system of claim 11, wherein the processor is further operable when executing the one or more instructions to:

receive an indication of the data sink, wherein the indication comprises at least one of a pointer to the data sink, a link to the data sink or a network address of the data sink;

receive an indication of the data source, wherein the indication comprises at least one of a pointer to the data source, a link to the data source or a network address of the data source.