Data transmission methods, user equipment, base stations and storage media

Abstract

This application proposes a data transmission method, apparatus, user equipment, base station, and storage medium. The method includes: finding a mapping relationship between the resource configuration of the Physical Uplink Shared Channel (PUSCH) resources and preamble sequence configuration information based on the resource configuration of the PUSCH resources; determining the preamble sequence configuration information corresponding to the resource configuration; mapping the preamble sequence to the Physical Random Access Channel (PRACH) resources according to the preamble sequence configuration information; and sending a message containing the PRACH resources and the PUSCH resources. This application facilitates the UE in selecting transmission resources based on the resource configuration of the PUSCH resources.

Description

[0001] This application is a divisional application of patent application number 201910190286.7 (the original application was filed on March 13, 2019, and the invention was entitled "Data Transmission Method, Apparatus, User Equipment, Base Station and Storage Medium"). Technical Field

[0002] This application relates to the field of communications, specifically to data transmission methods, apparatus, user equipment, base stations, and storage media. Background Technology

[0003] In 2-step RACH or connectionless data transmission, the Random Access A message (msgA) or data packet is transmitted through both the Physical Random Access Channel (PRACH) and Physical Uplink Shared Channel (PUSCH) resources. The User Equipment (UE) maps the preamble sequence to the PRACH resource according to different preamble sequence configuration information. The PUSCH resource carries at least the UE identifier (ID), which can be 56 bits, 72 bits, 144 bits, or 208 bits. Depending on the UE's state and the triggering event, the payload size of the message may exceed 208 bits. Different payload sizes may correspond to different PUSCH resource configurations. In existing technology, the UE cannot select the corresponding preamble sequence configuration information to map the preamble sequence based on its own PUSCH resource configuration. Summary of the Invention

[0004] To address at least one of the aforementioned technical problems, embodiments of this application provide the following solutions.

[0005] This application provides a data transmission method, including:

[0006] Based on the resource configuration of the PUSCH resource, find the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, and determine the preamble sequence configuration information corresponding to the resource configuration.

[0007] Map the preamble sequence to the PRACH resource according to the preamble sequence configuration information;

[0008] Send a message containing the PRACH and PUSCH resources.

[0009] This application provides a data transmission method, including:

[0010] Receive messages containing PRACH and PUSCH resources;

[0011] Obtain the preamble sequence configuration information of the PRACH resource in the message;

[0012] Based on the preamble sequence configuration information, find the mapping relationship between the pre-saved PUSCH resource configuration and the preamble sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information.

[0013] Information from the PUSCH resource is obtained according to the resource configuration mode.

[0014] This application provides a data transmission device, including:

[0015] The first lookup module is used to look up the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information based on the resource configuration of the PUSCH resource, and determine the preamble sequence configuration information corresponding to the resource configuration.

[0016] The mapping module is used to map the preamble sequence to the PRACH resource according to the preamble sequence configuration information;

[0017] The first sending module is used to send a message containing the PRACH resource and the PUSCH resource.

[0018] This application provides a data transmission device, including:

[0019] The second receiving module is used to receive messages containing PRACH resources and PUSCH resources;

[0020] The first acquisition module is used to acquire the preamble sequence configuration information of the PRACH resource in the message;

[0021] The second lookup module is used to look up the mapping relationship between the pre-saved PUSCH resource configuration and the pre-saved sequence configuration information based on the pre-saved sequence configuration information, and to determine the resource configuration mode of the PUSCH resource corresponding to the pre-saved sequence configuration information.

[0022] The second acquisition module is used to acquire information from the PUSCH resource according to the resource configuration mode.

[0023] This application provides a data transmission UE, the UE including: a processor and a storage device;

[0024] The storage device is used to store one or more programs;

[0025] When the one or more programs are executed by the one or more processors, the processors implement any of the embodiments described in the first data transmission method above.

[0026] This application embodiment also provides a data transmission base station, the base station including: a processor and a storage device;

[0027] The storage device is used to store one or more programs;

[0028] When the one or more programs are executed by the one or more processors, the processors implement any of the embodiments described in the second data transmission method above.

[0029] This application provides a communication system, which includes a UE and a base station as described in this application.

[0030] This application provides a storage medium storing a computer program, which, when executed by a processor, implements any of the methods described in this application.

[0031] The data transmission method provided in this application allows the UE to select corresponding preamble sequence configuration information based on its own PUSCH resource configuration before sending a message. This preamble sequence configuration information is then used to map the preamble sequence to the PRACH resource, thus facilitating the UE's selection of transmission resources based on the PUSCH resource configuration. Furthermore, it simplifies the base station's reception of the message. Attached Figure Description

[0032] Figure 1 This is a schematic diagram illustrating the implementation process of a data transmission method according to an embodiment of this application;

[0033] Figure 2 This is a schematic diagram illustrating the mapping method of the M Preamble sequences included in the RO of this application embodiment;

[0034] Figure 3 This is a schematic diagram illustrating the implementation process of a data transmission method according to an embodiment of this application;

[0035] Figure 4 This is a schematic diagram illustrating the interaction process between the base station and the UE in an embodiment of this application;

[0036] Figure 5 This is a schematic diagram of a data transmission device according to an embodiment of this application;

[0037] Figure 6 This is a schematic diagram of a data transmission device according to an embodiment of this application;

[0038] Figure 7 This is a schematic diagram of the UE structure for data transmission according to an embodiment of this application;

[0039] Figure 8 This is a schematic diagram of the base station structure for data transmission according to an embodiment of this application;

[0040] Figure 9 This is a schematic diagram of the communication system structure according to an embodiment of this application. Detailed Implementation

[0041] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be arbitrarily combined with each other.

