Apparatus and accompanying methods for providing, through a centralized server site, a secure, cost-effective, web-enabled, integrated virtual office environment remotely accessible through a network-connected web browser

CLAIM TO PRIORITY

P-0001[0001] This application claims the benefit of our co-pending U.S. provisional patent application titled “VIRTUAL OFFICE” filed on Mar. 14, 2000 and assigned serial No. 60/189,251.

BACKGROUND OF THE DISCLOSURE

P-0002[0002] 1. Field of the Invention

P-0003[0003] The invention relates to apparatus and accompanying methods for use therein for implementing a secure, cost-effective, web-enabled, integrated, virtual office user environment, through a centralized server(s), through which a remotely stationed user can access typical office network-based applications, including, e.g., e-mail, file sharing and hosted thin-client application programs, through a remotely located network, e.g., WAN, connected web browser. The present invention is particularly, though not exclusively, suited for use in small to medium size organizations which, for economic reasons, do not have adequate in-house computer support (technical and administrative) capabilities.

P-0004[0004] 2. Description of the Prior Art

P-0005[0005] With laptop personal computers (PCs) having become rather ubiquitous over the last several years, individuals who are away from their office, typically desktop, PCs and hence not in communication with their office networks, because they are either traveling or are at home, often have a continuing need to gain access to those networks. Such access is required if, for no other reasons, than only for those users to transfer files between their laptop PCs and servers on these networks and/or access their network-based e-mail servers (both for receiving incoming and transmitting outgoing messages).

P-0006[0006] This need is not only shared by many individuals but also by organizations of widely varying size, from large organizations to very small businesses and other groups.

P-0007[0007] The art teaches various approaches to meet this need. However, they are all deficient in one respect or another. In that regard, none of these approaches offers an effective, integrated solution that readily provides all the functionality obtainable using an office network through one simple remote user interface, such as a web browser.

P-0008[0008] Specifically, one approach is to simply install appropriate conventional communications software in each client laptop PC and permit its user to access, through a dial-up telephone line, his(her) office network to gain access to the network server for file transfer and e-mail functionality. All application programs would reside on and locally execute on the client laptop PC. While this approach is quite simple, nevertheless it necessitates that each and every such application program be installed, configured and then maintained on that PC. Consequently, over time, this approach, particularly in view of the on-going support costs of the installed application programs, can become quite expensive.

P-0009[0009] Another approach involves using a traditional virtual private network (VPN) to provide wide area network (WAN) connectivity from a user's remote or home location to an office local area network (LAN). A VPN WAN connection implements a so-called OSI layer 2 extension or “conduit” of the office network itself between the LAN and the user's remote/home location. A remote client PC, connected through a VPN to an office LAN, locally appears on the LAN, as far as that user is concerned, as if that client PC were directly connected to it. In essence, for packets destined from the client PC to the LAN, a VPN connection therebetween involves, at a near end of the VPN connection, encapsulating outgoing OSI layer 3 packets at the client PC into layer 2 IP (Internet protocol) packets and transmitting those layer 2 packets over the VPN connection (in effect tunneling those layer 3 packets through the VPN connection), and subsequently, at a remote (LAN) end of the VPN connection, disassembling the layer 2 packets to yield the layer 3 packets and applying the resulting layer 3 packets onto the LAN for carriage to their ultimate destination, such as a network server. The opposite operation occurs in reverse for packets emanating from LAN, e.g., the server, and destined, over the VPN connection, to the remote client PC. Since the layer 2 packet tunneling is totally transparent to both the LAN and the client PC, advantageously the client PC can provide the same level of functionality to its user as if that PC were directly connected to the LAN.

P-0010[0010] Historically, a VPN connection required special, expensive VPN termination equipment located at each end of the connection, or required special client software to be installed and configured at the client machine. This equipment was rather expensive to acquire, and proved to be rather tedious to properly configure and hence costly to administer and maintain, particularly for those small to medium sized organizations that lacked adequate in-house technical support personnel.

