US20010047394A1 - System, method, and computer program product for executing scripts on mobile devices - Google Patents

System, method, and computer program product for executing scripts on mobile devices Download PDF

Info

Publication number
US20010047394A1
US20010047394A1 US09754256 US75425601A US2001047394A1 US 20010047394 A1 US20010047394 A1 US 20010047394A1 US 09754256 US09754256 US 09754256 US 75425601 A US75425601 A US 75425601A US 2001047394 A1 US2001047394 A1 US 2001047394A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
object
script
server
computer
client
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09754256
Inventor
David Kloba
Michael Gray
David Moore
Thomas Whittaker
David Williams
Rafael Weinstein
Joshua Freeman
Linus Upson
Adam Dingle
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AvantGo Inc
Original Assignee
AvantGo Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • G06F16/957
    • G06F16/9574
    • G06F16/9577
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/04Network-specific arrangements or communication protocols supporting networked applications adapted for terminals or networks with limited resources or for terminal portability, e.g. wireless application protocol [WAP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/22Tracking the activity of the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/30Network-specific arrangements or communication protocols supporting networked applications involving profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/02Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/30Network-specific arrangements or communication protocols supporting networked applications involving profiles
    • H04L67/306User profiles

Abstract

Described herein are systems, methods, computer program products, and combinations and sub-combinations thereof, for executing scripts that can be loaded on mobile devices (as well as other types of devices), and for users of mobile devices to interact with such scripts on their devices in an interactive manner. According to embodiments, the present invention performs script operations for mobile devices including steps for sending a request for an object and a list of support languages, and receiving the object and any related scripts in the supported languages.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0001]
  • The present invention relates generally to mobile communications, and more particularly relates to technology for using interactive applications while on-line and off-line on mobile devices. [0002]
  • 2. Related Art [0003]
  • A variety of mobile devices (such as personal data assistants, or PDAs) exist. Such mobile devices include ones based on the Palm operating environment and the Windows CE operating environment. [0004]
  • A variety of software applications for those mobile devices also exist. [0005]
  • What does not exist prior to the invention are software applications for enabling web content (as well as other objects) to be loaded on mobile devices, and for users of mobile devices to operate with such web content on their mobile devices in an interactive manner while in an off-line mode. [0006]
  • SUMMARY OF THE INVENTION
  • Briefly stated, the invention includes systems, methods, computer program products, and combinations and sub-combinations thereof for enabling web content (as well as other objects) to be loaded on mobile devices (as well as other types of devices), and for users of mobile devices to operate with such web content on their mobile devices in an interactive manner while in an off-line mode. [0007]
  • According to embodiments, the present invention performs script operations for mobile devices including steps for sending a request for an object and a list of support languages, and receiving the object and any related scripts in the supported languages. [0008]
  • These and additional features and advantages of the present invention will become more apparent from the detailed description set forth below when taken in conjunction with the drawings in which like reference characters generally identify corresponding elements throughout.[0009]
  • BRIEF DESCRIPTION OF THE FIGURES
  • The accompanying drawings, which are incorporated herein and form part of the specification, illustrate embodiments of the present invention and, together with the description, further serve to explain the principles of embodiments of the invention. [0010]
  • FIG. 1A is a block diagram of an embodiment of the invention; [0011]
  • FIG. 1B is an alternative block diagram of the invention; [0012]
  • FIG. 1B[0013] 1 is a block diagram of an example data processing unit useful in some embodiments for implementing items from FIGS. 1A and 1B;
  • FIGS. 1C, 1D, [0014] 1E, 1F, 1G, 1H, 1I, and 1J are used to generally describe embodiments of the invention;
  • FIG. 2A is a block diagram illustrating additional modules according to an embodiment of the invention; [0015]
  • FIG. 2B[0016] 1 is a block diagram illustrating an additional module according to an embodiment of the invention;
  • FIG. 2B[0017] 2 is a block diagram illustrating an additional module according to an embodiment of the invention;
  • FIG. 2C is a diagram illustrating some processing components according to an embodiment of the invention; [0018]
  • FIG. 2D[0019] 1 is an example flowchart relating to structuring interactive content according to an embodiment of the invention;
  • FIG. 2D[0020] 2 is an example flowchart relating to structuring and rendering interactive content according to another embodiment of the invention;
  • FIG. 2E is a diagram illustrating an example of content formatting according to an embodiment of the invention; [0021]
  • FIG. 2F[0022] 1 is a diagram illustrating the content instantiation architecture according to an embodiment of the invention;
  • FIG. 2F[0023] 2 is a diagram illustrating the content instantiation architecture according to another embodiment of the invention;
  • FIG. 2F[0024] 3 is a flowchart relating to a optimized data modification according to an embodiment of the invention;
  • FIG. 2G is a diagram illustrating an example of a database architecture; [0025]
  • FIG. 2H is a diagram illustrating the content structure according to an embodiment of the invention; [0026]
  • FIGS. [0027] 2I1 and 2I2 demonstrate CSS style examples according to embodiments of the invention;
  • FIG. 2J demonstrates an example of floating images, where the text flows around the image; [0028]
  • FIG. 2K is an example architecture showing construction, layout, rendering, and cross-platform technology, according to embodiments of the invention; [0029]
  • FIG. 2L is an example operation where a device is able to sync with a current server, according to embodiments of the invention; [0030]
  • FIG. 3A is an example flowchart relating to a server cache for transformed content according to an embodiment of the invention; [0031]
  • FIG. 3B is an example flowchart relating to a server cache for transformed content having negative caching according to an embodiment of the invention; [0032]
  • FIG. 3C is an exemplary fetch diagram illustrating hits on a server occurring at the same time; [0033]
  • FIG. 3D is an example flow diagram representing a method for randomizing the expiration of objects set to expire at the same time according to an embodiment of the invention; [0034]
  • FIG. 3E is a diagram showing freshness lifetime for an object according to an embodiment of the present invention; [0035]
  • FIG. 3F is a block diagram illustrating a single account/profile having multiple devices according to an embodiment of the invention; [0036]
  • FIG. 3G shows an example screen shot for enabling a user to add multiple servers according to an embodiment of the invention; [0037]
  • FIG. 3H is an exemplary block diagram representing a single mobile device that connects to multiple servers according to an embodiment of the invention; [0038]
  • FIG. 3I is an exemplary flow diagram representing a sync process for a device connected to multiple servers according to an embodiment of the invention; [0039]
  • FIG. 3J is an exemplary diagram illustrating a multiple device—multiple server configuration according to an embodiment of the invention; [0040]
  • FIG. 4 is a block diagram illustrating script compiler modules according to an embodiment of the invention; [0041]
  • FIG. 5 is a block diagram illustrating a language interpreter module according to an embodiment of the invention; [0042]
  • FIG. 6 is a block diagram illustrating the operations of delegated language interpreter modules according to an embodiment of the invention; [0043]
  • FIG. 7 is a block diagram illustrating a server with a server-side language interpreter module according to an embodiment of the invention; [0044]
  • FIG. 8 is a flowchart showing a routine for script operations according to an embodiment of the invention; [0045]
  • FIG. 9 is a flowchart showing a routine for executing scripts according to an embodiment of the invention; [0046]
  • FIG. 10 is a flowchart showing a routine for updating properties according to an embodiment of the invention; and [0047]
  • FIG. 11 is a flowchart showing a routine for server-side script operations according to an embodiment of the invention.[0048]
  • It should be understood that these figures depict embodiments of the invention. Variations of these embodiments will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. For example, the flow charts contained in these figures depict particular operational flows. However, the functions and steps contained in these flow charts can be performed in other sequences, as will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. [0049]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • 1. Overview of Embodiments of the Present Invention [0050]
  • Embodiments of the present invention are briefly described in this section. [0051]
  • Briefly stated, the invention is directed to placing objects such as, but not limited to, Internet or Web content on data processing devices, such as but not limited to mobile devices. Table 1 lists examples of such Internet content, although the invention is not limited to these examples. [0052]
    TABLE 1
    Internet Content
    Internet content includes but is not limited to:
    HTML
    JavaScript ™
    Channels
    Java ™
    ActiveX
    Multimedia:
    Images (e.g., JPEG, GIF, PNG, vector graphics, etc.)
    Audio Files (e.g. MP3)
    Video (e.g. AVI)
    Streaming Content: Voice/Data/Video
    Binary files
    XML
    Applications
    Data Objects
    Documents
    Anything that can be delivered via a “browser”
  • Table 2 lists examples of mobile devices, although the invention is not limited to these examples. [0053]
    TABLE 2
    Mobile Devices
    Mobile devices include but are not limited to:
    Handheld Computers
    Cellular Phones
    Internet-enabled Phones
    Pagers
    Radios
    TVs
    Audio Devices
    Car Audio Systems
    Recorders
    Text-to-Speech Devices
    Bar-code Scanners
    Net Appliances
    Mini-browsers
    Personal Data Assistants (PDAs)
  • FIG. 1C illustrates the concept of the invention of placing objects on data processing devices, such as mobile devices. [0054]
  • 1.1 Enabling Mobile Devices to Interact with Networked Applications [0055]
  • The invention includes technology for using applications on mobile devices that interact with the Internet or with intranets. The invention enables applications available via a network or via an Internet/intranet to download and to run on mobile devices. Consequently, the invention includes software and methods for administering a server that manages the variables relevant to a mobile device/server environment. [0056]
  • The invention enables: [0057]
  • Mobile devices to operate in conjunction with a Web server, even when the mobile devices are not coupled directly to the PC using portable on-device servers: Web pages are loaded, viewed, cached, and deleted even when the device is not coupled to any network. [0058]
  • Mobile devices to operate in conjunction with the Web, Internet, or intranet via a connection mechanism and then in disconnected mode or with the Web, Internet, or intranet in wireless mode with a continuous or a discontinuous connection mechanism. [0059]
  • A technique for interactive connectivity between handheld computers and computer networks. [0060]
  • Fleet management for centrally administering information in a handheld network environment that includes, but is not limited to, user data, user groups, group channels, channel data, personal channels, commercial channels, user accounts, corporate account, software groupings, personal information management, form delivery, form management, device configuration, device databases, device contents, and devices parameters. [0061]
  • Obtaining updated Web pages and other network objects, for use when the mobile device is not communicating with the PC. [0062]
  • An example mobile device/server environment is shown in FIG. 1D. [0063]
  • 1.2. Rapid Transfer of Web Pages to Mobile Devices [0064]
  • To improve efficiency of data exchange between mobile devices and networked content, the invention includes an improved communication protocol that collects requests and responses for network objects into a smaller number of protocol (such as HTTP) requests and responses. The server also determines the nature and the resources of the mobile device. This protocol is represented, for example, in FIG. 1E. [0065]
  • Downstream, the data is encoded in a data format called content stream (tokenized version of the data) and sent to the device. The content stream format creates a tokenized codification of HTML pages that is sent to the device. (The device receives the content stream and presents the material on the device.) [0066]
  • The HTML page is encoded into the content stream and sent to the device. The encoding is a mapping of parent and child HTML elements and/or resources to alphanumeric values. [0067]
  • The sync operation of the invention includes various synchronization processes that can collect information from the Internet to a server, and to the client. In embodiments, the usage of the term “sync” refers to the overall operation of connecting a client to a server for the exchange, interaction, creation, and removal of data. [0068]
  • In one embodiment, syncing can be defined as mirroring data on a client and a server, such that the data is the same on client and server. In other embodiments, syncing can be defined as overwriting data on a client or on a server, such that the data on either a client replaces the data on a server, and vice versa. [0069]
  • In one embodiment, a sync operation involves a user placing a mobile device into an adapter that includes a sync button. The adapter is connected to a server. Upon pressing the sync button, the user initiates the sync operations of the present invention, which include various synchronization processes (specific delivery modes). Thus, the term sync is meant to refer to the overall operation of linking a client to a server. Synchronization is meant to refer to the specific process of copying, adding, filtering, removing, updating and merging the information between a client and a server. Any number of synchronization processes can be executed during a sync. [0070]
  • Before being sent downstream the data is compared to the data that is known to be on the client and then the client is updated all at once in a one-up/one-down synchronization method, which is represented in FIG. 1F. The server sets the client to preemptively prepare all device information necessary during the sync. Then the server receives the set of information in a one-up fashion. The server collates the information and sends the information in a one-down fashion. This optimizes the sync's efficiency and speed. The sync process, according to embodiments of the invention, is represented in FIGS. 1G and 1H. [0071]
  • 1.3. Optimizing Content of Web Pages for Mobile Devices [0072]
  • When Web content and other network objects pass through the server they are processed to minimize their size and to optimize their delivery to mobile devices: for presentation, for ease of use, for efficiency, for size, etc. [0073]
  • The invention uses server logic to optimize content. The server assesses the mobile device to optimize web content for the particular device. Factors that the server logic considers when performing this optimization include, but are not limited to (it is noted that the server may consider subsets of the following, depending on the application and implementation): [0074]
  • Dynamic memory specifications [0075]
  • High memory specifications [0076]
  • Protected Memory [0077]
  • Storage Memory [0078]
  • Database Memory [0079]
  • Available storage space [0080]
  • Screen size [0081]
  • User profile(s) [0082]
  • Color depth [0083]
  • Applications on device [0084]
  • Buttons on-device [0085]
  • Data markers (e.g., cookies, tokens) [0086]
  • Preferences [0087]
  • Fonts [0088]
  • Font specifications [0089]
  • Sync type [0090]
  • Synchronization types [0091]
  • Supported data types [0092]
  • Supported mime types [0093]
  • Connection/Network profile [0094]
  • An example optimization process is shown in FIG. 11. [0095]
  • On the server, the graphic is optimized per the state information of the device. If the device sends down the need for the graphic on a page for a device with a display that is 27 cm wide and in grayscale, the server sends its best version of a graphic optimized for that environment. [0096]
  • The technology of the invention is extended by tags on HTML pages that identify content that is designed for additional modifications. Any and all bytes processed by the server are potentially examined for compression/optimization. The server detects the tag and executes the necessary logic. [0097]
  • Table 3 illustrates example tags (the invention is not limited to the tags shown in Table 3). [0098]
    TABLE 3
    Sample Markup Language
    Tag Effect
    <META NAME=“Handheld- This tag enables several HTML features
    Friendly” content=“True”> that are normally turned off. Most notably,
    The invention does not try to display
    TABLE tags or the HSPACE and
    VSPACE attributes of
    IMG tags unless the page is marked as
    “HandheldFriendly”. Most TABLEs or
    H/VSPACEs are designed for much larger
    screens.
    <AGIGNORE></ Used in a wireless channel. Use the
    AGIGNORE> AGIGNORE tag to surround content
    within an HTML page that may be
    inappropriate or unattractive on Internet-
    enabled phones.
    <AGPAGEBREAK Used in a wireless channel. Breaks up
    TITLE=”your title> pages on request. When processing pages
    for devices other than WAP phones, the
    server ignores the AGPAGEBREAK tag.
  • Web Content Aggregation, Web Channel Development, and Web Content Delivery for Users of the Internet and of Mobile Devices [0099]
  • The invention is extended by the coupling of devices to the content available at the server web site (see the example shown in FIG. 1J). [0100]
  • These and other embodiments of the present invention are described in greater detail below. [0101]
  • Structural Embodiments of the Present Invention [0102]
  • FIG. 1A is a block diagram of a data processing environment [0103] 102 according to an embodiment of the invention. The data processing environment 102 includes a server 104 (although only one server 104 is shown, in practice the data processing environment 102 may include a plurality of servers), one or more devices 106, one or more adapters 118, and one or more providers 128.
  • Generally, the server [0104] 104 maintains a collection of channels. In an embodiment, a channel comprises a collection of objects. An object is any entity that can be transferred to a client 108, such as but not limited to content, applications, services, images, movies, music, links, etc.
  • A channel includes a number of properties. At least some of these properties define the objects that the channel includes. Such properties include, but are not limited to, the following (properties of channels may vary depending on the application and/or implementation): [0105]
  • A name of the channel. [0106]
  • A location of a root object (such as but not limited to a URL). In an embodiment, this root object is included in the channel. An indication of the number of levels below the root object, for which to include objects in the channel. For example, in an embodiment, if this property is equal to “1 level,” then all objects that are 1 level down from the root object (reached by traversing links in the root object), are included in the channel. If this property is equal to “2 levels,” then all objects that are 1 level down from the root object (reached by traversing links in the root object), and all objects that are 1 level down from those objects (reached by traversing links in those objects), are included in the channel. Embodiments of the invention allow “uneven” trees, where some branches of the tree extent to a greater number of levels than other branches of the tree. In other embodiments, the trees are even or balanced. [0107]
  • A maximum size of the channel. For example, if this is set to 500 Kbytes, then the aggregate size of the objects in the channel cannot be greater than 500 Kbytes. If the aggregate size of the objects in the channel is greater than this value, then embodiments of the invention may delete objects from the channel and/or delete portions of objects in the channel. [0108]
  • An indication of which resource objects are enabled for the channel: [0109]
  • An indication of whether or not images are to be included in or excluded from objects in the channel; and [0110]
  • An indication of whether or not scripts are enabled in objects in the channel. [0111]
  • A refresh methodology. [0112]
  • It is noted that the properties associated with channels may vary from implementation to implementation. Also, implementations may employ combinations of the above properties, and/or properties in addition to the following, as will be appreciated by persons skilled in the relevant art(s). [0113]
  • The invention includes processes for managing channels, including but not limited to adding channels to the collection of channels maintained by the server [0114] 104.
  • The server [0115] 104 offers channels to clients 108. A user associated with or on behalf of a client 108 may access the server 104 and view the collection of channels. The client 108 (via the user, for example) may then select any combination of the channels in the collection. The server 104 maintains a list of the channels associated with each of the clients 108.
  • During a synchronization process, the server [0116] 104 loads a device 108 with the channels associated with the client 108. Generally, the server 104 does this by obtaining from providers 128 the objects defined by the channels, and causing those objects to be stored on the client 108. Thus, during the synchronization process, the server 104 will load the client 108 with the selected channels. More particularly, the server 104 will load the client 108 with the objects associated with the channels.
  • The client [0117] 108 may process and use those objects when not connected to the server 104. The invention enables the client 108 to actively interact with the objects and channels.
  • In one embodiment, the client [0118] 108A directly interacts with the server 104 via some transmission medium 120B, which may be any wired or wireless medium using any communication protocol.
  • In another embodiment, the client [0119] 108B indirectly interacts with the server 104 via an adapter 118. For example, the client 108B may be a mobile device (such as a Palm device) and the adapter 118 may be a cradle and a computer coupled to the cradle (the mobile device is inserted into the cradle). In this instance, the adapter 118 presents itself to the server 104 as a client 108B (via client communications module 110C). When the server 104 sends objects to the adapter 118, the adapter interface module 116 writes those objects to client 108B. In embodiments, adapter interface module 116 can be a Hot Sync™ Manager, an Active Sync™, etc. It is noted that the invention is not limited to any of the implementation examples discussed herein.
  • The components shown in FIG. 1A shall now be described in greater detail. [0120]
  • The server [0121] 104 includes an administration module 122, a database module 126, a user interface 130, a web synchronization module 124, a server extension module 156, a fleet management module 154, a notification module 132, and a server communication module 114. Other embodiments of server 104 may include a subset of these modules, and/or may include additional modules.
  • The administration module [0122] 122 controls and manages the states of the server 104 and the clients 108. For example, the administration module 122 manages and controls groups of clients 108, permissions assigned to clients 108, groups, and channels. For example, the administration module 122 administers the users/clients 108 assigned to groups, and the channels associated with users. These and additional functions performed by the administration module 122 are described herein.
  • The database module [0123] 126 controls access to databases associated with the server 104. The database module 126 maintains information relevant to the clients 108, as well as information relevant to the modules contained in the server 104. The database module 126 manages information on the collection of channels maintained by server 104. These and additional functions performed by the database module 126 are described herein.
  • The user interface [0124] 130 is, in an embodiment, a graphical user interface (GUI) that enables users and clients 108 to access functions and modules offered by the server 104. More generally, the user interface 130 within server 104 provides access to server 104 and the modules and resources contained therein.
  • The invention supports various server web sites that are available through any communication medium, such as but not limited to the Internet, intranets, direct dial up links, etc. The UI [0125] 130 enables such web sites.
  • These and additional functions performed by the user interface [0126] 130 are described herein.
  • The web synchronization module [0127] 124 is an application/instance of server extension module 156, and controls synchronization of web content to client 108. The invention may include other synchronization modules (which are application/instances of server extension module 156) that control synchronization of other types of objects to clients 108. For example, the server 104 may administer a calendar that may be installed on clients 108. The synchronization of appointments, events and/or dates on this calendar between clients 108 and the server 104 may be performed by a calendar synchronization module. These and additional functions performed by the server extension module 156 are described herein.
  • The fleet management module [0128] 154 performs functions associated with fleets of clients 108, which are groups of clients 108. For example, fleet management module 154 may perform global or mass operations on groups (fleets) of clients 108, such as loading or updating an application on groups (fleets) of clients 108. Another example of a mass operation is retrieval of information on clients 108 in a fleet, such as the free memory in clients 108 in a fleet (this would help an organization determine if its clients 108 need a memory upgrade). These and additional functions performed by the fleet management module 154 are described herein.
  • The server extension interface/module [0129] 156 enables modules, such as third party modules, to operate in or work with the server 104 (and modules contained in the server 104). The server extension module 156 presents an API (application programming interface). Modules in the server 104 may operate with other devices in the server 104 by conforming to the server API.
  • For example, the web synchronization module [0130] 124 and the fleet management module 154 (as well as other types of synchronization modules, not shown in FIG. 1A) may interact with databases on the server 104 via the database module 126 by going through the server extension module 156. The web synchronization module 124 and the fleet management module 154 may not be able to interact directly with the database module 126 for a number of reasons. For example, they may support different data formats or simply “speak different languages.” However, they can interact via the server extension module 156 as well as other server modules as long as they conform to the API of the server extension module 156. This is true of any modules in the server 104, or that interact with the server 104.
  • Server communication module [0131] 114 enables communication between the server 104 and entities external to the server 104, such as clients 108, adapters 118, providers 128, work stations, etc. The server 104 communicates with these entities via communication mediums 120, which may be any type of wireless or wired communication using any protocol. It is noted that multiple server communication modules 114 may execute in a single server 104. For example, in one embodiment, server communication module 114 is a TCP/IP stack. In another embodiment, server communication module 114 is a secure socket layer stack or a compression stack. The invention is not limited to any implementation examples discussed herein. These and additional functions performed by the server communication module 114 are described herein.
  • The notification module [0132] 132 sends objects to clients 108 beyond objects related to channels associated with clients 108. Such objects could be requested by client 108 in advance. For example, a client 108 could ask for a notification when an event happens, such as when a stock reaches a target price. When the event occurs, the notification module 132 would cause an appropriate notification(s)/object(s) to be sent to the client 108. Alternatively, the notification module 132 may send objects to clients 108 without any prior explicit request from the client 108. For example, the notification module 132 might send channels to clients 108 when such channels are identified to be similar to those already selected by the clients 108. Also, the notification module 132 might send appropriate notifications/objects to the clients 108 when such clients 108 receive email or faxes at the server 104. In embodiments, the notification module 132 transmits such objects to the client 108 immediately when the event occurs, during the next synchronization with the client 108, or at some other future synchronization.
  • An alternative representation of server [0133] 104 is shown in FIG. 1B. FIG. 1B illustrates, for example, that messages from entities outside of server 104 are received by server extension interface/module 156 via server communications modules 114. Generally, such messages represent requests for the server 104 to perform various functions. The server extension module 156 conceptually operates as a dispatcher who routes such messages to other modules contained in the server 104, such as web synchronization module 124 (who handles requests to synchronize with web content), notification module 132, fleet management module 154 (who handles fleet related requests), and/or third party modules 155 (such as other synchronization modules). Thus, the invention supports modules 155 generated by third parties to perform various functions. Such modules 155 “plug-in” to the server 104 via the server extension module 156.
  • Referring again to FIG. 1A, the devices [0134] 106 may be any type of data processing device. In embodiments of the invention, the devices 106 are mobile computing devices, although the invention is not limited to these embodiments. In such example embodiments, the devices 106 may include, but are not limited to, handheld computers, cellular phones, internet-enabled phones, pagers, radios, tvs, audio devices, car audio systems, recorders, text-to-speech devices, bar-code scanners, net appliances, mini-browsers, personal data assistants (PDAs), etc.
  • In embodiments of the invention, the devices [0135] 106 include software, hardware, and/or combinations thereof related to client functionality (such client functionality is described herein). When a device 106 includes such software, hardware, and/or combinations thereof, the device 106 is referred to herein as a client 108. Accordingly, it can be said that the data processing environment 102 includes one or more clients 108.
  • Clients [0136] 108 each may include a layout and rendering module 134, a forms module 136, a control module 142, a user interface 144, a client extension interface 138, a client interface module 112, a client communications module 110, a JavaScript™ engine 140, and a database module 146. Other embodiments of clients 108 may include a subset of these modules, and/or may include additional modules.
  • Layout and rendering module [0137] 134 controls the processing of data objects on client 108, such as the layout and rendering of data objects on client 108. For example, the layout portion of module 134 obtains information from databases of the client 108 (via the database manager 146) and determines where such information should be rendered on the display of the client 108. Such information may include anything that can be rendered, such as but not limited to images, text, links, etc. The rendering portion of module 134 is responsible for drawing items on the display (drawing bits to the screen). These and additional functions performed by the layout and rendering module 134 are described herein.
  • The forms module [0138] 136 controls and manages forms. For example, in embodiments the forms module 136 manages aspects of off-line forms, such as HTML forms and/or multi-page forms. The forms module 136 enables access to and user interaction with forms (in some embodiments, the forms module 136 via UI 144 enables users of client 108 to directly access forms). The forms module 136 maintains the status of forms. Forms module 136 can also include a forms manager (not shown) to provide added functionality. These and additional functions performed by the forms module 136 are described herein.
  • The user interface [0139] 144 is preferably a graphical user interface that enables users to interact with client 108 and functions and modules provided by the client 108. More generally, UI 144 controls how functions presented by modules of the client 108 are presented to users. The UI 144 controls how users interact with such functions and modules. It is noted that the functionality of the UI 144 may be distributed. For example, portions of the UI 144 may reside in the forms module 136, as well as other modules of client 108. These and additional functions performed by the user interface 144 are described herein.
  • The client extension interface [0140] 138 enables modules, such as third party modules, to operate in or work with the client 108 (and modules contained in the client 108). The client extension interface 138, also known as an on-device server, presents an API (application programming interface) that is, in embodiments, common to clients 108 on many architectures.
  • Modules in the client [0141] 108 can work together via the client extension interface 138. For example, the JavaScript™ engine 140 may decide that it wishes to display a message to the user. To do this, the JavaScript™ engine 140 would work through the client extension interface 138 to cause the UI 144 to display the message to the user. The JavaScript™ engine 140 may not know how to directly interact with the UI 144. However, as long as both the JavaScript™ engine 140 and the UI 144 conform to the API of the client extension interface 138, then they can operate together.
  • Similarly, the control module [0142] 142 may decide that it needs to store some data in a database. The control module 142 would do this by working with the client extension interface 138 to access the database module 146 to effect such a modification to the databases in the client 108. These and additional functions performed by the client extension interface 138 are described herein.
  • The JavaScript™ engine [0143] 140 executes objects written in the JavaScript™ language that operate on client 108. As noted, the JavaScript™ engine 140 conforms to the API of the client extension interface 138, and works with the client extension interface 138 to work with other modules in client 108. These and additional functions performed by the JavaScript™ engine 140 are described herein.
  • Although not shown in FIG. 1A, embodiments of the invention include other engines for executing other types of scripts on client [0144] 108. These other engines can interact with other modules on client 108 as long as the engines conform to the API of the client extension interface 138.
  • The database module [0145] 146 controls access to databases associated with client 108. More generally, the database manager 146 controls access to resources on the client 108. For example, the control module 142 may interact with the database manager 146 to open an address book in the databases, and to write a record to the address book. Alternatively, the forms module 136 can interact with the database module 146 to access forms that are stored in the databases. These and additional functions performed by the database module 146 are described herein.
  • Client communications module [0146] 110 enables the client 108 to interact with external entities, such as server 104. In embodiments, the client communications module 110 enables TCP/IP traffic, although the invention is not limited to this example. More generally, the client communications module 110 enables communication over any type of communication medium 120, such as wireless, wired, etc., using any communication protocol, such as a pager protocol. These and additional functions performed by the client communications module 110 are described herein. The client interface module 112 enables the client 108 to communicate with adapters 118. Client interface module 112 optionally links to client communications module 110 in some embodiments to provide functionality (for example, when the client communications module 110 uses a wireless modem's drivers, which are accessed via client interface module 112). In embodiments, the client interface module 112 may be Hot Sync™ Manager in the Palm operating environment, or Active Sync™ in the Windows CE™ operating environment, or Pilot Link™ in the Unix operating environment. It is noted that these implementation examples are provided for illustrative purposes only. The invention is not limited to these examples. These and additional functions performed by the client interface module 112 are described herein.
  • The control module [0147] 142 coordinates the activities of the other modules in client 108 so that all the modules share resources properly. For instance, control module 142 can determine priorities for shared resources such as processing time, accessing memory, etc.
  • Providers [0148] 128 are sources of various types of objects, such as but not limited to content (content providers 128A), applications (application providers 128B), services (service providers 128C), etc. Providers 128 may also include servers 104′ (similar to server 104), which may provide objects such as but not limited to content, applications, services, etc. For example, and without limitation, the application providers 128B may provide objects relating to (without limitation) operating system updates/changes, system upgrades, application updates/changes, etc.
  • Adapters [0149] 118 include an adapter interface module 116, a user interface 148, a database module 150, an adapter synchronization module 152, and a client communications module 110. Other embodiments of adapters 118 may include a subset of these modules, and/or may include additional modules.
  • Client communications module [0150] 110 is the same as similarly named modules in clients 108.
  • The adapter interface module [0151] 116 enables the adapter 118 to communicate with clients 108.
  • The adapter synchronization module [0152] 152 is involved with synchronization operations between server 104 and clients 108.
  • The UI [0153] 148 enables users to interact with modules and functions of adapter 118.
  • The database module [0154] 150 controls access to databases associated with adapter 118. The database module 150 manages information needed for clients 108 to remain in sync with server 104. In some embodiments, the adapter 118 does not include the database module 150 or the UI 148 (i.e., in embodiments where the adapter 118 operates essentially as a pipe, as in some embodiments on Unix).
  • These and additional functions performed by modules of the adapter [0155] 118 are described herein.
  • Additional modules and features of embodiments of the invention are described below. [0156]
  • 1.4 Example Implementation Embodiments [0157]
  • FIG. 1B[0158] 1 illustrates a block diagram of a data processing unit 103A that can be used to implement the entities shown in FIGS. 1A and 1B. It is noted that the entities shown in FIGS. 1A and 1B may be implemented using any number of data processing units 103A, and the configuration actually used is implementation specific.
  • Data processing unit [0159] 103A may represent laptop computers, hand held computers, lap top computers, and/or any other type of data processing devices. Which type of data processing device used to implement entities shown in FIGS. 1A and 1B is implementation specific.
  • Data processing unit [0160] 103A includes a communication medium 103B (such as a bus, for example) to which other modules are attached.
  • Data processing unit [0161] 103A includes one or more processor(s) 103C, and a main memory 103D. Main memory 103D may be RAM, ROM, or any other memory type, or combinations thereof.
  • Data processing unit [0162] 103A may include secondary storage devices 103E, such as but not limited to hard drives 103F or computer program product interfaces 103G. Computer program product interfaces 103G are devices that access objects (such as information and/or software) stored in computer program products 103. Examples of computer program product interfaces 103G include, but are not limited to, floppy drives, ZIP™ drives, JAZ™ drives, optical storage devices, etc. Examples of computer program products 103H include, but are not limited to, floppy disks, ZIP™ and JAZ™ disks, memory sticks, memory cards, or any other medium on which objects may be stored.
  • The computer program products [0163] 103H include computer useable mediums in which objects may be stored, such as but not limited to optical mediums, magnetic mediums, etc.
  • Control logic or software may be stored in main memory [0164] 103D, secondary storage device(s) 103E, and/or computer program products 103H.
  • More generally, the term “computer program product” refers to any device in which control logic (software) is stored, so in this context a computer program product could be any memory device having control logic stored therein. The invention is directed to computer program products having stored therein software that enables a computer/processor to perform functions of the invention as described herein. [0165]
  • The data processing unit [0166] 103A may also include an interface 103J which may receive objects (such as data, applications, software, images, etc.) from external entities 103N via any communication mediums including wired and wireless communication mediums. In such cases, the objects 103L are transported between external entities 103N and interface 103J via signals 103K, 103M. In other words, such signals 103K, 103M include or represent control logic for enabling a processor or computer to perform functions of the invention. According to embodiments of the invention, such signals 103K, 103M are also considered to be computer program products, and the invention is directed to such computer program products.
  • 2. A Cross-Platform Browser and Cleint/Server Software Innovation for Mobile Devices [0167]
  • As described above, the technology uses a cross-platform strategy for serving and obtaining content requests on and across platforms and processors available to mobile devices. In some embodiments, the client enables desktop personal computer (PC) functionality on mobile devices. For example, the client can support dynamic hypertext mark-up language (DHTML) on mobile devices; it can support device-side interpretation of JavaScript™; and it can provide secure client/secure protocol/secure server interaction. It is noted that these examples are mentioned for illustrative purposes only, and are not limiting. Addition functions and capabilities are within the scope and spirit of the present invention, as will be appreciated by persons skilled in the relevant art(s) based on the teachings contained herein. [0168]
  • Additionally, the client [0169] 108 of the invention enables per channel (and/or per page) username and password authentication for transactions (e.g. in e-commerce applications and/or channels), digital notarization, content hold and deliver technology in connected and disconnected modes, and bookmarks. Furthermore, the clients 108 (i.e., client 108A and 108B) of the invention enable support for multiple protocols such as mailto and dialto interfaces, and DHTML. It is noted that these examples are mentioned for illustrative purposes only, and are not limiting. The invention is applicable to other protocols, as will be appreciated by persons skilled in the relevant art(s) based on the teachings contained herein.
  • In an embodiment, the client [0170] 108 of the invention integrates with other mobile device applications through methods such as but not limited to: cut and paste, domain integration of Find and/or Search methods, and mobile device communication between on-device applications and their separate tables of data. For example, the client 108 of the invention can invoke a vector graphics display or a word processor or spreadsheet file synced to the device. In one embodiment, these features correspond and extend the functionality of pluggable MIME types on server 104.
  • In embodiments, the client [0171] 108 is designed to support the additional Internet document standards: HTML 4.0, XHTML 1.0, CSS (Cascading Style Sheets), and the W3C DOM (Document Object Model). It is noted that these examples are mentioned for illustrative purposes only, and are not limiting. The invention is applicable to other standards, as will be appreciated by persons skilled in the relevant art(s) based on the teachings contained herein.
  • Referring to FIG. 2A, a block diagram, illustrating additional modules according to an embodiment of the invention, is shown. [0172]
  • Server [0173] 104 can include parser module 201A, layout module 201B, and/or proxy rendering module 201C. Modules 201A-201C can be implemented in server 104 alone or in combination with other elements or modules, such as in combination with clients (such functionality can also be performed completely by clients). It is noted that the functionality associated with modules may vary from implementation to implementation. The specific functionality and implementation described herein represent an example embodiment of the invention. Other embodiments will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein.
  • Also, implementations may employ combinations of the above modules, and/or employ the functionalities of the above modules as sub-modules to other modules of server [0174] 104, as will be appreciated by persons skilled in the relevant art(s).
  • In one embodiment, parser module [0175] 201A reads the objects on a page, such as a Web page. The parser module 201A separates out the description of each object on the page and generates a tree of objects based on their descriptions and the inherent relationship defined by the descriptions. In one embodiment, the tree of objects is compatible with the W3C DOM. Thus, in the case of HTML, the Web page is a description of content objects using tags, attributes, and styles. In the case of WML, the page is a description of content object using binary data.
  • In one embodiment, layout module [0176] 201B maps the parsed objects of a page and determines how the objects can be positioned and sized (or laid out) in order to provide a page with similar substance on the mobile device to which it is going to be transmitted. As with the other embodiments of the layout module described herein, the layout module 201B receives display, font color, and other device configuration information from the proxy render module 201C.
  • In a server-side layout embodiment, layout module [0177] 201B receives the display configuration of the mobile device from proxy render module 201C. Proxy render module 201C provides server 104 with the functionality of layout and rendering module 134 (in this case, either of modules 134A or 134B) for any number of clients 108. In one embodiment, the proxy render module 201C provides configuration information from a database, which stores previously obtained configuration information. In embodiments described herein, the server 104 receives the configuration information from the client 108. For example, server 104 receives the configuration information from layout and rendering module 134. From this information, server 104 is able to operate proxy render module 201C accordingly and provide data in the proper format. For example, in one embodiment, the proxy render module 201C is able to produce byte code in the form of a content stream compatible with the display hardware of device 106.
  • As such, proxy rendering module [0178] 201C determines the display capabilities of the device 106 to which the content stream is going to be transmitted. Furthermore, in one embodiment, proxy rendering module 201C determines information about how particular objects can appear (i.e., are positioned) on the display of a mobile device from device information stored in database module 126, rather than for a specific device 106 from information provided by client 108.
  • Furthermore, the functionality of these modules can be implemented on clients [0179] 108. For example, the rendering functionality of layout and rendering module 134 can provide the configuration information directly to the layout functionality of the same module. In embodiments, modules implemented on the client 108 are designed to operate on relatively small computers and/or mobile devices such as those described herein as well as those similarly designed. The combination of functionalities in one module 134 is for illustrative purposes. The combination may be separated and implemented in two separate modules as discussed with respect to server 104 above. These implementations are discussed in more detail below.
  • Referring to FIG. 2B[0180] 1, a block diagram, illustrating an additional module according to an embodiment of the invention, is shown.
  • Client [0181] 108A can include client parser module 202A. Client parser module 202A provides functionality similar to parser module 201A as described herein.
  • Referring to FIG. 2B[0182] 2, a block diagram, illustrating additional modules according to an embodiment of the invention, is shown.
  • Client [0183] 108B can include client parser module 202B and client interface module 112B. Client parser module 202B provides functionality similar to parser module 201A as described herein. Client interface module 112B is capable of connecting with providers 128 via communication medium 120E. Providers 128, as described herein, are content providers, such as Web sites. Communications medium 120E may be implemented to augment the connection with server 104 via adapter 118. For example, communications medium 120E, as shown, could connect directly to providers 128 via a wireless link in order to obtain updated content from providers 128 or to transmit data to providers 128.
  • In one embodiment, the parsing functionality added to client [0184] 108 via client parser modules 202A and 202B allows clients 108 to obtain content directly from providers 128 without server 104 transformation. Some embodiments of this distribution of functionality is discussed below with respect to FIG. 2C.
  • Referring to FIG. 2C, a diagram, illustrating some processing components according to embodiments of the invention, is shown. [0185]
  • Content [0186] 203A from a page in the form of objects is parsed by parser module 203B, laid out by layout module 203C, rendered by rendering module 203D, and sent to mobile devices for display in the form of pixel data 203E. These objects can include but are not limited to tags, attributes, and style information.
  • The modules [0187] 203B, 203C, and 203D are similar to the modules discussed in FIGS. 2A, 2B1, and 2B2. FIG. 2C illustrates the feature of the invention where the method, system and computer program product can be configured such that the operations of modules can be performed on server 104 and/or clients 108, as well as on adapter 118 as well as combinations thereof.
  • In the examples of FIG. 2C, the operational processes of each of modules [0188] 203B, 203C, and 203D are delineated by marker 203F for parser module 203B. Similarly, marker 203G delineates the operational processes of layout module 203C. Marker 203H shows the operational processes for rendering module 203D.
  • In embodiments of the invention, the operational processes of these modules, as well as the modules themselves, can be implemented on either or both the server [0189] 104 or the client 108 (or adapter 118). This flexibility allows the invention to optimize the transformation and delivery of content to mobile devices based on the capabilities of the devices and/or requirements of users.
  • Line [0190] 203I illustrates an example implementation where modules 203B and 203C are operating on server 104 to perform the functions of parsing and layout. The asterisk of line 203I shows the transition to client 108 (or adapter 118) and thus the operations of module 203D are performed on client 108.
  • Similarly, lines [0191] 203J, 203K, and 203L illustrate other possible apportioning of the operational tasks. The markers between the arrows of lines 203J, 203K, and 203L similarly showing the transition from one of the server 104 to client 108 (and/or adapter 118).
  • In additional embodiments, modules on both server [0192] 104 and client 108 (and adapter 118) can operate in parallel or series on the objects of content 203A.
  • Referring to FIG. 2D[0193] 1, an example flowchart 204 relating to structuring interactive content, according to an embodiment of the invention, is shown.
  • In step [0194] 204A, server 104 receives a request for pages. In one embodiment, the client 108 sends the request.
  • In step [0195] 204B, server 104 receives mobile device and client information describing the capabilities of the client 108 and the device 106. In one embodiment, client 108 sends information regarding the display and memory specifications of the mobile device upon which it is operating.
  • In step [0196] 204C, server 104 parses the pages into a mutable document of content according to the device and client information of step 204B. In one embodiment, parser module 201A parses the pages into discrete objects.
  • In step [0197] 204D, server 104 determines the rendering parameters of the client and mobile device according to the information obtained in step 204B. In one embodiment, proxy rendering module 201C provides the rendering parameters of the client and mobile device.
  • In step [0198] 204E, server 104 lays out the document content according to the rendering parameters determined in step 204D. In one embodiment, the parsed objects of a page are assembled and formatted such that the page displayed by the client on the mobile device has the same functional display or presentation as on any other device. In an embodiment, layout module 201B provides common layout services for the server 104. Similarly, layout and rendering module 134A of FIG. 1A provides these services on client 108A.
  • In step [0199] 204F, server 104 determines the document table and document content to be sent to client 108 so that the client 108 can use the content of the page(s). The structure and format of the document table and document content (according to embodiments) are discussed below.
  • In step [0200] 204G, server 104 compresses the document content, preferably on a discrete object-by-object basis (although other embodiments are possible). For example, the discrete objects obtained from the parsing of step 204C are compressed individually in step 204G.
  • In step [0201] 204H, server 104 encrypts the document content, preferably on a discrete object-by-object basis. For example, the discrete objects obtained from the parsing of step 204C are encrypted individually in step 204H.
  • In step [0202] 204I, server 104 serializes the document content according to the discrete basis. For example, the document content is placed in ordered blocks or sections. In one embodiment, the discrete basis may prioritize index or home pages and place them in places in the serialized chain of objects so that they may be readily recalled.
  • In step [0203] 204J, server 104 serializes the document attributes related to the document content according to the discrete basis. In one embodiment, the document attributes are placed in a similar order as the document objects in step 204I. In another embodiment, the document attributes are serialized based on the type of objects they respectively identify.
  • In step [0204] 204K, server 104 transmits the serialized document to client 108A and/or adapter 118 for delivery to client 108B. In one embodiment, the serialized document is a content stream transmitted to the device for client 108. The serialized document can provide an optimized format for delivering content to mobile devices that may not be designed to accommodate the relatively large file formats, which PCs are used to handling.
  • In the above description, server [0205] 104 is discussed as performing the operations of flowcharts 204. This is just one embodiment of the invention. Variations of this embodiment will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. For example, client 108 can perform some or all of the operations of flowchart 204, as discussed below.
  • Referring to FIG. 2D[0206] 2, an example flowchart 204M relating to structuring interactive content according to another embodiment of the invention is shown.
  • In step [0207] 204N, client 108 (as discussed above, client 108 is used to refer generically to client 108A and/or client 108B, unless stated otherwise) sends a request for pages.
  • In step [0208] 204Q, client 108 receives the requested pages. In one embodiment, client 108B receives the pages directly from providers 128, as shown in FIG. 2B2. In another embodiment, client 108 receives the requested pages from the server 104.
  • In step [0209] 204R, client 108 parses the pages into a mutable document of content. As described above, the mutable document allows for better access and storage for the client.
  • In step [0210] 204S, client 108 determines the rendering parameters according to the local render module, such as layout and rendering module 134.
  • In step [0211] 204T, client 108 lays out the document of content according to the rendering parameters determined by the local render module, such as layout and rendering module 134. Such parameters include, for example, colors supported, device screen size, font characteristics, etc.
  • In step [0212] 204U, client 108 displays the data on the screen. In one embodiment, the render module of client 108 puts the pixel data on the screen.
  • For example, the client communications module [0213] 110A receives the pages from server 104. Client parser module 202A parses the pages. Layout and rendering module 134A determines the rendering and layout parameters and forwards the pixel data to the screen. Other examples and embodiments are discussed in detail below.
  • 2.1 Serialized Document Model [0214]
  • Similar to the PODS described herein, the document (data object) assembled through the steps of flowcharts [0215] 204 and 204M includes a structure that is advantageous for mobile devices. The document object models (DOM) of an embodiment of the invention supports Copy-On-Write which is usually only implemented in hardware. This enables the creation of discretely compressed read-only documents (for example, the pre-processed content stream as described herein) that can be modified and saved and then loaded and modified incrementally on a discrete basis.
  • This embodiment allocates data in its final form. In an embodiment, read-only data in the content stream is, as best can be achieved, in its final, usable form. The data does not have to be duplicated for use as with other types of models. This aspect of the invention is important given the relatively limited resources of mobile devices. [0216]
  • 2.2 Memory Allocation [0217]
  • Furthermore, this model has a tight memory allocation scheme. In an embodiment, memory is allocated in Pools and Arenas that are scoped to the lifetime of the object being allocated. For example, documents have a memory scope. When an object whose lifetime is that of a document is allocated, it is allocated from the owner document's memory scope. [0218]
  • When the document is destroyed, the associated memory scope can be freed immediately. Objects that will exist for the life of a memory scope will be allocated from the scope Arena (in an embodiment, arena allocated objects cannot be individually freed). In an embodiment, objects whose lifetimes are more volatile will be allocated from the scope pool (where they can be later freed). This allocation is but an example and others can be implemented depending on the device's memory structure (and also possibly depending on other factors) as one skilled in the relevant art would recognize. As in the above example, when both arena and pool memory types exist, content can be stored in a read-only (arena) and/or in a writeable (pool). Further embodiments using this type of memory allocation are discussed below. [0219]
  • Referring to FIG. 2E, a diagram illustrating an example of content formatting according to an embodiment of the invention is shown. In this embodiment, an example button is shown within the document [0220] 205A. The button object includes a header 205B and the parameter information stored as data 205C. Header 205B can include type information which provides a mechanism whereby there is a pointer or pointers to the type of functions which operate on the data 205C.
  • Referring to FIG. 2G, a diagram illustrating an object model related to those shown in FIGS. [0221] 2F1 and 2F2 is shown. FIG. 2G shows a button object 207A that includes object pointers 207K. Object pointers 207K comprise a vtable pointer 207B and a data object 207C. Vtable pointer 207B points to a vtable 207D that contains function pointers 207F for accessing instance methods 207H.
  • Button object [0222] 207A and data 207C can be placed in writeable memory. Qualitative data can be read and written (thus, modified) by instance methods 207H, which are designed to read and manipulate data 207C.
  • There are drawbacks to this object model. They include, but are not limited to: [0223]
  • 1) Data [0224] 207C is in writeable memory. Data 207C is relatively large. If data 207C is first available in read-only form, then it must first be copied into writeable memory.
  • 2) Writeable memory is often scarce on mobile devices (as well as other devices). [0225]
  • 3) Data [0226] 207C cannot easily be maintained in compressed form as the size of data 207C will change as it is modified. This requires additional writeable memory.
  • Additionally, the lack of a document table effectively means that any changes to the data [0227] 207C or the type information in header 207B requires a change to the vtable 207D which is used to operate on data 207C. These changes have to be made globally so that the entire document is recreated.
  • FIGS. [0228] 2F1 and 2F2 illustrate content instantiation architectures according to embodiments of the invention.
  • Referring to FIG. 2F[0229] 2, a diagram illustrating the content instantiation architecture according to an embodiment of the invention is shown. FIG. 2F2 differs from FIG. 2G in that data 206K2 is separated from object 206A. The addition of attribute pointer 206C, which points to data 206K2, serves as a link so that changes do not have to be made globally as in FIG. 2G.
  • Referring to FIG. 2F[0230] 1, a diagram illustrating the content instantiation architecture according to an embodiment of the invention is shown. FIG. 2F1 is differs from FIG. 2F2 in that data 206K can be read only and compressed. Instance methods 206H are designed to read the compressed data.
  • The architectures of FIGS. [0231] 2F1 and 2F2 have advantages over the architecture of FIG. 2G. Unlike the architecture of FIG. 2G, data does not have to be decompressed or copied to writeable memory for initial use. Data can be read, and/or displayed immediately. The architectures of FIGS. 2F1 and 2F2 are very efficient for mobile devices (as well as other devices), which can have relatively limited memory or processing capabilities, because they use compressed read-only data. Additionally, the architectures of FIGS. 2F1 and 2F2 are useful for applications where memory and processing requirements need to be optimized, as well as for other applications as will be appreciated by persons skilled in the relevant art(s) based on the teachings contained herein.
  • Referring to FIG. 2F[0232] 1, for example, document table 206A provides two pointers: Vtable pointer 206B and attribute pointer 206C. Vtable pointer 206B points to a vtable 206D which includes header 206F and function pointers 206G. Header 206F includes information pertaining to the class and type of functions being called. Function pointers 206G includes global, user, and low-level function pointers that provide access to the instance methods 206H of functions 206E.
  • Attribute pointer [0233] 206C points to the specific object in the content stream 206I similar to that discussed with respect to FIG. 2E. Header 206J and data 206K provide specific information about how to perform the functions pointed to in the vtable.
  • The use of document table [0234] 206A allows the entire document to be incrementally altered as may be required without having to totally restructure the document.
  • It is noted that the data [0235] 206K can be compressed. Content stream 206I, header 206J, and data 206K can be in read-only memory. Instance methods 206H can be designed to interpret the compressed data 206K so that instance methods 206H can read, display and process data 206K properly.
  • According to embodiments of the invention, modifications to data [0236] 206K are possible, but any modified data 206K objects are stored in writeable memory. Attribute pointer 206C is updated to reflect the modification so that future use of the specific data 206K object is directed to the modified object. The embodiments of FIGS. 2F1 and 2F2 therefore provide for relatively less use of writeable memory on the mobile device.
  • Software Modification on Write Method and Example [0237]
  • The embodiments of FIGS. [0238] 2F1 and 2F2 offer important advantages to browsers. For example, mobile devices typically are designed around several different operating systems and/or hardware standards. The use of a client that enhances access helps to assure compatibility. Furthermore, the general features of mobile devices are relatively limited compared to their PC counterparts. As such, mobile devices benefit from enhanced content storage, retrieval and modification techniques.
  • In an embodiment, data can be transformed as shown in FIGS. [0239] 2F1 and 2F2. In an example embodiment, the objects 206A in FIG. 2F1 and 2F2 share the same form, i.e., a compressed, read-only form. The read-only objects 206A of FIG. 2F1 can be transformed by instance method 206H into the writeable form shown in FIG. 2F2. In one embodiment, when instance method 206H is called, a software exception similar to a hardware exception occurs.
  • Referring to FIG. 2F[0240] 3, a flowchart 206P, relating to an enhanced data modification process according to an embodiment of the invention, is shown. For illustrative purposes, FIG. 2F3 is described with reference to FIG. 2F1. However, the operations of FIG. 2F3 are applicable to other embodiments, such as the example embodiment of FIG. 2F2.
  • In an embodiment, control module [0241] 142 performs the steps of routine 206P.
  • In step [0242] 206Q, client 108 accesses an object pointer 206L in a document (object) table 206A. The object pointer is an element of the document table, which in one embodiment, is placed at the beginning of the content stream.
  • In step [0243] 206R, client 108 accesses a vtable pointer 206B for access to the vtable's function pointers 206G.
  • In step [0244] 206S, client 108 accesses an attribute pointer 206C for access to data in a content stream 206I.
  • In step [0245] 206T, client 108 uses the vtable pointer 206B to read function pointers 206G for access to instance methods 206H.
  • In step [0246] 206U, client 108 reads the content stream 206I for access to data 206K pointed to by attribute pointer 206C.
  • In step [0247] 206V, client 108 determines the requirements for the data 206K. In one embodiment, client 108 determines the amount of writeable memory that the data 206K will take up.
  • In step [0248] 206W, client 108 allocates writeable memory according to the requirements determined in step 206V.
  • In step [0249] 206X, client 108 decompresses and copies the data 206K into writeable memory. In one embodiment, the client 108 access portions of hardware and operating system software of device 106 to decompress and copy the decompressed data. In another embodiment, the client 108 internalizes the decompression and copying step.
  • In step [0250] 206Y, client 108 updates attribute pointer 206C to point to the data 206K in writeable memory.
  • In step [0251] 206Z, client 108 updates vtable pointer 206B to point to instance methods 206H for non-compressed, writeable data.
  • For example, referring also to FIG. 2F[0252] 2, a routine can allocate writeable memory for data 206K2. It decompresses the data 206K and copies the data 206K into writeable memory, shown as data 206K2. The method then changes the attribute pointer 206C to point to data 206K2. It also changes the vtable pointer 206B to point to the non-compressed, writeable instance functions vtable 206D2.
  • With the modification complete, the instance method [0253] 206H calls an equivalent instance method 206H2 to actually perform the required write operation of the data 206K2.
  • A feature of this embodiment is that the operations of FIGS. [0254] 2F1 and 2F2 occur invisibly (transparently) to the application calling the pointers. An additional feature is that the operation is performed once on a per object basis. Once performed, the object stays in writeable memory for the life of the document(s)/object(s).
  • A result of these embodiments is that object pointer [0255] 206L is preserved. This is important as many other objects may already have a reference to object 206A via object pointer 206L.
  • 2.3 Detailed Object Model Embodiments [0256]
  • In an example application of the embodiment of FIG. 2F[0257] 1, every object in the tree has an 8 byte (two pointers) entry in the Document Object Table (DOT). The entry consists of a pointer to the object's class vtable (table of function pointers for instance methods), and a pointer to the object's data. In the case of content stream formatted documents, the object's data pointer points into the content stream. It is noted that the invention is not limited to this example embodiment.
  • Inter-object references are via Object Identifiers (OID), which are unique 16 bit identifiers for each object in the document. Unlike pointers, OIDs support relocation and transmission between server and client. Entries in the DOT are ordered in OID order. That is, the OID is also the index into the DOT. Thus, an OID can quickly be translated into an Object pointer (which is desirable at runtime) by performing array arithmetic (object =&dot[oid]). By using OIDs and pointers in the DOT approach, a number of advantages are achieved: relocatability and transmittability from the OIDs, and ease of use, and a rational runtime model from the Object model. [0258]
  • The DOT is created when the document is being loaded, as shown in FIG. 2F[0259] 1 and 2F2. An example scenario is as follows: The content stream is interrogated to see how many objects are in the document. A DOT large enough to accommodate that number of objects is created. An application quickly scans through the content stream, which has objects in OID order. For each object the application checks the type, ensures that the class and vtable 206D for that type is created, writes the vtable pointer 206B in the DOT entry, then writes in the data pointer 206C, pointing back to the content stream data 206K. Then, the application skips to the next object in content stream (each entry has a length prefix stored in header 206J). When the application is done it has a fully populated DOT, with a number of objects that are writeable. If more objects are added to the document (via scripting requests), they are dynamically added to the end of the DOT in the form of FIG. 2F2, for example.
  • Like the PODS object model, the invention's Object Model, while implemented in C, is compatible with C++. Objects can be represented as abstract classes (pure virtual member functions), where the base class has no data slots. On most C++ compilers, this will guarantee that the C++ vtable entry will be forced to offset zero in the class. The benefit: both C [i.e., ADOM setValue(object, “xxx”)] and C++ [i.e., object->setValue(“xxx”);] bindings (APIs) to the same object are provided. [0260]
  • Referring to FIG. 2H, a diagram illustrating content structure according to an embodiment of the invention is shown. [0261]
  • Document stream [0262] 208A illustrates at a high level the structure of the document that includes header 208B, string table 208C, and object table 208D. Header 208B includes the document table information, which can include object size, number of objects and string sizes. String table 208C includes string identifiers (SIDs) 208E that are ordered based on the SID in a manner similar to OIDs, as discussed above. String identifiers 208E include lists of word identifiers 208F, which are ordered word tables 208G. Each word table contains characters 208H that are represented by a certain code 208I.
  • The structure embodied in stream [0263] 208A provides the compressed and ordered nature described herein. Object table 208D includes the type and size and other attribute information for each object in the document as in FIG. 2E. String objects in these objects are string identifiers referring to 208C.
  • 2.4 CSS Style Sheet Technology on Mobile Devices [0264]
  • Style Sheets represent a mechanism for setting and holding style attributes. HTML elements have a number of attributes that are stylistic in nature (dimensions, colors, font information, list bullet styles, etc.). Style Sheets are just a formalized scheme of setting, getting, and most importantly sharing these attributes. An advantage of Style Sheets is that they make it very easy to make global or semi global stylistic changes to a document. [0265]
  • For example, if one wants all the image borders to be 4 pixels wide, one can do that easily in one place. An advantage of supporting styles is it will make it easier for the content developer to share HTML between desktop and mobile devices—without recoding the HTML. [0266]
  • Also, style sheets represent a useful abstraction for attribute information. In an embodiment, the HTML Element super class of HTML/DOM is aware of style sheets. HTML Element provides the interface to get all attribute information for each object in the document. In one embodiment, HTML Element obtains most of this information from the style sheet that is associated with the object. As style sheets tend to be shared by like objects, the memory hit is not substantial. [0267]
  • FIGS. [0268] 2I1 and 2I2 demonstrate the effect of example style sheets.
  • In FIGS. [0269] 2I1 and 2I2, note the borders around Product List. The top and left borders are lighter, while the bottom and right borders are darker than the background—creating a stand-out 3D effect.
  • The tree is made up of a three element list, where each item is a title label and an embedded list. The embedded list is hidden by setting the top level display property to none, then shown again by setting the property to block. [0270]
  • FIG. 2J demonstrates floating images, where the text flows around the image. The example of FIG. 2J may represent a page created as a HTML source file, compiled on the server, and loaded onto the device for viewing. [0271]
  • 2.5 Overview to the Architecture of the Technology [0272]
  • According to an embodiment, the architecture of the invention is designed so that a majority of the code is in the cross platform core pieces. A component that cannot be easily made cross platform is graphics code that draws bits on the screen. According to an embodiment, an approach is to break this component out as the Render abstraction, define a strict interface between Render and the rest of the code, and then utilize platform specific graphics subsystems capable of plugging back into the rest of the system. [0273]
  • The Draw code module deals with the semantic and programmatic level of graphics, leaving the Render module with only the responsibility of putting bits on the screen, such as bits in the form of strings, rectangles, border frames, etc. By keeping the abstraction level low, more functionality is maintained in the cross platform code, leaving the platform specific Render engine author with less code to write and maintain. [0274]
  • 2.6 Classes and Relationships within the Technology [0275]
  • The relationship between the render modules and the rest of the system is defined by a render interface. In one embodiment, an example header file can be implemented. Such an example header file can includes one or more of three interfaces: ARenderMgr, ADrawCtx, and ARenderFont. [0276]
  • In one embodiment, ARenderMgr is the render engine. In a given executable based on this technology, one can have 0, 1, or N objects that implement an ARenderMgr interface. In order to do a layout or draw on a DOM tree, one must have an ARenderMgr instance (actually one needs a DrawCtx which is created by a RenderMgr object—see the discussion below). The render engine for a given platform's graphics subsystem is created by a factory method on the object subclass implemented by that platform. [0277]
  • In one embodiment, ARenderFont is a font in the world of this technology. ARenderFont basically defines a logical abstraction of the kinds of questions the core code (especially layout) needs to ask of a font, without locking down to the (very) platform specific details of any platform's font subsystem. ARenderFont only defines font metrics, such as “in one font, how many pixels wide is this string,” but most platform specific render engines may sub class and add drawing behavior to the ARenderFont class. [0278]
  • In one embodiment, ADrawCtx is a drawing context and includes many rendering and drawing capabilities. ADrawCtx provides methods for getting bits on the screen (drawstring( ), drawRectangle( ), etc), it provides the abstraction for the logical drawing surface (the Window, Form, or Port) that drawing occurs on, and also acts as memo pad for coordinate information during drawing. [0279]
  • 2.7 Example Features [0280]
  • Cross-platform Construction, Layout, and Rendering Technology for DOM Application Browsers or Viewers for Mobile Devices and DHTML Layout and Cascading Style Sheets [0281]
  • According to an embodiment of the invention, the cross-platform construction, layout, and rendering technology first parses HTML and then constructs a document object model based on HTML tags. It then lays out those objects in the tree that represent those tags in their logical pattern relative to their parent and children including details such as an x/y location and width and height attributes. After the layout is complete, the invention serializes the data and transmits it to the client in the case of the client/server browser embodiment. [0282]
  • FIG. 2D[0283] 1 and 2D2 (described above) illustrate example diagrams showing an embodiment of the rendering of the client and/or server.
  • Rendering functionality can reside on device or on the server. All of the processes can be present on the server, leaving only the device specific reader to complete the pixelation of the objects, or all of the processes can be present on the device including the parser. Thus, in some embodiments, the device can receive HTML and parse it appropriately. [0284]
  • FIG. 2K illustrates an example construction, layout, rendering and cross-platform technology architecture according to embodiments of the invention (see also FIGS. [0285] 2D1 and 2D2).
  • The diagram [0286] 227 includes server 104 and device 106. As discussed above, content 227A in the form of HTML, CSS, wireless markup language (WML), or other format enters the system.
  • Parser module [0287] 227B receives the content and formats it into discrete objects. Parser 227B assembles the objects into DOM 227F. Here, DOM 227F is simply a placeholder for the content stream as it is being assembled. Layout module 227C reads configuration information from proxy render module 227E. Proxy render module 227E obtains this information from the device, shown here as device configuration 227D.
  • Once the content stream has been assembled, emitter and compressor module [0288] 227G forwards the content stream via communications medium 227H to client 108.
  • The client [0289] 108 receives the content stream in DOM 227L. Loader 227J forwards the content stream to render module 227M for display on screen 227N.
  • Additionally, client [0290] 108 can also include optional parser module 227I, and optional layout module 227K. In embodiments that include these modules, client 108 is capable of receiving content 227A and parsing it into a content stream. Furthermore, layout module 227K can provide the proper configuration information directly from the device on which it is operating.
  • In an embodiment, the above-described processes begin with a user account and device specific sync to server [0291] 104, where the server 104 preemptively gathers enough information to represent the requirements of device 106.
  • If the device is capable of layout (i.e., includes a layout and rendering module [0292] 134), then the server may sync to the device only the DOM in content stream format. Layout operations are then performed on the device for the document.
  • If the device does not have a layout module, or if the server is configured to perform the layout operations, then the server will layout the document and then sync the document content and layout information to the device. [0293]
  • Another feature of this embodiment is that HTML is sent to the server. There a parser communicates with the document object model that creates a collection of objects (including the ability to generate objects based on invalid HTML). From these objects, a tree of objects is generated that includes their layout attributes such as x/y coordinates and their width and height. This layout is based on a proxy of the device on the server. [0294]
  • Another feature is that the level of the technology that is synced or loaded to the device can be preemptively determined. The device, known or unknown to the server, will sync a proxy, or map, of the device requirements to the server. At the server, objects are rendered to the specifications of that proxied device before the device syncs. This involves parsing, rendering, and laying out of document objects using the proxy map of the device. [0295]
  • For example, suppose that a future device syncs to a current server. The invention enables the device to inform the server of enough information to represent its requirements. In other words, the device provides enough information to enable the server to create a proxy of the device. The server then proxy-renders the objects to the device based on the proxy of the device. Then, the server may send the parsed and laid out objects or the parsed only objects to the device. In the case of raw HTML being sent to the device, the server may not need to participate in the parsing process or other processes performed by the client. [0296]
  • FIG. 2L illustrates an example process where a future device is able to sync with a current server. The loader, layout, and rendering modules (as described above with respect to FIG. 2K) of the client employ an incremental and/or on-demand approach. To view the first page of the document, only the first few objects (those visible) are loaded from the content stream. Content stream layout and rendering operations stop after the visible set of objects has been handled. [0297]
  • On-device pages are not necessarily created in their entirety (although they can be). They may be viewed as instantiated objects as they are needed. The content stream is rendered based on the need for the elements on a page. Compressed (in content stream format) objects are instantiated based on deltas against a default set of attributes (such as found in HTML) coded into the client application. [0298]
  • For example, if a document sent to the device needs to be viewed, it is quickly rendered as a set of objects rather than as a rebuilt page of HTML. [0299]
  • In addition, if the page needs to change, the relevant objects are incrementally decompressed from the content stream as described above with respect to FIGS. [0300] 2F1 and 2F2. Thus, the decompressed versions of only the required objects are created. When a value in an attribute is changed by a user (for example, the name of a button is lengthened or a paragraph of text is added to the page), only the objects that must be changed are decompressed.
  • For each instance of these objects, there is a table of objects providing an efficient way of making a byte stream into a data model. The tables are heuristic tables for matching calls to data. The objects viewed are seen through the laid out objects. When the objects are changed, a duplicate is created or morphed from the original object or set of objects and thus expanded based on a set of deltas. The result is a fully rendered copy of the object that is now writeable. A key to this functionality is how small the viewable objects are (as they need to be on mobile devices) until they need to be writeable. They become writeable when they are uncompressed or inflated to a fully rendered version. [0301]
  • The document object table that enables the content stream to be rendered by the invention is variable and customizable. The table may map to a function that calls data as easily as it maps to tables of data as easily as it maps to strings of code. [0302]
  • Another feature is that of on-device HTML authoring. Rendered HTML and resources can be redrawn and the HTML can be sent back in a content stream via a sync for storage in a database or posting on a network, intranet, or Internet. [0303]
  • Another feature is that the proxy-rendered nature of the invention enables a sync process to “take-over” a device. The result may be a single function device with a browser or application lock that can only be reset by another sync to the server, based on new server preferences. This means the client in conjunction with the object renderer and via a sync or other “install” mechanism, can “take over” a device for a use as a single function/single application device. [0304]
  • 3.0 Server-Side Preparation of Data, HTML, and Other Network Resources and Objects for Ease-of-Use on Mobile Devices [0305]
  • 3.1 Server Cache Operations [0306]
  • As previously stated, in embodiments the invention uses server logic to optimize content for delivery on mobile devices. Server [0307] 104 also stores optimized content in a cache. The optimized content is based on the type of mobile device that requested the content. Thus, the invention stores device specific versions of content requested by mobile devices. For example, suppose a first Palm device requests document A from provider 128A. Provider 128A controls page caching using relative or absolute date-time stamps. Server 104 may optionally override the page caching from Provider 128A. Document A is retrieved from provider 128A and optimized by web synchronization module 124 for use on the first Palm device. The optimized content is then cached for the first Palm device. Next a Windows CE device requests document A from provider 128A. Document A is retrieved from provider 128A, optimized for use by the Windows CE device, and cached for the Windows CE device. If, sometime later, a second Palm device with identical or similar characteristics (depending on the implementation) as the first Palm device requests document A from provider 128A, document A, specific to the first Palm device, is immediately retrieved from the cache. The web synchronization module 124 does not have to retrieve document A from provider 128A for the second Palm device. As the number of users increases, the cache hit ratio increases, resulting in fewer fetches from providers 128. As the need for web synchronization module 124 to retrieve an object from provider 128 decreases, server bandwidth requirements also decrease.
  • FIG. 3A is a flow diagram representing an exemplary server cache operation of transformed content. The process begins with step [0308] 302. In step 302, a data object request is made by a mobile device. The mobile device may be, but is not limited to, any mobile device listed in Table 2. The process proceeds to step 304.
  • In step [0309] 304, web synchronization module 124 checks to see if the data object specific or applicable to the requesting mobile device is found in the cache associated with the server. If the data object specific or applicable to the requesting mobile device is found in the cache and is still valid, the process proceeds to step 306.
  • In step [0310] 306, web synchronization module 124 retrieves the optimized data object from cache. The process then proceeds to step 314.
  • Returning to step [0311] 304, if the data object specific or applicable to the requesting mobile device is not found in the cache or is no longer valid, the process proceeds to step 308.
  • In step [0312] 308, web synchronization module 124 retrieves the data object from provider 128. The retrieved data object may include a date-time stamp and/or other information indicating when the data object will expire. The process then proceeds to step 310.
  • In step [0313] 310, web synchronization module 124 transforms the data object to a form suitable for use and/or display on the requesting mobile device. For example, an address book entry will differ for Palm and Windows CE devices. The process then proceeds to step 312.
  • In step [0314] 312, the transformed data object is stored in the cache with device specific information, along with information on how long the data object can remain in the cache (such information may include the date-time stamp information of step 308). Note that the transformed data object is only stored in the cache if information retrieved from provider 128A indicates that the data object is cacheable or if server 104 is set to override the information from provider 128A. The process then proceeds to step 314.
  • In step [0315] 314, the transformed data object is sent to the requesting mobile device.
  • 3.1.1 Special Case of Optimization for Mobile Devices: [0316]
  • Negative Caching of Compressed Error Messages In one embodiment, negative caching is implemented. Negative caching involves caching errors that result when web synchronization module [0317] 124 is unable to retrieve the requested data object from provider 128. This eliminates the need to subsequently access the provider 128. For example, if provider 128 is down, negative caching may lessen the number of negative hits that would otherwise result if attempts were made to retrieve data objects from provider 128. When web synchronization module 124 subsequently checks the cache for the irretrievable requested data, it will see the cached error message and will make no attempt to retrieve the data from provider 128.
  • For example, suppose device A requests a page. The web synchronization module [0318] 124 requests the page from provider 128. However, when web synchronization module 124 requests the page from provider 128, an error is returned indicating that the page is unavailable. Web synchronization module 124 caches the error, setting configurable expiration information. Later, another device (device B) with characteristics similar to device A requests the same page. Web synchronization module 124 will see the cached error (assuming that this cached error is still valid) indicating that the page is irretrievable. Therefore, web synchronization module 124 will not have to make an attempt to retrieve the page from provider 128.
  • FIG. 3B is an exemplary flow diagram representing negative caching of error messages. The process begins with step [0319] 322. In step 322, a data object request is made by a mobile device. The process proceeds to step 324.
  • In step [0320] 324, web synchronization module 124 checks to see if the data object specific or applicable to the requesting mobile device is found in the cache associated with the server. If the data object specific or applicable to the requesting mobile device is found in the cache, the process proceeds to step 326.
  • In step [0321] 326, web synchronization module 124 retrieves the optimized data object from the cache. The process then proceeds to step 336.
  • Returning to step [0322] 324, if the data object specific or applicable to the requesting mobile device is not found in the cache, the process proceeds to step 328.
  • In step [0323] 328, web synchronization module 124 attempts to retrieve the data object from provider 128. The retrieved data object may include a date-time stamp and/or other information indicating when the data object will expire. The process then proceeds to decision step 330.
  • In decision step [0324] 330, it is determined whether an error indicating that the requested data object was irretrievable occurred as a result of step 328. If an error message occurred, the process proceeds to step 333. If no error message occurred, the process proceeds to step 332.
  • In step [0325] 332, web synchronization module 124 transforms the retrieved data object to a form suitable for use and/or display on the requesting mobile device. The process then proceeds to step 334.
  • Returning to decision step [0326] 330, if an error message occurred, web synchronization module 124, in step 333, transforms the error message to a form suitable for display on the requesting mobile device. The process then proceeds to step 334.
  • In step [0327] 334, the transformed data object or the error message is stored in the cache with device specific information, which may include an indication of how long such information may be cached (as explained above). Note that the transformed data object or error message is only stored in the cache if information retrieved from provider 128A indicates that the data object is cacheable or if server 104 is set to override the information from provider 128A. Server 104 may provide special overrides for negative caching of error messages. The process then proceeds to step 336.
  • In step [0328] 336, the transformed data object or the error message is sent to the mobile device.
  • 3.1.2 Stochastic Cache Expiration Algorithm [0329]
  • Normally, when a large group of users sync daily, at least some of the users are syncing the same version of a set of pages all of which will expire at the same time. For example, if server [0330] 104 has a million users with a page on each user's device that expires at 12 midnight on Sep. 9, 2000, every single device connected to server 104 at that moment (which in a wireless world may be all of the mobile devices) will request server 104 to provide those pages. An example diagram illustrating all hits on a server occurring at the same time is shown in FIG. 3C for the above example. As seen in FIG. 3C, the diagram shows all of the hits on server 104 occurring at once, that is, 12 midnight. This causes slow serving of new pages to all devices and puts excess stress on server 104 and provider 128.
  • To prevent the above scenario from occurring, an embodiment of the invention randomizes the expiration of the objects. This results in fast serving of new objects to all devices and puts less stress on server [0331] 104 and provider 128.
  • Server [0332] 104 sets a freshness lifetime for each object (or, in some embodiments, for groups of objects) stored in the cache. If the age of an object stored in the cache is within some % of the freshness lifetime (e.g. if it is about to expire), otherwise known as Server FL or server freshness lifetime, then server 104 will vary the expiration of the cached object to determine whether the cached object should expire. The % of the freshness lifetime is usually set at the startup of server 104 using server preferences set by an administrator. Alternatively, the % of the freshness lifetime may be configurable.
  • Server [0333] 104 uses freshness lifetime for determining whether or not to modify the expiration of the cached object. Server 104 determines whether the cached object is close to expiring and then in an embodiment it uses a stochastic function to determine whether or not to expire the cached objects. The stochastic function is used if the current age of the cached object is within some percentage of the freshness lifetime.
  • FIG. 3D is an example flow diagram representing a method for randomizing the expiration of objects set to expire at the same time according to an embodiment of the invention. The process is performed for any given object in the cache (called the cached object). The process begins with step [0334] 342. In step 342, server 104 determines the cached object's freshness lifetime. The cached object's freshness lifetime (FL) is the time of expiration (Texp) of the cached object minus the time in which the object was placed in the cache (Tin-cache). In embodiments, the time of expiration is given when the object is retrieved from the provider 128. If the time of expiration is not given, server 104 may set a time of expiration for the object, or this may be configurable. The cached object's freshness lifetime is:
  • Object's FL=Texp−Tin-cache  (1)
  • The process then proceeds to step [0335] 344.
  • In step [0336] 344, server 104 determines the cached object's age. The cached object's age is the total time that the object has been stored in the cache. The cached object's age is
  • Object's Age=Tnow−Tin-cache  (2)
  • where Tnow is the current time. The process then proceeds to step [0337] 346.
  • In step [0338] 346, server 104 determines the % of the object's freshness lifetime. The % of the object's freshness lifetime is the object's age divided by the object's freshness lifetime. The % of the object's freshness lifetime is:
  • % of the Object's FL=Object's Age/Object's FL  (3)
  • The process then proceeds to decision step [0339] 348.
  • In decision step [0340] 348, it is determined whether the % of the Object's FL<% of the server FL. As previously stated, the % of the server FL is the % of the freshness lifetime set at the startup of server 104 using server preferences set by an administrator. Alternatively, the % of the server FL may be configurable. If it is determined that the % of the Object's FL is less than the % of the Server FL, then the process proceeds to step 350.
  • In step [0341] 350, the object is determined not to have expired. The process then proceeds to step 352.
  • In step [0342] 352, the object is retrieved from the cache and processed in an implementation or application dependent manner.
  • Returning to decision step [0343] 348, if it is determined that the % of the Object's FL is greater than or equal to the % of the Server FL, then the process proceeds to step 354.
  • In step [0344] 354, in an embodiment, a random number is generated using a random number generator. In one embodiment, the random number generator may be normally distributed. In another embodiment, the random number generator may be uniformly distributed. One skilled in the relevant arts would know that other distributions may be used without departing from the scope of the present invention. The process then proceeds to decision step 356.
  • In decision step [0345] 356, it is determined whether the random number generated in step 354 is less than the % of the Object's FL. If the random number is greater than or equal to the % of the Object's FL, then the process proceeds to step 350, where the object is determined not to have expired, and is then retrieved from the cache in step 352.
  • Returning to decision step [0346] 356, if it is determined that the random number generated in step 354 is less than the % of the Object's FL, then the process proceeds to step 358.
  • In step [0347] 358, it is determined that the object has expired. The process then proceeds to step 360.
  • In step [0348] 360, server 104 attempts to retrieve the object from provider 128.
  • The following is an example of how the above method works according to an embodiment of the invention. As previously stated, if the % of the Object's FL is within the % of the FL set by the server, the stochastic process is implemented. If, for example, an object's age is 190 and the object's freshness lifetime is 200, the object's age is 95% of the object's freshness lifetime. Suppose server [0349] 104 was set for a threshold of 90% of the freshness lifetime. When a decision is made to vary the expiration for determining whether the object is fresh or expired, the probability that the object is expired is determined by figuring out what percentage of the vary range (90-100%) the current age of the object has covered. The vary range is 90-100 percent, and since the age of the object is 95%, 50% is the probability that the object is expired. If the age were 92% of the freshness lifetime, the probability would be 20%, if 98, 80%, etc. Similarly, if the range were 80-100, and the age is 95%, the probability would be 75%. Then the random number is generated, and compared to the probability in order to determine if the object is fresh or expired. Table 3 shows the age of the object, the object's % of freshness lifetime, and the probability that the object will expire for the above example.
    TABLE 3
    Age % of Freshness Lifetime/100 Probability of Expiring
    179 .895 0% (not considered)
    185 .925 25%
    190 .95 50%
    195 .975 75%
    200 1.0 100% 
  • FIG. 3E is a diagram showing freshness lifetime for the object described in the above example. The shaded area indicates the vary range in which it is determined if the object is fresh or expired. [0350]
  • 3.2 Syncing Mobile Devices [0351]
  • 3.2.1 Single Account/Profile-Multiple Devices [0352]
  • Server [0353] 104 enables a single account/profile user to sync multiple devices and obtain device specific content on each device. FIG. 3F is an example block diagram 362 illustrating a single account/profile having multiple devices. Block diagram 362 comprises a user account/profile 364, a first mobile device 366, a second mobile device 368, a third mobile device 370, server 104, and providers 128. First mobile device 366 may be a Palm device. Second mobile device 368 may be a cell phone. Third mobile device 370 may be Windows CE device. Although, FIG. 3F shows three mobile devices associated with a single account/profile, one skilled in the relevant art(s) would know that more devices or one less device could be added or subtracted, respectively, without departing from the scope of the invention. User account/profile 364 is associated with each mobile device 366-370. Each mobile device 366-370 interacts with server 104 via a transmission medium which may be any wired or wireless medium using any communication protocol. Server 104 may also connect to providers 128.
  • When any one of mobile devices [0354] 366-370 initially connects to server 104, each device 366-370 will provide its device characteristics to server 104. Server 104 will store the device characteristics in database module 126 and send the device characteristics to web synchronization module 124 and/or server extension module 156. For subsequent connections with server 104, each mobile device 366-370 will identify itself to server 104 and server 104 will retrieve the device's characteristics from database module 126. In one embodiment, as long as the user continues to sync devices 366-370 with server 104, server 104 will maintain each device's information on database module 126. If any one of devices 366-370 are not synced within some predetermined period, server 104 may optionally delete that device's information from database module 126. If a user syncs devices 366-370, one right after the other, each device 366-370 will have the same content, but the content will be optimized for each specific device 366-370.
  • An embodiment of the invention also provides a common link to share and sync data objects between disparate user devices. For example, if user account/profile [0355] 364 has a personal digital assistant and a cell phone, neither the PDA nor the cell phone may have the ability to communicate directly with each other. Assume an address book exists on both the cell phone and the PDA. The address book must be separately updated since the two devices do not have the ability to communicate with each other. However, by using server 104 of the present invention, the PDA and the cell phone may sync up with server 104 to provide the same information on both devices. In this example, the address book of both devices may sync up with server 104 to enable the address book on both the PDA and cell phone to contain the same information. Thus, the invention syncs disparate user devices by providing server 104 as a common link to share and sync data objects.
  • 3.2.2 Single Device—Multiple Servers [0356]
  • The invention also enables a single device to connect to multiple servers. FIG. 3G shows an example screen shot for enabling a user to add multiple servers. FIG. 3H is an exemplary block diagram [0357] 363 representing a single mobile device that connects to multiple servers. Diagram 363 comprises single user account/profile 364 connected to mobile device 366, which, in turn, can be connected to a plurality of servers 365, 367, and 369 that may be connected to any variety of providers 128, such as the Web, a database, such as LOTUS Notes, or a network, respectively. Although FIG. 3H shows three servers 365-369, one skilled in the relevant art(s), based on the teachings contained herein, would know that more servers or less servers could be implemented without departing from the scope of the invention. When a user initiates a sync, in an embodiment, device 366 will be synced to each enabled server on device 366, one at a time.
  • FIG. 3I is an exemplary flow diagram representing a sync process for a device connected to multiple servers. The process begins with step [0358] 374. In step 374, a user initiates a sync. The process proceeds to step 376.
  • In step [0359] 376, a list of sync servers and accounts per server are retrieved. The process then proceeds to step 378.
  • In step [0360] 378, device 366 is synced to each server, one at a time.
  • 3.2.3 Multiple Devices—Multiple Servers [0361]
  • The invention also allows multiple devices for a single user account/profile to be connected to a plurality of servers. A multiple device—multiple server scenario is shown in FIG. 3J. Although three mobile devices and three servers are shown in FIG. 3J, one skilled in the art would know that more or less devices and servers could be used without departing from the scope of the invention. In one embodiment, user account/profile [0362] 364 can cache a variety of device characteristics 366, 368, and 370 used to access a variety of servers 365, 367, and 369. In one embodiment, the user can store the device profiles on a desktop and store the multi-server connections on devices 366, 368, and 370. When the user initiates a sync for any one of devices 366, 368, and 370, a list of sync servers and accounts per server is retrieved for the device and the device is synced to each server in the list, one at a time. The user may then sync the next device, as described above in section 3.2.1.
  • 4. Executing Scripts on Mobile Devices [0363]
  • 4.1 Overview [0364]
  • According to an embodiment, the present invention transforms, loads, and executes scripts onto mobile devices. The present invention is able to retain the interactivity of the scripts with a data object, such as a HTML document or object of other forms, from which they were originally located. The present invention retains the functionality of the scripts on mobile devices, such as device [0365] 106. According to embodiments of the present invention, scripts can be executed on clients 108 which are currently connected to a server or network. According to alternative embodiments of the present invention, scripts can execute on devices which are not currently connected to a server or network through any type of connection (wired, wireless, etc.).
  • The terms “script,” “executable script,” “applet,” and the plural form of these terms are used interchangeably throughout this document to refer to programs that accompany or are embedded within an object (It is noted that the invention is described, at times, in terms of HTML documents for illustrative purposes, but the invention is not limited to this examples. The invention includes operations with other types of data objects, such as but not limited to other mark-up language or tag-based documents.). Various HTML specifications define how scripts can be included in objects (i.e., Web pages), so that programmers can develop objects that can accept scripts. [0366]
  • Scripts can be programmed to execute immediately when the object is loaded into a client, a client's Web browser or other display-interface program. Alternatively, scripts can also be programmed to execute in response to browser events, such as when a user clicks on a button or when the user resets a form in the object. [0367]
  • The terms “scripting language,” “script language,” “programming languages,” and the plural form of these terms are used interchangeably throughout this document to refer to computer programming languages used to make scripts. As one skilled in the relevant art(s) would recognize, based at least on the teachings herein, many programming languages can be used as scripting languages, including but not limited to the following programming languages: JavaScript, ECMAScript, Java, Perl, Tcl, Visual Basic, and VBScript. [0368]
  • 4.2 Server-Side Compilation [0369]
  • Many programming languages are implemented with executable programs which transform their source file (e.g., a script) into a program. Many programming languages include a compiler. Some programming languages include an interpreter. [0370]
  • A compiler translates a file written in a source language into an equivalent computer program in a target language. Some compilers translate the file written in the source language directly to a machine language, which can be directly executed by a device [0371] 106, server 104, or client 108. Other compilers translate the file into an intermediate stage known as a virtual machine language.
  • An interpreter is an auxiliary program which can execute virtual machine code. Virtual machine languages are sometimes called byte code or P-code languages. Interpreters for these languages are sometimes called byte code interpreters or P-code interpreters. [0372]
  • FIG. 4 is a block diagram illustrating script compiler modules according to an embodiment of the invention. In FIG. 4, block diagram [0373] 400 depicts content provider 128, server 104 and client 108. The server 104 includes script compiler modules 402 a-402 n for compiling, transforming, and recompiling scripts into languages executable and compatible with client 108 and device 106. The client 108 includes several language interpreter modules 404 a-404 n for interpreting scripts arriving in form of virtual machine language.
  • In FIG. 4, a content provider [0374] 128 sends scripts along with an HTML page to the server 104. The server 104 interprets the page's scripts, which generate HTML and scripts as its output. This output is tokenized and sent to the client 108.
  • The client [0375] 108 also includes several script compiler modules 406 a-406 n which are capable of performing the functionality of script compiler modules 402 a-402 n. Modules 406 are available in embodiments where the server 104 is bypassed.
  • The content provider [0376] 128 sends objects and scripts to the server 104. According to one embodiment of the present invention, the script compiler module 402 compiles the scripts to virtual machine language according to the specifications of the client 108 and/or device 106. The server 104 sends the compiled scripts along with tokenized object to the client 108.
  • In one embodiment of the present invention, the client [0377] 108 requests an object from the server 104. Upon receiving the request, the script compiler modules 402 of the server 104 compile each script associated with the object, according to the script language for which they are implemented. In embodiments of the present invention, the server 104 can contain a separate script compiler module for each scripting language which it supports.
  • In one embodiment, as shown in FIG. 4, the script compiler modules [0378] 402 are managed by the server extension module 156. Each compiled script is sent to the requesting client where it can be stored and executed. In alternative embodiments of the invention, the client-side script compiler modules 406 can compile scripts directly to the machine language of a target client 108. In other embodiments of the invention, the client-side compiler modules 406 can compile scripts to a virtual machine language, which is interpreted by the language interpreter modules 404 of the client 108.
  • In one embodiment of the present invention, clients [0379] 108 and devices 106 can support several different virtual machine languages. A single client 108 can contain several language interpreter modules 404. The language interpreter modules 404 of client 108 can be managed by the client extension interface 138, as shown in FIG. 4.
  • In further embodiments, the server [0380] 104 can communicate with a number of clients 108 and devices 106 which support differing sets of virtual machine languages.
  • In one embodiment of the present invention, when the client [0381] 108 syncs with the server 104, it sends to the server 104 an encoded list of the virtual machine languages which it supports. In one embodiment of the present invention, if the server 104 is not able to compile a script in a particular script language to any of the languages which the client 108 supports, then it will not send any virtual machine code for the script to the client 108 and the client 108 can effectively ignore the script.
  • 4.3 Storing Interpreter Data Structures [0382]
  • As described herein, the language interpreter modules [0383] 404 on the client 108 interpret virtual machine code sent from the server 104. In one embodiment, the client operating system (e.g., Palm OS, Windows CE, Pocket PC) provides applications with two different types of memory architecture: one type which is fast to write to; and another type which is much slower to write to (It is noted that these speeds are relative and the actual speeds are implementation and application dependant.).
  • For example, but without limitation, on Palm devices, Palm OS provides applications with dynamic memory, which is a read-write random-access memory (RAM) which can be read or written in a single machine instruction. It also provides a storage memory, which is RAM which can be read with a single machine instruction, but which can be written only through a call to the operating system, which can take tens or hundreds of machine instructions to execute. [0384]
  • Here, the generic terms fast-write memory and slow-write memory are used. On Palm OS, dynamic memory is fast-write memory and storage memory is slow-write memory. In embodiments, language interpreter modules [0385] 404 store data structures which are frequently updated in fast-write memory, and store other data structures in slow-write memory.
  • According to embodiments of the present invention, certain virtual machine languages can contain instructions which manipulate objects. Each object has a number of properties, each of which has a name and a value. For example, the JavaScript language includes objects which have a name and a value. In embodiments using these or similar properties, language interpreter modules [0386] 404 store the name of each object property in slow-write memory. Modules 404 also store the value of each object property in fast-write memory.
  • This means that the language interpreter modules [0387] 404 can update the value of an existing object property by writing only to fast-write memory. In one embodiment, adding a new property to an object requires writing to slow-write memory. FIG. 5 is a block diagram illustrating a language interpreter module according to an embodiment of the invention. In FIG. 5, a diagram depicts how a language interpreter module 404 might represent a particular object O 502. Object O 502 has five properties, whose names 504 are “x,” “y,” “abc,” “foo,” and “xyz,” respectively. The properties' values 510 are “3,” “7,” “home,” “start,” and “false,” respectively.
  • As one skilled in the relevant art(s) would recognize, based at least on the teachings described herein, object O [0388] 502 can have more or less than five properties (i.e., more than or less than five names and/or values). More specifically, one skilled in the relevant art(s), based at least on the teachings described herein (e.g., with respect to the discussion of FIGS. 5 and 6), would be able to construct object with any number of properties.
  • In one embodiment of the present invention, the base data structure representing the object O [0389] 502 is stored in slow-write memory and has two fields names 504 and values 510. The names 504 are used as pointers to an array in slow-write memory which holds pointers to each property name. The values 510 are pointers to an array in fast-write memory which holds each property value.
  • 4.4 Using Object Delegation to Share Global Variables Across Pages [0390]
  • In one embodiment of the present invention, virtual machine languages can support global variables, which are values that are referenced by name anywhere within any script. [0391]
  • Delegation can be implemented in a number of ways. According to a method used in embodiments of the present invention, encapsulated objects are linked to other objects, so that they inherit properties via a parent or root object. Delegation introduces dynamic sharing of behavior between objects by adding the idea of a prototype or super object to every object. This in turn means that one can have a prototype or root object to begin process and pass along properties to all other linked objects. [0392]
  • FIG. 6 is a block diagram illustrating the operations of delegated language interpreter modules according to an embodiment of the present invention. In FIG. 6, diagram [0393] 600 illustrates the operations of language interpreter modules with delegation using represented global variables as the client 108 moves from one object to the next. There are two permanent global variables Math 608 and Date 610. These are stored as properties of the prototype object P 606.
  • On the first page represented by object G [0394] 602, the global variable document 612 points to an object representing the HTML document 618 viewed on the client 108. A script constructs two global variables x 616 and y 614 with values 5 and 7, respectively. The global variables document 612, x 616 and y 614 are stored as properties of a global object G 602 whose prototype object is object P 606. These variables are accessible to scripts only while the client 108 remains on the first page represented by object G 602. When the client 108 moves to a new HTML document, it constructs a new global object H 604 and gives it its own property document 614′ pointing to the new page's document object 620. A script on the second page constructs two global variables x 616′ and y 614′ with values 4 and abc, respectively. These global variables are stored as properties of object H 604.
  • According to embodiments of the present invention, the values of certain global variables can depend on the Web page currently being viewed. For example, in some embodiments, a global variable document [0395] 612 contains an object representing the current HTML document, such as document object 618, which is different for each Web page view on client 108. In an alternative embodiment, scripts can define new global variables which should be accessible to other scripts on the same HTML document, but which should not be accessible to scripts running on other HTML documents.
  • In further embodiments, global values are made permanent. They have values which are the same for all HTML documents. For example, in embodiments which support the JavaScript language, there is a global variable Math which holds an object containing various mathematical utility functions, such as Math.sin and Math.cos. In this embodiment, all scripts on all documents can access the Math object. [0396]
  • The embodiments described above illustrate the use of virtual machine languages with instructions which manipulate objects with properties. In a language with delegation, each object can contain a pointer to a prototype object. In one embodiment, whenever the language interpreter module [0397] 404 looks for a property of an object O 502, it first looks for the property in the object O itself, then in O's prototype object, then in that object's prototype object, and so on until it either finds the property or reaches an object which has no prototype object.
  • In one example, the Self language is used because it supports delegation. In another example, JavaScript is used because it also supports delegation. As one skilled in the relevant art(s) would recognize, based at least on the teachings described herein, other languages can be used, so long as they support the features of delegation. [0398]
  • In embodiments of the present invention, where the script language is the JavaScript language, global variables are actually properties of a global object. In one embodiment, if a virtual machine language supports delegation, then the global object G [0399] 602 has a prototype object P 606. The object G 602 contains global variables whose values depend on the HTML document currently being viewed.
  • The object P [0400] 606 contains global variables whose values are the same for all HTML documents. When the browser moves to a HTML document, the virtual machine interpreter modules 404 construct a new global object H 604. Object H's prototype object is the same object P 606 which was used as the prototype object for the old global object G 602. This means that the interpreter module 404 does not need to reconstruct the global values in object P 606 or add them explicitly to the new global object H 604. The global values in object P 606 are accessible through object H 604 just as they were through object G 602.
  • While only object [0401] 602-606 are described, it will be apparent to one skilled in the relevant art(s), based at least on the teachings herein, that the system of the present invention can support a plurality of objects and HTML documents. Furthermore, according to the embodiments described herein, the objects can be cascaded with additional layers of global objects.
  • 4.5 Server-Side Interpretation [0402]
  • Referring to FIG. 7, according to one embodiment of the present invention, the server [0403] 104 can contain one or more server-side language interpreter modules 704 which are used for interpreting scripts. Modules 704 are managed by the server extension module 156.
  • In an embodiment, if a device [0404] 106 requests an object containing a script; and
  • the device does not support any virtual machine language to which the server can compile the script; [0405]
  • the server contains a server-side language interpreter module which can interpret the script; [0406]
  • the script requires no user input; [0407]
  • the script performs output only by generating HTML; [0408]
  • the script requires no access to objects which are available only when its HTML page is viewed in a browser; [0409]
  • then the server [0410] 104 interprets the script, and sends the resulting HTML to the device 106 without sending the compiled script to the device 106. This allows even devices 106 and client 108 which have no virtual machine interpreter modules 404 to view and interact with objects which contain scripts.
  • FIG. 7 is a block diagram illustrating a server with a server-side language interpreter module according to an embodiment of the invention. [0411]
  • More specifically, FIG. 7 depicts a server [0412] 104 with a server-side language interpreter module 704 communicating with a client 108 that has no language interpreter modules 404. In FIG. 7, a content provider 128 sends scripts along with an HTML page to the server 104. The server-side language interpreter module 704 interprets the page's scripts, which generate HTML as their output. This HTML is tokenized and sent to the client 108 along with the HTML representing the page itself.
  • 4.6 Further Embodiments of Script Operations [0413]
  • Referring to FIG. 8, a routine for script operations according to an embodiment of the invention is shown. The process begins with step [0414] 802 and proceeds to step 804. In step 804, a client 108 sends a request for a document to a server 104. The client 108 can be on a device 106. The process proceeds to step 806.
  • In step [0415] 806, the client 108 sends a list of languages that it supports (i.e., languages that is understands and is able to compile and/or interpret) to the server 104. Although, at times, this embodiment refers to documents, the invention operates with any objects. The process proceeds to step 808.
  • In step [0416] 808, the client 108 receives from the server 104 the document that it requested along with a script related to that document. The client 108 can request more than one document, such as a series of documents which constitute a Web site. Accordingly, the client 108 can receive any number of scripts related to those requested documents. The process proceeds to step 810.
  • In step [0417] 810, the client 108 stores the document and script that it received in step 808. The process proceeds to step 812.
  • In step [0418] 812, the client 108 accesses the stored document. The process proceeds to step 814.
  • In step [0419] 814, the client 108 executes the stored script related to the stored document. The process proceeds to step 816.
  • In step [0420] 816, the client 108 updates the properties and/or performs other functions as called on by the executed script.
  • While the above embodiment describes the client [0421] 108 as operating on one document and one script, one skilled in the relevant art(s), based at least on the teachings described herein, would recognize that the above embodiment can operate with any number of documents and scripts.
  • Referring to FIG. 9, a flowchart showing a routine for executing scripts according to an embodiment of the invention is shown. The process provides a detailed embodiment of the operations of step [0422] 814. The process begins in step 904. In step 904, the client 108 determines the language in which the script is written. The process proceeds to step 906.
  • In step [0423] 906, the client 108 performs the optional step of compiling the script. In one embodiment, script compiler module 406a compiles the script. The process proceeds to step 908.
  • In step [0424] 908, the client 108 interprets or executes the script. In one embodiment, language interpreter module 404a interprets the script. The process proceeds to step 910.
  • In step [0425] 910, the client 108 receives a new page specific global object. In one embodiment, the client 108 receives the new page specific global object from operations performed by the script's operation in step 814. The process proceeds to step 912.
  • In step [0426] 912, the client 108 forwards a new page specific global object to storage memory for later retrieval. The process proceeds to step 816.
  • Referring to FIG. 10, a flowchart showing a routine for updating properties according to an embodiment of the invention is shown. The process provides a detailed embodiment of the operations of step [0427] 816. The process begins in step 1004. In step 1004, the client 108 accesses properties associated with a new page specific global object. In one embodiment, the new page specific global object is determined in step 814. The process proceeds to step 1006.
  • In step [0428] 1006, the client 108 updates the associated properties. The process proceeds to step 1008.
  • In step [0429] 1008, the client 108 stores the associate properties.
  • Referring to FIG. 11, a flowchart showing a routine for server-side script operations according to an embodiment of the invention is shown. The process begins with step [0430] 1102 and proceeds to step 1104. In step 1104, a client 108 sends a request for a document or other object to a server 104. The client 108 can be on a device 106. The process proceeds to step 1106.
  • In step [0431] 1106, the client 108 sends a list of languages that it supports (i.e., languages that is understands and is able to compile and/or interpret) to the server 104. In one embodiment, the client 108 can send a null list to the server 104 that indicates that the client 108 does not support any languages. The process proceeds to step 1108.
  • In step [0432] 1108, the client 108 receives from the server 104 the document or other object that it requested with information representing the related scripts. The client 108 can request more than one document or object, such as a series of documents which constitute a Web site. Accordingly, the client 108 can receive any number of pieces of information related to those requested scripts. The process proceeds to step 1110.
  • In step [0433] 1110, the client 108 stores the document and information that it received in step 1108. The process proceeds to step 1112.
  • In step [0434] 1112, the client 108 accesses the stored document. The process proceeds to step 1114.
  • In step [0435] 1114, the client 108 accessed the stored information related to the represented script.
  • While the above embodiment describes the client [0436] 108 as operating on one document or object, one skilled in the relevant art(s), based at least on the teachings described herein, would recognize that the above embodiment can operate with any number of documents.
  • 5. Conclusion [0437]
  • While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. [0438]

