Emergency call processing method and device and network side equipment

Abstract

The invention discloses an emergency call processing method and device and network side equipment, and belongs to the technical field of wireless communication. The method comprises the following steps: a first network element receives a first emergency call request sent by a remote terminal; the first network element obtains an identifier of a relay terminal corresponding to the remote terminal; and the first network element sends a second emergency call request to a second network element, the second emergency call request carrying the identifier of the relay terminal.

Description

Technical Field

[0001] The present application belongs to the field of wireless communication technology, and specifically relates to a method, device and network-side equipment for processing emergency calls. Background Art

[0002] With the development of network informatization, in order to expand network coverage, the current mainstream solution is to enable terminals at the edge of the cell or outside the network coverage to access the network through the relay terminal (relay UE) to obtain network services. In the layer 3 relay communication scenario (Layer-3 UE-to-Network relay), the relay terminal (relay UE) can provide relay services for the remote terminal (Remote UE). For example, the relay terminal (relay UE) receives service data from the remote terminal (Remote UE) and forwards it to the network, or the relay terminal (relay UE) receives data sent by the network to the remote terminal (Remote UE) and forwards it to the remote terminal (Remote UE).

[0003] When the terminal initiates an Internet Protocol (IP) Multimedia Subsystem (IMS) emergency call, the emergency call session control function (CSCF) receives the emergency call request sent by the UE and sends a request to the location retrieval function (LRF) to verify the location information (for example, cell ID) carried by the UE, or to obtain the location information of the UE (for example, the UE does not carry location information).

[0004] In the process of the relay terminal (relay UE) providing relay service for the remote terminal (Remote UE), when the remote terminal (Remote UE) initiates a (multimedia subsystem) emergency call through the relay terminal (relay UE), since the remote terminal (Remote UE) is connected to the 4G or 5G network through the relay terminal, the remote terminal may not be registered in the 4G or 5G network. Therefore, the location retrieval function (Location Retrieval Function, LRF) may not be able to obtain the location information of the remote terminal, resulting in the emergency call session control function (Emergency CSCF, E-CSCF) rejecting the IMS emergency call initiated by the remote terminal because it cannot obtain the location of the remote terminal, resulting in the failure of the emergency call. Summary of the invention

[0005] The embodiments of the present application provide an emergency call processing method, apparatus and network-side equipment, which can solve the problem that the E-CSCF rejects the IMS emergency call initiated by the remote terminal because the location of the remote terminal cannot be obtained, thereby causing the emergency call to fail.

[0006] In the first aspect, a method for processing an emergency call is provided, the method comprising: a first network element receives a first emergency call request sent by a remote terminal; the first network element obtains an identifier of a relay terminal corresponding to the remote terminal; the first network element sends a second emergency call request to a second network element, wherein the second emergency call request carries the identifier of the relay terminal.

[0007] In a second aspect, a method for processing an emergency call is provided, the method comprising: a second network element receives a second emergency call request sent by a first network element, wherein the second emergency call request carries an identifier of a relay terminal; and the second network element sends the identifier of the relay terminal to a fourth network element.

[0008] According to a third aspect, an emergency call processing device is provided, which includes: a first receiving module for receiving a first emergency call request sent by a remote terminal; an acquisition module for acquiring an identifier of a relay terminal corresponding to the remote terminal; and a first sending module for sending a second emergency call request to a second network element, wherein the second emergency call request carries the identifier of the relay terminal.

[0009] In a fourth aspect, a device for processing an emergency call is provided, which includes: a second receiving module for receiving a second emergency call request sent by a first network element, wherein the second emergency call request carries an identifier of a relay terminal; and a second sending module for sending the identifier of the relay terminal to a fourth network element.

[0010] In a fifth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0011] In a sixth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0012] In a seventh aspect, a wireless communication system is provided, comprising: a network side device, wherein the network side device can be used to execute the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0013] In an eighth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0014] In a ninth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method according to the first aspect, or to implement the steps of the method according to the second aspect,

[0015] In an embodiment of the present application, after receiving the first emergency call request sent by the remote terminal, the first network element obtains the identifier of the relay terminal corresponding to the remote terminal, and then sends a second emergency call request carrying the identifier of the relay terminal to the second network element, so that the network side can obtain the corresponding location information based on the identifier of the relay terminal for emergency call processing, thereby solving the problem that the E-CSCF rejects the IMS emergency call initiated by the remote terminal because it cannot obtain the location of the remote terminal, resulting in the failure of the emergency call. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A block diagram showing a wireless communication system to which the embodiments of the present application can be applied;

[0017] Figure 2 A flow chart showing a method for processing an emergency call provided in the related art;

