IP Library › Granted Patent US 9,294,544
Granted Patent B1
US 9,294,544 · App. 13/487,138 · Granted Mar 22, 2016

System and method for facilitating client-server communication

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,294,544
App. No.
13/487,138
Granted
Mar 22, 2016
Kind
B1
Abstract

Computer-implemented method is disclosed. Method includes defining, at one or more computing devices, first client-server communication protocol for communication between client side and server side. First client-server communication protocol is application layer protocol in OSI model. Method also includes defining connection for client side associated with first client-server communication protocol. Method also includes defining data sink for first client-server communication protocol. Data sink is external to client side and external to server side. Data sink is configured to receive and process output of client side or server side. Method also includes defining data source for first client-server communication protocol. Data source is external to client side and external to server side. Data source is configured to provide input for client side or server side. Method also includes defining communication pathway between two or more of data source, data sink, client side, and server side to facilitate communication.

Claims (45)

1. A method, implemented on one or more computing devices, for facilitating communication, the method comprising:

defining, at the one or more computing devices, a first client-server communication protocol for communication between a client side and a server side, wherein the first client-server communication protocol is an application layer protocol in an open systems interconnection (OSI) model;

defining a connection for the client side associated with the first client-server communication protocol;

defining a data sink for the first client-server communication protocol, wherein the data sink is external to the client side and external to the server side, and wherein the data sink is configured to receive and process an output of the client side or the server side;

defining a data source for the first client-server communication protocol, wherein the data source is external to the client side and external to the server side, and wherein the data source is configured to provide an input for the client side or the server side;

defining a communication pathway between two or more of the data source, the data sink, the client side, and the server side to facilitate communication between the two or more of the data source, the data sink, the client side, and the server side via the communication pathways;

defining a second client-server communication protocol associated with the data source and the data sink; and

transcoding data between a format associated with the first client-server communication protocol and a format associated with the second client-server communication protocol.

2. The method of claim 1 , wherein the server side is associated with a first operating system in a first operating system family, wherein the data source and the data sink are associated with a second operating system in a second operating system family, wherein the first operating system family is separate and distinct from the second operating system family, and wherein the first operating system family comprises a Microsoft operating system family.

3. The method of claim 1 , wherein the data source and the data sink reside in a hypertext transfer protocol (HTTP) server, wherein the HTTP server is communicatively coupleable with an HTTP client, wherein the data source is configured to receive the input from the HTTP client, wherein the data sink is configured to provide the output to the HTTP client, and wherein the defining the connection for the client side comprises defining connection for the server side.

4. A non-transitory machine-readable medium for facilitating communication, the non-transitory machine-readable medium comprising instructions that are executable by one or more processors to perform one or more operations, the instructions comprising:

code for causing the one or more processors to define a first client-server communication protocol for communication between a client side and a server side, wherein the first client-server communication protocol is an application layer protocol in an open systems interconnection (OSI) model;

code for causing the one or more processors to define a connection for the client side associated with the first client-server communication protocol;

code for causing the one or more processors to define a data sink for the first client-server communication protocol, wherein the data sink is external to the client side and external to the server side, and wherein the data sink is configured to receive and process an output of the client side or the server side;

code for causing the one or more processors to define a data source for the first client-server communication protocol, wherein the data source is external to the client side and external to the server side, and wherein the data source is configured to provide an input for the client side or the server side;

code for causing the one or more processors to define a communication pathway between two or more of the data source, the data sink, the client side, and the server side to facilitate communication between the two or more of the data source, the data sink, the client side, and the server side via the communication pathways;

code for causing the one or more processors to define a second client-server communication protocol associated with the data source and the data sink; and

code for causing the one or more processors to transcode data between a format associated with the first client-server communication protocol and a format associated with the second client-server communication protocol.

5. The non-transitory machine-readable medium of claim 4 , wherein the server side is associated with a first operating system in a first operating system family, wherein the data source and the data sink are associated with a second operating system in a second operating system family, wherein the first operating system family is separate and distinct from the second operating system family, and wherein the first operating system family comprises a Microsoft operating system family.

6. The non-transitory machine-readable medium of claim 5 , wherein the first operating system resides on a remote computing device communicatively coupleable with the server side, wherein the remote computing device is separate and distinct from the server side.

7. The non-transitory machine-readable medium of claim 4 , wherein the data sink comprises a virtual machine, and wherein the data source comprises a virtual machine.

8. The non-transitory machine-readable medium of claim 4 , wherein the data sink and the data source reside on a same physical device.

9. The non-transitory machine-readable medium of claim 4 , wherein the data sink and the data source reside on different physical devices.

10. The non-transitory machine-readable medium of claim 4 , further comprising instructions that are executable by the one or more processors to perform one or more operations, the instructions comprising:

code for causing the one or more processors to define validation information for validating the connection for the client side in the first client-server communication protocol,

wherein the code for causing the one or more processors to define a connection for the client side comprises code for causing the one or more processors to define connection for the server side and connection between the client side and the server side.

