DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0047] The present invention relates to a filter proxy system for comprehensive content acceleration and automated content formatting and method for re-authoring, re-purposing, and/or compressing content control languages and/or images for delivery and/or interaction with devices of varying capacity and/or bandwidth availability without operator's intervention, and interaction with other systems having same filter proxy systems for reducing bandwidth utilization between each other and distributing the re-authoring, re-purposing, and compression processing of the content control language and/or images for content for delivery of and/or interaction with devices of varying capacity and/or bandwidth availability without operator's intervention.

[0048] A generalized and exemplary list of components, functions, and filters that are incorporated into one embodiment of a filter proxy system for handling requests, re-purposing of images, compression, and/or re-authoring the content and mark-up language, are as follows:

[0049] Client Components and Proxy

[0050] A user proxy module operable on a requesting device, or equivalent means to redirect URI requested to the filter proxy system.

[0051] A client proxy module that provides custom transport protocol capability having the ability to accept data streamed from the filter proxy system, support a continuous connection with the filter proxy system, and reduction of the number of TCP/IP connections made for referenced content in the ML, reduce the number of acknowledgements for received packets, and custom packet sizes.

[0052] A user proxy module operable on the requesting device, when applicable, which provides secure communications and content control.

[0053] A browser and image-rendering module.

[0054] ML, text, and script compression and decompression module.

[0055] Custom rendering applications that can maintain secure control of the content to the user.

[0056] User Profile Application Support (as Applicable)

[0057] User defined configurations and interface thereto.

[0058] User control interface to set user preferences for content re-purposing and compression.

[0059] A “speedometer” visualizing the apparent download speed.

[0060] A transparent user setting (raw or un-enhanced access to the Internet).

[0061] Support for other proxies on client or no proxy setting.

[0062] URL access limitations as set by user or corporations.

[0063] User authentication and data encryption.

[0064] Communications/Gateway

[0065] Establishing a connection via a communications/gateway server upon a user request.

[0066] User interface for user profile update.

[0067] Caching a transport protocol, such as HTTP.

[0068] User authentication, e.g. two (2) factor authentication.

[0069] Logging and alarm functions.

[0070] Byte usage and other accounting features.

[0071] Compliant with standard transport protocols, such as HTTP 1.0 and HTTP 1.1 as well as allowing for custom protocols.

[0072] Online Help as necessary.

[0073] Master Browser and Filter Proxy

[0074] Access to device and user profiles and ML template databases as well as logic to process and filter according to profile specifications.

[0075] Access and logic to search and retrieve a target URI from a cache and a host system over a network, process according to the device and user profiles, and analyze, coordinate, prioritize, and task filter functions for one or multiple simultaneous URI requests.

[0076] Logic to download all URI mark-up language and content, such as images on behalf of the client proxy, process them concurrently, and send them to the requesting via the client proxy on the requesting device as a single data stream to reduce the number of TCP/IP connections made by the device for every content referenced in the ML, bandwidth utilization, and filter proxy resources.

[0077] Logic to recognize, communicate, pass processing parameters, and manage with another same filter proxy system the processing resource distribution, process balancing over a network, compression of the processed data to reduce bandwidth utilization between the two servers, and a data streaming protocol.

[0078] Load balancing data and processes across multiple servers of the filter proxy.

[0079] Distributed Internet/intranet caching and retrieval logic between a requesting server having a filter proxy system and a content & ML host having the filter proxy system to reduce the process overhead of ML and content previously re-authored, re-purposed, and/or compressed.

[0080] ML page analysis and profiling based upon device and user profiles for determination and/or generation of best-fit ML template for ML page.

[0081] Re-authoring ML as required based upon profiles and template parameters.

[0082] Image filters for re-purposing and compression logic and operations for:

[0083] an image enhancement and/or compression process.

[0084] 24-bit RGB color to 16- and 8-bit color conversion and compression.

[0085] 24- and 8-bit color to gray scale both 8- and 1-bit black and white conversion and compression. Format conversion from BMP, TIF, PNG, and GIF to

[0086] JPG, TIF, PNG or other format.

[0087] Conversion of animated GIF to static GIF, PNG, or JPEG formats.

[0088] Video image streaming format conversion and compression.

[0089] Removal of all images or selective removal of images, e.g. removal of GIF.

[0090] Automatic resizing of images based upon the device and user profiles.

[0091] Converting to special image formats.

[0092] ML re-authoring and editing filters and logic as required by profiles and template parameters:

[0093] White space elimination.

[0094] Header conversion or elimination.

[0095] Background images elimination.

[0096] Comments elimination.

[0097] Meta tags stripping.

[0098] Tables re-authoring and presentation.

