US11792881B2 - Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation - Google Patents
Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation Download PDFInfo
- Publication number
- US11792881B2 US11792881B2 US17/447,831 US202117447831A US11792881B2 US 11792881 B2 US11792881 B2 US 11792881B2 US 202117447831 A US202117447831 A US 202117447831A US 11792881 B2 US11792881 B2 US 11792881B2
- Authority
- US
- United States
- Prior art keywords
- upd
- minimum
- update interval
- anchor
- trs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/0035—Synchronisation arrangements detecting errors in frequency or phase
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- This application relates generally to wireless communication systems, including carrier aggregation in cellular systems.
- Wireless mobile communication technology uses various standards and protocols to transmit data between a base station 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 Wi-Fi®).
- 3GPP 3rd Generation Partnership Project
- LTE long term evolution
- NR 3GPP new radio
- Wi-Fi® IEEE 802.11 standard for wireless local area networks
- 3GPP radio access networks
- 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).
- GSM global system for mobile communications
- EDGE enhanced data rates for GSM evolution
- GERAN Universal Terrestrial Radio Access Network
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- NG-RAN Next-Generation Radio Access Network
- Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE.
- RATs radio access technologies
- 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)
- NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR).
- the E-UTRAN may also implement NR RAT.
- NG-RAN may also implement LTE RAT.
- a base station used by a RAN may correspond to that RAN.
- E-UTRAN base station 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).
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- eNodeB enhanced Node B
- NG-RAN base station is a next generation Node B (also sometimes referred to as a or g Node B or gNB).
- a RAN provides its communication services with external entities through its connection to a core network (CN).
- CN core network
- E-UTRAN may utilize an Evolved Packet Core (EPC)
- NG-RAN may utilize a 5G Core Network (5GC).
- EPC Evolved Packet Core
- 5GC 5G Core Network
- FIG. 1 illustrates early wake-ups on available component carriers before an Active Time in accordance with aspects of certain embodiments.
- FIG. 2 illustrates normalized frequency changes due to Doppler over time for a UE passing a base station in accordance with aspects of certain embodiments.
- FIG. 3 illustrates updating a frequency offset delta between component carriers in a first DRX cycle and applying the frequency offset delta in a second DRX cycle in accordance with one embodiment.
- FIG. 4 illustrates an extension of the example shown in FIG. 3 across a plurality of DRX cycles in accordance with one embodiment.
- FIG. 5 is a flowchart of a method for a UE to schedule wake-ups on a specific component carrier for frequency offset delta tracking in accordance with one embodiment.
- FIG. 6 illustrates an example of a UE scheduling wake-ups for frequency offset delta tracking in accordance with one embodiment.
- FIG. 7 is a block diagram illustrating determination of a minimum update interval ⁇ t upd in accordance with one embodiment.
- FIG. 8 is a flowchart of a method for a UE to perform frequency offset delta tracking between an anchor component carrier and a non-anchor component carrier in accordance with one embodiment.
- FIG. 9 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
- FIG. 10 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.
- a UE Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
- Suitable reference signals for NR in Connected mode DRX include a tracking reference signal (TRS) and a synchronization signal block (SSB).
- TRS tracking reference signal
- SSB synchronization signal block
- certain embodiments disclosed herein are described with respect to TRS. Persons skilled in the art will recognize from the disclosure herein, however, that such embodiments are not so limited and may be applicable to other types of reference signals, such as SSB. Further, certain embodiments may be applicable to a combination of SSB and TRS (e.g., using SSB on CC0 and TRS on CC1).
- TRS may be transmitted with a certain periodicity (e.g., ⁇ 10 ms).
- the periodicity of the TRS in NR can present challenges in certain situations. For example, during normal reception phases of NR, reference signals such as TRS are regularly received (e.g., every 10-20 ms) to correct frequency and timing errors, including errors caused by Doppler and oscillator drifts. In inactivity phases, e.g. NR connected mode discontinuous reception (C-DRx), it is likely that no reference signals are available during discontinuous reception (DRX) Active Time. Therefore, early wake-ups during non-Active Time are scheduled to perform tracking updates. It is useful to schedule as few additional wake-ups as possible to save power and as many wake-ups as necessary for ensuring adequate demodulation performance.
- C-DRx NR connected mode discontinuous reception
- DRX discontinuous reception
- FIG. 1 illustrates early wake-ups on active CCs before an Active Time (shown as an “ON” state) during a DRX cycle to provide regular tracking updates on the CCs.
- an Active Time shown as an “ON” state
- the UE may wake up during the non-Active Time of the DRX cycle to measure TRS 102 , TRS 104 , TRS 106 , and TRS 108 to determine frequency offsets on both a first CC (shown as CC0) and a second CC (shown as CC1).
- various radio frequency (RF) and baseband (BB) components of the UE are frequently active. See, e.g., RF CC0 activity, RF CC1 activity, and BB activity shown in FIG. 1 being either active or in light sleep modes during the non-Active Time (rather than in a deep sleep mode).
- Misaligned TRS can further reduce RF and/or BB sleep durations and UE power efficiency, since longer deep sleep durations are split into shorter light sleep durations, which increases power consumption.
- Frequency error at a UE may be caused by, for example, UE oscillator frequency drift (which may be CC-independent), Doppler frequency shift (which may be velocity and CC-dependent), and base station oscillator frequency drift (which may be CC-dependent).
- base station oscillator frequency drift is typically small and slow.
- Doppler frequency changes may also be slow compared to UE oscillator frequency drift.
- FIG. 2 illustrates normalized frequency changes due to Doppler over time for a UE passing a base station (BS) at 120 kilometers per hour (km/h) at a carrier frequency of 4 gigahertz (GHz).
- BS base station
- GHz gigahertz
- relative Doppler frequency change is smaller than 1% for a duration between updates of 320 ms.
- the Doppler statistics may only need to be updated approximately every 320 ms while the UE oscillator frequency drift may need to be tracked more frequently.
- certain embodiments disclosed herein only occasionally (not every C-DRx cycle) perform tracking updates on all CCs and determine a frequency offset (FO) delta between an anchor CC and a non-anchor CC to capture changes of CC-dependent components.
- FO frequency offset
- FIG. 3 illustrates updating an FO delta between CCs in a first DRX cycle and applying the FO delta in a second DRX cycle according to certain embodiments.
- CC0 is an anchor CC
- CC1 is a non-anchor CC. Skilled persons will recognize from the disclosure herein that the illustrated concepts may be applied to any number of additional non-anchor CCs.
- the UE measures, in an active state, a TRS 302 on CC0 and a TRS 304 on CC1.
- the UE determines a first FO for the CC0, which may be based on the UE's oscillator frequency error (common for all CCs), a base station's frequency error for CC0, and the Doppler frequency for CC0.
- the UE determines a second FO for the CC1, which may be based on the UE's oscillator frequency error (common for all CCs), a base station's frequency error for CC1, and the Doppler frequency for CC1.
- the UE determines an FO delta (i.e., difference) between the CC0 and the CC1.
- the FO delta captures the changes between the CC-dependent components.
- the UE wakes up and measures a TRS 306 for the CC0. Based on a TRS reception, the UE then determines an updated first FO for the CC0 based on current channel conditions, velocity, and oscillator temperatures. However, rather than waking up to measure a TRS for CC1 during the time period t 2 , the UE applies the FO delta determined during the time period t 1 to update the second FO for the CC1. Thus, rather than being in an active mode or a light sleep mode throughout the time period t 2 (as in the time period t 1 ), the UE experiences a prolonged sleep duration 308 that extends into the time period t 2 .
- FIG. 4 extends the example shown in FIG. 3 across a plurality of DRX cycles according to certain embodiments.
- the UE performs tracking updates on TRS signals and updates the FO delta between CC0 and CC1 (and any other non-anchor CCs) during time periods t 1 and t 4 to capture changes of CC-dependent components.
- the UE obtains CC-independent information only on CC0 (the anchor CC) to reduce the number of wake-ups on the non-anchor CCs to a minimum.
- the tracking results of the anchor CC are used for the non-anchor CC(s) by applying the FO delta (e.g., with no wake-up to measure TRS for CC1 during time periods t 2 and t 3 ).
- values such as the 40 ms DRX cycle are not limiting and are provided by way of example only.
- the illustrated pattern is only an example and that other patterns are also possible.
- the overall update interval ⁇ t upd is determined by taking a minimum of other parameter update intervals such as a power delay profile (PDP) update interval, an FO update interval, a Doppler shift update interval, and timing offset (TO) update interval.
- PDP power delay profile
- TO timing offset
- the update rate of the FO delta between the anchor CC and non-anchor CC(s) may depend on how long Doppler and base station oscillator frequency drift remain approximately constant. As discussed above with respect to FIG. 2 , simulation results show that even at high UE velocities (120 km/h), the Doppler remains approximately constant for 320 ms. In case of a C-DRx cycle of 40 ms as shown in the example of FIG.
- FO delta tracking may be described mathematically.
- TRS wake-up at t 2 can be skipped for CC1. See, e.g., FIG. 3 .
- the usage of certain embodiments disclosed herein may be detected, for example, by monitoring whether and how the RF and/or BB activities and power consumption change when switching from single CC to CA.
- an identical C-DRx configuration may be used for all CCs (e.g., same TRS positions and periodicities). If an embodiment described herein is used, only a single CC (e.g., anchor CC) shows regular activities during C-DRx non-Active Time, while other CCs show a different behavior (i.e., less active), even though they are configured in the same way as the more active anchor CC.
- embodiments disclosed herein may be detected by configuring different TRS positions and periodicities for different CCs and observing when the UE wakes up for TRS receptions.
- CC0 may be configured with TRS shortly before an ON duration and CC1 may be configured with TRS 40 ms before an ON duration. Then, whether and how often UE wakes up for the TRS located 40 ms before the ON duration may be monitored. If the UE does not wake up every C-DRx cycle for the TRS located 40 ms before the ON duration, it is an indication that a disclosed embodiment is used.
- FIG. 5 is a flowchart of a method 500 for a UE to schedule wake-ups on a specific CC for FO delta tracking according to one embodiment.
- the method may be used to ensure that only a last possible TRS before an Active Time is used (i.e., no wake-ups in the beginning or middle of a non-Active Time).
- the method 500 begins, in block 502 , before entering a non-Active Time (NAT) (e.g., light sleep or deep sleep).
- NAT non-Active Time
- the method 500 includes determining whether the CC is an anchor CC. If the CC is an anchor CC, at block 518 , the method 500 includes using a baseline single-carrier C-DRx procedure, such as that shown in FIG. 1 . If the CC is not an anchor CC, in block 506 , the method 500 includes determining a minimum update interval ⁇ t upd taking into account FO, TO, PDP, and Doppler. An example of determining the minimum update interval ⁇ t upd is discussed below with respect to FIG. 7 .
- the method 500 includes comparing the minimum update interval ⁇ t upd to a DRX cycle duration ⁇ t DrxCycle . If the minimum update interval ⁇ t upd is less than the DRX cycle duration ⁇ t DrxCycle , at block 518 , the method 500 includes using the baseline single-carrier C-DRx procedure, such as that shown in FIG. 1 . If ⁇ t upd > ⁇ t DrxCycle , then in block 510 the method 500 includes calculating a time duration ⁇ t oppNextButOne from a last performed TRS reception to a possible TRS reception in the next but one NAT (i.e., the NAT after the next NAT). As discussed below with respect to FIG.
- the UE determines a first time duration ⁇ t oppNextButOne in CC1 corresponding to the time (80 ms) between receiving a last TRS 606 and a possible TRS reception 608 in a second DRX cycle 610 , where a first deep sleep mode after the first ON duration 602 in the first DRX cycle 604 is the next NAT and a second deep sleep mode after a second ON duration 612 in the second DRX cycle 610 is the next but one NAT.
- the method 500 includes comparing the time duration ⁇ t oppNextButOne to the minimum update interval ⁇ t upd . If the ⁇ t oppNextButOne is greater than the minimum update interval ⁇ t upd , then in block 514 the method 500 includes planning or scheduling an update of the frequency delta based on a TRS in the upcoming NAT. The method 500 then proceeds to the block 518 to use the baseline single-carrier C-DRx procedure. If, however, ⁇ t oppNextButOne ⁇ t upd , in block 516 the UE determines that no TRS reception is required in the upcoming sleep duration. The method 500 may then return to block 502 for the next NAT.
- Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 500 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include one or more non-transitory computer-readable media comprising 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 500 .
- This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 500 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising 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 500 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 500 .
- Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 500 .
- the processor may be a processor of a UE (such as a processor(s) 1004 of a wireless device 1002 that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein).
- FIG. 6 illustrates an example of a UE scheduling wake-ups for FO delta tracking according to one embodiment.
- the UE may use the method 500 shown in FIG. 5 .
- the example shown in FIG. 6 is for two CCs and a DRX cycle duration of 40 ms, and it is assumed that CC1's minimum update interval ⁇ t upd remains substantially constant at 140 ms. It may be noted that, in theory, an update may be required after 3.5 DRX cycles. However, since it is desired to use the last TRS occasion before an Active Time, the update in this example occurs every third DRX cycle.
- the UE performs a first decision process 614 .
- the UE determines the first time duration ⁇ t oppNextButOne in CC1 corresponding to the time (80 ms) between receiving the last TRS 606 and a possible TRS reception 608 in a second DRX cycle 610 .
- the UE does not update the FO delta in the first DRX cycle 604 or wake up for a possible TRS reception 616 . Rather, the UE remains in a deep sleep on CC1 until the next Active Time or second ON duration 612 in the second DRX cycle 610 .
- the UE performs a second decision process 618 .
- the UE determines a second time duration ⁇ t oppNextButOne in CC1 corresponding to a time (120 ms) between receiving the last TRS 606 and possibly receiving a TRS 620 in a third DRX cycle 622 .
- the UE does not update the FO delta in the second DRX cycle 610 or wake up for the possible TRS reception 608 .
- the UE remains in a deep sleep on CC1 until the next Active Time or third ON duration 624 in the third DRX cycle 622 .
- the UE performs a third decision process 626 .
- the UE determines a third time duration ⁇ t oppNextButOne in CC1 corresponding to a time (160 ms) between receiving the last TRS 606 and a possible TRS reception (not shown) in a next but one NAT.
- the UE schedules reception of the TRS 620 in the upcoming non-Active Time of the third DRX cycle 622 .
- the UE can then update the FO delta.
- the UE's power consumption may be considerably reduced.
- the disclosed solutions herein may be applied to timing errors (i.e., TO delta tracking). Further, embodiments disclosed herein may be applied to Idle mode scenarios, where only SSB is available for FO and/or TO updates. As discussed above, embodiments disclosed herein may also be applied in combination with SSB receptions in Connected mode DRX.
- FIG. 7 is a block diagram illustrating determination of a minimum update interval ⁇ t upd according to one embodiment.
- dynamic parameters, semi-static parameters, and predefined parameters are provided to a process 702 to determine a minimum update interval for TO estimation, a process 704 to determine a minimum update interval for PDP estimation, and a process 706 to determine a minimum update interval for Doppler estimation (also covering FO estimation).
- the dynamic parameters include a UE velocity estimate and a temperature drift estimate.
- the semi-static parameters include a subcarrier spacing (SCS), a channel bandwidth (BW) and/or sampling rate, and a carrier frequency.
- the predefined parameters include a demodulation performance (Perf) with respect to Doppler/PDP/TO drift, a TO capture range of parameter estimation algorithms, and an oscillator drift model.
- Perf demodulation performance
- a minimum function 708 is used to determine the overall update interval ⁇ t upd by taking a minimum of the other parameter update intervals.
- the minimum PDP update interval ⁇ t upd,PDP may be based on a basic performance requirement that a maximum PDP shift is smaller than one sample.
- the minimum FO update interval ⁇ t upd,FO may depend on Doppler shift (CC-dependent), UE oscillator frequency drift (CC-independent), and BS oscillator frequency drift (CC-dependent).
- the UE oscillator frequency drift may be sufficiently compensated for by the anchor CC, and therefore may not be relevant to the calculation of the minimum FO update interval ⁇ t upd,FO .
- the BS oscillator frequency drift is typically small and slow, and therefore may be neglected in the calculation of the minimum FO update interval ⁇ t upd,FO .
- the Doppler shift may be treated as a separate parameter estimate (see below), e.g., ⁇ t upd,FO ⁇ t upd,Doppler .
- the minimum TO update interval ⁇ t upd,TO may be based on synchronization and demodulation performance. For synchronization, the TO is selected to be smaller than a TO capture range of TRS. For the demodulation performance, a maximum allowed TO and resulting update interval is determined by performance simulations.
- the minimum TO update interval ⁇ t upd,TO may be based on UE velocity, temperature gradient, oscillator drift model, subcarrier spacing, TRS TO capture ranges, and demodulation performance requirement with respect to TO drift.
- errors may be considered such as timing drift of the oscillator and propagation delay change because of UE mobility.
- FIG. 8 is a flowchart of a method 800 for a UE to perform FO delta tracking between an anchor CC and a non-anchor CC for DRX CA according to one embodiment.
- the method 800 includes waking up to perform tracking updates on a plurality of successive DRX cycles.
- the method 800 includes: determining (block 804 ) a minimum update interval ⁇ t upd ; scheduling (in block 806 ) wake-ups on a first subset of the plurality of successive DRX cycles based on the minimum update interval ⁇ t upd ; for the first subset of the plurality of successive DRX cycles with scheduled wake-ups, performing (in block 808 ) the tracking updates and updating an FO delta between the anchor CC and the non-anchor CC; and for a second subset of the plurality of successive DRX cycles without the scheduled wake-ups, applying (in block 810 ) the FO delta to correct for a frequency error on the non-anchor CC.
- waking up to perform tracking updates on the anchor CC comprises: receiving a tracking reference signal (TRS) or a synchronization signal block (SSB) on the anchor CC; and determining FO information on the anchor CC based at least in part on the TRS or the SSB.
- the FO information may include, for example, CC-independent information and/or CC-dependent information. Applying the FO delta may include using the FO information determined for the anchor CC on the non-anchor CC.
- scheduling the wake-ups for the non-anchor CC comprises, before entering a non-Active Time (NAT): determining the minimum update interval ⁇ t upd based on one or more of a minimum FO update interval ⁇ t upd,FO , a minimum timing offset (TO) update interval ⁇ t upd,TO , a minimum power delay profile (PDP) update interval ⁇ t upd,PDP , and a minimum Doppler shift update interval ⁇ t upd,Doppler ; in response to the minimum update interval ⁇ t upd being greater than a DRX cycle duration ⁇ t DrxCycle , calculating a time duration ⁇ t oppNextButOne from a last performed tracking reference signal (TRS) reception to a possible TRS reception in a next but one NAT; when the ⁇ t oppNextButOne is greater than the minimum update interval ⁇ t upd , scheduling an update of the FO delta based on a TRS in the NAT; and
- TRS tracking reference signal
- ⁇ t upd min( ⁇ t upd,FO , ⁇ t upd,TO , ⁇ t upd,PDP , ⁇ t upd,Doppler ).
- the minimum PDP update interval ⁇ t upd,PDP ⁇ (1/S ⁇ c/v), where v is a UE velocity, S is a sampling rate, and c is the speed of light.
- the minimum FO update interval ⁇ t upd,FO depends on one or more of a Doppler shift, a UE oscillator frequency drift, and a base station oscillator frequency drift.
- the minimum Doppler shift update interval ⁇ t upd,Doppler is based on simulations to determine expected Doppler shift changes and resulting update intervals for different UE velocities and carrier frequencies.
- the minimum TO update interval ⁇ t upd,TO is based one or more of a UE velocity, a temperature gradient, an oscillator drift model, a subcarrier spacing, a TRS TO capture range, and a demodulation performance requirement with respect to TO drift.
- Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 800 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include one or more non-transitory computer-readable media comprising 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 800 .
- This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 800 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising 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 800 .
- This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1002 that is a UE, as described herein).
- Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 800 .
- Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 800 .
- the processor may be a processor of a UE (such as a processor(s) 1004 of a wireless device 1002 that is a UE, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 1006 of a wireless device 1002 that is a UE, as described herein).
- FIG. 9 illustrates an example architecture of a wireless communication system 900 , according to embodiments disclosed herein.
- the following description is provided for an example wireless communication system 900 that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications.
- the wireless communication system 900 includes UE 902 and UE 904 (although any number of UEs may be used).
- the UE 902 and the UE 904 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.
- the UE 902 and UE 904 may be configured to communicatively couple with a RAN 906 .
- the RAN 906 may be NG-RAN, E-UTRAN, etc.
- the UE 902 and UE 904 utilize connections (or channels) (shown as connection 908 and connection 910 , respectively) with the RAN 906 , each of which comprises a physical communications interface.
- the RAN 906 can include one or more base stations, such as base station 912 and base station 914 , that enable the connection 908 and connection 910 .
- connection 908 and connection 910 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 906 , such as, for example, an LTE and/or NR.
- the UE 902 and UE 904 may also directly exchange communication data via a sidelink interface 916 .
- the UE 904 is shown to be configured to access an access point (shown as AP 918 ) via connection 920 .
- the connection 920 can comprise a local wireless connection, such as a connection consistent with any IEEE 902.11 protocol, wherein the AP 918 may comprise a Wi-Fi® router.
- the AP 918 may be connected to another network (for example, the Internet) without going through a CN 924 .
- the UE 902 and UE 904 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 912 and/or the base station 914 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.
- OFDM signals can comprise a plurality of orthogonal subcarriers.
- the base station 912 or base station 914 may be implemented as one or more software entities running on server computers as part of a virtual network.
- the base station 912 or base station 914 may be configured to communicate with one another via interface 922 .
- the interface 922 may be an X2 interface.
- the X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
- the interface 922 may be an Xn interface.
- the Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 912 (e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 924 ).
- the RAN 906 is shown to be communicatively coupled to the CN 924 .
- the CN 924 may comprise one or more network elements 926 , which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 902 and UE 904 ) who are connected to the CN 924 via the RAN 906 .
- the components of the CN 924 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).
- the CN 924 may be an EPC, and the RAN 906 may be connected with the CN 924 via an S1 interface 928 .
- the S1 interface 928 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 912 or base station 914 and a serving gateway (S-GW), and the S1-MME interface, which is a signaling interface between the base station 912 or base station 914 and mobility management entities (MMEs).
- S1-U S1 user plane
- S-GW serving gateway
- MMEs mobility management entities
- the CN 924 may be a 5GC, and the RAN 906 may be connected with the CN 924 via an NG interface 928 .
- the NG interface 928 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 912 or base station 914 and a user plane function (UPF), and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 912 or base station 914 and access and mobility management functions (AMFs).
- NG-U NG user plane
- UPF user plane function
- S1 control plane S1 control plane
- an application server 930 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 924 (e.g., packet switched data services).
- IP internet protocol
- the application server 930 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 902 and UE 904 via the CN 924 .
- the application server 930 may communicate with the CN 924 through an IP communications interface 932 .
- FIG. 10 illustrates a system 1000 for performing signaling 1032 between a wireless device 1002 and a network device 1018 , according to embodiments disclosed herein.
- the system 1000 may be a portion of a wireless communications system as herein described.
- the wireless device 1002 may be, for example, a UE of a wireless communication system.
- the network device 1018 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.
- the wireless device 1002 may include one or more processor(s) 1004 .
- the processor(s) 1004 may execute instructions such that various operations of the wireless device 1002 are performed, as described herein.
- the processor(s) 1004 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.
- CPU central processing unit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- the wireless device 1002 may include a memory 1006 .
- the memory 1006 may be a non-transitory computer-readable storage medium that stores instructions 1008 (which may include, for example, the instructions being executed by the processor(s) 1004 ).
- the instructions 1008 may also be referred to as program code or a computer program.
- the memory 1006 may also store data used by, and results computed by, the processor(s) 1004 .
- the wireless device 1002 may include one or more transceiver(s) 1010 that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna(s) 1012 of the wireless device 1002 to facilitate signaling (e.g., the signaling 1032 ) to and/or from the wireless device 1002 with other devices (e.g., the network device 1018 ) according to corresponding RATs.
- RF radio frequency
- the wireless device 1002 may include one or more antenna(s) 1012 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 1012 , the wireless device 1002 may leverage the spatial diversity of such multiple antenna(s) 1012 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, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect).
- MIMO multiple input multiple output
- MIMO transmissions by the wireless device 1002 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1002 that multiplexes the data streams across the antenna(s) 1012 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).
- Certain 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).
- SU-MIMO single user MIMO
- MU-MIMO multi user MIMO
- the wireless device 1002 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 1012 are relatively adjusted such that the (joint) transmission of the antenna(s) 1012 can be directed (this is sometimes referred to as beam steering).
- the wireless device 1002 may include one or more interface(s) 1014 .
- the interface(s) 1014 may be used to provide input to or output from the wireless device 1002 .
- a wireless device 1002 that is a UE may include interface(s) 1014 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) 1010 /antenna(s) 1012 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).
- known protocols e.g., Wi-Fi®, Bluetooth®, and the like.
- the wireless device 1002 may include an FO delta tracking module 1016 .
- the FO delta tracking module 1016 may be implemented via hardware, software, or combinations thereof.
- the FO delta tracking module 1016 may be implemented as a processor, circuit, and/or instructions 1008 stored in the memory 1006 and executed by the processor(s) 1004 .
- the FO delta tracking module 1016 may be integrated within the processor(s) 1004 and/or the transceiver(s) 1010 .
- the FO delta tracking module 1016 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) 1004 or the transceiver(s) 1010 .
- the FO delta tracking module 1016 may be used for various aspects of the present disclosure, for example, aspects of FIG. 3 , FIG. 4 , FIG. 5 , FIG. 6 , FIG. 7 , and/or FIG. 8 .
- the network device 1018 may include one or more processor(s) 1020 .
- the processor(s) 1020 may execute instructions such that various operations of the network device 1018 are performed, as described herein.
- the processor(s) 1020 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.
- the network device 1018 may include a memory 1022 .
- the memory 1022 may be a non-transitory computer-readable storage medium that stores instructions 1024 (which may include, for example, the instructions being executed by the processor(s) 1020 ).
- the instructions 1024 may also be referred to as program code or a computer program.
- the memory 1022 may also store data used by, and results computed by, the processor(s) 1020 .
- the network device 1018 may include one or more transceiver(s) 1026 that may include RF transmitter and/or receiver circuitry that use the antenna(s) 1028 of the network device 1018 to facilitate signaling (e.g., the signaling 1032 ) to and/or from the network device 1018 with other devices (e.g., the wireless device 1002 ) according to corresponding RATs.
- transceiver(s) 1026 may include RF transmitter and/or receiver circuitry that use the antenna(s) 1028 of the network device 1018 to facilitate signaling (e.g., the signaling 1032 ) to and/or from the network device 1018 with other devices (e.g., the wireless device 1002 ) according to corresponding RATs.
- the network device 1018 may include one or more antenna(s) 1028 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 1028 , the network device 1018 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
- the network device 1018 may include one or more interface(s) 1030 .
- the interface(s) 1030 may be used to provide input to or output from the network device 1018 .
- a network device 1018 that is a base station may include interface(s) 1030 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 1026 /antenna(s) 1028 already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
- circuitry e.g., other than the transceiver(s) 1026 /antenna(s) 1028 already described
- 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.
- a baseband 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.
- circuitry associated with a UE, base station, 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.
- 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.
- personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
- personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Abstract
Description
AFCCC0(t 1)=−RFOUE(t 1)+F CC0,BS(t 1)+F CC0,Doppler(t 1); and
AFCCC1(t 1)=−RFOUE(t 1)+F CC1,BS(t 1)+F CC1,Doppler(t 1),
where RFOUE(t1) is the Reference Frequency Offset of the UE's reference oscillator and represents the UE oscillator frequency error (common for all CCs), AFCCC0 is the Automatic Frequency Correction applied at the UE for CC0, AFCCC1 is the Automatic Frequency Correction applied at the UE for CC1, FCC0,BS is the frequency offset of the base station for CC0, FCC1,BS is the frequency offset of the base station for CC1, FCC0,Doppler is the Doppler frequency for CC0, and FCC1,Doppler is the Doppler frequency for CC1.
AFCCC1(t 2)=AFCCC0(t 2)−ΔAFCCC0,CC1(t 2)≈AFCCC0(t 2)−ΔAFCCC0,CC1(t 1).
Claims (20)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/447,831 US11792881B2 (en) | 2021-09-16 | 2021-09-16 | Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation |
EP22195596.6A EP4152840B1 (en) | 2021-09-16 | 2022-09-14 | Frequency offset delta tracking for nr connected mode discontinuous reception carrier aggregation |
CN202211117291.3A CN115835385A (en) | 2021-09-16 | 2022-09-14 | Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/447,831 US11792881B2 (en) | 2021-09-16 | 2021-09-16 | Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation |
Publications (2)
Publication Number | Publication Date |
---|---|
US20230079512A1 US20230079512A1 (en) | 2023-03-16 |
US11792881B2 true US11792881B2 (en) | 2023-10-17 |
Family
ID=83318958
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/447,831 Active 2042-03-14 US11792881B2 (en) | 2021-09-16 | 2021-09-16 | Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation |
Country Status (3)
Country | Link |
---|---|
US (1) | US11792881B2 (en) |
EP (1) | EP4152840B1 (en) |
CN (1) | CN115835385A (en) |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6370188B1 (en) * | 1999-03-31 | 2002-04-09 | Texas Instruments Incorporated | Phase and frequency offset compensation in a telecommunications receiver |
US20050079845A1 (en) * | 2001-12-05 | 2005-04-14 | Christian Ansorge | Frequency offset correction based on the presence or absence of a received signal |
US20050089115A1 (en) * | 2003-09-05 | 2005-04-28 | Ralf Hartmann | Method and receiving unit for compensation for a frequency offset and/or for a change in the phase of a transmission channel over time by receiver-end evaluation of edge symbols of a received data burst |
US20050213678A1 (en) * | 2004-03-23 | 2005-09-29 | Infineon Technologies Ag | Tracking system comprised in an OFDM receiver |
US20070183518A1 (en) * | 2005-12-10 | 2007-08-09 | Samsung Electronics Co., Ltd. | Method and apparatus for estimating timing error and frequency offset of mimo system |
US20100118990A1 (en) * | 2008-11-13 | 2010-05-13 | Hwang-Soo Lee | Apparatus for synchronizing ofdm signal using open-loop frequency synchronization method and frequency offset estimation scheme using the apparatus |
US20100227569A1 (en) * | 2008-10-20 | 2010-09-09 | Interdigital Patent Holdings, Inc. | Control channel signaling and acquisition for carrier aggregation |
US20130142178A1 (en) * | 2006-09-19 | 2013-06-06 | Samsung Electronics Co., Ltd. | Method and apparatus for performing discontinuous reception operation by connected mode user equipment in a mobile communication system |
US20130170590A1 (en) * | 2010-09-17 | 2013-07-04 | Telefonaktiebolaget L M Ericsson (Publ) | Receiver Node and A Method Therein for Compensating Frequency Offset |
CN105871530A (en) * | 2016-03-29 | 2016-08-17 | 成都国腾电子集团有限公司 | High dynamic deviation change resisting timing tracking method |
US20160277256A1 (en) | 2015-03-17 | 2016-09-22 | Telefonaktiebolaget L M Ericsson (Publ) | Access node, control node, and various methods for adapting a reporting period for a user equipment |
US20170311194A1 (en) * | 2014-11-21 | 2017-10-26 | Sony Production | Telecommunications apparatus and method |
US20190173627A1 (en) | 2015-09-22 | 2019-06-06 | Comcast Cable Communications, Llc | Carrier Activation in a Multi-Carrier Wireless Network |
US20190215897A1 (en) * | 2018-01-11 | 2019-07-11 | Alireza Babaei | Discontinuous Reception And CSI |
CN114615122A (en) * | 2022-01-30 | 2022-06-10 | 北京邮电大学 | Frequency offset determination method and device for communication signals |
US20230007587A1 (en) * | 2021-07-02 | 2023-01-05 | Qualcomm Incorporated | Techniques for wireless communication in connected discontinuous reception mode |
-
2021
- 2021-09-16 US US17/447,831 patent/US11792881B2/en active Active
-
2022
- 2022-09-14 EP EP22195596.6A patent/EP4152840B1/en active Active
- 2022-09-14 CN CN202211117291.3A patent/CN115835385A/en active Pending
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6370188B1 (en) * | 1999-03-31 | 2002-04-09 | Texas Instruments Incorporated | Phase and frequency offset compensation in a telecommunications receiver |
US20050079845A1 (en) * | 2001-12-05 | 2005-04-14 | Christian Ansorge | Frequency offset correction based on the presence or absence of a received signal |
US20050089115A1 (en) * | 2003-09-05 | 2005-04-28 | Ralf Hartmann | Method and receiving unit for compensation for a frequency offset and/or for a change in the phase of a transmission channel over time by receiver-end evaluation of edge symbols of a received data burst |
US20050213678A1 (en) * | 2004-03-23 | 2005-09-29 | Infineon Technologies Ag | Tracking system comprised in an OFDM receiver |
US20070183518A1 (en) * | 2005-12-10 | 2007-08-09 | Samsung Electronics Co., Ltd. | Method and apparatus for estimating timing error and frequency offset of mimo system |
US20130142178A1 (en) * | 2006-09-19 | 2013-06-06 | Samsung Electronics Co., Ltd. | Method and apparatus for performing discontinuous reception operation by connected mode user equipment in a mobile communication system |
US20100227569A1 (en) * | 2008-10-20 | 2010-09-09 | Interdigital Patent Holdings, Inc. | Control channel signaling and acquisition for carrier aggregation |
US20100118990A1 (en) * | 2008-11-13 | 2010-05-13 | Hwang-Soo Lee | Apparatus for synchronizing ofdm signal using open-loop frequency synchronization method and frequency offset estimation scheme using the apparatus |
US20130170590A1 (en) * | 2010-09-17 | 2013-07-04 | Telefonaktiebolaget L M Ericsson (Publ) | Receiver Node and A Method Therein for Compensating Frequency Offset |
US20170311194A1 (en) * | 2014-11-21 | 2017-10-26 | Sony Production | Telecommunications apparatus and method |
US20160277256A1 (en) | 2015-03-17 | 2016-09-22 | Telefonaktiebolaget L M Ericsson (Publ) | Access node, control node, and various methods for adapting a reporting period for a user equipment |
US20190173627A1 (en) | 2015-09-22 | 2019-06-06 | Comcast Cable Communications, Llc | Carrier Activation in a Multi-Carrier Wireless Network |
CN105871530A (en) * | 2016-03-29 | 2016-08-17 | 成都国腾电子集团有限公司 | High dynamic deviation change resisting timing tracking method |
US20190215897A1 (en) * | 2018-01-11 | 2019-07-11 | Alireza Babaei | Discontinuous Reception And CSI |
US20230007587A1 (en) * | 2021-07-02 | 2023-01-05 | Qualcomm Incorporated | Techniques for wireless communication in connected discontinuous reception mode |
CN114615122A (en) * | 2022-01-30 | 2022-06-10 | 北京邮电大学 | Frequency offset determination method and device for communication signals |
Non-Patent Citations (2)
Title |
---|
Ericsson , "NRS transmission on non-anchor carriers", R1-1701894, 3GPP TSG RAN#88, Athens, Greece, Agenda Item 7.2.4.4, Feb. 13-17, 2017, 6 pages. |
Ericsson, St-Ericsson , "On Time and Frequency Synchronization on Additional Carrier Types", R1-112926, 3GPP TSG RAN WG1 Meeting #66bis, Zhuhai, China, Agenda Item 6.2.3, Oct. 10-14, 2011, 2 pages. |
Also Published As
Publication number | Publication date |
---|---|
US20230079512A1 (en) | 2023-03-16 |
EP4152840B1 (en) | 2023-12-27 |
EP4152840A1 (en) | 2023-03-22 |
CN115835385A (en) | 2023-03-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210059005A1 (en) | Discontinuous reception configuration for sidelink | |
US11924755B2 (en) | Facilitating discontinuous reception for mutli-panel user equipment | |
US10051611B2 (en) | Network scheduled device to device communication | |
US20200337110A1 (en) | Method and apparatus for low power consumption operation of terminal in mobile communication system | |
JP2013520050A (en) | Method and apparatus in a wireless communication system | |
US20230053871A1 (en) | Beam failure recovery for single dci-based m-trp urllc transmissions | |
US20220408356A1 (en) | Discontinuous reception wakeup techniques | |
US11930451B2 (en) | Techniques for wireless communication in connected discontinuous reception mode | |
US11503489B2 (en) | Channel measurement techniques in discontinuous reception scenarios | |
US20230239093A1 (en) | Reference signal resource processing method and apparatus, device, and readable storage medium | |
US11895592B2 (en) | Selecting reference signal occasions for wakeup | |
US11792881B2 (en) | Frequency offset delta tracking for NR connected mode discontinuous reception carrier aggregation | |
US11871344B2 (en) | Preference signaling for a multi-subscription wireless device | |
WO2023044738A1 (en) | Methods and apparatus for signaling and state transition for pdcch skipping and sssg switching | |
WO2023137584A1 (en) | Systems and methods for conserving network power with a beam pattern update for transmitted synchronization signal blocks | |
WO2023151019A1 (en) | Action delay for a common transmission configuration indication (tci) switch | |
WO2024065383A1 (en) | Semi-static indication of communication modes | |
US20230007695A1 (en) | Techniques for managing discontinuous operation for wireless communication | |
US20240015759A1 (en) | Adaptive Configuration for Monitoring a Downlink Control Channel | |
WO2023151036A1 (en) | Timing advance validation enhancements in configured grant small data transmissions | |
US20230089297A1 (en) | Adjusting a user equipment activity timing based on multiple signal sources for wireless network | |
US20240098639A1 (en) | Systems and methods for connected mode discontinuous reception on/off determinations | |
WO2024087135A1 (en) | Tracking reference signals for energy saving modes | |
US20240015654A1 (en) | Enhanced power saving technique based on wake-up signal functionality | |
US20240098838A1 (en) | Systems and methods for connected mode discontinuous reception on/off determinations |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: APPLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OHMANN, DAVID;YAN, HONGBO;FARAJIDANA, AMIR;AND OTHERS;SIGNING DATES FROM 20210916 TO 20210921;REEL/FRAME:057580/0365 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: AWAITING TC RESP, ISSUE FEE PAYMENT VERIFIED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |