Method and apparatus for controlling access to resources in remote user interface service

• US 9,405,594 B2
• Filed: 11/03/2009
• Issued: 08/02/2016
• Est. Priority Date: 11/03/2008
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Ryu, Young-Sun, Lee, Kook-Heui, Song, Jae-Yeon
• Primary Examiner(s): Patel, Hitesh
• Application Number:
  US12/611,541
• Publication Number:
  US 20100115027A1
• Time in Patent Office: 2,464 Days
• Field of Search: 709/203, 709/205, 709/220, 709217-219, 718/103, 707/8, 707/10
• US Class Current: 1/1
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

A method is provided for controlling access to a resource of a Remote User Interface (RUI) server in an RUI client of an RUI system. The method includes sending a request for an RUI page for controlling the resource to the RUI server and receiving the RUI page, generating a connection to a Mutual Exclusion (MUTEX) of the RUI server, which corresponds to the resource, using the received RUT page, and sending a request for MUTEX locking for restricting access to the resource to the RUI server.

Claims

1. A method for controlling access to a mutual exclusion (MUTEX) resource by a remote user interface (RUI) client, comprising:

sending a request for an RUI page to an RUI server;

receiving the RUI page comprising a control ownership object associated with the MUTEX resource, from the RUI server;

establishing a connection to the MUTEX resource of the RUI server based on the control ownership object;

invoking a request for a MUTEX lock for causing the RUI server to restrict access to the MUTEX resource by another RUI client based on the control ownership object;

sending a request for releasing access restriction to the MUTEX resource to the RUI server, upon receiving an inaccessibility to the MUTEX resource from the RUI server as the MUTEX resource is being used by another RUI client;

waiting for acceptance of the request; and

providing the RUI page for controlling the MUTEX resource to the user, upon receiving a success in releasing the access restriction to the MUTEX resource.

2. The method of claim 1, further comprising, receiving information indicating the MUTEX resource is successfully locked by the RUI server;

and

loading the received RUI page based on the received information.

3. The method of claim 1, further comprising sending a request for releasing the MUTEX lock for the MUTEX resource to the RUI server if use of the MUTEX resource is completed.

4. The method of claim 1, further comprising waiting for a delay time duration after sending the request for MUTEX lock if it is identified that another RUI client is using the MUTEX resource.

5. The method of claim 1, further comprising providing an RUI page incapable of controlling the MUTEX resource to a user upon receiving an inaccessibility to the MUTEX resource from the RUI server.

6. The method of claim 1, wherein the control ownership object comprising information on the MUTEX indicates an occupation status for the MUTEX resource corresponding thereto.

7. A non-transitory computer readable medium containing program instructions executable by a computer device to perform a method for controlling access to a mutual exclusion (MUTEX) resource by a remote user interface (RUI) client, the computer readable medium comprising:

sending a request for an RUI page to an RUI server;

receiving the RUI page comprising a control ownership object associated with the MUTEX resource, from the RUI server;

establishing a connection to the MUTEX resource of the RUI server based on the control ownership object;

invoking a request for a MUTEX lock for causing the RUI server to restrict access to the MUTEX resource by another RUI client based on the control ownership object;

sending a request for releasing access restriction to the MUTEX resource to the RUI server, upon receiving an inaccessibility to the MUTEX resource from the RUI server as the MUTEX resource is being used by another RUI client;

waiting for acceptance of the request; and

providing the RUI page for controlling the MUTEX resource to the user, upon receiving a success in releasing the access restriction to the MUTEX resource.

8. The non-transitory computer readable medium of claim 7, further comprising:

receiving information indicating that the MUTEX resource is successfully locked by the RUI server; and

loading the received RUI page based on the received information.

9. The non-transitory computer readable medium of claim 7, further comprising:

sending a request for releasing the MUTEX lock for the MUTEX resource to the RUI server, if use of the MUTEX resource is completed.

10. The non-transitory computer readable medium of claim 7, further comprising:

waiting for a delay time duration after sending the request for MUTEX lock, if it is identified that another RUI client is using the MUTEX resource.

11. The non-transitory computer readable medium of claim 7, further comprising:

providing an RUI page incapable of controlling the MUTEX resource to a user upon receiving an indication of inaccessibility to the MUTEX resource from the RUI server.

12. The non-transitory computer readable medium of claim 7, wherein the control ownership object comprising information on the MUTEX indicates an occupation status for the MUTEX resource corresponding thereto.

13. A remote user interface (RUI) client for controlling access to a mutual exclusion (MUTEX) resource, the RUI client comprising:

a transceiver; and

a processor configured to;

send a request for an RUI page to an RUI server;

receive the RUI page comprising a control ownership object associated with the MUTEX resource, from the RUI server;

establish a connection to the MUTEX resource of the RUI server based on the control ownership object;

invoke a request for a MUTEX lock for causing the RUI server to restrict access to the MUTEX resource by another RUI client based on the control ownership object;

send a request for releasing access restriction to the MUTEX resource to the RUI server, upon receiving an inaccessibility to the MUTEX resource from the RUI server as the MUTEX resource is being used by another RUI client;

wait for acceptance of the request; and

provide the RUI page for controlling the MUTEX resource to the user, upon receiving a success in releasing the access restriction to the MUTEX resource.

14. The RUI client of claim 13, wherein the processor is further configured to:

receive information indicating the MUTEX resource is successfully locked by the RUI server; and

load the received RUI page based on the received information.

15. The RUI client of claim 13, wherein the processor is further configured to send a request for releasing the MUTEX lock for the MUTEX resource to the RUI server if use of the MUTEX resource is completed.

16. The RUI client of claim 13, wherein the processor is further configured to wait for a delay time duration after sending the request for MUTEX lock if it is identified that another RUI client is using the MUTEX resource.

17. The RUI client of claim 13, wherein the processor is further configured to provide the RUI page incapable of controlling the MUTEX resource to a user upon receiving an inaccessibility of the MUTEX resource from the RUI server.

18. The RUI client of claim 13, wherein the control ownership object comprises information on the MUTEX indicates an occupation status for the MUTEX resource corresponding thereto.

19. The RUI client of claim 14, wherein the processor is further configured to display the RUI based on the RUI page on the RUI client.