[0099] Frames re-authoring and representation.

[0100] Text re-formatting.

[0101] Font conversion.

[0102] Dynamic page presentation.

[0103] Java Applets execution or elimination.

[0104] JavaScript and VBScript proxy execution or elimination.

[0105] Plug-ins such as audio and video files elimination.

[0106] ML referenced document conversion. (Such as PDF file converted to HTML Text).

[0107] Re-authoring ML as a result of image re-purposing

[0108] Removal from original ML any code fixing the size of images

[0109] Error trapping and recovery logic to handle conditions not addressed in the re-authoring and re-purposing logic.

[0110] Authoring each page of ML by adding control language that provides a real-time user control interface on each Web page for user preferences of content re-purposing and compression parameters, such as image size and compression ratios.

[0111] ML, text, and script compression and decompression filters and operations.

[0112] Logic to execute client side script so as to be able to accelerate content delivery.

[0113] Logic to map and execute control code and script on behalf of the user and device on the filter proxy system when the device has limited capability.

[0114] Databases

[0115] Protocol (HTTP 1.0/1.1) database accessed by the communications/gateway server.

[0116] Device and user profiles database and error logging.

[0117] Mark-up language (ML) template database.

[0118] Security database.

[0119] User account database.

[0120] Statistical

[0121] In the following description of the preferred embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration several embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized as structural changes and may be made without departing from the spirit and scope of the present invention.

[0122] One embodiment of the present invention includes: 1) URI directing module and custom transport protocol that reduces the number of connections made to retrieve the URI mark-up language and it referenced content, supports a continuous connection, and accepts data streamed from the filter proxy system on a requesting device (Client Proxy); 2) a communication/gateway server that establishes a session with a remote device and creates a communication path with the filter proxy; 3) a set of content filters (Filter Proxy) that: (a) intelligently accepts redirected requests, retrieves and caches the requests on behalf of the requesting device; (b) includes a URI and ML content analysis component; (c) has a set of callable filters or a library of filters that perform the filtering and processing of the text, images, embedded script code, links, functional mapping, compression, and ML re-authoring and editing and conversion as a result of the analysis of the original mark-up language, its content, device and user profiles, and ML template; (d) has a software component that establishes whether the URI is in cache, up-to-date, and/or already pre-processed for a given device; 4) a Web page/URI caching server farm; 5) primary databases composed of the device and user profiles, error logging and statistical information, and secondarily those for security and user accounts; and 6) a Web page/URI caching retrieval server that: (a) communicates with host where requested URI resides; (b) communicates with another implementation of the filter proxy system present at the requested URI host; (c) passes the parameters for re-purposing and re-authoring the ML, text, images, and/or other content to the URI host filter proxy system to distribute the processing, reduce the resource utilization on requesting filter proxy system, and reduce the bandwidth utilization between the two filter proxy systems; (d) request of URI may be serviced from cache of the host filter proxy system if URI has previously been filtered by the hosting filter proxy system. These components may reside on a single physical server having a single or multiple processors or on multiple physical servers having one or more physical processors each and may be distributed across a network or networks. All processes work in a real-time environment to process the content “on-the-fly” at the time a request is made for final delivery to a requester.

[0123] In one embodiment, the method is further defined by the filter proxy system having the means and mechanisms for: 1) establishing, entering, updating, and retrieving device and user profiles specification and templates in the respective databases; 2) analyzing the ML while applying the specifications of the device and user profiles to determine what data formatting filters, e.g. re-purposing, re-authoring, and/or compression filters are required; 3) analyzing of the ML while applying the specifications of the device and user profiles to define an ML template or establish the best fit of an existing ML template to further refine the process of re-purposing, re-authoring, and formatting the ML and its content for a specific device and user; 4) calling and executing the proper filters that perform the filtering and processing of the ML and its content; 5) prioritizing and tasking the filtering and processing to different servers of the filter proxy server array for purposes of improving through-put and load balancing; 6) bandwidth-throttling by controlling how much ML re-authoring and/or when image enhancement and/or image pre-compression filtering are performed prior to compression; 7) may eliminate all duplicate references to a hyperlink/URI by text and/or graphics and utilizing control information from (1), (2), (3), and (4) above; 8) mapping to the filter proxy server memory relationships between hyperlinks and script to text and hot buttons sent to the user based upon the device capacity defined in the device profile; 9) executing on behalf of the device the hyperlinks and script code mapped on the server of the filter proxy upon a response of the user when necessary; 10) converting the executable ML to the proper language as defined by the device profile; 11) allowing the user to change their preferences and/or user profile at any time to define how the filter proxy re-purposes and compresses image content and text to be downloaded to the user so long as it conforms with the capacity of the device as defined in the device profile; 12) enhancing, converting, and/or compressing images to fit the device and user specifications and decrease the bandwidth requirements and download time; 13) converting various document forms to the device ML such as HTML; 14) compressing the text, ML, and script to decrease the bandwidth requirements and download time; and 15) providing a transport protocol that may be a standard, such as HTTP or a custom protocol that supports a continuous connection, reduces the TCP/IP connections required for the ML and its referenced content, improves the ratio of packet to response retaining data integrity and recovery, and supports data streaming between the server and the requesting devices having the appropriate client proxy.

