SYSTEM AND METHOD FOR LAUNCHING A RESOURCE IN A NETWORK

• US 20110167159A1
• Filed: 03/18/2011
• Published: 07/07/2011
• Est. Priority Date: 12/02/2004
• Status: Active Grant

• Current Assignee: Desktopsites Inc. (f/k/a CityCites.com Corp.)
• Original Assignee: Desktopsites Inc. (f/k/a CityCites.com Corp.)
• Inventors: BETHLEHEM, Alex, Chen, Yan, Li, Zhenwu, Zhou, Paul Zhiyong, Armstrong, Laura
• Granted Patent: US 8,306,961 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

The disclosure provides a system and method for a client connected to a server in a computer network to access a resource, such as an application, database (either local, server, or web-based), service and/or a file, stored in the network. The system comprises: the client in the network; the server in the network; an instance of the resource stored in at least one of the server and the client; a file associated with the application stored in at least one of the server and the client; and an access module operating to provide the client with access to the server. In the system at the client, a first icon associated with a said resource is provided and if the instance of the resource is stored at the server, the application is automatically accessed when the icon at the client is activated.

Claims

1. An access system for a client connected to a server in a computer network to an instance of said resource stored in at least one of said server and said client, said access system comprising:

a memory module containing data of a mapping of icon files and application files relating to said resource on said server; and

a first module providing instructions to a microprocessor in said client

to generate a first icon on a display associated with said client using said data, said first icon providing a graphic representation of a source of said instance of said resource reflecting whether said resource is located at said client or at said server;

to monitor for activation of said first icon at said client;

to initiate execution of said resource either on said client or said server for said client depending on whether said resource is to be accessed on said client first or said server first and to cause said application to access said file through either said client or said server depending on whether said file is to be accessed on either said client first or said server first;

to update a registry containing activation information on said resource, said registry being accessible by other processes operating on devices in said network;

to initiate an access of said resource on said client after attempting to access said resource on said server, if said server is not accessible;

wherein

said client provides a terminal-based environment for accessing said application that uses said file in said network through Remote Desktop Protocol (RDP) commands; and

said resource is an application that can execute on said client or said server.

2. The access system as claimed in claim 1, further comprising:

a second module in said client providing instructions to said microprocessor in said client operating to provide access to a directory structure stored on a server in said network using Active Directory (AD) protocols to authenticate said client with said server.

3. The access system as claimed in claim 1, further comprising:

a third module in said client providing instructions to a microprocessor in said client to provide said client with communication access to said server and to provide secure access using a secure gateway tunnel to said application that uses said file using said RDP commands.

4. The access system as claimed in claim 1, wherein when said resource is not stored on said client, said icon has attributes associated a location of said resource.

5. The access system as claimed in claim 4, wherein said client is provided with an option of searching for said instance of said resource on either said client first or said server first.

6. The access system as claimed in claim 5, further comprising user profile data relating to a user at said client stored in said network, said user profile data defining rights and access privileges of said resource assigned to said client.

7. The access system as claimed in claim 6, wherein a configuration management interface is provided defining logical data interfaces relating to said resource assigned to said client utilizing said user profile data.

8. The access system as claimed in claim 7, wherein said mapping of said resource utilizes information from said user profile data and provides access to said resource from said server to said client and from said client to said server.

9. The access system as claimed in claim 1, wherein said mapping is used to generate an alternative icon to overlay said first icon when said first icon does not indicate correctly where said resource resides.

10. The access system as claimed in claim 9, wherein when said resource resides on said server, at said client, said resource is reconfigured to present said resource to said user as a server-based resource through said client.

11. The access system as claimed in claim 1, wherein said server synchronizes instances of said file between said client and said server, said server synchronizing said file at any of when said application on said server is accessed, after access to said application on said server is completed or after said client is authenticated.

12. The access system as claimed in claim 1, wherein said first module generates said first icon at a location on said display that is in one of a system tray location, a start menu, a desktop shortcut, an activation bar.

13. The access system as claimed in claim 1, wherein said server further comprises:

a load balancing module invoked when said client requests said server-based resource to distribute terminals services to execute said server-based resource among a plurality of servers in said network.

14. A method for presenting information to a client in a network where resources are stored in at least said client or a server in said network, said method comprising:

when a request for an application is initiated in a graphical user interface (GUI) on said client, providing instructions for execution on a microprocessor on said client to access said application through said client or said server for said client depending whether said application is to be accessed through said client first or said server first;

utilizing a secure access through a secure gateway tunnel to said application using Remote Desktop Protocol (RDP) commands when accessing said application through said server; and

initiating an access of said application on said client after attempting to access said application on said server, when said application is to be initiated on said server first and said server is not accessible,

wherein

said client provides a terminal-based environment for accessing said resource that uses said file in the network through said RDP commands; and

said application can execute on said client or said server.

15. The method as claimed in claim 14, said method further comprising:

accessing a mapping of icon files and application files relating to said application on said server to identify a first icon associated with said application that indicates that said application is associated with said server if said application is to be associated first with said server.

16. The method as claimed in claim 15, wherein user profile data relating to a user at said client is provided in said network, said user profile data defining rights and access privileges to said application assigned to said client.

17. The method as claimed in claim 14, said method further comprising:

accessing a mapping of icon files and application files relating to said application on said server to identify a second icon that indicates that said application is associated with said client if said application is to be associated first with said client; and

using said mapping to overlay an alternative icon for said resource when said resource is not associated with an icon that correctly indicates where said resource resides.

18. The method as claimed in claim 14, further comprising:

initiating an authentication request regarding said client to an authentication service upon activation of said first icon.

19. The method as claimed in claim 14, further comprising:

providing said client with access to said application through said client, if said application is to be accessed on said client first and if said application is located on said client; and

providing said client with access to said application through said server, if said application is not located on said client.

20. The method as claimed in claim 15, further comprising:

generating said first icon at a location in said GUI that is in one of a system tray location, a start menu, a desktop shortcut, an activation bar.