Telematics API Segmentation for eCall Stability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telematics units face challenges in maintaining and verifying complex Application Programming Interfaces (APIs), which are often updated frequently, leading to increased costs and risks of failed updates, especially for legally required emergency call functions, necessitating costly and time-consuming certification processes.
Innovation Solution
The telematics unit separates the API into two distinct interfaces: an eCall-interface for legal emergency call functions and an app-interface for other applications, allowing independent updates and certification, with the eCall-interface prioritized for stability and minimal changes, and the app-interface for frequent updates and additional functionalities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single complex API is used to provide all telematics functions including eCall and applications, then the system is streamlined for versioning and maintenance, but any updates require recertification of the entire API solution even when only non-critical parts are changed
Solution Approach 1:
The patent segments the monolithic API into two distinct interfaces: a first interface for certified eCall functions and a second interface for applications. This segmentation allows the eCall interface to maintain certification stability while the application interface can be updated flexibly without triggering recertification requirements.
Solution Approach 2:
The patent extracts the eCall functionality from the general application API into a separate dedicated interface. This extraction isolates the certified components from the update-prone application layer, allowing independent maintenance and update cycles.
2Adaptability or versatility
If the API is highly integrated to provide feature-rich functionality, then versatility is improved, but maintenance and verification become challenging due to high frequency of changes
Solution Approach 1:
By dividing the API into separate eCall and application interfaces, the patent reduces the complexity of each individual interface. The eCall interface becomes simpler and more stable, while application functionality is isolated to the second interface, making maintenance and verification easier for each segment.
3Ease of operation
If priority control features are added to the API to manage application access, then application management capability is improved, but verification of priority control becomes difficult and time-consuming
Solution Approach 1:
The patent extracts priority control mechanisms from the general API to the hardware abstraction layer, where they can operate independently of application-specific logic. This separation simplifies verification by isolating the priority control functionality from the complex application layer.
4Adaptability or versatility
If frequent updates are performed to improve API functionality and adapt to technology progress, then adaptability is improved, but the risk of update failures and development time increases
Solution Approach 1:
The patent segments the update process into two independent streams: stable eCall interface updates and flexible application interface updates. This allows frequent application updates without affecting the stability of the certified eCall functions, thereby increasing overall update success rates.
Data Source
Figure 1
AI summary
The invention relates to Telematics unit (TU), wherein the telematics unit (TU) comprises a processor (P) and a storage device (S) and comprises as further hardware components a positioning hardware (400) and an audio hardware (500) and a modem hardware (600), wherein the telematics unit (TU) comprises at least two telematic applications (TAP), wherein the telematic applications (TAP) are connected for an exchange of commands and of information by an application programming interface (API) and hardware abstraction Layer (300)to the further hardware components (HC) .