WO2020182152A1 - 数据传输方法、装置、用户设备、基站、通信系统及存储介质 - Google Patents

数据传输方法、装置、用户设备、基站、通信系统及存储介质 Download PDF

Info

Publication number
WO2020182152A1
WO2020182152A1 PCT/CN2020/078802 CN2020078802W WO2020182152A1 WO 2020182152 A1 WO2020182152 A1 WO 2020182152A1 CN 2020078802 W CN2020078802 W CN 2020078802W WO 2020182152 A1 WO2020182152 A1 WO 2020182152A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
preamble sequence
pusch
pusch resource
configuration information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/078802
Other languages
English (en)
French (fr)
Inventor
胡宇洲
袁志锋
田力
张峻峰
戴建强
李卫敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to KR1020217029458A priority Critical patent/KR102899490B1/ko
Priority to EP20769058.7A priority patent/EP3941125A4/en
Publication of WO2020182152A1 publication Critical patent/WO2020182152A1/zh
Priority to US17/472,283 priority patent/US12414108B2/en
Anticipated expiration legal-status Critical
Priority to US19/322,353 priority patent/US20260006608A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/18—Phase-modulated carrier systems, i.e. using phase-shift keying
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/26025—Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2626—Arrangements specific to the transmitter only
    • H04L27/2627—Modulators
    • H04L27/2634—Inverse fast Fourier transform [IFFT] or inverse discrete Fourier transform [IDFT] modulators in combination with other circuits for modulation
    • H04L27/2636—Inverse fast Fourier transform [IFFT] or inverse discrete Fourier transform [IDFT] modulators in combination with other circuits for modulation with FFT or DFT modulators, e.g. standard single-carrier frequency-division multiple access [SC-FDMA] transmitter or DFT spread orthogonal frequency division multiplexing [DFT-SOFDM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0836—Random access procedures, e.g. with 4-step access with 2-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access

Definitions

  • This application relates to the field of communications, such as data transmission methods, devices, user equipment, base stations, communication systems, and storage media.
  • the random access A message (msgA) or data packet message will be in the physical random access channel (PRACH, Physical Random Access Channel) resource And Physical Uplink Shared Channel (PUSCH, Physical Uplink Shared Channel) resources.
  • the user equipment UE, User Equipment
  • the PUSCH resource at least carries a UE identification (ID, Identification), and the size of this identification information may be 56 bits (bit), 72 bits, 144 bits, or 208 bits.
  • the payload size (Payload Size) of the above message may also be greater than 208 bits. Different Payload Size may correspond to different resource configurations of PUSCH resources.
  • the UE cannot select corresponding preamble sequence configuration information to map the preamble sequence according to the resource configuration of its own PUSCH resource.
  • the embodiment of the application provides a data transmission method, including:
  • the resource configuration of the PUSCH resource search for 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;
  • the embodiment of the application provides a data transmission method, including:
  • preamble sequence configuration information search for a pre-saved mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information;
  • An embodiment of the present application provides a data transmission device, including:
  • the first searching module is configured to search for 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;
  • a mapping module configured to map the preamble sequence to the PRACH resource according to the preamble sequence configuration information
  • the first sending module is configured to send a message including the PRACH resource and PUSCH resource.
  • An embodiment of the present application provides a data transmission device, including:
  • the second receiving module is configured to receive a message including PRACH resources and PUSCH resources;
  • the first obtaining module is configured to obtain the preamble sequence configuration information of the PRACH resource in the message
  • the second searching module is configured to search for the pre-saved mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information according to the preamble sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information;
  • the second acquiring module is configured to acquire the information in the PUSCH resource according to the resource configuration mode.
  • the embodiment of the present application provides a UE for data transmission.
  • the UE includes a processor and a storage device;
  • the storage device is used to store one or more programs
  • the processor When the one or more programs are executed by the one or more processors, the processor is caused to implement any implementation manner in the foregoing first data transmission method.
  • An embodiment of the present application also provides a base station for data transmission, where the base station includes a processor and a storage device;
  • the storage device is used to store one or more programs
  • the processor When the one or more programs are executed by the one or more processors, the processor is caused to implement any implementation manner in the foregoing second data transmission method.
  • the embodiment of the present application provides a communication system, and the system includes the UE in the embodiment of the present application and the base station in the embodiment of the present application.
  • An embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.
  • the corresponding preamble sequence configuration information can be selected according to the resource configuration of its own PUSCH resource, and the preamble sequence configuration information is used to map the preamble sequence to the PRACH resource, thereby facilitating the UE
  • the transmission resource is selected according to the resource configuration of the PUSCH resource. Further, it is convenient to simplify the reception of the message by the base station.
  • FIG. 1 is a schematic diagram of the implementation process of a data transmission method according to an embodiment of the application
  • FIG. 2 is a schematic diagram of a mapping manner of M Preamble sequences included in the RO according to an embodiment of the application;
  • FIG. 3 is a schematic diagram of the implementation process of a data transmission method according to an embodiment of the application.
  • FIG. 4 is a schematic diagram of the interaction process flow between a base station and a UE according to an embodiment of the application;
  • FIG. 5 is a schematic structural diagram of a data transmission device according to an embodiment of the application.
  • FIG. 6 is a schematic structural diagram of a data transmission device according to an embodiment of the application.
  • FIG. 7 is a schematic diagram of a UE structure for data transmission according to an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a base station for data transmission according to an embodiment of the application.
  • Fig. 9 is a schematic structural diagram of a communication system according to an embodiment of the application.
  • the fifth-generation mobile communication new air interface technology (5G NR-U, 5th-Generation New Radio in Unlicensed Spectrum) that works in unlicensed spectrum introduces a new resource mapping mode for PRACH, that is, the preamble sequence is mapped to PRACH in an interlaced manner .
  • the following table 1 shows that the transmission bandwidth is 20MHz, under different subcarrier spacing (SCS, Subcarrier Spacing), the number of different interlace blocks (indicated by M in Table 1) and the resource block of each interlace block (RB, Resource Block) possible combinations (indicated by N in Table 1).
  • the interleaved mapping modes of PRACH include but are not limited to the following:
  • Uniform PRB-level interlace mapping (Uniform PRB-level interlace mapping), non-uniform PRB-level interlace mapping (Non-uniform PRB-level interlace mapping), uniform resource element (RE, Resource Element) ) Level of interlaced mapping and no interlaced mapping (Contiguous mapping).
  • FIG. 1 is a schematic diagram of the implementation process of a data transmission method according to an embodiment of the application, including:
  • Step S11 According to the resource configuration of the PUSCH resource, search for 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.
  • Step S12 Map the preamble sequence (Preamble sequence) to the PRACH resource according to the preamble sequence configuration information.
  • Step S13 Send a message including the PRACH resource and PUSCH resource.
  • the above-mentioned PUSCH resource information includes at least one of UE ID and user plane data.
  • the foregoing message may be a random access message or a data packet message.
  • the method proposed in the embodiment of this application can be applied to the UE. Before step S11, it may further include: the UE receives the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information from the base station.
  • the foregoing Preamble sequence configuration information may include: Preamble ID, Interlace ID, and the number of RBs contained in each Interlace block occupied by the Preamble sequence (i.e., Table 1 above) At least one of N) and time-frequency location information where the preamble sequence is located.
  • the aforementioned Preamble ID may include at least one of a preamble index (Preamble Index), a preamble group index (Preamble Group Index), and a sequence number of the preamble in the preamble group.
  • Preamble Index a preamble index
  • Preamble Group Index a preamble group index
  • sequence number of the preamble in the preamble group a sequence number of the preamble in the preamble group.
  • the aforementioned Interlace ID may include at least one of an interlace index (Interlace Index), an interlace group index (Interlace Group Index), and a sequence number of the interlace block in the interlace group.
  • the UE After determining the resource configuration of the PUSCH resource, the UE can determine the preamble sequence configuration information used when mapping the preamble sequence according to the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information through the above step S11.
  • the resource configuration of the PUSCH resource includes: the demodulation reference signal (DMRS, Demodulation Reference Signal) port index (Index) corresponding to the PUSCH resource, the frequency domain resource information of the PUSCH resource, and the information of the PUSCH resource At least one of time-domain resource information, payload size of the message, waveform, SCS, and modulation and coding scheme.
  • DMRS demodulation reference signal
  • Index Demodulation Reference Signal
  • 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 with respect to the frequency domain position of the Preamble sequence.
  • the location of the frequency domain resource of the PUSCH resource may include the RB block index of the start of the frequency domain resource of the PUSCH resource, the interlace block index where the frequency domain resource of the PUSCH resource is located, and the frequency domain resource of the PUSCH resource is located At least one item of the RB block index in Interlace.
  • the time domain resource information of the PUSCH resource may include: the number of slots or mini-slots occupied by the time domain resource of the PUSCH resource, and the position of the time domain resource of the PUSCH resource relative to the preamble sequence. The offset of the domain position.
  • the position of the time domain resource of the PUSCH resource includes: the system frame number (SFN, System Frame Number) of the start of the time domain resource of the PUSCH resource, the subframe number of the start of the time domain resource of the PUSCH resource, At least one of the slot/mini-slot position of the start point of the time domain resource of the PUSCH resource and the start symbol of the time domain resource of the PUSCH resource.
  • SFN System Frame Number
  • the UE when the UE determines the resource configuration of its own PUSCH resource, it may first determine the modulation and coding scheme (MCS, Modulation and Coding Scheme) level according to its own Payload Size and channel conditions. For example, a cell center UE with a better channel condition may use some MCS levels with a higher MCS order for data transmission, and a UE with a poor channel condition may use some MCS levels with a lower MCS order for data transmission. After that, the UE determines the resource configuration of its own PUSCH resource according to the determined MCS level. For example, the size of the occupied time-frequency resources (including the number of RBs).
  • MCS modulation and coding scheme
  • the Preamble resource pool can continue to use the NR/Long Term Evolution (LTE) Preamble resource pool, or some new Preamble resource pools can be added.
  • LTE Long Term Evolution
  • Typical granularity values are 1, 2, 3, and 6 RB.
  • the UE can select the Preamble resource pool according to the reference signal received power (RSRP, Reference Signal Receiving Power) and the transport block size (TBSize, Transport Block Size).
  • RSRP reference signal received power
  • TBSize Transport Block Size
  • the Preamble resource pool with the largest RB resource granularity can be selected;
  • the Preamble resource pool with larger granularity of corresponding RB resources can be selected;
  • the Preamble resource pool corresponding to the smallest RB resource granularity can be selected.
  • the MCS level can be determined.
  • RSRP path loss
  • the size of the aforementioned Preamble resource pool may be equal.
  • the size of each Preamble resource pool can also be determined according to the possible distribution of the size of the information carried by different PUSCH resources.
  • the user's DMRS port related information such as DMRS port Index or DMRS Orthogonal Cover Code (pattern)
  • the Interlace ID is related to the Interlace ID and Preamble ID.
  • the user's DMRS port related information is related to the Preamble ID.
  • the UE may calculate the MCS level according to its Payload Size and the size of the selected time-frequency resource block. For example, if the selected time-frequency resource block is larger, the MCS order used may be lower.
  • the order of the MCS type used for modulation at least part of the Payload Size includes at least Binary Phase Shift Keying (BPSK, Binary Phase Shift Keying), pi/2 BPSK, and Quadrature Phase Shift Keying (QPSK, Quadrature Phase Shift Keying).
  • BPSK Binary Phase Shift Keying
  • QPSK Quadrature Phase Shift Keying
  • the UE After the UE determines its own resource configuration of the PUSCH resource, it can determine the preamble sequence configuration information corresponding to the resource configuration of the PUSCH resource according to a preset rule.
  • the preset rule may specifically be the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, which is issued to the UE in advance by the base station.
  • the preset rule may be based on the index of the Interlace block, the size of the number of RBs occupied by the Interlace block, the possible start or end point of the Interlace block, or the preamble sequence related information in the Interlace block.
  • the related information may include Preamble Index, Cyclic Shift (CS, Cyclic Shift) information of the Preamble sequence, the bandwidth occupied by the preamble in the Interlace block, the number of REs in the Interlace block of the preamble, and the time-frequency position of the preamble. Wait.
  • CS Cyclic Shift
  • CS Cyclic Shift
  • the MCS mode, Payload Size, and traffic model adopted by the UE can be related to the Interlace block where the user's preamble is located.
  • Information for instructions For example, the start point, the end point, the size range of the Interlace block, the Interlace Index, the Preamble Index, the cyclic shift of the preamble, or the number of RBs included in the Interlace block correspond to different PUSCH resource resource configurations.
  • InterlaceID indicates different DMRS port indexes, and different PUSCH scheduling resource granularity items supported by the system.
  • Table 2A and Table 2B are examples of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is preamble sequence configuration information, specifically Interlace Index.
  • the last six columns are the resource configuration of PUSCH resources, including DMRS port Index and PUSCH resource frequency domain resource and time domain resource information.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 2A according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the first column is preamble sequence configuration information, specifically Interlace Index.
  • the last seven columns are the resource configuration of PUSCH resources, including DMRS port Index and PUSCH resource frequency domain resource and time domain resource information.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 2B according to the resource configuration of the PUSCH resource, and determines the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the mapping relationship shown in Tables 2A and 2B can be applied to a scenario where the preamble resource is 15 kHz and the OFDM symbol uses NR Type I (Type I) 1 preloaded symbol (front loaded symbol).
  • the mapping relationship shown in Table 2A and Table 2B is mainly determined according to the DMRS port configuration of PUSCH and the size of the RB that may be occupied, that is, it is multiplexed on a resource, and it is shifted and pushed apart in the time domain and frequency domain. of.
  • the value range of DMRS port Index is an integer in the range of 1 to 4, which includes 1, 2, 3, and 4. In other implementation manners of this application, the value range of DMRS port Index may also include other ranges, for example:
  • Table 3 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically the number of resource blocks RB included in each interlace block occupied by the preamble sequence.
  • the second column is the resource configuration of PUSCH resources, specifically Waveform.
  • Waveform There are two possible values for Waveform, including Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform and Orthogonal Frequency Division Multiplexing (DFT-S) with discrete Fourier transform spread spectrum.
  • CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing
  • DFT-S Orthogonal Frequency Division Multiplexing
  • -OFDM Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 3 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the value of N is preferably a multiple of 2, 3, or 5. Therefore, for the situation where there are two types of RB numbers of 12 and 13 and two waveforms are indicated, the situation that each Interlace occupied by the Preamble sequence contains 13 RBs will be used to indicate the CP-OFDM waveform, and the preamble sequence will be used. Each occupied Interlace contains 12 RBs to indicate the DFT-S-OFDM waveform.
  • Table 4 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically the number of resource blocks RB included in each interlace block occupied by the preamble sequence.
  • the second column is the resource configuration of PUSCH resources, specifically Payload Size.
  • Payload Size there are two possible values of Payload Size, including 56 bits and 72 bits.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 4 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Table 5A is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Index.
  • the second column is the resource configuration of PUSCH resources, specifically Waveform.
  • Waveform There are two possible values for Waveform, including CP-OFDM waveform and DFT-S-OFDM waveform.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 5A according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Interlace Index is greater than 2 items, in Table 5A, some possible values of Interlace Index can be selected to correspond to the CP-OFDM waveform, and other values are used to correspond to the DFT-S-OFDM waveform.
  • K is an integer greater than 1 and less than M-1.
  • the example in Table 5 is only an example.
  • the Interlace Index corresponding to a Waveform may be discontinuous.
  • Table 5B is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically Waveform.
  • Waveform There are two possible values for Waveform, including CP-OFDM waveform and DFT-S-OFDM waveform.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 5B according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Table 6A is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Index.
  • the second column is the resource configuration of PUSCH resources, specifically Payload Size.
  • Payload Size there are two possible values for Payload Size, including 56 bits and 72 bits.
  • the UE After the UE determines the resource configuration of its own PUSCH resource, it searches for the mapping relationship shown in Table 6A according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Interlace Index Since the value of Interlace Index is greater than 2 items, in Table 6A, some possible values of Interlace Index can be selected to correspond to 56 bits, and other values correspond to 72 bits.
  • Q is an integer greater than 1 and less than M-1.
  • the example in Table 6A is only an example.
  • the Interlace Index corresponding to a Payload Size may be discontinuous.
  • the Payload Size can also have values such as 144bits, 208bits, etc.
  • the implementation of this application can adopt a similar method, using different values of Interlace Index to correspond to 4 or more values of PayloadSize.
  • Table 6B is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically Payload Size.
  • Payload Size there are two possible values of Payload Size, including 56 bits and 72 bits.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 6B according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the embodiments of the present application may also indicate different situations of combinations of Waveform and Payload Size. As shown in Table 7A below.
  • Table 7A is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Index.
  • the second column is the resource configuration of PUSCH resources, specifically the combination of Waveform and Payload Size.
  • the UE After the UE determines the resource configuration of its own PUSCH resource, it searches for the mapping relationship shown in Table 7A according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Table 7A there are 4 possible values for the combination of Waveform and Payload Size.
  • G, L, T are integers greater than 1 and less than M-1, and G ⁇ L ⁇ T.
  • the three integers of G, L, and T divide the possible values of Interlace Index into 4 parts, and each part corresponds to a possible value of the combination of Waveform and Payload Size.
  • the example in Table 7A is only an example.
  • the Interlace Index corresponding to a combination of Waveform and Payload Size may be discontinuous.
  • 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 embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically the combination of Waveform and Payload Size.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 7B according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Interlace Group Index Waveform and Payload Size 1 CP-OFDM and 56bits 2 DFT-S-OFDM and 72bits 3 CP-OFDM and 72bits 4 DFT-S-OFDM and 56bits
  • 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 embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Index.
  • the second column is the resource configuration of PUSCH resources, specifically SCS. There are 3 possible values of SCS, including 15kHz, 15kHz and 60kHz.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 8A according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the Interlace Index corresponding to a type of SCS may be discontinuous.
  • Table 8B is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically SCS. There are 3 possible values of SCS, including 15kHz, 15kHz and 60kHz.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 8B according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • SCS may also have other possibilities, for example, including 15kHz, 30kHz, 60kHz and 120kHz.
  • Table 9A is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Index.
  • the second column is the resource configuration of PUSCH resources, specifically SCS. There are 4 possible values of SCS, including 15kHz, 30kHz, 60kHz and 120kHz.
  • the Interlace Index corresponding to a type of SCS may be discontinuous.
  • Table 9B is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the first column is the preamble sequence configuration information, specifically Interlace Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically SCS. There are 4 possible values of SCS, including 15kHz, 30kHz, 60kHz and 120kHz.
  • the embodiment of the present application may use the Preamble Group ID to implement the mapping with the resource configuration of the PUSCH resource.
  • the following Table 10 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaving pattern.
  • the first column is preamble sequence configuration information, specifically Preamble Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically Waveform. There are two possible values for Waveform, including CP-OFDM waveform and DFT-S-OFDM waveform.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 10 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • sequence numbers of the Preamble sequence in a Preamble Group may not be continuous.
  • Table 11 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaved block.
  • the first column is preamble sequence configuration information, specifically Preamble Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically Payload Size. There are two possible values of Payload Size, including 56bits and 72bits.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 11 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Table 12 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application in the absence of interleaved blocks.
  • the first column is preamble sequence configuration information, specifically Preamble Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically the combination of Waveform and Payload Size.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 12 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Preamble Group Index Waveform and Payload Size 1 CP-OFDM and 56bits 2 DFT-S-OFDM and 72bits 3 CP-OFDM and 72bits 4 DFT-S-OFDM and 56bits
  • sequence numbers of the Preamble sequence in a Preamble Group may not be continuous.
  • the possible values of Payload Size are 56 bits and 72 bits.
  • the implementation manner of this application may also indicate the cases where the possible values of Payload Size are 56 bits, 72 bits, 144 bits, and 208 bits.
  • the following Table 13 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaved block.
  • the first column is preamble sequence configuration information, specifically Preamble Group Index.
  • the second column is the resource configuration of PUSCH resources, specifically Payload Size.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE searches for the mapping relationship shown in Table 13 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • Preamble Group Index Payload Size 1 56bits 2 72bits 3 144bits 4 208bits
  • sequence numbers of the Preamble sequence in a Preamble Group may not be continuous.
  • Preamble Group Index is taken as an example for example.
  • Preamble Group Index is a possible case of preamble sequence identifier (Preamble ID).
  • the embodiment of the present application may also adopt other implementation manners, for example, a preamble sequence index (Preamble Index) instead of the Preamble Group Index in the foregoing mapping relationship table, as shown in Table 10B to Table 13B.
  • the sequence number of the preamble in the preamble group is used to replace the Preamble Group Index in the foregoing mapping relationship table, as shown in Tables 10C to 13C.
  • Preamble Index Waveform and Payload Size 1 ⁇ J CP-OFDM and 56bits J+1 ⁇ D DFT-S-OFDM and 72bits D+1 ⁇ E CP-OFDM and 72bits E+1 ⁇ F DFT-S-OFDM and 56bits
  • Preamble Index Payload Size 1 ⁇ S 56bits S+1 ⁇ H 72bits H+1 ⁇ I 144bits I+1 ⁇ R 208bits
  • Preamble in the preamble group Waveform and Payload Size 1 ⁇ CP-OFDM and 56bits 1 ⁇ DFT-S-OFDM and 72bits 1 ⁇ CP-OFDM and 72bits 1 ⁇ DFT-S-OFDM and 56bits
  • Preamble in the preamble group Payload Size 1 ⁇ 56bits 1 ⁇ 72bits 1 ⁇ 144bits 1 ⁇ 208bits
  • the resource configuration of the aforementioned PUSCH resource may also include a modulation and coding scheme.
  • the modulation and coding method may include at least one of BPSK modulation, pi/2-BPSK modulation, and QPSK modulation.
  • Table 13D and Table 13E are examples of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaved block.
  • the first column is the preamble sequence configuration information, specifically the sequence number of the preamble in the preamble group.
  • the second column is the resource configuration of PUSCH resources, specifically a combination of MCS index (MSC Index) and PayloadSize.
  • MCS Index MCS Index
  • PayloadSize the resource configuration of PUSCH resources, specifically a combination of MCS index (MSC Index) and PayloadSize.
  • MSC Index has two values, which can represent two modulation and coding methods.
  • sequence number of the preamble in the preamble group MCS Index&payload size 1 ⁇ 0&56bits 1 ⁇ 1&56bits 1 ⁇ 0&72bits 1 ⁇ 1&72 bits
  • the first column is the preamble sequence configuration information, specifically the preamble sequence number.
  • the second column is the resource configuration of PUSCH resources, specifically the combination of MSC Index and Payload Size.
  • the MSC Index has two values, which can represent two modulation and coding methods.
  • the following Table 14 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application under different interleaving modes.
  • the Preamble Index and Interlace Index may be used to jointly indicate the resource configuration of PUSCH resources.
  • the first column and the second column are preamble sequence configuration information, including Interlace Index and Preamble Index.
  • the last five columns are the resource configuration of PUSCH resources, including DMRS port Index and PUSCH resource frequency domain resource and time domain resource information.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 14 according to the resource configuration of the PUSCH resource, and determines the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the interlace block ID is specifically Interlace Index
  • the Preamble ID is specifically Preamble Index as an example for description.
  • the interlace block ID may also be an Interlace Group Index or the sequence number of the interlace block in the interlaced block group
  • the Preamble ID may also be the Preamble Group Index or the sequence number of the preamble in the preamble group.
  • the Preamble Index can be used to map the resource configuration of PUSCH resources and the preamble sequence configuration information.
  • the position or ID of the RO can be combined with the Preamble Index to map the resource configuration of PUSCH resources and the preamble sequence configuration information.
  • Table 15 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaved block.
  • the first column is preamble sequence configuration information, specifically Preamble Index.
  • the last five columns are the resource configuration of PUSCH resources, including DMRS port Index and PUSCH resource frequency domain resource and time domain resource information.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 15 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the specific value of the sixth column "the offset of the position of the time domain resource of the PUSCH resource with respect to the time domain position of the Preamble sequence" is a possible implementation manner.
  • the numbers in the 6th column of Table 15 can be other values, that is, the number 1 in the 6th column can be replaced with t1, and the number 2 in the 6th column can be replaced with t2, ... in the 6th column
  • the number 6 can be replaced with t6.
  • t1, t2, t3, t4, t5 and t6 are all integers.
  • Table 16 is an example of the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in the embodiment of the present application when there is no interleaved block.
  • the first column and the second column are preamble sequence configuration information, specifically RO ID and Preamble Index.
  • the last five columns are the resource configuration of PUSCH resources, including DMRS port Index and PUSCH resource frequency domain resource and time domain resource information.
  • the UE After determining the resource configuration of its own PUSCH resource, the UE looks up the mapping relationship shown in Table 16 according to the resource configuration of the PUSCH resource to determine the corresponding preamble sequence configuration information. Then, the preamble sequence is mapped according to the preamble sequence configuration information.
  • the specific value of the seventh column "the offset of the position of the time domain resource of the PUSCH resource with respect to the time domain position of the Preamble sequence" is a possible implementation manner.
  • the number in the seventh column of Table 16 can be other values, that is, the number 1 in the seventh column can be replaced by t1, and the number 2 in the sixth column can be replaced by t2.
  • t1 and t2 are both integers.
  • the number of Preamble sequences available for one RO is 13 as an example.
  • the above table uses all available Preamble sequences of one RO, any three Preamble sequences and Preamble Index of the second RO to jointly indicate the resource configuration of PUSCH resources.
  • FIG. 2 is a schematic diagram of a mapping manner of M Preamble sequences included in the RO according to an embodiment of the application.
  • RO includes M Preamble sequences, which are respectively P 1 , P 2 , ... P M.
  • P 1 , P 2 , ... PM are mapped to different positions respectively.
  • P number of RB occupied by a 1 the corresponding DMRS Port Index is K; the number of RB P 2 occupied is 2, the corresponding DMRS Port Index is m; the number of RB P M occupied 6, the corresponding DMRS Port Index of g .
  • the position of the frequency domain resource of the PUSCH resource includes at least one of the RB block index of the start 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: the system frame number (SFN, System Frame Number) of the starting point of the PUSCH time domain resource, the subframe number of the starting point of the PUSCH time domain resource, and the time slot or micro-frame of the starting point of the PUSCH time domain resource At least one of slot position and PUSCH start symbol.
  • mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information are introduced above, and the mapping relationship in the embodiment of the present application is not limited to the above form. 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 of PUSCH resources Granularity, the time-frequency resources occupied by users can be a multiple of this granularity.
  • the UE can determine the preamble sequence configuration information corresponding to the resource configuration of its own PUSCH resource, so as to realize the selection of transmission resources.
  • FIG. 3 is a schematic diagram of the implementation process of a data transmission method according to an embodiment of the application, including:
  • S31 Receive a message including physical random access channel PRACH resources and physical uplink shared channel PUSCH resources.
  • S33 According to the preamble sequence configuration information, search for a pre-saved mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, and determine the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information.
  • the above-mentioned PUSCH resource information includes at least one of UE ID and user plane data.
  • the foregoing message may be a random access message or a data packet message.
  • the method proposed in the embodiment of this application can be applied to a base station.
  • the method 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 mapping relationship between the resource configuration of the PUSCH resource and the mapping relationship. news.
  • mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information has been introduced in the foregoing embodiment, and will not be repeated here.
  • Figure 4 is a schematic diagram of the interaction process flow between the base station and the UE according to the embodiment of the application, including:
  • the base station issues the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information to the UE.
  • the UE searches for the mapping relationship according to the resource configuration of its own PUSCH resource, and determines corresponding preamble sequence configuration information.
  • the Preamble sequence is mapped to the PRACH resource according to the determined preamble sequence configuration information.
  • the UE sends a message including PRACH resources and PUSCH resources to the base station.
  • the base station receives the message, and obtains the preamble sequence configuration information of the PRACH resource in the message. According to the preamble sequence configuration information, search the pre-saved mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information, and determine the resource configuration mode of the corresponding PUSCH resource. Obtain the information in the PUSCH resource according to the resource configuration mode.
  • Fig. 5 is a schematic diagram of the structure of the data transmission device according to the embodiment of the application.
  • the mapping relationship with the preamble sequence configuration information is to determine the preamble sequence configuration information corresponding to the resource configuration;
  • the mapping module 502 is configured to map the preamble sequence to the PRACH resource according to the preamble sequence configuration information;
  • the first sending module 503 is configured to send a message including the PRACH resource and PUSCH resource.
  • the information in the PUSCH resource includes at least one of the UE ID and user plane data.
  • the foregoing apparatus may further include: a first receiving module 504, configured to receive a mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information from the base station.
  • This embodiment can be applied to UE.
  • the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in this embodiment is the same as the content introduced in the foregoing embodiment, and will not be repeated here.
  • FIG. 6 is a schematic structural diagram of a data transmission device according to an embodiment of the application, including: a second receiving module 601, configured to receive a message including PRACH resources and PUSCH resources; An obtaining module 602 is used to obtain the preamble sequence configuration information of the PRACH resource in the message; the second search module 603 is used to search for the resource configuration and preamble sequence configuration of the PUSCH resource stored in advance according to the preamble sequence configuration information The information mapping relationship determines the resource configuration mode of the PUSCH resource corresponding to the preamble sequence configuration information; the second obtaining module 604 is configured to obtain the information in the PUSCH resource according to the resource configuration mode.
  • the information in the PUSCH resource includes at least one of UE ID and user plane data.
  • the above-mentioned apparatus may further include: a second sending module 605, configured 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 can use its own PUSCH resource The resource configuration and the mapping relationship send the message.
  • a second sending module 605 configured 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 can use its own PUSCH resource The resource configuration and the mapping relationship send the message.
  • This embodiment can be applied to a base station.
  • the mapping relationship between the resource configuration of the PUSCH resource and the preamble sequence configuration information in this embodiment is the same as the content introduced in the foregoing embodiment, and will not be repeated here.
  • FIG. 7 is a schematic structural diagram of a UE for data transmission according to an embodiment of the application.
  • the UE 70 provided in the embodiment of the application includes a memory 703 and a processor 704.
  • the UE 70 may also include an interface 701 and a bus 702.
  • the interface 701, the memory 703, and the processor 704 are connected through a bus 702.
  • the memory 703 is used to store instructions.
  • the processor 704 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to the UE.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • FIG. 8 is a schematic diagram of the structure of a base station for data transmission according to an embodiment of this application.
  • the base station 80 may also include an interface 801 and a bus 802.
  • the interface 801, the memory 803, and the processor 804 are connected through a bus 802.
  • the memory 803 is used to store instructions.
  • the processor 804 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to the base station.
  • the implementation principles and technical effects are similar, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of a communication system according to an embodiment of the application. As shown in FIG. 9, the system includes: a UE 70 as in the foregoing embodiment and a base station 80 in the foregoing embodiment.
  • the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method in the foregoing embodiment is implemented.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of hardware embodiments, software embodiments, or embodiments combining software and hardware. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Discrete Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提出数据传输方法、装置、用户设备、基站、通信系统及存储介质，所述方法包括：根据物理上行共享信道(PUSCH)资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述PUSCH资源的资源配置对应的前导序列配置信息；根据所述前导序列配置信息将前导序列映射到物理随机接入信道(PRACH)资源；发送包含所述PRACH资源及PUSCH资源的消息。