P-0011[0011] In particular, at the remote client site, a so-called VPN terminator (also referred to as a “client-site VPN router”) was connected to a client PC to bi-directionally interface that PC to the VPN connection. This terminator provided layer 2 packet processing as well as appropriate packet encryption/decryption functionality. However, such a terminator, which included special-purpose software, was generally quite expensive to procure and needed to be installed and properly configured for its particular client PC—the latter entailing significant costs in both time and money. To mitigate the cost somewhat, various currently available PC operating systems (O/S's) now provide VPN support features, and, as an alternative, VPN vendors have built client VPN software that runs on the client machine and interacts with that vendors' own VPN server or with VPN servers from other vendors. Such client VPN software has been built to work with conventional PC O/S's such as Windows 98, Windows NT, Windows 2000, etc. However, PC O/S-based or client software based VPN support requires considerable packet processing (e.g., for packet encapsulation and disassembly, and cryptographic processing), which disadvantageously imposes a significant processing burden on the PC though this burden may be acceptable for a home PC with a relatively light processing load, rather than a remote PC connected to an office network.

P-0012[0012] Furthermore, VPN services must be very secure. Unfortunately, until rather recently such PC O/S-based VPN support used a rather small key size, such as 40-bits, which generally does not provide sufficient security against third-parties intrusion. While relatively new PC-based operating systems have become available that exhibit significantly increased VPN security, through use of triple DES and IPsec features—such as Microsoft Windows 2000 O/S (“Windows 2000” is a trademark of the Microsoft Corporation of Redmond, Wash.), this support still presents a considerable processing load to the PC; hence, denigrating PC performance, specifically processing throughput.

P-0013[0013] Moreover, such PC operating systems, whether those exhibiting increased VPN security or not, still do not provide requisite reliability.

P-0014[0014] As such, to provide VPN connectivity with required levels of security and reliability without imposing an undue processing load on the client PC, use of a separate dedicated client-site VPN terminator—even in view of its expense—is still strongly favored in practice.

P-0015[0015] Not only is expensive, specialized VPN equipment required at the client site (or alternatives such as OS-based VPN support or client software packages, both with their accompanying problems, need to be used), but it is also necessary, to an even greater extent, at the LAN (central) site. At the LAN site, VPN support requires installation and configuration of an office-site VPN router. Office-site routers are considerably more expensive than client-site VPN routers for the simple reason that the processing circuitry in the former, which implements the necessary cryptographic and packet processing operations, is sized based on a number of users that need to be simultaneously supported. Each user is allocated a certain slice of the available processing capacity. Even if such a router is sized to support just a few simultaneous remote users on the LAN, its cost can easily amount to several thousands of dollars, with the cost rapidly escalating as user load and hence necessary processing capacity of the VPN router increased. Recently, server operating systems, such as the Microsoft Windows 2000 server O/S, have become available that incorporate multi-user VPN support with sufficient security features; however, such support drains considerable processing resources from the server and still is insufficiently reliable. Moreover, if such a server O/S-based approach is used, counterpart client-site software, such as the Windows 2000 O/S, must be installed and properly configured on each client PC, which, if a large number of remote users exists, can be rather expensive and time consuming.

P-0016[0016] Therefore, in view of the relatively high cost involved, most small to medium sized organizations were and continue to be unable to afford the use of VPN connectivity, thus precluding themselves from providing secure remote office access to their internal networks and various business efficiencies and productivity increases that could have gained thereby.

P-0017[0017] A further, though totally different approach, evolved in the art for providing remote connectivity to an office LAN. This approach, predicated on an “application service provider” (ASP) model, involves installing specialized server software, such as “Metaframe” software available from Citrix Corporation, in the network server and an “ICA” client program in each client PC. Through the Metaframe program, the network server situated on the LAN would function as an ASP by hosting multiple virtual sessions of a given application program executing on the server, in effect implementing multiple virtual machines, to various different remotely located client PCs. Each remote client, running the ICA client program, would access, over, e.g., a WAN connection, a desired thin-client application hosted at the LAN-based server and establish a separate application session. The ICA client would communicate mouse clicks and keystrokes entered by a user stationed at the client PC, over the WAN connection, to the Metaframe program executing in the server which, in turn, would provide screen shots back to the client PC for local display to a user stationed thereat. This information would be carried between the client and server using an “ICA” protocol.

P-0018[0018] As PC manufacturers began equipping their PCs with client web browsers as standard issue software as well as users downloading such browsers for free from various software manufacturers, the Metaframe program evolved to permit remote browser-based web access, with the ICA client being replaced by the use of a resident client browser in the PC.

P-0019[0019] The concept of providing multiple virtual machines is also provided through “Windows Terminal Services” (WTS) software currently available from the Microsoft Corporation (“Windows” is a trademark of the Microsoft Corporation) for Windows NT 4 and Windows 2000 server operating systems, with client-server communication of screen shots, keystrokes and mouse clicks being carried to and from WTS using an “RDP (‘Remote Desktop Protocol’ defined by Microsoft Corporation and based on the ANSI T.128 standard)”, rather than an “ICA” protocol. Again, WTS, like the Metaframe program, still carries a considerable processing burden.

P-0020[0020] Unfortunately, with this ASP-based approach, the client PC did not appear as if it were connected to the LAN. As such, while this approach did allow remote application execution, it did not accommodate remote access of other essential office network-based functionality, such as file sharing and e-mail. Hence, this approach was seen as being rather “one-sided”.

P-0021[0021] The art supplemented this ASP-based approach by incorporating a VPN (layer 2) connection between the LAN and client PC. This, in turn, provided added client functionality inasmuch as the client PC appeared as though it was on the remote LAN. However, this approach not only proved to be rather inconvenient to use but also, due to its VPN connectivity and for the reasons set forth above, rather expensive.

P-0022[0022] Specifically, a VPN server was connected to the LAN and a VPN router (or VPN terminator) was connected to each client PC, or each client PC used OS-based VPN support, or special client software had to be installed on each PC. The Metaframe program or WTS executed on the server which provided access, through a client browser or a special client application program, to a server-hosted virtual application session. By virtue of the VPN connection, the user at the client PC could remotely execute server-hosted thin-client applications, with the client PC appearing as if it were directly connected to the LAN. Unfortunately, this approach, being hampered by the constraints of the Metaframe software or WTS, only accommodated thin-client applications through the browser, and hence was just as “one sided”. No other network functionality, such as e-mail or shared file access, was accommodated through the browser; hence, this approach proved somewhat inconvenient to use. Moreover, the high cost of the associated VPN client-site and office-site servers principally dissuaded many small to medium size organizations from using this approach.

P-0023[0023] To off-load some of the processing burden from the LAN server running WTS, a two-tier approach recently appeared in the art through which a specialized processing system was inserted between the server and a WAN connection. This processor converted RDP packets associated with WTS into AIP packets (AIP is a proprietary protocol owned by Tarantella Inc. of Santa Cruz, Calif.) or to some other less bandwidth-intensive protocol and conducted client application communication (screen shots, keystrokes and mouse clicks) with the far-end client PC through either of the latter protocols. ICA provides similar bandwidth conserving functionality. Alternatively, communication in native RDP may be used instead. In any event, the client PC interacted with the processing system through either a specialized client application program or a web browser executing an appropriate JAVA applet (“JAVA” is a trademark of Sun Microsystems, Inc. of Palo Alto, Calif.). While this scheme relieved some of the load on the server, it still suffered the same deficiency as an ASP approach: it was not integrated and thus failed to provide through one single user interface, such as a browser, all the functionality which that user would have if his(her) client PC were directly connected to his(her) office LAN.

P-0024[0024] In view of the increasing costs of software acquisition, client installation and maintenance of client application programs, internally centralized ASP-based remote application hosting may well become an attractive alternative for business users.

P-0025[0025] However, adequate security remains a concern, particularly for small to medium size businesses that seek to implement an ASP-approach using the Win 2000 O/S or similar system. In that regard, WTS provides cryptography, though at a 168-bit level, through use of a symmetric key. While each RDP message from a network server to a remote client is sufficiently encrypted by WTS to preclude its brute-force cryptanalysis, shared symmetric keys are vulnerable to third party discovery for the simple reason that the secret key has to be distributed to the parties using it, and thus can be obtained by a malicious party. Since the Windows 2000 WTS approach does not involve the use of certificates, it is vulnerable to “man-in-the-middle” attacks from malicious parties that have obtained the symmetric key. In symmetric-key cryptography, both sides, here being the remote client PC and the server, utilize the same key. As such, if a third-party interloper, a so-called “man in the middle” that had previously obtained the symmetric key, were to intercept communications, that party through its computer, could pose as the server to the client machine, and as the client to the server machine. However, that party would thus be privy to all communications attempted between the client and the server, and thus have access to information that could be highly proprietary. That party could readily decrypt each message it received from one end and then alter the message contents as it saw fit, and transmit a modified message to the other end, thus potentially causing considerable mischief. Since WTS provides no effective protection to so-called “man in the middle” attacks, inasmuch as its symmetric key scheme does not involve the use of certificates and public keys cryptography, use of WTS under the WIN 2000 O/S is still not viewed by many organizations as offering a sufficiently attractive or secure solution to properly support such centralized thin-client application program hosting.

P-0026[0026] Therefore, a need exists in the art for a technique, specifically apparatus and methods for use therein, that provides secure, but integrated network functionality through a remote WAN connection between a remote client PC and a server based on an office LAN. Such a technique should provide all network functionality, including, e.g., thin-client application program hosting, file sharing and e-mail, through a single, commonly available user interface, such as a web browser, as if that client PC were connected directly to the LAN. The security should be such as to substantially eliminate potential “man in the middle” attacks or other such third-party intrusions. Furthermore, through such a technique, the client PC should appear as if it were directly connected to the LAN.

P-0027[0027] While such a technique could utilize a VPN connection, it should function with preferably far less costly alternatives, such as interacting directly with transport schemes such as DSL (digital subscriber line) or other relatively low-cost, high-speed digital access modalities. Also, such a technique should be remotely administered and supported, particularly when employed in those organizations which can not afford to maintain adequate in-house computer support capabilities.

P-0028[0028] Such a technique, were it to exist, would likely be very attractive to many organizations, including small and medium sized businesses: (a) to permit effective internal ASP-based (centralized) thin-client application program hosting for remote client connectivity, with resulting cost savings to those organizations in application procurement as well as through centralized administration and maintenance of those application programs, and (b) through its use, to yield increased efficiency and productivity by providing remote access for individual users to all their office network-based functionality.

SUMMARY OF THE INVENTION

P-0029[0029] Advantageously, our present invention satisfies this need and overcomes the deficiencies in the art by providing a front-end, in the form of a service enablement platform (SEP), to a LAN-connected office server(s) for implementing secure, remote web-based access, through a WAN-connected user browser, for a user situated at a remote client computer (e.g., remote laptop PC). Through the SEP, the remote user is provided with essentially, if not completely, the same network-based office functionality implemented by the office server as if the remote computer were directly connected to that LAN.

P-0030[0030] In accordance with our inventive teachings, the SEP is situated between the LAN and the WAN-connected user. In use, the SEP acts both as a bridge between the remote user and his(her) office applications and as a protocol translator to enable bi-directional, web-based, real-time communication to occur between the user browser and each of these office applications. In that regard, the SEP provides bi-directional protocol translation to exchange necessary information (data and user interactions) between, on the one hand, application-specific protocols, such as MS-RDP, IMAP4 (Internet Mail Access Protocol version 4) or MS-Net SMB (Server Message Block), to communicate with office-based client application, e-mail and file servers; and, on the other hand, HTML, in conjunction with HTTP, as required by the user browser or some other protocol, e.g., AIP or the like, used by an applet within the browser.

P-0031[0031] The SEP establishes a LAN connection for the remote user that, as far as that user is concerned, places the remote PC directly on the LAN. By virtue of such a connection, the remote user can, e.g.: (a) send and receive e-mail through the office e-mail server and manipulate his(her) e-mail stored thereon, (b) access, through the office file server, all his and other shared files stored on and accessible through the LAN as well as transfer files, (c) remotely execute, through the thin-client application server any of his(her) hosted client application programs stored thereon, with real-time results of each of these operations being displayed in HTML form on the user browser.

P-0032[0032] Specifically, the SEP includes a separate client application module for each basic office function: file sharing, e-mail and thin-client application hosting. Each such module accepts as input, in one direction, user interaction data, in the form of URI/URL selection, form input, etc., user mouse clicks and keystrokes provided in HTML form (or in an intermediate transmission protocol, such as AIP), and generates a message, in the appropriate application protocol, containing this data to a corresponding office application. Each such module also operates in the reverse direction by accepting output information, such as a screen shot or data list, produced by its corresponding office application and converting that information, from its application protocol, into a graphical HTML page (or in the intermediate transmission protocol) for transmission to and rendering as a web page by the user browser. Thus, each of these modules acts both as a bridge between the user and a specific one of his(her) office applications and as a protocol translator to enable bi-directional, web-based, real-time communication to occur between the user browser and that particular office application.

P-0033[0033] Furthermore, since user access to the SEP is provided on an authenticated basis, through use of a unique, pre-defined and pre-stored certificate, rather than through use of a symmetric key, the present invention is generally not as susceptible to third-party intrusion through so-called “man in the middle” attacks.

P-0034[0034] In accordance with a feature of our invention, while the principal office-based applications are file sharing, e-mail and thin-client application program hosting, our invention can readily and easily accommodate web-based, secure, remote user access to other additional office-based applications by merely incorporating a corresponding client application module for each such additional office application to provide required bi-directional, real-time protocol translation for both incoming user interaction data to that office application and output data generated by that office application.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0035[0035] The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:

P-0036[0036]FIG. 1 depicts an overall high-level block diagram of a relatively simple and illustrative networked apparatus that embodies the teachings of our present invention and which would be typically used in conjunction with a relatively small office;

P-0037[0037]FIG. 2 depicts a high-level block diagram of service enablement platform (SEP) <b>200</b>, which is used to implement our present invention and as shown in FIG. 1;

P-0038[0038]FIG. 3A depicts a high-level block diagram of software <b>300</b> that executes within SEP <b>200</b> shown in FIG. 2;

P-0039[0039]FIG. 3B depicts principal message paths through software <b>300</b> shown in FIG. 3A for passing communication between LAN and WAN connections and through SEP <b>200</b>, as necessary, for implementing our present invention;

P-0040[0040]FIG. 4 depicts a high-level block diagram of virtual office server software <b>400</b>, executing within the SEP <b>200</b> shown in FIG. 2, for implementing our present invention;

P-0041[0041]FIG. 5 depicts a block diagram of file sharing application module <b>420</b> that forms a part of software <b>400</b> shown in FIG. 4;

P-0042[0042]FIG. 6 depicts state diagram <b>600</b> for state machine <b>522</b> shown in FIG. 5;

P-0043[0043]FIG. 7 depicts illustrative inter-process communication <b>700</b> that involves file sharing application module <b>420</b>, operative in conjunction with file server <b>78</b> (shown in FIG. 1), for obtaining and remotely displaying files for a given user;

P-0044[0044]FIG. 8 depicts a block diagram of e-mail application module <b>430</b> that forms a part of software <b>400</b> shown in FIG. 4;

P-0045[0045]FIG. 9 depicts state diagram <b>900</b> for state machine <b>822</b> shown in FIG. 8;

P-0046[0046]FIG. 10 depicts illustrative inter-process communication that involves e-mail application module <b>430</b>, operative in conjunction with e-mail server <b>76</b> (shown in FIG. 1), for retrieving and remotely displaying a list of incoming e-mail messages for a given user;

P-0047[0047]FIG. 11 depicts a block diagram of thin-client application module <b>440</b> that forms a part of software <b>400</b> shown in FIG. 4;

P-0048[0048]FIG. 12A depicts state diagram <b>1200</b> for state machine <b>1122</b> shown in FIG. 11 for those states associated with a user-initiated interaction with thin-client application server <b>72</b>, shown in FIG. 1, to start a client application session;

P-0049[0049]FIG. 12B depicts state diagram <b>1250</b> for state machine <b>1122</b> shown in FIG. 11 for those states associated with an interaction initiated by client application server <b>72</b>, shown in FIG. 1, specifically to update a display screen on user browser <b>15</b> for an executing thin-client application program;

P-0050[0050]FIG. 13 depicts illustrative inter-process communication that involves thin-client application module <b>440</b>, operative in conjunction with client application server <b>72</b> (shown in FIG. 1), for remotely executing a thin-client application program at server <b>72</b> and displaying graphical results therefrom on user browser <b>15</b>;

P-0051[0051]FIG. 14 shows a highly-simplified, high-level block diagram of administrative web site <b>20</b> shown in FIG. 1;

P-0052[0052]FIG. 15 depicts actual screen shot <b>1500</b> of a typical graphical display screen rendered at user browser <b>15</b>, shown in FIG. 1, through which a remote user logs onto his(her) virtual office capability provided by the present invention;

P-0053[0053]FIG. 16 depicts actual screen shot <b>1600</b> of a typical display screen rendered at user browser <b>15</b>, shown in FIG. 1, for permitting a remote user, through the file sharing capability of the present invention, can remotely access and manipulate his(her) files residing on file server <b>78</b>;

P-0054[0054]FIG. 17 depicts actual screen shot <b>1700</b> of a typical display screen rendered at user browser <b>15</b>, shown in FIG. 1, through which a remote user, through the e-mail capability of the present invention, can remotely access his(her) e-mail stored on e-mail server <b>76</b> as well as send outgoing e-mail to that server; and

P-0055[0055]FIG. 18 depicts actual screen shot <b>1800</b> of a typical display screen rendered at user browser <b>15</b>, shown in FIG. 1, through which a remote user, through thin-client application program support capability of the present invention, can remotely execute his(her) client application programs hosted on client application server <b>72</b>.

P-0056[0056] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.

DETAILED DESCRIPTION

P-0057[0057] After considering the following description, those skilled in the art will clearly realize that the teachings of our present invention can be utilized in any of a wide number of different client-server networked processing architectures that support remote access from a client PC to an office server. In essence, our invention provides remote, secure, web-based user access to network-supported and hosted office processing functions, including client application programs, e-mail and file sharing, to a remotely located user with the same capabilities and essentially the same ease of use as if his(her) computer were directly connected to an office network rather than through a wide area network (WAN) or other remote connection; hence, providing that user with a so-called “virtual office”. Advantageously, our inventive apparatus effectively implements a front-end to the office server, regardless of whether that office server is implemented by a single machine (computer) or multiple machines, and regardless of whether those machines are co-located or not, as long as they are interconnected to the apparatus through an appropriate network. If the office server is implemented by multiple inter-networked machines—as is often the case in medium or large sized organizations, each of these machines can handle one or more specific office processing tasks, e.g., client application program hosting, e-mail serving and/or file serving. Alternatively, for small organizations with limited processing equipment, either our inventive apparatus itself, through its internal processing capability, can implement all these tasks or can serve as a front-end to a single separate machine (computer) which does so. For the sake of simplicity, we will describe our invention for use in an small office environment where either the apparatus serves as a front-end to a single machine situated at an office location that collectively implements all the necessary office processing tasks or additionally implements all those tasks itself. Furthermore, although our invention can readily support simultaneous access by multiple remotely located clients, again for simplicity, we will describe our invention in the context of use with only one such client at a time. Clearly, based on the ensuing description, those skilled in the art can readily appreciate how our inventive architecture can simultaneously accommodate multiple clients and can be scaled upward to simultaneously handle relatively large numbers of such clients.

P-0058[0058]FIG. 1 depicts an overall high-level block diagram of illustrative networked environment <b>5</b> that embodies the teachings of our present invention and is particularly suited for use in conjunction with a small office.

P-0059[0059] As shown, this environment includes remote client <b>10</b>, that is typically a personal computer (PC) generally a laptop, connected through wide area network (WAN) <b>30</b>, to office server <b>40</b> situated at an office site. WAN <b>30</b> can be implemented by a publicly accessible network, such as the Internet, or a private network. Connectivity to the WAN is provided through any relatively high-speed (broadband) access modality such as, e.g., digital subscriber line (DSL), cable modem, integrated service digital network (ISDN), fractional T1 or even a T1 line. Alternatively, remote dial-up analog modem access can be used instead, though end-to-end transport delays, in view of a relatively slow communication speed provided by such a modem, may markedly slow system response as perceived by a user situated at PC <b>10</b>.

P-0060[0060] Our invention advantageously utilizes web-based access to office applications, with those applications being remotely hosted by virtual office server <b>40</b> and encrypted communication provided through conventional secure sockets layer (SSL) capability supported within the browser. As such, client <b>10</b> contains conventional user browser <b>15</b>. Advantageously, since all the office applications are hosted remotely, there is no need to install, configure or maintain any user application programs, other than a web browser, on remote client <b>10</b>; thereby, dramatically reducing cost of ownership of the client PC.

P-0061[0061] Virtual office server <b>40</b> contains conventional broadband WAN interface <b>53</b>, firewall/router <b>57</b>, service enablement platform (SEP) <b>200</b>, and server <b>70</b>. Interface <b>53</b> is conventional in nature and provides high-speed network access. It can take the form of, e.g., a cable modem, a DSL interface, an ISDN terminal adapter or a fractional/full T1 interface. The specific modality of peered-network access used by both client PC <b>10</b> and interface <b>53</b> is not critical provided that the chosen modality can support sufficiently high access speeds between the remote client and server <b>40</b>. Firewall/router <b>57</b> is conventional in nature and attempts to isolate server <b>40</b> from unauthorized network-based attacks as well as provide outgoing and incoming network routing capability to and from WAN <b>30</b>. While interface <b>53</b> and firewall/router <b>57</b> are both shown as being external to the SEP, interface <b>53</b> can be located internal to the SEP as, to the extent needed, can firewall/router <b>57</b>. From a network perspective, SEP <b>200</b> is situated between WAN <b>30</b> (via broadband interface <b>53</b> and firewall/router <b>57</b>) and local area network (LAN) <b>65</b>.

P-0062[0062] In accordance with our inventive teachings and as described in considerable detail below, SEP <b>200</b> provides a front end to server <b>70</b> for implementing secure, remote, web-based access, through browser <b>15</b>, by a user situated at client <b>10</b> to the network-based office functionality implemented by server <b>70</b> and to the same extent as if client PC <b>10</b> were directly connected to LAN <b>65</b>. Server <b>70</b> resides on LAN <b>65</b> to collectively implement, through separate internal LAN accessible application servers, various office processing applications (tasks) including, through client applications server <b>72</b>, thin-client hosted application programs; through web-enabled application server <b>74</b>, remotely-hosted web-enabled thin-client application programs; through e-mail server <b>76</b>, e-mail messaging; and, through file server <b>78</b>, shared file access. Each of these servers is conventional, with E-mail server <b>76</b> being implemented, for example, by a Microsoft Exchange Server (“Microsoft Exchange” is a trademark of Microsoft Corporation of Redmond, Wash.). As noted, in small offices, server <b>70</b> is typically implemented by a single server computer. Alternatively, rather than using two separate physical computers, server <b>70</b> and SEP <b>200</b> can be collectively implemented, as indicated by dot-dashed line <b>60</b>, on one single physical computer—with the necessary processing needed to implement server <b>70</b> being provided by SEP <b>200</b>. However, to facilitate understanding, we will depict SEP <b>200</b>, in terms of its functionality, separate from that of server <b>70</b> or any of the hosted applications and servers executing thereon.

P-0063[0063] Furthermore, during initial configuration of office server <b>40</b>, SEP <b>200</b> establishes a dial-up connection, as symbolized by line <b>59</b>, via WAN <b>30</b>, to administrative web site <b>20</b> (specifically a web site operated by Netilla Networks Inc., which is the present assignee thereof) through which a unique X.509 digital certificate is downloaded to and stored on SEP <b>200</b>, along with other configuration information, such as, e.g., necessary IP addresses. This certificate is used to provide secure conventional, encrypted, authenticated communication that is substantially immune to “man in the middle” attacks. Since the manner through which SEP <b>200</b> utilizes the certificate is conventional, as is the use of SSL by browser <b>15</b>, we will not address these aspects in any detail. Once this certificate and configuration information has been provided over connection <b>59</b>, SEP <b>200</b> establishes a web-based (HTTP) connection to web site <b>20</b> to complete its set-up procedure. SEP <b>200</b>, once fully configured and functioning in a network environment, continually monitors the state of its network connections, both to WAN <b>30</b> and LAN <b>65</b>, as well as the state of LAN <b>65</b> and the various application servers (whether executing in a separate physical computer or on the same computer that implements SEP <b>200</b>), and provides associated maintenance and status information back to a server (not shown) associated with web site <b>20</b>, by establishing a dial-up connection to WAN <b>30</b> via line <b>59</b>, for purposes of remote monitoring, problem diagnosis and routine maintenance. Since none of these particular functions is relevant to the present invention, these functions will not be discussed in any further detail.

P-0064[0064] Once SEP <b>200</b> is fully functioning in its network environment, a user situated at his(her) PC can readily and remotely access his(her) office network-based applications by simply establishing a secure web (HTTPS) connection to a web server implemented on SEP <b>200</b>. To do so, the user enters, through browser <b>15</b>, a web address associated with this server. Once the connection is established, a web page, as shown in screen shot <b>1500</b> for a typical graphical display depicted in FIG. 15, is downloaded by SEP <b>200</b> to the user browser through which, once rendered by the browser, the user then enters his(her) username and password to log on to virtual office capability provided by SEP <b>200</b>. After the user successfully logs in by entering his(her) username and password in fields <b>1510</b> and clicking on “Log In” button <b>1520</b>, a session begins through which a web page is downloaded by SEP <b>200</b>, as shown in FIG. 1, and displayed on the browser through which several icons, illustratively tabs, are displayed: “My Files”, “My E-mail”, “My Apps” and “My Admin” (such as those appearing in screen shots <b>1600</b>, <b>1700</b> and <b>1800</b> of the displays shown in FIGS. 16, 17 and <b>18</b>; all of which are discussed in detail below). The user can then click on any of these icons, which, once communicated back to SEP <b>200</b>, will cause the SEP <b>200</b> to launch the associated office application (or administrative function for the “My Admin” tab), generate an HTML file for a graphical display produced by that application, and then download the HTML file to browser <b>15</b>, for local rendering thereat. During the web session, browser <b>15</b> communicates user form input and URI (uniform resource identifier)/URL (uniform resource locator) selection via HTTP requests to SEP <b>200</b> which processes this input and provides an appropriate display back to the browser. In addition, for application support, an efficient protocol such as AIP (or the like) is used to transfer user keystrokes and mouse clicks from a window on the remote PC representing an application executing on a remote server to SEP <b>200</b>, which then relays that user interaction data to the application server via RDP for processing. Note that RDP itself could have been used between the remote browser and SEP <b>200</b>, but used AIP or a similar protocol provides more efficient bandwidth utilization. The user can readily move between one remote office application to the next by simply clicking on the associated icon.

P-0065[0065] In doing so, SEP <b>200</b> (see FIG. 1) establishes a LAN connection for the remote user that, as far as that user is concerned, places remote client <b>10</b> directly on the LAN. By virtue of such a connection, the remote user can, e.g.: (a) send and receive e-mail through server <b>76</b> and manipulate his(her) e-mail stored thereon, (b) access, through file server <b>76</b>, all his(her) files, as well as other shared files, stored on and accessible through LAN <b>65</b>, (c) remotely execute, through application server <b>72</b>, any of his(her) thin-client applications hosted thereon, as well as through server <b>74</b> remotely execute any of his(her) thin-client web-based applications hosted there, with real-time results of each of these operations being displayed in HTML form on browser <b>15</b>. Application server <b>72</b> receives user mouse clicks and keystroke data and provides user screen shot displays through use of Microsoft RDP (remote desktop protocol). Web-enabled application server <b>74</b> communicates client application information using HTTP. E-mail server <b>76</b> utilizes a conventional IMAP4 protocol; while file server <b>78</b> communicates user information using Microsoft MS-NET Simplified Message Block (SMB) data (to implement Microsoft NET-BIOS functionality). Note, that while SMB and IMAP4 were shown here as examples, other protocols such as Novell Netware and the POP3 (Post Office Protocol 3) are usable as well.

P-0066[0066] In essence, as the reader can appreciate, SEP <b>200</b> acts both as a bridge between the user and his(her) office applications and as a protocol translator to enable bi-directional, web-based, real-time communication to occur between user browser <b>15</b> and each of these office applications. In that regard, the SEP provides bi-directional protocol translation to exchange necessary information (data and user interactions) between, on the one hand, MS-RDP, IMAP4 or MS-Net SMB to communicate with office application servers <b>72</b>, <b>76</b> or <b>78</b>, respectively; and, on the other hand, HTML and HTTP as required by user browser <b>15</b> for non-thin-client applications, and AIP, or a similar protocol, for thin-client control information, or for thin-client user interaction data transfer (i.e., mouse clicks, keystrokes, control data).

P-0067[0067]FIG. 14 depicts a highly simplified, high-level block diagram of administrative web site <b>20</b>.

P-0068[0068] As shown, site <b>20</b> is formed of a front-end portion that provides homepage and user interface web pages, database <b>1420</b> and a back-end portion having interfaces <b>1430</b> and <b>1440</b>.

P-0069[0069] Front-end portion <b>1410</b> provides a home page and user interface which permits users <b>1460</b> to access this site. These users include appropriate Netilla Networks Inc. technical personnel (Netilla Networks Inc. is the present assignee hereof; hereinafter referred to as “Netilla”) as well authorized third-parties, such as Netilla partners (e.g., resellers), system integrators and installers, to log onto site <b>20</b>, on a secure, though restricted basis (depending on the person seeking access). Once appropriate username and password information is entered, each such user gains access for purposes of configuring and determining operational status of any SEP for which (s)he is then providing technical assistance or is responsible. In addition, members of the public can access certain web pages associated with site <b>20</b> that provide general information regarding the services currently offered by Netilla and other related information posted on that site. Database <b>1420</b>, which interacts with both the front- and back-end portions of site <b>20</b>, stores information for each SEP then in service, alarm reports generated by each such SEP and other related status as provided by that SEP, configuration and maintenance information for that SEP, as well as information (such as user name and password) to permit appropriate access to certain secure areas of the site by Netilla technical personnel as well as each authorized third-party user, i.e., resellers, installers and system integrators. Interface <b>1430</b> communicates with individual SEPs (of which, for simplicity, only one SEP <b>200</b> is shown in FIG. 1) in order to permit Netilla technical personnel or an authorized third-party to change configuration information, e.g., a profile, stored on a particular SEP and to instruct web site <b>20</b> to send such changed information to this particular SEP. This information will be stored within database <b>1420</b> and then sent, via this interface, to that SEP. Interface <b>1440</b>, utilizing information stored within database <b>1420</b>, communicates with conventional back-end business applications, such as accounting and billing systems <b>1450</b>, to, among other aspects, establish a new account for a SEP to be or then being installed, modify an existing account and periodically bill an appropriate party, such as a third-party reseller, for use of each SEP for which that party is responsible.

P-0070[0070]FIG. 2 depicts a high-level block diagram of service enablement platform (SEP) <b>200</b>. Though SEP <b>200</b> is depicted with a particular and rather simple architecture, it can alternatively be implemented by nearly any commercially available, general-purpose personal computer, workstation or server, providing it is equipped with two different and distinct Ethernet ports and a modem.

P-0071[0071] As shown, SEP <b>200</b> contains Ethernet I/F ports <b>220</b> and <b>250</b> (also referred to as Ethernet ports 1 and 2), V.90 Fax modem <b>230</b>, and microprocessor <b>260</b>, all interconnected by local bus <b>240</b>. Microprocessor <b>260</b>, which is illustratively any conventional Intel Pentium grade processor or equivalent (having a clock speed of, e.g., 300 MHz or higher) (Pentium is a trademark of Intel Corporation of Santa Clara, Calif.), is itself connected, through bus <b>267</b>, to memory <b>270</b> and via lines <b>263</b> to hard drive <b>280</b>. Memory <b>270</b> is illustratively synchronous dynamic random access memory (SDRAM). Hard drive <b>280</b> stores program <b>300</b> and X.509 certificate <b>284</b>. During operation of SEP <b>200</b>, segments of program <b>300</b>, to the extent needed, are copied from hard drive <b>280</b> into memory <b>270</b> from which those segments are executed. Memory <b>270</b>, being volatile, also stores temporary data, as required during program execution.

P-0072[0072] Ethernet ports 1 and 2 permit the SEP to be situated in series, via LAN connection <b>65</b>, between office server <b>70</b> (see FIG. 1), and, via an Ethernet connection symbolized by line <b>62</b>, to a broadband connection to the WAN, via interface <b>53</b> (through, e.g., firewall/router <b>57</b>). As such, SEP <b>200</b> can intercept incoming network messages incoming from WAN <b>30</b>, perform required protocol conversion and IP address translation on each such message and route that message to a correct office application server on LAN <b>65</b>, and provide the opposite functionality in a reverse direction for outgoing messages.

P-0073[0073] Fax modem <b>230</b> provides analog dial-up connectivity over line <b>59</b> for use, as described above, during installation of SEP <b>200</b>; for communicating monitoring and status information back to administrative web site <b>20</b>, and as a back-up data connection in the event the broadband connection fails. The fax capability of the modem is not used by SEP <b>200</b> unless a specific hosted user (thin-client) application program requests it.

P-0074[0074]FIG. 3A depicts a high-level block diagram of software <b>300</b> that executes within SEP <b>200</b> shown in FIG. 2.

P-0075[0075] This software is composed of two basic components: operating system (O/S) and related modules <b>305</b> and virtual office software <b>400</b>.

P-0076[0076] Component <b>305</b> is formed of a basic O/S kernel <b>310</b>, illustratively a conventional Linux O/S, with specific additional and conventional Linux modules to implement necessary network and web-based processing, and device operation. These modules include network address translation (NAT) module <b>320</b>, IP routing module <b>330</b>, Open SSL module <b>340</b>, web server <b>350</b> (which is currently available under the name “Apache web server”), send mail module <b>360</b>, TCP/IP processing module <b>370</b>, PPP processing module <b>380</b> and device drivers <b>390</b>. Software <b>300</b> includes, as its other component, virtual office software <b>400</b> that communicates, as symbolized by line <b>357</b>, through Apache web server <b>350</b>. Though a Linux O/S kernel is used, O/S <b>310</b> could just as easily be implemented using nearly any other PC or server-based operating system, such as a UNIX or Microsoft Windows operating system—though, of course, the modules would need to be compatible with the chosen O/S.

P-0077[0077] NAT module <b>320</b> is conventional in nature and translates network, specifically IP, addresses as requested by O/S kernel <b>310</b>. In particular, incoming messages from the WAN, depending on its port designation—which identifies a particular office application server and program on server <b>70</b> for which the message is intended, translates the address of that message from the IP address of the SEP to an IP address associated with that particular server. The port designation remains to define the particular server for that message. Similarly, though in a reverse direction, NAT <b>320</b> translates each outgoing message, based on its port address, from each one of the servers and destined to the remote client PC from the private IP address of the server to the public IP address of the SEP along with the corresponding port designation.

P-0078[0078] IP routing module <b>330</b> provides a routing table that provides IP routing information to O/S kernel <b>310</b>. This routing table is established during initial configuration of the SEP from routing information provided from administrative web site <b>20</b> (see FIG. 1). It can, alternatively, be updated via conventional dynamic routing protocols such as RIP, OSPF, etc.

P-0079[0079] Open SSL module <b>340</b>, as shown in FIG. 3A, provides conventional SSL processing—though in a Linux environment, including message encryption/decryption, using X.509 certificate <b>284</b>. This certificate once downloaded during initial configuration of the SEP, is then accessed, as symbolized by line <b>343</b>, by SSL process <b>340</b>. The Apache web server uses the Open SSL module for secure traffic received over TCP port number <b>443</b>.

P-0080[0080] Module <b>350</b> is a conventional web server, though again suited for use in a Linux environment, and provides a web-based portal through which virtual office software <b>400</b> communicates, over a WAN connection, with user browser <b>15</b> and receives user interaction data (mouse clicks and keystrokes therefrom) and provides screen shots thereto for local display on remote PC <b>10</b>.

P-0081[0081] Sendmail module <b>360</b> (also known as “Qmail” for use with the Linux O/S) is conventional and is employed if SEP <b>200</b> is used without an external e-mail server, such as e-mail server <b>76</b> shown in FIG. 1. Module <b>360</b> implements message transmission through use of SMTP (simplified mail transport protocol).

P-0082[0082] TCP/IP processing module <b>370</b> and PPP processing module <b>380</b>, shown in FIG. 3A, are conventional in nature and correspondingly implement a well-known TCP/IP stack (with packet assembly and disassembly) and provide point-to-point protocol (PPP) packet processing for use with packet transmission employing the PPP protocol over dial-up WAN link <b>59</b>.

P-0083[0083] Display drivers module <b>390</b> comprises a set of conventional display drivers operating under control of O/S kernel <b>310</b> to control two Ethernet ports <b>220</b> and <b>250</b>, V.90 fax/modem <b>230</b> and a local LCD display (not shown). Information is communicated between device drivers module <b>390</b> and Ethernet ports <b>220</b> (Port 1) and <b>250</b> (Port 2), and V.90 Fax Modem <b>230</b> as symbolized by lines <b>396</b>, <b>394</b> and <b>398</b>, respectively and, as symbolized by line <b>392</b>, between display drivers module <b>390</b> and O/S kernel <b>310</b>.

P-0084[0084] Communication between O/S kernel <b>310</b> and modules <b>320</b>, <b>330</b>, <b>340</b>, <b>350</b>, <b>360</b>, <b>370</b>, <b>380</b> and <b>390</b> is symbolized by lines <b>325</b>, <b>335</b>, <b>347</b>, <b>353</b>, <b>365</b>, <b>375</b> and <b>385</b>, respectively. Inasmuch as modules <b>320</b>, <b>330</b>, <b>340</b>, <b>350</b>, <b>360</b>, <b>370</b> and <b>380</b> are all conventional and readily available Linux components, none of them will not be discussed in any further detail.

P-0085[0085] Virtual office software <b>400</b>, operative in conjunction with web server module <b>350</b>, forms a core software component of our present inventive apparatus. In that regard, software <b>400</b> (which is discussed in detail below) implements real-time, bi-directional protocol translation, as described above, to enable the user situated at remote PC <b>10</b> to remotely control, execute and interact with any office application hosted at server <b>70</b> (see FIG. 1). In that regard, through appropriate protocol conversion, software <b>400</b>, as shown in FIG. 3A, exchanges necessary information (data and user interactions) between, on the one hand, MS-RDP, IMAP4 or MS-Net SMB to communicate with office application servers <b>72</b>, <b>76</b> or <b>78</b> (see FIG. 1), respectively; and, on the other hand, HTML and HTTP (or an intermediate transport protocol—AIP) as required by user browser <b>15</b> for non-thin-client applications, and AIP or a similar protocol for thin-client applications—all as required to support centralized hosting of office applications (e.g., user application hosting, file serving, and e-mail) but with user interaction and application display occurring remotely at the client computer under the browser. Modules <b>320</b>, <b>330</b>, <b>340</b>, <b>360</b>, <b>370</b> and <b>380</b>, as shown in FIG. 3A, all provide necessary network packet processing, including address translation, encryption/decryption and send mail functionality, ancillary to software <b>400</b> but necessary to support proper packet communication over a WAN connection between it and both remote PC <b>10</b> and individual office applications executing on local server <b>70</b> (shown in FIG. 1).

P-0086[0086]FIG. 3B depicts principal message paths through software <b>300</b> for passing communication between LAN and WAN connections and through SEP <b>200</b>.

P-0087[0087] Given the location of the SEP intermediate between LAN <b>65</b> and WAN <b>30</b>, three basic paths, i.e., paths <b>402</b>, <b>404</b> and <b>406</b>, exist, all three of which are under the control of O/S kernel <b>310</b>. Note that paths <b>404</b> and <b>404</b><i>a </i>are common from the bottom of the figure to a point just below the Apache web server. From that point, path <b>404</b> continues through the Apache web server to the virtual office software, while path <b>404</b><i>a </i>bypasses the Apache web server and goes directly to the virtual office software.

P-0088[0088] First, incoming packets from the WAN connection, i.e., originating from remote PC <b>10</b> (see FIG. 1) and containing user interaction information relevant to non-thin-client functionality (e.g., user URI/URL selection, forms inputs, etc.) flows, as symbolized by dashed line <b>404</b> (also labeled as path “B” in FIG. 3B), through Ethernet port <b>220</b> (port 1), within the SEP through device drivers module <b>390</b>, and via the O/S kernel, to TCP/IP processing module <b>370</b> for appropriate TCP/IP packet processing, including packet disassembly. From TCP/IP processing module <b>370</b>, the resulting information in the disassembled packet is provided by O/S kernel <b>310</b>, to web server <b>350</b>, which calls on services of Open SSL <b>340</b> to perform SSL processing on the packet if necessary; for the Netilla Virtual Office, all information transfer is protected by SSL. After SSL processing, the HTTP request is extracted and sent to virtual office software <b>400</b> for protocol translation into a form suitable for use by a desired office application. Once virtual office software <b>400</b> has appropriately processed the information, by providing suitable protocol conversion, that information flows directly from software <b>400</b> to that office application accessible through the LAN if necessary (i.e., if it cannot be handled directly by the virtual office software). Information (such as the network neighborhood for the file sharing application) from the SEP destined to the remote user flows along path <b>404</b> but in an opposite direction to that just described so as to provide the opposite functionality.

P-0089[0089] Incoming packets from the WAN connection, i.e., originating from remote PC <b>10</b> (see FIG. 1) and containing user interaction information relevant to thin-client functionality (e.g., starting of a thin-client application, keystrokes and mouse clicks associated with a thin-client application, etc.) flows, as symbolized by dashed line <b>404</b><i>a </i>(also labeled as path “B” in FIG. 3B), through Ethernet port <b>220</b> (port 1), within the SEP through device drivers module <b>390</b>, and via the O/S kernel, to TCP/IP processing module for appropriate TCP/IP packet processing, including packet disassembly. From TCP/IP processing module <b>370</b>, the resulting information in the disassembled packet is provided by O/S kernel <b>310</b>, to virtual office software <b>400</b> via path <b>404</b><i>a </i>(path <b>404</b> and <b>404</b><i>a </i>are identical except at the very end; <b>404</b> goes to the Apache web server while <b>404</b><i>a </i>goes to the virtual office software). Once virtual office software <b>400</b> has appropriately processed the information by providing suitable protocol conversion (including performing SSL operations on the data), that information flows directly from software <b>400</b> to that office application accessible through the LAN via path <b>402</b>, as described below, if necessary (i.e., if it cannot be handled by the virtual office software directly). Information (such as a thin-client screen update for a particular thin-client application, such as Microsoft Word, for example) from the SEP destined to the remote user flows along path <b>404</b><i>a </i>and then via path <b>404</b> but in an opposite direction to that just described so as to provide the opposite functionality.

P-0090[0090] Information incoming to the SEP from the LAN and which is ultimately destined to the remote user for non-thin-client applications (e-mail and file sharing) flows as shown by dotted path <b>402</b> (also labeled as path “A”) within the SEP. This information is first received by Ethernet interface <b>250</b> (port 2), which is connected to the LAN, and from there transits through device drivers module <b>390</b>, O/S kernel <b>310</b>, TCP/IP processing module <b>370</b> (again for packet disassembly), then back through the O/S kernel to virtual office software <b>400</b>. For non-thin-client data (i.e., data involved with file sharing or e-mail), software <b>400</b> generates an appropriate HTML page via an HTTP response containing this information and thereafter provides this page to web server <b>350</b>. The web server calls on the services of Open SSL to provide appropriate security functions, and then transmits this page, via an HTTP response, to the remote client PC, specifically user browser <b>15</b> for display thereat. The data path from the virtual office software subsequently follows path <b>404</b> described previously. Information from the SEP, i.e., originating from the user, to the LAN flows in a reverse direction to that described in order again to provide the opposite functionality.

P-0091[0091] Information incoming to the SEP from the LAN and which is ultimately destined to the remote user for thin-client applications flows as shown by dotted path <b>402</b> (also labeled as path “A”) within the SEP. This information is first received by Ethernet interface <b>250</b> (port 2), which is connected to the LAN, and from there transits through device drivers module <b>390</b>, O/S kernel <b>310</b>, TCP/IP processing module <b>370</b> (again for packet disassembly), then back through the O/S kernel to virtual office software <b>400</b>. For thin-client data (i.e., data involved with application execution on servers on the LAN), virtual office software <b>400</b> performs data protocol conversion if necessary (for example, from RDP to AIP), along with the appropriate image conversions. Software <b>400</b> then generates appropriate AIP packets, on which it performs security operations on as necessary, and then forwards those packets along path <b>404</b><i>a </i>to the remote client PC, specifically user browser <b>15</b> for display thereat. Information from the SEP, i.e., originating from the user, to the LAN flows in a reverse direction to that described in order again to provide the opposite functionality.

P-0092[0092] Note that in the traversals described above, the transference of data is traced through the O/S kernel as much as possible. However, since the kernel is involved in essentially all operations that occurs in the SEP, FIG. 3B only shows those data flows particularly pertinent to the present invention, else showing every single interaction with the kernel would result in overwhelmingly complex data flow diagram with essentially nothing gained from a perspective of understanding. Thus, for example, when the Apache web server hands off data to the virtual office software, it must use some kernel services to do so. But this does not add to the understanding, and unnecessarily complicates the diagram if one were to show this—therefore, FIG. 3B traces a direct path between the web server software and the virtual office software.

P-0093[0093] Lastly, information incoming to the SEP through the dial-up connection, such as from administrative web site <b>20</b>, flows as shown by dot-dashed path <b>406</b> (also labeled as path “C”). This information is first received by V.90 fax modem <b>230</b>, such as from the administrative web site via the WAN, and from there transits through device drivers module <b>390</b>, O/S kernel <b>310</b> and PPP processing module <b>380</b>. Once module <b>380</b> has provided requisite PPP processing, O/S kernel <b>310</b> routes the resulting processed message to TCP/IP processing module <b>370</b> (again for packet disassembly), then back through the O/S kernel to virtual office software <b>400</b>, via web server <b>350</b>, for protocol translation into a form suitable for use by a desired office management process or application and subsequent application to the appropriate office application server, if necessary. Outgoing information from the SEP, i.e., originating from an office management process or application server and destined to, e.g., the administrative web site but carried through the dial-up WAN connection flows in a reverse direction to that described in order to provide the opposite functionality. Specifically, for such outgoing information, software <b>400</b> first receives the information from the office management process or application server and then applies this information to web server <b>350</b> which in turn imparts HTTP processing of this message. The message then transits, via the O/S kernel, to TCP/IP processing module <b>370</b> and PPP processing module <b>380</b> prior to be routed, via device drivers <b>390</b>, to the V.90 fax modem for transmission, via dial-up WAN connection <b>62</b>, to the user browser. Note that sessions originating from the SEP, such as sessions to the administrative web site from the management process in the SEP, would follow essentially the same outgoing and incoming paths, except that they would not go through the Apache web server.

P-0094[0094]FIG. 4 depicts a high-level block diagram of virtual Office server software <b>400</b>.

P-0095[0095] As shown, software <b>400</b> contains four office application modules: file sharing application module <b>420</b>, e-mail application module <b>430</b>, thin-client application module <b>440</b> and administration module <b>450</b>; along with multiplexor <b>410</b>.

P-0096[0096] In general, each of the modules accepts as input, in one direction, user interaction data, in the form of user URI/URL inputs and form data provided via HTTP/secure HTTP or in the form of keystrokes, mouse clicks, etc. encoded via a transport protocol such as AIP (optionally secured by SSL) for the thin-client support) and generates a message, in an appropriate application protocol, containing this data to a corresponding office application. Each such module also operates in the reverse direction by accepting output information, such as a screen shot or data list, produced by its corresponding office application and converting that information, from its application protocol, into a graphical HTML page in a secure HTTP Response or into a transport protocol such as AIP secured by SSL for thin-client support for transmission to and rendering, as a web page, by the user browser. Thus, each of these modules acts both as a bridge between the user and a specific one of his(her) office applications and as a protocol translator to enable bi-directional, secure, web-based, real-time communication to occur between user browser <b>15</b> and that particular office application.

