Secure Element Emergency Profile Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current emergency call systems require external command from a subscription manager-secure routing entity to switch to an emergency profile, which is not compatible with the requirements of emergency services, especially in situations where human intervention is not possible, such as accidents outside the network coverage associated with the active profile.
Innovation Solution
A system and method that automatically activate an emergency profile, referred to as the 'eCall Profile', within a communications device equipped with a secure element, allowing emergency calls to be made without human intervention, even if the device is outside the network coverage associated with the active profile, by using a device like an airbag mechanism or on-board computer to generate an event and switch to the emergency profile.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system waits for an external command from SM-SR to switch to emergency profile, then network security and control are maintained, but emergency call response time is delayed and automatic emergency calling is prevented
Solution Approach 1:
The system pre-configures multiple operational profiles including an emergency profile within the secure element before an emergency event occurs. When an emergency event is detected by the triggering device, the system can immediately activate the pre-configured emergency profile without waiting for external commands, thus reducing response time while maintaining security through pre-established authentication credentials.
Solution Approach 2:
The secure element is designed to autonomously switch between operational profiles based on events received from the triggering device. The system performs self-service by automatically detecting emergency events and activating the appropriate profile without requiring external intervention from SM-SR, enabling immediate emergency calling while the secure element manages its own profile activation internally.
2Ease of operation
If the system uses a single active operational profile, then network authentication is simplified, but the system cannot automatically switch to emergency profile when needed
Solution Approach 1:
The system segments the operational profiles into distinct, isolated units within the secure element, with each profile containing its own authentication credentials and configuration. The triggering device and secure element work together to select and activate the appropriate segmented profile based on the event type, maintaining simple authentication for each individual profile while enabling versatile profile switching capability.
Solution Approach 2:
The system transitions from a static single-profile configuration to a dynamic multi-profile architecture where the active profile can change based on events. The secure element maintains multiple operational profiles in a dormant state and dynamically activates the emergency profile when triggered, providing both operational simplicity and adaptive switching capability.
3Reliability
If manual intervention is required to activate emergency profile, then security control is maintained, but automatic emergency calling in accidents is prevented
Solution Approach 1:
The triggering device acts as an intermediary between the emergency event and the secure element. When an emergency event occurs (such as an accident detected by sensors), the triggering device automatically sends a trigger signal to the secure element, which then activates the emergency profile. This intermediary mechanism enables automatic activation while maintaining security through the secure element's controlled profile management.
Solution Approach 2:
The system implements self-service automation where the triggering device automatically detects emergency events and triggers profile activation without human intervention. The secure element autonomously receives the trigger signal and activates the appropriate operational profile based on pre-configured event types, enabling fully automatic emergency calling while maintaining security through cryptographic authentication in the secure element.
Data Source
AI summary
An example of an emergency call system includes a device for triggering an emergency call and a communications device having a secure element. In various implementations, the secure element includes at least two profiles, one of which is an emergency profile; and a receiver that receives, over a local communications channel, an event issued by the device for triggering an emergency call. The communications device may also include means for activating the emergency profile, which enables emergency calls to be made in a communications network if the emergency profile is not already active. The communications device may also include means for calling an emergency number in the communications network in order to make the emergency call.