Emergency call method, apparatus, device, medium and product

Abstract

The present disclosure relates to the technical field of communication, and particularly provides an emergency call method, device, equipment, medium and product. In the disclosure, a call request from a user equipment (UE) is received; the type of the call request is identified; when the type of the call request is an emergency call, a target municipal center IP is determined based on a target unified routing table from a unified data management function (UDM); an emergency call signaling is sent to a centralized service exposure point (SEPP), and an emergency session establishment request is sent to a session management function (SMF), the emergency call signaling is used for an inter-operator and / or cross-region emergency call, and the emergency call signaling at least includes the target municipal center IP. By obtaining the target unified routing table, the target municipal center IP accessed by the emergency call can be determined, and the emergency call information is sent to the SEPP for inter-operator collaborative forwarding, so as to realize the inter-operator and cross-region emergency call. Therefore, the efficiency of the emergency call can be improved.

Description

Technical Field

[0001] This disclosure belongs to the field of communication technology, and specifically relates to an emergency call method, device, equipment, medium and product. Background Technology

[0002] 5G (5th Generation Mobile Communication Technology) unified emergency call routing refers to a unified call routing mechanism in a 5G network environment to ensure that users can quickly and accurately access emergency communication services in emergency situations. It enables efficient routing of emergency call requests to the nearest public safety response center regardless of the type of terminal device or network access used by the user, thereby improving the response speed and processing efficiency of emergency events.

[0003] In related technologies, emergency calls are typically based on TAC (Tracking Area Code) area division, obtaining the route to the caller's home location through the user's location information. However, this method cannot access a unified route across TAC areas during emergency calls in extreme disaster scenarios, making it difficult to meet the needs of emergency communication assurance in multi-carrier roaming environments. Therefore, it reduces the efficiency of emergency calls. Summary of the Invention

[0004] This disclosure addresses some of the deficiencies mentioned in the background art by providing an emergency call method, apparatus, device, medium, and product that can improve the efficiency of emergency calls.

[0005] In a first aspect, embodiments of this disclosure provide an emergency call method applied to an Access and Mobility Management Function (AMF), the method comprising: Receive call requests from user equipment (UE); Identify the type of the call request; When the type of the call request is an emergency call, the target city-level center address IP is determined based on the target unified routing table from the unified data management function UDM; An emergency call signaling is sent to the centralized service exposure point SEPP, and an emergency session establishment request is sent to the session management function SMF. The emergency call signaling is used for emergency calls across operators and / or across regions, and the emergency call signaling includes at least the target city-level center IP.

[0006] Optionally, the call request includes at least one of the following first call information: emergency service number, Session Initiation Protocol (SIP) message, and user roaming status.

[0007] Optionally, identifying the type of the call request includes: Extract the first call information from the call request; If the first call information satisfies at least one of the following, then the type of the call request is determined to be an emergency call: The emergency service number belongs to a pre-configured emergency number database; The SIP message is parsed, and it is determined that the SIP message represents an emergency service type or priority as an emergency. When the user's roaming status is that of an inter-network roaming user, the user's roaming status is queried based on the Inter-network Network Resource Function (I-NRF) and the user is determined to be an emergency roaming user.

[0008] Optionally, when the call request type is an emergency call, determining the target city-level center address IP based on the target unified routing table from the unified data management function UDM includes: Send a route query request to the UDM; The system receives the target unified routing table from the UDM. The target unified routing table includes at least the primary address of the target city center and the city code of the target city center. The target unified routing table is used to determine the mapping relationship between the UE and the target city center. When the user's roaming status is that of a cross-network roaming user, the home city code of the UE is obtained based on the cross-network network resource function I-NRF; Based on the UE's home city code and the city code of the target unified routing table, the corresponding primary address is determined, and the primary address is used as the target city-level center IP.

[0009] Optionally, the target unified routing table further includes a backup address for the target city-level center, and the method further includes: Send a disaster recovery detection request to the primary address; If no feedback message is received from the primary address for N consecutive times, it is determined that the primary address has failed, and the target city-level center IP is switched to the backup address, where N is an integer greater than or equal to 1.

[0010] Optionally, the emergency call signaling includes at least one of the following information: core identification information, service configuration information, and routing control information, wherein the core identification information includes at least one of the target city-level center IP addresses.

[0011] In a second aspect, embodiments of this disclosure provide an emergency call method applied to a unified data management function (UDM), the method comprising: Receive a routing query request from the Access and Mobility Management Function (AMF), the routing query request being sent by the AMF when it recognizes that the type of the received call request is an emergency call; Invoke the pre-configured city-level emergency call unified routing table and determine the target unified routing table; The target unified routing table is returned to the AMF; the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

[0012] In a third aspect, embodiments of this disclosure provide an emergency call method applied to a centralized service exposure point (SEPP), the method comprising: Receive emergency call signaling from the Access and Mobility Management Function (AMF), wherein the emergency call signaling includes at least the target city-level center IP; Based on the affiliated operating user of the target city-level center, determine the target forwarding path of the emergency call signaling; Based on the target forwarding path and the target city-level center IP, the emergency call signaling is sent to the target city-level center.