P-0097[0097] File-sharing application module <b>420</b> (described in detail below in conjunction with FIGS. <b>5</b>-<b>7</b>) interacts with a client file handler (specifically a Linux “SAMBA” module which is an open source software component which implements a NET-BIOS Windows Networking client on a Linux O/S to interact with Windows based file servers) to provide user file information, such as listings of desired directories, and permit the user to copy, move and delete files, as desired.

P-0098[0098] E-mail application module <b>430</b> (described in detail below in conjunction with FIGS. <b>8</b>-<b>10</b>) interacts with a client e-mail handler (specifically an IMAP client) to access and retrieve user e-mail stored on an e-mail server, such as a Microsoft Exchange server, as well as to manipulate stored e-mail residing in his(her) e-mail folders (Inbox, Outbox, Sent Mail and the like) on that server. In terms of message reception, module <b>430</b> provides a list of received messages, typically with address and truncated content information—as typically occurs in e-mail clients (such as in Microsoft Outlook e-mail client program; “Microsoft Outlook” is a trademark of the Microsoft Corporation of Redmond, Wash.) and, once displayed, permits the user to select and separately and fully display each message as desired. This module also permits the user to send outgoing e-mail to and through that server.

P-0099[0099] Thin-client application module <b>440</b> (described in detail below in conjunction with FIGS. <b>11</b>-<b>13</b>) interacts, through the remote desktop protocol (RDP), with a client application program (e.g., Microsoft Word, Microsoft Excel or other application program; “Microsoft Word” and “Microsoft Excel” are trademarks of the Microsoft Corporation of Redmond, Wash.) being hosted on server <b>70</b>. Module <b>440</b> receives user mouse clicks and keystrokes from the user browser, in AIP form, and passes that information, via RDP, to the client application program to control its execution. In return, this module obtains graphical output displays, as screen shots, generated by the client application program and in RDP form, and converts those screen shots into AIP form and then transmits AIP messages, containing the screen shots, back to the user, specifically the user browser for rendering thereat.

