# US 2003/0206192 A1 · Asynchronous message push to web browser

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

- Number: US 2003/0206192 A1
- Document ID: US20030206192A1
- Status: Published application
- Kind: A1
- Application number: 10/033,146
- Filed: 2001-10-27
- Published: 2003-11-06
- Earliest claimed: 2001-03-31
- Inventors: Mingte Chen; Sing Yip; Yan Ma; Gilberto Arnaiz; Srikant Krishnapuram Tirumalai; David Tchankotadze; Kuang Huang; Anil Kumar Annadata
- Web page: https://patentgrep.com/patent/US20030206192A1

## CPC

- H04M 3/5191: {interacting with the Internet}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/55: Push-based network services
- H04L 67/75: Indicating network or usage conditions on the user display
- H04L 69/329: in the application layer [OSI layer 7]
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method and system for controlling a user interface presented by a web browser. A web server pushes an asynchronous message to the web browser. The web browser is not blocked waiting for the asynchronous message. The web browser presents a user interface and presents a user interface change in response to receiving the asynchronous message.

## Claims

### Claim 1

A method for communicating comprising:
controlling a user interface presented by a web browser comprising:
causing a web server to push an asynchronous message to the web browser;
wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
generating the asynchronous message.

### Claim 3 (depends on 1)

The method of claim 1 further comprising:
preparing to receive the asynchronous message.

### Claim 4 (depends on 3)

The method of claim 3 wherein the preparing comprises:
causing the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
identifying a source of the asynchronous message; and
associating the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message.

### Claim 5 (depends on 1)

The method of claim 1 further comprising:
causing the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
identifying a source of the asynchronous message; and
associating the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message.

### Claim 6 (depends on 1)

The method of claim 1 further comprising:
causing the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
generating the asynchronous message, the asynchronous message identifying the wait request, wherein the identifying identifies the web browser as a recipient of the asynchronous message; and
providing the asynchronous message to the web server.

### Claim 7 (depends on 6)

The method of claim 6 wherein causing the web browser to provide the wait request comprises:
downloading requesting instructions to the web browser, wherein
the downloading causes the web browser to execute the requesting instructions.

### Claim 8 (depends on 6)

The method of claim 6 further comprising:
storing a reference to a callback function with information from the wait request; and
using the reference to call the callback function when the asynchronous message is provided to the web server, wherein the callback function pushes the asynchronous message.

### Claim 9 (depends on 8)

The method of claim 8 further comprising:
providing the callback function with context information, the context information identifying the web browser.

### Claim 10 (depends on 6)

The method of claim 6 further comprising:
assigning the wait request to a connection between the web server and a business process server; and
listening to the connection for the asynchronous message.

### Claim 11 (depends on 6)

The method of claim 6 further comprising:
assigning the wait request to a session between the web server and a business process server, the session being associated with a connection; and
listening to the connection for the asynchronous message for the session.

### Claim 12 (depends on 1)

The method of claim 1 wherein causing the web server to push the asynchronous message comprises:
calling a callback function associated with the web browser when the asynchronous message is received, wherein the callback function pushes the asynchronous message.

### Claim 13 (depends on 12)

The method of claim 12 further comprising:
storing a reference to the callback function; and
using the reference for calling the callback function.

### Claim 14 (depends on 13)

The method of claim 13 further comprising:
storing a second reference to context information, the context information identifying the web browser; and
using the second reference for providing the context information to the callback function.

### Claim 15 (depends on 1)

The method of claim 1 wherein
the user interface change comprises at least one of a group consisting of the following:
causing a first user interface object to move to visually capture a user's attention;
causing a second user interface object to issue a sound to capture the user's attention;
presenting a screen pop of data; and
bringing a web browser window to front of screen.

### Claim 16

A method for communicating comprising:
causing a web server to push an asynchronous message to a web browser, wherein
the web browser performs an action in response to the asynchronous message.

### Claim 17 (depends on 16)

The method of claim 16 wherein
the asynchronous message includes an action instruction to cause the web browser to perform the action.

### Claim 18 (depends on 16)

The method of claim 16 wherein the performing the action comprises performing at least one of a group consisting of the following:
causing a first user interface object to move to visually capture a user's attention;
causing a second user interface object to issue a sound to capture the user's attention;
presenting a screen pop of data; and
bringing a web browser window to front of screen.

### Claim 19

A method for communicating comprising:
establishing a first connection between a web browser and a web server;
establishing a second connection between the web server and a business process server;
controlling a user interface presented by the web browser comprising:
registering the web browser with the business process server;
providing the web server with an asynchronous message to push to the web browser, the providing being performed by the business process server; and
causing the web server to push the asynchronous message to the web browser;
wherein the web browser performs a user interface change in response to the asynchronous message.

### Claim 20

A method for communicating comprising:
controlling a user interface presented by a web browser comprising:
registering the web browser as available to receive an asynchronous message, wherein
the web browser is not blocked waiting for the asynchronous message; and
causing a web server to push the asynchronous message to the web browser;
wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 21

