PCI Satellite Exchange Transmission Management

Description

1 / 87 “Transmission Management for PCI Satellite Exchange” Cross-reference to related requests

[001] This application claims the benefit of US Provisional Patent Application No. 63 / 456,866, filed April 4, 2023, which is incorporated herein by reference in its entirety. FUNDAMENTALS OF THE INVENTION

[002] A WTRU can be configured for use in non-terrestrial networks (NTNs). Non-terrestrial networks (NTNs) can facilitate the deployment of wireless networks in areas where terrestrial antennas may be impractical and / or undesirable. For example, terrestrial antennas may be impractical due to geography and / or cost. Along with terrestrial networks, NTNs can provide ubiquitous 5G network coverage. Some examples of NTN deployments can support basic communication and text worldwide. NTN deployments, along with the proliferation of next-generation low-orbit satellites, can enable additional services (e.g., web browsing).

[003] An NTN may include an aerial or space-based platform that, via a gateway (GW), can carry signals from a ground-based gNB to a WTRU and vice versa. Examples of NTN deployments may support a power class 3 WTRU with an omnidirectional antenna and linear polarization, or a small aperture antenna terminal (VSAT) with a directional antenna and circular polarization. Examples of NTNs may provide support for LTE-based narrowband IoT (NB-IoT) and eMTC-type devices. In examples, regardless of the device type, NTN WTRUs may be GNSS-compatible. SUMMARY OF THE INVENTION

[004] A wireless transmit / receive unit (WTRU) may comprise a processor configured to receive configuration information indicating the time for a satellite change of the same physical cell identity. Petition 870250090286, dated 03 / 10 / 2025, page 11 / 119 2 / 87 (PCI) from a first satellite to a second satellite. The configuration information may include a start time and an indication of an end time for the same-PCI satellite exchange from the first satellite to the second satellite. The processor may be further configured to receive a configuration for satellite resynchronization with the second satellite. The processor may be further configured to perform the same-PCI satellite exchange to the second satellite based on the configuration information indicating the time for the same-PCI satellite exchange.

[005] Configuration information can be received via broadcast signaling. The processor can be further configured to initiate a resynchronization interval in response to a satellite change on the same PCI. The processor can be further configured to suspend uplink transmission with the first satellite in response to a satellite change on the same PCI. The processor can be further configured to execute one or more resynchronization procedures in response to a satellite change on the same PCI. The processor can be further configured to transmit a successful resynchronization indication in response to successful resynchronization to the second satellite.

[006] One or more resynchronization procedures may comprise a time advance calculation, a Doppler compensation, a power control procedure, and / or a measurement procedure. In response to a satellite change on the same PCI, the processor may be further configured to initiate a resynchronization interval, suspend uplink transmission and downlink reception, and execute one or more resynchronization procedures. The resynchronization procedures may comprise a time advance calculation, a Doppler compensation, a power control procedure, and / or a measurement procedure. The configuration for satellite resynchronization may comprise a resynchronization interval configuration, a condition for Petition 870250090286, dated 03 / 10 / 2025, page 12 / 119 3 / 87 declare a resynchronization failure, and / or resources to indicate successful resynchronization for the second satellite.

[007] The processor can be further configured to transmit assistance information related to a resynchronization time, to assist in setting the measurement interval. The assistance information may include a resynchronization duration, an indication that the WTRU can perform a synchronization procedure before switching to a satellite with the same PCI, and / or an indication of a time when the WTRU can resume communication with the second satellite after switching to a satellite with the same PCI. BRIEF DESCRIPTION OF THE DRAWINGS

[008] Figure 1A is a system diagram that illustrates an exemplary communications system in which one or more of the described modalities can be implemented.

[009] Figure 1B is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that can be used within the communications system illustrated in Figure 1A according to one embodiment.

[010] Figure 1C is a system diagram that illustrates an exemplary radio access network (RAN) and an exemplary central network (CN) that can be used within the communications system illustrated in Figure 1A according to one modality.

[011] Figure 1D is a system diagram that illustrates an additional exemplary RAN and an additional exemplary CN that can be used within the communications system illustrated in Figure 1A, according to one embodiment.

[012] Figure 2 illustrates exemplary interfaces in a non-terrestrial network.

[013] Figure 3 illustrates an example of two satellites serving the same PCI.

[014] Figure 4 is a flowchart that illustrates the pre-calculation of time advance. Petition 870250090286, dated 03 / 10 / 2025, page 13 / 119 4 / 87 and the report for an incoming satellite during a satellite exchange of the same PCI.

[015] Figure 5 is a flowchart that illustrates an exemplary radio link monitoring during a satellite exchange of the same PCI.

[016] Figure 6 is a flowchart that illustrates an exemplary transmission management and measurement interval configuration during a satellite exchange of the same PCI.

[017] Figure 7 is a flowchart that illustrates an exemplary power control during a satellite change of the same PCI.

[018] Figure 8 is a flowchart that illustrates an exemplary beam management during a satellite exchange of the same PCI. DETAILED DESCRIPTION

[019] Figure 1A is a diagram illustrating an exemplary 100 communications system, in which one or more described modalities can be implemented. The 100 communications system can be a multiple access system that provides content, such as voice, data, video, messages, transmission, etc., to multiple wireless users. The 100 communications system can allow multiple wireless users to access such content by sharing system resources, including wireless bandwidth.For example, communication systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero-tailed single-word DFT propagation OFDM (ZT UW DTS-s OFDM), single-word OFDM (UWOFDM), feature block filtered OFDM, filter bank multicarrier (FBMC), and the like.

[020] As shown in Figure 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, Petition 870250090286, dated 03 / 10 / 2025, page 14 / 119 5 / 87 a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, although it is important to note that the modalities described consider any number of WTRUs, base stations, networks and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. By way of example, WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a mobile phone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device,A watch or other wearable device, virtual reality glasses (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in industrial and / or automated process chain contexts), a consumer electronic device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a WTRU. Furthermore, any description made herein with reference to a UE may be equally applicable to a WTRU (or vice versa). For example, a WTRU may be configured to perform any of the processes or procedures described herein as being performed by a UE (or vice versa).

[021] Communication systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interact with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more Petition 870250090286, dated 03 / 10 / 2025, p. 15 / 119 6 / 87 communication networks, such as CN 106 / 115, the Internet 110 and / or other networks 112. By way of example, base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR NodeB, a site controller, an access point (AP), a wireless router and the like. Although base stations 114a, 114b are represented as a single element, it is important to note that base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[022] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be called a cell (not shown). These frequencies may be in the licensed spectrum, the unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographic area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors.Thus, in one embodiment, base station 114a may include three transceivers, i.e., one for each sector of the cell. In another embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in the desired spatial directions.

[023] Base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an air interface 116, which can Petition 870250090286, dated 03 / 10 / 2025, p. 16 / 119 7 / 87 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter waves, micrometer waves, infrared (IR), ultraviolet (UV), visible light, etc.). The 116 air interface can be established using any appropriate radio access technology (RAT).

[024] More specifically, as noted above, communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and the like. For example, base station 114a in RAN 104 / 113 and WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or HSPA Enhanced (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​Uplink (UL) Packet Access (HSUPA).

[025] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology, such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE Advanced (LTE-A) and / or LTE Advanced Pro (LTE-A Pro).

[026] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement a radio technology, such as NR Radio Access, which can establish the 116 air interface using New Radio (NR).

[027] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c can implement LTE radio access and NR radio access together, for example, using principles of Petition 870250090286, dated 03 / 10 / 2025, p. 17 / 119 8 / 87 Dual connectivity (DC). Thus, the air interface used by WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[028] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rates (EDGE), GSM EDGE (GERAN) and the like.

[029] Base station 114b in Figure 1A can be a wireless router, a Home NodeB, a Home eNodeB, or an access point, for example, and can utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a commercial location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a highway, and the like. In one embodiment, base station 114b and WTRUs 102c, 102d can implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d can implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, base station 114b and WTRUs 102c, 102d can use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell.As shown in Figure 1A, base station 114b can have a direct connection to the 110 Internet. Thus, base station 114b may not need to access the 110 Internet via CN 106 / 115.

[030] RAN 104 / 113 may be in communication with CN 106 / 115, which Petition 870250090286, dated 03 / 10 / 2025, page 18 / 119 9 / 87 can be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying Quality of Service (QoS) requirements, such as different requirements for throughput, latency, error tolerance, reliability, data throughput, mobility, and the like. CN 106 / 115 may provide call control, billing services, location-based mobile services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it is important to note that RAN 104 / 113 and / or CN 106 / 115 may be in direct or indirect communication with other RANs using the same RAT as RAN 104 / 113 or a different RAT.For example, in addition to being connected to RAN 104 / 113, which may use NR radio technology, CN 106 / 115 may also be communicating with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[031] CN 106 / 115 may also serve as a gateway for WTRUs 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110 and / or other networks 112. PSTN 108 may include circuit-switched telephone networks that provide traditional telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP) and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. Networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, 112 networks may include another NC connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT. Petition 870250090286, dated 03 / 10 / 2025, p. 19 / 119 10 / 87

[032] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode capabilities (for example, WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communication with different wireless networks via different wireless links). For example, WTRU 102c shown in Figure 1A may be configured to communicate with base station 114a, which may employ cellular-based radio technology, and with base station 114b, which may employ IEEE 802 radio technology.

[033] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a numeric keypad 126, a touchscreen / touch surface 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136 and / or other peripherals 138, among others. It should be noted that the WTRU 102 may include any subcombination of the above elements, while remaining consistent with an embodiment.

[034] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application-Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functionality that allows WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmit / receive element 122. While Figure Petition 870250090286, dated 03 / 10 / 2025, page 20 / 119 11 / 87 1B represents processor 118 and transceiver 120 as separate components; it is important to note that processor 118 and transceiver 120 can be integrated into a single electronic package or chip.

[035] The transmit / receive element 122 can be configured to transmit to or receive signals from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 can be an antenna configured to transmit and / or receive RF signals. In another embodiment, the transmit / receive element 122 can be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 can be configured to transmit and / or receive both RF and light signals. It is important to note that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[036] Although the transmit / receive element 122 is represented in Figure 1B as a single element, the WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. Thus, in one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) to transmit and receive wireless signals through the air interface 116.

[037] Transceiver 120 can be configured to modulate the signals to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, WTRU 102 can have multimode capabilities. Thus, transceiver 120 can include multiple transceivers to allow WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[038] The WTRU 102 118 processor can be coupled and receive data Petition 870250090286, dated 03 / 10 / 2025, p. 21 / 119 12 / 87 User input from the speaker / microphone 124, the numeric keypad 126 and / or the screen / touch surface 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also send user data to the speaker / microphone 124, the numeric keypad 126 and / or the screen / touch surface 128. In addition, the processor 118 can access information and store data in any suitable type of memory, such as non-removable memory 130 and / or removable memory 132. Non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk or any other type of memory storage device. Removable memory 132 may include a SIM card (subscriber identity module), a memory card, a secure digital memory card (SD) and the like.In other embodiments, processor 118 can access information and store data in memory that is not physically located in WTRU 102, such as in a server or a home computer (not shown).

[039] Processor 118 can receive power from power supply 134 and can be configured to distribute and / or control power to the other components in WTRU 102. Power supply 134 can be any device suitable for powering WTRU 102. For example, power supply 134 can include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[040] Processor 118 can also be coupled to GPS chipset 136, which can be configured to provide location information (e.g., longitude and latitude) relating to the current location of WTRU 102. In addition to, or replacing, the information from GPS chipset 136, WTRU 102 can receive location information via air interface 116 from a station. Petition 870250090286, dated 03 / 10 / 2025, page 22 / 119 13 / 87 base (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It is important to note that WTRU 102 can acquire location information through any suitable location determination method, remaining consistent with a modality.

[041] The processor 118 may also be coupled with other peripherals 138, which may include one or more software and / or hardware modules that provide additional wired or wireless features, functionality and / or connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs and / or video), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker and the like. Peripherals 138 may include one or more sensors.The sensors may be one or more of a gyroscope, accelerometer, Hall effect sensor, magnetometer, orientation sensor, proximity sensor, temperature sensor, time sensor; geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or a humidity sensor.

[042] The WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and DL (e.g., for reception) may be simultaneous. The full-duplex radio may include an interference management unit to substantially reduce and / or eliminate self-interference by means of hardware (e.g., an inductor) or processing. Petition 870250090286, dated 03 / 10 / 2025, page 23 / 119 14 / 87 of signal via a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, the WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., associated with specific subframes for the UL (e.g., for transmission) or the DL (e.g., for reception)).

[043] Figure 1C is a system diagram illustrating RAN 104 and CN 106 according to one mode. As noted above, RAN 104 can employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 104 can also be in communication with CN 106.

[044] RAN 104 may include eNode-Bs 160a, 160b, 160c, although it is important to note that RAN 104 may include any number of eNode-Bs, remaining consistent with one embodiment. eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via wireless interface 116. In one embodiment, eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from WTRU 102a.

[045] Each of the eNode-Bs 160a, 160b, 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, transfer decisions, user scheduling in the UL and / or DL, and the like. As shown in Figure 1C, the eNode-Bs 160a, 160b, 160c can communicate with each other via an X2 interface.

[046] CN 106 shown in Figure 1C may include a mobility management entity (MME) 162, a service gateway (SGW) 164, and a packet data network gateway (PGW) 166. Although the above elements are represented as part of CN 106, it is important to note that Petition 870250090286, dated 03 / 10 / 2025, page 24 / 119 15 / 87 any of these elements may be owned and / or operated by an entity other than the CN operator.

[047] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in RAN 104 via an S1 interface and can serve as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, 102c, carrier activation / deactivation, selection of a specific service gateway during an initial connection of WTRUs 102a, 102b, 102c, and similar. The MME 162 can provide a control plane function to switch between RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[048] The SGW 164 can be connected to each of the B eNodes 160a, 160b, 160c in RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as anchoring user planes during transfers between B eNodes, initiating paging when DL data is available for WTRUs 102a, 102b, 102c, managing and storing contexts of WTRUs 102a, 102b, 102c and similar.

[049] SGW 164 can be connected to PGW 166, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices.

[050] CN 106 can facilitate communications with other networks. For example, CN 106 can provide WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as PSTN 108, to facilitate communications between WTRUs 102a, 102b, 102c and traditional fixed-line communication devices. For example, CN 106 can include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as a Petition 870250090286, dated 03 / 10 / 2025, p. 25 / 119 16 / 87 interface between CN 106 and PSTN 108. In addition, CN 106 can provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[051] Although the WTRU is described in Figures 1A-1D as a wireless terminal, it is considered that, in certain representative embodiments, such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[052] In representative modalities, the other 112 network may be a WLAN.

[053] A WLAN in Basic Services Infrastructure Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access to or an interface with a Distribution System (DS) or other type of wired / wireless network that carries inbound and / or outbound traffic from the BSS. Traffic to the STAs originating from outside the BSS may arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP to be delivered to the respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the originating STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between (e.g., directly between) the source and destination STAs with a Direct Link System (DLS) configuration.In certain representative configurations, DLS may use either 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to here as an “ad-hoc” communication mode. Petition 870250090286, dated 03 / 10 / 2025, p. 26 / 119 17 / 87

[054] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit a beacon on a fixed channel, such as a primary channel. The primary channel can have a fixed width (e.g., 20 MHz bandwidth) or a dynamically defined width. The primary channel can be the BSS's operating channel and can be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access and Collision Avoidance (CSMA / CA) can be implemented, for example, in 802.11 systems. For CSMA / CA, STAs (e.g., each STA), including the AP, can sense the primary channel. If the primary channel is sensed and / or determined to be occupied by a specific STA, that specific STA can back off. An STA (e.g., only one station) can transmit at any time on a given BSS.

[055] High Throughput (HT) STAs can use a 40 MHz wide channel for communication, for example, by combining the 20 MHz primary channel with an adjacent or non-adjacent 20 MHz channel to form a 40 MHz wide channel.

