Secure Communication Tech LLC v. Google LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Secure Communication Technologies, LLC. (Texas)
  • Defendant: Google LLC (Delaware)
  • Plaintiff's Counsel: Nelson Bumgardner Conroy PC
• Case Identification: 1:25-cv-1207, W.D. Tex., 09/08/2025
• Venue Allegations: Plaintiff alleges venue is proper in the Western District of Texas because Defendant maintains regular and established places of business in the district, including multiple permanent offices and full-time employees in Austin, and has committed the alleged acts of infringement in the district.
• Core Dispute: Plaintiff alleges that Defendant's Google-branded and Android-based mobile devices and laptops, incorporating features such as Nearby Share, Fast Pair, and Find Hub, infringe five patents related to secure and efficient proximity-based wireless communication.
• Technical Context: The technology at issue involves using a combination of short-range (e.g., Bluetooth) and long-range (e.g., cellular) wireless protocols to enable secure discovery, communication, and transactions between nearby devices, brokered by a central server.
• Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of the patents-in-suit through various means, including direct notice from the inventor as early as 2012, Defendant's own patent prosecution activities, and a prior lawsuit, Secure Communication Tech LLC v. Samsung Electronics Co. Ltd. (No. 2:24-cv-00484-JRG, E.D. Tex.). The complaint also notes that Defendant has filed Inter Partes Review (IPR) petitions challenging the validity of several of the patents-in-suit.

Case Timeline

Date	Event
2008-09-08	Earliest Priority Date for all Patents-in-Suit
2010-01-01	Release of Google Nexus One Smartphone
2010-01-01	Release of Bluetooth v4.0 (including Bluetooth Low Energy)
2012-02-09	Plaintiff alleges Google was informed of the '749 Patent
2012-02-14	U.S. Patent No. 8,116,749 Issues
2012-12-17	Plaintiff alleges Google disclosed the '749 Patent in an IDS
2013-01-01	Release of Google's Find Hub feature
2017-01-01	Release of Google's Fast Pair feature
2020-01-01	Release of Google's Nearby Share feature
2022-05-17	U.S. Patent No. 11,334,918 Issues
2022-09-13	U.S. Patent No. 11,443,344 Issues
2023-06-27	U.S. Patent No. 11,687,971 Issues
2024-05-28	U.S. Patent No. 11,995,685 Issues
2025-07-02	Alleged date before which Google filed IPRs against the patents
2025-08-04	Original Complaint filed in related Samsung case
2025-09-08	First Amended Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 8,116,749

• Patent Identification: U.S. Patent No. 8,116,749, Protocol for anonymous wireless communication, issued February 14, 2012 Compl. ¶19

The Invention Explained

• Problem Addressed: The patent describes the need for a secure, anonymous, and convenient method for individuals in close proximity to specify a party for an electronic transaction, cross-validate identities, and conduct the transaction, particularly in indoor locations where GPS is unreliable '749 Patent, col. 2:15-24 Existing peer-to-peer and GPS-based social networking solutions were described as inadequate for secure mobile e-commerce due to security risks and poor indoor performance '749 Patent, col. 1:35-67
• The Patented Solution: The invention proposes a hybrid system where a first device uses a short-range wireless protocol (like Bluetooth) to detect an identifier from a second device, but then uses a long-range wireless network (like cellular) to communicate with a central server '749 Patent, abstract This server acts as a trusted third party to broker the exchange of information and facilitate transactions, applying security and privacy policies based on the identities of the entities involved '749 Patent, col. 3:4-34 This architecture allows for secure, proximity-based interactions without relying on GPS and adds a layer of server-managed security, as depicted in the patent's Figure 1 '749 Patent, fig. 1
• Technical Importance: The technology aimed to bridge the gap between online e-commerce and in-person transactions by enabling secure, proximity-based mobile payments and interactions before such systems were widespread.

Key Claims at a Glance

• The complaint asserts at least independent claim 1 Compl. ¶68
• Claim 1 of the '749 Patent is a method claim with essential elements including:
  • Providing initial identification information from a first wireless device to a central server, collected from a second wireless device via a direct, short-range wireless link.
  • Associating the initial identification information at the server with an identity of a user or entity.
  • At the second wireless device, upon a predetermined event, providing modified identification information over the short-range link.
  • Associating the modified identification information at the server with the same identity.
  • At the first wireless device, collecting the modified identification information.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

U.S. Patent No. 11,334,918

• Patent Identification: U.S. Patent No. 11,334,918, Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided, issued May 17, 2022 Compl. ¶23

The Invention Explained