A method for communicating comprising:
controlling a user interface presented by a web browser comprising:
causing the web browser to provide a wait request to a web server, the wait request being associated with the web browser;
identifying a source of an asynchronous message;
associating the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message; and
pushing the asynchronous message to the web browser;
wherein the browser presents a user interface change in response to the asynchronous message.

### Claim 22

A method for communicating comprising:
controlling a user interface presented by a web browser comprising:
causing the web browser to provide a wait request to a web server, wherein
the wait request is associated with the web browser and a target from which an asynchronous message originates;
generating the asynchronous message, the asynchronous message identifying the web browser as a recipient of the asynchronous message, the generating being performed by the target;
providing the asynchronous message to the web server; and
causing the web server to push the asynchronous message to the web browser;
wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 23

A computer program product comprising:
controlling instructions to control a user interface presented by a web browser comprising:
pushing instructions to cause a web server to push an asynchronous message to the web browser, wherein
the web browser presents a user interface change in response to the asynchronous message; and
a computer-readable medium for storing the controlling instructions and the pushing instructions.

### Claim 24 (depends on 23)

The computer program product of claim 23 further comprising:
providing instructions to cause the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
identifying instructions to identify a source of the asynchronous message; and
associating instructions to associate the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message;
wherein the computer-readable medium further stores the providing instructions, the identifying instructions, and the associating instructions.

### Claim 25 (depends on 23)

The computer program product of claim 23 further comprising:
request providing instructions to cause the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
generating instructions to generate the asynchronous message, the asynchronous message identifying the wait request, wherein the identifying identifies the web browser as a recipient of the asynchronous message; and
message providing instructions to provide the asynchronous message to the web server;
wherein the computer-readable medium further stores the request providing instructions, the generating instructions, and the message providing instructions.

### Claim 26 (depends on 25)

The computer program product of claim 25 further comprising:
storing instructions to store a reference to a callback function with information from the wait request; and
using instructions to use the reference to call the callback function when the asynchronous message is provided to the web server, wherein the callback function pushes the asynchronous message;
wherein the computer-readable medium further stores the storing instructions and the using instructions.

### Claim 27 (depends on 26)

The computer program product of claim 26 further comprising:
context providing instructions to provide the callback function with context information, the context information identifying the web browser;
wherein the computer-readable medium further stores the context providing instructions.

### Claim 28 (depends on 25)

The computer program product of claim 25 further comprising:
assigning instructions to assign the wait request to a connection between the web server and a business process server; and
listening instructions to listen to the connection for the asynchronous message;
wherein the computer-readable medium further stores the assigning instructions and the listening instructions.

### Claim 29 (depends on 23)

The computer program product of claim 23 wherein
the pushing instructions comprise:
calling instructions to call a callback function associated with the web browser when the asynchronous message is received, wherein the callback function pushes the asynchronous message; and
the computer-readable medium further stores the calling instructions.

### Claim 30 (depends on 29)

The computer program product of claim 29 further comprising:
reference storing instructions to store a reference to the callback function; and reference using instructions to use the reference for calling the callback function;
wherein the computer-readable medium further stores the reference storing instructions and the reference using instructions.

### Claim 31 (depends on 30)

The computer program product of claim 30 further comprising:
context storing instructions to store a second reference to context information, the context information identifying the web browser; and
context using instructions to use the second reference for providing the context information to the callback function;
wherein the computer-readable medium further stores the context storing instructions and the context using instructions.

### Claim 32 (depends on 23)

The computer program product of claim 23 further comprising:
user interface changing instructions configured to perform at least one of a group consisting of the following:
cause a first user interface object to move to visually capture a user's attention;
cause a second user interface object to issue a sound to capture the user's attention;
present a screen pop of data; and
bring a web browser window to front of screen;
wherein the computer-readable medium further stores the user interface changing instructions.

### Claim 33

A computer program product comprising:
controlling instructions to control a user interface presented by a web browser comprising:
registering instructions to register the web browser as available to receive an asynchronous message, wherein
the web browser is not blocked waiting for the asynchronous message; and
pushing instructions to cause a web server to push the asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message; and
a computer-readable medium for storing the controlling instructions, the registering instructions, and the pushing instructions.

### Claim 34

A computer system comprising:
a processor;
a memory, the memory storing instructions for executing on the processor, the instructions comprising:
controlling instructions to control a user interface presented by a web browser comprising:
pushing instructions to cause a web server to push an asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 35 (depends on 34)

The computer system of claim 34 wherein the instructions further comprise:
providing instructions to cause the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
identifying instructions to identify a source of the asynchronous message; and
associating instructions to associate the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message.

### Claim 36 (depends on 34)

The computer system of claim 34 wherein the instructions further comprise:
request providing instructions to cause the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
generating instructions to generate the asynchronous message, the asynchronous message identifying the wait request, wherein the identifying identifies the web browser as a recipient of the asynchronous message; and
message providing instructions to provide the asynchronous message to the web server.

### Claim 37 (depends on 36)