[056] Very High Throughput (VHT) STAs can support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 40 MHz and / or 80 MHz channels can be formed by combining contiguous 20 MHz channels. A 160 MHz channel can be formed by combining 8 contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which can be called an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, can be passed through a segment analyzer that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed on each stream separately. Streams can be mapped to the two 80 MHz channels, and data can be transmitted via a transmitting STA. At the receiver of Petition 870250090286, dated 03 / 10 / 2025, page 27 / 119 18 / 87 For the receiving STA, the operation described above for the 80+80 configuration can be reversed, and the combined data can be sent to the Medium Access Control (MAC).

[057] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, and 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support Meter Type Control / Machine Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain features, for example, limited features, including support for (e.g., support only for) certain bandwidths and / or limited bandwidths. MTC devices may include a battery with a lifespan exceeding a certain limit (e.g., to maintain a very long battery life).

[058] WLAN systems, which can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the highest common operational bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be defined and / or limited by an STA, among all STAs operating in a BSS that support the operating mode with the lowest bandwidth. In the 802.11ah example, the primary channel can be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only support) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing settings Petition 870250090286, dated 03 / 10 / 2025, page 28 / 119 19 / 87 and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, due to a STA (which only supports 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered occupied, even if most of them remain idle and could be available.

[059] In the United States, the available frequency bands that can be used by 802.11ah are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is from 6 MHz to 26 MHz, depending on the country code.

[060] Figure 1D is a system diagram illustrating RAN 113 and CN 115 according to a modality. As noted above, RAN 113 can employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 113 can also be in communication with CN 115.

[061] RAN 113 may include gNBs 180a, 180b, 180c, although it is important to note that RAN 113 may include any number of gNBs, remaining consistent with a modality. gNBs 180a, 180b, 180c may each include one or more transceivers for communication with WTRUs 102a, 102b, 102c via air interface 116. In a modality, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may use beamforming to transmit to and / or receive signals from gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can use multiple antennas to transmit to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers to the WTRU 102a (not shown). A subset of these Petition 870250090286, dated 03 / 10 / 2025, p. 29 / 119 20 / 87 component carriers may be in unlicensed spectrum, while the remaining component carriers may be in licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c may implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[062] WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using transmissions associated with scalable numerology. For example, the spacing of OFDM symbols and / or the spacing of OFDM subcarriers can vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing a variable number of OFDM symbols and / or with variable absolute time duration).

[063] gNBs 180a, 180b, 180c can be configured to communicate with WTRUs 102a, 102b, 102c in a standalone and / or non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c can use one or more of gNBs 180a, 180b, 180c as a mobility docking point. In a standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in an unlicensed band. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect to gNBs 180a, 180b, and 180c, while also communicating / connecting to another RAN, such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate with one or more gNBs 180a, 180b, and 180c. Petition 870250090286, dated 03 / 10 / 2025, p. 30 / 119 21 / 87 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, the eNode-Bs 160a, 160b, 160c can serve as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c can provide additional coverage and / or throughput to serve the WTRUs 102a, 102b, 102c.

[064] Each of the gNBs 180a, 180b, 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, transfer decisions, user scheduling in the UL and / or DL, network slicing support, DC, interoperability between NR and E-UTRA, user plane data routing to User Plane Function (UPF) 184a, 184b, control plane information routing to Access and Mobility Management Function (AMF) 182a, 182b and similar. As shown in Figure 1D, the gNBs 180a, 180b, 180c can communicate with each other via an Xn interface.

[065] The CN 115 shown in Figure 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b and possibly a Data Network (DN) 185a, 185b. Although the above elements are represented as part of the CN 115, it is important to note that any of these elements may be owned and / or operated by an entity other than the CN operator.

[066] AMF 182a, 182b can be connected to one or more of the gNBs 180a, 180b, 180c in RAN 104 via an N2 interface and can serve as a control node. For example, AMF 182a, 182b can be responsible for authenticating users of WTRUs 102a, 102b, 102c, for supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), for selecting a specific SMF 183a, 183b, for managing the log area, and for terminating non-access stratum signaling. Petition 870250090286, dated 03 / 10 / 2025, page 31 / 119 22 / 87 (NAS), for mobility management and similar purposes. Network slicing can be used by AMF 182a, 182b to customize CN support for WTRUs 102a, 102b, 102c based on the types of services used in WTRUs 102a, 102b, 102c. For example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low-latency access (URLLC), services that rely on enhanced massive mobile broadband (eMBB) access, services for MTC access, and similar uses. AMF 182a, 182b can provide a control plane function to switch between RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[067] SMF 183a, 183b can be connected to AMF 182a, 182b on CN 115 via an N11 interface. SMF 183a, 183b can also be connected to UPF 184a, 184b on CN 115 via an N4 interface. SMF 183a, 183b can select and control UPF 184a, 184b and configure traffic routing through UPF 184a, 184b. SMF 183a, 183b can perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy and QoS enforcement, providing DL data notifications, and similar functions. A PDU session type can be IP-based, non-IP-based, Ethernet-based, and similar.

[068] UPF 184a, 184b can be connected to one or more of gNBs 180a, 180b, 180c in RAN 113 via an N3 interface, which can provide WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between WTRUs 102a, 102b, 102c and IP-enabled devices. UPF 184, 184b can perform other functions such as packet routing and forwarding, user plane policy enforcement, support for multihomed PDU sessions, user plane QoS handling, DL packet storage, provision of Petition 870250090286, dated 03 / 10 / 2025, page 32 / 119 23 / 87 Mobility anchoring and similar.

[069] CN 115 can facilitate communications with other networks. For example, CN 115 can include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 115 and PSTN 108. In addition, CN 115 can provide WTRUs 102a, 102b, 102c with access to other 112 networks, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, 102c can be connected to a local DN 185a, 185b via UPF 184a, 184b, through the N3 interface to UPF 184a, 184b, and through an N6 interface between UPF 184a, 184b and DN 185a, 185b.

[070] Considering Figures 1A-1D and the corresponding description of Figures 1A-1D, one or more, or all of the functions described herein, in relation to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein, may be performed by one or more emulation devices (not shown). Emulation devices may be one or more devices configured to emulate one or more, or all of the functions described herein. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[071] Emulation devices may be designed to implement one or more tests of other devices in a laboratory environment and / or in a carrier network environment. For example, one or more emulation devices may perform one or more, or all, of the functions while fully or partially deployed and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more emulation devices may perform one or more, or all, of the functions while temporarily deployed / deployed. Petition 870250090286, dated 03 / 10 / 2025, page 33 / 119 24 / 7 as part of a wired and / or wireless communication network. The emulation device can be directly coupled to another device for testing purposes and / or perform tests using wireless over-the-air communications.

