Mobile App DRx Sync with Vehicle Hardware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle hardware in a mobile vehicle enters a powered-down state to conserve battery when the ignition is off, leading to potential battery drain and communication disruptions, as network access devices continue to search for signals, making it unclear when the vehicle is available for requests through mobile applications.

Innovation Solution

A system and method where the vehicle's telecommunications unit sends a synchronization message to the mobile device when the ignition is off, allowing the mobile application to align with the vehicle's discontinuous receive (DRx) schedule, which includes standby, cyclic, and powered-down modes, enabling the application to determine vehicle availability and process user requests accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If the vehicle hardware is placed into standby state or DRx cycle to minimize power drain, then energy consumption is reduced, but communication availability deteriorates as the vehicle may be unable to communicate during certain periods

Engineering Contradiction:
Improvepower drainVSAvoidcommunication availability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The system performs preliminary actions by having the mobile application determine the DRx schedule and vehicle availability windows in advance. The application synchronizes with the vehicle's DRx cycle timing, allowing it to predict when the vehicle will be available for communication and prepare requests accordingly, thus maintaining reliability while the vehicle remains in low-power state.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The vehicle operates in periodic DRx cycles with alternating active and sleep periods. The mobile application is synchronized to these periodic cycles, enabling it to send requests only during windows when the vehicle is awake and available, thus maintaining communication reliability while the vehicle minimizes power consumption during sleep periods.

Inventive Principle:
Principle #19Periodic action

2Reliability

If the network access device continues to search for signal in standby state, then communication reliability is maintained, but battery drain increases

Engineering Contradiction:
Improvesignal availabilityVSAvoidbattery drain
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The mobile application performs preliminary synchronization to obtain the DRx schedule and determine vehicle availability windows before attempting communication. This allows the application to know in advance when the vehicle will be available, eliminating the need for continuous signal searching and reducing energy consumption while maintaining the ability to establish reliable communication at the appropriate times.

Inventive Principle:
Principle #10Preliminary action

3Loss of energy

If the vehicle enters powered down mode after certain time in DRx cycle, then energy conservation is improved, but communication capability is lost

Engineering Contradiction:
Improvebattery conservationVSAvoidcommunication capability
Core Design Contradiction:
Loss of energyVSLoss of information

Solution Approach 1:

The mobile application synchronizes with the vehicle's DRx schedule in advance and determines the timing of powered-down mode transitions. This allows the application to send user requests and receive responses during the limited windows when the vehicle is available, before the vehicle enters powered-down mode, thus conserving battery while maintaining communication capability for essential operations.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If the mobile application sends requests immediately, then user responsiveness is improved, but request failure increases when vehicle is unavailable

Engineering Contradiction:
Improverequest processing speedVSAvoidrequest success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The mobile application performs preliminary synchronization to obtain the vehicle's DRx schedule and availability windows. Based on this advance knowledge, the application intelligently determines when to send requests - only during windows when the vehicle is known to be available - thus maintaining high request processing efficiency while avoiding failed requests that would occur if sent during unavailable periods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the mobile application receives information about vehicle availability status and DRx schedule from the vehicle. This feedback allows the application to adjust its request timing dynamically, sending requests only when the vehicle is available, thus maintaining both responsiveness and high success rate.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9237534B2Mobile application DRx synchronization with embedded vehicle hardware
Publication Date: 2016.01.12 GENERAL MOTORS LLC
  • US9237534B2 patent drawing
  • US9237534B2 patent drawing
  • US9237534B2 patent drawing

AI summary

The described method and system provide for synchronizing a mobile application on a mobile device with a DRx (discontinuous receive) schedule of a vehicle. When the vehicle ignition is turned off, a telecommunications unit on the vehicle sends a synchronization message to the mobile device, which allows the mobile application to synchronize with the DRx schedule of the vehicle. The DRx schedule includes a standby mode, a cyclic mode, and a powered down mode for the vehicle, and user requests inputted into the mobile application will be processed according to the mobile application's determination of vehicle availability during those modes. The mobile application is thus able to inform the user of the vehicle status at any point during the vehicle's DRx schedule without requiring any further information from the vehicle after the synchronization message.