IP Library › Granted Patent US 12,543,175
Granted Patent B2
US 12,543,175 · App. 18/108,049 · Granted Feb 3, 2026

Resource transmission method, resource transmission apparatus, and communications device

Inventors: Na Li (Guangdong, CN); Gen Li (Guangdong, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W72/1268H04W72/0453
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,543,175
App. No.
18/108,049
Granted
Feb 3, 2026
Kind
B2
Abstract

A resource transmission method, a resource transmission apparatus, and a communications device. The resource transmission method is applied to a terminal and includes: obtaining first information, where the first information includes at least one of configuration information and scheduling information for uplink transmission; and determining an uplink transmission mode based on the first information, where the uplink transmission mode supports frequency hopping on an unlicensed frequency band, or the uplink transmission mode does not support frequency hopping on the unlicensed frequency band.

Claims (56)

1 . A resource transmission method, applied to a terminal and comprising:

obtaining first information, wherein the first information comprises at least one of configuration information and scheduling information for uplink transmission; and

determining an uplink transmission mode based on the first information, wherein the uplink transmission mode supports frequency hopping on an unlicensed frequency band,

wherein in a case that the scheduling information indicates that the uplink transmission is a dynamic grant based PUSCH, and that a first preset condition is satisfied, the uplink transmission mode supports intra-slot frequency hopping on the unlicensed frequency band, and

wherein the first preset condition comprises at least one of the following: the terminal being not configured with a PUSCH aggregation factor; and scheduling of at least two PUSCHs being permitted in uplink scheduling, and time-domain resources for the at least two PUSCHs scheduled being located in at least one slot.

2 . The method according to claim 1 , wherein the first information satisfies any one of the following: being configured by a network-side device; and being specified by a protocol.

3 . The method according to claim 1 , wherein in a case that the scheduling information indicates that the uplink transmission is a configured grant based physical uplink shared channel PUSCH and that a number of candidate PUSCHs in a slot is 1, the uplink transmission mode supports intra-slot frequency hopping on the unlicensed frequency band.

4 . The method according to claim 1 , wherein in a case that the scheduling information indicates that the uplink transmission is a configured grant based PUSCH, that a number of candidate PUSCHs in a slot is 1, and that a number of consecutive slots is greater than 1, the uplink transmission mode supports intra-slot frequency hopping and/or inter-slot frequency hopping on the unlicensed frequency band.

5 . The method according to claim 1 , wherein

the first preset condition further comprises at least one of the following:

a number of repetitions of the dynamic grant based PUSCH being 1; and

scheduling of one PUSCH being permitted in uplink scheduling.

6 . The method according to claim 1 , wherein in a case that the scheduling information indicates that the uplink transmission is a dynamic grant based PUSCH and that a second preset condition is satisfied, the uplink transmission mode supports intra-slot frequency hopping and/or inter-slot frequency hopping on the unlicensed frequency band, wherein

the second preset condition comprises at least one of the following:

the terminal being configured with a PUSCH aggregation factor;

a number of repetitions of the dynamic grant based PUSCH being greater than 1;

scheduling of one PUSCH being permitted in uplink scheduling; and

scheduling of at least two PUSCHs being permitted in uplink scheduling, and time-domain resources for the at least two PUSCHs scheduled being located in at least one slot;

wherein in a case that scheduling of at least two PUSCHs is permitted in uplink scheduling, and that time-domain resources for the at least two PUSCHs scheduled are located in at least one slot, the terminal transmits only PUSCH(s) in a first slot.

7 . The method according to claim 1 , wherein in a case that the uplink transmission mode supports frequency hopping on the unlicensed frequency band, the uplink transmission mode supports intra-PUSCH frequency hopping.

8 . The method according to claim 7 , wherein the uplink transmission mode further supports at least one of the following frequency hopping patterns:

intra-slot frequency hopping for at least two PUSCHs;

consecutive inter-PUSCH frequency hopping; and

inter-slot frequency hopping.

9 . The method according to claim 7 , wherein in the frequency hopping patterns, the terminal transmits same or different PUSCHs in one dynamic scheduling.

10 . A resource transmission method, applied to a network-side device and comprising:

transmitting first information to a terminal; wherein

the first information comprises at least one of configuration information and scheduling information for uplink transmission, the first information is used to indicate an uplink transmission mode for the terminal, and the uplink transmission mode supports frequency hopping on an unlicensed frequency band,

wherein in a case that the scheduling information indicates that the uplink transmission is a dynamic grant based PUSCH, and that a first preset condition is satisfied, the uplink transmission mode supports intra-slot frequency hopping on the unlicensed frequency band, and

wherein the first preset condition comprises at least one of the following: the terminal being not configured with a PUSCH aggregation factor; and scheduling of at least two PUSCHs being permitted in uplink scheduling, and time-domain resources for the at least two PUSCHs scheduled being located in at least one slot.

11 . The method according to claim 10 , wherein in a case that the scheduling information indicates that the uplink transmission is a configured grant based physical uplink shared channel PUSCH and that a number of candidate PUSCHs in a slot is 1, the uplink transmission mode supports intra-slot frequency hopping on the unlicensed frequency band.

12 . The method according to claim 10 , wherein in a case that the scheduling information indicates that the uplink transmission is a configured grant based PUSCH, that a number of candidate PUSCHs in a slot is 1, and that a number of consecutive slots is greater than 1, the uplink transmission mode supports intra-slot frequency hopping and/or inter-slot frequency hopping on the unlicensed frequency band.

13 . The method according to claim 10 , wherein

the first preset condition further comprises at least one of the following:

a number of repetitions of the dynamic grant based PUSCH being 1; and

scheduling of one PUSCH being permitted in uplink scheduling.

14 . The method according to claim 10 , wherein in a case that the scheduling information indicates that the uplink transmission is a dynamic grant based PUSCH and that a second preset condition is satisfied, the uplink transmission mode supports intra-slot frequency hopping and/or inter-slot frequency hopping on the unlicensed frequency band, wherein

the second preset condition comprises at least one of the following:

the terminal being configured with a PUSCH aggregation factor;

a number of repetitions of the dynamic grant based PUSCH being greater than 1;

scheduling of one PUSCH being permitted in uplink scheduling; and

scheduling of at least two PUSCHs being permitted in uplink scheduling, and time-domain resources for the at least two PUSCHs scheduled being located in at least one slot.

15 . The method according to claim 14 , wherein in a case that scheduling of at least two PUSCHs is permitted in uplink scheduling, and that time-domain resources for the at least two PUSCHs scheduled are located in at least one slot, the first information is used to indicate that the terminal transmits only PUSCH(s) in a first slot.

16 . The method according to claim 10 , wherein in a case that the uplink transmission mode supports frequency hopping on the unlicensed frequency band, the uplink transmission mode supports intra-PUSCH frequency hopping.

17 . The method according to claim 16 , wherein the uplink transmission mode further supports at least one of the following frequency hopping patterns:

intra-slot frequency hopping for at least two PUSCHs;

consecutive inter-PUSCH frequency hopping; and

inter-slot frequency hopping.

18 . The method according to claim 16 , wherein in the frequency hopping patterns, the terminal transmits same or different PUSCHs in one dynamic scheduling.

19 . A communications device, comprising:

at least one hardware processor, a memory, and a program or instructions stored in the memory and capable of running on the at least one hardware processor, wherein when the program or instructions are executed by the at least one hardware processor, the at least one hardware processor is directed to perform:

obtaining first information, wherein the first information comprises at least one of configuration information and scheduling information for uplink transmission; and

determining an uplink transmission mode based on the first information, wherein the uplink transmission mode supports frequency hopping on an unlicensed frequency band,

wherein in a case that the scheduling information indicates that the uplink transmission is a dynamic grant based PUSCH, and that a first preset condition is satisfied, the uplink transmission mode supports intra-slot frequency hopping on the unlicensed frequency band, and

wherein the first preset condition comprises at least one of the following: the terminal being not configured with a PUSCH aggregation factor; and scheduling of at least two PUSCHs being permitted in uplink scheduling, and time-domain resources for the at least two PUSCHs scheduled being located in at least one slot.

20 . A communications device, comprising at least one hardware processor, a memory, and a program or instructions stored in the memory and capable of running on the at least one hardware processor, wherein when the program or instructions are executed by the at least one hardware processor, the resource transmission method according to claim 10 is implemented.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2023
From: LI, NA; LI, GEN
To: VIVO MOBILE COMMUNICATION CO., LTD.
Reel/Frame 062657/0993 →
Priority Claims (1)
CN 202010809437.5 · Aug 12, 2020 · national
Continuity (2)
Continuation PCTCN2021111499 · Aug 9, 2021
Related Publication 20230189259A1 · Jun 15, 2023
References Cited (37)
US 20180020452A1 · Yerramalli · 2018 [cited by examiner]
US 20180310341A1 · Yerramalli · 2018 [cited by examiner]
US 20180323932A1 · Huang et al. · 2018 [cited by applicant]
US 20190007946A1 · Yerramalli · 2019 [cited by examiner]
US 20190020424A1 · Yerramalli · 2019 [cited by examiner]
US 20200137788A1 · Chang et al. · 2020 [cited by applicant]
US 20200204327A1 · Jia et al. · 2020 [cited by applicant]
US 20200336973A1 · Niu · 2020 [cited by examiner]
US 20200374057A1 · Matsumura et al. · 2020 [cited by applicant]
US 20200374896A1 · Bae et al. · 2020 [cited by applicant]
US 20200412406A1 · Moroga et al. · 2020 [cited by applicant]
US 20210235496A1 · Park · 2021 [cited by examiner]
US 20210289547A1 · Ye · 2021 [cited by examiner]
US 20220022208A1 · Nakamura et al. · 2022 [cited by applicant]
US 20220060215A1 · Nakamura et al. · 2022 [cited by applicant]
CN 106550468A · 2017 [cited by applicant]
CN 109428626A · 2019 [cited by applicant]
CN 111246582A · 2020 [cited by applicant]
EP 3648386A1 · 2019 [cited by applicant]
JP 2018526890A · 2018 [cited by applicant]
JP 2020108103A · 2020 [cited by applicant]
JP 2020108104A · 2020 [cited by applicant]
WO 2018064525A1 · 2018 [cited by applicant]
WO 2019097655A1 · 2019 [cited by applicant]
WO 2019160359A1 · 2019 [cited by applicant]
WO 2019167939A1 · 2019 [cited by applicant]
WO 2020036464A1 · 2020 [cited by applicant]
WO 2020051152A1 · 2020 [cited by applicant]
WO 2020143689A1 · 2020 [cited by applicant]
Second Japanese Office Action for Japanese Patent Application No. 2023-509553 dated Sep. 20, 2024. 6 pages. [cited by applicant]
First Office Action for Chinese Application No. 202010809437.5, dated May 25, 2023, 6 Pages. [cited by applicant]
3GPPRAN1-AH-1801(signed). [cited by applicant]
MCC Support “Draft Report of 3GPP TSG RAN WG1 #AH_1801 v0.1.0” 3GPP TSG RAN WG1 Meeting #92, Athens, Greece, Mar. 2018, R1-180xxxx, 114 Pages. [cited by applicant]
TDoc_List_Meeting_RAN1-AH-1801(180201). [cited by applicant]
International Search Report and Written Opinion for Application No. PCT /CN2021/111499, dated Nov. 15, 2021, 7 Pages. [cited by applicant]
Extended European Search Report for Application No. 21855476.4, dated Nov. 20, 2023, 8 Pages. [cited by applicant]
First Office Action for Japanese Application No. 2023-509553, dated Mar. 22, 2024, 5 Pages. [cited by applicant]