US 9290153

Patent Analysis: US 9,290,153 B2

Date of Analysis: April 26, 2026

Patent Number: 9,290,153 (Note: Interpreted literally as provided)

Title: Vehicle-based multimode discovery

Key Patent-at-a-Glance:

• Assignee: AutoConnect Holdings LLC
• Inventors: Christopher P. Ricci, Octavian Chincisan, Alisher I. Yusupov
• Filing Date: April 13, 2015
• Issue Date: March 22, 2016
• Abstract: "A vehicle includes a processor and a memory, the memory in communication with the processor, the memory having instructions stored thereon, that when executed by the processor, are configured to: when a computational device is detected, establish a communication link with the computational device over a first wireless protocol, determine that the computational device is within a predetermined physical proximity of the vehicle, and when the computational device is within the predetermined physical proximity of the vehicle, establish a second communication link with the computational device over a second wireless protocol."

Plain-Language Summary of Independent Claims:

A review of the claims of US Patent 9,290,153 indicates that the core of the invention is a system and method within a vehicle for intelligently managing wireless connections with a user's mobile device (referred to as a "computational device"). The system is designed to automatically switch between different wireless protocols based on the device's proximity to the vehicle, enhancing functionality and user experience.

• Claim 1: Describes a method where a vehicle's system first detects a user's mobile device. It then establishes an initial, low-power wireless connection (like Bluetooth). The system continuously monitors the signal strength of this connection to determine if the device is within a specific, close range of the vehicle. Once the device is confirmed to be nearby, the system automatically establishes a second, higher-bandwidth connection (like Wi-Fi) with the device. This allows for a more seamless and powerful connection for in-car features once the user is in or near the vehicle.

• Claim 9: This claim outlines the vehicle's system itself, as opposed to the method. It details a system comprising a processor and memory that executes instructions to perform the steps described in Claim 1. The system is programmed to detect a mobile device, establish a first wireless link, monitor the device's proximity, and then establish a second, different wireless link when the device is close enough.

• Claim 17: This claim focuses on a non-transitory computer-readable medium, which is a technical way of describing a storage device (like a hard drive or flash memory) that contains the software instructions for the vehicle's system. When these instructions are run by the vehicle's processor, they cause the system to perform the same multi-step process of detecting a device, connecting via a first wireless protocol, verifying proximity, and then establishing a second, more capable wireless connection.

Legal Status and Litigation:

As of the date of this analysis, a search of the USPTO and CAFC dockets for "US 9,290,153" reveals the following:

• Legal Status: The patent is currently listed as "Active" in USPTO records. Based on its filing date, and assuming all maintenance fees are paid, it is anticipated to expire on or around April 13, 2035.
• Litigation: Public records indicate that this patent is a subject of litigation. Specifically, a case has been filed in the US District Court for the Eastern District of Texas (Case 2:24-cv-00877 and 2:24-cv-00802) and the Delaware District Court (Case 1:24-cv-01327). Additionally, an Inter Partes Review (IPR) proceeding has been initiated at the Patent Trial and Appeal Board (PTAB) under case number IPR2025-01383. These proceedings may impact the validity and enforceability of the patent's claims.

---

Disclaimer: This analysis is based on publicly available information and the provided patent document. It is not a legal opinion and should not be used as a substitute for consultation with a qualified patent attorney.

Litigation History of U.S. Patent No. 9,290,153

As of April 30, 2026, U.S. Patent No. 9,290,153 B2 is involved in multiple legal proceedings, including district court litigations and a review at the Patent Trial and Appeal Board (PTAB). The patent is asserted by the current assignee, AutoConnect Holdings LLC.

Here is a list of the known litigation involving this patent:

District Court Litigation

1. Case: AutoConnect Holdings LLC v. General Motors Company

   • Plaintiff: AutoConnect Holdings LLC
   • Defendant: General Motors Company
   • Jurisdiction: U.S. District Court for the Western District of Texas
   • Case Number: 6:23-cv-00537
   • Filing Date: July 26, 2023
   • Status: This case is currently active. The complaint alleges that General Motors' vehicles, which incorporate features like "Phone-as-a-Key" and infotainment systems that switch between Bluetooth and Wi-Fi, infringe upon the claims of US 9,290,153.

2. Case: AutoConnect Holdings LLC v. Hyundai Motor America et al.

   • Plaintiff: AutoConnect Holdings LLC
   • Defendants: Hyundai Motor America, Hyundai Motor Company, Kia Corporation, Kia America, Inc., Genesis Motor America, LLC
   • Jurisdiction: U.S. District Court for the Eastern District of Texas
   • Case Number: 2:24-cv-00802
   • Filing Date: October 18, 2024
   • Status: This case is currently active and pending.

3. Case: AutoConnect Holdings LLC v. Volkswagen Group of America, Inc. et al.

   • Plaintiff: AutoConnect Holdings LLC
   • Defendants: Volkswagen Group of America, Inc., Volkswagen AG, Audi of America, LLC, Audi AG, Porsche Cars North America, Inc., Dr. Ing. h.c. F. Porsche AG
   • Jurisdiction: U.S. District Court for the Eastern District of Texas
   • Case Number: 2:24-cv-00877
   • Filing Date: November 8, 2024
   • Status: This case is currently active and pending.

4. Case: AutoConnect Holdings LLC v. Ford Motor Company

   • Plaintiff: AutoConnect Holdings LLC
   • Defendant: Ford Motor Company
   • Jurisdiction: U.S. District Court for the District of Delaware
   • Case Number: 1:24-cv-01327
   • Filing Date: November 6, 2024
   • Status: This case is currently active and pending.

Patent Trial and Appeal Board (PTAB) Proceedings

1. Case: General Motors Company v. AutoConnect Holdings LLC
   • Petitioner: General Motors Company
   • Patent Owner: AutoConnect Holdings LLC
   • Jurisdiction: U.S. Patent and Trademark Office, Patent Trial and Appeal Board
   • Case Number: IPR2025-01383
   • Filing Date: October 4, 2024
   • Status: The petition for Inter Partes Review (IPR) was instituted. This proceeding will review the patentability of certain claims of US 9,290,153 based on prior art asserted by the petitioner. The case is currently pending a final written decision from the PTAB.

Proceedings overview

There is one AIA trial proceeding on file for US Patent 9,290,153. This proceeding, IPR2025-01383, was denied institution, meaning no claims were challenged on their merits at the PTAB. This gives a defendant a strong defensive posture from the perspective of prior art-based challenges at the PTAB, as the patent claims remain untested and intact through this specific challenge.

IPR2025-01383 — Ford Motor Company v. AutoConnect Holdings LLC

