Call setup method, apparatus, related device, storage medium and computer program product

Abstract

This application discloses a call setup method, apparatus, terminal, core network, storage medium, and computer program product. The method includes: a terminal sending first information to a core network, the terminal accessing the network via an access network device deployed on a satellite, the core network being deployed on the ground, the first information including the terminal's geographical location information, and the first information being used at least to establish an emergency call; and sending a first message, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a call setup method, apparatus, related equipment, storage medium, and computer program product. Background Technology

[0002] In related technologies, when a user makes an emergency call to a user connected to a terrestrial network, the network side sequentially performs emergency registration, emergency protocol data unit (PDU) establishment, and emergency call establishment procedures to provide the user with emergency call services.

[0003] However, there is currently no effective solution for providing emergency call services to users who access the network via satellite. Summary of the Invention

[0004] To address the related technical issues, embodiments of this application provide a call setup method, apparatus, terminal, core network, storage medium, and computer program product.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides a call setup method applied to a terminal, wherein the terminal accesses a network through an access network device deployed on a satellite, and the method includes:

[0007] Send first information to the core network, which is deployed on the ground, the first information including the geographical location information of the terminal, and the first information is used at least to establish an emergency call;

[0008] Send a first message, which requests the core network to establish an emergency call for the terminal based on the first information.

[0009] In the above scheme, sending the first information to the core network includes:

[0010] A second message is sent to the core network, the second message being used to request registration for emergency calls, and the second message containing the first information.

[0011] In the above scheme, sending the first information to the core network includes:

[0012] Send a third message to the core network, the third message being used to request the establishment of an emergency PDU session, the third message including the first message;

[0013] The first message is sent to the core network based on the established emergency PDU session.

[0014] The method in the above scheme further includes:

[0015] Obtain the geographical location information of the terminal.

[0016] This application also provides a call setup method applied to a core network, the method comprising:

[0017] The terminal receives first information, which includes the geographical location information of the terminal. The first information is used at least to establish an emergency call. The terminal accesses the network through an access network device deployed on a satellite.

[0018] The access network device receives a fourth message, which is sent after receiving a first message from the terminal. The first message is used to request the core network to establish an emergency call for the terminal based on the first information. The fourth message contains second information, which is used to indicate that the terminal's access type includes satellite access.

[0019] Using the first and second information, an emergency call associated with satellite access is established.

[0020] In the above scheme, receiving the first information includes:

[0021] The terminal sends a second message, which requests registration for an emergency call and includes the first information.

[0022] Register the terminal for emergency calls.

[0023] In the above scheme, receiving the first information includes:

[0024] The terminal sends a third message, which is used to request the establishment of an emergency PDU session, and the third message contains the first information.

[0025] Establish an emergency PDU session; wherein, during the establishment of the emergency PDU, the geographical location information of the terminal is not verified.

[0026] In the above scheme, the method for establishing an emergency PDU session includes:

[0027] Determine the first Quality of Service (QoS) rule;

[0028] Based on the determined first QoS rule, an emergency PDU session dedicated bearer is established and associated with satellite access. The emergency PDU session dedicated bearer is used for signaling transmission.

[0029] In the above scheme, the method for establishing an emergency PDU session includes:

[0030] A first user plane function is determined, which is at least used to transmit user plane data of the terminal.

[0031] In the above scheme, the function of determining the first user plane includes:

[0032] The user plane functions deployed on the satellite are designated as the first user plane functions;

[0033] or,

[0034] Based on the geographical location information of the ground gateway station corresponding to the satellite, the first user plane function is determined.

[0035] In the above scheme, the method for establishing an emergency call associated with satellite access includes:

[0036] Determine the second QoS rule;

[0037] Based on the determined second QoS rules, an emergency call dedicated bearer is established and associated with satellite access. The emergency call dedicated bearer is used for media streaming transmission.

[0038] In the above scheme, the method for establishing an emergency call associated with satellite access includes:

[0039] Using the first information, a first Public Safety Answering Point (PSAP) is determined, which is used at least to respond to emergency calls from the terminal.

[0040] In the above scheme, determining the first PSAP using the first information includes:

[0041] Verify the received geographical location information of the terminal to obtain the verification result;

[0042] The first PSAP is determined using the verification result.

[0043] In the above scheme, the verification of the received geographical location information of the terminal includes:

[0044] The received geographical location information of the terminal is verified using the measurement results of the round-trip time (RTT) between the terminal and the access network device.

[0045] In the above scheme, if the verification result indicates that the location information of the received terminal has been successfully verified, the first PSAP is determined using the received geographical location information of the terminal.

[0046] or,

[0047] If the verification result indicates that the location information of the terminal received has failed to be verified, the geographical location information of the terminal is estimated; and the estimated geographical location information of the terminal is used to determine the first PSAP.

[0048] This application embodiment also provides a call setup device, installed in a terminal, the terminal accessing the network through access network equipment deployed on a satellite, including:

[0049] The sending unit is configured to send first information to the core network, the core network being deployed on the ground, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call; and to send a first message, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

[0050] This application embodiment also provides a call setup device, installed in the core network, including:

[0051] A receiving unit is configured to receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through an access network device deployed on a satellite; and to receive a fourth message sent by the access network device, the fourth message being sent by the access network device after receiving the first message sent by the terminal, the first message being used to request the core network to establish an emergency call for the terminal based on the first information, the fourth message including second information, the second information being used to indicate that the terminal's access type includes satellite access;

[0052] The establishment unit is used to establish an emergency call associated with satellite access using the first information and the second information.

[0053] This application embodiment also provides a terminal, which accesses a network through an access network device deployed on a satellite, including: a first processor and a first communication interface; wherein,

[0054] The first processor is configured to send first information to the core network via the first communication interface, the core network being deployed on the ground, the first information including the geographical location information of the terminal, and the first information being used at least to establish an emergency call; and to send a first message via the first communication interface, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

[0055] This application also provides a core network, including: a second processor and a second communication interface; wherein,

[0056] The second communication interface is used to receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through an access network device deployed on a satellite; and to receive a fourth message sent by the access network device, the fourth message being sent by the access network device after receiving the first message sent by the terminal, the first message being used to request the core network to establish an emergency call for the terminal based on the first information, the fourth message including second information, the second information being used to indicate that the terminal's access type includes satellite access;

[0057] The second processor is used to establish an emergency call associated with satellite access using the first information and the second information.

[0058] This application also provides a terminal, including: a first processor and a first memory for storing a computer program capable of running on the processor.

[0059] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the above-described terminal-side methods.

[0060] This application also provides a core network, including: a second processor and a second memory for storing computer programs capable of running on the processor.

[0061] Wherein, when the second processor is running the computer program, it executes the steps of any of the above-mentioned core network side methods.

[0062] This application embodiment also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the above-described terminal-side methods, or implements the steps of any of the above-described core-network-side methods.

[0063] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described terminal-side methods or the steps of any of the above-described core-network-side methods.

[0064] The call establishment method, apparatus, related devices, storage medium, and computer program products provided in this application embodiment include: a terminal sending first information to a core network; the terminal accessing the network through an access network device deployed on a satellite; the core network being deployed on the ground; the first information including the terminal's geographical location information; and the first information being used at least to establish an emergency call; sending a first message requesting the core network to establish an emergency call for the terminal based on the first information; simultaneously, the core network receiving the first information; receiving a fourth message sent by the access network device after receiving the first message from the terminal; the fourth message including second information indicating that the terminal's access type includes satellite access; and using the first and second information, establishing an emergency call associated with satellite access. The solution provided in this application involves a terminal accessing the network via a satellite-deployed access network device reporting its geographical location information to the core network and then initiating a request to establish an emergency call. The satellite-deployed access network device forwards the request and informs the core network that the terminal accesses the network via satellite. Upon receiving the request, the core network establishes an emergency call based on the terminal's geographical location and access status. This allows the core network to accurately determine the terminal's location and route the terminal's emergency call to a responder (such as PSAP) capable of providing emergency call services (e.g., emergency rescue) to the terminal's location, ensuring timely and accurate processing of the user's emergency call. Furthermore, the core network can determine the terminal's access method (i.e., satellite access). By pre-configuring dedicated QoS for the emergency call service of satellite-accessed terminals, the core network can establish a bearer that meets the requirements of satellite emergency call scenarios for emergency calls requested by satellite-accessed terminals. This allows for timely and prioritized resource allocation for satellite emergency call tasks, ensuring the quality of the voice stream and providing effective emergency call services. Attached Figure Description

[0065] Figure 1 This is a schematic diagram of a process for establishing an emergency call in related technologies;

[0066] Figure 2 This is a schematic diagram of a process for establishing an emergency PDU session in related technologies;

[0067] Figure 3 This is a schematic diagram of a process for establishing an emergency call in related technologies;

[0068] Figure 4 This is a flowchart illustrating a call setup method according to an embodiment of this application;

[0069] Figure 5This is a flowchart illustrating another call setup method according to an embodiment of this application;

[0070] Figure 6 This application example provides a schematic diagram of the structure of a satellite emergency call establishment system.

[0071] Figure 7 This is a schematic diagram illustrating the process of establishing an emergency call PDU session as an application example of this application;

[0072] Figure 8 This is a schematic diagram illustrating a process for establishing an emergency call, serving as an application example of this application.

[0073] Figure 9 This is a schematic diagram of a call setup device as an application example of this application;

[0074] Figure 10 This is a schematic diagram of another call setup device according to an embodiment of this application;

[0075] Figure 11 This is a schematic diagram of the terminal structure according to an embodiment of this application;

