WO2006025893A1

WO2006025893A1 - Methods and apparatus for secure online access on a client device

Info

Publication number: WO2006025893A1
Application number: PCT/US2005/018461
Authority: WO
Inventors: Phillip N. Calvin
Original assignee: Citrix Systems, Inc.
Priority date: 2004-08-31
Filing date: 2005-05-25
Publication date: 2006-03-09
Also published as: US20060047956A1; US7797724B2

Abstract

A method of securely accessing at a client device content from a server without using the non-volatile memory of the client device is disclosed. The bypassing of non-volatile memory lessens the security risk of unauthorized viewing of the server-originated content. A transport mechanism is initiated on a client device and creates a document container. Downloaded documents from a server are mapped into the document container and saved within the document container in volatile memory. Substitute menus are generated within the container to replace application menus. User documents are saved directly to the originating server via the substitute menus. The downloaded copies in volatile memory automatically delete when the document container is destroyed thereby reducing security concerns of unauthorized viewing of the content at the client device.

Description

METHODSANDAPPARATUS FORSECURE ONLINEACCESS ONACLIENTDEVICE

Field of the Invention

The present invention relates generally to securely accessing content files from a server, and more particularly, to securely accessing content files from a server system without storing the content files in non-volatile memory on a client device.

Background of the Invention

Conventionally, users on a client system have used a combination of a web browser and other client-based applications to access a content file retrieved from a remote location. For example, the user may access Internet content using INTERNET EXPLORER from Microsoft Corporation of Redmond, Washington and then use WINDOWS EXPLORER also from Microsoft Corporation to access a desktop productivity document type such as a WORD document that has been downloaded to a local location.

The conventional process of accessing and retrieving the remotely located content and then editing the content file locally is shown in Figure 1. The sequence of steps followed to conventionally edit the downloaded content files begins by downloading the original file from its location and saving it to a local machine (step 2). The user then opens the file on the local machine, views the file and makes any desired changes (step 4), either by using a file manager which accesses the document and calls a associated application (e.g.: user accesses file with WINDOWS EXPLORER and selects a file which calls WORD from Microsoft Corporation to open a file with a .doc extension) or by opening an application such as WORD and then directly accessing the saved document with the application, such as by using the open command on the file menu. When the user is viewing or editing the document, the document is saved back to the local machine (step 6). The file may then be uploaded to a web server using the client browser (step 8).