[072] One or more emulation devices may perform one or more, including all, functions while not implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used in a test scenario in a test laboratory and / or in an undeployed (e.g., under test) wired and / or wireless communication network to implement the testing of one or more components. The emulation device(s) may be test equipment. Direct RF coupling and / or wireless communications via RF circuit arrays (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[073] The following abbreviations and acronyms, among others, are used here: Acknowledgment (ACK); Block Error Rate (BLER); Bandwidth Share (BWP); Channel Access Priority (CAP); Channel Access Priority Class (CAPC); Channel Clearance Assessment (CCA); Control Channel Element (CCE); Control Element (CE); Configured Grant or Cell Group (CG); Cyclic Prefix (CP); Conventional OFDM (based on cyclic prefix) (CPOFDM); Channel Quality Indicator (CQI); Cyclic Redundancy Check (CRC); Channel State Information (CSI); Contention Window (CW); Contention Window Size (CWS); Channel Occupancy (CO); Downlink Assignment Index (DAI); Downlink Control Information (DCI); Downlink Return Information (DFI); Dynamic Grant (DG); Downlink (DL); Demodulation Reference Signal (DM-RS); Data Radio Carrier (DRB); Enhanced Licensed Assisted Access (eLAA);Enhanced Licensed Assisted Access (FeLAA); Hybrid Auto-Retry Request (HARQ); License-Based Assisted Access; Petition 870250090286, dated 03 / 10 / 2025, page 34 / 119 25 / 87 (LAA); Listen Before Speaking (LBT); Long Term Evolution (LTE), e.g., from 3GPP LTE R8 and above; Line-of-Sight Probability Indication (LOSPI); Negative ACK (NACK); Non-Terrestrial Network (NTN); Modulation and Coding Scheme (MCS); Multiple Input Multiple Output (MIMO); New Radio (NR); Orthogonal Frequency Division Multiplexing (OFDM); Physical Layer (PHY); Process ID (PID); Paging Occasion (PO); Physical Random Access Channel (PRACH); Primary Synchronization Signal (PSS); Random Access (or Procedure) (RA); Random Access Channel (RACH); Random Access Response (RAR); Radio Access Network Central Unit (RCU); Radio Front-end (RF); Radio Link Failure (RLF); Radio Link Monitoring (RLM); Radio Network Identifier (RNTI); RACH Occasion (RO); Radio Resource Control (RRC); Radio Resource Management (RRM); Reference Signal (RS); Received Reference Signal Power (RSRP);Received Signal Strength Indicator (RSSI); Service Data Unit (SDU); Probing Reference Signal (SRS); Synchronization Signal (SS); Secondary Synchronization Signal (SSS); Exchange Interval (in a self-contained subframe) (SWG); Semi-Persistent Scheduling (SPS); Supplemental Uplink (SUL); Transport Block (TB); Transport Block Size (TBS); Transmit / Receive Point (TRP); Time-Sensitive Communications (TSC); Time-Sensitive Networks (TSN); Uplink (UL); Ultra-Reliable Low-Latency Communications (URLLC); Broadband Part (WBWP).

[074] A WTRU can support synchronization during a same-physical-cell identity (PCI) satellite exchange. In one or more cases, the WTRU may receive assistance information about a same-physical-cell identity (PCI) satellite exchange (e.g., via broadcast signaling). The information may include timing information and / or incoming satellite location information at the time a same-PCI satellite exchange occurs. The WTRU may pre-calculate a time advance based on the future location of the incoming satellite. Petition 870250090286, dated 03 / 10 / 2025, page 35 / 119 26 / 87 at the time of satellite changeover with the same PCI. WTRU can pre-report the future TA value at a specified offset before satellite changeover. WTRU can reset an L3 measurement window at the time of satellite changeover and can apply a measurement configuration. The measurement configuration can be pre-configured. The pre-configured measurement configuration may include, for example, but not limited to, denser measurement objects. WTRU can apply the pre-configured measurement configuration and can filter coefficients to evaluate new channel conditions.

[075] WTRU can provide capacity and / or assistance information related to resynchronization time, for example, to assist in setting up interval measurement. In examples, WTRU can ignore a pre-configured schedule (e.g., CG, periodic SRS, and similar) during resynchronization time.

[076] The WTRU can scale the power for an initial UL transmission to the incoming satellite. The WTRU can scale the power for the initial UL transmission based on the distance difference between the WTRU and the previous satellite and the incoming satellite. In one or more cases, power scaling can be enabled based on a setting / indication in a System Information Block (SIB). Additionally or alternatively, power scaling can be based on line-of-sight probability (e.g., LOSPI% > X).

[077] WTRU can measure reference signals from the incoming satellite to determine how to reorient the spatial filters when the new satellite takes over coverage. For example, WTRU can measure reference signals from an incoming satellite, such as one or more SSB / CSI-RS from a neighboring cell. In one or more cases, WTRU receives an indication / configuration of the reference signal where a first time period (e.g., pre-switch) is QCL with a second reference signal in the second time period (e.g., post-switch) to link the Petition 870250090286, dated 03 / 10 / 2025, page 36 / 119 27 / 87 measurements between cells originating from satellites.

[078] In one or more cases, WTRU may optionally send an ACK (e.g., via SR, via pre-provided resources, using the first available CG resources, etc.) to the incoming satellite to confirm that synchronization has been re-established. For example, WTRU may optionally send the ACK via one or more SRs, pre-provided resources, using the first available CG resources, and the like.

[079] A WTRU can be configured for use in non-terrestrial networks (NTNs). Non-terrestrial networks (NTNs) can facilitate the deployment of wireless networks in areas where terrestrial antennas may be impractical and / or undesirable. For example, terrestrial antennas may be impractical due to geography and / or cost. Along with terrestrial networks, NTNs can provide ubiquitous 5G network coverage. Some examples of NTN deployments can support basic communication and text worldwide. NTN deployments, along with the proliferation of next-generation low-orbit satellites, can enable additional services (e.g., web browsing).

[080] An NTN may include an aerial or space-based platform that, via a gateway (GW), can carry signals from a ground-based gNB to a WTRU and vice versa. Exemplary NTN deployments may support a power class 3 WTRU with an omnidirectional antenna and linear polarization, or a small aperture antenna terminal (VSAT) with a directional antenna and circular polarization. Exemplary NTNs may provide support for LTE-based narrowband IoT (NB-IoT) and eMTC devices. In examples, regardless of device type, NTN WTRUs may be GNSS-compatible.

[081] Aerial or space platforms can be classified in terms of orbit. In some implementations, low Earth orbit (LEO) satellites can operate in an altitude range of 300 to 1,500 km and Earth orbit satellites Petition 870250090286, dated 03 / 10 / 2025, p. 37 / 119 Geostationary (GEO) satellites can operate in an altitude range of 35 to 786 km. Additional platform classifications may also be supported. For example, medium Earth orbit (MEO) satellites, which can operate in an altitude range of 7,000 to 25,000 km, and high-altitude platform stations (HAPS), which can operate in an altitude range of 8 to 50 km, may be supported. Satellite platforms can be further classified as having a “transparent” or “regenerative” payload. Transparent satellite payloads may implement frequency conversion and RF amplification in both UL and DL configurations. In some implementations, multiple transparent satellites may be connected to a ground-based gNB. In some examples, regenerative satellite payloads may utilize a full gNB or a DU gNB onboard the satellite.Regenerative payloads can perform digital processing on the signal, including, for example, demodulation, decoding, recoding, remodulation and / or filtering.

[082] Figure 2 illustrates exemplary interfaces in a non-terrestrial network 200. The following radio interfaces can be defined in NTN. For example, a feed link 202a, 202b can be a wireless link between GW 210 and satellite 208a, 208b. A service link 206 can be a radio link between satellite 208a, 208b and WTRU 212. In some implementations, the Intersatellite Link (ISL) 204 can be a transport link between satellite 208a and satellite 208b. ISL 204 can be supported by regenerative payloads, and can be a proprietary 3GPP radio or optical interface.

[083] A variety of communication interfaces (e.g., 3GPP) can be used for each radio link, for example, depending on the satellite payload configuration. For example, in a transparent payload, the NR-Uu radio interface can be used for both the service link 206 and the feed link 202a, 202b. In examples, for a regenerative payload, the interface Petition 870250090286, dated 03 / 10 / 2025, page 38 / 119 29 / 87 NR-Uu can be used for service link 206, and a satellite radio interface (SRI) can be used for feeder links 202a and 202b. In some implementations, ISLs may not be used. In examples, there may be a UP / CP protocol stack for a transparent payload configuration.

[084] An NTN satellite can support multiple cells, wherein each cell comprises one or more satellite beams. Satellite beams can cover an area on Earth (e.g., as a ground cell). Satellite beams can vary in diameter (e.g., 100 to 1,000 km in LEO deployments, 200 to 3,500 km in diameter in GEO deployments). Beam footprints in GEO deployments can remain fixed relative to Earth. For LEO deployments, the area covered by a beam / cell can change over time due to satellite movement. In one example, beam movement can be classified as “Earth-moving,” in which the LEO beam can move continuously across the Earth. In another example, beam movement can be classified as “nearly fixed on Earth,” in which the beam can be directed to remain covering a fixed location until a new cell overtakes the coverage area in a discrete, coordinated change.

[085] The round-trip time (RTT) and / or maximum differential delay may be greater than those of terrestrial systems, for example, based on the altitude of the NTN platforms and / or the beam diameter. In an exemplary transparent NTN deployment, the RTT may vary from 25.77 ms (e.g., LEO at an altitude of 600 km) to 541.46 ms (GEO), and the maximum differential delay may vary from 3.12 ms to 10.3 ms. In examples, the RTT of a regenerative payload may be approximately half that of a transparent payload. The RTT of a regenerative payload may be approximately half that of a transparent payload, for example, because a transparent configuration may consider both the service link and the feed link, while the RTT of a payload Petition 870250090286, dated 03 / 10 / 2025, page 39 / 119 30 / 87 useful regenerative access can only consider the service link. To minimize the impact on existing NR systems (e.g., to avoid ambiguity in the preamble or to correctly time reception windows), WTRU can perform a time precompensation before initial access.

[086] In one or more cases, the WTRU can be configured with enhancements in the user plan. The pre-compensation procedure can indicate that the WTRU obtains the WTRU position via GNSS, the feed (or common) link delay, and the satellite position through satellite ephemeris data. Satellite ephemeris data can be transmitted periodically in the system information. In examples, satellite ephemeris data may contain the speed, direction, and / or velocity of the satellite. The WTRU can estimate the distance (and therefore the delay) to the satellite. The WTRU can add the feed link delay component to obtain the full WTRU-gNB RTT. The full WTRU-gNB RTT can be used to compensate for timers, receive windows, or timing relationships, including ra-ResponseWindow, msgb-ReponseWindow, and ra-ContentionResolutionTimer. The network can perform frequency compensation.

[087] The WTRU can calculate the WTRU-specific TA (and therefore the WTRUgNB RTT), and exemplary implementations may include a procedure for reporting the TA estimate to the network via a new MAC CE. A Time Advance Report (TAR) may be triggered, in some examples, if one or more of the following events occur. The TAR may be triggered by an indication from upper layers to trigger a Time Advance Report. If the WTRU has not previously reported a TA value for the current service cell, the TAR may be triggered based on an offsetThresholdTA setting by the upper layers. In another example, the TAR may be triggered if the variation between the current Time Advance information and the last reported Time Advance information is equal to or greater than offsetThresholdTA, if configured. Petition 870250090286, dated 03 / 10 / 2025, page 40 / 119 31 / 87

[088] In one or more cases, the WTRU can be configured with HARQ and / or DRX enhancements. The WTRU can be semi-statically configured via RRC to apply specific HARQ behavior to a set of HARQ process IDs. This semi-static configuration can be configured per service cell. Additionally, the semi-static configuration can be optionally configured for UL HARQ and DL processes via one or both of the optional settings, downlinkHARQ-feedbackDisabled and uplinkHARQ-Mode. Regarding downlinkHARQ-feedbackDisabled, the WTRU can be configured per HARQ process ID, and indicates whether HARQ DL feedback is enabled or disabled. Regarding uplinkHARQ-Mode, the WTRU can be configured per HARQ process ID and indicates whether a UL HARQ process uses HARQModeA or HARQmodeB.In examples, HARQmodeA can be applied to transmissions with UL HARQ retransmission enabled, and HARQmodeB can be applied to transmissions with UL HARQ retransmission disabled or with blind UL retransmission.

[089] The WTRU can adapt DRX timers based on the configured HARQ capabilities of a HARQ process. DRX can be adapted for both UL and DL to adapt the DRX active time account for additional propagation delay (e.g., if HARQ feedback is enabled) and / or to allow for additional WTRU power savings (e.g., if HARQ feedback is disabled). The WTRU can adapt the operation based on one or more of the following examples. The WTRU can adapt the DRX timers relative to DL based on one or more of the following examples. For example, if downlinkHARQ-feedbackDisabled is configured for this service cell, upon receiving DL, the WTRU can extend the duration of the HARQ RTT DL Timer by the WTRU-gNB RTT (e.g., propagation delay) if HARQ feedback is enabled for the HARQ process. If downlinkHARQ-feedbackDisabled is configured for this service cell, the WTRU may not be available at the DL reception. Petition 870250090286, dated 03 / 10 / 2025, p. 41 / 119 32 / 87 Initiate drx-RetransmissionTimerDL to allow for additional power savings if HARQ feedback is disabled for the HARQ process. Regarding DL, if downlinkHARQ-feedbackDisabled is configured for this service cell, upon DL reception, the WTRU may apply legacy behavior (e.g., initiate drx-RetransmissionTimerDL after drx-HARQ-RTT-TimerDL expires) if downlinkHARQ-feedbackDisabled is not configured.

[090] The WTRU can adapt the DRX timers relative to the DL relative to the UL based on one or more of the following examples. For example, if uplinkHARQ-Mode is configured for this service cell, in UL transmission, the WTRU can extend the duration of the HARQ RTT DL timer by the WTRU-gNB RTT (i.e., propagation delay) if the HARQ process is configured as HARQModeA. If uplinkHARQ-Mode is configured for this service cell, in UL transmission, the WTRU can not start drx-RetransmissionTimerDL to allow for additional power savings if the HARQ process is configured as HARQModeB. If uplinkHARQ-Mode is configured for this service cell, in UL transmission, the WTRU can apply legacy behavior (e.g., starting drx-RetransmissionTimerUL after drx-HARQ-RTTTimerUL expires) if uplinkHARQ-Mode is not configured.

[091] In one or more cases, the WTRU can be configured with LCP enhancements based on HARQ behavior. The WTRU can be configured to apply an LCP restriction based on the HARQ UL mode configured for the HARQ process ID to which a UL grant is assigned. In one or more instances, the WTRU behavior can be specified based on two optional RRC settings, uplinkHARQ-Mode and allowedHARQ-Mode. uplinkHARQ-Mode can configure HARQ process IDs such as HARQModeA or HARQModeB. allowedHARQ-Mode can be configured per logical channel and defines the allowed HARQ mode of a mapped HARQ process. Petition 870250090286, dated 03 / 10 / 2025, p. 42 / 119 33 / 87 this logical channel.

[092] Upon receiving a new UL grant, the WTRU can determine whether the allowedHARQ-Mode is configured for this LCH, and / or whether a HARQ Mode has been configured for the UL grant's HARQ process. If both are configured, and the LCH can be mapped to HARQ mode, the constraint can be satisfied and the data from this logical channel can be mapped to the UL grant. If uplinkHARQ-Mode or allowedHARQ-Mode is not configured, the WTRU can map this logical channel to any HARQ process.

[093] In one or more cases, the WTRU can be configured with enhancements to the control plane. For example, enhancements to RRC_CONNECTED adapt mobility and / or measurement procedures to non-terrestrial environments. Mobility modifications can include additional execution conditions for conditional transfer, such as the A4 event, and time / location-based conditions. The location-based event can be defined by condEventD1. The location-based event can be satisfied if the distance between the WTRU and a first reference location (e.g., within the service cell) is above a threshold and a second reference location (e.g., within a neighboring cell) is below a threshold. The time-based event can be defined by condEventT1. The time-based event can be satisfied if the conditional transfer execution occurs between, for example, T1 and T2, where T2 = T1 + a duration.

[094] In exemplary NTN implementations, time- and location-based trigger conditions can be configured simultaneously with a measurement condition (e.g., A4). Other modifications can be applied to measurements and may comprise one or more of the following: location-based measurement reports, measurement time configuration (SMTCs) based on Petition 870250090286, dated 03 / 10 / 2025, page 43 / 119 34 / 87 Multiple Synchronization Signal Blocks (SSB) and / or measurement intervals. Location-based measurement reports can be based on eventD1, and can use an execution condition similar to condEventD1. Multiple SMTCs can be configured per carrier for a given set of cells based, for example, on propagation delay difference, feed link delay, and / or satellite ephemeris of the service / neighboring cell. In examples, measurement intervals can be configured using the same or similar propagation delay differences as those calculated for SMTC.

[095] A stationary WTRU can be expected to perform mobility functions for LEO deployments. Based on this, enhanced mobility is of particular interest in LEO deployments. Due to satellite movement, a stationary WTRU can be expected to perform mobility, for example, approximately every 7 seconds, depending on the deployment characteristics.

[096] Enhancements to the re-selection of IDLE / INACTIVE cells may include new measurement rules. Two main enhancements may be based on the distance of a WTRU from a cell reference point, and the time at which a near-terrestrial cell may cease serving the current area (e.g., indicated by t-Service). The cell reference point, or the parameter used to assess the distance condition (e.g., t-Service and distanceThresh), may optionally be transmitted in a SIB (e.g., SIB19). SIB19 may be a new system information block that carries NTN-specific information.

[097] Location-based enhancement can allow for relaxation of the measurement, for example, when the WTRU is located within a boundary (e.g., distanceThresh) of a cell reference point. In one or more implementations, the cell reference point may be the center of the cell. In some examples, there may be a cell reference point that is not the center of the cell. Petition 870250090286, dated 03 / 10 / 2025, page 44 / 119 35 / 87 cell. Based on meeting the conditions, the WTRU will not be able to perform intra-frequency measurements, NR inter-frequency cell measurements of equal or lower priority, and / or inter-RAT frequency cell measurements of lower priority. For example, the WTRU will not be able to perform the above measurements if all of the following conditions are met: the service cell meets Srxlev > SIntraSearchP and Squal > SIntraSearchQ; the WTRU has valid WTRU location information (i.e., the WTRU implementation has available WTRU location information); and the distance between the WTRU and the service cell reference location is less than distanceThresh.

[098] Time-based enhancement may indicate that the WTRU will perform cell reselection measurements on a near-ground fixed cell at some point based on the WTRU implementation (e.g., before tService). In examples, the WTRU may perform intrafrequency, interfrequency, and / or inter-RAT measurements before tService, regardless of the distance between the WTRU and the service cell measurement or whether the service cell meets Srxlev > SIntraSearchP and Squal > SIntraSearchQ, or Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ. Distance and time-based measurement rules may not affect interfrequency NR measurement and / or higher priority inter-RAT frequencies. In examples, the WTRU may perform these measurements regardless of the remaining service time and / or the distance from the cell reference point.

[099] In one or more cases, WTRU can be configured for IoT NTNs. In examples, NR NTN enhancements can be used for IoT NTNs. For example, enhancements may include: time / frequency pre-compensation; time advance reporting; monitoring window and timer compensation; and / or cell (re)selection enhancements based on t-service. Some implementations may support enhancements such as HARQ return. Petition 870250090286, dated 03 / 10 / 2025, page 45 / 119 36 / 87 disabled and / or mobility enhancements.

[0100] IoT NTNs can utilize enhancements related to considering discontinuous coverage scenarios. Discontinuous coverage for NTNs can refer to temporary and / or predictable coverage gaps caused by non-continuous coverage in non-geostationary satellite orbit (NGSO) deployments. This may not be a problem if continuous coverage is available globally, but continuous coverage may not be available globally in some NTN deployments (e.g., early deployments, deep rural deployments). IoT NTNs can provide enhancements to handle discontinuous coverage scenarios. In some instances, these enhancements may not be present for NR NTNs.

[0101] Due to the deterministic movement of the satellite, coverage intervals can be predicted and accounted for. IoT NTNs can support additional assistance information (e.g., satellite ephemeris and coverage parameters such as coverage radius, cell reference points or elevation angles, and / or the service start time for a neighboring cell provided by t-servicestart) to predict the duration of a coverage interval. While within a discontinuous coverage interval, the WTRU can suspend AS functionality.

[0102] In some implementations, there may be enhancements for NR NTNs. For example, enhancements for NR NTNs may include: coverage enhancements, NR-NTNs above 10 GHz, network-verified WTRU (NW) location and / or NTN-NTN and NTN-TN mobility and / or continuity of service. Coverage enhancements may include enhancements to PUCCH for Msg4 HARQ-ACK, DMRS grouping for PUCCH (e.g., considering specific NTN issues), and support for blind MSG3 relay grant reception. For NR-NTN above 10 GHz, there may be an analysis of, for example, regulations and channel coexistence scenarios. Petition 870250090286, dated 03 / 10 / 2025, page 46 / 119 37 / 87 adjacent, Rx / Tx requirements for satellite access node and WTRU class, and / or values ​​for physical layer parameters. There may be enhancements for network-verified WTRU location, for example, multi-RTT to support network-verified WTRU location. For NTN-NTN and NTN-TN mobility and continuity of service, there may be enhancements related to, for example: (re)selection of cells for NTN-TN cells and ground movement, transfer to reduce signaling overhead, and / or Xn / NG signaling to support feed link exchanges.

[0103] In some implementations, there may be enhancements for IoT NTNs. For example, IoT NTN enhancements may include: performance enhancements, mobility enhancements, and / or discontinuous coverage scenarios. For performance enhancements, there may be support for disabled HARQ return and / or enhanced GNSS operations for a new position fix for WTRU pre-compensation during long connection times. For mobility enhancements, there may be measurement triggering before RLF, signaling in neighboring cell ephemeris system information, adoption of Rel-17 solutions introduced in NR-NTN for mobility enhancement, and / or basic WTRU RRM requirements for the listed features. For discontinuous coverage scenarios, enhancements may include the specification of mobility management enhancements and / or power saving enhancements for discontinuous coverage.

[0104] In one or more cases, the WTRU can be configured for synchronization during the exchange of satellites of the same PCI. In some NTNs, cells originating from different satellites can be associated with different PCIs. A stationary WTRU can experience continuous L3 mobility as the satellite in service moves over the earth and goes out of coverage (e.g., due to the curvature of the Earth), and a new satellite can take over coverage of the geographic area. Petition 870250090286, dated 03 / 10 / 2025, p. 47 / 119 38 / 87

[0105] Figure 3 illustrates a same PCI 300 exchange, where satellites 302a and 302b serve the same PCI 304a. For quasi-terrestrial fixed cell cases, a hard exchange can occur on the same SSB frequency and the same gNB. In these quasi-terrestrial fixed cell cases, satellite exchange without PCI exchange can be supported. In example 300, a PCI exchange is shown. A WTRU 310 can support resynchronization with an incoming satellite 302b serving the same PCI 304a. Methods and implementations for WTRU resynchronization can reduce downtime during satellite exchange and avoid unnecessary radio link failures (RLF).

[0106] In the example of the same PCI 300, a geographic area is associated with PCIs 304a, 304b, 304c and gNB 306. At time T0, PCI 304a is served by a first satellite 302a. As the first satellite 302a moves out of range (e.g., due to the curvature of the Earth), a second (incoming) satellite 302b connected to the same gNB 306 can begin serving PCI 304a. This can occur at some transition point 308 that can be known in advance by the network. This solution avoids the need for L3 mobility, thus reducing signaling overhead. However, since the previous satellite 302a and the incoming satellite 302b are physically distant, WTRU 310 needs to resynchronize with the new satellite 302b, as the radio conditions, time advance, Doppler compensation, and UL beam direction can be very different.Since PCI 304a, gNB 306, and the SSB frequency remain the same, satellite switching can be virtually transparent to the WTRU 310, and the WTRU 310 may need some service information to facilitate resynchronization with the incoming satellite 302b. The WTRU 310 can support resynchronization with the incoming satellite 302b, which meets the same PCI 304a. Resynchronization of the WTRU can reduce downtime during satellite switching and avoid unnecessary RLF.

[0107] A WTRU can be configured for time synchronization. Petition 870250090286, dated 03 / 10 / 2025, p. 48 / 119 39 / 87 during a same-PCI satellite exchange. In one or more cases, prior to the same-PCI satellite exchange, the WTRU may be configured to pre-report the time advance and assistance information for the incoming satellite (e.g., time and position of the incoming satellite at the same-PCI satellite exchange). The WTRU may be configured to reduce TA resynchronization time and congestion due to large-scale TA reporting. The WTRU may calculate the incoming satellite's time advance at the time of the same-PCI satellite exchange using the assistance information and report the future TA at an offset configured for the satellite exchange time. The future TA at the offset configured for the satellite exchange time may indicate, for example, the TA value applicable to the incoming satellite. At the time of the satellite exchange, the WTRU may apply the pre-calculated TA to subsequent transmissions.If the WTRU successfully reports the TA to the incoming satellite before the satellite switch, the WTRU can ignore the TAR trigger (e.g., due to the offsetThresholdTA setting).

[0108] In some instances, WTRU may calculate a TA value using ephemeris data before RACH. Thus, a large time difference at the time of a same-PCI satellite exchange (which does not require RACH) can cause TA synchronization failure. Relying on certain triggers for TA reporting (e.g., offsetThresholdTA) can cause significant signaling overhead after the exchange time. Therefore, to address the problems in these systems, WTRU may pre-calculate TA based on the future location of the incoming satellite at the time of the same-PCI satellite exchange. WTRU may pre-report the future TA value, for example, at an indicated offset before the satellite exchange.

[0109] The WTRU can receive (e.g., via broadcast) the time and position of the incoming satellite for the same PCI satellite exchange. In one or more cases, the WTRU can receive a configuration to pre-report the TA to the new satellite (pre Petition 870250090286, dated 03 / 10 / 2025, p. 49 / 119 40 / 87 (TAR). The WTRU may receive a configuration comprising one or more of the following: an enable / disable indication for pre-TAR reporting; an offset prior to the satellite exchange time for pre-TAR reporting; a time period for pre-TAR reporting; and / or conditions for pre-TAR reporting. Conditions for pre-TAR reporting may include, for example, a TA delta limit for the preceding satellite. In one or more cases, the WTRU may pre-calculate the TA value for the incoming satellite using the incoming satellite's position at the time of PCI exchange. In one or more cases, the WTRU may transmit the pre-calculated TA value according to the pre-report configuration. In examples, the pre-report configuration may indicate that the TA value is associated with the incoming satellite. In one or more cases, the WTRU may apply pre-calculated TA to the incoming satellite at the time of same PCI satellite exchange.For cases where WTRU successfully reported the future time advance before the satellite change (e.g., WTRU receives an ACK for the transmission carrying the pre-TAR), WTRU can ignore the trigger condition if the offsetThresholdTA is configured and the TAR is triggered due to the satellite change. For cases where WTRU failed to successfully report the future time advance before the satellite change, WTRU can transmit a TAR at the time of the satellite change using the pre-calculated time advance. In one or more cases, WTRU can transmit a UL TB using the pre-calculated TA (e.g., after a satellite change on the same PCI).

[0110] A WTRU can be configured for radio link monitoring (RLM) during a same-PCI satellite change. After a same-PCI satellite change, the cell quality measurements and / or information associated with the previous satellite may no longer be valid. To prevent the channel conditions for the incoming satellite from being averaged, the WTRU can reset the L3 measurement window at the time of the satellite change. The WTRU can apply a Petition 870250090286, dated 03 / 10 / 2025, page 50 / 119 41 / 87 new measurement configuration (e.g., a temporary configuration with a denser set of measurement objects) and / or L3 filter coefficients after satellite change to acquire measurements and resynchronize with the incoming satellite. WTRU may temporarily suspend L3 event-based reporting with some offset before and / or after satellite change to avoid unnecessary reporting and mobility. For example, to avoid using resources that report to a cell that is no longer available, WTRU may temporarily suspend L3 event-based reporting by some offset before satellite change, such as if channel conditions were about to change. Alternatively or additionally, WTRU may temporarily suspend L3 event-based reporting by some offset to allow time to properly measure the new channel conditions.

[0111] In some implementations, WTRU may average cell measurements over time to obtain L3 cell quality. This process can delay the detection of radio problems for the new satellite after satellite switching, and rapid communication of new measurements with the incoming satellite may require a measurement reconfiguration after satellite switching. A measurement reconfiguration can be time-consuming, considering the WTRU-gNB RTT and / or the risk of RLF. In examples, to solve the above problem, WTRU may reset the L3 measurement window at the time of satellite switching and may apply a pre-configured measurement configuration (e.g., with denser measurement objects) and / or filter coefficients to quickly assess the new channel conditions.

[0112] In one or more cases, the WTRU receives (e.g., via broadcast) the time when a satellite changeover of the same PCI will occur. The WTRU may receive a measurement configuration to be applied at the time of the satellite changeover of the same PCI. The measurement configuration may comprise one or more of the Petition 870250090286, dated 03 / 10 / 2025, page 51 / 119 42 / 87 following: a temporary measurement configuration; expiration conditions for the temporary measurement configuration (e.g., number of measured RSs, duration, etc.); a second measurement configuration (e.g., to be applied after the temporary measurement configuration); L3 filter coefficients to be applied at the time of satellite switching; and / or a configuration to suspend measurement reporting. The configuration information indicating the suspension of measurement reporting may comprise one or both of the following, for example, a start time and a duration.

[0113] WTRU can perform same-PCI satellite exchange based on the received configuration. WTRU can perform one or more of the following actions related to performing a same-PCI satellite exchange: suspend measurement reporting (e.g., subject to some configured ban duration); reset an L3 measurement window (e.g., discarding previous measurements from the service cell); apply a temporary measurement configuration; and / or apply updated L3 filter coefficients. In examples, the expiration conditions for the temporary measurement configuration may not be met, or may not be configured, and WTRU may perform measurements according to the temporary measurement configuration and filtering based on the updated L3 filter coefficients.If the expiration conditions for the temporary measurement configuration are met and the WTRU has not received a second measurement configuration, the WTRU may revert to a previous measurement configuration (e.g., the configuration used before the satellite change). The WTRU may transmit a measurement report based on the new measurement configuration.

[0114] A WTRU can be configured for transmission handling for same-PCI satellite exchange. The WTRU resynchronization time associated with a same-PCI satellite exchange may vary based on the WTRU's ability to determine, or pre-determine, aspects of synchronization (e.g., advance of Petition 870250090286, dated 03 / 10 / 2025, page 52 / 119 43 / 87 timing, power control, etc.). During resynchronization, transmission and / or reception may be suspended. If the network is unaware of the WTRU's resynchronization time, there may be associated risks. For example, there may be a risk of additional latency and missed transmission opportunities (e.g., if the resynchronization time is overestimated) or missed transmission (TX) and / or reception (RX) opportunities (e.g., if the resynchronization time is underestimated). To support the resynchronization interval configuration, WTRU may send capacity and / or assistance information (e.g., estimated resynchronization time) before the satellite change. During resynchronization, WTRU may suspend TX and / or RX, including, for example, pre-scheduled transmissions such as configured leases, periodic CSI / SRS, etc.In one or more instances, after resynchronization, the WTRU may signal that synchronization is complete (e.g., by transmitting one or more UL signals). Examples of UL signals may include, but are not limited to: SR, CG transmission, PRACH, HARQ ACK, and similar signals.

[0115] In some implementations, WTRU may rely on network scheduling and / or periodicity settings for pre-configured transmissions to ensure that WTRU transmission and / or reception does not occur during resynchronization to a new satellite. If the network's resynchronization time estimate is incorrect, resynchronization to a new satellite may cause wasted resources (e.g., overestimated) or loss of TX and / or RX (e.g., underestimated). To address issues in these systems, WTRU may provide capacity information and / or assistance regarding resynchronization time to aid in setting the measurement interval. WTRU may ignore a pre-configured schedule (e.g., periodic CG, SRS, and similar) during the resynchronization time. Alternatively or additionally, WTRU may optionally send an ACK to confirm that synchronization has been achieved. Petition 870250090286, dated 03 / 10 / 2025, p. 53 / 119 44 / 87 retrieved. For example, WTRU can optionally send the ACK via one or more SRs, pre-provided resources, using the first available CG resources, and similar methods.

[0116] The WTRU may receive (e.g., via broadcast) configuration information indicating the time at which a same-PCI satellite exchange will occur. In one or more instances, the WTRU may transmit assistance information prior to the same-PCI satellite exchange. Assistance information may, for example, include one or more of the following: resynchronization duration; WTRU's ability to perform synchronization procedures (e.g., pre-calculation and time-advance reporting); prior to the same-PCI satellite exchange; and / or a time at which the WTRU may resume transmission and / or reception after the same-PCI satellite exchange. The WTRU may receive configuration information for satellite resynchronization.The configuration for satellite resynchronization may, for example, comprise one or more of the following: a resynchronization interval configuration; conditions for declaring resynchronization failure; and / or features (e.g., a UL grant, dedicated RACH preamble) to indicate successful resynchronization.

[0117] The WTRU can perform a same-PCI satellite switch to the second satellite, for example, based on configuration information indicating the time for the same-PCI satellite switch. When performing a same-PCI satellite switch, the WTRU can initiate a resynchronization interval, suspend UL transmission and / or DL ​​reception, and perform one or more resynchronization procedures (e.g., time advance calculation, Doppler compensation, power control, measurements) for the incoming satellite. The WTRU can initiate a resynchronization interval using the received configuration information. The WTRU can transmit a successful resynchronization indication (e.g., via provided resources), if configured to do so, after the Petition 870250090286, dated 03 / 10 / 2025, page 54 / 119 45 / 87 successful resynchronization with the satellite.

[0118] A WTRU can be configured for power control for switching satellites of the same PCI. The UL TX power required by the WTRU after a satellite switch can vary significantly, for example, due to the large difference in location between the previous satellite and the incoming satellite. If the WTRU consumes too little power, it risks unsuccessful reception. If it consumes too much power, it risks interference and unnecessary power consumption. In examples, line of sight (LOS) may be likely (e.g., highly likely) in NTN environments. If LOS is present, the largest component of path loss may be due to propagation losses in free space.

[0119] WTRU can estimate free-space propagation losses based on known information. For example, WTRU can estimate free-space propagation losses based on the known location of the preceding and incoming satellites (e.g., through assist information). Using the free-space propagation estimate, WTRU can scale the UL transmit power for the initial transmission to the incoming satellite based on the delta distance from the preceding satellite. The UL transmit power can be further controlled by the NW setting (e.g., enabled / disabled, maximum delta scaling allowed). Additionally or alternatively, the UL transmit power may be subject to conditions. For example, the UL transmit power may be based on the line-of-sight probability (LOSPI) for the preceding satellite and / or the incoming satellite being above a configured threshold.

[0120] In some instances, the WTRU may wait to adjust the UL transmission power after a satellite change until a power control command is received. In such instances, waiting for a power control command to adjust the UL transmission power may cause failures in the(s) Petition 870250090286, dated 03 / 10 / 2025, page 55 / 119 46 / 87 transmission(s) (e.g., if the initial power is too low) or interference and / or excessive power consumption (e.g., if the power control is too high). To resolve this, the WTRU can scale the power used for the initial UL transmission to the new satellite based on the distance difference between the WTRU, the old satellite, and the new satellite. In examples, scaled power can be enabled based on a configuration and / or indication in a SIB. Additionally or alternatively, scaled power can depend on a high probability of line-of-sight (i.e., LOSPI% > X).

[0121] The WTRU may receive (e.g., via broadcast) assistance information for the preceding satellite and the incoming satellite. Assistance information may include one or more of the following: ephemeris data of the currently in-service satellite; the time of the same PCI satellite change; and / or the position of an incoming satellite at the time of the same PCI satellite change. In one or more cases, the WTRU may receive configuration information to calculate the UL TX power for the incoming satellite. The configuration to calculate the UL TX power may comprise one or more of the following: an enable / disable indication; a maximum delta value to which the original TX power can be autonomously adjusted by the WTRU; a minimum line-of-sight probability limit for the preceding satellite and the incoming satellite; and / or a determination as to whether to indicate by how much the WTRU adjusted the UL TX power and / or the UL TX power level (e.g., on the first transmission).In one or more cases, WTRU may acquire updated information from WTRU (e.g., via GNSS). WTRU may calculate the distance from WTRU to the satellite for each satellite at the time of a same-PCI satellite exchange (e.g., using satellite assistance information). In one or more cases, WTRU may calculate the target line probability for each satellite. For example, for a same-PCI satellite exchange, if WTRU's autonomous UL TX power adjustment is enabled and the line conditions are... Petition 870250090286, dated 03 / 10 / 2025, p. 56 / 119 If line-of-sight conditions for the preceding satellite and the incoming satellite are met, the WTRU can adjust the UL TX power (e.g., proportional to the relative distance between the two satellites). The WTRU can transmit an initial UL transmission using the adjusted UL TX power. The WTRU can include the delta adjustment and / or the current UL TX power in the initial transmission (e.g., if configured by the network). In examples, for a same-PC satellite exchange, if the WTRU's autonomous UL TX power adjustment is not enabled and / or the line-of-sight conditions for the preceding satellite and the incoming satellite have not been met, the WTRU can transmit an initial UL transmission with the UL TX power used for transmission to the preceding satellite.

[0122] A WTRU can be configured for beam management during same-PCI satellite exchange. The in-service satellite and the incoming satellite during a same-PCI satellite exchange may be in different locations. Thus, the WTRU can reorient the UL TX beam after the satellite exchange. The WTRU can predict how to reorient the WTRU's spatial filters, for example, using a reference signal from a neighboring cell (e.g., SSB / CSI-RS) originating from the incoming satellite that will take over the PCI. To support this mapping, the WTRU can receive an indication and / or configuration that a reference signal (e.g., originating from the incoming satellite) in a first time period (e.g., before the satellite exchange) is nearly colocalized (QCL) with a second reference signal in a second time period (e.g., after the satellite exchange).In this way, WTRU can apply measurements taken before the switch to predetermine the beam direction and channel conditions for the incoming satellite after the switch, thus speeding up resynchronization for the incoming satellite.

[0123] In some instances, WTRU may wait to determine how to reorient spatial filters and perform channel measurements until after a satellite exchange event, thus increasing the resynchronization time. To resolve Petition 870250090286, dated 03 / 10 / 2025, page 57 / 119 48 / 87 Problems in legacy systems, the WTRU can measure reference signals from the incoming satellite (e.g., some SSB / CSI-RS from a neighboring cell) to understand how to reorient spatial filters when the incoming satellite takes over coverage. The WTRU can receive an indication and / or configuration of the reference signal in the first time period (i.e., pre-switch) in QCL with a second reference signal in the second time period (i.e., post-switch) to link the measurements before and after the switch.

[0124] The WTRU may receive (e.g., via transmission) configuration information indicating the time of satellite switching from the same PCI. In one or more cases, the WTRU may receive an indication and / or configuration that a reference signal in a first time period (e.g., before satellite switching) is QCL with a second reference signal in the second time period (e.g., after satellite switching). In examples, the WTRU may measure reference signals originating from the incoming satellite during the first time period. In one or more cases, the WTRU calculates the beam direction and path loss DL to the incoming satellite using reference signals from the first time period.In a same-PCI satellite exchange, the WTRU can reorient the UL TX beam (e.g., by applying an updated spatial filter) and adjust the transmit power for the initial UL transmission (e.g., based on the measured DL path loss from the first time period) based on the mapping configuration and the first time period reference signal measurements. In examples, the WTRU can link first time period measurements to second time period measurements. In examples, the WTRU can transmit a same-PCI satellite exchange confirmation (e.g., using a pre-configured MAC CE or PUCCH) using a determined UL TX beam and the transmit power calculated based on the received reference signal power (RSRP) of the reference signal during the first time period. Petition 870250090286, dated 03 / 10 / 2025, page 58 / 119 49 / 87

[0125] Note that the term “previous satellite” may refer to the satellite serving the PCI before a same-PCI satellite exchange. Furthermore, note that the term “incoming satellite” may refer to the satellite serving the PCI after a same-PCI satellite exchange. Note that the term “temporary measurement configuration” may refer to a measurement configuration applied at or near the time of a same-PCI satellite exchange to, for example, support fast resynchronization with the incoming satellite. Furthermore, note that the term “resynchronization interval” may refer to a period specified or configured by the network during which the WTRU is expected to perform one or more aspects of resynchronization with an incoming satellite during a same-PCI satellite exchange.It is also observed that the term "autonomous WTRU power adjustment" may refer to an adjustment of the UL transmission power by the WTRU for an initial UL transmission to the incoming satellite after a satellite change with the same PCI.

[0126] The methods and modalities described herein may refer to examples of same-PCI satellite exchange. However, it should be understood that the modalities may apply to other non-terrestrial mobility scenarios, such as, but not limited to: feed link exchange, quasi-terrestrial fixed cell change and / or intersatellite mobility and / or cell (re)selection (e.g., replacing “same-PCI satellite exchange” with one or more of the above scenarios in a given solution). Furthermore, it should be understood that the modalities may apply to multi-TRP scenarios, in which more than one TRP serves a PCI, and to resynchronization during transfer without RACH. Additionally, the modalities described herein may support resynchronization enhancements (e.g., faster resynchronization) for an incoming satellite during a same-PCI satellite exchange.Thus, methods and approaches can reduce service interruption time and / or reduce the risk of RLF (Remote Logistic Failure) due to incorrect synchronization. Petition 870250090286, dated 03 / 10 / 2025, page 59 / 119 50 / 87 In examples, these modes can allow pre-synchronization, thus reducing the risk of congestion caused by signal overload after a satellite change. It should be noted that the modes discussed here can be combined with one or more of the other modes discussed here.

[0127] A WTRU can be configured with configuration and / or assistance information to support resynchronization with an incoming satellite. To support resynchronization of same-PCI satellite switching, the WTRU can receive assistance and / or configuration information from the network. Assistance and / or configuration information can be provided, for example, via dedicated signaling (e.g., via RRC, MAC CE, or DCI signaling), transmitted system information, or both. For example, the WTRU can receive assistance information, such as same-PCI switching time and information related to the neighboring satellite's position, in a transmitted manner, and the WTRU can receive configuration information for TA calculation, measurement reports, resynchronization interval configuration, power control, and / or beam management in a dedicated manner (e.g., via RRC).In one or more cases, WTRU may (for example, through configuration) receive and maintain up-to-date system information prior to a satellite change on the same PCI. WTRU may receive and maintain up-to-date system information prior to a satellite change on the same PCI to minimize the risk of resynchronization failure and ensure that the necessary information is available at the time of the satellite change on the same PCI.

[0128] WTRU configuration and / or dedicated support information may override support information received via broadcast indication in some cases. For example, WTRU may receive one or more of the following support information and / or configurations to support same-PCI satellite exchange resynchronization: Petition 870250090286, dated 03 / 10 / 2025, pp. 60 / 119 51 / 87 a same PCI satellite exchange time (e.g., 10:31:20 UTC); a location of the incoming satellite at the time of the same PCI satellite exchange; a location of the previous satellite at the time of the same PCI satellite exchange; ephemeris data of the incoming satellite (e.g., to support WTRU prediction of the incoming satellite location at the time of the same PCI satellite exchange); ephemeris data of the previous satellite (e.g., to support WTRU prediction of the previous satellite location at the time of the same PCI satellite exchange); common time information (e.g., feed link delay, kmac, and similar) for the incoming satellite and / or previous satellite (e.g., at the time of the same PCI satellite exchange); information and / or settings to support pre-calculation and reporting of the time advance for the incoming satellite;Information and / or settings to support radio link monitoring; information and / or settings for RX / TX resynchronization interval and suspend; information and / or settings to support WTRU autonomous UL power adjustment; information and / or settings to support beam management; information and / or settings to support resynchronization status indication.

[0129] In one or more instances, the WTRU may be configured to request inbound satellite assistance information during a same-PCI satellite exchange. The WTRU may request assistance information to support resynchronization with an inbound satellite during a same-PCI satellite exchange. For example, if the WTRU was unable to acquire one or more information fields required to complete resynchronization before the same-PCI satellite exchange, the WTRU may trigger a request. Alternatively or additionally, the WTRU may trigger a request for assistance information based on connection establishment (e.g., initial access, service resumption) or mobility. In one or more instances, the request for information of Petition 870250090286, dated 03 / 10 / 2025, pp. 61 / 119 52 / 87 assistance can be sent via, for example, UCI, SR, RACH messages (e.g., MSGA, MSG3, MSG5), PUSCH, MAC CE and / or RRC signaling. The assistance information request may include a general request (e.g., a flag indicating a request for all available information). The assistance information may indicate one or more specific information fields to be provided to WTRU.

[0130] A WTRU can be configured for time synchronization for a same-PCI satellite exchange. Due to the fact that the incoming satellite and the preceding satellite, during a same-PCI satellite exchange, are physically located very far apart, the WTRU may exhibit a large difference in time advance when the satellite exchange occurs. In examples (e.g., legacy implementations), a WTRU may calculate a TA value via ephemeris before RACH. Based on this, there may be a TA difference at the time of a same-PCI satellite exchange (e.g., which may not require RACH), which may cause TA synchronization failure. In examples, relying on existing triggers for TA reporting (e.g., offsetThresholdTA) may cause congestion after the satellite exchange due to, for example, signaling overhead resulting from triggering large-scale TA reporting.

[0131] The methods and modalities described herein can reduce TA resynchronization time and / or decrease the risk of congestion after a satellite exchange (e.g., due to large-scale TA reporting). For example, a WTRU can pre-calculate TA values ​​based on the future location of an incoming satellite at the time of the same PCI satellite exchange and pre-report the future TA value at a specified offset before the satellite exchange.

[0132] In one or more implementations, the WTRU can be configured to pre-calculate a time advance for an incoming satellite. The WTRU can pre-calculate the TA for an incoming satellite to the time of satellite switching. Petition 870250090286, dated 03 / 10 / 2025, page 62 / 119 53 / 87 same PCI. The WTRU can pre-calculate the TA to, for example, allow fast time synchronization for an incoming satellite after a same PCI satellite change. In examples, the network can control (e.g., enable / disable) the WTRU's ability to pre-calculate the TA through one or more explicitly configured RRCs, indication in the transmission signaling, and a (dis)activation command (e.g., via MAC CE). The network can configure a window (e.g., a time period) and / or an offset of the same PCI satellite change for the WTRU to pre-calculate the TA. In cases where the WTRU cannot determine the future TA until the end of this time period or until a specified time, the WTRU cannot pre-calculate the time advance. In cases where time advance pre-calculation is enabled and the WTRU cannot perform the pre-calculation, the WTRU can send a report or indication to the network.

[0133] To support TA pre-calculation, WTRU may use configuration and / or assistance information corresponding to the incoming satellite to determine, for example, common time information (e.g., feed link delay) and / or the satellite location at the time of same-PCI satellite exchange. This information may be, for example, the explicit position of the satellite at the time of same-PCI satellite exchange. Alternatively or additionally, WTRU may use ephemeris data from the incoming satellite to predict the satellite location at the time of same-PCI satellite exchange. WTRU may obtain the WTRU location (e.g., via GNSS) and calculate the distance between WTRU and the incoming satellite at the time of same-PCI satellite exchange.Using the distance between the WTRU and the incoming satellite to estimate the service link delay, the WTRU can add the common timing information from the incoming satellite to determine the total time advance between the WTRU and the incoming satellite at the time of the same PCI satellite change. The WTRU can store the pre-calculated value to be applied in subsequent UL transmissions. Petition 870250090286, dated 03 / 10 / 2025, page 63 / 119 54 / 87 same time as the PCI satellite exchange and / or after that time (or another time explicitly indicated).

[0134] In one or more cases of time advance pre-calculation, the WTRU may be requested and / or triggered to report the WTRU location so that the network can calculate the WTRU time advance. The WTRU may be requested and / or triggered, for example, at a prior offset before the same PCI satellite change, to report the WTRU location. In some cases, the WTRU may be requested and / or triggered to report the estimated location of the WTRU at the time of the satellite change. In examples, the network may provide a time advance command with an associated activation time. The associated activation time may be, for example, the same time as the same PCI satellite change. In one or more cases, the WTRU may apply the TA value to transmissions that occur after the activation time.

[0135] For cases where the WTRU has pre-reported the TA value, the WTRU may receive additional TA adjustments from the network before the satellite change. For example, the network may indicate (e.g., explicitly) whether a TA command is for the current TA (e.g., for the previous satellite) or for the future TA (e.g., for the incoming satellite).

[0136] In one or more cases, the WTRU may be provided with two types of ephemeris information to determine time advance values. A first type of ephemeris information may be used to determine one or more transmission parameters for a transmission on the current uplink. The first type of ephemeris information may be used to determine one or more transmission parameters for a first time window. The transmission parameters may be, for example, WTRU-specific and / or cell-specific time advance value, K_offset, K_mac, and the like. A second type of ephemeris information may be used to determine one or more transmission parameters. Petition 870250090286, dated 03 / 10 / 2025, pp. 64 / 119 55 / 87 for a future uplink transmission. The second type of ephemeris information can be used to determine one or more transmission parameters for a second time window. In one or more cases, the first type of ephemeris information can be associated with the current satellite and the second type of ephemeris information can be associated with the incoming satellite. In one or more cases, the second type of ephemeris information can be provided by the current satellite. In one or more cases, one or more ephemeris information pieces can be configured or provided to the WTRU (e.g., via a top signal) and each ephemeris information piece can be indicated or associated with time information. Time information can include, for example, a validity timer, timestamp, validity duration, start time, start / end time, and the like.

[0137] WTRU can report time advance to the incoming satellite. WTRU can report TA based on a configuration. WTRU can report pre-calculated TA to the incoming satellite before same-PCI satellite exchange. WTRU can report pre-calculated TA to the incoming satellite to reduce congestion after same-PCI satellite exchange caused by large-scale TAR. WTRU pre-TA reporting (i.e., pre-TAR) may be subject to configuration, which may include one or more of the following: an enable / disable indication; a same-PCI exchange time offset to perform pre-TAR; a window (e.g., time period) to report pre-TAR; and / or features (e.g., a UL scheduling grant) to report to pre-TAR which information fields to include in a pre-TAR (e.g., service link TA vs. full TA).

[0138] WTRU can pre-report TA to the incoming satellite. For example, WTRU can pre-report the time advance to the incoming satellite if a valid configuration is provided and / or upon explicit request from Petition 870250090286, dated 03 / 10 / 2025, p. 65 / 119 56 / 87 network. Alternatively or additionally, WTRU may report the TA value in advance, subject to one or more pre-configured conditions. For example, WTRU may transmit a pre-TAR for cases where the TA difference between the previous satellite and the incoming satellite is greater than a threshold.

[0139] For cases where the time advance pre-report is enabled and all configured conditions are met, the WTRU may trigger the transmission of a pre-TAR. A pre-TAR may include one or more of the following: an explicit indication that the TAR corresponds to a future time advance value (e.g., for the incoming satellite at the time of the same PCI satellite change); an absolute TA value corresponding to the total time advance of WTRUgNB; an absolute TA value for the service link (e.g., WTRU-incoming satellite time delay); the delta of the currently applied time advance (e.g., for the previous satellite); information used to pre-calculate the TA (e.g., the location and timing information of the incoming satellite); and / or an estimate by the WTRU of when the WTRU will be time-synchronized (e.g., when the WTRU applies the TA value to subsequent UL transmissions).

[0140] In one or more cases, the WTRU can be configured to perform one or more actions at the time of a same-PCI satellite exchange. At the time of a same-PCI satellite exchange (or at an explicitly indicated activation time), the WTRU can apply the pre-calculated TA value and use it for subsequent transmissions. If the WTRU is configured with offsetThresholdTA and the application of the new TA value triggers a time advance report (TAR), the WTRU can ignore the TAR trigger if it has already pre-reported the TA value to the incoming satellite. The WTRU can ignore the TAR trigger by not triggering the TAR and sending an updated report. In one example, the WTRU can ignore the trigger subject to confirmation that the pre-reported time advance value was successfully received. The WTRU can assume successful reception, for example, based on Petition 870250090286, dated 03 / 10 / 2025, p. 66 / 119 57 / 87 at the HARQ-ACK reception.

[0141] Figure 4 is a flowchart illustrating a 400 process for pre-calculating the time advance and reporting for an incoming satellite during a same-PCI satellite exchange. In one or more cases, prior to the satellite exchange, the WTRU may receive the TA reporting configuration and information about the time and position of the neighboring satellite at the satellite exchange point. In 402, the WTRU may receive assistance information about the incoming satellite. The assistance information received in 402 may include one or more of the following: the time of the same-PCI satellite exchange; the location of the incoming satellite at the same-PCI satellite exchange; and / or ephemeris data of the incoming satellite. In 404, the WTRU may receive configuration information to pre-report the time advance of an incoming satellite.For example, the configuration information received in 404 may include: an enable / disable indication; a reporting time offset relative to the same PCI satellite change time; a time window for pre-reporting the same PCI satellite change; resources to report; and / or conditional limits for enabling pre-reporting (e.g., delta time).

[0142] On 406, the WTRU can pre-calculate the time advance for the incoming satellite to the same PCI satellite changeover time (e.g., if enabled and all configured conditions met). If the WTRU is configured to pre-report the time advance on 408, and the pre-reporting conditions are met on 410, then the WTRU can transmit the time advance report including TA for the incoming satellite on 412. The WTRU can report the new TA at a configured offset for the transition time. The WTRU can report a new TA at a configured offset for the transition time and can indicate the time advance value for the new satellite. If the WTRU is not configured to pre-report the time advance on 408, or if the WTRU has transmitted a pre-report TA on 412, the WTRU can wait for the time of Petition 870250090286, dated 03 / 10 / 2025, p. 67 / 119 58 / 87 Satellite swap of the same PCI at 414. At the time of the satellite swap of the same PCI, determined at 414, the WTRU may apply the pre-calculated TA to the new satellite at 416. The WTRU may apply a new time advance at the time of the satellite swap or during that time. At 418, offsetThresholdTA may be configured. If offsetThresholdTA is configured (e.g., determined at 418), the WTRU may ignore a trigger to report a TA if that TA has been pre-reported. For example, at 420, the WTRU may determine that the TA has been successfully pre-reported and ignore the trigger at 422. If the TA has not been determined to have been pre-reported at 420, the WTRU may transmit a TAR at 424.

[0143] In examples, WTRU may perform one or more of the following actions to support time synchronization during the exchange of satellites on the same PCI. For example, WTRU may receive (e.g., via broadcast) the time and position of an incoming satellite at the time of the exchange of satellites on the same PCI. WTRU may receive a configuration to pre-report the time advance to the new satellite (pre-TAR). The configuration to pre-report the time advance may include one or more of the following: an enable / disable indication for pre-TAR reporting; an offset before the time of satellite exchange to report the pre-TAR; a time period to report the pre-TAR; and conditions for reporting the pre-TAR (e.g., a delta limit of the time advance to the previous satellite). WTRU may pre-calculate a time advance value for the incoming satellite using the position of the incoming satellite at the time of the PCI exchange.WTRU can transmit the pre-calculated TA value according to the pre-report configuration. In one or more cases, the pre-report configuration may explicitly indicate that the TA value is associated with the incoming satellite. WTRU can apply the pre-calculated time advance to the incoming satellite at the time of satellite switching on the same PCI. For cases where WTRU successfully reports the future time advance before satellite switching (e.g., WTRU receives an ACK for transmission that...). Petition 870250090286, dated 03 / 10 / 2025, pp. 68 / 119 59 / 87 carries the pre-TAR), WTRU ignores the trigger condition based on the offsetThresholdTA setting and the TAR trigger due to the satellite change. For cases where WTRU does not successfully report the future time advance before the satellite change, WTRU transmits a TAR at the time of the satellite change using the pre-calculated time advance. In one or more cases, WTRU transmits a UL TB using the pre-calculated time advance.

[0144] A WTRU can be configured for RLM for a same-PCI satellite exchange. In examples, for radio link monitoring (RLM), the WTRU can average cell measurements over time to obtain L3 cell quality. After a same-PCI satellite exchange, the cell quality measurements and / or information associated with the previous satellite may no longer be valid. This can result in a delay in detecting radio problems for an incoming satellite after a satellite exchange. The detection delay can be partially resolved by acquiring many new measurements quickly after the satellite exchange. Acquiring new measurements for an incoming satellite may require a measurement reconfiguration after the satellite exchange. This process can be time-consuming, for example, considering the WTRU-gNB RTT and the risk of RLF.The methods and modalities discussed here may be related to RLM enhancements to address these problems, for example, delayed detection. For instance, WTRU could reset the L3 measurement window at the time of satellite switching, apply a pre-configured measurement setting (e.g., with denser measurement objects), and / or filter coefficients to quickly assess new channel conditions.

[0145] The WTRU can be configured for measurement configuration after a satellite change within the same PCI. For example, the WTRU can receive measurement configuration information to apply at the time of a satellite change within the same PCI. The measurement configuration may include, for example, a Petition 870250090286, dated 03 / 10 / 2025, pp. 69 / 119 60 / 87 denser measurement object configuration to quickly acquire channel conditions for the incoming satellite. In some instances, the measurement configuration may replace all or part of the current measurement configuration. For example, WTRU may remove and / or reconfigure one or more aspects of the current configuration. In one or more cases, the new measurement configuration may add one or more additional measurement objects and / or identities to the current configuration. The new measurement configuration may modify (e.g., add / remove / reconfigure) other aspects of a measurement configuration, such as, but not limited to, reporting settings, quantity settings, measurement intervals, and the like.

[0146] The WTRU can receive and store measurement configuration(s) prior to a same-PCI satellite change. The measurement configuration(s) may optionally include a condition and / or indication that can be applied at the time of a same-PCI satellite change. For example, the WTRU may obtain the condition and / or indication, for example, through transmitted same-PCI satellite change assistance information. For example, the measurement configuration may include an explicit “activation time,” where the measurement configuration explicitly includes the time to apply the measurement configuration. The WTRU may apply the new measurement configuration based on the satisfaction of the condition (e.g., activation time / same-PCI change time).

[0147] The measurement configuration may include one or more expiration conditions. Expiration conditions may be referred to hereafter as “temporary measurement configuration”. An expiration condition may be time-based. For example, the time-based expiration condition may be an explicit time. The time-based expiration condition may correspond to the end of a time period initiated with the application of the measurement configuration. An expiration condition may be based on several measured reference signals (by Petition 870250090286, dated 03 / 10 / 2025, pp. 70 / 119 61 / 87 example, SSB / CSI-RS) and / or measurement objects. An expiration condition may be based on the determination that a stable channel quality has been established. For example, the expiration condition may be based on channel quality metrics such as, but not limited to, a measurement variance or standard deviation. An expiration condition may be based on the measurement value (e.g., the RSRP / RSRQ / SINR value) exceeding or falling below a threshold. An expiration condition may correspond to the activation of a second measurement setting.

[0148] In one or more instances, the WTRU may apply subsequent measurement configurations based on the satisfaction of the expiration condition, for example, a second configuration. The second configuration may have been received before the expiration condition was satisfied and may be stored by the WTRU. In instances, the second configuration may include an optional indication to apply the second configuration after the expiration of the first measurement configuration. In instances, the measurement configuration applied at the time of the same PCI satellite change may include an indication to store the previous measurement configuration. For example, the indication to store the previous measurement configuration may correspond to the configuration prior to the same PCI satellite change. In instances, the WTRU may revert to the previous measurement configuration based on the satisfaction of one or more expiration conditions.

[0149] WTRU can be configured for L3 filtering after a same-PCI satellite exchange. In examples, WTRU can reset the L3 measurement window based on a same-PCI satellite exchange. WTRU can reset the L3 measurement window to avoid detecting poor channel conditions due to, for example, averaging the incoming satellite measurements with the previous satellite measurements in a same-PCI satellite exchange. In examples, WTRU can discard one or more measurements associated with the previous satellite. For example, WTRU can consider channel and / or cell quality drifts (e.g., RSRP / RSRP / SINR), Petition 870250090286, dated 03 / 10 / 2025, pp. 71 / 119 62 / 87 including one or more measurements associated with the previous satellite, as invalid. An invalid measurement result may, for example, be discarded, not used for event evaluation, cell (re)selection or mobility decision, and / or not included in a measurement report.

[0150] The WTRU may receive a new or revised set of L3 filter coefficients. For example, the WTRU may receive the new or revised set of L3 filter coefficients to apply at the time of satellite changeover on the same PCI. In some cases, the filter coefficients may be provided and stored together with the measurement configuration(s) discussed herein. In some cases, the filter coefficients may be received independently. Similar to the temporary measurement configuration, the set of L3 filter coefficients may be associated with one or more of the following: an activation condition; an expiration condition; an indication to store the previous set of L3 filter coefficients to be used after expiration; and a second set of L3 filter coefficients to be applied after the expiration of the temporary L3 filter coefficients.

[0151] The WTRU can be configured to generate measurement reports before and / or after a same-PCI satellite exchange. To avoid sending measurement reports that will soon become invalid, or to avoid triggering a measurement report before channel quality acquisition for a new cell, the WTRU can suspend the sending of measurement reports on, or before, a same-PCI satellite exchange. In some cases, the WTRU may determine whether to suspend the sending of measurement reports before a satellite exchange based on an explicit network configuration. In other cases, the WTRU may determine whether to suspend the measurement report before a satellite exchange based on an explicit configuration transmitted in the system information (e.g., within the same-PCI satellite exchange assistance information). Petition 870250090286, dated 03 / 10 / 2025, pp. 72 / 119 63 / 87 of the configuration and / or suspension indication, WTRU may receive one or more of the following: conditions for initiating the suspension of the measurement report; conditions for resuming the measurement report; aspects of the measurement report to which the suspension applies (e.g., a subset of events, the report type, etc.); and exceptions to the suspension of the measurement report.

[0152] The WTRU determines when to start suspending the measurement report based on time. For example, the WTRU may suspend the measurement report at the time of the same PCI satellite change. In some cases, the start time may occur at an offset from the same PCI satellite change (e.g., 10s before the change) or at an explicit time (e.g., 10:30:02 UTC). In one or more cases, the network may optionally provide a period / duration during which the measurement report is suspended and may be maintained by the WTRU (e.g., by means of a prohibition timer).

[0153] In examples, the suspension may apply to one or more aspects of the measurement report. For example, the suspension may apply to event-triggered measurement reports, periodic measurement reports, or both. In examples, the suspension may apply to a subset of measurement events (e.g., A3-triggered measurement reports are suspended). In examples, the suspension may apply to a measurement report triggered by measurements performed on one or more measurement cells or objects / IDs. In some cases, the suspension may be overridden, for example, based on more than one event-based measurement trigger being met; based on the fulfillment of specific event-based triggers; and / or to support recovery procedures, such as radio link failure.

[0154] WTRU can resume measurement reporting based on one or more of the following examples. WTRU can resume measurement reporting, for example, based on the expiration of a temporary measurement setting. A Petition 870250090286, dated 03 / 10 / 2025, pp. 73 / 119 64 / 87 WTRU can resume measurement reporting, for example, based on the reconfiguration of a measurement setting. WTRU can resume measurement reporting, for example, based on the activation of a second measurement setting. WTRU can resume measurement reporting, for example, based on the satisfaction of a measurement-based condition (e.g., RSRP / RSRP / SINR exceeds or falls below some threshold). WTRU can resume measurement reporting, for example, after a period of time. WTRU can resume measurement reporting, for example, based on reaching an absolute time.

[0155] The WTRU can be configured with an association between the measurement report and ephemeris information. The WTRU can be configured with one or more ephemeris information for one or more satellites for a satellite exchange of the same PCI. The WTRU can perform L3 filtering of a measurement when the location of the associated satellite changes within a certain threshold. For example, when the change in the location of the associated satellite is greater than a threshold, the WTRU can reset the L3 filter and start L3 filtering of a measurement. In examples, the change in satellite location can be determined based on an ephemeris identity associated with a measurement. For example, the WTRU can be provided with one or more ephemerides, and each ephemeris can be associated with an identity. The identity can indicate which ephemeris-id is active, and / or which ephemeris-id will be active from which start time (e.g., associated with an input satellite).In one or more cases, the change in satellite location can be determined based on the area of ​​interest (AoD) of a beam on the satellite. For example, a reset of the L3 filter for a measurement can be triggered when the change in the area of ​​interest (e.g., service beam) is greater than a threshold. In one or more cases, the length of the L3 filter can be determined based on one or more ephemeris information parameters. For example, for cases where the satellite velocity is greater than a threshold, a first... Petition 870250090286, dated 03 / 10 / 2025, pp. 74 / 119 A 65 / 87 L3 filter length can be used. For cases where the satellite speed is below the limit, a second L3 filter length can be used, in which case the first L3 filter length can be shorter than the second L3 filter length.

[0156] In one or more instances, WTRU may reset a measurement window at the time of satellite change to prevent channel conditions for the new satellite from being averaged. WTRU may apply a new measurement configuration, such as a temporary configuration with a denser set of measurement objects. WTRU may filter coefficients after a satellite change to quickly acquire measurements and resynchronize with the new satellite. WTRU may temporarily suspend L3 event-based reporting with an offset before the satellite change (if channel conditions are about to change, there is no need to use resources to report on a cell that is no longer available) and / or after the satellite change (to allow time to properly measure the new channel conditions) to avoid unnecessary reporting.WTRU may, for example, temporarily suspend L3 event-based reporting with an offset before a satellite change, in cases where channel conditions are about to change and there is no need to use resources to report on a cell that is no longer available. WTRU may, for example, temporarily suspend L3 event-based reporting with an offset after a satellite change, to allow time to properly measure the new channel conditions and avoid unnecessary reporting.

[0157] Figure 5 is a flowchart illustrating an exemplary 500 radio link monitoring process during a same-PCI satellite exchange. The WTRU may perform one or more of the following procedures to support RLM during a same-PCI satellite exchange. In 502, the WTRU may receive assistance information about the incoming satellite. For example, the WTRU Petition 870250090286, dated 03 / 10 / 2025, pp. 75 / 119 66 / 87 can receive (e.g., via broadcast) the time when a satellite changeover of the same PCI will occur. In 504, the WTRU can receive configuration information for the RLM of the incoming satellite. The WTRU can receive a measurement configuration to be applied at the time of the satellite changeover of the same PCI. The measurement configuration may include, for example, but not limited to, one or more of the following: a temporary measurement configuration; expiration conditions for the temporary measurement configuration (e.g., number of RSs measured, duration, etc.); a second measurement configuration (e.g., to be applied after the temporary measurement configuration); L3 filter coefficients to be applied at the time of the satellite changeover; and a configuration to suspend the measurement report, including one or more of the following: a start time and duration.

[0158] The WTRU may determine whether to suspend the measurement report based on the configuration information in 506. For example, if configured to suspend the report before the same PCI satellite change, the WTRU may suspend the measurement report in 508. In 510, based on the received configuration information, the WTRU may wait for the start time of the same PCI satellite change. In 512 (for example, the time of the same PCI satellite change), the WTRU may perform one or more of the following actions based on the received configuration information: reset the L3 measurement window; apply temporary measurement configuration and / or filter coefficients; if still enabled, suspend the measurement report; and / or perform measurements on the input satellite.

[0159] In 514, the WTRU may determine that the conditions for resuming the measurement report have been met, and resume the measurement report in 518. In 516, the WTRU may determine whether the expiration conditions have been met. If no expiration condition for the temporary measurement configuration has been met, the WTRU may continue to perform measurements according to the temporary measurement configuration in 520. In 522, the WTRU may determine whether the conditions Petition 870250090286, dated 03 / 10 / 2025, p. 76 / 119 67 / 87 expiration conditions for the temporary measurement configuration have been met. For cases where the expiration conditions for the temporary measurement configuration are not met (or not configured), the WTRU may perform measurements according to the temporary measurement configuration and filter based on the updated L3 filter coefficients. In examples, the WTRU may receive a second measurement configuration on 524. For cases where the expiration conditions for the temporary measurement configuration are met, and the WTRU has received a second measurement configuration, the WTRU may apply the second measurement configuration on 526. For cases where the expiration conditions for the temporary measurement configuration are met and no second measurement configuration has been received, the WTRU may determine on 524 to revert to the previous measurement configuration (e.g., used before the satellite change).For example, in 528, WTRU may apply the previous measurement configuration (e.g., pre-satellite exchange). In one or more cases, WTRU may transmit a measurement report based on the new measurement configuration.

[0160] A WTRU can be configured for transmission management for a same-PCI satellite exchange. The WTRU's resynchronization time for a same-PCI satellite exchange can vary based on the WTRU's ability to determine, or pre-determine, aspects of synchronization (e.g., time advance, power control, etc.). During resynchronization, transmission and / or reception may be suspended. If the network is unaware of the WTRU's resynchronization time, there may be associated risks. For example, there may be a risk of additional latency and wasted transmission opportunities (e.g., if the resynchronization time is overestimated) or missed TX and / or RX opportunities (e.g., if the resynchronization time is underestimated). The methods and modalities discussed here may refer to support for proper configuration of the resynchronization interval. Petition 870250090286, dated 03 / 10 / 2025, pp. 77 / 119 68 / 87 and to WTRU's TX / RX management. For example, WTRU can provide capacity and / or assistance information related to resynchronization time to help configure the resynchronization interval and manage transmission during the resynchronization time.

[0161] The WTRU can be configured with assistance information for resynchronization of an interval configuration during a same-PCI satellite exchange. The WTRU can be configured with a “resynchronization interval” to facilitate resynchronization with an incoming satellite during a same-PCI satellite exchange. During a resynchronization interval, the WTRU can perform one or more resynchronization actions and / or procedures related to the incoming satellite. Resynchronization actions and / or procedures may include, for example, time advance calculation, Doppler compensation, power control, measurements / RLM, and / or beam management. During resynchronization, the WTRU may suspend (or is not expected to perform) DL reception and / or UL transmission. TX and / or RX suspension may include, for example, dynamic scheduling and pre-configured transmissions (e.g., configured grants, periodic CSI / SRS reports, etc.).

[0162] WTRU can provide assistance information (e.g., via CE MAC signaling and / or RRC) to support the proper configuration of a resynchronization interval. WTRU's assistance information for configuring the resynchronization interval may include, for example, one or more of the following: a time to perform the complete resynchronization; a time to perform one or more aspects of the resynchronization (e.g., time synchronization, UL power control); an ability to perform one or more aspects of the resynchronization before switching to a satellite of the same PCI; an estimated time for completion of the resynchronization (e.g., 10:32:30:00 UTC); a determination of whether WTRU can continue to receive / transmit during the time of Petition 870250090286, dated 03 / 10 / 2025, pp. 78 / 119 69 / 87 resynchronization; an earlier time at which the WTRU can resume transmitting / receiving (e.g., 10:32:40:00 UTC); measurements of neighboring cells (e.g., in the case of fallback or RLF); and / or a determination of whether one or more pre-configured transmissions overlap the resynchronization interval.

[0163] WTRU can provide assistance information (e.g., one or more of the above options) for setting the resynchronization interval. For example, WTRU can provide one or more of the above assistance information based on an explicit network request. In examples, WTRU can provide assistance information (e.g., one or more of the above options) for setting the resynchronization interval upon connection to, or resumption of connection to, the network (e.g., during WTRU capacity transfer). In examples, WTRU can provide assistance information (e.g., one or more of the above options) for setting the resynchronization interval within the WTRU assistance information (UAI) message.In examples, WTRU may provide assistance information (e.g., one or more of the options above) for setting the resynchronization interval within the “WTRU Information Response” message (e.g., based on a request or indication within the “WTRU Information Request” message sent over the network).

[0164] WTRU can determine the transmission of assistance information for the transmission of the resynchronization interval configuration based on configured conditions. For example, WTRU can determine to send assistance information based on the variation between the current state of one or more information fields and / or previously reported information. This variation, between the current state of one or more information fields and previously reported information, can be, for example, any amount of variation. In examples, WTRU can determine to send assistance information based Petition 870250090286, dated 03 / 10 / 2025, pp. 79 / 119 70 / 87 in the variation that exceeds a configured limit. In examples, the WTRU may determine to send the assistance information at a configured time (e.g., an absolute time, offset, time period) before the satellite change of the same PCI. To aid in reliability, the WTRU may transmit assistance information about HARQ processes when HARQ return / retransmission is configured (e.g., HARQ mode A).

[0165] The WTRU can receive configuration information for setting the resynchronization interval. The WTRU can perform actions during the resynchronization interval based on the received configuration information. In examples, the WTRU can receive the resynchronization interval via MAC CE and / or broadcast signaling. In examples, the resynchronization interval can be configured directly via RRC signaling.

[0166] Configuration information (e.g., resynchronization interval configuration information) may include one or more of the following: a start time for a resynchronization interval; an end time for a resynchronization interval; a duration for the resynchronization interval; a determination of whether to suspend one, more, or all UL transmissions / receptions during resynchronization (e.g., the network may indicate that one or more transmission / reception types, such as periodic scheduling, are suspended, but others, such as dynamic scheduling, are still enabled); a determination of which resynchronization procedures to perform before resynchronization (e.g., time advance pre-calculation / reporting); a determination of which aspects of resynchronization to perform during the resynchronization interval; and / or information and / or settings to perform one or more resynchronization procedures.Configuration information that includes a start time for a resynchronization interval can, for example, indicate that the resynchronization interval begins at the same time as... Petition 870250090286, dated 03 / 10 / 2025, pp. 80 / 119 71 / 87 satellite change on the same PCI or on some other occasion. For example, configuration information comprising a start time and a resynchronization interval duration may indicate the expected end time of the satellite change on the same PCI. For example, configuration information comprising a start time and an end time of the resynchronization interval may indicate the expected duration of the satellite change on the same PCI.

[0167] In some cases, WTRU may select, request, or suggest a resynchronization interval setting (for example, through the content of WTRU support information). The network may provide confirmation of the requested setting. In some cases, the network may pre-configure, broadcast, or indicate a set of candidate resynchronization interval settings. For example, the network may indicate a resynchronization interval setting by broadcasting and indicating an index corresponding to a setting.

[0168] WTRU may apply the resynchronization interval setting for same PCI satellite exchange. In instances, the resynchronization interval setting may be applied to one or more future satellite exchange events. In instances, WTRU may determine whether to store and / or maintain the current resynchronization interval setting (e.g., for use in subsequent same PCI satellite exchange events) based on an indication (e.g., an explicit indication) and / or setting. In instances, WTRU may apply the same interval setting to subsequent same PCI satellite exchange(s) until the setting is disabled, and / or a revised resynchronization interval setting is received.

[0169] In one or more cases, to support the resynchronization interval configuration, WTRU may send capacity and / or assistance information (e.g., estimated resynchronization time) prior to satellite switching. Before Petition 870250090286, dated 03 / 10 / 2025, pp. 81 / 119 72 / 87 of the same PCI satellite exchange, the WTRU may receive configuration information for a resynchronization interval. The configuration information for the resynchronization interval may include, for example, an indication of a start time, an end time, and / or a duration of the resynchronization interval. At the time of the same PCI satellite exchange, the WTRU may initiate the resynchronization interval. In examples, the WTRU may initiate the resynchronization interval at an offset from the same PCI satellite exchange (e.g., based on an indication in the configuration). While the interval is in progress, the WTRU may suspend TX and / or RX. In some cases, the WTRU may suspend pre-scheduled transmissions, such as, for example, configured leases, periodic CSI / SRS, and the like.WTRU can signal that synchronization has been completed by transmitting a UL signal, for example, among others, to an SR transmission in CG, PRACH, HARQ ACK and similar systems.

[0170] Figure 6 is a flowchart illustrating a process 600 of an exemplary transmission management and measurement interval configuration during a same-PCI satellite exchange. In one or more cases, the WTRU may perform one or more of the following steps to support transmission management and measurement interval configuration during a same-PCI satellite exchange. In 602, the WTRU may receive assistance information associated with the incoming satellite. For example, the WTRU may receive (e.g., via broadcast) the time at which a same-PCI satellite exchange will occur. Before the same-PCI satellite exchange, in 604, the WTRU may transmit assistance information.Support information may include one or more of the following: a resynchronization duration; the WTRU's ability to perform synchronization procedures (e.g., pre-calculation and time-advance reporting) prior to switching to a satellite on the same PCI; and / or determining when the WTRU can resume RX / TX after switching to a satellite on the same PCI. In 606, the WTRU may receive... Petition 870250090286, dated 03 / 10 / 2025, page 82 / 119 73 / 87 configuration information for satellite resynchronization. The configuration information for satellite resynchronization may include one or more of the following: configuration information for a resynchronization interval; conditions for declaring resynchronization failure; and / or features (e.g., a UL grant, dedicated RACH preamble, and the like) to indicate successful resynchronization.

[0171] Based on configuration and / or assistance information, on 608, the WTRU may wait for the satellite change to occur on the same PCI. On 610, at the time of the satellite change, the WTRU may initiate the resynchronization interval and suspend UL transmission and / or DL ​​reception. On 610, the WTRU may perform one or more resynchronization procedures for the incoming satellite (e.g., time advance calculation, Doppler compensation, power control, measurements). On 612, the WTRU may successfully resynchronize with the satellite. In case of successful resynchronization, the WTRU may resume DL reception and UL transmission on 616. If, on 620, the WTRU is configured to confirm or indicate successful resynchronization, the WTRU may transmit a successful resynchronization indication (e.g., using the provided resources). In 612, WTRU may not be successful in resynchronizing with the satellite.In 614, the WTRU may time out and determine that a resynchronization failed. If the timeout is not reached, the WTRU may continue to execute the resynchronization interval procedures in 610 based on the configuration. In 614, the WTRU may determine that a resynchronization failed, and if the timeout is reached, the WTRU may declare RLF and execute the associated recovery actions in 618.

[0172] In one or more cases, the WTRU can be configured for power control during a satellite change of the same PCI. The UL TX power required after a satellite change can vary significantly due to the large difference Petition 870250090286, dated 03 / 10 / 2025, p. 83 / 119 74 / 87 location between the previous satellite and the incoming satellite. If the WTRU relies on legacy closed-loop power control (i.e., the WTRU waits until the power control command is received after satellite switching) to adjust the UL transmit power, the WTRU may risk a failed transmission if the initial transmit power is too low or there is interference. Additionally, the WTRU may risk excessive power consumption if the initial transmit power is too high. The modalities described here refer to supporting power control during same-PC satellite switching. Furthermore, the modalities provide processes for the WTRU to adjust the power for the initial UL transmission to a new satellite based on the distance difference between the WTRU and the old and new satellites.

[0173] A WTRU can be configured for autonomous adjustment of transmission power during a satellite change on the same PCI. The WTRU can adjust the power to the incoming satellite after a satellite change on the same PCI. For example, the WTRU can adjust the power to the incoming satellite after a satellite change on the same PCI to avoid using too much or too little UL transmission power for an initial transmission. The WTRU's ability to autonomously adjust transmission power can be enabled / disabled by the network. For example, the network can enable / disable the WTRU's ability to autonomously adjust transmission power through a setting or RRC indication, such as, but not limited to, transmission signaling in SIB, MAC CE and / or DCI. The network can provide additional information / settings to calculate the initial UL TX power for the incoming satellite.Additional information / settings may include one or more of the following: a maximum delta value of the original TX power that can be adjusted autonomously by the WTRU; a maximum and / or minimum absolute TX power; a mapping between distance and power adjustment (e.g., 100 km = 1 dB); a mapping between distance and a scaling coefficient (e.g., 100). Petition 870250090286, dated 03 / 10 / 2025, pp. 84 / 119 75 / 87 km = 1.25 x); a determination of how to scale the transmission power (e.g., scale by a factor, add / subtract power); a determination of whether to scale the total transmission power or one or more components of the transmission power (e.g., path loss); corresponding support information on the transmission characteristics of the input satellite (e.g., antenna gain); and a free space coefficient to be applied to calculate the change in path loss.