[0018] Figure 3 A schematic diagram showing a flow chart of a method for processing an emergency call provided in an embodiment of the present application;

[0019] Figure 4 Another schematic diagram showing a flow chart of a method for processing an emergency call provided in an embodiment of the present application;

[0020] Figure 5 Another flowchart of the method for processing an emergency call provided in an embodiment of the present application is shown;

[0021] Figure 6 A schematic diagram showing the structure of an emergency call processing device provided in an embodiment of the present application;

[0022] Figure 7 Another structural schematic diagram of an emergency call processing device provided in an embodiment of the present application is shown;

[0023] Figure 8 A schematic diagram showing the structure of a communication device provided in an embodiment of the present application is shown;

[0024] Fig. 9 A schematic diagram of the hardware structure of a network side device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0025] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0026] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0027] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0028] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0029] Figure 1 A block diagram of a wireless communication system to which the present application embodiment can be applied is shown. Figure 1 As shown, the wireless communication system includes a relay terminal 11, a network side device 12 and a remote terminal 13. In the embodiment of the present application, the remote terminal 13 communicates with the relay terminal 11 via a PC5 (secondary link) interface, and the relay terminal 11 communicates with the network side device 12 via a Uu interface.

[0030] Among them, the relay terminal 11 can also be called a relay terminal device or a relay user terminal (User Equipment, UE), the remote terminal 13 can also be called a remote terminal device or a remote UE, the relay terminal 11 and the remote terminal 13 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. In addition to the above-mentioned terminal devices, it can also be a chip in the terminal, such as a modem chip, a system-level chip (System on Chip, SoC). It should be noted that the specific types of the relay terminal 11 and the remote terminal 13 are not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0031] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0032] In the Layer-3 UE-to-Network relay scenario, the relay terminal (relay UE) can provide relay services for the remote terminal (Remote UE). For example, the relay UE receives service data from the remote UE and then routes it to the network, or the relay UE receives data sent by the network to the remote UE and then routes it to the Remote UE. In the process of the relay UE providing relay services for the remote UE, the relay UE allocates an IP address to the remote UE, and the Remote UE generates an IP packet using the IP address allocated by the relay UE. If the relay UE itself only has an IPv4 address, the relay UE will allocate a private network IP address to the remote UE. For example, the allocated private network IP address is IP-A. After the relay UE receives the IP packet containing the IP-A from the remote UE, it converts IP-A to IP-B through NAT (Network Address Translation) and sends it to the network. IP-B can be the IP address allocated to the relay UE by the network.

[0033] Figure 2 FIG. 1 is a flow chart showing a method for processing an emergency call provided in the related art. Figure 2 As shown, the method may include the following steps:

[0034] S201: The UE is in a registered state in the 5G network, and the UE establishes an emergency protocol data unit (PDU) session; it is worth noting that the 5G network is used as an example here, but it is also applicable to 4G or 6G networks.

[0035] S202: The UE initiates an IMS emergency call through an Invite message, which includes the IMS identification information of the UE and the location information of the UE, such as the cell identity (ID) of the UE.

[0036] S203: The Proxy CSCF (P-CSCF) obtains the UE identity according to the IMS identity, and sends the Invite message and the UE identity to the Emergency CSCF (E-CSCF).

[0037] S204: The Emergency CSCF (E-CSCF) sends a request to the LRF, carrying the UE identity. The message is used to verify the cell ID carried by the UE, or to request the location of the UE.

[0038] S205: The LRF obtains the Access and Mobility Management Function (AMF) that provides services for the UE based on the UE identifier, and requests the UE location information from the AMF.

[0039] S206: AMF requests the location information of the UE from the Location Management Function (LMF).

[0040] S207: LMF performs the Positioning function to obtain the location information of the UE.

[0041] S208: LMF sends the UE location information to AMF.

[0042] S209: The Access and Mobility Management Function (AMF) sends the UE location information to the LRF.

[0043] S210: The LRF sends the UE location information or verification result to the E-CSCF.

[0044] S211: The E-CSCF obtains the PSAP (Public Safety Access Point) that provides services for the UE according to the location of the UE, and completes the subsequent emergency call process.

[0045] However, in the relay communication scenario, when the Remote UE initiates an IMS emergency call through the relay UE, after receiving the emergency call request sent by the UE, the E-CSCF will send a request to the LRF (Location Retrieval Function) to verify the location information (e.g., cell ID) carried by the UE, or to obtain the location information of the UE (e.g., the UE does not carry location information). Since the remote UE is connected to the 4G or 5G network through the relay UE, the remote UE itself may not be registered in the 4G or 5G network, so the LRF cannot obtain the location information of the remote UE, causing the E-CSCF to reject the IMS emergency call initiated by the remote UE because it cannot obtain the location of the remote UE.

