[go: up one dir, main page]

WO2025072431A1 - Estimation de l'impact d'un partage de puissance et amélioration conditionnelle de la couverture dl - Google Patents

Estimation de l'impact d'un partage de puissance et amélioration conditionnelle de la couverture dl Download PDF

Info

Publication number
WO2025072431A1
WO2025072431A1 PCT/US2024/048543 US2024048543W WO2025072431A1 WO 2025072431 A1 WO2025072431 A1 WO 2025072431A1 US 2024048543 W US2024048543 W US 2024048543W WO 2025072431 A1 WO2025072431 A1 WO 2025072431A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
power sharing
assistance information
power
coverage
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/048543
Other languages
English (en)
Inventor
Dylan WATTS
Moon Il Lee
Brian Martin
Paul Marinier
Faris ALFARHAN
Martino Freda
Oumer Teyeb
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025072431A1 publication Critical patent/WO2025072431A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851—Systems using a satellite or space-based relay
    • H04B7/18513—Transmission in a satellite or space-based system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • H04B7/18543—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection for adaptation of transmission parameters, e.g. power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0245—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal according to signal strength

Definitions

  • Non-terrestrial networks facilitate deployment of wireless networks in areas where land- based antennas may be impractical, such as due to geography or cost. NTN deployments support basic talk and text anywhere in the world. Further, future releases coupled with proliferation of next-generation low-orbit satellites may enable enhanced services such as web browsing.
  • a basic NTN consists of an aerial or space-borne platform which, via a gateway (GW), transports signals from a land-based based gNB to a wireless transmit/receive unit (WTRU) and vice-versa.
  • NTN supports power class 3 WTRUs with omnidirectional antenna and linear polarization, or a very small aperture antenna (VSAT) terminal with directive antenna and circular polarization. It is assumed that all NTN WTRUs may be Global Navigation Satellite System (GNSS) capable.
  • GNSS Global Navigation Satellite System
  • a wireless transmit/receive unit may comprise 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 of an NTN device.
  • the processor may determine location information associated with the WTRU.
  • the processor may send a report that indicates the WTRU may be impacted by the power saving state based on the power sharing assistance information, the NTN assistance information, and/or the location information.
  • the power sharing assistance information may be, for example, one or more of an expected impact of power sharing state, an indication of an area impacted by the power sharing state, a start time of the power sharing state, or a duration of the power sharing state.
  • the report may include, for example, an indication of one or more of an estimated duration of the expected impact of power sharing state, a downlink (DL) coverage reduction, or whether the WTRU will remain in connection with the NTN device.
  • the indication of an area impacted by the power sharing state may include, for example, an explicit area description via reference point and radius or a synchronization signal block (SSB) index.
  • the expected impact of power sharing state may include, for example, a percent reduction in radiated power density.
  • the power sharing assistance information may include, for example, a flag enabling pre-reporting and/or an indication to include additional assistance information in the report.
  • Additional assistance information may include, for example, a predicted magnitude of a DL coverage loss, information needed to access a non-terrestrial cell, and/or power sharing assistance information for one or more non-terrestrial cells which are currently serving an area.
  • the processor may be configured to receive one of more revised modulation and coding scheme (MCS).
  • MCS modulation and coding scheme
  • the processor may be configured to receive a downlink (DL) using the revised MCS.
  • the processor may be configured to receive one of more revised downlink (DL) coverage enhancements.
  • the processor may be configured to receive a DL transmission using the DL coverage enhancements.
  • the processor may be configured to suspend transmission to the NTN device for a duration of the power saving state.
  • the processor may be configured to revert to an original DL coverage configuration upon completion of the power sharing state.
  • the NTN assistance information may include, for example, one or more of cell reference point, cell radius, or satellite ephemeris.
  • the NTN assistance information may be acquired via a system information block (SIB).
  • SIB system information block
  • a WTRU may be configured to perform a method that includes 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 of an NTN device.
  • the method may include determining location information associated with the WTRU.
  • the method may include sending a report that indicates the WTRU may be impacted by the power saving state based on the power sharing assistance information, the NTN assistance information, and/or the location information.
  • the power sharing assistance information may be, for example, one or more of an expected impact of power sharing state, an indication of an area impacted by the power sharing state, a start time of the power sharing state, or a duration of the power sharing state.
  • the report may include, for example, an indication of one or more of an estimated duration of the expected impact of power sharing state, a downlink (DL) coverage reduction, or whether the WTRU will remain in connection with the NTN device.
  • DL downlink
  • the indication of an area impacted by the power sharing state may include, for example, an explicit area description via reference point and radius or a synchronization signal block (SSB) index.
  • the expected impact of power sharing state may include, for example, a percent reduction in radiated power density.
  • the power sharing assistance information may include, for example, a flag enabling pre-reporting and/or an indication to include additional assistance information in the report.
  • Additional assistance information may include, for example, a predicted magnitude of a DL coverage loss, information needed to access a non-terrestrial cell, and/or power sharing assistance information for one or more non-terrestrial cells which are currently serving an area.
  • the method may include receiving one of more revised modulation and coding scheme (MCS).
  • MCS modulation and coding scheme
  • the method may include receiving a downlink (DL) using the revised MCS.
  • the method may include receiving one of more revised downlink (DL) coverage enhancements.
  • the method may include receiving a DL transmission using the DL coverage enhancements.
  • the method may include suspending transmission to the NTN device for a duration of the power saving state.
  • the method may include reverting to an original DL coverage configuration upon completion of the power sharing state.
  • the NTN assistance information may include, for example, one or more of cell reference point, cell radius, or satellite ephemeris.
  • the NTN assistance information may be acquired via a system information block (SIB).
  • SIB system information block
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • RAN radio access network
  • CN core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • FIG. 2 is a system diagram illustrating different interfaces in a non-terrestrial network (NTN).
  • NTN non-terrestrial network
  • FIG. 3 is a diagram depicting example beam power sharing scenarios in NTNs.
  • FIG. 4 is a diagram illustrating example network assistance information providing current and future power sharing states with associated applicability times.
  • FIG. 5 is a system diagram illustrating example power sharing impact estimation and conditional downlink (DL) coverage enhancement.
  • FIG. 6 is a diagram illustrating example power sharing impact post evaluation and reporting.
  • FIG. 7 is a system diagram illustrating example network (NW) polling of power sharing impact to idle/inactive WTRUs.
  • NW network
  • FIG. 8 is a diagram illustrating an example pre-configuration handling under power sharing.
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a CN 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the I nternet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
  • a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • the air interface 116 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like.
  • the base station 114a in the RAN 104/113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., a eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • the RAN 104/113 and/or the CN 106/115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104/113 or a different RAT.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include 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 source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the 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.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 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, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the 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 either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C 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 are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11 e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine- Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 113 may also be in communication with the CN 115.
  • the RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment.
  • the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D 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. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184, 184b may 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, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the 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 in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • Non-terrestrial networks facilitate deployment of wireless networks in areas where land- based antennas may be impractical, such as due to geography or cost.
  • Current standard NTN deployments support basic talk and text anywhere in the world.
  • future releases coupled with proliferation of nextgeneration low-orbit satellites may enable enhanced services such as web browsing.
  • a basic NTN consists of an aerial or space-borne platform which, via a gateway (GW), transports signals from a land-based based gNB to a WTRU and vice-versa.
  • NTN supports power class 3 UE with omnidirectional antenna and linear polarization, or a very small aperture antenna (VSAT) terminal with directive antenna and circular polarization.
  • VSAT very small aperture antenna
  • Power sharing impact estimation and conditional DL coverage enhancement may be implemented.
  • a WTRU may calculate if and/or when a WTRU may be impacted by a future NW power saving state via network assistance information and WTRU characteristics (e.g., WTRU location, speed, etc.).
  • the WTRU may report the periods of impact and may report the estimated degree of impact to the NW.
  • the WTRU may be preconfigured with DL coverage enhancements to apply once the WTRU enters the region and/or time where it may be impacted by the changes to DL coverage.
  • Power sharing impact post evaluation and reporting may be implemented.
  • a WTRU may measure the RSRP in a time period both before and/or after the power sharing state activation.
  • the WTRU may be configured with a new event, where if the DL coverage drops from time T1 (pre-power sharing state) to T2 (post-power sharing state) by a configured threshold the WTRU may report the RSRP measurements.
  • Network polling for RRCJDLE/INACTIVE WTRU may be implemented.
  • An I DLE/I NACTI VE WTRU may be polled to provide feedback of an anticipated power share state activation by reception of a paging message.
  • the WTRU may receive power sharing state assistance information and may determine whether it will be impacted.
  • the WTRU may determine dedicated preambles and reporting conditions to indicate the severity of the impact (e.g., Preamble A: WTRU expects to entirely lose coverage and/or Preamble B: WTRU expects to be impacted).
  • the network may respond with Random Access Response (RAR) and/or an UL grant requesting for additional assistance information (e.g., the duration of the coverage impact and/or the predicted magnitude of the DL coverage loss).
  • RAR Random Access Response
  • Pre-configuration handling under beam power sharing may be implemented.
  • a WTRU may receive power sharing state assistance information for neighboring cells and/or satellites.
  • the WTRU may determine whether one or more neighboring cells impacted by a power sharing decision is a Layer 1 /Layer 2 (L1/L2) Triggered Mobility (LTM) and/or Conditional Handover (CHO) candidate.
  • L1/L2 Layer 1 /Layer 2
  • LTM Triggered Mobility
  • CHO Conditional Handover
  • the WTRU may suspend (and/or bias against triggering) the configuration to the LTM and/or CHO candidate for the duration of the power saving state to avoid a handover to a cell which will experience poor coverage.
  • Aerial or space-borne platforms are classified in terms of orbit. Current standardization focuses on low-earth orbit (LEO) satellites with altitude range of 300 - 1500 km and geostationary earth orbit (GEO) satellites with altitude at 35786 km. Other platform classifications, for example medium-earth orbit (MEO) satellites are defined as having an altitude range of 7000 - 25000 km and high-altitude platform stations (HAPS) with altitude of 8 - 50 km, are assumed to be implicitly supported. Satellite platforms are further classified as having a “transparent” or “regenerative” payload. Transparent satellite payloads implement frequency conversion and RF amplification in both uplink and downlink, with multiple transparent satellites possibly connected to one land-based gNB. Regenerative satellite payloads can implement either a full gNB or gNB DU onboard the satellite. Regenerative payloads may perform digital processing on the signal including demodulation, decoding, re-encoding, re-modulation and/or filtering.
  • LEO low
  • FIG. 2 depicts example interfaces in a NTN.
  • a feeder-link may include a wireless link between the GW and satellite.
  • a service link may include a radio link between the satellite and WTRU.
  • An inter-satellite Link may include a transport link between satellites. The ISL may be supported (e.g., supported only) by regenerative payloads and may be a 3GPP radio or proprietary optical interface.
  • the NR-Uu radio interface may be used for both the service link and feeder-link.
  • the NR-Uu interface may be used on the service link, and a satellite radio interface (SRI) may be used for the feeder-link.
  • SRI satellite radio interface
  • a detailed UP/CP protocol stack may be used for a transparent payload configuration.
  • An NTN satellite can support multiple cells, where each cell comprises one or more satellite beams. Satellite beams cover a footprint on earth (like a terrestrial cell) and can range in diameter. For example, a 100 - 1000 km in LEO deployments or a 200 - 3500 km diameter in GEO deployments. Beam footprints in GEO deployments remain fixed relative to earth, and in LEO deployments the area covered by a beam/cell changes over time due to satellite movement. This beam movement can be classified as “earth moving” where the LEO beam moves continuously across the earth, or “earth fixed” where the beam is steered to remain covering a fixed location until a new cell overtakes the coverage area in a discrete and coordinated change.
  • RTT round-trip time
  • GEO 541.46 ms
  • the RTT of a regenerative payload is approximately half that of a transparent payload, as a transparent configuration consists of both the service and feeder links, whereas the RTT of a regenerative payload considers the service link only.
  • a WTRU may perform timing pre-compensation.
  • NTNs may support one or more of the following: support for regenerative payload, DL coverage enhancements, WTRU without Global navigation Satellite System (GNSS), Multi-Connectivity, RedCap over NTN, Support for Store and Forward, Discontinuous Coverage enhancements, mobility enhancements, and more.
  • GNSS Global navigation Satellite System
  • support for regenerative payload may include different architectures such as full gNB on board, Centralized Unit-Distributed Unit (CU-DU) split, and support for inter-satellite links.
  • CU-DU Centralized Unit-Distributed Unit
  • DL coverage enhancements may include enhanced DL coverage to address reduced Equivalent Isotropic Radiated Power (EIRP) density and/or power density due to satellite power limitations.
  • the DL coverage enhancements may include identification of channels to be enhanced and candidate enhancements.
  • a “pre-paging” notification/alert may be defined for near or non-line of sight (NLOS) WTRUs experiencing continuous paging failure.
  • NTNs may support WTRUs without access to GNSS services, including enhancements to Random Access Channel (RACH) and time/frequency synchronization procedures.
  • RACH Random Access Channel
  • Multi-Connectivity may be provided, for example, including dual connectivity between satellites and intra-satellite carrier aggregation.
  • NTNs may support reduced capability devices, specifically support for half-duplex frequency division duplex (HD-FDD) Reduced Capacity (RedCap) WTRUs which can have issues due to large and open-loop TA, identification of missing RRM requirements, and/or DL coverage requirements.
  • HD-FDD half-duplex frequency division duplex
  • RedCap Reduced Capacity
  • NTNs may support Store and Forward. Introduction of support for discontinuous feeder-link may be provided, for example, using SA2 conclusions and regenerative architecture as baseline.
  • Discontinuous Coverage enhancements e.g., introduction of discontinuous coverage support for NR
  • LoT internet of things
  • Mobility enhancements may be provided, for example, including enhanced TN/NTN interworking, group-based HO, and NTN/NTN interworking between orbits.
  • Other topics may include, for example, support for MBS.
  • Other topics may include expansion of RAT-dependent positioning in NTN.
  • Other topics may include IAB support in NTN.
  • Other topics may include support for high-power (PC2) WTRUs.
  • Other topics may include beam-level polarization indication and/or beam hopping mechanisms.
  • Other topics may include co-existence between TN and NTN.
  • EIRP may be a satellite parameter, and has been used in DL coverage evaluations.
  • the DL parameter set doesn’t properly account for power limitations onboard a satellite, and for some satellites with many beams (e.g., 1200) the satellite power must be shared between beams. This solution may result in lower EIRP density per beam and worse DL coverage than originally expected.
  • beam power sharing is to split the power between different beams, referred to herein as “beam power sharing”.
  • FIG. 3 depicts several example beam power sharing scenarios in NTNs.
  • full power may be allocated across one or more (e.g., all) beams.
  • allocating full power across one or more (e.g., all) beams may not be practical for some deployments considering power limitations on satellite.
  • power sharing across one or more (e.g., all) beams may be performed. Power sharing across one or more (e.g., all) beams may result in worse DL coverage.
  • turning off parts of the cell may allow full power on some beams and not others, providing coverage in some areas of the cell at the expense of others.
  • a combination of power sharing and turning off may allow for a flexible deployment where power can be distributed between beams anywhere between full power and fully turned off.
  • Turning off parts of the cell may introduce coverage gaps within a cell not currently addressed in the non-terrestrial networks feature. Considering the size of NTN cells can cause WTRUs to be clustered in certain areas (e.g., cities, towns, on ground) where power is likely to be concentrated, and large areas with no WTRUs at all (e.g., Oceans) where power is likely to be reduced.
  • Methods and systems are provided to ensure that a WTRU remains reachable and/or can maintain a connection if the network enables power sharing between beams reducing DL coverage, including turning off coverage to parts of a cell.
  • Power sharing decisions may be deterministic and may be controlled by the network. Assistance information may allow estimation of impact DL coverage and advanced actions to mitigate potential coverage issues. A reduction in EIRP density may not correspond one-to-one to a reduction in DL coverage. Any estimated impact may require confirmation by measurements. Beam power sharing may cause certain beams to be illuminated at different times, which can be partially mitigated by system-level solutions.
  • beam power sharing refers to a reduction in EIRP density of a beam due to power limitations on a satellite.
  • beam power sharing state describes the current power allocated to a beam, and may range from full power, to being completely turned off.
  • coverage state describes the quality of DL coverage based on the beam power sharing state of the current beam.
  • Some material described in this specification may 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 to a reduction in DL coverage; Beam power sharing can cause certain beams are illuminated at different times; Beam power sharing can range from full power to no power at all; A cell may consist of one or more beams, and each beam may be in a different coverage state; Configurations or Pre-configurations which are provided to compensate for a drop in DL coverage frequently mention revised parameters (e.g., MCS, power, repetition, frequency hopping, MIMO, or other configurations to support improved reception).
  • Non-terrestrial network may be an exemplary scenario, however some embodiments may also apply to other scenarios such as terrestrial networks using network energy saving, etc.
  • Benefits common to the solutions described herein include fast adaptation to DL coverage reduction due to satellite beam power sharing, which can reduce possible service interruption and Radio Link Failure (RLF).
  • RLF Radio Link Failure
  • Implementation of the solutions described herein may provide significant benefits over existing technologies. For example, WTRUs may immediately react to a drop in DL coverage by applying a more suitable reconfiguration, reducing the risk of RLF. This is especially important in NTN, where the large signaling delay can introduce significant delays in addressing coverage issues.
  • the network can factor in estimated impact and duration of impact to WTRUs when making future beam power sharing decision.
  • congestion due to large scale measurement reporting is reduced as reporting is limited only to those WTRUs most affected by the beam power sharing decision.
  • the network is able to determine/consider the impact to I DLE/I NACTI VE WTRUs when making beam power sharing decisions, which likely represents the majority of the total WTRUs served by nonterrestrial networks.
  • the WTRU may avoid handing over to a cell which may not be suitable in the near future, avoiding possible RLF or service interruption due to a subsequent mobility event.
  • the network may provide assistance information about the current and/or future power sharing state of a beam/cell/area, herein referred to as “power sharing assistance information”.
  • the power sharing assistance information may include, for example, one or more of the following aspects: Power sharing state, description of impacted area, timing of power sharing state, neighboring and/or upcoming assistance information, broadcast power sharing assistance information, dedicated power sharing assistance information, group power sharing assistance information, additional assistance information for WTRU moving from terrestrial to non-terrestrial networks, and additional assistance information for WTRU moving from non-terrestrial to terrestrial networks.
  • the power sharing assistance information may include the power sharing state of a specific area of coverage, which can represent the power and/or portion of power allocated to the beam/cell serving the area.
  • the power sharing state may be represented, for example: by an explicit value (e.g., the EIRP density); an index within a pre-determined or pre-configured range of values; a percentage of the maximum power allocation (e.g., 50% of maximum power); an offset from a reference value (e.g., plus-or-minus X from a provided reference value).
  • the beam power sharing state may range from full power (e.g., the maximum supported EIRP density) to no power allocated.
  • the beam power sharing state may include information about the current power sharing state, past power sharing state, and/or the future state of the beam/cell.
  • the power sharing assistance information may include a description of impacted area.
  • the power sharing assistance information can be associated with a specific area like the satellite coverage footprint or a subsection of the satellite coverage.
  • the power sharing assistance information may be specific to one or more of: a beam or group of beams (e.g., via a beam index), a cell or group of cells, a geographic area (e.g., described via a reference signal + radius), a tracking area and or Radio Access Area (RAN) Notification Area (RNA), a Public Land Mobile Network (PLMN), or a country or specific geopolitical area. Examples may refer to “beam”, “cell” or “area”, however this may be interchanged equally with any of the above.
  • the power sharing assistance information may have information associated with when the information is applicable (e.g., the timing of power sharing state).
  • the time of applicability can be a current time and or time range, and/or be associated with some future time.
  • the power sharing state may be associated with one or more pre-existing pieces of information, such as the satellite epoch time. If no time is provided this may assume that the current power sharing state will remain for some undetermined time.
  • the time may be provided as an explicit time, time range, or time plus duration.
  • FIG. 4 depicts example network assistance information providing current and future power sharing state with associated applicability time.
  • the WTRU may provide power sharing assistance information and associated times of validity for the current and future time periods of the area associated with the power sharing assistance information, as described in FIG. 4.
  • the network may provide one or more of the following pieces of information to indicate the validity time of the power sharing assistance information: the time a power sharing state is starting (e.g., the past, current value or future time); the time the power sharing state is ending; a time duration the power sharing state is applicable; and/or the duration of a power sharing state.
  • the power sharing information may be provided on a one-time basis or may be associated with a periodicity.
  • the power sharing state may be associated with a start time, on-duration, and periodicity, where the power sharing state is considered as valid from the start time to the start time plus duration and restarting after each periodicity.
  • the power sharing assistance information may include neighboring and/or upcoming assistance information.
  • the power sharing assistance information may contain information for the current serving area (e.g., current beam and/or cell).
  • the power sharing assistance information may also include information (e.g., power sharing state, timing information, impacted area etc.) about one or more neighboring areas. This may include, for example, the area served by other beams of the same cell, other cells originating from the same satellite, or areas served by other satellites.
  • the power sharing assistance information may include broadcast power sharing assistance information.
  • the power sharing assistance information may be provided in a broadcast manner, for example, via system information.
  • the power sharing assistance information can be carried in an existing system information block (SIB), or via a newly defined SIB.
  • SIB system information block
  • the WTRU may only acquire updated system information for power sharing assistance information in certain circumstances.
  • the WTRU may acquire power sharing assistance information in one or more of the following circumstances: the power sharing assistance information (e.g., such as beam state) has changed from the previously stored/acquired version (e.g., via reception of a flag in system information); a validity condition associated with the assistance information has expired or is about to expire; an explicit indication from the network has been received by the WTRU (e.g., an activation command); based on a (re)configuration (e.g., the network has configured the WTRU to perform one or more actions which require power sharing assistance information); the WTRU performs cell (re)selection; or the WTRU performs mobility (e.g., the WTRU receives an RRC Reconfiguration message).
  • the power sharing assistance information e.g., such as beam state
  • the WTRU performs cell (re)selection
  • mobility e.g., the WTRU receives an RRC Reconfiguration message
  • the power sharing assistance information may include dedicated power sharing assistance information.
  • the WTRU may also be provided with power sharing assistance information via dedicated signaling (e.g., via RRC, MAC CE, PDSCH, PDCCH, MSGB, MSG2/MSG4). This information may be received based on WTRU request and/or coupled with activation or configuration of a procedure which requires power sharing assistance information (e.g., described below within this document).
  • the WTRU may acquire a default power sharing assistance information via system information, which may be complemented by additional power sharing assistance information provided via dedicated signaling.
  • the WTRU may take several actions. For example, the WTRU may overwrite any broadcast information with dedicated information. In another example, the WTRU may maintain the most recent information, regardless of how the information was provided (e.g., via dedicated or broadcast signaling).
  • the power sharing assistance information may include group power sharing assistance information.
  • the network may only update the power sharing assistance information for a portion of cell, wherein only the WTRUs served within that cell portion (e.g., beam) will be affected.
  • the WTRU may be provided with a group Radio Network Temporary Identifier (RNTI) associated with the coverage area.
  • RNTI Radio Network Temporary Identifier
  • the WTRU may monitor for a notification using the group RNTI, and upon reception, and upon reception of a notification addressed to the group RNTI, the WTRU may update (and/or receive updated) power sharing assistance information.
  • the power sharing assistance information may be associated with one or more expiry conditions, where if one or more of the associated expiry conditions is satisfied the WTRU may consider the power sharing assistance information as not valid.
  • the WTRU may be configured with one or more of the following expiry conditions: Upon reaching a specific time (e.g., the epoch time), at the end of a time duration or offset, based on satisfaction of a condition, upon notification that the power sharing assistance 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.
  • a specific time e.g., the epoch time
  • the WTRU may be configured with one or more of the following expiry conditions: Upon reaching a specific time (e.g., the epoch time), at the end of a time duration or offset, based on satisfaction of a condition, upon notification that the
  • An example of an end of time duration or offset that may be an expiry condition is if the WTRU acquired power sharing assistance information which can be the beginning of the time duration. At the end of the time duration (or at a fixed offset from the time), the WTRU may consider the power saving assistance information as expired. The duration and/or the time offset may be provided to the WTRU along with the power sharing assistance information. This may be maintained, for example, via a WTRU timer. [0136] Based on satisfaction of a condition may also be an expiry condition. For example, the WTRU may set the WTRU location at the time of power sharing assistance information acquisition as the reference location. If the WTRU has moved more than a configured threshold, then the WTRU can consider the power sharing assistance information as expired.
  • the distance threshold may be provided to the WTRU along with the power sharing assistance information.
  • Expiry conditions may be based on (re)configuration. For example, the network may disable or deactivate a procedure which requires power sharing assistance information. Upon reception of this reconfiguration, the WTRU may consider power sharing assistance information as expired.
  • Expiry conditions may be based on a mobility action (e.g., including cell (re)selection).
  • the WTRU may camp on or connect to a cell which does not support power sharing assistance information.
  • the WTRU may detect that a cell does not support power sharing based on, for example and explicit indication (e.g., a flag in system information) or implicitly (e.g., the cell does not broadcast power sharing assistance information).
  • Release from the network may also comprise an expiry condition.
  • the WTRU may consider stored power sharing assistance information as expired upon being released to RRC INACTIVE state (e.g., upon reception of an RRCRelease with suspend indication) or upon being release to RRC IDLE state (e.g., upon reception of an RRCRelease message).
  • the WTRU may use the power sharing assistance information for as long as it is considered valid (e.g., one or more of the above associated expiry condition(s) has not been met). If the power sharing assistance information is considered not valid, the WTRU may or may not update power sharing assistance information (e.g., re-acquire SIB), or notify the network (e.g., transmit an indication/notification that power sharing assistance information is no longer valid). Additionally or alternatively, the WTRU may attempt to update power sharing assistance information prior to satisfaction of an expiry condition (e.g., while the power sharing assistance information is still considered valid).
  • power sharing assistance information e.g., re-acquire SIB
  • the WTRU may reset the associated expiry conditions (e.g., update any reference points associated with distance thresholds, reset associated validity timers etc.).
  • the WTRU may notify the network that it has updated power sharing assistance information.
  • the WTRU may be provided with additional power sharing assistance information if it is transitioning between different network types (e.g., between terrestrial and non-terrestrial networks, and/or between non-terrestrial networks of different orbits/altitudes).
  • different network types e.g., between terrestrial and non-terrestrial networks, and/or between non-terrestrial networks of different orbits/altitudes.
  • Additional assistance information may be included for a WTRU moving from terrestrial to nonterrestrial networks (e.g., connect to).
  • the WTRU may be provided with this information, for example, because the terrestrial cell is entering a network energy saving (NES) state which can no longer serve the WTRU.
  • the WTRU may be provided, by the terrestrial cell, one or more of the following: information needed to access a non-terrestrial cell (e.g., time/frequency compensation information) for one or more NTN cells which are current serving the area; or power sharing assistance information for one or more nonterrestrial cells which are currently serving the area.
  • Additional assistance information for WTRU moving from non-terrestrial to terrestrial networks may be provided.
  • a WTRU served by a non-terrestrial network may be provided with additional assistance information to transition (e.g., connect to) a terrestrial network.
  • the network may include additional information about the network energy saving (NES) state of cells associated with each terrestrial network.
  • NES network energy saving
  • Such assistance information can include one or more of, for example: whether a terrestrial cell is in an NES state, whether a terrestrial cell is about to enter or exit an NES state, or the percentage of terrestrial cells within a given area that are in an NES state.
  • WTRU determination of coverage state plus duration may be implemented.
  • the WTRU may (e.g., upon acquisition of power sharing assistance information) estimate and report the impact of power sharing to, for example, the coverage characteristics.
  • the term “power sharing decision” referred to within this section refers to a current or future power sharing action (e.g., a change in power sharing state as previously described) which the network may undertake and inform the WTRU of via power sharing assistance information.
  • the WTRU may estimate that it will be impacted by a power sharing decision.
  • the estimation may be based on, for example, the power sharing assistance information and/or one or more other characteristics of the satellite such as: assistance information to determine the trajectory of the satellite/cell like the satellite ephemeris data (e.g., the satellite location, direction, speed, or orbital information); a cell and/or beam reference point; assistance information to determine the trajectory of the satellite reference point (e.g., if the satellite deployment uses earth-moving beams; satellite footprint information (e.g., the satellite footprint diameter, cell footprint diameter and/or beam footprint diameter); the beam configuration for a cell and/or satellite (e.g., the total number of beams on a satellite, the number of beams within a cell, the pattern of beams within a cell, the polarization characteristics of a beam); or power characteristics of a satellite (e.g., the EIRP density per beam, the total power available to a satellite etc.).
  • Similar information may also be provided for a neighboring satellite/cell/beam and/or upcoming satellite/cell/beam, which the WTRU may use to estimate the impact of a future power sharing decision.
  • the WTRU may also use one or more WTRU characteristics to evaluate the coverage state.
  • the WTRU may use on or more of the following: the WTRU location information (e.g., GNSS position); information about the WTRU movement (e.g., WTRU speed, direction); WTRU receiver characteristics (e.g., antenna characteristics like number of antennas, beamforming capability, whether the antenna is omnidirectional or directive etc.); or WTRU power characteristics (e.g., WTRU power class).
  • Assistance information may also include coverage state determination.
  • the WTRU may use one or more pieces of assistance information (e.g., power sharing assistance information or other information described above) to determine whether the WTRU will be impacted by a power sharing decision.
  • Assistance information may also comprise power sharing impact determination based on WTRU calculation.
  • the WTRU may determine whether it is currently located in area impacted by power sharing using the power sharing assistance information. For example, the WTRU may acquire the power sharing assistance information indicating the power sharing state of different areas of the cell. The WTRU may then acquire its own location information and may determine if it is located within an area of cell coverage which is experiencing reduced coverage due to power sharing.
  • the WTRU may determine it is within an area undergoing power sharing, for example, via one or more of the following methods: the WTRU is served by a beam/cell/satellite which is described as undergoing power sharing; or the WTRU is located within an area described within the power sharing assistance information (e.g., the WTRU distance between a reference point is less than the described radius, the WTRU is located within a range of longitude/latitude, the WTRU is located within an explicitly described polygonal area etc.).
  • the WTRU is served by a beam/cell/satellite which is described as undergoing power sharing
  • the WTRU is located within an area described within the power sharing assistance information (e.g., the WTRU distance between a reference point is less than the described radius, the WTRU is located within a range of longitude/latitude, the WTRU is located within an explicitly described polygonal area etc.).
  • the WTRU may determine whether it will be located in an area which will be impacted by a future power sharing decision. For example, the WTRU may acquire the power sharing assistance information indicating the power sharing state of different areas within the cell and the associated timing of the power sharing state (e.g., when the power sharing state will be activated and for how long the power sharing state will occur). The WTRU may acquire its location information and determine if it is located within an area impact by a future power sharing decision, and potentially characteristics of when it will be impacted by the power sharing decision (e.g., the start time and duration of impact).
  • the power sharing assistance information indicating the power sharing state of different areas within the cell and the associated timing of the power sharing state (e.g., when the power sharing state will be activated and for how long the power sharing state will occur).
  • the WTRU may acquire its location information and determine if it is located within an area impact by a future power sharing decision, and potentially characteristics of when it will be impacted by the power sharing decision (e.g., the start time and
  • the WTRU may also factor in satellite movement when determining whether the WTRU will be impacted by a future power sharing decision. For example, in addition to acquiring the power sharing assistance information the WTRU may acquire additional information (e.g., via SIB reception) to determine the trajectory of the cell such as the satellite ephemeris data, cell footprint information, and one or more cell reference point(s). The WTRU may acquire its own location and, via the trajectory information, determine the series of upcoming cell (s) or area(s) which will serve the WTRU location in the future. The WTRU may then determine if these upcoming areas are associated with a future power sharing decision. The WTRU may determine the duration of impact factoring in both the duration the WTRU will be within the coverage area and the duration of the power sharing decision.
  • additional information e.g., via SIB reception
  • the WTRU may acquire its own location and, via the trajectory information, determine the series of upcoming cell (s) or area(s) which will serve the WTRU location in the future
  • the WTRU may assess the impact of neighboring power sharing decisions in a similar manner as described above, however via acquisition of the power sharing assistance information for neighboring cells/beams/satellites.
  • Assistance information may also include power sharing impact determination based on the Network.
  • the network may indicate that one or more WTRUs will be affected by a power sharing decision.
  • the network may send a dedicated message (e.g., via RRC or MAC CE) information the WTRU it will be impacted by a power sharing decision, optionally including additional assistance information such as power sharing state information and timing of power sharing decision.
  • additional assistance information such as power sharing state information and timing of power sharing decision.
  • Such information may also be group cast to a set of WTRUs, which the WTRU may monitor via a dedicated group RNTI.
  • Beam power sharing is not currently supported in NTN and fluctuation in DL coverage is due to pseudo-random variation in channel conditions.
  • Adjustments are made reactively (e.g., based on measurement reporting), possibly risking the connection if not detected and/or corrected early enough.
  • Power sharing among satellite beams can result in dynamic DL coverage conditions, impacting WTRU performance.
  • Providing network assistance information that pertains to the current or planned power saving state can enable the WTRU to understand how DL coverage will change in the future.
  • the network could provide power saving state assistance information for one or more neighboring cells and/or satellites allowing WTRU to predict possible impacts in DL coverage. This can support pre-provisioning of contingencies (e.g., more conservative MCS, PDCCH repetition etc.) to avoid losing WTRU connection.
  • Power sharing impact estimation and conditional DL coverage enhancement may be provided.
  • a network may be aware of beam power sharing decisions ahead of time and can share assistance information about decisions.
  • WTRU calculates if and/or when WTRU will be impacted by future NW power saving state via network assistance information and WTRU characteristics (e.g., WTRU location, speed, etc.). Further, a WTRU may report the periods of impact and optionally the estimated degree of impact to the NW, and WTRU can be preconfigured with DL coverage enhancements to apply once WTRU enters the region and/or time where it will be impacted by the changes to DL coverage. This may allow WTRUs to immediately react to a drop in DL coverage by applying a more suitable pre-configuration, reducing the risk of RLF.
  • a WTRU may acquire power sharing assistance information (e.g., via SI) indicating the upcoming power sharing state of the cell.
  • the upcoming power sharing state of the cell may include one or more of an expected impact of power sharing state (e.g., % reduction in EIRP density), an area impacted by power sharing (e.g., explicit area description via reference point and radius, SSB index), a start time of power sharing state (e.g., UTC time), a duration of beam power sharing state (e.g., 10s), or a configuration for WTRUs to pre-report if there is an issue (e.g., a flag enabling pre-reporting, an indication to include additional assistance information etc.).
  • an expected impact of power sharing state e.g., % reduction in EIRP density
  • an area impacted by power sharing e.g., explicit area description via reference point and radius, SSB index
  • a start time of power sharing state e.g., UTC time
  • a duration of beam power sharing state e.g. 10s
  • a configuration for WTRUs to pre-report if there is an issue
  • the WTRU may acquire NTN assistance information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris).
  • the WTRU may acquire its location and calculates if/when the WTRU will be impacted by the power saving state, including the time and duration of impact.
  • the WTRU may determine the start time and/or duration of impact via beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics. If prereporting is enabled and the WTRU is impacted by beam power sharing, the WTRU may pre-report that it will be impacted by the power sharing plan.
  • the WTRU may indicate the estimated duration, DL coverage reduction, and/or whether it anticipates the ability to maintain connection.
  • the WTRU may receive a revised MCS and/or additional ULDL coverage enhancements (e.g., PDCCH/PDSCH repetition, etc.) to apply at the time of power sharing state activation.
  • the WTRU may apply the revised MCS and/or UL/DL coverage enhancement techniques.
  • the WTRU may revert to the original DL coverage configuration (e.g., original MCS, repetition number, etc.).
  • the WTRU may perform several configurations of power sharing impact pre-reporting or coverage enhancements.
  • Power sharing impact pre-reporting may refer to a WTRU configured to pre-report the potential impact of power sharing state, or a NW including triggering conditions for a WTRU to transmit the power sharing impact pre-report.
  • a WTRU may be configured to pre-report the potential impact of power sharing state.
  • the configuration may include a configuration to enable/disable power sharing impact pre-reporting, a configuration to report one or more prices of assistance information (e.g., as described herein); one or more resources (e.g., an UL grant or transmission occasions) to transmit a power sharing pre-report, or whether the WTRU may trigger an SR if resources are not available to transmit a power sharing pre-report.
  • the network may include one or more triggering conditions for a WTRU to transmit the power sharing impact pre-report.
  • the one or more triggering conditions may include one or more of upon reception of a network request, the WTRU determining the WTRU will be impacted by a power sharing state, the WTRU determining the WTRU will be impacted by a future power sharing state, the WTRU determining the WTRU will be impacted by the power sharing state of a neighboring cell, or the estimated impact of power sharing drops the coverage by a configured threshold.
  • the power sharing impact pre-report may include one or more of whether the WTRU is currently impacted by a power sharing state, when the WTRU will stop being impacted by a current power sharing state, the current WTRU location, whether the WTRU will be impacted by a future power sharing state, one or more future time range(s) that a WTRU will be indicated by a power sharing state, the SSB index or cell identifier (e.g., PCI) associated with the area of the WTRU, the estimated drop in DL coverage resulting from a power sharing decision, whether the WTRU will lose coverage entirely, or whether the WTRU has an alternative.
  • the SSB index or cell identifier e.g., PCI
  • a WTRU may transmit the power sharing impact pre-report via RRC, MAC CE, PUSCH, RACH (e.g., MSGA, MSG3, MSG5), and/or PUCCH signaling. If the WTRU does not have resources available to transmit the power sharing impact pre-report, the WTRU may trigger an SR to acquire resources.
  • a WTRU may receive a configuration to enhance DL coverage in reaction to a power sharing state activation (or in response to a pre-reported estimate of the power sharing impact).
  • the configuration may consist of DL coverage enhancement(s) and associated conditions to apply the DL coverage enhancements.
  • the enhanced DL coverage may include an alternative MCS (e.g., a more conservative MCS) and/or additional repetitions (e.g., PDSCH or PDCCH repetitions).
  • the WTRU may apply the DL coverage enhancements indefinitely, or subject to a preconfigured duration. For example, a WTRU may apply a more conservative coverage configuration for one or more of the following durations: for the duration of a power sharing state, for X number of power sharing states, for a time period (e.g., UTC T1 to UTC T2, or a configured duration), while connected to the cell, and/or while connected to the satellite.
  • the WTRU may be triggered to apply and/or terminate DL coverage enhancements.
  • the WTRU may apply the DL coverage enhancements based on satisfaction of a condition or an event.
  • the WTRU may apply DL coverage enhancements based on one or more of upon reception (e.g., immediately upon reception) of the enhanced DL coverage configuration, based on reception of an explicit indication, upon activation of the power sharing state, a configured offset before (or alternatively after) the activation of the power sharing state, or conditionally (e.g., if the estimate (or measured) coverage after the power sharing state activation has dropped by a predetermined amount of dB).
  • the WTRU may suspend, revert to the default (e.g., original) configuration, or not apply the DL coverage enhancements based on one or more of the following: based on explicit indication, once the power sharing state has concluded, some offset after power sharing state has concluded, or conditionally (e.g., when the DL coverage has improved by a predetermined amount of dB and/or during a particular time period (e.g., from time T 1 to T2)). If the beam, cell, and/or satellite power sharing assistance indicates that the power will be completely turned off, the WTRU may not apply coverage enhancements and instead the WTRU may suspend transmission entirely.
  • the beam, cell, and/or satellite power sharing assistance indicates that the power will be completely turned off
  • FIG. 5 illustrates an example power sharing impact estimation and conditional DL coverage enhancement.
  • the WTRU may calculate if and/or when the WTRU will be impacted by future NW power saving state via network assistance information and WTRU characteristics (e.g., WTRU location, speed, etc.).
  • the WTRU may report the periods the WTRU will be impacted by power sharing and/or the estimated degree of impact to the NW.
  • the WTRU may receive one or more pre-configured DL coverage enhancements to apply once the WTRU enters a region/time where the WTRU will be impacted by power sharing decision.
  • the WTRU may perform one or more of the following to support power sharing impact estimation and conditional DL coverage enhancement.
  • the WTRU may receive power sharing assistance information, for example, from a gNB.
  • the WTRU may receive NTN assistance information (e.g., used to determine cell characteristics such as cell reference point, cell radius, or satellite ephemeris), for example, from the gNB.
  • the WTRU may determine its location and/or may estimate the impact of a power sharing.
  • the WTRU may pre-report the estimated impact of the power sharing.
  • the network e.g., the gNB
  • the network may determine a revised configuration with enhanced DL coverage based on the estimated impact indicated in the pre-report.
  • the WTRU may receive a preconfiguration for DL coverage enhancements from the network (e.g., the gNB).
  • the WTRU may apply the DL coverage enhancements indicated in the pre-config uration for DL coverage enhancements.
  • the WTRU may revert to the original DL coverage configuration (e.g., original MCS, repetition number, etc.).
  • the WTRU may receive power sharing assistance information (e.g., via SI) indicating the upcoming power sharing state of the cell.
  • the power sharing assistance information may include one or more of an expected impact of power sharing state (e.g., % reduction in EIRP density), an area impacted by power sharing (e.g., explicit area description via reference point and radius, SSB index), a start time of power sharing state (e.g., UTC time), a duration of beam power sharing state (e.g., 10s), or a configuration for WTRUs to pre-report if there is an issue (e.g., a flag enabling pre-reporting, an indication to include additional assistance information etc.).
  • an expected impact of power sharing state e.g., % reduction in EIRP density
  • an area impacted by power sharing e.g., explicit area description via reference point and radius, SSB index
  • a start time of power sharing state e.g., UTC time
  • the WTRU may acquire NTN assistance information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, and/or satellite ephemeris).
  • cell characteristics e.g., cell reference point, cell radius, and/or satellite ephemeris
  • the WTRU may acquire its location and may calculate if and/or when the WTRU will be impacted by the power saving state.
  • the WTRU may determine the start time and/or duration of impact, for example, via beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics.
  • the WTRU may prereport that the WTRU will be impacted by the power sharing plan.
  • the WTRU may indicate an estimated duration of the impact, a DL coverage reduction of the impact, and/or whether the WTRU anticipates the ability to maintain connection.
  • the WTRU may receive a revised MCS and/or one or more additional UL/DL coverage enhancements (e.g., PDCCH/PDSCH repetition, etc.) to apply at the time of power sharing state activation.
  • the WTRU may apply the revised MCS and/or the one or more UL/DL coverage enhancements.
  • the WTRU may revert to the original DL coverage configuration (e.g., original MCS, repetition number, etc.).
  • the WTRU may receive one or more condition(s) which must be fulfilled prior to applying the preconfigured DL coverage enhancements, for example, to avoid the WTRU applying over-conservative DL coverage enhancements in case the impact of power sharing impact was overestimated.
  • the WTRU may apply (e.g., only apply) DL coverage enhancements if the pre-reported value was within a percentage tolerance of the actual impact to the WTRU.
  • the WTRU may report to the network if the WTRU does not apply the pre-configured coverage enhancements (e.g., to avoid a mis-synchronization with the network, or to be provided with revised coverage enhancements better suited to the actual impact).
  • Power sharing impact post evaluation and reporting may be implemented.
  • a WTRU may periodically perform one or more measurements and may detect coverage issues due to a power saving event, triggering a measurement report and subsequent reconfiguration. Unless reporting events are carefully configured, power sharing decisions may trigger one or more WTRUs to report measurements simultaneously causing congestion and RLF if the network cannot reconfigure severely impact WTRUs quickly enough. Due to the large cell size and number of WTRUs typically served by a non-terrestrial network, there may be a significant difference in how power sharing affects different WTRUs. The power sharing impact can be evaluated by configuring one or more (e.g., all) WTRUs (e.g., even those with little impact) to report measurements after power sharing activation which can lead to large signaling overhead and congestion at the time of power sharing.
  • the power sharing impact can be evaluated by configuring one or more (e.g., all) WTRUs (e.g., even those with little impact) to report measurements after power sharing activation which can lead to large signaling overhead and congestion at the time of power sharing.
  • a WTRU may be configured with a time-based measurement event, where if the DL coverage drops from a first time, T 1 (e.g., a pre-power sharing state) to a second time, T2 (e.g., a post-power sharing state) by a configured threshold the WTRU notifies the network.
  • T 1 e.g., a pre-power sharing state
  • T2 e.g., a post-power sharing state
  • congestion due to large scale measurement reporting may be reduced as reporting is limited to (e.g., only to) those WTRUs most affected by the beam power sharing decision.
  • a WTRU may receive a measurement configuration dedicated to assessing and/or reporting an impact of a power sharing state.
  • the measurement configuration may include dedicated measurement windows pre- and post- power sharing activation (e.g., to evaluate the change in RSRP due to power sharing), one or more additional measurement objects (e.g., to quickly assess the impact of the power sharing state), a measurement gap (e.g., to suspend UL/DL data to assess the impact of power sharing state), and/or one or more conditions to report that there is an issue with the power sharing state (e.g., if the serving cell RSRP drops by a first threshold T 1 after power sharing state activation).
  • the WTRU may reset the L3 measurement window.
  • the WTRU may apply the measurement configuration.
  • the WTRU may evaluate the pre-power sharing RSRP.
  • the WTRU continues applying the measurement configuration after power sharing activation.
  • the WTRU may reset the L3 measurement window and may evaluate the post-power sharing RSRP.
  • the WTRU may evaluate the one or more reporting conditions provided in the dedicated measurement configuration (e.g., to report issue with power sharing state). If the difference in RSRP pre- and post- power sharing exceeds the first threshold T1 (e.g., the RSRP reduction > T1) then the reporting condition is satisfied. If reporting conditions are satisfied, the WTRU may trigger a measurement report indicating that the WTRU is affected by power sharing.
  • T1 e.g., the RSRP reduction > T1
  • the WTRU may include additional assistance information (e.g., such as DL measurements pre/post the power sharing activation) in the measurement report. Additionally or alternatively, if the expected duration of the power saving state exceeds a predetermined time duration (e.g., 10s), the WTRU may trigger the measurement report.
  • the expected duration of the power saving state may be derived with NW assistance information on the power sharing state.
  • the WTRU may be configured (e.g., via RRC signaling) with a dedicated measurement configuration, which the network may use to evaluate the impact of the power sharing decision, and/or to ensure that WTRUs most impacted by the power sharing decision are able to trigger a measurement report.
  • the network may use the measurement report to determine the level of DL coverage enhancements that the WTRU needs (e.g., by comparing the RSRP of the cell pre and post power sharing activation).
  • the dedicated measurement configuration used to evaluate the impact of power sharing may include a configuration to evaluate the RSRP/RSRQ of a cell prior to power sharing, a configuration to evaluate the RSRP/RSRQ of a cell after power sharing, a configuration to trigger a measurement report (e.g., if the WTRU has been severely impacted by the power sharing decision, and/or a configuration of what to include in the measurement report (e.g., additional measurements to include).
  • the WTRU may be provided with one or more additional measurement objects (e.g., reference signals, CSI-RS, SSB, etc.) to evaluate the channel.
  • Reference signals may occur before and/or after the power sharing activation.
  • a WTRU may be provided with a measurement window to evaluate the RSRP/RSRQ of the channel. The measurement window may be defined before and/or after the power sharing activation.
  • the measurement window may be defined via one or more of the following, a set of absolute times (e.g., 10:20:35, 10:20:40 etc.) which may define the start and end of a measurement window, a duration and offset from a reference time (e.g., the power sharing activation time), a start time plus a duration (e.g., 10:20:35, 10s), or a start time and number N of measurements for which WTRU may consider the window complete upon performing N measurements after the start time. If a WTRU is provided a duration and offset from a reference time, the WTRU may start a first measurement window an offset before the reference time and may start a second measurement window an offset after a reference time.
  • a set of absolute times e.g., 10:20:35, 10:20:40 etc.
  • a duration and offset from a reference time e.g., the power sharing activation time
  • a start time plus a duration e.g., 10:20:35, 10
  • the WTRU may use (e.g., only use) measurements taken within the measurement window, for example, to evaluate the RSRP/RSRQ of the cell. For example, upon starting the measurement window, the WTRU may restart the L3 measurement window, and may accumulate measurements throughout the measurement window to evaluate the RSRP/RSRQ. At the end of the measurement window, the WTRU may store the averaged L3 RSRP/RSRQ measurement to be used for evaluation of the measurement reporting condition.
  • the WTRU may use (e.g., only use) measurements taken within the measurement window, for example, to evaluate the RSRP/RSRQ of the cell. For example, upon starting the measurement window, the WTRU may restart the L3 measurement window, and may accumulate measurements throughout the measurement window to evaluate the RSRP/RSRQ. At the end of the measurement window, the WTRU may store the averaged L3 RSRP/RSRQ measurement to be used for evaluation of the measurement reporting condition.
  • the WTRU may be provided with a measurement gap (e.g., in order to not waste transmissions which may not be successfully received based on poor DL coverage.)
  • the WTRU may start the measurement gap upon power sharing activation, and may end the measurement gap upon, for example, evaluation of the channel, satisfaction of the measurement reporting criteria, or reception of DL coverage enhancements. While the WTRU is within the measurement gap, the WTRU may not expect any DL data transmissions.
  • the WTRU may be provided with a measurement reporting configuration as part of the dedicated measurement configuration to evaluate the power sharing impact.
  • the WTRU may be configured with a measurement threshold Thresh- 1 . If the difference between the measurements taken before the power sharing activation and the measurements taken after the power sharing activation exceed the threshold, the WTRU may trigger a measurement report.
  • the threshold may measure, for example, the difference between the highest/lowest measurement taken within a period pre-post power sharing activation or may measure the difference between the average measurements.
  • the WTRU may be configured to include the measurement results taken before the power sharing activation, after the power sharing activation, or both.
  • the WTRU may perform measurements on the indicated measurement objects in the indicated times and may report the configured measurement quantities if the measurement reporting conditions are satisfied.
  • the WTRU may release the previous measurement configuration and continue with the new measurement configuration indefinitely.
  • the WTRU may maintain and/or store the current measurement configuration, and apply the new measurement temporarily (e.g., to evaluate the RSRP/RSRQ of the cell pre-/post- power sharing). Whether the WTRU stores or releases the original measurement configuration may be based on network indication or configuration (e.g., based on a configuration within the dedicated measurement configuration).
  • the 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.
  • the WTRU may revert to the original measurement configuration if the WTRU does not satisfy the reporting condition after the power sharing activation (e.g., the power sharing event did not severely impact the WTRU).
  • the WTRU may revert back to the original measurement configuration at any time in response to an explicit indication from the network.
  • FIG. 6 depicts an example power sharing impact post evaluation and reporting.
  • a WTRU may be provided with a dedicated measurement configuration to assess the impact of power sharing.
  • the dedicated measurement configuration may include a time-based measurement event, where if the DL coverage drops from a first time, T 1 (e.g., a pre-power sharing state) to a second time, T2 (e.g., a post-power sharing state) by a configured threshold the WTRU notifies the network.
  • T 1 e.g., a pre-power sharing state
  • T2 e.g., a post-power sharing state
  • the WTRU may evaluate the RSRP of the cell pre- and post- power sharing. If the reporting configuration is satisfied, the WTRU may report the measurements to the network and/or may indicate that the WTRU has been impacted (e.g., severely impacted) by the power sharing decision.
  • the WTRU may perform one or more operations to support power sharing state post evaluation and reporting.
  • a WTRU may receive a measurement configuration dedicated to assessing and/or reporting the impact of the power sharing state.
  • the measurement configuration may include dedicated measurement windows pre- and post- power sharing activation (e.g., to evaluate the change in RSRP due to power sharing), additional measurement objects (e.g., to quickly assess the impact of the power sharing state, a measurement gap (e.g., to suspend UL/DL data to assess the impact of power sharing state), and/or one or more conditions to report that there is an issue with the power sharing state (e.g., if the serving cell RSRP drops by a threshold T 1 after power sharing state activation).
  • dedicated measurement windows pre- and post- power sharing activation e.g., to evaluate the change in RSRP due to power sharing
  • additional measurement objects e.g., to quickly assess the impact of the power sharing state
  • a measurement gap e.g., to suspend UL/DL data to assess
  • the WTRU may reset a L3 measurement window, may apply the measurement configuration, and/or may evaluate the prepower sharing RSRP.
  • the WTRU may continue applying the measurement configuration after power sharing activation.
  • the WTRU may reset the L3 measurement window and may evaluate the post-power sharing RSRP.
  • the WTRU may evaluate the one or more reporting conditions provided in the dedicated measurement configuration (e.g, to report issue with power sharing state).
  • the reporting condition may be satisfied. If the reporting condition is satisfied, the WTRU may trigger a measurement report indicating that the WTRU is affected by power sharing.
  • the WTRU may include additional assistance information (e.g., DL measurements pre and/or post the power sharing activation) in the measurement report.
  • the network may provide an alternative or additional reporting condition that the WTRU shall only report if the expected duration of the power saving state exceeds a time duration (e.g., 10s), for example, to further reduce congestion from excessive measurement reporting.
  • the WTRU may determine the duration of power sharing impact based on, for example, WTRU characteristics and/or NW assistance information as described herein.
  • Network polling for IDLE and/or INACTIVE WTRUs may be implemented.
  • a RAN network may obtain a rough estimate of how many INACTIVE state WTRU’s are within a geographic area based on an RNA tracking area.
  • the information may be stored at CN and may not be known to RAN.
  • many WTRUs e.g., several orders of magnitude more than terrestrial case
  • the ability for IDLE/INACTIVE WTRUs to provide feedback on planned network power sharing decisions may be limited.
  • the network may not know how many WTRUs will be impacted by a given decision since mobility is WTRU controlled in these states. It is important that a WTRU remains reachable in IDLE/INACTIVE for regulatory reasons. For example, to receive emergency messaging. The network may avoid reducing coverage for IDLE/INACTIVE WTRUs that do not have an alternative.
  • a WTRU may be polled to provide feedback of an anticipated power share state activation by reception of a paging message.
  • the WTRU may receive power sharing state assistance information and may determine whether the WTRU will be impacted.
  • the WTRU may receive dedicated preambles and/or reporting conditions to indicate the severity of the impact. Example preambles include if a WTRU expects to entirely lose coverage or if a WTRU expects to be impacted.
  • the network may respond with RAR and an UL grant requesting for additional assistance information (e.g, such as the duration of the coverage impact and/or the predicted magnitude of the DL coverage loss). In such an example, the network may determine and/or consider the impact to IDLE/INACTIVE WTRUs when making beam power sharing decisions, which may represent the majority of the total WTRUs served by the non-terrestrial networks.
  • a WTRU may be released to I DLE/I NACTIVE (e.g., via the reception of RRCRelease or RRCReleasewithSuspend message) and may monitor paging.
  • the WTRU may receive paging requesting an assessment of future power sharing state impact.
  • the WTRU may receive beam power sharing assistance information e.g., via specific SIB) indicating the planned power sharing state of the cell, including one or more of an area impacted by beam power sharing (e.g., explicit area description via reference point and radius, SSB index etc.), a time of beam power sharing implementation (e.g., UTC time), a duration of beam power sharing (e.g., 10s), an expected impact of beam power sharing (e.g., reduction in power/coverage by dB, cell completely turned off), or a configuration for IDLE/I NACTIVE UEs to report if there is an issue with updated power sharing state.
  • beam power sharing assistance information e.g., via specific SIB
  • an area impacted by beam power sharing e.g., explicit area description via reference point and radius, SSB index etc.
  • a time of beam power sharing implementation e.g., UTC time
  • a duration of beam power sharing e.g. 10s
  • an expected impact of beam power sharing e
  • the configuration may include one or more reporting conditions (e.g., WTRU will be impacted by power sharing decision, if duration of impact exceeds time period, etc.) and/or one or more preambles associated with a specific impact (e.g., Preamble A: coverage limited, Preamble B: lost coverage).
  • reporting conditions e.g., WTRU will be impacted by power sharing decision, if duration of impact exceeds time period, etc.
  • preambles associated with a specific impact e.g., Preamble A: coverage limited, Preamble B: lost coverage.
  • the WTRU may calculate if and/or when the WTRU will be impacted by the power saving state, including the time and duration of impact.
  • the WTRU may determine the start time and duration of impact via beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics. If the WTRU fulfills the reporting conditions within the IDLE/I NACTIVE reporting configuration (e.g., WTRU will be impacted) the WTRU may send preamble A if the WTRU estimates the WTRU will become severely coverage limited or send preamble B if the WTRU estimates the WTRU will entirely lose coverage.
  • the WTRU may perform paging-based network polling or follow-up WTRU.
  • An IDLE/I NACTIVE WTRU may be polled to determine whether it may be impacted by a future power sharing decision. In one example, this may be performed by using the network paging procedure, where the network would page one or more WTRUs requesting input on whether they will be impacted by a power sharing decision.
  • the WTRUs may provide a simple response (e.g., yes/no) via dedicated preamble transmission.
  • the WTRU may receive a configuration to support network polling in RRC_I DLE/I NACTIVE.
  • network polling refers to a request from the network to provide some assistance information about the impact of a power sharing decision to IDLE/INACTIVE WTRUs.
  • a WTRU may be configured to monitor for paging information for the purposes of network polling of power sharing impact.
  • the network polling may be indicated within a typical paging message (e.g., via a request within a paging short message), or the WTRU may be provided with a dedicated RNTI to monitor for network polling requests.
  • the WTRU may either re-use the existing paging cycle to monitor for network polling, or the WTRU may be configured with a dedicated occasion to monitor network polling.
  • the WTRU may be configured with one or more preambles to indicate that there if there is an estimated issue with a current and/or future power sharing decision.
  • the network may configure a dedicated preamble or set of preambles which may indicate one or more of the following: the WTRU is impacted by the current power sharing state; the WTRU will be impacted by a future power sharing state; the WTRU may not be impacted by a power sharing state; the WTRU estimates it may lose connection based on a power sharing state but there is an acceptable alternative cell to re-connect to; and/or the WTRU may lose connection and does not have an alternative for connection (e.g., there is no suitable neighbor cell or terrestrial network available for the WTRU to connect to).
  • the WTRU may also select one or more RACH occasions to transmit the preamble to convey additional information (e.g., the SSB in which the WTRU is currently located).
  • additional information e.g., the SSB in which the WTRU is currently located.
  • the WTRU may be configured to initiate a connection to the cell (e.g., via transmission of an RRC Setup message or RRC Resume message) in case it is (or may be in the future) severely impacted by the power sharing state.
  • Network polling may be enabled/disabled by indication explicitly (e.g., via a flag within the power sharing assistance information and/or network polling configuration) or implicitly (e.g., via absence of one or more pieces of information needed to receive network polling such as those described above).
  • the configuration for network polling and be provided, for example, via system information (e.g., as part of power sharing assistance information), within the RRC Release message or RRC release with suspend indication message. If a WTRU is provided with default configuration via system information and receives a subsequent dedicated configuration via the RRCRelease/RRCRelease with suspend message, the WTRU may override the default configuration and apply the dedicated polling configuration.
  • the WTRU may monitor for a network polling message according to the indicated configuration (e.g., at the configured occasions and with the indicated RNTIs). The WTRU may stop monitoring for network polling, for example, if the WTRU receives a subsequent indication that network polling is disabled, or upon cell (re)selection to a cell which does not support (or has disabled) network polling.
  • the WTRU may acquire updated power sharing assistance information (e.g., via SIB acquisition) as well as other information required to assess the impact of power sharing to the WTRU (e.g., satellite assistance information, WTRU location, etc.). The WTRU may then calculate whether it will be impacted by a current or future power sharing decision (e.g., as described elsewhere within this document).
  • the WTRU may select one or more reserved preambles and/or RACH occasions or may connect to the network in response.
  • the network polling message or network polling configuration may have an associated set of conditions in order to response.
  • the WTRU may only need to respond to network polling if one or more of the following conditions have been satisfied: 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 power sharing impact exceeds a specific time duration; the estimated drop in DL coverage exceeds a given threshold; the WTRU estimates it will lose connection; and/or the WTRU does not have an alternative cell available which it can maintain a connection.
  • the WTRU may select a preamble best representative of the power sharing impact of the WTRU and respond to the network polling message according to the configuration.
  • the network may request additional information regarding the impact to and IDLE/I NACTIVE WTRU.
  • the WTRU may monitor for additional signaling (e.g., Random access response (RAR)) after transmission of the paging response to receive additional requests.
  • RAR Random access response
  • the WTRU may receive a configuration (e.g. as part of the network polling configuration or separately, such as within the network polling message) to support additional monitoring for a follow up message from the original network polling message.
  • the configuration may indicate that the WTRU can reuse the ra_ReponseWindow to monitor for a subsequent request or may alternatively indicate a new duration to monitor PDCCH for a follow up message.
  • the follow up network polling message may include, for example, one or more of the following pieces of information: UL Grant to report the follow up assistance information, the RNTI for the specific WTRU, which information to include as assistance information, an indication to continue random access and connect to the cell, or an indication to enable a coverage enhancement (e.g., MSG3 repetition).
  • Information indicated to be included as assistance information may be, for example, one or more of: how long the WTRU is expecting to be impacted by the power sharing state; the area the WTRU is in (e.g., the associated SSB index); the estimated drop in DL coverage; or the current WTRU measurements.
  • the WTRU may monitor for a follow-up polling message.
  • the WTRU may start monitoring immediately after the initial response to the network polling (e.g., the preamble transmission), of the WTRU may offset the start of monitoring by the WTRU-gNB round trip time (RTT).
  • the WTRU may respond by including the requested assistance information and transmitting the assistance information within the indicated grant.
  • the WTRU may transmit the message via MSGA PUSCH, MSG3 format, or a MAC CE.
  • FIG. 7 depicts an example NW polling of power sharing impact to I DLE/I NACTIVE WTRUs.
  • an IDLE/I NACTIVE WTRU may be polled to provide feedback of an anticipated power share state activation by reception of a paging message at 704.
  • the WTRU may receive power sharing state assistance information and may determine whether it will be impacted at 706, as well as dedicated preambles and reporting conditions to indicate the severity of the impact (e.g., at 708 Preamble A: WTRU expects to entirely lose coverage; Preamble B: WTRU expects to be impacted).
  • a WTRU may perform one or more of the following to support NW polling for RRCJ DLE/I NACTIVE WTRUs.
  • the WTRU may be released to I DLE/I NACTIVE (e.g., via the reception of RRCRelease or RRCReleasewithSuspend message) and may monitor paging.
  • the WTRU may receive paging requesting an assessment of future power sharing state impact.
  • the WTRU may acquire beam power sharing assistance information (e.g., via specific SIB).
  • the WTRU may calculate if and/or when the WTRU will be impacted by the power saving state, including the time and duration of impact.
  • the WTRU may determine the start time and duration of impact via beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics. If WTRU fulfills the reporting conditions within the IDLE/INACTIVE reporting configuration (e.g., WTRU will be impacted), at 708, the WTRU may send preamble A if the WTRU estimates that the WTRU will become severely coverage limited or send preamble B if the WTRU estimates that the WTRU will entirely lose coverage.
  • power sharing assistance information acquired by the WTRU may indicate the planned power sharing state of the cell.
  • the planned power sharing state of the cell may include one or more of an area impacted by beam power sharing (e.g., explicit area description via reference point and radius, SSB index etc.), a time of beam power sharing implementation (e.g., UTC time), a duration of beam power sharing (e.g., 10s), an expected impact of beam power sharing (e.g., reduction in power/coverage by dB, cell completely turned off), or a configuration for I DLE/I NACTI VE WTRUs to report if there is an issue with updated power sharing state.
  • an area impacted by beam power sharing e.g., explicit area description via reference point and radius, SSB index etc.
  • a time of beam power sharing implementation e.g., UTC time
  • a duration of beam power sharing e.g. 10s
  • an expected impact of beam power sharing e.g., reduction in power/coverage by dB
  • the configuration may include one or more reporting conditions (e.g., WTRU will be impacted by power sharing decision, if duration of impact exceeds time period, etc.) or preambles associated with a specific impact (e.g., Preamble A: coverage limited, Preamble B: lost coverage).
  • reporting conditions e.g., WTRU will be impacted by power sharing decision, if duration of impact exceeds time period, etc.
  • preambles associated with a specific impact e.g., Preamble A: coverage limited, Preamble B: lost coverage.
  • the NW may respond with RAR and an UL grant requesting for additional assistance information such as the duration of the coverage impact and/or the predicted magnitude of the DL coverage loss, for example, to provide additional assistance information regarding the impact to a WTRU.
  • additional assistance information such as the duration of the coverage impact and/or the predicted magnitude of the DL coverage loss, for example, to provide additional assistance information regarding the impact to a WTRU.
  • the WTRU monitors for an additional grant may be explicitly configured (e.g., in the power sharing assistance information), or may be requested within the initial polling request.
  • the WTRU may provide, for example, the impacted SSB index, duration of impact etc.
  • the NW may receive MSG3 with assistance information and may terminate the RACH procedure.
  • Pre-configuration handling under power sharing may be implemented.
  • the WTRU executes the mobility event even though the target cell may shortly after entering a beam power sharing state.
  • pre-configuring target cells for handover is well suited to NTN. NTN relies heavily on distance and time-based triggers, which may not consider fully the measurements of the target cell. If the power sharing state of an upcoming satellite is known and will impact a cell which is configured as a candidate, then the WTRU may risk handing over to a cell which is about to experience DL coverage issues.
  • NTN relies heavily on distance and time-based triggers, which may not consider fully the measurements of the target cell. If the power sharing state of an upcoming satellite is known and will impact a cell which is configured as a candidate, then the WTRU may risk handing over to a cell which is about to experience DL coverage issues.
  • a WTRU may receive power sharing state assistance information for neighboring cells/satellites.
  • the WTRU may determine whether one or more neighboring cells impacted by a power sharing decision is an LTM or CHO candidate.
  • the WTRU may suspend (e.g., or bias against triggering) the configuration to the LTM/CHO candidate for the duration of the power saving state, for example, to avoid handover to a cell which will experience poor coverage.
  • the WTRU may avoid handing over to a cell which may not be suitable in the near future and may avoid possible RLF or service interruption due to a subsequent mobility event.
  • the WTRU may acquire power sharing assistance information (e.g., via SI) indicating the upcoming power sharing state of the current serving cell and one or more neighboring cells.
  • the power sharing assistance information may include an expected impact of power sharing state (e.g., % reduction in EIRP density), an area impacted by power sharing (e.g., explicit area description via reference point and radius, SSB index), a start time of power sharing state (e.g., UTC time), and/or a duration of beam power sharing state (e.g., 10s).
  • the WTRU may acquire NTN assistance information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris) for the serving cell and for neighboring cells (e.g., if the neighboring cell originates from a different satellite).
  • the WTRU may acquire its location and may calculate if/when the WTRU will be impacted by the power saving state, including the time and duration of impact for both serving and neighboring cells.
  • the WTRU may determine the start time and duration of impact based on beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics.
  • the WTRU may determine that one or more neighboring cells which will be impacted is/are a LTM/CHO candidate(s). During the time period that the WTRU is impacted by the power sharing state of the candidate cell, the WTRU may not consider the candidate (e.g., does not execute LTM, does not monitor for CHO conditions). The WTRU may bias the execution conditions during the power sharing state. Once the coverage state impact is over, the WTRU may re-consider the LTM/CHO candidate. The WTRU may execute LTM/CHO (e.g., if conditions are satisfied).
  • the WTRU may indicate whether the candidate will be impacted by a power saving state (either currently or in the future). To make this determination, the WTRU may acquire power sharing assistance information for one or more candidate cells and calculate whether one of the candidate cells will be impacted by a neighboring cell power sharing (as described previously in this document). Alternatively, the network may provide, as part of the candidate cell configuration, the power sharing assistance information.
  • Power sharing assistance information for a candidate cell may be associated with an expiry condition (e.g., such as those described within this document).
  • the WTRU may, for example, perform one or more of the following options: do not modify the handling of the candidate cell, and perform legacy actions, release the candidate cell configuration and optionally notify the network, or reacquire power sharing assistance information.
  • a WTRU may be configured to apply specific handling to pre-configured mobility candidates based on the power sharing state of a neighboring candidate cell.
  • the configuration for preconfigured mobility handling may include a flag to enable/disable modified handling of preconfigured mobility candidates based on power sharing state, one or more bias(es) to apply (e.g., to the triggering event) in case a candidate cell will be impacted by power sharing, a configuration to release the candidate in case the candidate cell will be impacted by power sharing, or a configuration to report to the network in case a candidate cell is impacted by power sharing.
  • the WTRU may apply one or more actions to the preconfigured mobility configuration. For example, a WTRU may release the candidate configuration, a WTRU may suspend CHO and/or LTM candidates, a WTRU may bias triggering conditions for CHO and/or LTM execution, or a WTRU may trigger CHO and/or LTM, however, not apply the RRC reconfiguration message/synchronize with the upcoming cell until the power sharing state is over.
  • a preconfigured mobility candidate e.g., a CHO and/or LTM candidate
  • the WTRU may apply one or more actions to the preconfigured mobility configuration. For example, a WTRU may release the candidate configuration, a WTRU may suspend CHO and/or LTM candidates, a WTRU may bias triggering conditions for CHO and/or LTM execution, or a WTRU may trigger CHO and/or LTM, however, not apply the RRC reconfiguration message/synchronize with the upcoming cell until the power sharing state is over.
  • the WTRU may trigger a preconfigured mobility anyways. For example, the WTRU may be provided with multiple thresholds. If the first is satisfied the WTRU suspends the configuration, if the second is satisfied the WTRU triggers mobility anyways. If the candidate configuration may be impacted by a future power sharing event, the WTRU may perform one or more of the above actions (e.g., bias triggering conditions, suspending a candidate etc.) indefinitely, or alternatively only for the duration of the power sharing impact.
  • the WTRU may perform one or more of the above actions (e.g., bias triggering conditions, suspending a candidate etc.) indefinitely, or alternatively only for the duration of the power sharing impact.
  • the WTRU may report to the network. Whether the WTRU reports the impact to a preconfigured mobility candidate to the network can be based on configuration, or alternatively may be based on configuration. For example, the WTRU may report that it has applied a modified handling of a configured mobility candidate based on if the WTRU has released a pre-configured mobility candidate, the WTRU has applied a bias to a preconfigured mobility candidate, the WTRU has suspended a preconfigured mobility candidate, if the duration of the modified handling of preconfigured candidates exceeds a threshold.
  • FIG. 8 illustrates an example pre-configuration handling under power sharing.
  • the WTRU may perform one or more of the operations. For example, in addition to calculating the impact of power sharing to the current serving cell, the WTRU may also acquire and evaluate power sharing state assistance information for neighboring cells. If the WTRU determines whether one or more neighboring cells impacted by a power sharing decision is an LTM or CHO candidate, the WTRU may suspend (or alternatively bias against triggering) the configuration to the LTM/CHO candidate for the duration of the power saving state to avoid handover to a cell which will experience poor coverage.
  • a WTRU may acquire power sharing assistance information (e.g., via SI) indicating the upcoming power sharing state of the current serving cell and one or more neighboring cells.
  • the power sharing assistance information may include expected impact of power sharing state (e.g., % reduction in EIRP density).
  • the power sharing assistance information may include the area impacted by power sharing (e.g., explicit area description via reference point and radius, SSB index).
  • the power sharing assistance information may include the start time of power sharing state (e.g., UTC time).
  • the power sharing assistance information may include the duration of beam power sharing state (e.g., 10s).
  • the WTRU may acquire NTN assistance information (e.g., via SIB 19) to determine cell characteristics (e.g., cell reference point, cell radius, satellite ephemeris) for the serving cell and for neighboring cells (if the neighboring cell originates from a different satellite).
  • the WTRU may acquire its location and may calculate if and/or when the WTRU will be impacted by the power saving state, including the time and duration of impact for both serving and neighboring cells.
  • the WTRU may determine the start time and duration of impact based on beam power sharing assistance information, NTN assistance information, and/or WTRU location/characteristics.
  • the WTRU may determine that one or more neighboring cell which will be impacted is a LTM/CHO candidate.
  • the WTRU may not consider the candidate (e.g., does not execute LTM, does not monitor for CHO conditions).
  • a WTRU may bias the execution conditions during the power sharing state. Once the coverage state impact is over, the WTRU may re-consider the LTM/CHO candidate. The WTRU may execute LTM/CHO, for example, if conditions are satisfied.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Une unité d'émission/réception sans fil (WTRU) comprend un processeur configuré pour recevoir des informations d'assistance de partage de puissance et des informations d'assistance de réseau non terrestre (NTN). Les informations d'assistance de partage de puissance peuvent comprendre une indication d'un état d'économie d'énergie à venir d'un dispositif NTN. Le processeur peut déterminer des informations d'emplacement associées à la WTRU. Le processeur peut envoyer un rapport qui indique que la WTRU peut être affectée par l'état d'économie d'énergie sur la base des informations d'assistance de partage d'énergie, des informations d'assistance NTN et/ou des informations d'emplacement.