Description

数据传输方法、装置、用户设备、基站、通信系统及存储介质
本申请要求在2019年03月13日提交中国专利局、申请号为201910190286.7的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如涉及数据传输方法、装置、用户设备、基站、通信系统及存储介质。
背景技术
在2步随机接入(2-step RACH)或者非连接态数据传输过程中，随机接入A消息(msgA)或数据小包的消息会在物理随机接入信道(PRACH，Physical Random Access Channel)资源和物理共享信道(PUSCH，Physical Uplink Shared Channel)资源中传输。其中，用户设备(UE，User Equipment)将前导(Preamble)序列根据不同的前导序列配置信息映射到PRACH资源上。PUSCH资源至少会携带UE标识(ID，Identification)，这一标识信息的大小可能取值为56比特(bit)、72bits、144bits或者208bits。根据UE所处的状态及触发事件的不同，上述消息的载荷大小(Payload Size)还可能会大于208bits。不同的Payload Size可能对应不同的PUSCH资源的资源配置。在相关技术中，UE无法根据自身的PUSCH资源的资源配置选择对应的前导序列配置信息对前导序列进行映射。
发明内容
为了解决上述至少一个技术问题，本申请实施例提供了以下方案。
本申请实施例提供了一种数据传输方法，包括：
根据PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述资源配置对应的前导序列配置信息；
根据所述前导序列配置信息将前导序列映射到PRACH资源；
发送包含所述PRACH资源及PUSCH资源的消息。
本申请实施例提供了一种数据传输方法，包括：
接收包含PRACH资源及PUSCH资源的消息；
获取所述消息中的PRACH资源的前导序列配置信息；
根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式；
根据所述资源配置模式获取所述PUSCH资源中的信息。
本申请实施例提供了一种数据传输装置，包括：
第一查找模块，用于根据PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述资源配置对应的前导序列配置信息；
映射模块，用于根据所述前导序列配置信息将前导序列映射到PRACH资源；
第一发送模块，用于发送包含所述PRACH资源及PUSCH资源的消息。
本申请实施例提供了一种数据传输装置，包括：
第二接收模块，用于接收包含PRACH资源及PUSCH资源的消息；
第一获取模块，用于获取所述消息中的PRACH资源的前导序列配置信息；
第二查找模块，用于根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式；
第二获取模块，用于根据所述资源配置模式获取所述PUSCH资源中的信息。
本申请实施例提供了一种数据传输的UE，所述UE包括：处理器及存储装置；
所述存储装置，用于存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行时，使得所述处理器实现如上述第一种数据传输方法中的任意实施方式。
本申请实施例还提供了一种数据传输的基站，所述基站包括：处理器及存储装置；
所述存储装置，用于存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行时，使得所述处理器实现如上述第二种数据传输方法中的任意实施方式。
本申请实施例提供了一种通信系统，所述系统包括本申请实施例中的UE及本申请实施例中的基站。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中的任意一种方法。
本申请实施例所提供的数据传输方法，在发送消息之前，可以根据自身的PUSCH资源的资源配置选择对应的前导序列配置信息，采用该前导序列配置信息将前导序列映射到PRACH资源，因此便于UE根据PUSCH资源的资源配置对传输资源进行选择。进一步地，便于简化基站对该消息的接收。
附图说明
图1为本申请实施例的一种数据传输方法实现流程示意图；
图2为本申请实施例RO中包含的M个Preamble序列的映射方式示意图；
图3为本申请实施例的一种数据传输方法实现流程示意图；
图4为本申请实施例基站与UE的交互过程流程示意图；
图5为本申请实施例的一种数据传输装置结构示意图；
图6为本申请实施例的一种数据传输装置结构示意图；
图7为本申请实施例的数据传输的UE结构示意图；
图8为本申请实施例的数据传输的基站结构示意图；
图9为本申请实施例的通信系统结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
工作于非授权频谱的第五代移动通信新空口技术(5G NR-U，5th-Generation New Radio in Unlicensed Spectrum)对PRACH引入了新的资源映射模式，即将Preamble序列以交错的形式映射到PRACH上。下表1给出了发射带宽是20MHz，在不同的子载波间隔(SCS，Subcarrier Spacing)下，不同的交错(Interlace)块 数目(表1中用M表示)和每个交错块的资源块(RB，Resource Block)数目(表1中用N表示)的可能组合。
表1
Figure PCTCN2020078802-appb-000001
PRACH的交错映射模式包括但不限于以下几种：
均匀物理资源块(PRB，Physical Resource Block)级别的交错映射(Uniform PRB-level interlace mapping)、非均匀PRB级别的交错映射(Non-uniform PRB-level interlace mapping)、均匀资源元素(RE，Resource Element)级别的交错映射以及不做交错映射(Contiguous mapping)。
针对不同的PRACH交错映射模式，本申请实施例提出一种数据传输方法，如图1为本申请实施例的一种数据传输方法实现流程示意图，包括：
步骤S11：根据PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述资源配置对应的前导序列配置信息。
步骤S12：根据所述前导序列配置信息将前导序列(Preamble序列)映射到PRACH资源。
步骤S13：发送包含所述PRACH资源及PUSCH资源的消息。
在一种实施方式中，上述PUSCH资源的信息中至少包括UE ID和用户面数据中的至少一项。上述消息可以为随机接入消息或数据小包消息。
本申请实施例提出的方法可以应用于UE。在上述步骤S11之前，可以进一步包括：UE接收来自基站的所述PUSCH资源的资源配置与前导序列配置信息的映射关系。
在一种实施方式中，上述Preamble序列配置信息可以包括：前导标识(Preamble ID)、交错块标识(Interlace ID)、Preamble序列所占据的每个Interlace块中包含的RB个数(即上述表1中的N)及前导序列所在的时频位置信息中的至少一项。
在一种实施方式中，上述Preamble ID可以包括：前导索引(Preamble Index)、前导组索引(Preamble Group Index)及前导在前导组内的序号中的至少一项。
在一种实施方式中，上述Interlace ID可以包括：交错块索引(Interlace Index)、交错块组索引(Interlace Group Index)及交错块在交错块组内的序号中的至少一项。
UE在确定PUSCH资源的资源配置之后，通过上述步骤S11，根据PUSCH资源的资源配置与前导序列配置信息的映射关系，可以确定出将Preamble序列进行映射时采用的前导序列配置信息。
在一种实施方式中，上述PUSCH资源的资源配置包括：PUSCH资源对应的解调参考信号(DMRS，Demodulation Reference Signal)端口(port)索引(Index)、PUSCH资源的频域资源信息、PUSCH资源的时域资源信息、消息的Payload Size、波形(Waveform)、SCS及调制编码方式中的至少一项。
其中，PUSCH资源的频域资源信息可以包括：PUSCH资源的频域资源所占据的RB个数、以及PUSCH资源的频域资源的位置相对于Preamble序列频域 位置的偏移。
在一种实施方式中，PUSCH资源的频域资源的位置可以包括PUSCH资源的频域资源的起点的RB块索引、PUSCH资源的频域资源所处的交错块索引及PUSCH资源的频域资源位于Interlace中的RB块索引中的至少一项。
PUSCH资源的时域资源信息可以包括：PUSCH资源的时域资源所占据的时隙(slot)或微时隙(mini-slot)个数、以及PUSCH资源的时域资源的位置相对于Preamble序列时域位置的偏移。
在一种实施方式中，PUSCH资源的时域资源的位置包括：PUSCH资源的时域资源的起点的系统帧号(SFN，System Frame Number)、PUSCH资源的时域资源的起点的子帧号、PUSCH资源的时域资源的起点的slot/mini-slot位置及PUSCH资源的时域资源的起始符号中的至少一项。
在一种实施方式中，UE在确定自身的PUSCH资源的资源配置时，可以首先根据自己的Payload Size和信道情况，确定调制与编码方式(MCS，Modulation and Coding Scheme)级别。例如，信道情况较好的小区中心UE可以采用MCS阶数较高的某些MCS级别进行数据传输，信道情况较差的UE可以采用MCS阶数较低的某些MCS级别进行数据传输。之后，UE再根据确定的MCS级别确定自身的PUSCH资源的资源配置。例如，占据的时频资源的大小(包括RB的数目)。
对于2-step RACH PUSCH RB资源块的配置，可以采用不同的颗粒度来对用户进行配置，并与不同组的Preamble资源池进行映射。其中，Preamble资源池可以沿用NR/长期演进(LTE，Long Term Evolution)的Preamble资源池，也可以增加一些新的Preamble资源池。典型的颗粒度取值为1、2、3和6 RB。
UE可以根据参考信号接收功率(RSRP，Reference Signal Receiving Power)及传输块大小(TBSize，Transport Block Size)选取Preamble资源池。
具体地，如果RSRP大于或等于RSRP的阈值(RSRP0)，并且TBSize大于或等于TBSize的阈值(TBSize0)，可以选取对应的RB资源颗粒度最大的Preamble资源池；
如果RSRP与TBSize中的任意一个大于或等于相应的阈值，则可以选取对 应RB资源颗粒度较大的Preamble资源池；
如果RSRP小于或等于RSRP的阈值(RSRP0)，并且TBSize小于或等于TBSize的阈值(TBSize0)，可以选取对应RB资源颗粒度最小的Preamble资源池。
确定了Preamble资源池及相应的RB资源颗粒度，则可以确定MCS级别。
此外，上述RSRP也可以替换为路径损失(pathloss)。
上述的Preamble资源池的大小可能相等。也可以根据不同的PUSCH资源携带信息大小的可能分布，来决定每个Preamble资源池的大小。
对于存在Interlace的资源配置场景，用户的DMRS port相关信息，例如DMRS port Index或DMRS正交覆盖码(OCC，Orthogonal Cover Code)模式(pattern)，与Interlace ID和Preamble ID有关。对于不存在Interlace的资源配置场景，用户的DMRS port相关信息，例如DMRS port Index或DMRS OCCpattern，与Preamble ID有关。
或者，UE可以根据自己的Payload Size和选定的时频资源块的大小计算MCS级别。比如，如果选定的时频资源块较大，则采用的MCS阶数可能会更低。Payload Size的至少一部分被调制所采用的MCS类型阶数至少包括二进制相移键控(BPSK，Binary Phase Shift Keying)、pi/2 BPSK及正交相移键控(QPSK，Quadrature Phase Shift Keying)。
UE确定出自身的上述PUSCH资源的资源配置后，根据预设的规则可以确定出该PUSCH资源的资源配置对应的前导序列配置信息。该预设的规则具体可以为PUSCH资源的资源配置与前导序列配置信息的映射关系，由基站预先下发给UE。预设的规则可能是基于Interlace块的索引、Interlace块所占据的RB数目的大小、Interlace块的可能的起点或者终点、或者Interlace块中的前导序列相关信息。其中，该相关信息可以包括Preamble Index、Preamble序列的循环移位(CS，Cyclic Shift)信息、前导在Interlace块中所占据的带宽大小、前导在Interlace块中的RE数目、前导所在的时频位置等。
针对PRACH映射存在非均匀PRB级的交错模式(pattern)的情况，对于不同的交错模式，UE采用的MCS模式、Payload Size和传输模型(traffic model)等, 可以通过用户的前导所在的Interlace块相关的信息进行指示。例如Interlace块的起点、终点、大小范围、Interlace Index、Preamble Index、前导的循环移位或者Interlace块包含RB的数目大小对应不同的PUSCH资源的资源配置。InterlaceID指示不同的DMRS port索引，系统支持的不同PUSCH调度的资源颗粒度项。
如下表2A和表2B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
在表2A中，第一列为前导序列配置信息，具体为Interlace Index。后六列为PUSCH资源的资源配置，包括DMRS port Index以及PUSCH资源的频域资源和时域资源信息。UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表2A所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表2A
Figure PCTCN2020078802-appb-000002
Figure PCTCN2020078802-appb-000003
在表2B中，第一列为前导序列配置信息，具体为Interlace Index。后七列为 PUSCH资源的资源配置，包括DMRS port Index 以及PUSCH资源的频域资源和时域资源信息。UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表2B所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表2B
Figure PCTCN2020078802-appb-000004
Figure PCTCN2020078802-appb-000005
表2A和2B所示的映射关系可以应用于前导资源为15kHz、OFDM符号采用NR类型I(Type I)1前置符号(front loaded symbol)的场景。表2A和表2B所示的映射关系主要是按照PUSCH的DMRS port配置和可能占据的RB大小等信息确定的，即在一块资源上是复用的，在时域和频域上是平移推开的。
在表2A和2B中，DMRS port Index的取值范围为1至4范围内的整数，即包括1、2、3和4。在本申请的其他实施方式中，DMRS port Index的取值范围还可以包括其他范围，例如：
0至3范围内的整数，即0、1、2和3；或者，
0至5范围内的整数，即0、1、2、3、4和5；或者，
0至7范围内的整数，即0、1、2、3、4、5、6和7；或者；
0至11范围内的整数，即0、1、2、3、4、5、6、7、8、9、10和11；或者；
1至4范围内的整数，即1、2、3和4；或者，
1至6范围内的整数，即1、2、3、4、5和6；或者，
1至8范围内的整数，即1、2、3、4、5、6、7和8；或者；
1至12范围内的整数，即1、2、3、4、5、6、7、8、9、10、11和12。
如下表3为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为前导序列所占据的每个交错块中包含的资源块RB个数。第二列为PUSCH资源的资源配置，具体为Waveform。Waveform的可能取值有2种，包括循环前缀正交频分复用(CP-OFDM，Cyclic Prefix Orthogonal Frequency Division Multiplexing)波形和离散傅里叶变换扩频的正交频分复用(DFT-S-OFDM，Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing)波形。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表3所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表3
Figure PCTCN2020078802-appb-000006
对于DFT-S-OFDM波形，为了便于波形生成，N的取值最好是2、3或5的倍数。因此，对于存在12和13两种RB数目的并且是指示两种波形的情况，会采用Preamble序列所占据的每个Interlace中包含13个RB的情况来指示CP-OFDM波形，并采用Preamble序列所占据的每个Interlace中包含12个RB的情况来指示DFT-S-OFDM波形。
如下表4为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为前导序列所占据的每个交错块中包含的资源块RB个数。第二列为PUSCH资源的资源配置，具体为Payload Size。在表4中，Payload Size的可能取值有2种，包括56bits和72bits。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表4所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表4
Figure PCTCN2020078802-appb-000007
如下表5A为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Index。第二列为PUSCH资源的资源配置，具体为Waveform。Waveform的可能取值有2种，包CP-OFDM波形和DFT-S-OFDM波形。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表5A所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表5A
Interlace Index Waveform
1～K CP-OFDM
K+1～M DFT-S-OFDM
由于Interlace Index的取值大于2项，因此在表5A中，可以选择Interlace Index的部分可能取值对应CP-OFDM波形，采用其他取值对应DFT-S-OFDM波形。在表5A中，K为大于1小于M-1的整数。表5的示例仅为一种举例，在本申请实施例中，对应一种Waveform的Interlace Index可以是不连续的。
如下表5B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置 与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Group Index。第二列为PUSCH资源的资源配置，具体为Waveform。Waveform的可能取值有2种，包括CP-OFDM波形和DFT-S-OFDM波形。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表5B所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表5B
Interlace Group Index Waveform
1 CP-OFDM
2 DFT-S-OFDM
如下表6A为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Index。第二列为PUSCH资源的资源配置，具体为Payload Size。在表6A中，Payload Size的可能取值有2种，包括56bits和72bits。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表6A所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表6A
Interlace Index Payload Size
1～Q 56bits
Q+1～M 72bits
由于Interlace Index的取值大于2项，因此在表6A中，可以选择Interlace Index的部分可能取值对应56bits，采用其他取值对应72bits。在表6A中，Q为大于1小于M-1的整数。表6A的示例仅为一种举例，在本申请实施例中，对 应一种Payload Size的Interlace Index可以是不连续的。此外，Payload Size还可以有144bits、208bits等取值，本申请实施方式可以采用类似的方式，采用Interlace Index的不同取值对应4种或多种Payload Size的取值。
如下表6B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Group Index。第二列为PUSCH资源的资源配置，具体为Payload Size。在表6B中，Payload Size的可能取值有2种，包括56bits和72bits。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表6B所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表6B
Interlace Group Index Payload Size
1 56bits
2 72bits
本申请实施例还可以指示Waveform和Payload Size的组合的不同情况。如下表7A所示。
如下表7A为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Index。第二列为PUSCH资源的资源配置，具体为Waveform和Payload Size的组合。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表7A所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表7A
Interlace Index Waveform和Payload Size
1～G CP-OFDM和56bits
G+1～L DFT-S-OFDM和72bits
L+1～T CP-OFDM和72bits
T+1～M DFT-S-OFDM和56bits
在表7A中，Waveform和Payload Size的组合的可能取值有4种。在表7A中，G、L、T为大于1小于M-1的整数，并且G<L<T。G、L、T这三个整数将Interlace Index的部分可能取值分为4部分，每部分对应Waveform和Payload Size的组合的一种可能取值。表7A的示例仅为一种举例，在申请实施例中，对应一种Waveform和Payload Size的组合的可能取值的Interlace Index可以是不连续的。
如下表7B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Group Index。第二列为PUSCH资源的资源配置，具体为Waveform和Payload Size的组合。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表7B所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表7B
Interlace Group Index Waveform和Payload Size
1 CP-OFDM和56bits
2 DFT-S-OFDM和72bits
3 CP-OFDM和72bits
4 DFT-S-OFDM和56bits
如下表8A为在不同交错模式下，本申请实施例中PUSCH资源的资源配置 与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Index。第二列为PUSCH资源的资源配置，具体为SCS。SCS的可能取值有3种，包括15kHz、15kHz和60kHz。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表8A所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表8A
Interlace Index SCS(kHz)
1 15
2 15
3 15
4 15
5 30
6 30
7 30
8 30
9 60
10 60
11 60
12 60
表8A的示例仅为一种举例，在申请实施例中，对应一种SCS的Interlace Index可以是不连续的。
如下表8B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Group Index。第二列为PUSCH资源的资源配置，具体为SCS。SCS的可能取值有3种，包括15kHz、15kHz和60kHz。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表8B所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表8B
Interlace Group Index SCS(kHz)
1 15
2 30
3 60
SCS的可能取值还可以有其他可能，例如，包括15kHz、30kHz、60kHz和120kHz。如下表9A为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Index。第二列为PUSCH资源的资源配置，具体为SCS。SCS的可能取值有4种，包括15kHz、30kHz、60kHz和120kHz。
表9A
Interlace Index SCS(kHz)
1 15
2 15
3 15
4 30
5 30
6 30
7 60
8 60
9 60
10 120
11 120
12 120
表9A的示例仅为一种举例，在申请实施例中，对应一种SCS的Interlace Index可以是不连续的。
如下表9B为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Interlace Group Index。第二列为PUSCH资源的资源配置，具体为SCS。SCS的可能取值有4种，包括15kHz、30kHz、60kHz和120kHz。
表9B
Interlace Group Index SCS(kHz)
1 15
2 30
3 60
4 120
在表5A至表9B中，介绍了在不同交错模式下，Interlace Index/Interlace Group Index与Payload Size/Waveform/SCS的映射关系。本申请实施例还可以采 用其他的交错块ID，例如交错块在交错块组内的序号，实现与PUSCH资源的资源配置的映射。
对于不存在交错块的情况，本申请实施方式可以采用Preamble Group ID实现与PUSCH资源的资源配置的映射。如下表10为不存在交错模式的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Preamble Group Index。第二列为PUSCH资源的资源配置，具体为Waveform。Waveform的可能取值有2种，包括CP-OFDM波形和DFT-S-OFDM波形。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表10所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表10
Preamble Group Index Waveform
1 CP-OFDM
2 DFT-S-OFDM
在表10中，一个Preamble Group内的Preamble序列的序号可以是不连续的。
如下表11为不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Preamble Group Index。第二列为PUSCH资源的资源配置，具体为Payload Size。Payload Size的可能取值有2种，包括56bits和72bits。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表11所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表11
Preamble Group Index Payload Size
A 56bits
B 72bits
如下表12为在不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Preamble Group Index。第二列为PUSCH资源的资源配置，具体为Waveform和Payload Size的组合。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表12所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表12
Preamble Group Index Waveform和Payload Size
1 CP-OFDM和56bits
2 DFT-S-OFDM和72bits
3 CP-OFDM和72bits
4 DFT-S-OFDM和56bits
在表12中，一个Preamble Group内的Preamble序列的序号可以是不连续的。
在上述实施方式中，Payload Size的可能取值为56bits和72bits。本申请实施方式还可以指示Payload Size的可能取值为56bits、72bits、144bits和208bits的情况。如下表13为在不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Preamble Group Index。第二列为PUSCH资源的资源配置，具体为Payload Size。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表13所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表13
Preamble Group Index Payload Size
1 56bits
2 72bits
3 144bits
4 208bits
在表13中，一个Preamble Group内的Preamble序列的序号可以是不连续的。
在表10至表13中，介绍了不存在交错块的情况下，Preamble Group Index与Payload Size/Waveform的映射关系。在上述实施方式中，采用Preamble Group Index为例进行举例。Preamble Group Index是前导序列标识(Preamble ID)的一种可能情况。本申请实施例还可以采用其他的实施方式，例如前导序列索引(Preamble Index)替代上述映射关系表格中的Preamble Group Index，如表10B至表13B所示。或者，采用前导在前导组内序号替代上述映射关系表格中的Preamble Group Index，如表10C至13C所示。采用前述实施方式，实现Preamble ID与PUSCH资源的资源配置的映射。需要指出的是，在表10C至表13C中，即便采用了不同的符号标记，如果每组的前导分配是均衡的，则前导在组内的序号的最大值也可能相等。
表10B
Preamble Index Waveform
1-W CP-OFDM
W+1-N DFT-S-OFDM
表11B
Preamble Index Payload Size
1～O 56bits
O+1～P 72bits
表12B
Preamble Index Waveform和Payload Size
1～J CP-OFDM和56bits
J+1～D DFT-S-OFDM和72bits
D+1～E CP-OFDM和72bits
E+1～F DFT-S-OFDM和56bits
表13B
Preamble Index Payload Size
1～S 56bits
S+1～H 72bits
H+1～I 144bits
I+1～R 208bits
表10C
前导在前导组内序号 Waveform
1～U CP-OFDM
1～V DFT-S-OFDM
表11C
前导在前导组内序号 Payload Size
1～U' 56bits
1～V' 72bits
表12C
前导在前导组内序号 Waveform和Payload Size
1～λ CP-OFDM和56bits
1～μ DFT-S-OFDM和72bits
1～Ф CP-OFDM和72bits
1～δ DFT-S-OFDM和56bits
表13C
前导在前导组内序号 Payload Size
1～σ 56bits
1～ρ 72bits
1～π 144bits
1～ω 208bits
此外，上述PUSCH资源的资源配置还可以包括调制编码方式。调制编码方式可以包括BPSK调制、pi/2-BPSK调制及QPSK调制中的至少一项。如下表13D和表13E为在不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
在下表13D中，第一列为前导序列配置信息，具体为前导在前导组内的序 号。第二列为PUSCH资源的资源配置，具体为MCS索引(MSC Index)和PayloadSize的组合。在表13D中，MSC Index有2种取值，能够代表2种调制编码方式。
表13D
前导在前导组内的序号 MCS Index&payload size
1～σ 0&56bits
1～ρ 1&56bits
1～π 0&72bits
1～ω 1&72 bits
在表下13D中，第一列为前导序列配置信息，具体为前导序号。第二列为PUSCH资源的资源配置，具体为MSC Index和Payload Size的组合。在表13E中，MSC Index有2种取值，能够代表2种调制编码方式。
表13E
前导序号 MCS Index&payload size
1～S 0&56bits
S+1～H 1&56bits
H+1～I 0&72bits
I+1～R 1&72 bits
如下表14为在不同交错模式下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。在本实施例中，一个接入机会(RO，RACH Occasion)上有多条(例如64条)Preamble序列，则可以采用Preamble Index和Interlace Index联合指示PUSCH资源的资源配置。在表14中，第一列和第二列为前导序列配置信息，包括Interlace Index和Preamble Index。后五列为PUSCH资源的资源配置，包括DMRS port Index以及PUSCH资源的频域资源 和时域资源信息。
UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表14所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表14
Figure PCTCN2020078802-appb-000008
Figure PCTCN2020078802-appb-000009
Figure PCTCN2020078802-appb-000010
Figure PCTCN2020078802-appb-000011
Figure PCTCN2020078802-appb-000012
Figure PCTCN2020078802-appb-000013
Figure PCTCN2020078802-appb-000014
Figure PCTCN2020078802-appb-000015
Figure PCTCN2020078802-appb-000016
Figure PCTCN2020078802-appb-000017
在上表中，采用交错块ID具体为Interlace Index，并且Preamble ID具体为 Preamble Index为例进行说明。在本申请实施方式中，交错块ID还可以为Interlace Group Index或交错块在交错块组内的序号，并且Preamble ID还可以为Preamble Group Index或前导在前导组内的序号。
在没有交错模式的情况下，对于DMRS Port数目可以被Preamble序列数目整除的情况，可以采用Preamble Index进行PUSCH资源的资源配置与前导序列配置信息的映射。在没有交错模式的情况下，对于DMRS Port数目不可以被Preamble序列数目整除的情况，可以采用RO的位置或ID联合Preamble Index，来进行PUSCH资源的资源配置与前导序列配置信息的映射。以下分别采用表15和表16来介绍上述两种情况。
如表15为在不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列为前导序列配置信息，具体为Preamble Index。后五列为PUSCH资源的资源配置，包括DMRS port Index以及PUSCH资源的频域资源和时域资源信息。UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表15所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表15
Figure PCTCN2020078802-appb-000018
Figure PCTCN2020078802-appb-000019
Figure PCTCN2020078802-appb-000020
Figure PCTCN2020078802-appb-000021
Figure PCTCN2020078802-appb-000022
上表中，第6列“PUSCH资源的时域资源的位置相对于Preamble序列时域位置的偏移”的具体值是一种可能的实施方式。在本申请实施方式中，表15中第6列中的数字可以为其他值，即第6列中数字1可以替换为t1，第6列中数字2可以替换为t2、……第6列中数字6可以替换为t6。其中，t1、t2、t3、t4、t5和t6均为整数。
如表16为在不存在交错块的情况下，本申请实施例中PUSCH资源的资源配置与前导序列配置信息的映射关系示例。
其中，第一列和第二列为前导序列配置信息，具体为RO ID和Preamble Index。后五列为PUSCH资源的资源配置，包括DMRS port Index以及PUSCH资源的频域资源和时域资源信息。UE确定自身的PUSCH资源的资源配置后，根据该PUSCH资源的资源配置查找如表16所示的映射关系，确定对应的前导序列配置信息。之后根据该前导序列配置信息进行Preamble序列的映射。
表16
Figure PCTCN2020078802-appb-000023
Figure PCTCN2020078802-appb-000024
上表中，第7列“PUSCH资源的时域资源的位置相对于Preamble序列时域位置的偏移”的具体值是一种可能的实施方式。在本申请实施方式中，表16中第7列中的数字可以为其他值，即第7列中数字1可以替换为t1，第6列中数字2可以替换为t2。其中，t1和t2均为整数。在上表中，以一个RO可用的Preamble序列数目为13为例进行介绍。上表采用了一个RO的所有可用的Preamble序列、第二个RO的任意3条Preamble序列和Preamble Index，来联合指示PUSCH资源的资源配置。
如图2为本申请实施例RO中包含的M个Preamble序列的映射方式示意图。在图2中，RO包括M个Preamble序列，分别为P 1、P 2、……P M。P 1、P 2、……P M分别映射到不同的位置。P 1占据的RB数目为1，对应的DMRS Port Index为k；P 2占据的RB数目为2，对应的DMRS Port Index为m；P M占据的RB数目为6，对应的DMRS Port Index为g。
在上述各个表格介绍的映射关系中，PUSCH资源的频域资源的位置包括：PUSCH频域资源的起点的RB块索引和PUSCH所处的交错块索引中的至少一项。PUSCH资源的频域资源的位置包括：PUSCH时域资源的起点的系统帧号(SFN，System Frame Number)、PUSCH时域资源的起点的子帧号、PUSCH时域资源的起点的时隙或微时隙位置及PUSCH起始符号中的至少一项。
以上介绍了PUSCH资源的资源配置与前导序列配置信息的映射关系多种形式，本申请实施方式的映射关系不限于以上形式。需要说明的是，上述表格中，“PUSCH资源的频域资源所占据的RB个数”及“PUSCH资源的时域资源所占据的时slot/mini-slot个数”可以指PUSCH资源的资源分配粒度，用户占据的时频资源可以是这一粒度的倍数。
根据上述映射关系，UE可以确定与自身的PUSCH资源的资源配置对应的前导序列配置信息，实现对传输资源的选择。
相应地，基站采用上述映射关系，也可以简化接收解调过程。如图3为本申请实施例的一种数据传输方法实现流程示意图，包括：
S31：接收包含物理随机接入信道PRACH资源及物理上行共享信道PUSCH资源的消息。
S32：获取所述消息中的PRACH资源的前导序列配置信息。
S33：根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式。
S34：根据所述资源配置模式获取所述PUSCH资源中的信息。
在一种实施方式中，上述PUSCH资源的信息中至少包括UE ID和用户面数据中的至少一项。上述消息可以为随机接入消息或数据小包消息。
本申请实施例提出的方法可以应用于基站。在上述步骤S31之前，可以进一步包括：向UE发送所述PUSCH资源的资源配置与前导序列配置信息的映射关系，以使所述UE根据自身的PUSCH资源的资源配置及所述映射关系发送所述消息。
PUSCH资源的资源配置与前导序列配置信息的映射关系在上述实施例中已有介绍，在此不再赘述。
如图4为本申请实施例基站与UE的交互过程流程示意图，包括：
S41：基站向UE下发PUSCH资源的资源配置与前导序列配置信息的映射关系。
S42：UE根据自身的PUSCH资源的资源配置查找该映射关系，确定对应的前导序列配置信息。根据确定的前导序列配置信息将Preamble序列映射到PRACH资源。UE向基站发送包含PRACH资源及PUSCH资源的消息。
S43：基站接收该消息，获取该消息中的PRACH资源的前导序列配置信息。根据前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定对应的PUSCH资源的资源配置模式。根据该资源配置模式获取PUSCH资源中的信息。
本申请实施例还提出一种数据传输装置，如图5为本申请实施例的数据传输装置结构示意图，包括：第一查找模块501，用于根据PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述资源配置对应的前导序列配置信息；映射模块502，用于根据所述前导序列配置信息将前导序列映射到PRACH资源；
第一发送模块503，用于发送包含所述PRACH资源及PUSCH资源的消息。
在以上实施方式中，上述PUSCH资源中的信息包括UE ID和用户面数据中的至少一项。
在一种实施方式中，上述装置还可以包括：第一接收模块504，用于接收来自基站的所述PUSCH资源的资源配置与前导序列配置信息的映射关系。
本实施例可以应用于UE。本实施例中的PUSCH资源的资源配置与前导序列配置信息的映射关系与上述实施例介绍的内容相同，在此不再赘述。
本申请实施例还提出一种数据传输装置，如图6为本申请实施例的一种数据传输装置结构示意图，包括：第二接收模块601，用于接收包含PRACH资源及PUSCH资源的消息；第一获取模块602，用于获取所述消息中的PRACH资源的前导序列配置信息；第二查找模块603，用于根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式；第二获取模块604，用于根据所述资源配置模式获取所述PUSCH资源中的信息。
在一种实施方式中，所述PUSCH资源中的信息包括UE ID和用户面数据中的至少一项。
在一种实施方式中，上述装置还可以包括：第二发送模块605，用于向UE发送所述PUSCH资源的资源配置与前导序列配置信息的映射关系，以使所述UE根据自身的PUSCH资源的资源配置及所述映射关系发送所述消息。
本实施例可以应用于基站。本实施例中的PUSCH资源的资源配置与前导序列配置信息的映射关系与上述实施例介绍的内容相同，在此不再赘述。
本申请实施例各装置中的各模块的功能可以参见上述方法实施例中的对应描述，在此不再赘述。
图7为本申请实施例的数据传输的UE结构示意图，如图7所示，本申请实施例提供的UE 70包括：存储器703与处理器704。所述UE 70还可以包括接口701和总线702。所述接口701、存储器703与处理器704通过总线702相连接。所述存储器703用于存储指令。所述处理器704被配置为读取所述指令以执行上述应用于UE的方法实施例的技术方案，其实现原理和技术效果类似，此处不再赘述。
图8为本申请实施例的数据传输的基站结构示意图，如图8所示，本申请实施例提供的基站80包括：存储器803与处理器804。所述基站80还可以包括接口801和总线802。所述接口801、存储器803与处理器804通过总线802相连接。所述存储器803用于存储指令。所述处理器804被配置为读取所述指令以执行上述应用于基站的方法实施例的技术方案，其实现原理和技术效果类似，此处不再赘述。
图9为本申请实施例的通信系统结构示意图，如图9所示，该系统包括：如上述实施例的UE 70以及上述实施例的基站80。
本申请提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述实施例中的方法。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包括有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本申请的可选实施例而已，并非用于限定本申请的保护范围。

