Power sharing impact estimation and conditional DL coverage enhancements

Abstract

A wireless transmit / receive unit (WTRU) includes a processor configured to receive power sharing assistance information and non-terrestrial network (NTN) assistance information. The power sharing assistance information may include an indication of an upcoming power saving state of the NTN device. The processor may determine location information associated with the WTRU. The processor may send a report indicating that the WTRU may be affected by the power saving state based on the power sharing assistance information, the NTN assistance information, and / or the location information.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Application No. 63 / 585,354, filed September 26, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0002] Non-terrestrial networks (NTNs) facilitate the deployment of wireless networks in areas where terrestrial antennas may be impractical (e.g., due to geography or cost). NTN deployments support basic conversations and text communication anywhere in the world. Furthermore, future versions coupled with the proliferation of next-generation low-Earth orbit satellites could enable enhanced services such as web browsing.

[0003] A basic NTN comprises an airborne or space-based bearer platform that transmits signals from a terrestrial-based gNB to a radio transmit / receive unit (WTRU) and vice versa via a gateway (GW). The NTN supports WTRUs of power level 3 with omnidirectional antennas and linear polarization, or Very Small Aperture Antenna (VSAT) terminals with directional antennas and circular polarization. It is assumed that all NTN WTRUs can have Global Navigation Satellite System (GNSS) capability. Summary of the Invention

[0004] The Wireless Transmit / Receive Unit (WTRU) may include a processor. The processor may be configured to receive power-sharing assistance information and non-terrestrial network (NTN) assistance information. The power-sharing assistance information may include, for example, an indication of an upcoming power-saving state for an NTN device. The processor may determine location information associated with the WTRU. The processor may transmit a report indicating that the WTRU may be affected by a power-saving state, based on the power-sharing assistance information, NTN assistance information, and / or location information.

[0005] Power sharing auxiliary information may be one or more of the following: the expected impact of the power sharing status, an indication of the area affected by the power sharing status, the start time of the power sharing status, or the duration of the power sharing status.

[0006] The report may include, for example, an estimated duration of the expected impact of power sharing status, downlink (DL) coverage reduction, or an indication of one or more of whether the WTRU will maintain connectivity with the NTN device.

[0007] Indications of areas affected by power-sharing status may include, for example, explicit area descriptions via reference points and radii or indexes of Synchronization Signal Blocks (SSBs). The anticipated effects of power-sharing status may include, for example, a percentage reduction in radiated power density.

[0008] Power sharing ancillary information may include, for example, flags enabling pre-reporting and / or indications for including additional ancillary information in the report. Additional ancillary information may include, for example, the predicted magnitude of DL coverage loss, information required for access to non-terrestrial cells, and / or power sharing ancillary information for one or more non-terrestrial cells currently serving the area.

[0009] The processor can be configured to receive one or more modified modulation and coding schemes (MCS). The processor can be configured to use the modified MCS to receive downlink (DL).

[0010] The processor can be configured to receive one or more modified downlink (DL) coverage enhancements. The processor can be configured to receive DL transmissions using DL coverage enhancements.

[0011] The processor can be configured to pause transmissions to NTN devices during the duration of a power-saving state.

[0012] The processor can be configured to revert to the original DL overlay configuration when the power sharing state is complete.

[0013] NTN auxiliary information may include one or more of the following: cell reference point, cell radius, or satellite ephemeris. NTN auxiliary information can be obtained via the System Information Block (SIB).

[0014] The WTRU can be configured to perform methods including one or more of the following steps. The method may include receiving power-sharing assistance information and non-terrestrial network (NTN) assistance information. The power-sharing assistance information may include, for example, an indication of an upcoming power-saving state for NTN equipment. The method may include determining location information associated with the WTRU. The method may include sending a report indicating that the WTRU may be affected by a power-saving state based on the power-sharing assistance information, NTN assistance information, and / or location information.

[0015] Power sharing auxiliary information may be one or more of the following: the expected impact of the power sharing status, an indication of the area affected by the power sharing status, the start time of the power sharing status, or the duration of the power sharing status.

[0016] The report may include, for example, an estimated duration of the expected impact of power sharing status, downlink (DL) coverage reduction, or an indication of whether the WTRU will remain connected to one or more of the NTN devices.

[0017] Indications of areas affected by power-sharing status may include, for example, explicit area descriptions via reference points and radii or indexes of Synchronization Signal Blocks (SSBs). The anticipated effects of power-sharing status may include, for example, a percentage reduction in radiated power density.

[0018] Power sharing ancillary information may include, for example, flags enabling pre-reporting and / or indications for including additional ancillary information in the report. Additional ancillary information may include, for example, the predicted magnitude of DL coverage loss, information required for access to non-terrestrial cells, and / or power sharing ancillary information for one or more non-terrestrial cells currently serving the area.

[0019] The method may include receiving one or more modified modulation and coding schemes (MCS). The method may include using the modified MCS to receive downlink (DL).

[0020] The method may include receiving one or more modified downlink (DL) coverage enhancements. The method may include using DL coverage enhancements to receive DL transmissions.

[0021] This method may include suspending transmissions to the NTN device during the duration of a power-saving state.

[0022] This method may include restoring to the original DL coverage configuration upon completion of the power sharing state.

[0023] NTN auxiliary information may include one or more of the following: cell reference point, cell radius, or satellite ephemeris. NTN auxiliary information can be obtained via the System Information Block (SIB). Attached Figure Description

[0024] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments can be implemented.

[0025] Figure 1B The illustration shows that, according to the embodiment, it is possible to... Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0026] Figure 1C The illustration shows that, according to the embodiment, it is possible to... Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system.

[0027] Figure 1D The illustration shows that, according to the embodiment, it is possible to... Figure 1A The diagram shows another example RAN and another example CN used in the communication system.

[0028] Figure 2 This is a system diagram illustrating the different interfaces in a non-terrestrial network (NTN).

[0029] Figure 3 This is a diagram depicting an example beam power sharing scenario in an NTN.

[0030] Figure 4 This is a diagram illustrating example network auxiliary information that provides current and future power-sharing states with associated applicable timeframes.

[0031] Figure 5 This is a system diagram illustrating an example of power sharing impact estimation and conditional downlink (DL) coverage enhancement.

[0032] Figure 6 This is a diagram illustrating the post-assessment and reporting of the impact of example power sharing.

[0033] Figure 7 This is a system diagram illustrating the impact of power sharing on idle / inactive WTRUs in an example network (NW) polling.

[0034] Figure 8 This is a diagram illustrating an example pre-configuration process under power sharing. Detailed Implementation

[0035] Figure 1A This is a schematic diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 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-Tail Unique Word DFT Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0036] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as WTRUs.

[0037] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, eNode B, home node B, home eNode B, gNB, NR node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0038] 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 base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of radio services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further 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 transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0039] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0040] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0041] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0042] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using a new radio (NR).

[0043] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can jointly implement LTE radio access and NR radio access, for example, using the dual connectivity (DC) principle. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0044] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0045] For example, Figure 1ABase station 114b can be a wireless router, home node B, home eNodeB, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0046] RAN 104 / 113 can communicate with CN 106 / 115, which 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 WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0047] CN 106 / 115 can also serve as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0049] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripheral devices 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0050] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable 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. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

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

[0052] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmit / receive elements 122. More specifically, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals on air interface 116.

[0053] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Thus, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0054] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable 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 user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

[0055] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device that powers the WTRU 102. For example, the power supply 134 may 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, etc.

[0056] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (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 should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0057] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, such as gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors.

[0058] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0059] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0060] RAN 104 may include eNode-B 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-B 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRU 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-B 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

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

[0062] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0063] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0064] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0065] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0066] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0067] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0068] In a representative embodiment, another network 112 may be a WLAN.

[0069] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as the "ad-hoc" communication mode.

[0070] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0071] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0072] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0073] 802.11af and 802.11ah support operating modes below 1 GHz. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support metering-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only) certain and / or limited bandwidths. MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

[0074] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, 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 Sense and / or Network Assignment Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy, even if most of the available band remains idle and can be available.

[0075] In the United States, the available frequency band for 802.11ah is from 902 MHz to 928 MHz. In South Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0076] Figure 1D This diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0077] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0078] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a variable number of OFDM symbols and / or a continuously variable absolute time).

[0079] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without accessing other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN such as eNode-Bs 160a, 160b, and 160c. For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can act as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

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

[0081] Figure 1DThe CN 115 shown 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 each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0082] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the service types used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, and / or so on. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as WiFi.

[0083] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0084] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This N3 interface provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

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

[0086] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0087] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device and / or use over-the-air wireless communication to perform tests for testing purposes.

[0088] One or more simulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to implement the testing of one or more components. One or more simulation devices may be test devices. Simulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0089] Non-terrestrial networks (NTNs) facilitate the deployment of wireless networks in areas where terrestrial antennas may be impractical (e.g., due to geography or cost). Current standard NTN deployments support basic conversations and text communication anywhere in the world. Furthermore, future versions coupled with the proliferation of next-generation low-Earth orbit satellites could enable enhanced services such as web browsing.

[0090] A basic NTN consists of an airborne or space-based bearer platform that transmits signals from a land-based gNB to a WTRU via a gateway (GW) and vice versa. NTN supports power class 3 UEs with omnidirectional antennas and linear polarization, or Very Small Aperture Antenna (VSAT) terminals with directional antennas and circular polarization.

[0091] It enables power sharing impact estimation and conditional DL coverage enhancement. The WTRU can calculate whether and / or when it might be affected by future NW power-saving states using network-aided information and WTRU characteristics (e.g., WTRU location, speed, etc.). The WTRU can report the period of impact to the NW and the estimated extent of the impact. The WTRU can be pre-configured with DL coverage enhancement to be applied after the WTRU enters an area and / or time that may be affected by DL coverage changes.