[0013] Optionally, determining the target forwarding path for the emergency call signaling based on the home operator user of the target city-level center includes: When the user attribution is a local user, the target forwarding path is determined to be a direct forwarding from the local SEPP to the target city-level center; When the user to which the operation belongs is another user, the target forwarding path is determined to be forwarded to the target city-level center in sequence through the local SEPP, the provincial SEPP, and the SEPP corresponding to the other user.

[0014] In a fourth aspect, embodiments of this disclosure provide an emergency call device for use with an Access and Mobility Management Function (AMF), the device comprising: The first receiving module is used to receive call requests from user equipment (UE). The identification module is used to identify the type of the call request; The first determining module is used to determine the target city-level center address IP based on the target unified routing table from the unified data management function UDM when the type of the call request is an emergency call. The first sending module is used to send emergency call signaling to the centralized service exposure point SEPP and to send an emergency session establishment request to the session management function SMF. The emergency call signaling is used for emergency calls across operators and / or across regions, and the emergency call signaling includes at least the target city-level center IP.

[0015] In a fifth aspect, embodiments of this disclosure provide an emergency call device applied to a unified data management function (UDM), the device comprising: The second receiving module is used to receive a routing query request from the Access and Mobility Management Function (AMF), which is sent by the AMF when it recognizes that the type of the received call request is an emergency call. The calling module is used to invoke the pre-configured city-level emergency call unified routing table and determine the target unified routing table; The second sending module is used to return the target unified routing table to the AMF; the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

[0016] In a sixth aspect, embodiments of this disclosure provide an emergency call device applied to a centralized service exposure point (SEPP), the device comprising: The third receiving module is used to receive emergency call signaling from the Access and Mobility Management Function (AMF), wherein the emergency call signaling includes at least the target city-level center IP. The second determining module is used to determine the target forwarding path of the emergency call signaling based on the affiliated operating user of the target city-level center. The third sending module is used to send the emergency call signaling to the target city-level center based on the target forwarding path and the target city-level center IP.

[0017] In a seventh aspect, embodiments of this disclosure provide an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor running the computer program to implement the above-described emergency call method.

[0018] In an eighth aspect, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the above-described emergency call method.

[0019] In a ninth aspect, embodiments of this disclosure provide a computer program product including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device executes the above-described emergency call method.

[0020] This disclosure involves receiving a call request from a User Equipment (UE); identifying the type of the call request; when the call request is an emergency call, determining the target municipal-level center address (IP) based on the target unified routing table from the Unified Data Management Function (UDM); sending emergency call signaling to the Central Service Exposure Point (SEPP) and an emergency session establishment request to the Session Management Function (SMF). The emergency call signaling is used for cross-carrier and / or cross-regional emergency calls and includes at least the target municipal-level center IP. By obtaining the target unified routing table, the target municipal-level center IP that the emergency call needs to access can be determined. The emergency call information is then sent to the SEPP for cross-carrier collaborative forwarding to achieve cross-carrier and cross-regional emergency calls. Simultaneously, the AMF initiates an emergency session establishment request to enable communication between the UE and the target municipal-level center. In this way, under extreme disaster scenarios, the target unified routing table can overcome TAC (Traffic Authority Area) restrictions, ensuring smooth communication between users and emergency command, and providing crucial communication support for disaster prevention, mitigation, and relief. Therefore, the efficiency of emergency calls can be improved.

[0021] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0022] Figure 1 This is a flowchart of an emergency call method provided in this disclosure.

[0023] Figure 2 Another flowchart of an emergency call method provided in this disclosure.

[0024] Figure 3 This is yet another flowchart of an emergency call method provided in this disclosure.

[0025] Figure 4 Another flowchart of an emergency call method provided in this disclosure.

[0026] Figure 5 This is a schematic diagram of an emergency call device provided in this disclosure.

[0027] Figure 6 This is another structural schematic diagram of an emergency call device provided in this disclosure.

[0028] Figure 7 This is another structural schematic diagram of an emergency call device provided in this disclosure.

[0029] Figure 8 This is a hardware block diagram of an electronic device provided in this disclosure.

[0030] Figure 9This is a schematic diagram of a computer program product provided in this disclosure. Detailed Implementation

[0031] To enable those skilled in the art to better understand the technical solution of this application, the application scenario of this application will be described first below.

[0032] 5G (5th Generation Mobile Communication Technology) unified emergency call routing refers to a unified call routing mechanism in a 5G network environment to ensure that users can quickly and accurately access emergency communication services in emergency situations. It enables efficient routing of emergency call requests to the nearest public safety response center regardless of the type of terminal device or network access used by the user, thereby improving the response speed and processing efficiency of emergency events.

[0033] Currently, for 5G emergency calls, relevant technical solutions include routing methods based on Tracking Area Code (TAC) area division, dynamic routing technology based on user location information, and, typically, routing based on TAC (Tracking Area Code) area division, obtaining the route to the caller's home location using the user's location information. Alternatively, priority guarantee technology based on network slicing, IMS (IP Multimedia Subsystem) technology, and emergency call positioning technology combined with GPS or BeiDou positioning can achieve unified routing access for emergency calls. However, this method cannot access unified routing across TAC areas during emergency calls in extreme disaster scenarios, making it difficult to meet the needs of emergency communication assurance in multi-operator roaming environments. Therefore, it reduces the efficiency of emergency calls.

