Configuration for inter-satellite links

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may communicate with a non-terrestrial network entity over a serving link using a radio configuration. The UE may receive an indication of a topology change event that will occur in association with an inter-satellite link. The UE may communicate over the service link using at least a portion of the radio configuration after the topology change event. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 812,349, filed on July 13, 2022, entitled “CONFIGURATION FOR INTER-SATELLITE LINK,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for using radio configurations involving inter-satellite links. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: communicating with a non-terrestrial network (NTN) entity on a serving link using a radio configuration. The method may include: receiving an indication of a topology change event, the topology change event to occur in association with an inter-satellite link (ISL). The method may include: communicating on the serving link using at least a portion of the radio configuration after the topology change event.

[0008] Some aspects described herein relate to a method of wireless communication performed by an NTN entity. The method may include: communicating with a UE using a radio configuration for a service link. The method may include: sending an indication of a topology change event, the topology change event will occur in association with an ISL and the indication indicates that the service link will be used before and after the topology change event. The method may include: communicating using at least a portion of the radio configuration for the service link after the topology change event.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to communicate with an NTN entity on a service link using a radio configuration. The one or more processors may be configured to receive an indication of a topology change event that will occur in association with an ISL. The one or more processors may be configured to communicate on the service link using at least a portion of the radio configuration after the topology change event.

[0010] Some aspects described herein relate to an NTN for wireless communications. The non-terrestrial network may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to communicate with a UE using a radio configuration for a service link. The one or more processors may be configured to send an indication of a topology change event that will occur in association with an ISL and the indication indicates that the service link will be used before and after the topology change event. The one or more processors may be configured to communicate using at least a portion of the radio configuration for the service link after the topology change event.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to communicate with an NTN entity on a service link using a radio configuration. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication of a topology change event that will occur in association with an ISL. The instruction set, when executed by one or more processors of the UE, may cause the UE to communicate on the service link using at least a portion of the radio configuration after the topology change event.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication via one or more instructions, which, when executed by one or more processors of an NTN entity, may cause the NTN entity to communicate with a UE using a radio configuration for a service link. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to send an indication of a topology change event, which will occur in association with an ISL and the indication indicates that the service link will be used before and after the topology change event. The instruction set, when executed by one or more processors of the NTN entity, may cause the NTN entity to communicate using at least a portion of the radio configuration for the service link after the topology change event.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for communicating with an NTN entity on a service link using a radio configuration. The apparatus may include means for receiving an indication of a topology change event that will occur in association with an ISL. The apparatus may include means for communicating on the service link using at least a portion of the radio configuration after the topology change event.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for communicating with another apparatus using a radio configuration for a service link. The apparatus may include a component for sending an indication of a topology change event, the topology change event will occur in association with an ISL and the indication indicates that the service link will be used before and after the topology change event. The apparatus may include a component for communicating using at least a portion of the radio configuration for the service link after the topology change event.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer readable media, UEs, base stations, network entities, NTN entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of regenerative satellite deployment and an example of transparent satellite deployment in a non-terrestrial network (NTN) according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of inter-satellite link (ISL) activation and an example of ISL deactivation according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of indicating a topology change event according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, by an NTN entity according to the present disclosure.

[0027] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0028] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0029] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0031] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0032] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0033] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0034] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0035] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0036] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0037] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for the network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

[0038] In some aspects, as shown, the cell may be provided by a network entity (e.g., base station 110) of a non-terrestrial network (NTN). As used herein, a "non-terrestrial network" may refer to a network provided with access by a non-terrestrial base station (such as a base station carried by a satellite, balloon, airship, airplane, unmanned aerial vehicle, and / or a high-altitude platform station). A network entity in an NTN (NTN network entity) may use polarization. For example, a network entity in a satellite 135 (NTN network entity) may use circular polarization 136 or linear polarization 138 to send communications to a UE 120. Circular polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space moves around a circle, and the electromagnetic wave may be formed by superimposing two orthogonal linearly polarized waves of equal amplitude and a phase difference of 90 degrees. Circular polarization may be right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). Linear polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space oscillates along a straight line over time.

[0039] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0040] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0041] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0043] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (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 to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] Considering the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may communicate with an NTN entity on a service link using a radio configuration; receive an indication of a topology change event that will occur in association with an inter-satellite link (ISL); and communicate on the service link using at least a portion of the radio configuration following the topology change event. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0047] In some aspects, an NTN network entity (e.g., a base station 110, a network entity, a satellite 135) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may communicate with the UE using a radio configuration for a service link; send an indication of a topology change event that will occur in association with an ISL and that indicates that the service link will be used before and after the topology change event; and communicate using at least a portion of the radio configuration for the service link after the topology change event. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0049] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0050] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data destined for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t). Base station 110 may be an NTN network entity located in a terrestrial location or a non-terrestrial location (eg, satellite 135).

[0051] At the UE 120, a group of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a group of received signals (e.g., R received signals) to a group of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0054] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (e.g., a controller / processor 280) and a memory 282 to perform operations described herein (e.g., reference 1). Figures 4 to 10 )Aspects of any of the methods described herein.

[0055] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 10 )Aspects of any of the methods described herein.