[0092] It enables post-power-sharing impact assessment and reporting. The WTRU can measure RSRP for a period of time before and / or after the power-sharing state is activated. The WTRU can be configured with new events, whereby the WTRU can report RSRP measurement results if the DL coverage decreases from time T1 (pre-power-sharing state) to T2 (post-power-sharing state).

[0093] Network polling for RRC_IDLE / INACTIVE WTRUs is possible. Idle / inactive WTRUs can be polled to provide feedback on anticipated power-sharing state activation by receiving paging messages. WTRUs can receive power-sharing state ancillary information and determine whether they will be affected. WTRUs can determine specific preambles and reporting conditions to indicate the severity of the impact (e.g., preamble A: WTRU anticipates complete loss of coverage and / or preamble B: WTRU anticipates being affected). The network can respond with a Random Access Response (RAR) and / or UL Authorization, requesting additional ancillary information (e.g., duration of coverage impact and / or predicted magnitude of DL coverage loss).

[0094] Pre-configuration processing under beam power sharing can be implemented. The WTRU can receive power sharing status auxiliary information from neighboring cells and / or satellites. The WTRU can determine whether one or more neighboring cells affected by the power sharing decision are Layer 1 / L2 (L1 / L2) triggered mobility (LTM) and / or conditional handover (CHO) candidates. The WTRU can suspend (and / or offset-triggered) the configuration of LTM and / or CHO candidates during the duration of the power-saving state to avoid handover to cells that will experience poor coverage.

[0095] Airborne or space-based carrier platforms are classified according to their orbits. Current standardization focuses on Low Earth Orbit (LEO) satellites with an altitude range of 300–1500 km and Geostationary Orbit (GEO) satellites with an altitude of 35,786 km. Other platform classifications, such as Medium Earth Orbit (MEO) satellites, are defined with an altitude range of 7,000–25,000 km, and High Altitude Platform Stations (HAPS) with an altitude of 8–50 km are assumed to be implicitly supported. Satellite platforms are further classified as having “transparent” or “regenerative” payloads. Transparent satellite payloads implement frequency conversion and RF amplification in both the uplink and downlink, where multiple transparent satellites may be connected to a terrestrial-based gNB. Regenerative satellite payloads can implement a complete gNB or gNB DU on the satellite. Regenerative payloads can perform digital processing on signals, including demodulation, decoding, recoding, remodulation, and / or filtering.

[0096] Figure 2Example interfaces in an NTN are depicted. For example, several radio interfaces can be defined in an NTN. Feeder links can include radio links between the GW and satellites. Serving links can include radio links between satellites and WTRUs. Inter-satellite links (ISLs) can include transport links between satellites. ISLs can be supported by regenerative payloads (e.g., supported only) and can be 3GPP radios or proprietary optical interfaces.

[0097] Depending on the satellite payload configuration, different 3GPP interfaces can be used for each radio link. For example, in a transparent payload, the NR-Uu radio interface can be used for both the serving link and the feeder link. For a regenerative payload, the NR-Uu interface can be used on the serving link, and the Satellite Radio Interface (SRI) can be used for the feeder link. Detailed UP / CP protocol stack information can be obtained for transparent payload configurations.

[0098] NTN satellites can support multiple cells, each comprising one or more satellite beams. These satellite beams cover an area on Earth (e.g., a terrestrial cell) and can vary in diameter. For example, 100-1000 km in LEO deployments or 200-3500 km in GEO deployments. In GEO deployments, the beam coverage area remains fixed relative to the Earth, while in LEO deployments, the area covered by the beam / cell changes over time due to satellite movement. This beam movement can be categorized as "Earth-moving" (where the LEO beam moves continuously on Earth) or "Earth-fixed" (where the beam is redirected to maintain a fixed coverage position until a new cell catches up with (overtakes) the coverage area with discrete and coordinated changes).

[0099] Due to the altitude and beam diameter of the NTN platform, the round-trip time (RTT) and maximum differential delay can be significantly greater than those of terrestrial systems. In transparent NTN deployments, the RTT can range from 25.77 ms (LEO@600km altitude) to 541.46 ms (GEO), and the maximum differential delay ranges from 3.12 ms to 10.3 ms. The RTT of a regenerated payload is approximately half that of a transparent payload because the transparent configuration includes both the serving and feeder links, while the RTT of a regenerated payload only considers the serving link. To minimize the impact on existing NR systems (e.g., to avoid preamble ambiguity or to properly time the receive window), the WTRU can perform timing pre-compensation prior to initial access.

[0100] NTN can support one or more of the following: support for regenerated payloads, DL coverage enhancement, WTRU without Global Navigation Satellite System (GNSS), multiple connectivity, RedCap on NTN, support for store and forward, discontinuous coverage enhancement, mobility enhancement, etc.

[0101] For example, support for regenerable payloads can include different architectures such as full-board gNB, centralized cell-distributed cell (CU-DU) split, and support for inter-satellite links.

[0102] DL coverage enhancement can include enhanced DL coverage to address reduced equivalent isotropic radiated power (EIRP) density and / or power density due to satellite power limitations. DL coverage enhancement may include the identification of candidate enhancements and channels to be enhanced. A “pre-paging” notification / alarm can be defined for near or non-line-of-sight (NLOS) WTRUs experiencing consecutive paging failures.

[0103] NTN can support WTRU without accessing GNSS services, including enhancements to the Random Access Channel (RACH) and time / frequency synchronization processes.

[0104] Multiple connections can be provided, such as dual connections between satellites and intra-satellite carrier aggregation.

[0105] NTN can support reduced-capacity equipment, specifically supporting half-duplex frequency division duplex (HD-FDD) reduced-capacity (RedCap) WTRUs, which may have issues due to large and open-loop TA, missing RRM requirements, and / or DL ​​coverage requirements.

[0106] NTN can support store-and-forward. Support for discontinuous feeder links can be introduced, for example, using SA2 conclusions and regenerative architectures as a baseline.

[0107] Protocols from the Internet of Things (IoT) NTN can be used as a baseline to provide discontinuous coverage enhancements (e.g., introducing discontinuous coverage support for NR).

[0108] Mobility enhancements can be provided, such as enhanced TN / NTN interoperability, group-based HO, and NTN / NTN interoperability between tracks.

[0109] Other topics may include, for example, support for MBS. Other topics may include extensions to RAT-related positioning in NTN. Other topics may include IAB support in NTN. Other topics may include support for high-power (PC2) WTRU. Other topics may include beam-level polarization indication and / or beam hopping mechanisms. Other topics may include coexistence between TN and NTN.

[0110] The methods and processes described in this paper address system-level solutions related to DL coverage enhancement. More specifically, they address the reduction in EIRP density per beam caused by beam power sharing in power-constrained satellites.

[0111] EIRPs can be satellite parameters and have been used in DL coverage assessments. DL parameter sets do not adequately account for power limitations on satellites, and for some satellites with many beams (e.g., 1200), satellite power must be shared among the beams. This solution can result in lower EIRP density per beam and poorer DL coverage compared to the initial expectations. To avoid impacting DL coverage for some or all devices served by satellites, one technique is to split power among different beams, referred to in this paper as “beam power sharing.”

[0112] Figure 3 Several example beam power sharing scenarios in NTN are described. In some examples, full power can be allocated across one or more (e.g., all) beams. As discussed in this paper, allocating full power across one or more (e.g., all) beams may be impractical for some deployments due to power constraints on satellites. In some examples, power sharing across one or more (e.g., all) beams can be performed. Power sharing across one or more (e.g., all) beams can result in poor DL ​​coverage. These challenges can be addressed through general improvements to DL coverage and appropriate network configurations, such as a more conservative MCS and higher transmit power.

[0113] In some examples, closing portions of a cell can allow some beams, instead of full power on their beams, to provide coverage in some areas of the cell at the expense of other areas. In some examples, a combination of power sharing and closing can allow for flexible deployments where power can be distributed between beams anywhere between full power and complete closure. Closing portions of a cell may introduce currently unresolved coverage gaps within the cell that are characteristic of non-terrestrial networks. Considering the size of NTN cells, WTRUs may be concentrated in certain areas (e.g., cities, towns, terrestrial) where power may be concentrated, and in large areas where there are no WTRUs at all (e.g., ocean) where power may be reduced.

[0114] Methods and systems are provided to ensure that WTRU remains accessible and / or connectivity is maintained if the network enables power sharing between beams, thereby reducing DL coverage (including disabling coverage of cell portions).

[0115] Power sharing decisions can be deterministic and can be controlled by the network. Ancillary information can allow estimation of the impact on DL coverage and advanced actions to mitigate potential coverage problems. A reduction in EIRP density may not correspond one-to-one with a reduction in DL coverage. Any estimated impact may require confirmation through measurements. Beam power sharing can result in some beams being illuminated at different times, which can be partially mitigated by system-level solutions.

[0116] The term "beam power sharing" refers to the reduction in EIRP density of a beam due to power limitations on the satellite. The term "beam power sharing state" describes the current power allocated to the beam and can range from full power to completely off. The term "coverage state" describes the quality of DL coverage based on the current beam power sharing state of the beam.

[0117] Some of the materials described in this specification can operate under one or more of the following assumptions: beam power sharing decisions are deterministic and controlled by the network; a reduction in EIRP density may not necessarily correspond one-to-one with a reduction in DL coverage; beam power sharing can result in some beams being illuminated at different times; the range of beam power sharing can be from full power to no power at all; a cell may include one or more beams, and each beam may be in a different coverage state; configurations or pre-configurations provided to compensate for the decline in DL coverage often refer to modified parameters (e.g., MCS, power, repetition, frequency hopping, MIMO, or other configurations that support improved reception). Non-terrestrial networks may be an exemplary scenario; however, some embodiments can also be applied to other scenarios, such as terrestrial networks using network energy conservation.

[0118] The common benefits of the solutions described in this paper include rapid adaptation to reduced DL coverage (due to satellite beam power sharing), which can reduce potential service disruptions and radio link failures (RLF).