[0124] It will be appreciated by those skilled in the art that the process and methods described herein may operate on the Internet, Intranet, or a local network over a wired or wireless connection.

[0125] FIG. 1 depicts one embodiment of a network for Web to wireless mobile or wired dial-in Internet communication system 100 having a filter proxy system 102 in accordance with the principles of the present invention. The filter proxy system 102 provides a method for re-authoring mark-up language (ML) and/or control languages, such as HTML and WML, re-purposing the associated content, such as text, document files, and images. The re-authoring or filtering of the ML may, but not limited to, address updating the ML when referenced content is re-purposed, editing out comments and white spaces, formatting the content in accordance with the user's preferences and profile and the device capabilities in accordance with the device profile and/or translate the ML language and/or control languages into an appropriate ML or control language used by a device further defined by its device profile. The device profile provides device specific parameters required for re-authoring the ML for rendering on a device that can further be refined and controlled by the application of templates.

[0126] The filter proxy system 102 includes a communications/gateway server 104 , a filter proxy 106 , a Web cache server farm 108 , a caching retrieval server 110 , and databases 120 . The communications/gateway server 104 establishes a connection with a user/requestor's device 116 to the Internet 112 via a variety of communication media 114 . The filter proxy 106 is coupled to the communications/gateway server 104 through an Internet Protocol (IP) port tunnel. The filter proxy 106 also communicates and controls the Web cache server farm 108 and the caching retrieval server 110 . The communications/gateway server 104 may use a cache 118 for its transport protocol. The filter proxy communicates and fetches processing parameters such as user and device profiles and ML template from databases 120 .

[0127] In FIG. 1, a user no longer connects directly to a requested URI or network content host or provider on the Internet via a communications/gateway server as illustrated in FIG. 11 . Instead, in FIG. 1, a connection is made between the user and the filter proxy 106 via the communications/gateway server 104 . The filter proxy system 102 uses the cache & caching memories 118 for a URI's original content and a filtered content to include images and mark-up language, as well as databases for device and user profiles stored in the databases 120 , ML templates, accounting, and security as required by the operational environment. Accordingly, no changes are required on a WWW server that hosts the requested original URI content on the Internet. The databases 120 that are stored on memories may include device and/or user profiles, ML templates, accounting, logging and statistics. The cache & caching memories 118 may include caching of URI and its original and changed content having a high request count. The databases 120 and the cache & caching memories 118 facilitate and reduce the overhead of re-authoring and re-purposing the same ML and images. The filter proxy 106 then applies the proper filters to re-purpose text and image content, re-author mark-up language as required for a specific device, and/or compresses the mark-up language, text, and image.

[0128] Furthermore in FIG. 1 , the requesting filter proxy 106 may intelligently communicate with another filter proxy system 103 that hosts the requested URI, pass device and user parameters for re-purposing and/or compression processing of the ML and content on behalf of the requesting filter proxy 106 where the processing of the filter proxy system 103 occurs for purposes of reducing bandwidth and distributing processing and/or may be retrieved from cache if the URI has been previously filtered. Such content already processed and resident on the host filter proxy system 103 may be accessed directly from its Web cache server farm 108 without further processing. The filter proxy system 103 preferably includes the same components as the filter proxy system 102 .