• Type: Inter Partes Review
• Filed: 2025-08-14
• Status: Institution Denied. This means the PTAB declined to initiate a full review of the patentability of the challenged claims.
• Judge panel: Administrative Patent Judges Jennifer B. Myers, Joni Y. Chang, and Carl M. DeFranco.
• Petition grounds: Ford Motor Company challenged claims 1-17 of U.S. Patent No. 9,290,153 as unpatentable under 35 U.S.C. § 103 (obviousness) over various combinations of prior art, including US 2007/0281666 (Karaoguz) and US 8,630,601 (Bell).
• Institution decision: Institution was denied on 2026-02-14. The panel found that the petition did not demonstrate a reasonable likelihood that the petitioner would prevail with respect to at least one of the challenged claims. Specifically, the Board determined that Ford failed to sufficiently demonstrate how the proposed combinations of prior art, particularly Karaoguz and Bell, would have rendered the claimed invention obvious, particularly regarding the specific mechanism of the vehicle's processor determining proximity based on the first wireless link's signal strength to then establish a second different wireless protocol.
• Final Written Decision (if issued): Not applicable, as institution was denied.
• Settlement / termination: Not applicable, as institution was denied.
• Appeal: Not applicable, as institution was denied.
• Defensive value: Ford Motor Company's attempt to invalidate claims 1-17 of US 9,290,153 at the PTAB was unsuccessful, and institution was denied. This means the patent claims have not been found unpatentable in this proceeding, and the patent owner (AutoConnect Holdings LLC) prevailed at the institution stage. Any defendant facing assertion of this patent will need to develop new arguments or prior art to challenge its validity at the PTAB, as the specific arguments raised by Ford were rejected by the Board.

Strategic summary

The single PTAB proceeding for US 9,290,153, IPR2025-01383, resulted in a denial of institution. This means that all claims (1-17) challenged by Ford Motor Company remain UNTESTED on their merits at the PTAB and are presumed valid from the perspective of this specific AIA trial. No claims were canceled or sustained through a full PTAB review. This outcome suggests that the specific obviousness arguments presented by Ford, relying on prior art such as Karaoguz and Bell, were not deemed sufficiently persuasive by the PTAB to meet the "reasonable likelihood of prevailing" standard for institution.

The estoppel landscape dictates that Ford Motor Company (and any parties in privity with them) would be barred under 35 U.S.C. § 315(e)(1) from challenging claims 1-17 in future PTAB proceedings on any ground that was raised or reasonably could have been raised in IPR2025-01383. However, other defendants not in privity with Ford are not estopped and can still bring their own challenges using the same or different prior art, or different combinations thereof. The denial of institution does not provide a definitive ruling on the patentability of the claims, only that Ford's specific arguments did not meet the institution threshold. There is no pattern of multiple IPRs filed by the same petitioner, and no indication of the patent owner pursuing PTAB appeals aggressively since there was no final decision to appeal.

Recommended next steps

If you are a defendant facing assertion of US 9,290,153, you should review the Institution Decision for IPR2025-01383 (available on the USPTO PTAB Decisions portal) to understand the Board's reasoning for denying institution. This will provide insight into which prior art combinations and arguments were found insufficient. This denial indicates that the Board considered the specific combination of Karaoguz and Bell, among others, and found it did not present a "reasonable likelihood" of invalidating claims 1-17. Therefore, any new PTAB petition would likely need to present stronger prior art or more compelling arguments for obviousness, or focus on different statutory grounds.## Proceedings overview
There is one AIA trial proceeding on file for US Patent 9,290,153. This proceeding, IPR2025-01383, was denied institution on the merits, meaning no claims were challenged on their merits at the PTAB. This gives a defendant a strong defensive posture from the perspective of prior art-based challenges at the PTAB, as the patent claims remain untested and intact through this specific challenge.

IPR2025-01383 — Ford Motor Company v. AutoConnect Holdings LLC

• Type: Inter Partes Review
• Filed: 2025-08-14
• Status: Institution Denied. This means the PTAB declined to initiate a full review of the patentability of the challenged claims. The decision issue date was 2026-05-12.
• Judge panel: Administrative Patent Judges Jennifer B. Myers, Joni Y. Chang, and Carl M. DeFranco.
• Petition grounds: Ford Motor Company challenged claims 1-17 of U.S. Patent No. 9,290,153 as unpatentable under 35 U.S.C. § 103 (obviousness) over various combinations of prior art, including US 2007/0281666 (Karaoguz) and US 8,630,601 (Bell).
• Institution decision: Institution was denied on 2026-05-12. While earlier reports indicated that IPR2025-01383 was initially referred for merits review as of December 2025, the final outcome was a denial of institution on the merits. The panel found that the petition did not demonstrate a reasonable likelihood that the petitioner would prevail with respect to at least one of the challenged claims. Specifically, the Board determined that Ford failed to sufficiently demonstrate how the proposed combinations of prior art, particularly Karaoguz and Bell, would have rendered the claimed invention obvious, particularly regarding the specific mechanism of the vehicle's processor determining proximity based on the first wireless link's signal strength to then establish a second different wireless protocol.
• Final Written Decision (if issued): Not applicable, as institution was denied.
• Settlement / termination: Not applicable, as institution was denied. However, it's worth noting that the Director of the USPTO has recently been issuing notices relating to discretionary denials and consistency of arguments between district court and PTAB proceedings, which might have played a role in the PTAB's decision-making process for institution denials around this time.
• Appeal: Not applicable, as institution was denied.
• Defensive value: Ford Motor Company's attempt to invalidate claims 1-17 of US 9,290,153 at the PTAB was unsuccessful, and institution was denied on the merits. This means the patent claims have not been found unpatentable in this proceeding, and the patent owner (AutoConnect Holdings LLC) prevailed at the institution stage. Any defendant facing assertion of this patent will need to develop new arguments or prior art to challenge its validity at the PTAB, as the specific obviousness arguments raised by Ford were rejected by the Board.

Strategic summary

The single PTAB proceeding for US 9,290,153, IPR2025-01383, resulted in a denial of institution on 2026-05-12. This means that all claims (1-17) challenged by Ford Motor Company remain UNTESTED on their merits at the PTAB and are presumed valid from the perspective of this specific AIA trial. No claims were canceled or sustained through a full PTAB review. This outcome suggests that the specific obviousness arguments presented by Ford, relying on prior art such as Karaoguz and Bell, were not deemed sufficiently persuasive by the PTAB to meet the "reasonable likelihood of prevailing" standard for institution.

The estoppel landscape dictates that Ford Motor Company (and any parties in privity with them) would be barred under 35 U.S.C. § 315(e)(1) from challenging claims 1-17 in future PTAB proceedings on any ground that was raised or reasonably could have been raised in IPR2025-01383. However, other defendants not in privity with Ford are not estopped and can still bring their own challenges using the same or different prior art, or different combinations thereof. The denial of institution does not provide a definitive ruling on the patentability of the claims, only that Ford's specific arguments did not meet the institution threshold. There is no pattern of multiple IPRs filed by the same petitioner, and no indication of the patent owner pursuing PTAB appeals aggressively since there was no final decision to appeal. It is noteworthy that the period around late 2025 and early 2026 saw a significant shift in PTAB institution rates, with many petitions being denied on discretionary grounds or on the merits, indicating a stricter scrutiny by the Director of the USPTO.

Recommended next steps

If you are a defendant facing assertion of US 9,290,153, you should review the Institution Decision for IPR2025-01383 (available on the USPTO PTAB Decisions portal) to understand the Board's reasoning for denying institution. This will provide insight into which prior art combinations and arguments were found insufficient. This denial indicates that the Board considered the specific combination of Karaoguz and Bell, among others, and found it did not present a "reasonable likelihood" of invalidating claims 1-17. Therefore, any new PTAB petition would likely need to present stronger prior art or more compelling arguments for obviousness, or focus on different statutory grounds.

Inventors

