Techniques to handle interruptions in satellite-based communications

Abstract

Apparatuses, methods, and computer-readable media for facilitating disruption handling in satellite-based communications are disclosed herein. An example method for wireless communication at a UE includes determining an interruption of a satellite-based communication link based in part on UE location information and blocking information that blocks LOS propagation obstacles of the satellite-based communication link. The example method also includes refraining from performing one or more communication link correction procedures within a time period associated with the interrupt.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Non - Provisional Patent Application Serial No. 18 / 073,532, filed on December 1, 2022, entitled "TECHNIQUES TO HANDLE INTERRUPTION IN SATELLITE - BASED COMMUNICATIONS", which is hereby incorporated by reference in its entirety. Background of the Invention

[0003] The present disclosure generally relates to communication systems and, more particularly, to wireless communication employing satellite - based communication.

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple access techniques capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single - Carrier Frequency Division Multiple Access (SC - FDMA) systems, and Time - Division Synchronous Code Division Multiple Access (TD - SCDMA) systems.

[0005] These multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long - Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access techniques and telecommunication standards that employ these techniques. Summary of the Invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. The summary neither identifies key or critical elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0007] In one aspect of the present disclosure, a method for wireless communication at a user equipment (UE) is provided. The method may include: determining an interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle that blocks line-of-sight (LOS) propagation of the satellite-based communication link. The example method may further include: avoiding performing one or more communication link calibration processes during a time period associated with the interruption.

[0008] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a UE including a memory and at least one processor coupled to the memory, and the at least one processor may be configured to: determine an interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link. The at least one processor may further be configured to: avoid performing one or more communication link calibration processes during a time period associated with the interruption.

[0009] In another aspect of the present disclosure, a device for wireless communication at a UE is provided. The device may include: means for determining an interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link. The example device may further include: means for avoiding performing one or more communication link calibration processes during a time period associated with the interruption.

[0010] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. When executed, the code may cause a processor to: determine an interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link. The example code may further cause the processor to: avoid performing one or more communication link calibration processes during a time period associated with the interruption.

[0011] In one aspect of the present disclosure, a method for wireless communication at a base station is provided. The method may include: determining an interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link with the UE. The example method may further include: avoiding scheduling communication with the UE during a time period associated with the interruption.

[0012] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a network entity including a memory and at least one processor coupled to the memory, the at least one processor being configured to: determine an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link with the UE. The at least one processor may further be configured to: avoid scheduling communication with the UE during a time period associated with the interruption.

[0013] In another aspect of the present disclosure, a device for wireless communication at a base station is provided. The device may include: means for determining an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link with the UE. The example device may further include: means for avoiding scheduling communication with the UE during a time period associated with the interruption.

[0014] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a network entity is provided. The code, when executed, may cause a processor to: determine an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link with the UE. The example code, when executed, may further cause the processor to: avoid scheduling communication with the UE during a time period associated with the interruption.

[0015] To achieve the foregoing and related purposes, one or more aspects may include the features described in detail hereinafter and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network (NW).

[0017] Figure 2 shows a diagram illustrating an example of the architecture of a split base station.

[0018] Figure 3A is a diagram illustrating an example of a first subframe within a 5G NR frame structure.

[0019] Figure 3B is a diagram illustrating an example of a DL channel within a 5G NR subframe.

[0020] Figure 3C is a diagram illustrating an example of a second subframe within a 5G NR frame structure.

[0021] Figure 3D It is a diagram illustrating an example of a UL channel within a 5G NR subframe.

[0022] Figure 4 It is a block diagram illustrating an example of a first wireless device configured to exchange wireless communication with a second wireless device.

[0023] Figure 5 It illustrates an example of communication between devices according to the teachings disclosed herein.

[0024] Figure 6 It is a diagram illustrating an example environment that supports satellite-based communication to a UE according to the teachings disclosed herein.

[0025] Figure 7 It illustrates a part of a digital map according to the teachings disclosed herein.

[0026] Figure 8 It illustrates an example communication flow between a first device and a second device according to the teachings disclosed herein.

[0027] Figure 9 It illustrates an example communication flow between a network entity and a UE according to the teachings disclosed herein.

[0028] Figure 10 It is a flowchart of a method for wireless communication at a UE according to the teachings disclosed herein.

[0029] Figure 11 It is a flowchart of a method for wireless communication at a UE according to the teachings disclosed herein.

[0030] Figure 12 It is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.

[0031] Figure 13 It is a flowchart of a method for wireless communication at a network entity according to the teachings disclosed herein.

[0032] Figure 14 It is a flowchart of a method for wireless communication at a network entity according to the teachings disclosed herein.

[0033] Figure 15 It is a diagram illustrating an example of a hardware implementation for an example network entity. Detailed Description

[0034] Various aspects generally relate to wireless communication and, more specifically, to satellite-based communication with a UE such as a vehicle (which may also be referred to herein as "satellite-based vehicle communication"). Some aspects more specifically relate to handling an interruption of a satellite-based communication link between the UE and the satellite due to an obstacle that blocks line-of-sight (LOS) propagation of a signal between the UE and the satellite.

[0035] In some aspects, a UE (e.g., a vehicle) may be configured to communicate with other devices. For example, a connected vehicle may refer to a vehicle equipped with an on-board unit (OBU) that enables the vehicle to perform vehicle-based communication. The connected vehicle (which may also be referred to herein as "vehicle UE" or "UE") may communicate with other OBUs (e.g., other vehicles equipped with OBUs), roadside units (RSUs) (e.g., road infrastructure nodes), vulnerable road users (VRUs) (e.g., a child's scooter, a pedestrian's smartphone, etc.), and the like. The connected vehicle may be configured to communicate between vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from the connected vehicle to a road infrastructure node such as an RSU), vehicle-to-network (V2N) (e.g., from the connected vehicle to one or more network nodes such as a base station or a component of a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof and / or communicate with other devices, and such communications may be collectively referred to as vehicle-to-everything (V2X) communications.

[0036] In some aspects, the connected vehicle may communicate with other devices via a sidelink. In some aspects, the connected vehicle may communicate with other devices via a cellular network (e.g., via the Uu link). In some aspects, the connected vehicle may communicate with other devices via satellite-based communication. In some aspects, the satellite-based communication may be complementary to sidelink communication or Uu link communication to provide, for example, ubiquitous connectivity.

[0037] According to one or more examples, the satellite-based communication may be based on a technology specified by 3GPP or by a dedicated satellite communication system. The satellite communication system may provide service coverage to areas where the terrestrial network may not be able to provide service coverage, such as rural areas. In the satellite communication system, the UE may make an air connection with a base station (or a component of a base station) via a satellite. As used herein, a satellite may also refer to an aerial device that provides access to a network (e.g., NTN) for a UE via a satellite-based communication link, such as an unmanned aerial system (UAS) platform, a balloon, a drone, an unmanned aerial vehicle (UAV), etc.

[0038] Communication via a satellite-based wireless channel can be characterized by line-of-sight (LOS) propagation between a UE and a satellite. In scenarios where the signal can travel directly between the UE and the satellite (e.g., without being reflected by an object), the satellite-based wireless channel can be characterized by strong LOS propagation. Even with LOS propagation, the signal may be reflected from an object before reaching its intended target (e.g., the UE or another satellite). As the number of reflections increases and the degree of reflection of the signal on the object increases, communication via the satellite-based wireless channel can be characterized by weak LOS propagation or non-line-of-sight (NLOS) propagation. However, a UE with mobility capabilities (e.g., a vehicle with mobility capabilities such as a car, train, ship, etc.) may encounter obstacles over time, such as overpasses, interchanges, bridges, etc. Such obstacles may cause LOS blockage between the UE and the satellite, which may interrupt satellite-based communication.

[0039] Aspects disclosed herein enable a UE and / or a network entity (e.g., a satellite, a base station, components of a base station, etc.) to predict the occurrence of an interruption due to blockage of LOS propagation between the UE and the satellite, thereby facilitating satellite-based communication with the UE. In some aspects, based on the predicted interruption, the UE and / or the network entity may avoid performing one or more processes to mitigate the impact of an interruption of the communication link between the UE and the satellite.

[0040] Aspects disclosed herein provide techniques for predicting an interruption of a communication link between a UE and a satellite, e.g., due to an obstacle in the path of the UE (e.g., a vehicle). For example, according to one aspect, the disclosed techniques include using location information of the obstacle to predict a possible interruption of the satellite-based communication link between the UE and the satellite. A network entity (e.g., a satellite, a base station, components of a base station, etc.) and the UE may then exchange information about the predicted interruption. In some aspects disclosed herein, the network entity and the UE may each perform at least one action to mitigate the impact of the predicted interruption.

[0041] In some aspects disclosed herein, a network entity may predict the occurrence of an interruption of a communication link due to an obstacle. In other aspects, a UE may predict the occurrence of an interruption of a communication link due to an obstacle. As used herein, an obstacle may refer to an object that may block the LOS propagation of a signal between the UE and a satellite, such as an overpass, an interchange, a bridge, etc. A prediction device (e.g., a UE and / or a network entity) may predict the interruption based in part on blocking information associated with an obstacle in the path of the UE. For example, the prediction device may access a digital map that includes information about the location, size, etc. of the obstacle. As used herein, a digital map may refer to a representation of an area stored in digital format. The digital map may include information about the terrain of the area and / or information (e.g., location, size, etc.) about landmarks such as roads, bridges, overpasses, exits, etc. The prediction device may also access location information of the UE (e.g., a vehicle). For example, a network entity may access UE location information to facilitate satellite-based communication with the UE. The UE location information may include the coordinates of the UE (e.g., geographical coordinates), may include the rate of the UE (e.g., the traveling speed of the UE and the traveling direction of the UE), etc.

[0042] The prediction device may use the UE location information and the blocking information to predict the occurrence of an interruption of the communication link between the UE and the satellite. For example, based on the traveling direction of the UE and the location information of the obstacle, the prediction device may predict that the UE and the satellite may experience an interruption of their communication link (e.g., blocking of the LOS propagation). The prediction device may also predict the interruption duration of the predicted interruption that the UE and the satellite may experience in their communication link. For example, based on the traveling speed of the UE and the size information of the obstacle, the prediction device may predict the amount of time associated with the blocking of the LOS propagation (e.g., the interruption duration).

[0043] In certain aspects disclosed herein, the network entity and the UE may exchange information about the predicted interruption of the communication link between the UE and the satellite. For example, after predicting the interruption, the network entity may provide an indication of the predicted interruption to the UE, or the UE may provide an indication of the predicted interruption to the network entity. The indication of the predicted interruption may include a time period associated with the interruption duration. The time period may include the duration, the start time, and / or the end time. In some examples, the duration of the time period may include a time buffer to account for uncertainties. For example, the prediction device may estimate the interruption duration as three seconds, but may set the time period duration to five seconds (e.g., a two-second time buffer) to account for uncertainties such as the size of the obstacle and / or the traveling speed of the UE.

[0044] In some examples, the time period duration may correspond to the outage duration associated with the blockage of LOS propagation. For example, the time period may indicate a time window of future time as the duration (e.g., the start time of the predicted outage may be offset from the current time). For example, the time period may indicate a five-second duration corresponding to the outage duration and a start time of ten seconds from the current time. In some examples, the time period duration may indicate a duration starting from the current time. For example, the time period duration may include a 15-second duration that includes a five-second duration corresponding to the outage duration and a ten-second offset from the current time corresponding to the time when the expected communication link is expected to experience the predicted outage.

[0045] The network entity and the UE may then perform actions to mitigate or reduce the impact of the predicted outage (e.g., disruption of the communication link). For example, within the time period associated with the outage duration, the network entity may pause or avoid scheduling communication with the UE (e.g., uplink transmission and / or downlink transmission). Additionally or alternatively, the UE may defer (e.g., avoid) performing one or more procedures that may be associated with correcting the outage of the communication link within the indicated time period, such as declaring radio link failure (RLF), releasing radio resource control (RRC) connection, performing a new satellite search procedure, performing beam steering, etc. The network entity and the UE may perform actions within the time period duration starting from the current time or a future time.

[0046] Particular aspects of the subject matter described in this disclosure may be implemented to improve communication performance. For example, satellite-based communication may provide service coverage to areas where terrestrial networks may not provide service coverage, such as rural areas. By predicting outages, the aspects disclosed herein may improve communication performance by taking actions to mitigate the impact on satellite-based communication due to outages. More specifically, the UE and the network entity may operate as if there is no traffic scheduling during the time period associated with the outage. Thus, the UE may avoid performing one or more communication link correction procedures that may increase signaling overhead and thus may cause communication latency. Additionally, within the indicated time period associated with the outage duration, the network entity may avoid scheduling communication with the UE that may increase signaling overhead and thus may cause communication latency. By avoiding performing one or more communication link correction procedures due to obstacles blocking LOS propagation and avoiding scheduling communication within the time period associated with the outage duration, the aspects disclosed herein may improve connectivity while improving spectral efficiency.

[0047] Although the following description provides examples related to 5G NR, the concepts described herein may be applicable to other similar domains, such as 6G, 5G-advanced, LTE, LTE-A, CDMA, GSM, and / or other wireless technologies.

[0048] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, the concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0049] Several aspects of a telecommunications system are given with reference to various apparatuses and methods. These apparatuses and methods are described in the following specific embodiments and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0050] As an example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