[0042] 5G NR-U, operating in unlicensed spectrum, introduces a new resource mapping mode for PRACH, mapping preamble sequences onto PRACH in an interleaved manner. Table 1 below shows the possible combinations of the number of interlaced blocks (denoted by M in Table 1) and the number of resource blocks (RBs) per interlaced block (denoted by N in Table 1) for a transmit bandwidth of 20MHz under different subcarrier spacings (SCS).

[0043] Table 1

[0044]

[0045] The interleaved mapping patterns of PRACH include, but are not limited to, the following:

[0046] Interlacing at the level of a uniform physical resource block (PRB), interlacing at the level of a non-uniform PRB, interlacing at the level of a uniform resource element (RE), and contiguous mapping.

[0047] For different PRACH interleaving mapping modes, embodiments of this application propose a data transmission method, such as... Figure 1 This is a schematic diagram illustrating the implementation flow of a data transmission method according to an embodiment of this application, including:

[0048] Step S11: Based on the resource configuration of the PUSCH resource, find the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, and determine the preamble sequence configuration information corresponding to the resource configuration;

[0049] Step S12: Map the preamble sequence to the PRACH resource according to the preamble sequence configuration information;

[0050] Step S13: Send a message containing the PRACH resource and PUSCH resource.

[0051] In one implementation, the information in the PUSCH resource includes at least one of UE ID and user plane data. The message can be a random access message or a data packet message.

[0052] The method proposed in this application embodiment can be applied to a UE. Before step S11 above, it may further include: the UE receiving the mapping relationship between the resource configuration and preamble sequence configuration information of the PUSCH resource from the base station.

[0053] In one implementation, the Preamble sequence configuration information may include at least one of the following: Preamble ID, Interlace ID, the number of RBs in each Interlace block occupied by the Preamble sequence (i.e., N in Table 1 above), and the time-frequency location information of the preamble sequence.

[0054] In one implementation, the Preamble ID may include at least one of the following: a Preamble Index, a Preamble Group Index, and the sequence number of the preamble within the preamble group.

[0055] In one implementation, the Interlace ID may include at least one of the following: Interlace Index, Interlace Group Index, and the sequence number of the interlace block within the interlace group.

[0056] After determining the resource configuration of the PUSCH resource, the UE can determine the preamble sequence configuration information to be used when mapping the preamble sequence by following the above step S11, based on the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information.

[0057] In one implementation, the resource configuration of the PUSCH resource includes at least one of the following: the port index of the demodulation reference signal (DMRS) corresponding to the PUSCH resource, the frequency domain resource information of the PUSCH resource, the time domain resource information of the PUSCH resource, the payload size of the message, the waveform, the SCS, and the modulation and coding scheme.

[0058] The frequency domain resource information of the PUSCH resource may include: the number of RBs occupied by the frequency domain resource of the PUSCH resource, and the offset of the position of the frequency domain resource of the PUSCH resource relative to the frequency domain position of the Preamble sequence.

[0059] In one implementation, the location of the frequency domain resource of the PUSCH resource may include at least one of the RB block index of the starting point of the frequency domain resource of the PUSCH resource, the interlaced block index where the frequency domain resource of the PUSCH resource is located, and the RB block index of the frequency domain resource of the PUSCH resource in the Interlace.

[0060] The temporal resource information of the PUSCH resource may include: the number of slots or mini-slots occupied by the temporal resource of the PUSCH resource, and the offset of the position of the temporal resource of the PUSCH resource relative to the temporal position of the Preamble sequence.

[0061] In one implementation, the location of the temporal resource of the PUSCH resource includes at least one of the following: the system frame number (SFN) of the starting point of the temporal resource of the PUSCH resource, the subframe number of the starting point of the temporal resource of the PUSCH resource, the slot / mini-slot position of the starting point of the temporal resource of the PUSCH resource, and the start symbol of the temporal resource of the PUSCH resource.

[0062] In one implementation, when determining its PUSCH resource allocation, the UE can first determine the Modulation and Coding Scheme (MCS) level based on its Payload Size and channel conditions. For example, a UE in a cell center with better channel conditions can use certain MCS levels with higher MCS orders for data transmission, while a UE with poorer channel conditions can use certain MCS levels with lower MCS orders. Then, the UE determines its PUSCH resource allocation based on the determined MCS level, such as the size of the time-frequency resources occupied (including the number of RBs).

[0063] For the configuration of 2-step RACH PUSCH RB resource blocks, different granularities can be used to configure users and map them to different groups of Preamble resource pools. The Preamble resource pool can be the same as the NR / LTE Preamble resource pool, or some new Preamble resource pools can be added. Typical granularity values ​​are 1, 2, 3, and 6 RBs.

[0064] The UE can select the Preamble resource pool based on the Reference Signal Receiving Power (RSRP) and the Transport Block Size (TBSize).

[0065] Specifically, if RSRP is greater than or equal to the threshold of RSRP (RSRP0) and TBSize is greater than or equal to the threshold of TBSize (TBSize0), the Preamble resource pool with the largest corresponding RB resource granularity can be selected.

[0066] If either RSRP or TBSize is greater than or equal to the corresponding threshold, then a Preamble resource pool with a larger RB resource granularity can be selected.

[0067] If RSRP is less than or equal to the threshold of RSRP (RSRP0), and TBSize is less than or equal to the threshold of TBSize (TBSize0), the Preamble resource pool with the smallest corresponding RB resource granularity can be selected.

[0068] Once the Preamble resource pool and the corresponding RB resource granularity are determined, the MCS level can be determined.

[0069] In addition, the RSRP mentioned above can also be replaced by path loss.

[0070] The sizes of the aforementioned Preamble resource pools may be equal. Alternatively, the size of each Preamble resource pool may be determined based on the possible distribution of the information carried by different PUSCH resources.