11. The non-transitory machine-readable medium of claim 4 , wherein the first client-server communication protocol comprises a remote desktop protocol (RDP), the client side comprises an RDP client, and the server side comprises an RDP server.

12. The non-transitory machine-readable medium of claim 4 , wherein the first client-server communication protocol is communicatively coupleable to an operating system for running at least one application, wherein the input comprises an input for the at least one application, and wherein the output comprises an output of the at least one application.

13. The non-transitory machine-readable medium of claim 4 , wherein the data source and the data sink reside in a hypertext transfer protocol (HTTP) server, wherein the HTTP server is communicatively coupleable with an HTTP client, wherein the data source is configured to facilitate receiving the input from the HTTP client, and wherein the data sink is configured to facilitate providing the output to the HTTP client.

14. The non-transitory machine-readable medium of claim 4 , wherein the second client-server communication protocol comprises a session initiation protocol (SIP).

15. The non-transitory machine-readable medium of claim 4 , wherein the second client-server communication protocol comprises hypertext transfer protocol (HTTP).

16. The non-transitory machine-readable medium of claim 4 , wherein the code for defining the data sink comprises code for facilitating communicatively coupling the data sink with one or more of a video output unit, a display output unit, or an audio output unit, and wherein the code for defining the data source comprises code for communicatively coupling the data source with one or more of a keyboard, a mouse, a touch screen, a camera, or an audio input unit.

17. The non-transitory machine-readable medium of claim 4 , further comprising instructions that are executable by the one or more processors to perform one or more operations, the instructions comprising:

closing the communication pathway and freeing resources consumed by the communication pathway upon termination of a communication session between the two or more of the data source, the data sink, the client side, and the server side.

18. An apparatus for facilitating communication, the apparatus comprising:

one or more modules configured to perform one or more operations comprising:

defining a first client-server communication protocol for communication between a client side and a server side, wherein the first client-server communication protocol is an application layer protocol in an open systems interconnection (OSI) model;

defining a connection for the client side associated with the first client-server communication protocol;

defining a data sink for the first client-server communication protocol, wherein the data sink is external to the client side and external to the server side, and wherein the data sink is configured to receive and process an output of the client side or the server side;

defining a data source for the first client-server communication protocol, wherein the data source is external to the client side and external to the server side, and wherein the data source is configured to provide an input for the client side or the server side;

defining a communication pathway between two or more of the data source, the data sink, the client side, and the server side to facilitate communication between the two or more of the data source, the data sink, the client side, and the server side via the communication pathways;

defining a second client-server communication protocol associated with the data source and the data sink; and

transcoding data between a format associated with the first client-server communication protocol and a format associated with the second client-server communication protocol.

19. The apparatus of claim 18 , wherein the server side is associated with a first operating system in a first operating system family, wherein the data source and the data sink are associated with a second operating system in a second operating system family, wherein the first operating system family is separate and distinct from the second operating system family, wherein the first operating system family comprises a Microsoft operating system family, and wherein the defining the connection comprises defining connection for the server side and between the client side and the server side.

20. The apparatus of claim 18 , wherein the data source and the data sink reside in a hypertext transfer protocol (HTTP) server, and wherein the HTTP server is communicatively coupleable with an HTTP client, wherein the data source is configured to receive the input from the HTTP client, and wherein the data sink is configured to provide the output to the HTTP client.

Assignments (17)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
MERGER Recorded May 13, 2022
From: WYSE TECHNOLOGY L.L.C.
To: DELL MARKETING CORPORATION
Reel/Frame 060064/0586 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040065/0618 →
RELEASE OF SECURITY INTEREST Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040040/0001 →
RELEASE OF SECURITY INTEREST Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL MARKETING L.P.; ASAP SOFTWARE EXPRESS, INC.; APPASSURE SOFTWARE, INC.; COMPELLANT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL PRODUCTS L.P.; DELL USA L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040065/0216 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Jan 2, 2014
From: APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS FIRST LIEN COLLATERAL AGENT
Reel/Frame 031897/0348 →
PATENT SECURITY AGREEMENT (ABL) Recorded Jan 2, 2014
From: DELL INC.; APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 031898/0001 →
PATENT SECURITY AGREEMENT (TERM LOAN) Recorded Jan 2, 2014
From: DELL INC.; APPASSURE SOFTWARE, INC.; ASAP SOFTWARE EXPRESS, INC.; BOOMI, INC.; COMPELLENT TECHNOLOGIES, INC.; CREDANT TECHNOLOGIES, INC.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL USA L.P.; FORCE10 NETWORKS, INC.; GALE TECHNOLOGIES, INC.; PEROT SYSTEMS CORPORATION; SECUREWORKS, INC.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 031899/0261 →
CHANGE OF NAME Recorded Nov 15, 2013
From: WYSE TECHNOLOGY INC.
To: WYSE TECHNOLOGY L.L.C.
Reel/Frame 031645/0051 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2012
From: FAUSAK, ANDREW T.; ROMBAKH, OLEG; LIU, DE YU
To: WYSE TECHNOLOGY INC.
Reel/Frame 028724/0675 →