DCT
1:22-cv-10130
Savannah Licensing LLC v. CME Group Inc
Key Events
Complaint
Table of Contents
complaint Intelligence
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Savannah Licensing LLC (Texas)
- Defendant: CME Group Inc. (Delaware)
- Plaintiff's Counsel: Sand, Sebolt & Wernow, LPA
- Case Identification: 1:22-cv-10130, S.D.N.Y., 11/29/2022
- Venue Allegations: Venue is alleged to be proper in the Southern District of New York because the Defendant maintains a regular and established place of business within the district.
- Core Dispute: Plaintiff alleges that Defendant's website, by using analytics software to monitor user interactions, infringes two patents related to detecting user frustration and using that data to improve user experience.
- Technical Context: The technology involves device-side or client-side monitoring of user behavior to identify moments of frustration, packaging that data with contextual information about the device's activity, and transmitting it for analysis and action.
- Key Procedural History: The complaint notes that during prosecution for both the '992 and '777 patents, the applicant amended the claims to overcome prior art rejections. These amendments focused on the combination of associating a frustration event with an active device operation and forming a detailed event package. This prosecution history may be relevant to the scope and interpretation of the asserted claims.
Case Timeline
| Date | Event |
|---|---|
| 2010-09-03 | Priority Date for '992 Patent and '777 Patent |
| 2013-09-19 | Applicant Amendment during '992 Patent prosecution |
| 2014-03-25 | '992 Patent Issued |
| 2016-06-21 | Applicant Amendment during '777 Patent prosecution |
| 2016-09-27 | '777 Patent Issued |
| 2022-11-29 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,680,992
- Patent Identification: U.S. Patent No. 8,680,992, "Measuring and Improving the Quality of a User Experience," issued on March 25, 2014 (the "'992 Patent").
The Invention Explained
- Problem Addressed: The patent identifies that prior methods for evaluating user experience were often network-based and resulted in feedback being "delayed from the user's experience" Compl. ¶21 '992 Patent, col. 1:12-15 This created a gap between when a user became frustrated and when that frustration could be analyzed.
- The Patented Solution: The invention proposes a method implemented on the user's device to provide immediate feedback. It involves detecting a "user frustration event" (e.g., shaking the device), associating that event with what the device was actively doing at that moment, creating an "event package" containing details about the frustration and device state, and transmitting it over a network Compl. ¶19 '992 Patent, abstract '992 Patent, col. 3:26-42 This shifts the point of data collection from the network to the user's device itself.
- Technical Importance: The technology provides a framework for capturing qualitative user experience data in real-time, directly linking user sentiment (frustration) to specific software or network performance issues as they occur.
Key Claims at a Glance
- The complaint asserts independent Claim 1 Compl. ¶19
- The essential elements of Claim 1 are:
- detecting a user frustration event;
- associating the user frustration event with a device event that includes an active operation of the device at a time when the user frustration event occurred;
- forming an event package based at least in part on the user frustration event and the device event that includes information indicating a level, a type of user frustration, and information related to routing the event package through a network; and
- transmitting the event package.
- The complaint does not explicitly reserve the right to assert dependent claims.
U.S. Patent No. 9,454,777
- Patent Identification: U.S. Patent No. 9,454,777, "Measuring and Improving the Quality of a User Experience Upon Receiving a Frustration Event Package," issued on September 27, 2016 (the "'777 Patent").
The Invention Explained
- Problem Addressed: Like its parent, the '777 Patent addresses the deficiencies of delayed, network-based methods for evaluating user experience Compl. ¶50 '777 Patent, col. 1:23-27
- The Patented Solution: This invention focuses on the server-side or receiving end of the system. It describes a method where a computing device receives the "frustration event package" (generated by a method like that in the '992 Patent), analyzes the package to determine feedback, and then implements a "network action" based on that feedback Compl. ¶51 '777 Patent, col. 7:1-14 This closes the feedback loop, allowing a system to react to the reported user frustration.
- Technical Importance: The technology enables a system to not only receive user frustration data but also to act upon it, potentially in an automated fashion, to improve network or service performance.
Key Claims at a Glance
- The complaint asserts independent Claim 1 Compl. ¶51
- The essential elements of Claim 1 are:
- receiving, by the computing device, a frustration event package comprising a user frustration event indicator and an associated event indicator that indicates a level and a type of user frustration, where the frustration event is associated with an active device operation;
- determining, by the computing device, feedback based at least in part on the user frustration event indicator and the associated event indicator; and
- implementing, by the computing device, a network action based on the determined feedback.
- The complaint does not explicitly reserve the right to assert dependent claims.
III. The Accused Instrumentality
- Product Identification: The accused instrumentality is Defendant's website, "www.cmegroup.com", and its incorporated systems (the "Accused Instrumentality") Compl. ¶6 Compl. ¶74
- Functionality and Market Context: The complaint alleges that the Accused Instrumentality, at least in internal testing, utilizes a third-party tool called LogRocket Compl. ¶75 This tool is alleged to detect and capture user "rage click sessions" (repeatedly clicking on an element), which the plaintiff characterizes as a "user frustration event" Compl. ¶76 Upon detecting such an event, the system allegedly captures session data (e.g., replay videos, click maps, heat maps) and generates a "session event report" that is transmitted to Defendant's teams for analysis to "improve their services" Compl. ¶76 A screenshot from a LogRocket marketing page suggests its service is designed to collect user experience data, including "User Frustration," and surface it to engineering and product teams Compl. Ex. F, p. 6 Another visual from Exhibit F shows a Fiddler packet capture, which Plaintiff alleges demonstrates that the CME website makes a call to a LogRocket script Compl. Ex. F, p. 3
IV. Analysis of Infringement Allegations
'992 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| detecting a user frustration event; | The Accused Instrumentality allegedly uses LogRocket to detect "rage clicks," which are defined as a user repeatedly clicking on a particular element or area of the website. | ¶76 | col. 3:51-61 |
| associating the user frustration event with a device event that includes an active operation of the device at a time when the user frustration event occurred; | The system allegedly associates the rage clicking event with the active user session on the website, which includes capturing session data related to the rage clicks as they happen. | ¶77 | col. 4:30-38 |
| forming an event package based at least in part on the user frustration event and the device event that includes information indicating a level, a type of user frustration, and information related to routing the event package through a network; | The system allegedly generates a "session event report" that includes session replay videos and heat maps (level), identifies the event as a rage click (type), and contains the IP address of the server (routing information). | ¶78 | col. 4:62-67 |
| transmitting the event package. | The session event report is allegedly transmitted over the internet to the teams of the Accused Instrumentality for analysis. | ¶79 | col. 5:5-11 |
'777 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving, by the computing device, a frustration event package comprising a user frustration event indicator and an associated event indicator that indicates a level and a type of user frustration... | A server of the Accused Instrumentality allegedly receives the "session event report" from LogRocket, which contains an indicator that the event is a "rage click" and associated data like session replays and heat maps. A screenshot from LogRocket's documentation shows a dashboard for reviewing user feedback submissions linked to a session report Compl. Ex. F, p. 10 | ¶94 | col. 7:15-24 |
| determining, by the computing device, feedback based at least in part on the user frustration event indicator and the associated event indicator; and | The server allegedly determines feedback based on the rage click indicator and the associated session data, such as captured session replays and click maps. | ¶95 | col. 7:31-38 |
| implementing, by the computing device, a network action based on the determined feedback. | The system allegedly implements a network action by notifying the respective team at CME Group about the session report and its included frustration signals. | ¶96 | col. 8:8-14 |
- Identified Points of Contention:
- Scope Questions: The infringement theory for both patents hinges on whether "rage clicks" (rapid, repeated clicks in a web browser) constitute a "user frustration event" as contemplated by the patents. The specifications provide examples like shaking the device or hard button presses (e.g.,'992 Patent, col. 3:1-5), raising the question of whether the claimed term is limited to such physical device manipulations.
- Technical Questions: For the '777 Patent, a central question is whether "notify[ing] the respective team" Compl. ¶96 meets the "implementing... a network action" limitation. The patent specification gives examples of network actions such as "increasing a network service in a local area" or "beam steering" Compl. Ex. C, col. 8:8-14, which suggests a more automated, technical intervention in the network itself, rather than a notification to a human.
V. Key Claim Terms for Construction
The Term: "user frustration event"
Context and Importance: This term is the trigger for the methods in both asserted patents. Its definition is critical because the Defendant's alleged "rage clicks" must fall within its scope for there to be infringement. Practitioners may focus on this term because the patent's examples (shaking a device) differ from the accused functionality (mouse clicks on a website).
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes frustration as causing "non-productive actions by the user" '992 Patent, col. 3:1-3 and mentions detecting a "look of frustration" with a camera '992 Patent, col. 3:59-60, which could support an interpretation that is not limited to specific physical acts.
- Evidence for a Narrower Interpretation: The primary examples provided are physical manipulations of the device itself, such as "shaking the device or pressing buttons or a touch screen harder or longer than may be necessary" '992 Patent, col. 3:3-5 Dependent claims of the '992 Patent (e.g., claim 2) specifically recite "shaking of the device," which may be used to argue the independent claim should be interpreted more broadly, but could also suggest these are the core types of events envisioned.
The Term: "network action"
Context and Importance: This is the final, operative step of asserted Claim 1 of the '777 Patent. The Plaintiff alleges this is met by notifying a team. The validity of this mapping is a core infringement question.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim term itself is not explicitly limited. The specification states that feedback may be for "network developers" and can be provided as a "data file" or "summary" '777 Patent, col. 7:32-38, which might support an argument that providing actionable data to a relevant party constitutes a "network action."
- Evidence for a Narrower Interpretation: The specification provides specific, technical examples of a "network action," including "increasing a network service in a local area," "increasing a power modulation," and "beam steering" '777 Patent, col. 8:8-14 This language may support an argument that the term requires a direct, automated technical change to network operations, not merely a notification to a person.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced and contributory infringement for both patents Compl. ¶¶85-86 Compl. ¶¶102-103 The allegations state Defendant encourages infringement and contributes by selling the Accused Instrumentality to customers. However, the factual support primarily describes Defendant's own alleged "internal testing and usage" Compl. ¶75, and the allegations concerning infringement by customers are conclusory.
- Willful Infringement: The complaint seeks "enhanced damages" Compl. p. 25, ¶f Knowledge of the patents is alleged to have occurred "at least as of the service of the present Complaint" Compl. ¶83 Compl. ¶100, which would only support a claim for post-filing willfulness.
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: can the term "user frustration event," rooted in the patents' examples of physical device manipulation like shaking, be construed to cover "rage clicks" within a web application as detected by the accused system?
- A second pivotal question, specific to the '777 Patent, will be one of functional interpretation: does "implementing a network action" require a direct, automated technical change to network resources as exemplified in the specification, or can it be satisfied by the alleged act of "notifying a human team" about a frustration report?
- A key evidentiary question will be one of third-party instrumentality: given the alleged reliance on the LogRocket tool, the case may explore the extent to which Defendant's configuration and use of this third-party service constitutes "making" or "using" the claimed methods, particularly as it relates to the specific details of forming and processing the alleged "event package."
Analysis metadata
Loading Complaint
Suggested improvements