Unfortunately, this conventional sequence of downloading-editing-storing and uploading presents difficulties from a security standpoint. In order to access the content at the client, the user is required to twice save the content locally to non-volatile memory. The first save is required during download and the second is required post editing prior to the uploading process. Additionally, many users frequently move and/or copy the downloaded content from one local directory to another (e.g.: from dir://downloaded_files to dir://my_documents). Each of these save actions creates a local copy of the document on the client. Very few users of the client device will remember to manually delete these local copies of the documents which accordingly remain on the client device.

Direct manipulation of the client device's storage may be inaccessible to the user, such as the situation where the client device is located in a public kiosk setting. In these cases, the option of deleting the local copy is not available to the user. Since documents left on the client may be accessed by unauthorized individuals with access to the client machine this presents a significant security issue.

Summary of the Invention

The illustrative embodiment of the present invention provides a method of containing and controlling the distribution of confidential information from a server. By creating a mechanism to control the viewing, editing and storing of content files at the client device, the present invention enables secure online access to documents that helps prevent unwanted disclosure of confidential information. Rule-based policies may be implemented to prevent the storage of content files on the client device thereby preventing copies of stored content files from being accidentally left on the client device. The rule-based policies may also be used to prevent or modify the type of content accessible to the user in addition to limiting the manipulation of the content at the client device. The present invention also allows the tailoring of an appropriate level of output from a server to a requesting client.

The illustrative embodiment of the present invention provides a method of securely accessing at a client device content from a server without using the non-volatile memory of the client device. Bypassing non-volatile memory lessens the security risk of unauthorized viewing, editing or acquisition of the server-originated content. A transport mechanism is initiated on a client device and creates a document container on the client device. Documents from the server are mapped into the document container and saved in volatile memory allocated to the document container. Substitute menus are generated within the container to replace the usual menus of the applications used to access and/or edit the content files. User documents are saved directly to the originating server via the substitute menus. The downloaded content in volatile memory automatically delete when the document container is destroyed thereby reducing security concerns regarding unauthorized viewing of the content at the client device.

In one embodiment, a method for securely providing access to a content file includes the step of requesting access to a content file and receiving from the server the requested file. The method further includes storing the received content file in a volatile memory element. The method also invokes an application program associated with the content file. A set of replacement menu commands for interacting with the application program are provided. The set of replacement menu commands are consistent with a set of menu commands associated with the invoked application program.

In another embodiment, an apparatus for securely providing access to a content file includes a file transport mechanism. The apparatus also includes a storage buffer created by the transport mechanism in a volatile memory element. The file transport mechanism stores a received content file in the storage buffer. The apparatus further includes a document container that is invoked by and in communication with the file transport mechanism. The document container provides a context for execution of an application program associated with the content file. The document container provides a set of replacement menu commands for interacting with the application program. The set of replacement menu commands are consistent with a set of menu commands associated with the invoked application program. Brief Description of the Drawings

These and other aspects of this invention will be readily apparent from the detailed description below and the appended drawings, which are meant to illustrate and not to limit the invention, and in which: Figure 1 (prior art) depicts the conventional sequence of steps followed at a client device to edit and save content that is retrieved from a server;

Figure 2 is a block diagram of an embodiment of an environment suitable for practicing the illustrative embodiment of the present invention;

Figures 3A and 3B are block diagrams depicting embodiments of computers useful in connection with the present invention;

Figure 4 is a flowchart of one embodiment of the overall sequence of steps followed by the illustrative embodiment of the present invention to securely edit downloaded content at a client device without using non-volatile memory;

Figure 5 is a flowchart of one embodiment of the sequence of steps followed by the illustrative embodiment of the present invention to perform OLE in-place activation in the document container;

Figure 6 is a flowchart of one embodiment of the sequence of steps followed by the illustrative embodiment of the present invention to save documents being edited in the document container; and

Figure 7 is a flowchart of one embodiment of the sequence of steps followed by the illustrative embodiment of the present invention to filter document requests coming from the client device; and

Figure 8 is a block diagram of one embodiment of a system for providing application output to devices having constrained system resources.

Detailed Description

The illustrative embodiment of the present invention allows the distribution of content files from a server to a client for viewing or editing locally that controls the ability of a user at the client to edit and save the content locally. By bypassing non-volatile memory on the client device in favor of volatile memory assigned to an instantiated document container object, the risk of extra copies of the content being saved on the client device is greatly lessened. Additionally, the ability to perform menu substitution for the client-side applications executing within the instantiated document container allows control over the editing process. To increase security, the content distribution system can also employ a filtering process at a proxy server to apply a rules-based filter to content requests prior to delivering the content to the document container on the client device.

The illustrative embodiment of the present invention is applicable to a distributed networking environment where a remote user requests access to content. Prior to discussing the specifics of the present invention, it may be helpful to discuss some of the network environments in which the illustrative embodiment of the present invention may be employed.

Figure 2 is a block diagram of an environment suitable for practicing the illustrative embodiment of the present invention. A client device 480 includes a web browser 503 and application programs 504a, 504b...504n. An application program is any program that processes data to provide output and that uses an operating system for access to system resources. Exemplary application programs include: word processing applications, such as MICROSOFT WORD, manufactured by Microsoft Corporation of Redmond, Washington; spreadsheet programs, such as MICROSOFT EXCEL, manufactured by Microsoft Corporation; electronic mail programs, such as MICROSOFT OUTLOOK, manufactured by Microsoft Corporation and GROUPWISE, manufactured by Novell Corp. of Provo, Utah; and productivity suites such as STAR OFFICE, manufactured by Sun Microsystems of Mountain View, California.

A file server 510 includes content files 511 and may be connected to databases 506 and 508 holding additional content files 507 and 509 respectively. Those skilled in the art will recognize that other network storage devices or document repositories holding content files may also be networked to the file server 510 without departing from the scope of the present invention. A user of the client device 480 may request content from the file server 510 using the web browser 503 to send a request such as the depicted Hypertext Transport Protocol Secure (HTTPS) request 513, or an HTTP (Hypertext Transport Protocol) or FTP (File Transport Protocol) request. The selection of the resource causes the creation of a transport mechanism such as an Active X transport control 502 on the client device 480. An Active X control is a specialized COM (Component Object Model) object that implements a set of interfaces that enable it to look and act like a control. Alternatively, the transport mechanism may be a dynamically linked library (.dll). The transport control 502 creates an instance of a document container 500 on the client device such as an Active X document container. The Active X document container 500 is a window hosting the Active X transport control 502 which is used to retrieve the requested content 507, 509, and 511 from the file server 510. Those skilled in the art will recognize that other types of containers, such as a JAVA-based container may also be used to create the document container. The Active X document container 500 is associated with a storage buffer 530 created in a volatile memory element 505. The storage buffer 530 is used to hold content files 507, 509 and 511 requested from the file server. As set forth further below, the storage buffer 530 may be a Win32 mapping object. Since the content files 507, 509 and 511 are stored in the storage buffer 530 in the volatile memory element 505, once the memory holding the content file in the volatile storage element is released, the content file ceases to exist on the client device. The client device 480 may also send the request for a content file via a proxy server 520 (such as via the depicted HTTPS connection 512). The proxy server 520 may filter the request prior based on pre-determined rules prior to delivering any content to the client device 480. Those skilled in the art will recognize that the requested content may be stored on the file server 510 such as file content 511 or may be located at another location accessible to the file server such as database 506 and 508. The creation of the document container 500 and the mapping of the content file to the document container is discussed further below in relation to Figure 4.

In many embodiments, the file server 510, client device 480 and the proxy server 520 are provided as personal computer or computer servers, of the sort manufactured by the Hewlett-Packard Corporation of Palo Alto, California or the Dell Corporation of Round Rock, TX. Figures 3A and 3B depict block diagrams of a typical computer 200 useful as the file server 510, the proxy server 520, or the client device 480 in those embodiments. As shown in Figures 3A and 3B, each computer 200 includes a central processing unit 202, and a main memory unit 204. Each computer 200 may also include other optional elements, such as one or more input/output devices 230a-230n (generally referred to using reference numeral 230), and a cache memory 240 in communication with the central processing unit 202. The central processing unit 202 is any logic circuitry that responds to and processes instructions fetched from the main memory unit 204. In many embodiments, the central processing unit is provided by a microprocessor unit, such as: the 8088, the 80286, the 80386, the 80486, the Pentium, Pentium Pro, the Pentium II, the Celeron, or the Xeon processor, all of which are manufactured by Intel Corporation of Mountain View, California; the 68000, the 68010, the 68020, the 68030, the 68040, the PowerPC 601 , the PowerPC604, the PowerPC604e, the MPC603e, the MPC603ei, the MPC603ev, the MPC603r, the MPC603p, the MPC740, the MPC745, the MPC750, the MPC755, the MPC7400, the MPC7410, the MPC7441 , the MPC7445, the MPC7447, the MPC7450, the MPC7451 , the MPC7455, the MPC7457 processor, all of which are manufactured by Motorola Corporation of Schaumburg, Illinois; the Crusoe TM5800, the Crusoe TM5600, the Crusoe TM5500, the Crusoe TM5400, the Efficeon TM8600, the Efficeon TM8300, or the Efficeon TM8620 processor, manufactured by Transmeta Corporation of Santa Clara, California; the RS/6000 processor, the RS64, the RS 64 II, the P2SC, the POWER3, the RS64 III, the POWER3-II, the RS 64 IV, the POWER4, the POWER4+, the POWER5, or the POWER6 processor, all of which are manufactured by International Business Machines of White Plains, New York; or the AMD Opteron, the AMD Athalon 64 FX, the AMD Athalon, or the AMD Duron processor, manufactured by Advanced Micro Devices of Sunnyvale, California.

Main memory unit 204 may be one or more memory chips capable of storing data and allowing any storage location to be directly accessed by the microprocessor 202, such as Static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM), synchronous DRAM (SDRAM), JEDEC SRAM, PC100 SDRAM, Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM), Direct Rambus DRAM (DRDRAM), or Ferroelectric RAM (FRAM). In the embodiment shown in Figure 3A, the processor 202 communicates with main memory 204 via a system bus 220 (described in more detail below). Figure 3B depicts an embodiment of a computer system 200 in which the processor communicates directly with main memory 204 via a memory port. For example, in Figure 3B the main memory 204 may be DRDRAM.