[0051] Thus, in one or more example aspects, embodiments, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0052] Although aspects, embodiments, and / or use cases are described by way of some examples in this application, additional or different aspects, embodiments, and use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be embodied via integrated chips and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the described examples may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more of the technologies herein. In some actual settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The technologies described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0053] Figure 1FIG. is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (which is also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (e.g., EPC 160), and another core network 190 (e.g., 5G core (5GC)). The base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0054] The base station 102 configured for 4G LTE (collectively referred to as the evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., S1 interface). The base station 102 configured for 5G NR (collectively referred to as the next generation RAN (NG-RAN)) may interface with the core network 190 via a second backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly with each other (e.g., via the EPC 160 or the core network 190) via a third backhaul link 134 (e.g., X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0055] In some aspects, a base station (e.g., one of the base stations 102 or one of the base stations 180) may be referred to as a RAN and may include aggregated components or disaggregated components. As an example of a disaggregated RAN, a base station may include a central unit (CU) (e.g., CU 106), one or more distributed units (DUs) (e.g., DU 105), and / or one or more remote units (RUs) (e.g., RU 109), as Figure 1As illustrated. The RAN can be decomposed by using the split between RU 109 and the aggregated CU / DU. The RAN can be decomposed by using the split between CU 106, DU 105, and RU 109. The RAN can be decomposed by using the split between CU 106 and the aggregated DU / RU. CU 106 and one or more DUs can be connected via the F1 interface. DU 105 and RU 109 can be connected via the fronthaul interface. The connection between CU 106 and DU 105 can be referred to as the midhaul, and the connection between DU 105 and RU 109 can be referred to as the fronthaul. The connection between CU 106 and the core network 190 can be referred to as the backhaul.

[0056] The RAN can be based on a functional split between various components of the RAN (e.g., between CU 106, DU 105, or RU 109). CU 106 can be configured to perform one or more aspects of the radio communication protocol, e.g., handle one or more layers of the protocol stack, and one or more DUs can be configured to handle other aspects of the radio communication protocol, e.g., other layers of the protocol stack. In different embodiments, the split between the layers handled by the CU and the layers handled by the DU can occur at different layers of the protocol stack. As a non-limiting example, DU 105 can provide a logical node for hosting at least a portion of the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer based on the functional split. The RU can provide a logical node configured to host at least a portion of the PHY layer and radio frequency (RF) processing. CU 106 can host higher layer functions such as the service data adaptation protocol (SDAP) layer, the packet data convergence protocol (PDCP) layer, and / or upper layers, e.g., above the RLC layer. In other embodiments, the split between the layer functions provided by the CU, DU, or RU can be different.

[0057] Base station 102 can communicate wirelessly with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographical coverage area 110. There may be overlapping geographical coverage areas. For example, small cell 103 may have a coverage area 111 that overlaps with the corresponding geographical coverage area 110 of one or more base stations (e.g., one or more macro base stations, such as base station 102). A network including both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include a Home evolved Node B (HeNB), which can serve a restricted group known as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from the UE to the base station and / or a downlink (DL) (also referred to as a forward link) transmission from the base station to the UE. The communication link 120 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can pass through one or more carriers. For each carrier allocated in carrier aggregation with a total of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 can use a spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers can be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be referred to as the Primary Cell (PCell) and the secondary component carriers can be referred to as Secondary Cells (SCells).

[0058] Some UEs can communicate with each other using device-to-device (D2D) communication links (such as D2D communication link 158). D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0059] The wireless communication system may also include a Wi-Fi access point (AP) (such as AP 150), which communicates with a Wi-Fi station (STA) (such as STA 152) via a communication link 154, for example, in an unlicensed spectrum such as the 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0060] The small cell 103 may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 103 may adopt NR and use the same unlicensed spectrum (such as 5 GHz, etc.) as that used by the Wi-Fi AP 150. The small cell 103 adopting NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0061] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0062] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating frequency bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The frequency bands falling within FR3 may inherit the characteristics of FR1 and / or FR2, and thus can effectively extend the characteristics of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0063] In view of the above aspects, unless otherwise specifically stated, if terms such as "below 6 GHz" are used herein, they can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include intermediate band frequencies. In addition, unless otherwise specifically stated, if terms such as "millimeter wave" are used herein, they can broadly represent frequencies that can include intermediate band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0064] A base station (whether it is a small cell 103 or a large cell (e.g., a macro base station)) can include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNBs) can operate in the conventional below 6 GHz spectrum, at millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When a gNB operates at millimeter wave frequencies or near millimeter wave frequencies, the base station 180 can be referred to as a millimeter wave base station. The millimeter wave base station can utilize beamforming 181 with the UE 104 to compensate for path loss and near - range. The base station 180 and the UE 104 can each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0065] The base station 180 can transmit a beamformed signal to the UE 104 in one or more transmission directions 182. The UE 104 can receive the beamformed signal from the base station 180 in one or more reception directions 183. The UE 104 can also transmit a beamformed signal to the base station 180 in one or more transmission directions. The base station 180 can receive the beamformed signal from the UE 104 in one or more reception directions. The base station 180 / UE 104 can perform beam training to determine the best reception direction and the best transmission direction for each of the base station 180 / UE 104. The transmission direction and the reception direction of the base station 180 can be the same or can be different. The transmission direction and the reception direction of the UE 104 can be the same or can be different.

[0066] The EPC 160 may include a Mobility Management Entity (e.g., MME 162), other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway (e.g., PDN Gateway 172). The MME 162 may communicate with a Home Subscriber Server (HSS) (e.g., HSS 174). The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All User Internet Protocol (IP) packets are transmitted through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area for a particular broadcast service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0067] The core network 190 may include an Access and Mobility Management Function (AMF) (e.g., AMF 192), other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) (e.g., UPF 195). The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All User Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0068] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission and reception point (TRP), network node, network entity, network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of the CU, DU, and / or RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN). The base station 102 provides an access point for the UE 104 to the EPC 160 or the core network 190.

[0069] Examples of UEs include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, gaming consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other device with a similar function. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). The UE may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation. One or more of these devices may access the network jointly and / or access the network individually.

[0070] Referring again to Figure 1, in some aspects, a device communicating with a network entity, such as a UE 104 communicating with one of the base stations 102 in a base station or a component of a base station (e.g., CU 106, DU 105, and / or RU 109), may be configured to manage one or more aspects of wireless communication. For example, UE 104 may have a UE interruption handling component 198, which may be configured to facilitate handling of an interruption of a satellite-based communication link due to blockage of LOS propagation. In some aspects, UE interruption handling component 198 may be configured to determine the interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle blocking the LOS propagation of the satellite-based communication link. Example UE interruption handling component 198 may also be configured to avoid performing one or more communication link correction processes during a time period associated with the interruption.

[0071] In another configuration, a network entity, such as one of satellite 107, base station 102, or a component of a base station (e.g., CU 106, DU 105, and / or RU 109), may be configured to manage one or more aspects of wireless communication. For example, one of base station 102 or satellite 107 may have an NW interruption handling component 199, which may be configured to facilitate handling of an interruption of a satellite-based communication link due to blockage of LOS propagation. In some aspects, NW interruption handling component 199 may be configured to determine the interruption of the satellite-based communication link based in part on UE location information and blockage information of an obstacle blocking the LOS propagation of the satellite-based communication link with the UE. Example NW interruption handling component 199 may also be configured to avoid scheduling communication with the UE during a time period associated with the interruption.

[0072] Aspects disclosed herein facilitate a UE and / or a network entity predicting the occurrence of an interruption of a communication link due to blockage of LOS propagation between the UE and a satellite, thereby facilitating satellite-based communication of the UE. In some aspects, based on the predicted interruption, the UE and the network entity may avoid performing at least one process to mitigate the impact of the interruption of the communication link.

[0073] The deployment of a communication system, such as a 5G NR system, can be arranged with various components or constituent parts in various ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in a centralized architecture or a split architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit-receive point (TRP), or cell, etc.) can be implemented as a centralized base station (also referred to as a stand-alone BS or monolithic BS) or a split base station.

[0074] A centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A split base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed among one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0075] Base station operation or network design can consider the aggregation characteristics of base station functionality. For example, split base stations can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting can include distributing functionality across two or more units at various physical locations and virtually distributing the functionality of at least one unit, which can achieve flexibility in network design. The various units of a split base station or a split RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0076] For example, Figure 2A diagram showing an example of the architecture of an exemplary decomposed base station 200 is presented. The architecture of the decomposed base station 200 may include one or more CUs (e.g., CU 210), which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) (e.g., near RT RIC 225) via an E2 link, or a non-real-time (non RT) RIC 215 associated with a service management and orchestration (SMO) framework (e.g., SMO framework 205), or both. The CU 210 may communicate with one or more DUs (e.g., DU 230) via a corresponding midhaul link, such as an F1 interface. The DU 230 may communicate with one or more RUs (e.g., RU 240) via a corresponding fronthaul link. The RU 240 may communicate with a corresponding UE (e.g., UE 204) via one or more radio frequency (RF) access links. In some specific implementations, the UE 204 may be served simultaneously by multiple RUs.

[0077] Each unit (i.e., CU (e.g., CU 210), DU (e.g., DU 230), RU (e.g., RU 240), and near RT RIC (e.g., near RT RIC 225), non RT RIC (e.g., non RT RIC 215), and SMO framework 205) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive signals or transmit signals or both to one or more of the other units via a wireless transmission medium.

[0078] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), or Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some specific implementations, the CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bi-directionally with the CU-CP units via an interface such as the E1 interface. As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0079] The DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, the DU 230 may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high Physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, or demodulation, etc.) at least partially based on a functional split (such as those defined by 3GPP). In some aspects, the DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 230 or with the control functions hosted by the CU 210.

[0080] The lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both at least partially based on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communication with one or more UEs (e.g., UE 204). In some specific implementations, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 240 may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU 210 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0081] The SMO framework 205 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, the CU, DU, RU, and near-RT RIC. In some specific embodiments, the SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific embodiments, the SMO framework 205 can communicate directly with one or more RUs via the O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0082] The non-RT RIC 215 can be configured to include a logical function that can implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225 (such as via the A1 interface). The near-RT RIC 225 can be configured to include a logical function that can achieve near-real-time control and optimization of RAN elements and resources through an interface (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs, one or more DUs, or both, and the O-eNB to the near-RT RIC 225.

[0083] In some specific embodiments, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 225 and can be received from non-network data sources or from network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 can be configured to regulate RAN behavior or performance. For example, the non-RT RIC 215 can monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 205 (such as via reconfiguration of the O1) or via the creation of RAN management policies (such as A1 policies).

[0084] At least one of CU 210, DU 230, and RU 240 may be referred to as base station 202. Thus, base station 202 may include one or more of CU 210, DU 230, and RU 240 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 202). Base station 202 provides an access point to core network 220 for UE 204. The communication link between an RU (e.g., RU 240) and a UE (e.g., UE 204) may include an uplink (UL) (also referred to as a reverse link) transmission from UE 204 to RU 240 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 240 to UE 204.

[0085] Some UEs may use D2D communication (e.g., D2D communication link 258) to communicate with each other. D2D communication link 258 may use DL / UL WWAN spectrum. D2D communication link 258 may use one or more sidelink channels. D2D communication may be through various wireless D2D communication systems, such as for example Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0086] The wireless communication system may also include a Wi-Fi AP 250 that communicates with UE 204 (also referred to as a Wi-Fi STA) via a communication link 254, such as in the 5 GHz unlicensed spectrum etc. When communicating in the unlicensed spectrum, UE204 / Wi-Fi AP 250 may perform CCA before communication to determine whether the channel is available.

[0087] Base station 202 and UE 204 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 202 may transmit a beamformed signal 282 to UE 204 in one or more transmission directions. UE 204 may receive the beamformed signal from base station 202 in one or more reception directions. UE 204 may also transmit a beamformed signal 284 to base station 202 in one or more transmission directions. Base station 202 may receive the beamformed signal from UE 204 in one or more reception directions. Base station 202 / UE 204 may perform beam training to determine the best reception direction and the best transmission direction for each of base station 202 / UE 204. The transmission direction and the reception direction of base station 202 may be the same or may not be the same. The transmission direction and the reception direction of UE 204 may be the same or may not be the same.