[0119] The solutions described in this paper offer significant benefits compared to existing technologies. For example, by applying more appropriate reconfiguration, WTRUs can react immediately to a decline in DL coverage, reducing the risk of RLF. This is particularly important in NTNs, where large signaling delays can introduce significant latency when addressing coverage issues. In another example, when making future beam power sharing decisions, the network can take into account the estimated impact on WTRUs and the duration of that impact. In yet another embodiment, congestion is reduced due to large-scale measurement reporting, as reporting is limited to those WTRUs most affected by the beam power sharing decision. In yet another example, when making beam power sharing decisions, the network is able to determine / consider the impact on idle / inactive WTRUs, which may represent a large portion of the total WTRUs served by non-terrestrial networks. In yet another example, by considering the future power sharing state of a pre-configured target cell, WTRUs can avoid switching to cells that may be unsuitable in the near future, thus avoiding potential RLF or service disruptions due to subsequent mobility events.

[0120] The common solutions and / or actions described in this specification may be combined with one or more of the solutions described herein.

[0121] It can provide general auxiliary information for power sharing in NTN.

[0122] In some embodiments, the network may provide auxiliary information regarding the current and / or future power sharing status of a beam / cell / area, referred to herein as "power sharing auxiliary information." Power sharing auxiliary information may include one or more of the following: power sharing status, description of the affected area, timing of the power sharing status, adjacent and / or upcoming auxiliary information, broadcast power sharing auxiliary information, dedicated power sharing auxiliary information, group power sharing auxiliary information, additional auxiliary information for WTRUs moving from terrestrial to non-terrestrial networks, and additional auxiliary information for WTRUs moving from non-terrestrial to terrestrial networks.

[0123] Power sharing auxiliary information may include the power sharing status of a specific coverage area, which may represent the power and / or a portion of the power allocated to the beam / cell serving that area. The power sharing status may be represented, for example, by: an explicit value (e.g., EIRP density); an index within a predetermined or pre-configured range of values; a percentage of maximum power allocation (e.g., 50% of maximum power); and an offset from a reference value (e.g., increasing or decreasing by X from the provided reference value). The range of beam power sharing status can be from full power (e.g., maximum supported EIRP density) to no allocated power. The beam power sharing status may include information about the current power sharing status, past power sharing status, and / or future status of the beam / cell.

[0124] Power sharing auxiliary information may include a description of the affected area. Power sharing auxiliary information may be associated with a specific area (such as a coverage area or sub-section of satellite coverage). For example, power sharing auxiliary information may be specific to one or more of the following: a beam or beam group (e.g., via beam index), a cell or cell group, a geographic area (e.g., described via reference signal + radius), a tracking area and / or a radio access area (RAN) notification area (RNA), a public terrestrial mobile network (PLMN), or a country or specific geopolitical region. Examples may refer to “beam,” “cell,” or “area,” however, these can be used interchangeably with any of the above.

[0125] Power-sharing auxiliary information may include information related to when the information is applicable (e.g., the timing of the power-sharing state). The applicable time may be the current time and / or a time range, and / or associated with a future time. The power-sharing state may be associated with one or more pre-existing information segments (such as satellite epoch times). If no time is provided, it can be assumed that the current power-sharing state will remain indeterminate for a period of time. Time may be provided as a specific time, a time range, or a time plus a duration.

[0126] Figure 4 Example network ancillary information is depicted, providing current and future power sharing status with associated applicable times. The WTRU can provide power sharing ancillary information, as well as associated effective times for current and future time periods of the region associated with the power sharing ancillary information, such as... Figure 4 As shown. The network can provide one or more of the following information fragments to indicate the validity period of power sharing auxiliary information: the time when the power sharing state begins (e.g., a past, current, or future time); the time when the power sharing state ends; the duration for which the power sharing state applies; and / or the duration of the power sharing state. Power sharing information can be provided once or can be associated with periodicity. For example, a power sharing state can be associated with a start time, an on-duration period, and a periodicity, wherein the power sharing state is considered valid from the start time to the start time plus the duration, and restarts after each periodicity.

[0127] Power sharing auxiliary information may include neighboring and / or upcoming auxiliary information. Power sharing auxiliary information may include information about the current service area (e.g., the current beam and / or cell). Power sharing auxiliary information may also include information about one or more neighboring areas (e.g., power sharing status, timing information, affected areas, etc.). This may include, for example, areas served by other beams of the same cell, other cells originating from the same satellite, or areas served by other satellites.

[0128] It can implement signaling for auxiliary information.

[0129] Power sharing auxiliary information may include broadcast power sharing auxiliary information. Power sharing auxiliary information may be provided, for example, via system information broadcast. Power sharing auxiliary information may be carried in an existing System Information Block (SIB) or via a newly defined SIB. To reduce the frequency of system information retrieval, in some cases, the WTRU may only retrieve updated system information used for power sharing auxiliary information. For example, the WTRU may retrieve power sharing auxiliary information in one or more of the following situations: the power sharing auxiliary information (e.g., such as beam status) has changed from a previously stored / retrieved version (e.g., via flags in received system information); the validity conditions associated with the auxiliary information have expired or are about to expire; the WTRU has received an explicit indication from the network (e.g., an activation command); based on (re)configuration (e.g., the network has configured the WTRU to perform one or more actions requiring power sharing auxiliary information); the WTRU performs cell (re)selection; or the WTRU performs mobility (e.g., the WTRU receives an RRC reconfiguration message).

[0130] Power sharing ancillary information may include dedicated power sharing ancillary information. The WTRU may also be provided with power sharing ancillary information via dedicated signaling (e.g., via RRC, MAC CE, PDSCH, PDCCH, MSGB, MSG2 / MSG4). This information may be based on the WTRU requesting to receive and / or coupled with the activation or configuration of procedures requiring power sharing ancillary information (e.g., as described below in this document). For example, the WTRU may obtain default power sharing ancillary information via system information, which may be supplemented by additional power sharing ancillary information provided via dedicated signaling.

[0131] If the WTRU is provided with updated power-sharing ancillary information that overlaps with (e.g., contradicts) earlier power-sharing ancillary information (e.g., via dedicated signaling), the WTRU can take several actions. For example, the WTRU can rewrite any broadcast information with the dedicated information. In another example, the WTRU can maintain up-to-date information regardless of how the information is provided (e.g., via dedicated or broadcast signaling).

[0132] Power sharing ancillary information may include group power sharing ancillary information. The network may update power sharing ancillary information only for a portion of a cell, where WTRUs serving only within that portion of the cell (e.g., a beam) will be affected. A group radio network temporary identifier (RNTI) associated with the coverage area may be provided to the WTRU. The WTRU can use the group RNTI to monitor notifications, and upon receiving a notification addressed to the group RNTI, the WTRU may update (and / or receive updated) power sharing ancillary information.

[0133] It can enable the verification of power sharing auxiliary information.

[0134] Power sharing ancillary information can be associated with one or more expiration conditions, wherein the WTRU may consider the power sharing ancillary information invalid if one or more of the associated expiration conditions are met. For example, the WTRU may be configured with one or more of the following expiration conditions: upon reaching a specific time (e.g., epoch time), at the end of a time duration or offset, based on the satisfaction of the condition, upon notification that the power sharing ancillary information has been updated (e.g., via a flag in system information or a dedicated network message), based on (re)configuration, based on mobility actions (e.g., cell (re)selection), or upon release from the network.

[0135] An example of an expiration condition offset or the end of a time duration is if the WTRU acquires power-sharing auxiliary information that could be the start of a time duration. At the end of the time duration (or at a fixed offset from the time), the WTRU can consider the power-saving auxiliary information to have expired. The duration and / or time offset can be provided to the WTRU along with the power-sharing auxiliary information. This can be maintained, for example, via a WTRU timer.

[0136] The fulfillment of a condition can also be an expiration condition. For example, the WTRU can set its position as a reference position when acquiring power sharing assistance information. If the WTRU has moved beyond a configured threshold, it can consider the power sharing assistance information to have expired. The distance threshold can be provided to the WTRU along with the power sharing assistance information.

[0137] Expiration conditions can be based on (re)configuration. For example, the network can disable or deactivate processes that require power sharing ancillary information. Upon receiving this reconfiguration, the WTRU can consider the power sharing ancillary information to have expired.

[0138] Expiration conditions can be based on mobility actions (e.g., including cell (re)selection). For example, a WTRU can camp on or connect to a cell that does not support power sharing ancillary information. The WTRU can detect that a cell does not support power sharing based on, for example, explicit indications (e.g., flags in system information) or implicitly (e.g., the cell does not broadcast power sharing ancillary information).

[0139] Release from the network can also include expiration conditions. For example, the WTRU may consider stored power-sharing auxiliary information to have expired when released to the RRC INACTIVE state (e.g., upon receiving an RRC Lease message with a pause indication) or when released to the RRC Idle state (e.g., upon receiving an RRC Lease message).

[0140] The WTRU may use the power-sharing auxiliary information as long as it is deemed valid (e.g., one or more of the associated expiry conditions(s) described above have not been met). If the power-sharing auxiliary information is deemed invalid, the WTRU may or may not update the power-sharing auxiliary information (e.g., reacquire the SIB), or notify the network (e.g., transmit an indication / notification that the power-sharing auxiliary information is no longer valid). Alternatively or additionally, the WTRU may attempt to update the power-sharing auxiliary information before the expiry conditions are met (e.g., while the power-sharing auxiliary information is still considered valid). If the WTRU is able to update the power-sharing auxiliary information before expiry, the WTRU may reset the associated expiry conditions (e.g., update any reference points associated with the distance threshold, reset the associated validity timer, etc.). The WTRU may notify the network that it has updated power-sharing auxiliary information.

[0141] Additional information can be used for switching between terrestrial and non-terrestrial networks.

[0142] If the WTRU is switching between different network types (e.g., between ground and non-ground networks, and / or between non-ground networks at different orbits / altitudes), additional power-sharing auxiliary information can be provided to the WTRU.