[0076] Figure 12 This is a schematic diagram of the core network structure of an embodiment of this application;

[0077] Figure 13 This is a schematic diagram of the call establishment system structure for an embodiment of this application. Detailed Implementation

[0078] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0079] Emergency call service is a call service provided based on the widespread availability of telephone services. In emergency call service, users (also understood as user equipment (UE) or mobile users) can initiate an emergency call using an emergency call number. Upon receiving the emergency call, the network connects it to the emergency service center corresponding to the emergency call number, which is the closest emergency service center to the user's base station. This emergency service center then provides emergency services to the user. Emergency call service takes priority over other services, and can be successfully made even when the user is in arrears or has their service suspended, reflecting the operator's social responsibility. The process of the network connecting a user-initiated emergency call to the emergency service center can also be understood as establishing an emergency call. Emergency service centers may include PSAP (Powered Service Access Point).

[0080] In 5G networks, the process of establishing an emergency call includes three sub-processes: emergency registration, emergency PDU session establishment, and emergency call establishment. The emergency registration sub-process includes the following steps:

[0081] Step 1: The UE sends a registration message to the Proxy Call Session Control Function (P-CSCF) of the Internet Protocol Multimedia Subsystem (IMS, which can also be understood as the network entry point of IMS); wherein, the registration message is used to request emergency registration;

[0082] Specifically, when the Uniform Resource Identifier (URI) parameter of the Contact header field (which can also be understood as a field) in the registration message carries the "SOS" identifier, the registration message is used to request emergency registration (which can also be understood as indicating that the registration message is used to request emergency registration).

[0083] Step 2: After receiving the registration message, the P-CSCF performs emergency registration for the UE based on the registration message.

[0084] After emergency registration is completed, such as Figure 1 As shown, emergency PDU session establishment and emergency call sub-process establishment can be performed, specifically including the following steps:

[0085] Step 101: The UE sends an emergency PDU session request (or initiates an emergency PDU session request) to the Access and Mobility Management Function (AMF) to request the establishment of an emergency PDU session; After receiving the emergency PDU session request, the AMF identifies that the request is associated with an emergency call, and based on the emergency service policy, skips the user authentication and subscription verification process and prioritizes the processing of the request, that is, prioritizes the establishment of the emergency PDU session corresponding to the request, so as to speed up the processing of emergency calls;

[0086] Specifically, such as Figure 2 As shown, the process of establishing an emergency PDU session may include the following steps:

[0087] Step 201: The UE sends a PDU Session Establishment Request message to the base station via Non-Access Stratum signaling. The PDU Session Establishment Request message carries request type information, which indicates "Emergency Request".

[0088] Step 202: After receiving the PDU session establishment request, the base station forwards the PDU session establishment request to the AMF;

[0089] Step 203: After receiving the PDU session establishment request, the AMF confirms the user's location and obtains the confirmation result. It then uses the confirmation result to determine whether to process the PDU session establishment request, such as whether to select the corresponding session management function (SMF) for the PDU session establishment request based on the local emergency configuration data.

[0090] Step 204: After the AMF determines to process the PDU session establishment request and selects the corresponding SMF, it constructs a Create Session Management Context Request (NSMF_PDUSession_CreateSMContext Request) message and sends the constructed Create Session Management Context Request message to the selected SMF.

[0091] Step 205: After receiving the Create Session Management Context Request message, SMF creates a session management context and constructs a Create Session Management Context Response message (which can be expressed as Nsmf_PDUSession_CreateSMContextResponse in English), and then sends the constructed Create Session Management Context Response message to AMF;

[0092] Step 206: The SMF selects the Policy Control Function (PCF) to serve this emergency PDU session;

[0093] Step 207: The SMF sends a Session Management Policy Association Establishment (SMPolicyAssociationEstablishment) message to the selected PCF. This message includes the request type information. Then, the PCF uses the received SMPolicyAssociationEstablishment message and local configuration data to generate corresponding session rules, policy and charging control (PCC) rules for the UE, and sends the generated session rules and PCC rules to the SMF. The session rules and PCC rules include: session management policy, emergency QoS policy, and charging policy.

[0094] Step 208: The SMF uses the request type information, UE location information, etc. contained in the Create Session Management Context Request message to select the User Plane Function (UPF) corresponding to the emergency PDU session;

[0095] Step 209: The SMF sends an N4 session establishment request message to the selected UPF, wherein the N4 session is associated with the emergency PDU session;

[0096] Step 210: After receiving the N4 session establishment request message, the UPF sends an N4 session establishment response message to the SMF;

[0097] Step 211: The SMF constructs an N1N2 message transfer message (which can be expressed as Namf_Communication_N1N2MessageTransfer) and sends the constructed N1N2 message transfer message to the AMF so that the AMF can transmit N1 and N2 messages. The N1 message contains information elements (IEs) such as: PDU session establishment acceptance information, emergency call QoS data, slice representation, data network name (DNN), P-CSCF address, and assigned IP address. The N2 message contains IEs such as: PDU session identifier (e.g., PDU session ID), core network (CN) tunnel information (e.g., UPF tunnel address information), and slice identifier information.

[0098] Step 212: After receiving the N1N2 message transmission message, the AMF constructs an N2PDU session request message and sends the constructed N2PDU session request message to the base station;

[0099] Step 213: After receiving the N2PDU session request message, the base station constructs a PDU session establishment acceptance message and sends it to the UE, and allocates the corresponding PDU session resources.

[0100] Step 214: After the base station completes the PDU session resource allocation, it constructs an N2PDU session response message and sends the constructed N2PDU session response message to the AMF; wherein, the N2PDU session response message carries the PDU session identifier, the operation result cause code, N2 session management information, access network (AN) tunnel information (such as base station tunnel address information), etc.

[0101] Step 215: After receiving the N2PDU session response message, the AMF sends an Update Session Management Context Request (which can be expressed as Nsmf_PDUSession_UpdateSMContextRequest) message to the SMF; wherein, the Update Session Management Context Request message carries N2 session management information, session management context identifier (such as session management context ID), request type, etc.

[0102] Step 216: After receiving the Update Session Management Context Request message, the SMF constructs an N4 Session Modification Request message and sends it to the UPF. The N4 Session Modification Request message includes AN tunnel information (such as base station tunnel address information), PDU session identifier, relevant information of the Forwarding Action Rule (FAR), relevant information of the Packet Detection Rule (PDR), UPF address, and other IEs.

[0103] Step 217: After receiving the N4 session modification request message, the UPF sends an N4 session modification response message to the SMF; wherein, the N4 session modification response message carries relevant information for establishing local rules such as FAR and PDR;

[0104] Step 218: After receiving the N4 session modification response message, the SMF sends an update session management context response (which can be expressed as Nsmf_PDUSession_UpdateSMContextResponse) message to the AMF to inform the AMF that the session context update is complete.

[0105] In practical applications, after executing steps 201 to 208, the establishment of the emergency PDU session is completed. Then, steps 102 to 104 can be executed to establish an emergency call (which can also be understood as establishing an emergency call conversation).

[0106] Step 102: The UE sends an emergency call session request to the P-CSCF (specifically, this can be done via an INVITE message); upon receiving the emergency call session request, the P-CSCF determines (or identifies) the requested call as an emergency call based on the called number carried in the request. Then, the P-CSCF sends a policy request to the PCF via the N5 interface. This policy request is used to request the establishment of a dedicated bearer for the emergency call; upon receiving the policy request, the PCF performs a service check on the emergency call corresponding to the policy request and generates the QoS rules (or emergency QoS rules) for the emergency call. Then, it sends the generated QoS rules to the PCF via the N7 interface. The S rule is sent to the SMF; after receiving the QoS rule, the SMF distributes the QoS rule to the UPF through the N4 interface so that the UPF can allocate a dedicated bearer for emergency calls (which can also be understood as a private bearer); after the UPF establishes the dedicated bearer for emergency calls according to the QoS rule, it sends a response message to the PCF through the SMF to confirm the establishment of the dedicated bearer. The response message may contain the UE's geographical location information; after receiving the response message, the PCF returns a policy response message to the P-CSCF indicating the successful establishment of the dedicated bearer for emergency calls. The policy response message contains the UE's geographical location information; the P-CSCF sends the UE's geographical location information to the Emergency Call Session Control Function (E-CSCF) and / or the PSAP; specifically, the E-CSCF can obtain the UE's geographical location information sent by the P-CSCF through the Mw interface; the PSAP can use the obtained UE's geographical location information for emergency rescue positioning.

[0107] Step 103: The P-CSCF routes the emergency call session request (which can also be understood as an emergency call request or emergency call) to the E-CSCF; after receiving the emergency call session request, the E-CSCF returns a 100 Trying message to the P-CSCF to confirm that the emergency call session request has been received. At the same time, the E-CSCF parses the called number corresponding to the emergency call session request; then, the E-CSCF uses the parsed called number and the UE's geographical location information sent by the P-CSCF to determine the appropriate PSAP and routes the emergency call session request to the determined PSAP.

[0108] Step 104: After receiving the emergency call session request, the PSAP establishes a communication connection with the UE to establish an emergency call between the UE and the PSAP.

[0109] In practical applications, steps 102 to 104 can also be understood as the emergency call setup process in a 5G network. Meanwhile, in fourth-generation mobile communication (4G) networks, such as... Figure 3 As shown, the emergency call setup process may include the following steps:

[0110] Step 301: The UE initiates an emergency call session request to the P-CSCF via an INVITE message on the Emergency Call Access Point Name (APN); wherein, the request URI header field in the INVITE message includes: the Uniform Resource Name (URN) corresponding to the emergency call service;

[0111] Step 302: After receiving the emergency call session request, the P-CSCF returns 100Trying to the UE to inform the UE that the request has been successfully received;

[0112] Step 303: The P-CSCF parses the emergency call session request to obtain the called number corresponding to the emergency call session request; using the called number, it determines that the call to be established is an emergency call, and then sends an Authorization and Accounting Request (AAR) message to the Policy and Charging Rules Function (PCRF) through the Diameter Routing Agent (DRA) to request the establishment of an emergency call dedicated bearer; wherein, the AAR message contains an attribute-value pair (AVP) consisting of a service and a URN, and the AVP is used to indicate an emergency call;

[0113] Step 304: After receiving the AAR message, the PCRF performs a service check on the emergency call corresponding to the AAR message, binds the emergency call session to the corresponding IP-Connectivity Access Network (IP-CAN) session, and generates QoS rules for the emergency call. The QoS rules include Allocation and Retention Priority (ARP), and the ARP for the emergency call is higher than that for a normal call. Then, the PCRF sends the generated QoS rules to the Packet Data Network Gateway (P-GW) via the DRA through a Re-Authorization Request (RAR) message.

[0114] Step 305: After receiving the QoS rules, the P-GW returns a Re-Authorization Answer (RAA) message to the PCRF, and then establishes a dedicated bearer for the emergency call (which can also be understood as an emergency call voice dedicated bearer).

[0115] Step 306: After receiving the RAA message, the PCRF returns an Authorization and Accounting Answer (AAA) message to the P-CSCF, indicating that the establishment of the dedicated bearer for emergency calls has been successful. The AAA message contains user location information, which may specifically include a Tracking Area Identity (TAI) and an eNB identifier, which is taken from the Envolved Universal Mobile Telecommunications System Terrestrial Radio Access Network Cell Global Identifier (ECGI).

[0116] Step 307: After establishing the dedicated bearer, the P-CSCF routes the emergency call session request to the E-CSCF;

[0117] Step 308: After receiving the emergency call session request, the E-CSCF returns 100 Trying to the P-CSCF to inform the P-CSCF that the request has been successfully received.

[0118] Step 309: The E-CSCF performs the following processes in sequence:

[0119] a) The E-CSCF anchors the emergency call session request to the Emergency Access Transfer Function (EATF). The EATF records the calling number in the P-Asserted-Identity header field of the emergency call session request, as well as the instance identifier (which can be expressed as Instance-id) parameter in the Contact header field. The calling number and instance identifier parameters can be used to match calls with handover when an emergency call handover request is received.

[0120] b) The E-CSCF parses the called number corresponding to the emergency call session request and the UE's geographical location information in the P-Access-Network-Info header field; then, the E-CSCF determines the appropriate PSAP address information based on the called number, the UE's geographical location information, and the local routing table, and routes the emergency call session request to that PSAP.

[0121] Step 310: After receiving the emergency call session request, PSAP returns a 100 Trying message to E-CSCF;

[0122] Step 311: The device on the PSAP side (such as a telephone on the PSAP) starts ringing and sends a 180 Ringing message to the UE via E-CSCF and P-CSCF to inform the UE that the called device is ringing;

[0123] Step 312: After the device on the PSAP side is connected, it sends a 200 OK message to the UE through E-CSCF and P-CSCF to inform the UE that the emergency call has been successfully established;

[0124] Step 313: The UE sends an ACK message to the PSAP via the P-CSCF and E-CSCF to confirm the establishment of the emergency call.

[0125] However, with technological advancements, in scenarios where base stations are deployed on satellites (also known as base station onboarding), and users access the network through satellite-deployed base stations (also known as satellite-based base stations), the emergency call establishment schemes in related technologies have the following problems:

[0126] 1) Low positioning accuracy. Specifically, in related technologies, PASPs are typically configured for each Tracking Area (TA). Therefore, when establishing an emergency call, the network side can determine the user's location based on the Tracking Area (TA) and route the user's emergency call request to the PSAP corresponding to that TA, enabling a rapid response to the emergency call. When a user accesses a traditional terrestrial network, the range of the cell the user accesses is usually smaller than the range of a single TA. That is, a single TA can contain one or more (or at least one) cells. Therefore, the network side can determine the user's TA based on the cell the user accesses and accurately route the user's emergency call request to the PSAP corresponding to that TA. However, in scenarios where users access the network via satellite, the coverage and characteristics of satellite networks differ from those of terrestrial networks. A single cell in a satellite network may cover the range of multiple TAs. In this case, the network side has difficulty determining the user's TA based on the cell the user accesses, making it difficult to obtain the user's precise location information. This may result in the network routing the user's emergency call request to a PSAP that does not have the capability to handle emergency events in the user's area, leading to response delays and / or incorrect handling.

[0127] 2) QoS is difficult to guarantee in satellite access scenarios. Specifically, when a user initiates an emergency call in a traditional terrestrial network, a dedicated bearer for an emergency PDU session for IMS signaling transmission and a dedicated bearer for emergency call data transmission are established for the user based on the configured 5G QoS Identifier (5QI). However, in scenarios where users access the network via satellite, transmission latency is high and bandwidth is limited. The 5QI configured for emergency calls on terrestrial networks may be insufficient to support emergency call services in satellite access scenarios. This could lead to the network struggling to distinguish the priority of emergency calls from regular calls, thus failing to guarantee that satellite emergency calls (i.e., emergency calls in satellite access scenarios) can obtain the necessary network resources in a timely manner. For example, in situations of network congestion or resource scarcity, satellite emergency calls may be delayed or even fail to initiate. Furthermore, the lack of a dedicated 5QI for satellite emergency calls may make it difficult for the network to prioritize satellite emergency calls when allocating resources, affecting the speed and stability of establishing emergency call connections. Additionally, emergency calls typically require high-quality voice transmission. Without a dedicated 5QI for satellite emergency calls, it may be difficult to establish a dedicated emergency call bearer that meets the QoS requirements of satellite emergency calls, resulting in compromised voice stream quality, such as poor voice quality and high call drop rates, thereby affecting the effectiveness of emergency rescue.

[0128] As can be seen from the above description, there is an urgent need for a solution that can reliably and accurately establish emergency calls for scenarios where users access the network via satellite.

[0129] Based on this, in various embodiments of this application, a terminal accessing the network through an access network device deployed on a satellite reports its geographical location information to the core network, then requests the establishment of an emergency call from the core network, informing the core network that the terminal accesses via satellite. After receiving the information reported by the terminal, the core network establishes an emergency call based on this information. In this way, on the one hand, the core network can accurately know the location of the terminal, and thus can route the terminal's emergency call to a responder (such as PSAP) that can provide emergency call services (such as emergency rescue) to the terminal's location, so as to ensure that the user's emergency call can be processed in a timely and correct manner. On the other hand, the core network can determine the access method (i.e., satellite access) of the terminal requesting to establish an emergency call. With a dedicated QoS configured in advance for the emergency call service of the satellite access terminal, the core network can use the configured QoS to establish a bearer that meets the satellite emergency call scenario for the emergency call requested by the terminal accessing via satellite, thereby allocating resources for the satellite emergency call task in a timely and prioritized manner, ensuring the quality of the voice stream, and thus providing effective emergency call services.

[0130] This application provides a call setup method applied to a terminal, wherein the terminal accesses the network through access network equipment deployed on a satellite, such as... Figure 4 As shown, the method includes:

[0131] Step 401: Send first information to the core network, the core network being deployed on the ground, the first information containing the geographical location information of the terminal, the first information being used at least to establish an emergency call;

[0132] Step 402: Send a first message, which requests the core network to establish an emergency call for the terminal based on the first information.

[0133] In practical applications, the terminal may be referred to as a UE, terminal device, device, or user, etc., and this application embodiment does not limit this. The access network device may specifically be a base station, such as a gNB. This application embodiment does not limit the name of the network device, as long as it performs its function. The core network specifically refers to core network equipment. In practical applications, the core network may include multiple network elements, such as AMF, UPF, SMF, P-CSCF, etc., and this application embodiment does not limit this.

[0134] In practical applications, the terminal accesses the network through access network equipment deployed on the satellite, which can also be understood as the terminal accessing a non-terrestrial network (NTN). The satellite can operate in a regenerative scenario or a transparent transmission scenario, which is not limited in this embodiment. In the above scenario, the information sent by the terminal needs to be transmitted to the core network through the access network equipment deployed on the satellite, and at the same time, the information sent from the core network to the terminal also needs to be transmitted through the access network equipment deployed on the satellite.

[0135] In practical applications, when the terminal dials an emergency number to make an emergency call, the terminal first initiates an emergency registration request. After emergency registration is completed, the terminal initiates an emergency PDU establishment request. After the emergency PDU is established, the terminal initiates an emergency call session request. Upon receiving the emergency call session request, the core network needs to route the terminal's emergency call session request to a responder (such as PSAP) capable of providing emergency call services (which can also be understood as emergency response, such as emergency rescue) for the terminal. The responder then handles the user's emergency call. Since responders typically provide emergency call services for different geographical areas, the core network needs to accurately determine the terminal's geographical location information to accurately determine the most suitable responder to provide emergency call services to the terminal (e.g., the one geographically closest to the terminal), ensuring that the user's emergency call is handled promptly and correctly.