Figures 3A and 3B depict embodiments in which the main processor 202 communicates directly with cache memory 240 via a secondary bus, sometimes referred to as a "backside" bus. In other embodiments, the main processor 202 communicates with cache memory 240 using the system bus 220. Cache memory 240 typically has a faster response time than main memory 204 and is typically provided by SRAM, BSRAM, or EDRAM.

In the embodiment shown in Figure 3A, the processor 202 communicates with various I/O devices 230 via a local system bus 220. Various busses may be used to connect the central processing unit 202 to the I/O devices 230, including a VESA VL bus, an ISA bus, an EISA bus, a MicroChannel Architecture (MCA) bus, a PCI bus, a PCI-X bus, a PCI-Express bus, or a NuBus. For embodiments in which the I/O device is a video display, the processor 202 may use an Advanced Graphics Port (AGP) to communicate with the display. Figure 3B depicts an embodiment of a computer system 200 in which the main processor 202 communicates directly with I/O device 230b via HyperTransport, Rapid I/O, or InfiniBand. Figure 3B also depicts an embodiment in which local busses and direct communication are mixed: the processor 202 communicates with I/O device 230a using a local interconnect bus while communicating with I/O device 230b directly.

A wide variety of I/O devices 230 may be present in the computer system 200. Input devices include keyboards, mice, trackpads, trackballs, microphones, and drawing tablets. Output devices include video displays, speakers, inkjet printers, laser printers, and dye-sublimation printers. An i/O device may also provide mass storage for the computer system 200 such as a hard disk drive, a floppy disk drive for receiving floppy disks such as 3.5-inch, 5.25-inch disks or ZIP disks, a CD-ROM drive, a CD-R/RW drive, a DVD-ROM drive, tape drives of various formats, and USB storage devices such as the USB Flash Drive line of devices manufactured by Twintech Industry, Inc. of Los Alamitos, California.