Claims (29)

  1. 一种数据传输方法，包括：
    根据物理上行共享信道PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述PUSCH资源的资源配置对应的前导序列配置信息；
    根据所述前导序列配置信息将前导序列映射到物理随机接入信道PRACH资源；
    发送包含所述PRACH资源及所述PUSCH资源的消息。
  2. 根据权利要求1所述的方法，其中，所述PUSCH资源中的信息包括用户设备UE标识ID和用户面数据中的至少一项。
  3. 根据权利要求1或2所述的方法，所述根据PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述资源配置对应的前导序列配置信息之前还包括：
    接收来自基站的所述PUSCH资源的资源配置与前导序列配置信息的映射关系。
  4. 根据权利要求1或2所述的方法，其中，所述前导序列配置信息包括：
    前导ID、交错块ID、前导序列所占据的每个交错块中包含的资源块RB个数及前导序列所在的时频位置信息中的至少一项。
  5. 根据权利要求4所述的方法，其中，所述前导ID包括：
    前导索引、前导组索引及前导在前导组内的序号中的至少一项。
  6. 根据权利要求4所述的方法，其中，所述交错块ID包括：
    交错块索引、交错块组索引及交错块在交错块组内的序号中的至少一项。
  7. 根据权利要求1或2所述的方法，其中，所述PUSCH资源的资源配置包括：
    所述PUSCH资源对应的解调参考信号DMRS端口索引、所述PUSCH资源的频域资源信息、所述PUSCH资源的时域资源信息、所述消息的载荷大小、波形、子载波间隔及调制编码方式中的至少一项。
  8. 根据权利要求7所述方法，其中，所述PUSCH资源对应的DMRS端口索引的取值范围包括以下范围中的至少一种：
    0至3范围内的整数、0至5范围内的整数、0至7范围内的整数、0至11范围内的整数、1至4范围内的整数、1至6范围内的整数、1至8范围内的整数及1至12范围内的整数。
  9. 根据权利要求7所述的方法，其中，所述PUSCH资源的频域资源信息包括：PUSCH资源的频域资源所占据的RB个数及PUSCH资源的频域资源的位置相对于前导序列频域位置的偏移。
  10. 根据权利要求9所述的方法，其中，所述PUSCH资源的频域资源的位置包括：PUSCH资源的频域资源的起点的RB块索引、PUSCH资源的频域资源所处的交错块索引及PUSCH资源的频域资源位于交错块中的RB块索引中的至少一项。
  11. 根据权利要求7所述的方法，其中，所述PUSCH资源的时域资源信息包括：PUSCH资源的时域资源所占据的时隙或微时隙个数及PUSCH资源的时域资源的位置相对于前导序列时域位置的偏移。
  12. 根据权利要求11所述的方法，其中，所述PUSCH资源的时域资源的位置包括：
    PUSCH资源的时域资源的起点的系统帧号SFN、PUSCH资源的时域资源的起点的子帧号、PUSCH资源的时域资源的起点的时隙或微时隙位置及PUSCH资源的时域资源的起始符号中的至少一项。
  13. 根据权利要求7所述的方法，其中，所述消息的载荷大小包括：
    56比特、72比特、144比特及208比特中的至少一项。
  14. 根据权利要求7所述方法，其中，所述波形包括：
    循环前缀正交频分复用CP-OFDM波形和离散傅里叶变换扩频的正交频分复用DFT-S-OFDM波形中的至少一项。
  15. 根据权利要求7所述方法，其中，所述载波间隔包括：
    15kHz、30kHz、60kHz及120kHz中的至少一项。
  16. 根据权利要求7所述的方法，其中，所述调制编码方式包括：
    二进制相移键控BPSK调制、pi/2-BPSK调制及正交相移键控QPSK调制中的至少一项。
  17. 一种数据传输方法，包括：
    接收包含物理随机接入信道PRACH资源及物理上行共享信道PUSCH资源的消息；
    获取所述消息中的PRACH资源的前导序列配置信息；
    根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式；
    根据所述资源配置模式获取所述PUSCH资源中的信息。
  18. 根据权利要求17所述的方法，其中，所述PUSCH资源中的信息包括用户设备UE标识ID和用户面数据中的至少一项。
  19. 根据权利要求17或18所述的方法，，所述接收包含物理随机接入信道PRACH资源及物理上行共享信道PUSCH资源的消息之前还包括：
    向用户设备发送所述PUSCH资源的资源配置与前导序列配置信息的映射关系，以使所述用户设备根据自身的PUSCH资源的资源配置及所述映射关系发送所述消息。
  20. 一种数据传输装置，包括：
    查找模块，设置为根据物理上行共享信道PUSCH资源的资源配置，查找PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述PUSCH资源的资源配置对应的前导序列配置信息；
    映射模块，设置为根据所述前导序列配置信息将前导序列映射到物理随机接入信道PRACH资源；
    发送模块，设置为发送包含所述PRACH资源及所述PUSCH资源的消息。
  21. 根据权利要求20所述的装置，其中，所述PUSCH资源中的信息包括用户设备UE标识ID和用户面数据中的至少一项。
  22. 根据权利要求20或21所述的装置，还包括：
    接收模块，设置为接收来自基站的所述PUSCH资源的资源配置与前导序列配置信息的映射关系。
  23. 一种数据传输装置，包括：
    接收模块，设置为接收包含物理随机接入信道PRACH资源及物理上行共享信道PUSCH资源的消息；
    第一获取模块，设置为获取所述消息中的PRACH资源的前导序列配置信息；
    查找模块，设置为根据所述前导序列配置信息，查找预先保存的PUSCH资源的资源配置与前导序列配置信息的映射关系，确定与所述前导序列配置信息对应的PUSCH资源的资源配置模式；
    第二获取模块，设置为根据所述资源配置模式获取所述PUSCH资源中的信息。
  24. 根据权利要求23所述的装置，其中，所述PUSCH资源中的信息包括用户设备UE标识ID和用户面数据中的至少一项。
  25. 根据权利要求23或24所述的装置，还包括：
    发送模块，设置为向用户设备发送所述PUSCH资源的资源配置与前导序列配置信息的映射关系，以使所述用户设备根据自身的PUSCH资源的资源配置及所述映射关系发送所述消息。
  26. 一种数据传输的用户设备UE，包括：处理器及存储器；
    所述存储器被配置为存储指令；
    所述处理器被配置为读取所述指令以执行如权利要求1至16中任一所述的方法。
  27. 一种数据传输的基站，包括：处理器及存储器；
    所述存储器被配置为存储指令；
    所述处理器被配置为读取所述指令以执行如权利要求17至19中任一所述的方法。
  28. 一种通信系统，包括如权利要求26所述的用户设备UE及如权利要求27所述的基站。
  29. 一种存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1至19任一项所述的方法。