[0046] In order to solve the above technical problems, the present application provides a method, apparatus and network-side equipment for processing an emergency call.

[0047] In conjunction with the accompanying drawings, an emergency call processing method, apparatus, and network-side device provided in an embodiment of the present application are described in detail below through some embodiments and their application scenarios.

[0048] Figure 3 A flow chart of a method for processing an emergency call in an embodiment of the present application is shown, and the method 300 may be executed by a first network element. In other words, the method may be executed by software or hardware installed on the first network element.

[0049] In the embodiment of the present application, the first network element may be a functional entity in the core network for proxy call session control. For example, the first network element may be a proxy call session control function (Proxy CSCF, P-CSCF) in the core network. Figure 3 As shown, the method may include the following steps.

[0050] S310: A first network element receives a first emergency call request sent by a remote terminal.

[0051] For example, the remote terminal may send the first emergency call request through an Invite message, and the first network element receives the first emergency call request.

[0052] In an embodiment of the present application, the remote terminal may send the above-mentioned first emergency call request through a relay terminal, and the relay terminal forwards the first emergency call request to the network side.

[0053] For example, the remote terminal can establish a PC5 connection with the relay terminal, which is in a registered state in the network, and then the remote terminal sends a first emergency call request to the relay terminal through the PC5 interface. After the relay terminal receives the first emergency call request through the PC5 interface, it forwards the first emergency call request to the network side.

[0054] Optionally, the first emergency call request may carry the following information:

[0055] (1) IMS identification information of the remote UE; for example, the IP address allocated by the relay UE to the remote UE.

[0056] (2) Location information of the relay UE, such as the cell ID of the UE, where the remote UE can obtain the location information of the relay UE from the relay UE;

[0057] (3) access type "3GPP-NR-ProSe-L3UNR"; wherein access type "3GPP-NR-ProSe-L3UNR" indicates that the value of access type is "3rd Generation Partnership Project - New Radio - Short Range Service - Layer 3 User Equipment to Network Relay (3GPP-NR-ProSe-L3UNR)", which can also be expressed as access type = "3GPP-NR-ProSe-L3UNR";

[0058] (4) access type "3GPP-E-UTRAN-ProSe-UNR"; wherein access type "3GPP-E-UTRAN-ProSe-UNR" indicates that the value of access type is "3rd Generation Partnership Project Evolved Universal Terrestrial Radio Access Network - Short Range Service - User Equipment to Network Relay (3GPP-E-UTRAN-ProSe-UNR)", which can also be expressed as access type = "3GPP-E-UTRAN-ProSe-UNR".

[0059] It should be noted that the access type carried in the first emergency call request may be included in the access network information (P-Access-Network-Info) header of the IMS message.

[0060] It should be noted that in the 5G communication system, when the remote UE sends the first emergency call request through the relay UE, the value of the access type carried is 3GPP-NR-ProSe-L3UNR; in the 4G communication system, when the remote UE sends the first emergency call request through the relay UE, the value of the access type carried is 3GPP-E-UTRAN-ProSe-UNR; similarly, in the 6G communication system, when the remote UE sends an IMS message through the relay UE, the value of the access type carried can be 3GPP-6G-ProSe-L3UNR, where 6G can be replaced according to the actual naming of the 6G communication system. For example, when 6G is named FR, the value of the access type can be 3GPP-FR-ProSe-L3UNR.

[0061] S312: The first network element obtains an identifier of a relay terminal corresponding to the remote terminal.

[0062] In an embodiment of the present application, the first network element may obtain the identifier of the relay terminal according to the value of the access type carried in the first emergency call request.

[0063] For example, the first network element determines, based on the access type "3GPP-NR-ProSe-L3UNR" carried in the first emergency call request, that the first emergency call request is sent by the remote UE through the relay UE, and obtains the ID of the relay UE.

[0064] In one implementation, the first network element may obtain the identifier of the relay terminal locally.

[0065] For example, before S310, the first network element receives an IMS registration (Register) request from the remote terminal, and the IMS registration request carries an IP address assigned by the relay terminal to the remote terminal. The first network element requests the third network element (e.g., PCF) for the identifier of the UE corresponding to the IP address based on the IP address. The third network element determines that the IP address is the address assigned to the relay terminal, and therefore returns the identifier of the relay terminal to the first network element, which stores the identifier of the relay terminal. Upon receiving the first emergency call request sent by the remote terminal, the identifier of the relay terminal is obtained from the locally stored data.