In further embodiments, an I/O device 230 may be a bridge between the system bus 220 and an external communication bus, such as a USB bus, an Apple Desktop Bus, an RS-232 serial connection, a SCSI bus, a FireWire bus, a FireWire 800 bus, an Ethernet bus, an AppleTalk bus, a Gigabit Ethernet bus, an Asynchronous Transfer Mode bus, a HIPPI bus, a Super HIPPI bus, a SeriaIPIus bus, a SCI/LAMP bus, a FibreChannel bus, or a Serial Attached small computer system interface bus.

General-purpose desktop computers of the sort depicted in Figures 3A and 3B typically operate under the control of operating systems, which control scheduling of tasks and access to system resources. Typical operating systems include: MICROSOFT WINDOWS, manufactured by Microsoft Corp. of Redmond, Washington; MacOS, manufactured by Apple Computer of Cupertino, California; OS/2, manufactured by International Business Machines of Armonk, New York; and Linux, a freely-available operating system distributed by Caldera Corp. of Salt Lake City, Utah, among others.

For embodiments in which the client device 480 is a mobile device, the client device may be a JAVA-enabled cellular telephone, such as the iδOsx, iδδsr, iδδsr, iδδs, i88s, i90c, i9δcl, or the im11000, all of which are manufactured by Motorola Corp. of Schaumburg, Illinois, the 603δ or the 713δ, manufactured by Kyocera of Kyoto, Japan, or the i300 or i330, manufactured by Samsung Electronics Co., Ltd., of Seoul, Korea. In other embodiments in which the client device 480 is mobile, it may be a personal digital assistant (PDA) operating under control of the PalmOS operating system, such as the Tungsten W, the VII, the VIIx, the i70δ, all of which are manufactured by palmOne, Inc. of Milpitas, California. In further embodiments, the client device 480 may be a personal digital assistant (PDA) operating under control of the PocketPC operating system, such as the iPAQ 41 δδ, iPAQ δδδδ, iPAQ 194δ, iPAQ 221 δ, and iPAQ 42δδ, all of which manufactured by Hewlett-Packard Corporation of Palo Alto, California, the ViewSonic V36, manufactured by ViewSonic of Walnut, California, or the Toshiba PocketPC e40δ, manufactured by Toshiba America, Inc. of New York, New York. In still other embodiments the client device is a combination PDA/telephone device such as the Treo 180, Treo 270 or Treo 600, all of which are manufactured by palmOne, Inc. of Milpitas, California. In still further embodiment, the client device 480 is a cellular telephone that operates under control of the PocketPC operating system, such as the MPx200, manufactured by Motorola Corp.