[0056] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of may perform one or more techniques associated with using a radio configuration involving an inter-satellite link. In some aspects, the NTN entity is a network entity at the surface or at a satellite (e.g., 135). For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can execute or guide e.g. Figure 7 The process 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of a network entity and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or the network entity to perform or direct, for example, Figure 7 The process 700 Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0057] In some aspects, the UE includes means for communicating with an NTN entity on a service link using a radio configuration; means for receiving an indication of a topology change event that will occur in association with the ISL; and / or means for communicating on the service link using at least a portion of the radio configuration after the topology change event. Means for UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0058] In some aspects, the NTN entity (e.g., base station 110, network entity, satellite 135) includes: means for communicating with the UE using a radio configuration for a service link; means for sending an indication of a topology change event that will occur in association with the ISL and the indication indicating that the service link will be used before and after the topology change event; and / or means for communicating using at least a portion of the radio configuration for the service link after the topology change event. In some aspects, the means for the NTN entity to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0059] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0061] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0062] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) may be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an 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)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0065] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0066] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0067] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 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, CU 310 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 unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0068] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium 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 and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 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 DU 330 or with control functions hosted by CU 310.

[0069] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control and user planes of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0071] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0074] Figure 4 is a diagram illustrating an example 400 of a regenerative satellite deployment and an example 410 of a transparent satellite deployment in an NTN according to the present disclosure.

[0075] Example 400 illustrates a regenerative satellite deployment. In example 400, UE 120 is served by satellite 420 (e.g., satellite 135) via service link 430. For example, satellite 420 may include a network entity (e.g., base station 110, BS110a, gNB). In some aspects, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, an onboard processing repeater, and / or an NTN entity. In some aspects, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to produce downlink radio frequency transmissions. Satellite 420 may transmit downlink radio frequency signals on service link 430. Satellite 420 may provide a cell covering UE 120.

[0076] Example 410 shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In example 410, UE 120 is served by satellite 440 via service link 430. Satellite 440 may also be considered an NTN entity. Satellite 440 may be a transparent satellite. Satellite 440 may relay signals received from gateway 450 via feeder link 460. For example, a satellite may receive uplink radio frequency transmissions, and may transmit downlink radio frequency transmissions without demodulating uplink radio frequency transmissions. In some aspects, a satellite may convert the uplink radio frequency transmission frequency received on service link 430 to the frequency of the uplink radio frequency transmission on feeder link 460, and may amplify and / or filter the uplink radio frequency transmissions. In some aspects, the UE 120 shown in examples 400 and 410 may be associated with global navigation satellite system (GNSS) capabilities, global positioning system (GPS) capabilities, etc., but not all UEs have such capabilities. Satellite 440 may provide a cell covering UE 120.

[0077] The service link 430 may include a link between the satellite 440 and the UE 120, and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 440 and the gateway 450, and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0078] Due to the movement of satellites 420 and 440 and the potential movement of UE 120, feeder link 460 and service link 430 may each experience Doppler effects. These Doppler effects may be significantly greater than the Doppler effects in the ground network. The Doppler effect on feeder link 460 can be compensated to a certain extent, but may still be associated with a certain amount of uncompensated frequency error. In addition, gateway 450 may be associated with residual frequency error, and / or satellite 420 / 440 may be associated with onboard frequency error. These frequency error sources may cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.

[0079] Satellites 420 and 440 may be satellites in a geostationary orbit (GSO) or a geosynchronous equatorial orbit (GEO), which may be located, for example, 36,000 kilometers (km) above the earth. The satellites have a negligible velocity for the earth, but have a round trip propagation delay of greater than 500 ms, compared to a round trip propagation delay of 25 milliseconds (ms) for a low earth orbit (LEO) satellite 600 km above the earth. In NTNs where the distance between the UE 120 and the satellite may be greater than 600 km, path loss changes may not be properly reflected in propagation delay variations. It is expected that the UE 120 can autonomously pre-compensate for propagation delays up to a reference point, and thus timing advance (TA) verification may be performed more directly, rather than relying on indirect parameters such as RSRP. Due to propagation delays, the UE 120 may use the TA for timing alignment of communications. The TA may inform the UE 120 to send communications in the uplink earlier than the reference downlink time slot timing by the TA amount. In the case of a change in the propagation distance between the UE 120 and the network entity, the TA may need to be verified. Furthermore, the satellite may not always be available to the UE 120 in the case where the satellite is in a non-geostationary orbit (NGSO).

[0080] Some satellite operators may deploy satellite access with intentional coverage gaps or discontinuous coverage (DC). DC may involve LEO satellites, IoT networks, or satellite constellations that do not always cover a specific location on the earth. Some services may be delay tolerant and can use DC. Such services may include services for IoT devices and networks, services for utility meters, or services using sensors. DC can be used to address service availability and power consumption. In addition to DC, the feeder link 460 may have an intermittent connection to a ground station (such as gateway 450). Due to deployment design and / or cost, there may be some areas where it is not feasible to deploy ground stations.