[0143] Additional ancillary information may be included for WTRUs moving from terrestrial to non-terrestrial networks (e.g., connecting to). WTRUs may be provided with this information, for example, because a terrestrial cell has entered Network Energy Saving (NES) state and can no longer serve WTRUs. WTRUs may be provided by the terrestrial cell with one or more of the following: information required for non-terrestrial cells to access one or more NTN cells currently serving the area (e.g., time / frequency compensation information); or power sharing ancillary information for one or more non-terrestrial cells currently serving the area.

[0144] Additional ancillary information can be provided for WTRUs moving from non-terrestrial networks to terrestrial networks. WTRUs served by non-terrestrial networks can provide additional ancillary information for switching (e.g., connecting to) terrestrial networks. For example, in addition to the description of broadcast TN coverage information and associated frequencies, the network can include additional information about the Network Energy Saving (NES) status of cells associated with each terrestrial network. Such ancillary information may include, for example, one or more of the following: whether a terrestrial cell is in NES status, whether a terrestrial cell is about to enter or exit NES status, or the percentage of terrestrial cells in NES status within a given area.

[0145] It can determine the WTRU by adding the coverage status and duration.

[0146] The WTRU can (e.g., when acquiring power sharing auxiliary information) estimate and report the impact of power sharing on, for example, coverage characteristics. The term "power sharing decision" as used in this section refers to current or future power sharing actions (e.g., changes in power sharing state as described above) that the network can engage in and notify the WTRU of via power sharing auxiliary information.

[0147] WTRU can estimate the impact of power sharing decisions on it. This estimation can be based on, for example, power sharing ancillary information and / or one or more other satellite characteristics, such as: ancillary information for determining the satellite / cell trajectory, such as satellite ephemeris data (e.g., satellite position, orientation, velocity, or orbital information); cell and / or beam reference points; ancillary information for determining the trajectory of the satellite reference points (e.g., whether the satellite deployment uses Earth-moving beams); satellite coverage area information (e.g., satellite coverage area diameter, cell coverage area diameter, and / or beam coverage area diameter); cell and / or satellite beam configuration (e.g., total number of beams on the satellite, number of beams within the cell, beam pattern within the cell, beam polarization characteristics); or satellite power characteristics (e.g., EIRP density per beam, total available power of the satellite, etc.).

[0148] Similar information (e.g., power sharing auxiliary information and / or more) can also be provided for adjacent satellites / cells / beams and / or upcoming satellites / cells / beams, which the WTRU can use to estimate the impact of future power sharing decisions.

[0149] The WTRU can also use one or more WTRU characteristics to assess coverage status. For example, the WTRU can use one or more of the following: WTRU location information (e.g., GNSS location); information about WTRU movement (e.g., WTRU speed, direction); WTRU receiver characteristics (e.g., antenna characteristics, such as the number of antennas, beamforming capability, whether the antenna is omnidirectional or directional); or WTRU power characteristics (e.g., WTRU power level).

[0150] Ancillary information may also include coverage status determination. The WTRU may use fragments of one or more ancillary information (e.g., power sharing ancillary information or other information mentioned above) to determine whether the WTRU will be affected by a power sharing decision.

[0151] Ancillary information may also include power sharing impact determination based on WTRU calculations. The WTRU can use power sharing ancillary information to determine whether it is currently located in an area affected by power sharing. For example, the WTRU can acquire power sharing ancillary information indicating the power sharing status of different areas of the cell. The WTRU can then acquire its own location information and determine whether it is located within a cell coverage area experiencing reduced coverage due to power sharing. The WTRU can determine its location within an area experiencing power sharing, for example, by one or more of the following methods: the WTRU is served by a beam / cell / satellite described as experiencing power sharing; or the WTRU is located within an area described in the power sharing ancillary information (e.g., the distance between the WTRU and a reference point is less than the described radius, the WTRU is within a longitude / latitude range, the WTRU is located within a clearly described polygonal area, etc.).

[0152] The WTRU can determine whether it will be located in an area that will be affected by a future power-sharing decision. For example, the WTRU can acquire power-sharing auxiliary information indicating the power-sharing status of different areas within the cell and the associated timing of the power-sharing status (e.g., when the power-sharing status will be activated and for how long). The WTRU can acquire its location information and determine whether it is within the area affected by a future power-sharing decision and the potential characteristics of when it will be affected by the power-sharing decision (e.g., the start time and duration of the impact).

[0153] In cases where the satellite is non-geosynchronous (e.g., LEO or MEO), the WTRU can also consider satellite movement when determining whether it will be affected by future power-sharing decisions. For example, in addition to acquiring power-sharing auxiliary information, the WTRU can acquire additional information (e.g., via SIB reception) to determine cell trajectories, such as satellite ephemeris data, cell coverage information, and one or more cell reference points. The WTRU can acquire its own location and, via the trajectory information, determine a series of upcoming cells(s) or areas(s) that will serve the WTRU's location in the future. The WTRU can then determine whether these upcoming areas are associated with future power-sharing decisions. The WTRU can determine the duration of the impact, taking into account both the duration the WTRU will be within its coverage area and the duration of the power-sharing decision.

[0154] However, the WTRU can assess the impact of neighboring power sharing decisions in a similar manner to the above by obtaining auxiliary information on power sharing between neighboring cells / beams / satellites.

[0155] Ancillary information may also include network-based power sharing impact determination. The network may indicate that one or more WTRUs will be affected by the power sharing decision. In one example, the network may send a dedicated message (e.g., via RRC or MAC CE) to the WTRUs informing them that they will be affected by the power sharing decision, which may optionally include additional ancillary information such as power sharing status information and the timing of the power sharing decision. Such information may also be multicast to a set of WTRUs, which can monitor it via a dedicated group RNTI.

[0156] Beam power sharing is not currently supported in NTN, and fluctuations in DL coverage are due to pseudo-random variations in channel conditions. Adjustments are made reactively (e.g., based on measurement reports), and if not detected and / or corrected sufficiently early, they can pose risks to connectivity. Power sharing between satellite beams can lead to dynamic DL coverage conditions, thus impacting WTRU performance. Providing network-aided information related to current or planned power-saving states allows WTRUs to understand how DL coverage will change in the future. Based on the deterministic and / or predictive nature of satellite movement, the network may provide power-saving state aids for one or more neighboring cells and / or satellites, allowing WTRUs to predict potential impacts on DL coverage. This can support the pre-definition of incidental events (e.g., more conservative MCS, PDCCH repetition, etc.) to avoid lost WTRU connectivity. Power sharing impact estimates and conditional DL coverage enhancements can be provided.

[0157] In one embodiment, the network can know the beam power sharing decision in advance and can share auxiliary information about the decision. The WTRU calculates whether and / or when it will be affected by future NW power saving states, based on network auxiliary information and WTRU characteristics (e.g., WTRU location, speed, etc.). Furthermore, the WTRU can report the duration of the impact and optionally the estimated extent of the impact to the NW, and the WTRU can be pre-configured with DL coverage enhancements to be applied after the WTRU enters the area and / or time when it will be affected by changes in DL coverage. This allows the WTRU to react immediately to the decline in DL coverage by applying a more appropriate pre-configuration, thereby reducing the risk of RLF. This is particularly important in NTNs, where large signaling delays can introduce significant latency when resolving coverage issues. Additionally, when making future power sharing decisions, the network can consider the estimated impact on the WTRU and the duration of that impact.

[0158] The WTRU can acquire power sharing auxiliary information (e.g., via SI) indicating the upcoming power sharing state of a cell. The upcoming power sharing state of a cell may include one or more of the following: the expected impact of the power sharing state (e.g., a reduction in EIRP density %), the area affected by power sharing (e.g., an explicit area description via reference points and radii, SSB index), the start time of the power sharing state (e.g., UTC time), the duration of the beam power sharing state (e.g., 10s), or configurations for the WTRU to pre-report the presence of problems (e.g., flags enabling pre-reporting, indications including additional auxiliary information, etc.).

[0159] The WTRU can acquire NTN auxiliary information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris). The WTRU can acquire its location and calculate whether / when the WTRU will be affected by a power-saving state, including the timing and duration of the effect. The WTRU can determine the start time and / or duration of the effect via beam power sharing auxiliary information, NTN auxiliary information, and / or the WTRU's location / characteristics. If pre-reporting is enabled and the WTRU is affected by beam power sharing, the WTRU can pre-report that it will be affected by the power sharing plan. Additionally or alternatively, the WTRU can indicate the estimated duration, DL coverage reduction, and / or its ability to maintain connectivity.

[0160] The WTRU can receive modified MCS and / or additional ULDL coverage enhancements (e.g., PDCCH / PDSCH repetition, etc.) to apply when power sharing is activated. When power sharing is activated, the WTRU can apply the modified MCS and / or UL / DL coverage enhancement techniques. Upon completion of power sharing, the WTRU can revert to the original DL coverage configuration (e.g., original MCS, repetition count, etc.).

[0161] To support WTRU estimation / pre-reporting of conditional DL coverage enhancement and power sharing impacts, WTRU can perform several configurations for power sharing impact pre-reporting or coverage enhancement.

[0162] A power sharing impact pre-report can refer to a WTRU configured to pre-report the potential impact of a power sharing state, or an NW that includes triggering conditions for the WTRU to transmit a power sharing impact pre-report.

[0163] The WTRU can be configured to pre-report the potential impact of power sharing status. This configuration may include configurations for enabling / disabling power sharing impact pre-reporting, configurations for one or more prices for reporting ancillary information (e.g., as described herein), one or more resources for transmitting the power sharing pre-report (e.g., UL authorization or transmission timing), or whether the WTRU can trigger an SR if resources are unavailable for transmitting the power sharing pre-report.

[0164] The network may include one or more triggering conditions for the WTRU to transmit a power sharing impact pre-report. For example, one or more triggering conditions may include one or more of the following: upon receiving a network request, the WTRU determines that it will be affected by the power sharing state; the WTRU determines that it will be affected by the future power sharing state; the WTRU determines that it will be affected by the power sharing state of neighboring cells; or the estimated impact of power sharing causes a coverage reduction configuration threshold.