P-0100[0100] Administration module <b>450</b> maintains lists of user names and passwords and other information necessary to permit controlled, secure, remote access to the virtual office functionality as well as to properly monitor its ongoing operation. This module interacts through web server <b>350</b> and contains a conventional internal database and associated processes (all of which are not shown but well known) to maintain lists (including establishing initial lists and updating them as needed) of authorized user names and passwords, and, based on login information supplied by a user then seeking remote access, determine whether that user is to be permitted to access virtual office functionality and, if so, to enable such access. This module also alerts administrative web site <b>20</b> (see FIG. 1) if, as a result of its monitoring tasks, it detects any abnormal operation for any of the virtual office functionality. Since this module is not particularly relevant to the present invention, we will not discuss it in any further detail.

P-0101[0101] Multiplexor <b>410</b> passes each outgoing message from each of the modules destined to the user to web server <b>350</b> or directly to TCP/IP module <b>370</b> for the thin-client processing, as well as each incoming message from the user, as received by the web server or directly from the TCP/IP module, to an associated one of the application modules. Communication between each of applications <b>420</b>, <b>430</b>, <b>440</b> and <b>450</b>, and multiplexor <b>410</b> is symbolized by lines <b>425</b>, <b>435</b>, <b>445</b> and <b>455</b>, respectively; while communication between the multiplexor and the web server is symbolized by line <b>357</b> and communication between the multiplexor and the TCP/IP module is symbolized by line <b>358</b>.

