Enhanced discontinuous reception operation for reduced capability user equipment in non-terrestrial networks
By optimizing eDRX operations with timely ephemeris updates during sleep durations, RedCap UEs maintain valid information for NTN devices, addressing communication disruptions and power consumption issues.
Patent Information
- Application Number
- PCT/CN2024/077277
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-16
- Publication Date
- 2025-08-21
AI Technical Summary
RedCap UEs communicating with NTN devices face challenges in maintaining valid ephemeris information due to the expiration of validity timers during extended discontinuous reception cycles, leading to disrupted communications and increased power consumption when frequent waking up is required.
The UE wakes up during sleep durations of eDRX cycles based on validity timers to obtain updated ephemeris information, using trigger conditions and eDRX configurations tailored to NTN device types, ensuring valid information is available for paging time windows.
This approach maintains effective communication with NTN devices while reducing power consumption by optimizing eDRX operations, ensuring valid ephemeris information is available when needed, thus enhancing power savings and communication reliability.
Smart Images

Figure CN2024077277_21082025_PF_FP_ABST
Abstract
Description
ENHANCED DISCONTINUOUS RECEPTION OPERATION FOR REDUCED CAPABILITY USER EQUIPMENT IN NON-TERRESTRIAL NETWORKSTECHNICAL FIELD
[0001] This application relates generally to wireless communication systems, including systems, apparatuses, and methods for enhanced discontinuous reception (eDRX) operation for reduced capability (RedCap) user equipment (UE) in non-terrestrial networks (NTN) .BACKGROUND
[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc. ) and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) , 3GPP new radio (NR) (e.g., 5G) , and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as ) .
[0003] As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a network device of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a UE. 3GPP RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for 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 may use one or more radio access technologies (RATs) to perform communication between the network device and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE) , and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR) . In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.
[0005] A network device used by a RAN may correspond to that RAN. One example of an E-UTRAN network device is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) . One example of an NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
[0006] A RAN provides its communication services with external entities through its connection to a core network (CN) . For example, E-UTRAN may utilize an Evolved Packet Core (EPC) , while NG-RAN may utilize a 5G Core Network (5GC) .BRIEF DESCRIPTION OF THE DRAWINGS
[0007] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.
[0008] FIG. 1 shows an example wireless communication system, according to one or more aspects described herein.
[0009] FIGs. 2A-2C show example timing diagrams, according to one or more aspects described herein.
[0010] FIG. 3A shows an example signaling diagram, according to one or more aspects described herein.
[0011] FIG. 3B shows an example timing diagram, according to one or more aspects described herein.
[0012] FIG. 4 shows an example method of wireless communication by a user equipment (UE) , according to one or more aspects described herein.
[0013] FIG. 5 shows another example method of wireless communication by a network device, according to one or more aspects described herein.
[0014] FIG. 6 illustrates an example architecture of a wireless communication system, according to one or more aspects described herein.
[0015] FIG. 7 illustrates an example system for performing signaling between a wireless device and a network device, according to one or more aspects described herein.DETAILED DESCRIPTION
[0016] Various embodiments are described with regard to a processor (e.g., baseband processor) , wireless device (e.g., a user equipment (UE) ) , a non-terrestrial network (NTN) device, or a network device (e.g., a terrestrial network (TN) device) . However, reference to a processor, wireless device, NTN device, or network device is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component or device that may establish a wireless connection and is configured with the hardware, software, and / or firmware to exchange information and data over the wireless connection. Therefore, the processors, wireless devices, NTN devices, and network devices described herein are used to represent any appropriate electronic components or devices.
[0017] In addition to utilizing TN devices (terrestrial base stations such as an eNB or a gNB) for wireless communications, cellular networks may use NTN devices. NTN devices may include various network devices operating above the surface of the Earth that provide communication resources to UEs (e.g., terrestrial, airborne, or on water) with a particular coverage area served by the NTN device. For example, an appropriately configured UE may communicate with an NTN device instead of a TN device, for example if the UE lacks coverage from a TN device. In some deployments, NTN devices are stationary relative to features on the ground, but other NTN devices move relative to the ground. Examples of stationary NTN devices include satellites in geosynchronous orbit (GSO or GEO) . Examples of moving (non-stationary) NTN devices include high-altitude platforms (HAPS) , drones, and satellites in a low Earth orbit (LEO) , a medium Earth orbit (MEO) , or a polar orbit. UEs may operate on the surface of the Earth but may also operate above or below the surface, or on water, for example on or as part of an aircraft or ship.
[0018] A reduced capability (RedCap) device in a TN is generally a UE with a reduced capability set relative to other UEs. RedCap UEs may have reduced processing power, memory, or radio capabilities, making them especially suitable for use in low-cost devices, low-power or power-constrained applications, or in environments where full UE capabilities are unnecessary. RedCap UEs may further be characterized by fewer receive (Rx) and / or transmit (Tx) antennas, reduced use of bandwidth, lower power consumption, relaxed (e.g., slower) data rates, relaxed processing times, relaxed processing capabilities, and so on. Specific use cases for RedCap UEs include for industrial wireless sensors, video surveillance, and wearables, such as a watches (e.g., smartwatches) , headsets (e.g., virtual reality (VR) or augmented reality (AR) headsets) , rings, and the like. RedCap UEs may make use of extended discontinuous reception (DRX) in a radio resource control (RRC) idle state or inactive state, or relaxed radio resource management (RRM) measurements for neighboring cells (e.g., in a stationary state, or when not at a cell edge) .
[0019] To save power, RedCap UEs can be configured to operate using extended discontinuous reception (eDRX) , which enhances the power-saving capabilities of the RedCap UE by allowing it to remain in a low-power sleep state for longer durations. In conventional discontinuous reception (DRX) , a UE periodically wakes up to check for incoming data or signaling from the network. However, this periodic waking up can consume significant power, especially for devices that need to maintain long battery life such as RedCap UEs. eDRX addresses this issue by allowing the UE to extend the duration of sleep periods, thereby reducing the frequency of waking up to check for network activity and reducing corresponding power consumption. To remain reachable by the network during eDRX, UEs incorporates a paging mechanism where paging messages are scheduled to wake up the UE at predetermined intervals. As such, the UE may briefly awake periodically during a paging timing window (PTW) to listen for paging messages from the network, allowing the UE to briefly exit the low-power state.
[0020] For RedCap UE, saving power may be especially important. As such, the periodicity of eDRX may be relatively quite long compared to non-RedCap UE to increase power savings. For example, the eDRX cycle periodicity in some cases may be anywhere from about 20 seconds to nearly 3 hours (e.g., in some implementations from about 20.48 seconds to about 10485.76 seconds) . In such case, the time between PTW instances is correspondingly about 20 seconds to nearly 3 hours.
[0021] Increasingly, it may be desirable to support RedCap UEs to wirelessly communicate with NTN devices in a network. In order to appropriately communicate with an NTN device, the UE needs current ephemeris information for the NTN device. Ephemeris information for an NTN device includes orbital information such as position and velocity information at a particular time, and may be broadcast by the NTN device in system information (e.g., a system information block type 19 (SIB19) ) . The UE may use the ephemeris information to perform downlink synchronization, time-frequency tracking, and detection and measurement of serving cells and NTN cells. However, ephemeris information has a limited validity time, for example because the NTN device may be moving relative to Earth, atmospheric conditions may be changing and affecting the channel, or the UE itself may move. As such, a validity timer (e.g., ntn-UlSyncValidityDuration) may be associated with the ephemeris information.
[0022] For RedCap UE communicating with NTN devices, it may be desirable to operate the UE with a long eDRX period, but a validity timer for NTN ephemeris information may expire outside the PTW. As such, the network may have refreshed the ephemeris information or the validity timer may have expired outside the PTW. Consequently, the UE will not have valid ephemeris information for the NTN device when the UE awakes, which may disrupt communications between the RedCap UE and the NTN device. Alternatively, the UE could wake up more frequently, at the expense of power consumption. Techniques for RedCap UE communicating with NTN devices are desired to support eDRX operation for power saving.
[0023] As further described herein, a UE obtains ephemeris information for a serving NTN device when the UE is awake, such as during a paging time window of an eDRX cycle. The ephemeris information has a validity timer that indicates for how long the ephemeris information is valid for the serving NTN device. The UE may then enter a sleep duration of the eDRX cycle, according to an eDRX configuration. The UE then then wakes up during the sleep duration 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] FIG. 1 shows an example wireless communications system 100, according to one or more aspects described herein. In one or more embodiments, wireless communications system 100 supports one or more aspects of enhanced discontinuous reception operation for reduced capability user equipment in non-terrestrial networks, as further described herein.
[0025] Wireless communications system 100 includes one or more UE 102 that may be being served by (e.g., has an established radio resource control (RRC) connection with) an NTN device 106 via communication link 130. Coverage area 110 is the service area for the RF spectrum band utilized by NTN device 106 serving the UE 102 (e.g., a cell or serving cell, which may include multiple cells) . UE 102 is a RedCap UE (e.g., a smartwatch or the like) , discussed above. In some embodiments, NTN device 106 may be a non-stationary NTN device (e.g., a satellite having a low or medium Earth orbit) , such that NTN device 106 is at a first position at a first time (t0) , and a second position at a second time (t1) . NTN device 106 may, for example, have an orbital path 114 relative to the Earth when NTN device 106 is a non-stationary NTN device, whether providing Earth fixed cells or Earth moving cells. In other embodiments, NTN device 106 may be a stationary NTN device (e.g., a geosynchronous satellite) , such that the first position at the first time is the same or about the same as the second position at the second time.
[0026] To support power savings by the UE 102, the UE 102 may be capable of supporting eDRX operations. The UE may be provided with eDRX configuration signaling 120 from the network via the NTN device 106 (or another TN or NTN network device in some examples) . The eDRX configuration indicates, among other things, an eDRX cycle length (a duration or period length in length for the eDRX cycle) and a paging time window.
[0027] The UE 102 also receives first ephemeris information 122, as well as a validity duration 124 associated with ephemeris information for the NTN device 106. In some embodiments, the first ephemeris information 122 and an indication of the validity duration 124 may be transmitted by the NTN device 106 in system information, such as a SIB19. In some examples, each system information message broadcast by the NTN device 106 that includes ephemeris information for that NTN device 106 may include a validity duration associated with that ephemeris information. At the UE 102, a validity duration timer (e.g., ntn-UlSyncValidityDuration) may be set or reset for the ephemeris information. In some examples, the system information include an epoch time (e.g., indicating a subframe number) corresponding to the ephemeris information that the UE 102 uses to set the start of the validity timer duration.
[0028] In one or more embodiments, the UE 102 receives the first ephemeris information 122 and the indication of the validity duration 124 during a paging time window of an eDRX cycle. At or after the end of the paging time window, the UE 102 enters a sleep duration of the eDRX cycle. In one or more embodiments, the validity duration timer will expire at some point during the sleep duration of the eDRX cycle.
[0029] During the sleep duration, the UE 102 then wakes up to obtain the second ephemeris information 126. Like the first ephemeris information 122, the second ephemeris information 126 may be broadcast by the NTN device 106 in system information along with an associated validity duration. As further discussed herein, the UE 102 may wake up prior to expiration of the validity duration timer for the first ephemeris information 122, just before the next paging time window, or based on identifying a trigger condition has been met.
[0030] The UE 102, at the next paging time window, may wake up to listen (monitor, configure to receive) paging messages 128 from the NTN device 106 using the second ephemeris information 126.
[0031] FIG. 2A shows an example timing diagram 201, 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 reduced capability user equipment in non-terrestrial networks, as further described herein. Timing diagram 201 generally illustrates an example where the UE 102 wakes up outside the paging time window to read system information (e.g., SIB19) or to otherwise take an ephemeris information reading, before the validity timer expiration. For example, the UE 102 may wake up to monitor the broadcasting channel for NTN-config to acquire the ephemeris information. In another example, the UE 102 may wake up to monitor paging for physical downlink shared channel (PDSCH) transmissions from network, where such PDSCH transmissions can carry the ephemeris information..
[0032] Timing diagram 201 includes an eDRX periodicity 204 corresponding to the eDRX cycle duration received by a UE 102 as part of the eDRX configuration, which also indicates a paging time window (PTW) 206. Sleep duration 208 corresponds to the time duration of the eDRX periodicity 204 between paging time windows, for example between the PTW 206 and a next PTW 206-a.
[0033] Timing diagram 201 also includes a first duration for a validity timer 212, a second duration for a validity timer 216, and a third duration for a validity timer that covers the next PTW 206-a. During the PTW 206 at 210, for example near the end of the PTW 206, the UE 102 may listen for and receive control signaling indicating ephemeris information for an NTN device 106. In some embodiments, the control signaling may also indicate a duration for the validity timer. In other embodiments, the duration for the validity timer may be received by the UE 102 in different control or configuration signaling from the NTN device 106, or another network device.
[0034] At 214, for example near an end or expiry of the validity timer 212, the UE 102 may wake up to listen for and receive new ephemeris information for the NTN device 106. Having received the ephemeris information having a duration for a validity timer 216, the UE 102 again returns to sleep, as per the eDRX configuration. At 218, for example near an end or expiry of the validity timer 216, the UE 102 may again wake up to listen for and receive new ephemeris information for the NTN device 106. Having received the ephemeris information having a duration for a validity timer 218, which may cover at least a portion of the next PTW 206-a, the UE 102 again returns to sleep, as per the eDRX configuration. The UE 102 then wakes up per the eDRX configuration at the next PTW 206-a.
[0035] In some embodiments, the UE 102 may wake up before expiry of a validity timer, obtain ephemeris information, and return to sleep as many times as needed to span the sleep duration until the next PTW 206-a. In some embodiments, timing diagram 201 may apply in cases where the eDRX periodicity 204 is configured to be greater than 20.48 seconds.
[0036] FIG. 2B shows an example timing diagram 202, 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 reduced capability user equipment in non-terrestrial networks, as further described herein. Timing diagram 202 generally illustrates an example where the UE 102 keeps sleeping outside the PTW 206 (e.g., during the sleep duration 208) even after the validity timer 212 is expired, and the UE 102 wakes up before the next PTW 206-a for ephemeris information reacquisition. That is, the UE 102 is ready to perform paging monitoring and cell measurement when UE 102 enters the next PTW 206-a.
[0037] Following PTW 206, the UE 102 enters the sleep duration 208. At 222, the validity timer 212 expires and UE 102 remains in a sleep state. Between 222 and the next PTW 206-a (or just before the next PTW 206-a, following 226) , UE 102 may not have valid ephemeris information for the NTN device 106.
[0038] At 226, which may be a predetermined duration 224 of the next PTW 206-a, the UE 102 wakes up to listen for and receive new ephemeris information for the NTN device 106 to use during the next PTW 206-a. Having valid ephemeris information during the next PTW 206-a, the UE 102 is able to listen (monitor) for paging from NTN device 106 and perform cell measurements at the start of the next PTW 206-a.
[0039] In some embodiments, timing diagram 202 may apply in cases where the eDRX periodicity 204 is configured to be greater than 20.48 seconds. In some cases, aspects illustrated with reference to timing diagram 202 may save additional power over aspects illustrated with reference to timing diagram 201, for example because the UE 102 may awake and sleep fewer times during the sleep duration 208. In some cases, ephemeris acquisition may be more difficult or complex for timing diagram 202 because the last ephemeris information may have expired, at 222, a relatively long time before the UE 102 wakes up at 226.
[0040] FIG. 2C shows an example timing diagram 202, 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 reduced capability user equipment in non-terrestrial networks, as further described herein. Timing diagram 203 generally illustrates an example where the UE 102 wake ups outside the PTW 206 when the one or multiple conditions are met.
[0041] As previously described, following PTW 206, the UE 102 enters the sleep duration 208. At 222, the validity timer 212 expires and UE 102 remains in a sleep state. Between 222 and the next PTW 206-a, UE 102 may not have valid ephemeris information for the NTN device 106. In one or more embodiments, the UE 102 wakes up before the next PTW 206-a when one or more conditions are met, at trigger 230. Having detected or otherwise determined that the trigger 230 has occurred, the UE 102 wakes up for duration 232. In some embodiments, the duration 232 extends until a next PTW 206-a. In other embodiments, the duration 232 may end prior to a next PTW 206-a, such that the UE 102 may return to sleep prior to the next PTW 206-a. The UE 102 may then wake up again prior to the next PTW 206-a, for example to obtain new ephemeris information as discussed with reference to timing diagram 202.
[0042] In some embodiments, the condition is that the speed of UE 102 is greater than a threshold speed. The UE 102 speed is acquired from a global navigation satellite system (GNSS) model at the UE 102, for example based on positioning signals received from GNSS satellites during the sleep duration 208. In some embodiments, the speed threshold is a predefined value. In other embodiments, the speed threshold is preconfigured by the network for the UE 102.
[0043] In some embodiments, the condition is that the distance from the UE 102 to the NTN device 106 serving the UE 102 is greater than a threshold distance. The UE 102 may determine the distance as a different between the position of the UE 102 (e.g., determined via GNSS model) and the position of the NTN device 106 (e.g., determined via ephemeris information, such as the last ephemeris information obtained by UE 102 at 210) . In some embodiments, the distance threshold is a predefined value. In other embodiments, the distance threshold is preconfigured by the network for the UE 102.
[0044] In some embodiments, the condition is that the distance from the UE 102 to a neighbor NTN device is less than a threshold distance. The UE 102 may determine the distance as a different between the position of the UE 102 (e.g., determined via GNSS model) and the position of the neighbor NTN device is determined based on ephemeris information obtained form the neighbor NTN device (e.g., such as ephemeris information obtained by UE 102 during PTW 206 for neighboring NTN devices, for example via a SIB19 of the neighboring NTN device) . In some embodiments, the distance threshold is a predefined value. In other embodiments, the distance threshold is preconfigured by the network for the UE 102.
[0045] In some embodiments, a service time of the serving cell of NTN device 106 may expire, for example during the sleep duration 208, the condition is the expiry of the service time. The UE 102 may wake up prior to the service time expiry, as trigger 230, to measure neighbor NTN devices.
[0046] In some embodiments, if the NTN device 106 serving the UE 102 is a non-stationary NTN device (e.g., a non-GEO satellite) , the UE 102 may ignore the PTW window operation of the eDRX periodicity 204, and awake during what would be the sleep duration according to a discontinuous reception (DRX) cycle operation (non-eDRX operation or legacy DRX operation) . As such, the trigger 230 for the UE 102 to wake up is a DRX on-duration (awake state) of the DRX cycle, and the UE may return to a sleep state (off-duration) following the on-duration periodically according to a DRX configuration (and not the eDRX configuration) .
[0047] Similarly, in some embodiments, if a neighboring NTN device that the UE 102 is measuring is a non-stationary NTN device (e.g., a non-GEO satellite) , the UE 102 may ignore the PTW window operation of the eDRX periodicity 204, and awake during what would be the sleep duration according to a discontinuous reception (DRX) cycle operation (non-eDRX operation or legacy DRX operation) to measure the neighboring NTN device. As such, the trigger 230 for the UE 102 to wake up is a DRX on-duration (awake state) of the DRX cycle, and the UE may return to a sleep state (off-duration) following the on-duration periodically according to a DRX configuration (and not the eDRX configuration) .
[0048] In some embodiments, if the NTN device 106 serving the UE 102 is a non-stationary NTN device (e.g., a non-GEO satellite) and the UE 102 identifies or detects that the NTN device 106 is the non-stationary NTN device, then the UE 102 may operate as described with reference to timing diagram 201 during the sleep duration 208, for example to obtain ephemeris information for the NTN device 106. Similarly, if a neighboring NTN device that the UE 102 is measuring is a non-stationary NTN device, then the UE 102 may operate as described with reference to timing diagram 201 during the sleep duration 208, for example to measure the neighboring NTN device.
[0049] FIG. 3A shows a signaling diagram 301, 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 reduced capability user equipment in non-terrestrial networks, as further described herein. The UE 102 may be an example of a UE 102 being served by NTN device 106, as further described herein. In one or more embodiments, the UE 102 that is providing the UE capability signaling 304 may be configured with eDRX that is greater than 20.48 seconds.
[0050] At 304, the UE 102 transmits UE capability signaling 304 to NTN device 106. In one or more embodiments, the UE capability signaling 304 relates to the capabilities of UE 102, which is a RedCap UE, with reference to eDRX and / or DRX operation, as further described herein. In some embodiments, the UE capability signaling 304 may be RRC signaling, and transmitted by UE 102 to NTN device 106 as part of a connection (e.g., attachment) procedure.
[0051] In one or more embodiments, the UE capability signaling 304 includes an indication that the UE 102 can support eDRX cycles up to 10.24 seconds. Additionally, or alternatively, the UE capability signaling 304 includes an indication that the UE 102 can support, eDRX cycles greater than or equal to 2.56 seconds. In some embodiments, the UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, the UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., and not stationary NTN devices) . The indication included in the UE capability signaling 304 may apply on a UE-basis, or on a per-band basis. When the indication applies on a per-band bases, the UE 102 may provide an indication for more than one band.
[0052] In one or more embodiments, the UE capability signaling 304 includes an indication that the UE 102 can support eDRX cycles greater than 10.24 seconds. Additionally, or alternatively, the UE capability signaling 304 includes an indication that the UE supports eDRX using PTW. In some embodiments, the UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, the UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., and not stationary NTN devices) . The indication included in the UE capability signaling 304 may apply on a UE-basis, or on a per-band basis. When the indication applies on a per-band bases, the UE 102 may provide an indication for more than one band.
[0053] In one or more embodiments, the UE capability signaling 304 includes an indication (e.g., an explicit indication) of a length (duration) of an eDRX cycles that the UE 102 can support. In some embodiments, the UE capability signaling 304 may indicate that the capability applies to both stationary NTN devices and non-stationary NTN devices. In other embodiments, the UE capability signaling 304 may indicate that the capability applies to non-stationary NTN devices (e.g., and not stationary NTN devices) . In other embodiments, the UE capability signaling 304 may indicate that the capability applies to stationary NTN devices (e.g., and not to non-stationary NTN devices) . The indication included in the UE capability signaling 304 may apply on a UE-basis, or on a per-band basis. When the indication applies on a per-band bases, the UE 102 may provide an indication for more than one band.
[0054] The NTN device 106 receives the UE capability signaling, including the indication, and at 306, selects an eDRX cycle length (duration, period) for the UE 102 based at least in part on (e.g., in response to) the indicated UE capability, for example as part of selecting an eDRX configuration for the UE 102.
[0055] In one or more embodiments, the selected eDRX configuration is limited to eDRX cycles no greater than the validity timer length. For example, the eDRX cycle may be limited by a specific fraction of the ephemeris validity timer length, such that eDRX cycle length is X*(ephemeris validity timer length) , X ≤ 1.
[0056] In one or more embodiments, in cases when the serving cell of the NTN device 106, or a target neighbor cell for UE measurement, is of a non-stationary NTN device (e.g., a NGSO) , then eDRX cycles for configuration may be limited to no more than 10.24 seconds. That is, in some examples, eDRX without PTW is configured.
[0057] In one or more embodiments, in cases when the serving cell of the NTN device 106, or a target neighbor cell for UE measurement, is of a non-stationary NTN device (e.g., a NGSO) , then no eDRX is configured (nor used) , and only legacy DRX can be configured (and used) .
[0058] In one or more embodiments, the DRX configuration is limited to eDRX cycles no greater than the serving cell service-time (e.g., the service-time for the serving cell of NTN device 106 that serves UE 102) . Additionally, or alternative the DRX configuration is limited such that at least one PTW is guaranteed to occur before the serving cell service-time expiration.
[0059] At 308, the NTN device 106 may select the validity timer duration based at least in part on (e.g., in response to) the indicated UE capability, for example as part of selecting an eDRX configuration for the UE 102.
[0060] In one or more embodiments, the NTN device 106 can extend the ephemeris validity timer length to be comparable to the eDRX cycle periodicity. For example, the NTN device 106 can select the validity timer duration to be up to 10485.76 second, which in some cases corresponds to the longest eDRX cycle available to the NTN device 106 for configuration for the UE 102. For example, the NTN device 106 may select the validity timer duration to be no less than the UE-supported eDRX cycle. In some embodiments, a field may be defined as follows: ntn-UlSyncValidityDuration-r19 ENUMERATED {X, Y, Z, …} ; where X, Y, Z >900 seconds.
[0061] At 310, the NTN device 106 transmits an indication of the discontinuous reception configuration for the UE 102. As further described herein the discontinuous reception configuration may be or include an eDRX configuration, a DRX configuration, or both.
[0062] The UE 102 may then operate at 312 according to the discontinuous reception configuration received from the NTN device 106, according to one or more aspects described herein, including receiving ephemeris information 314 for NTN device 106.
[0063] FIG. 3B shows an example timing diagram 302, 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 reduced capability user equipment in non-terrestrial networks, as further described herein. Timing diagram 302 generally illustrates the example described above with reference to signaling diagram 301 where the selected eDRX configuration is limited to eDRX cycles no greater than the validity timer length.
[0064] The timing diagram includes an eDRX periodicity 324 corresponding to the eDRX cycle duration received by a UE 102 as part of the discontinuous reception configuration (e.g., eDRX configuration) , which also indicates a PTW 326. Sleep duration 328 corresponds to the time duration of the eDRX periodicity 324 between paging time windows, for example between the PTW 326 and a next PTW 326-a. At 330, the UE 102 may obtain ephemeris information for the NTN device 106 at 330, and set a duration of a validity timer 332. In one or more embodiments, the NTN device 106 may have configured the UE 102 with an eDRX periodicity 324 (e.g., of N seconds) that is no greater than the duration of the validity timer 332 (e.g., the duration of the validity timer 332 is greater than or equal to N. As such, the validity timer expires during the next PTW 326-a, at 336. By such restriction at NTN device 106, and the corresponding configuration for the UE 102, the UE 102 may obtain the second (updated) ephemeris information for NTN device 106 at 334, once the UE 102 is already awake for the next PTW 326-a.
[0065] In some examples, NTN device 106 is restricted such that the eDRX cycles is a fraction of the invalidity timer duration. As a specific example, if ephemeris validity timer length is 900 seconds, then the eDRX cycle can be up to 900 second. As a result, the UE 102 will have at least one PTW before the validity timer expires at 336, and UE will anyway have one PTW for ephemeris information renew before validity timer expiration.
[0066] FIG. 4 shows an example method 400 of wireless communication by a UE. In some cases, the UE may be the wireless device 702 or UE 102. In some cases, the method 400 may be performed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores, and memory that is coupled to the processor core (s) . The memory may store instructions that, when executed by the processor core (s) , causes the baseband processor to perform the operations of the method 400. As the baseband processor performs the operations of the method 400, the baseband processor may also cause other components of the UE to perform, or discontinue, various operations.
[0067] At 402, the method 400 includes receiving, from an NTN device serving the UE (e.g., a RedCap UE) , control signaling that indicates a duration of a validity timer for first ephemeris information of the NTN device.
[0068] At 404, the method 400 includes entering a sleep duration of an extended discontinuous reception cycle configured for the UE, the sleep duration being a time duration between consecutive paging time windows of the extended discontinuous reception cycle.
[0069] At 406, the 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 for the NTN device.
[0070] At 408, the method 400 includes receiving, from the NTN device and based at least in part on waking up during the sleep duration, a control message that includes the second ephemeris information of the NTN device.
[0071] In some embodiments, waking up during the sleep duration includes waking up prior to an expiration of the validity timer to listen for the control message that includes the second ephemeris information.
[0072] In some embodiments, waking up during the sleep duration includes waking up, after an expiration of the validity timer and prior to a next paging time window of the extended discontinuous reception cycle to listen for the control message that includes the second ephemeris information.
[0073] In one or more embodiments, the method further includes determining, during the sleep duration, that a speed of the UE satisfies a speed threshold, the waking up in response to the determining. In one or more embodiments, the method further includes determining, during the sleep duration, that a distance between the UE and the NTN device serving the UE is greater than or equal to a distance threshold, the waking up in response to the determining. In one or more embodiments, the method further includes determining, during the sleep duration, that a distance between the UE and a neighboring NTN device is less than or equal to a distance threshold, the waking up in response to the determining. In some embodiments, waking up during the sleep duration includes waking up prior to expiration of a service timer for the NTN device serving the UE.In one or more embodiments, the method further includes waking up during the sleep duration includes waking up during the sleep duration according to a discontinuous reception cycle based at least in part on the NTN device serving the UE being a non-stationary NTN device. In one or more embodiments, the method further includes waking up during the sleep duration according to a discontinuous reception cycle based at least in part on the NTN device serving the reduced capability UE covering a non-Earth fixed cell. In one or more embodiments, the method further includes waking up during the sleep duration includes waking up during the sleep duration according to a discontinuous reception cycle based at least in part on a neighboring NTN device to be measured by the UE being a non-stationary satellite, the control signaling received at least in part in response to the transmitted UE capability signaling. In one or more embodiments, the method further includes waking up during the sleep duration comprises waking up during the sleep duration according to a discontinuous reception cycle based at least in part on a neighboring NTN device to be measured by the reduced capability UE covering a non-Earth fixed cell.
[0074] In one or more embodiments, the method further includes transmitting UE capability signaling that indicates whether the UE supports the extended discontinuous reception cycle being greater than 10.24 seconds, the control signaling 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 the extended discontinuous reception cycle being greater than 10.24 seconds is applicable to non-stationary NTN devices. In one or more embodiments, the method further includes transmitting UE capability signaling that indicates a duration of extended discontinuous reception cycles supported by the UE.
[0075] In one or more embodiments, the method further includes listening, using the second ephemeris information, for paging messages transmitted by the NTN device during a next paging time window.
[0076] The method 400 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
[0077] FIG. 5 shows an example method 500 of wireless communication by a network device. In one or more embodiments, method 500 supports one or more aspects of enhanced discontinuous reception operation for reduced capability user equipment in non-terrestrial networks, as further described herein. In some cases, the network device may be the network device 104, network device 720, or one of the other network devices described herein. The method 500 may be performed using a processor, a transceiver (e.g., main radio) , or other components of the network device.
[0078] At 502, the method 500 includes receiving, from a RedCap UE, UE capability signaling that indicates a duration of a UE-supported extended discontinuous reception cycle.
[0079] At 504, the method 500 includes transmitting, to the RedCap UE and at least in part in response to the duration of the UE-supported extended discontinuous reception cycle, a discontinuous reception configuration for the RedCap UE and a validity timer duration for ephemeris information transmitted by the NTN device.
[0080] In one or more embodiments, the method further includes selecting, based at least in part on the NTN device being a non-stationary NTN device, the duration of an extended discontinuous reception cycle for the UE to be no greater than the validity timer duration for the ephemeris information, 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, based at least in part on the NTN device being a non-stationary NTN device, the duration of an extended discontinuous reception cycle for the UE to be no greater than 10.
[0082] In one or more embodiments, the method further includes selecting, based at least in part on the NTN device being a non-stationary NTN device, a discontinuous reception cycle length for the UE, the discontinuous reception configuration indicating the selected discontinuous reception cycle length; and refraining, based at least in part on the NTN device being the non-stationary NTN device, from configuring an extended discontinuous reception operation.
[0083] In one or more embodiments, the method further includes selecting the validity timer duration to be no less than the UE-supported extended discontinuous reception cycle.
[0084] In one or more embodiments, the method further includes selecting the duration of an extended discontinuous reception cycle for the UE to be no greater than a duration of a service timer for 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 the 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 the UE on a per-band basis, the discontinuous reception configuration indicating the selected duration and an indication of a radio frequency spectrum band to which the selected duration applies.
[0086] The method 500 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.
[0087] Embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 400 or 500. In the context of method 400, this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) . In the context of method 500, this non-transitory computer-readable media may be, for example, a memory of a network device (such as a memory 724 of a network device 720, as described herein) .
[0088] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method 400 or 500. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE) . In the context of method 500, this apparatus may be, for example, an apparatus of a network device (such as a network device 720, as described herein) .
[0089] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 400 or 500. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 702 that is a UE, as described herein) . In the context of the method 500, this apparatus may be, for example, an apparatus of a network device (such as a network device 720, as described herein) .
[0090] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 400, or 500.
[0091] 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 carry out one or more elements of the method 400 or 500. In the context of method 400, the processor may be a processor of a UE (such as a processor (s) 704 of a wireless device 702 that is a UE, as described herein) , and the instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 706 of a wireless device 702 that is a UE, as described herein) . In the context of method 500, the processor may be a processor of a network device (such as a processor (s) 722 of a network device 720, as described herein) , and the instructions may be, for example, located in the processor and / or on a memory of the network device (such as a memory 724 of a network device 720, as described herein) .
[0092] FIG. 6 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example wireless communication system 600 that operates in conjunction with the LTE system standards or specifications and / or 5G or NR system standards or specifications, as provided by 3GPP technical specifications.
[0093] As shown, the wireless communication system 600 includes UE 602 and UE 604 (although any number of UEs may be used) . In this example, the UE 602 and the UE 604 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.
[0094] The UE 602 and UE 604 may be configured to communicatively couple with a RAN 606. In embodiments, the RAN 606 may be NG-RAN, E-UTRAN, etc. The UE 602 and UE 604 utilize connections (or channels) (shown as connection 608 and connection 610, respectively) with the RAN 606, each of which comprises a physical communications interface. The RAN 606 can include one or more network devices, such as base station 612 and base station 614, that enable the connection 608 and connection 610.
[0095] In this example, the connection 608 and connection 610 are air interfaces to enable such communicative coupling and may be consistent with RAT (s) used by the RAN 606, such as, for example, an LTE and / or NR.
[0096] In some embodiments, the UE 602 and UE 604 may also directly exchange communication data via a sidelink interface 616. The UE 604 is shown to be configured to access an access point (shown as AP 618) via connection 620. By way of example, the connection 620 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 618 may comprise a router. In this example, the AP 618 may be connected to another network (for example, the Internet) without going through a CN 624.
[0097] In embodiments, the UE 602 and UE 604 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 612 and / or the base station 614 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.
[0098] In some embodiments, all or parts of the base station 612 or base station 614 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 612 or base station 614 may be configured to communicate with one another via interface 622. In embodiments where the wireless communication system 600 is an LTE system (e.g., when the CN 624 is an EPC) , the interface 622 may be an X2 interface. The X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 600 is an NR system (e.g., when CN 624 is a 5GC) , the interface 622 may be an Xn interface. The Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 612 (e.g., a gNB) connecting to the 5GC and an eNB, and / or between two eNBs connecting to the 5GC (e.g., CN 624) .
[0099] The RAN 606 is shown to be communicatively coupled to the CN 624. The CN 624 may comprise one or more network elements 626, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 602 and UE 604) who are connected to the CN 624 via the RAN 606. The components of the CN 624 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0100] In embodiments, the CN 624 may be an EPC, and the RAN 606 may be connected with the CN 624 via an S1 interface 628. In embodiments, the S1 interface 628 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 612 or base station 614 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 612 or base station 614 and mobility management entities (MMEs) .
[0101] In embodiments, the CN 624 may be a 5GC, and the RAN 606 may be connected with the CN 624 via an NG interface 628. In embodiments, the NG interface 628 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 612 or base station 614 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 612 or base station 614 and access and mobility management functions (AMFs) .
[0102] Generally, an application server 630 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 624 (e.g., packet switched data services) . The application server 630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 602 and UE 604 via the CN 624. The application server 630 may communicate with the CN 624 through an IP communications interface 632.
[0103] FIG. 7 illustrates an example system 700 for performing signaling 738 between a wireless device 702 and a network device 720, according to embodiments described herein. The system 700 may be a portion of a wireless communication system as herein described. The wireless device 702 may be, for example, a UE of a wireless communication system. The network device 720 may be, for example, a base station (e.g., an eNB or a gNB) or a radio head of a wireless communication system.
[0104] The wireless device 702 may include one or more processor (s) 704. The processor (s) 704 may execute instructions such that various operations of the wireless device 702 are performed, as described herein. The processor (s) 704 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0105] In one or more embodiments, one or more of processor (s) 704 may be a baseband processor. In some embodiments, a baseband processor includes one or more cores coupled with memory and one or more interfaces, and other components or circuitry to facilitate or otherwise support wireless communications by the wireless device 702, including performing one or more operations further described herein. Cores of the baseband processor can include one or more of a wireless communication processor, a central processing unit, a graphical processing unit, an artificial intelligence engine, a security engine, an image signal processor, a sensing system, a location system, or a display processor. A core may also be referred to as, for example, a processor, processor core, processing unit, engine, or accelerator. One or more wireless communications processors may include support for cellular communications or wireless local area network (WLAN) communications.
[0106] The wireless device 702 may include a memory 706. The memory 706 may be a non-transitory computer-readable storage medium that stores instructions 708 (which may include, for example, the instructions being executed by the processor (s) 704) . The instructions 708 may also be referred to as program code or a computer program. The memory 706 may also store data used by, and results computed by, the processor (s) 704.
[0107] The wireless device 702 may include one or more transceiver (s) 710 (also collectively referred to as a transceiver 710) that may include radio frequency (RF) transmitter and / or receiver circuitry that use the antenna (s) 712 of the wireless device 702 to facilitate signaling (e.g., the signaling 738) to and / or from the wireless device 702 with other devices (e.g., the network device 720) according to corresponding RATs.
[0108] The wireless device 702 may include one or more antenna (s) 712 (e.g., one, two, four, eight, or more) . For embodiments with multiple antenna (s) 712, the wireless device 702 may leverage the spatial diversity of such multiple antenna (s) 712 to send 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 the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) . MIMO transmissions by the wireless device 702 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 702 that multiplexes the data streams across the antenna (s) 712 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) . Some embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi- user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
[0109] In some embodiments having multiple antennas, the wireless device 702 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 712 are relatively adjusted such that the (joint) transmission of the antenna (s) 712 can be directed (this is sometimes referred to as beam steering) .
[0110] The wireless device 702 may include one or more interface (s) 714. The interface (s) 714 may be used to provide input to or output from the wireless device 702. For example, a wireless device 702 that is a UE may include interface (s) 714 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 710 / antenna (s) 712 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
[0111] The wireless device 702 may include extended discontinuous reception manager 716. The extended discontinuous reception manager 716 may be implemented via hardware, software, or combinations thereof. For example, the extended discontinuous reception manager 716 may be implemented as a processor, circuit, and / or instructions 708 stored in the memory 706 and executed by the processor (s) 704. In some examples, the extended discontinuous reception manager 716 may be integrated within the processor (s) 704 and / or the transceiver (s) 710. For example, the extended discontinuous reception manager 716 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 704 or the transceiver (s) 710.
[0112] The extended discontinuous reception manager 716 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-7, from a wireless device or UE perspective. The extended discontinuous reception manager 716 may be configured to, for example, perform receiving, from a NTN device serving the UE, control signaling that indicates a duration of a validity timer for first ephemeris information of the NTN device, the UE being a reduced capability UE;entering a sleep duration of an extended discontinuous reception cycle configured for the UE, the sleep duration being a time duration between consecutive paging time windows of the extended discontinuous reception cycle; waking up, based at least in part on the duration of the validity timer, during the sleep duration to obtain second ephemeris information for the NTN device; and receiving, from the NTN device, a control message that includes the second ephemeris information of the NTN device based at least in part on waking up during the sleep duration.
[0113] The network device 720 may include one or more processor (s) 722. The processor (s) 722 may execute instructions such that various operations of the network device 720 are performed, as described herein. The processor (s) 722 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
[0114] The network device 720 may include a memory 724. The memory 724 may be a non-transitory computer-readable storage medium that stores instructions 726 (which may include, for example, the instructions being executed by the processor (s) 722) . The instructions 726 may also be referred to as program code or a computer program. The memory 724 may also store data used by, and results computed by, the processor (s) 722.
[0115] The network device 720 may include one or more transceiver (s) 728 (also collectively referred to as a transceiver 728) that may include RF transmitter and / or receiver circuitry that use the antenna (s) 730 of the network device 720 to facilitate signaling (e.g., the signaling 738) to and / or from the network device 720 with other devices (e.g., the wireless device 702) according to corresponding RATs.
[0116] The network device 720 may include one or more antenna (s) 730 (e.g., one, two, four, or more) . In embodiments having multiple antenna (s) 730, the network device 720 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
[0117] The network device 720 may include one or more interface (s) 732. The interface (s) 732 may be used to provide input to or output from the network device 720. For example, a network device 720 of a RAN (e.g., a base station, a radio head, etc. ) may include interface (s) 732 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 728 / antenna (s) 730 already described) that enables the network device 720 to communicate with other equipment in a network, and / or that enables the network device 720 to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the network device 720 or other equipment operably connected thereto.
[0118] The network device 720 may include at least one extended discontinuous reception manager 734. The extended discontinuous reception manager 734 may be implemented via hardware, software, or combinations thereof. For example, the extended discontinuous reception manager 734 may be implemented as a processor, circuit, and / or instructions 726 stored in the memory 724 and executed by the processor (s) 722. In some examples, the extended discontinuous reception manager 734 may be integrated within the processor (s) 722 and / or the transceiver (s) 728. For example, the extended discontinuous reception manager 734 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 722 or the transceiver (s) 728.
[0119] The extended discontinuous reception manager 734 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-7, from a network device perspective. The extended discontinuous reception manager 734 may be configured to, for example, perform receiving, from a UE that is a reduced capability UE, UE capability signaling that indicates a duration of a UE-supported extended discontinuous reception cycle; and transmitting, to the UE and at least in part in response to the duration of the UE-supported extended discontinuous reception cycle, a discontinuous reception configuration for the UE and a validity timer duration for ephemeris information transmitted by the NTN device.
[0120] For one or more embodiments, at least one of the components set forth in one or more of the preceding 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 connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, network device, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
[0121] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments) , unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
[0122] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) . The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.
[0123] The systems described herein pertain to specific embodiments but are provided as examples. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.
[0124] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein but may be modified within the scope and equivalents of the appended claims.
Claims
1.A baseband processor configured to:receive, from a non-terrestrial network (NTN) device, control signaling for a reduced capability user equipment (UE) that indicates a duration of a validity timer for first ephemeris information of the NTN device;cause the reduced capability UE to enter a sleep duration of an extended discontinuous reception cycle configured, the sleep duration being a time duration between consecutive paging time windows of the extended discontinuous reception cycle;cause the reduced capability UE to wake up during the sleep duration, based at least in part on the duration of the validity timer, to obtain second ephemeris information for the NTN device; andreceive, from the NTN device and based at least in part on waking up during the sleep duration, a control message that includes the second ephemeris information of the NTN device.2.The baseband processor of claim 1, further configured to:wake up prior to an expiration of the validity timer to listen for the control message that includes the second ephemeris information.3.The baseband processor of claim 1, further configured to:wake up, prior to a next paging time window of the extended discontinuous reception cycle to listen for the control message that includes the second ephemeris information.4.The baseband processor of claim 1, further configured to:determine, during the sleep duration, that a speed of the reduced capability UE satisfies a speed threshold, the baseband processor waking up in response to the determining.5.The baseband processor of claim 1, further configured to:determine, during the sleep duration, that a distance between the reduced capability UE and the NTN device serving the reduced capability UE is greater than or equal to a distance threshold, the baseband processor waking up in response to the determining.6.The baseband processor of claim 1, further configured to:determine, during the sleep duration, that a distance between the reduced capability UE and a neighboring NTN device is less than or equal to a distance threshold, the baseband processor waking up in response to the determining.7.The baseband processor of claim 1, further configured to:cause the reduced capability UE to wake up prior to expiration of a service timer for the NTN device serving the reduced capability UE.8.The baseband processor of claim 1, further configured to:cause the reduced capability UE to wake up during the sleep duration according to a discontinuous reception cycle based at least in part on the NTN device serving the reduced capability UE being a non-stationary NTN device.9.The baseband processor of claim 1, further configured to:cause the reduced capability UE to wake up during the sleep duration according to a discontinuous reception cycle based at least in part on the NTN device serving the reduced capability UE covering a non-Earth fixed cell.10.The baseband processor of claim 1, further configured to:cause the reduced capability UE to wake up during the sleep duration comprises waking up during the sleep duration according to a discontinuous reception cycle based at least in part on a neighboring NTN device to be measured by the reduced capability UE being a non-stationary satellite.11.The baseband processor of claim 1, further configured to:cause the reduced capability UE to wake up during the sleep duration comprises waking up during the sleep duration according to a discontinuous reception cycle based at least in part on a neighboring NTN device to be measured by the reduced capability UE covering a non-Earth fixed cell.12.The baseband processor of claim 1, further configured to:transmit UE capability signaling that indicates whether the reduced capability UE supports the extended discontinuous reception cycle being greater than 10.24 seconds, the control signaling received at least in part in response to the transmitted UE capability signaling, wherein the UE capability signaling further comprises an indication that the reduced capability UE supporting the extended discontinuous reception cycle being greater than 10.24 seconds is applicable to non-stationary NTN devices.13.The baseband processor of claim 1, further configured to:transmit UE capability signaling that indicates a duration of extended discontinuous reception cycles supported by the reduced capability UE.14.A method of wireless communication at a non-terrestrial network (NTN) device, comprising:receiving, from a reduced capability user equipment (UE) , UE capability signaling that indicates a duration of a UE-supported extended discontinuous reception cycle; andtransmitting, to the reduced capability UE and at least in part in response to the duration of the UE-supported extended discontinuous reception cycle, a discontinuous reception configuration for the reduced capability UE and a validity timer duration for ephemeris information transmitted by the NTN device.15.The method of claim 14, further comprising:selecting, based at least in part on the NTN device being a non-stationary NTN device, the duration of an extended discontinuous reception cycle for the reduced capability UE to be no greater than the validity timer duration for the ephemeris information, the discontinuous reception configuration indicating the selected duration of the extended discontinuous reception cycle.16.The method of claim 14, further comprising:selecting, based at least in part on the NTN device being a non-stationary NTN device, the duration of an extended discontinuous reception cycle for the reduced capability UE to be no greater than 10.24 seconds, the discontinuous reception configuration indicating the selected duration of the extended discontinuous reception cycle.17.The method of claim 14, further comprising:selecting, based at least in part on the NTN device being a non-stationary NTN device, a discontinuous reception cycle length for the reduced capability UE, the discontinuous reception configuration indicating the selected discontinuous reception cycle length; andrefraining, based at least in part on the NTN device being the non-stationary NTN device, from configuring an extended discontinuous reception operation.18.The method of claim 14, further comprising:selecting the validity timer duration to be no less than the UE-supported extended discontinuous reception cycle.19.The method of claim 14, further comprising:selecting the duration of an extended discontinuous reception cycle for the reduced capability UE to be no greater than a duration of a service timer for the NTN device serving the reduced capability UE, the discontinuous reception configuration indicating the selected duration of the extended discontinuous reception cycle.20.A method of wireless communication at a reduced capability user equipment (UE) , comprising:receiving, from a non-terrestrial network (NTN) device serving the reduced capability UE, control signaling that indicates a duration of a validity timer for first ephemeris information of the NTN device;entering a sleep duration of an extended discontinuous reception cycle configured for the reduced capability UE, the sleep duration being a time duration between consecutive paging time windows of the extended discontinuous reception cycle;waking up during the sleep duration, based at least in part on the duration of the validity timer, to obtain second ephemeris information for the NTN device; andreceiving, from the NTN device and based at least in part on waking up during the sleep duration, a control message that includes the second ephemeris information of the NTN device.
Citation Information
Patent Citations
Satellite communication method, device and system
CN115189747A
Discontinuous coverage in NR NTN and IoT NTN systems
WO2023010336A1
Sleep wakeup methods for discontinuous coverage in non- terrestrial network
WO2023015132A1
Managing discontinuous coverage and discontinuous reception in ntn
WO2023211833A1