[0034] To address the aforementioned technical issues, this disclosure provides an inventive concept: by obtaining a unified target routing table, the target municipal-level center IP address that an emergency call needs to access can be determined. The emergency call information is then sent to the SEPP for cross-carrier collaborative forwarding, enabling cross-carrier and cross-regional emergency calls. Simultaneously, the AMF initiates an emergency session establishment request to facilitate communication between the UE and the target municipal-level center. This approach can resolve issues in existing 5G networks, such as inconsistent routing, difficulties in cross-carrier collaboration, and insufficient resource guarantees, caused by TAC (Traffic Access Control) area restrictions, in extreme disaster scenarios. By overcoming TAC area restrictions through a unified target routing table, unimpeded communication between users and emergency command is achieved, providing crucial communication support for disaster prevention, mitigation, and relief. Therefore, the efficiency of emergency calls can be improved.

[0035] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0036] Figure 1 This is a flowchart illustrating an emergency call method provided in this disclosure. Figure 1 As shown, this method is applied to the Access and Mobility Management Function (AMF) and includes: S101: Receive a call request from the user equipment (UE).

[0037] S102: Identify the type of call request.

[0038] Specifically, call requests from the UE are parsed to obtain information from multiple dimensions. Data processing is performed on a portion of this information to obtain the first call information. This facilitates the rapid and accurate identification of emergency calls and determines the type of call request. Data processing includes, but is not limited to, data cleaning, normalization, and field extraction. Data cleaning removes invalid characters and verifies the legality of number formats; normalization unifies number formats from different operators to a standard format (e.g., removing area code prefixes); field extraction extracts key fields from the SIP messages in the call request. The first call information is then analyzed to identify the type of call request. The type of call request includes at least an emergency call.

[0039] S103: When the call request type is an emergency call, the target city-level center address IP is determined based on the target unified routing table from the Unified Data Management Function (UDM).

[0040] Specifically, when the call type is determined to be an emergency call, the AMF sends a route query request to the UDM, triggering the unified route acquisition process. Afterwards, it receives the target unified routing table from the UDM. From the target unified routing table, the AMF can determine the target city-level center IP address, ensuring a successful emergency session establishment between the UE and the target city-level center IP address during subsequent emergency session establishment. The target unified routing table includes at least the primary and backup addresses of the target city-level center.

[0041] S104: Send an emergency call signaling message to the centralized service exposure point SEPP and an emergency session establishment request to the session management function SMF.

[0042] Specifically, the SEPP, as a cross-carrier collaborative node, undertakes signaling forwarding and protocol adaptation functions. The AMF sends emergency call signaling to the SEPP, which can then forward it to the SEPP corresponding to the target city-level center, thus achieving cross-domain forwarding. The emergency call signaling is used for cross-carrier and / or cross-regional emergency calls and must include at least the target city-level center's IP address. Simultaneously, the AMF sends an emergency session establishment request to the SMF, enabling the SMF to invoke emergency call resources in the User Plane Function (UPF) to successfully establish the emergency session.

[0043] This disclosure involves receiving a call request from a User Equipment (UE); identifying the type of the call request; when the call request is an emergency call, determining the target municipal-level center address (IP) based on the target unified routing table from the Unified Data Management Function (UDM); sending emergency call signaling to the Central Service Exposure Point (SEPP) and an emergency session establishment request to the Session Management Function (SMF). The emergency call signaling is used for cross-carrier and / or cross-regional emergency calls and includes at least the target municipal-level center IP. By obtaining the target unified routing table, the target municipal-level center IP that the emergency call needs to access can be determined. The emergency call information is then sent to the SEPP for cross-carrier collaborative forwarding to achieve cross-carrier and cross-regional emergency calls. Simultaneously, the AMF initiates an emergency session establishment request to enable communication between the UE and the target municipal-level center. In this way, under extreme disaster scenarios, the target unified routing table can overcome TAC (Traffic Authority Area) restrictions, ensuring smooth communication between users and emergency command, and providing crucial communication support for disaster prevention, mitigation, and relief. Therefore, the efficiency of emergency calls can be improved.

[0044] Figure 2 Another flowchart of an emergency call method provided in this disclosure. Figure 2 As shown, this method is applied to the Unified Data Management Function (UDM), including: S201: Receive a routing query request from the Access and Mobility Management Function (AMF).

[0045] The routing query request is sent by the AMF when it recognizes that the type of the received call request is an emergency call.

[0046] S202: Invoke the pre-configured city-level emergency call unified routing table and determine the target unified routing table.

[0047] Specifically, the UDM stores a unified routing table for city-level emergency calls, as shown in Table 1. This unified routing table includes at least one of the following: city code, emergency service type, primary address, backup address, operator identifier, and encryption algorithm. The UE's home city code in the routing query request can be matched against the unified routing table to determine the target unified routing table. It is understood that the content in the table is merely illustrative, and this disclosure does not impose specific limitations on it.

[0048] Table 1 Unified Routing Table for Municipal Emergency Calls

[0049] Furthermore, the city-level unified emergency call routing table can be structured data, and the city-level codes can adopt the ISO3166-2 standard; emergency service types can be in the form of "voice" or "SMS"; the primary address can be an IPv4 / IPv6 address; the backup address can be an IPv4 / IPv6 address; the operator identifier can be "CMCC", "CTCC", or "CRTC"; and the signaling encryption algorithm can be TLS 1.3 or DTLS 1.2. This city-level unified emergency call routing table is maintained uniformly by the provincial government and synchronized with the UDMs of various operators through the provincial SEPP interconnection nodes. The synchronization latency can be ≤5 minutes.