[0136] In practical applications, the core network typically determines the location information of a terminal through the cell it accesses. However, when the terminal accesses the network through an access network device deployed on a satellite, the cell it accesses is a satellite cell (i.e., the cell corresponding to the satellite). Since satellite cells have a large coverage area and may involve multiple TAs (such as multiple countries or regions), it may lead to a situation where the responder determined by the core network is unable to provide emergency call services to the terminal.

[0137] For example, suppose the satellite cell accessed by the terminal covers three TAs, namely TA1, TA2 and TA3, and the terminal is located within TA1. In this case, the core network may have difficulty determining which TA the terminal is located in based on the location information of the satellite cell accessed by the terminal. Therefore, the emergency call session request initiated by the terminal may be routed to the responder corresponding to TA2 or TA3. When the responder cannot provide emergency call service for TA1, it will lead to response delay and error processing.

[0138] Based on this, in step 401, the terminal actively reports first information containing the terminal's geographical location information to the core network, so that the core network can know the terminal's first location information, thereby accurately establishing an emergency call (i.e., routing the emergency call session request to the most suitable responder). Here, the first information can also be called geographical location information; this application embodiment does not limit the name of the first information. The terminal can know its own geographical location information in advance; that is, before step 401, the method may further include: obtaining the terminal's geographical location information.

[0139] Specifically, the method by which the terminal obtains its own geographical location information can be set according to actual needs. For example, it can obtain its own geographical location information through the Global Navigation Satellite System (GNSS) receiving module carried by the terminal; pre-set the geographical location information of the terminal; or determine the terminal's own geographical location information through ephemeris information, historical positioning information, etc. This application embodiment does not limit this.

[0140] In practical applications, the terminal can send the first information to the core network during the process of requesting emergency registration. Specifically, in one embodiment, the implementation of step 401 may include:

[0141] A second message is sent to the core network, the second message being used to request registration for emergency calls, and the second message containing the first information.

[0142] In practical applications, the second message can also be understood as an emergency registration request message. This embodiment does not limit the name of the second message. The method of setting the first information in the second message can be selected according to actual needs, such as setting the first information in the header of the second message. This embodiment does not limit this approach.

[0143] Of course, the terminal can also send the first information to the core network during the establishment of an emergency PDU session. Specifically, in one embodiment, the specific implementation of step 401 may include:

[0144] A third message is sent to the core network, the third message being used to request the establishment of an emergency PDU session, the third message including the first message.

[0145] In practical applications, the third message can also be understood as a PDU session establishment request message. This application embodiment does not limit the name of the third message. The method of setting the first information in the third message can be selected according to actual needs, such as setting the first information in the header of the third message. This application embodiment does not limit this.

[0146] After establishing an emergency PDU session and sending the first information to the core network, in step 402, the terminal sends a first message to request the core network to establish an emergency call for the terminal. This first message can also be called an emergency call session request message (e.g., an INVITE message), and the name of the first message is not limited in this embodiment.

[0147] In practical applications, third information can be set in the first message, meaning the first message contains third information. This third information indicates that the requested call is an emergency call. Specifically, the third information may be the URN corresponding to the emergency call service. This application embodiment does not limit the name or specific implementation of the third information. Specifically, the method of setting the third information in the first message can be selected according to actual needs, such as setting the third information in the header of the first message (specifically, the Request-URI header field in the INVITE message), etc. This application embodiment does not limit this approach.

[0148] Accordingly, embodiments of this application also provide a call establishment method, applied to the core network, such as... Figure 5 As shown, the method includes:

[0149] Step 501: Receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through access network equipment deployed on the satellite;

[0150] Step 502: Receive a fourth message sent by the access network device. The fourth message is sent by the access network device after receiving the first message sent by the terminal. The first message is used to request the core network to establish an emergency call for the terminal based on the first information. The fourth message contains second information, which is used to indicate that the terminal's access type includes satellite access.

[0151] Step 503: Using the first information and the second information, establish an emergency call associated with satellite access.

[0152] In practical applications, when requesting emergency registration, the terminal can send first information containing its own geographical location to the core network. Accordingly, in one embodiment, step 501 may include:

[0153] The terminal sends a second message, which requests registration for emergency calls and includes the first information.

[0154] In practical applications, after receiving the second message, the core network (specifically, it may include the P-CSCF) triggers an emergency registration process. Specifically, in one embodiment, the method may further include:

[0155] Register the terminal for emergency calls.

[0156] Of course, the terminal may also send the first information to the core network when establishing an emergency PDU session. Accordingly, in one embodiment, the specific implementation of step 501 may include:

[0157] The terminal sends a third message, which is used to request the establishment of an emergency PDU session, and the third message contains the first information.

[0158] In practical applications, after the core network (specifically, it may include the AMF) receives the third message, it triggers the process of establishing an emergency PDU session. Specifically, in one embodiment, the method may further include:

[0159] Establish an emergency PDU session; wherein, during the establishment of the emergency PDU, the geographical location information of the terminal is not verified.

[0160] In practical application, the process of the terminal sending the third message to the core network includes: the terminal sending the third message to the access network equipment deployed on the satellite; and the access network equipment forwarding the third message to the core network.

[0161] In order to identify that the terminal corresponding to the third message accesses the network via satellite, the access network device may set fourth information in the third message. The fourth information is used to indicate that the access type of the terminal includes satellite access. The fourth information may also be called Access Type information. This application embodiment does not limit the name and specific implementation of the fourth information. After the core network receives the third message, it can determine based on the fourth information that the PDU establishment request was initiated by the terminal with satellite access.

[0162] Because of the different Public Land Mobile Network (PLMN) licenses in cross-border access scenarios, when the core network receives a PDU establishment request initiated by a satellite access terminal, the core network usually needs to verify (or understand as) the terminal's location information to avoid the establishment of illegal PDU sessions. However, verifying the terminal's location information may lead to increased processing latency, which is not conducive to achieving efficient response to emergency call services.

[0163] Therefore, in practical applications, the third message may also include fifth information. This fifth information indicates an emergency call, specifically that the PDU session is an emergency PDU session. The fifth information can also be understood as a request type. This application embodiment does not limit the name of the fifth information. Thus, after receiving the third message, the core network can determine that the session is an emergency PDU session based on the fifth information and decide not to verify the terminal's geographical location information, thereby reducing processing latency and improving response efficiency.

[0164] In related technologies, the QoS (specifically identified by 5QI) configured by the network for establishing a dedicated bearer for emergency PDU sessions is usually only applicable to users in traditional terrestrial networks. Therefore, when a user accessing via satellite initiates an emergency call, if the network side establishes a dedicated bearer for the emergency PDU session based on the QoS configured in related technologies, it may be difficult for the network side to distinguish the priority of emergency calls from that of ordinary calls. This would result in the satellite emergency call service (i.e., emergency calls in satellite access scenarios) being unable to obtain the necessary network resources in a timely manner, thereby affecting the speed and stability of establishing an emergency call connection.

[0165] Based on this, the core network (specifically, it may include PCF or PCRF) can configure dedicated QoS rules (or QoS policies) for PDU session requests initiated by satellite-accessed terminals, as well as the corresponding 5QI. Thus, when establishing an emergency PDU session in a satellite access scenario, the core network can establish a dedicated bearer for the emergency PDU session based on the dedicated QoS rules, ensuring that the established dedicated emergency call bearer can meet the signaling transmission requirements of satellite emergency call services.

[0166] Based on this, in one embodiment, the method may further include the following during the establishment of an emergency PDU session:

[0167] Determine the first QoS rule;

[0168] Based on the determined first QoS rule, an emergency PDU session dedicated bearer is established and associated with satellite access. The emergency PDU session dedicated bearer is used for signaling transmission.

[0169] In practical applications, establishing a dedicated bearer for emergency PDU sessions associated with satellite access based on the first QoS rule can specifically include: the PCF issuing the first QoS rule to the SMF, and then the SMF mapping the first QoS rule to the emergency PDU session associated with satellite access; or, determining that the QoS flow carried on the dedicated bearer for emergency PDU sessions associated with satellite access satisfies the first QoS rule.

[0170] When establishing an emergency PDU session in a satellite access scenario, the core network (specifically, it may include an SMF) selects an appropriate User Plane Function (UPF) to process the user plane data of the terminal. In other words, in one embodiment, the method for establishing an emergency PDU session may include:

[0171] A first user plane function is determined, which is at least used to transmit user plane data of the terminal.

[0172] Specifically, in one embodiment where the satellite is equipped with user plane functions, the core network can use the user plane functions deployed on the satellite as the first user plane function. The first user plane function may include a UPF (User Plane Function), and this embodiment does not limit this. It should be noted that in this embodiment, the first user plane function may be referred to as a user plane function entity (the first user plane function is called the first user plane function body), a communication node (the first user plane function is called the first user plane communication node), or a network element (the first user plane function is called the first user plane network element), etc., and this embodiment does not limit this.

[0173] Of course, in the absence of user plane functionality deployed on the satellite, in one embodiment, the core network can determine the first user plane functionality based on the geographical location information of the ground gateway station corresponding to the satellite. Specifically, the core network can select the user plane functionality geographically closest to the ground gateway station as the first user plane functionality.

[0174] After establishing an emergency PDU session, the terminal can send a first message to request the establishment of an emergency call. Then, after receiving the first message, the access network device deployed on the satellite sends a fourth message to the core network to request the core network to establish an emergency call for the terminal. The fourth message includes second information to inform the core network that the terminal's access method is satellite access. Accordingly, in step 502, the core network receives the fourth message. The second information can also be called access type information; this application embodiment does not limit the name of the second information.

