APPARATUS AND METHOD FOR INTERFACING BETWEEN A REMOTE USER INTERFACE SERVER AND A REMOTE USER INTERFACE CLIENT

• US 20110060999A1
• Filed: 10/12/2010
• Published: 03/10/2011
• Est. Priority Date: 10/09/2009
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Song, Jae-Yeon, Ryu, Young-Sun, SO, Young-Wan
• Granted Patent: US 8,769,415 B2
• Time in Patent Office: Days
• US Class Current: 715/740
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Provided is a method and apparatus for providing a User Interface (UI) component to a second Remote User Interface Client (RUIC) incapable of directly receiving the UI component from a Remote User Interface Server (RUIS) in a first RUIC capable of directly receiving the UI component from the RUIS. In the method, the first RUIC discovers the second RUIC that will receive the UI component. Upon discovering the second RUIC, the first RUIC performs a device capability matching procedure between the RUIS and the second RUIC. After completion of the device capability matching procedure, the first RUIC provides the second RUIC with a UI component received from the RUIS and processed for the second RUIC, and delivers control information for the UI component from the second RUIC to the RUIS.

Claims

1. A method for providing a User Interface (UI) component to a second Remote User Interface Client (RUIC) incapable of directly receiving the UI component from a Remote User Interface Server (RUIS) in a first RUIC capable of directly receiving the UI component from the RUIS, comprising:

discovering the second RUIC that will receive the UI component;

upon discovering the second RUIC, performing a device capability matching procedure between the RUIS and the second RUIC;

after completion of the device capability matching procedure, providing the second RUIC with a UI component received from the RUIS and processed for the second RUIC; and

delivering control information for the UI component from the second RUIC to the RUIS.

2. The method of claim 1, wherein discovering the second RUIC comprises receiving, from the second RUIC, specific information indicating whether the second RUIC can receive the UI component provided from the RUIS.

3. The method of claim 1, wherein discovering the second RUIC comprises transmitting specific information indicating that the first RUIC can operate as a proxy of the second RUIC.

4. The method of claim 1, wherein performing a device capability matching procedure comprises transmitting, to the RUIS, profile information of the second RUIC, acquired from a device description received from the second RUIC, and profile information of the first RUIC.

5. The method of claim 4, wherein the UI component comprises at least one of a remote UI page and content.

6. The method of claim 5, wherein providing a processed UI component to the second RUIC comprises:

if the second RUIC can provide the remote UI page, providing the second RUIC with the at least one of a remote UI page and content according to whether the second RUIC has a capability to provide the at least one of a remote UI page and content.

7. The method of claim 6, wherein if the second RUIC can provide the remote UI page, the processed UI component includes a remote UI page having the profile information of the second RUIC, and if the second RUIC can provide the content, the processed UI component includes content having the profile information of the second RUIC.

8. A first Remote User Interface Client (RUIC) device for providing a User Interface (UI) component to a second RUIC incapable of directly receiving the UI component from a Remote User Interface Server (RUIS), comprising:

a UI control module for performing a device capability matching procedure between the RUIS and the second RUIC upon discovering the second RUIC that will receive the UI component;

a remote UI page manager for receiving the UI component from the RUIS, and if the device capability matching procedure is completed, delivering to the second RUIC a UI component received from the RUIS and processed for the second RUIC; and

a message relay unit for delivering control information for the UI component from the second RUIC to the RUIS.

9. The first RUIC device of claim 8, further comprising an available service list transmitter for providing information indicating that the first RUIC can operate as a proxy RUI for the second RUIC, and information about a list of services available for the second RUIC.

10. The first RUIC device of claim 8, wherein the UI control module receives, from the second RUIC, specific information indicating whether the second RUIC can receive the UI component provided from the RUIS.

11. The first RUIC device of claim 8, wherein the UI control module performs the device capability matching procedure using profile information of the second RUIC, acquired from a device description received from the second RUIC, and profile information of the first RUIC.

12. The first RUIC device of claim 11, wherein the UI component comprises at least one of a remote UI page and content.

13. The first RUIC device of claim 12, wherein if the second RUIC can provide the remote UI page, the remote UI page manager delivers the at least one of a remote UI page and content to the second RUIC according to whether the second RUIC has a capability to provide the at least one of a remote UI page and content.

14. The first RUIC device of claim 13, wherein if the second RUIC can provide the remote UI page, the processed UI component includes a remote UI page having the profile information of the second RUIC, and if the second RUIC can provide the content, the processed UI component includes content having the profile information of the second RUIC.