Enhanced discontinuous reception operation for reduced capability user equipment in non-terrestrial networks

Abstract

A baseband processor, a UE, and a network device are described. The UE can perform the following operations: receive control signaling from a non-terrestrial network (NTN) device serving the UE, the control signaling indicating the duration of a validity timer for first ephemeris information of the NTN device, the UE being a degraded UE; enter a sleep duration configured for an extended discontinuous reception cycle for a degraded UE, the sleep duration being the duration between consecutive paging time windows of the extended discontinuous reception cycle; wake up during the sleep duration based at least in part on the duration of the validity timer to obtain second ephemeris information of the NTN device; and receive a control message from the NTN device including the second ephemeris information of the NTN device based at least in part on waking up during the sleep duration.

Description

Technical Field

[0001] This application relates throughout to wireless communication systems, including systems, apparatus, and methods for enhanced discontinuous reception (eDRX) operation of degraded capability (RedCap) user equipment (UE) in non-terrestrial networks (NTNs). Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between network devices (e.g., base stations, radio heads, etc.) and wireless communication devices. Wireless communication system standards and protocols may include, for example, 3GPP Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs) (often referred to as Wi-Fi within industry organizations). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between RAN network equipment (sometimes collectively referred to as RAN nodes, network nodes, or simply nodes) and wireless communication equipment called UEs. 3GPP RANs can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more Radio Access Technologies (RATs) for communication between network devices and UEs. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements the NR RAT (sometimes referred to herein as the 5G RAT, 5G NR RAT, or simply NR). In some deployments, E-UTRAN may also implement the NR RAT. In some deployments, NG-RAN may also implement the LTE RAT.

[0005] The network equipment used in a RAN can correspond to that RAN. An example of E-UTRAN network equipment is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB). An example of NG-RAN network equipment is a Next Generation Node B (sometimes also called gNodeB or gNB).

[0006] The RAN provides communication services to external entities through its connection with the core network (CN). For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC). Attached Figure Description

[0007] To facilitate the identification of any particular element or action in the discussion, one or more of the most significant digits in the figure reference numerals refer to the figure number in which the element was first introduced.

[0008] Figure 1 An example wireless communication system is shown according to one or more aspects described herein.

[0009] Figures 2A to 2C Example timing diagrams are shown based on one or more aspects described herein.

[0010] Figure 3A Example signaling diagrams are shown based on one or more aspects described herein.

[0011] Figure 3B Example timing diagrams are shown based on one or more aspects described herein.

[0012] Figure 4 An example method of wireless communication performed by a user equipment (UE) according to one or more aspects described herein is illustrated.

[0013] Figure 5 Another example method of wireless communication by a network device is shown, based on one or more aspects described herein.

[0014] Figure 6 Example architectures of wireless communication systems based on one or more aspects described herein are illustrated.

[0015] Figure 7 An example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein, is illustrated. Detailed Implementation

[0016] Various embodiments are described with respect to processors (e.g., baseband processors), wireless devices (e.g., user equipment (UE)), non-terrestrial network (NTN) devices, or network devices (e.g., terrestrial network (TN) devices). However, references to processors, wireless devices, NTN devices, or network devices are provided for illustrative purposes only. The example embodiments can be used with any electronic component or device capable of establishing a wireless connection and configured with hardware, software, and / or firmware for exchanging information and data via the wireless connection. Therefore, the processors, wireless devices, NTN devices, and network devices described herein are used to represent any suitable electronic component or device.

[0017] In addition to using TN equipment (such as eNBs or gNBs) for wireless communication, cellular networks can also use NTN equipment. NTN equipment can include various network devices operating above the Earth's surface that provide communication resources to UEs (e.g., on the ground, in the air, or on water) with specific coverage areas served by the NTN equipment. For example, a properly configured UE can communicate with NTN equipment instead of TN equipment, such as when the UE lacks coverage from TN equipment. In some deployments, NTN equipment is characterized as stationary relative to the ground, while other NTN equipment is mobile relative to the ground. Examples of stationary NTN equipment include satellites in geosynchronous orbit (GSO or GEO). Examples of mobile (non-stationary) NTN equipment include high-altitude platforms (HAPS), drones, and satellites in low Earth orbit (LEO), medium Earth orbit (MEO), or polar orbit. UEs can operate on the Earth's surface, but can also operate above or below that surface or on water, such as on or as part of an aircraft or ship.

[0018] Capability Reduction (RedCap) devices in the TN are typically UEs with a reduced set of capabilities relative to other UEs. RedCap UEs may have reduced processing power, memory, or radio capabilities, making them particularly suitable for low-cost devices, low-power or power-constrained applications, or environments where full UE capabilities are not required. RedCap UEs can be further characterized by fewer receive (Rx) and / or transmit (Tx) antennas, reduced bandwidth usage, lower power consumption, more lenient (e.g., slower) data rates, more lenient processing times, more lenient processing capabilities, etc. Specific use cases for RedCap UEs include industrial wireless sensors, video surveillance, and wearable devices such as watches (e.g., smartwatches), headsets (e.g., virtual reality (VR) or augmented reality (AR) headsets), rings, etc. RedCap UEs can utilize Extended Discontinuous Receive (DRX) in Radio Resource Control (RRC) idle or inactive states, or utilize lenient Radio Resource Management (RRM) measurements for neighboring cells (e.g., in a stationary state, or when not at the cell edge).

[0019] To conserve power, RedCap UEs can be configured to operate using Extended Discontinuous Receive (eDRX), which enhances power saving by allowing the RedCap UE to remain in a low-power sleep state for longer durations. In regular Discontinuous Receive (DRX), the UE periodically wakes up to check for incoming data or signaling from the network. However, this periodic waking can consume significant power, especially for devices requiring long battery life, such as RedCap UEs. eDRX addresses this by allowing the UE to extend the duration of its sleep cycles, thereby reducing the frequency of waking to check for network activity and consequently reducing power consumption. To maintain network reachability during eDRX, the UE incorporates a paging mechanism, where paging messages are scheduled to wake the UE at predetermined intervals. Thus, the UE can periodically and briefly wake up during the Paging Timed Window (PTW) to listen for paging messages from the network, allowing the UE to briefly exit the low-power state.