[0050] S203: Return the target unified routing table to AMF.

[0051] Specifically, the target unified routing table is returned to the AMF, and the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

[0052] This disclosure effectively solves the problem of scattered and inconsistent emergency call routing caused by TAC area restrictions in traditional 5G networks by using a unified routing table for city-level emergency calls and a method for identifying call request types. It ensures that users can be accurately routed to the corresponding target city-level center regardless of which TAC area they are in, thereby improving the response efficiency and reliability of emergency calls.

[0053] Figure 3 This is yet another flowchart illustrating an emergency call method provided in this disclosure. Figure 3 As shown, this method is applied to the centralized service exposure point SEPP and includes: S301: Receive emergency call signaling from the Access and Mobility Management Function (AMF).

[0054] Specifically, SEPP, as a key node in cross-carrier collaboration, is responsible for signaling forwarding and protocol adaptation. Emergency call signaling must include at least the target city-level center IP address.

[0055] S302: Determine the target forwarding path for emergency call signaling based on the home operator user of the target city-level center.

[0056] Specifically, the type of user belonging to the target city-level center is determined, thereby identifying the target forwarding path corresponding to different user types.

[0057] S303: Based on the target forwarding path and the target city-level center IP, the emergency call signaling is sent to the target city-level center.

[0058] Specifically, based on the determined target forwarding path and the target city-level center IP, the emergency call signaling of the call request can be sent to the correct target city-level center so that an emergency session can be successfully established.

[0059] In one possible implementation, identifying the type of call request includes: Extract the first call information from the call request; if the first call information satisfies at least one of the following, then determine that the type of the call request is an emergency call: The emergency service number belongs to the pre-configured emergency number database; the SIP message is parsed and the emergency service type or priority represented by the SIP message is determined to be an emergency; when the user's roaming status is an inter-network roaming user, the user's roaming status is queried based on the inter-network network resource function I-NRF and the user is determined to be an emergency roaming user.

[0060] For example, a call request may include at least one of the following first call information: emergency service number, Session Initiation Protocol (SIP) message, and user roaming status.

[0061] Specifically, the AMF performs data identification on the received call requests from the UE to obtain the first call information. This call request identification includes, but is not limited to, number segment identification, SIP message identifier identification, and inter-network roaming identifier identification. Number segment identification matches the call number sent by the UE against a pre-configured emergency number database, which includes emergency service numbers such as "110", "119", "120", and "122", as well as emergency numbers with area codes (such as "010-110"). SIP message identifier identification parses fields in the SIP message, such as Emergency-Service-Type or Priority=emergency, to determine whether the call request is an emergency call. Inter-network roaming identifier identification determines the user's roaming status by querying the user's home operator information via I-NRF. If the user's roaming status is marked as "emergency roaming user", then any calls initiated by that user are treated as emergency calls by default.

[0062] Emergency service numbers are stored as strings, such as "110" and "120", and support regular expression matching; SIP message field identification data format is encapsulated in XML or JSON format, including field names and values; inter-network roaming identification data format: user attribute fields returned by I-NRF.

[0063] The following is an example of the logic for identifying the type of call request: IF (Number range ∈ Emergency Number Database) THEN Determined as an emergency call ELSE IF (SIP message contains "Emergency-Service-Type" OR "Priority=emergency") THEN Determined as an emergency call ELSE IF (I-NRF returns EmergencyRoamingUser = true) THEN Determined as an emergency call ELSE Non-emergency calls This judgment logic ensures the accuracy and comprehensiveness of emergency call identification through multi-condition judgment.

[0064] In one possible implementation, when the call request type is an emergency call, the target city-level center address IP is determined based on the target unified routing table from the Unified Data Management Function (UDM), including: Send a route query request to the UDM; receive the target unified routing table from the UDM; when the user's roaming status is inter-network roaming user, obtain the UE's home city code based on the inter-network network resource function I-NRF; based on the UE's home city code and the city code of the target unified routing table, determine the corresponding primary address, and use the primary address as the target city-level center IP.

[0065] Specifically, the AMF sends a route query request to the UDM. The UDM matches the UE's home city code from the city-level emergency call unified routing table using the route query request, and determines the information with matching city codes as the target unified routing table. The target unified routing table includes at least the primary address and city code of the target city-level center, and is used to determine the mapping relationship between the UE and the target city-level center. Afterwards, the UDM sends the target unified routing table back to the AMF, which determines the user's roaming status and identifies the target city-level center IP from the target unified routing table.

[0066] The following is an example of the judgment logic for route query: AMF sends a routing query request to UDM UDM query city-level emergency call unified routing table IF (UE is a user roaming on a different network) THEN AMF obtains the city code of origin through I-NRF. By combining the inbound carrier's UDM routing table, the target city-level center IP is determined. ELSE Directly return the primary and backup addresses This logic ensures that the target city-level central IP address can be correctly obtained regardless of whether the user is a roaming user on a different network.

