METHOD AND APPARATUS FOR CONTROLLING ACCESS TO RESOURCES IN REMOTE USER INTERFACE SERVICE

• US 20100115027A1
• Filed: 11/03/2009
• Published: 05/06/2010
• Est. Priority Date: 11/03/2008
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd. (Samsung Group)
• Original Assignee: Samsung Electronics Co. Ltd. (Samsung Group)
• Inventors: Lee, Kook-Heui, RYU, Young-Sun, Song, Jae-Yeon
• Granted Patent: US 9,405,594 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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 resource of a Remote User Interface (RUI) server in an RUI client of an RUI system, comprising:

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 that corresponds to the resource, using the received RUI page; and

sending a request for MUTEX locking for restricting access to the 10 resource to the RUI server.

2. The method of claim 1, further comprising loading the received RUI page for controlling the resource upon receiving information indicating a success in the MUTEX locking from the RUI server, after sending the request for MUTEX locking.

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

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

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

6. The method of claim 1, wherein the MUTEX indicates an occupation status for the resource corresponding thereto.

7. The method of claim 1, further comprising:

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

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

8. A method for controlling access to a resource of a Remote User Interface (RUI) server in the RUI server of an RUI system, comprising:

transmitting an RUI page for controlling the resource to an RUI client upon request from the RUI client; and

receiving a request for a Mutual Exclusion (MUTEX) locking for restricting access to the resource from the RUI client that generates a connection to a MUTEX corresponding to the resource.

9. The method of claim 8, further comprising restricting access to the resource by another RUI client upon receiving the request for MUTEX locking from the RUI client.

10. The method of claim 8, further comprising releasing the MUTEX locking for the resource upon receiving a release request for the MUTEX locking from the RUE client as use of the resource is completed.

11. The method of claim 8, further comprising waiting for a delay time duration before approving a request for MUTEX locking from another RUI client, upon receiving the request for MUTEX locking for the resource from another RUI client while the RUI client is using the resource.

12. The method of claim 8, further comprising:

determining whether an access restriction release request is received within a response wait time from another RUI client that is currently accessing the resource, if a MUTEX corresponding to the resource indicates an access restricted status;

delivering an access approval to the resource to the RUI client upon receiving the access restriction release request within the response wait time; and

delivering an inaccessibility to the resource to the RUI client upon failure to receive the access restriction release request within the response wait time.

13. The method of claim 8, wherein the MUTEX indicates an occupation status for the resource to which it corresponds.

14. The method of claim 8, further comprising:

receiving a request for releasing access restriction to the resource from the RUI client;

sending a request for releasing access restriction to the resource to another RUI;

client;

sending a success in releasing the access restriction to the RUI client upon receiving a release approval for access restriction to the resource from another RUI client; and

sending a release failure for access restriction to the RUI client upon receiving an impossibility of releasing access restriction to the resource from another RUI client.

15. A Remote User Interface (RUI) client apparatus for controlling access to a resource of an RUI server in an RUI system, comprising:

a Web browser module for sending a request for an RUI page to the RUI server and receiving the RUI page; and

a Mutual Exclusion (MUTEX) handler for sending to the RUI server a request for restricting access to a resource selected in the RUI page by another RUI client, to request access to the selected resource,

wherein the Web browser module provides an RUI page capable of controlling the selected resource to a user, upon receiving an access approval to the selected resource from the RUI server.

16. The RUI client apparatus of claim 15, wherein the Web browser module provides an RUI page incapable of controlling the selected resource to the user, upon receiving an inaccessibility to the selected resource from the RUI server.

17. The RUI client apparatus of claim 15, wherein upon receiving an access request to the resource selected in the RUI page from the user, the MUTEX handler accesses a MUTEX corresponding to the selected resource, which exists in the RUI server, and sends a request for changing a status of the MUTEX to an access restricted status;

wherein the MUTEX indicates an occupation status by the RUE client for the selected resource.

18. The RUI client apparatus of claim 15, wherein the MUTEX handler requests releasing access restriction to the selected resource upon receiving an inaccessibility to the selected resource from the RUI server as the selected resource is being used by another RUI client,

wherein the Web browser module provides an RUI page capable of controlling the selected resource to the user upon receiving a success in releasing access restriction to the selected resource.

19. The RUI client apparatus of claim 18, wherein the MUTEX handler includes:

upon receiving an access request to the resource selected in the RUI page from the user, a device for accessing a MUTEX corresponding to the selected resource, which exists in the RUI server, and sending a request for changing a status of the MUTEX into an access restricted status in order to request access to the selected resource; and

upon receiving an inaccessibility to the selected resource as the status of the MUTEX is already set to an access restricted status, a device for requesting releasing access restriction to the selected resource by requesting releasing access restriction to the MUTEX in order to request releasing access restriction to the selected resource.

20. A Remote User Interface (RUI) server apparatus for controlling access to a resource in an RUI system, comprising:

a plurality of Mutual Exclusions (MUTEXs) corresponding to respective resources that correspond to respective control ownership associated with applications provided by the RUI server apparatus; and

a Web server for transmitting an RUI page to an RUI client upon request of the RUI client, receiving an access request to a selected resource by receiving from the RUI client a request for restricting access to the resource selected in the RUI page by another RUI client, and sending an access approval to the selected resource to the RUI client if a MUTEX corresponding to the selected resource does not indicate an access restricted status.

21. The RUI server apparatus of claim 20, wherein the Web server includes:

a device for determining whether an access restriction release request is received within a response wait time from another RUI client that is presently accessing the selected resource, if a MUTEX corresponding to the selected source indicates an access restricted status;

a device for delivering an access approval to the selected resource to the RUI client if the access restriction release request is received within the response wait time; and

a device for sending an inaccessibility to the selected resource to the RUI client if the access restriction release request is not received within the response wait time.

22. The RUI server apparatus of claim 20, wherein the Web server receives an access request to the selected resource by receiving from the RUI client a request for changing a status of a MUTEX corresponding to the selected resource to an access restricted status.

23. The RUI server apparatus of claim 21, wherein the Web server includes:

a device for sending a request for releasing access restriction to the selected resource to another RUI client upon receiving an access restriction release request for the selected resource from the RUI client;

a device for sending a success in releasing access restriction to the RUI client upon receiving a release approval for access restriction to the selected resource from another RUI client; and

a device for sending a release failure for access restriction to the RUI client upon receiving an impossibility of releasing access restriction to the selected resource from another RUE client.

24. The RUI server apparatus of claim 23, wherein the Web server receives from the RUI client an access restriction release request for the MUTEX, which is sent to request releasing access restriction to the selected resource.

25. The RUI server apparatus of claim 20, wherein each of the plurality of MUTEXs is distinguishable by a unique Uniform Resource Locator (URL), and access to each of the plurality of MUTEXs is achieved by a resource method.