IP Library › Granted Patent US 12,232,174
Granted Patent B2
US 12,232,174 · App. 17/422,565 · Granted Feb 18, 2025

Data transmission method and device

Inventor: Xinghang Gao (Beijing, CN)
Assignee: Beijing UNISOC Communications Technology Co., Ltd.
H04W74/0833H04W72/1268
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,232,174
App. No.
17/422,565
Granted
Feb 18, 2025
Kind
B2
Abstract

The present disclosure relates to a data transmission method and device. Said method comprises: determining, according to resource configuration information, a preamble sequence, a physical random access channel (PRACH) time-frequency resource, a physical uplink shared channel (PUSCH) time-frequency resource set and a mapping relationship between the preamble sequence and PUSCH time-frequency resources in the PUSCH time-frequency resource set; transmitting the preamble sequence by using the PRACH time-frequency resource, and transmitting data by using a PUSCH time-frequency resource determined according to the preamble sequence and the mapping relationship; and detecting a random access response message MsgB in a random access response window. In the present disclosure, a preamble sequence and data are sent at the same time, and after the preamble sequence and the data are sent, the detection and reception of random access response information MsgB to the base station can be performed, thereby realizing a random access between a terminal and the base station by means of two-step interaction, reducing the latency.

Claims (108)

1. A data transmission method applicable to a terminal, the method comprising:

determining a preamble sequence, a physical random access channel PRACH time-frequency resource, a physical uplink shared channel PUSCH time-frequency resource set, and a mapping relationship between the preamble sequence and PUSCH time-frequency resources in the PUSCH time-frequency resource set, based on resource configuration information;

transmitting the preamble sequence by using the PRACH time-frequency resource, and transmitting the data by using a PUSCH time-frequency resource determined from the preamble sequence and the mapping relationship; and

detecting a random access response message MsgB in a random access response window.

2. The data transmission method according to claim 1 , wherein the PUSCH time-frequency resource set includes a PUSCH time domain resource set and a PUSCH frequency domain resource set; and said determining, based on the resource configuration information, the preamble sequence, the physical random access channel PRACH time-frequency resource, the physical uplink shared channel PUSCH time-frequency resource set, and the mapping relationship between the preamble sequence and the PUSCH time-frequency resources in the PUSCH time-frequency resource set comprises:

determining the PUSCH time domain resource set; and

determining the PUSCH frequency domain resource set.

3. The data transmission method according to claim 2 , wherein said determining the PUSCH time domain resource set comprises:

determining a starting slot and a starting time domain symbol of the PUSCH time domain resource set; and

determining an ending slot and an ending time domain symbol of the PUSCH time domain resource set.

4. The data transmission method according to claim 3 , wherein said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set comprises:

determining a slot where a last time domain symbol of time domain resources in the PRACH time-frequency resource is located as the starting slot, and determining a last time domain symbol of time domain resources in the PRACH time-frequency resource as the starting time domain symbol:

or

the resource configuration information includes a length of a PUSCH time domain resource and a number of consecutively occupied time domains, and said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set further comprises:

determining a slot where a first time domain symbol of time domain resources in the PRACH time-frequency resource is located as the ending slot, and determining a first time domain symbol of time domain resources in the PRACH time-frequency resource as the ending time domain symbol; and

determining the starting slot based on the length of the PUSCH time domain resources, the number of consecutively occupied time domains, and the ending slot; and determining the starting time domain symbol based on the length of the PUSCH time domain resources, the number of consecutively occupied time domains of the PUSCH time domain resources, and the ending time domain symbol;

or

the resource configuration information includes a slot offset and a starting symbol index, and said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set further comprises:

determining the starting slot of the PUSCH time domain resource based on the slot where a last time domain symbol of the time domain sources in the PRACH time-frequency resources is located and the slot offset, and determining the starting time domain symbol in the starting slot based on the starting symbol index;

or

the resource configuration information includes a starting symbol index, and said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set further comprises:

determining, as the starting slot, an uplink slot adjacent to a slot where a last time domain symbol of the time domain sources in the PRACH time-frequency resources is located, and determining the starting time domain symbol in the starting slot based on the starting symbol index;

or

the resource configuration information includes a number of interval slots and a starting symbol index, and said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set further comprises:

determining, as the starting slot, a slot offset by the number of the interval slots from a slot where a last time domain symbol of the time domain sources in the PRACH time-frequency resources is located, and determining the starting time domain symbol in the starting slot based on the starting symbol index;

or

the resource configuration information includes a starting symbol index, and said determining the starting slot and the starting time domain symbol of the PUSCH time domain resource set further comprises:

determining, as the starting slot, a slot where the ending time domain symbol of the PUSCH time domain resource set is located, the PUSCH time domain resource set corresponding to a preceding PRACH time domain source in the same slot, using the ending time domain symbol of the PUSCH time domain resource set as the starting time domain symbol, or determining the starting time domain symbol based on the starting symbol index and an ending symbol of the PUSCH time domain resource set;

or

the resource configuration information further includes a PUSCH time domain resource length and a number of consecutively occupied time domains throughout the PUSCH time domain resource length, and said determining the ending slot and the ending time domain symbol of the PUSCH time domain resource set comprises:

determining the ending slot and the ending time domain symbol of the time domain resource set based on the starting slot, the starting time domain symbol, the PUSCH time domain resource length, and the number of consecutively occupied time domains throughout the PUSCH time domain resource length;

or

the resource configuration information further includes at least one of a number of the preamble sequences, a length and a number of consecutively occupied frequency domains of the PUSCH frequency domain resource, or PUSCH time domain resource length, and said determining the ending slot and the ending time domain symbol of the PUSCH time domain resource set comprises:

determining the ending slot and the ending time domain symbol based on at least one of the number of the preamble sequences, the length and the number of consecutively occupied frequency domains of the PUSCH frequency domain resource, the PUSCH time domain resource length, or a mapping relationship between preamble sequences in a preamble sequence set and PUSCH time-frequency resources in the PUSCH time-frequency resource set.

5. The data transmission method according to claim 2 , wherein said determining the PUSCH frequency domain resource set comprises:

determining a starting position of the PUSCH frequency domain resource set; and

determining an ending position of the PUSCH frequency domain resource set.

6. The data transmission method according to claim 5 , wherein the resource configuration information includes a frequency domain offset and/or a frequency domain reference point, and said determining the starting position of the PUSCH frequency domain resource set comprises:

determining the starting position of the PUSCH frequency domain resource set based on the frequency domain starting position, the frequency domain ending position, or the frequency domain reference point of the PRACH frequency domain resource set, along with the frequency domain offset.

7. The data transmission method according to claim 6 , wherein said determining the starting position of the PUSCH frequency domain resource set comprises:

determining the ending position of the PUSCH frequency domain resource set corresponding to a preceding adjacent frequency domain as a starting position of the adjacent PUSCH frequency domain resource set.

8. The data transmission method according to claim 5 , wherein the resource configuration information includes at least one of a number of preamble sequences, a length of the PUSCH frequency domain resources, or a number of consecutively occupied time domains throughout the PUSCH time domain resource length, and said determining the ending position of the PUSCH frequency domain resource set comprises:

determining the ending position of the PUSCH frequency domain resource set based on at least one of the starting position of the PUSCH frequency domain resource set, the number of the preamble sequences, the PUSCH frequency domain resource length, the number of consecutively occupied time domains throughout the PUSCH time domain resource length, or the mapping relationship.

9. The data transmission method according to claim 5 , wherein the resource configuration information further includes a length of the PUSCH frequency domain resources, a number of consecutively occupied frequency domains throughout the PUSCH frequency domain resource length, and a number of the PRACH frequency domain resources, and said determining the ending position of the PUSCH frequency domain resource set comprises:

determining an ending position of a total PUSCH frequency domain resource set comprising a plurality of the PUSCH frequency domain resource sets, based on the length of the PUSCH frequency domain resources and the number of consecutively occupied frequency domains throughout the length of the PUSCH frequency domain resources;

or

wherein the resource configuration information includes at least one of a number of preamble sequences, a length of the PUSCH frequency domain resources, a length of the PUSCH time domain resources, or a number of consecutively occupied time domains, and said determining the ending position of the PUSCH frequency domain resource set comprises:

determining an ending position of a total PUSCH frequency domain resource set comprising a plurality of the PUSCH frequency domain resource sets, based on the number of the PRACH frequency domain resources and at least one of the starting position of the PUSCH frequency domain resource set, the number of the preamble sequences, the PUSCH frequency domain resource length, the PUSCH time domain resource length, the number of consecutively occupied time domains throughout the PUSCH time domain resource length, or the mapping relationship.