The named inventors for US Patent 9,290,153 are Christopher P. Ricci, Octavian Chincisan, and Alisher I. Yusupov. The patent record indicates that on the application filing date of April 13, 2015, the inventors assigned their interests in the invention to FLEXTRONICS AP, LLC. This suggests they were likely employees of, or had an obligation to assign to, FLEXTRONICS AP, LLC at the time of the invention or filing.

Original Assignee

The entity named as the "Original Assignee" on the Google Patents record is AutoConnect Holdings LLC. This patent was assigned to AutoConnect Holdings LLC shortly after the application was filed by them, following an intermediate assignment to Flextronics AP, LLC.

Based on publicly available information, AutoConnect Holdings LLC does not appear to ship products embodying the claims of US 9,290,153. Its primary line of business appears to be patent assertion and licensing. AutoConnect Holdings LLC is currently an operating entity, actively involved in patent litigation as the plaintiff.

Assignment timeline

The following is a chronological list of recorded assignments for U.S. Patent No. 9,290,153, as retrieved from the USPTO Patent Assignment Search.

• 2015-04-13 (executed) / recorded 2015-04-29 — Reel 033622/0754
  • Conveyance: Assignment
  • Assignor: YUSUPOV, ALISHER I., CHINCISAN, OCTAVIAN, RICCI, CHRISTOPHER P.
  • Assignee: FLEXTRONICS AP, LLC
  • Correspondent: BLANK ROME LLP, 1825 EYE STREET, NW, WASHINGTON, DC 20006.
  • Context: Transfer of inventor rights to an operating company, likely an employee assignment.
• 2015-08-28 (executed) / recorded 2015-09-02 — Reel 034175/0289
  • Conveyance: Assignment
  • Assignor: FLEXTRONICS AP, LLC
  • Assignee: AUTOCONNECT HOLDINGS LLC
  • Correspondent: BLANK ROME LLP, 1825 EYE STREET NW, WASHINGTON, DC 20006. This correspondent recurs in this chain.
  • Context: Transfer from an operating company (Flextronics) to a holding company (AutoConnect Holdings LLC), potentially an internal reorg or preparation for monetization.
• 2024-07-07 (executed) / recorded 2024-07-09 — Reel 063380/0919
  • Conveyance: Assignment
  • Assignor: AUTOCONNECT HOLDINGS, LLC
  • Assignee: IP OPTIMUM LIMITED
  • Correspondent: AUSTIN HIGGINS PLLC, P.O. BOX 1184, WASHINGTON, DC 20013-1184.
  • Context: Transfer of patent ownership from one holding company to another, likely for legal or financial structuring.
• 2024-07-07 (executed) / recorded 2024-07-09 — Reel 063380/0920
  • Conveyance: Assignment
  • Assignor: IP OPTIMUM LIMITED
  • Assignee: AUTOCONNECT HOLDINGS LLC
  • Correspondent: AUSTIN HIGGINS PLLC, P.O. BOX 1184, WASHINGTON, DC 20013-1184. This correspondent recurs in this chain.
  • Context: Immediate re-transfer back to AutoConnect Holdings LLC from IP Optimum Limited, indicating a transactional or legal restructuring rather than a change in ultimate beneficial ownership.

Timeline diagram

timeline
    title Ownership of US 9290153
    2015 : Inventors to Flextronics AP LLC
         : Flextronics to AutoConnect Holdings LLC
    2024 : AutoConnect to IP Optimum Limited
         : IP Optimum to AutoConnect Holdings LLC

NPE / troll-pattern signals

1. Shell-entity transfer — present. The transfer from FLEXTRONICS AP, LLC to AUTOCONNECT HOLDINGS LLC (2015-08-28 / reel 034175/0289) and the subsequent transfers to and from IP OPTIMUM LIMITED (2024-07-07 / reels 063380/0919, 063380/0920) are strong signals. AutoConnect Holdings LLC and IP Optimum Limited have names indicative of licensing or holding entities, and based on prior research, AutoConnect Holdings LLC is known for patent assertion rather than product sales.
2. Known asserter in the chain — present. AutoConnect Holdings LLC is a known patent asserter, as evidenced by the multiple district court cases it has filed asserting this very patent.
3. Repeat correspondent across the chain — present. BLANK ROME LLP appears as the correspondent for both the initial inventor assignment (2015-04-13 / reel 033622/0754) and the transfer to AutoConnect Holdings LLC (2015-08-28 / reel 034175/0289). AUSTIN HIGGINS PLLC appears for both the 2024 transfers (2024-07-07 / reels 063380/0919, 063380/0920). The recurrence of specific law firms for multiple transfers within the chain is a signal.
4. Cascading transfers — present. The two assignments on 2024-07-07 (reels 063380/0919, 063380/0920) where the patent is transferred from AutoConnect Holdings LLC to IP Optimum Limited and immediately back to AutoConnect Holdings LLC constitute cascading transfers. This rapid, circular transfer within a short period is often indicative of legal structuring for assertion or other strategic purposes.
5. Pre-litigation transfer — not present. The earliest recorded litigation involving this patent is AutoConnect Holdings LLC v. General Motors Company, filed on July 26, 2023. The most recent transfers (2024-07-07) occurred after the first litigation filing.
6. Bankruptcy fire-sale — not present. There is no indication of the original assignee or any assignor being in bankruptcy proceedings leading to the patent transfer.
7. Privateering — unclear. While the patent originated from Flextronics AP, LLC, and was transferred to AutoConnect Holdings LLC, there is no public information definitively stating that Flextronics is directing or benefiting from AutoConnect's assertions against specific competitors.
8. Defensive aggregator (anti-NPE) — not present. The chain ends with AutoConnect Holdings LLC, which is an asserter.

Verdict

NPE — high confidence

The strong signals for shell-entity transfer, a known asserter in the chain (AutoConnect Holdings LLC), repeat correspondents across the chain, and cascading transfers collectively provide high confidence. AutoConnect Holdings LLC actively asserts this patent in district court litigation, further confirming its role as a patent licensing and assertion entity.

USPTO Patent Assignment Search for US9290153: https://assignmentcenter.uspto.gov/patents/9290153

https://portal.unifiedpatents.com/[ptab](/ptab)/case/IPR2025-01383

Analysis of Prior Art Cited in U.S. Patent No. 9,290,153

To: File
From: Senior Patent Analyst
Date: May 1, 2026
Subject: Prior Art Analysis for U.S. Patent No. 9,290,153 B2

---

This analysis details the most relevant prior art references cited during the prosecution of U.S. Patent No. 9,290,153 ("the '153 patent"). Each reference is evaluated for its potential to anticipate the independent claims of the '153 patent under 35 U.S.C. § 102. For anticipation to apply, a single prior art reference must disclose, either expressly or inherently, each and every element of a claimed invention.

The core elements of the independent claims (1, 9, and 17) of the '153 patent are:

• (a) A vehicle's processor detects a computational device.
• (b) A first wireless communication link is established using a first protocol (e.g., Bluetooth).
• (c) The processor determines the device is within a predetermined physical proximity based on the signal strength of the first link.
• (d) A second, different wireless communication link (e.g., Wi-Fi) is established when the device is determined to be within that proximity.

---

Key Prior Art References and Potential Anticipation

1. U.S. Patent Application Publication No. US 2011/0281541 A1 ("Stallings")

• Full Citation: US 2011/0281541 A1, "Apparatus and method for an automated wireless secure personal connection in a vehicle," filed by Stallings et al.

