US12557126B2ActiveUtilityA1

User equipment (UE) capability for radio resource control (RRC) based bandwidth part (BWP) switching delay

56
Assignee: APPLE INCPriority: May 13, 2019Filed: May 13, 2020Granted: Feb 17, 2026
Est. expiryMay 13, 2039(~12.8 yrs left)· nominal 20-yr term from priority
H04W 72/21H04W 72/044H04W 60/04H04W 76/22H04L 5/0007H04L 5/0044H04L 5/0078H04L 5/0096H04W 72/51H04L 5/0094
56
PatentIndex Score
0
Cited by
31
References
18
Claims

Abstract

The disclosure relates to RRC based BWP switching delay and use of UE capability information to minimize the amount of schedules BWP switching delay for those UE with capabilities that can properly transmit and receive data under lower BWP switching delay constraints.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . An apparatus for wireless communication, comprising:
 one or more memories configured to store instructions;   one or more processors coupled to the one or more memories, and when executing the instructions, configured to:
 cause to transmit, to a network node, UE capability information indicative of a bandwidth part (BWP) switching delay of a BWP switching triggered by a radio resource control (RRC) message; and 
 cause to communicate data with the network node according to the BWP switching delay, 
   wherein the UE capability information includes a selection from at least a first UE capability type and a second UE capability type, wherein the first UE capability type determines a first BWP switching delay; and the second UE capability type determines a second BWP switching delay greater than the first BWP switching delay.   
     
     
         2 . The apparatus of  claim 1 , wherein the one or more processors are further configured to:
 cause to receive a UE capability inquiry message from the network node; and   cause to transmit the UE capability information in response to the UE capability inquiry message, or   cause to transmit the UE capability information in conjunction with a registration process with the network node.   
     
     
         3 . The apparatus of  claim 1 , wherein the first BWP switching delay and the second BWP switching delay are independent of a slot length. 
     
     
         4 . The apparatus of  claim 1 , wherein the first BWP switching delay and the second BWP switching delay are predetermined, fixed time delay values. 
     
     
         5 . The apparatus of  claim 1 , wherein the first BWP switching delay and the second BWP switching delay are configured rather than fixed values. 
     
     
         6 . The apparatus of  claim 1 , wherein the UE capability information is communicated using radio resource control (RRC) based messaging. 
     
     
         7 . The apparatus of  claim 1 , wherein the one or more processors are further configured to receive on Physical Downlink Shared Channel (PDSCH) from the network node or transmit on Physical Uplink Shared Channel (PUSCH) to the network node on a new BWP at a time period, t, dictated by the BWP switching delay. 
     
     
         8 . The apparatus of  claim 7 , wherein the time period,
     t =(TRRCprocessingDelay+TBWPswitchDelayRRC)/NRslot length,   wherein TBWPswitchDelayRRC is a function of the BWP switching delay.   
     
     
         9 . The apparatus of  claim 1 , wherein the first BWP switching delay is equal to or smaller than 5 milliseconds, and wherein the second BWP switching delay is equal to or smaller than 10 milliseconds. 
     
     
         10 . A method of performing bandwidth part (BWP) switching, comprising:
 obtaining, from a network node, a triggering notification for user equipment (UE) capability reporting, the triggering notification comprising a UE capability inquiry message; and   transmitting, to the network node, UE capability information of a UE in response to the triggering notification,   wherein the UE capability information indicates a BWP switching delay of a BWP switching triggered by a radio resource control (RRC) message, wherein the UE capability information includes a selection from at least a first UE capability type and a second UE capability type, wherein the first UE capability type determines a first BWP switching delay value, and the second UE capability type determines a second BWP switching delay value greater than the first BWP switching delay value.   
     
     
         11 . The method of  claim 10 , wherein the triggering notification comprises a registration initialization procedure by which the UE registers with the network node. 
     
     
         12 . The method of  claim 10 , wherein the UE capability information is indicative of a time value reflecting a speed at which the UE can perform a BWP switching from a first BWP to a second, different BWP. 
     
     
         13 . The method of  claim 10 , wherein the first and second BWP switching delay values are independent of a slot length. 
     
     
         14 . The method of  claim 10 , wherein the first BWP switching delay value and the second BWP switching delay value are configured rather than fixed values. 
     
     
         15 . The method of  claim 10 , wherein transmitting the UE capability information comprising transmitting using radio resource control (RRC) based messaging. 
     
     
         16 . The method of  claim 10 , further comprising receiving data on a Physical Downlink Shared Channel (PDSCH) from the network node or transmit on Physical Uplink Shared Channel (PUSCH) to the network node on a new BWP at a time period, t, dictated by the BWP switching delay. 
     
     
         17 . The method of  claim 16 , wherein the time period,
     t =(TRRCprocessingDelay+TBWPswitchDelayRRC)/NRslot length,   wherein TBWPswitchDelayRRC is a function of the BWP switching delay.   
     
     
         18 . The method of  claim 17 , wherein if the BWP switching delay indicates a high capability, TBWPswitchDelayRRC is Xms; and if the BWP switching delay indicates a low capability that is less than the high capability, TBWPswitchDelayRRC is Yms, where 5 ms≤X<Y≤8 ms.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.