PCT/US2024/048543 2023-09-26 2024-09-26 Estimation de l'impact d'un partage de puissance et amélioration conditionnelle de la couverture dl Pending WO2025072431A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363585354P 2023-09-26 2023-09-26
US63/585,354 2023-09-26

Publications (1)

Publication Number Publication Date
WO2025072431A1 true WO2025072431A1 (fr) 2025-04-03

Family

ID=93061520

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/048543 Pending WO2025072431A1 (fr) 2023-09-26 2024-09-26 Estimation de l'impact d'un partage de puissance et amélioration conditionnelle de la couverture dl

Country Status (1)

Country Link
WO (1) WO2025072431A1 (fr)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
THALES ET AL: "Proposed RAN1/2/3 led potential topics for Rel-19 NTN evolution", vol. RAN WG1, no. Bangalore; 20230911 - 20230915, 4 September 2023 (2023-09-04), XP052515016, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/TSG_RAN/TSGR_101/Docs/RP-231565.zip RP-231565 Rel-19 NTN evolution RAN123 topics_v37.docx> [retrieved on 20230904] *

Similar Documents

Publication Publication Date Title
US12231974B2 (en) Methods and apparatus for mobility in moving networks
US20220030532A1 (en) Methods for radio resource management in moving networks
US20250233650A1 (en) Adapting mobility under discontinuous coverage
EP4595684A1 (fr) Procédés d&#39;amélioration de rlf et de rétablissement dans ntn
EP4409763A1 (fr) Procédés et appareil pour une reprise après défaillance de faisceau dans des réseaux non terrestres new radio
WO2024211466A1 (fr) Gestion de faisceau pour commutations de satellites de même pci
WO2024173500A1 (fr) Procédés de vérification de localisation déclenchée par mobilité
WO2025072431A1 (fr) Estimation de l&#39;impact d&#39;un partage de puissance et amélioration conditionnelle de la couverture dl
JP7769142B2 (ja) Ｐｃｉ衛星切り替えのための送信処理
US20250343598A1 (en) Preconfigured uplink resource sharing in non-terrestrial networks
WO2024211465A1 (fr) Configuration de régulation de puissance pour commutateurs de satellites à pci identique
WO2024211462A1 (fr) Synchronisation temporelle pour des commutations de satellites à pci identique
WO2024211463A1 (fr) Surveillance de liaison radio pour commutateurs satellites de pci identiques
WO2025212332A1 (fr) Transmission et réception de diffusion/multidiffusion améliorées associées à des réseaux non terrestres
WO2025235439A1 (fr) Gestion de collision dans la prise en charge de réseaux
EP4594772A1 (fr) Acquisition et rapport de système global de navigation par satellite (gnss) pour des dispositifs à capacité réduite
EP4666096A1 (fr) Procédés de vérification de localisation déclenchée par mobilité

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24787651

Country of ref document: EP

Kind code of ref document: A1