[0174] In examples, the WTRU may autonomously adjust the transmission power. For example, the WTRU may autonomously adjust the transmission power based on the satisfaction of one or more conditions. For example, the WTRU may calculate the line-of-sight probability for the preceding satellite and the incoming satellite. If the line-of-sight probability (e.g., LOSPI) for the preceding satellite, the incoming satellite, or both satellites is below a configured threshold (e.g., 95%), the WTRU may not autonomously adjust the transmission power. In some cases, the network may provide a threshold to be used for LOS evaluation for the incoming satellite and the preceding satellite. In some cases, the network may provide a threshold for each satellite.

[0175] The WTRU can evaluate and / or determine the path loss of the incoming satellite during a same-PCI satellite exchange. For example, to support autonomous power adjustment of the WTRU, the WTRU can use assist information corresponding to the incoming satellite to determine the satellite's location at the time of the same-PCI satellite exchange. The assist information can be, for example, the explicit position of the satellite at the time of the same-PCI satellite exchange. For example, the WTRU can use ephemeris data from the incoming satellite to predict the satellite's location at the time of the same-PCI satellite exchange. The WTRU can obtain the WTRU's location (e.g., via GNSS) and calculate the distance between the WTRU and the incoming satellite. Petition 870250090286, dated 03 / 10 / 2025, page 85 / 119 76 / 87 moment of switching satellites of the same PCI. WTRU can use a similar set of procedures to determine the location of the previous satellite (e.g., at the time of switching satellites of the same PCI).

