IP Library › Granted Patent US 12,219,556
Granted Patent B2
US 12,219,556 · App. 17/744,227 · Granted Feb 4, 2025

Uplink resource determining method, uplink resource indication method, terminal, and network device

Inventors: Na Li (Guangdong, CN); Gen Li (Guangdong, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W72/1268H04W72/044H04W72/23H04W74/0808
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 12,219,556
App. No.
17/744,227
Granted
Feb 4, 2025
Kind
B2
Abstract

An uplink resource determining method, an uplink resource indication method, a terminal, and a network device are disclosed. The method includes: receiving first DCI used to schedule transmission of a PUSCH on a target BWP, where the first DCI includes an allocation field for frequency domain resource allocation, the allocation field is determined based on a configuration of a reference BWP, and the allocation field includes first bits; and determining an uplink resource indicated by the allocation field, where the uplink resource is an uplink resource determined based on valid bits of the first bits; and a resource allocation type of at least one of the reference BWP and the target BWP is interlace resource allocation.

Claims (53)

1. An uplink resource determining method, applied to a terminal and comprising:

receiving first downlink control information DCI used to schedule transmission of a physical uplink shared channel PUSCH on a target bandwidth part BWP, wherein the first DCI comprises an allocation field for frequency domain resource allocation, the allocation field is determined based on a configuration of a reference BWP, and the allocation field comprises first bits; and

determining an uplink resource indicated by the allocation field, wherein the uplink resource is an uplink resource determined based on valid bits of the first bits; and

a resource allocation type of at least one of the reference BWP and the target BWP is interlace resource allocation.

2. The method according to claim 1 , wherein the valid bits are all or a part of the first bits; or

the valid bits are M pieces of bit content obtained by dividing all or a part of the first bits, wherein the M pieces of bit content are M resource indications, and M is an integer greater than or equal to 1.

3. The method according to claim 1 , wherein the determining an uplink resource indicated by the allocation field comprises:

determining, based on a configuration of the target BWP, the number of bits required by the field for frequency domain resource allocation in the DCI used to schedule transmission of the PUSCH on the target BWP; and

determining, based on the number of required bits, the uplink resource indicated by the allocation field.

4. The method according to claim 3 , wherein if the number of bits of the first bits is greater than or equal to the number of required bits, and the number of bits of the valid bits is equal to the number of required bits; or

if the number of bits of the first bits is less than the number of required bits, the uplink resource is the uplink resource indicated by the valid bits in some resources of the target BWP, or the uplink resource indicated by the valid bits at the scaled granularity, or the predefined uplink resource in the resources of the target BWP.

5. The method according to claim 4 , wherein in a case that the number of bits of the first bits is less than the number of required bits:

if the first bits comprise interlace indication bits and/or LBT bandwidth indication bits, the number of interlace indication bits is less than or equal to the number of bits required by interlace indication bits in the number of required bits, and/or the number of LBT bandwidth indication bits is less than or equal to the number of bits required by LBT bandwidth indication bits in the number of required bits.

6. The method according to claim 5 , wherein if the number of interlace indication bits of the first bits is less than the number of bits required by the interlace indication bits in the number of required bits, the interlace comprised in the uplink resources is the interlace is the interlace indicated by the interlace indication bits in the valid bits in some interlace of the target BWP, or the interlace indicated by the interlace indication bits in the valid bits at the amplified granularity; or

if the number of LBT bandwidth indication bits of the first bits is less than the number of bits required by the LBT bandwidth indication bits in the number of required bits, the LBT bandwidth comprised in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits in some LBT bandwidths of the target BWP, or the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits at the amplified granularity, or the predefined LBT bandwidth of the target BWP.

7. The method according to claim 3 , wherein if the number of interlace indication bits of the first bits is greater than or equal to the number of bits required by interlace indication bits in the number of required bits, the interlace in the uplink resource is the interlace indicated by the interlace indication bits in the valid bits, wherein the number of bits of interlace indication bits in the valid bits is equal to the number of bits required by the interlace indication bits; or

if the number of LBT bandwidth indication bits of the first bits is greater than or equal to the number of bits required by LBT bandwidth indication bits in the number of required bits, the LBT bandwidth in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits, wherein the number of bits of LBT bandwidth indication bits in the valid bits is equal to the number of bits required by the LBT bandwidth indication bits; or

if the number of interlace indication bits of the first bits is less than the number of bits required by the interlace indication bits in the number of required bits, the interlace in the uplink resources is the interlace is the interlace indicated by the interlace indication bits in the valid bits in some interlace of the target BWP, or the interlace indicated by the interlace indication bits in the valid bits at the amplified granularity; or

if the number of LBT bandwidth indication bits of the first bits is less than the number of bits required by the LBT bandwidth indication bits in the number of required bits, the LBT bandwidth comprised in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits in some LBT bandwidths of the target BWP, or the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits at the amplified granularity, or the predefined LBT bandwidth of the target BWP.

8. The method according to claim 3 , wherein both a frequency domain resource allocation type of the reference BWP and a frequency domain resource allocation type of the target BWP are an interlace resource allocation type; or

a frequency domain resource allocation type of the reference BWP is an interlace resource allocation type, and a resource allocation type of the target BWP is a resource allocation type 0 or a resource allocation type 1; or

a frequency domain resource allocation type of the reference BWP is a resource allocation type 0 or a resource allocation type 1, and a resource allocation type of the target BWP is an interlace resource allocation type.

9. A terminal, comprising a memory, a processor, and a program that is stored in the memory and that can be run on the processor, wherein when the program is executed by the processor, the steps of the uplink resource determining method are implemented, wherein the method comprises:

receiving first downlink control information DCI used to schedule transmission of a physical uplink shared channel PUSCH on a target bandwidth part BWP, wherein the first DCI comprises an allocation field for frequency domain resource allocation, the allocation field is determined based on a configuration of a reference BWP, and the allocation field comprises first bits; and

determining an uplink resource indicated by the allocation field, wherein the uplink resource is an uplink resource determined based on valid bits of the first bits; and

a resource allocation type of at least one of the reference BWP and the target BWP is interlace resource allocation.

10. The terminal according to claim 9 , wherein the determining an uplink resource indicated by the allocation field comprises:

determining, based on a configuration of the target BWP, the number of bits required by the field for frequency domain resource allocation in the DCI used to schedule transmission of the PUSCH on the target BWP; and

determining, based on the number of required bits, the uplink resource indicated by the allocation field.

11. The terminal according to claim 10 , wherein if the number of bits of the first bits is greater than or equal to the number of required bits, and the number of bits of the valid bits is equal to the number of required bits; or

if the number of bits of the first bits is less than the number of required bits, the uplink resource is the uplink resource indicated by the valid bits in some resources of the target BWP, or the uplink resource indicated by the valid bits at the scaled granularity, or the predefined uplink resource in the resources of the target BWP.

12. The terminal according to claim 11 , wherein in a case that the number of bits of the first bits is less than the number of required bits:

if the first bits comprise interlace indication bits and/or LBT bandwidth indication bits, the number of interlace indication bits is less than or equal to the number of bits required by interlace indication bits in the number of required bits, and/or the number of LBT bandwidth indication bits is less than or equal to the number of bits required by LBT bandwidth indication bits in the number of required bits.

13. The terminal according to claim 12 , wherein if the number of interlace indication bits of the first bits is less than the number of bits required by the interlace indication bits in the number of required bits, the interlace comprised in the uplink resources is the interlace is the interlace indicated by the interlace indication bits in the valid bits in some interlace of the target BWP, or the interlace indicated by the interlace indication bits in the valid bits at the amplified granularity; or

if the number of LBT bandwidth indication bits of the first bits is less than the number of bits required by the LBT bandwidth indication bits in the number of required bits, the LBT bandwidth comprised in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits in some LBT bandwidths of the target BWP, or the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits at the amplified granularity, or the predefined LBT bandwidth of the target BWP.

14. The terminal according to claim 11 , wherein if the number of interlace indication bits of the first bits is greater than or equal to the number of bits required by interlace indication bits in the number of required bits, the interlace in the uplink resource is the interlace indicated by the interlace indication bits in the valid bits, wherein the number of bits of interlace indication bits in the valid bits is equal to the number of bits required by the interlace indication bits; or

if the number of LBT bandwidth indication bits of the first bits is greater than or equal to the number of bits required by LBT bandwidth indication bits in the number of required bits, the LBT bandwidth in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits, wherein the number of bits of LBT bandwidth indication bits in the valid bits is equal to the number of bits required by the LBT bandwidth indication bits; or

if the number of interlace indication bits of the first bits is less than the number of bits required by the interlace indication bits in the number of required bits, the interlace in the uplink resources is the interlace is the interlace indicated by the interlace indication bits in the valid bits in some interlace of the target BWP, or the interlace indicated by the interlace indication bits in the valid bits at the amplified granularity; or

if the number of LBT bandwidth indication bits of the first bits is less than the number of bits required by the LBT bandwidth indication bits in the number of required bits, the LBT bandwidth comprised in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits in some LBT bandwidths of the target BWP, or the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits at the amplified granularity, or the predefined LBT bandwidth of the target BWP.

15. The terminal according to claim 11 , wherein both a frequency domain resource allocation type of the reference BWP and a frequency domain resource allocation type of the target BWP are an interlace resource allocation type; or

a frequency domain resource allocation type of the reference BWP is an interlace resource allocation type, and a resource allocation type of the target BWP is a resource allocation type 0 or a resource allocation type 1; or

a frequency domain resource allocation type of the reference BWP is a resource allocation type 0 or a resource allocation type 1, and a resource allocation type of the target BWP is an interlace resource allocation type.

16. A network device, comprising a memory, a processor, and a program that is stored in the memory and that can be run on the processor, wherein when the program is executed by the processor, the steps of the uplink resource indication method are implemented, wherein the method comprises:

sending first downlink control information DCI used to schedule transmission of a physical uplink shared channel PUSCH on a target bandwidth part BWP, wherein the first DCI comprises an allocation field for frequency domain resource allocation, the allocation field is determined based on a configuration of a reference BWP, and the allocation field comprises first bits; and

the allocation field indicates that an uplink resource is indicated by using valid bits of the first bits; and

a resource allocation type of at least one of the reference BWP and the target BWP is interlace resource allocation.

17. The network device according to claim 16 , wherein the uplink resource comprises an uplink resource that is indicated by the valid bits and that is determined based on the number of required bits, wherein the number of required bits is the number that is of bits required by the field for frequency domain resource allocation in the DCI used to schedule transmission of the PUSCH on the target BWP and that is determined based on a configuration of the target BWP.

18. The network device according to claim 17 , wherein if the number of bits of the first bits is greater than or equal to the number of required bits, and the number of bits of the valid bits is equal to the number of required bits; or

if the number of bits of the first bits is less than the number of required bits, the uplink resource is the uplink resource indicated by the valid bits in some resources of the target BWP, or the uplink resource indicated by the valid bits at the scaled granularity, or the predefined uplink resource in the resources of the target BWP.

19. The network device according to claim 18 , wherein in a case that the number of bits of the first bits is less than the number of required bits:

if the first bits comprise interlace indication bits and/or LBT bandwidth indication bits, the number of interlace indication bits is less than or equal to the number of bits required by interlace indication bits in the number of required bits, and/or the number of LBT bandwidth indication bits is less than or equal to the number of bits required by LBT bandwidth indication bits in the number of required bits.

20. The network device according to claim 19 , wherein if the number of interlace indication bits of the first bits is less than the number of bits required by the interlace indication bits in the number of required bits, the interlace comprised in the uplink resources is the interlace is the interlace indicated by the interlace indication bits in the valid bits in some interlace of the target BWP, or the interlace indicated by the interlace indication bits in the valid bits at the amplified granularity; or

if the number of LBT bandwidth indication bits of the first bits is less than the number of bits required by the LBT bandwidth indication bits in the number of required bits, the LBT bandwidth comprised in the uplink resource is the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits in some LBT bandwidths of the target BWP, or the LBT bandwidth indicated by the LBT bandwidth indication bits in the valid bits at the amplified granularity, or the predefined LBT bandwidth of the target BWP.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2022
From: LI, NA; LI, GEN
To: VIVO MOBILE COMMUNICATION CO., LTD.
Reel/Frame 059911/0661 →
Priority Claims (1)
CN 201911115704.2 · Nov 14, 2019 · national
Continuity (2)
Continuation PCTCN2020128002 · Nov 11, 2020
Related Publication 20220272730A1 · Aug 25, 2022
References Cited (38)
US 20180146480A1 · Chendamarai Kannan et al. · 2018 [cited by applicant]
US 20190132109A1 · Zhou · 2019 [cited by examiner]
US 20190132845A1 · Babaei · 2019 [cited by examiner]
US 20190132857A1 · Babaei · 2019 [cited by examiner]
US 20190141546A1 · Zhou · 2019 [cited by examiner]
US 20190141742A1 · Zhou · 2019 [cited by examiner]
US 20190149380A1 · Babaei · 2019 [cited by examiner]
US 20190313377A1 · Abdoli et al. · 2019 [cited by applicant]
US 20190313412A1 · Baldemair et al. · 2019 [cited by applicant]
US 20200296758A1 · Li et al. · 2020 [cited by applicant]
US 20210176736A1 · Harada et al. · 2021 [cited by applicant]
US 20220272730A1 · Li · 2022 [cited by examiner]
US 20220369384A1 · Sakhnini · 2022 [cited by examiner]
CN 107801246A · 2018 [cited by applicant]
CN 108476506A · 2018 [cited by applicant]
CN 109586878A · 2019 [cited by applicant]
CN 109983827A · 2019 [cited by applicant]
CN 109995497A · 2019 [cited by applicant]
WO 2017165811A1 · 2017 [cited by applicant]
WO WO2018232284A1 · 2018 [cited by examiner]
WO 2019050379A1 · 2019 [cited by applicant]
WO WO2019084570A1 · 2019 [cited by examiner]
Extended European Search Report for Application No. 20887363.8-1215, dated Nov. 25, 2022, 12 Pages. [cited by applicant]
MCC Support, “Final Report of 3GPP TSG RAN WG1 #98 v2.0.0 (Prague, Czech Rep, Aug. 26-30, 2019),” 3GPP TSG RAN WG1 Meeting #98bis, Oct. 14-18, 2019, R1-1911429, Chongqing, China, 180 Pages. [cited by applicant]
Ericsson, “UL Signals and Channels for NR-U,” 3GPP TSG-RAN WG1 Meeting #99, Agenda item 7.2.2.1.3, Nov. 18-22, 2019, R1-1912708, Reno, Nevada, USA, 24 Pages. [cited by applicant]
First Office Action for Japanese Application No. 2022-526339, dated Apr. 19, 2023, 5 Pages. [cited by applicant]
3GPP Organizational Partners “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control” France, 3GPP TS 38.213 V15.7.0, Sep. 2019, 108 Pages. [cited by applicant]
Nokia, Nokia Shanghai Bell “Remaining details on NR-U uplink signals and channels” 3GPP TSG RAN WG1 #99, Reno, USA, Nov. 2019, R1-1912259, 16 Pages. [cited by applicant]
Samsung “Uplink signal and channel design for NR-U” 3GPP TSG-RAN WG1 Meeting #99, Reno, USA, Nov. 2019, R1-1912448, 7 Pages. [cited by applicant]
First Office Action for Chinese Application No. 201911115704.2, dated Mar. 3, 2022, 8 Pages. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/CN2020/128002, dated Jan. 28, 2021, 9 Pages. [cited by applicant]
CATT, “On PDSCH and PUSCH Resource Allocation,” 3GPP TSG RAN WG1 #1, Agenda item 7.3.3.1, Nov. 27-Dec. 1, 2017, R1-1721416, Reno, NV, USA, 18 Pages. [cited by applicant]
Qualcomm Incorporated, “Remaining Issues on BWP,” 3GPP TSG RAN WG1 Meeting AH 1801, Agenda item 7.3.4.1, Jan. 22-26, 2018, R1-1800879, Vancouver, Canada, 13 Pages. [cited by applicant]
Samsung, “DCI Contents and Formats,” 3GPP TSG RAN WG1 #93, Agenda item 7.1.3.1.4, May 21-25, 2018, R1-1806731, Busan, Korea, 4 Pages. [cited by applicant]
Charter Communications, “UL BWP Management in NR-U,” 3GPP TSG RAN WG1 #94BIS, Agenda item 7.2.2.4.4, Oct. 8-12, 2018, R1-1811320, Chengdu, P.R. China, 3 Pages. [cited by applicant]
First Office Action in KR Application No. 10-2022-7019718 dated Nov. 27, 2024 (11 pages, including English translation). [cited by applicant]
Ericsson, UL Signals and Channels for NR-U, Apr. 2019, 9 pages, R1-1904334, Xi'an, China. [cited by applicant]
UL Signals and Channels for NR-U Operation, MediaTek Inc., Nov. 2019, 10 pages, R1-1912087, Reno, USA. [cited by applicant]