[0066] It should be noted that when the relay terminal establishes a PDU session, the 5G network can allocate a group of IP addresses to the relay terminal, such as 10 IPs. When the remote terminal is connected to the relay terminal, the relay terminal allocates one of the IP addresses (for example, one of the 10 IPs) to the remote terminal. The remote terminal carries the IP address in the first emergency call request. The first network element can determine the relay terminal corresponding to the remote terminal based on the IP address.

[0067] In another implementation manner, the first network element may also obtain the identifier of the relay terminal from the third network element.

[0068] For example, the first network element requests the UE identifier corresponding to the IP address carried in the first emergency call request from the third network element (for example, PCF). The third network element determines that the IP address is the address assigned to the relay terminal, and therefore returns the identifier of the relay terminal to the first network element.

[0069] For example, the first network element may send one of the following message requests to the third network element:

[0070] Npcf_PolicyAuthorization_Create;

[0071] Npcf_PolicyAuthorization_Update.

[0072] The above message request may include the IP address of the relay UE.

[0073] In an embodiment of the present application, the identifier of the relay terminal may include at least one of the following:

[0074] The Mobile Station international ISDN number (MSISDN) of the relay terminal;

[0075] The Generic Public Subscription Identifier (GPSI) of the relay terminal;

[0076] The International Mobile Subscriber Identity (IMSI) of the relay terminal;

[0077] The Subscription Permanent Identifier (SUPI) of the relay terminal.

[0078] S314, the first network element sends a second emergency call request to the second network element, where the second emergency call request carries the identifier of the relay terminal.

[0079] It should be noted that the second emergency call request is obtained based on the first emergency call request and carries the identifier of the relay terminal on the basis of the first emergency call request.

[0080] In an embodiment of the present application, the first network element makes the second network element execute the subsequent procedures of the emergency call according to the identifier of the relay terminal by carrying the identifier of the relay terminal in the second emergency call request message, so as to ensure the normal execution of the emergency call.

[0081] In an embodiment of the present application, the second network element may be a functional entity in the core network for processing emergency call control. For example, the second network element may be an Emergency Call Session Control Function (E-CSCF).

[0082] In one implementation, the identifier of the relay terminal may be carried in the message header of the second emergency call request.

[0083] Optionally, the message header may include at least one of the following:

[0084] (1) Contact message header; for example, contact: <relay UE identifier>; indication.

[0085] (2) From header; for example, From: <relay UE identifier>; indication.

[0086] Among them, the indication in (1) or (2) is used to indicate that the content within <> is the identifier of the relay UE, for example, relay UE ID.

[0087] (3) Access network information (P-Access-Network-Info) header, for example, P-Access-Network-Info: Access type “3GPP-NR-ProSe-L3UNR”, relay UE identifier. Among them, access type is a parameter of P-Access-Network-Info. In this implementation manner, a new information for carrying the relay UE ID is added to the access type parameter; or, a new parameter for carrying the relay UE ID is added to P-Access-Network-Info.

[0088] In one implementation manner, the first network element can determine to send the second emergency call request carrying the identifier of the relay terminal to the second network element according to the value of the access type in the first emergency call request. For example, the second network element can obtain the ID of the relay UE according to access type “3GPP-NR-ProSe-L3UNR” and determine to send the identifier of the relay UE to the second network element.

[0089] It should be noted that the first network element can determine to send the second emergency call request carrying the identifier of the relay terminal to the second network element according to the value of the access type in the first emergency call request, and it can also be understood that: the first network element can determine to send the second emergency call request carrying the identifier of the relay terminal to the second network element according to the access type in the first emergency call request.

[0090] Through the above emergency call processing method provided by the embodiments of the present application, when the first network element receives an emergency call request sent by a remote terminal, it can obtain the identifier of the relay terminal corresponding to the remote terminal, and then send the emergency call request carrying the identifier of the relay terminal to the second network element, so that the second network element can process the subsequent process of the emergency call according to the identifier of the relay terminal, ensuring the success of the emergency call.

[0091] Figure 4 Another process schematic diagram showing the processing method of the emergency call in the embodiments of the present application is shown. This method 400 can be executed by the second network element. In other words, the method can be executed by software or hardware installed on the second network element.

[0092] In an embodiment of the present application, the second network element may be a functional entity in the core network for emergency call session control. For example, the second network element may be the Proxy Call Session Control Function (P-CSCF) in the core network. As Figure 4 shown, the method may include the following steps.

[0093] S410, the second network element receives a second emergency call request sent by the first network element, where the second emergency call request carries an identifier of the relay terminal.