[0176] For cases where the WTRU is configured with a line-of-sight condition, the WTRU can calculate the line-of-sight probability (LOSPI) for the preceding satellite and / or for the incoming satellite. The calculation of the line-of-sight probability by the WTRU for one or both satellites may depend on whether or not a LOSPI evaluation is needed for one or both satellites. The WTRU can calculate the line-of-sight probability, for example, using assist information related to each satellite (e.g., location, ephemeris data, orbital characteristics) and / or reference signals (e.g., SSB, CSI-RS, PRS). The WTRU can receive and / or evaluate reference signals from the incoming satellite, for example, through measurements in one or more neighboring cells originating from the incoming satellite.

[0177] In some instances, the LOSPI may be evaluated by the network. In such cases, the WTRU may provide the WTRU location (e.g., current location or estimated location at the time of same PCI satellite change). The network may provide a LOSPI associated with one or both satellites (e.g., at the time of same PCI satellite change) to be used in the conditional evaluation. In one or more other instances, the LOSPI indication may be evaluated directly by the network. The evaluation of the LOSPI indication may be used to enable / disable the WTRU's autonomous power adjustment.

[0178] In some examples, the WTRU can be configured for autonomous UL TX power adjustment during a same-PCI satellite switch. At the time of the same-PCI satellite switch (or at some point between the same-PCI satellite switch and the initial transmission to the incoming satellite), the WTRU can determine whether autonomous transmission power adjustment is enabled and Petition 870250090286, dated 03 / 10 / 2025, pp. 86 / 119 77 / 87 configured. If any necessary or configured conditions are met (e.g., based on line-of-sight probability), WTRU may adjust the transmission power for the initial transmission. If WTRU's autonomous power adjustment is disabled / deactivated, or if autonomous power adjustment is enabled and one or more conditions are not met, WTRU may use the transmission power of the previous satellite for the initial transmission to the incoming satellite.