[0088] The core network 220 may include an Access and Mobility Management Function (AMF) (e.g., AMF 261), a Session Management Function (SMF) (e.g., SMF 262), a User Plane Function (UPF) (e.g., UPF 263), a Unified Data Management (UDM) (e.g., UDM 264), one or more location servers 268, and other functional entities. The AMF 261 is a control node that processes signaling between the UE 204 and the core network 220. The AMF 261 supports registration management, connection management, mobility management, and other functions. The SMF 262 supports session management and other functions. The UPF 263 supports packet routing, packet forwarding, and other functions. The UDM 264 supports the generation of Authentication and Key Agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 268 are illustrated as including a Gateway Mobile Location Center (GMLC) (e.g., GMLC 265) and a Location Management Function (LMF) (e.g., LMF 266). However, in general, one or more location servers 268 may include one or more location / locationing servers, and the one or more location / locationing servers may include one or more of the GMLC 265, LMF 266, a Position Determination Entity (PDE), a Serving Mobile Location Center (SMLC), or a Mobile Positioning Center (MPC), etc. The GMLC 265 and LMF 266 support UE location services. The GMLC 265 provides an interface for clients / applications (e.g., emergency services) to access UE location information. The LMF 266 receives measurement results and assistance information from the NG-RAN and the UE 204 via the AMF 261 to calculate the location of the UE 204. The NG-RAN may utilize one or more locationing methods to determine the location of the UE 204. Locating the UE 204 may involve signal measurements, location estimation, and optional rate calculations based on these measurements. The signal measurements may be performed by the UE 204 and / or the base station 202 serving the UE 204. The measured signals may be based on a Satellite Positioning System (SPS) 270 (e.g., a Global Navigation Satellite System (GNSS), a Global Positioning System (GPS), a Non-Terrestrial Network (NTN), or one or more of other satellite positioning / location systems), an LTE signal, a Wireless Local Area Network (WLAN) signal, a Bluetooth signal, a Terrestrial Beacon System (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR Enhanced Cell ID (NR E-CID) method, an NR signal (e.g., multi-Round Trip Time (multi-RTT), DL Angle of Departure (DL-AoD), DL Time Difference of Arrival (DL-TDOA), UL Time Difference of Arrival (UL-TDOA), and UL Angle of Arrival (UL-AoA) locationing), and / or one or more of other systems / signals / sensors.

[0089] A wireless device (such as UE 204) may include a UE interruption handling component 198, which may be configured to facilitate handling of an interruption of a satellite-based communication link due to blockage of LOS propagation, as described in the example associated with Figure 1 .

[0090] In some aspects, a base station (such as the split base station 200) or a component of the base station may include an NW interruption handling component 199, which may be configured to facilitate handling of an interruption of a satellite-based communication link due to blockage of LOS propagation, as described in the example associated with Figure 1 .

[0091] Figure 3A FIG. 300 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 3B FIG. 330 is a diagram illustrating an example of a DL channel within a 5G NR subframe. Figure 3C FIG. 350 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 3D FIG. 380 is a diagram illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD) (where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL), or may be time division duplexing (TDD) (where for a specific set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In the examples provided in Figure 3A , Figure 3C , the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3, 4 are shown as having slot formats 1, 28 respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0, 1 are full DL, full UL respectively. The other slot formats 2 to 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by the received slot format indicator (SFI) (configured dynamically by DL control information (DCI) or semi-statically / statically by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0092] Figures 3A to 3DA frame structure is illustrated, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. The subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. The symbols on the DL may be cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration may be scaled by 1 / SCS.

[0093]

[0094] Table 1: Parameter sets, SCS, and CP

[0095] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 time slots per subframe, respectively. For extended CP, parameter set 2 allows 4 time slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols per time slot and 2 μ time slots per subframe. As shown in Table 1, the subcarrier spacing may be equal to 2 μ * 15 kHz, where μ is parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 3A to 3D An example is provided with normal CP having 14 symbols per time slot and parameter set μ = 2 having 4 time slots per subframe. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 3B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0096] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0097] As Figure 3A illustrated, some of the REs in the RE carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (designated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0098] Figure 3B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six resource element groups (REGs), each REG including 12 consecutive RES in the OFDM symbols of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring occasion on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of the frame. The PSS is used by the UE to determine subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be in symbol 4 of a particular subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and the SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as system information blocks (SIBs)), and paging messages.

[0099] As Figure 3CAs illustrated, some of the REs in the RE carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the previous one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and according to the specific PUCCH format used, the PUCCH DM-RS may be transmitted in different configurations. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0100] Figure 3D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0101] Figure 4 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. In Figure 4 the example illustrated, the first wireless device may include a base station 410, the second wireless device may include a UE 450, and the base station 410 may communicate with the UE 450 in an access network. As Figure 4 shown, the base station 410 includes a transmit processor (TX processor 416), a transmitter 418Tx, a receiver 418Rx, an antenna 420, a receive processor (RX processor 470), a channel estimator 474, a controller / processor 475, and a memory 476. An example UE 450 includes an antenna 452, a transmitter 454Tx, a receiver 454Rx, an RX processor 456, a channel estimator 458, a controller / processor 459, a memory 460, and a TX processor 468. In other examples, the base station 410 and / or the UE 450 may include additional or alternative components.

[0102] In DL, Internet Protocol (IP) packets can be provided to a controller / processor 475. The controller / processor 475 implements layer 3 and layer 2 functionality. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with the broadcast of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering of RLC data PDUs; and MAC layer functionality associated with the mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0103] The TX processor 416 and the RX processor 470 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the Physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 416 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). Then, the encoded and modulated symbols may be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined together using the inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is precoded in space to generate multiple spatial streams. Channel estimates from the channel estimator 474 may be used to determine the encoding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 450 and / or channel state feedback. Each spatial stream may then be provided to a different antenna in the antenna 420 via a separate transmitter (e.g., transmitter 418Tx). Each transmitter 418Tx may modulate a radio frequency (RF) carrier using the corresponding spatial stream for transmission.

[0104] At the UE 450, each receiver 454Rx receives signals via its corresponding antenna in the antenna 452. Each receiver 454Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 456. The TX processor 468 and the RX processor 456 implement Layer 1 functionality associated with various signal processing functions. The RX processor 456 may perform spatial processing on the information to recover any spatial streams destined for the UE 450. In the case where multiple spatial streams are destined for the UE 450, the RX processor 456 may combine two or more of the multiple spatial streams into a single OFDM symbol stream. The RX processor 456 then uses the fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 410. These soft decisions may be based on the channel estimates calculated by the channel estimator 458. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 410 on the physical channel. The data and control signals are then provided to the controller / processor 459, which implements Layer 3 and Layer 2 functionality.

[0105] The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. In the UL, the controller / processor 459 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 459 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0106] Similar to the functionality described in connection with DL transmission by the base station 410, the controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0107] Channel estimates derived by the channel estimator 458 from reference signals or feedback transmitted by the base station 410 may be used by the TX processor 468 to select appropriate decoding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 468 may be provided to different antennas in the antenna 452 via separate transmitters (e.g., transmitter 454Tx). Each transmitter 454Tx may modulate an RF carrier using the corresponding spatial stream for transmission.

[0108] UL transmission is processed at the base station 410 in a manner similar to that described in connection with the receiver functionality at the UE 450. Each receiver 418Rx receives signals via its corresponding antenna in the antenna 420. Each receiver 418Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 470.

[0109] The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. In the UL, the controller / processor 475 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing, to recover IP packets. The controller / processor 475 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0110] At least one of TX processor 468, RX processor 456, and controller / processor 459 may be configured to perform aspects related to Figure 1 the UE interruption handling component 198 of

[0111] At least one of TX processor 416, RX processor 470, and controller / processor 475 may be configured to perform aspects related to Figure 1 the NW interruption handling component 199 of

[0112] Figure 5 Example 500 illustrates communication between devices as presented herein. For example, a first UE 502 may send a communication 514, which may be received by a second UE 504, a third UE 506, and / or a fourth UE 508. In some examples, the communication 514 may be received directly from the first UE 502, e.g., without being sent through a base station. Additionally or alternatively, an RSU 507 may receive communications from and / or send communications to the first UE 502, the second UE 504, the third UE 506, and / or the fourth UE 508. As Figure 5 shown, the RSU 507 may send a communication 518 that is received directly from the RSU 507.

[0113] In addition to operating as a receiving device, each of the first UE 502, the second UE 504, the third UE 506, the fourth UE 508, and / or the RSU 507 may also be capable of operating as a sending device. Thus, the second UE 504 is illustrated as sending a second communication 513 and a third communication 515, the third UE 506 is illustrated as sending a fourth communication 516, and the fourth UE 508 is illustrated as sending a fifth communication 520. One or more of the communications may be broadcast or multicast to nearby devices. For example, the first UE 502 may send a communication intended to be received by other UEs within the range 501 of the first UE 502. In other examples, one or more of the communications may be multicast to nearby devices that are members of a group. In other examples, one or more of the communications may be unicast from one UE to another UE.

[0114] Figure 6 is a diagram illustrating an example environment 600 that may support satellite-based communication for a UE 604, as presented herein. In Figure 6 the illustrated example, the UE 604 may send or receive satellite-based communications (e.g., via satellite-based 3GPP NTN or a dedicated satellite communication system). For example, a first satellite 606 may provide coverage to the UE 604 located within the coverage area 608 of the first satellite 606. In some aspects, the coverage area 608 may represent the field of view of the first satellite 606.

[0115] In Figure 6 the illustrated example, the first satellite 606 communicates with the UE 604 via the service link 610. The service link 610 may include a radio link that provides wireless communication between the UE 604 and the first satellite 606.