[0081] In order to handle the unavailability of the feeder link 460, the satellite transmitter may include a network element at the satellite 420 / 440. Both the radio network and the core network aspects may be installed on the satellite 420 / 440. In one scenario, the entire control plane and user plane path may be installed on the satellite 420 / 440. For example, the control plane management entity (e.g., the mobile management entity (MME) in 4G or the access and mobility management function (AMF) and session management function (SMF) in NR) and the user plane path (e.g., the service gateway (GW) and the packet data network GW for 4G or the user plane function in NR) may be installed on the satellite 420 / 440. In this scenario, the ground station (e.g., the gateway 450) may include a home subscriber service (HSS), which includes subscription management, user authentication and authorization. In addition, in this scenario, some parts of the control plane path may be at the ground station (e.g., coordination between control plane management entities in different satellites, buffering of user data and control plane data when FL is unavailable). In this scenario, there may also be user data plane and control plane data buffering at the satellite due to DC. Finally, the Internet connection for the data plane may be at the ground station. Other functional splits between the satellite transmitter and the ground station may be employed.

[0082] Example 470 shows the use of ISL 480 between satellite 440 and satellite 490. ISL 480 can be used to support coverage extension in NTN. For example, if gateway 450 is deployed with certain restrictions and satellite 440 does not have a direct feeder link connection to gateway 450, satellite 440 can be connected to satellite 490 having feeder link 460 through ISL 480. In this way, satellite 440 has access to feeder link 460 and service availability is improved.

[0083] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0084] Figure 5 is a diagram illustrating an example 500 of ISL activation and an example 502 of ISL deactivation according to the present disclosure.

[0085] Example 500 shows that satellite 440 may have feeder link 510. However, a topology change event may occur where there is a change in the communication path in the NTN topology. This may include a change in the link used or a change in the operation of the NTN entity. In example 500, the topology change event is an ISL activation where satellite 440 no longer uses feeder link 510 and switches to using ISL 480 to peer satellite 490. This may be due to satellite 440 moving to a location where there is no line of sight to gateway 450. From the perspective of the UE, the connection or communication path between satellite 440 and gateway 450 may be an extended feeder link, even if the communication path advances through ISL 480 and satellite 490.

[0086] Example 502 shows that a topology change event may be an ISL deactivation, where the satellite switches from using ISL 480 to using feeder link 510. For example, satellite 440 or the network may determine that satellite 440 has or will have line of sight with gateway 450. In other words, satellite 440 may activate use of ISL 480 as it moves further away from gateway 450, and deactivate use of ISL 480 as it moves closer to gateway 450.

[0087] UE 120 may use the same serving satellite (e.g., satellite 440) before and after ISL activation or deactivation. Therefore, UE 120 may use the same serving link 430 to satellite 440 before and after ISL activation or deactivation. In other words, only the feeder link of satellite 440 changes before and after ISL activation or deactivation. However, even if serving link 430 and satellite 440 have not changed for UE 120, NTN may change physical cell ID (PCI) after ISL activation or deactivation. In this scenario, UE 120 detects different cells before and after ISL activation or deactivation. Therefore, UE 120 may perform legacy mobility-related procedures to handle ISL activation or deactivation. This may include reusing RRC re-establishment procedures, (conditional) handover procedures, and / or cell reselection procedures. Such procedures involve a large amount of signaling so that UE 120 regains uplink synchronization and accesses new cells, as well as obtains communication configuration parameters. The signaling may include signaling / procedures such as signaling for a random access procedure, signaling for a new RRC configuration, or for resetting a protocol stack layer of UE 120.

[0088] In addition, the current system information (SI) update procedure is not sufficient to support the ISL activation or deactivation procedure under consideration. For example, when satellite 440 activates ISL 480, there may be a sudden propagation duration increase on feeder link 460. There will be a time gap between the last time slot before the ISL activation and the first time slot after the ISL activation. This time gap cannot be handled by the current SI update procedure.

[0089] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0090] Figure 6 600 is a diagram illustrating an example of indicating a topology change event according to the present disclosure. Figure 6 As shown, NTN entity 610 (e.g., base station 110, network entity, satellite 420, satellite 440) and UE 620 (e.g., UE 120) may communicate with each other. UE 620 and ground network entity (e.g., ground station 630) may communicate via NTN entity 610. There may be another NTN entity 640 (e.g., base station 110, network entity, satellite 420, satellite 490) having a feeder link (e.g., feeder link 460) to the ground network entity, and there may be an ISL (e.g., ISL 480) activated or deactivated between NTN entity 610 and NTN entity 640.

[0091] According to various aspects described herein, when a topology change event occurs in association with an ISL, the UE 620 and the NTN entity 610 may use a lighter signaling procedure to reduce signaling overhead and service interruption time. For example, the UE 620 may receive an indication of a topology change event that is about to occur. The topology change event may be an ISL activation. The UE 620 may use a radio configuration for a service link before the ISL activation. Then, the UE 620 may use at least a portion of the same radio configuration for the service link after the ISL activation. This is because some parameters of the radio configuration may remain valid (applicable) both before and after the ISL activation, because the same service link still exists before and after the ISL activation. Such parameters (a first set of parameters) may include satellite ephemeris, closed-loop timing advance, frequency compensation for a service link, hybrid automatic repeat request (HARQ) process configuration, serving cell or beam antenna polarization, timing advance for the last report of the service link, and / or the last reported position of the UE 620.