[0179] The autonomous power adjustment of the WTRU may be based on one or more of the following: the distance(s) between the WTRU and the incoming satellite and / or the previous satellite; the delta distance between the WTRU-previous satellite and the WTRU-incoming satellite; a determination of how the WTRU adjusts the power (e.g., whether the WTRU adds / subtracts power and / or applies a scaling coefficient); a mapping or relationship between the distances and the determination of how the power is adjusted; maximum absolute values ​​(or delta) of the original power that can be modified by the WTRU; transmission characteristics of the incoming satellite (e.g., antenna gain); and / or a total transmission power by the WTRU.

[0180] In one or more cases, the WTRU may calculate the delta distance between the WTRU and the incoming satellite and the previous satellite. Applying a delta-to-delta-dB distance mapping provided by the network, the WTRU may determine an amount (e.g., in dB) to adjust the power. The WTRU may adjust the total transmission power or may adjust one or more components of the power calculation (e.g., the path loss value) based on the configuration. For cases where the delta power adjustment exceeds a maximum / minimum allowed power adjustment, the WTRU may select the limit value. For cases where the adjusted value exceeds the maximum total transmission power allowed by the WTRU, the WTRU may select the maximum allowed transmission power. The WTRU may apply the scaled power for the initial transmission to the satellite of Petition 870250090286, dated 03 / 10 / 2025, p. 87 / 119 78 / 87 entry after switching to a satellite of the same PCI. In one or more cases, WTRU may use the delta distance and apply a free-space propagation loss coefficient to determine the change in path loss between the entry satellite and the previous satellite. WTRU may adjust the transmission power accordingly to compensate for the adjusted path loss.

