Lightweight remote display protocol

• US 20050267972A1
• Filed: 05/25/2004
• Published: 12/01/2005
• Est. Priority Date: 05/25/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Jacobs, Remeres, Costa-Requena, Jose, Stirbu, Vlad
• Application Number:
  US10/853,738
• Publication Number:
  US 20050267972A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A light (resource-preserving) remote desktop protocol (32-35) for enabling a user of a client communication terminal (12) to interface with an application hosted by another communication terminal (14). Prior to exchanging remote user interfacing information according to the light remote desktop protocol, a discovery process (31) is performed. The light remote desktop protocol (32-35) provides for exchanging the user interfacing information according to a BEEP-like transport protocol and for indicating the user interfacing information itself using XML or SOAP to describe screens by which a user of the client makes inputs to the application and receives outputs from the application, and using a KPML-like or SOAP protocol derived from an input-event XML schema for the other communication terminal/remote user interfacing server (14) input events on the client communication terminal (12), including events in which a key is pressed on the client (12).

Claims

1. A method by which user interfacing information is exchanged between a client communication terminal and a server communication terminal to enable a user of the client to interact with an application hosted by the server, comprising:

a discovery step, in which a remote user interfacing exchange protocol supported by both the client and the server or a gateway to the server is determined; and

a remote interfacing step, in which the user interfacing information is exchanged according to a BEEP-like transport protocol for providing the user interfacing information.

2. A method as in claim 1, wherein the discovery step includes inspecting respective profile descriptions associated with the server or a gateway to the server or inspecting other messages provided by the server of a gateway to the server in response to a query regarding protocols supported by the server or gateway to the server.

3. A method as in claim 1, wherein the gateway maps the BEEP-like transport protocol to another protocol for use in exchanging the user interfacing information with the server.

4. A method as in claim 1, wherein the BEEP-like transport protocol is a protocol using a single connection for data exchange.

5. A method as in claim 4, wherein the single connection is a TCP connection or a UDP connection.

6. A method as in claim 4, wherein the single connection comprises multiple data streams.

7. A method as in claim 1, wherein in the remote interfacing step, the remote user interfacing information is indicated using a mark up language to describe screens by which a user of the client makes inputs to the application and receives outputs from the application.

8. A method as in claim 7, wherein the mark up language is XML or an XML-like mark up language.

9. A method as in claim 7, wherein the mark up language is XML or SOAP.

10. A method as in claim 1, wherein in the remote interfacing step, a mark up language is used to indicate to the server input events on the client including events in which a key is pressed on the client.

11. A method as in claim 10, wherein the mark up language is XML or an XML-like mark up language.

12. A method as in claim 10, wherein the mark up language is KPML or SOAP.

13. A method as in claim 1, wherein the remote user interfacing information includes information indicating screens by which a user of the client makes inputs to the application and receives outputs from the application, and wherein in the remote interfacing step, the remote user interfacing information is indicated according to an algorithm in which when a change is made to a screen, only the change is communicated in exchanging the user interfacing information.

14. A method as in claim 1, wherein the discovery step is performed according to a UPnP-like protocol over at least one segment of a communication path linking the client communication terminal to the server communication terminal.

15. A method as in claim 1, further comprising a step of authentication and confirming authorization in which at least the server communication terminal authenticates the client communication terminal and confirms that the client communication terminal is authorized to engage in a remote user interface sharing session.

16. A method as in claim 15, wherein in the step of authentication and confirming authorization the client communication terminal authenticates the server communication terminal.

17. A method as in claim 1, wherein the profile descriptions are according to an XML schema and the remote user interfacing exchange protocol is indicated in a UPNP <

Protocol>

description tag.

18. A method as in claim 17, wherein the parameters needed to set up the remote interfacing session are provided in an optional <

ProtocolInfo>

tag.

19. A computer program product comprising:

a computer readable storage structure embodying computer program code thereon for execution by a computer processor in a communication terminal, with said computer program code characterized in that it includes instructions for performing the steps of the method of claim 1.

20. A communication terminal, comprising:

means for providing a profile description indicating support for a protocol for the exchange of user interfacing information with another communication terminal for enabling remote interfacing to an application hosted by the communication terminal or hosted by the other communication terminal; and

means by which the user interfacing information is exchanged in a remote interfacing session according to a BEEP-like transport protocol for providing the user interfacing information.

21. A communication terminal as in claim 20, wherein the BEEP-like transport protocol is a protocol using a single connection for data exchange.

22. A communication terminal as in claim 20, wherein the remote user interfacing information is indicated using a mark up language to describe screens by which a user of the client makes inputs to the application and receives outputs from the application.

23. A communication terminal as in claim 22, wherein the mark up language is XML or an XML-like mark up language.

24. A communication terminal as in claim 22, wherein the mark up language is XML or SOAP.

25. A communication terminal as in claim 20, wherein the remote interfacing means uses a mark up language to communicate input events including events in which a key is pressed on the communication terminal or on the other communication terminal.

26. A communication terminal as in claim 25, wherein the mark up language is XML or an XML-like mark up language.

27. A communication terminal as in claim 25, wherein the mark up language is KPML or SOAP.

28. A communication terminal as in claim 20, wherein the means for indicating support for a protocol uses a UPnP-like protocol.

29. A communication terminal as in claim 20, wherein the profile descriptions are according to an XML schema and the protocol for the exchange of user interfacing information is indicated in a <

protocol>

tag.

30. A communication terminal as in claim 29, wherein the parameters needed to set up the remote interfacing session are provided in an optional <

ProtocolInfo>

tag.

31. A communication terminal as in claim 20, wherein the application is hosted by the other communication terminal.

32. A communication terminal as in claim 20, wherein the communication terminal hosts the application.

33. A communication terminal as in claim 20, wherein the communication terminal is an element of an operator network forming part of a wireless communication network.

34. A communication terminal as in claim 20, wherein the communication terminal is a mobile communication terminal.

35. A communication terminal as in claim 20, further comprising equipment providing cellular communication functionality.

36. A communication terminal as in claim 20, further comprising equipment providing short-range wireless communication functionality.

37. A communication terminal as in claim 20, further comprising means for authenticating another communication terminal.

38. A communication terminal as in claim 37, further comprising means for confirming authorization that another communication terminal is authorized to engage in a remote user interface sharing session.

39. A system, comprising a plurality of communication terminals according to claim 20.