Figure 4 is a flowchart of one embodiment of the overall sequence of steps followed by the illustrative embodiment of the present invention to securely access content at a client device without using non-volatile memory. The sequence begins when a user at the client device initiates the specialized editing process from the user interface (step 550). This may occur automatically when the user requests any content from a specialized server or may occur through an affirmative user selection of particular content on a server. Following the selection, the transport mechanism 502 is then instantiated on the client device. In one embodiment this transport mechanism 502 is an Active X control object. In other embodiments, the transport mechanism may be a JAVA-based object or some other type of transport mechanism other than an Active X control object. In one implementation, the Active X control object is invoked by a JAVA script which passes the control parameters for the transport mechanism to the Active X control object. The transport mechanism is initialized and then creates an instance of the document container 500 on the client device 480 that will eventually receive the requested content 507, 509, 511. The document container may be an Active X/OLE (Object Linking and Embedding) container or some other type of container such as a JAVA-based container hosting a transport mechanism. The transport mechanism 502 requests the container 500 access a document and in response, the container creates a WIN32 Mapping object (step 556).

The document container 500 uses an URL moniker to transport the requested content file 507,509, 511 to the client device. An URL moniker is a system-provided moniker class that supports binding objects such as files, items and pointers to an URL. The use of the URL moniker restricts the transferred data to the current HTTPS session by binding the content file to the current session. The data from the content file is read into the newly created mapping object/global memory associated with the document container 500 (step 558). The document container then creates an interface to the mapping object, such as an llockBytes instance mapped to the file mapping object (step 560). After the document container confirms the presence of a storage object, the document container runs an OLE in-place Activation sequence to embed an OLE-enabled application into the container where it will be used to access the content file. Examples of OLE-enabled applications include WORD, EXCEL and POWERPOINT, all from Microsoft Corporation of Redmond, Washington (step 562). The In-Place Activation Sequence is examined in more detail during the discussion regarding Figure 5 below. As a result of the In-Place Activation sequence, the file menu ends up being controlled by the container 500.

Figure 5 is a flowchart of one embodiment of the sequence of steps followed to perform OLE in-place activation in the document container 500. The In-Place Activation sequence begins once the storage object is found (step 570). The storage object is then created as an IStorage object (step 572) which allows a stream to be managed within the storage object. The CLSID (class ID) associated with the storage is then determined (step 574). An In-Place Object is created and bound to the storage object (step 576). Once the client is activated, the menus and toolbars are negotiated to give control to the document container rather than the editing application (step 578). As a result of the In-Place Activation sequence the container 500 controls the file menu instead of the native application controlling the file menu.

The menu substitution performed in the container 500 may take many forms. Copy and paste functions in the application may be controlled by disabling the clipboard. Similarly, the printer functionality may be disabled. Save options may be limited to locations on the server by disabling any local save options. Client drive mapping may also be disabled. For an application such as a web browser, the cache function may be altered or turned off for certain types or all documents. Those skilled in the art will recognize that many additional forms of menu substitution and/or application function alterations may take place within the scope of the present invention.

Figure 6 is a flowchart of one embodiment of the sequence of steps followed by the present invention to save documents being edited in the document container. The save sequence begins when the user selects "save" from the UI (step 590). To the user at the client device 480, the save operation appears to be a normal save operation. However, the document container 500 intercepts the save message (step 592). The document container 500 obtains the current IStorage from the In-Place object and the storage bytes are read into the ILockBytes Object (step 594). The ILockBytes Object is then posted to the server via the URL moniker mechanism created by the transport 502 (step 596). The server retrieves the bytes and saves the updated file over the original on the server (step 598).