[0165] The power sharing impact pre-report may include one or more of the following: whether the WTRU is currently affected by the power sharing status, when the WTRU will cease to be affected by the current power sharing status, the current location of the WTRU, whether the WTRU will be affected by future power sharing status, one or more future time ranges indicated by the power sharing status for the WTRU, the SSB index or cell identifier (e.g., PCI) associated with the WTRU’s area, the estimated decrease in DL coverage caused by the power sharing decision, whether the WTRU will completely lose coverage, or whether the WTRU has an alternative.

[0166] The WTRU can transmit power sharing impact pre-reports via RRC, MAC CE, PUSCH, RACH (e.g., MSGA, MSG3, MSG5) and / or PUCCH signaling. If the WTRU does not have resources available for transmitting power sharing impact pre-reports, the WTRU can trigger an SR to acquire those resources.

[0167] The WTRU can receive a configuration to enhance DL coverage as a response to power-sharing state activation (or in response to a pre-reported estimate of the effects of power-sharing). This configuration may include one or more DL coverage enhancements and associated conditions for applying the enhancements. Enhanced DL coverage may include an alternative MCS (e.g., a more conservative MCS) and / or additional repetitions (e.g., PDSCH or PDCCH repetitions).

[0168] Upon receiving an enhanced DL coverage configuration, the WTRU can apply the DL coverage enhancement indefinitely or conform to a pre-configured duration. For example, the WTRU can apply a more conservative coverage configuration for one or more of the following durations: duration for a power-sharing state, duration for X power-sharing states, duration for a time period (e.g., UTC T1 to UTC T2 or a configured duration), when connecting to a cell, and / or when connecting to a satellite.

[0169] A WTRU can be triggered to apply and / or terminate DL coverage enhancements. The WTRU can apply DL coverage enhancements based on the satisfaction of conditions or events. For example, the WTRU can apply DL coverage enhancements based on one or more of the following: upon receiving an enhanced DL coverage configuration (e.g., immediately upon receipt), based on receiving an explicit indication, upon activating power sharing, an offset of the configuration before (or alternatively after) activating power sharing, or conditionally (e.g., if the estimated (or measured) coverage has decreased by a predetermined amount of dB after power sharing activation).

[0170] The WTRU may suspend, revert to the default (e.g., original) configuration, or not apply DL coverage enhancements based on one or more of the following: based on explicit indication, after the power sharing state has ended, at a certain offset after the power sharing state has ended, or conditionally (e.g., when DL coverage has been improved by a predetermined amount of dB and / or during a specific time period (e.g., from time T1 to T2)). If beam, cell, and / or satellite power sharing auxiliary indication power will be completely turned off, the WTRU may not apply coverage enhancements; instead, the WTRU may completely suspend transmissions.

[0171] Figure 5 The illustration depicts an example of power sharing impact estimation and conditional DL coverage enhancement. The WTRU can calculate whether and / or when it will be affected by future NW power-saving states using network-aided information and WTRU characteristics (e.g., WTRU location, speed, etc.). The WTRU can report to the NW the time period and / or estimated extent of the power sharing impact. After the WTRU enters the area / time period where it will be affected by a power sharing decision, it can receive one or more pre-configured DL coverage enhancements to be applied.

[0172] For example, as shown in process 500, the WTRU may perform one or more of the following to support power sharing impact estimation and conditional DL coverage enhancement. At 502, the WTRU may receive power sharing auxiliary information, for example, from the gNB. At 502, the WTRU may receive NTN auxiliary information, for example, from the gNB (e.g., for determining cell characteristics such as cell reference point, cell radius, or satellite ephemeris). At 504, the WTRU may determine its location and / or may estimate the impact of power sharing. At 506, if enabled, the WTRU may pre-report the estimated impact of power sharing. At 508, the network (e.g., the gNB) may receive the pre-report from the WTRU. The network (e.g., the gNB) may determine a modified configuration with enhanced DL coverage based on the estimated impact indicated in the pre-report. The WTRU may receive a pre-configuration for DL ​​coverage enhancement from the network (e.g., the gNB). At 510, when power sharing is activated, the WTRU may apply the DL coverage enhancement indicated in the pre-configuration for DL ​​coverage enhancement. At point 512, upon completion of power sharing activation, WTRU can revert to the original DL coverage configuration (e.g., original MCS, number of repetitions, etc.).

[0173] The WTRU can receive power sharing auxiliary information (e.g., via SI) indicating an upcoming power sharing state for the cell. The power sharing auxiliary information may include one or more of the following: the expected impact of the power sharing state (e.g., a reduction in EIRP density %), the area affected by power sharing (e.g., an explicit area description via reference points and radii, SSB index), the start time of the power sharing state (e.g., UTC time), the duration of the beam power sharing state (e.g., 10 s), or configurations for the WTRU to pre-report the presence of problems (e.g., flags enabling pre-reporting, indications including additional auxiliary information, etc.).

[0174] The WTRU can acquire NTN auxiliary information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, and / or satellite ephemeris).

[0175] The WTRU can acquire its location and calculate whether and / or when it will be affected by the power-saving state. The start time and / or duration of the effect can be determined, for example, via beam power sharing auxiliary information, NTN auxiliary information, and / or WTRU location / characteristics.

[0176] If pre-reporting is enabled and the WTRU is affected by beam power sharing, the WTRU can pre-report that it will be affected by the power sharing plan. The WTRU can indicate the estimated duration of the impact, the reduction in DL coverage affected, and / or whether the WTRU expects to maintain connectivity. The WTRU can receive a modified MCS and / or one or more additional UL / DL coverage enhancements (e.g., PDCCH / PDSCH repetitions, etc.) to apply when power sharing is activated. Upon activation of power sharing, the WTRU can apply the modified MCS and / or one or more UL / DL coverage enhancements. Upon completion of power sharing, the WTRU can revert to the original DL coverage configuration (e.g., original MCS, number of repetitions, etc.).

[0177] The WTRU can receive one or more conditions that must be met before applying pre-configured DL coverage enhancements, for example, to prevent the WTRU from applying overly conservative DL coverage enhancements if the impact of power sharing is overestimated. For example, if the pre-reported value is within the percentage tolerance of the actual impact on the WTRU, the WTRU can apply (e.g., apply only) the DL coverage enhancement. If the WTRU does not apply the pre-configured coverage enhancement (e.g., to avoid missynchronization with the network, or because a modified coverage enhancement more suitable for the actual impact has been provided), the WTRU can report this to the network.

[0178] Post-power sharing impact assessment and reporting are possible. WTRUs can periodically perform one or more measurements and can detect coverage issues caused by power-saving events, triggering measurement result reporting and subsequent reconfiguration. Unless reporting events are carefully configured, a power sharing decision can trigger one or more WTRUs to report measurements simultaneously, leading to congestion and RLF if the network cannot reconfigure severely affected WTRUs quickly enough. Due to the large cell size and number of WTRUs typically served by non-terrestrial networks, the impact of power sharing on different WTRUs can vary significantly. The impact of power sharing can be assessed by configuring one or more (e.g., all) WTRUs (e.g., even those less affected) to report measurements after power sharing activation, which can result in large signaling overhead and congestion during power sharing. This can delay measurement results from the WTRUs most affected by power sharing and may risk those WTRUs losing connectivity entirely unless DL coverage is immediately enhanced. Limitations on measurement result reporting are necessary to prioritize those WTRUs most affected by the power sharing decision.

[0179] WTRUs can be configured with time-based measurement events, whereby a WTRU notifies the network if the DL coverage decreases by a configured threshold from a first time T1 (e.g., before power sharing) to a second time T2 (e.g., after power sharing). In this example, congestion caused by large-scale measurement result reporting can be reduced because reporting is limited (e.g., restricted to) those WTRUs most affected by the beam power sharing decision.

[0180] The WTRU can receive measurement configurations dedicated to assessing and / or reporting the impact of power sharing status. Measurement configurations may include dedicated measurement windows before and after power sharing activation (e.g., for assessing changes in RSRP due to power sharing), one or more additional measurement objects (e.g., for quickly assessing the impact of power sharing status), measurement gaps (e.g., for pausing UL / DL data to assess the impact of power sharing status), and / or one or more conditions for reporting problems with power sharing status (e.g., if the serving cell RSRP drops a first threshold T1 after power sharing status activation).

[0181] At the start of the first measurement window (e.g., before power state activation), the WTRU can reset the L3 measurement window. The WTRU can apply the measurement configuration. The WTRU can evaluate the RSRP before power sharing.

[0182] The WTRU continues to apply the measurement configuration after power sharing activation. At the start of the second measurement window, the WTRU can reset the L3 measurement window and evaluate the RSRP after power sharing. At the end of the second measurement window, the WTRU can evaluate one or more reporting conditions provided in the dedicated measurement configuration (e.g., to report issues related to the power sharing state). If the difference between the RSRP before and after power sharing exceeds a first threshold T1 (e.g., RSRP decrease > T1), the reporting condition is met. If the reporting condition is met, the WTRU can trigger a measurement result report indicating that the WTRU is affected by power sharing. The WTRU can include additional auxiliary information in the measurement result report (e.g., DL measurement results before / after power sharing activation). Additionally or alternatively, if the expected duration of the power-saving state exceeds a predetermined time duration (e.g., 10 s), the WTRU can trigger a measurement result report. The expected duration of the power-saving state can be derived using NW auxiliary information about the power sharing state.

[0183] To support post-assessment and impact reporting of WTRU power sharing effects, WTRUs can be configured (e.g., via RRC signaling) with dedicated measurement configurations that the network can use to assess the impact of the power sharing decision and / or ensure that the WTRU most affected by the power sharing decision triggers measurement result reporting. The network can use the measurement result reports to determine the level of DL coverage enhancement required by the WTRU (e.g., by comparing the RSRP of the cell before and after power sharing activation).

