Prior art — US Patent 12337715

Prior Art and Novelty Analysis

To: File
From: Senior Patent Analyst
Date: May 13, 2026
Subject: Anticipation Analysis of U.S. Patent No. 12,337,715 Under 35 U.S.C. § 102

Legal Standard for Anticipation

Under 35 U.S.C. § 102, a claim is "anticipated," and therefore not novel, if every single element and limitation of that claim is found in a single prior art reference. The disclosure in the prior art reference must be enabling, meaning it would teach a person of ordinary skill in the art (POSITA) how to make and use the claimed invention. This analysis examines key prior art references to determine if any single reference anticipates the independent claims (1, 15, and 20) of U.S. Patent No. 12,337,715 ('715 patent), which has a priority date of April 22, 2012.

Note: The official list of references cited by the USPTO examiner for the '715 patent is not available. The following analysis focuses on highly relevant prior art that would likely have been considered during the patent's prosecution or in subsequent validity challenges.

Reference 1: Smith et al. (GM Global Technology Operations)

Citation: U.S. Patent No. 7,791,469 B2, "System and Method for Authenticated Vehicle Access"
Dates: Filed: August 2, 2007; Issued: September 7, 2010. This qualifies as prior art.
Brief Description: Smith discloses a system where a vehicle owner can grant temporary access to another person using a wireless device. The system involves a remote server that receives a request from the owner, generates a temporary access credential (a "token" or "digital key"), and sends it to the recipient's mobile device. The recipient's device can then communicate with the vehicle via a short-range protocol (e.g., Bluetooth) to unlock and operate it.
Anticipation Analysis (§ 102):
- Claim 1: Not anticipated. Smith discloses receiving a request, generating an electronic key, transmitting it to a recipient's device, and enabling vehicle use. However, Smith does not explicitly teach including a "condition of use" (like a speed limit or geofence) in the request, monitoring vehicle use data against that condition, and sending a "warning notification" if the condition is violated. These elements are central to claim 1 of the '715 patent.
- Claim 15: Not anticipated. While Smith describes generating a unique access code and sending it to a recipient, it lacks the '715 patent's claimed steps of receiving "use metrics of the vehicle" during operation, storing these metrics as a "history of use for the e-keys," and having a mechanism for a remote "request to cancel the e-keys."
- Claim 20: Not anticipated. Smith's system enables vehicle access via a wireless device, but it does not describe the specific two-step activation process claimed in the '715 patent, where the smartphone sends an encrypted e-key to the vehicle and receives back an activated e-key that enables a specific graphical user interface with controls. Smith's focus is on the credential exchange for authentication, not the specific user interface activation flow.

Reference 2: Tieman et al. (General Motors Corp.)

Citation: U.S. Patent No. 7,675,422 B2, "Vehicle Monitoring System"
Dates: Filed: November 2, 2007; Issued: March 9, 2010. This qualifies as prior art.
Brief Description: Tieman describes a system for monitoring a vehicle's operation against a set of predefined parameters. An administrator (such as a parent or fleet manager) can establish rules, including maximum speed limits and geographic boundaries (geofences). A device in the vehicle tracks its GPS location and speed. If the vehicle violates one of the set parameters, the system generates and sends an alert or notification to the administrator.
Anticipation Analysis (§ 102):
- Claim 1: Not anticipated. Tieman strongly teaches the concept of setting a "condition of use," receiving "use data," identifying a "violation," and sending a "warning notification." However, it is missing the core context of claim 1: it does not describe a system for generating and sharing a temporary electronic key with a third-party recipient. Tieman's system is for monitoring a vehicle that a user already has access to, not for granting that access in the first place via a sharable e-key.
- Claim 15: Not anticipated. For the same reasons as claim 1, Tieman does not teach receiving a request to generate and send e-keys to a recipient's device. It is a monitoring and alert system, not an access-granting system.
- Claim 20: Not anticipated. Tieman does not disclose any aspect of a user's smartphone receiving an encrypted key, transmitting it to a vehicle, and receiving an activated key back to enable a GUI. The system's architecture is fundamentally different.

Reference 3: Mikan et al. (Daimler AG)

Citation: U.S. Patent No. 7,719,431 B2, "System and Method for Remotely Controlling Vehicle Functions"
Dates: Filed: July 2, 2008; Issued: May 18, 2010. This qualifies as prior art.
Brief Description: Mikan discloses a system for controlling vehicle functions (like locking/unlocking doors, starting the engine, and activating the horn) from a user's remote device, such as a PDA or mobile phone. The system uses a central server that authenticates the user and relays commands to the vehicle's telematics unit. It focuses on providing remote control capabilities to the primary owner or an authorized user.
Anticipation Analysis (§ 102):
- Claim 1: Not anticipated. Mikan describes a server-mediated system for remote vehicle control, which involves communication between a server, a user device, and the vehicle. However, it does not teach the key elements of sharing access with a different recipient by generating a temporary e-key, associating that key with specific "conditions of use," or monitoring for and warning about violations of those conditions. The system is for the primary user's convenience, not for managed delegation of access.
- Claim 15: Not anticipated. The claims of the '715 patent are directed to granting e-keys to a recipient. Mikan's system is for the owner to control their own car remotely. It does not disclose the generation of unique access codes for third parties or the management of their privileges and use history.
- Claim 20: Not anticipated. Mikan does not describe the specific e-key sharing and activation workflow where a recipient's device receives an encrypted key and sends it to the vehicle to get back an activated key. The authentication and command flow in Mikan is tied to the primary user's account, not a temporary, delegated credential.