[0092] UE 620 may determine update information (e.g., new values) for parameters that may change or not remain valid after ISL activation. Such parameters (second set of parameters) may include common timing advance parameters, slot timing parameters indicating the time gap between the last slot before the topology change event and the first slot after the topology change event, serving cell measurements, K mac Timing parameters, K 偏移 parameters, synchronization signal block (SSB) measurement timing configuration, measurement gap configuration and / or conditional handover configuration. macThe timing parameter may be a feeder link round trip time between a network entity (eg, base station 110) and a reference point at which the uplink time slot timing and the downlink time slot timing are aligned. 偏移 The parameter may be a timing offset used to enhance the timing relationship between uplink transmission and downlink reception in order to handle the large TA values ​​applied by UE 620. For example, K 偏移 is added to the time parameter K2 to determine the number of time slots between the downlink time slot in which the UE 620 receives a command (e.g., scheduling downlink control information (DCI), MAC control element (MAC CE)) and the uplink time slot used to apply the command (e.g., transmit). K2 is equal to K 偏移 Together, the UE 620 may be given enough time to process the command and / or prepare to send, even though the UE 620 applies a large TA, which is equal to the round trip time between the UE 620 and the reference point.

[0093] Example 600 shows that UE 620 receives an indication of a topology change event and uses at least a portion of the same radio configuration to use less signaling than currently used for the topology change event. The topology change event can be an ISL activation, an ISL deactivation, or another action involving the ISL. In example 600, the topology change event is an ISL activation.

[0094] As shown by reference numeral 635, UE 620 and NTN entity 610 may use Figure 5 As shown in the service link 430, the NTN entity 610 can use Figure 5 The feeder link 510 shown communicates with the ground station 630. The NTN entity 610 and / or the ground station 630 may determine that the NTN entity 610 may not be able to use the feeder link 510 based on scheduling or other information. As shown by reference numeral 645, the NTN entity 610 and / or the ground station 630 may send an indication of a topology change event (e.g., ISL activation) to the UE 620. The indication may be received in a SIB, which may be NTN-specific or dedicated to the NTN. The indication may be received in a DCI, a MAC CE, or an RRC message. The indication may be received via a short message on a physical downlink control channel (PDCCH) in a paging occasion (e.g., for an RRC-inactive or RRC-idle UE). The indication may be received in a dedicated RRC message for an RRC-connected UE. For example, the indication may be a handover command, wherein the target cell identifier (ID) contained in the handover command indicates the same cell ID as the current serving cell of the UE 620 on the serving link 430 before the topology change event. Therefore, if the UE 620 receives a handover command requesting the UE 620 to handover to the current serving cell, the UE 620 may detect the indication.

[0095] In some aspects, the indication may include the timing of the topology change event (explicitly or implicitly), such as how long before the topology change event occurs, when the topology change event occurs, and / or how long the topology change event will last.

[0096] The indication may indicate the first set of parameters and / or the second set of parameters. The first set of parameters that remain the same before and after the topology change event may include the satellite ephemeris N at the UE. TA value, downlink and / or uplink frequency compensation of the serving link, HARQ process configuration (e.g., whether the downlink HARQ process has HARQ feedback enabled or disabled, the HARQ state or mode of the uplink HARQ process), downlink and / or uplink antenna polarization of the serving cell / beam, the last reported serving link TA of UE 620, and / or the last reported location of UE 620 for determining the triggering update report.

[0097] The second set of parameters updated or changed at the UE after a topology change event may include TA_common parameters, downlink or uplink timeslot timing (e.g., to handle the time gap between the last timeslot before ISL activation and the first timeslot after ISL activation), reset of measurements of the serving cell, K mac , UE-specific and / or cell-specific K 偏移 , SSB measurement timing configuration (SMTC), measurement gap configuration and / or conditional handover configuration (CHO). Some parameters may be updated explicitly or implicitly based on explicitly updated parameters. For example, UE 620 may infer the updated K by considering the difference between the old TA_common parameters and the updated TA_common parameters explicitly updated by the network. 偏移 In another example, UE 620 may update the time window and / or measurement gap of the SMTC based at least in part on a time difference between downlink slot timing of the serving cell before and after ISL activation or deactivation.

[0098] The indication may include one or more bits or information elements (IEs). For example, the SIB may include a one-bit flag (e.g., IE t-Service) in the NTN-specific SIB. If the one-bit flag is set, the UE 620 may determine that the SIB indicates a topology change event. Additionally or alternatively, the UE 620 may determine that the IE t-Service refers to the timing of ISL activation or deactivation, and may determine that the same service link will continue to serve the UE 620 after the ISL activation or deactivation. Note that in the current NTN design, the IE t-Service refers to the timing when the current cell stops serving the area. Alternatively, a new IE may be included in the NTN-specific SIB to indicate the timing for ISL activation or deactivation.

[0099] As shown at reference numeral 650, the NTN entity 610 may activate an ISL, such as Figure 5 480 shown. As shown by reference numeral 655, for communications after the topology change event at step 660, the UE 620 may maintain use of at least a portion of the same radio configuration used for communications at steps 635 and 640. In some aspects, the UE 620 may determine radio configuration parameters that remain valid after the ISL activation based at least in part on the indication. This may enable the UE 620 to skip some procedures or use smaller, modified procedures with less signaling and with less latency. For example, in some aspects, because the closed-loop TA adjustment value (i.e., N TA The value) remains valid and the impact of ISL activation or deactivation may have been included in the updated TA_common parameters, so UE 620 can skip the random access procedure after ISL activation or deactivation, which can further save additional signaling and reduce service interruption time. UE 620 can use this part of the same radio configuration (the same first set of parameters) to communicate with ground station 630 via ISL 480. UE 620 can determine or receive update information about what part of the radio configuration will be modified or updated. UE 620 can determine the updated parameters or receive updated parameters. In one option, some parameters in the parameters may need to be updated or may not need to be updated. This may depend on whether the network does not provide a new configuration. For example, UE 620 can wait to see if a new configuration is provided within a certain period of time. If a new configuration is not provided within the period of time, UE 620 can reuse the old configuration. Otherwise, UE 620 can apply the new configuration.