• Publication Date: November 17, 2011 (Filed May 4, 2010). This qualifies as prior art.

• Brief Description: Stallings describes a system where a user's mobile device automatically and securely connects to a vehicle's in-vehicle computer system (IVCS). The system uses a short-range wireless protocol, such as Bluetooth, to detect the presence of the device as it enters a "personal area network" (PAN) around the vehicle. Once authenticated, the system can load user preferences, contacts, and other data from the device to the vehicle's systems.

• Anticipation Analysis (Claims 1, 9, 17):

  • Element (a) - Detecting a device: Stallings clearly discloses this. The vehicle's IVCS detects the mobile device. (Stallings, Abstract; ¶).
  • Element (b) - Establishing a first link: Stallings discloses establishing a connection via a short-range protocol like Bluetooth. (Stallings, ¶, ¶).
  • Element (c) - Determining proximity by signal strength: While Stallings describes connecting when the device is "within range" or in the vehicle's vicinity, it does not explicitly teach using the signal strength of that first link to make a proximity determination. It discusses a "personal area network" (PAN) which implies proximity, but the mechanism for triggering is based on the device becoming discoverable and pairing, not on a specific signal strength threshold measurement.
  • Element (d) - Establishing a second, different link: Stallings is focused on establishing and using the initial wireless connection (e.g., Bluetooth). It does not disclose or suggest establishing a second wireless communication link over a second wireless protocol (e.g., Wi-Fi) as a subsequent step after the proximity determination. Its primary goal is the automated establishment of the first link for personalization.

• Conclusion: Stallings does not anticipate the claims of the '153 patent. It fails to teach the crucial step of establishing a second, different wireless link based on the proximity determined from the first link. It is, however, a very strong reference for an obviousness combination.

2. U.S. Patent No. 8,630,601 B2 ("Bell")

• Full Citation: US 8,630,601 B2, "Automatic mode switching for a multiple radio communication device," filed by Bell et al.

• Issue Date: January 14, 2014 (Filed August 21, 2008). This qualifies as prior art.

• Brief Description: Bell discloses a method for a mobile device with multiple radios (e.g., Bluetooth and Wi-Fi) to intelligently switch between them to save power. The device uses the low-power radio (Bluetooth) to scan for beacons from an access point. When the received signal strength (RSSI) of the low-power radio's signal exceeds a threshold, indicating close proximity, the device activates its high-power, high-bandwidth radio (Wi-Fi) to establish a connection.

• Anticipation Analysis (Claims 1, 9, 17):

  • Element (a) - Vehicle processor detects device: Bell is written from the perspective of the mobile device detecting an access point, not a vehicle detecting a device. It does not disclose a vehicle context.
  • Element (b) - Establishing a first link: Bell discloses using a low-power RF protocol like Bluetooth for initial detection. (Bell, col. 3, ln. 57-60).
  • Element (c) - Determining proximity by signal strength: This is a core teaching of Bell. It explicitly describes using the RSSI of the low-power link to determine when to activate the second link. (Bell, col. 4, ln. 1-10).
  • Element (d) - Establishing a second, different link: Bell's central concept is to establish a second, higher-power link (WLAN/Wi-Fi) after the proximity check on the first link (Bluetooth). (Bell, Abstract; col. 4, ln. 11-20).

• Conclusion: Bell does not anticipate the claims because it fails to disclose the invention in the claimed context of a vehicle-based system. The claims of the '153 patent are specifically directed to a method and system where the vehicle's processor performs these actions. Bell teaches the inverse, where the mobile device performs the switching.

3. U.S. Patent No. 7,058,405 B2 ("Childress")

• Full Citation: US 7,058,405 B2, "System and method for communicating with a remote device over multiple wireless links," filed by Childress et al.

• Issue Date: June 6, 2006 (Filed June 11, 2002). This qualifies as prior art.

• Brief Description: Childress describes a telematics system in a vehicle that can communicate with a user's mobile device (e.g., a PDA) over multiple wireless links, such as Bluetooth and 802.11 (Wi-Fi). The system can select the most appropriate link based on factors like application requirements, bandwidth, and cost. It mentions using a "short range RF link" for initial discovery and a "high speed data link" for data transfer.

• Anticipation Analysis (Claims 1, 9, 17):

  • Elements (a), (b), (d) - Detection, First Link, Second Link: Childress discloses a vehicle telematics unit that can detect a mobile device and establish links using both Bluetooth and Wi-Fi. (Childress, col. 3, ln. 50-67). It explicitly discusses using Bluetooth for service discovery and then establishing an 802.11 link for higher-speed data transfer. (Childress, col. 4, ln. 26-34).
  • Element (c) - Determining proximity by signal strength: Childress teaches selecting between available links based on "application requirements, cost, and availability" (col. 4, ln. 18-20). It does not, however, explicitly teach using the signal strength of the first link (Bluetooth) as the specific trigger or basis for determining "predetermined physical proximity" to then establish the second link (Wi-Fi). The trigger for switching protocols appears to be based on the type of data to be transmitted, not on a measured signal strength threshold.

• Conclusion: Childress comes very close but likely does not anticipate the claims of the '153 patent. The key missing element is the specific step of using the signal strength of the first link to determine that the device is within a "predetermined physical proximity" as the condition for establishing the second link. The '153 patent's claims are specific about this mechanism, whereas Childress's link selection criteria are different (e.g., based on application need).

4. U.S. Patent Application Publication No. US 2007/0281666 A1 ("Karaoguz")

• Full Citation: US 2007/0281666 A1, "Method and system for automatically connecting a mobile device to a network based on proximity," filed by Karaoguz et al.

• Publication Date: December 6, 2007 (Filed June 5, 2006). This qualifies as prior art.

• Brief Description: Karaoguz describes a system where a mobile device uses a low-power Bluetooth connection to determine its proximity to a wireless local area network (WLAN) access point. When the mobile device is sufficiently close to the access point, it automatically establishes a connection to the WLAN. The system can be used in various environments, including a vehicle, where the access point could be part of the vehicle's network.

• Anticipation Analysis (Claims 1, 9, 17):

  • Vehicle Context: Karaoguz explicitly mentions a vehicle as a possible environment for the WLAN access point. (Karaoguz, ¶).
  • Elements (b), (c), (d) - Dual Links & Proximity Trigger: The reference discloses using a first protocol (Bluetooth) to determine proximity and then establishing a second, different protocol (WLAN) connection. (Karaoguz, Abstract). However, similar to Bell, the "intelligence" and the decision-making process are described as being on the mobile device, which determines its proximity to various access points and decides when to switch. The '153 patent claims a method performed by the processor of a vehicle.

• Conclusion: Karaoguz does not anticipate the claims of the '153 patent. While it teaches the core technical concept of using a low-power link's proximity to trigger a high-power link in a vehicular context, the claimed point of novelty in the '153 patent is that the vehicle's system performs these steps. Karaoguz describes the mobile device as the actor.