[0067] In one possible implementation, the target unified routing table also includes a backup address for the target city-level center. The AMF monitors the primary address of the target city-level center, and if the primary address fails, it switches to the backup address of the target city-level center.

[0068] Example methods include: Send a disaster recovery detection request to the primary address; if no feedback message is received from the primary address for N consecutive times, it is determined that the primary address has failed, and the target city-level center IP is switched to the backup address. N is an integer greater than or equal to 1.

[0069] Specifically, the AMF monitors the status of the city-level center in real time and determines whether the primary address has failed by sending heartbeat detection packets. If no response is received three times consecutively, the primary address is deemed to have failed, and the system automatically switches to the backup address. The switching latency is ≤1 second, and the emergency call connection rate after switching is ≥99%. This effectively solves the problem of emergency call interruption caused by single point of failure in traditional networks, and improves the system's disaster recovery switching capability and stability.

[0070] The following is an example of the judgment logic for disaster recovery detection: AMF sends heartbeat detection packets to the primary address. IF (No response received after 3 consecutive attempts) THEN Determine if the primary address is invalid Automatically switch to backup address Switching latency ≤ 1 second After handover, the call connection rate is ≥99%. This decision logic ensures that emergency calls can be quickly restored even when the primary address fails.

[0071] In one possible implementation, the emergency call signaling includes at least one of the following information: core identification information, service configuration information, and routing control information, wherein the core identification information includes at least one type of information: the target city-level center IP address.

[0072] Specifically, core identification information is used to uniquely identify the initiator, service attribute, and target recipient of an emergency call. It forms the basis for SEPP to determine the forwarding path and includes at least one of the following: emergency call identifier, UE identifier, and target city-level center identifier. The emergency call identifier clearly distinguishes between emergency and regular calls, triggering SEPP's forwarding logic. The UE identifier traces the call initiating user and is used for I-NRF querying the home operator in cross-network roaming scenarios. The target city-level center identifier can be directly associated with the city-level unified emergency call routing table returned by UDM, locking the primary and backup IPs. Service configuration information is used by SMF and UPF to configure dedicated resources, including at least one of the following: emergency service type, QoS configuration parameters, and session identifier. Emergency service types can be assigned corresponding dedicated QoS parameters (e.g., voice 5QI=5, SMS 5QI=7); QoS configuration parameters ensure that UPF reserves dedicated bandwidth for emergency calls (e.g., 15%-20% user plane bandwidth); the session identifier can be associated with emergency PDU sessions created by SMF, avoiding resource conflicts with regular sessions. Routing control information guides SEPP to achieve accurate cross-domain forwarding and includes at least one of the following: home operator identifier, roaming operator identifier, and forwarding priority identifier. The home operator identifier is used to determine if the user is roaming on a different network. If so, SEPP needs to forward the message to the home operator through the provincial interconnection node. The roaming operator identifier identifies the operator the user is currently connected to, and SEPP selects the local forwarding interface accordingly. The forwarding priority identifier ensures that emergency signaling packets are processed first in the SEPP forwarding queue, reducing latency.

[0073] In one possible implementation, the target forwarding path for emergency call signaling is determined based on the home operator user of the target city-level center, including: When the user to which the operation belongs is a local user, the target forwarding path is determined to be that the local SEPP forwards directly to the target city-level center; when the user to which the operation belongs is another user, the target forwarding path is determined to be that the forwarding goes through the local SEPP, the provincial SEPP, and the SEPP corresponding to the other user in sequence, before being forwarded to the target city-level center.

[0074] Specifically, if the operator user is determined to be a local user, then there is no need for a provincial SEPP as a forwarding node to adapt the protocol fields of emergency call signaling for different operators; the data can be directly forwarded to the target city-level center through the local SEPP. If the operator user is determined to be another user, it means that the operator of the target city-level center is different from the operator of the emergency call signaling. In this case, a provincial SEPP is required as a forwarding node to adapt the protocol fields of emergency call signaling for different operators. The provincial SEPP then forwards the data to the SEPP corresponding to the other user, and thus forwards it to the target city-level center.

[0075] The following is an example of the judgment logic for signaling forwarding: Encapsulate emergency signaling packets: Includes source address, destination address, encrypted fields, and business type. IF (Target center is connected to local operator) THEN Local SEPP direct forwarding ELSE Local SEPP forwards data through provincial SEPP interconnection nodes. SEPP encrypted signaling packets: Use TLS 1.3 or DTLS 1.2. Complete protocol field adaptation This signaling forwarding ensures the security and compatibility of signaling in cross-carrier environments.

[0076] In this embodiment, the SEPP cross-domain forwarding mechanism, combined with provincial SEPP interconnection nodes, enables signaling collaborative forwarding among multiple operators. This solves the problem in traditional networks where emergency calls cannot be transmitted across domains due to differences in operator protocols or signaling incompatibility, improving emergency communication capabilities in multi-operator environments, achieving cross-operator collaborative forwarding, and enhancing signaling interoperability. Furthermore, SEPP uses TLS 1.3 or DTLS 1.2 encryption for emergency signaling packets, enabling adaptation of signaling protocol fields across different operators, effectively preventing signaling tampering or interception, and ensuring cross-operator signaling compatibility and transmission security.

[0077] Figure 4 Another flowchart of an emergency call method provided in this disclosure. Figure 4 As shown, the method includes: S401: The UE initiates an emergency call, and the base station forwards the call request to the AMF.