[0175] Upon receiving the fourth message, the core network can determine the second information from the fourth message; then, in step 503, the core network uses the first and second information to establish an emergency call associated with satellite access.

[0176] In related technologies, the QoS (specifically identified by 5QI) configured by the network for establishing a dedicated bearer for emergency calls is usually only applicable to users in traditional terrestrial networks. Therefore, when a user accessing the network via satellite initiates an emergency call, if the network side establishes a dedicated bearer for emergency calls based on the QoS configured in related technologies, there may be a problem of poor voice stream quality for establishing the emergency call, which may affect the effectiveness of emergency rescue.

[0177] Based on this, the core network (specifically, it may include PCF or PCRF) can configure dedicated QoS rules and corresponding 5QI for emergency call establishment requests initiated by satellite-accessed terminals. Thus, when establishing an emergency call in a satellite access scenario, the core network can establish a dedicated emergency call bearer based on these dedicated QoS rules to ensure that the established dedicated emergency call bearer can meet the media stream transmission (or media transmission) requirements of the satellite emergency call service.

[0178] Based on this, in one embodiment, the method includes the following steps during the process of establishing an emergency call associated with satellite access:

[0179] Determine the second QoS rule;

[0180] Based on the determined second QoS rules, an emergency call dedicated bearer is established and associated with satellite access. The emergency call dedicated bearer is used for media streaming transmission.

[0181] In practical applications, when the core network establishes an emergency call associated with satellite access, it routes the emergency call to a responder (such as PSAP) whose geographical location information matches that of the terminal. In other words, in one embodiment, the method for establishing an emergency call associated with satellite access may include:

[0182] Using the first information, a first PSAP is determined, which is at least used to respond to an emergency call from the terminal.

[0183] In practical applications, in order to ensure that the first PSAP determined based on the terminal's location information can provide emergency call services to the terminal, the core network can verify the terminal's location information.

[0184] Based on this, in one embodiment, determining the first PSAP using the first information includes:

[0185] Verify the received geographical location information of the terminal to obtain the verification result;

[0186] The first PSAP is determined using the verification result.

[0187] Specifically, the core network can trigger a location information verification process for the terminal. This process includes: the core network measuring the round-trip time (RTT) between itself (specifically, the AMF) and the access network device, and verifying the location information of the terminal contained in the first information based on the measurement results. In other words, in one embodiment, the core network uses the measurement results of the RTT between itself and the access network device to verify the received location information of the terminal.

[0188] More specifically, the core network can use the round-trip time measurement results to determine the service area (which can also be understood as the geographical area range) of the satellite. If the terminal's geographical location information belongs to the determined service area, a verification result indicating successful verification of the received terminal's location information (i.e., the terminal's location information contained in the first information) is obtained. In this case, in one embodiment, the core network can consider the terminal's location information contained in the first information reliable and determine the first PSAP using the received terminal's geographical location information. If the terminal's geographical location information does not belong to the determined service area, a verification result indicating failed verification of the received terminal's location information (i.e., the terminal's location information contained in the first information) is obtained. In this case, in one embodiment, the core network can estimate the terminal's geographical location information and determine the first PSAP using the estimated terminal's geographical location information. The method by which the core network estimates the terminal's geographical location information can be set according to actual needs, such as using the terminal's IP address or other information to estimate the terminal's geographical location information. This application embodiment does not limit this.

[0189] After the first PSAP is determined, the core network can route the emergency call corresponding to the terminal to the first PSAP, thereby completing the establishment of an emergency call between the terminal and the first PSAP.

[0190] The call setup method provided in this application embodiment includes: a terminal sending first information to a core network; the terminal accessing the network through an access network device deployed on a satellite; the core network being deployed on the ground; the first information including the terminal's geographical location information; and the first information being used at least to establish an emergency call; sending a first message requesting the core network to establish an emergency call for the terminal based on the first information; simultaneously, the core network receiving the first information; receiving a fourth message sent by the access network device after receiving the first message from the terminal; the fourth message including second information indicating that the terminal's access type includes satellite access; and using the first and second information, establishing an emergency call associated with satellite access. The solution provided in this application involves a terminal accessing the network via a satellite-deployed access network device reporting its geographical location information to the core network and then initiating a request to establish an emergency call. The satellite-deployed access network device forwards the request and informs the core network that the terminal accesses the network via satellite. Upon receiving the request, the core network establishes an emergency call based on the terminal's geographical location and access status. This allows the core network to accurately determine the terminal's location and route the terminal's emergency call to a responder (such as PSAP) capable of providing emergency call services (e.g., emergency rescue) to the terminal's location, ensuring timely and accurate processing of the user's emergency call. Furthermore, the core network can determine the terminal's access method (i.e., satellite access). By pre-configuring dedicated QoS for the emergency call service of satellite-accessed terminals, the core network can establish a bearer that meets the requirements of satellite emergency call scenarios for emergency calls requested by satellite-accessed terminals. This allows for timely and prioritized resource allocation for satellite emergency call tasks, ensuring the quality of the voice stream and providing effective emergency call services.

[0191] The following section provides a more detailed description of this application with reference to application examples.

[0192] This application provides an application example of a satellite emergency call establishment system, such as... Figure 6As shown, the system includes: a calling UE (hereinafter referred to as UE, i.e., the aforementioned terminal), a satellite, a ground gateway station (also understood as a ground station), a core network, a PSAP (or emergency call center), and a location retrieval function (LRF); wherein, the satellite is equipped with base stations (i.e., the aforementioned access network equipment), and the satellite may also be equipped with a UPF and / or a session border controller (SBC); the core network may include AMF, SMF, UPF, PCF, SBC, P-CSCF (… Figure 6 (Not shown in the image), E-CSCF, Interrogation CSCF (I-CSCF), Serving CSCF (S-CSCF), Unified Data Management (UDM), Home Subscriber Server (HSS), etc.

[0193] Based on the above system, this application proposes a satellite emergency call establishment method, including an emergency registration process, an emergency call PDU session establishment process, and an emergency call establishment process. The emergency registration process includes the following steps:

[0194] Step 1: When a UE accessing via satellite dials an emergency number to make an emergency call, it sends an emergency registration request message (i.e., the second message mentioned above) to the base station; wherein, the URI parameter of the Contact header field in the emergency registration request message contains an "SOS" identifier, which is used to indicate emergency registration, and the emergency registration request message may also contain the geographical location information of the UE; the UE can obtain its current geographical location information through the GNSS receiving module;

[0195] Step 2: The base station sends the emergency registration request message to the core network through the ground gateway station;

[0196] Step 3: The core network performs emergency registration according to the emergency registration process in the relevant technology.

[0197] After completing the emergency registration, the emergency call PDU session establishment process is executed, such as... Figure 7 As shown, the emergency call PDU session establishment process includes the following steps:

[0198] Step 701: The UE sends a NAS signaling PDU session establishment request message (i.e., the third message mentioned above) to the base station; the PDU session establishment request message includes the request type and the UE's geographical location information (which can also be understood as the user's geographical location information), and the request type indicates "Emergency Request" (i.e., indicating the establishment of a PDU session corresponding to an emergency call);

[0199] Step 702: After receiving the PDU session establishment request message, the base station forwards the PDU session establishment request message to the ground gateway station through the feeder link according to the ground gateway station address recorded locally;

[0200] Specifically, the base station sends the PDU session establishment request message to the ground gateway station via an uplink NAS transmission (UL NASTRANSPORT) message on the N2 interface. In other words, the base station sends an uplink NAS transmission message to the ground gateway station, and this uplink NAS transmission message contains the PDU session establishment request message. The uplink NAS transmission message may also contain one or more of the following: PDU session identifier (e.g., PDU session ID), request type information (also understood as request type parameters), and access type information (also understood as access type parameters). When the access type indicates one or more of New Radio (NR) - Low Earth Orbit (LEO), NR - Medium Earth Orbit (MEO), and NR - Geostationary Earth Orbit (GEO), the access type is satellite access.

[0201] Step 703: The ground gateway forwards the received PDU session establishment request message to the AMF;

[0202] Step 704: The AMF determines, based on the request type information and access type information contained in the received PDU session establishment request message, that the PDU session establishment request is for requesting the establishment of an emergency PDU session for satellite access; then, without performing UE location confirmation, it directly receives the PDU session establishment request and selects the SMF corresponding to the PDU session establishment request based on local configuration data.

[0203] Step 705: The AMF constructs an Nsmf_PDUSession_CreateSMContextRequest message and sends the Nsmf_PDUSession_CreateSMContextRequest message to the selected SMF; the Nsmf_PDUSession_CreateSMContextRequest message contains one or more of the following: Radio Access Technology (RAT) type information (such as satellite access type), request type information, UE geographical location information, etc.

[0204] Step 706: After receiving the Nsmf_PDUSession_CreateSMContextRequest message, the SMF constructs an Nsmf_PDUSession_CreateSMContextResponse message and sends it to the AMF;

[0205] Step 707: The SMF uses the request type and RAT type contained in the Nsmf_PDUSession_CreateSMContextRequest message to determine the PCF used to establish an emergency PDU session (which can also be understood as used to serve the emergency PDU session) and which is dedicated to the satellite communication scenario;

[0206] Step 708: The SMF sends an SMPolicyAssociationEstablishment message to the selected PCF to request the establishment of a Session Management Policy Association (SM Policy Association). The SMPolicyAssociationEstablishment message contains one or more of the following: RAT type information, request type information, etc.