As noted above, a filtering mechanism may also be deployed to further restrict the content accessible to the document container. Figure 7 is a flowchart of the sequence of steps followed by one embodiment of the present invention to filter document requests coming from the client device. The sequence begins with interception of a content request to the web server by a process running on a proxy server 520 (step 610). The request is examined (step 612) and previously determined rules are applied to the request (step 614). Following the application of the rules, the request may be processed normally with no alteration (step 616), the request may be modified based on a rule and then processed normally (step 618), or the request may be denied based upon the application of a rule (step 620). The filtering of the request may be done at the proxy server when the request is inbound or may be done by examining the responsive content being sent by the file server in an outbound direction.

The rules may filter the request for a content file based on a user profile leveraging information collected from a user at login. For example, the rules may filter the request for a content file based upon the type or amount of content requested and the job title of the requesting user. A program developer may have access to content files that a data entry clerk will not. The content files may be categorized and the availability of the content files may be restricted by the rules based on category. The rules may filter content based upon the type of connection established by the client with the user. For example, the display capabilities and the processing resources available to the client device may be considered in determining whether the requested content is transmitted without alteration to the client device, modified prior to transmission, or not transmitted. Similarly, the location of the requesting client may also impact whether the requested content is delivered and the form in which it is delivered. URL rewriting may be employed to redirect all of the content file requests to a specified server where the rules are applied to the request.

Technologies for providing remote access to networked resources include a variety of client/server software combinations. One of these combinations is often referred to as a "thin-client" or a "distributed application processing" system. The illustrative embodiment of the present invention may also be practiced in a thin-client environment. Similar to other distributed environments, practicing the illustrative embodiment of the present invention in a thin-client environment allows control over the distribution of the content file to the client system. In these systems, an application program is executed by a server computing device, usually referred to as the "application server," on behalf of one or more client computing devices, usually referred to as the "thin-client" or the "thin-client application." Only input to the application received from the user at the thin-client and output produced by an application executing on the application server are transmitted between the thin-client and the application server. Thin-client computing architectures are popular implementations for providing remote connectivity to applications and other system resources. Examples of such systems include: Citrix MetaFrame Presentation Server software in combination with Intelligent Computing Architecture (ICA) clients, available from Citrix Systems, Inc. of Fort Lauderdale, Florida; X servers in combination with X Windows clients available from the X Consortium; and Microsoft Windows NT Server 4.0 Terminal Server Edition in combination with Remote Display Protocol (RDP) clients, available from Microsoft Corporation of Redmond, Washington.

Because a client in a thin-client computing architecture does not execute the application program and is required to transmit only user input to the application server and display only output of the application executing on the application server, the client device may offer limited amounts of memory, slower communication subsystems, and limited system resources without degradation in performance that is noticeable to the user. A personal computer, workstation, or other similar computing device typically provides ample system resources to execute the thin-client application and communicate with the application server.

However, more users requiring remote connectivity are using computing devices as thin-clients that do not provide sufficient memory, network resources, or proper operating system environments to function as thin-clients, such as cell phones and personal digital assistants. For example, many current cell phones provide less than 1 Megabyte of random access memory, which is generally not sufficient for execution of the thin-client application. Further, it is often useful for an embedded system to access an application server for application output. Typically, these systems are also limited in resources such as memory.

In one embodiment of the present invention, the document container and transport mechanism are created on a client device with constrained resources. In such a case, the applications used to access the content file are executed from a remote location rather being executed on the client device. The output from the remotely executing application may then be downloaded to the document container on the client device so that it is not permanently stored on the client device. Those skilled in the art will recognize that remote applications may be executed on the server providing the content or may be executed from a different location.

Referring now to Figure 8, a system 100 for securely providing application output to a client device having constrained system resources includes an application server 110, a proxy server 150, and a client 140. Although only one application server 110, proxy server 150, and client 140 is depicted in the embodiment shown in Figure 8, it should be understood that the system may provide multiple ones of any or each of those components. For example, in one embodiment, the system 100 includes multiple, logically- grouped application servers 110, each of which are available to execute applications on behalf of a client 140. In these embodiments, the logical group of servers may be referred to as a "server farm." In other embodiments, multiple proxy servers 150 may be provided. In some of these embodiments, the proxy servers may be geographically dispersed.