[0020] For RedCap UEs, power saving can be particularly important. Therefore, the eDRX cycle periodicity can be relatively long compared to non-RedCap UEs to increase power savings. For example, in some cases, the eDRX cycle periodicity can range anywhere from approximately 20 seconds to close to 3 hours (e.g., from approximately 20.48 seconds to approximately 10485.76 seconds in some specific implementations). In this case, the time between PTW instances corresponds to approximately 20 seconds to close to 3 hours.

[0021] Increasingly, it may be desirable to support RedCap UEs in wireless communication with NTN devices in the network. To communicate properly with NTN devices, the UE needs the current ephemeris information of the NTN devices. Ephemeris information for NTN devices includes orbital information (such as position and velocity information at a specific time) and can be broadcast by the NTN devices in system information (e.g., System Information Block Type 19 (SIB19)). The UE can use ephemeris information to perform downlink synchronization, time-frequency tracking, and detection and measurement of the serving cell and NTN cells. However, ephemeris information has a limited validity period, for example, because the NTN device may be moving relative to the Earth, atmospheric conditions may be changing and affecting the channel, or the UE itself may be moving. Therefore, a validity timer (e.g., ntn-UlSyncValidityDuration) may be associated with the ephemeris information.

[0022] For RedCap UEs communicating with NTN devices, it may be desirable to operate the UE with long eDRX cycles. However, the validity timer for NTN ephemeris information may expire outside the PTW (Placement Time Warp). Therefore, the network may have already refreshed the ephemeris information, or the validity timer may have expired outside the PTW. Consequently, when the UE wakes up, it will not have valid ephemeris information for the NTN device, potentially interrupting communication between the RedCap UE and the NTN device. Alternatively, the UE can wake up more frequently at the cost of increased power consumption. Technical support for eDRX operation is desired for RedCap UEs communicating with NTN devices to save power.

[0023] As further described herein, when the UE wakes up, such as during a paging time window of an eDRX cycle, the UE obtains ephemeris information for serving the NTN device. The ephemeris information has a validity timer that indicates how long the ephemeris information is valid for serving the NTN device. The UE can then enter a sleep period of the eDRX cycle according to the eDRX configuration. The UE then wakes up during the sleep period to obtain second (new or updated) ephemeris information for the NTN device, obtaining the second ephemeris information including receiving a control message (e.g., SIB19 or NTN-Config) that includes the second ephemeris information.

[0024] Figure 1 An example wireless communication system 100 according to one or more aspects described herein is illustrated. In one or more embodiments, the wireless communication system 100 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein.

[0025] Wireless communication system 100 includes one or more UEs 102, which can be served by NTN device 106 via communication link 130 (e.g., having a Radio Resource Control (RRC) connection established with the NTN device). Coverage area 110 is the service area (e.g., a cell or serving cell, which may include multiple cells) of the RF spectrum band utilized by the NTN device 106 serving the UE 102. UE 102 is a RedCap UE discussed above (e.g., a smartwatch, etc.). In some embodiments, NTN device 106 may be a non-stationary NTN device (e.g., a satellite with low or medium Earth orbit), such that NTN device 106 is in a first position at a first time (t0) and in a second position at a second time (t1). When NTN device 106 is a non-stationary NTN device, whether providing a fixed Earth cell or a mobile Earth cell, NTN device 106 may, for example, have an orbital path 114 relative to the Earth. In other embodiments, NTN device 106 may be a geostationary NTN device (e.g., a geostationary satellite) such that a first position at a first time is the same as or substantially the same as a second position at a second time.

[0026] To support power savings for UE 102, UE 102 may be able to support eDRX operation. eDRX configuration signaling 120 can be provided to the UE from the network via NTN device 106 (or, in some examples, another TN or NTN network device). Among other things, the eDRX configuration indicates the eDRX cycle length (the duration or period of the eDRX cycle) and the paging time window.

[0027] UE 102 also receives first ephemeris information 122 and a validity duration 124 associated with the ephemeris information for NTN device 106. In some embodiments, the first ephemeris information 122 and the indication of the validity duration 124 may be sent by NTN device 106 in system information (such as SIB 19). In some examples, each system information message broadcast by NTN device 106 that includes ephemeris information for that NTN device 106 may include a validity duration associated with that ephemeris information. At UE 102, a validity duration timer (e.g., ntn-UlSyncValidityDuration) can be set or reset for the ephemeris information. In some examples, the system information includes an epoch time corresponding to the ephemeris information (e.g., an indication subframe number), which UE 102 uses to set the start of the validity timer duration.

[0028] In one or more embodiments, UE 102 receives first ephemeris information 122 and an indication of validity duration 124 during the paging time window of the eDRX cycle. At or after the end of the paging time window, UE 102 enters the sleep duration of the eDRX cycle. In one or more embodiments, the validity duration timer expires at some point during the sleep duration of the eDRX cycle.

[0029] During the sleep duration, UE 102 subsequently wakes up to obtain second ephemeris information 126. Similar to the first ephemeris information 122, the second ephemeris information 126 can be broadcast by NTN device 106 in system information along with the associated validity duration. As further discussed herein, UE 102 can wake up before the validity duration timer for the first ephemeris information 122 expires, just before the next paging time window, or based on the indication that the triggering conditions have been met.

[0030] UE 102 can wake up at the next paging time window to use the second ephemeris information 126 to listen for (monitor, configure to receive) paging messages 128 from NTN device 106.

[0031] Figure 2A Example timing diagram 201 is shown according to one or more aspects described herein. In one or more embodiments, timing diagram 201 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. Timing diagram 201 generally illustrates an example in which UE 102 wakes up outside a paging time window to read system information (e.g., SIB19) or otherwise perform ephemeris information reading before a validity timer expires. For example, UE 102 may wake up to monitor a broadcast channel for NTN-config to obtain ephemeris information. In another example, UE 102 may wake up to monitor paging transmitted from the network's Physical Downlink Shared Channel (PDSCH), where such PDSCH transmissions may carry ephemeris information.

[0032] Timing diagram 201 includes eDRX periodicity 204 corresponding to the eDRX cycle duration received by UE 102 as part of the eDRX configuration, and also indicates paging time window (PTW) 206. Sleep duration 208 corresponds to the time duration of eDRX periodicity 204 between paging time windows (e.g., between PTW 206 and the next PTW 206-a).

