Remote access software solution for rapidly deploying a desktop

• US 20040255289A1
• Filed: 06/11/2003
• Published: 12/16/2004
• Est. Priority Date: 06/11/2003
• Status: Abandoned Application

• Current Assignee: Citycites Com Corporation
• Original Assignee: Citycites Com Corporation
• Inventors: Alex George, Bethlehem, Laura Lillian, Armstrong
• Application Number:
  US10/458,743
• Publication Number:
  US 20040255289A1
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

The present invention comprises a remote access software solution for rapidly deploying a desktop. The present invention includes a remote software application that functions through a client system, a server and a means of communication between the client system and server. A front end and back end coding structure are included programmed into the remote software application. The back end code is installed and functions on the server system and the front end code is installed and functions on the client system. The back end code process user requests and collects desktop specifications and send this information to the front end code by way of the communication means so that a personal desktop environment may be displayed on the client system. The personal desktop environment is deployed according to details of a user'"'"'s specific user rights and access to specified network resources captured through back end code.

Claims

1. A remote access software solution for rapidly deploying a personalized user desktop environment comprising:

a server system;

a client system capable of displaying a desktop environment;

a remote access software application having a front end coding structure and a back end coding structure the front end coding structure being stored on and functioning from the client system and the back end coding structure being stored on and functioning from the server system;

a means of communication between the front end and back end coding structures whereby the client system and the server system may communicate.

2. The remote access desktop software application according to claim 1 wherein the client system incorporates a hard drive.

3. The remote access desktop software application according to claim 1 wherein communication means between the client system and the server system may be effected via the Internet accessed through the web browser and the application of a remote secure access connectivity software application.

4. The remote access desktop software application according to claim 1 wherein the back end coding structure gathers data from the server necessary to replicate a desktop environment and sends the desktop data to the front end coding structure.

6. The remote access desktop software application according to claim 4 wherein the string of proprietary data includes a user ID and a user password gathered by the front end code and transferred to the back end code by way of the communication means.

7. The remote access desktop software application according to claim 1 wherein a license manager routine confirms that a valid license is available for the remote access software before the back end coding structure transfers data from the server to the client system.

8. The remote access desktop software application according to claim 1 wherein the front end code maps the client system to make image objects links for folders, files and applications existing on the client hard drive available to the desktop environment.

9. The remote access desktop software application according to claim 8 wherein the image object has a non-proprietary icon related to it that is included on an array list of desktop icons.

10. The remote access desktop software application according to claim 1 wherein the integration of the front end code and the back end code functions in a manner that is seamless as perceived by a user.

11. The remote access desktop software application according to claim 1 wherein a virtual drive mapping component enables an application to run locally on a client while data is accessed and stored remotely.

5. The remote access desktop software application according to claim 5 wherein the back end coding structure utilizes a string of proprietary data to access the desktop data or the server.

12. A method of applying a remote access software solution for rapidly deploying a personalized user desktop environment comprising:

a server system;

a client system capable of displaying a desktop environment;

a remote access software application having a front end and a back end coding structure being stored on and functioning from the client system and the back end coding structure being stored on and functioning from the server system;

a means of communication between the front end coding structure and the back end coding structure whereby the client system and the server system may communicate;

a means for personalization of a desktop environment to provide a user with access to particular information and applications whereby the data necessary to emulate the personalized desktop environment of a user may be collected by the back end coding structure and transferred via the communication means to the front end coding structure.

13. The remote access desktop software application according to claim 12 wherein the client system incorporates a hard drive.

14. The remote access desktop software application according to claim 12 wherein communication means between the client system and the server system may be effected via the Internet accessed through the web browser and the application of a remote secure access connectivity software application.

15. The remote access desktop software application according to claim 12 wherein the back end coding structure utilizes a string of proprietary data to access the personalized desktop data on the server.

16. The remote access desktop software application according to claim 15 wherein the string of proprietary data includes a user ID and a user password gathered by the front end code and transferred to the back end code by way of the communication means.

17. The remote access desktop software application according to claim 15 wherein the string of proprietary data is created when a user inputs data into a dialog box and the datastring is collected from a graphic interface by the front end coding structure and is transferred to the server via the communication means so that the string of proprietary data can be utilized by the back end coding structure to conduct the login routine and to handle and verify the results from the server side login module to gain access to at least a portion of the server.

18. The remote access desktop software application according to claim 12 wherein the personalized desktop data is stored in a folder on the server.

19. The remote access desktop software application according to claim 18 wherein the folder is created by the back end coding structure.

20. The remote access desktop software application according to claim 12 wherein a graphical user interface applet is launched to provide access to both the local client system and a network system existing on the server.

21. The remote access desktop software application according to claim 20 wherein the graphical user interface applet makes a graphical user interface explorer available to be launched to expand either or both the local or network system drives from the desktop environment.

22. The remote access desktop software application according to claim 12 wherein a license manager routine confirms that a valid license is available for the remote access software before the back end coding structure transfers data from the server to the client system and prohibits a user from the remote access software if a valid license is not available.

23. The remote access desktop software application according to claims 23 and 16 wherein the license manager routine generates a digital key pair, including a private key and a public key, the public key compares itself to the user id and password contained within the string of proprietary information and the public key is emailed to be installed on the network server.

24. The remote access desktop software application according to claim 12 wherein the front end code maps the client system to make image objects links for folders, files and applications existing on the client hard drive available to the desktop environment.

25. The remote access desktop software application according to claim 12 wherein the personalized desktop data is translated to make image objects links for folders, files and applications existing on the server available to the desktop environment.

26. The remote access desktop software application according to claim 25 wherein the image object integrates a specific marking into the image object icon displayed on the desktop environment.

27. The remote access desktop software application according to claims 24 and 25 wherein the image object is produced in a manner that is seamless as perceived by a user.

28. The remote access desktop software application according to claims 24 and 25 wherein the icon may be copied, cut, pasted, deleted and renamed from the desktop environment.

29. The remote access desktop software application according to claims 24 and 25 wherein the image object displays shared folders as an icon on the desktop environment.

30. The remote access desktop software application according to claim 12 wherein the integration of the front end code and the back end code functions in a manner that is seamless as perceived by a user.

31. The remote access desktop software application according to claim 12 wherein a virtual drive mapping component enables an application to run locally on a client while data is accessed remotely.

32. The remote access desktop software application according to claim 12 wherein a servlet monitors the server and dynamically updates the communication string passed between the front end code and the back end code.

33. The remote access desktop software application according to claim 31 wherein the servlet causes an update of the communication string to be seamless as perceived by a user.