The application server 110 communicates with the proxy server 150 over a first network 125. The first network 125 can be a local area network (LAN), a metropolitan area network (MAN), or a wide area network (WAN) such as the Internet. The application server 110 and the proxy server 150 may connect to the first network 125 through a variety of connections including standard telephone lines, LAN or WAN links (e.g., T1 , T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), and wireless connections. Connections between the application server 110 and the proxy server 150 may use a variety of data-link layer communication protocols (e.g., TCP/IP, IPX, SPX, NetBIOS, NetBEUI, SMB, Ethernet, ARCNET, Fiber Distributed Data Interface (FDDI), RS232, IEEE 802.11 , IEEE 802.11a, IEE 802.11b, IEEE 802.11g and direct asynchronous connections).

The proxy server 150 executes one or more thin-client applications 152, 154 such as a Remote Display Protocol client, manufactured by Microsoft Corporation or an ICA client, manufactured by Citrix Systems, Inc. of Fort Lauderdale, Florida. The application server 110 communicates the output of the application programs 122, 124, 126, 128 to thin-client applications 152, 154 executing on the proxy server 150 and receives user input directed to the application programs 122, 124, 126, 128 from the thin-client application 152, 154. The application server 110 communicates with the thin-client applications 152, 154 over network 125 using a presentation-layer protocol such as the Independent Computing Architecture (ICA) protocol, available from Citrix Systems, Inc. of Fort Lauderdale, Florida or the Remote Display Protocol (RDP), available from Microsoft Corporation. Although only two thin-client applications are depicted in the embodiment shown in Figure 8, the proxy server 150 may host any number of thin-client applications 152, 154.

The proxy server 150 also executes a proxy server application 158. The proxy server application 158 may be an application program, a subsystem or a service. The proxy server application 158 manages the thin-client applications 152, 154 hosted by the proxy server 150. The proxy server application also transmits application output received by the thin-client applications 152, 154 to the client device 140 and transmits user input received from the client device 140 to the appropriate thin-client application 152, 154 executing on the proxy server 150. The proxy server application 158 executing on the proxy server 150 communicates with the client 140 over a second network 175. For embodiments in which the client 140 is an embedded system, the client 140 and the proxy server 150 may connect to the second network 175 through a variety of connections including standard telephone lines, LAN or WAN links (e.g., T1 , T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), and wireless connections. Connections between the client 140 and the proxy server 150 may use a variety of data-link layer communication protocols (e.g., TCP/IP, IPX, SPX, NetBIOS, NetBEUI, SMB, Ethernet, ARCNET, Fiber Distributed Data Interface (FDDI), RS232, IEEE 802.11 , IEEE 802.11a, IEE 802.11b, IEEE 802.11g and direct asynchronous connections).

In other embodiments, the client device 140 is a mobile device, such as a cellular telephone or a personal digital assistant. In these embodiments, the client 140 and the proxy server application 158 connect to the second network using any one of a number of well-known protocols from the GSM or CDMA families, such as W-CDMA. These protocols support commercial wireless communication services and W-CDMA, in particular, is the underlying protocol supporting i-Mode and mMode services, offered by NTT DoCoMo.

The client device 140 executes a client application 146. The client application transmits and receives http or https requests to and from the proxy server application 158. The client application 148 transmits user input directed to an executing application program 122, 124, 126, 128 to the proxy server application 158 over the second network 175. It is also responsible for rendering graphical output on the screen of the client device corresponding to the output of the application program 122, 124, 126, 128 executing on the application server 110.

The present invention may be provided as one or more computer- readable programs embodied on or in one or more articles of manufacture. The article of manufacture may be a floppy disk, a hard disk, a compact disc, a digital versatile disc, a flash memory card, a PROM, a RAM, a ROM, or a magnetic tape. In general, the computer-readable programs may be implemented in any programming language. Some examples of languages that can be used include C, C++, C#, or JAVA. The software programs may be stored on or in one or more articles of manufacture as object code.

While the invention has been shown and described with reference to specific preferred embodiments, it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention as defined by the following claims.