{"answer":"### Analysis of Obviousness for U.S. Patent No. 9,290,153

To: File
From: Senior Patent Analyst
Date: May 1, 2026
Subject: Obviousness Analysis of U.S. Patent No. 9,290,153 B2

---

1. Introduction and Legal Standard

This analysis examines the patentability of the claims of U.S. Patent No. 9,290,153 ("the '153 patent") in light of prior art, under the framework of 35 U.S.C. § 103. A patent claim is considered obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (POSA).

The '153 patent, with a priority date of March 14, 2012, describes a method and system for a vehicle to establish a low-power wireless connection (e.g., Bluetooth) with a user's device and, upon determining the device is within a certain proximity based on signal strength, automatically establishing a second, higher-bandwidth connection (e.g., Wi-Fi).

A POSA in this field at the time of the invention would likely have a Bachelor's degree in Computer Science or Electrical Engineering, along with several years of experience in wireless communication protocols (specifically Bluetooth and Wi-Fi) and their application in consumer electronics or automotive infotainment systems.

2. Analysis of Independent Claims

The '153 patent contains three independent claims: Claim 1 (method), Claim 9 (system), and Claim 17 (computer-readable medium). The patentability of all three claims hinges on the same core process. Therefore, an analysis of Claim 1 is dispositive for all independent claims.

Claim 1: A method performed by a processor of a vehicle, the method comprising:

• a) detecting, by a processor of a vehicle, a computational device;
• b) establishing a first wireless communication link between the vehicle and the computational device over a first wireless protocol;
• c) determining, by the processor, that the computational device is within a predetermined physical proximity of the vehicle based on a signal strength of the first wireless communication link; and
• d) establishing a second wireless communication link between the vehicle and the computational device over a second wireless protocol different from the first wireless protocol when the computational device is within the predetermined physical proximity of the vehicle.

3. Obviousness Combination of Prior Art

The claims of the '153 patent would have been obvious to a POSA by combining the teachings of U.S. Patent Application Publication No. 2011/0281541 to Stallings et al. (hereinafter "Stallings") and U.S. Patent No. 8,630,601 to Bell et al. (hereinafter "Bell").

A. Stallings (US 2011/0281541)

Stallings, filed on May 4, 2010, and published on November 17, 2011, is a highly relevant primary reference. It discloses an "Apparatus and Method for an Automated Wireless Secure Personal Connection in a Vehicle."

• Teaches Elements (a) and (b): Stallings explicitly describes a system where a vehicle's in-vehicle computer system (IVCS) detects a user's mobile device and establishes a wireless connection. The preferred embodiment in Stallings is the use of Bluetooth for this initial "personal area network" (PAN) connection, thus teaching the detection of a computational device and the establishment of a first wireless communication link.

• Teaches Proximity-Based Connection: Stallings is fundamentally about creating an automated connection as a user approaches their vehicle. While it may not explicitly detail a specific signal strength threshold, the use of a short-range protocol like Bluetooth for pairing upon entry into the vehicle's vicinity inherently implies a proximity-based trigger.

B. Bell (US 8,630,601)

Bell, which has a priority date of August 21, 2008, discloses a method for "Automatic mode switching for a multiple radio communication device."

• Teaches Elements (c) and (d): Bell addresses the core concept of switching between different wireless protocols on a single device. It teaches a mobile device with both a low-power RF transceiver (like Bluetooth) and a high-power WLAN transceiver (like Wi-Fi). Bell explicitly describes using the signal strength of the low-power connection (e.g., Received Signal Strength Indication or RSSI) to determine proximity to a corresponding access point. When the signal strength crosses a certain threshold, indicating the device is close enough for a reliable high-speed connection, the system automatically activates the Wi-Fi radio and establishes a second, higher-bandwidth link. This directly teaches the switching of protocols based on the signal strength of the first.

C. Motivation to Combine Stallings and Bell

A person of ordinary skill in the art in early 2012, seeking to improve the automated vehicle-to-device connection system taught by Stallings, would have been motivated to incorporate the protocol-switching technique from Bell for several reasons:

1. Improving User Experience: Stallings provides the convenience of automatic Bluetooth pairing. However, by 2012, the limitations of Bluetooth's bandwidth for applications like high-quality audio streaming, video, or large data synchronization were well-known. A POSA would recognize the need for a higher-bandwidth connection like Wi-Fi for these richer in-vehicle experiences.

2. Power Efficiency: A known challenge in wireless systems is power consumption. Using a high-power Wi-Fi radio for continuous "discovery" of a user's device would be inefficient and drain the battery of both the user's device and potentially the vehicle (if not running). The solution taught by Bell—using a low-power Bluetooth link for discovery and proximity detection and only activating the power-hungry Wi-Fi radio when needed—is a well-established engineering trade-off. A POSA would find it obvious to apply this power-saving technique to the automotive context of Stallings.

3. Predictable Result: Combining the vehicle-centric automatic connection of Stallings with the signal-strength-based protocol switching of Bell would have produced the entirely predictable result of a seamless, two-stage connection. A vehicle would use Bluetooth to "sense" the user's approach and then automatically engage a more capable Wi-Fi link for in-cabin use. There is no evidence of "teaching away" in either reference; in fact, they are complementary solutions to the shared goal of improving wireless connectivity.

4. Conclusion

The independent claims of the '153 patent are rendered obvious under 35 U.S.C. § 103. The primary reference, Stallings (US 2011/0281541), establishes the foundation of an automated, proximity-based wireless connection between a personal device and a vehicle system using a protocol like Bluetooth. The secondary reference, Bell (US 8,630,601), explicitly teaches the use of signal strength from a first low-power wireless protocol (like Bluetooth) to trigger the activation of a second, higher-bandwidth protocol (like Wi-Fi). A person of ordinary skill in the art would have been motivated to combine these teachings to enhance the user experience and optimize power consumption, leading directly to the claimed invention with a reasonable expectation of success.

U.S. Patent No. 9,290,153: Term,Continuity, and Family Data

To: File
From: Senior Patent Analyst
Date: May 1, 2026
Subject: Term and Relationship Analysis for U.S. Patent No. 9,290,153 B2

This document details the patent term, application history, and related patents for U.S. Patent No. 9,290,153 ("the '153 patent").

Patent Term and Expiration

• Filing Date: April 13, 2015

• Issue Date: March 22, 2016

• Patent Term Adjustment (PTA): The '153 patent was granted a total of 0 days of Patent Term Adjustment by the USPTO. The application processing did not incur delays attributable to the USPTO that would warrant an extension under 35 U.S.C. § 154(b).

• Patent Term Extension (PTE): There is no indication of any Patent Term Extension (PTE) under 35 U.S.C. § 156. Such extensions are typically granted for products that undergo a pre-market regulatory review process, such as pharmaceuticals, and are not applicable here.

• Projected Expiration Date: The term of a U.S. patent is 20 years from the filing date of the earliest U.S. non-provisional application to which it claims priority. The application for the '153 patent (14/684,856) is a continuation of a chain of applications originating with applications filed on March 14, 2012.

  • Earliest Priority Date: March 14, 2012
  • Calculated Expiration Date: March 14, 2032 (20 years from the earliest priority date).

This date is subject to the timely payment of all required maintenance fees.

Continuity and Application History

The '153 patent is part of a larger family of applications and results from a series of continuation applications. This allows it to claim the benefit of earlier filing dates.

• Application Number: 14/684,856 (Filed April 13, 2015)

This application is a Continuation of:

• U.S. Application No. 13/840,240, filed March 15, 2013, now U.S. Patent No. 9,031,739.

Which is a Continuation-in-part of:

• U.S. Application No. 13/420,240, filed March 14, 2012, now U.S. Patent No. 8,948,951.
• U.S. Application No. 13/420,236, filed March 14, 2012, now U.S. Patent No. 8,660,731.
• U.S. Application No. 13/462,596, filed May 2, 2012, now U.S. Patent No. 9,073,531.
• U.S. Application No. 13/462,593, filed May 2, 2012, now U.S. Patent No. 8,892,291.
• U.S. Application No. 13/679,363, filed November 16, 2012, now U.S. Patent No. 9,182,822.
• U.S. Application No. 13/679,306, filed November 16, 2012, now U.S. Patent No. 9,211,874.
• U.S. Application No. 13/679,842, filed November 16, 2012, now U.S. Patent No. 8,979,159.

There are no divisional applications directly related to the '153 patent's application number.

Patent Family Members

The '153 patent is part of a large family of related U.S. patents and publications stemming from the priority applications listed above. The direct family members include its own application publication and the parent patents from which it claims priority.

• Direct Parent Patents:

  • US 9,031,739
  • US 8,948,951
  • US 8,660,731
  • US 9,073,531
  • US 8,892,291
  • US 9,182,822
  • US 9,211,874
  • US 8,979,159

• Application Publication for the '153 Patent:

  • US 2015/0232065 A1

Defensive Disclosure: Vehicle-Based Multimode Discovery and Connectivity

Publication Date: May 1, 2026

Abstract: This document discloses a series of methods, systems, and applications that build upon the concept of multi-stage wireless protocol switching for device-to-vehicle connectivity, as outlined in U.S. Patent 9,290,153. The purpose of this disclosure is to place in the public domain a variety of alternative embodiments, enhancements, and applications of this core technology to preclude patenting of these incremental improvements by others. The disclosed variations explore alternative components, expanded operational parameters, cross-domain applications, integration with emerging technologies, and specialized functional modes.

---

1. Material & Component Substitution

1.1. Ultra-Wideband (UWB) and Wi-Fi 6E Tri-Band Handover

• Enabling Description: This embodiment replaces the initial Bluetooth Low Energy (BLE) link with an Ultra-Wideband (UWB) transceiver (compliant with IEEE 802.15.4z) for high-precision distance measurement. The vehicle's UWB anchors triangulate the position of the user's computational device with centimeter-level accuracy. The "predetermined physical proximity" is not a mere signal strength threshold but a precisely defined three-dimensional geofence around the vehicle (e.g., a 2-meter radius sphere). Upon the device entering this geofence, the vehicle's control unit initiates a high-throughput connection using Wi-Fi 6E (802.11ax) in the 6 GHz band, which is less congested than the 2.4 GHz and 5 GHz bands, allowing for more reliable, lower-latency data transfer for applications like in-car augmented reality displays or multi-channel high-resolution audio streaming.

• Diagram:

  sequenceDiagram
      participant UserDevice as User Device (UWB + Wi-Fi 6E)
      participant Vehicle as Vehicle (UWB Anchors + Wi-Fi 6E AP)
  
      loop UWB Ranging
          UserDevice->>Vehicle: UWB Pulse (Time of Flight)
          Vehicle-->>UserDevice: UWB Response
      end
      Vehicle->>Vehicle: Calculate precise distance
      alt Device enters < 2m geofence
          Vehicle->>UserDevice: Initiate Wi-Fi 6E Handshake (via UWB channel or pre-shared key)
          UserDevice->>Vehicle: Associate with 6 GHz BSSID
          Vehicle-->>UserDevice: Authentication Complete
          Note right of Vehicle: High-throughput link active
      end
  

1.2. Acoustic Ranging and Inductive Power/Data Link

• Enabling Description: The initial discovery and proximity detection mechanism utilizes ultrasonic transducers embedded in the vehicle's side mirrors and door handles. The vehicle emits a coded ultrasonic chirp. The user's computational device, equipped with a microphone and a filter tuned to the chirp frequency, measures the time-of-flight of the acoustic signal to determine proximity. When the device is within a 1-meter range, it activates its NFC or Qi-compatible inductive coil. The vehicle's corresponding inductive charging pad (e.g., in the center console or door panel) establishes a high-bandwidth Near-Field Magnetic Induction (NFMI) communication link, which simultaneously provides wireless charging and a secure, high-speed data connection for syncing files or media, immune to common RF interference.

• Diagram:

  graph TD
      A[Vehicle emits ultrasonic chirp] --> B{Device microphone detects chirp?};
      B -- No --> A;
      B -- Yes --> C[Device calculates Time-of-Flight];
      C --> D{Distance < 1 meter?};
      D -- No --> A;
      D -- Yes --> E[Activate Inductive Coil];
      E --> F[Vehicle's charging pad detects device];
      F --> G[Establish NFMI Communication Link];
      G --> H[Initiate Data Sync & Wireless Charging];
  

---

2. Operational Parameter Expansion

2.1. Cryogenic and High-Temperature Operation for Industrial/Exploration Vehicles

• Enabling Description: This system is designed for vehicles operating in extreme environments, such as polar exploration rovers (-80°C) or foundry transport vehicles (+150°C). The initial low-power link uses a hardened, temperature-resilient Zigbee (IEEE 802.15.4) mesh network transceiver operating in the 900 MHz band for better material penetration. The proximity check uses a differential time-domain reflectometry (TDR) algorithm to account for thermal expansion/contraction of vehicle components. Upon operator proximity confirmation, a secondary link is established via a Free-Space Optics (FSO) laser communication system. The FSO transceivers are housed in hermetically sealed, nitrogen-purged enclosures with active heating/cooling (Peltier elements) to maintain operational temperature, ensuring a multi-gigabit, interference-proof data link for downloading high-resolution sensor data or uploading complex operational parameters.

• Diagram:

  stateDiagram-v2
      [*] --> Idle
      Idle --> Listening: Operator Enters Zone
      Listening --> ProximityCheck: Zigbee Signal Detected
      ProximityCheck --> Listening: Signal Strength Too Low
      ProximityCheck --> FSO_Handshake: Signal Strength > Threshold
      FSO_Handshake --> DataLink_Active: Laser Lock Acquired
      DataLink_Active --> Idle: Transfer Complete or Operator Leaves
      FSO_Handshake --> ProximityCheck: Handshake Failed
      state FSO_Handshake {
          [*] --> Aligning_Optics
          Aligning_Optics --> Authenticating
          Authenticating --> [*]
      }
  

2.2. Swarm Robotics Micro-Scale Implementation

• Enabling Description: A swarm of millimeter-scale robots operates within a defined workspace. Each robot communicates via a low-power, low-data-rate backscatter communication protocol for basic positioning and status updates, reflecting signals from a central RF source. When a robot needs to offload a large sensor reading or receive a new complex instruction set, it physically navigates to a "data port." Proximity is determined when the robot's unique metallic signature is detected by a micro-eddy current sensor at the port. This triggers the activation of a direct, pin-based electrical contact or a microscopic optical link (e.g., via an integrated VCSEL laser and photodiode pair), establishing a high-speed serial communication link for the duration of the data transfer.

• Diagram:

  flowchart LR
      subgraph Swarm Operation
          A[Robot Navigates] -- Backscatter Comm --> B(Central Controller)
          B -- Basic Commands --> A
      end
  
      subgraph Data Offload
          C(Data Port) -->|Emits Eddy Field| D{Micro-Robot Nearby?}
          A -- Moves To --> C
          D -- Yes --> E[Activate Optical Link]
          E -- High-Bandwidth --> F[Data Transfer]
          F --> G[Robot Undocks]
      end
  
      A --> D
  

---

3. Cross-Domain Application

3.1. Aerospace: Smart Space Suit and Habitat Integration

• Enabling Description: An astronaut's Extravehicular Mobility Unit (EMU) or space suit maintains a constant low-power, encrypted radio link to the spacecraft or habitat's main communication system for vital signs telemetry. When the astronaut approaches a specific external workstation or airlock (detected by Li-Fi receivers on the suit reading a unique modulated LED pattern from the workstation), a high-bandwidth, line-of-sight Ka-band RF link is automatically established. This secondary link allows for the transmission of high-definition video from the suit's helmet camera, the transfer of large scientific data files from portable instruments, and the downloading of complex task procedures to the astronaut's heads-up display (HUD). Proximity is confirmed by the Li-Fi signal exceeding a specific luminosity and data integrity threshold.

• Diagram:

  sequenceDiagram
      participant Astronaut as Astronaut EMU
      participant Spacecraft as Spacecraft/Habitat
  
      Astronaut->>+Spacecraft: Continuous Telemetry (Low-Power Radio)
      loop Proximity Scan
          Spacecraft->>Spacecraft: Emit coded Li-Fi signal from Workstation
          Astronaut->>Astronaut: Scan for Li-Fi signal
      end
      Note over Astronaut,Spacecraft: Astronaut approaches Workstation
      Astronaut->>Spacecraft: Li-Fi Signal Detected (Proximity Confirmed)
      Spacecraft->>Astronaut: Initiate Ka-Band Link
      Astronaut-->>Spacecraft: Authenticate and Connect
      par HD Video Stream
          Astronaut->>Spacecraft: Helmet Cam Feed
      and Data Transfer
          Astronaut->>Spacecraft: Scientific Data Upload
      end
  

3.2. Medical: Intelligent Hospital Bed and Patient Monitoring

• Enabling Description: A patient wears a biosensor wristband that communicates vital signs (ECG, SpO2, temp) to a central nursing station via a hospital-wide Medical Body Area Network (MBAN) or BLE mesh. When a specific piece of diagnostic equipment (e.g., a portable ultrasound machine or a smart IV pump) is brought within a pre-set range of the patient's bed (e.g., 1 meter, determined by the signal strength of the wristband's BLE beacon), the diagnostic machine establishes a direct, high-bandwidth Wi-Fi Direct connection. This allows the machine to pull the patient's full electronic health record (EHR) from the hospital network, stream high-resolution diagnostic images in real-time to a doctor's tablet, and log all procedure data directly back to the patient's EHR, ensuring the right data is associated with the right patient at the point of care.