[0116] The first satellite 606 may radiate different beams. Additionally, each of the different beams may be associated with a corresponding coverage area (e.g., beam coverage area 612) having a boundary at the ground level (e.g., at the Earth's surface). Thus, the UE 604 may receive signals from one beam of the first satellite 606 via the service link 610 while being located within the corresponding beam coverage area.

[0117] In Figure 6 the illustrated example, the satellite-based gateway 614 connects the UE 604 to the data network 616 via the communication link 618. The satellite-based gateway 614 may include an earth station or a gateway located at the Earth's surface. The satellite-based gateway 614 may provide sufficient RF power and RF sensitivity for accessing satellites (such as the first satellite 606 and / or the second satellite 620). The satellite-based gateway 614 may be a transport network layer (TNL) node.

[0118] In some aspects, the first satellite 606 may be configured to communicate directly with the satellite-based gateway 614 via the first feeder link 622. The first feeder link 622 may include a radio link that provides wireless communication between the first satellite 606 and the satellite-based gateway 614.

[0119] In other aspects, the first satellite 606 may communicate with the satellite-based gateway 614 via one or more other satellites. For example, the first satellite 606 and the second satellite 620 may be part of a satellite constellation that communicates via an inter-satellite link (ISL). In Figure 6 the example, the first satellite 606 may establish an ISL 624 with the second satellite 620. The ISL 624 may be a radio interface or an optical interface and operate in the RF frequency or optical band, respectively. The second satellite 620 may communicate with the satellite-based gateway 614 via the second feeder link 626.

[0120] In Figure 6In the illustrated example, the first satellite 606 and / or the second satellite 620 may include airborne devices such as UAS platforms, balloons, unmanned aircraft, UAVs, etc. Examples of satellites that can be used for satellite-based communication include spacecraft placed in low Earth orbit (LEO), medium Earth orbit (MEO), geostationary orbit (GEO), or highly elliptical orbit (HEO). Examples of UAS platforms that can be used for satellite-based communication include systems that include tethered UAS (TUA), lighter-than-air UAS (LTA), heavier-than-air UAS (HTA), and high-altitude platforms (HAP).

[0121] In some aspects, the first satellite 606 and / or the second satellite 620 may implement a transparent payload (sometimes referred to as a "bent pipe" payload). For example, after receiving a signal, a transparent satellite may have the ability to change the frequency carrier of the signal, perform RF filtering on the signal, and amplify the signal before outputting the signal. In such aspects, the signal output by the transparent satellite may be a repeated signal, where the waveform of the output signal has not changed relative to the received signal.

[0122] In other aspects, the first satellite 606 and / or the second satellite 620 may implement a regenerative payload. For example, a regenerative satellite may have the ability to perform all or part of the base station functions, such as transforming and amplifying the received signal via on-board processing before outputting the signal. In some such aspects, the transformation of the received signal may refer to digital processing, which may include demodulating, decoding, switching, and / or routing, re-encoding, re-modulating, and / or filtering the received signal.

[0123] In an example where a satellite implements a transparent payload, the transparent satellite may communicate with a ground base station via a satellite-based gateway 614. In some such examples, the ground base station may facilitate communication between the satellite-based gateway 614 and the data network 616. In an example where a satellite implements a regenerative payload, the regenerative satellite may have an on-board base station. In some such examples, the on-board base station may communicate with the data network 616 via the satellite-based gateway 614. In some examples, the on-board base station may include a DU and a CU, such as Figure 1 DU 105 and CU 106. In some examples, the on-board base station may include a DU that communicates with a corresponding CU on the ground.

[0124] In Figure 6In an example, the UE 604 and the satellite-based communication system maintain the location information of the UE 604. For example, the first satellite 606 may maintain the UE location information (e.g., the location information of the UE 604, the rate of the UE, the traveling speed of the UE, the traveling direction of the UE, etc.) to perform a beam management process. In some examples, the satellite-based communication system may maintain the UE location information because the services available for the UE 604 may be bound to the location of the UE 604. For example, the beam coverage area may be a large beam coverage area and may extend beyond the boundaries of a country in some scenarios. In some such examples, the UE 604 may be located within the beam coverage area of the first satellite 606 but outside the country where the UE is served. For example, the UE 604 may be registered with the network operator of the first country. When traveling within the first country, the UE 604 may be served by the beam of the first satellite 606. At a later time, the UE 604 may travel outside the first country to a second country, and the beam coverage area of the beam serving the UE 604 may overlap with at least a part of the second country. In some such examples, even though the UE 604 may be served by the same beam in the first country and the second country, the UE 604 may not be registered for service in the second country. Therefore, based on the location information indicating that the UE 604 is within the second country, the UE 604 may not receive any communication services or may receive simplified communication services compared to when the UE 604 is within the first country.

[0125] In some examples, the UE 604 and / or the satellite-based communication system may obtain the UE location information via a satellite positioning system such as GNSS, GPS, NTN, or other satellite positioning / location systems. In some examples, the UE 604 may position itself and report its UE location information to the satellite-based communication system. However, in other examples, other techniques may be used to position the location of the UE 604.

[0126] The satellite-based wireless channel between the UE 604 and the first satellite 606 may be characterized by strong LOS propagation. In some aspects, when the UE 604 is a stationary UE (e.g., a non-mobile UE or a fixed UE), the UE 604 may have strong LOS propagation. In some such examples, the location of the UE 604 may be planned such that at least one antenna of the UE 604 may have an unobstructed sky view field, and thus strong LOS propagation between the UE 604 and the first satellite 606 may be achieved.

[0127] However, in some aspects, the UE 604 can be non-stationary, such as a connected vehicle. For example, a connected vehicle can be equipped with a rooftop antenna that facilitates satellite-based communication at the connected vehicle. A non-stationary UE such as a connected vehicle (e.g., a UE with mobility capabilities) may experience blockage of LOS propagation. For example, the UE 604 can travel under an overpass or interchange that may block the communication link between the UE 604 and the first satellite 606 with LOS propagation. In some such aspects, the blockage of LOS propagation may cause an interruption of the connection (e.g., communication link) between the UE and the satellite-based communication system. For example, the blockage may cause an interruption of the serving link 610 between the UE 604 and the first satellite 606.

[0128] In some aspects of wireless communication, an interruption of a connection (e.g., communication link), even a brief interruption (e.g., due to passing under an overpass), may cause a degradation of communication performance at the UE. For example, after the UE detects an interruption of the communication link, the UE can initiate one or more corrective processes to correct the interruption of the communication link. Performing one or more communication link corrective processes may be associated with signaling overhead, which may cause communication latency.

[0129] For example, after the UE detects an interruption of the communication link, the UE can trigger a declaration of RLF, which can cause the UE to perform one or more processes to re-establish the radio link (or communication link). In some aspects, after the UE detects an interruption of the communication link, the UE can release the RRC connection, which can cause the UE to perform one or more processes (e.g., random access process) to establish a new RRC connection. In some aspects, after the UE detects an interruption of the communication link, the UE can perform a beam steering process to search for a new satellite. In some aspects, after the UE detects an interruption of the communication link, the UE can perform a process to re-establish (or re-acquire) the communication link with the satellite.

[0130] Aspects disclosed herein provide techniques for predicting the occurrence of an interruption of a communication link between a UE and a satellite, such as due to an obstacle that causes blockage of LOS propagation between the UE and the satellite. For example, the disclosed techniques include using information about the obstacle (e.g., blockage information) to predict an interruption of the satellite-based communication link between the UE and the satellite. A network entity (e.g., the first satellite 606, the satellite-based gateway 614, a terrestrial base station, a vehicle-mounted base station, a component of a base station, etc.) of the satellite-based communication system and the UE can then exchange information about the predicted interruption. In some aspects disclosed herein, the network entity and the UE can perform at least one action to mitigate the impact from the predicted interruption (e.g., mitigate disruption to satellite-based communication based on the interruption).

[0131] Figure 7 Illustrates a portion of a digital map 700 as presented herein. The digital map 700 is a graphical representation of an area stored in digital format. The digital map 700 may include topological information of the area and / or location information of landmarks (such as roads, bridges, overpasses, exits, etc.).

[0132] In Figure 7 the illustrated example, the digital map 700 includes an indication of a UE 704. The UE 704 may correspond to a connected vehicle that is moving and may experience service interruption due to the blockage of predictable LOS propagation. For example, the UE 704 may include a vehicle (such as Figure 7 shown) like a car, a train, a ship, etc., that is traveling under an obstacle (such as an overpass, an interchange, a bridge, etc.) with a known position. In Figure 7 the orientation of the illustrated example, the UE 704 is traveling in direction 720 from left to right. The path of the UE 704 may be based on the position information of the UE 704 mapped to the digital map 700. For example, based on the position information of the UE 704 and the direction 720, the path of the UE 704 may be mapped to a first road 706 via the digital map 700.

[0133] The example digital map 700 also includes indications of landmarks, such as an indication of a first road 706, an indication of an obstacle 708, an indication of a second road 722, an indication of an exit 724, and an indication of a building 726. In Figure 7 the illustrated example, the obstacle 708 includes an overpass. The digital map 700 may include position information associated with the landmarks (e.g., the first road 706, the obstacle 708, the second road 722, the exit 724, and the building 726). This position information may include coordinate and size information. For example, the position information of the obstacle 708 may include geographical coordinates 728 that provide the position and dimensions of the obstacle 708. The position information of the obstacle 708 may also include size information 730 corresponding to the dimensions of the obstacle 708 that may block LOS propagation.

[0134] In Figure 7 the example, the obstacle 708 may correspond to an obstacle that may block the LOS between the UE 704 and a satellite 714 (such as Figure 6 the first satellite 606). For example, at time T0, the UE 704 may be located at a first position, and a first signal 716 may travel directly (e.g., without being reflected by an object) between the UE 704 and the satellite 714. The first signal 716 may be via a communication link between the UE 704 and the satellite 714 (such as Figure 6communicated by the service link 610). However, at time T2, the UE 704 may be at a second position below the obstacle 708. In such a scenario, the second signal 718 between the UE 704 and the satellite 714 may be blocked by the obstacle 708. That is, when the UE 704 travels under the obstacle 708, the obstacle 708 may interrupt the communication link between the UE 704 and the satellite 714.

[0135] The digital map 700 may be accessed by the UE 704 and / or the satellite 714. In some examples, the digital map 700 may be stored at the UE 704 and / or the satellite 714. In some examples, the digital map 700 may be stored on a server accessible by the UE 704 and / or the satellite 714. The server may be operated by a network operator or a third party. In some examples, the digital map 700 may be updated periodically, aperiodically, or as a one-time event. For example, when the digital map 700 is locally stored at the UE 704 and / or the satellite 714, the operator may periodically provide an update to the digital map 700 with one or more changes. For example, the first iteration of the digital map may include Figure 7 landmarks of the digital map 700, and the second iteration of the digital map may include new roads.

[0136] As described above, the prediction device may predict the occurrence of an interruption of the communication link based on the obstacle. For example, the UE 704 or a network entity (e.g., the satellite 714) may be configured to predict an interruption due to the blockage of LOS propagation caused by the obstacle 708. The prediction device may use the location information of the UE 704 (e.g., UE location information, rate information of the UE 704, speed information of the UE 704, etc.) and the blockage information of the obstacle 708 (e.g., location information, size information, etc.) to predict the interruption. In some examples, the prediction device may also use information about the satellite (e.g., location information, mobility information, etc.) to predict the interruption.

[0137] In some examples, the prediction device may predict the interruption duration associated with the predicted interruption. For example, based on the size of the obstacle 708 (e.g., size information 730) and the speed of the UE, the prediction device may predict the amount of time during which the communication link between the UE 704 and the satellite 714 may be interrupted. In some examples, the speed of the UE may be known to the prediction device. For example, the UE 704 may provide UE location information including the coordinates of the UE 704 and the current traveling speed of the UE 704. In other examples, the speed of the UE may be determined based on the change of the UE location information over time.

[0138] In Figure 7In the illustrated example, the UE 704 is at the first position at time T0. Based on the direction 720, the speed of the UE 704, and the size information 730 of the obstacle 708, it can be predicted that the UE 704 will travel under the obstacle 708 at time T1 and leave under the obstacle 708 at time T3. Therefore, the prediction device can predict the amount of time during which the communication link between the UE 704 and the satellite 714 may be interrupted based on the interruption duration 710 corresponding to the difference between time T3 and time T1.

[0139] To help the UE 704 and the satellite 714 mitigate the impact of the interruption, the prediction device can provide an indication of the interruption to another device (e.g., a non-prediction device). The indication can indicate the predicted interruption of the communication link between the UE 704 and the satellite 714. In some examples, the indication can also include time information related to the interruption. For example, the indication can include the duration of a time period and a start time offset. The duration of the time period can correspond to the amount of time during which the UE 704 and the satellite 714 can perform at least one action to mitigate the impact of the interruption. The start time offset can indicate whether the duration of the time period starts at a future time (e.g., based on a non-zero value) or at the current time (e.g., based on a zero value).

[0140] In some examples, the start time offset can indicate that the duration of the time period starts at a future time. For example, in Figure 7 the example, the UE 704 can receive an indication of the predicted interruption from the satellite 714 at time T0. The indication can include the duration of the time period corresponding to the interruption duration 710. The indication can also include a start time offset that indicates the amount of time before the interruption duration 710 starts based on the interval 712. In Figure 7 the example, the interval 712 can correspond to the difference between time T1 and time T0. For example, the interruption duration 710 can be five seconds and the interval 712 can be ten seconds. In such a scenario, the UE 704 and the satellite 714 can wait for ten seconds before performing at least one action to mitigate the impact of the interruption of the communication link within the interruption duration 710.

[0141] In some examples, the start time offset can indicate that the duration of the time period starts at the current time (e.g., when the UE 704 receives an indication of the predicted interruption from the satellite 714 at time T0). In some such examples, the indication can include the duration of the time period corresponding to the difference between time T3 and time T0. For example, in the above example, based on the five seconds associated with the interruption duration 710 and the ten seconds associated with the interval 712, the duration of the time period can be 15 seconds. Additionally, the indication can include a start time offset that indicates that the start time of the duration of the time period is the current time.

[0142] Figure 8 Illustrates an example communication flow 800 between a first device 802 and a second device 804 as presented herein. The first device 802 and the second device 804 may be components of a satellite-based communication system. For example, the first device 802 may be implemented by a UE, and the second device 804 may be implemented by a network entity. In other examples, the first device 802 may be implemented by a network entity, and the second device 804 may be implemented by a UE. The network entity may be implemented by a satellite or a ground-based device. The network entity may be implemented by a satellite, an AMF, a base station, or components of a base station (e.g., a CU, a DU, and / or an RU), etc.

[0143] In Figure 8 the illustrated example, the communication flow 800 facilitates each of the first device 802 and the second device 804 to take at least one action to mitigate the impact of a predicted interruption due to an obstacle blocking the LOS propagation between the UE and the satellite for satellite-based communication. The prediction device may predict the interruption based on the information available to the prediction device. In Figure 8 the example, the first device 802 is a device capable of predicting an interruption of a communication link (such as Figure 6 the serving link 610) between the UE and the satellite. The second device 804 is a device capable of receiving an indication of the interruption from the first device 802. The first device 802 and the second device 804 may also each perform at least one action to reduce the impact of the interruption of the communication link between the UE and the satellite.

[0144] In Figure 8 the illustrated example, the first device 802 may predict an interruption of the communication link based on the information available to the first device 802 (such as UE location information and blocking information). For example, the first device 802 may execute a process 810 to access the UE location information 812 of the UE. The UE location information 812 may include the coordinates of the UE, may include the rate of the UE (e.g., the traveling speed of the UE and the traveling direction of the UE), etc. In some aspects, the first device 802 may access the UE location information 812 via a satellite positioning system. In some aspects, the first device 802 may receive the UE location information 812 from the second device 804. For example, in a scenario where the second device 804 is implemented by a UE, the second device 804 may have the ability to locate its position and subsequently provide the UE location information 812 to the first device 802.

[0145] The first device 802 may execute process 814 to access blockage information 816 for an obstacle that blocks LOS propagation between the UE and the satellite. The blockage information 816 may include location information of the obstacle (e.g., geographical coordinates of the obstacle), may include size information of the obstacle (e.g., dimensions), etc. The obstacle may be an object that blocks LOS propagation and has a location available to the first device 802. For example, the first device 802 may access the blockage information 816 via a digital map (such as Figure 7 the digital map 700). In Figure 8 the illustrated example, the first device 802 may access the digital map 806 to obtain location information of landmarks represented by the digital map 806. In some examples, the digital map 806 may be locally stored at the first device 802. For example, the digital map 806 may be stored in the memory or storage device of the first device 802. In some examples, the digital map 806 may be stored at a server accessible to the first device 802. The server may be operated by a network operator (e.g., an operator of a satellite-based communication system) or may be operated by a third party.

[0146] In Figure 8 the illustrated example, the first device 802 executes process 820 to predict an interruption 822 of the communication link, for example, based on UE location information 812 and blockage information 816. In some examples, the first device 802 may predict the interruption 822 based on a formula or equation having an input that includes UE location information 812 and blockage information 816.

[0147] In some examples, the first device 802 may predict the interruption 822 by identifying the current path that the UE is traveling on (e.g., a road, highway, waterway, train route, etc.). For example, the first device 802 may use the digital map 806 to identify the current path of the UE based on UE location information 812 (e.g., coordinates of the UE). The first device 802 may then parse the digital map 806 to identify any obstacles that overlap the current path. For example, and referring to Figure 7 the example of, the first device 802 may use UE location information 812 and the digital map 806 to identify that the UE 704 is traveling on a first road 706. The first device 802 may also use the direction of travel of the UE704 (e.g., direction 720) and the digital map 806 to identify that the obstacle 708 overlaps the first road 706 and may thus cause an interruption of the communication link between the UE and the satellite. However, other examples may employ additional or alternative techniques for predicting the interruption 822 based at least on UE location information 812 and blockage information 816.

[0148] An interruption 822 may be associated with an interruption duration 824. The interruption duration 824 may correspond to the amount of time that a corresponding obstacle may block the LOS propagation between the UE and the satellite. In some examples, the first device 802 may predict the interruption duration 824 based on the UE location information 812 and the blocking information 816. For example, the first device 802 may use the blocking information 816 to determine the size of the corresponding obstacle. The first device 802 may use the UE location information 812 to determine the traveling speed of the UE. In such scenarios, the first device 802 may predict the interruption duration 824 associated with the interruption 822 based on the size of the obstacle and the traveling speed of the UE. In some examples, the interruption duration 824 may include a time buffer to account for uncertainties such as the size of the obstacle and / or the speed of the UE.

[0149] In Figure 8 the illustrated example, the first device 802 provides (e.g., sends or outputs) an indication 826, which is obtained by the second device 804. In some aspects, the first device 802 may provide the indication 826 to the second device 804 via RRC signaling. In some aspects, the first device 802 may provide the indication 826 to the second device 804 in a MAC - control element (MAC - CE). In some aspects, the first device 802 may provide the indication 826 to the second device 804 via control information. For example, in a scenario where the first device 802 is implemented by a network entity and the second device 804 is implemented by a UE, the first device 802 may provide the indication 826 to the second device 804 via downlink control information. In other scenarios where the first device 802 is implemented by a UE and the second device 804 is implemented by a network entity, the first device 802 may provide the indication 826 to the second device 804 via uplink control information.

[0150] In Figure 8 the example, the indication 826 indicates the interruption 822 to the second device 804. In some examples, the indication 826 may indicate a time period 828 associated with the interruption duration 824. The time period 828 may include a time period duration 830 and a start time offset 832. The time period duration 830 may indicate the amount of time that the first device 802 and the second device 804 may perform at least one action based on the prediction of the interruption 822. For example, the UE and the satellite may set a timer with a value corresponding to the time period duration 830. In some such examples, when the timer is active, the UE and the satellite may perform at least one action to mitigate the impact of the interruption 822.

[0151] The start time offset 832 may indicate a delay from the current time at which a timer associated with the time period duration 830 may be active. For example, the second device 804 may receive the indication 826 at the current time and wait for an amount of time corresponding to the start time offset 832 to activate the timer associated with the time period duration 830. In some examples, the start time offset 832 may indicate activation of the timer at a future time (e.g., the start time offset 832 may indicate a non-zero offset). For example, and referring to Figure 7 the example of, the start time offset 832 may indicate that the interruption duration 710 starts after the interval 712. For example, the start time offset 832 may indicate that the interruption duration 824 of the interruption 822 is five seconds (e.g., the interruption duration 710 is five seconds) and the interruption time starts within ten seconds (e.g., the interval 712 is ten seconds). In some such scenarios, the second device 804 may not start performing one or more actions to mitigate the impact of the interruption in response to receiving the indication 826. For example, the second device 804 may wait for the duration of the interval 712 before performing one or more actions to mitigate the impact of the interruption.

[0152] In some examples, the start time offset 832 may indicate activation of the timer at the current time (e.g., without delay or offset). For example, and referring to Figure 7 the example of, the time period duration 830 may indicate an amount of time corresponding to the interruption duration 710 and the interval 712. For example, and referring to the above example, the time period duration 830 may indicate an amount of time of 15 seconds corresponding to the interruption duration 710 and the interval 712. In some such examples, the second device 804 may start performing one or more actions to mitigate the impact of the interruption in response to receiving the indication 826. For example, the second device 804 may start an interruption timer having an amount of time corresponding to the time period duration 830.

[0153] In some examples, the indication 826 may be an implicit indication of the interruption 822. For example, a network entity may provide the indication 826, which may be configured to cause the UE to transition to a sleep mode for a certain period of time. In the sleep mode (sometimes referred to as a "low power mode"), the UE may deactivate communication functions and thus allow the UE to be unaffected by the interruption 822. In some examples, a network entity may provide the indication 826, which may be configured to cause the UE to maintain its current configuration and / or skip performing one or more actions for a certain period of time. For example, the indication 826 may be configured to cause the UE not to perform downlink measurements, not to perform uplink transmissions, not to change its beam pointing direction, etc. for a certain period of time. In some examples, the UE may provide the indication 826, which may indicate to the network entity that the UE is not available for communication with the network for a certain period of time. In examples where the indication 826 corresponds to an implicit indication, the period of time may correspond to the interruption duration 824 or the time period 828.

[0154] As Figure 8 shown, the first device 802 may perform at least one of the first actions 840 to mitigate the impact of the interruption 822 during the time period 828. Additionally, the second device 804 may perform at least one of the second actions 842 based on the indication 826 to mitigate the impact of the interruption 822 during the time period 828. The first action 840 and the second action 842 may respectively enable the first device 802 and the second device 804 to operate as if there were no traffic to schedule during the time period 828. For example, the network entity may avoid (e.g., steer clear of, suppress, skip, or forgo) scheduling communication with the UE during the time period 828.

[0155] Additionally, the UE may avoid (e.g., steer clear of, suppress, skip, or forgo) monitoring downlink communication from the satellite during the time period 828. The UE may also avoid sending uplink communication to the satellite during the time period 828. For example, at a certain time, the PUSCH may be scheduled for uplink transmission, or the PUCCH may be triggered for uplink transmission, and this time overlaps with the time when the timer associated with the time period duration 830 is active. In some such examples, the UE may skip sending uplink communication during the time period 828. In another example, periodic resources for the UE's uplink communication may be allocated, for example, via a configured grant. If the periodic resources overlap with the time when the timer associated with the time period duration 830 is active, the UE may avoid sending uplink communication during the time period 828.

[0156] In some aspects, performing at least one of the first actions 840 and / or at least one of the second actions 842 may include avoiding performing one or more procedures. For example, during the time period 828, the UE may avoid (e.g., steer clear of, suppress, skip, or forgo) performing one or more procedures to correct the communication link. In some examples, the UE may avoid declaring RLF during the time period 828. In some examples, the UE may avoid performing the RRC connection release procedure during the time period 828. In some examples, the UE may avoid performing the beam steering procedure during the time period 828. In some examples, the UE may avoid performing the connection reestablishment (or reacquisition) procedure with the satellite during the time period 828.

[0157] Figure 9Illustrates an example communication flow 900 between a network entity 902 and a UE 904 as presented herein. One or more aspects described for the network entity 902 may be performed by a satellite, a base station, or components of a base station or network entity, such as a CU, DU, RU, and / or AMF. In the illustrated example, the communication flow 900 facilitates the UE 904 and the network entity 902 to take actions to mitigate the impact of interruptions caused by obstacles blocking the LOS propagation of satellite-based communication.

[0158] Aspects of the network entity 902 may be performed by Figure 1 satellite 107 of Figure 1 one of the base stations 102 of Figure 4 and / or base station 410 of Figure 1 Aspects of the UE 904 may be performed by Figure 4 UE 104 of Figure 9 and / or one of the UEs 450 of

[0159] In some aspects, the network entity 902 may detect an interruption. For example, the network entity 902 may execute process 910 and detect an interruption. The network entity 902 may detect an interruption based on UE location information and blocking information, such as Figure 8 UE location information 812 and blocking information 816 of Figure 7 respectively. In some aspects, the network entity 902 may obtain or access blocking information via a digital map, such as Figure 8 digital map 700 of Figure 8 and / or digital map 806 of

[0160] Aspects of detecting an interruption are described in connection with Figure 8 interruption 822 of

[0161] In Figure 9In the illustrated example, network entity 902 provides network indication 918 received by UE 904. Network entity 902 may provide network indication 918 via RRC signaling, in a MAC-CE, and / or in DCI. In some examples, network indication 918 may indicate an interruption and a time period 940 associated with the interruption duration. Time period 940 may include a time period duration and a start time offset. In some examples, time period 940 may correspond to a time window of a future time. For example, the start time offset may indicate a non-zero value to indicate that the time period duration starts at a future time (e.g., a time offset from the current time). In some examples, the start time offset of time period 940 may indicate that the time period duration starts at the current time.

[0162] In some aspects, the UE may detect an interruption. For example, UE 904 may execute procedure 912 and detect an interruption. UE 904 may detect an interruption based on UE location information and blocking information (such as UE location information 812 and blocking information 816 respectively). Figure 8 In some aspects, UE 904 may obtain or access blocking information via a digital map (such as digital map 700 and / or Figure 7 digital map 806). Aspects of detecting an interruption are described in connection with Figure 8 interruption 822. Figure 8

[0163] UE 904 may execute procedure 916 to predict an interruption duration associated with an interruption. For example, UE 904 may use size information of an obstacle causing the predicted interruption and speed information of UE 904 to predict the amount of time during which the communication link between UE 904 and network entity 902 may be interrupted. Aspects of predicting an interruption duration are described in connection with Figure 8 interruption duration 824.

[0164] In Figure 9 the illustrated example, UE 904 provides UE indication 920, which is obtained (e.g., received) by network entity 902. UE 904 may provide UE indication 920 via RRC signaling, in a MAC-CE, and / or in UCI. In some examples, UE indication 920 may indicate an interruption and a time period 940 associated with the interruption duration. Time period 940 may include a time period duration and a start time offset. In some examples, time period 940 may correspond to a time window of a future time. For example, the start time offset may indicate a non-zero value to indicate that the time period duration starts at a future time (e.g., a time offset from the current time). In some examples, the start time offset of time period 940 may indicate that the time period duration starts at the current time.

[0165] In Figure 9In the illustrated example, time period 940 starts at a first time 942 and ends at a second time 944. In an example where an indication of an interruption (e.g., network indication 918 or UE indication 920) corresponds to the duration of a time period that starts at a future time, the duration of time period 940 may correspond to the interruption duration, such as Figure 7 the interruption duration 710 of Figure 8 and / or Figure 7 the interruption duration 824 of Figure 7 For example, the first time 942 may correspond to Figure 7 time T1 of

[0166] and the second time 944 may correspond to time T3 of this figure. In an example where an indication of an interruption (e.g., network indication 918 or UE indication 920) corresponds to the duration of a time period that starts at the current time, time period 940 may correspond to the interruption duration and an offset before the interruption starts, such as Figure 7 the interruption duration 710 and the interval 712 of

[0167] For example, the first time 942 may correspond to Figure 9 time T0 of

[0168] In Figure 9 In some examples, UE 904 may execute process 924 to start an interruption timer. UE 904 may start the interruption timer to align with time period 940. In an example where the time period duration starts at a future time, UE 904 may wait for an amount of time based on the start time offset to start the interruption timer (e.g., after the interval 712 of

[0169] has elapsed). In an example where the time period duration starts at the current time, then UE 904 may start the interruption timer after receiving network indication 918 or after sending UE indication 920. The duration of the interruption timer may correspond to the time period duration (e.g., the amount of time that an obstacle may block LOS propagation and interrupt communication between UE 904 and network entity 902).

[0167] In Figure 9 In an example, network entity 902 and UE 904 may provide network indication 918 and UE indication 920, respectively, such that network entity 902 and UE 904 each know about the predicted interruption. After receiving the indication, both network entity 902 and UE 904 may perform at least one action, and the at least one action may mitigate (or reduce) the impact of the interruption.

[0168] In Figure 9 In an example, network entity 902 may execute process 926 to avoid scheduling communication with UE 904 within time period 940. For example, network entity 902 may avoid scheduling downlink communication with UE 904 within time period 940. Additionally or alternatively, network entity 902 may avoid scheduling uplink communication with UE 904 within time period 940.

[0169] AsFigure 9 As shown, after the expiration of the time period 940 associated with the interruption, the network entity 902 may execute process 932 to resume scheduling communication with the UE 904. For example, the network entity 902 may schedule downlink communication with the UE 904 at a time after the second time 944 in the time domain. Additionally or alternatively, the network entity 902 may schedule uplink communication with the UE 904 at a time after the second time 944 in the time domain.

[0170] In Figure 9 In the illustrated example, based on the predicted interruption, the UE 904 may perform at least one action to mitigate the impact of the interruption. For example, within the time period 940, the UE 904 may execute process 928 to avoid performing one or more communication link calibration processes. In some examples, the UE 904 may avoid declaring RLF within the time period 940. In some examples, the UE 904 may avoid performing an RRC connection release process within the time period 940. In some examples, the UE 904 may avoid performing a beam steering process within the time period 940. In some examples, the UE 904 may avoid performing a connection re-establishment (or reacquisition) process with a satellite within the time period 940.

[0171] In some aspects, the UE 904 executes process 930 to avoid communicating with a satellite within the time period 940, thereby facilitating satellite-based communication. For example, the UE 904 may avoid monitoring downlink communication from the satellite and / or the network entity 902. Additionally or alternatively, the UE 904 may avoid transmitting uplink communication within the time period 940. In some examples, the UE 904 may not change its downlink beam pointing direction and / or its uplink beam pointing direction within the time period 940.

[0172] As Figure 9 shown, after the expiration of the time period 940 associated with the interruption, the UE 904 may execute process 934 to resume communication with the satellite and / or the network entity 902. For example, the UE 904 may receive downlink communication (e.g., PDCCH or PDSCH) from the network entity 902 at a time after the second time 944 in the time domain and / or may transmit uplink communication (e.g., PUCCH or PUSCH) to the network entity 902. Additionally, the UE 904 may resume communication with the same satellite with which it communicated prior to the time period 940. For example, and referring to Figure 6 the example of, the UE 604 may communicate with the first satellite 606 prior to the time period 940, may avoid communicating with the first satellite 606 within the time period 940, and may resume communicating with the first satellite 606 after the time period 940.

[0173] UE 904 may also communicate with the satellite after time period 940 using the same beam configuration as before time period 940. For example, as described in connection with process 930, UE 904 may not change its downlink beam pointing direction and / or its uplink beam pointing direction within time period 940. Thus, after time period 940 concludes, the downlink beam pointing direction and / or the uplink beam pointing direction are the same as before time period 940.

[0174] In some examples, network indication 918 provided by network entity 902 may correspond to an implicit indication of an interruption. For example, network indication 918 may be configured to cause UE 904 to transition to a sleep mode instead of indicating the interruption and time period 940. For example, after receiving network indication 918, UE 904 may perform process 922 to transition to the sleep mode. Network indication 918 may indicate a period of time for which UE 904 is to remain in the sleep mode. In some examples, the period of time may be based on the interruption duration or time period 940. For example, network indication 918 may be configured to cause UE 904 to transition to the sleep mode until after time period 940 concludes.

[0175] In some examples, network indication 918 provided by network entity 902 may configure UE 904 to perform or avoid performing one or more actions for a period of time. For example, network indication 918 may be configured to cause UE 904 not to perform downlink measurements for the period of time. In some examples, network indication 918 may be configured to cause UE 904 not to perform uplink transmissions for the period of time. In some examples, network indication 918 may be configured to cause UE 904 not to change its beam pointing direction for the period of time. In some examples, the period of time may be based on the interruption duration or time period 940. Thus, UE 904 may not perform downlink measurements, may not perform uplink transmissions, may not change its beam pointing direction, etc., until time period 940 concludes.

[0176] In some examples, UE indication 920 provided by UE 904 may be configured to indicate to network entity 902 that UE 904 is not available for communication with the network for a period of time. In some examples, the period of time may be based on the interruption duration or time period 940. For example, UE indication 920 may indicate to network entity 902 that UE 904 is not available for communication until after time period 940 concludes.

[0177] Figure 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104 and / or Figure 12One of the apparatuses 1204). The method can facilitate improving communication performance associated with satellite-based communication by predicting an interruption and performing one or more actions to mitigate the impact of the interruption.