[0078] Specifically, when the UE dials an emergency number (such as 110), the base station receives the call request and forwards it to the AMF.

[0079] S402: AMF identifies the type of call request.

[0080] Specifically, an emergency call can be determined and a unified routing process triggered based on at least one of the following methods: number segment identification, SIP message identifier identification, and inter-network roaming identifier identification. If the number segment matches a pre-configured emergency number database (such as "110", "120", etc.), it is determined to be an emergency call; if the SIP message contains the "Emergency-Service-Type" or "Priority=emergency" field, it is determined to be an emergency call; if the user is an inter-network roaming user and the I-NRF return result is true, it is treated as an emergency call by default.

[0081] S403: The AMF sends a route query request to the UDM. The UDM calls the pre-stored city-level emergency call unified routing table, and the AMF determines the primary and backup addresses of the target city-level center.

[0082] Specifically, the AMF sends a route query request to the UDM, which then uses the pre-configured city-level emergency call unified routing table to determine the primary and backup addresses of the target city-level center. If the UE is a roaming user from another network, the AMF obtains the user's home city code through I-NRF and, in conjunction with the routing table of the roaming operator's UDM, determines the IP address of the target city-level center.

[0083] S404: The AMF sends an emergency call signal to the SEPP.

[0084] Specifically, the emergency call signaling includes the primary address. The AMF encapsulates the emergency call signaling and sends it to the local operator's centralized SEPP. If the target city-level center is connected to the local operator, the local operator's SEPP forwards it directly; if it is connected to another operator, the local operator's SEPP forwards it to the corresponding operator's SEPP through the provincial SEPP interconnection node, and then the corresponding SEPP forwards it to the target city-level center.

[0085] S405: SMF receives an emergency session establishment request from AMF and establishes an emergency session.

[0086] Specifically, the SMF invokes the emergency call resource pool in the UPF, configures dedicated QoS parameters, and establishes an emergency session. Dedicated QoS parameters are configured, such as allocating QI=5 for emergency voice calls and QI=7 for SMS messages, and reserving 15%-20% of user plane bandwidth. When the resource pool utilization exceeds 90%, the system automatically reduces the QoS level of non-emergency services to free up bandwidth.

[0087] By deploying an emergency call resource pool through SMF and UPF, dedicated QoS parameters are allocated for emergency voice and SMS, and a certain proportion of user plane bandwidth is reserved to ensure that emergency services are prioritized when resources are scarce, and to avoid call failures or delays due to insufficient resources.

[0088] The following is an example of the decision logic for resource security: SMF receives AMF session request UPF invokes the emergency call resource pool IF (Resource pool utilization < 90%) THEN Reserve 15%-20% of user plane bandwidth ELSE Automatically downgrade the QoS level of non-urgent services This decision-making logic ensures that emergency calls are given priority even when resources are scarce.

[0089] S406: AMF monitors the status of the target city-level center in real time.

[0090] Specifically, when the primary address fails, it automatically switches to the backup address to ensure uninterrupted routing. Furthermore, the city-level center can deploy a dedicated signaling gateway that only allows emergency signaling forwarded by SEPP to access the system, blocking non-emergency signaling and ensuring the security of alarm reception.

[0091] This disclosure applies to scenarios such as high-speed rail dynamic roaming, earthquake / flood disaster emergency response, and urban boundary communication. Target users include operators, vehicle terminal manufacturers, and third-party testing institutions. Multi-standard compatibility reduces certification costs for automakers and provides full-scenario technical support for 5G emergency communication. In high-speed rail scenarios, routing switching latency is ≤50ms, and the call drop rate is reduced to below 1.2%. In disaster emergency scenarios, cross-network access within 30 seconds is achieved through the TAC resource pool. QoS parameter synchronization deviation in urban boundary areas is <5%. Specifically, the TAI list dynamic update cycle is ≤20ms, the GNSS-TAC mapping accuracy is 99.8%, and the voice call establishment success rate is ≥99.9%, fully meeting the mandatory requirements of GB45672-2025 for emergency call continuity and positioning accuracy.

[0092] Figure 5 This is a schematic diagram of an emergency call device provided in this disclosure. Figure 5 As shown, the device 500 is applied to the Access and Mobility Management Function (AMF) and includes: a first receiving module 510, an identification module 520, a first determining module 530, and a first transmitting module 540.

[0093] The first receiving module 510 is used to receive a call request from the user equipment (UE). Identification module 520 is used to identify the type of the call request; The first determining module 530 is used to determine the target city-level center address IP based on the target unified routing table from the unified data management function UDM when the type of the call request is an emergency call. The first sending module 540 is used to send emergency call signaling to the centralized service exposure point SEPP and to send an emergency session establishment request to the session management function SMF. The emergency call signaling is used for emergency calls across operators and / or across regions, and the emergency call signaling includes at least the target city-level center IP.

[0094] Optionally, the identification module is used for: Extract the first call information from the call request; If the first call information satisfies at least one of the following, then the type of the call request is determined to be an emergency call: The emergency service number belongs to a pre-configured emergency number database; The SIP message is parsed, and it is determined that the SIP message represents an emergency service type or priority as an emergency. When the user's roaming status is that of an inter-network roaming user, the user's roaming status is queried based on the Inter-network Network Resource Function (I-NRF) and the user is determined to be an emergency roaming user.