[0100] As shown by reference numeral 660, UE 620 may communicate over the same service link 430 using a portion of the same radio configuration and any updated parameters. As shown by reference numeral 665, NTN entity 610 may communicate with NTN entity 640 via ISL 480. As shown by reference numeral 670, NTN entity 640 may communicate with ground station 630 using feeder link 460.

[0101] By indicating a topology change event and configuring the UE 620 to use part of the same serving link and the same radio configuration, the NTN and the UE 620 can improve communication services while reducing latency and saving processing and signaling resources.

[0102] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0103] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a UE according to the present disclosure. Example process 700 is an example in which a UE (eg, UE 120, UE 620) performs operations associated with using the same radio configuration before and after a topology change event associated with an ISL.

[0104] like Figure 7 As shown, in some aspects, process 700 may include: communicating with an NTN entity on a serving link using a radio configuration (block 710). For example, a UE (e.g., using Fig. 9 The communication manager 908, receiving component 902 and / or sending component 904 depicted in FIG. 1 may communicate with the NTN entity over the service link using the radio configuration, as described above.

[0105] like Figure 7 As further shown, in some aspects, process 700 may include receiving an indication of a topology change event that will occur in association with an ISL (block 720). For example, a UE (e.g., using Fig. 9 The communication manager 908 and / or receiving component 902 depicted in FIG. 1 may receive an indication of a topology change event that will occur in association with an ISL, as described above.

[0106] like Figure 7 As further shown, in some aspects, process 700 may include: communicating on the serving link using at least a portion of the radio configuration after the topology change event (block 730). Fig. 9The communication manager 908, receiving component 902, and / or sending component 904 depicted in FIG. 1 may communicate over the serving link using at least a portion of the radio configuration following the topology change event, as described above.

[0107] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0108] In a first aspect, the indication indicates that the service link is to be used before and after the topology change event.

[0109] In a second aspect, alone or in combination with the first aspect, the topology change event is activation or deactivation of an ISL.

[0110] In a third aspect, alone or in combination with one or more of the first and second aspects, at least a portion of the radio configuration comprises a first set of parameters that are valid both before and after the topology change event.

[0111] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the first set of parameters includes one or more of the following: satellite ephemeris information, closed-loop TA, frequency compensation for the service link, HARQ process configuration, service cell or beam antenna polarization, the last reported TA for the service link, or the last reported position of the UE.

[0112] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 700 includes determining update information of a second set of parameters of the radio configuration that are invalid after the topology change event, and updating the second set of parameters based at least in part on the update information.

[0113] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, determining the update information includes: receiving the update information.

[0114] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, the second set of parameters includes one or more of the following: a common timing advance parameter, a slot timing parameter indicating a time gap between a last slot before a topology change event and a first slot after a topology change event, a serving cell measurement, a K mac Timing parameters, K 偏移 parameters, SSB measurement timing configuration, measurement gap configuration, or conditional handover configuration.

[0115] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the indication indicates a timing of the topology change event.

[0116] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, receiving the indication includes: receiving the indication via a SIB.

[0117] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the SIB is NTN specific.

[0118] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the indication comprises one or more bits or information elements in the SIB.

[0119] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, receiving the indication includes: receiving the indication via a DCI, a MAC CE or an RRC message.

[0120] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, receiving the indication includes: receiving the indication via a short message on a PDCCH in a paging occasion.

[0121] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the indication indicates a first set of parameters that are to remain the same after the topology change event.

[0122] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the indication indicates a second set of parameters to be updated after the topology change event.

[0123] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 700 includes skipping a random access procedure after the topology change event.

[0124] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of process 700 may be performed in parallel.

[0125] Figure 8is a diagram illustrating an example process 800 performed, for example, by an NTN entity according to the present disclosure. The example process 800 is an example in which an NTN entity (eg, base station 110, satellite 420 / 440, NTN entity 610) performs operations associated with indicating a topology change event.

[0126] like Figure 8 As further shown, in some aspects, process 800 may include communicating with the UE using a radio configuration for a serving link (block 810). For example, an NTN entity (e.g., using Fig.10 The communication manager 1008, receiving component 1002 and / or sending component 1004 depicted in FIG. 1004 may communicate with the UE using the radio configuration for the serving link, as described above.

[0127] like Figure 8 As further shown, in some aspects, process 800 may include sending an indication of a topology change event that will occur in association with an ISL and indicating that the service link will be used before and after the topology change event (block 820). For example, an NTN entity (e.g., using Fig.10 The communication manager 1008 and / or sending component 1004 depicted in FIG. 1004 may send an indication of a topology change event that will occur in association with the ISL and the indication indicating that the service link will be used before and after the topology change event, as described above.

[0128] like Figure 8 As further shown, in some aspects, process 800 may include: communicating using at least a portion of the radio configuration for the service link after the topology change event (block 830). Fig.10 The communication manager 1008, receiving component 1002, and / or sending component 1004 depicted in FIG. 1 may communicate using at least a portion of the radio configuration for the service link following the topology change event, as described above.

[0129] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0130] In a first aspect, the topology change event is activation or deactivation of an ISL.

[0131] In a second aspect, alone or in combination with the first aspect, the at least a portion of the radio configuration comprises a first set of parameters valid both before and after the topology change event.

[0132] In a third aspect, either alone or in combination with one or more of the first and second aspects, the first set of parameters includes one or more of: satellite ephemeris information, closed-loop TA, frequency compensation for the service link, HARQ process configuration, service cell or beam antenna polarization, the last reported TA for the service link, or the last reported position of the UE.

[0133] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 800 includes sending update information of a second set of parameters of the radio configuration that are invalid after the topology change event.

[0134] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the second set of parameters includes one or more of the following: a common TA parameter, a slot timing parameter indicating a time gap between a last slot before a topology change event and a first slot after a topology change event, a serving cell measurement, a K mac Timing parameters, K 偏移 parameters, SSB measurement timing configuration, measurement gap configuration, or conditional handover configuration.

[0135] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the indication indicates a timing of the topology change event.

[0136] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, sending the indication includes: sending the indication via an NTN-specific SIB.

[0137] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, sending the indication includes: sending the indication via a DCI, a MAC CE or an RRC message.

[0138] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending the indication includes: sending the indication via a short message on a PDCCH in a paging occasion.

[0139] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the indication indicates a first set of parameters that are to remain the same after the topology change event.

[0140] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the indication indicates a second set of parameters to be updated after the topology change event.

[0141] although Figure 8An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0142] Although the described examples include satellites, aspects described herein may also be applied to link and topology change events involving other NTN entities, such as drones, unmanned aerial vehicles, and / or high-altitude platforms.

[0143] Fig. 9 is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a UE (e.g., UE 120, UE 620), or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 908. Communication manager 908 may control and / or otherwise manage one or more operations of receiving component 902 and / or transmitting component 904. In some aspects, communication manager 908 may include a communication manager 908 in conjunction with a receiving component 902 and / or transmitting component 904. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 908 may be Figure 1 and Figure 2 The communication manager 908 depicted or similar Figure 1 and Figure 2 For example, in some aspects, the communication manager 908 can be configured to perform one or more of the functions described as being performed by the communication manager 908. In some aspects, the communication manager 908 can include a receiving component 902 and / or a sending component 904. The communication manager 140 can include a configuring component 910, among other things.

[0144] In some aspects, the apparatus 900 may be configured to perform Figures 1 to 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig. 9One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0145] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0146] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications and may provide the generated communications to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0147] The receiving component 902 and the sending component 904 can communicate with the NTN entity on the service link using the radio configuration. The receiving component 902 can receive an indication of a topology change event, which will occur in association with the ISL. The receiving component 902 and the sending component 904 use at least a portion of the radio configuration on the service link after the topology change event. The configuration component 910 can determine how to reuse a portion of the radio configuration used before the topology change event. The configuration component 910 can determine update information of a second group of parameters of the radio configuration that are invalid after the topology change event. The configuration component 910 can update the second group of parameters based at least in part on the update information. The configuration component 910 can skip a random access procedure after the topology change event.