[0071] For resource configuration scenarios with interlaces, the user's DMRS port-related information, such as the DMRS port index or DMRS orthogonal cover code (OCC) pattern, is related to the interlace ID and preamble ID. For resource configuration scenarios without interlaces, the user's DMRS port-related information, such as the DMRS port index or DMRS OCC pattern, is related to the preamble ID.

[0072] Alternatively, the UE can calculate the MCS level based on its payload size and the size of the selected time-frequency resource block. For example, if the selected time-frequency resource block is large, the MCS order used may be lower. At least a portion of the payload size is modulated using an MCS type order that includes at least Binary Phase Shift Keying (BPSK), pi-2BPSK, and Quadrature Phase Shift Keying (QPSK).

[0073] After the UE determines its PUSCH resource configuration, it can determine the preamble sequence configuration information corresponding to that PUSCH resource configuration according to preset rules. These preset rules can specifically be a mapping relationship between the PUSCH resource configuration and the preamble sequence configuration information, and are pre-issued to the UE by the base station. The preset rules may be based on the interlace block index, the number of redundancies (RBs) occupied by the interlace block, the possible start or end point of the interlace block, or preamble sequence related information within the interlace block. This related information may include the PreambleIndex, the cyclic shift (CS) information of the preamble sequence, the bandwidth occupied by the preamble in the interlace block, the number of recurrent elements (REs) in the interlace block, and the time-frequency position of the preamble, etc.

[0074] For PRACH mapping with non-uniform PRB-level interleaving patterns, the UE's MCS mode, payload size, and traffic model for different interleaving patterns can be indicated by information related to the interlace block containing the user's preamble. For example, the start and end points, size range, interlace index, preamble index, cyclic shift of the preamble, or the number of RBs contained in the interlace block correspond to different PUSCH resource configurations. The interlace ID indicates different DMRS port indices and resource granularity items for different PUSCH scheduling supported by the system.

[0075] Tables 2A and 2B below show examples of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0076] In Table 2A, the first column contains preamble sequence configuration information, specifically the Interlace Index. The following six columns contain PUSCH resource configurations, including the DMRS port index and the frequency and time domain resource information for the PUSCH resources. After determining its own PUSCH resource configuration, the UE uses this configuration to find the mapping relationship shown in Table 2A to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped based on this preamble sequence configuration information.

[0077] Table 2A

[0078]

[0079]

[0080] In Table 2B, the first column contains preamble sequence configuration information, specifically the Interlace Index. The following seven columns contain PUSCH resource configurations, including the DMRS port index and the frequency and time domain resource information for the PUSCH. After determining its own PUSCH resource configuration, the UE uses this configuration to find the mapping relationship shown in Table 2B to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped based on this preamble sequence configuration information.

[0081] Table 2B

[0082]

[0083]

[0084] The mapping relationships shown in Tables 2A and 2B can be applied to scenarios where the preamble resource is 15kHz and the OFDM symbol uses NR Type I1 front-loaded symbol. The mapping relationships shown in Tables 2A and 2B are mainly determined according to the PUSCH DMRS port configuration and the size of the RBs that may be occupied, that is, they are multiplexed on a single resource and shifted apart in the time and frequency domains.

[0085] In Tables 2A and 2B, the DMRS port Index ranges from 1 to 4, specifically including 1, 2, 3, and 4. In other embodiments of this application, the DMRS port Index may also include other ranges, for example:

[0086] Integers in the range of 0 to 3, i.e., 0, 1, 2, and 3; or,

[0087] Integers in the range of 0 to 5, i.e., 0, 1, 2, 3, 4, and 5; or,

[0088] Integers in the range 0 to 7, namely 0, 1, 2, 3, 4, 5, 6, and 7; or;

[0089] Integers in the range 0 to 11, namely 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and 11; or;

[0090] Integers in the range of 1 to 4, i.e., 1, 2, 3, and 4; or,

[0091] Integers in the range 1 to 6, namely 1, 2, 3, 4, 5, and 6; or,

[0092] Integers in the range 1 to 8, namely 1, 2, 3, 4, 5, 6, 7, and 8; or;

[0093] Integers in the range of 1 to 12, namely 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 and 12.

[0094] Table 3 below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0095] The first column contains preamble sequence configuration information, specifically the number of resource blocks (RBs) in each interleaved block occupied by the preamble sequence. The second column contains PUSCH resource configuration, specifically the Waveform. There are two possible values ​​for Waveform: Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform and Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) waveform.

[0096] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 3 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0097] Table 3

[0098]

[0099] For DFT-S-OFDM waveforms, to facilitate waveform generation, the value of N is preferably a multiple of 2, 3, or 5. Therefore, for cases where there are two different numbers of RBs (12 and 13) and these represent two different waveforms, the case where each interlace occupied by the preamble sequence contains 13 RBs is used to indicate the CP-OFDM waveform, and the case where each interlace occupied by the preamble sequence contains 12 RBs is used to indicate the DFT-S-OFDM waveform.

[0100] Table 4 below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0101] The first column contains the preamble sequence configuration information, specifically the number of resource blocks (RBs) in each interleaved block occupied by the preamble sequence. The second column contains the resource configuration of the PUSCH resource, specifically the Payload Size. In Table 4, the PayloadSize has two possible values: 56 bits and 72 bits.

[0102] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 4 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0103] Table 4

[0104]

[0105]

[0106] Table 5A below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0107] The first column contains the preamble sequence configuration information, specifically the Interlace Index. The second column contains the PUSCH resource configuration, specifically the Waveform. The Waveform can have two possible values: CP-OFDM waveform and DFT-S-OFDM waveform.

[0108] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 5A based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0109] Table 5A

[0110] Interlace Index Waveform 1～K CP-OFDM K+1~M DFT-S-OFDM