[0129] The changing/re-authoring of the ML or control language by the filter proxy 106 can be done at the time a requested URI is downloaded or made available from the cache 118 to the filter proxy 106 such that an original ML may remain dynamic at its host. For example, as depicted in FIG. 10 , the filter proxy 106 retrieves and converts a 24-bit color RGB image referenced in an original ML hosted on a remote server on the Internet to an 8-bit grey scale image and alters its size to meet device specifications. The associated text of the original ML retrieved is also formatted to meet the device specifications. All required hyperlinks are mapped in the cache 118 of the filter proxy ready for execution on behalf of the device upon a corresponding user response. The owner of the original ML may change the image and the associated text at any time residing on a remote server(s) without the ML or content having to be customized manually for a specific device. In one embodiment, the rules that establish how the image, text, and functionality are to be changed are dependent upon and defined primarily by the device profile, further by the user profile, and the ML template. The analysis of an ML page for a specific device profile establishes the characteristics required to associate a best ML Template that will provide the re-authoring parameters, such that the re-authored ML and its content are formatted for the specific requesting device. Accordingly, the filter proxy 106 reduces the overhead required to process the ML and its content. The last or previous user profile updated by the user may be set as the default, which are referenced and loaded for parameters at the time of login. Furthermore, the filter proxy 106 controls URI content processing parameters and available system resources for such processing based upon bandwidth availability, number of concurrent users, and filtering load. During periods when bandwidth availability restrictions exist, the filter proxy 106 is capable of reducing the bandwidth available per user session thereby reducing the need for queuing and thus servicing more sessions effectively. When large numbers of concurrent users are making requests, the filter proxy 106 may over-ride user parameters and restrict the image enhancement and pre-compression processes that consume processing resources to balance the available resources and service all users equitably during peak periods.

[0130] FIG. 2 is a schematic view of functional relationships and operations of the filter proxy 106 in the filter proxy system 102 , 103 in accordance with the principles of the present invention. The filter proxy 106 includes a master browser 122 and a filter proxy server array 124 for processing ML and content. The master browser 122 preferably is the primary control service that provides the functionality required to direct, control, and monitor the filtering and caching processes as per the exemplary filter functions previously defined under the title of Master Browser & Filter Proxy (see also FIG. 3 ). The filter proxy server array 124 is capable of processing a plurality of MLs and contents virtually the same time.

[0131] In operation, a user, via a client proxy on a device or some other means, directs a client browser to the communications/gateway server 104 associated with the filter proxy 106 and requests a connection. Then, the communications/gateway server 104 establishes a connection between a device and a communications network. The network can be wired or wireless. Depending upon the type of service(s) provided, the connection may be in either a secured or unsecured nature. The communications/gateway server 104 , upon establishing the connection, passes the connection information to the filter proxy 106 where an application session is established. The profiles associated with the user and the device are then retrieved from the databases 120 for processing any request for a URI upon its receipt from the connected device. Upon receipt of the request for a URI, the filter proxy 106 performs the required tasks to establish the validity of the request, i.e. whether the URI is cached or current, and/or whether the cached URI is already formatted for the requesting device or not. The user or host services, via the user profile, may restrict access to a valid list of trusted URI's or allow global access to any URI available on the network. Upon establishing access rights to the requested URI, the filter proxy 106 checks its cache 118 to determine if the URI is already resident to determine whether it requires to be downloaded in its entirety or only the most current associated content, and initiates a connection with the host of the URI to determine whether any changes to the original URI format or content have occurred since last downloaded. If the cached URI and all content are current, the connection with the URI host is terminated, and the filter proxy 106 uses the cached URI content.

[0132] If the URI is not in cache 118 , the master browser 122 establishes whether a same filter proxy system 103 is resident at the URI host. If the filter proxy system 103 is present at the URI's host, parameters for re-authoring, re-purposing, and/or compressing the requested ML and its content are sent to the URI's host where the URI will be processed on behalf of the user so as to reduce the bandwidth used between the two hosts and optimize the processing resource utilization across the network. Such processing by the URI's host filter proxy system 103 on behalf of the requesting filter proxy system 102 may be determined by the existing load and the need for original content by the requesting filter proxy 102 . Regardless, in one embodiment, compression of the original ML and text will occur as well as for the associated images whereupon downloading of the data continues.

[0133] If the requested URI content is cached and it is determined that the content has been changed since last cached, the caching retrieval server 110 establishes connection with the URI host filter proxy system 103 . The parameters for re-authoring, re-purposing, and/or compressing the content are sent to the URI's host where the URI will be processed on behalf of the user so as to reduce bandwidth used between the two hosts and processing resource utilization based. The existing load and the need for original content by the requesting filter proxy 106 may determine such processing by the URI's host filter proxy system 103 on behalf of the requesting filter proxy system 102 . Regardless, in one embodiment, compression of the original ML and text will occur as well as for the associated images whereupon downloading of the data continues.

[0134] URI in cache is determined by comparison of the cached version with that being downloaded, initially a header and metadata, and finally the content such as ML, text, and image tags, etc. Additionally, cache is checked for a current device version of the URI content as a result of a previous request. One of the purposes of identifying a content type of a URI within a ML template is to reduce the overhead for determining the immediate need for content update.

[0135] As shown in FIG. 3 , the filter proxy 106 analyzes the ML and URI content. The filter proxy 106 uses the device and user profile parameters for re-purposing of any text and images, maps ML functionality for execution on the server of the filter proxy 106 on behalf of the requestor, and/or re-authors and converts the ML according to the device and user profiles parameters using the best fit ML Template.