The computer system of claim 36 wherein the instructions further comprise:
storing instructions to store a reference to a callback function with information from the wait request; and
using instructions to use the reference to call the callback function when the asynchronous message is provided to the web server, wherein the callback function pushes the asynchronous message.

### Claim 38 (depends on 37)

The computer system of claim 37 wherein the instructions further comprise:
context providing instructions to provide the callback function with context information, the context information identifying the web browser.

### Claim 39 (depends on 36)

The computer system of claim 36 wherein the instructions further comprise:
assigning instructions to assign the wait request to a connection between the web server and a business process server; and
listening instructions to listen to the connection for the asynchronous message.

### Claim 40 (depends on 34)

The computer system of claim 34 wherein the pushing instructions comprise:
calling instructions to call a callback function associated with the web browser when the asynchronous message is received, wherein the callback function pushes the asynchronous message.

### Claim 41 (depends on 40)

The computer system of claim 40 wherein the instructions further comprise:
reference storing instructions to store a reference to the callback function; and
reference using instructions to use the reference for calling the callback function.

### Claim 42 (depends on 41)

The computer system of claim 41 wherein the instructions further comprise:
context storing instructions to store a second reference to context information, the context information identifying the web browser; and
context using instructions to use the second reference for providing the context information to the callback function.

### Claim 43 (depends on 34)

The computer system of claim 34 wherein the instructions further comprise:
user interface changing instructions configured to perform at least one of a group consisting of the following:
cause a first user interface object to move to visually capture a user's attention;
cause a second user interface object to issue a sound to capture the user's attention;
present a screen pop of data; and
bring a web browser window to front of screen.

### Claim 44

A computer system comprising:
a processor;
a memory, the memory storing instructions for executing on the processor, the instructions comprising:
controlling instructions to control a user interface presented by a web browser comprising:
registering instructions to register the web browser as available to receive an asynchronous message, wherein the web browser is not blocked waiting for the asynchronous message; and
pushing instructions to cause a web server to push the asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 45

A system comprising:
controlling means for controlling a user interface presented by a web browser comprising:
pushing means for causing a web server to push an asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 46 (depends on 45)

The system of claim 45 further comprising:
providing means for causing the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
identifying means for identifying a source of the asynchronous message; and
associating means for associating the wait request with the source, wherein the associating identifies the web browser as a recipient of the asynchronous message.

### Claim 47 (depends on 45)

The system of claim 45 farther comprising:
request providing means for causing the web browser to provide a wait request to the web server, the wait request being associated with the web browser;
generating means for generating the asynchronous message, the asynchronous message identifying the wait request, wherein the identifying identifies the web browser as a recipient of the asynchronous message; and
message providing means for providing the asynchronous message to the web server.

### Claim 48 (depends on 47)

The system of claim 47 farther comprising:
storing means for storing a reference to a callback function with information from the wait request; and
using means for using the reference to call the callback function when the asynchronous message is provided to the web server, wherein the callback function pushes the asynchronous message.

### Claim 49 (depends on 48)

The system of claim 48 farther comprising:
context providing means for providing the callback function with context information, the context information identifying the web browser.

### Claim 50 (depends on 47)

The system of claim 47 further comprising:
assigning means for assigning the wait request to a connection between the web server and a business process server; and
listening means for listening to the connection for the asynchronous message.

### Claim 51 (depends on 45)

The system of claim 45 wherein the pushing means comprise:
calling means for calling a callback function associated with the web browser when the asynchronous message is received, wherein the callback function pushes the asynchronous message.

### Claim 52 (depends on 51)

The system of claim 51 further comprising:
reference storing means for storing a reference to the callback function; and reference using means for using the reference for calling the callback function.

### Claim 53 (depends on 52)

The system of claim 52 further comprising:
context storing means for storing a second reference to context information, the context information identifying the web browser; and
context using means for using the second reference for providing the context information to the callback function.

### Claim 54 (depends on 45)

The system of claim 45 further comprising:
user interface changing means configured to perform at least one of a group consisting of the following:
cause a first user interface object to move to visually capture a user's attention;
cause a second user interface object to issue a sound to capture the user's attention;
present a screen pop of data; and
bring a web browser window to front of screen.

### Claim 55

A system comprising:
controlling means for controlling a user interface presented by a web browser comprising:
registering means for registering the web browser as available to receive an asynchronous message, wherein
the web browser is not blocked waiting for the asynchronous message; and
pushing means for causing a web server to push the asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message.

### Claim 56

A signal embodied in a carrier wave comprising:
controlling instructions to control a user interface presented by a web browser comprising:
pushing instructions to cause a web server to push an asynchronous message to the web browser, wherein the web browser presents
a user interface change in response to the asynchronous message.

### Claim 57

A signal embodied in a carrier wave comprising:
controlling instructions to control a user interface presented by a web browser comprising:
registering instructions to register the web browser as available to receive an asynchronous message, wherein
the web browser is not blocked waiting for the asynchronous message; and
pushing instructions to cause a web server to push the asynchronous message to the web browser, wherein the web browser presents a user interface change in response to the asynchronous message.