[0178] At 1002, the UE determines an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link, as described in at least conjunction with Figure 8 interruption 822 and / or Figure 9 process 912. The determination of the interruption at 1002 can be performed by Figure 12 the UE interruption handling component 198 of the apparatus 1204.

[0179] At 1004, the UE avoids performing one or more communication link calibration processes during a time period associated with the interruption, as described in at least conjunction with Figure 8 at least one action of the first action 840 or at least one action of the second action 842 and / or Figure 9 process 928 or process 930. The avoidance of performing the one or more communication link calibration processes at 1004 can be performed by Figure 12 the UE interruption handling component 198 of the apparatus 1204.

[0180] Figure 11 is a flowchart 1100 of a method of wireless communication. The method can be performed by a UE (e.g., UE 104 and / or Figure 12 one of the apparatuses 1204). The method can facilitate improving communication performance associated with satellite-based communication by predicting an interruption and performing one or more actions to mitigate the impact of the interruption.

[0181] At 1112, the UE determines an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks LOS propagation of the satellite-based communication link, as described in at least conjunction with Figure 8 interruption 822 and / or Figure 9 process 912. The determination of the interruption at 1112 can be performed by Figure 12 the UE interruption handling component 198 of the apparatus 1204.

[0182] At 1114, the UE avoids performing one or more communication link calibration processes during a time period associated with the interruption, as described in at least conjunction with Figure 8 at least one action of the first action 840 or at least one action of the second action 842 and / or Figure 9described by process 928 or process 930. In some examples, the one or more communication link correction processes may include the declaration of RLF. In some examples, the one or more communication link correction processes may include an RRC connection release process. In some examples, the one or more communication link correction processes may include a new satellite search process. In some examples, the one or more communication link correction processes may include a beam search process. Avoiding the execution of the one or more communication link correction processes at 1114 may be performed by Figure 12 the UE interruption handling component 198 of the device 1204.

