# US 12,182,865 B2 · Exchange feed for trade reporting having reduced redundancy

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

- Number: US 12,182,865 B2
- Document ID: US12182865B2
- Status: Granted
- Kind: B2
- Application number: 18/495,198
- Filed: 2023-10-26
- Published: 2024-04-18
- Granted: 2024-12-31
- Earliest claimed: 2013-12-09
- Assignees: Chicago Mercantile Exchange Inc.
- Applicants: Chicago Mercantile Exchange Inc.
- Inventors: Paul Callaway; Fritz Caskey; Dennis Genetski; Pearce Peck-Walden; José Antonio Acuña-Rohter; Priteshkumar Soni; Rosa Frenkel
- Web page: https://patentgrep.com/patent/US12182865B2

## CPC

- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The disclosed embodiments relate to communication of messages from a database to participants whereby messages, or at least a portion of the content thereof, indicative of changes in the database, due to one or more transactions between two or more participants, are structured so as to reduce redundant data therein and prioritize the transmission of that portion of the message which summarizes the event and result thereof. Further, these event reporting messages may further consolidate, or otherwise be combined with, the corresponding directed reporting messages communicated to the particular participants participating in the reported transaction while preserving the anonymity of those participants to which messages are particularly directed.

## Claims

### Claim 1

A system including:
a transaction processor configured to determine a change in a state of a database as a result of a plurality of requests received from a plurality of sources;
a message generator configured to generate a change message including a notification portion and a request data portion, wherein the notification portion includes notification data conveying the change in the state of the database without identifying all of the plurality of requests and the request data portion includes request data identifying at least one of the plurality of requests, and wherein the request data included in the request data portion is not included in the notification portion; and
a message transmitter configured to:
transmit the notification portion of the change message to a plurality of recipients prior to transmission of the request data portion, wherein receipt of only the notification portion by any of the plurality of recipients informs the recipient of the change in the state of the database; and
transmit, after transmission of the notification portion, the request data portion to the plurality of recipients as a plurality of packets, the plurality of packets including:
an encrypted packet including at least a part of the request data portion; and
a last packet including a decryption key to decrypt the encrypted packet, wherein transmission of the last packet is timed to shorten a period of time between individual updates to each of the plurality of recipients by delaying access to the request data portion for some of the plurality of recipients.

### Claim 2 (depends on 1)

The system of claim 1, wherein the request data includes data that allows, upon receipt of the request data portion, a submitting participant of a previously received but unsatisfied request to determine that their request has been at least partially satisfied.

### Claim 3 (depends on 1)

The system of claim 1, wherein the request data includes a request-unique identifier for each of the plurality of requests that were at least partially satisfied.

### Claim 4 (depends on 3)

The system of claim 3, wherein the request data further includes a quantity for each of the plurality of requests that were at least partially satisfied.

### Claim 5 (depends on 1)

The system of claim 1, wherein the request data excludes any information regarding an incoming request quantity or a pre-trade modification to allow only a submitting participant of a corresponding incoming request to comprehend an extent to which the incoming request is satisfied.

### Claim 6 (depends on 1)

The system of claim 1, wherein the message transmitter is further operative to not transmit an individualized message acknowledging the at least partial satisfaction of a previously received but unsatisfied request solely to a submitting participant thereof.

### Claim 7 (depends on 1)

The system of claim 1, wherein the notification data includes at least a count of ones of the plurality of requests that were at least partially satisfied.

### Claim 8 (depends on 1)

The system of claim 1, wherein the notification data further indicates aggregate transacted quantity and transaction price of each of one or more financial products transacted as a result of an at least partial satisfaction of an incoming request a previously received but unsatisfied request.

### Claim 9 (depends on 1)

The system of claim 1, wherein the notification portion further includes data relating to a result of a plurality changes in the state of the database.

### Claim 10 (depends on 1)

The system of claim 1, wherein the database includes an electronic order book that implements an electronic marketplace.

### Claim 11

A method including:
determining, by a processor a change in a state of a database as a result of plurality of requests received from one or more sources;
generating, by the processor, a message including a notification portion and a request data portion, wherein the notification portion includes notification data conveying the change in the state of the database without identifying all of the plurality of requests and the request data portion includes request data identifying at least one of the plurality of requests, and wherein the request data included in the request data portion is not included in the notification portion;
transmitting the notification portion of the message to a plurality of recipients prior to transmitting the request data portion, wherein receipt of only the notification portion by any of the plurality of recipients informs the recipient of the change in the state of the database; and
transmitting, after transmitting the notification portion, the request data portion to the plurality of recipients as a plurality of packets, the plurality of packets including:
an encrypted packet including at least a part of the request data portion; and
a last packet including a decryption key to decrypt the encrypted packet, wherein transmission of the last packet is timed to shorten a period of time between individual updates to each of the plurality of recipients by delaying access to the request data portion for some of the plurality of recipients.

### Claim 12 (depends on 11)

The method of claim 11, wherein the request data includes data that allows, upon receipt of the request data portion, a submitting participant of a previously received but unsatisfied request to determine that their request has been at least partially satisfied.

### Claim 13 (depends on 11)

The method of claim 11, wherein the request data includes a request-unique identifier for each of the plurality of requests that were at least partially satisfied.

### Claim 14 (depends on 13)

The method of claim 13, wherein the request data further includes a quantity for each of the plurality of requests that were at least partially satisfied.

### Claim 15 (depends on 11)

The method of claim 11, wherein the request data excludes any information regarding an incoming request quantity or a pre-trade modification to allow only a submitting participant of a corresponding incoming request to comprehend an extent to which the incoming request is satisfied.

### Claim 16 (depends on 11)

The method of claim 11, wherein the notification data includes at least a count of ones of the plurality of requests that were at least partially satisfied.

### Claim 17 (depends on 11)

The method of claim 11, wherein the notification data further indicates aggregate transacted quantity and transaction price of each of one or more financial products transacted as a result of an at least partial satisfaction of an incoming request a previously received but unsatisfied request.

### Claim 18 (depends on 11)

The method of claim 11, wherein the notification portion further includes data relating to a result of a plurality of changes in the state of the database.

### Claim 19 (depends on 11)

The method of claim 11, wherein the database includes an electronic order book that implements an electronic marketplace.

### Claim 20

A system including:
means for determining a change in a state of a database as a result of plurality of requests received from one or more sources;
means for generating a message including a notification portion and a request data portion, wherein the notification portion includes notification data conveying the change in the state of the database without identifying all of the plurality of requests and the request data portion includes request data identifying at least one of the plurality of requests, and wherein the request data included in the request data portion is not included in the notification portion;
means for transmitting the notification portion of the message to a plurality of recipients prior to transmission of the request data portion, wherein receipt of only the notification portion by any of the plurality of recipients informs the recipient of the change in the state of the database; and
means for transmitting, after transmitting the notification portion, the request data portion to the plurality of recipients as a plurality of packets, the plurality of packets including:
an encrypted packet including at least a part of the request data portion; and
a last packet including a decryption key to decrypt the encrypted packet, wherein transmission of the last packet is timed to shorten a period of time between individual updates to each of the plurality of recipients by delaying access to the request data portion for some of the plurality of recipients.