[0033] Timing diagram 201 also includes a first duration of validity timer 212, a second duration of validity timer 216, and a third duration of validity timer covering the next PTW 206-a. During PTW 206 at 210, for example, near the end of PTW 206, UE 102 can listen for and receive control signaling indicating ephemeris information of NTN device 106. In some embodiments, the control signaling may also indicate the duration of the validity timer. In other embodiments, the duration of the validity timer may be received by UE 102 in different control or configuration signaling from NTN device 106 or another network device.

[0034] At 214, for example, near the end or expiration of validity timer 212, UE 102 can wake up to listen for and receive new ephemeris information from NTN device 106. After receiving ephemeris information with validity timer 216, UE 102 returns to sleep again according to eDRX configuration. At 218, for example, near the end or expiration of validity timer 216, UE 102 can wake up again to listen for and receive new ephemeris information from NTN device 106. After receiving ephemeris information with validity timer 218, UE 102 returns to sleep again according to eDRX configuration, which can cover at least a portion of the next PTW 206-a. UE 102 then wakes up at the next PTW 206-a according to eDRX configuration.

[0035] In some implementations, UE 102 can wake up before the validity timer expires, obtain ephemeris information, and return to sleep multiple times as needed to span the sleep duration until the next PTW 206-a. In some implementations, timing diagram 201 can be applied when eDRX periodicity 204 is configured to be greater than 20.48 seconds.

[0036] Figure 2B An example timing diagram 202 is shown according to one or more aspects described herein. In one or more embodiments, timing diagram 202 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. Timing diagram 202 generally illustrates an example in which UE 102 remains asleep outside PTW 206 (e.g., during sleep duration 208) even after validity timer 212 has expired, and UE 102 wakes up before the next PTW 206-a for ephemeris information reacquisition. That is, when UE 102 enters the next PTW 206-a, UE 102 is ready to perform paging monitoring and cell measurements.

[0037] After PTW 206, UE 102 enters sleep mode for duration 208. At 222, validity timer 212 expires, and UE 102 remains in sleep mode. Between 222 and the next PTW 206-a (or just before the next PTW 206-a, after 226), UE 102 may not have valid ephemeris information for NTN device 106.

[0038] At 226 (which could be the scheduled duration 224 of the next PTW 206-a), UE 102 wakes up to listen for and receive new ephemeris information for NTN device 106 to use during the next PTW 206-a. With valid ephemeris information available during the next PTW 206-a, UE 102 is able to listen for (monitor) paging from NTN device 106 and perform cell measurements at the start of the next PTW 206-a.

[0039] In some implementations, timing diagram 202 can be applied when eDRX periodicity 204 is configured to be greater than 20.48 seconds. In some cases, the aspects illustrated with reference to timing diagram 202 can save additional power than those illustrated with reference to timing diagram 201, for example, because UE 102 can wake up and sleep fewer times during sleep duration 208. In some cases, ephemeris acquisition may be more difficult or complex with timing diagram 202 because at 222, the last ephemeris information may have expired a relatively long time before UE 102 wakes up at 226.

[0040] Figure 2C Example timing diagram 202 is shown according to one or more aspects described herein. In one or more embodiments, timing diagram 202 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. Timing diagram 203 generally illustrates an example in which UE 102 wakes up outside PTW 206 when one or more conditions are met.

[0041] As previously described, after PTW 206, UE 102 enters sleep duration 208. At 222, validity timer 212 expires, and UE 102 remains in sleep. Between 222 and the next PTW 206-a, UE 102 may not have valid ephemeris information for NTN device 106. In one or more embodiments, at trigger 230, UE 102 wakes up before the next PTW 206-a when one or more conditions are met. After trigger 230 is detected or otherwise determined to have occurred, UE 102 wakes up within duration 232. In some embodiments, duration 232 is extended until the next PTW 206-a. In other embodiments, duration 232 may end before the next PTW 206-a, allowing UE 102 to return to sleep before the next PTW 206-a. UE 102 can then wake up again before the next PTW 206-a, for example, to obtain nova ephemeris information, as discussed in reference timing diagram 202.

[0042] In some implementations, the condition is that the velocity of UE 102 is greater than a threshold velocity. For example, the velocity of UE 102 is obtained from a Global Navigation Satellite System (GNSS) model at UE 102 based on positioning signals received from GNSS satellites during a sleep duration of 208. In some implementations, the velocity threshold is a predefined value. In other implementations, the velocity threshold is pre-configured by the network for UE 102.

[0043] In some implementations, the condition is that the distance from UE 102 to the NTN device 106 serving UE 102 is greater than a threshold distance. UE 102 can determine this distance as the difference between the location of UE 102 (e.g., determined via a GNSS model) and the location of NTN device 106 (e.g., determined via ephemeris information, such as the last ephemeris information obtained by UE 102 at 210). In some implementations, the distance threshold is a predefined value. In other implementations, the distance threshold is pre-configured by the network for UE 102.

[0044] In some implementations, the condition is that the distance from UE 102 to a neighboring NTN device is less than a threshold distance. UE 102 can determine the distance as the difference between the location of UE 102 (e.g., determined via a GNSS model) and the location of the neighboring NTN device, which is determined based on ephemeris information obtained from the neighboring NTN device (e.g., ephemeris information obtained by UE 102 during PTW 206, for example via SIB19 for the neighboring NTN device). In some implementations, the distance threshold is a predefined value. In other implementations, the distance threshold is pre-configured by the network for UE 102.

[0045] In some implementations, the service time of the serving cell of NTN device 106 may expire, for example, during sleep duration 208, provided that the service time has expired. UE 102 may wake up before the service time expires, as triggered 230, to measure neighboring NTN devices.

[0046] In some implementations, if the NTN device 106 serving UE 102 is a non-stationary NTN device (e.g., a non-GEO satellite), UE 102 can ignore the PTW window operation of eDRX periodicity 204 and wake up during the duration of the sleep period according to the discontinuous reception (DRX) cycle operation (non-eDRX operation or legacy DRX operation). Therefore, the trigger 230 for UE 102 to wake up is the DRX-on period of the DRX cycle (wake-up state), and the UE can periodically return to the sleep state (off period) after the on period according to the DRX configuration (instead of the eDRX configuration).

