# US 2006/0168101 A1 · Proactive browser system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0168101 A1
- Document ID: US20060168101A1
- Status: Published application
- Kind: A1
- Application number: 11/317,731
- Filed: 2005-12-23
- Published: 2006-07-27
- Earliest claimed: 2001-07-20
- Assignees: Flowfinity Wireless, Inc.
- Inventors: Dmytro Mikhailov; Olga Sboychakova; Geoffrey Hansen
- Web page: https://patentgrep.com/patent/US20060168101A1

## CPC

- H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
- G06F 16/95: Retrieval from the web
- G06K 13/0825: {the ejection arrangement being of the push-push kind}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/75: Indicating network or usage conditions on the user display
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06K: GRAPHICAL DATA READING (image or video recognition or understanding G06V); PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS

## Abstract

A proactive browser system configured to implement stateful frame navigation using content specific icons, background frame maintenance, and asynchronous frame submissions. The proactive browser system includes three components: user-side proactive application terminals (PAT), network-resident proactivity enablement servers (PES), and server-side proactive wireless web-based application servers. The PAT resides on user terminals and functions as an enhanced browser that accommodates proactive application services. The PES resides in the wireless network between the proactive application servers and the user terminals, and implements proactivity support services including queuing of proactive application submissions, presence detection of proactive application terminals, and routing of proactive application submissions from proactive application servers to the proactive application terminals. The proactive application servers are web-based application servers configured to provide proactive application services to take advantage of the enhanced capabilities enabled by the PAT and PES components.

## Claims

### Claim at position 1

1-24. (canceled)

### Claim 25

A network-based proactive application system comprising:
a proactive application terminal operable for running a browser configured to implement a current browser page that is configured for user interaction with a wireless network-based application server;
the browser further configured to implement a background browser page in an initial state that is not configured for user interaction; and
a proactive application server configured to detect a triggering event and, in response to the triggering event, to automatically interact with the background browser page to alter the background browser page from the initial state to an updated state without interrupting the user interaction with the current browser page; and
the browser further configured to activate the background browser page in the updated state for user interaction.

### Claim 26 (depends on 25)

The network-based proactive application system of claim 25, further comprising a proactivity enablement server located in a communication path between the proactive application terminal and the proactive application server, the proactivity enablement server configured to:
queue submission from the proactive application server to the proactive application terminal;
detect on-line presence of the proactive application terminal; and
route a submission to the proactive application terminal upon detection of the on-line presence of the proactive application terminal.

### Claim 27 (depends on 26)

The network-based proactive application system of claim 26, wherein the proactivity enablement server of claim 26 is further configured to:
receive presence notification messages from the proactive application terminal; and
send a notification message to the proactive application server corresponding to the presence notification messages from the proactive application terminal.

### Claim 28

A method for implementing a network-based proactive application system including a proactive application terminal running a browser displaying a first browser page downloaded from a network-based proactive application server, comprising the steps of:
at the proactive application server:
monitoring network presence of the proactive application terminal,
entering an off-line interaction mode in response to detecting a lack of network presence of the proactive application terminal,
during the off-line interaction mode, receiving and queuing updates for the first browser page from the proactive application server,
entering an on-line interaction mode in response to detecting network presence of the proactive application terminal, and
during the on-line interaction mode, transmitting the queued updates for the first browser page to the proactive application terminal; and
at the proactive application terminal:
monitoring network presence of the proactive application terminal,
entering an off-line interaction mode in response to detecting a lack of network presence of the proactive application terminal,
during the off-line interaction mode, receiving and queuing user submissions directed to the proactive application server from the first browser page,
entering an on-line interaction mode in response to detecting network presence of the proactive application terminal, and
during the on-line interaction mode, transmitting the queued user submissions to the proactive application server and ignoring corresponding responses from the proactive application server.

### Claim 29 (depends on 28)

The method of claim 28, further comprising the step of, at the proactive application terminal in response to receiving the queued updates for the first browser page to the proactive application terminal, activating the first browser page as a current browser page that is configured for user interaction and loading the updates into the first page upon receipt from the proactive application terminal.

### Claim 30 (depends on 28)

The method of claim 28, further comprising the steps of, at the proactive application terminal:
prior to receiving the queued updates for the first browser page, activating a second browser page as a current browser page that is configured for user interaction;
maintaining the first browser page as a background browser page that is not configured for user interaction;
loading the updates into the first browser page without interrupting the user interaction with the second browser page.

### Claim 31

A method for reverse posting document parameters from an proactive application server to a browser residing on a client terminal, comprising the steps of downloading a document from the proactive application server to the client terminal, and on the client terminal:
loading the document into the browser;
converting the document into a document template resident within the browser, the document template comprising variable parameters;
receiving a request to update the document;
in response to the request, downloading updated variable parameters from the proactive application server to the client terminal; and
updating the variable parameters within the document template without reloading the document from the proactive application server into the browser.

### Claim 32 (depends on 31)

The method of claim 31, wherein the request to update comprises a pull request initiated by the client terminal.

### Claim 33 (depends on 31)

The method of claim 31, wherein the request to update comprises a push request initiated by the proactive application server.

### Claim 34

A method for implementing editable browser pages on a client terminal running a browser, comprising the steps of downloading a document in an initial format from an proactive application server to the client terminal, and on the client terminal:
loading the document into a browser page running on the browser;
converting the document into a document template resident within the browser page comprising editable variable parameters corresponding to data contained in the document that is non-editable by the browser in the initial format;
receiving edits to the variable parameters entered through the browser page; and
updating the variable parameters within the document template without reloading the document into the browser page from the proactive application server.

### Claim 35 (depends on 28)

An apparatus configured to perform the method of claim 28 or a computer storage medium storing computer executable instructions for causing the apparatus to perform the method of claim 28.

### Claim 36 (depends on 31)

An apparatus configured to perform the method of claim 31 or a computer storage medium storing computer executable instructions for causing the apparatus to perform the method of claim 31.

### Claim 37 (depends on 34)

An apparatus configured to perform the method of claim 34 or a computer storage medium storing computer executable instructions for causing the apparatus to perform the method of claim 34.