P-0102[0102]FIG. 5 depicts a block diagram of file sharing application module <b>420</b> that forms a part of software <b>400</b> shown in FIG. 4. As noted above, this module interacts with a client file handler (file server) to provide the remote user with his(her) file information, such as listings of desired directories, and permit that user to copy, move and/or delete files to which that user has appropriate access.

P-0103[0103] Module <b>420</b> contains SAMBA component <b>510</b>, file sharing front end component <b>520</b> and HTML pages <b>530</b>.

P-0104[0104] SAMBA component <b>510</b> is a conventional open source LINUX component that implements a NET-BIOS Windows Networking client for interacting with a Windows remote file server, here file server <b>78</b> on LAN <b>65</b>. File sharing front end <b>520</b> is itself formed of state machine <b>522</b> and user interaction component <b>526</b> which communicate with each other through an application programming interface (API) as symbolized by line <b>524</b>.

P-0105[0105] User interaction component <b>526</b> obtains, as symbolized by line <b>540</b>, user interaction data, i.e., URL/URI selection and form input, incoming from multiplexor <b>15</b> and contained in secure HTTP requests provided by user browser <b>15</b>, representative of a user request to file server <b>78</b>. Component <b>526</b> extracts the information from these web pages. This request can take the form of, e.g., the user clicking, through his(her) user browser, on a displayed icon in order to obtain a network environment (“network neighborhood”) listing for the LAN or a directory or sub-directory listing for a particular computer then connected to the LAN. Once component <b>526</b> obtains sufficient user interaction data to issue the request to the file server, this component then translates this interaction data into a corresponding request to state machine <b>522</b>. The state machine, in turn, interprets this request into a sequence of specific commands, by issuing one command at a time based, where appropriate, on a immediately prior response from the file server. In that regard, state machine <b>522</b> applies, as symbolized by line <b>515</b>, a command to SAMBA component <b>510</b> which directly interacts, over the LAN and as symbolized by dashed line <b>505</b>, with file server <b>78</b>. File server <b>78</b> provides its response to that command back to SAMBA component <b>510</b> which, in turn, provides that response to state machine <b>522</b>. Based on each response it receives, via SAMBA component <b>510</b> and via line <b>515</b>, from file server <b>78</b>, state machine <b>522</b> will react accordingly and could issue another command, via the SAMBA component, to the file server for additional data which the state machine then needs to fulfill the user request or, if all such data has then been received, construct a suitable response containing that data (if any) and provide it, via API <b>524</b>, to user interaction component <b>526</b>. Once the data has been provided to component <b>526</b>, that component will retrieve, based on the nature of the user request and as symbolized by line <b>535</b>, a corresponding stored HTML template page from stored pages <b>530</b> and populate that template with the data returned in the list. Component <b>526</b> then returns, here symbolized by line <b>540</b>, a resulting populated HTML page, via multiplexor <b>410</b>, to web server <b>350</b> for transmission, via HTTP, to user browser <b>15</b> for rendering thereat.

P-0106[0106]FIG. 16 depicts actual screen shot <b>1600</b> of a typical graphical display produced, at user browser <b>15</b>, by component <b>420</b> for depicting and manipulated shared user files. This capability is invoked by the user having clicked on the “My Files” tab in display area <b>1610</b>. Visual feedback of that selection is illustratively provided through a highlighted background for this tab.

P-0107[0107] As depicted in screen shot <b>1600</b>, a network neighborhood, showing various computers then available on the LAN, appears in graphical form as a vertical list in left panel <b>1630</b> with each computer being represented by an icon and its machine name. Should a user click on any icon in the left panel, user interaction component <b>526</b> will generate, based on information it receives from state machine <b>522</b> and originating from file server <b>78</b>, a hierarchical display under that icon, in effect expanding that hierarchy one level, to show a next lower level in the hierarchy, and so on. Hence, all the directories for the machine represented by the icon will be displayed directly under that icon and appropriately indented and graphically linked to show their hierarchical relationship. The contents at that lower level of the hierarchy or any user selected item at that level will be displayed in right panel <b>1640</b>. The user can then click on any directory at that hierarchical level, on either the left or right panels, to gain a listing of the next lower hierarchical level, and so forth, with the further expanded hierarchy shown in left panel <b>1630</b> and the contents of any selected item at that lower level in that hierarchy shown in right panel <b>1640</b>. At a lowest level of the hierarchy, panel <b>1630</b> will depict the sub-directories at that level with panel <b>1640</b> depicting the files for a selected sub-directory thereat. By successively clicking on an icon in the hierarchy, the user can drill down the hierarchy to examine a particular sub-directory of interest on a desired networked machine available on LAN <b>65</b>. The illustrative display in screen shot <b>1600</b> specifically depicts a high level of the hierarchy prior to the user selecting any of the network-connected computers for further examination. Further, by clicking on an “Up”, “New Folder”, “Paste” or “Upload” button in display area <b>1620</b>, the file sharing application module will display a next higher level of the hierarchy, create a new folder (or file), paste a folder into a desired location in the hierarchy or upload a selected folder residing on the remote client PC to a desired location at the file server, respectively. Note that popup menus are provided when, at particular levels of the hierarchy, to allow for features such as the copying, deleting, etc. of files and directories.

P-0108[0108] To gain improved understanding of the operation of file sharing application module <b>420</b>, the reader should now simultaneously refer to FIGS. 6 and 7.

P-0109[0109]FIG. 6 depicts state diagram <b>600</b> for file sharing front-end state machine <b>522</b>. FIG. 7 depicts illustrative inter-process communication <b>700</b> that involves file sharing application module <b>420</b>, operative in conjunction with the file server <b>78</b>, for obtaining and remotely displaying files for a given user.

P-0110[0110] As shown, state machine <b>622</b> contains four distinct states: null state <b>610</b>, command interpretation state <b>620</b>, waiting for response state <b>630</b> and response construction state <b>640</b>.