PCT/CN2020/078802 2019-03-13 2020-03-11 数据传输方法、装置、用户设备、基站、通信系统及存储介质 Ceased WO2020182152A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020217029458A KR102899490B1 (ko) 2019-03-13 2020-03-11 데이터 전송 방법 및 디바이스, 사용자 장비, 기지국, 통신 시스템, 그리고 저장 매체
EP20769058.7A EP3941125A4 (en) 2019-03-13 2020-03-11 DATA TRANSMISSION METHOD AND DEVICE, USER EQUIPMENT, BASE STATION, COMMUNICATION SYSTEM AND STORAGE MEDIA
US17/472,283 US12414108B2 (en) 2019-03-13 2021-09-10 Data transmission method and device, user equipment, base station, communication system and storage medium
US19/322,353 US20260006608A1 (en) 2019-03-13 2025-09-08 Data Transmission Method and Device, User Equipment, Base Station, Communication System and Storage Medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910190286.7 2019-03-13
CN201910190286.7A CN110536418A (zh) 2019-03-13 2019-03-13 数据传输方法、装置、用户设备、基站及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/472,283 Continuation US12414108B2 (en) 2019-03-13 2021-09-10 Data transmission method and device, user equipment, base station, communication system and storage medium

Publications (1)

Publication Number Publication Date
WO2020182152A1 true WO2020182152A1 (zh) 2020-09-17