[0111] Since the Interlace Index can take more than two values, in Table 5A, some possible values ​​of the Interlace Index can be selected to correspond to the CP-OFDM waveform, while other values ​​can be used to correspond to the DFT-S-OFDM waveform. In Table 5A, K is an integer greater than 1 and less than (M-1). The example in Table 5 is only one example; in the embodiments of this application, the Interlace Index corresponding to a Waveform can be discontinuous.

[0112] Table 5B below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0113] The first column contains the preamble sequence configuration information, specifically the Interlace Group Index. The second column contains the PUSCH resource configuration, specifically the Waveform. The Waveform can have two possible values: CP-OFDM waveform and DFT-S-OFDM waveform.

[0114] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 5B based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0115] Table 5B

[0116]

[0117]

[0118] Table 6A below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0119] The first column contains the preamble sequence configuration information, specifically the Interlace Index. The second column contains the PUSCH resource configuration, specifically the Payload Size. In Table 6A, the Payload Size can have two possible values: 56 bits and 72 bits.

[0120] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 6A based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0121] Table 6A

[0122] Interlace Index Payload Size 1～Q 56 bits Q+1~M 72 bits

[0123] Since the Interlace Index can have more than two values, in Table 6A, some possible values ​​of the Interlace Index can be selected, corresponding to 56 bits, while other values ​​can be used, totaling 72 bits. In Table 6A, Q is an integer greater than 1 and less than (M-1). The example in Table 6A is merely one illustration; in this embodiment, the Interlace Index corresponding to one Payload Size can be non-contiguous. Furthermore, the Payload Size can also have values ​​such as 144 bits and 208 bits. This embodiment can adopt a similar approach, using different values ​​of the Interlace Index to correspond to four or more Payload Size values.

[0124] Table 6B below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0125] The first column contains the preamble sequence configuration information, specifically the Interlace Group Index. The second column contains the PUSCH resource configuration, specifically the Payload Size. In Table 6B, the Payload Size can have two possible values: 56 bits and 72 bits.

[0126] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 6B based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0127] Table 6B

[0128] Interlace Group Index Payload Size 1 56 bits 2 72 bits

[0129] This application embodiment can also indicate different combinations of Waveform and Payload Size, as shown in Table 7A below.

[0130] Table 7A below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in the embodiments of this application.

[0131] The first column contains the preamble sequence configuration information, specifically the Interlace Index. The second column contains the PUSCH resource configuration, specifically the combination of Waveform and Payload Size.

[0132] After the UE determines the resource configuration of its own PUSCH resource, it looks up the mapping relationship shown in Table 7A according to the resource configuration of the PUSCH resource, and determines the corresponding preamble sequence configuration information. Then, it maps the Preamble sequence according to the preamble sequence configuration information.

[0133] Table 7A

[0134] Interlace Index Waveform and Payload Size 1～G CP-OFDM and 56-bit G+1~L DFT-S-OFDM and 72-bit L+1~T CP-OFDM and 72-bit T+1~M DFT-S-OFDM and 56-bit

[0135] In Table 7A, there are 4 possible values for the combination of Waveform and Payload Size. In Table 7A, G, L, and T are integers greater than 1 and less than (M - 1), and G < L < T. These three integers G, L, and T divide some of the possible values of the Interlace Index into 4 parts, and each part corresponds to one possible value of the combination of Waveform and Payload Size. The example of Table 7A is only an illustration, and in the application embodiment, the Interlace Index corresponding to one possible value of the combination of Waveform and Payload Size can be discontinuous.

[0136] The following Table 7B is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the application embodiment under different interleaving modes.

[0137] Among them, the first column is the preamble sequence configuration information, specifically the Interlace Group Index. The second column is the resource configuration of the PUSCH resource, specifically the combination of Waveform and Payload Size.

[0138] After the UE determines the resource configuration of its own PUSCH resource, it looks up the mapping relationship shown in Table 7B according to the resource configuration of the PUSCH resource, and determines the corresponding preamble sequence configuration information. Then, it maps the Preamble sequence according to the preamble sequence configuration information.

[0139] Table 7B

[0140] Interlace Group Index Waveform and Payload Size 1 CP-OFDM and 56-bit 2 DFT-S-OFDM and 72-bit 3 CP-OFDM and 72-bit 4 DFT-S-OFDM and 56-bit

[0141] The following Table 8A is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the application embodiment under different interleaving modes.

[0142] Among them, the first column is the preamble sequence configuration information, specifically the Interlace Index. The second column is the resource configuration of the PUSCH resource, specifically the SCS. There are 3 possible values for SCS, including 15kHz, 15kHz, and 60kHz.

[0143] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 8A based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0144] Table 8A

[0145]

[0146]

[0147] The example in Table 8A is merely one illustration. In the application embodiments, the Interlace Index corresponding to a SCS may be discontinuous.

[0148] Table 8B below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in the embodiments of this application.

[0149] The first column contains the preamble sequence configuration information, specifically the Interlace Group Index. The second column contains the PUSCH resource configuration, specifically the SCS. The SCS can have three possible values: 15kHz, 15kHz, and 60kHz.

[0150] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 8B based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0151] Table 8B

[0152] Interlace Group Index SCS 1 15 2 30 3 60

[0153] The possible values ​​for SCS can also include other values, such as 15kHz, 30kHz, 60kHz, and 120kHz. Table 9A below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in the embodiments of this application.

[0154] The first column contains preamble sequence configuration information, specifically the Interlace Index. The second column contains PUSCH resource configuration, specifically the SCS. The SCS has four possible values: 15kHz, 30kHz, 60kHz, and 120kHz.

[0155] Table 9A

[0156]

[0157]

[0158] The example in Table 9A is merely one example. In the application embodiments, the Interlace Index corresponding to a SCS may be discontinuous.

[0159] Table 9B below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in different interleaving modes in this application embodiment.