Claims

WΘ Claim:

1. A method for securely providing access to a content file, the method comprising the steps of:

(a) requesting access to a content file;

(b) receiving, from a server, the content file;

(c) storing the received content file in a volatile memory element;

(d) invoking an application program associated with the content file; and

(e) providing a set of replacement menu commands for interacting with the application program, the set of replacement menu commands consistent with a set of menu commands associated with the invoked application program.

2. The method of claim 1 wherein step (a) comprises requesting access to a content file using an URL moniker.

3. The method of claim 1 further comprising the step of instantiating a transport mechanism.

4. The method of claim 3 wherein step (d) comprises:

(d-1 ) creating, by the transport mechanism, a container instance; and (d-2) invoking an application program associated with the content file for execution within the created container instance.

5. The method of claim 1 further comprising the step of creating a storage location in a volatile memory element.

6. The method of claim 1 further comprising the steps of: receiving a command to save the content file; and transmitting the content file to the server.

7. The method of claim 6 further comprising the step of: releasing the memory associated with the content file in the volatile memory element.

8. An apparatus for securely providing access to a content file comprising: a file transport mechanism; a storage buffer created by the transport mechanism in a volatile memory element, the file transport mechanism storing a received content file in the storage buffer; a document container invoked by and in communication with the file transport mechanism, the document container providing a context for execution of an application program associated with the content file, the document container providing a set of replacement menu commands for interacting with the application program, the set of replacement menu commands consistent with a set of menu commands associated with the invoked application program.

9. The apparatus of claim 8 wherein the file transport mechanism comprises a dynamically-linked library.

10. The apparatus of claim 8 wherein the document container comprises an ActiveX control.

11.The apparatus of claim 8 wherein the document container comprises a JAVA applet.

12. The apparatus of claim 8 wherein the storage buffer comprises a Win32 file mapping object.

13. A method for securely providing access to a content file, the method comprising the steps of:

(a) requesting access to a content file;

(b) filtering the request by applying pre-determined rules; (c) receiving, from a server, the content file following said filtering;

(d) storing the received content file in a volatile memory element;

(e) invoking an application program associated with the content file; and

(f) providing a set of replacement menu commands for interacting with the application program, the set of replacement menu commands consistent with a set of menu commands associated with the invoked application program.

14. The method of claim 13 wherein step (b) further comprises: modifying said request based on said rules.

15. The method of claim 14 wherein step (b) further comprises: restricting the at least one of the type and amount of the content requested.

16. The method of claim 13 wherein said rules are applied based upon a profile of a requesting user.

17. The method of claim 13 wherein said rules are applied based upon a category of the content file requested.

18. The method of claim 13 wherein said filtering takes place before the request is forwarded to the server.

19. The method of claim 13 wherein said filtering takes place after the request is for the server.

20. An article of manufacture having embodied thereon computer- readable program means for securely providing access to a content file, the article of manufacture comprising:

(a) computer-readable program means for requesting access to a content file; (b) computer-readable program means for receiving, from a server, the content file;

(c) computer-readable program means for storing the received content file in a volatile memory element;

(d) computer-readable program means for invoking an application program associated with the content file; and

(e) computer-readable program means for providing a set of replacement menu commands for interacting with the application program, the set of replacement menu commands consistent with a set of menu commands associated with the invoked application program.

21. The article of manufacture of claim 20 wherein the computer- readable program means of step (a) further comprises requesting access to a content file using an URL moniker.

22. The article of manufacture of claim 20 further comprising: computer-readable program means for instantiating a transport mechanism.

23. The article of manufacture of claim 21 wherein the computer-readable program means of step (d) further comprises :

(d-1) computer-readable program means for creating, by the transport mechanism, a container instance; and

(d-2) computer-readable program means for invoking an application program associated with the content file for execution within the created container instance.

24. The article of manufacture of claim 20 further comprising: computer-readable program means for creating a storage location in a volatile memory element.

25. The article of manufacture of claim 20 further comprising: computer-readable program means for receiving a command to save the content file; and computer-readable program means for transmitting the content file to the server.

26. The article of manufacture of claim 25 further comprising: computer-readable program means for releasing the memory associated with the content file in the volatile memory element.