[0047] Similarly, in some implementations, if the neighboring NTN device that UE 102 is measuring is a non-stationary NTN device (e.g., a non-GEO satellite), UE 102 can ignore the PTW window operation of eDRX periodicity 204 and wake up to measure the neighboring NTN device during the duration that would be a sleep period, according to discontinuous reception (DRX) cycle operation (non-eDRX operation or legacy DRX operation). Therefore, the trigger 230 for UE 102 to wake up is the DRX-on period of the DRX cycle (wake-up state), and the UE can periodically return to the sleep state (off period) after the on period according to the DRX configuration (instead of the eDRX configuration).

[0048] In some implementations, if the NTN device 106 serving UE 102 is a non-stationary NTN device (e.g., a non-GEO satellite), and UE 102 identifies or detects that NTN device 106 is a non-stationary NTN device, then UE 102 may operate during sleep duration 208 as described with reference to timing diagram 201, for example, to obtain ephemeris information of NTN device 106. Similarly, if the neighboring NTN device that UE 102 is measuring is a non-stationary NTN device, then UE 102 may operate during sleep duration 208 as described with reference to timing diagram 201, for example, to measure the neighboring NTN device.

[0049] Figure 3ASignaling diagram 301 is shown according to one or more aspects described herein. In one or more embodiments, signaling diagram 301 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. UE 102 may be an example of UE 102 being served by NTN device 106, as further described herein. In one or more embodiments, UE 102 providing UE capability signaling 304 may be configured with an eDRX duration greater than 20.48 seconds.

[0050] At 304, UE 102 sends UE capability signaling 304 to NTN device 106. In one or more embodiments, referring to eDRX and / or DRX operation, UE capability signaling 304 relates to the capabilities of UE 102 as a RedCap UE, as further described herein. In some embodiments, UE capability signaling 304 may be RRC signaling and is sent by UE 102 to NTN device 106 as part of a connection (e.g., attachment) procedure.

[0051] In one or more embodiments, UE capability signaling 304 includes an indication that UE 102 can support eDRX cycles of up to 10.24 seconds. Additionally or alternatively, UE capability signaling 304 includes an indication that UE 102 can support eDRX cycles of 2.56 seconds or more. In some embodiments, UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., not stationary NTN devices). The indication included in UE capability signaling 304 can be applied on a UE-based or per-band basis. When the indication is applied on a per-band basis, UE 102 can provide indications for more than one band.

[0052] In one or more embodiments, UE capability signaling 304 includes an indication that UE 102 can support eDRX cycles longer than 10.24 seconds. Additionally or alternatively, UE capability signaling 304 includes an indication that the UE supports eDRX using PTW. In some embodiments, UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., not stationary NTN devices). The indication included in UE capability signaling 304 can be applied on a UE-based or per-band basis. When the indication is applied on a per-band basis, UE 102 can provide indications for more than one band.

[0053] In one or more embodiments, UE capability signaling 304 includes an indication (e.g., an explicit indication) of the length (duration) of an eDRX cycle that UE 102 can support. In some embodiments, UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., not stationary NTN devices). In still other embodiments, UE capability signaling 304 may indicate that the capability applies to stationary NTN devices (e.g., not non-stationary NTN devices). The indication included in UE capability signaling 304 may be applied on a UE-based or per-band basis. When the indication is applied on a per-band basis, UE 102 can provide indications for more than one band.

[0054] NTN device 106 receives UE capability signaling including the indication, and at 306, selects the eDRX cycle length (duration, period) of UE 102 at least in part based on (e.g., in response to) the indicated UE capability, for example as part of selecting the eDRX configuration of UE 102.

[0055] In one or more implementations, the selected eDRX configuration is restricted to an eDRX cycle no longer than the ephemeris validity timer length. For example, the eDRX cycle may be subject to a specific fractional restriction on the ephemeris validity timer length, such that the eDRX cycle length is X*(ephemeris validity timer length), where X≤1.

[0056] In one or more implementations, if the serving cell of NTN device 106 or the target neighbor cell used for UE measurement is a non-stationary NTN device (e.g., NGSO), the eDRX cycle used for configuration can be limited to no more than 10.24 seconds. That is, in some examples, eDRX is configured without PTW.

[0057] In one or more implementations, if the serving cell of NTN device 106 or the target neighbor cell used for UE measurement is a non-stationary NTN device (e.g., NGSO), then eDRX is not configured (and not used), and only legacy DRX can be configured (and used).

[0058] In one or more embodiments, the DRX configuration is limited to an eDRX cycle no longer than the serving cell service time (e.g., the service time of the serving cell of the NTN device 106 serving UE 102). Additionally or alternatively, the DRX configuration is limited such that at least one PTW is guaranteed to occur before the serving cell service time expires.

[0059] At 308, NTN device 106 may select the validity timer duration at least in part based on (e.g., in response to) the indicated UE capability, for example as part of the eDRX configuration for selecting UE 102.

[0060] In one or more implementations, the NTN device 106 may extend the ephemeris validity timer length to be comparable to the eDRX cycle periodicity. For example, the NTN device 106 may select a validity timer duration of up to 10485.76 seconds, which in some cases corresponds to the longest eDRX cycle that the NTN device 106 can use for the configuration of UE 102. For example, the NTN device 106 may select a validity timer duration that is not less than the eDRX cycle supported by the UE. In some implementations, the field may be defined as follows: ntn-UlSyncValidityDuration-r19 ENUMERATED{X, Y, Z,…}; where X, Y, Z > 900 seconds.

[0061] At 310, NTN device 106 sends an indication of discontinuous reception configuration for UE 102. As further described herein, discontinuous reception configuration may be or include eDRX configuration, DRX configuration, or both.

[0062] According to one or more aspects described herein, UE 102 may then operate at 312 based on a discontinuous reception configuration received from NTN device 106, including receiving ephemeris information 314 from NTN device 106.

[0063] Figure 3B Example timing diagram 302 is shown according to one or more aspects described herein. In one or more embodiments, timing diagram 302 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. Timing diagram 302 generally exemplifies the example described above with reference to signaling diagram 301, wherein the selected eDRX configuration is limited to an eDRX cycle no longer than the validity timer length.