[0183] In some examples, the UE may avoid communicating via the satellite-based communication link based on the interruption. For example, at 1116, the UE may avoid monitoring downlink communication during the time period, such as at least in combination with Figure 8 the first action 840 and the second action 842 and / or Figure 9 described by process 930. Additionally, at 1118, the UE may avoid sending uplink communication during the time period, such as at least in combination with Figure 8 the first action 840 and the second action 842 and / or Figure 9 described by process 930. Avoiding communicating via the satellite-based communication link at 1116 and 1118 may be performed by Figure 12 the UE interruption handling component 198 of the device 1204.

[0184] At 1120, after the time period associated with the interruption is completed, the UE may resume communication via the satellite-based communication link, such as at least in combination with Figure 9 described by process 934. Resuming communication via the satellite-based communication link at 1120 may be performed by Figure 12 the UE interruption handling component 198 of the device 1204.

[0185] In some examples, the UE may (e.g., at 1112) determine the interruption based on the received indication. For example, at 1102, the UE may receive an indication associated with the interruption, such as at least in combination with Figure 8 the indication 826 and / or Figure 9 described by the network indication 918. In some examples, the UE may receive the indication via RRC signaling. In some examples, the UE may receive the indication via MAC-CE. In some examples, the UE may receive the indication via DCI. Receiving the indication at 1102 may be performed by Figure 12 the UE interruption handling component 198 of the device 1204.

[0186] In some examples, the indication may indicate the time period, which includes the time period duration and a start time offset of a future time.

[0187] In some examples, the indication may indicate the time period, which includes the time period duration and a start time offset of a current time. In some such examples, the UE may start a timer after receiving the indication, as described in conjunction with Figure 9 procedure 924.

[0188] In some examples, the indication may be configured to cause the UE to transition to a sleep mode within the duration of the time based on the time period, as described in conjunction with at least Figure 9 procedure 922.

[0189] In some examples, the indication may be configured to cause the UE to avoid performing the one or more communication link calibration procedures within the duration of the time based on the time period, as described in conjunction with at least one of the actions in the second action 842 of Figure 8 and / or Figure 9 procedure 928.

[0190] In some examples, the UE may determine the interruption (e.g., at 1112) based on performing a prediction of the interruption. For example, at 1104, the UE may detect the interruption based on the UE location information and the blocking information, as described in conjunction with at least Figure 8 procedure 820 and / or Figure 9 procedure 912. The detection of the interruption at 1104 may be performed by the UE interruption handling component 198 of the apparatus 1204 of Figure 12 .

[0191] At 1106, the UE may access the blocking information via a digital map, as described in conjunction with at least Figure 8 digital map 806 and blocking information 816. The access to the blocking information at 1106 may be performed by the UE interruption handling component 198 of the apparatus 1204 of Figure 12 .

[0192] At 1108, the UE may predict the time period associated with the interruption, as described in conjunction with at least Figure 8 interruption duration 824 and / or Figure 9 procedure 916. The prediction of the time period at 1108 may be performed by the UE interruption handling component 198 of the apparatus 1204 of Figure 12 .

[0193] At 1110, the UE may send an indication of the time period, as described in conjunction with at least Figure 8 indication 826 and / or Figure 9as described by UE indication 920. In some examples, the UE may send the indication via RRC signaling. In some examples, the UE may send the indication via MAC-CE. In some examples, the UE may send the indication via UCI. The sending of the indication at 1110 may be performed by Figure 12 the UE interruption handling component 198 of the apparatus 1204.

[0194] In some examples, the indication may indicate the time period, which includes the time period duration and the start time offset of a future time.

[0195] In some examples, the indication may indicate the time period, which includes the time period duration and the start time offset of the current time.

[0196] In some examples, the indication may indicate the duration of the time when the UE is not available for communication via the satellite-based communication link, as described at least in conjunction with Figure 8 the first action 840 and / or Figure 9 UE indication 920. The duration of this time may be based on the time period.

[0197] Figure 12FIG. 1200 is an illustration of an example of a hardware implementation for device 1204. Device 1204 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 1204 may include a cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers (e.g., cellular RF transceiver 1222). The cellular baseband processor 1224 may include on-chip memory 1224'. In some aspects, device 1204 may also include one or more subscriber identity module (SIM) cards 1220 and an application processor 1206, which is coupled to a secure digital (SD) card 1208 and a screen 1210. The application processor 1206 may include on-chip memory 1206'. In some aspects, device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., GNSS module), one or more sensor modules 1218 (e.g., barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), additional memory modules 1226, a power supply 1230, and / or a camera 1232. The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). The Bluetooth module 1212, the WLAN module 1214, and the SPS module 1216 may include their own dedicated antennas and / or communicate using one or more antennas 1280. The cellular baseband processor 1224 communicates with one of the UEs in UE 104 and / or with the RU associated with network entity 1202 via one or more antennas 1280 through a transceiver (e.g., cellular RF transceiver 1222). The cellular baseband processor 1224 and the application processor 1206 may each include computer-readable media / memory, such as on-chip memory 1224' and on-chip memory 1206', respectively. The additional memory modules 1226 may also be considered computer-readable media / memory. Each computer-readable media / memory (e.g., on-chip memory 1224', on-chip memory 1206', and / or additional memory modules 1226) may be non-transitory. The cellular baseband processor 1224 and the application processor 1206 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1224 / application processor 1206, causes the cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1224 / application processor 1206 when executing the software.The cellular baseband processor 1224 / applications processor 1206 may be components of the UE 450 and may include the memory 460 and / or at least one of the TX processor 468, RX processor 456, and controller / processor 459. In one configuration, the device 1204 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 1224 and / or applications processor 1206, while in another configuration, the device 1204 may be the entire UE (e.g., see Figure 4 the UE 450) and include additional modules of the device 1204.