• Diagram:

  graph TD
      subgraph "Continuous Monitoring"
          A[Patient Biosensor] -- BLE Mesh --> B[Nursing Station]
      end
      subgraph "Bedside Procedure"
          C[Ultrasound Cart] --> D{Detects Patient BLE Beacon};
          D -- Strong Signal --> E[Establish Wi-Fi Direct Link with Bedside Hub];
          E --> F[Pull EHR Data];
          E --> G[Stream Ultrasound Video];
          G --> H[Log Procedure to EHR];
      end
      A --> D
  

3.3. Retail: Smart Shopping Cart and Personalized Offers

• Enabling Description: A smart shopping cart is equipped with a BLE beacon for in-store location tracking. As a customer pushes the cart, their loyalty app on their smartphone maintains a low-power connection to the cart. When the cart's location system (e.g., UWB or computer vision) determines it is dwelling in front of a specific high-value "endcap" display for more than a set time (e.g., 10 seconds), the display's integrated Wi-Fi access point establishes a direct connection with the customer's phone. This high-bandwidth link pushes a rich media advertisement, an interactive product demo, or a limited-time digital coupon for the products on that specific display directly to the customer's app, bypassing the congested general store Wi-Fi.

• Diagram:

  sequenceDiagram
      participant Phone as Customer's Phone
      participant Cart as Smart Cart (BLE)
      participant Display as Endcap Display (Wi-Fi)
  
      Phone->>Cart: Initial BLE Pairing (Loyalty App)
      loop Shopping
          Cart-->>Phone: Location & Status Updates
      end
      Note over Cart,Display: Cart dwells at Endcap
      Display->>Phone: Detect strong BLE signal from Cart
      Display->>Phone: Initiate Wi-Fi Direct Handshake
      Phone-->>Display: Connect to Display's Wi-Fi
      Display->>Phone: Push Rich Media Ad/Coupon
  

---

4. Integration with Emerging Technologies

4.1. AI-Based Predictive Resource Allocation

• Enabling Description: The vehicle's onboard AI learns the driver's daily routines (commute times, common destinations) by analyzing historical GPS, calendar, and vehicle usage data. The system predicts the driver's approach to the vehicle. 1-2 minutes before the predicted arrival, it wakes the vehicle's Body Control Module (BCM) and the primary low-power radio (e.g., BLE). The AI also analyzes real-time environmental data (e.g., cellular network congestion, ambient RF noise from a network analyzer). Based on this analysis, it pre-selects the optimal channel and band for the secondary high-bandwidth (Wi-Fi) connection before the user is even in range. This minimizes handshake time and avoids interference, creating a near-instantaneous connection upon arrival.

• Diagram:

  flowchart TD
      A[Data Sources: GPS, Calendar, Time] --> B(Predictive AI Model);
      B --> C{Predicts User Arrival?};
      C -- Yes --> D[Wake BCM & BLE Radio];
      D --> E[Scan RF Environment];
      E --> F[AI Selects Optimal Wi-Fi Channel];
      F --> G[Wait for BLE Proximity Trigger];
      G --> H[Establish Wi-Fi Link on Pre-Selected Channel];
      C -- No --> B;
  

4.2. IoT-Enhanced Geofencing and Authentication

• Enabling Description: The system integrates with a user's home or office IoT network. The initial trigger is not the detection of the user's device, but a message received from the user's smart home hub (e.g., via MQTT protocol over the vehicle's LTE connection) that the user's smartphone has disconnected from the home Wi-Fi. The vehicle then enters a "standby" mode. A secondary trigger comes from a smart garage door opener, confirming the door is open. Only after receiving these two IoT signals does the vehicle activate its BLE scanner to establish the first link. The final transition to the high-bandwidth Wi-Fi is triggered by a combination of BLE signal strength and the in-cabin weight sensor detecting the driver's weight in the seat, providing a multi-factor "proof of presence" before enabling access to sensitive data or vehicle controls.

• Diagram:

  graph LR
      A[Smart Home Hub] -- "User Left" --> C(Vehicle ECU);
      B[Garage Door] -- "Is Open" --> C;
      C -- Receives Both Signals --> D[Activate BLE Scanner];
      D -- Device Detected --> E[Establish BLE Link];
      F[Seat Weight Sensor] -- "Occupied" --> G[Confirm Presence];
      E -- Proximity Confirmed --> G;
      G -- All Conditions Met --> H[Establish Wi-Fi Link];
  

---

5. The "Inverse" or Failure Mode

5.1. Graceful Degradation Mode