[0160] The first column contains the preamble sequence configuration information, specifically the Interlace Group Index. The second column contains the PUSCH resource configuration, specifically the SCS. The SCS has four possible values: 15kHz, 30kHz, 60kHz, and 120kHz.

[0161] Table 9B

[0162] Interlace Group Index SCS 1 15 2 30 3 60 4 120

[0163] Tables 5A to 9B describe the mapping relationship between Interlace Index / Interlace GroupIndex and Payload Size / Waveform / SCS under different interlacing modes. Embodiments of this application can also use other interlacing block IDs, such as the interlacing block's sequence number within the interlacing block group, to achieve mapping with the resource configuration of PUSCH resources.

[0164] In the absence of interleaved blocks, the implementation of this application can use Preamble Group ID to map the resource configuration of PUSCH resources. Table 10 below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in the embodiment of this application when there is no interleaved mode.

[0165] The first column contains preamble sequence configuration information, specifically the Preamble Group Index. The second column contains PUSCH resource configuration, specifically the Waveform. The Waveform can have two possible values: CP-OFDM waveform and DFT-S-OFDM waveform.

[0166] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 10 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0167] Table 10

[0168] Preamble Group Index Waveform 1 CP-OFDM 2 DFT-S-OFDM

[0169] In Table 10, the sequence numbers of the Preamble sequences within a Preamble Group can be non-consecutive.

[0170] Table 11 below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in the embodiment of this application when there is no interleaving block.

[0171] The first column contains the preamble sequence configuration information, specifically the Preamble Group Index. The second column contains the PUSCH resource configuration, specifically the Payload Size. The Payload Size can have two possible values: 56 bits and 72 bits.

[0172] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 11 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0173] Table 11

[0174] Preamble Group Index Payload Size A 56 bits B 72 bits

[0175] Table 12 below shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in the embodiments of this application when there is no interleaving block.

[0176] The first column contains the preamble sequence configuration information, specifically the Preamble Group Index. The second column contains the PUSCH resource configuration, specifically the combination of Waveform and Payload Size.

[0177] After determining the resource configuration of its PUSCH resources, the UE looks up the mapping relationship shown in Table 12 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0178] Table 12

[0179] Preamble Group Index Waveform and Payload Size 1 CP-OFDM and 56-bit 2 DFT-S-OFDM and 72-bit 3 CP-OFDM and 72-bit 4 DFT-S-OFDM and 56-bit

[0180] In Table 12, the sequence numbers of the Preamble sequences within a Preamble Group can be non-consecutive.

[0181] In the above embodiments, the possible values ​​for Payload Size are 56 bits and 72 bits. Embodiments of this application may also indicate possible values ​​for Payload Size as 56 bits, 72 bits, 144 bits, and 208 bits. Table 13 below shows an example of the mapping relationship between PUSCH resource configuration and preamble sequence configuration information in embodiments of this application when there are no interleaved blocks.

[0182] The first column contains the preamble sequence configuration information, specifically the Preamble Group Index. The second column contains the PUSCH resource configuration, specifically the Payload Size.

[0183] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 13 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0184] Table 13

[0185]

[0186]

[0187] In Table 13, the sequence numbers of the Preamble sequences within a Preamble Group can be non-consecutive.

[0188] Tables 10 to 13 illustrate the mapping relationship between the Preamble Group Index and Payload Size / Waveform in the absence of interleaved blocks. The Preamble Group Index is used as an example in the above implementation. The Preamble Group Index is one possible case for the Preamble ID. Other implementations can also be used in this application, such as replacing the Preamble Group Index in the above mapping tables with the Preamble Index, as shown in Tables 10B to 13B. Alternatively, the Preamble Group Index can be replaced with the Preamble ID's sequence number within the Preamble Group, as shown in Tables 10C to 13C. Using the aforementioned implementations, the mapping between the Preamble ID and the resource allocation of PUSCH resources is achieved. It should be noted that even if different symbols are used in Tables 10C to 13C, if the Preamble allocation in each group is balanced, the maximum value of the Preamble ID's sequence number within the group may be equal.

[0189] Table 10B

[0190] Preamble Index Waveform 1-W CP-OFDM W+1-N DFT-S-OFDM

[0191] Table 11B

[0192] Preamble Index Payload Size 1～O 56 bits O+1~P 72 bits

[0193] Table 12B

[0194]

[0195]

[0196] Table 13B

[0197] Preamble Index Payload Size 1～S 56 bits S+1~H 72 bits H+1~I 144 bits I+1~R 208 bits

[0198] Table 10C

[0199] The sequence number of the leader within the leader group Waveform 1～U CP-OFDM 1～V DFT-S-OFDM

[0200] Table 11C

[0201] The sequence number of the leader within the leader group Payload Size 1～U' 56 bits 1～V' 72 bits

[0202] Table 12C

[0203] The sequence number of the leader within the leader group Waveform and Payload Size 1~λ CP-OFDM and 56-bit 1~μ DFT-S-OFDM and 72-bit 1~Ф CP-OFDM and 72-bit 1~δ DFT-S-OFDM and 56-bit

[0204] Table 13C

[0205] The sequence number of the leader within the leader group Payload Size 1~σ 56 bits 1~ρ 72 bits 1～π 144 bits 1~ω 208 bits

[0206] Furthermore, the resource configuration of the aforementioned PUSCH resources may also include modulation and coding schemes. Modulation and coding schemes may include at least one of BPSK modulation, pi / 2-BPSK modulation, and QPSK modulation. Tables 13D and 13E below show examples of the mapping relationship between the resource configuration of PUSCH resources and preamble sequence configuration information in embodiments of this application when there are no interleaved blocks.

[0207] In Table 13D below, the first column shows the preamble sequence configuration information, specifically the preamble's sequence number within the preamble group. The second column shows the PUSCH resource configuration, specifically the combination of the MCS index (MSC Index) and the payload size. In Table 13D, the MSC Index has two possible values, representing two modulation and coding schemes.

