Exhibit 9

 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 1 of 15 PageID #: 190
1 

Exhibit 9 to Complaint 

Intellectual Ventures I LLC and Intellectual Ventures II LLC 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 2 of 15 PageID #: 191
2 

Example Chase Count II Systems and Services 

U.S. Patent No. 8,407,722 (“the ’722 Patent”) 

The Accused Services and Systems include, without limitation Chase’s systems that implement Kafka; all past, current and future 

systems and services that operate in the same or substantially similar manner as the specifically identified systems and services; and all 

past, current and future Chase’s systems and services that have the same or substantially similar features as the specifically identified 

(“Example Chase Count II Systems and Services”). 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 3 of 15 PageID #: 192
3 

U.S. Patent No. 8,407,722 

Example Claim 14 Example Chase Count II Systems and Services 

14. A method 

comprising: 

providing, using a 

processing device of an 

input source, a data 

representation to a client 

device, different from 

the input source, 

coupled to a routing 

network, wherein the 

data representation 

includes at least one live 

object recognizable by 

the client device, and 

causing the client device 

to respond to the live 

object of the data 

representation by 

determining an object 

identifier (ID) of the live 

object and to register for 

updates of the live 

object with the routing 

network, such that 

registering the client 

device with the routing 

network provides client 

connection information 

to a node in the routing 

network; and

Upon information and belief, Chase’s systems perform “providing, using a processing device of an input 

source, a data representation to a client device, different from the input source, coupled to a routing 

network, wherein the data representation includes at least one live object recognizable by the client 

device, and causing the client device to respond to the live object of the data representation by 

determining an object identifier (ID) of the live object and to register for updates of the live object with 

the routing network, such that registering the client device with the routing network provides client 

connection information to a node in the routing network.” Kafka facilitates the receipt of messages 

identifying a live object and containing data for updating the property of the live object at end-user 

devices. 

See https://kafka.apache.org/documentation/ (last accessed on November 10, 2023). 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 4 of 15 PageID #: 193
4 

Kafka clusters receive an update message sent by a input source. 

See https://kafka.apache.org/documentation/ (last accessed on November 10, 2023). 

See https://kafka.apache.org/intro (last accessed on November 10, 2023). 

Chase Bank implements Kafka to provide end users with updates in real time. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 5 of 15 PageID #: 194
5 

See https://www.linkedin.com/jobs/view/lead-software-engineer-java-react-and-kafka-at-jpmorganchase-co-3657409994/ (last accessed on November 10, 2023). 

See https://www.slideshare.net/HostedbyConfluent/changing-landscapes-in-data-integration-kafkaconnect-for-near-realtime-data-moving-pipelines-ashok-kadambala-and-shreesha-hebbar-jp-morganchase (last accessed on November 10, 2023). 

See https://careers.jpmorgan.com/us/en/students/programs/software-engineerfulltime?search=&tags=location__Americas__UnitedStatesofAmerica (last accessed on November 10, 

2023). 

See https://www.linkedin.com/jobs/jpmorgan-chase-apache-kafka-jobs/?currentJobId=3739947175 (last 

accessed on November 10, 2023).

See also 

https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1002/job/210456194/?keywor

d=kafka&mode=location (last accessed on November 13, 2023); and 

https://jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1002/job/210437611/?keywor

d=kafka&mode=location (last accessed on November 13, 2023). 

Each new event/record updates a previous record. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 6 of 15 PageID #: 195
6 

See https://kafka.apache.org/documentation/#producerapi (last accessed on November 10 2023). 

See https://kafka.apache.org/0100/javadoc/org/apache/kafka/clients/producer/KafkaProducer.html (last 

accessed on November 10, 2023). 

See https://kafka.apache.org/23/javadoc/org/apache/kafka/streams/kstream/KTable.html (last accessed on 

November 10, 2023). 

See https://docs.confluent.io/platform/current/streams/concepts.html (last accessed on November 10, 

2023).

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 7 of 15 PageID #: 196
7 

sending, using the 

processing device of the 

input source, an update 

message to the routing 

network, wherein the 

update message 

identifies the live object 

and contains update data 

that updates a property 

of the live object; 

Upon information and belief, Chase’s systems perform “sending, using the processing device of the input 

source, an update message to the routing network, wherein the update message identifies the live object 

and contains update data that updates a property of the live object.” Each new event/record comprises an 

event key. The key is used to determine the partition/topic (“a category”) to which the event should be 

written. 

See https://kafka.apache.org/0100/javadoc/org/apache/kafka/clients/producer/KafkaProducer.html (last 

accessed on November 10, 2023).

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 8 of 15 PageID #: 197
8 

See https://kafka.apache.org/ (last accessed on November 10, 2023). 

wherein a gateway 

device at the routing 

network is configured to 

identify a category of 

the update message 

based on the input 

source, to determine a 

node type to which the 

Upon information and belief, Chase’s systems include “wherein a gateway device at the routing network 

is configured to identify a category of the update message based on the input source, to determine a node 

type to which the identified category maps, and to route the update message to the node, having the node 

type, at the routing network.” Chase’s systems include Kafka Clusters that comprise multiple Kafka 

brokers (“nodes”). A broker includes multiple topics (and partitions). A broker is selected based upon the 

topic/partition to which the event belongs. The broker stores the events inside the partitions of the topics. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 9 of 15 PageID #: 198
9 

identified category 

maps, and to route the 

update message to the 

node, having the node 

type, at the routing 

network,; 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 10 of 15 PageID #: 199
10 

See https://kafka.apache.org/documentation/ (last accessed on November 10, 2023). 

A Kafka Cluster comprises of multiple Kafka brokers (“nodes”). A broker includes multiple topics (and 

partitions). A broker is selected based upon the topic/partition to which the event belongs. The broker 

stores the events inside the partitions of the topics. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 11 of 15 PageID #: 200
11 

See https://kafka.apache.org/ (last accessed on November 10, 2023). 

See Kafka Architecture & Internal. This talks about the Apache Kafka... | by Narayan Kumar | Medium 

(last accessed on November 10, 2023). 

wherein the node is 

configured to identify 

the client device as a 

registered device and to 

route the update 

message to the client 

device, and 

Upon information and belief, Chase’s systems include “wherein the node is configured to identify the 

client device as a registered device and to route the update message to the client device.” Consumers 

subscribe (“register”) to a topic (all the events present inside the topic). The broker pushes (“routes”) the 

events of a topic to the consumer in real time that have subscribed to the topic. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 12 of 15 PageID #: 201
12 

See https://kafka.apache.org/intro (last accessed on November 10, 2023). 

Consumers subscribe (“register”) to a topic (all the events present inside the topic). The broker pushes 

(“routes”) the events of a topic to the consumer in real time that have subscribed to the topic. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 13 of 15 PageID #: 202
13 

See https://kafka.apache.org/documentation/ (last accessed on November 10, 2023). 

wherein the client 

device processes the 

update message upon 

receipt to update the 

property of the live 

object at the client 

device. 

Upon information and belief, Chase’s systems include “wherein the client device processes the update 

message upon receipt to update the property of the live object at the client device.” Upon receiving the 

events from one or more topics, the consumer processes the events. Processing might be an aggregation 

of events into a new topic. 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 14 of 15 PageID #: 203
14 

See https://docs.Kafka.com/storage/storagedriver/ (last accessed on November 10, 2023). 

Case 2:23-cv-00523-JRG Document 1-10 Filed 11/15/23 Page 15 of 15 PageID #: 204