Techniques for configuring control resources using piggyback downlink control information

Abstract

A scheduling entity can schedule regular or periodic control resources (CORESETs) that are relatively sparse in the time domain compared to dynamic CORESETS. Sparsely scheduled regular CORESETs can reduce the overhead incurred by a user equipment for monitoring the control channels in the CORESETs or search spaces. When the network has a burst of data to send, the scheduling entity can use downlink control information (DCI) piggybacked in physical downlink shared channel (PDSCH) resources to schedule dynamic CORESETs between the regular CORESETs. The dynamic CORESETs can provide resources for a PDSCH and/or physical downlink shared channel (PUSCH).

What is claimed is: 
     
       1. A method of wireless communication at a scheduling entity, comprising:
 configuring a first control resource set (CORESET) and a second CORESET for wireless communication with a user equipment (UE); and 
 transmitting, to the UE, a piggyback downlink control information (DCI) in a downlink data channel using downlink data channel resources that are temporally configured between the first CORESET and the second CORESET, for altering one or more third CORESETs temporally configured between the first CORESET and the second CORESET. 
 
     
     
       2. The method of  claim 1 , wherein the piggyback DCI is configured to alter the one or more third CORESETs, at least in part, based on a time duration between the piggyback DCI and the one or more third CORESETs. 
     
     
       3. The method of  claim 1 , wherein the altering the one or more third CORESETs comprises at least one of:
 activating the one or more third CORESETs; 
 deactivating the one or more third CORESETs ahead of a time corresponding to the second CORESET; or 
 modifying the one or more third CORESETs. 
 
     
     
       4. The method of  claim 3 , wherein the activating the one or more third CORESETs comprises:
 scheduling a physical downlink control channel (PDCCH) in the activated one or more third CORESETs. 
 
     
     
       5. The method of  claim 3 , wherein the activating the one or more third CORESETs comprises:
 scheduling the one or more third CORESETs to occur before the upcoming second CORESET. 
 
     
     
       6. The method of  claim 3 , wherein the modifying the one or more third CORESETs comprises:
 modifying at least one parameter of the one or more third CORESETs, 
 wherein the at least one parameter comprises at least one of time-frequency resources, a resource mapping type, a precoding parameter, a beam configuration, an aggregation level, or a number of physical downlink control channel (PDCCH) candidates. 
 
     
     
       7. The method of  claim 1 ,
 wherein the piggyback DCI comprises a transmission configuration indicator (TCI) for the one or more third CORESETs, and 
 wherein the piggyback DCI is configured to alter the one or more third CORESETs based on the TCI and a time duration between the piggyback DCI and the one or more third CORESETs. 
 
     
     
       8. A scheduling entity, comprising:
 a communication interface configured to communicate with a user equipment (UE); 
 a memory; and 
 a processor operatively coupled with the communication interface and the memory, 
 wherein the processor and the memory are configured to:
 configure a first control resource set (CORESET) and a second CORESET for wireless communication with the UE; and 
 transmit, to the UE using the communication interface, a piggyback downlink control information (DCI) in a downlink data channel using downlink data channel resources that are temporally configured between the first CORESET and the second CORESET, for altering one or more third CORESETs temporally configured between the first CORESET and the second CORESET. 
 
 
     
     
       9. The scheduling entity of  claim 8 , wherein the piggyback DCI is configured to alter the one or more third CORESETs, at least in part, based on a time duration between the piggyback DCI and the one or more third CORESETs. 
     
     
       10. The scheduling entity of  claim 8 , wherein the processor and the memory are further configured to alter the one or more third CORESETs by at least one of:
 activating the one or more third CORESETs; 
 deactivating the one or more third CORESETs ahead of a time corresponding to the second CORESET; or 
 modifying the one or more third CORESETs. 
 
     
     
       11. The scheduling entity of  claim 10 , wherein the processor and the memory are further configured to:
 schedule a physical downlink control channel (PDCCH) in the activated one or more third CORESETs. 
 
     
     
       12. The scheduling entity of  claim 10 , wherein the processor and the memory are further configured to:
 schedule the activated one or more third CORESETs to occur before the upcoming second CORESET. 
 
     
     
       13. The scheduling entity of  claim 10 , wherein the processor and the memory are further configured to:
 modify at least one parameter of the one or more third CORESETs, 
 wherein the at least one parameter comprises at least one of time-frequency resources, a resource mapping type, a precoding parameter, a beam configuration, an aggregation level, or a number of physical downlink control channel (PDCCH) candidates. 
 
     
     
       14. The scheduling entity of  claim 8 ,
 wherein the piggyback DCI comprises a transmission configuration indicator (TCI) for the one or more third CORESETs, and 
 wherein the piggyback DCI is configured to alter the one or more third CORESETs based on the TCI and a time duration between the piggyback DCI and the one or more third CORESETs. 
 
     
     
       15. A method of wireless communication at a user equipment (UE), comprising:
 receiving, from a scheduling entity, control information for configuring a first control resource set (CORESET) and a second CORESET; and 
 receiving, from the scheduling entity, a piggyback downlink control information (DCI) in a downlink data channel using downlink data channel resources temporally configured between the first CORESET and the second CORESET, 
 wherein the piggyback DCI is configured to alter one or more third CORESETs temporally configured between the first CORESET and the second CORESET. 
 
     
     
       16. The method of  claim 15 , wherein the piggyback DCI is configured to alter the one or more third CORESETs, at least in part, based on a time duration between the piggyback DCI and the one or more third CORESETs. 
     
     
       17. The method of  claim 15 , wherein the piggyback DCI is configured to activate the one or more third CORESETs, the method further comprising:
 monitoring the one or more third CORESETs for a physical downlink control channel (PDCCH) in the one or more third CORESETs activated by the piggyback DCI. 
 
     
     
       18. The method of  claim 17 , wherein the one or more third CORESETs comprises at least one dynamic CORESET, the method further comprising:
 monitoring the at least one dynamic CORESET before an upcoming periodic CORESET. 
 
     
     
       19. The method of  claim 15 , wherein the piggyback DCI is configured to modify at least one parameter of the one or more third CORESETs,
 wherein the at least one parameter comprises at least one of time-frequency resources, a resource mapping type, a precoding parameter, a beam configuration, aggregation level, or a number of physical downlink control channel (PDCCH) candidates. 
 
     
     
       20. The method of  claim 15 , wherein the piggyback DCI is configured to modify a transmission configuration indicator (TCI) state of a physical downlink control channel (PDCCH) in the one or more third CORESETs, according to TCI information contained in the piggyback DCI and based on a time duration between the piggyback DCI and the PDCCH. 
     
     
       21. The method of  claim 15 , wherein the piggyback DCI is configured to modify a transmission configuration indicator (TCI) state of a physical downlink control channel (PDCCH) in the one or more third CORESETs to be the same as a TCI state used for receiving the piggyback DCI and based on a time duration between the piggyback DCI and the PDCCH. 
     
     
       22. The method of  claim 15 , wherein the piggyback DCI is configured to deactivate the one or more third CORESETs, the method further comprising:
 forgoing monitoring the one or more third CORESETs deactivated by the piggyback DCI. 
 
     
     
       23. A user equipment (UE), comprising:
 a communication interface configured to communicate with a scheduling entity; 
 a memory; and 
 a processor operatively coupled with the communication interface and the memory, 
 wherein the processor and the memory are configured to:
 receive, from the scheduling entity using the communication interface, control information for configuring a first control resource set (CORESET) and a second CORESET; and 
 receive, from the scheduling entity, a piggyback downlink control information (DCI) in a downlink data channel using downlink data channel resources temporally configured between the first CORESET and the second CORESET, 
 wherein the piggyback DCI is configured to control one or more third CORESETs temporally configured between the first CORESET and the second CORESET. 
 
 
     
     
       24. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to control the one or more third CORESETs, at least in part, based on a time duration between the piggyback DCI and the one or more third CORESETs. 
     
     
       25. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to activate the one or more third CORESETs, the processor and the memory are further configured to:
 monitor the one or more third CORESETs for a physical downlink control channel (PDCCH) in the one or more third CORESETs activated by the piggyback DCI. 
 
     
     
       26. The scheduled entity of  claim 25 , wherein the one or more third CORESETs comprises at least one dynamic CORESET, the processor and the memory are further configured to:
 monitor the at least one dynamic CORESET before an upcoming periodic CORESET. 
 
     
     
       27. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to modify at least one parameter of the one or more third CORESETs,
 wherein the at least one parameter comprises at least one of time-frequency resources, a resource mapping type, a precoding parameter, a beam configuration, aggregation level, or a number of physical downlink control channel (PDCCH) candidates. 
 
     
     
       28. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to modify a transmission configuration indicator (TCI) state of a physical downlink control channel (PDCCH) in the one or more third CORESETs, according to TCI information contained in the piggyback DCI and based on a time duration between the piggyback DCI and the PDCCH. 
     
     
       29. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to modify a transmission configuration indicator (TCI) state of a physical downlink control channel (PDCCH) in the one or more third CORESETs to be the same as a TCI state used for receiving the piggyback DCI and based on a time duration between the piggyback DCI and the PDCCH. 
     
     
       30. The scheduled entity of  claim 23 , wherein the piggyback DCI is configured to deactivate the one or more third CORESETs, the processor and the memory are further configured to:
 forgo monitoring the one or more third CORESETs deactivated by the piggyback DCI.