Telematics Provisioning via Multicast Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional telematics provisioning methods waste resources due to inefficient communication and resource allocation, particularly in multicast communication scenarios where multiple telematics units with varying software versions need to be provisioned, leading to delays and increased communication costs.
Innovation Solution
Implementing a multicast telematics provisioning method that uses a reservation schedule, where a telematics multimedia system center transmits SMS with provisioning information and schedules, allowing telematics units to request provisioning only when ready, thereby optimizing resource allocation and reducing waste by allocating resources only upon request and improving communication efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional provisioning is executed by transmitting SMS to wake up telematics units one by one, then provisioning can be performed for each vehicle, but resource waste occurs due to holding communication channels and allocating resources for units that may not respond
Solution Approach 1:
The patent applies preliminary action by having the telematics unit pre-register its software version information with the TMS center before provisioning execution. This allows the TMS center to have advance knowledge of which units are provisionable, eliminating the need to waste resources on units that cannot be provisioned. The pre-registration creates a prepared state where provisioning can be executed efficiently without trial-and-error SMS transmissions.
Solution Approach 2:
The patent implements feedback by establishing a registration mechanism where telematics units provide information about their software versions to the TMS center. This feedback loop allows the TMS center to make informed decisions about provisioning allocation, only attempting to provision units that have registered and indicated compatibility. This eliminates the blind resource allocation inherent in conventional SMS-based wake-up approaches.
2Productivity
If provisioning is executed by dividing TMUs into groups and transmitting wakeup SMS, then multiple vehicles can be provisioned, but communication cost and time increase due to repeated transmissions and waiting
Solution Approach 1:
The patent applies preliminary action by having telematics units pre-register their presence and software version information with the TMS center before provisioning execution. This creates a ready state where the TMS center can immediately begin provisioning registered units without needing to transmit wake-up SMS messages. The pre-registration eliminates the time-consuming wake-up process while maintaining the ability to provision multiple units efficiently.
Solution Approach 2:
The patent extracts the wake-up SMS transmission step from the provisioning process. By separating the registration function from the provisioning execution, the system eliminates the need for repeated SMS transmissions. The provisioning process directly operates on already-awake, registered units, removing the time-consuming communication overhead of conventional approaches.
3Reliability
If the TMS center allocates resources for provisioning from SMS transmission to receiving ACK signal, then provisioning can be completed, but resources are held for about 2 minutes causing inefficiency
Solution Approach 1:
The patent applies preliminary action by having telematics units pre-register their software version information and provisioning requirements with the TMS center before actual provisioning execution. This allows the TMS center to prepare provisioning data in advance and allocate resources only when needed, rather than holding resources for extended periods while waiting for ACK signals. The pre-registration creates a ready state that eliminates resource holding delays.
Solution Approach 2:
The patent implements dynamics by making resource allocation dynamic and on-demand rather than static and predetermined. Resources are allocated to the TMS center only when provisioning is actually executed for registered units, rather than being held in reserve for potential provisioning attempts. This dynamic allocation matches resource usage to actual need, eliminating the 2-minute resource holding period.
4Productivity
If conventional provisioning is executed without considering software versions, then provisioning can be attempted for all TMUs, but failure rate increases due to incompatibility
Solution Approach 1:
The patent applies local quality by making provisioning execution specific to each telematics unit's software version characteristics. Rather than attempting uniform provisioning for all units, the system tailors provisioning to the local conditions of each registered unit. The TMS center uses the pre-registered software version information to determine compatibility and execute provisioning only for compatible units, ensuring high success rates while maintaining broad coverage.
Solution Approach 2:
The patent implements parameter changes by using software version information as a key parameter for provisioning decisions. The system changes the provisioning parameter set based on the registered software version of each telematics unit, selecting appropriate provisioning data and methods that match the unit's capabilities. This parameter-based approach ensures compatibility while maintaining wide provisioning coverage across different vehicle types and software versions.
Data Source
AI summary
A telematics provisioning method is executed by a telematics multimedia system (TMS) center and a telematics unit (TMU), and the TMU is provided in a vehicle to communicate with the TMS center. The method includes executing multicast provisioning; operating a provisioning scheduler to form a provisioning schedule; transmitting a short message service (SMS) from the TMS center to the TMU after the provisioning scheduler operates; identifying whether the TMU executes provisioning based on the provisioning schedule of the SMS; if the TMU does not execute provisioning based on the provisioning schedule of the SMS, reforming, by the TMS center, the provisioning schedule; requesting, by the TMU that receives the SMS from the TMS center, provisioning to the TMS center according to reservation information of the SMS; and executing predetermined provisioning when the TMS center receives the provisioning requested from the TMU.