[0208] Table 13D

[0209] The sequence number of the leader within the leader group MCS Index & payload size 1~σ 0 & 56 bits 1~ρ 1 & 56 bits 1～π 0 & 72 bits 1~ω 1 & 72 bits

[0210] In Table 13D, the first column contains preamble sequence configuration information, specifically the preamble number. The second column contains PUSCH resource configuration, specifically the combination of MSC Index and Payload Size. In Table 13E, the MSC Index has two possible values, representing two modulation and coding schemes.

[0211] Table 13E

[0212]

[0213]

[0214] Table 14 below shows an example of the mapping relationship between PUSCH resource configuration and preamble sequence configuration information in different interleaving modes in this application embodiment. In this embodiment, if there are multiple (e.g., 64) preamble sequences on an access opportunity (RO, RACH Occasion), the preamble index and interlace index can be used to jointly indicate the PUSCH resource configuration. In Table 14, the first and second columns are the preamble sequence configuration information, including the interlace index and preamble index. The last five columns are the PUSCH resource configuration, including the DMRS port index and the frequency domain and time domain resource information of the PUSCH resource.

[0215] After determining the resource configuration of its PUSCH resources, the UE searches for the mapping relationship shown in Table 14 based on the resource configuration of the PUSCH resources to determine the corresponding preamble sequence configuration information. Then, it performs the mapping of the preamble sequence based on the preamble sequence configuration information.

[0216] Table 14

[0217]

[0218]

[0219]

[0220]

[0221]

[0222]

[0223]

[0224]

[0225] In the table above, the interlaced block ID is specifically the Interlace Index, and the Preamble ID is specifically the Preamble Index, as an example for illustration. In the embodiments of this application, the interlaced block ID can also be the Interlace Group Index or the sequence number of the interlaced block within the interlaced block group, and the Preamble ID can also be the Preamble Group Index or the sequence number of the leader within the leader group.

[0226] In the absence of interleaving mode, if the number of DMRS ports is divisible by the number of preamble sequences, the preamble index can be used to map the resource configuration of PUSCH resources to the preamble sequence configuration information. If, in the absence of interleaving mode, the number of DMRS ports is not divisible by the number of preamble sequences, the location or ID of the RO (Real Estate Organization) combined with the preamble index can be used to map the resource configuration of PUSCH resources to the preamble sequence configuration information. Tables 15 and 16 below illustrate these two scenarios respectively.

[0227] Table 15 shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in the embodiments of this application when there is no interleaving block.

[0228] The first column contains preamble sequence configuration information, specifically the Preamble Index. The following five columns contain PUSCH resource configurations, including the DMRS port index and the frequency and time domain resource information for the PUSCH. After determining its own PUSCH resource configuration, the UE uses the mapping relationship shown in Table 15 to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped based on this preamble sequence configuration information.

[0229] Table 15

[0230]

[0231]

[0232]

[0233] In the table above, the specific value in column 6, "Offset of the temporal resource position of the PUSCH resource relative to the temporal position of the Preamble sequence," represents one possible implementation. In this embodiment, the numbers in column 6 of Table 15 can be other values; that is, number 1 in column 6 can be replaced with t1, number 2 in column 6 can be replaced with t2, and so on, and number 6 in column 6 can be replaced with t6. Where t1, t2, t3, t4, t5, and t6 are all integers.

[0234] Table 16 shows an example of the mapping relationship between the resource configuration of PUSCH resources and the preamble sequence configuration information in the embodiments of this application when there is no interleaving block.

[0235] The first and second columns contain preamble sequence configuration information, specifically the RO ID and Preamble Index. The last five columns contain PUSCH resource configuration, including the DMRS port index and the frequency and time domain resource information of the PUSCH resource. After the UE determines its own PUSCH resource configuration, it looks up the mapping relationship shown in Table 16 based on the PUSCH resource configuration to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to this preamble sequence configuration information.

[0236] Table 16

[0237]

[0238]

[0239] In the table above, the specific value in column 7, "Offset of the temporal resource position of the PUSCH resource relative to the temporal position of the Preamble sequence," represents one possible implementation. In this embodiment, the numbers in column 7 of Table 16 can be other values; that is, number 1 in column 7 can be replaced with t1, and number 2 in column 6 can be replaced with t2. Both t1 and t2 are integers. The table above uses an example where 13 Preamble sequences are available for a single RO. The table uses all available Preamble sequences from one RO and any three Preamble sequences from a second RO, combined with the Preamble Index, to jointly indicate the resource configuration of the PUSCH resource.

[0240] like Figure 2 This is a schematic diagram illustrating the mapping method of the M Preamble sequences included in the RO of this application embodiment. Figure 2 In this context, RO comprises M preamble sequences, namely P1, P2, ..., P... M P1, P2, ... P MThey are mapped to different locations respectively. P1 occupies 1 RB, with a corresponding DMRS Port Index of k; P2 occupies 2 RBs, with a corresponding DMRS Port Index of m; P M The number of RBs occupied is 6, and the corresponding DMRS Port Index is g.

[0241] In the mapping relationships described in the tables above, the location of the frequency domain resource of the PUSCH resource includes at least one of the following: the RB block index of the starting point of the PUSCH frequency domain resource and the interleaved block index where the PUSCH is located. The location of the frequency domain resource of the PUSCH resource includes at least one of the following: the system frame number (SFN) of the starting point of the PUSCH time domain resource, the subframe number of the starting point of the PUSCH time domain resource, the time slot or micro-time slot position of the starting point of the PUSCH time domain resource, and the PUSCH start symbol.

