# US 7,412,478 B1 · Rich media file format and delivery methods

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

- Number: US 7,412,478 B1
- Document ID: US7412478B1
- Status: Granted
- Kind: B1
- Application number: 09/772,541
- Filed: 2001-01-29
- Granted: 2008-08-12
- Earliest claimed: 2000-01-27
- Assignees: Marger Johnson & McCollom, P.C.
- Inventors: Robert M. Caruso; Konstantin J. Balashov
- Web page: https://patentgrep.com/patent/US7412478B1

## CPC

- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- G06F 16/951: Indexing; Web crawling techniques
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 2463/102: applying security measure for e-commerce
- 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)

## Abstract

A rich media file is a self-contained file, including both the information to be viewed by a user and the viewer that displays the information to the user. The information can be formatted however the client likes: for example, the information can be split across several pages, and can include text and still and animated images. There can also be web links to pages on a network, and e-mail forms to simplify sending an e-mail message to the client. The rich media file can include viewing limitations, so that only the proper password can unlock the file, or that the rich media file will automatically expire after a specified condition occurs. The rich media file also assists the user in obtaining the latest version of the rich media file, by offering to retrieve a newer version for the user.

## Claims

### Claim 1

A rich media file stored in a machine-readable medium, comprising:
a client identifier to identify a creator of the rich media file;
a unique identifier to identify the rich media file;
a version number identifying a version of the rich media file;
a print module to enable printing of the rich media file if included by the creator of the rich media file and to disable printing if excluded by the creator;
a first dialogue box structured to appear responsive to viewing limits of the rich media file, the first dialogue box to communicate to a user an invitation to access another rich media file;
a second dialogue box structured to appear responsive to an update offer, the second dialogue box for prompting the user of the rich media file to check for a newer version of the rich media file;
a requester structured to retrieve the newer version of the rich media file responsive to an action by the user according to the update offer;
information to be displayed on a computer system, the information including text, at least one still image, and structured to include at least one of an animated image, a link to a web page, and an email link; and
a viewer built-in to the rich media file to display the information on the computer system,
wherein the client identifier, the unique identifier, the version number, the print module, the viewing limits, the update offer, the requester, the information to be displayed, and the built-in viewer comprise a single file.