[0184] Dedicated measurement configurations for assessing the impact of power sharing may include configurations for assessing the RSRP / RSRQ of a cell before power sharing, configurations for assessing the RSRP / RSRQ of a cell after power sharing, configurations for triggering measurement result reporting (e.g., if the WTRU has been severely affected by the power sharing decision), and / or configurations for what to include in the measurement result report (e.g., additional measurement results to be included).

[0185] As part of a measurement configuration for evaluating the impact of power sharing, one or more additional measurement objects (e.g., reference signal, CSI-RS, SSB, etc.) can be provided to the WTRU to evaluate the channel. The reference signal can occur before and / or after power sharing activation. In one example, a measurement window can be provided to the WTRU to evaluate the RSRP / RSRQ of the channel. The measurement window can be defined before and / or after power sharing activation. The measurement window can be defined via one or more of the following: the absolute set of start and end times of the measurement window (e.g., 10:20:35, 10:20:40, etc.), the duration and offset from the reference time (e.g., power sharing activation time), the start time plus the duration (e.g., 10:20:35, 10s), or the start time and number of measurements N that the WTRU considers complete when performing N measurements after the start time. If the duration and offset from the reference time are provided to the WTRU, the WTRU can start a first measurement window at an offset before the reference time and a second measurement window at an offset after the reference time.

[0186] Based on configuration, the WTRU can use (e.g., only use) the measurement results obtained within the measurement window, for example, to evaluate the RSRP / RSRQ of the cell. For instance, at the start of the measurement window, the WTRU can restart the L3 measurement window and accumulate measurement results throughout the measurement window to evaluate RSRP / RSRQ. At the end of the measurement window, the WTRU can store the average L3 RSRP / RSRQ measurement results to be used to evaluate the measurement result reporting conditions.

[0187] The WTRU may be provided with measurement gaps (e.g., to avoid wasting transmissions that might not be successfully received due to poor DL ​​coverage). The WTRU may begin a measurement gap when power sharing is activated and may end a measurement gap, for example, when evaluating the channel, meeting measurement result reporting criteria, or receiving DL coverage enhancements. While the WTRU is within a measurement gap, it may not expect any DL data transmission.

[0188] Measurement result reporting can be configured to be provided to the WTRU as part of a dedicated measurement configuration to assess the impact of power sharing. For example, the WTRU can be configured with a measurement result threshold, Thresh-1. The WTRU can trigger a measurement result report if the difference between a measurement obtained before power sharing activation and a measurement obtained after power sharing activation exceeds the threshold. The threshold can measure, for example, the difference between the highest / lowest measurement obtained during the period before and after power sharing activation, or the difference between average measurement results. The WTRU can be configured to include measurement results obtained before, after, or both of power sharing activation.

[0189] Upon receiving a dedicated measurement result report, the WTRU can perform a measurement on the indicated object within the specified time, and can report the configured measurement quantity if the measurement result report conditions are met.

[0190] Upon receiving a dedicated measurement configuration, the WTRU can release the previous measurement configuration and continue with the new measurement configuration indefinitely. Alternatively, the WTRU can maintain and / or store the current measurement configuration and temporarily apply new measurements (e.g., to evaluate RSRP / RSRQ of a cell before / after power sharing). Whether the WTRU stores or releases the original measurement configuration can be based on network indications or configurations (e.g., based on the configuration within the dedicated measurement configuration).

[0191] A dedicated measurement configuration may include an associated duration for which the WTRU will apply the dedicated measurement configuration. Upon completion of the associated duration, the WTRU may revert to the original stored measurement configuration. Alternatively, if the WTRU does not meet reporting conditions after power sharing activation (e.g., the power sharing event did not significantly affect the WTRU), the WTRU may revert to the original measurement configuration. In response to explicit instructions from the network, the WTRU may revert to the original measurement configuration at any time.

[0192] Figure 6An example of post-power-sharing impact assessment and reporting is described. Prior to power-sharing activation, a dedicated measurement configuration can be provided to the WTRU to assess the impact of power-sharing. This dedicated measurement configuration may include time-based measurement events, where the WTRU notifies the network if the DL coverage decreases from a first time T1 (e.g., pre-power-sharing state) to a second time T2 (e.g., post-power-sharing state) at a configured threshold. The WTRU can assess the RSRP of the cell before and after power-sharing. If the reporting configuration is met, the WTRU can report the measurement results to the network and / or indicate that the WTRU has been affected by the power-sharing decision (e.g., severely affected).

[0193] The WTRU can perform one or more operations to support post-power-sharing status assessment and reporting. For example, the WTRU can receive measurement configurations dedicated to assessing and / or reporting the impact of power-sharing status. Measurement configurations may include dedicated measurement windows before and after power-sharing activation (e.g., for assessing changes in RSRP due to power-sharing), additional measurement objects (e.g., for quickly assessing the impact of power-sharing status), measurement gaps (e.g., for pausing UL / DL data to assess the impact of power-sharing status), and / or one or more conditions for reporting problems with power-sharing status (e.g., if the serving cell RSRP drops by a threshold T1 after power-sharing status activation).

[0194] At the start of the first measurement window (e.g., before power state activation), the WTRU can reset the L3 measurement window, apply the measurement configuration, and / or evaluate the pre-power-sharing RSRP. The WTRU can continue applying the measurement configuration after power-sharing activation. At the start of the second measurement window, the WTRU can reset the L3 measurement window and evaluate the post-power-sharing RSRP.

[0195] At the end of the second measurement window, the WTRU can evaluate one or more reporting conditions provided in the dedicated measurement configuration (e.g., to report issues related to power sharing status). A reporting condition can be met if the difference in RSRP before and after power sharing exceeds a first threshold T1 (e.g., RSRP decrease > T1). If the reporting condition is met, the WTRU can trigger a measurement result report indicating that the WTRU is affected by power sharing. The WTRU can include additional auxiliary information in the measurement result report (e.g., DL measurement results before and / or after power sharing activation).

[0196] The network can provide alternative or additional reporting conditions. For example, if the expected duration of a power-saving state exceeds the time duration (e.g., 10 s), the WTRU should only report under that reporting condition to further reduce congestion from over-measurement reporting. The WTRU can determine the duration of the power-sharing effect based on, for example, WTRU characteristics and / or NW auxiliary information as described herein.

[0197] Network polling can be implemented for idle and / or inactive WTRUs. The RAN network can obtain a rough estimate of how many inactive WTRUs are in a geographic area based on the RNA tracking region. For idle WTRUs, this information may be stored at the CN and may not be known to the RAN.

[0198] Given the size of NTN cells, many WTRUs (e.g., several orders of magnitude more than in the terrestrial case) can be served by an NTN cell, some of which may be in idle / inactive states. The ability of idle / inactive WTRUs to provide feedback on planned network power sharing decisions may be limited. The network may not know how many WTRUs a given decision will affect, since mobility in these states is WTRU-controlled. Importantly, WTRUs remain reachable in idle / inactive states for regulatory reasons, such as for receiving emergency messages. The network can avoid reducing coverage for idle / inactive WTRUs that do not have alternatives.

[0199] WTRUs (e.g., idle / inactive WTRUs) can be polled to provide feedback on anticipated power-sharing state activation by receiving paging messages. WTRUs can receive power-sharing state ancillary information and can determine whether a WTRU will be affected. WTRUs can receive dedicated preambles and / or reporting conditions to indicate the severity of the impact. Example preambles include whether a WTRU anticipates complete coverage loss or whether a WTRU is expected to be affected. The network can respond with RAR and UL authorizations, requesting additional ancillary information (e.g., the duration of coverage impact and / or the predicted magnitude of DL coverage loss). In such an example, the network can determine and / or consider the impact on idle / inactive WTRUs when making beam power-sharing decisions, which may represent a large portion of the total WTRUs served by non-terrestrial networks.

[0200] The WTRU can be released to idle / inactive (e.g., via receiving an RRCRelease or RRCReleasewithSuspend message) and can monitor paging. The WTRU can receive paging requests to assess the impact of future power sharing status. The WTRU can receive beam power sharing auxiliary information (e.g., via a specific SIB) indicating the planned power sharing status of the cell, including one or more of the following: the area affected by beam power sharing (e.g., via an explicit area description of reference points and radii, SSB index, etc.), the time of beam power sharing implementation (e.g., UTC time), the duration of beam power sharing (e.g., 10s), the expected impact of beam power sharing (e.g., power / coverage reduction dB, cell completely shut down), or a configuration for idle / inactive UEs to report updates on the existence of problems with the power sharing status. This configuration may include one or more reporting conditions (e.g., if the duration of the impact exceeds a time period, the WTRU will be affected by the power sharing decision, etc.) and / or one or more preambles associated with a specific impact (e.g., preamble A: coverage limitation, preamble B: loss of coverage).

[0201] The WTRU can calculate whether and / or when it will be affected by a power-saving state, including the duration and timing of the impact. The WTRU can determine the start time and duration of the impact via beam power sharing auxiliary information, NTN auxiliary information, and / or WTRU location / characteristics. If the WTRU meets the reporting conditions within the idle / inactive reporting configuration (e.g., the WTRU will be affected), the WTRU can send preamble A if it estimates that it will become severely coverage-limited, or preamble B if it estimates that it will completely lose coverage.

[0202] To support NW polling of the power-sharing impact on idle / inactive WTRUs, WTRUs can perform paging-based network polling or follow-up WTRUs. Idle / inactive WTRUs can be polled to determine if they are likely to be affected by future power-sharing decisions. In one example, this can be performed using a network paging procedure, where the network will page one or more WTRUs, requesting input regarding whether they will be affected by a power-sharing decision. WTRUs can provide a simple response (e.g., yes / no) via a dedicated preamble transmission.

[0203] The WTRU can receive configurations to support network polling in RRC_IDLE / INACTIVE. The term "network polling" refers to a request from the network to provide some auxiliary information about the impact of power sharing decisions on idle / inactive WTRUs.

[0204] The WTRU can be configured to monitor paging information for the purpose of network polling due to power sharing effects. Network polling can be indicated within a typical paging message (e.g., via a request within a paging short message), or a dedicated RNTI can be provided to the WTRU to monitor network polling requests. The WTRU can reuse an existing paging cycle to monitor network polling, or the WTRU can be configured with dedicated timing for monitoring network polling.

[0205] The WTRU can be configured with one or more preambles to indicate whether there is an estimation problem in the current and / or future power sharing decisions. For example, the network can be configured with a dedicated preamble or set of preambles that can indicate one or more of the following: the WTRU is affected by the current power sharing state; the WTRU will be affected by the future power sharing state; the WTRU may not be affected by the power sharing state; the WTRU estimates that it may lose connectivity based on the power sharing state, but there are acceptable alternative cells to reconnect to; and / or the WTRU may lose connectivity and has no alternative connectivity (e.g., there are no suitable neighboring cells or terrestrial networks for the WTRU to connect to).

[0206] The WTRU can also select one or more RACH timings to transmit a preamble to convey additional information (e.g., the SSB in which the WTRU currently resides). Alternatively, the WTRU can be configured to initiate a connection to the cell (e.g., via the transmission of an RRC establishment message or RRC recovery message) if it is (or may be in the future) severely affected by a power-sharing state.

[0207] Network polling can be enabled / disabled by indicating explicitly (e.g., via flags within power sharing auxiliary information and / or network polling configuration) or implicitly (e.g., via the absence of one or more information segments required to receive network polling, such as those described above). The configuration for network polling can be provided, for example, via system information (e.g., as part of power sharing auxiliary information), within an RRC release message, or within an RRC release message with a pause indication. If the WTRU is provided with a default configuration via system information and receives subsequent dedicated configuration via an RRCRelease / RRRCRelease message with a pause, the WTRU can override the default configuration and apply the dedicated polling configuration.

[0208] When released to idle or inactive conditions, if network polling is enabled, the WTRU can monitor network polling messages according to the indicated configuration (e.g., at the configured time and using the indicated RNTI). For example, if the WTRU receives a subsequent indication that network polling is disabled, or if the cell is (re)selected to a cell that does not support (or has been disabled) network polling, the WTRU can stop monitoring network polling.

[0209] Upon receiving a network polling message, the WTRU can obtain updated power sharing support information (e.g., via SIB) and other information needed to assess the impact of power sharing on the WTRU (e.g., satellite support information, WTRU location, etc.). The WTRU can then calculate whether it will be affected by current or future power sharing decisions (e.g., as described elsewhere in this document).

[0210] Upon receiving a network poll, the WTRU can choose one or more reserved preambles and / or RACH timings, or it can connect to the network in response. Alternatively, the network polling message or network polling configuration can have an associated set of conditions for responding. For example, the WTRU may only need to respond to a network poll if one or more of the following conditions are met: the WTRU is located in a specific area; the WTRU is currently affected by power sharing; the WTRU is in idle mode; the WTRU is in inactive mode; the duration of the power sharing effect exceeds a specific time duration; the estimated decline in DL coverage exceeds a given threshold; the WTRU estimates that it will lose connectivity; and / or the WTRU does not have available alternative cells where it can maintain connectivity.

[0211] Upon receiving a network poll, and if all associated conditions have been met, the WTRU can select a preamble that best represents the power-sharing impact of the WTRU and respond to the network poll message according to its configuration.

[0212] Upon receiving a polling response (e.g., a dedicated preamble), the network may request additional information regarding the impact on idle / inactive WTRUs. In this scenario, the WTRU may monitor for additional signaling (e.g., a random access response (RAR)) after the paging response is transmitted to receive the additional request.

[0213] The WTRU can receive configurations (e.g., as part of a network polling configuration or separately, such as within a network polling message) to support additional monitoring of follow-up messages from the original network polling message. This configuration can instruct the WTRU to reuse ra_ResponseWindow to monitor subsequent requests, or alternatively, instruct a new duration for monitoring the PDCCH against follow-up messages.

[0214] Follow-up network polling messages may include one or more of the following information fragments: UL authorization to report follow-up auxiliary information, RNTI for a specific WTRU (which is included as auxiliary information), an indication to continue random access and connect to the cell, or an indication to enable coverage enhancement (e.g., MSG3 repetition). Information indicated as being included as auxiliary information may be one or more of the following: how long the WTRU is expected to be affected by power sharing status; the area where the WTRU is located (e.g., the associated SSB index); an estimated decrease in DL coverage; or current WTRU measurement results.

[0215] Upon receiving the initial network polling message and transmitting the initial polling response, if the WTRU is configured to monitor follow-up messages (and / or alternatively, if the network polling message indicates that follow-up messages should be monitored), the WTRU may monitor the follow-up polling message. The WTRU may begin monitoring immediately after the initial response to the network polling (e.g., preamble transmission), and the WTRU may offset the start of monitoring by the WTRU-gNB round-trip time (RTT).

[0216] Upon receiving a follow-up request, the WTRU can respond by transmitting the requested ancillary information within the indicated authorization. The WTRU can transmit the message via MSGA PUSCH, MSG3 format, or MAC CE.

[0217] Figure 7 An example NW polling of the power sharing impact on idle / inactive WTRUs is depicted. As shown in procedure 700, at 702, the idle / inactive WTRU can be polled to provide feedback on the expected power sharing state activation by receiving a paging message at 704. The WTRU can receive power sharing state auxiliary information and can determine at 706 whether it will be affected, as well as dedicated preambles and reporting conditions to indicate the severity of the impact (e.g., at 708, preamble A: WTRU expects complete loss of coverage; preamble B: WTRU expects to be affected).

[0218] The WTRU can perform one or more of the following to support NW polling for RRC_IDLE / INACTIVE WTRUs. The WTRU can be released to idle / inactive (e.g., via receiving an RRCLease or an RRCLease message with a pause) and can monitor paging. At 704, the WTRU can receive a paging request to assess the impact of a future power-sharing state. The WTRU can acquire beam power-sharing auxiliary information (e.g., via a specific SIB). At 706, the WTRU can calculate whether and / or when it will be affected by a power-saving state, including the time and duration of the impact. The WTRU can determine the start time and duration of the impact via beam power-sharing auxiliary information, NTN auxiliary information, and / or WTRU location / characteristics. If the WTRU meets the reporting conditions within the idle / inactive reporting configuration (e.g., the WTRU will be affected), then at 708, if the WTRU estimates that it will become severely coverage-limited, the WTRU can send preamble A, or if the WTRU estimates that it will completely lose coverage, the WTRU can send preamble B.

[0219] At 710, power sharing auxiliary information acquired by the WTRU (e.g., via a specific SIB) can indicate the planned power sharing status of the cell. The planned power sharing status of the cell can include one or more of the following: the area affected by beam power sharing (e.g., via explicit area description of reference points and radii, SSB index, etc.), the time of beam power sharing implementation (e.g., UTC time), the duration of beam power sharing (e.g., 10s), the expected impact of beam power sharing (e.g., power / coverage reduction dB, complete cell shutdown), or a configuration for reporting updates of the power sharing status to idle / inactive WTRUs. This configuration can include one or more reporting conditions (e.g., if the duration of the impact exceeds a time period, the WTRU will be affected by the power sharing decision, etc.) or a preamble associated with a specific impact (e.g., preamble A: coverage limitation, preamble B: loss of coverage).

[0220] At 712, the NW can respond with RAR and UL authorizations, requesting additional ancillary information (such as the duration of coverage impact and / or the predicted magnitude of DL coverage loss), for example, to provide additional ancillary information about the impact on the WTRU. Whether the WTRU monitors the additional authorizations can be explicitly configured (e.g., in power-sharing ancillary information) or can be requested within the initial polling request. At 714, upon receiving a UL authorization requesting additional ancillary information, the WTRU can provide, for example, the affected SSB index, the duration of impact, etc. At 716, the NW can receive an MSG3 with ancillary information and can terminate the RACH process.

[0221] Pre-configuration processing under power sharing is possible. In some cases of pre-configuration processing under power sharing, if the triggering conditions for executing the pre-configured mobility event are met, the WTRU will execute the mobility event even if the target cell may soon enter beam power sharing mode. Given the determinism of satellites, pre-configuring the target cell for handover is well-suited for NTNs. NTNs heavily rely on distance and time-based triggering, which may not fully consider the target cell's measurements. If the upcoming satellite's power sharing state is known and will affect cells configured as candidates, the WTRU may risk handing over to a cell that will experience DL coverage issues.

[0222] Given the determinism of satellites, pre-configured target cells for handover are well-suited for NTNs. NTNs heavily rely on distance and time-based triggering, which may not fully account for target cell measurements. If the power-sharing status of an upcoming satellite is known and will affect cells configured as candidates, the WTRU may risk handing over to a cell that will experience DL coverage issues.

[0223] The WTRU can receive power sharing status assistance information from neighboring cells / satellites. The WTRU can determine whether one or more neighboring cells affected by the power sharing decision are LTM candidates or CHO candidates. The WTRU can pause (e.g., or offset-triggered) the configuration of LTM / CHO candidates for the duration of the power-saving status, for example, to avoid handover to cells that will experience poor coverage. By considering the future power sharing status of the pre-configured target cells, the WTRU can avoid handover to cells that may be unsuitable in the near future and can avoid potential RLF or service disruptions due to subsequent mobility events.

[0224] The WTRU can acquire power sharing auxiliary information (e.g., via SI), which indicates the upcoming power sharing state of the current serving cell and one or more neighboring cells. Power sharing auxiliary information may include the expected impact of the power sharing state (e.g., a reduction in EIRP density %), the area affected by power sharing (e.g., an explicit area description via reference points and radii, SSB index), the start time of the power sharing state (e.g., UTC time), and / or the duration of the beam power sharing state (e.g., 10 s).