[0064] The timing diagram includes an eDRX periodicity 324 corresponding to the duration of an eDRX cycle received by UE 102 as part of a discontinuous reception configuration (e.g., eDRX configuration), which also indicates PTW 326. The sleep duration 328 corresponds to the duration of the eDRX periodicity 324 between paging time windows (e.g., between PTW 326 and the next PTW 326-a). At 330, UE 102 may obtain ephemeris information from NTN device 106 and set the duration of validity timer 332. In one or more embodiments, NTN device 106 may have configured UE 102 with an eDRX periodicity 324 (e.g., N seconds) with a duration not greater than the duration of validity timer 332 (e.g., the duration of validity timer 332 is greater than or equal to N). Therefore, at 336, the validity timer expires during the next PTW 326-a. With this restriction at NTN device 106 and the corresponding configuration of UE 102, once UE 102 has woken up in the next PTW 326-a, UE 102 can obtain the second (updated) ephemeris information of NTN device 106 at 334.

[0065] In some examples, NTN device 106 is restricted to make the eDRX cycle part of the invalidation timer duration. As a specific example, if the ephemeris validity timer length is 900 seconds, the eDRX cycle can be as long as 900 seconds. Therefore, at 336, UE 102 will have at least one PTW before the validity timer expires, and in any case, UE will have one PTW for ephemeris information renewal before the validity timer expires.

[0066] Figure 4 An example method 400 for wireless communication performed by a UE is illustrated. In some cases, the UE may be a wireless device 702 or a UE 102. In some cases, method 400 may be executed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores and memory coupled to the processor cores. The memory may store instructions that, when executed by the processor cores, cause the baseband processor to perform the operation 400 of the method. While the baseband processor is performing the operation of method 400, the baseband processor may also cause other components of the UE to perform or abort various operations.

[0067] At 402, method 400 includes receiving control signaling from an NTN device serving a UE (e.g., a RedCap UE), the control signaling indicating the duration of a validity timer for first ephemeris information of the NTN device.

[0068] At 404, method 400 includes entering a sleep duration configured for an extended discontinuous reception cycle for the UE, the sleep duration being the duration between consecutive paging time windows of the extended discontinuous reception cycle.

[0069] At 406, method 400 includes waking up during the sleep duration based at least in part on the duration of the validity timer to obtain second ephemeris information of the NTN device.

[0070] At 408, method 400 includes receiving a control message from the NTN device, including second ephemeris information of the NTN device, based at least in part on waking up during the sleep duration.

[0071] In some implementations, waking up during the sleep duration includes waking up before the validity timer expires to listen for control messages that include second ephemeris information.

[0072] In some implementations, waking up during the sleep duration includes waking up after the validity timer expires and before the next paging time window of the extended discontinuous reception cycle to listen for control messages that include second ephemeris information.

[0073] In one or more embodiments, the method further includes determining, during the sleep duration, that the UE's speed meets a speed threshold, and waking up in response to the determination. In one or more embodiments, the method further includes determining, during the sleep duration, that the distance between the UE and an NTN device serving the UE is greater than or equal to a distance threshold, and waking up in response to the determination. In one or more embodiments, the method further includes determining, during the sleep duration, that the distance between the UE and adjacent NTN devices is less than or equal to a distance threshold, and waking up in response to the determination. In some embodiments, waking up during the sleep duration includes waking up before the service timer of the NTN device serving the UE expires. In one or more embodiments, the method further includes waking up during the sleep duration based at least in part on the NTN device serving the UE being a non-stationary NTN device, according to a discontinuous reception cycle. In one or more embodiments, the method further includes waking up during the sleep duration based at least in part on the NTN device serving the degraded UE covering a non-fixed Earth cell, according to a discontinuous reception cycle. In one or more embodiments, the method further includes waking up during the sleep duration, including waking up during the sleep duration based at least in part on a discontinuous reception cycle based on a neighboring NTN device to be measured by the UE being a non-geostationary satellite, the control signaling being received at least in part in response to transmitted UE capability signaling. In one or more embodiments, the method further includes waking up during the sleep duration based at least in part on a neighboring NTN device to be measured by a capability-degraded UE covering a non-geostationary cell, according to a discontinuous reception cycle.

[0074] In one or more embodiments, the method further includes transmitting UE capability signaling indicating whether the UE supports extended discontinuous reception cycles longer than 10.24 seconds, wherein control signaling is received at least in part in response to the transmitted UE capability signaling. In some embodiments, the UE capability signaling further includes an indication that the UE supporting extended discontinuous reception cycles longer than 10.24 seconds is suitable for non-stationary NTN devices. In one or more embodiments, the method further includes transmitting UE capability signaling indicating the duration of extended discontinuous reception cycles supported by the UE.

[0075] In one or more embodiments, the method further includes using second ephemeris information to listen for paging messages sent by the NTN device during the next paging time window.

[0076] Method 400 may be embodied, extended or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0077] Figure 5 An example method 500 for wireless communication performed by a network device is illustrated. In one or more embodiments, method 500 supports one or more aspects of enhanced discontinuous reception operation for degraded user equipment in non-terrestrial networks, as further described herein. In some cases, the network device may be one of network device 104, network device 720, or other network devices described herein. Method 500 may be performed using a processor, transceiver (e.g., main radio component), or other components of the network device.

[0078] At 502, method 500 includes receiving from the RedCap UE a timed UE capability signaling indicating that the UE supports extended discontinuous reception cycles.

[0079] At 504, method 500 includes sending the RedCap UE's discontinuous reception configuration and the validity timer duration of ephemeris information sent by the NTN device to the RedCap UE, at least in part in response to the duration of the extended discontinuous reception cycle supported by the UE.

[0080] In one or more embodiments, the method further includes selecting the duration of the extended discontinuous reception cycle of the UE to be no greater than the validity timer duration of the ephemeris information, based at least in part on the fact that the NTN device is a non-stationary NTN device, the discontinuous reception configuration indicating the selected duration of the extended discontinuous reception cycle.

[0081] In one or more embodiments, the method further includes selecting the duration of the extended discontinuous reception cycle of the UE to be no greater than 10, based at least in part on the fact that the NTN device is a non-stationary NTN device.

[0082] In one or more embodiments, the method further includes selecting the discontinuous reception cycle length of the UE based at least in part on the fact that the NTN device is a non-stationary NTN device, the discontinuous reception configuration indicating the selected discontinuous reception cycle length; and avoiding configuration extended discontinuous reception operation based at least in part on the fact that the NTN device is a non-stationary NTN device.