10. The data transmission method according to claim 2 , wherein the resource configuration information further includes an association between a beam and the PRACH time-frequency resource, and said determining the PUSCH frequency domain resource set further comprises:

determining the PRACH time-frequency resource based on a selected beam and the association; and

determining the PUSCH frequency domain resource set based on the time-frequency resource and the mapping relationship.

11. The data transmission method according to claim 1 , wherein the resource configuration information includes a preamble sequence set, and the mapping relationship comprises:

a one-to-one mapping relationship between a preamble sequence in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set; or a one-to-many mapping relationship between a preamble sequence in the preamble sequence set and a plurality of PUSCH time-frequency resources in the PUSCH time-frequency resource set; or

a many-to-one mapping relationship between a plurality of preamble sequences in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set.

12. The data transmission method according to claim 11 , wherein the resource configuration information includes a mapping number parameter between preamble sequences and the PUSCH time-frequency resources, and further includes:

a one-to-one mapping relationship between a preamble sequence in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set, in a case where the mapping number is a first preset value; or

a one-to-many mapping relationship between a preamble sequence in the preamble sequence set and a plurality of PUSCH time-frequency resources in the PUSCH time-frequency resource set, or a many-to-one mapping relationship between a plurality of preamble sequences in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set, in a case where the mapping number is not the first preset value.

13. The data transmission method according to claim 11 , wherein the mapping relationship further comprises:

a mapping relationship between the preamble sequences in the preamble sequence set and the PUSCH time-frequency resources in the PUSCH time-frequency resource set, where a direction of time domain resources precedes over a direction of frequency domain resources; or

a mapping relationship between the preamble sequences in the preamble sequence set and the PUSCH time-frequency resources in the PUSCH time-frequency resource set, where the direction of frequency domain resources precedes over the direction of time domain resources.

14. The data transmission method according to claim 1 , wherein said transmitting the data by using the PUSCH time-frequency resource determined from the preamble sequence and the mapping relationship comprises:

randomly choosing one of a plurality of PUSCH time-frequency resources to transmit the data, in a case where the mapping relationship indicates a one-to-many mapping relationship between the preamble sequence and the plurality of PUSCH time-frequency resources;

or

wherein the method further comprises:

receiving a system message or dedicated radio resource control RRC signaling, the system message or the RRC signaling including the resource configuration information;

or

wherein the method further comprises:

acquiring the resource configuration information via a row index of a predefined table;

or

wherein said detecting the random access response message MsgB in the random access response window comprises:

starting the random access response window in a slot where a first available PDCCH detection resource after transmission of the preamble sequence and the data is located, and receiving the random access response message MsgB in the random access response window.

15. A data transmission method applicable to a base station, the method comprising:

establishing resource configuration information including at least one of preamble sequences, physical random access channel PRACH time-frequency resources, a physical uplink shared channel PUSCH time-frequency resource set, and a mapping relationship between the preamble sequences and PUSCH time-frequency resources in the PUSCH time-frequency resource set, the resource configuration information configured to allocate transmission resources; and

sending the resource configuration information.

16. The data transmission method according to claim 15 , wherein the PUSCH time-frequency resource set includes a PUSCH time domain resource set and a PUSCH frequency domain resource set, and the resource configuration information includes at least one of a starting slot, a starting time domain symbol, slot offset, a starting symbol index, and a number of interval slots of the PUSCH time domain resource set, length and a number of consecutively occupied time domains of a PUSCH time domain resource corresponding to each preamble sequence, a number of preamble sequences in the preamble sequence set, length and a number of consecutively occupied frequency domains of the PUSCH frequency domain resource, a number of PRACH frequency domain resources, and the mapping relationship, and is configured to allocate the PUSCH time domain resource set and/or the PUSCH frequency domain resource set.

17. The data transmission method according to claim 15 , wherein the mapping relationship comprises:

a one-to-one mapping relationship between a preamble sequence in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set; or

a one-to-many mapping relationship between a preamble sequence in the preamble sequence set and a plurality of PUSCH time-frequency resources in the PUSCH time-frequency resource set; or

a many-to-one mapping relationship between a plurality of preamble sequences in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set.

18. The data transmission method according to claim 17 , wherein the resource configuration information includes a mapping number parameter, and further includes:

a one-to-one mapping relationship between a preamble sequence in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set, in a case where the mapping number is a first preset value; or

a one-to-many mapping relationship between a preamble sequence in the preamble sequence set and a plurality of PUSCH time-frequency resources in the PUSCH time-frequency resource set, or a many-to-one mapping relationship between a plurality of preamble sequences in the preamble sequence set and a PUSCH time-frequency resource in the PUSCH time-frequency resource set, in a case where the mapping number is not the first preset value.

19. The data transmission method according to claim 18 , wherein the PUSCH time-frequency resource set includes a time domain resource set and a frequency domain resource set, and the mapping relationship further comprises:

a mapping relationship between the preamble sequences in the preamble sequence set and the PUSCH time-frequency resources in the PUSCH time-frequency resource set, where a direction of time domain resources precedes over a direction of frequency domain resources;

or

a mapping relationship between the preamble sequences in the preamble sequence set and the PUSCH time-frequency resources in the PUSCH time-frequency resource set, where a direction of frequency domain resources precedes over a direction of time domain resources.

20. The data transmission method according to claim 15 , wherein sending the resource configuration information comprises:

sending a system message or dedicated radio resource control RRC signaling, the system message or the RRC signaling including the resource configuration information;

or

wherein sending the resource configuration information further comprises:

sending the resource configuration information via a predefined table row index.

21. The data transmission method according to claim 15 , wherein the method further comprises:

detecting PRACH time-frequency resources in a physical random access channel, and acquiring preamble sequences in the the PRACH time-frequency resources;

acquiring PUSCH time-frequency resources corresponding to the preamble sequences based on the mapping relationship; and

acquiring data in the PUSCH time-frequency resources.

22. The data transmission method according to claim 21 , wherein the method further comprises:

sending a random access response message MsgB in a random access response window after receiving the preamble sequences and the data in the PUSCH time-frequency resources.

23. A data transmission device comprising:

a process; and

a memory configured to store instructions executable by the processor;

wherein the process is configured to:

execute the method of

determining a preamble sequence, a physical random access channel PRACH time-frequency resource, a physical uplink shared channel PUSCH time-frequency resource set, and a mapping relationship between the preamble sequence and PUSCH time-frequency resources in the PUSCH time-frequency resource set, based on resource configuration information;

transmitting the preamble sequence by using the PRACH time-frequency resource, and transmitting the data by using a PUSCH time-frequency resource determined from the preamble sequence and the mapping relationship; and

detecting a random access response message MsgB in a random access response window;

or execute the method of

establishing resource configuration information including preamble sequences, physical random access channel PRACH time-frequency resources, a physical uplink shared channel PUSCH time-frequency resource set, and a mapping relationship between the preamble sequences and PUSCH time-frequency resources in the PUSCH time-frequency resource set, the resource configuration information configured to allocate transmission resources; and

sending the resource configuration information.