[0095] Optionally, the identification module is used for: Send a route query request to the UDM; The system receives the target unified routing table from the UDM. The target unified routing table includes at least the primary address of the target city center and the city code of the target city center. The target unified routing table is used to determine the mapping relationship between the UE and the target city center. When the user's roaming status is that of a cross-network roaming user, the home city code of the UE is obtained based on the cross-network network resource function I-NRF; Based on the UE's home city code and the city code of the target unified routing table, the corresponding primary address is determined, and the primary address is used as the target city-level center IP.

[0096] Optionally, the device further includes: the target unified routing table also includes the backup address of the target city-level center, and a disaster recovery detection request is sent to the primary address; If no feedback message is received from the primary address for N consecutive times, it is determined that the primary address has failed, and the target city-level center IP is switched to the backup address, where N is an integer greater than or equal to 1.

[0097] Figure 6 This is another structural schematic diagram of an emergency call device provided in this disclosure. Figure 6 As shown, the device 600 is applied to the unified data management function (UDM) and includes: a second receiving module 610, a calling module 620, and a second sending module 630.

[0098] The second receiving module 610 is used to receive a routing query request from the Access and Mobility Management Function (AMF), the routing query request being sent by the AMF when it recognizes that the type of the received call request is an emergency call; Module 620 is invoked to call the pre-configured city-level emergency call unified routing table and determine the target unified routing table; The second sending module 630 is used to return the target unified routing table to the AMF; the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

[0099] Figure 7 This is another structural schematic diagram of an emergency call device provided in this disclosure. As shown in the figure, the device 700 is applied to a centralized service exposure point (SEPP) and includes: a third receiving module 710, a second determining module 720, and a third sending module 730.

[0100] The third receiving module 710 is used to receive emergency call signaling from the Access and Mobility Management Function (AMF), wherein the emergency call signaling includes at least the IP address of the target city-level center. The second determining module 720 is used to determine the target forwarding path of the emergency call signaling based on the home operating user of the target city-level center. The third sending module 730 is used to send the emergency call signaling to the target city-level center based on the target forwarding path and the target city-level center IP.

[0101] Optionally, the second determining module is used to: When the user attribution is a local user, the target forwarding path is determined to be a direct forwarding from the local SEPP to the target city-level center; When the user to which the operation belongs is another user, the target forwarding path is determined to be forwarded to the target city-level center in sequence through the local SEPP, the provincial SEPP, and the SEPP corresponding to the other user.

[0102] This application also provides an electronic device for performing the above-described emergency call method. Please refer to... Figure 8 It illustrates a schematic diagram of an electronic device provided by some embodiments of this application. For example... Figure 8 As shown, the electronic device 80 includes: a processor 800, a memory 801, a bus 802, and a communication interface 803. The processor 800, the communication interface 803, and the memory 801 are connected via the bus 802. The memory 801 stores a computer program that can run on the processor 800. When the processor 800 runs the computer program, it executes the emergency call method provided in any of the foregoing embodiments of this application.

[0103] The memory 801 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this device network element and at least one other network element is achieved through at least one communication interface 803 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0104] Bus 802 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 801 is used to store programs. After receiving an execution instruction, the processor 800 executes the program. The emergency call method disclosed in any of the foregoing embodiments of this application can be applied to the processor 800, or implemented by the processor 800.

[0105] The processor 800 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 800 or by instructions in software form. The processor 800 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 801. Processor 800 reads the information in memory 801 and, in conjunction with its hardware, completes the steps of the above method.

[0106] The electronic device provided in this application embodiment and the emergency call method provided in this application embodiment are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0107] This application also provides a computer-readable storage medium corresponding to the emergency call method provided in the foregoing embodiments. The computer-readable storage medium shown may be an optical disc, on which a computer program is stored. When the computer program is run by a processor, it executes the emergency call method provided in any of the foregoing embodiments.

[0108] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0109] The computer-readable storage medium provided in the above embodiments of this application and the emergency call method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0110] This application also provides a computer program product 900, such as... Figure 9 As shown. This computer program product carries a computer program 901, the instructions of which can be used to execute the steps of the emergency call method described in the above method embodiments, as detailed in the above method embodiments, which will not be repeated here.

[0111] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0112] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0113] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0114] Additionally, as used herein, the "or" used in a list of items beginning with "at least one" indicates a separate list, such that a list of, for example, "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not imply that the described example is preferred or better than other examples.

[0115] It should also be noted that in the systems and methods of this disclosure, the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered as equivalent solutions to this disclosure.

[0116] Various changes, substitutions, and modifications can be made to the technology described herein without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of this disclosure is not limited to the specific aspects of the processes, machines, manufactures, events, means, methods, and actions described above. Currently existing or later-developed processes, machines, manufactures, events, means, methods, or actions that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein can be utilized. Therefore, the appended claims include such processes, machines, manufactures, events, means, methods, or actions within their scope.