Family

ID=68659228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/078802 Ceased WO2020182152A1 (zh) 2019-03-13 2020-03-11 数据传输方法、装置、用户设备、基站、通信系统及存储介质

Country Status (5)

Country Link
US (2) US12414108B2 (zh)
EP (1) EP3941125A4 (zh)
KR (1) KR102899490B1 (zh)
CN (2) CN110536418A (zh)
WO (1) WO2020182152A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12414108B2 (en) 2019-03-13 2025-09-09 Zte Corporation Data transmission method and device, user equipment, base station, communication system and storage medium

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113330797B (zh) 2019-01-11 2024-08-16 瑞典爱立信有限公司 用于免许可频谱中上行链路传输的资源分配
CN111565471B (zh) * 2019-02-14 2022-05-03 大唐移动通信设备有限公司 一种信息传输方法、装置及设备
CN114342530A (zh) * 2019-07-03 2022-04-12 瑞典爱立信有限公司 针对交错传输的频域资源分配
KR102487216B1 (ko) * 2019-10-04 2023-01-12 엘지전자 주식회사 무선 통신 시스템에서 단말이 임의 접속 과정을 수행하는 방법 및 이를 위한 장치
US12294992B2 (en) 2020-01-22 2025-05-06 Lenovo (Beijing) Ltd. Method and apparatus for MSGA transmission
CN111328152B (zh) * 2020-02-27 2021-11-12 北京邮电大学 两步随机接入中MsgA的资源配置和传输方法
CN113453351B (zh) * 2020-03-27 2022-07-01 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2021184179A1 (zh) * 2020-03-17 2021-09-23 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端设备
CN113453372B (zh) 2020-03-25 2023-08-25 大唐移动通信设备有限公司 一种随机接入方法、基站、用户设备、装置、介质
EP4133827A4 (en) * 2020-04-08 2024-05-08 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for random access
CN114007264B (zh) * 2020-07-28 2025-09-12 大唐移动通信设备有限公司 一种数据传输方法、装置及存储介质
WO2022061755A1 (en) * 2020-09-25 2022-03-31 Lenovo (Beijing) Limited Methods and apparatuses for 2-step random access
KR102826044B1 (ko) * 2023-06-23 2025-06-27 한국전자통신연구원 무선 통신 시스템에서 랜덤 액세스 프리앰블 및 상향링크 데이터 신호의 도달 영역 증대를 위한 장치 및 방법
CN117956627A (zh) * 2024-01-12 2024-04-30 中兴通讯股份有限公司 传输资源配置方法、通信装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105848165A (zh) * 2015-01-14 2016-08-10 中兴通讯股份有限公司 非授权资源的使用方法、系统、基站及用户设备
CN105979594A (zh) * 2016-06-07 2016-09-28 北京邮电大学 一种基于资源分配的随机接入方法及装置
CN106465401A (zh) * 2014-02-28 2017-02-22 Lg电子株式会社 在无线通信系统中发送具有低延迟的上行链路数据的方法和设备
US20170273056A1 (en) * 2016-03-21 2017-09-21 Samsung Electronics Co., Ltd Scheduling uplink transmissions
CN110536418A (zh) * 2019-03-13 2019-12-03 中兴通讯股份有限公司 数据传输方法、装置、用户设备、基站及存储介质

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101447750B1 (ko) * 2008-01-04 2014-10-06 엘지전자 주식회사 랜덤 액세스 과정을 수행하는 방법
WO2014166046A1 (zh) 2013-04-08 2014-10-16 华为技术有限公司 随机接入前导的发送与接收方法、以及相应的设备
CN104254135B (zh) * 2013-06-27 2020-03-31 夏普株式会社 基站和用户设备及其方法
CN104981022B (zh) * 2014-04-04 2020-07-10 北京三星通信技术研究有限公司 数据传输的方法、基站及终端
US10231196B2 (en) * 2015-04-10 2019-03-12 Korea Advanced Institute Of Science And Technology Communication apparatus and method using random access procedure
US11700641B2 (en) * 2015-08-19 2023-07-11 Lg Electronics Inc. Random access procedure performing method in wireless communication system, and apparatus therefor
US10425970B2 (en) * 2016-09-30 2019-09-24 Qualcomm Incorporated Precoding management for random access procedures
CN108668361B (zh) * 2017-04-01 2023-08-04 北京三星通信技术研究有限公司 一种信息生成方法和设备
CN107371126B (zh) * 2017-08-21 2019-07-30 西安电子科技大学 基于fdd-lte网络的随机接入方法
CN111277382B (zh) * 2019-01-18 2021-10-22 维沃移动通信有限公司 一种随机接入过程的信息传输方法及终端
US11032854B2 (en) * 2019-01-18 2021-06-08 Qualcomm Incorporated Variable payload size for two-step random access
CN111565471B (zh) * 2019-02-14 2022-05-03 大唐移动通信设备有限公司 一种信息传输方法、装置及设备
CN115843116A (zh) * 2019-02-15 2023-03-24 华为技术有限公司 一种随机接入方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106465401A (zh) * 2014-02-28 2017-02-22 Lg电子株式会社 在无线通信系统中发送具有低延迟的上行链路数据的方法和设备
CN105848165A (zh) * 2015-01-14 2016-08-10 中兴通讯股份有限公司 非授权资源的使用方法、系统、基站及用户设备
US20170273056A1 (en) * 2016-03-21 2017-09-21 Samsung Electronics Co., Ltd Scheduling uplink transmissions
CN105979594A (zh) * 2016-06-07 2016-09-28 北京邮电大学 一种基于资源分配的随机接入方法及装置
CN110536418A (zh) * 2019-03-13 2019-12-03 中兴通讯股份有限公司 数据传输方法、装置、用户设备、基站及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3941125A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12414108B2 (en) 2019-03-13 2025-09-09 Zte Corporation Data transmission method and device, user equipment, base station, communication system and storage medium

