IP Library › Granted Patent US 11,678,323
Granted Patent B2
US 11,678,323 · App. 17/646,050 · Granted Jun 13, 2023

Method and devices for multiple transmit receive point cooperation for reliable communication

Inventors: Zhengwei Gong (Ottawa, CA); Amine Maaref (Ottawa, CA); Mohammadhadi Baligh (Ottawa, CA); Usa Vilaipornsawai (Nepean, CA); Hamidreza Farmanbar (Ottawa, CA); Aman Jassal (Ottawa, CA); Hua Xu (Ottawa, CA)
Assignee: Huawei Technologies Co., Ltd.
H04W72/1273H04L5/0055H04W24/08H04W72/1268H04W72/23H04W76/11H04W76/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,678,323
App. No.
17/646,050
Filed
Dec 27, 2021
Granted
Jun 13, 2023
Kind
B2
Art Unit
2467
USPC
370/329
Abstract

Embodiments of the present application pertain to control information for scheduling a transmission resource for downlink and uplink communications between one or more TRP and one or more UE. One Physical Downlink Control Channel (PDCCH) for DL control information transmission is assumed to carry at least one assignment or scheduling information block for at least one Physical Downlink Shared Channel (PDSCH) for DL data transmission or for at least one Physical Uplink Shared Channel (PUSCH) for UL data transmission. Embodiments of the present application provide methods of providing configuration information that can be used by a user equipment (UE) to determine transmission mode for the PDSCH and PUSCH as well as information to determine where to monitor for the PDSCH, PUSCH and PUCCH information.

Claims (49)

1. A method comprising:

receiving, by a user equipment (UE), a configuration to monitor more than one physical downlink control channel (PDCCH) in a single PDCCH monitoring occasion, wherein the more than one PDCCH schedules more than one physical downlink shared channel (PDSCH) overlapping in time, wherein the more than one PDCCH is associated with a radio network temporary identifier (RNTI);

monitoring, by the UE, the more than one PDCCH based on the configuration; and

receiving, by the UE, the more than one PDSCH in accordance with the more than one PDCCH.

2. The method of claim 1 , the more than one PDCCH scheduling more than the one PDSCH overlapping in frequency.

3. The method of claim 1 , further comprising:

determining, by the UE, a physical uplink control channel (PUCCH) feedback mode, wherein the determining the PUCCH feedback mode comprises receiving a radio resource control (RRC) signaling indicating the PUCCH feedback mode; and

transmitting, by the UE, a single or multiple PUCCHs based on the PUCCH feedback mode.

4. The method of claim 1 , further comprising:

transmitting, by the UE, multiple PUCCHs, wherein each PUCCH of the multiple PUCCHs is associated with a different PDCCH of the more than one PDCCH.

5. The method of claim 4 , wherein the multiple PUCCHs are transmitted within a slot.

6. The method of claim 5 , wherein the multiple PUCCHs do not overlap in time, and wherein a starting orthogonal frequency-division multiplexing (OFDM) symbol of each PUCCH is located within the slot, and a duration of the each PUCCH is less than a duration of the slot.

7. The method of claim 1 , wherein the more than one PDCCH is associated with one serving cell.

8. The method of claim 1 , further comprising:

obtaining, by the UE, an association between the more than one PDCCH and more than one control resource set (CORESET); and

monitoring, by the UE, a first PDCCH from a first CORESET group and a second PDCCH from a second CORESET group based on the association between the more than one PDCCH and the more than one CORESET,

wherein a CORESET group includes at least one user equipment (UE)-specific CORESET from a set of CORESETs.

9. The method of claim 8 , wherein the obtaining the association further comprises:

receiving, by the UE, information indicating more than one CORESET configuration, each CORESET configuration of the more than one CORESET configuration including one identity associated with one of the more than one PDCCH,

wherein at least two CORESET configurations of the more than one CORESET configuration include different identities.

10. A user equipment (UE) comprising:

at least one processor; and

a non-transitory computer readable storage medium storing programming for execution by the at least one processor, the programming including instructions to cause the UE to:

receive a configuration to monitor more than one physical downlink control channel (PDCCH) in a single PDCCH monitoring occasion, wherein the more than one PDCCH schedules more than one physical downlink shared channel (PDSCH) overlapping in time, wherein the more than one PDCCH is associated with a radio network temporary identifier (RNTI);

monitor the more than one PDCCH based on the configuration; and

receive the more than one PDSCH in accordance with the more than one PDCCH.

11. The UE of claim 10 , the more than one PDCCH scheduling more than the one PDSCH overlapping in frequency.

12. The UE of claim 10 , the programming further including instructions to cause the UE to:

determine a physical uplink control channel (PUCCH) feedback mode by receiving a radio resource control (RRC) signaling indicating the PUCCH feedback mode; and

transmit a single or multiple PUCCHs based on the PUCCH feedback mode.

13. The UE of claim 11 , the programming further including instructions to cause the UE to:

transmit multiple PUCCHs, wherein each PUCCH of the multiple PUCCHs is associated with a different PDCCH of the more than one PDCCH.

14. The UE of claim 13 , wherein the multiple PUCCHs are transmitted within a slot.

15. The UE of claim 14 , wherein the multiple PUCCHs do not overlap in time, and wherein a starting orthogonal frequency-division multiplexing (OFDM) symbol of each PUCCH is located within the slot, and a duration of the each PUCCH is less than a duration of the slot.

16. The UE of claim 10 , the programming further including instructions to cause the UE to:

obtain an association between the more than one PDCCH and more than one control resource set (CORESET); and

monitor a first PDCCH from a first CORESET group and a second PDCCH from a second CORESET group based on the association between the more than one PDCCH and the more than one CORESET,

wherein a CORESET group includes at least one user equipment (UE)-specific CORESET from a set of CORESETs.

17. The UE of claim 16 , wherein the instructions to obtain the association further include instructions to:

receive information indicating more than one CORESET configuration, each CORESET configuration of the more than one CORESET configuration including one identity associated with one of the more than one PDCCH,

wherein at least two CORESET configurations of the more than one CORESET configuration include different identities.

18. A base station comprising:

at least one processor; and

a non-transitory computer readable storage medium storing programming for execution by the at least one processor, the programming including instructions to cause the base station to:

send a configuration for a user equipment (UE) to monitor more than one physical downlink control channel (PDCCH) in a single PDCCH monitoring occasion, wherein the more than one PDCCH schedules more than one physical downlink shared channel (PDSCH) overlapping in time, wherein the more than one PDCCH is associated with a radio network temporary identifier (RNTI); and

send the more than one PDSCH in accordance with the more than one PDCCH.

19. The base station of claim 18 , further comprising: the programming further including instructions to cause the base station to:

receive multiple PUCCHs, wherein each PUCCH of the multiple PUCCHs is associated with a different PDCCH of the more than one PDCCH.

20. The base station of claim 19 , wherein the multiple PUCCHs are transmitted within a slot.

Continuity (5)
Continuation 16682822 · Nov 13, 2019
Continuation PCTCN2018091326 · Jun 14, 2018
Provisional Application 62568757 · Oct 5, 2017
Provisional Application 62520510 · Jun 15, 2017
Related Publication 20220201727A1 · Jun 23, 2022
Cited By (3)
US 12,207,254 US 12,212,395 US 12,245,227