[0136] In FIG. 3 , the master browser 122 performs the analysis of the ML and its content retrieved from the URI utilizing the system, device, and user profile databases 120 and the ML templates to determine what processing must occur. The ML and content processing is broken into discrete tasks by the master browser 122 that assigns them to filter proxy server array 124 on one or more processors and/or server devices for processing to meet the device and user dependent requirements. Finally, upon completion of processing all elements, the new ML and content are sent to the requesting user.

[0137] Furthermore, the master browser 122 measures resources available and prioritizes tasks and filtering to be performed by the filter proxy server array 124 . These measurements are used to load balance processing and maximize user request processing on individual filter proxy servers on the array 124 . The filter proxy 106 usually resides in a server environment. The filter proxy 106 may process in a multiple processor server environment using shared memory or an inter-process communications protocol such that the requested content does not have to be stored on a permanent storage medium, such as hard disk except for caching, thus increasing the throughput and number of simultaneous requests that may be processed.

[0138] Table 1 below lists exemplary filters having functional operations performed by the filter proxy 106 . 1

[0139] It is appreciated that other functional operations can be performed within the scope of the present invention. It is also appreciated that the implementation of these functional operations is generally known in the art and not the focus of the present invention.

[0140] If the URI content is present in cache and is already formatted as per the device and user specifications, the filter proxy 106 transmits the re-formatted URI and the most current content to the device for rendering. The filter proxy 106 may compress the processed ML, text, and any associated script to further reduce the bandwidth requirements according to device capacity defined within the device profile. The filter proxy 106 may also perform required cache updating, logging of statistical data, and accounting information as required by the system. The communications/gateway server 104 transmits the re-formatted information to the device 116 using the available transport protocol over the wired or wireless network or media 114 .

[0141] The following are the detailed descriptions of different modules of one embodiment of the filter proxy system 102 and filter proxy processes.

[0142] A. Client Services by Client Proxy Configuration

[0143] FIG. 4 illustrates one embodiment of a client proxy configuration 126 of the filter proxy system 102 in accordance with the principles of the present invention. The client proxy configuration 126 may be included on device 116 which is capable of communicating with the communications/gateway server 104 via some communication medium 114 having a web browser and operating system 128 or other software and hardware components, such as a component manager and security plug-ins, etc. The communication medium 114 enables the device 116 to execute a mark-up language, such as HTML, to render the content, and to interact with the user. A web browser 134 of the device interprets ML, renders content, executes script language, and allows the user to interact with the content and web provider or host services.

[0144] In FIG. 4 , the client proxy configuration 126 may also include a client proxy 132 or equivalent means for directing the connection to the filter proxy 106 via the communications/gateway server 104 , utilizing custom transport protocols other than HTTP that would further increase the efficiency of moving information across the communications medium by increasing the packet size and ratio to acknowledgments, and data stream the ML and its content at one time as an associated set of packets, not as individual requests as done by HTTP, thus eliminating a new TCP/IP connection for each referenced content, such as images. Furthermore, the client proxy configuration 126 may include plug-ins for special purpose applications, such as encryption, special file generation, and rendering applications all of which execute on the device and that may be under the control of the web browser or control the web browser and its functionality. It is appreciated that other client services can be implemented within the scope of the present invention. Examples of the other services which can be provided by the client proxy configuration 126 via the client proxy 132 or the web browser and operating system 128 are means of changing of the user profile, controlling applications distributed and updated over the network to the user's device, metering and billing of the distributed applications on the device based upon usage, a speedometer that shows the real-time compression and apparent increase in speed, account query capability, securing and retaining control of data on the device and during transmission, text data compression and decompression, and access to secure e-mail services, etc. Availability of each of these features may be device and host services dependent.

[0145] In a preferred embodiment, a user is required to interact with the filter proxy 106 to control content delivery and e-mail. This is accomplished by way of providing the user an interactive control box that has been authored by the filter proxy 106 and embedded on every page requested or provided to the user by the filter proxy 106 . The control interface/box may be made up of icons wherein each icon represents a request for a service or a content processing parameter that the user wishes the filter proxy 106 to use or respond to. For example, the user desiring to increase the compression of images would click/choose an icon within a control interface depicting an action that would signal the filter proxy 106 that the user requested a change in the compression ratio of the images to further reduce the download time. The filter proxy 106 correlates the request with a process parameter, compresses the images of the current page, and resends the compressed images to the user as well as all subsequent images that would be processed for that particular user or until the user requests another parameter change. The filter proxy 106 may override a user parameter when system load balancing and resources require such.

[0146] B. Communications/Gateway Server

