Telematics Service Provisioning for Context-Based Data Usage Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telematics devices in vehicles incur unnecessary data plan expenses and overages due to unmanaged data usage throughout the manufacturing and supply chain, lacking efficient management and provisioning methods.
Innovation Solution
A system and method that utilize a cloud-based telematics server to manage telematics devices by modifying their behavior based on context, such as location and manufacturing stage, to optimize data transmission and provisioning, avoiding excessive costs through intelligent plan selection and control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If telematics devices are activated throughout the supply chain process, then data collection and tracking capabilities are improved, but data plan expenses and overages increase
Solution Approach 1:
The patent implements dynamic provisioning of telematics services based on the device's location and status in the supply chain. The system transitions between different service states (e.g., full service activation during manufacturing, reduced service during storage, complete deactivation during delivery) to optimize data usage. This dynamic approach allows the system to maintain reliable data collection when needed while reducing costs during periods when the device is stationary or being transported.
Solution Approach 2:
The system changes key parameters such as data transmission frequency, data plan limits, and service availability based on contextual factors. During manufacturing, the system may enable frequent data transmissions for quality control; during storage, it reduces transmission frequency to minimize data plan consumption; during delivery, it suspends services entirely. This parameter change strategy resolves the contradiction by adapting service levels to actual operational needs.
2Adaptability or versatility
If telematics devices are provisioned with full service plans, then device functionality and data transmission capabilities are improved, but unnecessary data usage and overages occur during storage and transit
Solution Approach 1:
The patent segments the telematics service into different functional components that can be independently activated or deactivated based on context. Rather than providing a monolithic full-service plan, the system divides data collection, tracking, communication, and other functions into discrete modules. This allows the system to maintain essential functionality during manufacturing while suspending unnecessary data-intensive features during storage and transit, thereby reducing overall data usage.
Solution Approach 2:
The system applies partial action by providing only the necessary level of telematics service for each phase of the supply chain. During manufacturing, full service is provided to ensure device functionality and quality control. During storage, reduced service is applied to minimize data usage. This partial action approach prevents excessive data consumption while maintaining adequate functionality for each operational context.
3Ease of operation
If telematics services are managed manually at dealer level, then device control is simplified, but inefficient management and lack of centralized coordination occur throughout the supply chain
Solution Approach 1:
The patent merges the management of telematics devices across the entire supply chain into a single centralized system. Instead of managing devices independently at each stage (manufacturing, storage, delivery, dealer level), the system combines all management functions into one coordinated platform. This unified approach improves productivity by enabling centralized provisioning, real-time monitoring, and coordinated service delivery across all supply chain participants, while maintaining ease of operation through automated decision-making.
Data Source
AI summary
A system and method which enables a telematics server and its software to modify telematics device behavior based on the provisioned telecommunications plan depending on the context of the telematics device. The context may be the location, stage of manufacturing process for the device/equipment that the telematics device is fitted to (e.g. a vehicle), the speed, status of various sensors and others. This information is used to both modify device behavior in terms of how often and what is communicated to the telematics server but is also useful in modifying and provisioning new plans for the telematics device (with appropriate transmission configurations matched to the plan). The foregoing allows the telematics device to avoid operating in a way that exceeds telecom plan thresholds and limits.