[0083] In one or more embodiments, the method further includes selecting the validity timer duration to be no less than the extended discontinuous reception cycle supported by the UE.

[0084] In one or more embodiments, the method further includes selecting the duration of the extended discontinuous reception cycle of the UE to be no greater than the duration of the service timer of the NTN device serving the UE, the discontinuous reception configuration indicating the selected duration of the extended discontinuous reception cycle.

[0085] In one or more embodiments, the method further includes selecting the duration of an extended discontinuous reception cycle for a UE on a per-UE basis, the discontinuous reception configuration indicating the selected duration. In one or more embodiments, the method further includes selecting the duration of an extended discontinuous reception cycle for a UE on a per-band basis, the discontinuous reception configuration indicating the selected duration and an indication of the RF spectrum band to which the selected duration is applied.

[0086] Method 500 can be embodied, extended, or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0087] The embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 400 or 500. In the context of method 400, the non-transitory computer-readable medium may be, for example, the memory of a UE (such as memory 706 of a wireless device 702 as a UE, as described herein). In the context of method 500, the non-transitory computer-readable medium may be, for example, the memory of a network device (such as memory 724 of a network device 720, as described herein).

[0088] The embodiments contemplated herein include an apparatus having logic components, modules, or circuitry for performing one or more elements of method 400 or 500. In the context of method 400, the apparatus may be, for example, a UE (such as wireless device 702 as a UE). In the context of method 500, the apparatus may be, for example, a network device (such as network device 720, as described herein).

[0089] The embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 400 or 500. In the context of method 400, the apparatus may be, for example, a UE (such as wireless device 702 as a UE, as described herein). In the context of method 500, the apparatus may be, for example, a network device (such as network device 720, as described herein).

[0090] The implementation schemes envisioned herein include signals as described or associated with one or more elements of method 400 or 500.

[0091] The embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to perform one or more elements of method 400 or 500. In the context of method 400, the processor may be a processor of a UE (such as processor 704 of wireless device 702 as a UE, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the UE (such as memory 706 of wireless device 702 as a UE, as described herein). In the context of method 500, the processor may be a processor of a network device (such as processor 722 of network device 720, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the network device (such as memory 724 of network device 720, as described herein).

[0092] Figure 6 An example architecture of a wireless communication system according to the implementation scheme described herein is illustrated. The following description is provided for example wireless communication system 600, which operates in conjunction with LTE system standards or specifications and / or 5G or NR system standards or specifications as provided by 3GPP technical specifications.

[0093] As shown in the figure, the wireless communication system 600 includes UE 602 and UE 604 (but any number of UEs may be used). In this example, UE 602 and UE 604 are exemplified as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0094] UE 602 and UE 604 can be configured to communicatively couple with RAN 606. In implementations, RAN 606 can be NG-RAN, E-UTRAN, etc. UE 602 and UE 604 utilize connections (or channels) with RAN 606 (shown as connection 608 and connection 610, respectively), each of these connections including a physical communication interface. RAN 606 may include one or more network devices (such as base station 612 and base station 614) implementing connection 608 and connection 610.

[0095] In this example, Connection 608 and Connection 610 are air interfaces used to implement such communication coupling and are compliant with the RAT used by RAN 606, such as LTE and / or NR, for example.

[0096] In some implementations, UE 602 and UE 604 can also exchange communication data directly via sidelink interface 616. UE 604 is shown configured to access an access point (shown as AP 618) via connection 620. By way of example, connection 620 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 618 may include Wi-Fi. ® Router. In this example, AP 618 can connect to another network (e.g., the Internet) without going through CN624.

[0097] In the implementation, UE 602 and UE 604 may be configured to communicate with each other or with base station 612 and / or base station 614 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), although the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0098] In some implementations, all or some of the base stations in base station 612 or base station 614 may be implemented as one or more software entities running on a server computer as part of a virtual network. Furthermore, or in other implementations, base station 612 or base station 614 may be configured to communicate with each other via interface 622. In implementations where the wireless communication system 600 is an LTE system (e.g., when CN 624 is an EPC), interface 622 may be an X2 interface. This X2 interface may be defined between two or more network devices (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In implementations where the wireless communication system 600 is an NR system (e.g., when CN 624 is a 5GC), interface 622 may be an Xn interface. The Xn interface may be defined between two or more network devices (e.g., two or more gNBs, etc.) connected to the 5GC, between base station 612 (e.g., gNB) and eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 624).

[0099] RAN 606 is shown communicatively coupled to CN 624. CN 624 may include one or more network elements 626 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE602 and UE604) connected to CN 624 via RAN 606. Components of CN 624 may be implemented in a single physical device or a separate physical device including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media).

[0100] In this implementation, CN 624 may be an EPC, and RAN 606 may be connected to CN 624 via S1 interface 628. In this implementation, S1 interface 628 may be divided into two parts: an S1 user plane (S1-U) interface, which carries service data between base station 612 or base station 614 and the service gateway (S-GW); and an S1-MME interface, which is the signaling interface between base station 612 or base station 614 and the mobility management entity (MME).

[0101] In this implementation, CN 624 may be a 5GC, and RAN 606 may be connected to CN 624 via NG interface 628. In this implementation, NG interface 628 may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between base station 612 or 614 and the User Plane Function (UPF); and an S1 control plane (NG-C) interface, which is the signaling interface between base station 612 or 614 and the Access and Mobility Management Function (AMF).

[0102] Generally, application server 630 can be a component that provides Internet Protocol (IP) carried resources (e.g., packet-switched data services) for use with CN 624. Application server 630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 602 and UE 604 via CN 624. Application server 630 can communicate with CN 624 through IP communication interface 632.

[0103] Figure 7 An example system 700 for performing signaling 738 between a wireless device 702 and a network device 720 according to an embodiment described herein is illustrated. System 700 may be part of a wireless communication system as described herein. Wireless device 702 may be, for example, a UE of a wireless communication system. Network device 720 may be, for example, a base station (e.g., an eNB or gNB) or a radio headend of a wireless communication system.