[0147] The communications/gateway server 104 provides standard services, such as the transport level protocol, HTTP, WTP, and HDTP, for caching of the protocol, establishing the session with the device, passing connection and URI request information to the filter proxy 106 , and interfacing with the security components of the filter proxy system 102 , such as device dependent encryption and user authentication. Information required to establish the application session on the filter proxy 106 includes, but not limited to, the user identification, password, device and browser type, and IP address. The communications/gateway server 104 may also count the bytes sent to and received from the user for purpose of statistical analysis or billing if desired. Another function that the communications/gateway server 104 provides is measuring bandwidth availability. The bandwidth availability information is sent to the filter proxy 106 to change the image enhancement processing and to increase the image compression so as to further throttle the data to increase available bandwidth, service more users, and meet user requirements during peak usage periods.

[0148] C. Profile Databases

[0149] The profile databases 120 may include device and user profiles. It is appreciated that other profiles can be used within the scope of the present invention. For example, the profile databases 120 may include security data for maintaining password, user access level information, and potentially user accounting information.

[0150] FIGS. 5 and 6 illustrate exemplary profile databases for ML templates, system, device, and user profiles of the filter proxy system 102 in accordance with the principles of the present invention. Controls and interfaces are provided to the profile databases such that the host and/or the user can have access to the appropriate databases based upon the operational environment. As an example, the device profile is only available to the hosting service through the filter proxy 106 and administrative service graphical user interface. It is appreciated that any administrative service graphical user interface can be implemented without departing from the present invention. The user profile may or may not be accessible to the user directly. When accessible, the user may do so via the interface provided on the requesting device or another device registered with the host services.

[0151] In general, a device profile defines to the filter proxy 106 the capabilities and limits of a device to render content, methods of interaction with a user, programmability, protocols, languages, and the other essential information about a specific device that is used by the filter proxy 106 to make the content useable by the device. The device profile also provides essential information for building ML templates that may be referenced through an index or saved state information or by way of using a user profile for the given URI list as depicted in FIGS. 5 and 6 .

[0152] ML templates are device type dependent and original ML format dependent. ML templates provide formatting specifications optimized for a URI based upon its analysis by the filter proxy 106 . ML templates include information, such as text wrapping, text justifying, locating images, mapping text to functionality, that are emulated by the filter proxy 106 on behalf of the device, and whether the content is dynamic and referenced by a hyperlink which determines if the content must be downloaded upon each new request of the URI even if the ML is resident in cache. FIG. 7 illustrates an example of relationships of the various elements of the databases 120 and generation of a template for formatting content to a specific device and user requirements.

[0153] In general, a user profile provides the user via a user interface additional control over content downloaded. The user profile may include: 1) elimination of image content or an image compression ratio applied, re-sizing parameter, and image format to be downloaded, 2) a list of URL's to which the a user wishes to restrict access, 3) password administration, and 4) user account information. Interfaces are provided to allow new device registration, administration, changing of passwords, access to accounting information, and “on-the-fly” access to elements that impact downloading of content. The last or previous user profile updated by the user may be set as a default, which is referenced and loaded for parameters at the time of login. FIG. 6 illustrates an example of some of the elements that compose the user profile. Each device, where applicable, may have a separate user content profile table and a user URI list table. The optional security and accounting databases may be aggregated or device dependent depending upon the user's relationship with a hosting system and its operational environment. The user content profile is used with the device profile to establish the rules for changing and formatting of the image(s) and other content for a device for any given request for information or communication with the filter proxy 106 and any other services offered on the host system. The user profile is not required for the filter proxy 106 to function and process URI and its content for the requesting device in a dynamic “on-the-fly” environment.

[0154] D. Caching Services

[0155] In one embodiment, caching is an integral component of the filter proxy process. The caching services provide high speed and immediate data availability to the various components of the filter proxy system 102 .

[0156] Three exemplary types of caching services are shown in FIG. 2 . The first type of caching is that the web caching server farm 108 provides caching for previously downloaded URI content and any device dependent changes made to the URI content. The second type of caching is that the caching retrieval server 110 retrieves URI at the time of the request for purposes of comparison with existing cached content and acts as an intermediate buffer and retrieval service to offload tasks from the filter proxy 106 . The caching retrieval server 110 utilizes parameters established by the master browser 122 to communicate with another same filter proxy system 103 and accessing its cache over the network for download of requested URI that may already be formatted and compressed for the device thus reducing the bandwidth utilized between the two proxies and resources of the requesting filter proxy system 102 . The state of the requested URI on the hosting filter proxy system 103 is determined so that the processing is done in a manner for most efficient use of available resources across the network. Distribution of the processing between the two communicating filter proxy systems is managed in such manner that the system is capable of balancing the processing, reducing bandwidth utilization, meeting the device and user content requirements, and retaining content functionality.