[0117] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0118] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. An emergency call method, characterized in that, The method, applied to the Access and Mobility Management Function (AMF), includes: Receive call requests from user equipment (UE); Identify the type of the call request; When the type of the call request is an emergency call, the target city-level center address IP is determined based on the target unified routing table from the unified data management function UDM; An emergency call signaling is sent to the centralized service exposure point SEPP, and an emergency session establishment request is sent to the session management function SMF. The emergency call signaling is used for emergency calls across operators and / or across regions, and the emergency call signaling includes at least the target city-level center IP.

2. The method according to claim 1, characterized in that, The call request includes at least one of the following first call information: emergency service number, Session Initiation Protocol (SIP) message, and user roaming status.

3. The method according to claim 2, characterized in that, The identification of the type of the call request includes: Extract the first call information from the call request; If the first call information satisfies at least one of the following, then the type of the call request is determined to be an emergency call: The emergency service number belongs to a pre-configured emergency number database; The SIP message is parsed, and it is determined that the SIP message represents an emergency service type or priority as an emergency. When the user's roaming status is that of an inter-network roaming user, the user's roaming status is queried based on the Inter-network Network Resource Function (I-NRF) and the user is determined to be an emergency roaming user.

4. The method according to claim 2, characterized in that, When the call request type is an emergency call, the target city-level center address IP is determined based on the target unified routing table from the Unified Data Management Function (UDM), including: Send a route query request to the UDM; The system receives the target unified routing table from the UDM. The target unified routing table includes at least the primary address of the target city center and the city code of the target city center. The target unified routing table is used to determine the mapping relationship between the UE and the target city center. When the user's roaming status is that of a cross-network roaming user, the home city code of the UE is obtained based on the cross-network network resource function I-NRF; Based on the UE's home city code and the city code of the target unified routing table, the corresponding primary address is determined, and the primary address is used as the target city-level center IP.

5. The method according to claim 4, characterized in that, The target unified routing table also includes the backup address of the target city-level center, and the method further includes: Send a disaster recovery detection request to the primary address; If no feedback message is received from the primary address for N consecutive times, it is determined that the primary address has failed, and the target city-level center IP is switched to the backup address, where N is an integer greater than or equal to 1.

6. The method according to claim 1, characterized in that, The emergency call signaling includes at least one of the following: core identification information, service configuration information, and routing control information, wherein the core identification information includes at least one of the target municipal center IP addresses.

7. An emergency call method, characterized in that, The method, applied to a unified data management function (UDM), includes: Receive a routing query request from the Access and Mobility Management Function (AMF), the routing query request being sent by the AMF when it recognizes that the type of the received call request is an emergency call; Invoke the pre-configured city-level emergency call unified routing table and determine the target unified routing table; The target unified routing table is returned to the AMF; the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

8. An emergency call method, characterized in that, The method, applied to a centralized service exposure point (SEPP), includes: Receive emergency call signaling from the Access and Mobility Management Function (AMF), wherein the emergency call signaling includes at least the target city-level center address IP; Based on the affiliated operating user of the target city-level center, determine the target forwarding path of the emergency call signaling; Based on the target forwarding path and the target city-level center IP, the emergency call signaling is sent to the target city-level center.

9. The method according to claim 8, characterized in that, The determination of the target forwarding path for the emergency call signaling based on the home operator user at the target city-level center includes: When the user attribution is a local user, the target forwarding path is determined to be a direct forwarding from the local SEPP to the target city-level center; When the user to which the operation belongs is another user, the target forwarding path is determined to be forwarded to the target city-level center in sequence through the local SEPP, the provincial SEPP, and the SEPP corresponding to the other user.

10. An emergency call device, characterized in that, The device, used in Access and Mobility Management Function (AMF), includes: The first receiving module is used to receive call requests from user equipment (UE). The identification module is used to identify the type of the call request; The first determining module is used to determine the target city-level center address IP based on the target unified routing table from the unified data management function UDM when the type of the call request is an emergency call. The first sending module is used to send emergency call signaling to the centralized service exposure point SEPP and to send an emergency session establishment request to the session management function SMF. The emergency call signaling is used for emergency calls across operators and / or across regions, and the emergency call signaling includes at least the target city-level center IP.

11. An emergency call device, characterized in that, The device, used in Unified Data Management (UDM) functions, includes: The second receiving module is used to receive a routing query request from the Access and Mobility Management Function (AMF), which is sent by the AMF when it recognizes that the type of the received call request is an emergency call. The calling module is used to invoke the pre-configured city-level emergency call unified routing table and determine the target unified routing table; The second sending module is used to return the target unified routing table to the AMF; the target city-level center address IP in the target unified routing table is used by the AMF to initiate an emergency session establishment request.

12. An emergency call device, characterized in that, The device, applied to a centralized service exposure point (SEPP), includes: The third receiving module is used to receive emergency call signaling from the Access and Mobility Management Function (AMF), wherein the emergency call signaling includes at least the target city-level center address IP. The second determining module is used to determine the target forwarding path of the emergency call signaling based on the affiliated operating user of the target city-level center. The third sending module is used to send the emergency call signaling to the target city-level center based on the target forwarding path and the target city-level center IP.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the method as described in any one of claims 1-6, 7, 8-9.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by a processor to implement the method as described in any one of claims 1-6, 7, 8-9.

15. A computer program product, characterized in that, Includes computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is executed in a processor of an electronic device, the processor in the electronic device performs the method as described in any one of claims 1-6, 7, 8-9.

Images