Claims (24)

What is claimed is:
1. A method of performing script operations for mobile devices, comprising the steps of:
(1) sending a request for at least one object;
(2) sending a list of support languages;
(3) receiving said at least one object; and
(4) receiving at least one script related to said at least one object.
2. The method of
claim 1
, further comprising the step of:
(5) storing said at least one object and said at least script.
3. The method of
claim 1
, further comprising the steps of:
(5) accessing said at least one object;
(6) executing said at least one script related to said at least one object.
4. The method of
claim 3
, wherein step (6) comprises the steps of:
(a) determining said at least one script's language;
(b) interpreting said at least one script based on said language;
(c) receiving page specific global objects; and
(d) forwarding said page specific global objects.
5. The method of
claim 4
, wherein step (a) further comprises the step of:
(i) compiling said at least one script.
6. The method of
claim 1
, further comprising the step of:
(5) updating at least one property based on operation of said at least one script.
7. The method of
claim 6
, wherein step (5) comprises the steps of:
(a) accessing at least one property associated with page specific global objects;
(b) updating said at least one property; and
(c) storing said at least one property.
8. The method of
claim 1
, wherein step (4) comprises the step of:
receiving information representing said at least one script, wherein said information is accessed instead of said at least one script.
9. A system for performing script operations for mobile devices, comprising:
first means for sending a request for at least one object;
second means for sending a list of support languages;
first means for receiving said at least one object; and second means for receiving at least one script related to said at least one object.
10. The system of
claim 9
, further comprising: means for storing said at least one object and said at least script.
11. The system of
claim 9
, further comprising:
means for accessing said at least one object;
means for executing said at least one script related to said at least one object.
12. The system of
claim 11
, wherein said means for executing comprises:
means for determining said at least one script's language;
means for interpreting said at least one script based on said language;
third means for receiving page specific global objects; and
means for forwarding said page specific global objects.
13. The system of
claim 12
, wherein said means for determining further comprises:
means for compiling said at least one script.
14. The system of
claim 9
, further comprising:
first means for updating at least one property based on operation of said at least one script.
15. The system of
claim 14
, wherein said means for updating comprises:
means for accessing at least one property associated with page specific global objects;
second means for updating said at least one property; and
means for storing said at least one property.
16. The system of
claim 9
, wherein said second means for receiving comprises:
second means for receiving information representing said at least one script, wherein said information is accessed instead of said at least one script.
17. A computer program product comprising a computer usable medium having computer readable program code mans embodied in said medium for performing script operations for mobile devices, said computer readable program code means comprising:
a first computer readable program code means for causing a computer to send a request for at least one object;
a second computer readable program code means for causing a computer to send a list of support languages;
a third computer readable program code means for causing a computer to receive said at least one object; and
a fourth computer readable program code means for causing a computer to receive at least one script related to said at least one object.
18. The computer program product of
claim 17
, further comprising:
a fifth computer readable program code means for causing a computer to store said at least one object and said at least script.
19. The computer program product of
claim 17
, further comprising:
a fifth computer readable program code means for causing a computer to access said at least one object;
a sixth computer readable program code means for causing a computer to execute said at least one script related to said at least one object.
20. The computer program product of
claim 19
, wherein said sixth computer readable program code means comprises:
a first computer readable program code means for causing a computer to determine said at least one script's language;
a second computer readable program code means for causing a computer to interpret said at least one script based on said language;
a third computer readable program code means for causing a computer to receive page specific global objects; and
a fourth computer readable program code means for causing a computer to forward said page specific global objects.
21. The computer program product of
claim 20
, wherein said first computer readable program code means further comprises:
a first computer readable program code means for causing a computer to compile said at least one script.
22. The computer program product of
claim 17
, further comprising:
a fifth computer readable program code means for causing a computer to update at least one property based on operation of said at least one script.
23. The computer program product of
claim 22
, wherein said fifth computer readable program code means comprises:
a first computer readable program code means for causing a computer to access at least one property associated with page specific global objects;
a second computer readable program code means for causing a computer to update said at least one property; and
a third computer readable program code means for causing a computer to store said at least one property.
24. The computer program product of
claim 17
, wherein said fourth computer readable program code means comprises:
a first computer readable program code means for causing a computer to receive information representing said at least one script, wherein said information is accessed instead of said at least one script.
US09754256 1999-09-10 2001-01-05 System, method, and computer program product for executing scripts on mobile devices Abandoned US20010047394A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US39339099 true 1999-09-10 1999-09-10
US18996900 true 2000-03-17 2000-03-17
US09559964 US6779042B1 (en) 1999-09-10 2000-04-28 System, method, and computer program product for enabling on-device servers, offline forms, and dynamic ad tracking on mobile devices
US09705927 US7987420B1 (en) 1999-09-10 2000-11-06 System, method, and computer program product for a scalable, configurable, client/server, cross-platform browser for mobile devices
US09754256 US20010047394A1 (en) 1999-09-10 2001-01-05 System, method, and computer program product for executing scripts on mobile devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09754256 US20010047394A1 (en) 1999-09-10 2001-01-05 System, method, and computer program product for executing scripts on mobile devices
US11329226 US7840647B2 (en) 1999-09-10 2006-01-11 System, method, and computer program product for executing scripts on mobile devices

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09705927 Continuation-In-Part US7987420B1 (en) 1999-09-10 2000-11-06 System, method, and computer program product for a scalable, configurable, client/server, cross-platform browser for mobile devices

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11329226 Division US7840647B2 (en) 1999-09-10 2006-01-11 System, method, and computer program product for executing scripts on mobile devices

Publications (1)

Publication Number Publication Date
US20010047394A1 true true US20010047394A1 (en) 2001-11-29

Family

ID=27497826

Family Applications (2)

Application Number Title Priority Date Filing Date
US09754256 Abandoned US20010047394A1 (en) 1999-09-10 2001-01-05 System, method, and computer program product for executing scripts on mobile devices
US11329226 Active 2019-11-05 US7840647B2 (en) 1999-09-10 2006-01-11 System, method, and computer program product for executing scripts on mobile devices

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11329226 Active 2019-11-05 US7840647B2 (en) 1999-09-10 2006-01-11 System, method, and computer program product for executing scripts on mobile devices

Country Status (1)

Country Link
US (2) US20010047394A1 (en)

Cited By (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020120940A1 (en) * 2001-02-02 2002-08-29 Open Tv Method and apparatus compilation of an interpretative language for interactive television
US20030018898A1 (en) * 2001-07-23 2003-01-23 Lection David B. Method, system, and computer-program product for providing selective access to certain child nodes of a document object model (DOM)
US20030033517A1 (en) * 2001-06-01 2003-02-13 Rutherglen Jason John Secure data accessing system and method
US20030070158A1 (en) * 2001-07-02 2003-04-10 Lucas Terry L. Programming language extensions for processing data representation language objects and related applications
US20030167256A1 (en) * 2002-01-18 2003-09-04 Seth White System and method for read-only entity bean caching
US20030172186A1 (en) * 2002-03-07 2003-09-11 International Business Machines Coporation Method, system and program product for transcoding content
US20030182628A1 (en) * 2002-03-19 2003-09-25 Luigi Lira Reformatting columns of content for display
US20030217169A1 (en) * 2002-03-21 2003-11-20 International Business Machines Corporation High-speed content transformation engine
US20040004641A1 (en) * 2002-07-02 2004-01-08 Ullas Gargi Image segmentation and warping for specialized display viewing
US20040024843A1 (en) * 2002-07-31 2004-02-05 Smith Christopher T. Method for provisioning distributed web applications
US20040064551A1 (en) * 2001-01-15 2004-04-01 Miki Amano Control system
US20040107403A1 (en) * 2002-09-05 2004-06-03 Tetzchner Jon Stephensen Von Presenting HTML content on a small screen terminal display
US20040225747A1 (en) * 2003-05-09 2004-11-11 Zafer Kadi Providing compiled bytecode applications to a wireless device
US20050081061A1 (en) * 2003-08-26 2005-04-14 Acott Troy Steven Compile-time code validation based on configurable virtual machine
US20050289450A1 (en) * 2004-06-23 2005-12-29 Microsoft Corporation User interface virtualization
US20060073785A1 (en) * 2004-10-05 2006-04-06 Research In Motion Limited Mobile device diagnosis, test, application deployment and update from a web page
US20060200751A1 (en) * 1999-11-05 2006-09-07 Decentrix Inc. Method and apparatus for providing conditional customization for generating a web site
US20060200535A1 (en) * 2002-08-02 2006-09-07 Martin Moser Method and computer system for handling incremental data in client-server communication
US20060230226A1 (en) * 2005-04-12 2006-10-12 M-Systems Flash Disk Pioneers, Ltd. Hard disk drive with optional cache memory
US20060282511A1 (en) * 2005-06-14 2006-12-14 Hitachi Global Storage Technologies Netherlands B.V. Method for limiting utilizing terminal of contents, and memory device and system for method
US20070050502A1 (en) * 2005-08-31 2007-03-01 Research In Motion Limited Method, system and apparatus for selective application access and synchronization
US20070061700A1 (en) * 2005-09-12 2007-03-15 Microsoft Corporation Initial server-side content rendering for client-script web pages
WO2008039700A2 (en) * 2006-09-26 2008-04-03 Swift Creek Systems, Llc Method for enabling dynamic content in a markup language based page using a dynamic markup language element
US7380242B2 (en) * 2003-05-14 2008-05-27 Mainsoft Israel Ltd. Compiler and software product for compiling intermediate language bytecodes into Java bytecodes
US7383339B1 (en) * 2002-07-31 2008-06-03 Aol Llc, A Delaware Limited Liability Company Local proxy server for establishing device controls
US20080139191A1 (en) * 2006-12-08 2008-06-12 Miguel Melnyk Content adaptation
US7437457B1 (en) 2003-09-08 2008-10-14 Aol Llc, A Delaware Limited Liability Company Regulating concurrent logins associated with a single account
US20090063530A1 (en) * 2007-09-04 2009-03-05 Lg Telecom Ltd. System and method for mobile web service
US20100005410A1 (en) * 2008-07-03 2010-01-07 Pang Xin Mobile device application framework
US20100023699A1 (en) * 2008-07-22 2010-01-28 Bridgewater Systems Corp. System and Method for Usage Analyzer of Subscriber Access to Communications Network
US20100049721A1 (en) * 2001-11-01 2010-02-25 Anderson Jeffrey G Local Agent for Remote File Access System
US20100057468A1 (en) * 2008-08-28 2010-03-04 Nortel Networks Limited Binary-caching for xml documents with embedded executable code
US7676801B1 (en) * 2004-08-31 2010-03-09 Sun Microsystems, Inc. Scanning of evacuated objects in a generation managed by the train algorithm
US20100088591A1 (en) * 2008-10-03 2010-04-08 Google Inc. Vertical Content on Small Display Devices
US7761558B1 (en) * 2006-06-30 2010-07-20 Google Inc. Determining a number of users behind a set of one or more internet protocol (IP) addresses
US7818728B1 (en) * 2005-04-04 2010-10-19 Qd Technology Llc Maximizing system resources used to decompress read-only compressed analytic data in a relational database table
US7840647B2 (en) 1999-09-10 2010-11-23 Ianywhere Solutions, Inc. System, method, and computer program product for executing scripts on mobile devices
US20110154305A1 (en) * 2009-07-31 2011-06-23 Leroux Brian System and method for remotely compiling multi-platform native applications for mobile devices
US7987420B1 (en) 1999-09-10 2011-07-26 Ianywhere Solutions, Inc. System, method, and computer program product for a scalable, configurable, client/server, cross-platform browser for mobile devices
US8176416B1 (en) 2006-03-17 2012-05-08 Wells Fargo Bank, N.A. System and method for delivering a device-independent web page
US20120150993A1 (en) * 2010-10-29 2012-06-14 Akamai Technologies, Inc. Assisted delivery of content adapted for a requesting client
US8245128B1 (en) * 2002-07-17 2012-08-14 Oracle International Corporation Intelligent client agent for a hybrid online/offline application
US8595308B1 (en) 1999-09-10 2013-11-26 Ianywhere Solutions, Inc. System, method, and computer program product for server side processing in a mobile device environment
US20140032851A1 (en) * 2012-07-27 2014-01-30 International Business Machines Corporation Randomized page weights for optimizing buffer pool page reuse
US8838873B2 (en) 2011-06-15 2014-09-16 Data Design Corporation Methods and apparatus for data access by a reprogrammable circuit module
US20150163087A1 (en) * 2013-12-05 2015-06-11 Riverbed Technology, Inc. Transparently intercepting and optimizing resource requests
US9135227B2 (en) 2002-09-10 2015-09-15 SQGo, LLC Methods and systems for enabling the provisioning and execution of a platform-independent application
US20160098546A1 (en) * 2008-03-10 2016-04-07 Jill Lewis Maurer Digital Media Content Creation and Distribution Methods
US9418353B2 (en) 2010-12-20 2016-08-16 Akamai Technologies, Inc. Methods and systems for delivering content to differentiated client devices
US9417894B1 (en) 2011-06-15 2016-08-16 Ryft Systems, Inc. Methods and apparatus for a tablet computer system incorporating a reprogrammable circuit module
EP3090357A4 (en) * 2013-12-31 2017-05-31 Sweetlabs, Inc. Hosted application marketplaces
US20170230544A1 (en) * 2014-06-24 2017-08-10 Ec Data Systems Inc. Audit logging for a secure, scalable and flexible internet fax architecture
US9736258B2 (en) 2011-12-23 2017-08-15 Akamai Technologies, Inc. Assessment of content delivery services using performance measurements from within an end user client application
US10019247B2 (en) 2014-05-15 2018-07-10 Sweetlabs, Inc. Systems and methods for application installation platforms
US10089098B2 (en) 2014-05-15 2018-10-02 Sweetlabs, Inc. Systems and methods for application installation platforms

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087630A1 (en) 2000-10-20 2002-07-04 Jonathan Wu Enhanced information and presence service
US7596611B1 (en) * 2002-04-01 2009-09-29 Veritas Operating Corporation Method and apparatus for maintaining information for use in the configuration of a client
EP2131296A1 (en) * 2003-11-14 2009-12-09 Research in Motion Limited System and method of retrieving and presenting partial (skipped) document content
US7273179B2 (en) * 2004-07-09 2007-09-25 Datalogic Scanning, Inc. Portable data reading device with integrated web server for configuration and data extraction
US20090150825A1 (en) * 2006-03-13 2009-06-11 Fujitsu Limited Screen generation program, screen generation apparatus, and screen generation method
KR100796958B1 (en) * 2006-06-22 2008-01-22 신가정 Ip adapter for transferring contents to portable device and method of transferring contents using the same
CN101455057A (en) * 2006-06-30 2009-06-10 国际商业机器公司 A method and apparatus for caching broadcasting information
US20090210631A1 (en) 2006-09-22 2009-08-20 Bea Systems, Inc. Mobile application cache system
US8490052B2 (en) * 2008-10-14 2013-07-16 Microsoft Corporation Declarative programming model for authoring and execution control and data flow for resource oriented system
US8438295B2 (en) 2008-10-14 2013-05-07 Microsoft Corporation Declarative programming model for modeling and execution of triggers for resource oriented system
US8533666B2 (en) * 2008-10-17 2013-09-10 Microsoft Corporation Interactive design environments to visually model, debug and execute resource oriented programs
US8806325B2 (en) * 2009-11-18 2014-08-12 Apple Inc. Mode identification for selective document content presentation
GB2477318A (en) * 2010-01-29 2011-08-03 Amt Sybex A page rendering method for a small form factor device
US8977677B2 (en) 2010-12-01 2015-03-10 Microsoft Technology Licensing, Llc Throttling usage of resources
US9185513B1 (en) * 2011-12-02 2015-11-10 Google Inc. Method and system for compilation with profiling feedback from client
US9329901B2 (en) 2011-12-09 2016-05-03 Microsoft Technology Licensing, Llc Resource health based scheduling of workload tasks
US9305274B2 (en) 2012-01-16 2016-04-05 Microsoft Technology Licensing, Llc Traffic shaping based on request resource usage
US9122524B2 (en) 2013-01-08 2015-09-01 Microsoft Technology Licensing, Llc Identifying and throttling tasks based on task interactivity
US9448776B1 (en) 2015-01-08 2016-09-20 AppNotch LLC Method and apparatus for converting a website into a native mobile application
US20170300178A1 (en) * 2016-04-19 2017-10-19 Lexmark International Technology, Sarl System and Methods for Syncing Web Application Records Across Multiple Browser Windows

Citations (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5392390A (en) * 1992-04-10 1995-02-21 Intellilink Corp. Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5666530A (en) * 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
US5727159A (en) * 1996-04-10 1998-03-10 Kikinis; Dan System in which a Proxy-Server translates information received from the Internet into a form/format readily usable by low power portable computers
US5727202A (en) * 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US5884323A (en) * 1995-10-13 1999-03-16 3Com Corporation Extendible method and apparatus for synchronizing files on two different computer systems
US5905856A (en) * 1996-02-29 1999-05-18 Bankers Trust Australia Limited Determination of software functionality
US5917491A (en) * 1997-08-29 1999-06-29 Netscape Communications Corporation Page proxy
US5919247A (en) * 1996-07-24 1999-07-06 Marimba, Inc. Method for the distribution of code and data updates
US5943496A (en) * 1997-05-17 1999-08-24 Intertop Corporation Methods for developing and instantiating object classes using a java virtual machine extension
US5974238A (en) * 1996-08-07 1999-10-26 Compaq Computer Corporation Automatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elements
US6006274A (en) * 1997-01-30 1999-12-21 3Com Corporation Method and apparatus using a pass through personal computer connected to both a local communication link and a computer network for indentifying and synchronizing a preferred computer with a portable computer
US6012083A (en) * 1996-09-24 2000-01-04 Ricoh Company Ltd. Method and apparatus for document processing using agents to process transactions created based on document content
US6023701A (en) * 1997-09-25 2000-02-08 International Business Machines Corporation Skeleton page retrieval mode for web navigation
US6029195A (en) * 1994-11-29 2000-02-22 Herz; Frederick S. M. System for customized electronic identification of desirable objects
US6052735A (en) * 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6122658A (en) * 1997-07-03 2000-09-19 Microsoft Corporation Custom localized information in a networked server for display to an end user
US6148330A (en) * 1997-11-17 2000-11-14 Netscape Communications Corp. System and method for automatically generating content for a network channel
US6151610A (en) * 1993-12-27 2000-11-21 Digital Equipment Corporation Document display system using a scripting language having container variables setting document attributes
US6167255A (en) * 1998-07-29 2000-12-26 @Track Communications, Inc. System and method for providing menu data using a communication network
US6167441A (en) * 1997-11-21 2000-12-26 International Business Machines Corporation Customization of web pages based on requester type
US6209111B1 (en) * 1998-11-09 2001-03-27 Microsoft Corporation Error correction on a mobile device
US6236991B1 (en) * 1997-11-26 2001-05-22 International Business Machines Corp. Method and system for providing access for categorized information from online internet and intranet sources
US6266681B1 (en) * 1997-04-08 2001-07-24 Network Commerce Inc. Method and system for inserting code to conditionally incorporate a user interface component in an HTML document
US6311058B1 (en) * 1998-06-30 2001-10-30 Microsoft Corporation System for delivering data content over a low bit rate transmission channel
US6336137B1 (en) * 2000-03-31 2002-01-01 Siebel Systems, Inc. Web client-server system and method for incompatible page markup and presentation languages
US6449638B1 (en) * 1998-01-07 2002-09-10 Microsoft Corporation Channel definition architecture extension
US6470378B1 (en) * 1999-03-31 2002-10-22 Intel Corporation Dynamic content customization in a clientserver environment
US6493758B1 (en) * 1998-09-08 2002-12-10 Microsoft Corporation Offline viewing of internet content with a mobile device
US6496979B1 (en) * 1997-10-24 2002-12-17 Microsoft Corporation System and method for managing application installation for a mobile device

Family Cites Families (145)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5684828A (en) 1988-12-09 1997-11-04 Dallas Semiconductor Corp. Wireless data module with two separate transmitter control outputs
US5377326A (en) 1989-07-06 1994-12-27 Sharp Kabushiki Kaisha Electronic apparatus with remote data supplementation/update selection and error display
US5805807A (en) 1990-05-25 1998-09-08 Norand Corporation Multilevel data communication system including local and host systems
US5349678A (en) 1991-08-21 1994-09-20 Norand Corporation Versatile RF data capture system
JP2502914B2 (en) 1992-07-31 1996-05-29 インターナショナル・ビジネス・マシーンズ・コーポレイション De - data transfer method and apparatus
US5410543A (en) 1993-01-04 1995-04-25 Apple Computer, Inc. Method for connecting a mobile computer to a computer network by using an address server
US5426594A (en) 1993-04-02 1995-06-20 Motorola, Inc. Electronic greeting card store and communication system
US5694546A (en) 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US5724521A (en) 1994-11-03 1998-03-03 Intel Corporation Method and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing manner
US6128648A (en) 1994-11-23 2000-10-03 International Business Machines Corporation Information handling system and method for maintaining coherency between network servers and mobile terminals
US5684990A (en) 1995-01-11 1997-11-04 Puma Technology, Inc. Synchronization of disparate databases
US5729735A (en) 1995-02-08 1998-03-17 Meyering; Samuel C. Remote database file synchronizer
US5802292A (en) 1995-04-28 1998-09-01 Digital Equipment Corporation Method for predictive prefetching of information over a communications network
WO1997004389A1 (en) 1995-07-20 1997-02-06 Novell, Inc. Transaction synchronization in a disconnectable computer and network
US5850517A (en) 1995-08-31 1998-12-15 Oracle Corporation Communication link for client-server having agent which sends plurality of requests independent of client and receives information from the server independent of the server
JPH09231242A (en) 1995-09-14 1997-09-05 Sony Corp Terminal equipment placed in network and information recording medium that can be read by the terminal equipment
US5768511A (en) 1995-09-18 1998-06-16 International Business Machines Corporation Method and system for managing objects in networked computer system with action performed in the server and object updated in the client
US6029175A (en) 1995-10-26 2000-02-22 Teknowledge Corporation Automatic retrieval of changed files by a network software agent
US5794210A (en) 1995-12-11 1998-08-11 Cybergold, Inc. Attention brokerage
US6119155A (en) * 1995-12-11 2000-09-12 Phone.Com, Inc. Method and apparatus for accelerating navigation of hypertext pages using compound requests
US5915112A (en) 1996-01-02 1999-06-22 International Business Machines Corporation Remote procedure interface with support for multiple versions
US5732074A (en) 1996-01-16 1998-03-24 Cellport Labs, Inc. Mobile portable wireless communication system
US6021433A (en) 1996-01-26 2000-02-01 Wireless Internet, Inc. System and method for transmission of data
JPH09212397A (en) 1996-01-31 1997-08-15 Toshiba Corp File reading method
US5754774A (en) 1996-02-15 1998-05-19 International Business Machine Corp. Client/server communication system
US5862325A (en) 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
US5953392A (en) 1996-03-01 1999-09-14 Netphonic Communications, Inc. Method and apparatus for telephonically accessing and navigating the internet
US5673322A (en) 1996-03-22 1997-09-30 Bell Communications Research, Inc. System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks
US5937163A (en) 1996-03-26 1999-08-10 Industrial Technology Research Institute Method and system at a host node for hierarchically organizing the links visited by a world wide web browser executing at the host node
US6076109A (en) 1996-04-10 2000-06-13 Lextron, Systems, Inc. Simplified-file hyper text protocol
US5809242A (en) 1996-04-19 1998-09-15 Juno Online Services, L.P. Electronic mail system for displaying advertisement at local computer received from remote system while the local computer is off-line the remote system
US6516341B2 (en) 1998-09-14 2003-02-04 Juno Online Services, Inc. Electronic mail system with advertising
US5848396A (en) 1996-04-26 1998-12-08 Freedom Of Information, Inc. Method and apparatus for determining behavioral profile of a computer user
US5881234A (en) 1996-04-26 1999-03-09 Schwob; Pierre R. Method and system to provide internet access to users via non-home service providers
US5835712A (en) 1996-05-03 1998-11-10 Webmate Technologies, Inc. Client-server system using embedded hypertext tags for application and database development
US6085101A (en) 1996-05-17 2000-07-04 Telcordia Technologies, Inc. Communications network having a multicast capability
US5918013A (en) 1996-06-03 1999-06-29 Webtv Networks, Inc. Method of transcoding documents in a network environment using a proxy server
US5727129A (en) 1996-06-04 1998-03-10 International Business Machines Corporation Network system for profiling and actively facilitating user activities
US5961601A (en) 1996-06-07 1999-10-05 International Business Machines Corporation Preserving state information in a continuing conversation between a client and server networked via a stateless protocol
US5813007A (en) 1996-06-20 1998-09-22 Sun Microsystems, Inc. Automatic updates of bookmarks in a client computer
US5862346A (en) 1996-06-28 1999-01-19 Metadigm Distributed group activity data network system and corresponding method
US5906657A (en) 1996-07-01 1999-05-25 Sun Microsystems, Inc. System using position detector to determine location and orientation between computers to select information to be transferred via wireless medium
US5862339A (en) 1996-07-09 1999-01-19 Webtv Networks, Inc. Client connects to an internet access provider using algorithm downloaded from a central server based upon client's desired criteria after disconnected from the server
US5922045A (en) 1996-07-16 1999-07-13 At&T Corp. Method and apparatus for providing bookmarks when listening to previously recorded audio programs
US5794259A (en) 1996-07-25 1998-08-11 Lextron Systems, Inc Apparatus and methods to enhance web browsing on the internet
US5799063A (en) 1996-08-15 1998-08-25 Talk Web Inc. Communication system and method of providing access to pre-recorded audio messages via the Internet
US5933811A (en) 1996-08-20 1999-08-03 Paul D. Angles System and method for delivering customized advertisements within interactive communication systems
US6006231A (en) 1996-09-10 1999-12-21 Warp 10 Technologies Inc. File format for an image including multiple versions of an image, and related system and method
US5918237A (en) 1996-09-30 1999-06-29 At&T Corp. System and method for providing multimedia bookmarks for hypertext markup language files
US5943676A (en) 1996-11-13 1999-08-24 Puma Technology, Inc. Synchronization of recurring records in incompatible databases
US5864676A (en) 1996-11-14 1999-01-26 Triteal Corporation URL login
US6026474A (en) 1996-11-22 2000-02-15 Mangosoft Corporation Shared client-side web caching using globally addressable memory
US6023698A (en) 1996-12-05 2000-02-08 International Business Machines Corporation System and method for transparently registering and updating information over the internet
US6065059A (en) 1996-12-10 2000-05-16 International Business Machines Corporation Filtered utilization of internet data transfers to reduce delay and increase user control
US5896502A (en) 1996-12-10 1999-04-20 International Business Machines Corporation Internet data transfer control via a client system to reduce delay
EP0848339B1 (en) 1996-12-12 2007-01-24 SONY DEUTSCHLAND GmbH Server with automatic loading of menus
US5873100A (en) 1996-12-20 1999-02-16 Intel Corporation Internet browser that includes an enhanced cache for user-controlled document retention
US5978833A (en) 1996-12-31 1999-11-02 Intel Corporation Method and apparatus for accessing and downloading information from the internet
US5978842A (en) 1997-01-14 1999-11-02 Netmind Technologies, Inc. Distributed-client change-detection tool with change-detection augmented by multiple clients
US6049821A (en) 1997-01-24 2000-04-11 Motorola, Inc. Proxy host computer and method for accessing and retrieving information between a browser and a proxy
US6125281A (en) 1997-01-31 2000-09-26 Nokia Mobile Phones Limited Real-time SMS application messaging using an SMSC-linked server
US5790977A (en) 1997-02-06 1998-08-04 Hewlett-Packard Company Data acquisition from a remote instrument via the internet
US5961602A (en) 1997-02-10 1999-10-05 International Business Machines Corporation Method for optimizing off-peak caching of web data
US5948066A (en) 1997-03-13 1999-09-07 Motorola, Inc. System and method for delivery of information over narrow-band communications links
US5796952A (en) 1997-03-21 1998-08-18 Dot Com Development, Inc. Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database
US6182122B1 (en) 1997-03-26 2001-01-30 International Business Machines Corporation Precaching data at an intermediate server based on historical data requests by users of the intermediate server
US5890158A (en) 1997-03-31 1999-03-30 International Business Machines Corporation Method, apparatus, and program storage device for sharing objects with a network server and a database server using a common object model
US6085192A (en) 1997-04-11 2000-07-04 Roampage, Inc. System and method for securely synchronizing multiple copies of a workspace element in a network
US5946697A (en) 1997-04-22 1999-08-31 Microsoft Corporation Rapid transfer of HTML files
US5991800A (en) 1997-05-22 1999-11-23 Motorola, Inc. Method and apparatus for providing internet service at a subscriber premise
US6023708A (en) 1997-05-29 2000-02-08 Visto Corporation System and method for using a global translator to synchronize workspace elements across a network
US6195692B1 (en) 1997-06-02 2001-02-27 Sony Corporation Television/internet system having multiple data stream connections
US5987454A (en) 1997-06-09 1999-11-16 Hobbs; Allen Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource
US6091956A (en) 1997-06-12 2000-07-18 Hollenberg; Dennis D. Situation information system
US5978828A (en) 1997-06-13 1999-11-02 Intel Corporation URL bookmark update notification of page content or location changes
US6009462A (en) 1997-06-16 1999-12-28 Digital Equipment Corporation Replacing large bit component of electronic mail (e-mail) message with hot-link in distributed computer system
US6029141A (en) 1997-06-27 2000-02-22 Amazon.Com, Inc. Internet-based customer referral system
US6119167A (en) 1997-07-11 2000-09-12 Phone.Com, Inc. Pushing and pulling data in networks
US5895471A (en) 1997-07-11 1999-04-20 Unwired Planet, Inc. Providing a directory of frequently used hyperlinks on a remote server
US6061718A (en) 1997-07-23 2000-05-09 Ericsson Inc. Electronic mail delivery system in wired or wireless communications system
US6219696B1 (en) 1997-08-01 2001-04-17 Siemens Corporate Research, Inc. System for providing targeted internet information to mobile agents
US5877766A (en) 1997-08-15 1999-03-02 International Business Machines Corporation Multi-node user interface component and method thereof for use in accessing a plurality of linked records
US6035324A (en) 1997-08-28 2000-03-07 International Business Machines Corporation Client-side asynchronous form management
US6070184A (en) 1997-08-28 2000-05-30 International Business Machines Corporation Server-side asynchronous form management
US6182113B1 (en) 1997-09-16 2001-01-30 International Business Machines Corporation Dynamic multiplexing of hyperlinks and bookmarks
US6148005A (en) 1997-10-09 2000-11-14 Lucent Technologies Inc Layered video multicast transmission system with retransmission-based error recovery
US6041360A (en) 1997-11-21 2000-03-21 International Business Machines Corporation Web browser support for dynamic update of bookmarks
US6065120A (en) 1997-12-09 2000-05-16 Phone.Com, Inc. Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices
DE69935848T2 (en) 1998-01-07 2008-01-10 Microsoft Corp., Redmond A system for delivery of data over a transmission channel with low bit rates
US6032162A (en) 1998-01-08 2000-02-29 Burke; Alexander James System for processing and storing internet bookmark address links
US6023704A (en) 1998-01-29 2000-02-08 International Business Machines Corporation Apparatus and method for swapping identities of two objects to reference the object information of the other
US6092079A (en) 1998-01-29 2000-07-18 International Business Machines Corporation Apparatus and method for updating an object without affecting the unique identity of the object
US6560639B1 (en) 1998-02-13 2003-05-06 3565 Acquisition Corporation System for web content management based on server-side application
US6219679B1 (en) 1998-03-18 2001-04-17 Nortel Networks Limited Enhanced user-interactive information content bookmarking
US6065051A (en) 1998-04-15 2000-05-16 Hewlett-Packard Company Apparatus and method for communication between multiple browsers
CA2328913A1 (en) 1998-04-17 1999-10-28 Karl D. Zetmeir Telephone call management software and internet marketing method
JP3175692B2 (en) 1998-04-28 2001-06-11 日本電気株式会社 Data linkage system and method data links between computers and portable terminals
US6353839B1 (en) 1998-04-30 2002-03-05 Openwave Systems Inc. Method for inline variables management in a hypermedia display language
US6058416A (en) 1998-05-22 2000-05-02 International Business Machines Corportion Flexible state sharing and consistency mechanism for interactive applications
US6209027B1 (en) 1998-06-01 2001-03-27 International Business Machines Corporation Recirculating network address list with single button sequencer/selector
US6300947B1 (en) * 1998-07-06 2001-10-09 International Business Machines Corporation Display screen and window size related web page adaptation system
US6141010A (en) 1998-07-17 2000-10-31 B. E. Technology, Llc Computer interface method and apparatus with targeted advertising
US6925595B1 (en) 1998-08-05 2005-08-02 Spyglass, Inc. Method and system for content conversion of hypertext data using data mining
US6415316B1 (en) 1998-09-01 2002-07-02 Aidministrator Nederland B.V. Method and apparatus for implementing a web page diary
US6278449B1 (en) 1998-09-03 2001-08-21 Sony Corporation Apparatus and method for designating information to be retrieved over a computer network
US6226650B1 (en) 1998-09-17 2001-05-01 Synchrologic, Inc. Database synchronization and organization system and method
US6131096A (en) 1998-10-05 2000-10-10 Visto Corporation System and method for updating a remote database in a network
US6195024B1 (en) 1998-12-11 2001-02-27 Realtime Data, Llc Content independent data compression method and system
US6470358B1 (en) 1999-01-22 2002-10-22 Siemens Information And Communication Networks, Inc. Remote synchronization with intelligent power management
US6332127B1 (en) 1999-01-28 2001-12-18 International Business Machines Corporation Systems, methods and computer program products for providing time and location specific advertising via the internet
US20050192008A1 (en) 1999-03-31 2005-09-01 Nimesh Desai System and method for selective information exchange
WO2000062463A3 (en) 1999-04-08 2001-01-25 Plusfactor Software System and method for advertising during a data transfer process
US6553037B1 (en) 1999-04-08 2003-04-22 Palm, Inc. System and method for synchronizing data among a plurality of users via an intermittently accessed network
US6654746B1 (en) 1999-05-03 2003-11-25 Symantec Corporation Methods and apparatuses for single-connection file synchronization workgroup file update
US6650620B1 (en) 1999-05-04 2003-11-18 Tut Systems, Inc. Resource constrained routing in active networks
EP1061458A2 (en) 1999-06-15 2000-12-20 Sun Microsystems, Inc. Caching of reduced forms of web pages on a small footprint device
US6401104B1 (en) 1999-07-03 2002-06-04 Starfish Software, Inc. System and methods for synchronizing datasets using cooperation among multiple synchronization engines
US6671853B1 (en) 1999-07-15 2003-12-30 International Business Machines Corporation Method and system for selectively streaming markup language documents
US6535912B1 (en) 1999-08-31 2003-03-18 Lucent Technologies Inc. Method for creating and playing back a smart bookmark that automatically retrieves a requested Web page through a plurality of intermediate Web pages
US7392308B2 (en) 1999-09-10 2008-06-24 Ianywhere Solutions, Inc. System, method, and computer program product for placement of channels on a mobile device
US20020052781A1 (en) 1999-09-10 2002-05-02 Avantgo, Inc. Interactive advertisement mechanism on a mobile device
US20010047394A1 (en) 1999-09-10 2001-11-29 Kloba David D. System, method, and computer program product for executing scripts on mobile devices
US20080215672A1 (en) 1999-09-10 2008-09-04 Sybase 365, Inc. System, Method, and Computer Program Product for a Scalable, Configurable, Client/Server, Cross-Platform Browser for Mobile Devices
US6839744B1 (en) 1999-09-10 2005-01-04 Ianywhere Solutions, Inc. System, method, and computer program product for administering channels, content, and data for mobile devices
US6519627B1 (en) 1999-09-27 2003-02-11 International Business Machines Corporation System and method for conducting disconnected transactions with service contracts for pervasive computing devices
US6636897B1 (en) 1999-09-28 2003-10-21 Microsoft Corporation Selective information subset synchronization based on single user action
US6415317B1 (en) 1999-10-01 2002-07-02 Joshua Michael Yelon Software system for reducing the appearance of latency in a multi-user environment
US6236357B1 (en) 1999-10-25 2001-05-22 Lucent Technologies Inc. Automatic vehicle location system and method with reduced bandwidth requirement
US6275859B1 (en) 1999-10-28 2001-08-14 Sun Microsystems, Inc. Tree-based reliable multicast system where sessions are established by repair nodes that authenticate receiver nodes presenting participation certificates granted by a central authority
US6754670B1 (en) 1999-12-17 2004-06-22 International Business Machines Corporation Mapping relational tables to object oriented classes
CA2298003A1 (en) * 2000-02-04 2001-08-04 Ibm Canada Limited-Ibm Canada Limitee Scripting task-level user interfaces
US6615276B1 (en) 2000-02-09 2003-09-02 International Business Machines Corporation Method and apparatus for a centralized facility for administering and performing connectivity and information management tasks for a mobile user
US6587835B1 (en) 2000-02-09 2003-07-01 G. Victor Treyz Shopping assistance with handheld computing device
US20010047397A1 (en) * 2000-02-18 2001-11-29 Jameson David H. Method and system for using pervasive device to access webpages
US6993575B2 (en) 2000-02-22 2006-01-31 Oracle International Corporation Using one device to configure and emulate web site content to be displayed on another device
US6714992B1 (en) 2000-02-25 2004-03-30 Navic Systems, Inc. Method and system for embedded network device installation
US6665709B1 (en) 2000-03-27 2003-12-16 Securit-E-Doc, Inc. Method, apparatus, and system for secure data transport
US7072984B1 (en) * 2000-04-26 2006-07-04 Novarra, Inc. System and method for accessing customized information over the internet using a browser for a plurality of electronic devices
US7210100B2 (en) 2000-09-27 2007-04-24 Eizel Technologies, Inc. Configurable transformation of electronic documents
US6447396B1 (en) 2000-10-17 2002-09-10 Nearlife, Inc. Method and apparatus for coordinating an interactive computer game with a broadcast television program
US20020073235A1 (en) * 2000-12-11 2002-06-13 Chen Steve X. System and method for content distillation
US6961776B1 (en) 2000-12-22 2005-11-01 Nortel Networks Limited Architecture for multiple channel access to applications
US20020082912A1 (en) 2000-12-22 2002-06-27 Leon Batachia Transactions between vendors and customers using push/pull model
US6848542B2 (en) 2001-04-27 2005-02-01 Accenture Llp Method for passive mining of usage information in a location-based services system
US8135803B2 (en) 2004-08-23 2012-03-13 Ianywhere Solutions, Inc. Method, system, and computer program product for offline advertisement servicing and cycling

Patent Citations (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5666553A (en) * 1992-04-10 1997-09-09 Puma Technology, Inc. Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5392390A (en) * 1992-04-10 1995-02-21 Intellilink Corp. Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5928329A (en) * 1992-12-02 1999-07-27 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels therebetween
US5666530A (en) * 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
US6151610A (en) * 1993-12-27 2000-11-21 Digital Equipment Corporation Document display system using a scripting language having container variables setting document attributes
US6029195A (en) * 1994-11-29 2000-02-22 Herz; Frederick S. M. System for customized electronic identification of desirable objects
US6000000A (en) * 1995-10-13 1999-12-07 3Com Corporation Extendible method and apparatus for synchronizing multiple files on two different computer systems
US5884323A (en) * 1995-10-13 1999-03-16 3Com Corporation Extendible method and apparatus for synchronizing files on two different computer systems
US5727202A (en) * 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US5832489A (en) * 1995-10-18 1998-11-03 3 Com Corporation Method and apparatus for synchronizing information on two different computer systems
US5905856A (en) * 1996-02-29 1999-05-18 Bankers Trust Australia Limited Determination of software functionality
US5727159A (en) * 1996-04-10 1998-03-10 Kikinis; Dan System in which a Proxy-Server translates information received from the Internet into a form/format readily usable by low power portable computers
US5919247A (en) * 1996-07-24 1999-07-06 Marimba, Inc. Method for the distribution of code and data updates
US5974238A (en) * 1996-08-07 1999-10-26 Compaq Computer Corporation Automatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elements
US6012083A (en) * 1996-09-24 2000-01-04 Ricoh Company Ltd. Method and apparatus for document processing using agents to process transactions created based on document content
US6006274A (en) * 1997-01-30 1999-12-21 3Com Corporation Method and apparatus using a pass through personal computer connected to both a local communication link and a computer network for indentifying and synchronizing a preferred computer with a portable computer
US6266681B1 (en) * 1997-04-08 2001-07-24 Network Commerce Inc. Method and system for inserting code to conditionally incorporate a user interface component in an HTML document
US5943496A (en) * 1997-05-17 1999-08-24 Intertop Corporation Methods for developing and instantiating object classes using a java virtual machine extension
US6122658A (en) * 1997-07-03 2000-09-19 Microsoft Corporation Custom localized information in a networked server for display to an end user
US5917491A (en) * 1997-08-29 1999-06-29 Netscape Communications Corporation Page proxy
US6023701A (en) * 1997-09-25 2000-02-08 International Business Machines Corporation Skeleton page retrieval mode for web navigation
US6052735A (en) * 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6496979B1 (en) * 1997-10-24 2002-12-17 Microsoft Corporation System and method for managing application installation for a mobile device
US6148330A (en) * 1997-11-17 2000-11-14 Netscape Communications Corp. System and method for automatically generating content for a network channel
US6167441A (en) * 1997-11-21 2000-12-26 International Business Machines Corporation Customization of web pages based on requester type
US6236991B1 (en) * 1997-11-26 2001-05-22 International Business Machines Corp. Method and system for providing access for categorized information from online internet and intranet sources
US6449638B1 (en) * 1998-01-07 2002-09-10 Microsoft Corporation Channel definition architecture extension
US6311058B1 (en) * 1998-06-30 2001-10-30 Microsoft Corporation System for delivering data content over a low bit rate transmission channel
US6167255A (en) * 1998-07-29 2000-12-26 @Track Communications, Inc. System and method for providing menu data using a communication network
US6493758B1 (en) * 1998-09-08 2002-12-10 Microsoft Corporation Offline viewing of internet content with a mobile device
US6209111B1 (en) * 1998-11-09 2001-03-27 Microsoft Corporation Error correction on a mobile device
US6470378B1 (en) * 1999-03-31 2002-10-22 Intel Corporation Dynamic content customization in a clientserver environment
US6336137B1 (en) * 2000-03-31 2002-01-01 Siebel Systems, Inc. Web client-server system and method for incompatible page markup and presentation languages

Cited By (110)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7840647B2 (en) 1999-09-10 2010-11-23 Ianywhere Solutions, Inc. System, method, and computer program product for executing scripts on mobile devices
US8595308B1 (en) 1999-09-10 2013-11-26 Ianywhere Solutions, Inc. System, method, and computer program product for server side processing in a mobile device environment
US7987420B1 (en) 1999-09-10 2011-07-26 Ianywhere Solutions, Inc. System, method, and computer program product for a scalable, configurable, client/server, cross-platform browser for mobile devices
US20060200751A1 (en) * 1999-11-05 2006-09-07 Decentrix Inc. Method and apparatus for providing conditional customization for generating a web site
US9456048B2 (en) 1999-12-30 2016-09-27 Ianywhere Solutions, Inc. System, method, and computer program product for server side processing in a mobile device environment
US7512667B2 (en) * 2001-01-15 2009-03-31 Sharp Kabushuki Kaisha Control system
US20040064551A1 (en) * 2001-01-15 2004-04-01 Miki Amano Control system
US20020120940A1 (en) * 2001-02-02 2002-08-29 Open Tv Method and apparatus compilation of an interpretative language for interactive television
US7065752B2 (en) * 2001-02-02 2006-06-20 Opentv, Inc. Method and apparatus compilation of an interpretative language for interactive television
US20030033517A1 (en) * 2001-06-01 2003-02-13 Rutherglen Jason John Secure data accessing system and method
US7428752B2 (en) * 2001-06-01 2008-09-23 Applications In Internet Time, Llc Secure data accessing system and method
US20030070158A1 (en) * 2001-07-02 2003-04-10 Lucas Terry L. Programming language extensions for processing data representation language objects and related applications
US6918107B2 (en) * 2001-07-02 2005-07-12 Bea Systems, Inc. Programming language extensions for processing data representation language objects and related applications
US20050278710A1 (en) * 2001-07-02 2005-12-15 Lucas Terry L Programming extensions for processing language objects and related applications
US20030018898A1 (en) * 2001-07-23 2003-01-23 Lection David B. Method, system, and computer-program product for providing selective access to certain child nodes of a document object model (DOM)
US6976211B2 (en) * 2001-07-23 2005-12-13 International Business Machines Corporation Method, system, and computer-program product for providing selective access to certain child nodes of a document object model (DOM)
US20100049721A1 (en) * 2001-11-01 2010-02-25 Anderson Jeffrey G Local Agent for Remote File Access System
US20030167256A1 (en) * 2002-01-18 2003-09-04 Seth White System and method for read-only entity bean caching
US7136879B2 (en) * 2002-01-18 2006-11-14 Bea Systems, Inc. System and method for read-only entity bean caching
US20030172186A1 (en) * 2002-03-07 2003-09-11 International Business Machines Coporation Method, system and program product for transcoding content
US10055090B2 (en) 2002-03-19 2018-08-21 Facebook, Inc. Constraining display motion in display navigation
US9886163B2 (en) 2002-03-19 2018-02-06 Facebook, Inc. Constrained display navigation
US9851864B2 (en) 2002-03-19 2017-12-26 Facebook, Inc. Constraining display in display navigation
US9041737B2 (en) 2002-03-19 2015-05-26 Facebook, Inc. Display navigation using navigation controls
US9753606B2 (en) 2002-03-19 2017-09-05 Facebook, Inc. Animated display navigation
US9678621B2 (en) 2002-03-19 2017-06-13 Facebook, Inc. Constraining display motion in display navigation
US20030182628A1 (en) * 2002-03-19 2003-09-25 Luigi Lira Reformatting columns of content for display
US20070109277A1 (en) * 2002-03-19 2007-05-17 America Online, Inc. Constraining display motion in display navigation
US8902253B2 (en) 2002-03-19 2014-12-02 Facebook, Inc. Constrained display navigation
US20080030477A1 (en) * 2002-03-19 2008-02-07 Aol Llc Display Motion Multiplier
US9626073B2 (en) 2002-03-19 2017-04-18 Facebook, Inc. Display navigation
US9041738B2 (en) 2002-03-19 2015-05-26 Facebook, Inc. Display navigation
US7487444B2 (en) 2002-03-19 2009-02-03 Aol Llc Reformatting columns of content for display
US8648801B2 (en) 2002-03-19 2014-02-11 Facebook, Inc. Aligned display navigation
US9360993B2 (en) 2002-03-19 2016-06-07 Facebook, Inc. Display navigation
US7872640B2 (en) 2002-03-19 2011-01-18 Aol Inc. Constraining display motion in display navigation
US20030217169A1 (en) * 2002-03-21 2003-11-20 International Business Machines Corporation High-speed content transformation engine
US8484282B2 (en) 2002-03-21 2013-07-09 International Business Machines Corporation High-speed content transformation engine
US20040004641A1 (en) * 2002-07-02 2004-01-08 Ullas Gargi Image segmentation and warping for specialized display viewing
US7278117B2 (en) * 2002-07-02 2007-10-02 Hewlett-Packard Development Company, L.P. Image segmentation and warping for specialized display viewing
US8245128B1 (en) * 2002-07-17 2012-08-14 Oracle International Corporation Intelligent client agent for a hybrid online/offline application
US7383339B1 (en) * 2002-07-31 2008-06-03 Aol Llc, A Delaware Limited Liability Company Local proxy server for establishing device controls
US20040024843A1 (en) * 2002-07-31 2004-02-05 Smith Christopher T. Method for provisioning distributed web applications
US20060200535A1 (en) * 2002-08-02 2006-09-07 Martin Moser Method and computer system for handling incremental data in client-server communication
US20040107403A1 (en) * 2002-09-05 2004-06-03 Tetzchner Jon Stephensen Von Presenting HTML content on a small screen terminal display
US9390191B2 (en) 2002-09-10 2016-07-12 SQGo, LLC Methods and systems for the provisioning and execution of a mobile software application
US9135227B2 (en) 2002-09-10 2015-09-15 SQGo, LLC Methods and systems for enabling the provisioning and execution of a platform-independent application
US9311284B2 (en) 2002-09-10 2016-04-12 SQGo, LLC Methods and systems for enabling the provisioning and execution of a platform-independent application
US9342492B1 (en) 2002-09-10 2016-05-17 SQGo, LLC Methods and systems for the provisioning and execution of a mobile software application
US20040225747A1 (en) * 2003-05-09 2004-11-11 Zafer Kadi Providing compiled bytecode applications to a wireless device
US7380242B2 (en) * 2003-05-14 2008-05-27 Mainsoft Israel Ltd. Compiler and software product for compiling intermediate language bytecodes into Java bytecodes
US7913237B2 (en) * 2003-08-26 2011-03-22 Ensequence, Inc. Compile-time code validation based on configurable virtual machine
US20050081061A1 (en) * 2003-08-26 2005-04-14 Acott Troy Steven Compile-time code validation based on configurable virtual machine
US7437457B1 (en) 2003-09-08 2008-10-14 Aol Llc, A Delaware Limited Liability Company Regulating concurrent logins associated with a single account
US20050289450A1 (en) * 2004-06-23 2005-12-29 Microsoft Corporation User interface virtualization
US7676801B1 (en) * 2004-08-31 2010-03-09 Sun Microsystems, Inc. Scanning of evacuated objects in a generation managed by the train algorithm
US20060073785A1 (en) * 2004-10-05 2006-04-06 Research In Motion Limited Mobile device diagnosis, test, application deployment and update from a web page
US8818349B2 (en) * 2004-10-05 2014-08-26 Blackberry Limited Mobile device diagnosis, test, application deployment and update from a web page
US7818728B1 (en) * 2005-04-04 2010-10-19 Qd Technology Llc Maximizing system resources used to decompress read-only compressed analytic data in a relational database table
US20100325096A1 (en) * 2005-04-04 2010-12-23 Qd Technology, Llc Maximizing system resources used to decompress read-only compressed analytic data in a relational database table
US20100332462A1 (en) * 2005-04-04 2010-12-30 Qd Technology, Llc Maximizing system resources used to decompress read-only compressed analytic data in a relational database table
US20060230226A1 (en) * 2005-04-12 2006-10-12 M-Systems Flash Disk Pioneers, Ltd. Hard disk drive with optional cache memory
US7953098B2 (en) * 2005-06-14 2011-05-31 Hitachi Global Storage Technologies, Netherlands B.V. Method for limiting utilizing terminal of contents, and storage device and system for method
US20060282511A1 (en) * 2005-06-14 2006-12-14 Hitachi Global Storage Technologies Netherlands B.V. Method for limiting utilizing terminal of contents, and memory device and system for method
US20110029605A1 (en) * 2005-08-31 2011-02-03 Research In Motion Limited Method, System and Apparatus for Selective Application Access and Synchronization
US20070050502A1 (en) * 2005-08-31 2007-03-01 Research In Motion Limited Method, system and apparatus for selective application access and synchronization
US7840710B2 (en) * 2005-08-31 2010-11-23 Research In Motion Limited Method, system and apparatus for selective application access and synchronization
US8171172B2 (en) * 2005-08-31 2012-05-01 Research In Motion Limited Method, system and apparatus for selective application access and synchronization
US20070061700A1 (en) * 2005-09-12 2007-03-15 Microsoft Corporation Initial server-side content rendering for client-script web pages
US7814410B2 (en) * 2005-09-12 2010-10-12 Workman Nydegger Initial server-side content rendering for client-script web pages
US8176416B1 (en) 2006-03-17 2012-05-08 Wells Fargo Bank, N.A. System and method for delivering a device-independent web page
US8661119B1 (en) * 2006-06-30 2014-02-25 Google Inc. Determining a number of users behind a set of one or more internet protocol (IP) addresses
US7761558B1 (en) * 2006-06-30 2010-07-20 Google Inc. Determining a number of users behind a set of one or more internet protocol (IP) addresses
WO2008039700A2 (en) * 2006-09-26 2008-04-03 Swift Creek Systems, Llc Method for enabling dynamic content in a markup language based page using a dynamic markup language element
WO2008039700A3 (en) * 2006-09-26 2008-07-03 Swift Creek Systems Llc Method for enabling dynamic content in a markup language based page using a dynamic markup language element
US8181107B2 (en) 2006-12-08 2012-05-15 Bytemobile, Inc. Content adaptation
US20080139191A1 (en) * 2006-12-08 2008-06-12 Miguel Melnyk Content adaptation
US9275167B2 (en) 2006-12-08 2016-03-01 Citrix Systems, Inc. Content adaptation
WO2008073207A3 (en) * 2006-12-08 2009-01-15 Bytemobile Inc Content adaptation
US9292618B2 (en) 2006-12-08 2016-03-22 Citrix Systems, Inc. Content adaptation
WO2008073207A2 (en) * 2006-12-08 2008-06-19 Bytemobile, Inc. Content adaptation
US20090063530A1 (en) * 2007-09-04 2009-03-05 Lg Telecom Ltd. System and method for mobile web service
US9547755B2 (en) * 2008-03-10 2017-01-17 Jill Lewis Maurer Digital media content creation and distribution methods
US20160098546A1 (en) * 2008-03-10 2016-04-07 Jill Lewis Maurer Digital Media Content Creation and Distribution Methods
US20100005410A1 (en) * 2008-07-03 2010-01-07 Pang Xin Mobile device application framework
US20100023699A1 (en) * 2008-07-22 2010-01-28 Bridgewater Systems Corp. System and Method for Usage Analyzer of Subscriber Access to Communications Network
US8566527B2 (en) * 2008-07-22 2013-10-22 Bridgewater Systems Corp. System and method for usage analyzer of subscriber access to communications network
US9082409B2 (en) * 2008-08-28 2015-07-14 Avaya Inc. Binary-caching for XML documents with embedded executable code
US20100057468A1 (en) * 2008-08-28 2010-03-04 Nortel Networks Limited Binary-caching for xml documents with embedded executable code
US20100088591A1 (en) * 2008-10-03 2010-04-08 Google Inc. Vertical Content on Small Display Devices
US9087337B2 (en) * 2008-10-03 2015-07-21 Google Inc. Displaying vertical content on small display devices
US8612947B2 (en) * 2009-07-31 2013-12-17 Adobe Systems Canada Inc. System and method for remotely compiling multi-platform native applications for mobile devices
US20110154305A1 (en) * 2009-07-31 2011-06-23 Leroux Brian System and method for remotely compiling multi-platform native applications for mobile devices
US20120150993A1 (en) * 2010-10-29 2012-06-14 Akamai Technologies, Inc. Assisted delivery of content adapted for a requesting client
US9418353B2 (en) 2010-12-20 2016-08-16 Akamai Technologies, Inc. Methods and systems for delivering content to differentiated client devices
US8838873B2 (en) 2011-06-15 2014-09-16 Data Design Corporation Methods and apparatus for data access by a reprogrammable circuit module
US9417894B1 (en) 2011-06-15 2016-08-16 Ryft Systems, Inc. Methods and apparatus for a tablet computer system incorporating a reprogrammable circuit module
US9736258B2 (en) 2011-12-23 2017-08-15 Akamai Technologies, Inc. Assessment of content delivery services using performance measurements from within an end user client application
US9742858B2 (en) 2011-12-23 2017-08-22 Akamai Technologies Inc. Assessment of content delivery services using performance measurements from within an end user client application
US9037803B2 (en) * 2012-07-27 2015-05-19 International Business Machines Corporation Randomized page weights for optimizing buffer pool page reuse
US20140032852A1 (en) * 2012-07-27 2014-01-30 International Business Machines Corporation Randomized page weights for optimizing buffer pool page reuse
US20140032851A1 (en) * 2012-07-27 2014-01-30 International Business Machines Corporation Randomized page weights for optimizing buffer pool page reuse
US9825812B2 (en) * 2013-12-05 2017-11-21 Pulse Secure, Llc Transparently intercepting and optimizing resource requests
US20150163087A1 (en) * 2013-12-05 2015-06-11 Riverbed Technology, Inc. Transparently intercepting and optimizing resource requests
US9749440B2 (en) 2013-12-31 2017-08-29 Sweetlabs, Inc. Systems and methods for hosted application marketplaces
US10084878B2 (en) 2013-12-31 2018-09-25 Sweetlabs, Inc. Systems and methods for hosted application marketplaces
EP3090357A4 (en) * 2013-12-31 2017-05-31 Sweetlabs, Inc. Hosted application marketplaces
US10019247B2 (en) 2014-05-15 2018-07-10 Sweetlabs, Inc. Systems and methods for application installation platforms
US10089098B2 (en) 2014-05-15 2018-10-02 Sweetlabs, Inc. Systems and methods for application installation platforms
US20170230544A1 (en) * 2014-06-24 2017-08-10 Ec Data Systems Inc. Audit logging for a secure, scalable and flexible internet fax architecture

Also Published As

Publication number Publication date Type
US7840647B2 (en) 2010-11-23 grant
US20060136571A1 (en) 2006-06-22 application

Similar Documents

Publication Publication Date Title
US6981210B2 (en) Self-maintaining web browser bookmarks
US6353926B1 (en) Software update notification
US5991760A (en) Method and apparatus for modifying copies of remotely stored documents using a web browser
US6523062B1 (en) Facilitating memory constrained client devices by employing deck reduction techniques
US6553412B1 (en) System, method, and computer program product for web content aggregation and development, and web content delivery to clients
US6571245B2 (en) Virtual desktop in a computer network
US6715129B1 (en) Achieving application-specific document content by transcoding using Java Server Pages
US6596030B2 (en) Identifying changes in on-line data repositories
US6941511B1 (en) High-performance extensible document transformation
US6757900B1 (en) State management of server-side control objects
US6766313B1 (en) System and method for caching and retrieving information
US6920488B1 (en) Server assisted system for accessing web pages from a personal data assistant
US6031989A (en) Method of formatting and displaying nested documents
US7149776B1 (en) System and method for real-time co-browsing
US7747782B2 (en) System and method for providing and displaying information content
Douglis et al. The AT&T Internet Difference Engine: Tracking and viewing changes on the web
US6585778B1 (en) Enforcing data policy using style sheet processing
US20040015953A1 (en) Automatically updating software components across network as needed
US7636792B1 (en) Methods and systems for dynamic and automatic content creation for mobile devices
US6606525B1 (en) System and method of merging static data in web pages
US20050091670A1 (en) Programming interface for a computer platform
US6535896B2 (en) Systems, methods and computer program products for tailoring web page content in hypertext markup language format for display within pervasive computing devices using extensible markup language tools
US20020062325A1 (en) Configurable transformation of electronic documents
US20020147749A1 (en) Mobile presentation system
US8595186B1 (en) System and method for building and delivering mobile widgets

Legal Events

Date Code Title Description
AS Assignment

Owner name: AVANTGO, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KLOBA, DAVID D.;GRAY, MICHAEL R.;MOORE, DAVID M.;AND OTHERS;REEL/FRAME:011884/0616;SIGNING DATES FROM 20010412 TO 20010426

AS Assignment

Owner name: IANYWHERE SOLUTIONS, INC., CALIFORNIA

Free format text: BILL OF SALE;ASSIGNOR:AVANTGO, INC.;REEL/FRAME:014468/0087

Effective date: 20031218