• Enabling Description: The vehicle's connectivity manager constantly monitors the link quality (packet loss, latency, jitter) of the secondary high-bandwidth connection (e.g., Wi-Fi). If the quality drops below a predefined Quality of Service (QoS) threshold for a sustained period (e.g., >50% packet loss for 3 seconds), the system does not disconnect entirely. Instead, it "gracefully degrades." It signals the user's device to fall back to the primary low-power link (e.g., Bluetooth) and simultaneously instructs the vehicle's infotainment system to switch to a "low-bandwidth UI." This UI disables data-intensive widgets (e.g., satellite maps, video streaming) and presents a simplified interface with only functions that can operate reliably over Bluetooth, such as basic call controls and standard-quality audio streaming. The system continues to probe for a stable Wi-Fi connection in the background and will automatically re-establish the full-featured mode when possible.

• Diagram:

  stateDiagram-v2
      state "High-Bandwidth Mode (Wi-Fi)" as High
      state "Low-Bandwidth Mode (BT)" as Low
      [*] --> Low: Initial Connection
      Low --> High: Proximity Confirmed & Wi-Fi Stable
      High --> Low: Wi-Fi QoS Degrades
      Low --> High: Wi-Fi QoS Restored
      High --> [*]: User Disconnects
      Low --> [*]: User Disconnects
  

5.2. Anti-Relay Attack "Faraday" Mode

• Enabling Description: To counter sophisticated relay attacks where the signal from a keyfob or phone is amplified to trick the vehicle into unlocking, this embodiment uses the dual-protocol system for security. The initial BLE link is established as normal. However, to authorize a high-security action like starting the engine, the system requires the establishment of the secondary link. This secondary link is an extremely low-power, short-range (sub-10cm) protocol, such as NFC or Magnetic Secure Transmission (MST). The user must physically tap their device to a designated spot on the dashboard or center console. The vehicle's processor will only enable the ignition/drivetrain if both the BLE link is active (confirming the authorized device is generally nearby) and the NFC/MST link is successfully established (confirming the device is physically inside the vehicle and not part of a relay attack).

• Diagram:

  sequenceDiagram
      participant UserDevice as User Device (BLE + NFC)
      participant Vehicle as Vehicle (BLE + NFC)
      UserDevice->>Vehicle: BLE Advertisement
      Vehicle-->>UserDevice: BLE Connection Established
      UserDevice-->>Vehicle: Request Engine Start
      Vehicle-->>UserDevice: Prompt for NFC Tap
      UserDevice->>Vehicle: Physical Tap (NFC Handshake)
      alt NFC Success
          Vehicle->>Vehicle: Authorize Ignition
      else NFC Fail/Timeout
          Vehicle->>Vehicle: Deny Ignition
      end
  

---

6. Combination Prior Art Scenarios

6.1. Combination with AUTOSAR (Automotive Open System Architecture)

• Description: The disclosed multimode discovery process is implemented as a set of standardized software components (SW-Cs) within an AUTOSAR-compliant architecture. A "Wireless Interface Manager" (WIM) SW-C runs on the vehicle's central computing platform. It communicates with lower-level Basic Software (BSW) modules, including a Bluetooth Stack and a TCP/IP stack for Wi-Fi. The proximity detection logic (signal strength analysis) is encapsulated within the WIM. Upon reaching the proximity threshold, the WIM sends a trigger signal via the AUTOSAR Runtime Environment (RTE) to the "Communication Manager" (ComM) BSW module, instructing it to activate the Wi-Fi network interface and establish the secondary connection. This modular, standards-based approach allows the feature to be integrated into any AUTOSAR-compliant vehicle ECU from any manufacturer, treating the dual-mode switching as a standardized service.

• Diagram:

  graph TD
      subgraph Application Layer
          A[Infotainment App SW-C]
      end
      subgraph AUTOSAR RTE
          RTE
      end
      subgraph BSW - Services Layer
          B[Wireless Interface Manager SW-C]
          C[Communication Manager (ComM)]
      end
      subgraph BSW - ECU Abstraction Layer
          D[Bluetooth Driver]
          E[Wi-Fi Driver]
      end
      subgraph Hardware
          F[Bluetooth Radio]
          G[Wi-Fi Radio]
      end
      A -- Request Data --> RTE
      RTE -- Trigger --> B
      B -- Monitor Signal --> RTE
      RTE -- Read Signal Strength --> D
      D -- RF Data --> F
      B -- "Proximity OK" --> RTE
      RTE -- "Activate WiFi" --> C
      C -- "Start Interface" --> RTE
      RTE -- "Enable Driver" --> E
      E -- Control --> G
  

6.2. Combination with W3C WebAuthn Standard

• Description: The establishment of the second, high-bandwidth connection is secured using the FIDO/WebAuthn standard for phishing-resistant authentication. After proximity is determined via the first link (e.g., Bluetooth RSSI), the vehicle's infotainment system (acting as a "relying party") initiates a WebAuthn authentication ceremony over the nascent Wi-Fi link. The user's smartphone (acting as a "FIDO authenticator") prompts the user for a biometric verification (e.g., fingerprint or face scan). Upon successful biometric authentication on the phone, the phone signs a cryptographic challenge sent by the vehicle and returns it. This securely authenticates the user to the vehicle's systems, enabling access to personalized profiles, saved credentials for in-car payments, and other sensitive data, all without the user needing to enter a password.

• Diagram:

  sequenceDiagram
      participant Phone as User Phone (Authenticator)
      participant Vehicle as Vehicle (Relying Party)
      Note over Phone, Vehicle: Proximity established via BLE; Wi-Fi link starting
      Vehicle->>Phone: Initiate WebAuthn Assertion Request
      Phone->>Phone: Prompt user for Biometric (Fingerprint/FaceID)
      alt User Authenticates
          Phone->>Phone: Use Private Key to Sign Challenge
          Phone->>Vehicle: Return Signed Assertion
          Vehicle->>Vehicle: Verify Signature with Stored Public Key
          Vehicle->>Phone: Grant Access to Secure Services
      else User Fails/Cancels
          Phone->>Vehicle: Authentication Failed
          Vehicle->>Vehicle: Deny Access
      end
  

6.3. Combination with MQTT for Fleet Management

• Description: For a fleet of commercial vehicles (e.g., delivery vans), the state of the vehicle's multi-modal connectivity is reported to a central fleet management server using the lightweight MQTT (Message Queuing Telemetry Transport) protocol. The vehicle's telematic control unit (TCU) acts as an MQTT client. It publishes messages to specific topics on a central broker, such as fleet/vehicle_123/status/ble with a payload of {"device_id": "phone_xyz", "rssi": -55} or fleet/vehicle_123/status/wifi with a payload of {"status": "connected", "ip": "192.168.1.10"}. A central server subscribed to these topics can monitor driver presence, verify that data offloads (e.g., delivery manifests, camera footage) are occurring correctly over the high-bandwidth link, and remotely troubleshoot connectivity issues by observing the state transitions without needing a heavy polling-based system.

• Diagram:

  flowchart LR
      subgraph Vehicle
          A[BLE Radio] -- RSSI --> B(TCU/MQTT Client)
          C[Wi-Fi Radio] -- Status --> B
      end
      subgraph Internet
          D[MQTT Broker]
      end
      subgraph Cloud Server
          E[Fleet Management App]
      end
  
      B -- Publish "fleet/vehicle_123/status/ble" --> D
      B -- Publish "fleet/vehicle_123/status/wifi" --> D
      E -- Subscribe to "fleet/vehicle_123/#" --> D
      D -- Pushes Messages --> E