Assignments (2)
CHANGE OF NAME Recorded Nov 5, 2024
From: BEIJING SPREADTRUM HI-TECH COMMUNICATIONS TECHNOLOGY CO., LTD.
To: BEIJING UNISOC COMMUNICATIONS TECHNOLOGY CO., LTD.
Reel/Frame 069305/0365 →
CONFIDENTIAL INFORMATION AND INVENTION ASSIGNMENT AGREEMENT Recorded Jul 22, 2021
From: GAO, XINGHANG
To: BEIJING SPREADTRUM HI-TECH COMMUNICATIONS TECHNOLOGY CO., LTD.
Reel/Frame 056943/0759 →
Priority Claims (1)
CN 201910044101.1 · Jan 17, 2019 · national
Continuity (1)
Related Publication 20220104267A1 · Mar 31, 2022
References Cited (45)
US 20180103465A1 · Agiwal et al. · 2018 [cited by applicant]
US 20190007940A1 · Lee · 2019 [cited by examiner]
US 20190132882A1 · Li · 2019 [cited by examiner]
US 20200107235A1 · Peisa · 2020 [cited by examiner]
US 20200107277A1 · Jeon · 2020 [cited by examiner]
US 20200146055A1 · Lei · 2020 [cited by examiner]
US 20200221499A1 · Hofström · 2020 [cited by examiner]
US 20200288503A1 · Sahlin · 2020 [cited by examiner]
US 20200337044A1 · Lee · 2020 [cited by examiner]
US 20200359426A1 · Pan · 2020 [cited by examiner]
US 20200374730A1 · Gao · 2020 [cited by examiner]
US 20210058947A1 · Lin · 2021 [cited by examiner]
US 20210345424A1 · Cirik · 2021 [cited by examiner]
US 20220104267A1 · Gao · 2022 [cited by examiner]
CN 102231917A · 2011 [cited by applicant]
CN 107889273A · 2018 [cited by applicant]
CN 108631971A · 2018 [cited by applicant]
CN 108781463A · 2018 [cited by applicant]
KR 20180134305A · 2018 [cited by applicant]
TW 201401908A · 2014 [cited by examiner]
WO 2016048044A1 · 2016 [cited by applicant]
WO 2018031869A1 · 2018 [cited by applicant]
WO WO2018031623A1 · 2018 [cited by examiner]
WO 2018085205A1 · 2018 [cited by applicant]
WO 2018133437A1 · 2018 [cited by applicant]
WO WO2018139575A1 · 2018 [cited by examiner]
WO 2018175809A1 · 2018 [cited by applicant]
WO 2018226054A1 · 2018 [cited by applicant]
Vilgelm, Mikhail, et al. “Latmapa: Load-Adaptive Throughput-Maximizing Preamble Allocation for Prioritization in 5G Random Access.” IEEE Access, vol. 5, Jan. 10, 2017, pp. 1103-1116., https://doi.org/10.1109/access.2017… [cited by applicant]
InterDigital Communications “Reciprocity-based UL Beamformed Transmit Diversity” Jan. 2017. [cited by applicant]
ZTE Microelectronics “Consideration on the two-step RACH in NR” Jan. 2017. [cited by applicant]
Feng, Chuan, and Xiao-wen Li. Implemention of LTE System Random Access Procedure. Telecommunication Engineering, vol. 50, No. 9, Sep. 2010, pp. 78-81. [cited by applicant]
Chinese Office Action, dated Jan. 5, 2022 (11 pages). [cited by applicant]
“2-Step RACH Procedure” InterDigital, 3G99 TSG-RAN WG2 Meeting #103bis, R2-1814008, Sep. 27, 2018. [cited by applicant]
Chinese Office Action, dated Jun. 10, 2022 (11 Pages). [cited by applicant]
Nokia, Nokia Shanghai Bell, “On 2-step Random Access Procedure” [online], 3GPP TSG RAN WG1 adhoc_NR_AH_1901 R1 1901192, Internet<URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_AH/NR_AH_1901/Docs/R1 / 1901192.zip>, 20… [cited by applicant]
Samsung, “Discussion on transmission in preconfigured UL resources for NB / IOT” , [online], 3GPP TSG RAN WG1 #95 R1-1812947, Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_95/Docs/R1/1812947.zip>, 2018. [cited by applicant]
LG Electronics, “Consideration on RACH procedure in NR” [online], 3GPPTSG RAN WG1 #86b R1 / 1609267, Internet<URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_86b/Docs/R1, Oct. 1, 2015 1609267.zip>, 2016. [cited by applicant]
Ericsson, “Code Block Segmentation” [online],3GPP TSG RAN WG1 #89 R1 / 1707065, Internet<URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_89/Docs/R1-1707065.zip>, 2017. [cited by applicant]
Japanese Office Action, dated Oct. 3, 2022 (11 Pages). [cited by applicant]
LG Electronics Inc., “Considerations on 2-Step CBRA procedure for NR-U SA, R2-1809940,” 3GPP TSG-RAN WG2 #AH-1807, pp. 1-3, Jul. 6, 2018. [cited by applicant]
Ericsson, “NR two-step random access procedure, R1-1700300,” 3GPP TSG-RAN WGI NR adhoc, pp. 1-4, Jan. 20, 2017. [cited by applicant]
R1-1901192—On 2-step Random Access Procedure, 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901 Taipei, Taiwan, Jan. 21-25, 2019 (7 pages). [cited by applicant]
R1-1609267—Consideration on RACH procedure in NR, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016 (5 pages). [cited by applicant]
R1-1707065—Code Block Segmentation, 3GPP TSG RAN WG1 Meeting #89, Hangzhou, P.R. China, May 15-19, 2017 (4 pages). [cited by applicant]