[0148] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig. 9 Two or more components shown in may be implemented in a single component, or Fig. 9 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown in the executable is described as being composed of Fig. 9 Another collection of components shown in FIG. 1 performs one or more functions.

[0149] Fig.10 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be an NTN entity (e.g., base station 110, satellite 420 / 440, NTN entity 610), or an NTN entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 1008. Communication manager 1008 may control and / or otherwise manage one or more operations of receiving component 1002 and / or transmitting component 1004. In some aspects, communication manager 1008 may include a communication manager 1008 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities described. The communication manager 1008 may be Figure 1 and Figure 2 The communication manager 150 depicted in or similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1008 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1008 can include a receiving component 1002 and / or a sending component 1004. The communication manager 1008 can include a configuration component 1010, among other things.

[0150] In some aspects, the apparatus 1000 may be configured to perform Figures 1 to 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0151] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1006. The receiving component 1002 may provide the received communications to one or more other components of the device 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described NTN entities.

[0152] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1006. In some aspects, one or more other components of the device 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1006. In some aspects, the transmitting component 1004 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described NTN entities. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0153] The receiving component 1002 and the sending component 1004 can communicate with the UE using the radio configuration for the service link. The sending component 1004 can send an indication of a topology change event, which will occur in association with the ISL and the indication indicates that the service link will be used before and after the topology change event. The configuration component 910 can generate the indication. The receiving component 1002 and the sending component 1004 can communicate using at least a portion of the radio configuration for the service link after the topology change event. The sending component 1004 can send update information of a second set of parameters of the radio configuration that are invalid after the topology change event.

[0154] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of (one or more) components shown in the executable is described as being composed of Fig.10 Another collection of components shown in the figure performs one or more functions.

[0155] The following provides an overview of some aspects of the disclosure:

[0156] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: communicating with an NTN entity on a serving link using a radio configuration; receiving an indication of a topology change event, the topology change event to occur in association with an inter-satellite link (ISL); and communicating on the serving link using at least a portion of the radio configuration after the topology change event.

