METHOD FOR ESTABLISHING A THIN CLIENT SESSION

• US 20120102209A1
• Filed: 09/18/2009
• Published: 04/26/2012
• Est. Priority Date: 10/08/2008
• Status: Abandoned Application

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Fok Ah Chuen, Frederic, Lecroart, Benoit
• Application Number:
  US13/122,316
• Publication Number:
  US 20120102209A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/4015 where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference

Abstract

The exemplary embodiment concerns a method for establishing a Thin Client session between a Thin Client device (2) and a Thin Client Server (4) exchanging Handshaking and initialization messages during a session negotiation above a SIP-based framework, wherein said Thin Client device (2) and said Thin Client Server (4) exchange additional information representative of the Thin Client context enabling the combination and adaptive transfer of multiple media streams in at least one remote application display during said thin client session.

Claims

1. A method for establishing a Thin Client session between a Thin Client device and a Thin Client Server exchanging Handshaking and initialization messages during a session negotiation above a SIP-based framework, wherein said Thin Client device and said Thin Client Server exchange additional information representative of the Thin Client context enabling the combination and adaptive transfer of multiple media streams in at least one remote application display during said thin client session.

2. The method according to claim 1 wherein said additional information comprises Thin Client information formatted in SDP (Session Description Protocol) offer/answer messages.

3. The method according to claim 1 wherein said additional information comprises Thin Client information formatted in XML-based offer/answer messages embedded in the body of SIP messages.

4. The method according to claim 2 wherein said additional information comprises both multimedia transfers and remote desktop control capabilities.

5. The method according to claim 4 wherein said remote desktop control capabilities further comprises dynamically directing or redirecting graphical updates of a remote application from a first device onto a second device.

6. The method according to claim 5 wherein said first device is a mobile communication device and said second device is a fixed communication device.

7. The method according to claim 6 comprising, transferring uplink events on a separate radio bearer than the one used for the downlink graphical updates.

8. The method according to claim 7 comprising transferring uplink events on a separate IP connection that the one used for the downlink graphical updates.

9. The method according to claim 1 comprising, associating at least one audio/video stream to the thin client session.

10. The method according to claim 8 wherein said additional information comprises remote display framebuffer coordinates and size corresponding to said audio/video streams associated to said thin client session.

11. The method according to claim 9 wherein said additional information allows sending a client request (FramebufferForgetRequest) instructing the server that a specific area on the framebuffer does not require update.

12. The method according to claim 11 wherein said additional information comprises window-id attribute.

13. The method according to claim 12 wherein said additional information allow sending a client request (WindowUpdate) instructing a server that a graphical area identified by said window-id attribute has been resized, moved or both.

14. A thin client device adapted for implementing the method according to claim 1 for establishing a Thin Client session with a Thin Client Server, the thin client device comprising means for exchanging with said Thin Client Server additional information representative of the Thin Client context enabling the combination and adaptive transfer of multiple media streams in at least one remote application display during said thin client session, said additional information comprises SDP (Session Description Protocol) offer/answer messages Or XML-based offer/answer messages embedded in the body of SIP messages.

15. The thin client device according to claim 14 comprising a Mobile User Equipment comprising an interface to enable a user to register interest in media redirection in order to get notified upon reception of said media redirection, and to send a redirection answer.

16. The thin client device according to claim 14 adapted for establishing a separate IP connection for uplink events, for triggering the allocation of separate radio bearer for transferring said uplink events on a separate radio bearer than the one used for downlink graphical updates, and for mapping the rendering of audio/video stream(s) to said remote display framebuffer on its screen.

17. A Thin Client Server adapted for implementing the method according to claim 1 for establishing a Thin Client session with a Thin Client device, the Thin Client Server comprising means for exchanging with said Thin Client device additional information representative of the Thin Client context enabling the combination and adaptive transfer of multiple media streams in at least one remote application display during said thin client session.

18. The method according to claim 3 wherein said additional information comprises both multimedia transfers and remote desktop control capabilities.

19. The method according to claim 18 wherein said remote desktop control capabilities further comprises dynamically directing or redirecting graphical updates of a remote application from a first device onto a second device.

20. The method according to claim 19 wherein said first device is a mobile communication device and said second device is a fixed communication device.