[0157] Exemplary statistics that impact how the URI is downloaded to the requesting filter proxy 106 may include number of current request for the URI page, if and what multiple devices have made a request for it, historical data that would show time of day load and request and finally the current load of the two filter proxies 102 , 103 communicating. The processing parameters for the particular request are passed to the hosting filter proxy 103 where the re-purposing and compression of control code, text, and image content as per the rendering device and/or requestor specifications will be performed on behalf of the requesting filter proxy system 102 to reduce the bandwidth utilization between them and offload the required processing for making the content device compatible. Once it has been determined that the URI content is required, the URI content is moved to the web caching server farm 108 .

[0158] The third type of caching is a transport protocol cache 118 used by the communications/gateway server 104 as shown in FIG. 1 .

[0159] E. The Filter Proxy Process Steps and Functional Relations

[0160] The filter proxy 106 may be composed of a single or multiple physical processors on a single or multiple physical servers that work together to perform requested tasks “on-the-fly” at the time the request or requests are made.

[0161] Referring back to FIGS. 2 and 3 , the filter proxy 106 includes the master browser 122 and one or more physical and logical filter proxy components, which can be formed into the filter proxy server array 124 . FIG. 2 defines the relationships between the filter proxy 106 and the other services of the filter proxy system 102 as well as a task list for re-authoring, compressing, and/or re-purposing the ML and its referenced images and other content by the filter proxy server array 124 . The task list will be further discussed in more detail in the following section.

[0162] Referring now to FIG. 8 , one embodiment of a method of filter proxy process 135 according to the principles of the present invention is illustrated. The filter proxy process 135 includes the operations from connecting to a device to sending a re-formatted or filtered ML and its filter content to a requesting device. It is appreciated that the sequence or order of the filter proxy process can be altered without departing from the present invention.

[0163] As shown in FIG. 8 , the filter proxy process 135 starts with an operation 136 of establishing a connection with a connected device by the master browser 122 . Such connection is established upon receipt of appropriate connection information from the communications/gateway server. Next, the user's authentication is verified in an operation 138 . The databases are queried in an operation 142 for the parameters required to support the user and device. Then, upon receipt of a URI request by the connected device, the URI is tagged and passed to an appropriate application session in an operation 144 . Next, the master browser 122 queries the cache to determine if the URI is present in an operation 146 and if it is, i.e. the “yes” path, further determines if the cached URI is current in an operation 164 by downloading the meta tags and data that enable the filter proxy to discern the currency of the cached URI. If the cached URI is not current, i.e. the “no” path of the operation 146 , the master browser 122 initiates a request to the URI host for download and directs such download to the web cache in an operation 148 . Upon establishing communications with the host of the URI, the master browser 122 of the requesting filter proxy determines if a filter proxy system is present in an operation 150 . If the filter proxy system is not present in the operation 150 , i.e. the “no” path, the URI is downloaded in an operation 158 without change. The URI resource downloaded is evaluated and all its referenced content is then downloaded concurrently by initiating the same dialogue/query in the operation 158 with each URI content host. If the filter proxy system is present in the operation 150 , i.e. the “yes” path, according to an operation 151 , the requesting filter proxy evaluates and establishes the URI processing requirements it desires to be performed by the URI host. The operation 151 establishes parameters based upon current system resources and URI historical request statistics. In an operation 152 , the requested URI and the requested processing parameters are passed to the URI host filter proxy system. In operation 153 , the requested URI and its parameters are evaluated and processed by the URI host filter proxy in the same manner as the requesting filter proxy evaluates and processes a user's request. The process in the operation 153 is autonomous of the requested process requested and controlled by the URI host filter proxy system administration policy. In an operation 154 , the host filter proxy generates process “status data”, which will be evaluated in an operation 160 of the requesting filter proxy to determine further filter processing necessary to fulfill the user and device requirements, and then compresses the URI content. The host filter proxy, in an operation 156 , evaluates URI processed and caches it based upon its caching policy. In the operation 158 , the “status data” and the processed and compressed URI are downloaded to the requesting filter proxy. The master browser 122 in the operation 160 analyzes the URI and any “status data” to determine filtering tasks to be performed in accordance with the profiles and template parameters, and system resources, prioritizes required filtering, and tasks filter processes to the filter proxy array. If the cached URI is determined to be current in an operation 164 , then the device and user profiles, in an operation 166 , determine what further filtering is required, if a template for the URI content is required and exists and used to locate the cached device formatted URI. If the cached URI is not device compliant, the master browser then analyzes the URI mark-up language in the operation 160 relative to the profiles and system resources and prioritizes and tasks filter processes to the filter proxy array.

