Method for determining geolocation of UE, satellite-based data transmission method, and device incorporating the same
By dividing satellite coverage into sub-beams with predefined signal strength ranges and using orbit-specific mappings, the method addresses the challenge of accurately locating UE and ensuring reliable emergency communication in satellite systems, enhancing location determination and notification delivery.
Patent Information
- Application Number
- PCT/CN2025/094692
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
Existing satellite-based emergency communication systems face challenges in accurately locating user equipment (UE) within large satellite coverage areas and ensuring timely delivery of emergency notifications due to rapid satellite movement and poor reception conditions, leading to potential delays, interruptions, and missed messages.
A method involving the division of satellite coverage into sub-beams with predefined signal strength ranges and orbit-specific mappings, combined with real-time signal strength measurements, to accurately determine the UE's location and ensure reliable emergency communication.
Enhances the accuracy of UE location determination and ensures reliable delivery of emergency notifications by minimizing ambiguity and maintaining Quality of Service (QoS) requirements, even in rapidly changing satellite environments.
Smart Images

Figure CN2025094692_19112026_PF_FP_ABST
Abstract
Description
METHOD FOR DETERMINING GEOLOCATION OF UE, SATELLITE-BASED DATA TRANSMISSION METHOD, AND DEVICE INCORPORATING THE SAMETECHNICAL FIELD
[0001] The present disclosure generally relates to satellite-based wireless communication technology, and in particular to a method for determining a geolocation of a UE in a satellite-based data transmission process, a satellite-based data transmission method, a wireless communication device, and a computer readable medium.BACKGROUND
[0002] Satellite-enabled emergency communication plays a vital role, particularly in remote and inaccessible areas. In scenarios such as natural disasters, including tsunamis and earthquakes, where traditional communication networks are unavailable, satellite access serves as a critical lifeline and a last resort for survival. It facilitates rapid response and coordination of rescue efforts, ensuring timely assistance to those in need. Furthermore, satellite-supported emergency communication is indispensable for individuals traveling to remote locations for work or exploration. In the event of accidents or unexpected emergencies, satellite-enabled communication can swiftly initiate rescue operations, significantly enhancing survival prospects.
[0003] As part of advancements toward 5G Rel-20 (5G Advanced) , new study items have been approved to support emerging use cases, such as multi-orbit satellite access for diverse services and resilient notification mechanisms for receiving important and emergency calls in areas with compromised connectivity or coverage. These efforts also aim to enhance existing use cases, including satellite-enabled emergency communications and IMS voice services over GEO satellite access. The findings from these studies provide a foundation for establishing normative requirements to standardize these enhancements and capabilities within 5G Advanced and future 6G systems.
[0004] Looking ahead to 6G, transformative approaches to emergency communication and network resilience are being explored to address challenges such as latency, coverage gaps, and reliability in disaster response scenarios. Innovations focus on leveraging hybrid satellite-terrestrial networks, advanced encryption techniques, and dynamic spectrum sharing to ensure robust and secure communication during crises. Additionally, concepts such as self-healing networks and immersive alert systems are being investigated to further enhance emergency response capabilities.
[0005] The present disclosure focuses on analyzing enhancements that enable resilient communications (e.g., emergency communications) over satellite access while addressing critical gaps in coverage and reliability.SUMMARY
[0006] Accordingly, the present disclosure aims to provide a method for determining a geolocation of a UE in a satellite-based data transmission process, a satellite-based data transmission method, a wireless communication device, and a computer readable medium.
[0007] A technical scheme adopted by the present disclosure is to provide a method for determining a geolocation of a user equipment (UE) in a satellite-based data transmission process. The method is executed by a wireless communication node. The method includes: acquiring a mapping relation between a plurality of signal strength ranges and a plurality of sub-coverages of a satellite; and determining a current signal strength of downlink transmission of the satellite; wherein the mapping relation and the current signal strength are used for determination of an estimated sub-coverage of the satellite in which the UE is located.
[0008] Another technical scheme adopted by the present disclosure is to provide a method for determining a geolocation of a user equipment (UE) in a satellite-based data transmission process. The method is executed by a core network node. The method includes: acquiring an orbit type of a satellite which is configured for the UE to perform the satellite-based data transmission process; acquiring a latency requirement for the satellite-based data transmission process; and selecting a positioning method for determining the geolocation of the UE based on the orbit type of the satellite and the latency requirement.
[0009] Another technical scheme adopted by the present disclosure is to provide a satellite-based data transmission method. The method is executed by a wireless communication node. The method includes: acquiring an impacted geolocation corresponding to a satellite-based data transmission request; and checking whether the geolocation falls within a coverage range of a first satellite that is connected to the wireless communication node.
[0010] Another technical scheme adopted by the present disclosure is to provide a wireless communication device. The device includes a processor and a memory. The memory is configured to store executable instructions that, when executed by the processor, cause the processor to perform any of the foregoing methods.
[0011] Another technical scheme adopted by the present disclosure is to provide a non-transitory computer readable medium. The computer readable medium is configured to store executable instructions that, when executed by the processor, cause the processor to perform any of the foregoing methods.BRIEF DESCRIPTION OF THE DRAWINGS
[0012] In order to clearly explain the technical solutions in the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are merely some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings may also be obtained based on these drawings without any creative work.
[0013] FIG. 1 shows a flowchart of a method for determining a geolocation of a user equipment (UE) in satellite-based data transmission process according to an embodiment of the present disclosure.
[0014] FIG. 2 shows an exemplary scenario where the satellite coverage is divided into four sub-regions.
[0015] FIG. 3 illustrates an example of the whole signaling for determining the actual geolocation of UE.
[0016] FIG. 4 shows a flowchart of a method for determining a geolocation of a user equipment (UE) in satellite-based data transmission process according to an embodiment of the present disclosure.
[0017] FIG. 5 shows a flowchart of a satellite-based data transmission method according to an embodiment of the present disclosure.
[0018] FIG. 6 shows a method for determining the satellite coverage radius.
[0019] FIG. 7 shows an example of an impacted warning or emergency call paging area falling within the coverage of one satellite-enabled RAN node connected to the core network node.
[0020] FIG. 8 shows an example of an impacted warning or emergency call paging area partially or fully falling outside the coverage of one satellite-enabled RAN node connected to the core network node.
[0021] FIG. 9 illustrates the definitions of T_predict, T_change, and T_delivery.
[0022] FIG. 10 shows an example of an impacted warning or emergency call paging area falling within an overlapped coverage of two satellite-enabled RAN nodes.
[0023] FIG. 11 shows the signaling for addressing UE missing warning or emergency paging message due to poor radio channel condition (low SNR) or due to a condition of serving satellite change.
[0024] FIG. 12 illustrates an example of the whole signaling for guaranteeing emergency call and / or warning messages delivery.
[0025] FIG. 13 illustrates the essential parameters for satellite ephemeris.
[0026] FIG. 14 shows one representative form of the geolocation, footprints or geometric shapes described in the present disclosure.
[0027] FIG. 15 shows another representative form of the geolocation, footprints or geometric shapes described in the present disclosure.
[0028] FIG. 16 shows yet another representative form of the geolocation, footprints or geometric shapes described in the present disclosure.
[0029] FIG. 17 shows another example about signaling exchanges for locating the UE requesting emergency access.
[0030] FIG. 18 shows another example about signaling exchanges for preventing of missing emergency messages and call notification.
[0031] FIG. 19 is a schematic diagram of a wireless communication device according to an embodiment of the present disclosure.DETAILED DESCRIPTION
[0032] The disclosure will now be described in detail with reference to the accompanying drawings and examples. Apparently, the described embodiments are only a part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
[0033] The emergency services in 3GPP terrestrial networks can be classified into two categories. The first category is in the form of warning messages using public warning systems (PWS) , such as the Earthquake and Tsunami Warning System (ETWS) and the Commercial Mobile Alert System (CMAS) , which are delivered to UEs based on cell broadcast service (CBS) technology. The second category is in the form of emergency voice call connections initiated by a UE experiencing an emergency situation. These calls are directed to a public safety answering point (PSAP) , either by dialing a known emergency number (e.g., 110, 112, 999, 911) or via explicit GUI selection on the mobile phone. The details of how these emergency services work based on 3GPP systems are explained below.
[0034] 1) UE-Initiated Emergency
[0035] Emergency services in 5GS behave like a VoNR connection, wherein the IMS and RRC signaling flow includes RRC and SIP control messages that indicate "emergency" as the use case. When a UE initiates an emergency call toward a Public Safety Answering Point (PSAP) , the process begins with the UE detecting an emergency situation, either by recognizing a dialed emergency number (e.g., 110, 112, 911, or 999) or through an explicit user action, such as pressing an SOS button. The UE identifies the call as an emergency and sets the emergency indication in its signaling toward the 5G RAN, 5GC, and PSAP center. If the UE is in a limited-service state, it checks the ims-EmergencySupport flag in the SIB1 or the registration accept message to confirm network support for emergency services.
[0036] The UE then initiates the establishment of a Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB) with higher priority, skipping certain security procedures like authentication to minimize call setup time. The UE establishes a session to connect to an IP Connectivity Access Network (IP-CAN, e.g., 5GC (NG-RAN) or EPS (UTRAN and E-UTRAN) ) , configured with a default QoS flow to ensure prioritized resources for the emergency call.
[0037] Next, the UE performs a discovery procedure to locate the IP-CAN IMS control plane node (namely, Proxy Call Session Control Function or P-CSCF) responsible for handling the emergency call. If the UE has sufficient credentials, it initiates an IMS emergency registration by sending a SIP REGISTER message with an emergency indication to the IMS node of the P-CSCF. The P-CSCF forwards the registration to the S-CSCF, which may act as the E-CSCF for emergency services. Once registered, the UE initiates the IMS emergency PDU session setup by sending a SIP INVITE message to the P-CSCF, including the emergency service indication (e.g., "SOS" in the URN) and, if available, the UE's Public User Identifier. The P-CSCF prioritizes the emergency call and routes it to an Emergency-CSCF (E-CSCF) , which determines the appropriate PSAP based on the UE's location and local regulations. The E-CSCF establishes a connection to the PSAP, enabling the transfer of emergency-related information such as voice, location data, and optional assistance details. Throughout the process, the 5GC network ensures prioritized resource allocation for the emergency call.
[0038] The AMF (Access and Mobility Management Function) and SMF (Session Management Function) handle the emergency session configuration, including the selection of the emergency DNN and QoS parameters [TS 23.501, TS 23.502] , while the UPF ensures low-latency data transfer for the emergency session. If the UE lacks sufficient resources (e.g., due to ongoing sessions) , it terminates non-emergency communications to prioritize the emergency call setup. Once the connection is established, the UE and PSAP can communicate directly, with the network maintaining the necessary QoS to support the emergency call, ensuring rapid and reliable communication for public safety. More details about the process can be found in [TS 23.167] .
[0039] In cases where the emergency session initiated by the UE is over satellite access, the granularity of the location data for the initiated PDU emergency session is considered to be the entire NTN (Non-Terrestrial Networks) or satellite cell. This makes it difficult to locate the UE seeking emergency access and provide the required assistance or help.
[0040] 2) Network-Initiated Emergency
[0041] The system architecture of Public Warning Systems (PWS) , including Earthquake and Tsunami Warning Systems (ETWS) and Commercial Mobile Alert Systems (CMAS) , is designed to broadcast warning notifications to User Equipment (UE) , such as mobile devices, efficiently. These systems leverage cellular networks to deliver critical alerts to a large number of users promptly. The architecture typically involves a centralized warning message generation system, such as a Cell Broadcast Entity (CBE) , a Cell Broadcast Centre Function (CBCF) , or a Public Warning System -Interworking System (PWS-IWS) . These are responsible for creating and authenticating warning messages.
[0042] These messages are transmitted to the core infrastructure of the 5G cellular network, where they are processed and forwarded using Write-Replace-Warning transactions containing emergency information (e.g., "warning type" , "warning message" , "impacted area" , "time period" ) over NonUeMessageTransfer and N2 interfaces toward the appropriate base stations for broadcast towards UEs. The core network plays a crucial role in disseminating PWS messages. When a warning message is generated, it is first sent to the Mobile Management Entity (MME) in LTE networks or the Access and Mobility Management Function (AMF) in 5G networks. These nodes manage the signaling between the UE and the network. The MME or AMF then forwards the warning message to the relevant radio access network (RAN) node (eBs in LTE or gBs in 5G) within the targeted or affected geographic area. The base stations broadcast the warning message over the air interface using System Information Blocks (SIBs) or other dedicated signaling channels, ensuring that all UEs within the coverage area receive the alert. Upon receiving the broadcasted warning message, the UE processes the alert and presents it to the user through a visible and audible notification. More details about the process can be found in [TS 23.041] .
[0043] When considering the broadcasting of public warning emergency messages over satellite access, the following unique features of satellite access pose challenges:
[0044] a) Satellite coverage can move, while many aspects of the regulatory framework for emergency cell broadcast services (e.g., the area where PWS is broadcasted) are typically fixed on the ground (e.g., TN areas cell ids) . This poses a challenge of how the above signaling can be reused to guarantee that all UEs targeted by the emergency broadcasting can effectively receive it.
[0045] b) Under current 5G terrestrial warning specifications, PWS messages are not exchanged between gNBs, while the delivery duration time of PWS warning notifications from CBS to UE should be within 4 seconds (TS 22.26 section 5.2) . In the case of LEO satellite constellations, the satellite coverage changes at a speed less than the delivery time of PWS warning messages. This could cause delay, interruption, and / or even lead to a loss of PWS message.
[0046] As described above, both UE and network-initiated emergency services will be impacted when satellite access is considered. For example, for UE-initiated emergencies over satellite access, it is difficult to locate the UE seeking emergency access due to the large coverage area of satellite access compared to terrestrial. As for network-initiated warnings or emergency notification broadcasting over satellite access, there is a high chance of interruption, delay, or failure to deliver the notification due to the fast movement of satellites and / or the possibility of the UE missing the notification due to residing in very low SNR or poor channel reception conditions. The potential issues are explained below.
[0047] One potential issue is the failure to locate the UE which requests emergency access.
[0048] In the case of an emergency over satellite access, if we assume that the granularity of a UE-initiated IMS PDU emergency session is the entire satellite cell or beam, it would be difficult to determine the actual location where the UE requesting emergency access is residing in order to provide the required assistance or help.
[0049] In terrestrial networks, the actual location of a UE requesting an emergency service is determined based on the RAN cell ID and / or the tracking area where the UE was residing at the time the UE triggered the emergency session. This information is provided within NG UE initial messages from the RAN node (gNB) to the 5G core network (AMF) or retrieved from the LMF in cases where it is not provided by the RAN node. In the case of an emergency session over satellite access, if the granularity of location information provided from NG-RAN to the 5GC and PSAP system is considered to be the entire satellite cell or beam, it will be difficult to determine the actual location of the UE requesting emergency access. This is because satellite coverage is very large (i.e., satellite coverage is at the granularity of a country or even a subcontinent, compared to a 5G terrestrial cell, which is limited to a specific geographical location) .
[0050] For the option of retrieving UE location information from the LMF, the emergency PDU session uses a 5QI value of 5 to ensure high priority, which requires high reliability and a latency in the range of 100ms. However, most of the positioning estimation methods used by the LMF in the case of satellite access require a latency greater than 100ms.
[0051] Another potential issue is the failure to deliver emergency notifications, or missing or such notifications.
[0052] 1) Failure to deliver warning messages to UE
[0053] The delivery time of the duration of PWS Warning Notifications from the CBS center to the UE should be within 4 seconds. When the broadcasting of PWS Warning Notifications over satellite access is considered, especially in the case of LEO satellite constellations, where the satellite coverage on the ground is changing at a very fast speed, very close to the time duration required for the delivery of PWS Notifications to UEs. In such a case, the delivery of the PWS message could be interrupted, delayed, or even missed.
[0054] To assess the speed of change of satellite coverage in a satellite constellation, assuming there is no overlap of coverage of two satellites at a time from the satellite's point of view, we need to determine the average distance between satellites and the satellite's orbital velocity or orbital speed at a given time. Given the average distance between satellites and the satellite's orbital velocity or orbital speed at a given time, the satellite handover time in a satellite constellation can be calculated by: where (V) Distance is the distance between satellites.
[0055] For Star-link satellite constellation: Surface Area= 4π (6, 371+550) 2≈ 552million km2
[0056] Table 1 povides a detailed summary comparing the calculated handover times for several satellite constellations, including Starlink, Hongyun Technology, Genesat, and Guowang. Table 1 Summary of the Calculated Handover Time for Some Satellite Constellations
[0057] From this table, we can notice that in most of these satellite constellations, a satellite change or handover is expected to occur every 3 seconds. While according to TS 22.26 section 5.2, the delivery time of the duration of the Warning Notifications (i.e., from the time that the Warning Notification is received by the PLMN operator, i.e., the edge of the 3GPP network, to the time that the Warning Notification is successfully delivered to the UEs) should be delivered within 4 seconds, even under congestion situations. This means that the 3GPP network edge node responsible for the delivery of the Warning Notifications to the UEs will be changing at a speed lower than the expected time duration for the delivery of the Warning Notifications to the UE. This will lead to the following impacts:
[0058] a) Potential Loss of the Warning Message: If the Warning Notification has not been completely delivered before the handover occurs, the message might be lost, corrupted, or require retransmission. This can lead to incomplete or missed warnings.
[0059] b) Delay or Interruption of the Warning Message during Handover: When a handover occurs, the UE's connection to the current PLMN node is temporarily interrupted while it establishes a new connection with the next PLMN node. This interruption can cause a delay or even loss of the Warning Notification being delivered.
[0060] 2) Missing of Warning &Emergency Calls by UE
[0061] Communication between satellites and smartphones typically has very limited power margins and usually requires a line of sight (LOS) for optimal performance. For Mobile Originated (MO) calls, users are aware of the channel quality and can achieve LOS communication by consciously adjusting the spot for signal transmission / reception. However, for Mobile Terminated (MT) communication, including emergency calls and messages, users are unaware of the channel condition and might miss important calls / messages due to poor reception channel conditions. This requires the satellite access system to be capable of notifying users about missed incoming emergency calls and messages when they are not reachable in the satellite access system. A resilient notification mechanism ensures that notifications of important calls and messages reach users in areas where normal connectivity fails or is compromised.
[0062] When the User Equipment (UE) is inside a pocket or backpack, inside a car, or blocked by buildings and / or foliage, the additional path loss causes a very low signal-to-noise ratio (SNR) at the receiver. Per the 3GPP 5G New Radio (NR) Non-Terrestrial Network (NTN) standard TS 38.304 [5] , UE in Radio Resource Connection IDLE (RRC_IDLE) or Radio Resource Connection INACTIVE (RRC_INACTIVE) periodically wakes up to check for paging signals. When the UE wakes up, it first tries to detect the Synchronization Signal Block (SSB) for synchronization purposes and to extract the Master Information Block (MIB) . Then, it attempts to detect the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) to check for paging messages.
[0063] There are two types of paging in 5G NR:
[0064] a) Paging to trigger RRC setup, RRC request, or RRC resumption (most paging messages) .
[0065] b) System Information Modification and ETWS / CMAS indications (short messages) transmitted by PDCCH using Downlink Control Information (DCI) format 1_0 with P_RNTI and a short message.
[0066] As Public Warning System (PWS) warning notifications, such as ETWS / CMAS indications, are transmitted to UEs using the short message field of paging via DCI format 1_0 (see TS 38.212
[0017] , clause 7.3.1.2.1) , it is important to ensure that notifications or emergency call requests are successfully received by the UE. To achieve this, it is crucial to ensure that paging messages are successfully received by the intended users. However, when the Core Network or the gNB pages a UE in IDLE or INACTIVE mode, the UE may be in very poor channel conditions and may miss the 5G NR paging message due to very low SNR, even though it is still within the beam coverage of the NTN system.
[0067] Although some existing solutions have discussed issues related to ensuring resilient notifications of paging, these solutions have focused only on the design of the physical channel and have not addressed or covered the criteria to trigger or determine the number of repetitions for such resilient paging or the associated signaling design.
[0068] Embodiments of the present disclosure aim to solve at least some of the above-described issues.
[0069] FIG. 1 shows a flowchart of a method for determining a geolocation of a user equipment (UE) in satellite-based data transmission process. The method may be executed by a wireless communication node. As shown in FIG. 1, the method includes operations described in blocks S101 to S102.
[0070] In S101, a mapping relation between signal strength ranges and sub-coverages of a satellite is acquired.
[0071] The satellite-based data transmission process may involve a UE-initiated service that requires UE location information over wide coverage beam satellite access, and / or a network-initiated broadcasting or multicasting service over rapidly-moving satellite networks. For example, the satellite-based data transmission process may include, but is not limited to, an emergency request over satellite access, and may be performed via a satellite. The coverage or beam coverage of the satellite may be divided into sub-coverages identified by, for example, sub-beam identities (e.g., spot-beam identities) , geolocation footprints, sub-regions of the satellite beam, or sub-regions of cell coverage of the satellite.
[0072] The mapping relation between different signal strength ranges and different sub-coverages of the satellite may be pre-determined. In one example, the random access node (RAN) deployed with the satellite or a core network (CN) node may estimate the expected signal strength ranges corresponding to multiple sub-coverages of the satellite based on the distance between these sub-coverages and a center (e.g., centroid) of the satellite beam coverage. As another example, different UEs within known sub-coverages of the satellite may measure the signal strengths of DL transmission of the satellite, and then report the result to the RAN of the CN node. Based on the measurement result, the RAN or the CN node may determine the mapping relation between different signal strength ranges and different sub-coverages of the satellite. The mapping relation can also be dynamically updated.
[0073] In addition, given that different orbit types in satellite access may share the same ranges of signal-quality characteristics, this could create ambiguity for the User Equipment (UE) when determining the scope of signal-quality measurements currently under consideration for the ongoing UE emergency session. To address this, the method may further involve acquiring the orbit type of the satellite, wherein the mapping relation corresponds specifically to the acquired orbit type of the satellite. This implies that the mapping relation can be tailored based on a specific orbit type, or alternatively, the method may involve obtaining the mapping relations corresponding to all possible orbit types. This helps to ensure that the mapping relation used is appropriate for the specific orbit type of the satellite involved in the UE's current session, thereby reducing potential ambiguity and enhancing the accuracy of the UE's location determination.
[0074] In S102, a current signal strength of DL transmission of the satellite is determined.
[0075] The UE involved in the satellite-based data transmission process may measure the current signal strength of downlink (DL) transmission of the satellite in real-time, and then notify such information to other relevant nodes in the network. Alternatively, the satellite (or the random access node deployed with the satellite) may measure the current signal strength of uplink (UL) transmission of the satellite in real-time, and then notify such information to other relevant nodes in the network. The mapping relation and the current signal strength are used for determination of an estimated sub-coverage of the satellite in which the UE is located.
[0076] According to the present embodiment, the wireless communication node may acquire the mapping relation between signal strength ranges and sub-coverages of a satellite, and determine the current signal strength of DL transmission of the satellite. Thus, the wireless communication node may determine an actual location (i.e., the estimated sub-coverage of the satellite) in which the UE involved in the satellite-based data transmission process is located based on these information. Alternatively, the wireless communication node may provide these information to another node (e.g., a CN node) for determination of the actual location of the UE. By pinpointing the actual location of the UE, the method ensures accurate UE location determination when providing necessary assistance or help to the UE, while also maintaining the Quality of Service (QoS) requirements for the UE Protocol Data Unit (PDU) when retrieving UE location information from a location server.
[0077] In some embodiments, the method shown in FIG. 1 may further include the operation described in block S103.
[0078] In S103, an estimated sub-coverage of the satellite in which the UE is located is determined based on the mapping relation and the current signal strength.
[0079] It should be understood, the node calculating or determining the estimated sub-coverage of the satellite may be the same as the node acquiring the mapping relation and the current signal strength. Alternatively, the node calculating or determining the estimated sub-coverage of the satellite may be different from the node acquiring the mapping relation and the current signal strength. Different cases will be explained below.
[0080] In one embodiment, wherein the wireless communication node is the UE involved in the satellite-based data transmission process. The operation of determining the current signal strength of downlink transmission of the satellite may include: measuring the current signal strength of downlink transmission of the satellite.
[0081] In this case, the UE may determine the estimate sub-coverage of the satellite based on the mapping relation and the measured signal strength. Alternatively or additionally, the UE may provide the measured signal strength and / or the mapping relation (if it is not known to the RAN or core network) to the RAN on which the satellite is deployed or a core network node for determination of the estimated sub-coverage of the satellite, and then receive an indication for the estimated sub-coverage of the satellite from the RAN or the core network node.
[0082] The mapping relation may be pre-configured to the UE. Alternatively or additionally, the UE may receive, from the RAN on which the satellite is deployed, the mapping relation between the plurality of signal strength ranges and the plurality of sub-coverages of the satellite via a system information block (SIB) or a radio resource control (RRC) configuration.
[0083] The SIB or the RRC configuration may further include a satellite type indication configured to indicate an orbit type of the satellite. Alternatively or additionally, the SIB or the RRC configuration may further include an emergency support indication configured to indicate that the satellite supports emergency communication. In this case, the satellite-based data transmission process belongs to emergency communication.
[0084] In another embodiment, the wireless communication node is a radio access node (RAN) on which the satellite is deployed. The operation of determining the current signal strength of downlink transmission of the satellite may include: receiving, from the UE, the current signal strength of downlink transmission of the satellite.
[0085] In this case, the RAN may determine the estimated sub-coverage of the satellite based on the mapping relation and the received signal strength. Alternatively or additionally, the RAN may provide the received signal strength and / or the mapping relation (if unknown to the Core Network) to a core network node for determining the estimated sub-coverage of the satellite, or provide the mapping relation (if unknown to the UE) to the UE for determining the estimate sub-coverage of the satellite. The RAN may then receive an indication of the estimated sub-coverage of the satellite from the core network node or the UE.
[0086] Moreover, the RAN may further transmit the orbit type of the satellite to the core network node. The orbit type is configured to assist the core network node in determining a positioning method for estimating the sub-coverage of the satellite in which the UE is located. The positioning method may include at least one of the following: Cell Identifier (ID) method; Enhanced Cell ID method; Multi-Round Trip Time (Multi-RTT) method; Downlink Angle of Departure (DL-AoD) or Uplink Angle of Arrival (UL-AoA) method; Downlink Time Difference of Arrival (DL-TDOA) or Uplink Time Difference of Arrival (UL-TDOA) method; or Hybrid positioning method using Global Navigation Satellite System (GNSS) in conjunction with the cellular network. The CN node may select a specific positioning method from the above methods for determining the actual location of the UE. Besides, if the CN node receives the estimated sub-coverage of the satellite in which the UE is located, the CN node may decide whether to use this estimated result, or select one of the above-mentioned positioning methods to determine the actual location of the UE to replace this estimated result.
[0087] In yet another embodiment, the wireless communication node is a core network node. The operation of determining the current signal strength of downlink transmission of the satellite may include: receiving, from the UE or a radio access node (RAN) on which the satellite is deployed, the current signal strength of downlink transmission of the satellite.
[0088] Accordingly, the CN node may determine the estimated sub-coverage of the satellite in which the UE is located by itself based on the mapping relation and the current signal strength. Then the CN node may notify the estimated result to the RAN and / or the UE for data transmission.
[0089] Moreover, the CN node may further receive, from the UE or the RAN, an orbit type of the satellite, and determine another positioning method for determining the estimated sub-coverage of the satellite in which the UE is located based on the orbit type of the satellite instead of using the result generated based on the mapping relation and the current signal strength.
[0090] The satellite-based data transmission process may be an emergency call / request / session. A more detailed explanation about locating a UE during an emergency request over satellite access is given below. The solution involves dividing the satellite or beam coverage into smaller beams, each identified by a sub-beam identity, associated with a geolocation footprint and a range of signal strength.
[0091] The process entails measuring the actual signal quality of the UE and identifying the sub-beam with the closest signal strength and / or the shortest distance between the UE's geometric location (selected based on signal strength) and the geometric center of all sub-beam regions or geolocations. FIG. 2 shows an exemplary scenario where the satellite coverage is divided into four sub-regions including r1, r2, r3, and r4.
[0092] The solution leverages the exchange of key signaling parameters, such as an emergency support over satellite type indicator, an emergency support indication in conjunction with a satellite orbit type (LEO, GEO, MEO, or HEO) , and a predefined mapping between geolocations, identities of sub-regions of a satellite-beam coverage, and signal-quality ranges or signal strength tiers. Additionally, a UE or satellite time advance (TA) measurement is considered. These parameters are exchanged between the UE, a satellite-enabled Radio Access Network (RAN) node, and a core network node. Any of these nodes can use some or all of these signaling parameters to address the challenge of locating a UE during an emergency request over satellite access.
[0093] In one embodiment, a predefined mapping between geolocations, identities of sub-regions of a satellite-beam coverage, and signal-quality ranges or signal strength tiers is used by the UE, the RAN node, or a core network node to determine the sub-region of the beam where the UE requesting emergency access is located.
[0094] For instance, to determine such a region of a beam, the UE compares the signal strength measured at the time of requesting emergency access against the pre-determined geolocation-signal strength mapping provided by the RAN node. This comparison allows the UE to identify the sub-beam with the closest signal strength and / or the shortest distance between the UE's estimated geometric location and the centroid of the sub-beams.
[0095] Given that different orbit types in satellite access may share the same ranges of signal-quality characteristics, this could create ambiguity for the User Equipment (UE) when determining the scope of signal-quality measurements currently under consideration for the ongoing UE emergency session. Table 2 illustrates an example of measureable signal-quality ranges for LEO (Low Earth Orbit) , MEO (Medium Earth Orbit) and GEO (Geostationary Earth Orbit) satellites. Table 2
[0096] An emergency support over a satellite type indicator or an emergency support along with satellite orbit type indications (LEO, GEO, MEO, or HEO) are exchanged between the user equipment, the satellite-enabled RAN node, and / or the core network node. This exchange assists in determining the scope of the signal-quality measurement range under consideration for locating the UE requesting emergency access. For instance, if a RAN node provides an emergency support over a satellite type indicator or an emergency support indication along with a LEO satellite orbit type to the UE or AMF, these nodes understand that the last row of Table 2 is considered as the measurement scope range for the beam or satellite when determining the sub-region of the beam where the UE requesting emergency access is located or residing.
[0097] The proposed solution involves dividing the satellite beam or cell coverage into smaller regions or sub-beams (rk , k=1, 2, 3…n sub-beam) , each with a center (r1 (x1, y1, z1) , r2 (x2, y2, z2) …., r1 (xn, yn, zn) ) , and a coverage radius. The solution also divides the measurable signal strength ranges per satellite type (i.e., LEO, GEO, MEO) into sub-ranges (e.g., as given in Table 2) . For example, the actual measurable range of satellite EIRP by the UE for a LEO type satellite is between [20–40 dBW] . This range is divided into sub-ranges [35–40] , [30-35] , [25-30] , and [20-25] , as shown in Table 3a. Table 3a. Exemplary sub-regions for LEO satellite
[0098] Similarly, Table 3b and Table 3c show exemplary sub-regions for MEO and GEO satellite. Table 3b. Exemplary sub-regions for MEO satellite Table 3c. Exemplary sub-regions for GEO satellite
[0099] Subsequently, a mapping is constructed between the sub-beams, geometric locations, signal strength sub-ranges, and / or the initial weighting values. This mapping is used by the UE, RAN, or CN node for selecting the sub-beam where the UE is located. In addition, the weighting values may be used by for verifying that the UE sub-beam has been correctly selected, and / or providing more detailed information about the UE's location, which will be elaborated below.
[0100] In one approach, initial weighting values can be assigned by giving higher weighting to sub-beams / geolocations closer to the center of the satellite beam and lower weighting to those farther from the center.
[0101] In another approach, the initial mapping can be constructed based on actual historical regional geometrical measurements. For instance, satellite dishes distributed across various ground locations measure different levels of satellite signal strength. The initial mapping can then be constructed between the geometric region locations of these dishes (centroids, coverage radius) and their actual measured signal strength, with weights assigned based on such measurements.
[0102] After the User Equipment (UE) measures the actual signal strength received at its current physical location, it selects the sub-beam where it can measure the signal as an initial estimate of its location.
[0103] a) If the UE measures a signal strength within the highest sub-range, it uses the initial weighting values to verify that the sub-beam is correctly selected and / or to provide more detailed information about its location.
[0104] b) If the UE measures a signal strength below the highest sub-range, it selects the sub-beam based on its actual measured signal strength. In this case, when verifying the selected sub-beam or providing more detailed location information, the UE updates the initial weighting values. It assigns the highest weighting value to the specific sub-beam where the signal was measured and lower weighting values to the other sub-beams. This adjustment reflects the fact that, regardless of signal strength in other sub-beams, the UE cannot measure or report signals there due to its antenna's physical location within the selected sub-beam.
[0105] Based on the initial or updated weighting values mapping table, the UE, RAN node, and / or core network node verify the selected sub-beam by selecting / assigning random points within each sub-beam (e.g., (xr1…n, yr1..n, zr1..n) , located near the centroid of each sub-beam) . The verification process involves finding the point with the minimum weighted sum of horizontal and / or vertical distances to the centroids of all other sub-beams. For example, the weighted Euclidean distance can be used to evaluate the minimum weighted sum cost:
[0106] In the above formula, or TA×C / 2, if TA is available (TA stands for Time Advance) . The speed of light is denoted by 'C' . For balance, the distance is converted from kilometers to meters.
[0107] Consider an exemplary scenario of a model for locating a UE requesting emergency access under a satellite with (longitude, latitude, and coverage radius) as (0, 0, 100 km) . In this scenario, the satellite beam coverage is divided into four sub-beams regions or geolocations, each with a centroid and identity. The range of constellation type measurement is also divided into four ranges, such as [35–40] , [30-35] , [25-30] , and [20-25] for LEO type satellite EIRP measurements. This same division can be applied to other measurement types [RSRQ, RSRP, SNR] or other satellite types (GEO, MEO) . Each of these ranges is linked to a sub-beam identity (r) , a centroid, and / or a weighting tier as follows:
[0108] a) Sub-beam r1: Centroid at (25, 25, 10) , range [35–40] , weight = 0.4
[0109] b) Sub-beam r2: Centroid at (75, 25, 10) , range [30-35] , weight = 0.3
[0110] c) Sub-beam r3: Centroid at (50, 75, 10) , range [25-30] , weight = 0.2
[0111] d) Sub-beam r4: Centroid at (75, 75, 10) , range [20-25] , weight = 0.1
[0112] In this example, the above mapping information is provided to the UE, for example, in emergency support related signaling. After receiving the related signaling, the UE performs a signal quality strength measurement at its physical location. For instance, let's assume the UE measures a 37dBW signal strength. The UE then compares this measured signal strength against the provided initial mapping table from the RAN node (e.g., Table 3a) . Based on this comparison, the UE finds that the measured 37dBW falls within the [35–40] range, which corresponds to sub-beam r1 with a centroid at (25, 25, 10) . Thus, the UE selects the sub-beam r1 centroid at (25, 25, 10) as a possible initial estimate for its actual location.
[0113] To further verify that the UE sub-beam is correctly selected and / or to provide more detailed information (such as an estimated distance from the selected centroid) , the UE may select one random point within each sub-beam's region (excluding the centroids) . For example, assuming the following random points positioned at (horizontal radius, vertical) distance meters from the centroids were selected by UE:
[0114] a) Sub-beam r1: P1 (28, 22, 12) , positioned at (4.24, 2) from r1 centroid at (25, 25, 10)
[0115] b) Sub-beam r2: P2 (70, 30, 8) , positioned at (7.07, 2) meters from r2 centroid (75, 25, 10)
[0116] c) Sub-beam r3: P3 (55, 70, 15) , positioned at (7.07, 5) meters from r3 centroid (50, 75, 10)
[0117] d) Sub-beam r4: P4 (80, 80, 5) , located at (7.07, 5) meters from r4 centroid (75, 75, 10)
[0118] Using the initial weight values (i.e., 0.4 for r1, 0.3 for r2, 0.2 for r3, and 0.1 for r4) because the UE measured signal strength is within the highest sub-range [35–40] , the weighted sum cost of these points, computed based on the weighted Euclidean distance sum, is given in Table 4. From this table, the minimum sum is for the point P1 (28, 22, 12) in r1 with a cost of 31, 638.47 m. Therefore, the sub-beam r1 and / or the point P1 (28, 22, 12) can be provided as the granularity for UE location for the initiated session. Table 4. Weighted Euclidean Distance Sum for Randomly Selected Points
[0119] In another example, assume the UE measures a signal strength falling within any of the ranges [30-35] , [25-30] , or [20-25] . Let's assume the UE is currently located in sub-beam r2 and measures a signal strength falling within the range [30-35] , specifically 31 dBW. In this case, the measurable UE signal for other sub-beams (r1, r3, and r4) can be set to zero because the UE is physically unable to measure signals from those sub-beams. Only UEs located in those sub-beams can measure their respective signals. Based on this, the weighting table should be updated by assigning the highest weighting value [0.4] to r2 while distributing the remaining weighting values to the other sub-beams randomly (e.g., 0.3 for r1, 0.4 for r2, 0.2 for r3 and 0.1 for r4, as shown in Table 5) . Table 5. Updated Weights Mapping Table based on Actual UE Measurement
[0120] Using the updated weighting values mapping table, the weighted sum cost of these points, computed based on the weighted Euclidean distance sum, is shown in Table 6. From this table, the minimum sum is for the point P2 (70, 30, 8) in r2 with a cost of 31, 645.96 m. Therefore, the sub-beam r2 and / or the point P2 (70, 30, 8) can be provided as granularity for the UE location for the initiated session. Table 6. Weighted Euclidean Distance Sum for Randomly Selected Points
[0121] In an alternative solution of this embodiment, the UE or RAN node provides the core network node with the UE's measured signal strength and / or the satellite orbital type indication. Then, the core network node may either determine the UE location for the emergency sessions or may coordinate with another core network node, such as a location management function (LMF) , to select a positioning method suitable for determining the UE's location for the emergency session. This selection is based on the satellite orbit type and involves classifying positioning methods based on their latency budgets (which can be acquired in the emergency session request from the UE) . The most suitable method is then selected to meet the UE emergency session's Quality of Service (QoS) or latency requirement, as detailed in Table 7. Table 7. Positioning Methods Classified Based on Their Speed &Accuracy Comparison
[0122] For example, the core network node (e.g., Location Management Function, LMF) may dynamically select the positioning method based on the satellite orbit type to optimize response time and / or location accuracy for an emergency session. Examples are given below.
[0123] a) GEO Satellite Indication: If a GEO satellite is indicated, where latency is high (~500 ms) , the core network node prioritizes rapid response by selecting Cell ID positioning with approximately 100 km accuracy. Additionally, A-GNSS may be utilized when available to refine the accuracy to 3–10 meters.
[0124] b) MEO Satellite Indication: For MEO satellites, which have moderate latency (150–300 ms) , the core network node enables more precise positioning by coordinating multi-RTT (Round Trip Time) measurements between the UE and multiple satellites, achieving accuracy in the range of 50–500 meters. Alternatively, DL-TDOA (Downlink Time Difference of Arrival) may be employed, offering 100–1000 meters accuracy, provided satellite synchronization permits.
[0125] c) LEO Satellite Indication: In the case of LEO satellites, characterized by low latency (20–50 ms) , the core network node leverages the favorable conditions to implement high-accuracy positioning. It typically selects a hybrid method, combining GNSS (3–10 meters accuracy) with LEO Timing Advance (TA) for real-time updates. Alternatively, UL-TDOA (Uplink Time Difference of Arrival) may be activated, achieving 20–100 meters accuracy, if the UE supports uplink signaling.
[0126] By intelligently evaluating the satellite orbit type and network conditions, the core network node ensures that emergency services receive the most effective positioning data-balancing urgency with precision based on the satellite infrastructure in use (Table 8) . Table 8. Example of Core network node decision Table based on orbit type indication
[0127] FIG. 3 illustrates an example of the whole signaling for determining the actual geolocation of UE. In this part, the details of signaling and procedures for the approach used to determine the UE's actual geolocation during an emergency session are explained. The approach involves exchanging critical information between the User Equipment (UE) , the satellite-enabled Radio Access Network (RAN) node, or a core network node to determine the sub-region of the beam where the UE requesting emergency access is located.
[0128] For example, a gNB may provide, within a System Information Block (SIB) or a Radio Resource Control (RRC) configuration, a predefined mapping between geometric geolocations, identities of satellite sub-beams, signal-quality ranges, signal strength weighting tiers, emergency support over a satellite type indicator, or emergency support along with the satellite orbit type (LEO, GEO, MEO, or HEO) indications.
[0129] Upon reception of such information by the UE, one of the following options may apply:
[0130] 1) UE Determines Sub-Beam Region:
[0131] The UE measures the signal strength and compares the measured signal strength against the predefined geolocations, identities of satellite sub-beam coverage, signal-quality ranges, and / or signal strength weighting tiers mapping to determine its actual sub-beam region or geometric location. It then provides this sub-beam region information to a gNB node via an RRC connection message or to an AMF node via a Non-Access Stratum (NAS) connection message as a granularity for UE location during the initiated emergency session.
[0132] 2) gNB Determines Sub-Beam Region:
[0133] The UE measures the signal strength and provides it to the gNB. The gNB node determines the UE's sub-beam identity by comparing the UE's signal strength measurements against the locally predefined geolocations, identities of satellite sub-beam coverage, signal-quality ranges, and / or signal strength weighting tiers mapping. This location information is then provided to the AMF via a UE N2 initial message as a granularity for UE location during the initiated emergency session.
[0134] 3) AMF Determines Location or Delegates to LMF:
[0135] The UE or RAN node provides the AMF with the UE-measured or gNB-measured signal strength and / or the satellite orbital type indication. The AMF may: a) Determine the UE location for the emergency session; or b) Forward the UE / gNB measurements and the satellite orbit type parameter to the Location Management Function (LMF) to select the lowest-latency positioning method suitable for determining the UE's location during the emergency session. This ensures accurate UE location for emergency assistance.
[0136] The signaling for determining the UE's actual geolocation during an emergency session may follow at least one of the signaling methods depicted in FIG. 3, with procedures described by the following steps:
[0137] 1) Provision of Mapping Information:
[0138] The UE is provided by the gNB / eNB, within a SIB, a predefined mapping between geometric geolocations, identities of satellite sub-beams, signal-quality ranges, signal strength weighting tiers, emergency support over a satellite type indicator, or emergency support along with the satellite orbit type (LEO, GEO, MEO, or HEO) indications.
[0139] 2) Identification of Emergency Call:
[0140] The UE identifies an emergency call when a user dials an emergency number (e.g., 911, 112, 110) or triggers an SOS feature. Based on the emergency support over satellite indicator provided within the SIB, the UE measures the downlink channel signal strength and compares the measured signal against the predefined geolocations, identities of satellite sub-beam coverage, signal-quality ranges, and / or signal strength weighting tiers mapping to determine its actual sub-beam region.
[0141] 3) RRC Connection Initiation:
[0142] The UE initiates an RRC connection with higher priority, skipping non-critical security procedures (e.g., full authentication) to minimize setup time. It establishes an SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer) with the gNB / eNB for emergency traffic, indicating the measured signal strength or the determined actual sub-beam region or geometric location and / or updates the mapping table.
[0143] 4) Capability Transfer to Core Network:
[0144] The UE transfers its capability to the 5GC-connected and IMS system, indicating within the capability transfer signaling its measured signal strength and the determined UE location information for the emergency session.
[0145] 5) Sub-Beam Identity Determination by gNB / eNB:
[0146] The gNB / eNB node determines the UE's sub-beam identity by comparing the UE's signal strength measurements against the locally predefined geolocations, identities of satellite sub-beam coverage, signal-quality ranges, and / or signal strength weighting tiers mapping.
[0147] 6) N2 InitialUEMessage to AMF / MME:
[0148] The gNB / eNB sends an N2 InitialUEMessage to the AMF / MME, including: Emergency indication (in RRC EstablishmentCause) , UserLocationInfo (UE measured signal strength or determined actual sub-beam region or geometric location as a granularity for UE location for the initiated UE emergency session, or provides the updated mapping table) , UE identity (5G-S-TMSI or SUCI) .
[0149] 7) gNB / eNB Sends UE N2 Initial Message:
[0150] Alternatively, the gNB / eNB sends a UE N2 initial message including the satellite orbit type to the AMF to assist the AMF in selecting a positioning method suitable for determining the UE's location for this emergency session, ensuring an accurate UE location for emergency assistance.
[0151] 8) Emergency PDU Session Establishment:
[0152] The UE triggers an emergency PDU session establishment with 5GC (AMF / SMF / MME) , using a default emergency DNN and prioritized QoS parameters (e.g., 5QI for voice) . The UE may indicate within this step its measured signal strength or determined actual sub-beam region or geometric location, and / or updated mapping table to the AMF within the IMS PDU session to ensure an accurate UE location for emergency assistance.
[0153] 9) AMF / MME Determines Location:
[0154] The AMF / MME determines the sub-beam or geometric location of the UE requesting emergency access or selects a positioning method suitable for the indicated satellite type and emergency session QoS requirement. It validates the emergency request, assigns emergency-specific GUAMI and 5G-GUTI, and triggers emergency PDU session setup via the SMF. The UPF guarantees low-latency data transfer for the emergency session.
[0155] 10) P-CSCF Discovery:
[0156] The UE performs P-CSCF discovery (via DHCP / DNS or 5GC interaction) . If credentials are available, it sends a SIP REGISTER with an emergency indication and the geometric location of the UE for the emergency session. The S-CSCF / E-CSCF processes the registration, bypassing normal authentication if needed.
[0157] 11) SIP INVITE to P-CSCF:
[0158] The UE sends a SIP INVITE with an emergency URN (e.g., "urn: service: sos" ) to the P-CSCF, which routes it to the E-CSCF. The E-CSCF uses the location data (i.e., the geometric location of the UE for the emergency session) to select the nearest PSAP and establishes the IMS emergency call. The PSAP system receives the emergency call with prioritized resources. The 5GC maintains strict QoS (low latency, high reliability) , and the UE may pre-empt non-emergency sessions if needed. The call remains active until termination by the user or PSAP. This flow ensures rapid, reliable emergency communication in 4G / 5G systems.
[0159] It should be understood, in the above process, the method of using the orbit type by the LMF to select a suitable positioning method for the UE may be implemented independently. FIG. 4 shows a flowchart of a method for determining a geolocation of a user equipment (UE) in satellite-based data transmission process. The method may be executed by a core network node, such as the LMF node. As shown in FIG. 4, the method includes operations described in blocks S201 to S203.
[0160] In S201, an orbit type of a satellite for the UE to perform the satellite-based data transmission process is acquired.
[0161] The orbit type of the satellite may include one of LEO, MEO, GEO, or HEO.
[0162] In S202, a latency requirement for the satellite-based data transmission process is acquired.
[0163] For example, the UE or the RAN node initiating the satellite-based data transmission process may include the latency requirement in a signaling transmitted to the CN node.
[0164] In S203, a positioning method for determining the geolocation of the UE based on the orbit type of the satellite and the latency requirement is selected.
[0165] The positioning method may include at least one of: cell identifier (ID) method; enhanced cell ID method; Multi-Round Trip Time (Multi-RTT) method; Downlink Angle of Departure (DL-AoD) or Uplink Angle or Arrival (UL-AOA) method; Downlink Time Difference of Arrival (DL-TDOA) or Uplink Time Difference of Arrival (UL-TDOA) method; or hybrid positioning method by using Global Navigation Satellite System (GNSS) together with cellular network.
[0166] The CN node may select a specific positioning method from the above methods for determining the actual location of the UE. Besides, if the CN node receives the estimated sub-coverage of the satellite in which the UE is located, the CN node may decide whether to use this estimated result, or select one of the above-mentioned positioning methods to determine the actual location of the UE to replace this estimated result.
[0167] By intelligently evaluating the satellite orbit type and network conditions, the core network node ensures that emergency services receive the most effective positioning data-balancing urgency with precision based on the satellite infrastructure in use
[0168] The present disclosure further provides a satellite-based data transmission method to solve the issue of failure to deliver warning messages to UE or missing of warning &emergency calls by UE. FIG. 5 shows a flowchart of a satellite-based data transmission method according to an embodiment of the present disclosure. The method may be executed by a wireless communication node. As shown in FIG. 5, the method includes operations described in blocks S301 to S302.
[0169] In S301, an impacted geolocation corresponding to a request for a satellite-based data or message transmission is acquired.
[0170] The satellite-based data or message transmission may include a downlink broadcast, a multicast or group-cast transmission. The satellite-based data or message transmission may be, for example but not limited to, emergency call, emergency notification, emergency call paging messages, or warning messages. The request for the satellite-based data or message transmission may be generated by the wireless communication node itself, or by other nodes such as a UE, a RAN node, or a core network node.
[0171] The impacted geolocation corresponding to the satellite-based data or message transmission may be the geolocation where a UE initiates a request for the satellite-based data or message transmission. For example, the geolocation of the UE may be determined based on the methods described in foregoing sections of the present disclosure by using the measured signal strength or by using the specific positioning method determined by LMF.
[0172] Alternatively or additionally, the impacted geolocation corresponding to the satellite-based data or message transmission may be a region or area within which a notification or warning messages should be broadcasted. Such information may be determined by a RAN node or a core network node. For instance, in scenarios such as earthquakes or tsunamis, it becomes crucial to notify UEs within a specific area. In such cases, the impacted geolocation may correspond to the geographical region expected to be affected by the natural disaster. The system can identify this area based on data from external sources such as seismic monitoring stations or tsunami warning centers. Upon identifying the impacted geolocation, the system can initiate a satellite-based data or message transmission to broadcast emergency notifications or warning messages to all UEs within the defined area. These messages can include critical information about the impending disaster, safety instructions, and evacuation routes.
[0173] In S302, whether the impacted geolocation falls within a coverage range of a first satellite that is connected to the wireless communication node is checked.
[0174] The wireless communication node may be a RAN node or a core network node. The first satellite is connected to the wireless communication node at the time the wireless communication node verifies whether the impacted geolocation falls within its coverage.
[0175] The coverage range of the first satellite may be pre-determined. Alternatively or additionally, the wireless communication node may acquire ephemeris information and / or orbital parameters of the first satellite, and then determine the coverage range of the first satellite based on the ephemeris information and / or the orbital parameters.
[0176] In one embodiment, the operation of checking whether the impacted geolocation falls within the coverage range of the first satellite may include: comparing a distance between a centroid of the impacted geolocation and a centroid of the coverage range of the first satellite with the coverage range. When the distance between the centroid of the impacted geolocation and the centroid of the coverage range of the first satellite is less than or equal to the coverage range, it is determined that the geolocation falls within the coverage range of the first satellite.
[0177] In another embodiment, the impacted geolocation may include a specific area (e.g., represented by a center and a radius) . It may be compared with the coverage range of the first satellite such that it can be determined whether the impacted geolocation falls within the coverage range of the first satellite, partially outside the coverage range of the first satellite, or fully outside the coverage range of the first satellite.
[0178] According to the present embodiment, the wireless communication node (e.g., a core network node) may acquire the impacted geolocation corresponding to the satellite-based data or message transmission, and then verify whether the impacted geolocation falls within the coverage range of the first satellite that is connected to the wireless communication node. The result of this verification process can be utilized for further decision-making, such as selecting the most suitable data transmission method. Therefore, the system can effectively prevent issues such as missed transmissions, interference, or transmission failures. This not only enhances the reliability of the communication process but also ensures that critical emergency information reaches all relevant UEs promptly and accurately.
[0179] In one embodiment, if the impacted geolocation falls within the coverage range of the first satellite, the wireless network node may decide to transmit the satellite-based data or message transmission via the first satellite.
[0180] In some embodiments, the method shown in FIG. 5 may further include the operation described in block S303.
[0181] In S303, the satellite-based data or message transmission is pre-emptively or repetitively transmitted, retransmitted or rerouted to the connected node or nodes.
[0182] It should be understood, the node performing data transmission for the satellite-based data or message transmission may be the same as the node deciding whether the impacted geolocation falls within the coverage range of the first satellite. Alternatively, the node performing data transmission for the satellite-based data or message transmission may be different from the node deciding whether the impacted geolocation falls within the coverage range of the first satellite. Different cases will be explained below.
[0183] In one embodiment, the wireless communication node may determine a time window for data transmission corresponding to the satellite-based data or message transmission, wherein the time window starts from a last satellite handover. The wireless communication node may also determine a satellite change time between two satellite handovers. When the time window is less than the satellite change time, the wireless communication node may transmit the satellite-based data or message transmission via the first satellite. Alternatively or additionally, when the time window is larger than the satellite change time, the wireless communication node may transmit the satellite-based data or message transmission via a second satellite to which the first satellite is to be handed over or by using Inter-Satellite Link (ISL) routing.
[0184] Specifically, the satellite change time may be determined based on a distance between the first satellite and the second satellite, and a satellite orbital speed.
[0185] Furthermore, the wireless communication node may acquire a priority level of the satellite-based data or message transmission.
[0186] In another embodiment, the wireless communication node may determine a satellite change time between two satellites on-ground coverage change, and determine a repetition number based on a required delivery time of the satellite-based data or message transmission, the satellite change time and an interruption time. Then the wireless communication node may repetitively transmit the satellite-based data or message transmission to the first satellite and / or a second satellite to which the first satellite is to be handed over or has been handed over. The interruption time is a time period for reception of transmission failure indication.
[0187] In another embodiment, if the impacted geolocation falls outside the coverage range of the first satellite, the wireless communication node may buffer or instruct the first satellite to buffer the satellite-based data or message transmission, and re-transmit the satellite-based data or message transmission via a second satellite to which the first satellite has been handed over.
[0188] In another embodiment, if the impacted geolocation falls within both coverage ranges of the first satellite and a second satellite, the wireless communication node may select either the first satellite or the second satellite for transmission of the satellite-based data or message transmission. Alternatively, the wireless communication node may rout the satellite-based data or message transmission through Inter-Satellite Link (ISL) between the first satellite and the second satellite.
[0189] In another embodiment, the wireless communication node may transmitting one or more paging messages to a UE. When a number of the one or more paging messages reaches a first threshold or no response for the one or more paging messages is received within a pre-defined time, the wireless communication node may initiate a robust notification procedure for the satellite-based data or message transmission.
[0190] This embodiment details the solution which may address the challenges of delay, interruption, or potential loss of emergency messages and / or paging call notifications in rapidly-moving satellite networks. The solution relies on an exchange from an emergency or call notification node such as IMS or CBS to a core network node (e.g., an AMF) targeting or impacting a warning broadcasting or emergency call paging notification area / areas defined by a set of one or more geolocations or geometric shapes with longitude, latitude, and / or a coverage radius.
[0191] Then, the core network node checks in real-time whether the targeted / impacted warning broadcasting or emergency call paging notification area / areas fall within the coverage of the set of the satellite-enabled nodes that are currently connected to the core network node.
[0192] To check in real-time whether these area / areas are falling within the coverage of the set of satellite-enabled RAN nodes that are currently connected to the core network node, the core network node may invoke the satellite-enabled RAN node to exchange at least one key parameter such as a satellite orbital type (LEO, GEO, MEO, HEO) , a RAN node status (on-board / on-ground) , satellite coverage details (longitude, latitude, coverage radius) , satellite constellation information (altitude, satellite count, orbital dynamics) , and / or satellite ephemeris information such as the speed or location of the satellite at a given time. Then using these parameters, the core network node performs a real-time check to determine whether the impacted warning broadcasting or emergency call paging area / areas are falling within the coverage of the set of the satellite-enabled RAN nodes that are currently connected based on the following steps:
[0193] 1) Satellites Coverage Radius Tracking: This is done by calculating in real-time for each connected satellite, the coverage radius or footprint (i.e., the area that the satellite covers on the ground at a given time) using the satellite ephemeris information and / or the orbital parameters such as the altitude of the satellite. FIG. 6 shows a method for determining the satellite coverage radius, which is calculated as: where R is the radius of the Earth (≈ 6, 371 km) , and h is the altitude of the satellite (in km) .
[0194] 2) Geolocations Satellites Association Monitoring: This involves continuously checking in real-time which geolocations are covered by which satellites. It is done by calculating for each satellite in a set of satellites currently connected to the core network node, the distance between impacted area geolocations centroids at (φ1, λ1) , and satellites beams centroids at (φ2, λ2) e.g., using the great-circle distance between two points as given below: d (s, g) =2*R·arcsin ( (φ1, λ1) , (φ2, λ2) )
[0195] In the above formula, R is the radius of the sphere (e.g., Earth’s radius ≈ 6, 371 km) ; (φ1, λ1) are the satellite coordinates (latitude, longitude in radians) ; (φ2, λ2) are the geolocation coordinates (latitude, longitude in radians) .
[0196] Then, deciding based on comparing the great-circle distance between impacted area geolocations centroids and satellites beams centroids d (s, g) with satellite coverage radius R (s) : d (s, g) ≤ Rs
[0197] Based on the above check; if the great-circle distance between impacted area geolocations centroids and satellite centroids is less than or equal to the satellite coverage radius R (s) , it means that the impacted area geolocations are falling within the coverage of at least one of the currently connected satellites to the core network node. FIG. 7 shows an example of an impacted warning or emergency call paging area falling within the coverage of one satellite-enabled RAN node connected to the core network node.
[0198] Then, the core network node immediately broadcasts the warning message or the emergency call paging notification via at least one of those satellites.
[0199] On the other hand, if the great-circle distance between impacted area geolocations centroids and satellite centroids is greater than the satellite coverage radius, it means that the target area is partially or fully outside the coverage of the currently connected satellites. And / or if the satellite node in which the target area emergency warning is broadcasted is about to be handed over or charged due to orbital movement, then the core network node may evaluate based on the satellite orbital type (LEO, GEO, MEO, HEO) , a RAN node status (on-board / on-ground) , satellite constellation information (altitude, satellite count, orbital dynamics) , and / or satellite ephemeris information, the average distance between satellites, the satellite orbital velocity or speed at a given time, and assess the satellite change or handover time for the given satellite constellation. FIG. 8 shows an example of an impacted warning or emergency call paging area partially or fully falling outside the coverage of one satellite-enabled RAN node connected to the core network node.
[0200] The satellite change or handover time may be calculated as: wherein (V) Distance is the distance between the first satellite and the second satellite to which the first satellite is to be handed over or has been handed over.
[0201] After having acquired the satellite handover time or changing information as given above, the core network node may perform at least one of the following operations:
[0202] 1) Initiate repetitive or pre-emptive sending of the warning message and / or emergency call paging before the satellite change happens.
[0203] 2) Perform a re-transmitting or re-routing of the warning message and / or emergency call after the satellite change happens while maintaining the delivery time requirements (i.e., of PWS delivery and / or IMS call setup time delay constraints) of the warning message and / or the emergency call paging.
[0204] 3) Determine the number of paging re-tries that a RAN node shall use for the PHY channel toward the UE for a robust paging notification delivery.
[0205] Different operations as listed above will be introduced separately in subsequent sections.
[0206] (1) Sending the warning message and / or emergency call paging Pre-emptively or repetitively before satellite change
[0207] This operation considers the case when a satellite is about to move from covering a specific geographical area on Earth to a new one. In this case, if the targeted / impacted area by the warning and / or emergency calls paging notification messages falls within such a satellite, the delivery of these notification messages will be delayed or interrupted. To address this, the core network node may initiate repetitive or pre-emptive sending of the notification messages before the handover occurs.
[0208] In one embodiment, the core network node may initiate pre-emptive sending of the notification messages. Explanation is given below.
[0209] This option relies on the ability to predict the satellite changes before they occur. The prediction is mainly done by assessing the satellite changing time (T_change) for the given satellite constellation. After assessing this time change, the core network node can pre-emptively send the warning and / or emergency calls paging notification messages before the change happens by setting a prediction time window starting after the last satellite change and keep sending notification messages until the window size becomes equal to the satellite changing time (T_change) as explained below (as shown in FIG. 9) .
[0210] Given:
[0211] a) T_predict: Time window for predicting satellite changes (e.g., 2.9 seconds) after the last satellite change;
[0212] b) T_change: Time until the satellite changes (calculated based on satellite value, Constellation, Ephemeris information) .
[0213] c) T_delivery: Maximum allowed delivery time (4 seconds for PWS messages) .
[0214] If T_predict ≤ T_change, the core network node will pre-emptively send the warning and / or emergency calls paging notification messages through the current available satellites while T_delivery is still maintained (i.e., less than 4 seconds for PWS warning messages) .
[0215] On the other hand, if T_predict becomes larger than T_change or the pre-emptive sending fails, the core network node may use redundant satellites, buffering, or ISL routing to ensure delivery of the messages.
[0216] To effectively maintain T_delivery while pre-emptively sending notification messages, a priority level could be assigned for the warning messages and emergency calls paging notification. Within the window T_predict, the data or message transmission with the highest priority level (e.g., the PWS as shown in the Table 9) is pre-emptively transmitted. When the data or message transmission with the highest priority level has been successfully transmitted, the rest of the window T_predict may be utilized for transmission with the second highest priority level. For example, the highest priority level (e.g., priority level 1) , QoS traffic profiles, and / or QoS class identifier could be assigned for emergency and / or calls paging notification messages flow or bearers as given in Table 9. In the RAN layer: warning messages and emergency calls paging notification SIB Broadcasting Radio Bearer are treated according to the high priority to ensure reliability provided from the core network. This will ensure uninterrupted and timely delivery of emergency calls paging notification messages before satellites become unavailable, while maintaining the PWS delivery and / or IMS call setup time requirements constraints. Table 9. Example of Priority Level Assigned for Emergency and / or Call Paging Notification
[0217] In another embodiment, the core network node may initiate repetitive sending of the notification messages, for example, via redundant satellites.
[0218] This option involves repeating the transmission of the emergency and / or calls paging notification messages multiple times through all available satellites (including both the old and new satellites) simultaneously. This option first evaluates the interruption time, T_interrupt, by sending an initial warning or call paging message and recording the time until receiving an indication of a failure of the warning or paging call message from at least one of the connected satellites. Then, utilizing the interruption time, T_interrupt, along with the maximum allowed delivery duration of the warning or call notifications, T_delivery, and satellite change time, T_change, as calculated above, the number of repetitions, N, required to ensure the delivery of the message is computed as follows:
[0219] Based on the computed number of repetitions, N, the core network node repetitively transmits the warnings and / or emergency call paging notification messages N times through all available satellites (including both the old and new satellites) simultaneously. This ensures that the notification message delivery is guaranteed even during or after the satellite change. It should be understood that, in some cases, the core network node may repetitively transmits the warnings and / or emergency call paging notification messages N times only through the “new” satellites or the “old” satellites.
[0220] (2) Retransmitting / Re-routing the warning message and / or emergency call paging during or after the satellite change
[0221] This operation considers the case when a satellite is moving or has already moved from covering a specific geographical area on Earth to a new one. The options in this embodiment primarily focus on addressing the interruption issues of warnings and / or emergency call paging notification messages by either retransmitting or rerouting the notification messages, while maintaining strict delivery delay constraints for PWS or IMS call setup delivery.
[0222] In one embodiment, this operation may be achieved by buffering the notification and re-transmission.
[0223] This option relies on utilizing the interruption time, T_interrupt, the maximum allowed delivery duration of the warning or call notifications, T_delivery, and satellite change time, T_change, as calculated above, to compute the number of retransmissions, N, required to ensure the delivery of the notification message. The option includes:
[0224] a) Evaluating the interruption time based on satellite change dynamics as given above.
[0225] b) Computing the number of retransmissions, N, required to ensure an effective delivery as above.
[0226] Based on the computed number of required retransmissions, N, the core network node will buffer or instruct the connected satellite RAN nodes to buffer and retransmit the warnings and / or emergency call paging notification messages N times through a secondary satellite if delivery is interrupted due to primary satellite change. This will guarantee a reliable notification message delivery during or after the satellite change.
[0227] In another embodiment, this operation may be achieved by using Inter-Satellite Link (ISL) or selective routing.
[0228] This option is similar to repetitive transmission via redundant satellites option. However, it tries to identify whether the target notification message delivery geolocation (s) is / are covered by multiple satellites at a time (fall within an overlapping coverage of two satellite RAN nodes, as shown in FIG. 10) . FIG. 10 shows an example of an impacted warning or emergency call paging area falling within an overlapped coverage of two satellite-enabled RAN nodes.
[0229] If the target geolocation (s) is / are falling within an overlapping coverage of two satellite RAN nodes, instead of transmitting the warnings and / or emergency call paging notification messages to all the connected satellites to the core network node as in the case of repetitive transmission, the core network node may select to route the notification messages through only one satellite to reduce signaling overheads or to ensure saving bandwidth and resources for other traffic types in that satellite. On the other hand, if there are active inter-satellite links (ISLs) , the core network node may use inter-satellite links (ISL) to route notification messages through alternative satellites if the primary satellite is changed. Additionally, preemptive sending can be used along with the option of routing via ISLs to route messages through alternative satellites if the primary satellite is about to change.
[0230] (3) Determining number of physical radio channel repetition for the warning message and / or emergency call paging
[0231] This operation focuses on ensuring that warning and / or emergency call paging notification messages are successfully received by the UE. When the core network or the satellite-enabled RAN node pages an IDLE or INACTIVE mode UE, the UE may be in a poor radio channel condition (low Signal-to-Noise Ratio, SNR) and / or in a condition of serving satellite change. The UE may miss these paging messages under such circumstances. To ensure that warning and / or emergency call paging notification messages are successfully received by the UE, the following operations as illustrated in FIG. 11 may be performed.
[0232] a) The core network may compute the number of repetitions, N, required to ensure an effective delivery of the message, as explained in foregoing sections of the present disclosure. Based on this number, the core network node instructs, indicates or triggers the connected satellite RAN nodes to repetitively transmit the emergency and / or call paging notification messages N times over the physical radio channel towards the UE (s) . This guarantees the notification message delivery to the UEs during a satellite change.
[0233] b) To address the issue of missing warning and / or emergency call paging notification messages due to poor radio channel conditions (low SNR) , the satellite RAN node needs to be aware of the UE's SNR status or the delivery status of the initial warning and / or emergency paging message to the UE when triggering a robust notification procedure (repeating message transmission on physical radio channel resources) . The awareness of UE SNR status requires performance measurement which could add some additional overhead or latency. An alternative solution is to either perform a counter-based or timer-based estimation of when to trigger the robust notification procedures. This helps reduce additional overhead or latency due to measurement and avoids wasting radio channel physical resources.
[0234] The counter-based or timer-based estimations to trigger the robust notification procedures are as follows:
[0235] a) Counter-based option: The RAN node sets a number of paging retries. If the number of retries exceeds a specific limit, the RAN node can initiate the robust notification procedures towards the UE. In this case, the RAN node may indicate the number of initial paging retries within the robust notification procedures defined in RAN1 to assist the UE in understanding that it has been tried to be paged multiple times. It may also indicate a cause for paging via a Downlink Control Information (DCI) field or Radio Resource Control (RRC) field of Medium Access Control (MAC) Information Element (IE) field or suggest a beam or sub-beam location with better SNR for the UE to move to and receive the warning or the emergency call notification, or answer or perform the emergency call.
[0236] b) Timer-based option: The RAN node sets a timer from the moment the first paging is sent to the UE until receiving an RRC, resume, setup, and / or re-establishment response. If no response is received until the timer expires, the RAN node initiates the robust notification procedures towards the UE.
[0237] FIG. 12 illustrates an example of the whole signaling for guaranteeing emergency call and / or warning messages delivery.
[0238] This embodiment discusses the details of signaling and procedures for a solution approach to address delay, interruption, and / or potential loss of warning messages and / or emergency notifications in a rapidly-moving satellite network scenario. The approach relies on exchanging information from a warning or emergency notification node (e.g., IMS or CBS) to a core network node (e.g., an AMF) , regarding one or more impacted warning or emergency call notification areas defined by a set containing one or more geolocations or geometrical shapes. Then, the AMF node checks in real-time whether the geolocations or geometrical shapes are falling within the coverage set of the satellite RAN nodes (e.g., a gNB) that are currently connected to the core network node (AMF) or not.
[0239] In the case that the impacted geolocations are falling within at least one or more satellites from the set of satellites currently connected to the AMF, the AMF immediately broadcasts emergency messages or paging via those satellites (i.e., satellites covering the set of impacted geolocations) . On the other hand, if the one or more geolocations are partially or fully outside the coverage of currently connected satellites, or if the satellite / satellites covering the one or more geolocations are about to change due to the orbital movement of the constellation, the AMF initiates repetitive or preemptive sending of the warning or emergency notification messages before the satellite change occurs, ensuring that there is no gap or interruption in the delivery of warning or emergency notification messages.
[0240] For geolocation areas transitioning between satellites, the AMF may schedule a retransmission after the satellite change or select to route the warning or emergency notification messages through a specific set of satellites, skipping other satellites to reduce overhead or save bandwidth resources for other types of traffic in other satellites. Additionally, the AMF may perform a computation of the number of repetitions needed by the AMF or a satellite RAN node to ensure reliable delivery of the warning and notification messages during dynamic satellite transitions.
[0241] The signaling for guaranteeing the delivery of emergency and / or warning messages may follow at least one of the signaling methods depicted in FIG. 12, and the procedures are described by at least one of the following steps:
[0242] 1) A centralized alert or call notification system (e.g., Cell Broadcast Entity (CBE) , PWS-IWS, and / or IMS) generates a warning or emergency message containing: warning type (e.g., ETWS, CMAS, etc. ) or IMS call paging request; affected area (geographic scope, geolocations, or geometrical shapes such as longitude, latitude, or coverage radius) ; warning or emergency over satellite indication; and / or message content (e.g., text, severity, validity period) .
[0243] 2) The warning or emergency message containing the affected area (geographic scope, geolocations, or geometrical shapes) , warning or emergency over satellite indication, and message content is sent to the 5G core (AMF) or LTE core (MME) via CBCF (Cell Broadcast Centre Function) using Write-Replace-Warning or IMS paging procedures.
[0244] 3) Based on the warning or emergency over satellite indication, the AMF / MME invokes an exchange of assistance information (e.g., ephemeris, orbital type, constellation information) from its currently connected satellite gNB or eNB nodes over an N2 message.
[0245] 4) The AMF / MME identifies the satellite gNB / eNB nodes that are currently covering the affected area by checking in real-time whether the geolocations or geometrical shapes of the affected area fall within the coverage set of the satellite RAN nodes (e.g., a gNB) that are currently connected to the core network node (AMF / MME) . Based on this, the AMF / MME may proceed as follows:
[0246] If the impacted geolocations are covered, the AMF / MME immediately broadcasts emergency messages or paging via the satellites covering the impacted geolocations.
[0247] If the impacted geolocations are partially or fully outside coverage, or if the satellite / satellites covering the geolocations is / are about to change due to orbital movement of the constellation, the AMF / MME initiates repetitive or preemptive sending of the warning or emergency notification messages before the satellite change occurs, ensuring no gap or interruption in the delivery of warning or emergency notification messages.
[0248] For geolocation areas transitioning between satellites, the AMF may schedule a retransmission after the satellite change; or select to route the warning or emergency notification messages through specific satellites, skipping others to reduce overhead or save bandwidth resources for other types of traffic. Alternatively, the AMF may compute the number of repetitions needed by the AMF / MME or satellite gNB / eNB nodes to ensure reliable delivery during dynamic satellite transitions.
[0249] 5) In the case of CBS warning delivery, the AMF / MME may send a NonUeN2MessageTransfer with Write-Replace Warning to confirm that the messages were sent to the target satellite gNB or eNB nodes.
[0250] 6) The gNB or eNB nodes broadcast the alert based on the computed number of repetitions via system information blocks (SIBs) or RRC configuration over the air interface (Uu) , using: ETWS: Primary / Secondary Notification (SIB6 / SIB7) ; or CMAS: SIB8. The nodes may also provide a suggested beam or sub-beam identity and paging importance so that the UE may move or resume towards that sub-region for better SNR.
[0251] 7) The UE monitors PWS messages in SIBs and: validates the message integrity; and / or triggers an urgent pop-up and audible alarm (bypassing silent mode) .
[0252] 8) The UE displays the warning with: text content (e.g., "Tsunami Alert! " ) ; and / or geographic relevance (if location-aware) .
[0253] This ensures that warning and emergency messages are reliably delivered to UEs in rapidly-moving satellite network scenarios while addressing delay, interruption, and loss risks.
[0254] To help better understanding of the above described embodiments of the present disclosure, several methods for calculating the coverage of a satellite, satellite change time and so on are introduced below.
[0255] When assessing the speed of changing satellite coverage in a satellite constellation, assuming there is no overlap of coverage between two satellites at any given time from the satellite's point of view, the node carrying out the assessment should first estimate the effective coverage area of the entire satellite constellation. This is assumed to be the surface area of the Earth, which is given by: Surface Area of Earth = 4πrR2 where R is the radius of the Earth, approximately 6, 371 km.
[0256] Next, calculate the coverage area of a single satellite in the constellation by dividing the surface area of the Earth by the number of satellites, N, in the constellation:
[0257] After that, calculate the time period required for a satellite to change coverage from a specific region on the ground to a new one within the constellation (i.e., satellite handover time) . To calculate this, it's necessary to determine the distance between the satellites and the orbital speed of the satellite at its given altitude. The distance between the satellites is given by:
[0258] For a satellite constellation, a satellite orbital velocity or orbital speed at a given time given the constellation altitude can be calculated using the following formula: where R is the Earth's radius (≈6371 km) ; h: is the satellite's altitude above the Earth's surface; μ: is the Earth's gravitational parameter (3.986×A=3.98*1014 m3 / s2) .
[0259] Given the average distance between satellites and the satellite orbital velocity or orbital speed at a given time, the satellites handover time in a satellite constellation can be calculated by:
[0260] The satellite ephemeris information or parameters described in foregoing sections of the present disclosure are shown in FIG. 13 and Table 10. Table 10. Essential parameters for Ephemeris
[0261] The signal strength mentioned in foregoing sections of the present disclosure may be at least one of the following UE or satellite / RAN node measurements:
[0262] a) Signal-to-noise ratio (SNR) ;
[0263] b) Reference signal received power (RSRP) ;
[0264] c) Reference signal received quality (RSRQ) ;
[0265] d) Equivalent iso-tropically radiated power (EIRP) .
[0266] In foregoing embodiments, the geolocation, footprints, or geometric shapes are determined based on the satellite's altitude and the Earth’s curvature, and could be represented by:
[0267] a) A circle characterized by co-ordinates of a point (latitude, longitude) and a coverage distance radius r, as shown in FIG. 14;
[0268] b) A polygon shape i.e., a shape described by an ordered series of points between 3 and 15 points, as shown in FIG. 15;
[0269] c) An elliptical shape characterized by the co-ordinates of a point (latitude, longitude) and distances r1 and r2 and an angle of orientation A, as shown in FIG. 16.
[0270] In foregoing embodiments, great-circle distance between two points using Haversine formula is calculated using the following formula: where (φ1, λ1) is the Satellite coordinates (latitude, longitude in radians) ; (φ2, λ2) is the Geolocation coordinates (latitude, longitude in radians) ; Δφ=φ2-φ1; Δλ=λ2-λ1.
[0271] As a brief summary, the present disclosure presents a set of methods to enable resilient emergency communications over satellite access, encompassing both UE-initiated and network-initiated emergency communications.
[0272] A first method aims to address the challenge of determining the precise location of a user equipment requesting emergency access over wide coverage beam satellite networks, particularly in satellite constellations with extensive beam coverage, such as GEO / HEO constellations, or for UEs operating at varying altitudes (multi-altitude UEs) .
[0273] The method involves the exchange of critical information between the UE, a satellite-enabled radio access network (RAN) node, and / or a core network node. This information includes:
[0274] a) Mapping data, such as satellite beam coverage sub-region details, beam identity, signal-quality ranges, and / or signal strength weighing tiers.
[0275] b) Orbital characteristics, such as satellite orbit type and time advancement measurements.
[0276] By leveraging these parameters, the system determines the sub-region of the satellite beam or the precise geometric location of the UE requesting emergency access.
[0277] The method may be implemented in current 4G or 5G wireless communication architecture or other wireless communication network such as 6G network in the future. FIG. 17 shows another example about signaling exchanges for locating the UE requesting emergency access.
[0278] The procedure shown in FIG. 17 focuses on addressing the issue of determining the precise location or the cell in which the UE is located when the UE initiates an emergency request. This is achieved by dividing the satellite coverage or beam coverage into smaller sub-beams identified by geolocations, signal strength ranges, and / or weighting factors linked to the UE's actual signal measurements and / or predefined parameters based on the satellite orbit type (LEO, GEO, MEO, or HEO) . These predefined parameters include signal strength ranges and geolocation mapping. The solution involves identifying the sub-beam with the closest signal strength and / or the nearest vertical and / or horizontal geometric position that verifies the identified sub-beam or falls closer to the UE's measured signal radius.
[0279] This solution includes the exchange of at least one of the following parameters between the UE, a satellite-enabled Radio Access Network (RAN) node, and a core network node:
[0280] a) Emergency satellite orbit type indication: Indicating the satellite orbital type (LEO, GEO, MEO, or HEO) involved in the emergency communication.
[0281] b) Mapping between geolocations and signal strength ranges: This includes weighting factors linked to the UE's actual signal measurements and / or predefined values based on the satellite orbit type (LEO, GEO, MEO, or HEO) , signal strength ranges, and geolocation mapping.
[0282] c) Time Advance (TA) : A value, typically in microseconds (if available) , and / or a round-trip time delay when the UE sends a signal to the satellite (or vice versa) , measured by the UE or the satellite.
[0283] The solution utilizes at least one of these parameters by the UE, RAN, or core network node to determine the actual satellite geolocation sub-beam or the actual vertical and / or horizontal geometrical regions where the UE requesting emergency access is located. This determination is based on the mapping and / or the UE / satellite TA measurement value. The process involves comparing geolocation and signal strength range mappings against the UE's measured signal strength. The identity of the satellite sub-region / sub-beam and / or vertical geometrical regions is then provided to the core network node to ensure precise location information when providing the required assistance to the UE. Alternatively, based on the indicated satellite orbital type, the core network node may select a positioning method that guarantees the Quality of Service (QoS) or latency requirements of the UE's emergency session. This is achieved by classifying positioning methods based on their latency budgets and selecting a suitable method for the indicated satellite orbit type to meet the UE's emergency session QoS or latency requirements.
[0284] A second method aims to address the challenges of delay, interruption, or potential loss of emergency notifications in rapidly changing satellite networks, particularly in LEO / MEO constellations where satellite coverage changes frequently.
[0285] This method involves the exchange of real-time satellite orbital mechanics, constellation data, and coverage parameters between emergency notification nodes, core network nodes, and RAN nodes. These parameters are then used to:
[0286] a) Verify, in real time, the satellites covering the targeted emergency notification area (defined by geolocation or geometric footprints) for timely broadcasting of warning or emergency paging messages.
[0287] b) Trigger pre-emptive broadcasting to the affected area, using ephemeris data to precisely time prediction actions.
[0288] c) Schedule retransmissions of warning or emergency notifications after satellite changes.
[0289] d) Optimize routing of emergency notifications through specific satellites, skipping others to reduce overhead and conserve bandwidth.
[0290] e) Compute the number of repetitions required to ensure reliable delivery of messages during dynamic coverage transitions between satellites.
[0291] By combining these solutions, the satellite wireless communication system ensures accurate determination of the UE's location during emergency access requests and guarantees reliable, fast, and efficient delivery of warning and emergency call notifications within the QoS constraints of emergency systems.
[0292] The method may be implemented in current 4G or 5G wireless communication architecture or other wireless communication network such as 6G network in the future. FIG. 18 shows another example about signaling exchanges for preventing of missing emergency messages and call notification.
[0293] The procedure shown in FIG. 18 focuses on addressing the issues of delay, interruption, and / or potential loss of warning and / or emergency call paging messages in a rapidly-moving satellite network. The solution relies on continuous real-time checking of which satellites are covering the geolocations targeted by warning and / or emergency message delivery, and transmitting the warning and / or emergency messages accordingly.
[0294] This solution involves the exchange of at least one of the following parameters between an emergency notifications node, a core network node, and / or a radio access node:
[0295] a) Satellite orbital type: (e.g., LEO, GEO, MEO, HEO)
[0296] b) RAN node status: (e.g., on-board, on-ground)
[0297] c) Satellite coverage information: (e.g., longitude, latitude, coverage radius in km, number of beams)
[0298] d) Constellation information: (e.g., orbit type, altitude, number of satellites, changing information, etc. )
[0299] e) Ephemeris information: Such as the speed of the satellite and / or actual satellite location at a given time
[0300] f) Geolocation or geometrical areas targeted by warning or emergency paging / notifications broadcasting: (e.g., longitude, latitude, coverage radius in km)
[0301] Based on the above parameters, the core network node or RAN node may perform real-time checks to determine whether the area impacted by warning or call message notifications (i.e., indicated by a set of geolocations or geometrical information provided by the warning or emergency generating node) falls within the set of satellites currently connected to the core network.
[0302] If the geolocations are within the set of those satellites, the core network node may immediately broadcasts the warning or call message notifications to those satellites.
[0303] However, if the geolocations of the affected area partially or fully fall outside the coverage of the currently connected satellite, and / or if the satellites covering these geolocations are about to change due to the constellation's orbital movement, the core network node may perform at least one of the following operations.
[0304] a) Repetitively or preemptively transmits the warning message and / or emergency call paging before the satellite change occurs.
[0305] b) Re-transmits or re-routes the warning message and / or emergency call paging after the satellite change occurs while maintaining the delivery time requirements of the warning message and / or the emergency call paging.
[0306] c) Determines the number of physical radio channel repetitions that the core network or satellite RAN node uses to enable a robust or resilient delivery of the warning message and / or emergency call paging to UEs.
[0307] The above-described methods for resilient emergency communications over satellite access, addressing both UE-initiated and network-initiated emergencies. The proposed signaling enhancements and procedures mitigate delays, interruptions, and failures in broadcasting emergency messages or notifications while ensuring accurate UE location for assistance. The key effects of these methods may include:
[0308] a) Accurate UE Location: By identifying the precise location of the UE, the system ensures effective assistance while meeting QoS requirements for retrieving UE location information from a location server.
[0309] b) Pre-emptive Messaging: By sending messages pre-emptively before satellite handovers, the system ensures fast and reliable delivery, avoiding interruptions caused by satellite dynamics.
[0310] c) Redundant Messaging: By sending messages repeatedly via multiple satellites simultaneously, the system guarantees reliable delivery within strict time constraints, even during satellite transitions.
[0311] d) Optimized Retransmissions: By calculating the exact number of retransmissions required after satellite handovers, the system conserves bandwidth and resources.
[0312] e) Fallback Mechanisms: If pre-emptive messaging fails, the system buffers and retransmits messages to ensure delivery.
[0313] f) Inter-Satellite Routing: By routing paging and notification messages through alternative satellites when the primary satellite is unavailable, the system maintains message delivery continuity.
[0314] These methods collectively ensure accurate UE location determination and reliable emergency communication delivery, even in dynamic satellite environments.
[0315] FIG. 19 conceptually illustrates a wireless communication device 400 with which some embodiments of the invention are implemented. The device 400 may be a UE, a RAN node, or a core network node (such as AMF or LMF) . The device 400 may be a computer (e.g., a desktop computer, personal computer, tablet computer, etc. ) , phone, PDA, or any other sort of electronic device. Such an apparatus includes various types of computer readable media and interfaces for various other types of computer readable media. The device 400 includes a processor 402 and a memory 404. The memory 404 is configured to store executable instructions that, when executed by the processor, cause the processor to perform any one of the foregoing wireless communication methods.
[0316] The processor 402 may be a single processor or a multi-core processor in different embodiments. In some embodiments, the processor may include a GPU, NPU or DSP which may offload various computations or complement the image processing provided by the processor 402.
[0317] Some embodiments include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media) . Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM) , recordable compact discs (CD-R) , rewritable compact discs (CD-RW) , read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM) , a variety of recordable / rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc. ) , flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc. ) , magnetic and / or solid state hard drives, read-only and recordable discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
[0318] While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) . In some embodiments, such integrated circuits execute instructions that are stored on the circuit itself. In addition, some embodiments execute software stored in programmable logic devices (PLDs) , ROM, or RAM devices.
[0319] As used in this specification and any claims of this application, the terms “computer” , “server” , “processor” , and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. As used in this specification and any claims of this application, the terms “computer readable medium, ” “computer readable media, ” and “machine readable medium” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.
[0320] The present disclosure further provides a computer readable media which is configured to store executable instructions. When the instructions are executed by a processor, the processor may perform any one of the foregoing methods and processes. Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium) . When these instructions are executed by one or more computational or processing unit (s) (e.g., one or more processors, cores of processors, or other processing units) , they cause the processing unit (s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, random access memory (RAM) chips, hard drives, erasable programmable read only memories (EPROMs) , electrically erasable programmable read-only memories (EEPROMs) , etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
[0321] In this specification, the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage which can be read into memory for processing by a processor. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
[0322] While the disclosure has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. In addition, a number of the figures conceptually illustrate processes and methods. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Furthermore, the process could be implemented using several sub-processes, or as part of a larger macro process.
[0323] The foregoing is merely embodiments of the present disclosure, and is not intended to limit the scope of the disclosure. Any transformation of equivalent structure or equivalent process which uses the specification and the accompanying drawings of the present disclosure, or directly or indirectly application in other related technical fields, are likewise included within the scope of the protection of the present disclosure.
Claims
1.A method for determining a geolocation of a user equipment (UE) in a satellite-based data transmission process, executed by a wireless communication node, comprising:acquiring a mapping relation between a plurality of signal strength ranges and a plurality of sub-coverages of a satellite; anddetermining a current signal strength of downlink transmission of the satellite;wherein the mapping relation and the current signal strength are used for determination of an estimated sub-coverage of the satellite in which the UE is located.2.The method of claim 1,wherein the plurality of sub-coverages of the satellite comprises a plurality of sub-beams of the satellite, or a plurality of sub-regions of cell coverage of the satellite.3.The method of claim 1, further comprising:acquiring an orbit type of the satellite;wherein the mapping relation corresponds to the orbit type of the satellite.4.The method of claim 1, further comprising:acquiring a plurality of weights of the plurality of sub-coverages of the satellite;for each sub-coverage of the satellite, generating a reference point within the sub-coverage;calculating a distance between the reference point and a centroid of the sub-coverage;calculating a weighted sum value of distances between reference points and centroids of the plurality of sub-coverages; andbased on the weighted sum value, verifying the estimated sub-coverage of the satellite in which the UE is located, or determining a more detailed location of the UE with regard to the estimated sub-coverage of the satellite in which the UE is located.5.The method of claim 4, wherein the plurality of weights of the plurality of sub-coverages of the satellite are determined based on distances between the plurality of sub-coverages and a center of coverage of the satellite.6.The method of claim 5, wherein the plurality of weights of the plurality of sub-coverages of the satellite are updated by assigning a highest weight to the estimated sub-coverage.7.The method of claim 1,wherein the wireless communication node is the UE;wherein the determining the current signal strength of downlink transmission of the satellite comprises: measuring the current signal strength of downlink transmission of the satellite.8.The method of claim 7,wherein the UE determines the estimated sub-coverage of the satellite; orwherein the UE receives an indication for the estimated sub-coverage of the satellite which is determined by a radio access node (RAN) on which the satellite is deployed or a core network node.9.The method of claim 7, wherein the acquiring a mapping relation between the plurality of signal strength ranges and the plurality of sub-coverages of the satellite comprises:receiving, from a radio access node (RAN) on which the satellite is deployed, the mapping relation between the plurality of signal strength ranges and the plurality of sub-coverages of the satellite via a system information block (SIB) or a radio resource control (RRC) configuration.10.The method of claim 9,wherein the SIB or the RRC configuration further comprises a satellite type indication configured to indicate an orbit type of the satellite; orwherein the SIB or the RRC configuration further comprises an emergency support indication configured to indicate that the satellite supports emergency communication, and the satellite-based data transmission process belongs to emergency communication.11.The method of claim 1,wherein the wireless communication node is a radio access node (RAN) on which the satellite is deployed;wherein the determining the current signal strength of downlink transmission of the satellite comprises: receiving, from the UE, the current signal strength of downlink transmission of the satellite.12.The method of claim 11, further comprising:transmitting an orbit type of the satellite to a core network node;wherein the orbit type of the satellite is configured for the core network node to determine a positioning method for determining the estimated sub-coverage of the satellite in which the UE is located.13.The method of claim 12, wherein the positioning method comprises at least one of:cell identifier (ID) method;enhanced cell ID method;Multi-Round Trip Time (Multi-RTT) method;Downlink Angle of Departure (DL-AoD) or Uplink Angle or Arrival (UL-AOA) method;Downlink Time Difference of Arrival (DL-TDOA) or Uplink Time Difference of Arrival (UL-TDOA) method; orhybrid positioning method by using Global Navigation Satellite System (GNSS) together with cellular network.14.The method of claim 11,wherein the RAN determines the estimated sub-coverage of the satellite; orwherein the RAN receives an indication for the estimated sub-coverage of the satellite which is determined by the UE.15.The method of claim 14, further comprising:notifying the estimated sub-coverage of the satellite to a core network node;wherein the estimated sub-coverage of the satellite is configured for the core network node to determine a location of the UE for the satellite-based data transmission process.16.The method of claim 1,wherein the wireless communication node is a core network node;wherein the determining the current signal strength of downlink transmission of the satellite comprises: receiving, from the UE or a radio access node (RAN) on which the satellite is deployed, the current signal strength of downlink transmission of the satellite.17.The method of claim 16,wherein the core network node determines the estimated sub-coverage of the satellite in which the UE is located based on the mapping relation and the current signal strength.18.The method of claim 16, further comprising:receiving, from the UE or the RAN, an orbit type of the satellite; anddetermining a positioning method for determining the estimated sub-coverage of the satellite in which the UE is located based on the orbit type of the satellite.19.A method for determining a geolocation of a user equipment (UE) in a satellite-based data transmission process, executed by a core network node, comprising:acquiring an orbit type of a satellite which is configured for the UE to perform the satellite-based data transmission process;acquiring a latency requirement for the satellite-based data transmission process; andselecting a positioning method for determining the geolocation of the UE based on the orbit type of the satellite and the latency requirement.20.The method of claim 19, wherein the positioning method comprises at least one of:cell identifier (ID) method;enhanced cell ID method;Multi-Round Trip Time (Multi-RTT) method;Downlink Angle of Departure (DL-AoD) or Uplink Angle or Arrival (UL-AOA) method;Downlink Time Difference of Arrival (DL-TDOA) or Uplink Time Difference of Arrival (UL-TDOA) method; orhybrid positioning method by using Global Navigation Satellite System (GNSS) together with cellular network.21.A satellite-based data transmission method, executed by a wireless communication node, comprising:acquiring an impacted geolocation corresponding to a request for a satellite-based data or message transmission; andchecking whether the geolocation falls within a coverage range of a first satellite that is connected to the wireless communication node.22.The method of claim 21,wherein the satellite-based data or message transmission comprises, a downlink broadcast, a warning message, an emergency call page notification, or a multicast or group cast transmission.23.The method of claim 21, further comprising:acquiring ephemeris information and / or orbital parameters of the first satellite; anddetermining the coverage range of the first satellite based on the ephemeris information and / or the orbital parameters.24.The method of claim 21, wherein the checking whether the impacted geolocation falls within the coverage range of the first satellite comprises:comparing a distance between a centroid of the impacted geolocation and a centroid of the coverage range of the first satellite with the coverage range;wherein when the distance between the centroid of the impacted geolocation and the centroid of the coverage range of the first satellite is less than or equal to the coverage range, it is determined that the geolocation falls within the coverage range of the first satellite.25.The method of claim 21, further comprising:responsive to the impacted geolocation falling within the coverage range of the first satellite, transmitting the satellite-based data or message transmission via the first satellite.26.The method of claim 21, further comprising:determining a time window for data transmission corresponding to the satellite-based data or message transmission, wherein the time window starts from a last satellite handover;determining a satellite change time between two satellite handovers; andwhen the time window is less than the satellite change time, transmitting the satellite-based data or message transmission via the first satellite; orwhen the time window is larger than the satellite change time, transmitting the satellite-based data or message transmission via a second satellite to which the first satellite is to be handed over or by using Inter-Satellite Link (ISL) routing.27.The method of claim 26,wherein the satellite change time is determined based on a distance between the first satellite and the second satellite, and a satellite orbital speed.28.The method of claim 26, further comprising:acquiring a priority level of the satellite-based data or message transmission.29.The method of claim 21, further comprising:determining a satellite change time between two satellites on-ground coverage change;determining a repetition number based on a required delivery time of the satellite-based data or message transmission, the satellite change time and an interruption time, and repetitively transmitting the satellite-based data or message transmission to the first satellite and / or a second satellite to which the first satellite is to be handed over or has been handed over, wherein the interruption time is a time period for reception of transmission failure indication.30.The method of claim 21, further comprising:responsive to the impacted geolocation falling outside the coverage range of the first satellite, buffering or instructing the first satellite to buffer the satellite-based data or message transmission; andre-transmitting the satellite-based data or message transmission via a second satellite to which the first satellite has been handed over.31.The method of claim 21, further comprising:responsive to the impacted geolocation falling within both the coverage range of the first satellite and a coverage range of a second satellite:selecting either the first satellite or the second satellite for transmission of the satellite-based data or message transmission; orrouting the satellite-based data or message transmission through Inter-Satellite Link (ISL) between the first satellite and the second satellite.32.The method of claim 21, further comprising:transmitting one or more paging messages to a user equipment;when a number of the one or more paging messages reaches a first threshold or no response for the one or more paging messages is received within a pre-defined time, initiating a robust notification procedure for the satellite-based data or message transmission.33.A wireless communication device, comprising a processor and a memory, wherein the memory is configured to store executable instructions that, when executed by the processor, cause the processor to perform the method of any of claims 1 to 32.34.A non-transitory computer readable medium storing executable instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1 to 32.
