Method and apparatus of handling device-to-device resource pool without physical sidelink feedback channel in a wireless communication system
Abstract
A method and apparatus are disclosed from the perspective of a first device. In one embodiment, the method includes the first device receiving a configuration, from a network node, of a first sidelink resource pool without any Physical Sidelink Feedback Channel (PSFCH) resource. The method further includes the first device receiving a first sidelink grant transmitted, configured, or scheduled by the network node, wherein the first sidelink grant schedules or indicates at least a first sidelink resource in the first sidelink resource pool. Furthermore, the method includes the first device expecting or considering that the first sidelink grant provides no Physical Uplink Control Channel (PUCCH) resource for reporting Sidelink (SL) Hybrid Automatic Repeat Request (HARD) feedback.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method of a network node to schedule New Radio (NR) sidelink resources, comprising:
configuring a first NR sidelink resource pool with no Physical Sidelink Feedback Channel (PSFCH) resource; transmitting, configuring, or scheduling a first sidelink grant to a first device, wherein the first sidelink grant schedules or indicates at least a first NR sidelink resource in the first NR sidelink resource pool; and excluding, precluding, or preventing, based on the first NR sidelink resource pool being configured with no PSFCH resource, from providing a Physical Uplink Control Channel (PUCCH) resource associated with the first NR sidelink resource or the first sidelink grant.
2 . The method of claim 1 , wherein the PSFCH resource is used for transmitting sidelink Hybrid Automatic Repeat Request (HARD) feedback between devices.
3 . The method of claim 1 , further comprising transmitting or scheduling the first sidelink grant via a Downlink Control Information (DCI), wherein one combination or one codepoint of one or more fields in the DCI is set to indicate that no PUCCH resource is provided.
4 . The method of claim 1 , further comprising transmitting or scheduling the first sidelink grant via a DCI, wherein the first sidelink grant only indicates or is only allowed to indicate one combination or one codepoint of one or more fields in the DCI that no PUCCH resource is provided.
5 . The method of claim 1 , further comprising configuring the first sidelink grant via Radio Resource Control (RRC) signaling, wherein the configuration does not include or provide PUCCH resource configuration.
6 . The method of claim 1 , further comprising:
configuring a second NR sidelink resource pool with a PSFCH resource; transmitting, configuring, or scheduling a second sidelink grant to a second device, wherein the second sidelink grant schedules or indicates at least a second NR sidelink resource in the second NR sidelink resource pool; and allowing to provide a PUCCH resource associated with the second NR sidelink resource or the second sidelink grant.
7 . The method of claim 1 , wherein the first NR sidelink resource pool, with no PSFCH resource, includes a PSFCH periodicity configuration of the first NR sidelink resource pool that indicates no resources for PSFCH.
8 . A network node to schedule New Radio (NR) sidelink resources, comprising:
a processor; and a memory operatively coupled to the processor, wherein the processor is configured to execute program code to:
configure a first NR sidelink resource pool with no Physical Sidelink Feedback Channel (PSFCH) resource;
transmit, configure, or schedule a first sidelink grant to a first device, wherein the first sidelink grant schedules or indicates at least a first NR sidelink resource in the first NR sidelink resource pool; and
exclude, preclude, or prevent, based on the first NR sidelink resource pool being configured with no PSFCH resource, from providing a Physical Uplink Control Channel (PUCCH) resource associated with the first NR sidelink resource or the first sidelink grant.
9 . The network node of claim 8 , wherein the PSFCH resource is used for transmitting sidelink Hybrid Automatic Repeat Request (HARD) feedback between devices.
10 . The network node of claim 8 , wherein the processor is further configured to execute program code to transmit or schedule the first sidelink grant via a Downlink Control Information (DCI), wherein one combination or one codepoint of one or more fields in the DCI is set to indicate that no PUCCH resource is provided.
11 . The network node of claim 8 , wherein the processor is further configured to execute program code to transmit or schedule the first sidelink grant via a DCI, wherein the first sidelink grant only indicates or is only allowed to indicate one combination or one codepoint of one or more fields in the DCI that no PUCCH resource is provided.
12 . The network node of claim 8 , wherein the processor is further configured to execute program code to configure the first sidelink grant via Radio Resource Control (RRC) signaling, wherein the configuration does not include or provide PUCCH resource configuration.
13 . The network node of claim 8 , wherein the processor is further configured to execute program code to:
configure a second NR sidelink resource pool with PSFCH resource; transmit, configure, or schedule a second sidelink grant to a second device, wherein the second sidelink grant schedules or indicates at least a second NR sidelink resource in the second NR sidelink resource pool; and allow to provide a PUCCH resource associated with the second NR sidelink resource or the second sidelink grant.
14 . A method of a first device, comprising:
receiving a configuration, from a network node, of a first New Radio (NR) sidelink resource pool, wherein the first NR sidelink resource pool is configured with no Physical Sidelink Feedback Channel (PSFCH) resource; receiving a first sidelink grant transmitted, configured, or scheduled by the network node, wherein the first sidelink grant schedules or indicates at least a first NR sidelink resource in the first NR sidelink resource pool; and expecting or considering, based on the first NR sidelink resource pool being configured with no PSFCH resource, that the first sidelink grant provides no Physical Uplink Control Channel (PUCCH) resource for reporting sidelink Hybrid Automatic Repeat Request (HARD) feedback to the network node.
15 . The method of claim 14 , wherein the PSFCH resource is used for transmitting sidelink HARQ feedback between devices.
16 . The method of claim 14 , wherein:
the first sidelink grant is transmitted or scheduled via a Downlink Control Information (DCI), wherein one combination or one codepoint of one or more fields in the DCI is set to indicate that no PUCCH resource is provided; and/or the first sidelink grant is transmitted or scheduled via a DCI, wherein the first sidelink grant only indicates or is only allowed to indicate one combination or one codepoint of one or more fields in the DCI indicating that no PUCCH resource is provided.
17 . The method of claim 14 , wherein the first sidelink grant is configured via Radio Resource Control (RRC) signaling, wherein the configuration does not include or provide PUCCH resource configuration.
18 . The method of claim 14 , wherein if the first sidelink grant provides PUCCH resource for reporting sidelink HARQ feedback associated with the first NR sidelink resource or the first sidelink grant, the first device considers the first sidelink grant is an inconsistent scheduling and/or the first device drops the first sidelink grant.
19 . The method of claim 18 , wherein if the first device drops the first sidelink grant, the first device does not perform sidelink transmission on the first NR sidelink resource scheduled by the first sidelink grant.
20 . The method of claim 14 , wherein the configuration of the first NR sidelink resource pool, with no PSFCH resource, includes a PSFCH periodicity configuration of the first NR sidelink resource pool that indicates no resources for PSFCH.Join the waitlist — get patent alerts
Track US2022150886A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.