[0242] The above describes various forms of mapping relationships between PUSCH resource configuration and preamble sequence configuration information. The mapping relationships in the embodiments of this application are not limited to the above forms. It should be noted that in the above table, "the number of RBs occupied by the frequency domain resources of PUSCH resources" and "the number of time slots / mini-slots occupied by the time domain resources of PUSCH resources" can refer to the resource allocation granularity of PUSCH resources, and the time and frequency resources occupied by the user can be a multiple of this granularity.

[0243] Based on the above mapping relationship, the UE can determine the preamble sequence configuration information corresponding to its own PUSCH resource configuration, thereby enabling the selection of transmission resources.

[0244] Correspondingly, the base station can simplify the receiving and demodulation process by adopting the above mapping relationship. For example... Figure 3 This is a schematic diagram illustrating the implementation flow of a data transmission method according to an embodiment of this application, including:

[0245] S31: Receive a message containing Physical Random Access Channel (PRACH) resources and Physical Uplink Shared Channel (PUSCH) resources;

[0246] S32: Obtain the preamble sequence configuration information of the PRACH resource in the message;

[0247] S33: Based on the preamble sequence configuration information, find the mapping relationship between the pre-saved PUSCH resource configuration and the preamble sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information.

[0248] S34: Obtain information from the PUSCH resource according to the resource configuration mode.

[0249] In one implementation, the information in the PUSCH resource includes at least one of UE ID and user plane data. The message can be a random access message or a data packet message.

[0250] The method proposed in this application embodiment can be applied to a base station. Before step S31 above, it may further include: sending the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information to the UE, so that the UE sends the message according to its own PUSCH resource configuration and the mapping relationship.

[0251] The mapping relationship between the resource configuration of PUSCH resources and the configuration information of the preceding sequence has been described in the above embodiments and will not be repeated here.

[0252] like Figure 4 This is a schematic diagram of the interaction process between the base station and the UE in an embodiment of this application, including:

[0253] S41: The mapping relationship between the resource configuration and preamble sequence configuration information of the PUSCH resources sent by the base station to the UE.

[0254] S42: The UE looks up the mapping relationship based on its own PUSCH resource configuration and determines the corresponding preamble sequence configuration information. Based on the determined preamble sequence configuration information, the UE maps the preamble sequence to the PRACH resource. The UE sends a message containing the PRACH and PUSCH resources to the base station.

[0255] S43: The base station receives the message and obtains the preamble sequence configuration information of the PRACH resource from the message. Based on the preamble sequence configuration information, it looks up the pre-saved mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information to determine the resource configuration mode of the corresponding PUSCH resource. It then obtains the information from the PUSCH resource based on this resource configuration mode.

[0256] This application also proposes a data transmission device, such as... Figure 5 This is a schematic diagram of the data transmission device structure according to an embodiment of the present application, including:

[0257] The first lookup module 501 is used to look up the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information according to the resource configuration of the PUSCH resource, and determine the preamble sequence configuration information corresponding to the resource configuration.

[0258] Mapping module 502 is used to map the preamble sequence to PRACH resources according to the preamble sequence configuration information;

[0259] The first sending module 503 is used to send a message containing the PRACH resource and the PUSCH resource.

[0260] In the above embodiments, the information in the PUSCH resources includes at least one of UE ID and user plane data.

[0261] In one embodiment, the above-mentioned apparatus may further include:

[0262] The first receiving module 504 is used to receive the mapping relationship between the resource configuration and preamble sequence configuration information of the PUSCH resource from the base station.

[0263] This embodiment can be applied to the UE. The mapping relationship between the PUSCH resource configuration and the preamble sequence configuration information in this embodiment is the same as that described in the above embodiments, and will not be repeated here.

[0264] This application also proposes a data transmission device, such as... Figure 6 This is a schematic diagram of a data transmission device structure according to an embodiment of the present application, including:

[0265] The second receiving module 601 is used to receive a message containing PRACH resources and PUSCH resources;

[0266] The first acquisition module 602 is used to acquire the preamble sequence configuration information of the PRACH resource in the message;

[0267] The second lookup module 603 is used to look up the mapping relationship between the pre-saved PUSCH resource configuration and the pre-saved sequence configuration information according to the pre-saved sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the pre-saved sequence configuration information.

[0268] The second acquisition module 604 is used to acquire information from the PUSCH resource according to the resource configuration mode.

[0269] In one implementation, the information in the PUSCH resource includes at least one of UE ID and user plane data.

[0270] In one embodiment, the above-mentioned apparatus may further include:

[0271] The second sending module 605 is used to send the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information to the UE, so that the UE sends the message according to its own PUSCH resource configuration and the mapping relationship.

[0272] This embodiment can be applied to base stations. The mapping relationship between the PUSCH resource configuration and the preamble sequence configuration information in this embodiment is the same as that described in the above embodiments, and will not be repeated here.

[0273] The functions of each module in the devices of this application embodiment can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here.

[0274] Figure 7 This is a schematic diagram of the UE structure for data transmission according to an embodiment of this application, as shown below. Figure 7 As shown, the UE 70 provided in this application embodiment includes a memory 703 and a processor 704. The UE 70 may further include an interface 701 and a bus 702. The interface 701, memory 703, and processor 704 are connected via the bus 702. The memory 703 is used to store instructions. The processor 704 is configured to read the instructions to execute the technical solution of the method embodiment applied to the UE described above. Its implementation principle and technical effects are similar and will not be repeated here.

[0275] Figure 8 This is a schematic diagram of the base station structure for data transmission according to an embodiment of this application, as shown below. Figure 8 As shown in the figure, the base station 80 provided in this application embodiment includes a memory 803 and a processor 804. The base station 80 may further include an interface 801 and a bus 802. The interface 801, memory 803, and processor 804 are connected via the bus 802. The memory 803 is used to store instructions. The processor 804 is configured to read the instructions to execute the technical solution of the method embodiment applied to the base station described above. Its implementation principle and technical effects are similar, and will not be repeated here.