[0198] As discussed above, the UE interruption handling component 198 may be configured to determine an interruption of the satellite-based communication link based, in part, on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link; and avoid performing one or more communication link correction procedures during a time period associated with the interruption.

[0199] The UE interruption handling component 198 may be within the cellular baseband processor 1224, applications processor 1206, or both the cellular baseband processor 1224 and applications processor 1206. The UE interruption handling component 198 may be one or more hardware components specifically configured to perform the processes / algorithms, implemented by one or more processors configured to perform the processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above.

[0200] As shown, the device 1204 may include various components configured for various functions. For example, the UE interruption handling component 198 may include one or more hardware components that perform Figure 10 and / or Figure 11 each block in the algorithms of the flowcharts.

[0201] In one configuration, the device 1204 (and in particular the cellular baseband processor 1224 and / or applications processor 1206) may include: means for determining an interruption of the satellite-based communication link based, in part, on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link. The exemplary device 1204 further includes: means for avoiding performing one or more communication link correction procedures during a time period associated with the interruption.

[0202] In another configuration, the exemplary device 1204 further includes: means for avoiding monitoring downlink communication during the time period. The exemplary device 1204 further includes: means for avoiding transmitting uplink communication during the time period.

[0203] In another configuration, example apparatus 1204 further includes components for resuming communication via the satellite-based communication link after the expiration of the time period associated with the interruption.

[0204] In another configuration, example apparatus 1204 further includes components for receiving an indication associated with the interruption.

[0205] In another configuration, example apparatus 1204 further includes components for starting a timer after receiving the indication.

[0206] In another configuration, example apparatus 1204 further includes components for receiving the indication via at least one of RRC signaling, via MAC-CE, and downlink control information.

[0207] In another configuration, example apparatus 1204 further includes components for detecting the interruption based on the UE location information and the blockage information. Example apparatus 1204 further includes components for predicting the time period associated with the interruption. Example apparatus 1204 further includes components for sending an indication of the time period.

[0208] In another configuration, example apparatus 1204 further includes components for accessing the blockage information via a digital map.

[0209] In another configuration, example apparatus 1204 further includes components for sending the indication via at least one of RRC signaling, via MAC-CE, and uplink control information.

[0210] The components may be the UE interruption handling component 198 of apparatus 1204 configured to perform the functions recited by the components. As described above, apparatus 1204 may include a TX processor 468, an RX processor 456, and a controller / processor 459. Thus, in one configuration, the components may be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions recited by the components.

[0211] Figure 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a network node (e.g., Figure 15 one of base station 102 and / or network entity 1502). The method may facilitate improving communication performance associated with satellite-based communication by predicting an interruption and performing one or more actions to mitigate the impact of the interruption.

[0212] At 1302, the network node determines an interruption of the satellite-based communication link based at least in part on UE location information and obstruction information of an obstruction that blocks the LOS propagation of the satellite-based communication link with the UE, as described in at least interruption 822 in conjunction with Figure 8 and / or Figure 9 process 912. The determination of the interruption at 1302 may be performed by the NW interruption handling component 199 of the network entity 1502 in Figure 15 .

[0213] At 1304, the network node avoids scheduling communication with the UE during a time period associated with the interruption, as described in at least one action of the first action 840 in conjunction with Figure 8 and / or at least one action of the second action 842 and / or Figure 9 process 926. The avoidance of scheduling communication at 1304 may be performed by the NW interruption handling component 199 of the network entity 1502 in Figure 15 .

[0214] Figure 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a network node (e.g., Figure 15 base station 102 and / or one of network entities 1502). The method may facilitate improving communication performance associated with satellite-based communication by predicting an interruption and performing one or more actions to mitigate the effects of the interruption.

[0215] At 1412, the network node determines an interruption of the satellite-based communication link based at least in part on UE location information and obstruction information of an obstruction that blocks the LOS propagation of the satellite-based communication link with the UE, as described in at least interruption 822 in conjunction with Figure 8 and / or Figure 9 process 912. The determination of the interruption at 1412 may be performed by the NW interruption handling component 199 of the network entity 1502 in Figure 15 .

[0216] At 1414, the network node avoids scheduling communication with the UE during a time period associated with the interruption, as described in at least one action of the first action 840 in conjunction with Figure 8 and / or at least one action of the second action 842 and / or Figure 9 process 926. The avoidance of scheduling communication at 1414 may be performed by the NW interruption handling component 199 of the network entity 1502 in Figure 15 .

[0217] At 1416, after the time period associated with the interruption has ended, the network node may resume scheduling the communication with the UE via the satellite-based communication link, as described at least in conjunction with Figure 9 process 932. The resumption of the scheduling at 1416 may be performed by Figure 15 the NW interruption handling component 199 of network entity 1502.

[0218] In some examples, the network node may (e.g., at 1412) determine the interruption based on a received indication. For example, at 1402, the network node may receive an indication associated with the interruption, as described at least in conjunction with Figure 8 indication 826 and / or Figure 9 UE indication 920. In some examples, the network node may receive the indication via RRC signaling. In some examples, the network node may receive the indication via MAC-CE. In some examples, the network node may receive the indication via UCI. The reception of the indication at 1402 may be performed by Figure 15 the NW interruption handling component 199 of network entity 1502.

[0219] In some examples, the indication may indicate the time period, which includes the time period duration and the start time offset of a future time.

[0220] In some examples, the indication may indicate the time period, which includes the time period duration and the start time offset of the current time.

[0221] In some examples, the indication may indicate the duration of the time when the UE is not available for communication via the satellite-based communication link, and the duration of the time is based on the time period, as described at least in conjunction with Figure 8 the first action 840 and / or Figure 9 UE indication 920.

[0222] In some examples, the network entity may (e.g., at 1412) determine the interruption based on performing a prediction of the interruption. For example, at 1404, the network node may detect the interruption based on the UE location information and the blockage information, as described at least in conjunction with Figure 8 process 820 and / or Figure 9 process 910. The detection of the interruption at 1404 may be performed by Figure 15 the NW interruption handling component 199 of network entity 1502.

[0223] In some examples, at 1406, the network node may access the blockage information via a digital map, as described at least in conjunction with Figure 8described by the digital map 806 and the congestion information 816. The access to the congestion information at 1406 can be performed by Figure 15 the NW interruption handling component 199 of the network entity 1502.

[0224] At 1408, the network node can predict the time period associated with the interruption, such as at least in combination with Figure 8 the interruption duration 824 and / or Figure 9 the process 914 as described. The prediction of the time period at 1408 can be performed by Figure 15 the NW interruption handling component 199 of the network entity 1502.

[0225] At 1410, the network node can provide an indication of the time period, such as at least in combination with Figure 8 the indication 826 and / or Figure 9 the network indication 918 as described. In some examples, the network node can provide the indication via RRC signaling. In some examples, the network node can provide the indication via MAC-CE. In some examples, the network node can provide the indication via DCI. The provision of the indication at 1410 can be performed by Figure 15 the NW interruption handling component 199 of the network entity 1502.

[0226] In some examples, the indication can indicate the time period, which includes the time period duration and the start time offset of the future time.

[0227] In some examples, the indication can indicate the time period, which includes the time period duration and the start time offset of the current time.

[0228] In some examples, the indication can be configured to cause the UE to transition to the sleep mode within the duration of the time based on the time period, such as at least in combination with Figure 9 the process 922 as described.

[0229] In some examples, the indication can be configured to cause the UE to avoid performing one or more communication link calibration processes within the duration of the time based on the time period, such as at least in combination with Figure 8 the second action 842 and / or Figure 9 the action 928 as described.

[0230] Figure 15FIG. 1500 is a diagram illustrating an example of a hardware implementation for network entity 1502. Network entity 1502 may be a BS, a component of a BS, or may implement BS functionality. Network entity 1502 may include at least one of CU 1510, DU 1530, or RU 1540. For example, network entity 1502 may include CU 1510 according to the layer functionality handled by NW interruption handling component 199; both CU 1510 and DU 1530; each of CU 1510, DU 1530, and RU 1540; DU 1530; both DU 1530 and RU 1540; or RU 1540. CU 1510 may include CU processor 1512. CU processor 1512 may include on-chip memory 1512'. In some aspects, additional memory modules 1514 and communication interface 1518 may also be included. CU 1510 communicates with DU 1530 via an intermediate link (such as the F1 interface). DU 1530 may include DU processor 1532. DU processor 1532 may include on-chip memory 1532'. In some aspects, DU 1530 may also include additional memory modules 1534 and communication interface 1538. DU 1530 communicates with RU 1540 via a fronthaul link. RU 1540 may include RU processor 1542. RU processor 1542 may include on-chip memory 1542'. In some aspects, RU 1540 may also include additional memory modules 1544, one or more transceivers 1546, antenna 1580, and communication interface 1548. RU 1540 communicates with one of the UEs in UE 104. The on-chip memory (e.g., on-chip memory 1512', on-chip memory 1532', and / or on-chip memory 1542') and / or the additional memory modules (e.g., additional memory modules 1514, additional memory modules 1534, and / or additional memory modules 1544) may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of CU processor 1512, DU processor 1532, and RU processor 1542 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0231] As discussed above, NW interruption handling component 199 may be configured to determine an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link with the UE; and avoid scheduling communication with the UE during a time period associated with the interruption.

[0232] The NW interruption handling component 199 may be located within one or more processors of one or more of the CU 1510, DU 1530, and RU 1540. The NW interruption handling component 199 may be one or more hardware components specifically configured to execute the process / algorithm, implemented by one or more processors configured to execute the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above.

[0233] The network entity 1502 may include various components configured for various functions. For example, the NW interruption handling component 199 may include one or more hardware components that execute Figure 13 and / or Figure 14 each box in the algorithm in the flowchart of.

[0234] In one configuration, the network entity 1502 may include: components for determining an interruption of the satellite-based communication link based at least in part on UE location information and blocking information of an obstacle blocking the LOS propagation of the satellite-based communication link with the UE. The example network entity 1502 further includes: components for avoiding scheduling communication with the UE during the time period associated with the interruption.

[0235] In another configuration, the example network entity 1502 further includes: components for resuming scheduling communication with the UE via the satellite-based communication link after the expiration of the time period associated with the interruption.

[0236] In another configuration, the example network entity 1502 further includes: components for receiving an indication associated with the interruption.

[0237] In another configuration, the example network entity 1502 further includes: components for receiving the indication via at least one of RRC signaling, via MAC-CE, and uplink control information.

[0238] In another configuration, the example network entity 1502 further includes: components for detecting the interruption based on the UE location information and the blocking information. The example network entity 1502 further includes: components for predicting the time period associated with the interruption. The example network entity 1502 further includes: components for providing an indication of the time period.

[0239] In another configuration, the example network entity 1502 further includes: components for accessing the blocking information via a digital map.

[0240] In another configuration, the example network entity 1502 further includes: components for providing the indication via at least one of RRC signaling, via MAC-CE, and downlink control information.

[0241] The component can be the NW interruption handling component 199 of the network entity 1502 configured to perform the functions described by the component. As described above, the network entity 1502 can include a TX processor 416, an RX processor 470, and a controller / processor 475. Thus, in one configuration, the component can be the TX processor 416, the RX processor 470, and / or the controller / processor 475 configured to perform the functions described by the component.

[0242] Aspects disclosed herein provide techniques for predicting the occurrence of an interruption of a communication link between a UE and a satellite, such as due to an obstacle blocking LOS propagation via the communication link. For example, the disclosed techniques include using location information of the obstacle to predict when an interruption of a satellite-based communication link between the UE and the satellite may occur, thereby facilitating satellite-based communication. The network and the UE can then exchange information about the predicted interruption. In some aspects disclosed herein, the network and the UE can perform one or more actions to mitigate the effects from the predicted interruption.