[0164] The filter proxy re-authors, re-purposes, and/or compresses the URI Web page based on ML templates and the user and device profiles in an operation 162 . Then, the filter proxy moves to an operation 168 to cache qualified converted ML and text format based on URI reference and device profile. Data that is retrieved by the filter proxy and marked as “user private” follows caching rules, e.g., if cached, data may only be retrieved by an authorized user. If the URI in cache is determined to be compliant with the device, in the operation 166 , i.e. “yes” path, then the filter proxy moves to the operation 168 where all new compressed and re-authored ML are given a new reference name, and images and new ML are indexed to the URI in the appropriate databases for future quick retrieval, mapped to the cache and cached.

[0165] Finally, the processed ML and content are transmitted to the user in an operation 170 .

[0166] F. Filter Proxy Content Processing

[0167] Referring now to FIG. 9 , one embodiment of an operational process 172 of re-authoring, mapping, and conversion of the ML and the content of the filter proxy according to the present invention is illustrated in detail. It is appreciated that this embodiment illustrates the present invention as it is applied to mark-up language (ML) but is not limited to this form of control language. Furthermore, this embodiment is for illustrative purposes and does not restrict the content to text or static images but may include video, digital voice, and other types of digital content. Table 1 as discussed above illustrates the functions (e.g. a filter library) that may be performed to filter, re-author ML, re-purpose text, images, and/or other content, map functionality and hyperlinks, format the content for a device, and compress and convert the original ML, if necessary to another control language. It is appreciated that the list in Table 1 is for illustrative purposes and does not represent all task functions that are performed.

[0168] In FIG. 9 , the process 172 starts with an operation 174 of document conversion and determines if text only will be delivered to the user. Special document formats may not be renderable on the device by its browser. The device and user profiles, which determine the device ML and rendering capacity, are used to determine whether a document must be converted in an operation 176 to the ML, whereupon the proper conversion filter, in an operation 178 , is applied to convert it to appropriate ML. If no document conversion, in the operation 176 , is required, i.e. the “no” path, the device and user profiles are further used to determine if URI mark-up language content is stripped except for only the text in an operation 180 . Upon conversion of a document in the operation 178 , further filtering may be applied in accordance with the device and user profiles to determine if only text is allowed in the operation 180 . If text only, in the operation 180 , is required, i.e. the “yes” path, the ML is analyzed in an operation 182 for content and ML relationships such that all image references, associated hyperlinks, and other content forms are removed in an operation 184 , and duplicate text and hyperlinks are further edited from the original ML in an operation 186 to leave only the pertinent text. If text only is not a requirement in the operation 180 , i.e. the “no” path, further ML filtering is performed in an operation 188 .

[0169] The ML filter process 188 passes all ML to remove white spaces in an operation 190 , any comment in an operation 192 , un-needed background images in an operation 194 , and other references embedded in the ML. Upon removing such data, it will not affect the functionality or alter any copyrighted content but reduce the overall size of the ML that must be downloaded by the user and so as to re-author ML and content according to the device and user specifications, referencing FIG. 7 as an example of parameter relationship. The re-formatting of the ML and textural content for rendering on the specific device is determined in an operation 196 , and if required, i.e. the “yes” path, the device and template parameters are retrieved in an operation 198 and applied as constraints to the ML in an operation 200 . The device and template parameters from the operation 198 are further applied to any image filtering that may occur in an operation 214 . By applying ML constraints in the operation 200 , the ML is analyzed for text string length and maximum width setting in an operation 202 that is used to re-author the text control ML in an operation 204 by setting parameters such as a start point, max horizontal length, wrapping and image placement. Then, the tables are analyzed, converted, and re-authored in an operation 206 using the same parameter set. Next, dynamic pages are mapped as hyperlinks in an operation 208 so as to reduce overhead on initial download. Banners are eliminated as necessary in an operation 210 . Then, all duplicate hyperlink references and duplicates of text are removed in an operation 212 if not done so in the text only in the operation 180 “yes” path. The ML is ready for re-authoring of any required image references in an operation 244 upon completion of any image filtering in the operation 214 .

[0170] The image filter operation 214 utilizes input parameters from the device profile and ML template in the operation 198 and the resolved enhancement and pre-compression parameters in an operation 216 that are determined in response to system resources available in an operation 218 , such as bandwidth statistics provided by the communications/gateway server and filter processing resource statistics provided by the master browser. This allows to balance the system load and service the maximum number users and when user parameters are input in an operation 220 .

[0171] If re-purposing of images is required in an operation 222 , i.e. the “yes” path, images