Telematics Unit Load Balancing via Dynamic Processor Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As vehicle data transfer requirements increase, managing bandwidth effectively across multiple telematics control units (TCUs) with different carriers and billing cycles poses challenges in balancing data transfer, power usage, and transfer timing, leading to inefficiencies in cost, speed, and power consumption.
Innovation Solution
A processor in the vehicle dynamically selects the appropriate TCU based on variables such as power usage constraints, data usage over a billing cycle, and transfer timing requirements, using a selection strategy that prioritizes either speed, power preservation, or cost optimization depending on the scenario, to fulfill data transfer requests efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If multiple TCUs with different carriers are used to increase bandwidth, then data transfer speed is improved, but power consumption and cost management become more complex
Solution Approach 1:
The system dynamically selects which TCU to activate based on real-time conditions including power availability, data priority levels, and carrier status. The processor adjusts TCU selection dynamically rather than using a fixed configuration, allowing the system to optimize between speed and complexity management based on current vehicle state and data transfer requirements.
Solution Approach 2:
The system changes operational parameters by switching between different TCUs based on power consumption thresholds, data priority, and carrier data remaining. The processor modifies selection criteria based on varying conditions such as power availability, billing cycle status, and transfer urgency, thereby managing complexity through parameter-based decision logic.
2Speed
If data transfer priority is increased to meet timing requirements, then transfer speed is improved, but power consumption increases
Solution Approach 1:
The system applies partial action by selectively activating only the necessary TCU(s) based on data priority levels. For high-priority data, the system may activate multiple TCUs to maximize speed. For lower-priority data, it may activate a single TCU or enter power-saving mode, thereby reducing overall power consumption while meeting timing requirements only when necessary.
Solution Approach 2:
The processor dynamically adjusts power consumption based on data priority and timing requirements. The system transitions between different power states and TCU configurations in real-time, activating high-performance modes only when timing constraints require them, and switching to low-power modes when timing flexibility allows.
3Loss of energy
If carrier data usage is monitored to optimize costs, then cost efficiency is improved, but system complexity increases
Solution Approach 1:
The system implements feedback mechanisms where the processor continuously monitors carrier data usage, billing cycle status, and TCU performance. This feedback information is used to adjust future TCU selections and optimize cost efficiency. The feedback loop simplifies complexity management by using automated monitoring and adaptive decision-making rather than manual intervention.
Solution Approach 2:
The system performs self-service by automatically managing TCU selection based on carrier data remaining, billing cycle status, and historical usage patterns. The processor independently makes optimization decisions without external intervention, reducing the complexity burden on users while maintaining cost efficiency through automated carrier data monitoring and TCU management.
Data Source
AI summary
A vehicle includes a plurality of telematics control units (TCUs) and a processor. The vehicle may use the processor to consider vehicle variables, responsive to a data transfer request, including power usage constraints, data usage over a billing cycle for each carrier associated with a given TCU, and transfer timing requirements for a given data transfer request. Based on the considered variables, the vehicle may select at least one controlling variable and select at least one of the TCUs based on at least a value of the controlling variable, then use the selected TCU to fulfil the data transfer request.