[0104] Wireless device 702 may include one or more processors 704. Processor 704 may execute instructions that cause various operations of wireless device 702 to be performed as described herein. Processor 704 may include one or more baseband processors, which may be implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0105] In one or more embodiments, one or more processors in processor 704 may be baseband processors. In some embodiments, the baseband processor includes one or more cores coupled to memory and one or more interfaces, as well as other components or circuitry for facilitating or otherwise supporting wireless communication performed by wireless device 702, including performing one or more operations further described herein. The core of the baseband processor may include one or more of a wireless communication processor, a central processing unit, a graphics processing unit, an artificial intelligence engine, a security engine, an image signal processor, a sensing system, a positioning system, or a display processor. A core may also be referred to as, for example, a processor, a processor core, a processing unit, an engine, or an accelerator. One or more wireless communication processors may include support for cellular communication or wireless local area network (WLAN) communication.

[0106] Wireless device 702 may include memory 706. Memory 706 may be a non-transitory computer-readable storage medium that stores instructions 708, which may include instructions executed, for example, by processor 704. Instructions 708 may also be referred to as program code or a computer program. Memory 706 may also store data used by processor 704 and results calculated by the processor.

[0107] Wireless device 702 may include one or more transceivers 710 (also collectively referred to as transceivers 710), which may include radio frequency (RF) transmitter and / or receiver circuitry that uses antenna 712 of wireless device 702 to facilitate to-and-out signaling (e.g., signaling 738) from and to other devices (e.g., network device 720) in accordance with a corresponding RAT.

[0108] Wireless device 702 may include one or more (e.g., one, two, four, eight or more) antennas 712. In embodiments with multiple antennas 712, wireless device 702 can utilize the spatial diversity of such multiple antennas 712 to transmit and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, MIMO behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by wireless device 702 can be implemented according to pre-decoding (or digital beamforming) applied to wireless device 702, which multiplexes the data streams among antennas 712 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some embodiments may use a single-user MIMO (SU-MIMO) method (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) method (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0109] In some implementations with multiple antennas, the wireless device 702 can implement analog beamforming technology, whereby the phase of the signal transmitted by the antenna 712 is relatively adjusted so that the (joint) transmission of the antenna 712 can be directed (this is sometimes referred to as beam control).

[0110] Wireless device 702 may include one or more interfaces 714. Interfaces 714 can be used to provide input to or output to wireless device 702. For example, wireless device 702 as a UE may include interfaces 714, such as microphones, speakers, touchscreens, buttons, etc., to allow input and / or output from a user of the UE to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 710 / antenna 712 already described), allowing communication between the UE and other devices, and can be configured according to known protocols (e.g., Wi-Fi). ® ,Bluetooth ® (etc.) to perform the operation.

[0111] Wireless device 702 may include an extended discontinuous receiver manager 716. The extended discontinuous receiver manager 716 may be implemented via hardware, software, or a combination thereof. For example, the extended discontinuous receiver manager 716 may be implemented as a processor, circuitry, and / or instructions 708 stored in memory 706 and executed by processor 704. In some examples, the extended discontinuous receiver manager 716 may be integrated within processor 704 and / or transceiver 710. For example, the extended discontinuous receiver manager 716 may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 704 or transceiver 710.

[0112] From the perspective of a wireless device or UE, the extended discontinuous reception manager 716 can be used in various aspects of this disclosure, for example, Figures 1 to 7 The extended discontinuous reception manager 716 can be configured to, for example, receive control signaling from an NTN device serving the UE, the control signaling indicating the duration of a validity timer for first ephemeris information of the NTN device, the UE being a capability-degraded UE; enter a sleep duration configured for the UE in an extended discontinuous reception cycle, the sleep duration being the duration between consecutive paging time windows of the extended discontinuous reception cycle; wake up during the sleep duration based at least in part on the duration of the validity timer to obtain second ephemeris information of the NTN device; and receive a control message from the NTN device including the second ephemeris information of the NTN device based at least in part on waking up during the sleep duration.

[0113] Network device 720 may include one or more processors 722. Processor 722 may execute instructions to perform various operations of network device 720 as described herein. Processor 722 may include one or more baseband processors, which may be implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0114] Network device 720 may include memory 724. Memory 724 may be a non-transitory computer-readable storage medium that stores instructions 726, which may include instructions executed, for example, by processor 722. Instructions 726 may also be referred to as program code or a computer program. Memory 724 may also store data used by processor 722 and results calculated by the processor.

[0115] Network device 720 may include one or more transceivers 728 (also collectively referred to as transceiver 728), which may include RF transmitter and / or receiver circuitry that uses antenna 730 of network device 720 to facilitate to-and / or signaling from network device 720 to other devices (e.g., wireless device 702) and / or from network device 720 (e.g., signaling 738) in accordance with the corresponding RAT.

[0116] Network device 720 may include one or more antennas 730 (e.g., one, two, four or more). In embodiments having multiple antennas 730, network device 720 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described.

[0117] Network device 720 may include one or more interfaces 732. Interface 732 may be used to provide input to or output to network device 720. For example, RAN network device 720 (e.g., base station, radio head, etc.) may include interfaces 732 consisting of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 728 / antenna 730 already described), which enable network device 720 to communicate with other equipment in the network and / or enable network device 720 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining network device 720 or other equipment operatively connected to it.

[0118] Network device 720 may include at least one extended discontinuous receiver manager 734. The extended discontinuous receiver manager 734 may be implemented via hardware, software, or a combination thereof. For example, the extended discontinuous receiver manager 734 may be implemented as a processor, circuitry, and / or instructions 726 stored in memory 724 and executed by processor 722. In some examples, the extended discontinuous receiver manager 734 may be integrated within processor 722 and / or transceiver 728. For example, the extended discontinuous receiver manager 734 may be implemented by a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 722 or transceiver 728.

[0119] From a network device perspective, the extended discontinuous reception manager 734 can be used in various aspects of this disclosure, for example, Figures 1 to 7All aspects. The Extended Discontinuous Reception Manager 734 can be configured, for example, to receive UE capability signaling from a UE that is a UE with reduced capability, the UE capability signaling indicating the duration of the extended discontinuous reception cycle supported by the UE; and to send the UE's discontinuous reception configuration and the validity timer duration of ephemeris information sent by the NTN device to the UE, at least in part, in response to the duration of the extended discontinuous reception cycle supported by the UE.