[0243] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely illustrative of example approaches. It should be understood that, based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Additionally, some blocks can be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0244] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and elements recited in the foregoing description and claims in singular form are not meant to mean "one and only one" but "one or more." Terms such as "if," "when," and "while" do not denote a direct temporal relationship or reaction. That is, these phrases (e.g., "when...") do not imply an immediate action in response to or during the occurrence of an action, but simply imply that the action will occur if the condition is met, without requiring a specific or immediate time limitation for the occurrence of the action. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or having an advantage over other aspects. Unless specifically stated otherwise, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "any combination of A, B, C, or any of them" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. A set should be construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first and second devices, or indirectly between the first and second devices through a collection of devices. A device configured to "output" data (such as, a transmission, signal, or message) may, for example, transmit the data with a transceiver, or may convey the data to a device that transmits the data. A device configured to "obtain" data (such as, a transmission, signal, or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data. All structural and functional equivalents of the elements of the aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims.Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims. The terms "module", "mechanism", "element", "device", etc. shall not be used in place of the term "component". Accordingly, no claim element shall be construed as a means-plus-function unless the element is expressly recited using the phrase "means for".

[0245] As used herein, the phrase "based on" shall not be construed to mean a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) shall be construed as "at least based on A", unless specifically stated otherwise.

[0246] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0247] Aspect 1 is a method for wireless communication at a UE, the method comprising: determining an interruption of a satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks the LOS propagation of the satellite-based communication link; and avoiding performing one or more communication link correction procedures during a time period associated with the interruption.

[0248] Aspect 2 is the method according to aspect 1, the method further comprising: the one or more communication link correction procedures include at least one of the following: declaration of RLF; RRC connection release procedure; new satellite search procedure; and beam search procedure.

[0249] Aspect 3 is the method according to any one of aspects 1 and 2, the method further comprising: avoiding monitoring downlink communication during the time period; and avoiding transmitting uplink communication during the time period.

[0250] Aspect 4 is the method according to any one of aspects 1 to 3, the method further comprising: resuming communication via the satellite-based communication link after the time period associated with the interruption has elapsed.

[0251] Aspect 5 is the method according to any one of aspects 1 to 4, the method further comprising: receiving an indication associated with the interruption.

[0252] Aspect 6 is the method according to any one of aspects 1 to 5, the method further comprising: the indication indicates the time period, the time period including a time period duration and a start time offset of a future time.

[0253] Aspect 7 is the method according to any one of Aspects 1 to 5, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of the current time, and the method further comprising: starting a timer after receiving the indication.

[0254] Aspect 8 is the method according to any one of Aspects 1 to 5, the method further comprising: the indication being configured to cause the UE to transition to a sleep mode within the duration of the time based on the time period.

[0255] Aspect 9 is the method according to any one of Aspects 1 to 5, the method further comprising: the indication being configured to cause the UE to avoid performing the one or more communication link calibration processes within the duration of the time based on the time period.

[0256] Aspect 10 is the method according to any one of Aspects 1 to 9, the method further comprising: receiving the indication via at least one of RRC signaling, via MAC-CE, and downlink control information.

[0257] Aspect 11 is the method according to any one of Aspects 1 to 4, the method further comprising: detecting the interruption based on the UE location information and the blocking information; predicting the time period associated with the interruption; and sending an indication of the time period.

[0258] Aspect 12 is the method according to any one of Aspects 1 to 4 and 11, the method further comprising: accessing the blocking information via a digital map.

[0259] Aspect 13 is the method according to any one of Aspects 1 to 4, 11, and 12, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of a future time.

[0260] Aspect 14 is the method according to any one of Aspects 1 to 4, 11, and 12, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of the current time.

[0261] Aspect 15 is the method according to any one of Aspects 1 to 4, 11, and 12, the method further comprising: the indication indicating the duration of the time when the UE is not available for communication via the satellite-based communication link, the duration of the time being based on the time period.

[0262] Aspect 16 is the method according to any one of Aspects 1 to 4 and 11 to 15, the method further comprising: sending the indication via at least one of RRC signaling, via MAC-CE, and uplink control information.

[0263] Aspect 17 is an apparatus for wireless communication at a UE, the apparatus including at least one processor coupled to a memory and configured to implement any one of Aspects 1 to 16.

[0264] In aspect 18, the apparatus according to aspect 17 further includes: at least one antenna coupled to the at least one processor.

[0265] In aspect 19, the apparatus according to aspect 17 or 18 further includes: a transceiver coupled to the at least one processor.

[0266] Aspect 20 is an apparatus for wireless communication, the apparatus including components for implementing any one of Aspects 1 to 16.

[0267] In aspect 21, the apparatus according to aspect 20 further includes: at least one antenna coupled to the components for performing the method according to any one of Aspects 1 to 16.

[0268] In aspect 22, the apparatus according to aspect 20 or 21 further includes: a transceiver coupled to the components for performing the method according to any one of Aspects 1 to 16.

[0269] Aspect 23 is a non-transitory computer-readable storage medium storing computer-executable code, where the code, when executed, causes a processor to implement any one of Aspects 1 to 16.

[0270] Aspect 24 is a method for wireless communication at a network entity, the method including: determining an interruption of a satellite-based communication link based at least in part on UE location information and blocking information of an obstacle blocking LOS propagation of the satellite-based communication link with the UE; and avoiding scheduling communication with the UE during a time period associated with the interruption.

[0271] Aspect 25 is the method according to aspect 24, the method further including: after the time period associated with the interruption is completed, resuming scheduling communication with the UE via the satellite-based communication link.

[0272] Aspect 26 is the method according to any one of aspects 24 and 25, the method further including: receiving an indication associated with the interruption.

[0273] Aspect 27 is the method according to any one of aspects 24 to 26, the method further including: the indication indicating the time period, the time period including a time period duration and a start time offset of a future time.

[0274] Aspect 28 is the method according to any one of aspects 24 to 26, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of the current time.

[0275] Aspect 29 is the method according to any one of aspects 24 to 26, the method further comprising: the indication indicating the duration of the time when the UE is not available for communication via the satellite-based communication link, the duration of the time being based on the time period.

[0276] Aspect 30 is the method according to any one of aspects 24 to 29, the method further comprising: the at least one processor being configured to receive the indication via at least one of RRC signaling, via MAC-CE, and uplink control information.

[0277] Aspect 31 is the method according to any one of aspects 24 and 25, the method further comprising: detecting the interruption based on the UE location information and the blocking information; predicting the time period associated with the interruption; and providing an indication of the time period.

[0278] Aspect 32 is the method according to any one of aspects 24 to 25 and 31, the method further comprising: accessing the blocking information via a digital map.

[0279] Aspect 33 is the method according to any one of aspects 24 to 25, 31 and 32, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of a future time.

[0280] Aspect 34 is the method according to any one of aspects 24 to 25, 31 and 32, the method further comprising: the indication indicating the time period, the time period including a time period duration and a start time offset of the current time.

[0281] Aspect 35 is the method according to any one of aspects 24 to 25, 31 and 32, the method further comprising: the indication being configured to cause the UE to transition to a sleep mode during the duration of the time based on the time period.

[0282] Aspect 36 is the method according to any one of aspects 24 to 25, 31 and 32, the method further comprising: the indication being configured to cause the UE to avoid performing the one or more communication link calibration processes during the duration of the time based on the time period.

[0283] Aspect 37 is the method according to any one of aspects 24 to 25 and 31 to 36, the method further comprising: providing the indication via at least one of RRC signaling, via MAC-CE, and downlink control information.

[0284] Aspect 38 is a device for wireless communication at a network entity, the device comprising: at least one processor, the at least one processor coupled to a memory and configured to implement according to any one of aspects 24 to 37.

[0285] In aspect 39, the device according to aspect 38 further comprises: at least one antenna, the at least one antenna coupled to the at least one processor.

[0286] In aspect 40, the device according to aspect 38 or 39 further comprises: a transceiver, the transceiver coupled to the at least one processor.

[0287] Aspect 41 is a device for wireless communication, the device comprising components for implementing any one of aspects 24 to 37.

[0288] In aspect 42, the device according to aspect 41 further comprises: at least one antenna, the at least one antenna coupled to the components for performing the method according to any one of aspects 24 to 37.

[0289] In aspect 43, the device according to aspect 41 or 42 further comprises: a transceiver, the transceiver coupled to the components for performing the method according to any one of aspects 24 to 37.

[0290] Aspect 44 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code when executed causes a processor to implement according to any one of aspects 24 to 37.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured to: determine an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks line-of-sight (LOS) propagation of the satellite-based communication link; and avoid performing one or more communication link calibration procedures during a period associated with the interruption.

2. The apparatus according to claim 1, wherein the one or more communication link calibration procedures include at least one of the following: declaration of a radio link failure (RLF); a radio resource control (RRC) connection release procedure; a new satellite search procedure; and a beam search procedure.

3. The apparatus according to claim 1, the apparatus further comprising: at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to: avoid monitoring downlink communication during the period; and avoid transmitting uplink communication during the period.

4. The apparatus according to claim 1, wherein the at least one processor is further configured to: restore communication via the satellite-based communication link after the period associated with the interruption has ended.

5. The apparatus according to claim 1, wherein the at least one processor is further configured to: receive an indication associated with the interruption.

6. The apparatus according to claim 5, wherein the indication indicates the period, the period including a period duration and a start time offset of a future time.

7. The apparatus according to claim 5, wherein the indication indicates the period, the period including a period duration and a start time offset of a current time, and wherein the at least one processor is further configured to: start a timer after receiving the indication.

8. The apparatus according to claim 5, wherein the indication is configured to cause the UE to transition to a sleep mode within a duration of time based on the period.

9. The apparatus according to claim 5, wherein the indication is configured to cause the UE to avoid performing the one or more communication link calibration procedures within a duration of time based on the period.

10. The apparatus according to claim 1, wherein the at least one processor is further configured to: detect the interruption based on the UE location information and the blockage information; predict the period associated with the interruption; and send an indication of the period.

11. The apparatus according to claim 10, wherein the at least one processor is further configured to: access the blockage information via a digital map.

12. The apparatus according to claim 10, wherein the indication indicates the period, the period including a period duration and a start time offset of a future time.

13. The apparatus according to claim 10, wherein the indication indicates the time period, the time period including a time period duration and a start time offset of the current time.

14. The apparatus according to claim 10, wherein the indication indicates the duration of the time when the UE is not available for communication via the satellite-based communication link, the duration of the time being based on the time period.

15. A method for wireless communication at a user equipment (UE), the method comprising: determining an interruption of the satellite-based communication link based at least in part on UE location information and blockage information of an obstacle that blocks line-of-sight (LOS) propagation of the satellite-based communication link; and avoiding performing one or more communication link calibration procedures during a time period associated with the interruption.

16. The method according to claim 15, wherein the one or more communication link calibration procedures include at least one of the following: declaration of a radio link failure (RLF); a radio resource control (RRC) connection release procedure; a new satellite search procedure; a beam search procedure; monitoring downlink communication during the time period; and transmitting uplink communication during the time period.

17. An apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured to: determine an interruption of the satellite-based communication link based at least in part on user equipment (UE) location information and blockage information of an obstacle that blocks line-of-sight (LOS) propagation of the satellite-based communication link with the UE; and avoid scheduling communication with the UE during a time period associated with the interruption.

18. The apparatus according to claim 17, wherein the at least one processor is further configured to: after the time period associated with the interruption has ended, resume scheduling communication with the UE via the satellite-based communication link.

19. The apparatus according to claim 17, wherein the at least one processor is further configured to: receive an indication associated with the interruption.

20. The apparatus according to claim 19, wherein the indication indicates the time period, the time period including a time period duration and a start time offset of a future time.

21. The apparatus according to claim 19, wherein the indication indicates the time period, the time period including a time period duration and a start time offset of the current time.

22. The apparatus according to claim 19, wherein the indication indicates the duration of the time when the UE is not available for communication via the satellite-based communication link, the duration of the time being based on the time period.

23. The apparatus according to claim 17, wherein the at least one processor is further configured to: detect the interruption based on the UE location information and the blockage information; predict the time period associated with the interruption; and provide an indication of the time period.

24. The apparatus according to claim 23, wherein the at least one processor is further configured to: access the blocking information via a digital map.

25. The apparatus according to claim 23, wherein the indication indicates the time period, the time period including a time period duration and a start time offset of a future time.

26. The apparatus according to claim 23, wherein the indication indicates the time period, the time period including a time period duration and a start time offset of a current time.

27. The apparatus according to claim 23, wherein the indication is configured to cause the UE to transition to a sleep mode within a duration of time based on the time period.

28. The apparatus according to claim 23, wherein the indication is configured to cause the UE to avoid performing one or more communication link calibration processes within a duration of time based on the time period.

29. A method for wireless communication at a network entity, the method comprising: determining an interruption of a satellite-based communication link with a user equipment (UE) based at least in part on UE location information and blocking information of an obstacle that blocks line-of-sight (LOS) propagation of the satellite-based communication link with the UE; and avoiding scheduling communication with the UE during a time period associated with the interruption.

30. The method according to claim 29, wherein the method further comprises: After the time period associated with the interruption has elapsed, resuming scheduling communication with the UE via the satellite-based communication link.

Images