• Problem Addressed: The patent identifies challenges in facilitating secure transactions and information exchange between nearby mobile devices '918 Patent, background, col. 1:32-2:24 It notes that pure peer-to-peer systems lack a trusted third party, posing security risks, while GPS-based systems are often ineffective indoors '918 Patent, col. 2:5-11
• The Patented Solution: The '918 Patent discloses a system where a mobile device uses a short-range radio (e.g., Bluetooth) to detect a beacon transmission from another device, which contains a unique identifier and a specific "beacon service identifier." The receiving device then filters for this specific service identifier and uses a long-range radio (WWAN) to communicate with a central server, which holds stored information related to the unique identifier '918 Patent, abstract '918 Patent, claim 1 This server-brokered approach, illustrated in Figures 8A and 8B, enables secure, proximity-aware services and e-commerce transactions '918 Patent, figs. 8A-8B
• Technical Importance: This invention provided a method for devices to efficiently filter for specific proximity-based services and securely interact via a central server, enhancing both security and power efficiency for proximity-based applications.

Key Claims at a Glance

• The complaint asserts at least independent claims 1 and 9 Compl. ¶80
• Claim 1 of the '918 Patent is a method claim with essential elements including:
  • Receiving a plurality of beacon transmissions via a short-range protocol, each comprising a MAC address, a unique identifier, and a beacon service identifier.
  • Receiving stored information from a server via a second, different wireless protocol.
  • Selecting unique identifiers from the beacons by filtering for a particular beacon service identifier.
  • Taking a "first further action" related to the stored information if a specific "first unique identifier" is present in the selected set.
• Claim 9 of the '918 Patent is a method claim with essential elements including:
  • Communicating with a server to receive identifier-related information using a first radio.
  • Receiving short-range proximity beacon transmissions using a second radio.
  • Determining if a received transmission is a proximity beacon associated with the proximity beacon service.
  • If the above is true, determining that an entity is in proximity by using the identifier-related information and the unique identifier from the beacon.
• The complaint does not explicitly reserve the right to assert dependent claims for this patent.

Multi-Patent Capsule: U.S. Patent No. 11,443,344

• Patent Identification: U.S. Patent No. 11,443,344, Efficient and secure communication using wireless service identifiers, issued September 13, 2022 Compl. ¶27
• Technology Synopsis: The '344 Patent addresses the problem of securely and efficiently managing communications between nearby wireless devices. The patented solution involves a broadcast device transmitting a beacon with a unique identifier and a service identifier; a mobile device filters for that service identifier and then takes further action based on information stored on a server that is associated with the unique identifier, reducing unnecessary communications while enhancing security '344 Patent, abstract
• Asserted Claims: The complaint asserts at least independent claims 1, 29, and 30 Compl. ¶93
• Accused Features: The complaint alleges that Google's Fast Pair, Quick Share, and Find Hub features, which facilitate device discovery and communication, infringe the '344 Patent Compl. ¶43 Compl. ¶99

Multi-Patent Capsule: U.S. Patent No. 11,687,971

• Patent Identification: U.S. Patent No. 11,687,971, Efficient and secure communication using wireless service identifiers, issued June 27, 2023 Compl. ¶31
• Technology Synopsis: The '971 Patent describes a method for reducing communications between a mobile device and a server while maintaining security for beacon services. A mobile device receives beacon transmissions containing unique identifiers and a beacon service identifier, filters for that service, and only takes further action if a specific unique identifier is present among the filtered results, using information previously stored or received from the server '971 Patent, abstract
• Asserted Claims: The complaint asserts at least independent claims 1, 37, and 50 Compl. ¶106
• Accused Features: The complaint alleges that Google's Quick Share, Fast Pair, and Find Hub features infringe by implementing the claimed methods for device discovery and communication Compl. ¶43 Compl. ¶112

Multi-Patent Capsule: U.S. Patent No. 11,995,685

• Patent Identification: U.S. Patent No. 11,995,685, Efficient and secure communication using wireless service identifiers, issued May 28, 2024 Compl. ¶35
• Technology Synopsis: The '685 Patent discloses systems and methods for secure and efficient proximity-based communication. The technology involves a mobile device receiving short-range beacon transmissions, selecting beacons based on a specific service identifier, and then acting upon those selections using information from a server if a particular unique identifier is found, thereby providing enhanced security and reducing unnecessary data exchange '685 Patent, abstract
• Asserted Claims: The complaint asserts at least independent claim 1 Compl. ¶119
• Accused Features: The complaint alleges that Google's Fast Pair feature, which uses Bluetooth to quickly pair with nearby devices, infringes the '685 Patent Compl. ¶43 Compl. ¶125

III. The Accused Instrumentality

Product Identification

The complaint identifies the "Accused Products" as a broad category of Google-branded and third-party devices Compl. ¶42 This includes Google's Pixel phones and tablets (e.g., Pixel 10, Pixel 9 series, Pixel Tablet), Chromebook laptops, and other Android-based devices from manufacturers like Acer, ASUS, HP, Lenovo, Motorola, and OnePlus Compl. ¶¶39-41