[0120] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor (or processor) as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples presented herein. Similarly, circuitry associated with a UE, network device, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples presented herein.

[0121] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustrative and descriptive purposes, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form described. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from the practice of various embodiments.

[0122] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0123] The systems described herein relate to specific implementations but are provided as examples. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be understood that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0124] Although the foregoing has been described in considerable detail for clarity, it will be apparent that changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this description is not limited to the details given herein, but can be modified within the scope and equivalents of the appended claims.

Claims

1. A baseband processor, the baseband processor being configured to: Control signaling is received from a non-terrestrial network (NTN) device from a user equipment (UE) with reduced capability, the control signaling indicating the duration of a validity timer for the first ephemeris information of the NTN device; The capability reduces the sleep duration of the UE when it enters a configured extended discontinuous reception cycle, the sleep duration being the time duration between consecutive paging time windows of the extended discontinuous reception cycle. The capability is reduced such that the UE wakes up during the sleep duration based at least in part on the duration of the validity timer to obtain the second ephemeris information of the NTN device; and At least in part, it is based on receiving a control message from the NTN device, including the second ephemeris information of the NTN device, upon waking up during the sleep duration.

2. The baseband processor according to claim 1, wherein the baseband processor is further configured to: Wake up before the validity timer expires to listen for the control message that includes the second ephemeris information.

3. The baseband processor according to claim 1, wherein the baseband processor is further configured to: Wake up before the next paging time window of the extended discontinuous reception cycle to listen for the control message including the second ephemeris information.

4. The baseband processor according to claim 1, wherein the baseband processor is further configured to: During the sleep duration, if it is determined that the rate at which the capability of the UE decreases meets a speed threshold, the baseband processor wakes up in response to the determination.

5. The baseband processor according to claim 1, wherein the baseband processor is further configured to: If, during the sleep duration, it is determined that the distance between the degraded UE and the NTN device serving the degraded UE is greater than or equal to a distance threshold, the baseband processor wakes up in response to the determination.

6. The baseband processor according to claim 1, wherein the baseband processor is further configured to: If, during the sleep duration, it is determined that the distance between the capability-reduced UE and a neighboring NTN device is less than or equal to a distance threshold, the baseband processor wakes up in response to the determination.

7. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The reduced-capability UE is woken up before the service timer of the NTN device serving the reduced-capability UE expires.

8. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The reduced capability UE is awakened during the sleep duration based at least in part on the fact that the NTN device serving the reduced capability UE is a non-stationary NTN device.

9. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The reduced-capability UE is awakened during the sleep duration based on the NTN equipment serving the reduced-capability UE covering a non-Earth fixed cell, at least in part.

10. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The reduced capability UE is awakened during the sleep duration, including at least in part based on the fact that the neighboring NTN devices to be measured by the reduced capability UE are non-geostationary satellites, and awakening during the sleep duration according to a discontinuous reception cycle.

11. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The reduced capability UE is awakened during the sleep duration, including at least in part based on the coverage of non-Earth fixed cells by neighboring NTN devices to be measured by the reduced capability UE, according to a discontinuous reception cycle, to awaken during the sleep duration.

12. The baseband processor according to claim 1, wherein the baseband processor is further configured to: Send UE capability signaling indicating whether the capability-reduced UE supports the extended discontinuous reception cycle of more than 10.24 seconds, wherein the control signaling is received at least in part in response to the sent UE capability signaling, wherein the UE capability signaling further includes an indication that the capability-reduced UE supporting the extended discontinuous reception cycle of more than 10.24 seconds is suitable for non-stationary NTN devices.

13. The baseband processor according to claim 1, wherein the baseband processor is further configured to: Send UE capability signaling indicating the duration of extended discontinuous reception cycles supported by the UE due to the reduced capability.

14. A method for wireless communication at a non-terrestrial network (NTN) device, the method comprising: Receive UE capability signaling from a degraded user equipment (UE), the UE capability signaling indicating the duration of extended discontinuous reception cycles supported by the UE; as well as The validity timer duration of the extended discontinuous reception cycle supported by the UE is sent to the degraded UE at least in part in response to the duration of the extended discontinuous reception cycle supported by the UE. The discontinuous reception configuration of the degraded UE and the ephemeris information sent by the NTN device are also sent to the degraded UE.

15. The method according to claim 14, further comprising: The duration of the extended discontinuous reception cycle of the UE with reduced capability is selected to be no greater than the validity timer duration of the ephemeris information, at least in part based on the fact that the NTN device is a non-stationary NTN device. The discontinuous reception configuration indicates the selected duration of the extended discontinuous reception cycle.

16. The method of claim 14, further comprising: The duration of the extended discontinuous reception cycle for the UE is selected to be no more than 10.24 seconds, at least in part based on the fact that the NTN device is a non-stationary NTN device, and the discontinuous reception configuration indicates the selected duration of the extended discontinuous reception cycle.

17. The method of claim 14, further comprising: The capability to reduce the discontinuous reception cycle length of the UE is selected at least in part based on the fact that the NTN device is a non-stationary NTN device, and the discontinuous reception configuration indicates the selected discontinuous reception cycle length; as well as At least in part, this is based on the fact that the NTN device is a non-stationary NTN device to avoid configuring extended discontinuous reception operations.

18. The method according to claim 14, further comprising: The validity timer duration is selected to be no less than the extended discontinuous reception cycle supported by the UE.

19. The method of claim 14, further comprising: The duration of the extended discontinuous reception cycle of the degraded UE is selected to be no greater than the duration of the service timer of the NTN device serving the degraded UE, and the discontinuous reception configuration indicates the selected duration of the extended discontinuous reception cycle.

20. A method for conducting wireless communication at a degraded user equipment (UE), the method comprising: Control signaling is received from a non-terrestrial network (NTN) device serving the UE with reduced capability, the control signaling indicating the duration of a validity timer for the first ephemeris information of the NTN device; The sleep duration is the time duration between consecutive paging time windows of the extended discontinuous reception cycle configured for the capability-reduced UE. The device wakes up during the sleep duration based at least in part on the duration of the validity timer to obtain second ephemeris information of the NTN device; as well as At least in part, it is based on receiving a control message from the NTN device, including the second ephemeris information of the NTN device, upon waking up during the sleep duration.

Images