[0207] Step 709: The PCF uses the request type and RAT type contained in the SMPolicyAssociationEstablishment message and the local configuration data to generate an SM Policy for the UE. The SM Policy includes an emergency QoS policy (including a dedicated 5QI for satellite access scenarios) for IMS signaling transmission and a charging policy. Then, the PCF sends the SM Policy to the SMF to complete the establishment of the SM Policy Association.

[0208] Step 710: After establishing the SM Policy Association, if the satellite is equipped with a UPF, the SMF selects the satellite's UPF (i.e., the first user plane function mentioned above); or, if the satellite is not equipped with a UPF, the SMF selects the nearest UPF based on the geographical location information of the ground gateway station.

[0209] Step 711: The SMF sends an N4 session establishment request message to the selected UPF;

[0210] Step 712: After receiving the N4 session establishment request message, the UPF establishes an N4 session and sends an N4 session establishment response message to the SMF;

[0211] Step 713: After receiving the N4 session establishment response message, the SMF constructs a Namf_Communication_N1N2MessageTransfer message and sends it to the AMF; wherein, the Namf_Communication_N1N2MessageTransfer message contains an N1 message and an N2 message, wherein the N2 message contains a PDU session identifier, CN tunnel information (satellite / ground UPF tunnel address information), slice identifier information, etc.; the N1 message contains a PDU session establishment acceptance, satellite emergency call QoS data (i.e., emergency QoS policy for IMS signaling transmission under satellite access), slice identifier, DNN, P-CSCF address, and allocated IP address, etc.

[0212] Step 714: After receiving the Namf_Communication_N1N2MessageTransfer message, the AMF constructs an N2 PDU Session Request message based on the locally recorded ground gateway address and sends it to the ground gateway; wherein, the N2 PDU Session Request message contains satellite emergency call QoS data;

[0213] Step 715: The ground gateway station forwards the received N2 PDU Session Request message to the base station via the feeder link;

[0214] Step 716: After receiving the N2 PDU Session Request message, the base station constructs a PDU Session Establishment Accept message and sends it to the UE; wherein, the PDU Session Establishment Accept message contains satellite emergency call QoS data; then, the base station and the UE interact to complete the allocation of PDU session resources;

[0215] Step 717: After the base station completes resource allocation (which can also be understood as resource establishment), it constructs an N2 PDU SessionResponse message and sends it to the ground gateway station; wherein, the N2 PDU Session Response message includes PDU session identifier, Cause, N2 SM information, AN tunnel information (such as base station tunnel address information), etc.

[0216] Step 718: The ground gateway station forwards the received N2 PDU Session Response message to the AMF;

[0217] Step 719: After receiving the N2 PDU Session Response message, the AMF sends an Nsmf_PDUSession_UpdateSMContext Request message to the SMF; wherein the Nsmf_PDUSession_UpdateSMContext Request message contains information such as N2 SM information, SM context identifier, and request type;

[0218] Step 720: After receiving the Nsmf_PDUSession_UpdateSMContext Request message, the SMF constructs an N4SessionModificationRequest message and sends it to the UPF; wherein, the N4SessionModificationRequest message includes AN tunnel information, PDU session identifier, FAR related information, PDR related information, etc.

[0219] Step 721: After receiving the N4SessionModificationRequest message, the UPF modifies the PDU session and sends an N4SessionModificationResponse message to the SMF; wherein, the N4SessionModificationResponse message carries relevant information about local rules such as FAR and PDR;

[0220] Step 722: After receiving the N4SessionModificationResponse message, the SMF sends the Nsmf_PDUSession_UpdateSMContext Response message to the AMF, thereby completing the session context update.

[0221] After the emergency call PDU session is established, the emergency call establishment procedure is executed, such as... Figure 8 As shown, the emergency call setup process includes the following steps:

[0222] Step 801: The UE sends an INVITE message (i.e., the first message mentioned above, which can also be understood as initiating a satellite emergency call session request) to the P-CSCF on the established emergency call PDU. The INVITE message is used to request the establishment of a satellite emergency call session. The Request-URI header field in the INVITE message contains request type information (such as emergency call Service URN) and access type information, etc. The access type information indicates satellite access.

[0223] Step 802: After receiving the INVITE message, the P-CSCF parses the called number and access type information to identify the call as a satellite emergency call; then, the P-CSCF sends an AAR message to the PCF. The AAR message is used to request the establishment of a dedicated satellite emergency call bearer. The AAR message includes Service-URN AVP, access type information, etc.

[0224] In practical applications, PCRF can perform the functions of PCF in the context of a hybrid 4G and 5G network.

[0225] Step 803: After receiving the AAR message, the PCF performs an emergency call service check. Using the Service-URN AVP, access type information, and local configuration data contained in the AAR message, it generates an emergency QoS policy (which can also be understood as a satellite emergency call QoS rule) for IMS media transmission under satellite access. The generated emergency QoS policy is then sent to the SMF via a RAR message. The ARP indicated by the emergency QoS policy is higher than that of a normal satellite call.

[0226] Step 804: After receiving the RAR message, the SMF returns a RAA message to the PCF;

[0227] Step 805: SMF triggers the core network to establish a dedicated satellite emergency call voice bearer process, and establishes a dedicated satellite emergency call voice bearer based on the emergency QoS policy for IMS media transmission under satellite access;

[0228] Step 806: After receiving the RAA message, the PCF returns an AAA message to the P-CSCF indicating that the satellite emergency call voice dedicated bearer has been successfully established; wherein, the AAA message contains the UE's geographical location information, and the PCF can obtain the UE's geographical location information reported by the UE in the emergency registration process and / or emergency PDU session establishment process from the SBC;

[0229] Step 807: After receiving the AAA message, the P-CSCF determines the call type as an emergency call based on the called number and routes the INVITE message (which can also be understood as an emergency call) to the E-CSCF; wherein, the INVITE message contains the UE's geographical location information, access type information, etc.

[0230] Step 808: After receiving the INVITE message, the E-CSCF determines that the access type is satellite access based on the access type information and triggers the UE geolocation information verification process;

[0231] Specifically, the UE geolocation information verification process includes: the E-CSCF sending a location information verification request message to the LRF to request the LRF to verify the geolocation information of the UR. The location information verification request message includes the UE's geolocation information, access type, UE identifier and other information; then steps 809 to 812 are executed.

[0232] Step 809: After receiving the location information verification request message, the LRF sends a latency information acquisition request message to the AMF; wherein, the latency information acquisition request message includes information such as the UE identifier;

[0233] Step 810: After receiving the latency information acquisition request message, the AMF interacts with the base station based on the UE identifier and obtains the RTT measurement value (i.e., round-trip time) between the UE and the base station through RTT measurement and other methods.

[0234] Step 811: After obtaining the RTT measurement, the AMF sends a latency information response message to the LRF; wherein the latency information response message includes information such as the RTT measurement value and the UE identifier;

[0235] Step 812: After receiving the latency information response message, the LRF verifies the UE's geographical location information using the following two location parameters:

[0236] Parameter 1: UE's geographical location information;

[0237] Parameter 2: LRF uses time delay information to obtain the RTT measurement value contained in the response message to determine (or generate) the geographic area range; specifically, LRF can determine the intersection line of a sphere with satellite coordinates as the center and RTT measurement value as the radius with the Earth in the Earth-Centered Inertial (ECI) coordinate system, and the range enclosed by the intersection line is taken as the geographic area range;

[0238] In practical applications, the LRF determines whether the coordinates corresponding to parameter 1 are within the geographical area corresponding to parameter 2, and obtains the determination result. When the determination result indicates that the coordinates are within the geographical area corresponding to parameter 2, the LRF considers the UE's geographical location information to be verified, that is, the geographical location information reported by the UE is reliable geographical location information (which can also be understood as precise location information). When the determination result indicates that the coordinates are not within the geographical area corresponding to parameter 2, the LRF considers the UE's geographical location information to be verified. The LRF can use the UE's IP address information, etc., to perform a rough location of the UE and obtain reliable geographical location information (which can also be understood as rough location information). Then, the LRF can send a location information verification response message to the E-CSCF, and the location information verification response message contains reliable geographical location information.

[0239] Step 813: After receiving the location information verification response message, the E-CSCF determines the address information of the PSAP that can provide emergency call service to the UE based on the called number (e.g., URN) and trusted geographical location information, combined with the local routing table, and routes the INVITE message to the determined PSAP.

[0240] Step 814: After receiving the INVITE message, the PSAP completes the establishment of an emergency call between the UE and the PSAP; specifically, the PSAP sends a 200 OK message to the UE, and the UE sends an ACK message back to the PSAP.

[0241] The application example provided in this application demonstrates that when a UE makes an emergency call via satellite access, it reports its own location information. Based on the emergency call and the satellite emergency call QoS policy issued by the satellite access provider, the location information reported by the UE is verified, and PSAP selection is performed based on the verification result. This approach offers the following advantages:

[0242] 1) By having the UE report high-precision location information (which can also be understood as fine-grained location data) during emergency registration and / or emergency PDU session establishment, the core network can select the PSAP based on the reported location information. This avoids the possibility of area errors when selecting the PSAP using the TAI-based PSAP selection method (which can also be understood as the PSAP routing method) in satellite access scenarios. This can improve the accuracy of PSAP selection, shorten response time, and improve the accuracy of emergency event handling, thereby enhancing the security of users (UE users).