[0157] Aspect 2: The method according to aspect 1, wherein the indication indicates that the service link is to be used before and after the topology change event.

[0158] Aspect 3: The method according to aspect 1 or 2, wherein the topology change event is activation or deactivation of the ISL.

[0159] Aspect 4: The method according to any one of aspects 1 to 3, wherein the at least part of the radio configuration comprises a first set of parameters that are valid both before and after the topology change event.

[0160] Aspect 5: A method according to Aspect 4, wherein the first set of parameters includes one or more of the following: satellite ephemeris information, closed-loop timing advance, frequency compensation of the service link, hybrid automatic repeat request process configuration, serving cell or beam antenna polarization, the last reported timing advance for the service link, or the last reported position of the UE.

[0161] Aspect 6: The method according to aspect 5, further comprising: determining update information of a second set of parameters of the radio configuration that are invalid after the topology change event; and updating the second set of parameters based at least in part on the update information.

[0162] Aspect 7: The method according to aspect 6, wherein determining the update information comprises: receiving the update information.

[0163] Aspect 8: A method according to Aspect 6 or 7, wherein the second set of parameters includes one or more of the following: a common timing advance parameter, a time slot timing parameter indicating the time gap between the last time slot before the topology change event and the first time slot after the topology change event, a service cell measurement, a K_mac timing parameter, a K_offset parameter, a synchronization signal block measurement timing configuration, a measurement gap configuration, or a conditional handover configuration.

[0164] Aspect 9: The method according to any one of aspects 1 to 8, wherein the indication indicates the timing of the topology change event.

[0165] Aspect 10: The method according to any one of aspects 1 to 9, wherein receiving the indication comprises: receiving the indication via a system information block (SIB).

[0166] Aspect 11: The method according to aspect 10, wherein the SIB is NTN specific.

[0167] Aspect 12: The method according to aspect 10 or 11, wherein the indication comprises one or more bits or information elements in the SIB.

[0168] Aspect 13: The method according to any one of aspects 1 to 12, wherein receiving the indication comprises: receiving the indication via downlink control information, a medium access control control element, or a radio resource control message.

[0169] Aspect 14: The method according to any one of aspects 1 to 13, wherein receiving the indication comprises: receiving the indication via a short message on a physical downlink control channel in a paging occasion.

[0170] Aspect 15: The method according to any one of aspects 1 to 14, wherein the indication indicates a first set of parameters that will remain the same after the topology change event.

[0171] Aspect 16: The method according to any one of aspects 1 to 15, wherein the indication indicates a second set of parameters to be updated after the topology change event.

[0172] Aspect 17: The method according to any one of aspects 1 to 16, further comprising: skipping a random access procedure after the topology change event.

[0173] Aspect 18: A method of wireless communication performed by a non-terrestrial network (NTN) entity, the method comprising: communicating with a user equipment (UE) using a radio configuration for a service link; sending an indication of a topology change event, the topology change event will occur in association with an inter-satellite link (ISL) and the indication indicates that the service link will be used before and after the topology change event; and communicating using at least a portion of the radio configuration for the service link after the topology change event.

[0174] Aspect 19: The method according to Aspect 18, wherein the topology change event is activation or deactivation of the ISL.

[0175] Aspect 20: The method according to aspect 18 or 19, wherein the at least a portion of the radio configuration comprises a first set of parameters that are valid both before and after the topology change event.

[0176] Aspect 21: A method according to Aspect 20, wherein the first set of parameters includes one or more of the following: satellite ephemeris information, closed-loop timing advance, frequency compensation of the service link, hybrid automatic repeat request process configuration, serving cell or beam antenna polarization, the last reported timing advance for the service link, or the last reported position of the UE.

[0177] Aspect 22: The method according to aspect 21, further comprising: sending update information of a second set of parameters of the radio configuration that are invalid after the topology change event.

[0178] Aspect 23: A method according to Aspect 22, wherein the second set of parameters includes one or more of the following: a common timing advance parameter, a time slot timing parameter indicating the time gap between the last time slot before the topology change event and the first time slot after the topology change event, a service cell measurement, a K_mac timing parameter, a K_offset parameter, a synchronization signal block measurement timing configuration, a measurement gap configuration, or a conditional handover configuration.

[0179] Aspect 24: The method according to any one of aspects 18 to 23, wherein the indication indicates the timing of the topology change event.

[0180] Aspect 25: The method according to any one of aspects 18 to 24, wherein sending the indication comprises: sending the indication via an NTN-specific system information block (SIB).

[0181] Aspect 26: The method according to any one of aspects 18 to 25, wherein sending the indication comprises: sending the indication via downlink control information, a medium access control control element, or a radio resource control message.

[0182] Aspect 27: The method according to any one of aspects 18 to 26, wherein sending the indication comprises: sending the indication via a short message on a physical downlink control channel in a paging occasion.

[0183] Aspect 28: The method according to any one of aspects 18 to 27, wherein the indication indicates a first set of parameters that will remain the same after the topology change event.

[0184] Aspect 29: The method according to any one of aspects 18 to 28, wherein the indication indicates a second set of parameters to be updated after the topology change event.

[0185] Aspect 30: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 29.

[0186] Aspect 31: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 29.

[0187] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 29.

[0188] Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 29.