[0094] In an embodiment of the present application, the second emergency call request may be sent by the first network element after receiving a first emergency call request sent by a remote terminal. The first network element may send the second emergency call request in the manner described in the above method 300. For specific reference, see the description in the above method 300 and will not be elaborated here.

[0095] In one implementation, the identifier of the relay terminal may be carried in the message header of the second emergency call request.

[0096] Optionally, the message header may include at least one of the following:

[0097] (1) Contact message header; for example, contact: <relay UE identifier>; indication.

[0098] (2) From message header; for example, From: <relay UE identifier>; indication.

[0099] Wherein, the indication in (1) or (2) is used to indicate that the content within <> is the identifier of the relay UE, for example, relay UE ID.

[0100] (3) Access network information (P-Access-Network-Info) message header, for example, P-Access-Network-Info: Access type “3GPP-NR-ProSe-L3UNR”, relay UE identifier. Where access type is a parameter of P-Access-Network-Info. In this implementation, a new information for carrying the relay UE ID is added to the access type parameter; or a new parameter for carrying the relay UE ID is added to P-Access-Network-Info.

[0101] S412, the second network element sends the identifier of the relay terminal to the fourth network element.

[0102] In an embodiment of the present application, the fourth network element may be a functional entity for location acquisition, for example, the fourth network element may be a location retrieval function (LRF) or a gateway mobile location center (GMLC).

[0103] In one implementation, the second emergency call request may carry an access type, and a value of the access type includes any one of the following:

[0104] 3rd Generation Mobile Communications Partnership Project - New Radio - Short Range Services - Layer 3 User Equipment to Network Relay (3GPP-NR-ProSe-L3UNR);

[0105] 3rd Generation Partnership Project Evolved Universal Terrestrial Radio Access Network - Short Range Services - User Equipment to Network Relay (3GPP-E-UTRAN-ProSe-UNR).

[0106] In one implementation, before the second network element sends the identifier of the relay terminal to the fourth network element, the second network element determines and obtains the identifier of the relay terminal carried in the second emergency call request according to the value of the access type.

[0107] Optionally, the second network element determines, based on the value of the access type, that the second emergency call request is triggered by a remote terminal accessed through the relay terminal; the second network element obtains the identifier of the relay terminal carried in the second emergency call request. For example, the second network element obtains the ID of the relay UE based on the access type "3GPP-NR-ProSe-L3UNR" and sends the identifier of the relay UE to the fourth network element. The second network element may obtain the ID of the relay UE from the message header of at least one of the above in the second emergency call request.

[0108] In an embodiment of the present application, the second network element sends the identifier of the relay UE to the fourth network element, so that the location information corresponding to the identifier of the relay UE can be obtained through the fourth network element, and then, based on the location information, the public safety access point (PSAP) providing service for the remote UE is obtained, and the subsequent emergency call process is completed.

[0109] For example, after S412, the fourth network element can obtain the AMF providing services for the relay UE based on the identifier of the relay terminal, and request the location information of the Relay UE from the AMF. Then the AMF requests the location information of the Relay UE from the LMF (Location Management Function), and returns the acquired location information of the Relay UE to the fourth network element. The fourth network element returns the location information or the verification result to the second network element. The second network element obtains the Public Safety Access Point (PSAP) providing services for the UE based on the location information, and completes the subsequent emergency call process.

[0110] In the technical solution provided in the embodiment of the present application, after receiving the second emergency call request carrying the identifier of the relay terminal, the second network element sends the identifier of the relay terminal to the fourth network element to obtain the location information corresponding to the identifier, thereby providing emergency call service for the remote terminal.

[0111] The following uses an example in which the first network element is a P-CSCF and the second network element is an E-CSCF to illustrate the technical solution provided in the embodiment of the present application.

[0112] Figure 5 Another flow chart of the method for processing an emergency call according to an embodiment of the present application is shown. Figure 5 As shown, the method mainly includes the following steps:

[0113] S501. The Remote UE establishes a PC5 connection with the relay UE.

[0114] In an embodiment of the present application, the Relay UE is in a registered state in the 5G network, and the Relay UE has established an emergency protocol data unit (PDU) session.

[0115] S502. The Remote UE initiates an IMS emergency call via an Invite message.

[0116] The Invite message may include the following information:

[0117] (1) IMS identification information of remote UE;

[0118] (2) The location information of the relay UE, such as the cell ID of the UE; the remote UE obtains the location information of the relay UE from the relay UE.

[0119] (3)access type “3GPP-NR-ProSe-L3UNR”

[0120] Among them, access type "3GPP-NR-ProSe-L3UNR" means that the value of access type is "3GPP-NR-ProSe-L3UNR", which can also be expressed as access type = "3GPP-NR-ProSe-L3UNR".