Also Published As

Publication number Publication date
KR20210151063A (ko) 2021-12-13
CN114786256A (zh) 2022-07-22
US20260006608A1 (en) 2026-01-01
EP3941125A1 (en) 2022-01-19
US20220104226A1 (en) 2022-03-31
CN114786256B (zh) 2026-03-13
KR102899490B1 (ko) 2025-12-11
EP3941125A4 (en) 2022-10-26
CN110536418A (zh) 2019-12-03
US12414108B2 (en) 2025-09-09

Similar Documents

Publication Publication Date Title
WO2020182152A1 (zh) 数据传输方法、装置、用户设备、基站、通信系统及存储介质
US10644850B2 (en) Method and apparatus for uplink signal transmission
EP4307581B1 (en) Method and device for transmitting measurement reference signal
RU2589733C2 (ru) Способ обработки опорного сигнала демодуляции, базовая станция и оборудование пользователя
JP6616510B2 (ja) アップリンク制御情報送信の方法およびデバイス
US11272533B2 (en) Random-access sending and receiving method and apparatus, transmitting end and receiving end
CN105393576B (zh) 一种数据传输方法及设备
US11611967B2 (en) Scrambling-based data transmission method
CN103718526B (zh) 导频配置方法、发送方法及装置
CN110034910A (zh) 一种确定epdcch候选的方法及设备
CN107196735A (zh) 确定传输信息的方法、装置及系统
WO2017152407A1 (zh) 一种参考信号产生方法及装置
US10999108B2 (en) Wireless communication method, apparatus, and system
CN103326839A (zh) 增强的物理下行控制信道的发送、接收方法和装置
WO2020143591A1 (zh) 传输解调参考信号的方法、终端设备和网络设备
WO2016161916A1 (zh) 一种数据传输方法及设备
US11082178B2 (en) Message sending method and device, electronic device
CN105900388B (zh) Ltf生成方法和装置
CN108282308A (zh) 参考信号的处理方法及装置、设备
WO2017121416A1 (zh) 上行控制信息的发送方法及装置
TWI715883B (zh) Ｐｕｃｃｈ傳輸方法、終端及網路側設備
CN111464478A (zh) 一种信号发送、接收方法及设备
CN106911612A (zh) 信息的发送方法及装置
CN108616343B (zh) 一种用于无线通信中的ue、基站中的方法和装置
CN108631996A (zh) 一种参考信号发送、接收方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20769058

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20217029458

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020769058

Country of ref document: EP

Effective date: 20211013