[0243] 2) Introduce a dedicated QoS strategy for satellite access emergency call scenarios to provide dedicated QoS configuration for satellite emergency calls. This ensures the stability and success rate of emergency call connections, thereby accelerating the establishment of dedicated bearers for emergency PDU sessions and emergency call voice, reducing bearer establishment latency, and ensuring timely initiation of emergency calls. At the same time, by adapting the QoS configuration to the characteristics of satellite communication, it can better address the challenges of high transmission latency and limited bandwidth in satellite networks, enhance the stability and reliability of emergency calls, thereby improving the efficiency of emergency rescue, significantly enhancing the reliability and effectiveness of emergency calls, and playing a key role in the rescue process.

[0244] To implement the method provided on the terminal side in this application embodiment, this application embodiment also provides a call setup device, which is installed on the terminal. The terminal accesses the network through access network equipment deployed on a satellite, such as... Figure 9 As shown, the device includes:

[0245] The sending unit 901 is configured to send first information to the core network, the core network being deployed on the ground, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call; and to send a first message, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

[0246] In one embodiment, the sending unit 901 is specifically used for:

[0247] A second message is sent to the core network, the second message being used to request registration for emergency calls, and the second message containing the first information.

[0248] In one embodiment, the transmitting unit 901 is specifically used for:

[0249] Send a third message to the core network, the third message being used to request the establishment of an emergency PDU session, the third message including the first message;

[0250] The first message is sent to the core network based on the established emergency PDU session.

[0251] In one embodiment, such as Figure 9 As shown, the device may further include:

[0252] The acquisition unit 902 is used to acquire the geographical location information of the terminal.

[0253] In practical applications, the sending unit 901 can be implemented by the communication interface in the call setup device, and the acquisition unit 902 can be implemented by the processor in the call setup device in combination with the communication interface.

[0254] To implement the core network side method of this application embodiment, this application embodiment also provides a call setup device, which is set on the core network, such as... Figure 10 As shown, the device includes:

[0255] The receiving unit 1001 is configured to receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through an access network device deployed on a satellite; and to receive a fourth message sent by the access network device, the fourth message being sent by the access network device after receiving the first message sent by the terminal, the first message being used to request the core network to establish an emergency call for the terminal based on the first information, the fourth message including second information, the second information being used to indicate that the terminal's access type includes satellite access;

[0256] Establishment unit 1002 is used to establish an emergency call associated with satellite access using the first information and the second information.

[0257] In one embodiment, the receiving unit 1001 is specifically used for:

[0258] The terminal sends a second message, which requests registration for an emergency call and includes the first information.

[0259] The device may further include:

[0260] The registration unit is used to register the terminal for emergency calls.

[0261] In one embodiment, the receiving unit 1001 is specifically used for:

[0262] The terminal sends a third message, which is used to request the establishment of an emergency PDU session, and the third message contains the first information.

[0263] The establishment unit 1002 is further configured to:

[0264] Establish an emergency PDU session; wherein, during the establishment of the emergency PDU, the geographical location information of the terminal is not verified.

[0265] In one embodiment, during the establishment of an emergency PDU session, the establishment unit 1002 is specifically used for:

[0266] Determine the first QoS rule;

[0267] Based on the determined first QoS rule, an emergency PDU session dedicated bearer is established and associated with satellite access. The emergency PDU session dedicated bearer is used for signaling transmission.

[0268] In one embodiment, during the establishment of an emergency PDU session, the establishment unit 1002 is specifically used for:

[0269] A first user plane function is determined, which is at least used to transmit user plane data of the terminal.

[0270] In one embodiment, the establishment unit 1002 is specifically used for:

[0271] The user plane functions deployed on the satellite are designated as the first user plane functions;

[0272] or,

[0273] Based on the geographical location information of the ground gateway station corresponding to the satellite, the first user plane function is determined.

[0274] In one embodiment, during the process of establishing an emergency call associated with satellite access, the establishment unit 1002 is specifically used for:

[0275] Determine the second QoS rule;

[0276] Based on the determined second QoS rules, an emergency call dedicated bearer is established and associated with satellite access. The emergency call dedicated bearer is used for media streaming transmission.

[0277] In one embodiment, during the process of establishing an emergency call associated with satellite access, the establishment unit 1002 is specifically used for:

[0278] Using the first information, a first PSAP is determined, which is at least used to respond to an emergency call from the terminal.

[0279] In one embodiment, the establishment unit 1002 is specifically used for:

[0280] The received geographical location information of the terminal is verified using the RTT measurement results between the terminal and the access network device.

[0281] In one embodiment, the establishment unit 1002 is specifically used for:

[0282] If the verification result indicates that the location information of the received terminal has been successfully verified, the first PSAP is determined using the received geographical location information of the terminal;

[0283] or,

[0284] If the verification result indicates that the location information of the terminal received has failed to be verified, the geographical location information of the terminal is estimated; and the estimated geographical location information of the terminal is used to determine the first PSAP.

[0285] In practical applications, the receiving unit 1001 can be implemented by the communication interface in the call setup device, and the setup unit 1002 can be implemented by the processor in the call setup device in combination with the communication interface.

[0286] It should be noted that the call setup device provided in the above embodiments is only illustrated by the division of the above-described program units during call setup. In practical applications, the above processing can be assigned to different program units as needed, that is, the internal structure of the device can be divided into different program units to complete all or part of the processing described above. In addition, the call setup device and the call setup method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0287] Based on the hardware implementation of the above program modules, and in order to implement the terminal-side method of this application embodiment, this application embodiment also provides a terminal, which accesses the network through an access network device deployed on a satellite, such as... Figure 11 As shown, the terminal 1100 includes:

[0288] The first communication interface 1101 is capable of exchanging information with the core network of the access network device;

[0289] The first processor 1102 is connected to the first communication interface 1101 to enable information interaction with the core network and to execute the methods provided by one or more of the above-mentioned terminal-side technical solutions when running computer programs.

[0290] The computer program is stored in the first memory 1103.

[0291] Specifically, the first processor 1102 is used for:

[0292] The terminal sends first information to the core network via the first communication interface 1101. The core network is deployed on the ground. The first information includes the geographical location information of the terminal. The first information is used at least to establish an emergency call. The terminal also sends a first message via the first communication interface 1101. The first message is used to request the core network to establish an emergency call for the terminal based on the first information.

[0293] In one embodiment, the first processor 1102 is specifically used for:

[0294] A second message is sent to the core network through the first communication interface 1101. The second message is used to request registration for emergency calls and includes the first information.

[0295] In one embodiment, the first processor 1102 is specifically used for:

[0296] A third message is sent to the core network through the first communication interface 1101. The third message is used to request the establishment of an emergency PDU session. The third message includes the first message.

[0297] Based on the established emergency PDU session, the first message is sent to the core network through the first communication interface 1101.

[0298] In one embodiment, the first processor 1102 is further configured to:

[0299] The geographical location information of the terminal is obtained through the first communication interface 1101.

[0300] It should be noted that the specific processing procedures of the first processor 1102 and the first communication interface 1101 can be understood by referring to the above method.

[0301] Of course, in practical applications, the various components in terminal 1100 are coupled together through bus system 1104. It can be understood that bus system 1104 is used to realize the connection and communication between these components. In addition to a data bus, bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, in... Figure 11 The general designated all buses as Bus System 1104.

[0302] The first memory 1103 in this embodiment is used to store various types of data to support the operation of the terminal 1100. Examples of such data include any computer program used to operate on the terminal 1100.

[0303] The methods disclosed in the above embodiments of this application can be applied to the first processor 1102, or implemented by the first processor 1102. The first processor 1102 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 1102. The first processor 1102 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1102 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, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 1103. The first processor 1102 reads the information in the first memory 1103 and completes the steps of the aforementioned method in combination with its hardware.

[0304] In an exemplary embodiment, terminal 1100 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0305] Based on the hardware implementation of the above program modules, and in order to implement the core network side method of the embodiments of this application, the embodiments of this application also provide a core network, such as... Figure 12 As shown, the core network 1200 includes:

[0306] The second communication interface 1201 is capable of exchanging information with the terminal through access network equipment deployed on the satellite;

[0307] The second processor 1202 is connected to the second communication interface 1201 to enable information interaction with the terminal and to execute the methods provided by one or more technical solutions on the core network side when running computer programs.

[0308] The computer program is stored in the second memory 1203.

[0309] Specifically, the second communication interface 1201 is used for:

[0310] The system receives first information, which includes the geographical location information of the terminal, and is used at least to establish an emergency call. The terminal accesses the network through an access network device deployed on a satellite. The system also receives a fourth message sent by the access network device after receiving the first message from the terminal. The first message requests the core network to establish an emergency call for the terminal based on the first information. The fourth message includes second information, which indicates that the terminal's access type includes satellite access.

[0311] The second processor 1202 is used for:

[0312] Using the first and second information, an emergency call associated with satellite access is established.

[0313] In one embodiment, the second communication interface 1201 is specifically used for:

[0314] The terminal sends a second message, which requests registration for an emergency call and includes the first information.

[0315] The second processor 1202 is also used for:

[0316] Register the terminal for emergency calls.

[0317] In one embodiment, the second communication interface 1201 is specifically used for:

[0318] The terminal sends a third message, which is used to request the establishment of an emergency PDU session, and the third message contains the first information.

[0319] The second processor 1202 is also used for:

[0320] Establish an emergency PDU session; wherein, during the establishment of the emergency PDU, the geographical location information of the terminal is not verified.

[0321] In one embodiment, during the establishment of an emergency PDU session, the second processor 1202 is specifically used for:

[0322] Determine the first QoS rule;