[0276] Figure 9 This is a schematic diagram of the communication system structure according to an embodiment of this application, such as... Figure 9 As shown, the system includes: a UE 70 as described in the above embodiment, and a base station 80 as described in the above embodiment.

[0277] This application provides a storage medium storing a computer program that, when executed by a processor, implements the methods described in the above embodiments.

[0278] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) that include computer-usable program code.

[0279] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0280] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0281] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0282] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A data transmission method, characterized in that, include: Obtain the mapping relationship between the configuration of multiple Physical Uplink Shared Channels (PUSCH) resources and the configuration of multiple random access preamble sequences from the base station; For random access preamble transmission and PUSCH transmission, based on the payload size range of the PUSCH transmission, a random access preamble group index is determined among multiple random access preamble group indices. The multiple random access preamble group indices are used to indicate the random access preamble sequence configuration among multiple random access preamble sequence configurations for random access preamble transmission. Based on the mapping relationship and the determined random access preamble group index, the PUSCH resource configuration among the multiple PUSCH resource configurations is determined. Different PUSCH payload size ranges of PUSCH transmission correspond to different random access preamble group indices. The random access preamble sequence associated with the random access preamble group index is determined based on at least one of the following corresponding to the PUSCH resource configuration among the plurality of PUSCH resource configurations: demodulation reference signal DMRS port index, resource block RB index, number of time slots, and time domain position offset of the PUSCH resource. Map the determined random access preamble sequence to physical random access channel (PRACH) resources; Send messages and transmit PUSCH data through the PRACH resource.

2. The method according to claim 1, characterized in that, The PUSCH resource configuration includes the payload size of the PUSCH transmission.

3. A data transmission method, characterized in that, include: Send to User Equipment (UE) the mapping relationship between multiple Physical Uplink Shared Channel (PUSCH) resource configurations and multiple Random Access Preamble Sequence configurations; The random access preamble is received from the UE via the Physical Random Access Channel (PRACH) resource. The random access preamble sequence configuration of PRACH resources is obtained from the random access preamble, wherein the random access preamble sequence configuration indicates a random access preamble index and a random access preamble group index, the random access preamble index and the random access preamble group index also indicate a PUSCH resource configuration among a plurality of PUSCH resource configurations for PUSCH transmission based on the mapping relationship, the PUSCH transmission being associated with the random access preamble, the random access preamble group index also indicating the payload size range of the PUSCH transmission, wherein different random access preamble group indices correspond to different PUSCH payload size ranges, and the random access preamble index is determined in the random access preamble index within the random access preamble group index according to at least one of the following corresponding to the PUSCH resource configuration among the plurality of PUSCH resource configurations: demodulation reference signal DMRS port index, resource block RB index, number of time slots, and time domain position offset of the PUSCH resource; and The PUSCH transmission is received according to the PUSCH resource.

4. The method according to claim 3, characterized in that, The PUSCH resource configuration information includes the payload size range of the PUSCH transmission.

5. A user equipment for data transmission, comprising a processor and a memory, wherein, The memory is used to store instructions; and The processor is configured to read the instructions to execute: Obtain the mapping relationship between the configuration of multiple Physical Uplink Shared Channels (PUSCH) resources and the configuration of multiple random access preamble sequences from the base station; For random access preamble transmission and PUSCH transmission, based on the payload size range of the PUSCH transmission, a random access preamble group index is determined among multiple random access preamble group indices. The multiple random access preamble group indices are used to indicate the random access preamble sequence configuration among multiple random access preamble sequence configurations for random access preamble transmission. Based on the mapping relationship and the determined random access preamble group index, the PUSCH resource configuration among the multiple PUSCH resource configurations is determined. Different PUSCH payload size ranges of PUSCH transmission correspond to different random access preamble group indices. The random access preamble sequence associated with the random access preamble group index is determined based on at least one of the following corresponding to the PUSCH resource configuration among the plurality of PUSCH resource configurations: demodulation reference signal DMRS port index, resource block RB index, number of time slots, and time domain position offset of the PUSCH resource. Map the determined random access preamble sequence to physical random access channel (PRACH) resources; Send messages and transmit PUSCH data through the PRACH resource.

6. The user equipment according to claim 5, characterized in that, The PUSCH resource configuration includes the payload size range of the PUSCH transmission.

7. A base station for data transmission, characterized in that, The base station includes: a processor and a memory, wherein The memory is used to store instructions; and The processor is configured to read the instructions for execution: Send to User Equipment (UE) the mapping relationship between multiple Physical Uplink Shared Channel (PUSCH) resource configurations and multiple Random Access Preamble Sequence configurations; The random access preamble is received from the UE via the Physical Random Access Channel (PRACH) resource. The random access preamble sequence configuration of PRACH resources is obtained from the random access preamble, wherein the random access preamble sequence configuration indicates a random access preamble index and a random access preamble group index, the random access preamble index and the random access preamble group index also indicate a PUSCH resource configuration among a plurality of PUSCH resource configurations for PUSCH transmission based on the mapping relationship, the PUSCH transmission being associated with the random access preamble, the random access preamble group index also indicating the payload size range of the PUSCH transmission, wherein different random access preamble group indices correspond to different PUSCH payload size ranges, and the random access preamble index is determined in the random access preamble index within the random access preamble group index according to at least one of the following corresponding to the PUSCH resource configuration among the plurality of PUSCH resource configurations: demodulation reference signal DMRS port index, resource block RB index, number of time slots, and time domain position offset of the PUSCH resource; and The PUSCH transmission is received according to the PUSCH resource.

8. The base station according to claim 7, characterized in that, The PUSCH resource configuration includes the payload size range of the PUSCH transmission.

9. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-4.

Images