US2004015537A1PendingUtilityA1

Handheld client framework system

Priority: Jul 15, 2002Filed: Jul 15, 2002Published: Jan 22, 2004
Est. expiryJul 15, 2022(expired)· nominal 20-yr term from priority
H04L 67/565H04L 67/34H04L 69/329G06F 16/9574H04L 67/5682H04L 67/289G06F 16/9577H04L 9/40H04L 67/303
42
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A handheld client framework system provides a server proxy client that services client requests for network accessible information and determines the server that is most appropriate to supply the requested information and sends information request packets to that server across the Internet and/or intranet. Server responses to information requests are received by the server proxy client. The server proxy client separates the response information into the appropriate data components. Data components are sent to the appropriate client. Presentation and logic components are temporarily stored in a one-behind cache on the client. A client will continue to use the presentation and logic components already installed or in the one-behind cache to service the current user request. Any updates sent by the server proxy client and stored in the one-behind cache are retrieved by the client upon subsequent use by the user. The state of the client is saved by the server proxy client so that the client is not dropped when a user, for example, changes from a wired connection to a wireless connection. The invention includes a scripting language that supplies the logic component of the client and gives the client unlimited flexibility by allowing the host to modify the client's behavior or add new features at any time.

Claims

exact text as granted — not AI-modified
1 . A process for a framework architecture for client systems, comprising the steps of: 
 providing a server proxy client    providing means on said server proxy client for receiving a client information request from a client system;    providing server determination means on said server proxy client for determining the proper server to service said client request;    sending said client request to said proper server;    receiving said proper server's response to said client request;    wherein said server proxy client acts as a proxy client for said client system, performing the bulk of data processing for said client system;    wherein said server proxy client updates said client system with data, presentation, and logic components using a universal data format;    wherein said server proxy client separates raw data from presentation aspects of said response and places said data into said universal data format;    sending said data to said client system;    wherein said server proxy client receives presentation and logic component updates; and    wherein said presentation component updates are for a specific client device type.    
     
     
         2 . The process of  claim 1 , wherein said logic component updates are shared between different client device types.  
     
     
         3 . The process of  claim 1 , further comprising the step of: 
 providing a one-behind cache on said client system; and    wherein said client system checks said one-behind cache for any presentation or logic components relating to a user's request;    wherein if any components relating to a user's request exists in said one-behind cache, said client system checks if said components have expired;    wherein said client system uses said components to service the user's request.    
     
     
         4 . The process of  claim 3 , wherein if said components have expired, said client system requests any current versions of the expired components from said server proxy client, wherein said server proxy client checks the current version of a requesting client's presentation and logic components, if any of the presentation and logic components requires updating, then said server proxy client retrieves the latest version of any of the presentation and logic components and sends it to the requesting client, and wherein the requesting client stores the latest version of any of the presentation and logic components in said one-behind cache.  
     
     
         5 . The process of  claim 1 , further comprising the step of: 
 sending said presentation and logic component updates to a client system.    
     
     
         6 . The process of  claim 1 , wherein said client system uses said data and presentation components to create displays to a user.  
     
     
         7 . The process of  claim 1 , wherein said client system reuses said data component for other display purposes.  
     
     
         8 . The process of  claim 1 , further comprising the step of: 
 providing means on said server proxy client for saving a client system's state on storage device; and    wherein the saved client system's state allows said server proxy client to continue a client system's session when the client system changes connection methods to or loses coverage with said server proxy client.    
     
     
         9 . The process of  claim 1 , further comprising the step of: 
 providing a scripting language;    wherein said logic component updates are written in said scripting language;    wherein said server proxy client compiles scripts written in said scripting language into executable bytecodes;    wherein said server proxy client updates said client system's features by sending said client system said executable bytecodes; and    wherein said client system executes said executable bytecodes in response to a user's input.    
     
     
         10 . The process of  claim 9 , wherein a client system's presentation aspects are controlled using said scripting language.  
     
     
         11 . The process of  claim 1 , wherein communication between said server proxy client and said client system is via a binary encoding of an XML data stream.  
     
     
         12 . A process for dynamically configuring client systems, comprising the steps of: 
 providing a host server;    providing a scripting language;    wherein said host server compiles scripts written in said scripting language into executable bytecodes;    wherein said host server, upon receipt of a request for specific up to date presentation components and/or executable bytecodes from a client system, checks if the client system's original presentation components and/or executable bytecodes have expired;    wherein said host server updates the client system's features by sending the client system updated presentation components and/or executable bytecodes if the original presentation components and/or executable bytecodes on the client system have expired; and    wherein a client system executes presentation components and/or executable bytecodes in response to a user's input.    
     
     
         13 . The process of  claim 12 , wherein said scripts define program logic.  
     
     
         14 . The process of  claim 12 , wherein said scripts create and control user interface displays.  
     
     
         15 . The process of  claim 12 , wherein said client system receives requested network information from said host server separated into data and presentation components.  
     
     
         16 . An apparatus for a framework architecture for client systems, comprising: 
 a server proxy client;    means on said server proxy client for receiving a client information request from a client system;    server determination means on said server proxy client for determining the proper server to service said client request;    a module for sending said client request to said proper server;    a module for receiving said proper server's response to said client request;    wherein said server proxy client acts as a proxy client for said client system, performing the bulk of data processing for said client system;    wherein said server proxy client updates said client system with data, presentation, and logic components using a universal data format;    wherein said server proxy client separates raw data from presentation aspects of said response and places said data into said universal data format;    a module for sending said data to said client system;    wherein said server proxy client receives presentation and logic component updates; and    wherein said presentation updates are for a specific client device type.    
     
     
         17 . The apparatus of  claim 16 , wherein said logic component updates are shared between different client device types.  
     
     
         18 . The apparatus of  claim 16 , further comprising: 
 a one-behind cache on said client system; and    wherein said client system checks said one-behind cache for any presentation or logic components relating to a user's request;    wherein if any components relating to a user's request exists in said one-behind cache, said client system checks if said components have expired;    wherein said client system uses said components to service the user's request.    
     
     
         19 . The apparatus of  claim 18 , wherein if said components have expired, said client system requests any current versions of the expired components from said server proxy client, wherein said server proxy client checks the current version of a requesting client's presentation and logic components, if any of the presentation and logic components requires updating, then said server proxy client retrieves the latest version of any of the presentation and logic components and sends it to the requesting client, and wherein the requesting client stores the latest version of any of the presentation and logic components in said one-behind cache.  
     
     
         20 . The apparatus of  claim 16 , further comprising: 
 a module for sending said presentation and logic component updates to a client system.    
     
     
         21 . The apparatus of  claim 16 , wherein said client system uses said data and presentation components to create displays to a user.  
     
     
         22 . The apparatus of  claim 16 , wherein said client system reuses said data component for other display purposes.  
     
     
         23 . The apparatus of  claim 16 , further comprising: 
 means on said server proxy client for saving a client system's state on storage device; and    wherein the saved client system's state allows said server proxy client to continue a client system's session when the client system changes connection methods to or loses coverage with said server proxy client.    
     
     
         24 . The apparatus of  claim 16 , further comprising: 
 a scripting language;    wherein said logic component updates are written in said scripting language;    wherein said server proxy client compiles scripts written in said scripting language into executable bytecodes;    wherein said server proxy client updates said client system's features by sending said client system said executable bytecodes; and    wherein said client system executes said executable bytecodes in response to a user's input.    
     
     
         25 . The apparatus of  claim 24 , wherein a client system's presentation aspects are controlled using said scripting language.  
     
     
         26 . The apparatus of  claim 16 , wherein communication between said server proxy client and said client system is via a binary encoding of an XML data stream.  
     
     
         27 . An apparatus for dynamically configuring client systems, comprising: 
 a host server;    a scripting language;    wherein said host server compiles scripts written in said scripting language into executable bytecodes;    wherein said host server, upon receipt of a request for specific up to date presentation components and/or executable bytecodes from a client system, checks if the client system's original presentation components and/or executable bytecodes have expired;    wherein said host server updates the client system's features by sending the client system updated presentation components and/or executable bytecodes if the original presentation components and/or executable bytecodes on the client system have expired; and    wherein a client system executes presentation components and/or executable bytecodes in response to a user's input.    
     
     
         28 . The apparatus of  claim 27 , wherein said scripts define program logic.  
     
     
         29 . The apparatus of  claim 27 , wherein said scripts create and control user interface displays.  
     
     
         30 . The apparatus of  claim 27 , wherein said client system receives requested network information from said host server separated into data and presentation components.

Join the waitlist — get patent alerts

Track US2004015537A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.