[0323] Based on the determined first QoS rule, an emergency PDU session dedicated bearer is established and associated with satellite access. The emergency PDU session dedicated bearer is used for signaling transmission.

[0324] In one embodiment, during the establishment of an emergency PDU session, the second processor 1202 is specifically used for:

[0325] A first user plane function is determined, which is at least used to transmit user plane data of the terminal.

[0326] In one embodiment, the second processor 1202 is specifically used for:

[0327] The user plane functions deployed on the satellite are designated as the first user plane functions;

[0328] or,

[0329] Based on the geographical location information of the ground gateway station corresponding to the satellite, the first user plane function is determined.

[0330] In one embodiment, during the process of establishing an emergency call associated with satellite access, the second processor 1202 is specifically used for:

[0331] Determine the second QoS rule;

[0332] Based on the determined second QoS rules, an emergency call dedicated bearer is established and associated with satellite access. The emergency call dedicated bearer is used for media streaming transmission.

[0333] In one embodiment, during the process of establishing an emergency call associated with satellite access, the second processor 1202 is specifically used for:

[0334] Using the first information, a first PSAP is determined, which is at least used to respond to an emergency call from the terminal.

[0335] In one embodiment, the second processor 1202 is specifically used for:

[0336] Verify the received geographical location information of the terminal to obtain the verification result;

[0337] The first PSAP is determined using the verification result.

[0338] In one embodiment, the second processor 1202 is specifically used for:

[0339] The received geographical location information of the terminal is verified using the RTT measurement results between the terminal and the access network device.

[0340] In one embodiment, the second processor 1202 is specifically used for:

[0341] If the verification result indicates that the location information of the received terminal has been successfully verified, the first PSAP is determined using the received geographical location information of the terminal;

[0342] or,

[0343] If the verification result indicates that the location information of the terminal received has failed to be verified, the geographical location information of the terminal is estimated; and the estimated geographical location information of the terminal is used to determine the first PSAP.

[0344] It should be noted that the specific processing procedures of the second processor 1202 and the second communication interface 1201 can be understood by referring to the above method.

[0345] Of course, in practical applications, the various components in the core network 1200 are coupled together through the bus system 1204. It can be understood that the bus system 1204 is used to implement communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 12 The general labeled all buses as Bus System 1204.

[0346] The second memory 1203 in this embodiment is used to store various types of data to support the operation of the core network 1200. Examples of such data include any computer program used to operate on the core network 1200.

[0347] The methods disclosed in the embodiments of this application can be applied to the second processor 1202, or implemented by the second processor 1202. The second processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the second processor 1202. The second processor 1202 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1202 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, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the second memory 1203. The second processor 1202 reads the information in the second memory 1203 and completes the steps of the aforementioned method in combination with its hardware.

[0348] In an exemplary embodiment, the core network 1200 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0349] It is understood that the memories (first memory 1103, second memory 1203) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0350] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium. For example, it may include a first memory 1103 storing a computer program, which can be executed by the first processor 1102 of the terminal 1100 to complete the steps described in the aforementioned terminal-side method. Another example is a second memory 1203 storing a computer program, which can be executed by the second processor 1202 of the core network 1200 to complete the steps described in the aforementioned core network-side method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0351] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a first processor 1102 of a terminal 1100 to complete the steps described in the aforementioned terminal-side method, or the computer program can be executed by a second processor 1202 of a core network 1200 to complete the steps described in the aforementioned core network-side method.

[0352] To implement the method provided in the embodiments of this application, the embodiments of this application also provide a call setup system, such as... Figure 13 As shown, the system includes: terminal 1301, access network equipment 1302, and core network 1303.

[0353] It should be noted that the specific processing procedures of the terminal 1301, access network device 1302 and core network 1303 have been described in detail above and will not be repeated here.

[0354] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0355] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0356] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A call setup method, characterized in that, Applied to a terminal that accesses a network via access network equipment deployed on a satellite, the method includes: Send first information to the core network, which is deployed on the ground, the first information including the geographical location information of the terminal, and the first information is used at least to establish an emergency call; Send a first message, which requests the core network to establish an emergency call for the terminal based on the first information.

2. The method according to claim 1, characterized in that, The sending of the first information to the core network includes: A second message is sent to the core network, the second message being used to request registration for emergency calls, and the second message containing the first information.

3. The method according to claim 1, characterized in that, Sending the first information to the core network includes: Send a third message to the core network, the third message being used to request the establishment of an Emergency Protocol Data Unit (PDU) session, the third message including the first message; The first message is sent to the core network based on the established emergency PDU session.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Obtain the geographical location information of the terminal.

5. A call setup method, characterized in that, Applied to the core network, the method includes: The terminal receives first information, which includes the geographical location information of the terminal. The first information is used at least to establish an emergency call. The terminal accesses the network through an access network device deployed on a satellite. The access network device receives a fourth message, which is sent after receiving a first message from the terminal. The first message is used to request the core network to establish an emergency call for the terminal based on the first information. The fourth message contains second information, which is used to indicate that the terminal's access type includes satellite access. Using the first and second information, an emergency call associated with satellite access is established.

6. The method according to claim 5, characterized in that, The receiving of the first information includes: The terminal sends a second message, which requests registration for an emergency call and includes the first information. Register the terminal for emergency calls.

7. The method according to claim 5, characterized in that, The receiving of the first information includes: The terminal sends a third message, which is used to request the establishment of an emergency PDU session and includes the first information. Establish an emergency PDU session; wherein, during the establishment of the emergency PDU, the geographical location information of the terminal is not verified.

8. The method according to claim 7, characterized in that, The method for establishing an emergency PDU session includes: Determine the first Quality of Service (QoS) rule; Based on the determined first QoS rule, an emergency PDU session dedicated bearer is established and associated with satellite access. The emergency PDU session dedicated bearer is used for signaling transmission.

9. The method according to claim 7, characterized in that, The method for establishing an emergency PDU session includes: A first user plane function is determined, which is at least used to transmit user plane data of the terminal.

10. The method according to claim 9, characterized in that, The function of determining the first user plane includes: The user plane functions deployed on the satellite are designated as the first user plane functions; or, Based on the geographical location information of the ground gateway station corresponding to the satellite, the first user plane function is determined.

11. The method according to claim 5, characterized in that, The method includes the following steps in establishing an emergency call associated with satellite access: Determine the second QoS rule; Based on the determined second QoS rules, an emergency call dedicated bearer is established and associated with satellite access. The emergency call dedicated bearer is used for media streaming transmission.

12. The method according to any one of claims 5 to 11, characterized in that, In the process of establishing an emergency call associated with satellite access, the method includes: Using the first information, a first Public Safety Answering Point (PSAP) is determined, which is used at least to respond to emergency calls from the terminal.

13. The method according to claim 12, characterized in that, The step of using the first information to determine the first PSAP includes: Verify the received geographical location information of the terminal to obtain the verification result; The first PSAP is determined using the verification result.

14. The method according to claim 13, characterized in that, The verification of the received geographical location information of the terminal includes: The received geographical location information of the terminal is verified using the round-trip time (RTT) measurement results between the terminal and the access network device.

15. The method according to claim 13, characterized in that, If the verification result indicates that the location information of the received terminal has been successfully verified, the first PSAP is determined using the received geographical location information of the terminal; or, If the verification result indicates that the location information of the terminal received has failed to be verified, the geographical location information of the terminal is estimated. The first PSAP is determined using the estimated geographical location information of the terminal.

16. A call setup device, characterized in that, A terminal is configured to access the network via access network equipment deployed on a satellite, comprising: The sending unit is configured to send first information to the core network, the core network being deployed on the ground, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call; and to send a first message, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

17. A call setup device, characterized in that, Configured in the core network, including: A receiving unit is configured to receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through an access network device deployed on a satellite; and to receive a fourth message sent by the access network device, the fourth message being sent by the access network device after receiving the first message sent by the terminal, the first message being used to request the core network to establish an emergency call for the terminal based on the first information, the fourth message including second information, the second information being used to indicate that the terminal's access type includes satellite access; The establishment unit is used to establish an emergency call associated with satellite access using the first information and the second information.

18. A terminal, characterized in that, The terminal accesses the network through access network equipment deployed on the satellite, including: a first processor and a first communication interface; wherein, The first processor is configured to send first information to the core network via the first communication interface, the core network being deployed on the ground, the first information including the geographical location information of the terminal, and the first information being used at least to establish an emergency call; and to send a first message via the first communication interface, the first message being used to request the core network to establish an emergency call for the terminal based on the first information.

19. A core network, characterized in that, include: A second processor and a second communication interface; wherein... The second communication interface is used to receive first information, the first information including the geographical location information of the terminal, the first information being used at least to establish an emergency call, the terminal accessing the network through an access network device deployed on a satellite; and to receive a fourth message sent by the access network device, the fourth message being sent by the access network device after receiving the first message sent by the terminal, the first message being used to request the core network to establish an emergency call for the terminal based on the first information, the fourth message including second information, the second information being used to indicate that the terminal's access type includes satellite access; The second processor is used to establish an emergency call associated with satellite access using the first information and the second information.

20. A terminal, characterized in that, include: A first processor and a first memory for storing computer programs capable of running on the processor. Wherein, when the first processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 4.

21. A core network, characterized in that, include: A second processor and a second memory for storing computer programs that can run on the processor. Wherein, when the second processor is used to run the computer program, it performs the steps of the method according to any one of claims 5 to 15.

22. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4, or the steps of the method according to any one of claims 5 to 15.

23. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4, or the steps of the method according to any one of claims 5 to 15.

Images