[0225] The WTRU can acquire NTN auxiliary information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris) of the serving cell and neighboring cells (e.g., if neighboring cells originate from different satellites). The WTRU can acquire its location and calculate whether / when the WTRU will be affected by the power-saving state, including the timing and duration of the impact from both the serving cell and neighboring cells. The WTRU can determine the start time and duration of the impact based on beam power sharing auxiliary information, NTN auxiliary information, and / or the WTRU's location / characteristics.

[0226] The WTRU can identify one or more neighboring cells that will be affected as LTM / CHO candidates. During the period when the WTRU is affected by the power sharing state of the candidate cells, the WTRU may disregard the candidates (e.g., not perform LTM, not monitor CHO conditions). The WTRU may apply a bias to the execution conditions during the power sharing state. After the coverage state impact ends, the WTRU may reconsider the LTM / CHO candidates. The WTRU may then perform LTM / CHO (e.g., if the conditions are met).

[0227] Upon receiving a pre-configured mobility candidate (e.g., CHO configuration or LTM configuration), the WTRU can indicate whether the candidate will be affected by a power-saving state (current or future). To make this determination, the WTRU can acquire power-sharing assistance information for one or more candidate cells and calculate whether one of the candidate cells will be affected by power sharing with neighboring cells (as previously described in this document). Alternatively, the network can provide power-sharing assistance information as part of the candidate cell configuration.

[0228] Power sharing assistance information for a candidate cell can be associated with expiration conditions (e.g., those described in this document). If the expiration conditions are met, the WTRU no longer considers the associated power sharing assistance information valid, and the WTRU can, for example, perform one or more of the following options: not modify the candidate cell processing and perform the old actions, release the candidate cell configuration and optionally notify the network, or reacquire the power sharing assistance information.

[0229] The WTRU can be configured to apply specific processing to pre-configured mobility candidates based on the power sharing state of neighboring candidate cells. Configuration for the pre-configured mobility processing may include: flags for enabling / disabling modified processing of pre-configured mobility candidates based on power sharing state; one or more biases for applying (e.g., to triggering events) when candidate cells will be affected by power sharing; configuration for releasing candidates when candidate cells will be affected by power sharing; or configuration for reporting to the network when candidate cells are affected by power sharing.

[0230] When it is detected that a pre-configured mobility candidate (e.g., a CHO and / or LTM candidate) is affected by and / or will be affected by a power sharing state at some point in the future, the WTRU may apply one or more actions to the pre-configured mobility configuration. For example, the WTRU may release the candidate configuration, the WTRU may suspend the CHO and / or LTM candidate, the WTRU may bias the triggering conditions for CHO and / or LTM execution, or the WTRU may trigger CHO and / or LTM, however, the RRC reconfiguration message / synchronization with the upcoming cell is not applied until the power sharing state ends.

[0231] If the serving cell is also affected by the power sharing decision (or alternatively, if radio conditions are degraded by other means such as fading), the WTRU can trigger pre-configured mobility regardless. For example, multiple thresholds can be provided to the WTRU. If the first is met, the WTRU suspends configuration; if the second is met, the WTRU triggers mobility regardless. If a candidate configuration may be affected by future power sharing events, the WTRU can perform one or more of the above actions (e.g., adding bias triggering conditions, suspending candidates, etc.) indefinitely, or alternatively only for the duration of the power sharing effect.

[0232] If the WTRU has already applied pre-configured bias or suspended a pre-configured mobility candidate, it can report this to the network. Whether the WTRU reports the impact on the pre-configured mobility candidate can be based on configuration, or alternatively, on configuration. For example, the WTRU can report that it has applied modified processing to the configured mobility candidate based on whether it has released the pre-configured mobility candidate, whether it has applied bias to the pre-configured mobility candidate, whether it has suspended the pre-configured mobility candidate, or whether the duration of the modified processing of the pre-configured candidate exceeds a threshold.

[0233] Figure 8The illustration depicts an example pre-configuration process under power sharing. To support pre-configuration processing under power sharing, the WTRU can perform one or more of the operations described above. For example, in addition to calculating the impact of power sharing on the current serving cell, the WTRU can also acquire and evaluate power sharing status auxiliary information of neighboring cells. If the WTRU determines that one or more neighboring cells affected by the power sharing decision are LTM or CHO candidates, the WTRU can suspend (or alternatively bias-trigger) the configuration of LTM / CHO candidates for the duration of the power-saving state to avoid handover to cells that will experience poor coverage.

[0234] The WTRU can acquire power sharing auxiliary information (e.g., via SI) that indicates the upcoming power sharing state of the current serving cell and one or more neighboring cells. For example, the power sharing auxiliary information may include the expected impact of the power sharing state (e.g., EIRP density reduction %). The power sharing auxiliary information may include the area affected by power sharing (e.g., an explicit area description via reference points and radii, SSB index). The power sharing auxiliary information may include the start time of the power sharing state (e.g., UTC time). The power sharing auxiliary information may include the duration of the beam power sharing state (e.g., 10 s).

[0235] The WTRU can acquire NTN auxiliary information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris) of the serving cell and neighboring cells (if the neighboring cells originate from different satellites). The WTRU can acquire its location and calculate whether and / or when it will be affected by the power-saving state, including the time and duration of the impact on both the serving cell and neighboring cells. The WTRU can determine the start time and duration of the impact based on beam power sharing auxiliary information, NTN auxiliary information, and / or the WTRU's location / characteristics. The WTRU can identify one or more neighboring cells to be affected as LTM / CHO candidates. During the period when the WTRU is affected by the power-sharing state of a candidate cell, the WTRU may disregard the candidate (e.g., not perform LTM, not monitor CHO conditions). Alternatively, the WTRU may apply biased execution conditions during the power-sharing state. After the coverage state impact ends, the WTRU can reconsider the LTM / CHO candidate. The WTRU can perform LTM / CHO (e.g., if conditions are met).

Claims

1. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Receive power sharing assistance information and non-terrestrial network (NTN) assistance information, wherein the power sharing assistance information indicates an upcoming power saving state for the NTN equipment; Determine the location information associated with the WTRU; and A report indicating that the WTRU will be affected by the power-saving state is sent based on the power-sharing auxiliary information, the NTN auxiliary information, and the location information.

2. The WTRU of claim 1, wherein the power sharing auxiliary information includes one or more of the following: the expected impact of the power sharing state, an indication of the area affected by the power sharing state, the start time of the power sharing state, or the duration of the power sharing state.

3. The WTRU of claim 2, wherein the report indicates one or more of the estimated duration of the expected impact of the power sharing state, downlink (DL) coverage reduction, or whether the WTRU will maintain its connection with the NTN device.

4. The WTRU of claim 2, wherein the indication of the region affected by the power sharing state comprises an explicit region description or synchronization signal block (SSB) index via a reference point and radius; and The expected impact of the power-sharing state includes a percentage reduction in radiated power density.

5. The WTRU according to claim 1, wherein, The power sharing auxiliary information includes a flag that enables pre-reporting or an indication to include additional auxiliary information in the report, wherein the additional auxiliary information includes the predicted magnitude of DL coverage loss, information required for access to non-terrestrial cells, or power sharing auxiliary information of one or more non-terrestrial cells currently serving the area.

6. The WTRU of claim 1, wherein the processor is configured to: Receive one or more modified modulation and coding schemes (MCS); and Use the modified MCS to receive downlink (DL).

7. The WTRU of claim 1, wherein the processor is configured to: Receive one or more modified downlink (DL) coverage enhancements; and Use the DL coverage enhancement to receive DL transmissions.

8. The WTRU of claim 1, wherein the processor is configured to: Transmission to the NTN device is suspended during the duration of the power-saving state.

9. The WTRU of claim 1, wherein the processor is configured to: When the power sharing state is completed, the system will revert to the original DL coverage configuration.

10. The WTRU according to claim 1, wherein, The NTN auxiliary information includes one or more of the following: cell reference point, cell radius, or satellite ephemeris, and the NTN auxiliary information is obtained via the System Information Block (SIB).

11. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Receive power sharing assistance information and non-terrestrial network (NTN) assistance information, wherein the power sharing assistance information indicates an upcoming power saving state for the NTN device; Determine the location information associated with the WTRU; as well as A report indicating that the WTRU will be affected by the power-saving state is sent based on the power-sharing auxiliary information, the NTN auxiliary information, and the location information.

12. The method according to claim 11, wherein, The power sharing auxiliary information includes one or more of the following: the expected impact of the power sharing state, an indication of the area affected by the power sharing state, the start time of the power sharing state, or the duration of the power sharing state.

13. The method of claim 12, wherein, The report indicates one or more of the following: the estimated duration of the expected impact of the power sharing status, the reduction in downlink (DL) coverage, or whether the WTRU will maintain its connection to the NTN device.

14. The method according to claim 12, wherein, The indication of the region affected by the power sharing state includes an explicit region description via a reference point and radius or a synchronization signal block (SSB) index; and The expected impact of the power-sharing state includes a percentage reduction in radiated power density.

15. The method according to claim 11, wherein, The power sharing auxiliary information includes a flag enabling pre-reporting or an indication to include additional auxiliary information in the report, wherein the additional auxiliary information includes the predicted magnitude of DL coverage loss, information required for access to non-terrestrial cells, or power sharing auxiliary information for one or more non-terrestrial cells currently serving the area.

16. The method of claim 11, further comprising: Receive one or more modified modulation and coding schemes (MCS); as well as Use the modified MCS to receive downlink (DL).

17. The method of claim 11, further comprising: Receive one or more corrected downlink (DL) coverage enhancements; as well as Use the DL coverage enhancement to receive DL transmissions.

18. The method of claim 11, further comprising: Transmission to the NTN device is suspended during the duration of the power-saving state.

19. The method of claim 11, further comprising: When the power sharing state is completed, the system will revert to the original DL coverage configuration.

20. The method according to claim 11, wherein, The NTN auxiliary information includes one or more of the following: cell reference point, cell radius, or satellite ephemeris, and the NTN auxiliary information is obtained via the System Information Block (SIB).

Images