Emergency Number Description Support in 5G Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for providing emergency call services in 5G networks do not effectively support the display of textual descriptions for emergency numbers, which can be region-specific and subject to frequent changes, leading to confusion for both local and roaming users.

Innovation Solution

A method where a user equipment (UE) communicates with a network node to receive emergency number descriptions, with the network node determining the appropriate language and encoding based on UE capabilities and preferences, and the UE storing and managing these descriptions to provide user-friendly menu options for emergency services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the network provides emergency number descriptions to the UE, then user awareness and accessibility of emergency services is improved, but data transmission and battery consumption increase

Engineering Contradiction:
Improveuser awareness and accessibility of emergency servicesVSAvoidbattery consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The network node provides emergency number descriptions to the UE in advance during the registration procedure, before the UE needs to make an emergency call. This preliminary provision of information ensures that when emergency services are needed, the descriptions are already available for display, eliminating the need for real-time data transmission and reducing battery consumption during critical moments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The UE stores and manages the emergency number descriptions locally after receiving them from the network. The UE autonomously uses these stored descriptions to provide user-friendly menu options for emergency services without requiring continuous network connection or additional data transmission, thereby reducing energy consumption while maintaining functionality.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If the network provides emergency number descriptions in multiple languages, then adaptability to different user needs is improved, but data transmission volume increases

Engineering Contradiction:
Improvelanguage adaptabilityVSAvoiddata transmission volume
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Instead of providing all possible language descriptions for all emergency numbers, the network provides descriptions in a limited set of languages that are most relevant to the UE's location and usage patterns. This partial provision of language support reduces data transmission volume while still meeting the majority of user needs, and the UE can fall back to default language handling for unsupported languages.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The network determines the appropriate language and encoding for emergency number descriptions based on the UE's local context, such as the visited network's primary language or the UE's preferred language settings. By localizing the language selection to match the user's immediate environment rather than providing all languages universally, the data transmission volume is significantly reduced while maintaining high adaptability to local user needs.

Inventive Principle:
Principle #3Local quality

3Reliability

If the network sends emergency number descriptions periodically, then information freshness is improved, but data transmission frequency and energy consumption increase

Engineering Contradiction:
Improveinformation freshnessVSAvoidtime for data transmission
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The network provides emergency number descriptions to the UE during the initial registration procedure or when the UE enters a new network area, rather than using continuous periodic updates. This preliminary action ensures that the information is fresh and up-to-date at the moment of need, while avoiding the time and energy costs of continuous periodic transmission. The UE caches this information locally for use.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The network monitors UE mobility and network changes, triggering updates of emergency number descriptions only when necessary (e.g., when the UE registers on a new network, when the network configuration changes, or when the UE indicates a need for updated information). This feedback-driven approach ensures information freshness while minimizing unnecessary data transmission and energy consumption compared to fixed periodic schedules.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4236503B1Support of emergency number descriptions
Publication Date: 2025.04.30 MALIKIE INNOVATIONS LTD
  • EP4236503B1 patent drawingFigure 1
  • EP4236503B1 patent drawingFigure 2
  • EP4236503B1 patent drawingFigure 3~5

AI summary

A method is disclosed comprising: receiving, by a network node from a user equipment (UE), a registration message. The registration message comprising: a first indicator configured to indicate a status of emergency information previously received at the UE, the first indicator including a result of a hashing function of the previously received emergency information. The method comprises determining, by the network node, whether a second emergency information needs to be included in a registration accept message; and in response to determining that the second emergency information needs to be included in a registration accept message, transmitting, from the network node to the UE, a registration accept message including the second emergency information.