Emergency Network Slice for Roaming UE Call Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G communication networks face challenges in efficiently processing emergency calls for roaming user equipment (UE) in visited communication networks, as they require complex procedures to fetch subscriber-specific data and often experience congestion, leading to delayed emergency response times.
Innovation Solution
The implementation of an emergency network slice within the communication network, which includes a dedicated access network entity and emergency RAN entity, allows for prioritization and local routing of emergency calls, using an emergency identifier (E_ID) to detect and forward emergency messages directly to a public safety answering point (PSAP) via a specific communication interface, optimizing routing and resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If emergency calls are routed through the local network for roaming users, then emergency response time is reduced, but network congestion and overload increase
Solution Approach 1:
The network is segmented into a general network slice for regular traffic and a dedicated emergency network slice for emergency calls. This segmentation allows emergency traffic to be isolated and prioritized, preventing congestion in the general network while ensuring fast emergency response. The emergency slice includes dedicated access network entities and resources that are exclusively allocated for emergency communications.
Solution Approach 2:
An emergency network slice acts as an intermediary layer between the general network and PSAPs. This intermediary dedicated infrastructure handles emergency call routing separately, using specific interfaces (E1, E2) and entities (AMF, RAN) that are optimized for emergency traffic, thereby preventing overload on the general network while maintaining fast emergency response.
2Speed
If a dedicated emergency network slice is implemented, then emergency call processing speed is improved, but network complexity increases
Solution Approach 1:
The network architecture is segmented into distinct functional slices: a general network slice for regular communications and an emergency network slice for emergency calls. Each slice has its own access network entities (RAN, AMF) and resources. This segmentation enables specialized optimization for emergency traffic while maintaining the existing general network operations, thus improving emergency processing speed without fundamentally redesigning the entire network.
Solution Approach 2:
The emergency network slice utilizes the same core network infrastructure and protocols as the general network, maintaining compatibility and reusing existing components where possible. The emergency slice adds specialized functions (dedicated interfaces E1/E2, emergency-specific AMF and RAN entities) while building upon the universal 5G core network architecture, thereby limiting the increase in overall complexity.
3Reliability
If subscriber-specific data fetching procedures are required for roaming emergency calls, then call accuracy is improved, but processing time increases
Solution Approach 1:
The emergency network slice is pre-configured with emergency routing information and PSAP mappings before emergency calls occur. The dedicated emergency AMF and RAN entities have pre-established pathways to PSAPs, eliminating the need for real-time subscriber data fetching during emergency calls. This preliminary preparation ensures both accurate call routing and minimal processing time.
Solution Approach 2:
The emergency network slice extracts and isolates the critical emergency call handling functions from the general network procedures. By creating a separate emergency-specific pathway with dedicated entities (emergency AMF, emergency RAN) that operate independently from standard roaming procedures, the system eliminates the time-consuming subscriber data fetching steps while maintaining accurate emergency routing through pre-configured PSAP mappings.
Data Source
AI summary
A method for processing an emergency message in a communication network includes: transmitting, by a user equipment (UE), an emergency message to an access network entity of a network slice of the communication network, wherein the emergency message comprises an emergency identifier (E_ID); detecting by the access network entity of the network slice of the communication network, based on the E_ID, that the emergency message is related to an emergency; forwarding the emergency message to an emergency network slice of the communication network based on the emergency detection; and establishing, by the emergency network slice, a communication link between the UE and a public safety answering point (PSAP) for processing the emergency message.