[0121] S503. P-CSCF obtains the ID of relay UE.

[0122] The relay UE identifier may include at least one of the following:

[0123] MSISDN (Mobile Station international ISDN number);

[0124] GPSI (Generic Public Subs cription Identifier, general public user identification);

[0125] IMSI (International Mobile Subscriber Identity);

[0126] SUPI (SUbscription Permanent Identifier).

[0127] Among them, the P-CSCF determines that the invite request is sent by the remote UE through the relay UE according to the access type "3GPP-NR-ProSe-L3UNR", and then obtains the ID of the relay UE.

[0128] The ID of the relay UE may be obtained locally by the P-CSCF (for example, the ID of the relay UE obtained when the remote UE performs IMS registration); or,

[0129] The ID of the relay UE may also be requested by the P-CSCF to the PCF, specifically, the P-CSCF may request the PCF through the Npcf_PolicyAuthorization_Create or Npcf_PolicyAuthorization_Update message request. The request includes the IP address of the relay UE, thereby obtaining the ID of the relay UE from the PCF.

[0130] S504. The P-CSCF receives the ID of the relay UE sent by the PCF.

[0131] S505. The P-CSCF sends an invite message to the E-CSCF, carrying the ID of the relay UE in the invite message.

[0132] Among them, the carrying methods of the ID of the relay UE include at least one of the following:

[0133] (1) Carried through the Contact header: For example, contact: <relay UE identifier>; indication.

[0134] (2) Carried through the From header: For example, From: <relay UE identifier>; indication

[0135] Among them, the above indication is used to indicate that the content within <> is the identifier of the relay UE. For example, relay UE ID.

[0136] (3) Carried through the P-Access-Network-Info header: For example, P-Access-Network-Info: Accesstype “3GPP-NR-ProSe-L3UNR”, relay UE identifier.

[0137] Among them, access type is a parameter of P-Access-Network-Info. In the embodiments of this application, a new information for carrying the relay UE ID is added to the access type parameter; or, a new parameter for carrying the relay UE ID is added to the P-Access-Network-Info.

[0138] S506. The E-CSCF obtains the ID of the relay UE according to access type “3GPP-NR-ProSe-L3UNR” and sends the identifier of the relay UE to the LRF.

[0139] Among them, the E-CSCF can obtain the ID of the relay UE from the message header described in S505.

[0140] S507. Perform subsequent processes according to Figure 2 S205 - 211 therein.

[0141] Through the above-mentioned technical solution of the embodiment of the present application, after the P-CSCF receives the emergency call request sent by the remote UE, it obtains the identifier of the relay UE corresponding to the remote UE, carries the identifier of the relay UE in the emergency call request and sends it to the E-CSCF. The E-CSCF sends the identifier of the relay UE to the LRF, so that the location verification or acquisition process can be executed correctly, ensuring the correct execution of the emergency call.

[0142] The emergency call processing method provided in the embodiment of the present application can be executed by an emergency call processing device. In the embodiment of the present application, the emergency call processing device executing the emergency call processing method is taken as an example to illustrate the emergency call processing device provided in the embodiment of the present application.

[0143] Figure 6 A schematic diagram of the structure of an emergency call processing device provided in an embodiment of the present application is shown as follows: Figure 6 As shown, the device 600 mainly includes: a first receiving module 601, an acquiring module 602 and a first sending module 603.

[0144] In an embodiment of the present application, the first receiving module 601 is used to receive a first emergency call request sent by a remote terminal; the acquisition module 602 is used to obtain the identifier of the relay terminal corresponding to the remote terminal; the first sending module 603 is used to send a second emergency call request to a second network element, wherein the second emergency call request carries the identifier of the relay terminal.

[0145] In one implementation, the first emergency call request carries an access type, and a value of the access type includes any one of the following: 3GPP-NR-ProSe-L3UNR; 3GPP-E-UTRAN-ProSe-UNR.

[0146] In one implementation, the obtaining module 602 obtains the identifier of the relay terminal, including: obtaining the identifier of the relay terminal according to the value of the access type.

[0147] In one implementation, the acquiring module 602 acquires the identifier of the relay terminal corresponding to the remote terminal according to the access type, including:

[0148] Determining, according to a value of the access type, that the first emergency call request is sent by the remote terminal through the relay terminal;

[0149] Obtain an identifier of the relay terminal.

[0150] In one implementation, the obtaining module 602 obtains the identifier of the relay terminal, including one of the following:

[0151] Acquire the identification of the relay terminal locally;

[0152] The identifier of the relay terminal is obtained from a third network element.

[0153] In one implementation, the second emergency call request carries the identifier of the relay terminal, including:

[0154] The identifier of the relay terminal is carried in a message header of the second emergency call request.

[0155] In one implementation, the message header includes at least one of the following:

[0156] Contact message header;

[0157] From message header;

[0158] P-Access-Network-Info message header.

[0159] In one implementation, the first sending module 603 sends the second emergency call request to the second network element, including: sending the second emergency call request carrying the identifier of the relay terminal to the second network element according to the value of the access type.

[0160] In one implementation, the identifier of the relay terminal includes at least one of the following:

[0161] The mobile station International Integrated Services Digital Network (ISDN) number of the relay terminal;

[0162] The universal public user identity of the relay terminal;

[0163] The international mobile subscriber identity code of the relay terminal;

[0164] A permanent identifier of a user of the relay terminal.

[0165] By using the above-mentioned device provided in the embodiment of the present application, when an emergency call request sent by a remote terminal is received, the identifier of the relay terminal corresponding to the remote terminal can be obtained, and the identifier of the relay terminal can be carried in the emergency call request, so that the emergency call of the remote terminal can be processed according to the location of the relay terminal, thereby ensuring the success of the emergency call of the remote terminal.

[0166] Figure 7 Another structural schematic diagram of the emergency call processing device provided in an embodiment of the present application is shown. Figure 7 As shown, the device 700 mainly includes: a second receiving module 701 and a second sending module 702.

[0167] In an embodiment of the present application, the second receiving module 701 is used to receive a second emergency call request sent by a first network element, wherein the second emergency call request carries an identifier of a relay terminal; the second sending module 702 is used to send the identifier of the relay terminal to a fourth network element.

[0168] In one implementation, the second emergency call request carries an access type, and a value of the access type includes any one of the following:

[0169] 3GPP-NR-ProSe-L3UNR;

[0170] 3GPP-E-UTRAN-ProSe-UNR.

[0171] In one implementation, the method further includes: an acquisition module, configured to acquire the identifier of the relay terminal carried in the second emergency call request according to the value of the access type.

[0172] In one implementation, obtaining, according to the value of the access type, the identifier of the relay terminal carried in the second emergency call request includes:

[0173] Determining, according to a value of the access type, that the second emergency call request is triggered by a remote terminal accessed through the relay terminal;

[0174] Obtain the identifier of the relay terminal carried in the second emergency call request.

[0175] In one implementation, the identifier of the relay terminal is carried in a message header of the second emergency call request.

[0176] In one implementation, the message header includes one of the following:

[0177] Contact message header;

[0178] From the From message header;

[0179] Access network information P-Access-Network-Info message header.

[0180] Through the above-mentioned device provided in the embodiment of the present application, when an emergency call carrying the identifier of the relay terminal is received, the identifier of the relay terminal is sent to the fourth network element, so that the location information of the relay terminal can be obtained from the fourth network element, and the emergency call of the remote terminal is implemented according to the location information of the relay terminal.

[0181] The emergency call processing device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiment of the present application.

[0182] The emergency call processing device provided in the embodiment of the present application can achieve Figures 3 to 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0183] like Figure 8 As shown, an embodiment of the present application also provides a communication device 800, including a processor 801 and a memory 802, and the memory 802 stores programs or instructions that can be executed on the processor 801. For example, when the communication device 800 is a network side device, the program or instructions are executed by the processor 801 to implement the various steps of the above-mentioned emergency call processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0184] Specifically, the embodiment of the present application also provides a network side device. Fig. 9 As shown, the network side device 900 includes: a processor 901, a network interface 902 and a memory 903. The network interface 902 is, for example, a common public radio interface (CPRI).

[0185] Specifically, the network side device 900 of the embodiment of the present application further includes: an instruction or program stored in the memory 903 and executable on the processor 901, and the processor 901 calls the instruction or program in the memory 903 to execute Figure 6 or Figure 7 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0186] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned emergency call processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0187] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0188] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned emergency call processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0189] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0190] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned emergency call processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0191] The embodiment of the present application also provides an emergency call processing system, including a first network element and a second network element, wherein the first network element can be used to execute the above Figure 3 The steps of the emergency call processing method, the second network element can be used to perform the above Figure 4 The steps of the emergency call processing method.

[0192] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0193] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0194] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A method for processing an emergency call, characterized in that: include: The first network element receives a first emergency call request sent by a remote terminal; The first network element obtains an identifier of a relay terminal corresponding to the remote terminal; The first network element sends a second emergency call request to the second network element, wherein the second emergency call request carries an identifier of the relay terminal.