[0189] Aspect 34: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 29.

[0190] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0191] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be clear that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0192] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0193] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0194] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: communicating with a non-terrestrial network (NTN) entity over a service link using the radio configuration; receiving an indication of a topology change event that will occur in association with an inter-satellite link (ISL); and Communicating over the serving link using at least a portion of the radio configuration after the topology change event. 2 . The UE of claim 1 , wherein the indication indicates that the serving link is to be used before and after the topology change event. 3 . The UE according to claim 1 , wherein the topology change event is activation or deactivation of the ISL. 4 . The UE of claim 1 , wherein the at least a portion of the radio configuration comprises a first set of parameters that are valid both before and after the topology change event.

5. The UE of claim 4, wherein the first set of parameters comprises one or more of: satellite ephemeris information, closed-loop timing advance, frequency compensation of the serving link, hybrid automatic repeat request process configuration, serving cell or beam antenna polarization, last reported timing advance for the serving link, or last reported position of the UE.

6. The UE of claim 5, wherein the one or more processors are configured to: determining update information for a second set of parameters of the radio configuration that are invalid after the topology change event; and The second set of parameters is updated based at least in part on the update information. 7 . The UE of claim 6 , wherein in order to determine the update information, the one or more processors are configured to: receive the update information.

8. A UE according to claim 6, wherein the second set of parameters includes one or more of the following: a common timing advance parameter, a time slot timing parameter indicating the time gap between the last time slot before the topology change event and the first time slot after the topology change event, a serving cell measurement, a K_mac timing parameter, a K_offset parameter, a synchronization signal block measurement timing configuration, a measurement gap configuration or a conditional handover configuration.

9. The UE of claim 1, wherein the indication indicates a timing of the topology change event.

10. The UE of claim 1, wherein to receive the indication, the one or more processors are configured to receive the indication via a system information block (SIB). The UE according to claim 10 , wherein the SIB is NTN specific.

12. The UE of claim 10, wherein the indication comprises one or more bits or information elements in the SIB.

13. The UE of claim 1, wherein to receive the indication, the one or more processors are configured to receive the indication via downlink control information, a medium access control control element, or a radio resource control message.

14. The UE of claim 1, wherein to receive the indication, the one or more processors are configured to receive the indication via a short message on a physical downlink control channel in a paging occasion.

15. The UE of claim 1, wherein the indication indicates a first set of parameters that are to remain the same after the topology change event.

16. The UE of claim 1, wherein the indication indicates a second set of parameters to be updated after the topology change event.

17. The UE of claim 1, wherein the one or more processors are configured to skip a random access procedure after the topology change event.

18. A non-terrestrial network (NTN) entity for wireless communication, the non-terrestrial network (NTN) entity comprising: Memory; and one or more processors coupled to the memory and configured to: communicating with a user equipment (UE) using a radio configuration for a serving link; sending an indication of a topology change event that will occur in association with an inter-satellite link (ISL) and indicating that the service link will be used before and after the topology change event; and Communicating using at least a portion of the radio configuration for the serving link after the topology change event.

19. The NTN entity of claim 18, wherein the at least part of the radio configuration comprises a first set of parameters that are valid both before and after the topology change event.

20. The NTN entity of claim 19, wherein the first set of parameters comprises one or more of: satellite ephemeris information, closed loop timing advance, frequency compensation of the serving link, hybrid automatic repeat request process configuration, serving cell or beam antenna polarization, last reported timing advance for the serving link, or last reported position of the UE.

21. The NTN entity of claim 20, wherein the one or more processors are configured to send update information of a second set of parameters of the radio configuration that are invalid after the topology change event.

22. The NTN entity of claim 21, wherein the second set of parameters comprises one or more of: a common timing advance parameter, a slot timing parameter indicating a time gap between a last slot before the topology change event and a first slot after the topology change event, a serving cell measurement, a K_mac timing parameter, a K_offset parameter, a synchronization signal block measurement timing configuration, a measurement gap configuration, or a conditional handover configuration.

23. The NTN entity of claim 18, wherein the indication indicates a timing of the topology change event.

24. The NTN entity of claim 18, wherein to send the indication, the one or more processors are configured to send the indication via an NTN-specific System Information Block (SIB).

25. The NTN entity of claim 18, wherein to send the indication, the one or more processors are configured to send the indication via downlink control information, a medium access control control element, or a radio resource control message.

26. The NTN entity of claim 18, wherein to send the indication, the one or more processors are configured to send the indication via a short message on a physical downlink control channel in a paging occasion.

27. The NTN entity of claim 18, wherein the indication indicates a first set of parameters that are to remain the same after the topology change event.

28. The NTN entity of claim 18, wherein the indication indicates a second set of parameters to be updated after the topology change event.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: communicating with a non-terrestrial network (NTN) entity over a service link using the radio configuration; receiving an indication of a topology change event that will occur in association with an inter-satellite link (ISL); and Communicating over the serving link using at least a portion of the radio configuration after the topology change event.

30. A method of wireless communication performed by a non-terrestrial network (NTN) entity, the method comprising: communicating with a user equipment (UE) using a radio configuration for a serving link; sending an indication of a topology change event that will occur in association with an inter-satellite link (ISL) and indicating that the service link will be used before and after the topology change event; and Communicating using at least a portion of the radio configuration for the serving link after the topology change event.

Images