Functionality and Market Context

The infringement allegations center on specific software features within the Android operating system and Google's ecosystem: "Nearby Share/Quick Share," "Fast Pair," and "Find Hub" (previously "Find My") Compl. ¶43

• Nearby Share/Quick Share: A feature for transferring files between nearby Android devices, Chromebooks, and Windows PCs.
• Fast Pair: A feature that uses Bluetooth Low Energy to quickly discover and pair with nearby Bluetooth accessories.
• Find Hub (Find My Device): A service to locate, ring, or wipe a lost Android device.
• The complaint alleges these features were released years after the inventions of the patents-in-suit, citing release dates of 2020 for Nearby Share, 2017 for Fast Pair, and 2013 for Find Hub Compl. ¶59 The complaint provides a Google support page for the "Find Hub" feature, which contains instructions and illustrations for users on how to locate a lost Android device Compl. ¶73

IV. Analysis of Infringement Allegations

The complaint alleges infringement but incorporates its detailed theories into external exhibits which were not provided with the complaint text Compl. ¶69 Compl. ¶81 The following tables synthesize the infringement allegations for the lead patents based on the narrative descriptions in the complaint and the technical details of the accused features.

'749 Patent Infringement Allegations

The complaint alleges that the Accused Products, through features like Find Hub, infringe at least claim 1 of the '749 patent by implementing a protocol for anonymous wireless communication brokered by a central server Compl. ¶68 A Google support page for the "Find Hub" feature is provided as an example of materials that instruct and encourage customers to use the infringing functionality Compl. ¶73 The narrative suggests the following mapping:

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
at the first wireless device, providing initial identification information to a central server, said initial identification information having been collected by the first wireless device from the second wireless device via a first, direct, short range local wireless link...	An Accused Product (first device, e.g., a user's phone) allegedly uses a short-range protocol like Bluetooth to detect another device (second device, e.g., a lost phone) and communicates that identification to Google's servers (the central server).	¶43; ¶68	col. 3:9-14
at the second wireless device, upon an occurrence of a predetermined event, providing modified identification information over the first, direct, short range local wireless link...	The complaint's theory suggests that a lost device (second device) may change its identifier over time for security, constituting a "predetermined event" and providing "modified identification information" over Bluetooth.	¶43; ¶68	col. 4:46-52
at the first wireless device, collecting said modified identification information.	The user's phone (first device) allegedly collects this new, modified identifier from the lost device via the short-range link to continue the location process.	¶43; ¶68	col. 3:9-14

'918 Patent Infringement Allegations

The complaint alleges that features like Quick Share and Fast Pair infringe at least claims 1 and 9 of the '918 patent Compl. ¶80 A Google support page for "Quick Share" is referenced, showing instructions on how to share content with nearby devices, which allegedly induces infringement Compl. ¶86 The narrative suggests the following mapping:

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving, at a wireless device, via a short range wireless protocol, a first plurality of beacon transmissions... each beacon transmission comprising... a beacon service identifier...	Accused Products running features like Fast Pair allegedly receive Bluetooth Low Energy (a short-range protocol) beacon transmissions that contain a specific service identifier to initiate pairing.	¶43; ¶60	col. 9:36-44
receiving, at the wireless device via a second wireless protocol, stored information from one or more servers...	Accused Products allegedly use a second protocol (e.g., cellular/Wi-Fi) to receive information from Google's servers, such as device details or account information needed to complete the pairing or sharing process.	¶43; ¶80	col. 3:15-22
causing selection of one or more of the unique identifiers from the first plurality of beacon transmissions, by filtering the beacon transmissions which include a particular beacon service identifier...	The Fast Pair and Quick Share features are alleged to filter for specific Bluetooth service identifiers to distinguish them from other nearby Bluetooth devices and initiate the correct functionality.	¶43; ¶80	col. 5:47-67
taking first further action relating to the stored information, if the first unique identifier is present among the selected one or more unique identifiers.	After a device is selected based on its service identifier, the Accused Products allegedly use server-provided information (e.g., account details) to take further action, such as completing a pairing or file transfer.	¶43; ¶80	col. 8:1-10

• Identified Points of Contention:
  • Scope Questions: A central question may be whether the term "anonymous" in the '749 Patent, which implies a changing identifier to protect privacy, reads on the functionality of Google's Find Hub, where device identifiers may be more persistent for account-linking purposes. For the '918 Patent, a dispute may arise over whether the accused features' use of standard Bluetooth service discovery constitutes infringement of the claimed method of filtering for a specific "beacon service identifier".
  • Technical Questions: A key technical question will be what evidence demonstrates that the accused features perform the specific multi-step, server-brokered communication process as claimed. For instance, does Google's Fast Pair feature rely on "stored information" from a server to take a "further action" in the manner required by claim 1 of the '918 Patent, or does it operate primarily using local, peer-to-peer logic after the initial discovery?

V. Key Claim Terms for Construction

• Term: "predetermined event" (from '749 Patent, claim 1)

  • Context and Importance: This term is the trigger for the "second wireless device" to provide "modified identification information." Its definition is critical for determining infringement because the Plaintiff's theory relies on the accused devices changing their identifiers over time for security. Whether routine software updates, timers, or other system events in the Accused Products qualify as a "predetermined event" will be a key point of contention.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification does not narrowly define the term, leaving room to argue it could cover any event pre-planned in the system's logic, such as a periodic timer for updating security credentials. The patent's focus on enhancing anonymity and security could support an interpretation that includes any event that triggers an identifier change ('749 Patent, col. 4:46-52).
    • Evidence for a Narrower Interpretation: The term could be construed more narrowly to require an event specifically coordinated with the central server for the purpose of the claimed protocol, not just any routine background process. The context of a multi-step, server-brokered protocol may suggest the "event" must be more specific than a simple timer.

• Term: "beacon service identifier" (from '918 Patent, claim 1)

  • Context and Importance: This term is the basis for the claimed filtering step that distinguishes the invention from general device discovery. Practitioners may focus on this term because the case will likely turn on whether standard identifiers used in Bluetooth (like a Service Class ID or a GATT Service UUID) meet the definition of a "beacon service identifier." Google may argue these are conventional parts of the Bluetooth standard, while SCT may argue their specific use in the accused features to trigger a server-brokered process is what the patent covers.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification references standard protocols like IEEE 802.11 and the use of an SSID or BSSID as potential identifiers, suggesting the term is meant to be read broadly on identifiers used within existing wireless standards to signal a particular service ('918 Patent, col. 10:45-54).
    • Evidence for a Narrower Interpretation: The patent repeatedly emphasizes that the beacon service identifier is used to identify a "particular received beacon transmission is associated with a particular wireless beacon service" '918 Patent, claim 1 This could be interpreted to require a specific, proprietary service identifier created for the patented system, rather than a generic service identifier from a public standard like Bluetooth.

VI. Other Allegations

• Indirect Infringement: Plaintiff alleges induced infringement for all asserted patents. The complaint claims Google instructs and encourages its customers to use the Accused Products in an infringing manner by providing extensive customer support, user manuals, and instructional webpages Compl. ¶70 Compl. ¶82 Compl. ¶95 Compl. ¶108 Compl. ¶121 The complaint cites to specific Google support webpages for features like Find Hub, Quick Share, and Fast Pair as evidence of this inducement Compl. ¶73 Compl. ¶86 Compl. ¶99
• Willful Infringement: The complaint alleges willful infringement based on both pre- and post-suit knowledge. Pre-suit knowledge is alleged based on: (1) direct communication to Google from the inventor regarding the '749 patent family as early as February 9, 2012 Compl. ¶46; (2) Google's own citation of the '749 patent in its patent prosecution activities starting in 2012 Compl. ¶48; and (3) Google's knowledge of a prior lawsuit by SCT against Samsung involving the same patents and Google's Android operating system Compl. ¶44 Post-suit knowledge is based on the filing of this complaint and Google's IPR filings challenging the patents Compl. ¶44 Compl. ¶71

VII. Analyst's Conclusion: Key Questions for the Case

This dispute appears to center on the intersection of established wireless standards and patented methods for server-brokered communication. The outcome will likely depend on the court's interpretation of claim scope in light of the functionality of widely deployed technologies. The key questions for the case are:

1. A central issue will be one of technical and definitional scope: Does the functionality of Google's accused features (Fast Pair, Nearby Share, Find Hub) map onto the specific multi-step, server-brokered communication protocols required by the claims? For example, can a standard Bluetooth Service UUID be construed as the claimed "beacon service identifier" ('918 Patent), and does a device's identifier changing over time constitute the claimed "predetermined event" ('749 Patent)?

2. A key question on infringement will be one of causation and control: To what extent are Google's servers-the "central server" in the patents' architecture-actively brokering the accused interactions as claimed, versus merely providing background data to devices that then operate autonomously using standard peer-to-peer protocols? The degree of server involvement required by the claims versus that implemented in the Accused Products will be a primary point of contention.

3. An overarching theme will be the relationship between standards and invention: The case raises the question of whether the patents claim a specific, inventive application of standard wireless protocols (like Bluetooth discovery) to solve a technical problem, or if the claims, when construed, read on the conventional operation of those standards themselves. The court's analysis will likely explore the line between implementing a standard and infringing a patented method that uses that standard as a component.