P-0111[0111] Initially, state machine <b>522</b> resides in null state <b>610</b>. One a user clicks on the “My File” icon in the Netilla virtual office graphical interface (e.g., displays <b>1600</b>, <b>1700</b> or <b>1800</b> shown in FIGS. 16, 17 or <b>18</b>), this operation being symbolized by line <b>710</b>, user browser <b>15</b> issues, symbolized by line <b>720</b>, an appropriate HTTP request instruction (“HTTP_GET_REQ (hosts)”) to fetch the name of all the hosts on the LAN. File sharing front end <b>520</b>, specifically user interaction component <b>526</b> (see FIG. 5) receives this command, and in response thereto, issues a command to the state machine, such as “GET_SERVER_LIST”, to identify all the file servers on LAN <b>65</b>. State machine <b>522</b> then transitions as symbolized by path <b>615</b> (in FIG. 6), to command interpretation state <b>620</b>. While in this state, state machine <b>522</b> interprets the “GET_SERVER_LIST” command to yield a sequence of commands to SAMBA component <b>510</b> to query component <b>510</b> for the desired information. In particular, for the “GET_SERVER_LIST” command, command interpretation state <b>620</b> will first issue, as symbolized by line <b>730</b>, a “NMBLOOKUP -M-” command to SAMBA component <b>510</b> to query file server <b>78</b> for a list of master browsers then operating on the LAN. A master browser identifies a computer that contains a list of names of all the computers then accessible on the LAN for a particular domain. The SAMBA component will, in turn, send appropriate commands to file servers <b>78</b> to satisfy this query. Once this command is issued, state machine <b>522</b> will then transition, as symbolized by line <b>625</b>, to state <b>630</b> wherein the state machine will simply wait, as represented by line <b>633</b>, for a response from the file servers as provided by SAMBA component <b>510</b>. Eventually, the file servers responds to the SAMBA query through which, as a result, SAMBA component <b>510</b> provides, as symbolized by line <b>740</b> a list of the master browsers for each domain on the LAN to state machine <b>522</b> within file sharing front-end component <b>520</b>. In response, state <b>630</b> will determine if the state machine has received all the responses from the file server needed to satisfy the user request or whether additional information is necessary. If the latter occurs, then state <b>630</b> will transition, as symbolized by line <b>635</b>, back to command interpretation state <b>620</b> for the latter state to issue the next SAMBA command in sequence, and so forth. In the present example, once the list of master browsers is returned, command interpretation state <b>620</b> issues, as symbolized by line <b>750</b>, an “SMBCLIENT -L hostname” command where “hostname” is the name of the master browser for a particular domain on the LAN. In response to this latest command, again state machine <b>522</b> transitions, as symbolized by line <b>625</b>, to state <b>630</b> at which the state machine remains (as symbolized by line <b>633</b>) until it receives an appropriate response from the file server via the SAMBA command. In response to this command, the file server returns a list of services, a list of shares and a list of computers associated with the corresponding domain, which the SAMBA component in turn, passes, as symbolized by line <b>760</b>, back to file sharing front end <b>520</b> and specifically to state machine <b>522</b> therein. At this point, all the needed information has been received for this particular user request. Hence, state machine <b>522</b> transitions, as symbolized by line <b>637</b>, to response construction state <b>640</b>. Through this state, state machine <b>522</b> constructs a linked list that contains all the information supplied by the file server in response to the “GET-SERVER-LIST” message (which was originally sent as a result of the receipt of the “HTTP_GET_REQ (/hosts) message” and provides that list back to user interaction component <b>526</b>. Once this occurs, state machine <b>526</b> returns, as symbolized by line <b>645</b>, back to null state <b>610</b>. Once the user interaction component receives the linked list, it accesses an appropriate HTML template web page and populates that page with the information provided in the response. After the page is fully constructed, the user interaction component sends, as symbolized by line <b>770</b>, that page back through multiplexor <b>410</b> to web server <b>350</b>, via an “HTTP_GET_RESP” message, for transmission to user browser <b>15</b> to depict a graphical rendering of the hosts specified by the file server, e.g., a page of the form shown by screen shot <b>1600</b> for the typical display shown in FIG. 16. Response construction state <b>640</b>, shown in FIG. 6, is also entered from state <b>630</b> if excess time, i.e., a timeout condition, has occurred once a command has been issued to the SAMBA component without any corresponding response therefrom (which could be as a result of a problem with the SAMBA component, with the LAN itself, or with server(s) on the LAN. As such, state <b>640</b> will specify this timeout condition to the user interaction component which, in turn, will construct and then transmit a web page to user browser <b>15</b> notifying the user of an timeout/error condition.

P-0112[0112] Not only can the user display files through interaction with user browser <b>15</b>, but also, depending upon current permissions which this user then has, (s)he can move or copy selected files from one directory (sub-directory) to another, or delete such files. File sharing module <b>420</b>, including state machine <b>522</b>, operates in a very similar manner as that described above, with identical states though different commands, to execute file copy, move and delete operations through file server <b>78</b> in response to corresponding remote user interactions through user browser <b>15</b>.

P-0113[0113]FIG. 8 depicts a block diagram of e-mail application module <b>430</b> that forms a part of virtual office software <b>400</b> shown in FIG. 4. As noted above, module <b>430</b> interacts with a client e-mail IMAP handler to access and retrieve user e-mail stored on an e-mail server as well as to manipulate stored e-mail residing in his(her) e-mail folders (Inbox, Outbox, Sent Mail and the like) residing on that server.

P-0114[0114] Module <b>430</b> contains IMAP (Internet Message Access Protocol) client component <b>810</b>, e-mail front end component <b>820</b> and HTML pages <b>830</b>. As can be appreciated, module <b>430</b> has a very similar architecture to file sharing application module <b>420</b> shown in FIG. 5, as well as to thin-client application module <b>440</b> shown in FIG. 11 (and discussed in detail below).

P-0115[0115] IMAP client component <b>810</b> is a conventional e-mail client component that provides rich interaction with a mail server, such as Microsoft Exchange server, that supports the IMAP4 protocol. For example, the IMAP client downloads and displays stored e-mail messages, residing on the mail server, from an Inbox associated with a user. The IMAP client then permits the user to move and copy mail messages from one folder at the server associated with that user (e.g., Inbox) to another such folder (e.g., Sent), as well as delete any such messages from any such folder. E-mail front end <b>820</b> is itself formed of state machine <b>822</b> and user interaction component <b>826</b> which communicate with each other through an application programming interface (API) as symbolized by line <b>824</b>.

P-0116[0116] User interaction component <b>826</b> (in a similar manner as does user interaction component <b>526</b> described above) obtains, as symbolized by line <b>840</b>, user interaction data, i.e., form input data and URI/URL selections, incoming from multiplexor <b>15</b> and contained in HTTP requests provided by user browser <b>15</b>, representative of a user request to e-mail server <b>76</b>. Component <b>826</b> extracts the information from these requests. This request can take the form of, e.g., the user clicking, through user browser <b>15</b>, on the “My E-mail” tab to access and list the user's e-mail then residing in his(her) Inbox on the e-mail server. Such an interaction results in the user browser issuing an “HTTP_GET_REQ (/Inbox)” message (request) to obtain an HTML page in response (via an HTTP Response) that contains the desired list. Further, once this page and its list are returned and graphically rendered by the user browser, subsequent user interaction can take the form of the user clicking on an icon associated with a different folder of e-mail messages to obtain a list of the messages, in abbreviated form, in that folder; as well as the user clicking on any such entry in any such list then being displayed to expand that rendered version of the message. Similarly, the user, through appropriate mouse manipulation, can drag and drop, hence rearranging, e-mail messages from one of his(her) folders to another.

P-0117[0117] Once component <b>826</b> obtains sufficient user interaction data from the user—which in the simple case of the user clicking on the “My E-mail” tab is the HTTP request message, via web server <b>350</b> (see FIG. 3A) and multiplexor <b>410</b>, to issue a request to the e-mail server, this component then translates this interaction data into a corresponding request to state machine <b>822</b>, shown in FIG. 8. The state machine, in turn, interprets this request into a sequence of specific commands, by issuing one command at a time based, where appropriate, on a immediately prior response from the e-mail server. In that regard, state machine <b>822</b> applies, as symbolized by line <b>815</b>, a command to IMAP client component <b>810</b> which directly interacts, as symbolized by dashed line <b>805</b> and over LAN <b>65</b>, with e-mail server <b>76</b>. E-mail server <b>76</b> provides its response to that command back to IMAP client component <b>810</b> which, in turn, provides, via line <b>815</b>, that response to state machine <b>822</b>. Based on each response it receives, via IMAP client component <b>810</b>, from e-mail server <b>76</b>, state machine <b>822</b> will react accordingly and issue another command, via the IMAP client component, to the e-mail server for additional data which the state machine then needs to fulfill the user request or, if all such data has then been received, construct a suitable response containing that data and provide it, via API <b>824</b>, in the form of a linked list to user interaction component <b>826</b>. Once the linked list has been provided to component <b>826</b>, that component will retrieve, based on the nature of the user request and as symbolized by line <b>835</b>, a corresponding stored HTML template page from stored pages <b>830</b> and populate that template with the data returned in the list. Component <b>826</b> then returns, here symbolized by line <b>840</b>, a resulting populated HTML page, via multiplexor <b>410</b>, to web server <b>350</b> for transmission, via HTTP, to user browser <b>15</b> for rendering thereat.

P-0118[0118]FIG. 17 depicts screen shot <b>1700</b> of a typical graphical display produced, at user browser <b>15</b>, by component <b>420</b> for depicting e-mail usage. This capability is invoked by the user having clicked on the “My E-mail” tab in display area <b>1710</b>. Visual feedback of that selection is again illustratively provided through a highlighted background for this tab.

P-0119[0119] As depicted in display <b>1700</b>, a vertical list of the e-mail folders available for that user is graphically provided in left display panel <b>1730</b>. These folders include “Inbox”, “Drafts”, “Sent Items” as well as other folders such as “Spam” including those the user has specifically defined. When this capability is first invoked, a listing of the user's e-mail in his(her) Inbox folder is displayed in abbreviated form in mail list (upper right) display area <b>1740</b> as entries in a vertical table with contents of a most recent entry in that folder being displayed in mail content (lower right) display area <b>1750</b>. Here, that table contains only one illustrative entry with its specific contents being displayed. Should the mail list contain multiple entries, the user can click on any such entry. In response, user interaction component <b>826</b> will display the contents of the message, associated with that entry, in display area <b>1750</b>. The specific folder then being displayed is graphically indicated through an change (here being a small overlaid envelope symbol) in its displayed icon (as shown for the Inbox icon). Similarly, if the user clicks on an icon for a different folder, then display area <b>1740</b> will list the contents of that folder from which the user can select, again by clicking, a desired entry to reveal its contents in display area <b>1750</b>. In addition, through tool <b>1760</b>, specifically selection of either a “Move” or “Copy” link within links <b>1763</b> and selection of a desired folder through pull-down menu <b>1767</b>, the user can move or copy the presently displayed e-mail message to the selected folder. Contacts display area <b>1770</b> provides various folders which contain contact information, e.g., names, addresses—both postal and e-mail, telephone and facsimile numbers, and other information stored and organized by that user in various folders. Further, when the user clicks on a “New Mail”, “Reply”, “Reply All” or “Forward” button in display area <b>1720</b>, the e-mail application module will correspondingly invoke associated functionality to compose a new e-mail message; compose a reply message to the sender of a message then being displayed in area <b>1750</b> or to the sender and all recipients of that message, or forward the message then being displayed in area <b>1750</b> to a desired recipient, such as those in any of contacts folders. By clicking on a “Print” or “Delete” button in area <b>1720</b>, the e-mail application module will invoke associated functionality to print the e-mail message then selected in area <b>1740</b> or displayed in area <b>1750</b>, or to delete that message, respectively. Lastly, when the user clicks on the “Send/Rec”, “Addresses”, “Purge” or Find” buttons, the e-mail application module will correspondingly invoke functionality to toggle its mode from receiving to sending e-mail, list addresses through a conventional address book capability, purge a mail folder then being displayed of its entries, and finally undertake a search through an e-mail folder then being displayed for a desired message.

P-0120[0120] To gain improved understanding of the operation of e-mail application module <b>430</b>, the reader should now simultaneously refer to FIGS. 9 and 10.

P-0121[0121]FIG. 9 depicts state diagram <b>900</b> for e-mail front-end state machine <b>822</b>. FIG. 10 depicts illustrative inter-process communication <b>1000</b> that involves e-mail module <b>430</b>, operative in conjunction with the e-mail server <b>76</b>, for retrieving user e-mail messages residing on that server.

P-0122[0122] As shown, state machine <b>822</b> contains four distinct states (similar to those in state diagram <b>600</b> shown in FIG. 6 for state machine <b>522</b> in file sharing application module <b>420</b>): null state <b>910</b>, command interpretation state <b>920</b>, waiting for response state <b>930</b> and response construction state <b>940</b>.

P-0123[0123] Initially, state machine <b>822</b> resides in null state <b>910</b>. One a user clicks on the “My E-Mail” icon in the Netilla virtual office graphical interface (e.g., displays <b>1600</b>, <b>1700</b> or <b>1800</b> shown in FIGS. 16, 17 and <b>18</b>, respectively), this operation being symbolized by line <b>1010</b>, user browser <b>15</b> issues, as symbolized by line <b>1015</b>, an appropriate HTTP request instruction (“HTTP_GET_REQ (/Inbox)”) to fetch the contents of the user's Inbox. The e-mail application module, now acting through the IMAP client, interacts with the e-mail server, via the IMAP protocol, to retrieve a message list for the user's Inbox.

P-0124[0124] In doing so, e-mail front end <b>820</b>, specifically user interaction component <b>826</b> (see FIG. 8) receives this command, and in response thereto, issues a command, “GET_INBOX_LIST”, to state machine <b>822</b>. State machine <b>822</b> then transitions as symbolized by path <b>915</b>, to command interpretation state <b>920</b>. While in this latter state, state machine <b>822</b> interprets the “HTTP_GET_REQ (Inbox)” command to yield a sequence of commands to IMAP client component <b>810</b> to query e-mail server <b>76</b> for the desired inbox mail list.

P-0125[0125] For this HTTP command, command interpretation state <b>930</b> will first issue, as symbolized by line <b>1020</b>, a “A101 SELECT INBOX” command to the e-mail server to select the proper inbox on the e-mail server. Term “A101” (as well as similar term “A102”, and so forth) is a transaction tag assigned to this particular interaction between the state machine and the e-mail server such that server responses can be paired, by the state machine, with appropriate IMAP client requests. Identical circled numerals are shown in FIGS. 9 and 10 in order for the reader to visually correlate specific inter-component messages shown in communications <b>1000</b> with their corresponding events (including state transitions) in state diagram <b>900</b>. Once the “SELECT INBOX” command is issued, state machine <b>822</b> will then transition, as symbolized by line <b>925</b>, to state <b>930</b> wherein the state machine will simply wait, as represented by line <b>934</b>, for a response from the e-mail server as provided by IMAP client component <b>810</b>. Eventually, the e-mail server responds to the “SELECT INBOX” command through which, as a result, IMAP client <b>810</b> provides, as symbolized by lines <b>934</b> and <b>1025</b>, an indication of the number of messages in the user's Inbox. In the example shown in FIGS. 9 and 10, the response is “*3 EXISTS” which signifies that the Inbox contains three messages. This is followed by a “A101 OK [READ-WRITE] SELECT completed” response from the IMAP Server indicating that the A101 transacting has been completed, and that the Inbox can be read or written during this session. In response, state <b>930</b> will determine if the state machine has received all the responses from the e-mail server needed to satisfy the user request or whether additional information is necessary. For the example shown, at this point in the processing, state <b>930</b> will determine that messages need to be fetched from the e-mail server. Accordingly, once the “A101 OK [READ-WRITE] SELECT completed” message is received, state <b>930</b> will transition, as symbolized by line <b>932</b>, back to command interpretation state <b>920</b> for the latter state to issue subsequent IMAP commands as necessary. Illustratively, here, command interpretation state will issue, as symbolized by lines <b>935</b> and <b>1035</b>, a “FETCH 1:3” command to the e-mail server to fetch the three queued messages in the Inbox. Here, tag “A102” is attached to this message to uniquely define this interaction. Included in the “FETCH” command are parameters indicating that “date” and “from field” data from the header for each message should be fetched as well. At this point, the e-mail server issues individual fetch responses, here shown as “*1 FETCH”, “*2 FETCH” and “*3 FETCH” and as represented by lines <b>1040</b>, <b>1045</b> and <b>1050</b> in communication <b>1000</b>, back to the e-mail front end. During this time, state machine <b>822</b> will remain in state command interpretation state <b>930</b> as indicated by line <b>938</b>. Each response contains the fetched information for a corresponding e-mail message in the user's Inbox. Once all three messages have been successfully fetched, the e-mail server, as indicated by line <b>1055</b>, issues an “A102 OK FETCH” message which indicates the completion of this transaction. In response to this completion message, state <b>930</b> will determine that all the necessary responses have been received from the e-mail server. Hence, state machine <b>900</b> transitions, as symbolized by line <b>937</b>, to response construction state <b>940</b>. Through this state, state machine <b>822</b> constructs a linked list, here list <b>950</b>, that contains all the user messages supplied by the e-mail server in response to the “HTTP_GET_REQ (/Inbox)” message and provides that list back to user interaction component <b>826</b>. Once this occurs, state machine <b>826</b> returns, as symbolized by line <b>945</b>, back to null state <b>910</b>. Once the user interaction component receives the linked list, it accesses an appropriate HTML template web page and populates that page with the information provided in the response to yield, e.g., a page of the form shown by display page <b>1700</b> shown in FIG. 17 (with an Inbox icon in a left panel and titles to individual e-mail message in a right panel). After this page is fully constructed, the user interaction component sends, as symbolized by line <b>1060</b> in FIG. 10, that page back through multiplexor <b>410</b> to web server <b>350</b>, via an “HTTP_GET_RESP” message, for transmission to user browser <b>15</b> to depict the web page providing the e-mail messages downloaded from the e-mail server. Response construction state <b>940</b> is also entered from state <b>930</b> if excess time, i.e., a timeout condition, has occurred once a IMAP command has been issued to the e-mail server without any corresponding response therefrom. As such, state <b>940</b> will specify this timeout condition to the user interaction component which, in turn, will construct and then transmit a web page to user browser <b>15</b> notifying the user of an timeout/error condition.

P-0126[0126] Not only can the user download his e-mail messages through interaction with user browser <b>15</b>, but also, as discussed above, the user can move or copy selected e-mail messages from one e-mail folder to another, or delete any such messages. E-mail application module <b>430</b>, including state machine <b>822</b>, operates in a very similar manner as that described above, with identical states though different commands, to execute e-mail copy, move and delete operations through e-mail server <b>76</b> in response to remote user interactions through user browser <b>15</b>.

P-0127[0127] Furthermore, the user can also send an outgoing e-mail message through appropriate interaction with user browser <b>15</b> and particularly using e-mail application module <b>430</b>. Specifically, whenever the user clicks on “New Mail” button in area <b>1720</b> on e-mail display screen <b>1700</b> shown in FIG. 17, user interaction component <b>826</b> shown in FIG. 8 will interpret that response, as originated from user browser <b>15</b>, and access a correct HTML e-mail form from stored web pages <b>830</b> and return that form, as symbolized by line <b>840</b>, back to the user browser to be rendered to the user. Once the user appropriately completes the form, (s)he will click on the “Send/Rec” button in area <b>1720</b> to send the message. This interaction, originating from user browser <b>15</b> and when received by user interaction component <b>826</b> shown in FIG. 8, will cause that component to receive the form containing the e-mail from the user browser. Once the form is so received, user interaction component <b>826</b> will extract the content, including the sender and recipient addresses, of the particular e-mail message from the received form and then issue a command to state machine <b>822</b>, via API <b>824</b>, to send that content out to the e-mail server for transmission. This command will be a “SEND_MAIL_REQ” which will contain as a parameter the e-mail to be sent. To accomplish this, state machine <b>822</b> interacts with two components to actually send this outgoing e-mail message: SMTP (simplified mail transport protocol—conventional and not shown) and IMAP client <b>810</b>. The SMTP interaction provides the e-mail message and actually instructs the e-mail server to transmit the e-mail onward to its destination. Once this interaction concludes, state machine <b>822</b> interacts with the IMAP client in order to update the “Sent Mail” folder, maintained on the e-mail server, for that particular user to include this message in its listing of sent e-mail messages. The interaction involving state machine <b>822</b>, via the IMAP client, and the e-mail server is very similar to that used to read the Inbox, though different commands are used in order to write a message into the user's “Sent Mail” folder rather than read the user's “Inbox” folder. Once state machine <b>822</b> has successfully sent the e-mail to the server for transmission, the state machine then sends a positive response, i.e., an appropriate “SEND_MAIL_RESPONSE”, to user interaction component <b>826</b>. If this user interaction component maintains a local HTML page containing titles of all e-mails in the user's “Sent-Mail” folder, component <b>826</b> updates that HTML page to include the message that has just been sent and then supplies that page, as here symbolized by line <b>840</b>, back to user browser <b>15</b> for rendering to the user. Alternatively, the user interface component can also access, as symbolized here by line <b>835</b>, a predefined HTML page, from stored pages <b>830</b>, that merely contains a confirmation that the e-mail message was successfully sent and provide that particular web page, here too symbolized by line <b>840</b>, back to web server <b>350</b> for transmission, via HTTP, to user browser <b>15</b> for rendering to the user as appropriate visual confirmation that his(her) message was transmitted. If an external e-mail server is not used, then the IMAP client interacts with Sendmail module <b>360</b> (shown in FIG. 3A) instead.

P-0128[0128] Though we have described the interaction for both the file sharing and e-mail application modules as illustratively user-initiated, i.e., starting with a user request entered at user browser <b>15</b>, the interaction can be server-initiated as well, with either file server <b>78</b> or e-mail server <b>76</b>, via SAMBA component <b>510</b> or IMAP client <b>810</b>, respectively. In this case, as will be described below in connection with RDP client <b>1100</b> (in conjunction with FIG. 12B), a server-initiated request will be directed to the corresponding state machine, be processed by that state machine, and if appropriate, forward resulting data onward to the corresponding user interaction component to be incorporated into an appropriate web page and then transmitted to user browser <b>15</b> for rendering to the remote user. Alternatively, in some cases, once the state machine has processed the request, the state machine may, depending on the nature of the data supplied by the server, generate further commands to the server. Though the specific commands and transition events will likely vary, the state processing will be quite similar to that shown and described herein.

P-0129[0129]FIG. 11 depicts a block diagram of thin-client application module <b>440</b> that forms a part of software <b>400</b> shown in FIG. 4. As noted above, module <b>440</b> interacts through the remote desktop protocol (RDP) with a client application program then being hosted on server <b>70</b>. Module <b>440</b> receives user mouse clicks and keystrokes from the user browser, in AIP form or some other similar form, and passes that information, via RDP, to the client application program to control its execution. In return, this module obtains graphical output displays, as screen shots, generated by the client application program and in RDP form, and converts those screen shots into AIP form and then transmits AIP messages, containing the screen shots, back to the user, specifically the user browser for rendering thereat. Note that module <b>440</b> can also receive control information from the user browser via AIP or some similar protocol. This information will typically not require any interaction with the application server via RDP. For example, thin-client Java applet <b>1180</b> running within the browser could request from the SEP a list of the applications that the user has access to at startup time. Based on the response, applet <b>1180</b> would display icons representing these applications. This whole interaction would occur via the AIP (or some similar protocol). Alternatively, based on implementational considerations, such control interactions could also use a completely separate protocol from the data interactions such as keystrokes, mouse clicks, and screen updates.

P-0130[0130] Module <b>440</b> contains RDP component <b>1110</b>, thin-client front end component <b>1120</b>, stored HTML pages <b>1130</b> and user database <b>1190</b>.

P-0131[0131] Thin-client front end <b>1120</b> is itself formed of state machine <b>1122</b> and user interaction component <b>1126</b> which communicate with each other through an application programming interface (API) as symbolized by line <b>1124</b>. State machine <b>1122</b>, in a similar fashion to state machines <b>522</b> and <b>822</b> (in file sharing front end <b>520</b> and e-mail front end <b>820</b> shown in FIGS. 5 and 8, respectively), interacts with an RDP client component <b>1110</b> which, in turn, interacts with client applications server <b>72</b>. User interaction component <b>1126</b>, in a similar manner to user interaction components <b>526</b> and <b>826</b> (in file sharing front end <b>520</b> and e-mail front end <b>820</b> shown in FIGS. 5 and 8, respectively), interacts with user browser <b>15</b> and passes and receives application information to and from the state machine. Protocol engine <b>1160</b> receives user interaction data, i.e., user mouse clicks and keystrokes in the form of AIP messages, from user browser <b>15</b> that are related to a client application program then executing on server <b>72</b> and sends screen updates to the user browser for display thereat.

P-0132[0132] RDP component <b>1110</b> is conventional and implements a client side of the RDP. Specifically, it interacts directly with client application server <b>72</b> using RDP by translating commands from a format used by state machine <b>1122</b> into the RDP for application to server <b>72</b> and translating responses received from this server into an appropriate format for use by state machine <b>1122</b>.

P-0133[0133] User interaction component <b>1126</b> contains generic web page module <b>1150</b> and protocol engine <b>1160</b>. Generic web page module <b>1150</b> responds to a request from the user, and specifically user browser <b>15</b>, that do not directly involve the execution of a thin-client application program. For example, when the user first clicks on the “My Apps” tab, an HTML page that contains a Java applet that controls input/output to executing thin-client application programs, using the AIP protocol, is downloaded to the browser and then instantiated under the browser to become Java applet <b>1180</b>.

P-0134[0134] As shown in FIG. 11, user interaction data in the form of user mouse clicks and keystrokes is provided by user browser <b>15</b> and specifically through execution of conventional internal Java applet <b>1180</b> that encodes this data into the AIP protocol. Additionally, control information is passed between the Java applet and the SEP to enable the applet to, for example, correctly display the icons for the client application programs that a particular user can access. For the discussion that follows, this control data is also sent via the AIP protocol. In general, it could also be sent by the same protocol as is used for transfer of the user interaction data in the form of mouse clicks and keystrokes, or by some alternate protocol.

P-0135[0135] In any event, user interaction component <b>1120</b> obtains, as symbolized by line <b>1165</b>, this AIP message data incoming from multiplexor <b>15</b>. This message can take the form of a message indicating that a user has clicked on one of his(her) displayed client application program icons to invoke that particular application. Protocol engine <b>1160</b> within component <b>1126</b> extracts the interaction data from the AIP message. The state machine, in turn, provides, as symbolized by line <b>1115</b>, this command to RDP component <b>1110</b> which converts it into a corresponding RDP message. Component <b>1110</b> then sends that RDP message, over the LAN and as symbolized by dashed line <b>1105</b>, to client application server <b>72</b>. Server <b>72</b> then extracts the interaction data from the RDP message and applies it to the corresponding client application program then executing, or in the case of a user initially clicking on a client application program icon displayed by the user browser, launches that application on the server. The resulting graphical display produced by the application is then returned by the server, within an RDP message and also as symbolized by dashed line <b>1105</b>, back to RDP component <b>1110</b>. This component, in turn, provides the display data to state machine <b>1122</b>. The state machine will react accordingly and provide that data, via API <b>1124</b>, to user interaction component <b>1126</b>. This component, through protocol engine <b>1160</b>, converts that display data (screen shot) into an AIP message and then transmits that message, via multiplexor <b>410</b> and web server <b>350</b>, to user browser <b>15</b> to update the application display then being rendered thereat. Within the browser, Java applet <b>1180</b> converts the AIP message into an appropriate display to the user within the window assigned for this particular instance of the remotely executing client application program.

P-0136[0136] Protocol engine <b>1160</b> does not always need to interact with state machine <b>1122</b>. For example, when Java applet <b>1180</b> sends a request to the protocol engine for a list of client application programs to which the user can access (via the control portion of the AIP protocol or via a separate control protocol), the protocol engine can refer, as symbolized by line <b>1195</b>, to local user database <b>1190</b> for that application list. Once the list is returned to engine <b>1160</b>, in turn, will instruct the Java applet as to which specific applications to graphically display to the user. Alternatively, rather than accessing local user database <b>1190</b>, protocol engine <b>1160</b> could access a non-local database through a conventional protocol such as LDAP.

P-0137[0137] When the user clicks on the “My Apps” tab as displayed by user browser <b>15</b> in order to invoke thin-client application program hosting, a display similar to that shown in screen shot <b>1800</b> depicted in FIG. 18 is rendered as a result. Visual feedback of that selection is again illustratively provided through a highlighted background for this tab in display region <b>1810</b>. Those specific client application programs to which the user can access are displayed through separate graphical icons <b>1830</b> situated in display area <b>1820</b>. The user can then click on any of these icons to remotely launch the associated client application program in a separate browser window through which the user can fully interact with that application.

P-0138[0138] To gain improved understanding of the operation of thin-client application module <b>440</b>, the reader should now simultaneously refer to FIGS. 12A, 12B and <b>13</b>.

P-0139[0139]FIGS. 12A and 12B depict state diagram <b>1200</b> and <b>1250</b> for thin-client front-end state machine <b>1122</b> for user- and server-initiated interactions, respectively. The user-initiated interaction involves, e.g., startup of a client application program session, in response to a user command provided from user interaction component <b>1126</b>; the server-initiated interaction involves, e.g., an update, provided by client application server <b>72</b> and via RDP component <b>1110</b>, to an application display then being rendered by user browser <b>15</b>. FIG. 13 depicts illustrative inter-process communication <b>1300</b> that involves thin-client module <b>440</b>, operative in conjunction with the client application server <b>72</b>, for executing and interacting with hosted client application programs.

P-0140[0140] As shown, state machine <b>1122</b> contains four distinct states (similar to those in state diagrams <b>600</b> and <b>900</b> shown in FIGS. 6 and 9 for state machine <b>522</b> and <b>822</b> in file sharing application module <b>420</b> and e-mail application module <b>430</b>, respectively): null state <b>1210</b>, command interpretation state <b>1220</b>, waiting for response state <b>1230</b> and response construction state <b>940</b>.

P-0141[0141] Initially, state machine <b>1122</b> resides in null state <b>1210</b>. One a user clicks on the “My Apps” icon in the Netilla virtual office graphical interface (e.g., displays <b>1600</b>, <b>1700</b> or <b>1800</b> shown in FIGS. 16, 17 and <b>18</b>, respectively), this operation being symbolized by line <b>1305</b>, user browser <b>15</b> issues, as symbolized by line <b>1310</b>, an appropriate HTTP request instruction (“HTTP_GET_REQ (/Apps)”) to fetch a list of the client application programs which that user can access. User interaction component <b>1126</b> receives this command, and in response thereto, issues, as symbolized by line <b>1315</b>, an HTTP_GET_RESP message containing an HTML page with an embedded Java applet. Once downloaded into user browser <b>15</b>, this Java applet is instantiated by the browser as Java applet <b>1180</b> (see FIG. 11) and then issues, as symbolized by line <b>1320</b>, a query, “User_Desktop_Query”, to thin-client front end <b>1120</b> for a list of the user's accessible hosted client application programs. As a result of this query, component <b>1126</b> in thin-client front end <b>1120</b> returns, as symbolized by line <b>1325</b>, a response, “User_Desktop_Response”, based on stored user information contained within user database <b>1190</b>, containing a list of those application programs. Thereafter, Java applet <b>1180</b> executing in the browser displays an icon on user browser <b>15</b> for each of these application programs. At this point, the user, being provided with a graphical display such as display <b>1800</b> shown in FIG. 18, can click on any of these icons to invoke the corresponding client application program.

P-0142[0142] If the user then clicks on any such icon, e.g., that associated with the Microsoft Word program, this interaction being symbolized by line <b>1330</b>, Java applet <b>1180</b> spawns a new browser window (which the applet controls) for use as a user display area for that particular remotely hosted application program. In addition, then user browser <b>15</b> provides, as symbolized by line <b>1335</b>, a “Session_Start” command to thin-client front end <b>1120</b>. This command includes the name of an application server (server <b>72</b> as shown in FIG. 1), appropriate flags, a domain within which the application server runs, password of the user, the name of the application program (here “Word”), a name of a working directory and other related parameters needed to properly and remotely execute the application program (including fully defining its user environment).

P-0143[0143] In response to the “Session_Start” command, state machine <b>1200</b> transitions, as symbolized by line <b>1215</b> in FIG. 12A, from null state <b>1210</b> to command interpretation state <b>1220</b> where it processes this command. Similar to FIGS. 9 and 10, identical circled letters, rather than numerals, are shown in FIGS. 12A, 12B and <b>13</b> in order for the reader to visually correlate specific inter-component messages shown in communications <b>1300</b> with their corresponding events (including state transitions) in state diagrams <b>1200</b> and <b>1250</b>. Specifically, while in state <b>1220</b>, the state machine issues, as symbolized by line <b>1340</b>, an “RDP_CONNECT_REQ” request message to client RDP component <b>1110</b> to request a session with a particular client application server. This request contains, e.g., the server, directory, application program and other information provided, in the Session_Start command, to the thin-client front end. Once this message is issued, state machine <b>1200</b> transitions, as indicated by line <b>1225</b>, to waiting for response state <b>1230</b>, waiting for a response from the client application server, e.g., server <b>72</b> shown in FIG. 1.

P-0144[0144] Once the server has established the requested application session, the server issues an appropriate message to client RDP component <b>1110</b> as shown in FIGS. 12A and 13, which, in turn, provides, as symbolized by line <b>1340</b>, an RDP connect response message, “RDP_CONNECT_RESP”, to the thin-client front end. In response to this RDP message, state machine <b>1122</b> remains, as symbolized by line <b>1233</b>, in this state to determine if this is the only response that the state machine has been expecting from the client application server or not. If it is, as is the case here for session startup, then state machine <b>1122</b> transitions, as indicated by line <b>1237</b>, from state <b>1230</b> to response construction state <b>1240</b>. Once in the latter state, state machine <b>1122</b> constructs an appropriate session start response message. i.e., “SESSION_START_RESP”, to user interaction component <b>1126</b> after which the state machine transitions back, as symbolized by line <b>1245</b>, back to null state <b>1210</b>. As a result of this response message, the user interaction component sends a “Session_Start_Resp” message, as symbolized by line <b>1350</b>, to user browser <b>15</b> and specifically to Java applet <b>1180</b> executing thereunder to indicate that the desired application session has been established. In essentially the same manner as just described, subsequent user-initiated interactions, i.e., mouse clicks and keystrokes, with the executing application program will be provided by the user browser and processed through the thin-client front end and translated from AIP into appropriate RDP messages which, in turn, are provided to client application server <b>72</b> to control execution of that application program.

P-0145[0145] Returning to the example shown in FIG. 13 for startup of an remotely hosted thin-client application program session, once the application session has been established and the application invoked at server <b>72</b>, the server will provide RDP client component <b>1110</b> with an initial graphical display screen. In response, RDP component <b>1110</b> will issue, as symbolized by line <b>1355</b>, an “RDP_PROCESS_BITMAP_UPDATES (stream)” message containing screen bitmap display data for display. In response to this RDP message, state machine <b>1122</b> will transition, as symbolized by line <b>1263</b> in FIG. 12B, from null state <b>1210</b> to command interpretation state <b>1220</b>. In this latter state, the state machine will simply pass this bitmap data onward to user interaction component <b>1126</b> within thin-client front end <b>1120</b> such that this data can be forwarded to the user browser for rendering thereat. As such, state machine <b>1122</b> will issue, as symbolized by line <b>1360</b>, an image update command, “IMAGE UPDATE”, to the user interaction component, and, as symbolized by line <b>1267</b>, transition back to null state <b>1210</b>. In response to this state machine command, the user interaction component performs certain initial processing of this bitmap data. In particular, given limited display capabilities of a Java virtual machine executing in user browser <b>15</b>, this processing includes operations not supported by that virtual machine, such as, e.g., plane masking, logical operations and others. In addition, the user interaction component, through use of protocol engine <b>1160</b>, will also determine if Java applet <b>1180</b> has cached any portion of the display that can be reused in the updated display, e.g., a glyph representing a character, hence eliminating a need to resend that portion so as to conserve transmission bandwidth and expedite update time by user browser <b>15</b>. At the conclusion of this processing, user interaction component <b>1126</b> within thin-client front end <b>1120</b> will send, as symbolized by line <b>1160</b>, a “Display_Screen (Image)” message containing the update display data to user browser <b>15</b> for rendering thereat in the corresponding window spawned to support this particular client application program. In the same manner as described, subsequent server-initiated interactions, i.e., bitmap display screens, for this program will be provided by client application server <b>72</b> and processed through the thin-client front end and translated from RDP into appropriate AIP messages which, in turn, are provided to user browser <b>15</b> to appropriately update the display in the corresponding application window.

P-0146[0146] Though we have described client interaction component <b>1126</b> as utilizing protocol engine <b>1160</b> and user browser <b>15</b> as utilizing Java applet <b>1180</b>, both to support the AIP protocol in order to advantageously increase bandwidth efficiency, these components could use native RDP all the way to the user browser.

P-0147[0147] Furthermore, though we have described our invention as providing remote office functionality in terms of file access, e-mail and thin-client application hosting, our inventive teachings can be used with any other additional office-based application that is to be provided to remote users over a browser connection. In that regard, another application module would be implemented and incorporated into virtual office software <b>400</b> shown in FIG. 4—and similar to those described above—to provide necessary bi-directional, real-time protocol translation of user interaction data in secure HTTP (or a particular transmission protocol, if used in lieu of secure HTTP) into a particular protocol used by that other office-based application, and convert resulting output data (whether graphical or in another form) provided by that application-specific protocol into secure HTTP (or the intermediate transmission protocol) for transmission to the user browser and rendering, as a web page, to the user situated thereat. As such, by now, the reader can clearly appreciate that our inventive teachings are not limited to merely providing remote access to just office-based file access, e-mail and thin-client application hosting functions, though these functions are likely to be those most often appearing and needed in the processing environments for which the present invention will likely see use.

P-0148[0148] Although a single embodiment, with various modifications, which incorporates the teachings of the present invention has been shown and described in considerable detail herein, those skilled in the art can readily devise many other embodiments that still utilize these teachings.