2. The method according to claim 1, characterized in that The first emergency call request carries an access type, and the value of the access type includes any one of the following: 3rd Generation Mobile Communications Partnership Project - New Radio - Short Range Services - Layer 3 User Equipment to Network Relay 3GPP-NR-ProSe-L3UNR; 3rd Generation Partnership Project Evolved Universal Terrestrial Radio Access Network - Short Range Services - User Equipment to Network Relay 3GPP-E-UTRAN-ProSe-UNR.

3. The method according to claim 1 or 2, characterized in that: The first emergency call request carries an access type, and the first network element obtains the identifier of the relay terminal, including: The first network element obtains the identifier of the relay terminal according to the value of the access type.

4. The method according to claim 3, characterized in that The first network element acquiring, according to the access type, an identifier of a relay terminal corresponding to the remote terminal, including: The first network element determines, according to a value of the access type, that the first emergency call request is sent by the remote terminal through the relay terminal; The first network element obtains the identifier of the relay terminal.

5. The method according to any one of claims 1 to 4, characterized in that: The first network element obtains the identifier of the relay terminal, including one of the following: The first network element obtains the identifier of the relay terminal locally; The first network element obtains the identifier of the relay terminal from the third network element.

6. The method according to claim 5, characterized in that The third network element includes: a policy control function PCF.

7. The method according to claim 1, characterized in that The second emergency call request carries the identifier of the relay terminal, including: The identifier of the relay terminal is carried in a message header of the second emergency call request.

8. The method according to claim 7, characterized in that The message header includes at least one of the following: Contact message header; From the From message header; Access network information P-Access-Network-Info message header.

9. The method according to claim 2, characterized in that: The first network element sending a second emergency call request to the second network element includes: The first network element sends the second emergency call request carrying the identifier of the relay terminal to the second network element according to the value of the access type.

10. The method according to any one of claims 1 to 8, characterized in that: The identifier of the relay terminal includes at least one of the following: The mobile station International Integrated Services Digital Network (ISDN) number of the relay terminal; The universal public user identity of the relay terminal; The international mobile subscriber identity code of the relay terminal; A permanent identifier of a user of the relay terminal.

11. The method according to any one of claims 1 to 10, characterized in that: The first network element includes a proxy call session control function P-CSCF, and the second network element includes an emergency session control function E-CSCF.

12. A method for processing an emergency call, characterized in that: include: The second network element receives a second emergency call request sent by the first network element, wherein the second emergency call request carries an identifier of the relay terminal; The second network element sends the identifier of the relay terminal to the fourth network element.

13. The method according to claim 12, characterized in that The second emergency call request carries an access type, and a value of the access type includes any one of the following: 3rd Generation Mobile Communications Partnership Project - New Radio - Short Range Services - Layer 3 User Equipment to Network Relay 3GPP-NR-ProSe-L3UNR; 3rd Generation Partnership Project Evolved Universal Terrestrial Radio Access Network - Short Range Services - User Equipment to Network Relay 3GPP-E-UTRAN-ProSe-UNR.

14. The method according to claim 13, characterized in that The method further comprises: The second network element obtains the identifier of the relay terminal carried in the second emergency call request according to the value of the access type.

15. The method according to claim 14, characterized in that The second network element obtains, according to the value of the access type, the identifier of the relay terminal carried in the second emergency call request, including: The second network element determines, according to the value of the access type, that the second emergency call request is triggered by a remote terminal accessed through the relay terminal; The second network element obtains the identifier of the relay terminal carried in the second emergency call request.

16. The method according to any one of claims 12 to 15, characterized in that The identifier of the relay terminal is carried in a message header of the second emergency call request.

17. The method according to claim 16, characterized in that The message header includes one of the following: Contact message header; From the From message header; Access network information P-Access-Network-Info message header.

18. The method according to any one of claims 12 to 17, characterized in that The first network element includes a proxy call session control function P-CSCF, the second network element includes an emergency session control function E-CSCF, and the fourth network element includes a location reference function LRF.

19. An emergency call processing device, characterized in that: include: A first receiving module, used to receive a first emergency call request sent by a remote terminal; An acquisition module, used to acquire an identifier of a relay terminal corresponding to the remote terminal; The first sending module is configured to send a second emergency call request to a second network element, wherein the second emergency call request carries an identifier of the relay terminal.

20. An emergency call processing device, characterized in that: include: A second receiving module is used to receive a second emergency call request sent by the first network element, wherein the second emergency call request carries an identifier of the relay terminal; The second sending module is used to send the identifier of the relay terminal to the fourth network element.

21. A network side device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for processing an emergency call as claimed in any one of claims 1 to 18 are implemented.

22. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the emergency call processing method according to any one of claims 1 to 18 are implemented.

Images