[0181] In one or more cases, the WTRU may indicate WTRU autonomous power adjustment characteristics based on an indication or configuration. For example, the WTRU may indicate (e.g., via MAC CE or RRC signaling) a determination of how much the WTRU has adjusted the UL TX power and / or the UL TX power level (e.g., within the first transmission). In some cases, the configuration / request may include features (e.g., a dynamic UL grant) to send the indication. In other cases, the configuration / request may instruct the WTRU to include the indication in the initial transmission to the incoming satellite.

[0182] In one or more cases, WTRU may adjust the UL transmission power for the initial transmission to the new satellite based on the delta distance from the previous satellite. The UL transmission power may be further controlled by the network configuration. For example, the network configuration may enable / disable the UL transmission power. In another example, the network configuration may provide the maximum allowed delta scaling for the UL transmission. In one or more cases, the UL transmission power may be subject to conditions, for example, but not limited to, the probability that the line of sight to the LOSPI of the previous and current satellite is above a configured limit.

[0183] Figure 7 is a flowchart illustrating an exemplary power control process during a satellite exchange on the same PCI. In one or more cases, the WTRU may perform one or more of the following steps to support power control during a satellite exchange on the same PCI. In 702, the WTRU may receive (e.g., via broadcast) assistance information for the preceding satellite. Petition 870250090286, dated 03 / 10 / 2025, pp. 88 / 119 79 / 87 and the incoming satellite. Assistance information may include one or more of the following: ephemeris data of the currently in-service satellite; a time of the same PCI satellite change; and / or a position of the incoming satellite at the time of the same PCI satellite change. On 704, the WTRU may receive configuration information to calculate the UL TX power for the incoming satellite. The configuration may include one or more of the following: an enable / disable indication; a maximum delta value by which the original TX power can be autonomously adjusted by the WTRU; a minimum line-of-sight probability limit for the preceding satellite and the incoming satellite; and / or a determination of whether to indicate how much the WTRU has adjusted the UL TX power and / or the UL TX power level (e.g., within the first transmission). The WTRU may obtain updated information from the WTRU (e.g., via GNSS).

[0184] On 706, the WTRU can calculate one or more of the following: the WTRU satellite distance to each satellite at the time of same PCI satellite exchange (e.g., using satellite assistance information); and / or the line-of-sight probability for each satellite. The WTRU can acquire updated WTRU information (e.g., via GNSS). On 708, the WTRU can identify the start of the same PCI satellite exchange. On 710, if the WTRU's autonomous UL TX power adjustment is not enabled, the WTRU can perform any UL transmissions using the original UL TX power on 712. On 710, if the WTRU's autonomous UL TX power adjustment is enabled, the WTRU can adjust the UL TX power for the incoming satellite.In 714, for cases where WTRU's autonomous UL TX power adjustment is enabled and line-of-sight conditions to the preceding and incoming satellites have been met, WTRU can adjust the UL TX power (e.g., proportionally to the relative distance between the two satellites). WTRU can transmit an initial UL transmission with the adjusted UL TX power. WTRU may include delta adjustment and / or current UL TX power in the initial transmission, if applicable. Petition 870250090286, dated 03 / 10 / 2025, pp. 89 / 119 80 / 87 configured by NW. When switching between satellites on the same PCI, in cases where the WTRU's autonomous UL TX power adjustment is not enabled and / or the line-of-sight conditions for the previous satellite and the incoming satellite have been met, the WTRU transmits an initial UL transmission with the UL TX power used for transmission to the previous satellite. The WTRU can be configured to indicate the power setting determined in 716. If the WTRU is not configured to indicate the setting, subsequent UL transmissions can be performed using the power set in 718. If the WTRU is configured to indicate the setting, subsequent UL transmissions can be performed using the power set in 720, and the WTRU can indicate the power setting (e.g., during transmission).

