US 11606204

Here's a concise summary of US Patent 11606204:

Title: Systems and methods for “machine-to-machine” (M2M) communications between modules, servers, and an application using public key infrastructure (PKI)

Assignee: Network 1 Technologies Inc (Current Assignee as of 2023-01-04)

Inventors: John A. Nix

Filing Date: January 12, 2022

Issue Date: March 14, 2023

Abstract:
The patent describes systems and methods for secure and efficient machine-to-machine (M2M) communication using a server that facilitates interaction between modules and an application. The system employs public key infrastructure (PKI) algorithms and keys to secure communications, improve efficiency, and potentially extend battery life for modules. The module, server, and application each utilize a suite of cryptographic algorithms including asymmetric and symmetric ciphering, secure hash, and digital signature algorithms. The module can generate its own private and public keys, with the public key being recorded authoritatively by the server. The server can translate between different cryptographic methods (e.g., ECC for modules and RSA for applications) and communication protocols (e.g., UDP for modules and TCP for applications) to ensure compatibility. The system also allows for the secure update of cryptographic parameters, such as elliptic curve definitions, to modules even after deployment, enhancing security and flexibility. The server acts as an intermediary, receiving encrypted data from modules, decrypting it, and securely forwarding it to an application server, and vice versa.

---

Plain-Language Overview of Independent Claims:

• Independent Claim 1 (System Claim):
  This claim describes a system designed for secure and efficient "machine-to-machine" (M2M) communications. The system includes an M2M module and a server.

  • The M2M module has a processor, memory, and a transceiver, and is designed to communicate with a monitored unit. It stores a private key and generates a module public key and a module public key identity. It's configured to send messages to the server, including its public key, module identity, and encrypted data. The module can transition between sleep and active states to conserve power.
  • The server has a processor, memory, and a transceiver, and is configured to communicate with the module and an application server. It maintains a database to store module identities and their associated public keys. The server receives the module's public key and identity, decrypts module messages using the module's public key, and then securely forwards extracted data (like sensor measurements) to the application server using a secure connection and a server public key. The server also uses different cryptographic algorithms and protocols for communication with the module (e.g., ECC and UDP) and the application server (e.g., RSA and TCP).

• Independent Claim 10 (Method Claim):
  This claim describes a method performed by a server for enabling secure M2M communications between a module and an application.

  • The method involves the server establishing a secure connection with an application server using a first server public key.
  • It then receives a module public key and a module public key identity from a module, authenticates the module, and records the module public key.
  • Subsequently, the server receives an encrypted message from the module, decrypts it using the module public key, extracts data (like a sensor measurement), and sends this data to the application server using the secure connection and the first server public key.
  • The server is also configured to use different asymmetric ciphering algorithms and protocols when communicating with the module (e.g., ECC-based with a second public key and UDP) compared to the application server (e.g., RSA-based with the first public key and TCP).

• Independent Claim 16 (Method Claim for Module Instruction):
  This claim outlines a method for a server to process an application message that contains a module instruction and send it to a module.

  • The server receives an application message from an application server, where this message includes a module identity, a module instruction, and is encrypted using a first server public key.
  • The server decrypts the application message and records the module instruction.
  • It then waits for a message from the specified module.
  • Upon receiving a message from the module, the server sends the module instruction to that module, encrypted using a second server public key.
  • The first and second server public keys use different cryptographic algorithms (e.g., RSA for the first, ECC for the second).

• Independent Claim 19 (Method Claim for Key Update):
  This claim details a method performed by a server and a module for updating cryptographic keys.

  • The server receives a first message from a module, including a module identity and encrypted data (e.g., a sensor measurement), encrypted with a first module public key.
  • The server decrypts this data using the first module public key and forwards the sensor measurement to an application server using a second server public key.
  • The server then sends a module instruction and a set of parameters to the module, instructing it to derive a new set of keys.
  • The module, after receiving these, derives a second module public key and a second module private key and sends the second module public key and its identity to the server.
  • The server then receives a second encrypted message from the module, encrypted with the second module public key, extracts the data, and sends it to the application server using the same second server public key. This process allows the module's key to change while the server's communication with the application server remains consistent.

---

Legal Status and Litigation:
According to Google Patents, US11606204B2 is currently Active, with an adjusted expiration date of October 16, 2033.
The patent family is associated with litigation. Specifically:

• The first worldwide family litigation was filed.
• A PTAB case IPR2026-00115 has been filed and is Pending.
• A US case has been filed in the Texas Eastern District Court (case 2:25-cv-00667).

I did not find specific docket information for CAFC 2026 directly linking to US11606204 from the provided search results, beyond the general CAFC case information page. However, the Google Patents information clearly indicates ongoing litigation, including a PTAB case in 2026, which falls within the scope of the request. The USPTO search results provided general information about searching the USPTO database but no specific legal action for this patent number.