[0185] A WTRU can be configured to perform beam management during a same-PCI satellite exchange. The in-service satellite and the incoming satellite during a same-PCI satellite exchange may be in very different locations. Thus, the WTRU may need to reorient its UL TX beam after the satellite exchange. In one or more cases, it may be necessary to resort to legacy methods to reorient the spatial filters until after the satellite exchange event. However, reorienting the spatial filters after the satellite exchange event may increase the resynchronization time and therefore service interruption. The modalities described here refer to support for proper measurement interval configuration and TX / RX management of the WTRU.

[0186] The WTRU can measure reference signals from the incoming satellite (e.g., some SSB / CSI-RS from a neighboring cell) to understand how to reorient the spatial filters when a new satellite takes over coverage. The WTRU can receive an indication / configuration of the reference signal in a first time period (i.e., pre-switch) in QCL with a second reference signal in a second time period (i.e., post-switch) to link the measurements between the cells. Petition 870250090286, dated 03 / 10 / 2025, pp. 90 / 119 81 / 87

[0187] In one or more cases, the WTRU may be configured with an indication and / or configuration of a pre / post same-PCI satellite exchange QCL relationship. The WTRU may be provided with a QCL relationship between one or more reference signals originating from the input satellite and reference signals associated with the service cell. The relationship between one or more reference signals originating from the input satellite and reference signals associated with the service cell may be time-dependent, wherein the WTRU assumes that the relationship between the reference signals (e.g., from neighboring cells originating from the input satellite) is valid after the same-PCI satellite exchange (e.g., when the current service cell is served by the same satellite as the neighboring cells indicated in the mapping relationship).

[0188] In examples, the WTRU may receive an indication and / or configuration that a first reference signal from a first time period (e.g., a reference signal from a neighboring cell originating from the incoming satellite before the same PCI satellite change) is QCL with a second reference signal from a second time period (e.g., a reference signal in the current service cell after the same PCI satellite change). The WTRU may link measurements made in the first time period to support resynchronization (e.g., spatial filter determination, path loss estimation, etc.) after the same PCI satellite change. The configuration of the first or second reference signal may include, for example, the identity of an SSB, including at least the physical cell identity (PCI) and the SSB index, and / or the identity of a CSI-RS resource.For cases where the second reference signal is an SSB, WTRU can determine that the corresponding PCI is the one corresponding to the service cell.

[0189] In examples, WTRU can be configured for beam management at the time of satellite switching of the same PCI. Before satellite switching of Petition 870250090286, dated 03 / 10 / 2025, pp. 91 / 119 82 / 87 same PCI, WTRU can perform measurements on reference signals originating from the input satellite indicated in the mapping relationship. WTRU can use these measurements to determine transmission aspects to be applied to the service cell after switching to a same PCI satellite, such as spatial filtering, L3 measurements, and DL path loss. At the time of switching to a same PCI satellite, WTRU can link measurements of these reference signals to the current service cell. WTRU can apply the transmission aspects to subsequent UL transmissions to the input satellite.

[0190] In examples, the WTRU can be configured to filter samples before and after PCI exchange for L3 reporting. In another example, the WTRU can use the most recent filtered Layer 3 measurement result from the first reference signal of a first time period (e.g., before a same PCI satellite exchange time) to combine the most recent filtered Layer 3 measurement result with the first measurement result of the second reference signal of a second time period (e.g., after a same PCI satellite exchange time) and obtain an updated filtered measurement result applicable to the second reference signal. The WTRU can use the updated filtered measurement result for further Layer 3 filtering with subsequent measurement results, measurement reporting, and RSRP determination for uplink path loss and power estimation.

[0191] The WTRU can be configured to determine a spatial RX beam based on the location of an in-service satellite. In one or more cases, for a given TCI state (e.g., beam reference signal to indicate the RX beam in the WTRU), the WTRU can use, determine, or select an RX beam based on the satellite's location. For example, the WTRU can use a first RX beam when an in-service satellite is in a first location, and the WTRU can use a second RX beam when an in-service satellite is in a second location. Petition 870250090286, dated 03 / 10 / 2025, pp. 92 / 119 83 / 87 location and so on. WTRU can estimate the satellite location based on ephemeris information (e.g., a first type of ephemeris information and / or a second type of ephemeris information). In one or more cases, WTRU can reset the L3 filter of a measurement when an RX beam is changed. In one or more cases, WTRU can report RX beam information to gNB when the RX beam is changed.

[0192] The WTRU can reorient the spatial filter(s) using a reference signal from a neighboring cell (e.g., SSB / CSI-RS) originating from the satellite that will eventually take over the PCI. To support this mapping, the WTRU can receive an indication / configuration that a reference signal in a first time period (i.e., before the satellite change) is QCL with a second reference signal in a second time period (i.e., after the satellite change). Thus, everything measured from one satellite can be linked to a second input satellite.

[0193] Figure 8 is a flowchart illustrating an exemplary beam management process during a same-PCI satellite exchange. In one or more cases, the WTRU may perform one or more of the following steps to support beam management during a same-PCI satellite exchange. In 802, the WTRU may receive (e.g., via broadcast) assistance information about the incoming satellite. The assistance information may comprise, for example, a timing indication of the same-PCI satellite exchange, the location of the incoming satellite, and / or ephemeris data of the incoming satellite. In 804, the WTRU may receive an indication / configuration that a reference signal in a first time period (e.g., before the satellite exchange) is nearly colocalized (QCL) with a second reference signal in a second time period (e.g., after the satellite exchange).

[0194] In 806, WTRU can measure reference signals originating from the satellite. Petition 870250090286, dated 03 / 10 / 2025, pp. 93 / 119 84 / 87 input during the first time period. In 808, the WTRU can calculate, based on the information obtained in 806, the beam direction and / or the DL path loss to the input satellite using reference signals from the first time period.

[0195] At 810, at the time of satellite switching with the same PCI, the WTRU can perform actions associated with satellite switching. At 812, based on the mapping configuration and the reference signal measurements from the first time period, the WTRU can reorient the WTRU's UL transmission beam (e.g., by applying an updated spatial filter) and adjust the transmission power for the initial UL transmission (e.g., based on the DL trajectory loss measured in the first period). The WTRU can link the measurements from the first time period to the measurements from the second time period. At 814, the WTRU can perform a UL transmission using the newly applied spatial filter and the adjusted UL power.WTRU can transmit the same PCI satellite exchange confirmation (e.g., using pre-configured MAC CE or PUCCH) using the determined UL transmission beam and the transmission power calculated based on the RSRP of the reference signal during the first time period.

[0196] In one or more cases, the WTRU may be configured with an acknowledgment of a completed resynchronization after a same PCI exchange. The WTRU may be configured / requested / indicated to provide an indication or confirmation that the WTRU has regained synchronization with the incoming satellite after a same PCI satellite exchange. The resynchronization indication may be an explicit indication confirming that the WTRU has regained full synchronization or may indicate that one or more aspects of synchronization have been regained. In one or more cases, the acknowledgment may not refer to an aspect of resynchronization but may indicate that the WTRU can transmit and receive data from the incoming satellite. In one or more other cases, the acknowledgment may be Petition 870250090286, dated 03 / 10 / 2025, pp. 94 / 119 85 / 87 implicit, for example, based on the successful transmission of the WTRU to an incoming satellite at some point after a satellite exchange of the same PCI.

[0197] In one or more cases, the WTRU may send the indication by means of, for example, but not limited to, MAC CE, RRC signaling, UCI, RACH signaling (MSA, MSG3, MSG5) and / or a PUSCH transmission. The WTRU may be provided with dedicated resources (e.g., a UL grant, dedicated RACH preamble, specific RNTIs) to indicate successful resynchronization, whereby, upon receiving a transmission using the dedicated resources, the network may presume that resynchronization was successful. The WTRU may include additional assistance information relating to one or more resynchronization procedures. The additional assistance information may include one or more of the following: time advance, power information, measurement results and / or beam information (e.g., as described herein).

[0198] In one or more cases, WTRU may send the first transmission to an incoming satellite after a satellite exchange of the same PCI in reliably configured HARQ processes (e.g., in HARQ processes configured with HARQ Mode A). In some cases, WTRU may expect the first reception from an incoming satellite to be received in a HARQ process with HARQ return configured.

[0199] In one or more cases, the WTRU may be configured with a resynchronization failure statement. For cases where the WTRU fails to complete resynchronization with an incoming satellite, the WTRU may declare “resynchronization failure”. For example, if the WTRU has not recovered one or more aspects of synchronization (e.g., time, frequency, power, measurements) by the end of the resynchronization interval (or some other expiration time), the WTRU may declare resynchronization failure. In another example, if the WTRU has a scheduled DL reception or UL transmission to the satellite of Petition 870250090286, dated 03 / 10 / 2025, pp. 95 / 119 If an entry (e.g., after the resynchronization interval) that the WTRU cannot perform because it has not completed resynchronization, the WTRU may declare a resynchronization failure.

[0200] WTRU may declare a resynchronization failure before switching to a satellite with the same PCI. For example, in cases where WTRU was unable to receive the necessary information to perform resynchronization with the incoming satellite, WTRU may declare a resynchronization failure before switching to a satellite with the same PCI. In another example, if the connection to the previous satellite is still in progress, WTRU may report a resynchronization failure before switching to a satellite with the same PCI, including one or more procedures that WTRU is unable to complete and / or information that WTRU is unable to obtain.

[0201] In one or more cases, WTRU may declare a partial resynchronization failure if one or more aspects of the resynchronization are unsuccessful. For cases of partial resynchronization failure, WTRU may still resume RX / TX to the incoming satellite, however, with a less than ideal configuration (e.g., incorrect power). WTRU may indicate that one or more aspects cannot be completed or request the information necessary to correct the problem.

[0202] After a resynchronization failure (or partial resynchronization failure) declaration, WTRU may perform one or more recovery actions. One or more recovery actions may include, for example, but not limited to: beam failure recovery (BFR); radio link failure (RLF); time advance precompensation; conditional transfer; cell reselection; random access; applying an alternative measurement configuration; resuming measurement reporting; and / or transitioning to INACTIVE / IDLE RRC.

[0203] Although the resources and elements are described above in specific combinations, one skilled in the art will understand that each resource or Petition 870250090286, dated 03 / 10 / 2025, pp. 96 / 119 The 87 / 87 element can be used in isolation or in any combination with the other resources and elements. Furthermore, the methods described herein can be implemented in a computer program, software, or firmware embedded in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROMs and digital versatile discs (DVDs).A processor, in conjunction with software, can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. Petition 870250090286, dated 03 / 10 / 2025, pp. 97 / 119

Claims

1 / 4 CLAIMS 1. Wireless transmit / receive unit (WTRU), CHARACTERIZED in that it comprises: a processor configured to: receive configuration information indicating a time for a same-PCI satellite exchange from a first satellite to a second satellite, wherein the configuration information comprises an indication of a start time and an indication of an end time for the same-PCI satellite exchange from the first satellite to the second satellite; and execute the same-PCI satellite exchange to the second satellite based on the configuration information indicating the time for the same-PCI satellite exchange.

2. WTRU, according to claim 1, CHARACTERIZED in that configuration information is received via broadcast signaling.

3. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to initiate a resynchronization interval in response to the exchange of a satellite on the same PCI.

4. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to suspend uplink transmission with the first satellite in response to a satellite change on the same PCI.

5. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to perform one or more resynchronization procedures in response to satellite switching on the same PCI.

6. WTRU, according to claim 5, CHARACTERIZED in that one or more resynchronization procedures comprise a time advance calculation, a Doppler compensation, a power control procedure, or a measurement procedure. Petition 870250090286, dated 10 / 03 / 2025, pp. 116 / 119 2 / 4 7. WTRU, according to claim 1, CHARACTERIZED in that the processor is further configured to, in response to the exchange of satellites on the same PCI, initiate a resynchronization interval, suspend uplink transmission and downlink reception, and execute one or more resynchronization procedures, wherein one or more resynchronization procedures comprise a time advance calculation, a Doppler compensation, a power control procedure, and a measurement procedure.

8. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to: transmit assistance information related to a resynchronization time to assist in setting the measurement interval, wherein the assistance information comprises a resynchronization duration, an indication that the WTRU can perform a synchronization procedure before switching to a satellite of the same PCI, and an indication of a time at which the WTRU can resume communication with the second satellite after switching to a satellite of the same PCI.

9. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to receive a configuration for satellite resynchronization with the second satellite, the configuration for satellite resynchronization comprising a resynchronization interval configuration, a condition for declaring resynchronization failure, or resources to indicate successful resynchronization with the second satellite.

10. WTRU, according to claim 1, CHARACTERIZED in that the processor is additionally configured to transmit a successful resynchronization indication in response to successful resynchronization with the second satellite.

11. Method implemented in a wireless transmit / receive unit (WTRU) for transmission management during a satellite exchange of the same physical cell identity (PCI), the method CHARACTERIZED by the fact that it comprises: receiving configuration information indicating a time for a same PCI satellite exchange from a first satellite to a second satellite, wherein the configuration information comprises an indication of a start time and an indication of an end time for the same PCI satellite exchange from the first satellite to the second satellite; and executing the same PCI satellite exchange to the second satellite based on the configuration information indicating the time for the same PCI satellite exchange.

12. Method according to claim 11, CHARACTERIZED in that the configuration information is received via broadcast signaling.

13. Method according to claim 11, CHARACTERIZED in that it further comprises, in response to the exchange of satellites of the same PCI, initiating a resynchronization interval.

14. Method according to claim 11, CHARACTERIZED in that it further comprises, in response to a satellite change of the same PCI, suspending the uplink transmission with the first satellite.

15. Method according to claim 11, CHARACTERIZED in that it further comprises, in response to the exchange of satellites of the same PCI, performing one or more resynchronization procedures.

16. Method according to claim 15, CHARACTERIZED in that one or more resynchronization procedures comprise a time advance calculation, a Doppler compensation, a power control procedure, or a measurement procedure.

17. Method, according to claim 11, CHARACTERIZED in that it further comprises, in response to the exchange of a satellite of the same PCI, Petition 870250090286, dated 03 / 10 / 2025, pp. 118 / 119 4 / 4, initiating a resynchronization interval, suspending uplink transmission and downlink reception, and executing one or more resynchronization procedures, wherein the one or more resynchronization procedures comprise a time advance calculation, a Doppler compensation, a power control procedure, and a measurement procedure.

18. Method, according to claim 11, CHARACTERIZED in that it further comprises transmitting assistance information related to a resynchronization time to assist in setting the measurement interval, wherein the assistance information comprises a resynchronization duration, an indication that the WTRU can perform a synchronization procedure before switching to a satellite of the same PCI, and an indication of a time at which the WTRU can resume communication with the second satellite after switching to a satellite of the same PCI.

19. A method according to claim 11, characterized in that it further comprises receiving a configuration for satellite resynchronization with the second satellite, the configuration for satellite resynchronization comprising a resynchronization interval configuration, a condition for declaring resynchronization failure, or features for indicating successful resynchronization with the second satellite.

20. Method according to claim 11, CHARACTERIZED in that it further comprises, in response to successful resynchronization with the second satellite, transmitting an indication of successful resynchronization. Petition 870250090286, dated 03 / 10 / 2025, pp. 119 / 119

Images