WO2020164639A1 - 一种随机接入方法、设备及系统 - Google Patents

一种随机接入方法、设备及系统 Download PDF

Info

Publication number
WO2020164639A1
WO2020164639A1 PCT/CN2020/075603 CN2020075603W WO2020164639A1 WO 2020164639 A1 WO2020164639 A1 WO 2020164639A1 CN 2020075603 W CN2020075603 W CN 2020075603W WO 2020164639 A1 WO2020164639 A1 WO 2020164639A1
Authority
WO
WIPO (PCT)
Prior art keywords
frequency resource
time
configuration information
prach
pusch
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/075603
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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
Priority claimed from CN201910351921.5A external-priority patent/CN111586861B/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to AU2020220568A priority Critical patent/AU2020220568B2/en
Priority to JP2021547715A priority patent/JP7174859B2/ja
Priority to BR112021016150-3A priority patent/BR112021016150A2/pt
Priority to KR1020217029802A priority patent/KR102775331B1/ko
Priority to EP20756405.5A priority patent/EP3923652A4/en
Priority to CA3130419A priority patent/CA3130419A1/en
Publication of WO2020164639A1 publication Critical patent/WO2020164639A1/zh
Priority to US17/402,302 priority patent/US12052770B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • 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/0078—Timing of allocation
    • H04L5/0082—Timing of allocation at predetermined intervals
    • 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
    • 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/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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
    • 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/0866—Non-scheduled access, e.g. ALOHA using a dedicated channel for access
    • 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
    • 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

Definitions

  • This application relates to the field of communication technology, and in particular to a random access method, device and system.
  • UE user equipment
  • BS base station
  • random access procedure random access procedure
  • the UE can access the BS through a four-step random access process.
  • the four-step random access process is specifically as follows: the UE sends a random access preamble (random access preamble) to the BS, also known as message one (message1, Msg1). After detecting the random access preamble, the BS sends a random access response to the UE, which is also called message two (Msg2).
  • Msg2 message two
  • the UE sends an uplink message through a data channel (for example, a physical uplink shared channel (PUSCH)) on the allocated uplink resource according to the instruction of Msg2, which is also called message three (Msg3).
  • Msg3 will carry the unique identity information of the UE.
  • the BS can successfully receive the Msg3 sent by one UE at most at a time, or it may not be able to successfully receive the Msg3 sent by any UE due to interference between the UEs.
  • the BS returns a conflict resolution message (also referred to as Msg4) to the successfully accessed UE.
  • the Msg4 carries the unique identity in the Msg3 to specify the successfully accessed UE.
  • the industry has proposed a two-step random access process method.
  • the difference between the two-step random access process and the four-step random access process is that in the two-step random access process, the Msg A sent by the UE to the BS includes the random access preamble and uplink data, namely The uplink data is sent before the uplink synchronization is completed, thereby reducing the delay of uplink data transmission.
  • the Msg B sent by the BS to the UE in the two-step random access process does not need to send scheduling information of the data channel for the UE, thereby reducing signaling overhead.
  • This application provides a random access method, device and system, which can reduce signaling overhead and improve resource utilization.
  • a random access method including: a terminal receives first configuration information, second configuration information, and third configuration information sent by a network device, where the first configuration information is used to configure one or more physical random Access channel PRACH time-frequency resource and preamble sequence set; the second configuration information is used to configure the physical uplink shared channel PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource, when the PUSCH time-frequency resource block includes one or more PUSCH Frequency resources; the third configuration information is used to configure the size of each PUSCH time-frequency resource and the corresponding relationship between the preamble sequence and the PUSCH time-frequency resource; determine the first PRACH time-frequency resource according to the first configuration information; determine the need for the first PRACH The first preamble sequence sent on the frequency resource, the first preamble sequence is the preamble sequence in the preamble sequence set; the first preamble sequence is determined according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information
  • the terminal can determine the PUSCH time-frequency resource for the preamble sequence corresponding to the preamble sequence according to the first configuration information, the second configuration information, and the third configuration information configured by the network device. Therefore, the terminal can directly send the first message including the first preamble sequence and uplink data, which can reduce the delay of uplink data transmission.
  • the network equipment does not need to send PUSCH time-frequency resource scheduling information to each random access of the terminal, which can reduce signaling overhead.
  • the second configuration information includes information for configuring a demodulation reference signal DMRS port associated with the PUSCH time-frequency resource block.
  • the second configuration information includes configuration information of the first mapping pattern
  • the first mapping pattern includes one or more mapping rules
  • each mapping rule can be used in conjunction with at least one PRACH time-frequency resource to determine at least Time domain resources and frequency domain resources of one PUSCH time-frequency resource block.
  • the second configuration information includes a period T1 for configuring the PUSCH time-frequency resource block, and the first mapping pattern is used to determine the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource in the period T1.
  • the second configuration information includes a parameter N 1 , and the parameter N 1 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the parameter N 1 and the first mapping pattern are used to determine the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 2 and parameter N 3 , parameter N 2 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 3 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T1.
  • the second configuration information includes the period T2 of the PUSCH time-frequency resource block, the time-domain resource configuration information of the PUSCH time-frequency resource block and/or the frequency-domain resource configuration information of the PUSCH time-frequency resource block.
  • the second configuration information includes a mapping period T3, and the same rule is used in each mapping period T3 to determine the PUSCH time-frequency resource block corresponding to each configured PRACH time-frequency resource.
  • the second configuration information includes a parameter N 4 , and the parameter N 4 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 5 and parameter N 6 , parameter N 5 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 6 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T3.
  • the second configuration information further includes information about a parameter N 7 and a second mapping pattern.
  • the parameter N 7 is used to determine the number of PRACH time-frequency resources included in each PRACH resource group
  • the second mapping pattern includes One or more sequence number sets, each sequence number set contains one or more PUSCH time-frequency resource block sequence numbers, parameter N 7 and the second mapping pattern are used to determine the PUSCH time associated with each PRACH time-frequency resource group in period T3 The sequence number of the frequency resource block.
  • determining the PUSCH time-frequency resource corresponding to the first preamble sequence according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information includes: according to a preset PRACH The mapping sequence of the time-frequency resource to the PUSCH time-frequency resource block, the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information determine the PUSCH time-frequency resource corresponding to the first preamble sequence.
  • the third configuration information includes the size of each PUSCH time-frequency resource and a parameter N 8 , and the parameter N 8 is used to determine the number of PUSCH time-frequency resources corresponding to each preamble sequence.
  • determining the PUSCH time-frequency resource corresponding to the first preamble sequence according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information includes: according to a preset PRACH time-frequency resource Frequency resource to time-frequency resource block mapping sequence, preset preamble sequence to PUSCH time-frequency resource mapping sequence, first PRACH time-frequency resource, first preamble sequence, second configuration information, and third configuration information determine the first preamble The PUSCH time-frequency resource corresponding to the sequence.
  • the method further includes: determining the DMRS port associated with the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource according to a preset mapping sequence of the preamble sequence to the DMRS port.
  • a random access method including: a network device sends first configuration information, second configuration information, and third configuration information to a terminal, where the first configuration information is used to configure one or more physical random access Incoming channel PRACH time-frequency resource and preamble sequence set; the second configuration information is used to configure the physical uplink shared channel PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource, the PUSCH time-frequency resource block includes one or more PUSCH time-frequency resources Resource; the third configuration information is used to configure the size of each PUSCH time-frequency resource and the corresponding relationship between the preamble sequence and the PUSCH time-frequency resource; receiving the first message sent by the terminal containing the first preamble sequence and uplink data, where the first The preamble sequence is carried on the first PRACH time-frequency resource, and the uplink data is carried on the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource.
  • the first configuration information, the second configuration information, and the third configuration information configured by the network device can be used by the terminal to determine the PUSCH time-frequency resource corresponding to the preamble sequence and the preamble sequence. Therefore, the terminal can directly send the first message containing the first preamble sequence and uplink data, which can reduce the delay of uplink data transmission. In addition, the network equipment does not need to send PUSCH time-frequency resource scheduling information to each random access of the terminal, which can reduce signaling overhead.
  • the second configuration information includes information for configuring a demodulation reference signal DMRS port associated with the PUSCH time-frequency resource block.
  • the second configuration information includes configuration information of the first mapping pattern
  • the first mapping pattern includes one or more mapping rules
  • each mapping rule can be used in conjunction with at least one PRACH time-frequency resource to determine at least Time domain resources and frequency domain resources of one PUSCH time-frequency resource block.
  • the second configuration information includes a period T1 for configuring the PUSCH time-frequency resource block, and the first mapping pattern is used to determine the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource in the period T1.
  • the second configuration information includes a parameter N 1 , and the parameter N 1 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the parameter N 1 and the first mapping pattern are used to determine the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 2 and parameter N 3 , parameter N 2 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 3 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T1.
  • the second configuration information includes the period T2 of the PUSCH time-frequency resource block, the time-domain resource configuration information of the PUSCH time-frequency resource block and/or the frequency-domain resource configuration information of the PUSCH time-frequency resource block.
  • the second configuration information includes a mapping period T3, and the same rule is used in each mapping period T3 to determine the PUSCH time-frequency resource block corresponding to each configured PRACH time-frequency resource.
  • the second configuration information includes a parameter N 4 , and the parameter N 4 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 5 and parameter N 6 , parameter N 5 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 6 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T3.
  • the second configuration information further includes information about a parameter N 7 and a second mapping pattern.
  • the parameter N 7 is used to determine the number of PRACH time-frequency resources included in each PRACH resource group
  • the second mapping pattern includes One or more sequence number sets, each sequence number set contains one or more PUSCH time-frequency resource block sequence numbers, parameter N 7 and the second mapping pattern are used to determine the PUSCH time associated with each PRACH time-frequency resource group in period T3 The sequence number of the frequency resource block.
  • the third configuration information includes the size of each PUSCH time-frequency resource and a parameter N 8 , and the parameter N 8 is used to determine the number of PUSCH time-frequency resources corresponding to each preamble sequence.
  • a random access device including: a communication unit and a determining unit; the communication unit is configured to receive first configuration information, second configuration information, and third configuration information sent by a network device, and the first configuration information Used to configure one or more physical random access channel PRACH time-frequency resources and preamble sequence sets; the second configuration information is used to configure the physical uplink shared channel PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource, PUSCH time-frequency
  • the resource block includes one or more PUSCH time-frequency resources;
  • the third configuration information is used to configure the size of each PUSCH time-frequency resource and the corresponding relationship between the preamble sequence and the PUSCH time-frequency resource; the determining unit is used to determine according to the first configuration information
  • the first PRACH time-frequency resource; the determining unit is also used to determine the first preamble sequence that needs to be sent on the first PRACH time-frequency resource, the first preamble sequence is the preamble sequence in the preamble sequence set; the determining unit is also used
  • the second configuration information includes information for configuring a demodulation reference signal DMRS port associated with the PUSCH time-frequency resource block.
  • the second configuration information includes configuration information of the first mapping pattern
  • the first mapping pattern includes one or more mapping rules
  • each mapping rule can be used in conjunction with at least one PRACH time-frequency resource to determine at least Time domain resources and frequency domain resources of one PUSCH time-frequency resource block.
  • the second configuration information includes a period T1 for configuring the PUSCH time-frequency resource block, and the first mapping pattern is used to determine the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource in the period T1.
  • the second configuration information includes a parameter N 1 , and the parameter N 1 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the parameter N 1 and the first mapping pattern are used to determine the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 2 and parameter N 3 , parameter N 2 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 3 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T1.
  • the second configuration information includes the period T2 of the PUSCH time-frequency resource block, the time-domain resource configuration information of the PUSCH time-frequency resource block and/or the frequency-domain resource configuration information of the PUSCH time-frequency resource block.
  • the second configuration information includes a mapping period T3, and the same rule is used in each mapping period T3 to determine the PUSCH time-frequency resource block corresponding to each configured PRACH time-frequency resource.
  • the second configuration information includes a parameter N 4 , and the parameter N 4 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 5 and parameter N 6 , parameter N 5 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 6 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T3.
  • the second configuration information further includes information about a parameter N 7 and a second mapping pattern.
  • the parameter N 7 is used to determine the number of PRACH time-frequency resources included in each PRACH resource group
  • the second mapping pattern includes One or more sequence number sets, each sequence number set contains one or more PUSCH time-frequency resource block sequence numbers, parameter N 7 and the second mapping pattern are used to determine the PUSCH time associated with each PRACH time-frequency resource group in period T3 The sequence number of the frequency resource block.
  • the determining unit is further configured to determine the specific time-frequency resource of the PUSCH corresponding to the first preamble sequence according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information. It includes: a determining unit, specifically configured to determine the first PRACH time-frequency resource to the PUSCH time-frequency resource block mapping sequence, the first PRACH time-frequency resource, the first preamble sequence, the second configuration information and the third configuration information The PUSCH time-frequency resource corresponding to the preamble sequence.
  • the third configuration information includes the size of each PUSCH time-frequency resource and a parameter N 8 , and the parameter N 8 is used to determine the number of PUSCH time-frequency resources corresponding to each preamble sequence.
  • the determining unit is further configured to determine the PUSCH time-frequency resource corresponding to the first preamble sequence according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information, including: The determining unit is specifically configured to perform the mapping sequence from the preset PRACH time-frequency resource to the time-frequency resource block, the preset preamble sequence to the PUSCH time-frequency resource mapping sequence, the first PRACH time-frequency resource, the first preamble sequence, and the The second configuration information and the third configuration information determine the PUSCH time-frequency resource corresponding to the first preamble sequence.
  • the determining unit is further configured to determine the DMRS port associated with the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource according to the preset mapping sequence of the preamble sequence to the DMRS port.
  • a random access device including: a communication unit, configured to send first configuration information, second configuration information, and third configuration information to a terminal, and the first configuration information is used to configure one Or multiple physical random access channel PRACH time-frequency resources and preamble sequence sets; the second configuration information is used to configure the physical uplink shared channel PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource, and the PUSCH time-frequency resource block includes one Or multiple PUSCH time-frequency resources; the third configuration information is used to configure the size of each PUSCH time-frequency resource and the corresponding relationship between the preamble sequence and the PUSCH time-frequency resource; the communication unit is also used to receive the first preamble sequence sent by the terminal And the first message of uplink data, where the first preamble sequence is carried on the first PRACH time-frequency resource, and the uplink data is carried on the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource.
  • the second configuration information includes information for configuring a demodulation reference signal DMRS port associated with the PUSCH time-frequency resource block.
  • the second configuration information includes configuration information of the first mapping pattern
  • the first mapping pattern includes one or more mapping rules
  • each mapping rule can be used in conjunction with at least one PRACH time-frequency resource to determine at least Time domain resources and frequency domain resources of one PUSCH time-frequency resource block.
  • the second configuration information includes a period T1 for configuring the PUSCH time-frequency resource block, and the first mapping pattern is used to determine the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource in the period T1.
  • the second configuration information includes a parameter N 1 , and the parameter N 1 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the parameter N 1 and the first mapping pattern are used to determine the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 2 and parameter N 3 , parameter N 2 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 3 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T1.
  • the second configuration information includes the period T2 of the PUSCH time-frequency resource block, the time-domain resource configuration information of the PUSCH time-frequency resource block and/or the frequency-domain resource configuration information of the PUSCH time-frequency resource block.
  • the second configuration information includes a mapping period T3, and the same rule is used in each mapping period T3 to determine the PUSCH time-frequency resource block corresponding to each configured PRACH time-frequency resource.
  • the second configuration information includes a parameter N 4 , and the parameter N 4 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource.
  • the second configuration information includes parameter N 5 and parameter N 6 , parameter N 5 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group, and parameter N 6 is used to determine the period The number of PUSCH time-frequency resource blocks associated with each PRACH time-frequency resource group in T3.
  • the second configuration information further includes information about a parameter N 7 and a second mapping pattern.
  • the parameter N 7 is used to determine the number of PRACH time-frequency resources included in each PRACH resource group
  • the second mapping pattern includes One or more sequence number sets, each sequence number set contains one or more PUSCH time-frequency resource block sequence numbers, parameter N 7 and the second mapping pattern are used to determine the PUSCH time associated with each PRACH time-frequency resource group in period T3 The sequence number of the frequency resource block.
  • the third configuration information includes the size of each resource and PUSCH frequency parameters N 8, it is determined that the number of parameters for each N8 PUSCH preamble sequence corresponding to frequency resources.
  • a random access device in a fifth aspect, includes: a processor; optionally, further includes one or more of a memory, at least one communication interface, and a communication bus; the memory is used to store a computer The instructions are executed, the processor, the memory, and at least one communication interface are connected through a communication bus, and the processor executes the computer-executable instructions stored in the memory to enable the random access device to implement the method provided in the first aspect or the second aspect.
  • the random access device can exist in the form of a chip product.
  • a communication system including the random access devices provided in the third aspect and the fourth aspect.
  • a computer-readable storage medium including instructions, which when run on a computer, cause the computer to execute any one of the methods provided in the first aspect or the second aspect.
  • a computer program product containing instructions is provided.
  • the instructions run on a computer, the computer executes any method provided in any one of the first aspect or the second aspect.
  • Fig. 1 is a schematic diagram of a random access process provided in the prior art
  • FIG. 2 is a schematic diagram of the composition of a communication system provided by an embodiment of this application.
  • Fig. 3 is a schematic diagram of a 5G NR frame structure in the prior art
  • Figure 4 is a schematic diagram of another 5G NR frame structure in the prior art
  • 5A is a schematic diagram of a PRACH time-frequency resource numbering method provided by an embodiment of this application.
  • 5B is a schematic flowchart of a random access method provided by an embodiment of this application.
  • FIG. 5C is a schematic diagram of a frequency domain resource numbering method provided by an embodiment of this application.
  • 5D is a schematic diagram of a method for configuring PRACH time-frequency resources in a two-step random access process according to an embodiment of the application;
  • FIG. 5E is a schematic diagram of a method for configuring a mapping period according to an embodiment of this application.
  • FIG. 6 is a schematic diagram of a method for mapping PRACH time-frequency resources and PUSCH time-frequency resource blocks according to an embodiment of the application;
  • FIG. 7 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • FIG. 8 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • FIG. 9 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application.
  • FIG. 10 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • FIG. 11 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • FIG. 12 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • FIG. 13 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • FIG. 14 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • 15A is a schematic diagram of a method for configuring PRACH time-frequency resources according to an embodiment of the application.
  • 15B is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • FIG. 16 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • 17 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • 18 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • 19 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of this application;
  • 20 is a schematic diagram of another PRACH time-frequency resource and PUSCH time-frequency resource block mapping method provided by an embodiment of the application;
  • FIG. 21 is a schematic diagram of a method for mapping a preamble sequence and PUSCH time-frequency resources according to an embodiment of the application;
  • FIG. 22 is a schematic diagram of another preamble sequence and PUSCH time-frequency resource mapping method provided by an embodiment of the application.
  • FIG. 23 is a schematic diagram of another method for mapping a preamble sequence and a PUSCH time-frequency resource according to an embodiment of the application.
  • 24A is a schematic diagram of yet another method for mapping a preamble sequence and PUSCH time-frequency resources according to an embodiment of the application;
  • 24B is a schematic structural diagram of a device provided by an embodiment of the application.
  • 25 is a schematic structural diagram of another device provided by an embodiment of the application.
  • FIG. 26 is a schematic structural diagram of yet another device provided by an embodiment of this application.
  • FIG. 27 is a schematic structural diagram of another device provided by an embodiment of the application.
  • FIG. 28 is a schematic structural diagram of another device provided by an embodiment of the application.
  • FIG. 29 is a schematic structural diagram of another device provided by an embodiment of the application.
  • PRACH time-frequency resources also known as PRACH opportunities (occasion)
  • a PRACH opportunity is usually used to indicate a piece of time-frequency resource used to send a preamble.
  • Each PRACH time-frequency resource may contain 64 preamble sequences, and each preamble sequence may be called a preamble resource.
  • the PRACH time-frequency resource occupies time-frequency resources of different sizes according to the subcarrier spacing of the PRACH time-frequency resource and the difference of the preamble format.
  • Configuring the PRACH time-frequency resources on the network side specifically includes configuring time-domain resources and frequency-domain resources.
  • the network side can configure, for example, the parameter PRACH Configuration Index.
  • the network side can configure the frequency domain size of the PRACH time-frequency resources, the frequency domain starting position, and how many PRACH time domains are continuous in the frequency domain for each PRACH time domain opportunity Frequency resources.
  • the network side may configure, for example, the parameter msg1-FrequencyStart, which is used to indicate the frequency domain start position of the PRACH time-frequency resource.
  • the network side may also configure, for example, the parameter msg1-FDM, which is used to indicate how many PRACH time-frequency resources with continuous frequency domain are used for each PRACH time domain opportunity.
  • the network side may also configure, for example, the parameter PRACH Configuration Index, which is used to indicate the frequency domain size of the PRACH time-frequency resource.
  • the UE side can determine the preamble formats (Preamble formats) according to the parameter PRACH Configuration Index and look up Table 1.
  • the length of the preamble (L RA ) and the subcarrier spacing ( ⁇ f RA ) of the PRACH time-frequency resource can be determined according to the preamble format and the look-up table two or three.
  • the frequency domain size of the PRACH time-frequency resource can be determined by looking up Table 4 (I.e. the number of RBs occupied by PRACH time-frequency resources ).
  • 5G NR supports multiple subcarrier intervals, but under different subcarrier interval configurations, the length of the radio frame and the subframe are the same.
  • the radio frame length is 10ms
  • the subframe length is 1ms.
  • each slot will be different due to the difference of the sub-carrier spacing. Generally, as the sub-carrier spacing becomes larger, the time slot length becomes smaller. Therefore, the number of time slots contained in each subframe is different. In the case of a normal cyclic prefix (Cyclic Prefix, CP), each slot contains the same number of symbols, and they are all 14.
  • Cyclic Prefix Cyclic Prefix
  • a radio frame contains 10 sub-frames (the sub-frame numbers are #0 to #9), and each sub-frame has only 1 Therefore, the radio frame contains 10 time slots, that is, the sequence number of the subframe is the same as the sequence number of the time slot, and the subframe and the time slot can replace each other.
  • Each slot contains 14 OFDM symbols (the sequence numbers of the OFDM symbols in each slot are #0 to #13).
  • a radio frame contains 10 subframes (the sequence numbers of the subframes are #0 to #9 respectively), and each subframe has only 2 time slots (the sequence number of the time slots in each subframe is #0 to #1), so the radio frame contains 20 time slots.
  • Each slot contains 14 OFDM symbols (the sequence numbers of the OFDM symbols in each slot are #0 to #13).
  • XX#n the format of "XX#n” is used to represent “XX with a serial number of n".
  • n is a positive integer.
  • XX can be "radio frame”, “subframe”, “slot”, “symbol”, “PRACH time-frequency resource”, “PRACH time-frequency resource group”, “PUSCH time-frequency resource block”, “PUSCH time Frequency resources” and so on.
  • Subframe #4 means the subframe with the sequence number 4. This is a unified description, and will not be repeated here.
  • the sequence number of the PRACH time-frequency resource may be determined according to the sequence number of the time domain resource and the sequence number of the frequency domain resource.
  • the sequence number of the time domain resource can be based on the sequence number of the subframe occupied by the PRACH time-frequency resource, and the sequence number of the occupied time slot (when multiple time slots are occupied, it can be the start time The sequence number of the slot or the sequence number of the end time slot) and the sequence number of the occupied symbol (when multiple symbols are occupied, it can be the sequence number of the start symbol or the sequence number of the end symbol).
  • the ascending order of the sequence numbers of time domain resources can be the ascending order of the sequence numbers of the subframes occupied by PRACH time-frequency resources, and the ascending order of the sequence numbers of the occupied time slots (when multiple time slots are occupied, it can be the initial time slot
  • the ascending sequence of the sequence number of the occupied symbol when multiple symbols are occupied, it can be the sequence number of the start symbol or the sequence number of the end symbol in ascending order).
  • the sequence number of the frequency domain resource can be determined according to the sequence number of the RB occupied by the PRACH time-frequency resource.
  • the sequence number of the frequency domain resource can be determined according to the sequence number of the start RB or the sequence number of the end RB occupied by the PRACH time-frequency resource.
  • the ascending order of the sequence numbers of the frequency domain resources may be the ascending order of the sequence numbers of the RBs occupied by the PRACH time-frequency resources.
  • the ascending order of the frequency domain resource sequence number may be the ascending sequence of the sequence number of the start RB or the end RB occupied by the PRACH time-frequency resource.
  • the sequence number of the PRACH time-frequency resource can be determined first according to the sequence number of the frequency domain resource, and then according to the sequence number of the time domain resource.
  • the sequence number of the PRACH time-frequency resource can also be determined first according to the sequence number of the time domain resource, and then according to the sequence number of the frequency domain resource.
  • the ascending order of the sequence numbers of the PRACH time-frequency resources may be in the ascending order of the sequence numbers of the frequency domain resources first, and then in the ascending order of the sequence numbers of the time domain resources.
  • the subcarrier interval of the PRACH time-frequency resource is 15Khz, that is, one subframe only includes one time slot.
  • 4 PRACH time-frequency resources are configured, which are respectively configured in subframe #1 and subframe #6, and subframe #1 and subframe #6 are respectively frequency division multiplexed with 2 PRACH time-frequency resources .
  • the order of the four PRACH time-frequency resources is: starting from the leftmost subframe #1, in ascending order of the starting RB sequence number occupied by the PRACH time-frequency resources, that is, the lower PRACH time-frequency resources in subframe #1 It is PRACH time-frequency resource #0, and the upper PRACH time-frequency resource in subframe #1 is PRACH time-frequency resource #1. Then, the lower PRACH time-frequency resource in subframe #6 is PRACH time-frequency resource #2, and the upper PRACH time-frequency resource in subframe #6 is PRACH time-frequency resource #3.
  • DMRS ports can be represented by antenna ports, that is, different antenna ports correspond to different DMRS configurations.
  • Table 5 it is the parameter configuration information corresponding to PUSCH DMRS configuration type 1. It can be seen from Table 5 that PUSCH DMRS configuration type 1 can support up to 8 antenna ports, which can correspond to 8 different DMRS configurations, that is, 8 DMRS ports.
  • Table 6 the parameter configuration information corresponding to PUSCH DMRS configuration type 2. It can be seen from Table 6 that PUSCH DMRS configuration type 2 can support up to 12 antenna ports, corresponding to 12 different DMRS configurations, that is, 12 DMRS ports.
  • LTE long-term evolution
  • NR new radio
  • 5G fifth generation
  • future evolution future evolution
  • multiple communication convergence systems etc.
  • the technical solutions provided by the embodiments of the present application can be applied to various communication scenarios. For example, machine to machine (M2M), macro and micro communications, enhanced mobile broadband (eMBB), ultra-reliable & low latency communication (URLLC), and massive Internet of Things Communication (massive machine type communication, mMTC) and other scenarios.
  • M2M machine to machine
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable & low latency communication
  • massive Internet of Things Communication massive Internet of Things Communication
  • the communication subjects in these communication scenarios and transmission scenarios may include, but are not limited to: communication equipment and communication equipment (for example, terminals and terminals), network equipment and network equipment (for example, base stations and base stations), network equipment and communication equipment (for example, The communication scenarios between the base station and the terminal, etc.
  • communication equipment and communication equipment for example, terminals and terminals
  • network equipment and network equipment for example, base stations and base stations
  • network equipment and communication equipment for example, The communication scenarios between the base station and the terminal, etc.
  • Fig. 2 is a schematic diagram of the architecture of a mobile communication system applied in an embodiment of the present application.
  • the mobile communication system includes a terminal 100.
  • the terminal 100 accesses a wireless network to obtain services from an external network (such as the Internet) through the wireless network, or communicate with other terminals through the wireless network.
  • the wireless network includes a radio access network (radio access network, RAN) 110.
  • RAN radio access network
  • the RAN 110 is used to connect the terminal 100 to the wireless network.
  • the RAN 110 may include radio access network equipment.
  • the terminal is connected to the wireless access network device in a wireless manner, and can access the core network through the wireless access network device.
  • the terminal 100 may be in a fixed location or movable.
  • FIG. 2 is only a schematic diagram.
  • the communication system may also include other network equipment, such as wireless relay equipment and wireless backhaul equipment, which are not shown in FIG. 2.
  • the embodiment of the present application does not limit the number of radio access network devices and terminals included in the mobile communication system.
  • Wireless access network equipment and terminals can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on the water; they can also be deployed on airborne aircraft, balloons, and satellites.
  • the embodiments of the present application do not limit the application scenarios of radio access network equipment and terminals.
  • the terminal can also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent Or user device.
  • the terminal can be a station (STA) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, and a wireless local loop (wireless local loop).
  • WLAN wireless local area network
  • SIP session initiation protocol
  • wireless local loop wireless local loop
  • next-generation communication systems such as , A terminal in a fifth-generation (fifth-generation, 5G) communication network or a terminal in a public land mobile network (PLMN) network that will evolve in the future.
  • 5G can also be referred to as new radio (NR).
  • the terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the wireless access network device may be an access device used for a terminal to access the mobile communication system in a wireless manner.
  • the wireless access network device may be a network device.
  • the network equipment may be an access point (AP) in a WLAN, an evolved base station ((evolved Node B, eNB or eNodeB) in a long term evolution (LTE), or an NR The base station (next generation Node B, gNB)).
  • AP access point
  • eNB evolved Node B
  • gNB long term evolution
  • relay stations or access points, or vehicle-mounted equipment, wearable equipment, and network equipment in the future 5G network or network equipment in the future evolved PLMN network may be relay stations or access points, or vehicle-mounted equipment, wearable equipment, and network equipment in the future 5G network or network equipment in the future evolved PLMN network.
  • the network equipment provides services in a cell
  • the terminal communicates with the network equipment through the transmission resources (for example, frequency domain resources, or time-frequency resources) of the cell.
  • the cell can be a cell corresponding to a network device (e.g. a base station).
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: metro cell, micro cell ( Micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • the random access method and device provided in the embodiments of the present application can be applied to a terminal, and the terminal includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the specific structure of the executive body of the random access method is not particularly limited in the embodiments of the present application, as long as the random access method in the embodiment of the present application can be implemented.
  • various aspects or features of the embodiments of the present application may be implemented as methods, devices, or products using standard programming and/or engineering techniques.
  • article of manufacture as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium.
  • computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • the execution subject of a random access method in this application may be a terminal, or a device that supports the terminal to implement the method, such as a device applied in a terminal, for example, a chip system.
  • the execution subject of a random access method may be a network device, or a device that supports the network device to implement the method, such as a device applied to a network device, such as a chip system.
  • the execution subject of a random access method is a terminal, and the execution subject of a random access method is a network device as an example.
  • FIG. 5B shows a random access method provided by the present application, and the method includes:
  • S501 The terminal receives first configuration information, second configuration information, and third configuration information sent by a network device.
  • the first configuration information is used to configure one or more PRACH time-frequency resources and preamble sequence sets.
  • the leader sequence set includes one or more leader sequences. That is, the network device uses the first configuration information to provide PRACH time-frequency resources and preamble sequences that can be used by the terminal in the two-step random access process.
  • the second configuration information is used to configure the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource.
  • the PUSCH time-frequency resource block includes one or more PUSCH time-frequency resources. That is, the network device configures a corresponding PUSCH time-frequency resource block for each PRACH time-frequency resource through the second configuration information, and the PUSCH time-frequency resource in the PUSCH time-frequency resource block can be specifically used for the terminal to send uplink data.
  • the third configuration information is used to configure the size of each PUSCH time-frequency resource and the corresponding relationship between the preamble sequence and the time-frequency resource of the PUSCH. That is, the network device associates each preamble sequence in each PRACH time-frequency resource with each time-frequency resource in the PUSCH time-frequency resource block through the third configuration information.
  • the terminal when the terminal selects any preamble sequence in a certain PRACH time-frequency resource to send an access preamble, it can determine the PUSCH time-frequency resource corresponding to the preamble sequence, and send uplink data on the corresponding PUSCH time-frequency resource.
  • the network device when the network device receives an access preamble sent by the terminal, the network device can determine the PUSCH time-frequency resource corresponding to the access preamble, and then obtain uplink data on the PUSCH time-frequency resource to complete the randomization of the UE.
  • the blind inspection of network equipment is reduced.
  • the network device may send a broadcast message, such as an RRC message, in which the RRC message carries the first configuration information, the second configuration information, and the third configuration information.
  • the network device may simultaneously carry the first configuration information, the second configuration information, and the third configuration information in one RRC message. It is also possible to carry part or all of any one or more of the first configuration information, the second configuration information, and the third configuration information in multiple RRC messages, which is not specifically limited in the embodiment of the present application.
  • the network device may also carry the first configuration information, the second configuration information, and the third configuration information through specific one or more messages when the terminal is in the RRC connected state.
  • the specific content contained in the first configuration information, the second configuration information, and the third configuration information will be described in detail below, and will not be repeated here.
  • S502 The terminal determines the first PRACH time-frequency resource according to the first configuration information.
  • the terminal can determine the PRACH time-frequency resource that can be used for the random access process according to the first configuration information, and select the first PRACH time-frequency resource from it.
  • S503 The terminal determines the first preamble sequence that needs to be sent on the first PRACH time-frequency resource.
  • each PRACH time-frequency resource is used to send the access preamble. Therefore, the terminal can select the first preamble sequence from the first PRACH time-frequency resource according to the first configuration information for the random access process.
  • the terminal determines the PUSCH time-frequency resource corresponding to the first preamble sequence according to the first PRACH time-frequency resource, the first preamble sequence, the second configuration information, and the third configuration information.
  • the terminal can determine the PUSCH corresponding to the first PRACH time-frequency resource according to the first PRACH time-frequency resource and the second configuration information Time-frequency resource block. Further, since the third configuration information includes the size of each PUSCH time-frequency resource, the PUSCH time-frequency resource included in the PUSCH time-frequency resource block corresponding to the first PRACH time-frequency resource can be determined. Then, according to the correspondence between the preamble sequence and the PUSCH time-frequency resource in the third configuration information, the PUSCH time-frequency resource corresponding to the first preamble sequence can be determined.
  • the terminal device may determine the PUSCH subcarrier spacing configuration according to the determined first PRACH time-frequency resource and the position relationship of the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource.
  • the subcarrier interval of the PUSCH may be the same as the subcarrier interval of the uplink BWP where the PUSCH time-frequency resource is located.
  • the PUSCH sub-carrier spacing may be the same as that of the PRACH sub-carriers.
  • the interval is the same. In this way, when the network equipment processes the signals on the PRACH time-frequency resources and the PUSCH time-frequency resources, one subcarrier interval can be used for processing in one time slot, which is beneficial to improving the processing efficiency of the network equipment.
  • S505 The terminal sends a first preamble sequence and a first message of uplink data.
  • the random access preamble is carried on the first PRACH time-frequency resource, and the uplink data is carried on the PUSCH time-frequency resource corresponding to the first PRACH time-frequency resource.
  • the solution of the present application can also be applied to other scenarios where the data channel is sent without timing synchronization. This application does not limit this.
  • S506 The terminal receives the second message sent by the network device.
  • the second message is the response of the network device to the first preamble sequence and/or the first message, and may include UE identification, random access response, conflict resolution information, TA information, etc., which is not limited in this application.
  • the terminal can determine the PUSCH time-frequency resource for the preamble sequence corresponding to the preamble sequence according to the first configuration information, the second configuration information, and the third configuration information configured by the network device. Therefore, the terminal can directly send the first message including the first preamble sequence and uplink data, which can reduce the delay of uplink data transmission.
  • the network equipment does not need to send PUSCH time-frequency resource scheduling information to each random access of the terminal, which can reduce signaling overhead.
  • the specific content of the first configuration information, the second configuration information, and the third configuration information configured by the network device are respectively described in detail below.
  • the first configuration information may include configuration information of time-domain resources of PRACH time-frequency resources, and configuration information of frequency-domain resources of PRACH time-frequency resources.
  • the terminal may use the same PRACH time-frequency resources in the two-step random access process as the four-step random access process. Since in the existing system, the network equipment is configured with PRACH time-frequency resources for the four-step random access process, the network equipment does not need to additionally configure PRACH time-frequency resources for the two-step random access process.
  • the first configuration information can be understood as the configuration information of the PRACH time-frequency resource for the four-step random access process of the network device.
  • the network device can send an RRC message to the terminal, and the IE in the RRC message carries the first configuration information.
  • the first configuration information may include the parameter prach-ConfigurationIndex, the parameter Msg 1-FrequencyStart, the parameter Msg1-FDM, and so on.
  • the network device is the PRACH time-frequency resource separately configured by Msg A in the two-step random access process.
  • the method for the network device to configure the PRACH time-frequency resource for the Msg A is the same as the method for the network device to configure the PRACH time-frequency resource for the Msg 1 in the existing system.
  • the network equipment respectively configures PRACH time-frequency resources for the four-step random access process and the two-step random access process.
  • the network device can configure the PRACH time-frequency resource corresponding to Msg1 and the PRACH time-frequency resource corresponding to MsgA through two different IEs (the field names of the IEs are different) in the RRC.
  • the first configuration information includes configuration information used by the network device to configure PRACH time-frequency resources for the MsgA.
  • the first configuration information may include the parameter prach-ConfigurationIndex, the parameter Msg A-FrequencyStart, the parameter MsgA-FDM, and so on.
  • the parameter prach-ConfigurationIndex is used to indicate the time domain resource corresponding to the PRACH time-frequency resource corresponding to MsgA.
  • the parameter Msg A-FrequencyStart is used to indicate the start position of the frequency domain resource corresponding to the PRACH time-frequency resource.
  • the parameter MsgA-FDM is used to indicate how many PRACH time-frequency resources in the same time domain resource are frequency division multiplexed.
  • the network device when the network device separately configures the PRACH time-frequency resource for the two-step random access procedure Msg A, it can also separately configure the subcarrier interval for the PRACH of the two-step random access procedure.
  • the subcarrier interval configured for the PRACH of the two-step random access process may be the same as the PRACH subcarrier interval of the four-step random access process, or may be different from the PRACH subcarrier interval of the four-step random access process.
  • the PRACH of the two-step random access process may use the same subcarrier interval as the PRACH of the four-step random access process by default.
  • the sequence number of the PRACH time-frequency resource in the two-step random access process It is the same as the frequency domain resource sequence number of the PRACH time-frequency resource in the four-step random access process, which causes confusion when calculating the RA-RNTI corresponding to the PRACH time-frequency resource.
  • the smallest frequency domain resource sequence number of the PRACH time-frequency resource of the two-step random access process can be set to be equal to the number of PRACH time-frequency resources of the four-step random access process.
  • the frequency domain resources of the PRACH time-frequency resources in the four-step random access process are numbered first, and then the frequency domain resources of the PRACH time-frequency resources in the two-step random access process are numbered.
  • the PRACH time-frequency resources configured for the four-step random access process Msg1 and the PRACH time-domain resources configured for the two-step random access process MsgA are shown in Figure 5C, where the four-step random access process
  • the number of PRACH time-frequency resources configured by Msg1 is 2, and when the frequency domain resources of the PRACH time-frequency resources configured by MsgA are numbered in the two-step random access process, the sequence number of the smallest frequency domain resource is set to 2.
  • the network device when the network device separately configures PRACH time-frequency resources for the two-step random access process Msg A, some parameters can be configured, while the unconfigured parameters (or default parameters) can be defaulted to four steps
  • the corresponding parameters configured in the random access process Msg1 are the same when configuring PRACH time-frequency resources.
  • the network device configures the frequency division multiplexing parameter MsgA-FDM for the two-step random access process, but does not configure the prach-ConfigurationIndex and the frequency domain resource start position Msg A-FrequencyStart.
  • the two-step random access process uses the same time domain resource configuration prach-ConfigurationIndex and the frequency domain resource start position Msg 1-FrequencyStart as the four-step random access process, but uses different frequency domain resources.
  • the time domain resource indicated by prach-ConfigurationIndex and the start position of the frequency domain resource indicated by Msg 1-FrequencyStart there are a total of MsgA-FDM PRACH time-frequency resources, of which the first Msg1-FDM PRACH time-frequency resources It is used for four-step random access, and the remaining MsgA-FDM minus Msg1-FDM PRACH time-frequency resources are used for two-step random access.
  • the frequency domain resources used by the four-step random access process and the two-step random access process are different, and the sequence numbers of the frequency domain resources are also different, which is beneficial to the subsequent calculation of the PRACH time-frequency resource correspondence RA-RNTI.
  • MsgA can use Msg1's prach-ConfigurationIndex and Msg1FrequencyStart by default.
  • the first two PRACH time-frequency resources are used for four-step random access, and the last two PRACH time-frequency resources are used for two-step random access.
  • the PRACH time-frequency resource configured by the network device for the four-step random access process may be the same or different from the PRACH time-frequency resource configured by the network device for the two-step random access process.
  • the PRACH time-frequency resources corresponding to the four-step random access process and the PRACH time-frequency resources corresponding to the two-step random access process may not overlap, or may overlap completely or partially.
  • the network device can blindly check the PUSCH resource corresponding to the preamble sequence (that is, using this application The position of the PUSCH resource corresponding to the preamble sequence during the two-step random access process provided by the embodiment. If uplink data is detected at the location of the PUSCH resource, the network device considers this to be a two-step random access process; otherwise, the network device considers it to be a four-step random access process. It should be noted that, in the embodiment of the present application, when the PRACH time-frequency resources corresponding to the two random access procedures overlap, the network device does not specifically limit the method for distinguishing the two random access procedures.
  • the network device may select a preamble sequence subset from the random access preamble sequence set corresponding to each PRACH time-frequency resource configured for random access in the existing system as the two-step random The PRACH random access preamble of the access process, and the remaining preamble sequence is used for the PRACH random access preamble of the four-step random access process.
  • PRACH time-frequency resources include multiple preamble sequences, of which M preamble sequences are used for random access, and each PRACH time-frequency resource corresponds to N synchronization signal blocks (Synchronization Signal BlocQ, SSB), where the network equipment is configured in There are R preamble sequences in the random access preamble sequence set corresponding to each SSB on each PRACH time-frequency resource as the PRACH random access preamble used in the contention-based random access process.
  • SSB Synchronization Signal BlocQ
  • each SSB corresponds to 1/N PRACH time-frequency resources, and the consecutive R preamble sequences starting from the preamble sequence index #0 on each PRACH time-frequency resource corresponding to SSB#0 are regarded as the same as the SSB #0 corresponds to the random access preamble of contention-based random access.
  • N SSBs correspond to 1 PRACH time-frequency resource, then on this PRACH time-frequency resource, consecutive R preamble sequences starting from preamble index #(n*M/N) are regarded as corresponding to SSB#n Random access preamble for contention-based random access.
  • M is configured through the high-level parameter totalNumberOfRA-Preambles
  • N and R are configured through the high-level parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • the network device can select Q preamble sequences from the set of random access preamble sequences corresponding to each SSB on each PRACH time-frequency resource configured for contention-based random access as the two-step random access based on contention.
  • the random access preamble used by the process. This is because there is a mapping relationship between the SSB and the preamble, and the UE needs to detect the Reference Signal Receiving Power (RSRP) of the SSB before selecting the preamble, select an SSB from the SSB whose RSRP is greater than the threshold, and then select the SSB from this SSB. Select a preamble from the corresponding preamble set to send. Therefore, dividing a subset from the preamble set mapped to the same SSB can ensure that the UE can find a corresponding two-step access preamble when selecting any SSB.
  • RSRP Reference Signal Receiving Power
  • the network device may select the first Q preambles or the last Q preambles from the random access preamble sequence set corresponding to each SSB on each PRACH time-frequency resource configured for contention-based random access, PRACH time-frequency resource as a two-step random access process.
  • each SSB corresponds to 1/N PRACH time-frequency resources, which is the same as SSB#0 Q consecutive preamble sequences starting from preamble index #0 on each corresponding PRACH time-frequency resource are used as the contention-based two-step random access random access preamble corresponding to SSB#0; when N ⁇ 1, N SSB corresponds to one PRACH time-frequency resource.
  • the consecutive Q preamble sequences starting from the preamble index #(n*M/N) are used as the contention-based two-step random access corresponding to SSB#n.
  • the first configuration information may include parameter Q, parameter M, parameter N, and parameter R in addition to parameters used when the network device configures the PRACH time-frequency resource for the random access process.
  • the parameter Q can be used to instruct the network device to select the first few preambles from the PRACH resources configured for the contention-based random access process as the PRACH time-frequency resources for the contention-based two-step random access process, and the parameter M passes the high-level parameter totalNumberOfRA -Preambles configuration, parameter N and parameter R are configured through high-level parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • each SSB corresponds to 1/N PRACH time-frequency resources, and each corresponding to SSB#0 Q consecutive preamble sequences starting from preamble index #(R-Q+1) on each PRACH time-frequency resource are used as the contention-based two-step random access random access preamble corresponding to SSB#0; when N ⁇ 1 , N SSBs correspond to 1 PRACH time-frequency resource, then on this PRACH time-frequency resource, consecutive Q preamble sequences starting from preamble index #(n*M/N+R-Q+1) are used as the same as SSB#n The corresponding random access preamble based on contention-based two-step random access.
  • the first configuration information may include parameter Q, parameter M, parameter N, and parameter R in addition to parameters used when the network device configures the PRACH time-frequency resource for the random access process.
  • the parameter Q can be used to instruct the network device to select the last few preambles from the PRACH resources configured for the contention-based random access process as the PRACH time-frequency resources for the contention-based two-step random access process, and the parameter M is passed through the high-level parameter totalNumberOfRA -Preambles configuration, parameter N and parameter R are configured through high-level parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • the network device can select the middle Q preambles from the random access preamble sequence set corresponding to each SSB on each PRACH time-frequency resource configured for random access, as the PRACH of the two-step random access process Time-frequency resources.
  • each SSB corresponds to 1/N PRACH time-frequency resources
  • the consecutive R preamble sequences starting from the preamble index #0 on each PRACH time-frequency resource corresponding to SSB#0 are regarded as the same as SSB#0
  • the corresponding random access preamble of four-step random access based on contention, Q consecutive preamble sequences starting from preamble index #R are used as the random access preamble of two-step random access corresponding to SSB#0; when N ⁇ 1
  • N SSBs correspond to 1 PRACH time-frequency resource, on this PRACH time-frequency resource, consecutive R preamble sequences starting from preamble index #(n*M/N) are regarded as the contention-based corresponding to SSB#n Random access pre
  • the first configuration information may include parameter Q, parameter M, parameter N, and parameter R in addition to parameters used when the network device configures the PRACH time-frequency resource for the random access process.
  • the parameter Q can be used to instruct the network device to select which preamble from the PRACH resources configured for the random access process as the PRACH time-frequency resource for the contention-based two-step random access process.
  • the parameter M is configured by the high-level parameter totalNumberOfRA-Preambles.
  • N and parameter R are configured through high-level parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
  • the first configuration information may also include information for configuring a set of preamble sequences in the PRACH time-frequency resource.
  • the first configuration information includes the number of preamble sequences contained in each PRACH time-frequency resource.
  • the number of preamble sequences included in each PRACH time-frequency resource can be determined by the high-level parameter totalNumberOfRA-Preambles. Then, the preamble sequence set is the first totalNumberOfRA-Preambles preamble sequences in each PRACH time-frequency resource block.
  • the number of preamble sequences contained in each PRACH time-frequency resource can be determined by the high-level parameter totalNumberOfRA-Preambles. Then, the preamble sequence set is the first totalNumberOfRA-Preambles preamble sequences in each PRACH time-frequency resource.
  • the first configuration information may include the number U of preamble sequences included in each PRACH time-frequency resource. Then, the preamble sequence set is the first U preamble sequences in each PRACH time-frequency resource.
  • the preamble sequence set includes Q preamble sequences. That is, the set of preamble sequences is the first Q or the last Q preamble sequences in each PRACH time-frequency resource.
  • the mapping relationship between each PRACH time-frequency resource and PUSCH time-frequency resource block is established according to the second configuration information.
  • the mapping relationship between each PRACH time-frequency resource and the PUSCH time-frequency resource block is first established according to the second configuration information, and then according to a predefined rule, one or more PRACH time-frequency resources form a PRACH time-frequency resource group . Since each PRACH time-frequency resource in each PRACH time-frequency resource group has established a mapping relationship with the PUSCH time-frequency resource block, it is equivalent that each PRACH time-frequency resource group has also established a mapping relationship with the PUSCH time-frequency resource block.
  • one or more PRACH time-frequency resources are first formed into a PRACH time-frequency resource group according to the second configuration information, and then the PRACH time-frequency resource group is used as a unit to be mapped to a corresponding PUSCH time-frequency resource block.
  • the first method the network device can determine the PUSCH time-frequency resource block used for uplink transmission by configuring the first mapping pattern, and the correspondence between each PRACH time-frequency resource and the PUSCH time-frequency resource block used for uplink transmission.
  • the first mapping pattern configured by the network device may also have the periodicity (that is, the mapping period).
  • the network device may configure the period T1 of the first mapping pattern, which may also be understood as the mapping period, that is, the period of configuring the PUSCH resource block using the first mapping pattern. That is, the second configuration information may include the period T1.
  • the period T1 may be the same as the PRACH period, or may be an integer multiple of the PRACH period, which is not specifically limited in the embodiment of the present application.
  • the mapping period may be the period of PRACH by default.
  • the starting position of the mapping period may be the same or different from the starting position of the PRACH period.
  • the starting position of the mapping period is different from the PRACH period, that is, there is a time domain offset between the starting position of the mapping period and the starting position of the PRACH period.
  • the specific size of the time domain offset may be configured by the network device, or may be predefined.
  • one PRACH cycle is one radio frame as an example for description.
  • the time domain offset between the mapping period and the PRACH period is 1 time slot.
  • FIG. 5E also shows the PRACH time-frequency resources in the PRACH period and the PUSCH time-frequency resource blocks mapped to each PRACH time-frequency resource. It can be seen that the PRACH time-frequency resource located in the last time slot in the PRACH period can be located in the same mapping period as the PUSCH time-frequency resource block to which it is mapped.
  • time domain offset when the time domain offset is not predefined, and the network device is not configured with the time domain offset, the time domain offset may be defaulted to be zero.
  • the second configuration information includes information of the first mapping image.
  • the first mapping pattern is used to determine time domain resources and frequency domain resources of at least one PUSCH time-frequency resource block.
  • a first mapping pattern is a mapping rule included in a mapping period (ie, period T1).
  • the mapping rule here includes the configuration information of time domain resources and the configuration information of frequency domain resources, so it can also be called a mapping two-tuple.
  • the first mapping pattern may include one or more mapping 2-tuples.
  • Each mapping of a mapping two-tuple can be used to determine the time-frequency resources and frequency-domain resources of a PUSCH time-frequency resource block, that is, a mapping two-tuple includes the time-frequency resources of a PUSCH time-frequency resource block Configuration information and frequency domain resource configuration information.
  • a mapping two-tuple may be expressed as ( ⁇ K, S, L ⁇ , ⁇ RB start , L RBs ⁇ ), and the embodiment of the present application does not limit the representation form of the mapping two-tuple.
  • a mapping two-tuple can also only contain the time-domain resource configuration information of one PUSCH time-frequency resource block, then the frequency-domain resource of the PUSCH time-frequency resource block can be the same as that of the PRACN resource, or It has a preset relationship with the frequency domain resource of the PRACH time-frequency resource, or is a default frequency domain resource.
  • a mapping two-tuple may also only contain the configuration information of the frequency domain resources of a PUSCH time-frequency resource block, then the time domain resources of the PUSCH time-frequency resource block may be the same as the time domain resources of the PRACN resource, or the same as the PRACH
  • the time-domain resource of the time-frequency resource has a preset relationship or is a default time-domain resource. The embodiments of this application do not limit this.
  • mapping two-tuple is used to configure the time-frequency resources of the PUSCH time-frequency resource block
  • the time-frequency resource configuration information of the PUSCH time-frequency resource block may include: a time offset relative to the PRACH time-frequency resource, and the length of the time-domain resource of each PUSCH time-frequency resource block.
  • the time offset relative to the PRACH time-frequency resource may be: the sequence number of the time slot where the first symbol of the PUSCH time-frequency resource block is located and the first time occupied by the corresponding PRACH time-frequency resource
  • the length of the time domain resource of each PUSCH time-frequency resource block may be the number of consecutive symbols L occupied by each PUSCH time-frequency resource block.
  • the K value can be positive, negative and zero.
  • the time-domain resource configuration of the PUSCH time-frequency resource block is based on the first time slot occupied by the PRACH time-frequency resource or the last time slot occupied by the PRACH time-frequency resource is defined in the standard. Yes, it can also be pre-arranged by the network equipment and the UE, or the network equipment can notify the UE through indication information.
  • the indication information can be high-level signaling, such as RRC messages, or layer 1 and layer 2 indication signaling, such as media intervention Control (media access control, MAC)-control element (CE) signaling, or Downlink Control Information (DCI).
  • a table containing the relationship of K, L, and S may be predefined in the standard, as shown in Table 7. Then, the time-domain resource configuration information of the PUSCH time-frequency resource block sent by the network device to the terminal may specifically be the row index in Table 7. After receiving the row sequence number, the terminal can look up the values of K, S, and L corresponding to the row sequence number according to Table 7 to determine the time domain resources of the PUSCH time-frequency resource block. It should be noted that the values in Table 7 are only examples, and the values of K, S and L can also be other values, which are hereby explained.
  • the network device when the network device sends the time-domain resource configuration information of the PUSCH time-frequency resource block to the UE, it may also include at least two parameters K and startSymbolAndLength in the RRC information unit.
  • the UE can calculate the values of S and L according to the value of K and the parameter startSymbolAndLength through the following rules.
  • the network device when the network device sends the time-domain resource configuration information of the PUSCH time-frequency resource block to the UE, it may also include at least three parameters K, S, and L in the RRC information unit.
  • the network device when the network device sends the time-domain resource configuration information of the PUSCH time-frequency resource block to the UE, it may also include at least one or more parameters of K, S, and L in the RRC information unit. For example, if the RRC information element only contains S and L, it can be assumed that the first symbol of the PUSCH time-frequency resource block is located in the first available time slot after the time-domain resource occupied by the PRACH time-frequency resource.
  • the UE side obtains the time-domain resource configuration information K, S, and L of the PUSCH time-frequency resource block, and can determine the sequence number of the starting time slot of the PUSCH time-frequency resource block, the sequence number of the starting symbol, and the PUSCH time-frequency The symbol length occupied by the resource block. That is, the time domain resource corresponding to the PUSCH time-frequency resource block can be determined.
  • the starting time slot of the PUSCH time-frequency resource block determined above is (n ⁇ )+K, where n is the sequence number of the first time slot occupied by the PRACH time-frequency resource (or the last time slot Sequence number), where the sequence number of the PRACH time slot refers to the calculation according to the subcarrier interval assumed according to the frequency range.
  • ⁇ is a parameter calculated based on the PUSCH subcarrier interval and the subcarrier interval assumed when numbering the PRACH time slot.
  • the description of the time slot number of PRACH time-frequency resource configuration is FR1 (Frequency Range 1), the sub-carrier interval assumed by the time-frequency resource configuration time slot number of PRACH It is 15kHz; when the spectrum range is FR2, the subcarrier interval assumed by the PRACH time-frequency resource configuration slot number is 60kHz.
  • the network device may pre-configure a table of the correspondence between different PUSCH subcarrier intervals and the value of ⁇ . As shown in Table 8, the UE may obtain the value of ⁇ by looking up the table. Among them, ⁇ msgAPUSCH is the subcarrier spacing of PUSCH resources.
  • the UE may also calculate the value of ⁇ through formula (1).
  • the starting time slot of the PUSCH time-frequency resource block determined above is n+K.
  • mapping two-tuple is used to configure the frequency domain resources of the PUSCH time-frequency resource block
  • the optional range of the frequency domain resources of the PUSCH time-frequency resource block may be configured first.
  • the optional range of the frequency domain resources of the PUSCH time-frequency resource block can be configured within the frequency domain resource range of the uplink BWP, or it can be configured within the frequency domain resource range of the PRACH time-frequency resource associated with the PUSCH time-frequency resource block , And can also be configured in the frequency domain resource range of the PRACH time-frequency resource group associated with the PUSCH time-frequency resource block.
  • the optional range of the PUSCH frequency domain resources may also be predefined, which is not limited in the embodiment of the present application.
  • the size of the optional range of the configured PUSCH frequency domain resources may affect the length of the PUSCH frequency domain resource configuration information.
  • the selectable range of the PUSCH frequency domain resource is relatively large, the length of configuration information required to determine the PUSCH frequency domain resource from the relatively large range is relatively large.
  • the selectable range of the PUSCH frequency domain resource is small, the length of the configuration information that needs to be used to determine the PUSCH frequency domain resource from the small range is small.
  • the number of RBs in the selectable range of the PUSCH frequency domain resource is Y
  • log 2 The frequency domain resource configuration information of (Y*(Y+1))/2) bits is used to specify one of the above possible combinations.
  • the selectable range is 6 RB
  • the number of bits required for the configuration information is at least 5 bits.
  • the selectable range is 2 RB
  • the size of the number of bits required for frequency domain configuration information can be known.
  • the selectable range is larger, the length of the required PUSCH frequency domain resource configuration information is larger.
  • the selectable range is small, the length of the required PUSCH frequency domain resource configuration information is small.
  • the configuration information of the same frequency domain resources is subsequently interpreted differently.
  • the starting resource block (resource block, RB) sequence number RB start of the frequency domain resource configuration information can be interpreted as being currently activated
  • the first RB of the upstream bandwidth part (BWP) starts to be numbered.
  • the currently activated BWP may be the initial BWP.
  • the RB start of the frequency domain resource configuration information can be interpreted as being related to the PUSCH
  • the first RB number of the PRACH time-frequency resource associated with the time-frequency resource block is numbered.
  • the optional range of the PUSCH time-frequency resource block may be defaulted to be within the frequency domain resource range of the uplink BWP.
  • the selectable range of the frequency domain resource block of the PUSCH is within the frequency domain resource range of the uplink BWP.
  • the configuration information of the frequency domain resources of the PUSCH time-frequency resource block includes the start resource block (resource block, RB) sequence number RB start of the PUSCH time-frequency resource block, and the PUSCH time-frequency resource block occupies continuous The number of RBs L RBs .
  • the starting RB is numbered starting from the first RB of the currently activated uplink bandwidth part (BWP).
  • the currently activated BWP may be the initial BWP.
  • the PUSCH time-frequency resource block and the PRACH time-frequency resource can be on the same BWP or on different BWPs.
  • a possible implementation manner for the network device to configure RB start and L RBs is that the network device includes at least the parameter startRBAndLength in the RRC information element.
  • the UE can calculate RB start and L RBs according to the following rules, as follows:
  • the network device includes at least the parameters RB start and L RBs in the RRC information unit.
  • the configuration information of the frequency domain resources of the PUSCH time-frequency resource block includes the offset value RB offset between the sequence number of the start RB of the PUSCH time-frequency resource block and the sequence number of the start RB of the PRACH time-frequency resource, and
  • the PUSCH time-frequency resource block occupies the number of consecutive RBs L RBs .
  • the position of the frequency domain resource of the PUSCH time-frequency resource block can be determined according to the L RBs .
  • the second configuration information may further include a parameter N 1 , and the parameter N 1 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource. That is, each PRACH time-frequency resource corresponds to N 1 PUSCH time-frequency resource blocks.
  • the network device can determine the position and size of the PUSCH time-frequency resource block according to the configured parameter N 1 and the preset mapping sequence of the PRACH time-frequency resource to the PUSCH time-frequency resource block, and determine the PRACH The mapping relationship between time-frequency resources and PUSCH time-frequency resource blocks. Then, the PRACH time-frequency resource group is determined according to the predefined rules, and the PUSCH time-frequency resource block corresponding to each PRACH time-frequency resource group is determined, so that the preamble and PUSCH time in the PRACH time-frequency resource group are subsequently performed according to the third configuration information. The time-frequency resources in the frequency resource block are further mapped.
  • the predefined rule for determining the PRACH time-frequency resource group may be that each PRACH time-frequency resource is a PRACH time-frequency resource group by default, that is, the PRACH time-frequency resource is used as a unit to map the PUSCH time-frequency resource block. It may also be that PRACH time-frequency resources located in the same PRACH time-domain resource form a PRACH time-frequency resource group, or PRACH time-frequency resources located in the same time slot may form a PRACH time-frequency resource group. It may also be that PRACH time-frequency resources located in multiple consecutive time slots in the time domain form a PRACH time-frequency resource group. It is also possible to use the same PRACH time-frequency resource mapped to the two-tuple to form a PRACH time-frequency resource group. The embodiment of the application does not specifically limit the predefined rules for determining the PRACH time-frequency resource group.
  • each PRACH time-frequency resource when each PRACH time-frequency resource is mapped using one mapping two-tuple, one PUSCH time-frequency resource block is obtained. Then, each PRACH time-frequency resource corresponds to N 1 PUSCH time-frequency resource blocks. It can also be understood that each PRACH time-frequency resource uses N 1 mapping two-tuples for mapping, so the N corresponding to the PRACH time-frequency resource is obtained. 1 PUSCH time-frequency resource block.
  • the PUSCH time-frequency resource block used for uplink transmission can also be understood as a PUSCH resource group, that is, the PRACH time-frequency resource is mapped using N 1 mapping two-tuples to obtain the N corresponding to the PRACH time-frequency resource. 1 PUSCH resource group.
  • mapping is performed according to the preset mapping order of the PRACH time-frequency resource to the PUSCH time-frequency resource block.
  • the preset mapping sequence of the PRACH time-frequency resources to the PUSCH time-frequency resource blocks can be understood as mapping in the order of the sequence numbers of the PRACH time-frequency resources.
  • the mapping may be performed in the ascending order of the sequence numbers of the PRACH time-frequency resources, where the ascending order of the sequence numbers of the PRACH time-frequency resources may be first in the ascending order of the sequence numbers of the frequency domain resources, and then in the ascending order of the sequence numbers of the time domain resources.
  • the network device configures the first mapping pattern for the terminal, the first mapping pattern includes one or more mapping two-tuples. At this time, when the first mapping pattern contains multiple mapping two-tuples, it is equivalent to that the network device also configures the order of the multiple mapping two-tuples.
  • each PRACH time-frequency resource is mapped using N 1 mapping two-tuples, it is mapped according to the preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks, which includes at least two meanings: one is every The sequence of the mapping of PRACH time-frequency resources, that is, which PRACH time-frequency resource is mapped first, and which PRACH time-frequency resource is mapped later.
  • the second is that when each PRACH time-frequency resource is mapped, N 1 mapping two-tuples are selected for mapping according to the order of mapping two-tuples in the first mapping pattern. That is, when each PRACH time-frequency resource is mapped, which N 1 mapping two-tuples are selected for mapping.
  • the network device is configured with the PRACH time-frequency resource as shown in FIG. 5A, and the first mapping pattern includes two mapping two-tuples as an example, and an exemplary description is given in conjunction with the accompanying drawings.
  • the mapping two-tuple represents the mapped PUSCH time-frequency resource block
  • the time slot where the first symbol is located is the first time slot after the time slot occupied by the PRACH time-frequency resource, here it is a subframe
  • the start symbol is symbol #0, which occupies 14 symbols, that is, one subframe .
  • the starting RB is #12RB, which occupies 6RB.
  • mapping two-tuple ( ⁇ 2,0,14 ⁇ 6,6 ⁇ ) is the second mapping two-tuple.
  • the mapping two-tuple indicates that the time slot where the first symbol of the mapped PUSCH time-frequency resource block is located is in the second time slot after the time slot occupied by the PRACH time-frequency resource, which is a subframe here, and the start symbol It is symbol #0, which occupies 14 symbols, that is, one subframe.
  • the starting RB is #6RB, which occupies 6RB.
  • the sequence number of the first time slot occupied by the PRACH time-frequency resource is the same as the sequence number of the last time slot.
  • the sequence number of the first time slot occupied by the PRACH time-frequency resource is used as a reference to calculate the time-domain resource of the PUSCH time-frequency resource block.
  • FIG. 6 when the network device is configured When, it means that a PRACH time-frequency resource mapping is used
  • One mapping two-tuple that is, two PRACH time-frequency resources use one mapping two-tuple.
  • PRACH time-frequency resource #0 uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #1 also uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #2 uses the second mapping two-tuple for mapping
  • PRACH time-frequency resource #3 also uses the second mapping two-tuple for mapping.
  • the PUSCH time-frequency resource block obtained after the mapping, and the corresponding relationship between the PRACH time-frequency resource and the time-frequency resource are shown in FIG. 6.
  • PRACH time-frequency resource #0 uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #1 uses the second mapping two-tuple for mapping
  • PRACH time-frequency resource #2 cyclically uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #3 uses the second mapping two-tuple for mapping.
  • the PUSCH time-frequency resource block obtained after mapping, and the corresponding relationship between the PRACH time-frequency resource and the time-frequency resource are shown in FIG. 7.
  • the first mapping pattern contains 4 mapping 2-tuples as an example for description.
  • the first mapping pattern is
  • N 1 2 configured by the network device, it means that two mapping two-tuples are used when mapping a PRACH time-frequency resource.
  • PRACH time-frequency resource #0 uses the first and second mapping two-tuple for mapping
  • PRACH time-frequency resource #1 uses the third and fourth mapping two-tuple for mapping
  • PRACH time-frequency resource #2 cyclically uses the first and second mapping two-tuple for mapping
  • PRACH time-frequency resource #3 uses the third and fourth mapping two-tuple for mapping.
  • the PUSCH time-frequency resource block obtained after the mapping, and the corresponding relationship between the PRACH time-frequency resource and the time-frequency resource are shown in FIG. 8.
  • FIGS. 6 to 8 are all described by taking the same mapping period as the PRACH period (the period of the PRACH time-frequency resource) as an example. It is also mentioned above that the mapping period can also be an integer multiple of the PRACH period. Then, during the mapping, all PRACHs in the mapping period are mapped according to the preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks, and the sequence of mapping two-tuples in the first mapping pattern.
  • the mapping method Similarly, the following description takes the mapping period as 2 times the PRACH period as an example.
  • mapping period is twice the PRACH period, that is, the mapping period is 20 ms
  • the rest of the configuration information is the same as in FIG. 6.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 are mapped using the first mapping two-tuple
  • PRACH time-frequency resource #2 and PRACH time-frequency resource #3 Use the second mapping two-tuple for mapping.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 use the first mapping two-tuple for mapping
  • PRACH time-frequency resource #2 and PRACH time-frequency resource #3 use the second mapping Two tuples are mapped.
  • the PUSCH time-frequency resource block obtained after the mapping, and the corresponding relationship between the PRACH time-frequency resource and the time-frequency resource are shown in FIG. 9.
  • the PRACH time-frequency resources use the same mapping two-tuple.
  • PRACH time-frequency resources# To PRACH time-frequency resources# Use the mapping two-tuple #modulo(g, G), where g is the sequence number of the mapping two-tuple in the first mapping pattern, and G represents the number of mapping two-tuples in the first mapping pattern.
  • N 1 1
  • one PRACH time-frequency resource uses one mapping two-tuple.
  • the PRACH time-frequency resource #g is mapped to the mapping two-tuple #modulo(g, G).
  • one PRACH time-frequency resource uses N 1 mapping two-tuples. Specifically, PRACH opportunity #g is mapped to the mapping two-tuple #modulo(g ⁇ N 1 , G) to #modulo((g+1) ⁇ N 1 -1, G).
  • each PRACH time-frequency resource is a PRACH time-frequency resource group by default, for example: PRACH time-frequency resource #n constitutes a PRACH time-frequency resource group# in Figures 6 to 9 n, the sequence of the PRACH time-frequency resource group is the same as the sequence of the PRACH time-frequency resource.
  • the predefined rule is that PRACH time-frequency resources located in the same PRACH time-domain resource form a PRACH time-frequency resource group, or PRACH time-frequency resources located in the same time slot form a PRACH time-frequency resource group
  • PRACH time domain resource #0 and PRACH time domain resource #1 are located in the same PRACH time domain resource and also in the same time slot, then PRACH time-frequency resource #0 and PRACH time-frequency resource #1 can form a PRACH time-frequency resource group
  • PRACH time-domain resource #2 and PRACH time-domain resource #3 are located in the same PRACH time-domain resource and also in the same time slot, then PRACH time-frequency resource #2 and PRACH time-frequency resource #3 can form a PRACH time-frequency resource group;
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 use the same mapping two-tuple, then PRACH time-frequency resource #0 and PRACH time-frequency resource #1 can form a PRACH time-frequency resource group, which is a PRACH time-frequency resource group Resource group #0; PRACH time-frequency resource #2 and PRACH time-frequency resource #3 can form a PRACH time-frequency resource group, which is PRACH time-frequency resource group #1.
  • N 1 1 as shown in FIG.
  • each PRACH time-frequency resource in the mapping period can be a PRACH time-frequency resource group, and the sequence of the PRACH time-frequency resource group is the same as the sequence of the PRACH time-frequency resource.
  • N 1 >1
  • each PRACH time-frequency resource in the mapping period can be a PRACH time-frequency resource group, and the sequence of the PRACH time-frequency resource group is the same as the sequence of the PRACH time-frequency resource.
  • the second configuration information may further include a parameter N 2 and a parameter N 3 , where the parameter N 2 is used to configure a PRACH time-frequency resource group included in a PRACH time-frequency resource group.
  • the number of frequency resources, the parameter N 3 is used to determine the number of PUSCH time-frequency resource blocks corresponding to each PRACH time-frequency resource group.
  • the PRACH time-frequency resource group can be determined, and then the PRACH time-frequency resource group can be used for mapping to obtain each PRACH time-frequency resource group.
  • the preamble in the PRACH time-frequency resource group may be further mapped with the time-frequency resource in the PUSCH time-frequency resource block according to the third configuration information.
  • the sequence of the PRACH time-frequency resource group can be further determined according to the sequence of the PRACH time-frequency resource contained in the PRACH time-frequency resource group. That is, the sequence of the PRACH time-frequency resource group may be determined according to the sequence of the frequency domain resources and the sequence of the time domain resources of the included PRACH time-frequency resources. For example, the sequence of the PRACH time-frequency resource group may be sorted according to the ascending order of the frequency domain resources of the included PRACH time-frequency resources, and then according to the ascending order of the time domain resources of the included PRACH time-frequency resources.
  • the sequence of the PRACH time-frequency resource group is similar to the sequence of the PRACH time-frequency resource, and will not be repeated here.
  • the mapping may be performed according to the mapping order of the PRACH time-frequency resource group to the PUSCH time-frequency resource block, and the order of mapping the two-tuple in the first mapping pattern.
  • the mapping sequence of the PRACH time-frequency resource group to the PUSCH time-frequency resource block can be understood as the sequence of the PRACH time-frequency resource group.
  • a PRACH time-frequency resource group is configured by a network device to include two PRACH time-frequency resources, then according to the order of the PRACH time-frequency resources, the 4 PRACH time-frequency resources in a PRACH period can be divided into 2 PRACH Time-frequency resource group, PRACH time-frequency resource group #0 and PRACH time-frequency resource group #1.
  • PRACH time-frequency resource group #0 and PRACH time-frequency resource group #1 use the mapping two-tuple in the first mapping pattern according to the mapping order.
  • the mapping period is the same as the PRACH period, both are 10ms
  • both the PRACH time-frequency resource group #0 and the PRACH time-frequency resource group #1 use this mapping two-tuple for mapping. It can be seen that PRACH time-frequency resource group #0 corresponds to PUSCH time-frequency resource block #0, and PRACH time-frequency resource group #1 corresponds to PUSCH time-frequency resource block #1.
  • mapping period is the same as the PRACH period, both 10ms
  • the mapping two-tuple only contains time-domain resource information, so it can be assumed that the frequency-domain resources of the mapped PUSCH time-frequency resource block are the same as the frequency-domain resources of the PRACH time-frequency resource group.
  • both the PRACH time-frequency resource group #0 and the PRACH time-frequency resource group #1 use the mapping two-tuple for mapping.
  • PRACH time-frequency resource group #0 corresponds to PUSCH time-frequency resource block #0
  • PRACH time-frequency resource group #1 corresponds to PUSCH time-frequency resource block #1.
  • mapping period is the same as the PRACH period, both are 10 ms, and the first mapping pattern contains two mapping 2-tuples, for example:
  • PRACH time-frequency resource group #0 uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource group #1 uses the second mapping two-tuple for mapping. It can be seen that PRACH time-frequency resource group #0 corresponds to PUSCH time-frequency resource block #0, and PRACH time-frequency resource group #1 corresponds to PUSCH time-frequency resource block #1.
  • mapping period is twice the PRACH period, that is, 20ms
  • first mapping pattern contains four mapping 2-tuples, for example:
  • the PRACH time-frequency resource group #0 uses the first mapping two-tuple for mapping to obtain the PUSCH time-frequency resource block #0.
  • the PRACH time-frequency resource group #1 uses the second mapping two-tuple for mapping to obtain the PUSCH time-frequency resource block #1.
  • PRACH time-frequency resource group #2 uses the third mapping two-tuple for mapping to obtain PUSCH time-frequency resource block #2.
  • the PRACH time-frequency resource group #3 uses the fourth mapping two-tuple for mapping to obtain the PUSCH time-frequency resource block #3.
  • the second method first configure the periodic PUSCH time-frequency resource block, and then configure the periodic mapping rule, that is, the second mapping pattern, so that the periodic PRACH time-frequency resource is mapped to the periodic PUSCH time-frequency resource block.
  • the second mapping pattern configured by the network device may also be periodic (that is, the mapping cycle).
  • the network device may configure the period T3 of the second mapping image, which may also be understood as the mapping period, that is, the period of configuring the PUSCH resource block using the second mapping pattern. That is, the second configuration information may include the period T3.
  • the period T3 may be the same as the PRACH period, or may be an integer multiple of the PRACH period, which is not specifically limited in the embodiment of the present application.
  • the mapping period can be the PRACH period by default.
  • the starting position of the mapping period may be the same or different from the starting position of the PRACH period.
  • the starting position of the mapping period is different from the PRACH period, that is, there is a time domain offset between the starting position of the mapping period and the starting position of the PRACH period.
  • the specific size of the time domain offset may be configured by the network device, or may be predefined. When the time domain offset is not predefined, and the network device is not configured with the time domain offset, the time domain offset can be defaulted to be zero.
  • the second configuration information may further include the period T2 of the PUSCH time-frequency resource block, the configuration information of the time domain resource of the PUSCH time-frequency resource block, and/or the configuration information of the frequency domain resource.
  • the time-domain resource configuration information of the PUSCH time-frequency resource block includes at least a time-domain offset relative to the radio frame #0, a starting symbol sequence number, and the number of consecutive symbols occupied in a period.
  • the configuration information of the frequency domain resources of the PUSCH time-frequency resource block includes at least the starting RB sequence number and the number of consecutive RBs occupied in one period.
  • the starting RB sequence number is numbered from the first RB of the currently activated BWP.
  • the currently activated BWP may be the initial BWP.
  • the PUSCH time-frequency resource block and the PRACH time-frequency resource may be in the same BWP or in different BWPs, which is not limited in the embodiment of the present application.
  • the second configuration information may also include the time-domain resource configuration information of the PUSCH time-frequency resource block, and there is no frequency-domain resource configuration information, then the frequency domain resources of the PUSCH time-frequency resource block and PRACH time may be defaulted.
  • the frequency domain resources of the frequency resources are the same or have a preset relationship with the frequency domain resources of the PRACH time-frequency resources.
  • the second configuration information may also include the configuration information of the frequency domain resources of the PUSCH time-frequency resource block.
  • the time domain resources of the PUSCH time-frequency resource block and PRACH time-frequency resources can be defaulted.
  • the time domain resources of are the same, or have a preset relationship with the time domain resources of the PRACH time-frequency resource, or are the default time domain resources.
  • the network device may also configure the optional range of the frequency domain resource of the PUSCH time-frequency resource.
  • the optional range of the frequency domain resources of the PUSCH time-frequency resource block can be configured within the frequency domain resource range of the uplink BWP, or it can be configured within the frequency domain resource range of the PRACH time-frequency resource associated with the PUSCH time-frequency resource block , And can also be configured in the frequency domain resource range of the PRACH time-frequency resource group associated with the PUSCH time-frequency resource block.
  • the optional range of PUSCH frequency domain resources may also be predefined, which is not limited in the embodiment of the present application. For other content, please refer to the description of related content in the first method, which will not be repeated here.
  • the network device may also be configured with multiple groups (two groups or more) of PUSCH time-frequency resource blocks. That is, the second configuration information may also include the configuration information of multiple groups of PUSCH time-frequency resource blocks, and the configuration information of each group of PUSCH time-frequency resource blocks may include the period of the group of PUSCH time-frequency resource blocks and the time-frequency resource block of PUSCH. Configuration information of domain resources and/or configuration information of frequency domain resources. It can also be understood that the second configuration information may include the period T2 of multiple PUSCH time-frequency resource blocks, and the configuration information and/or frequency domain resource configuration information of the corresponding PUSCH time-frequency resource block in each period T2. information.
  • the PUSCH time-frequency resource block numbered #0 is the 0th group of PUSCH time-frequency resource blocks.
  • the PUSCH time-frequency resource block numbered #1 is the first group of PUSCH time-frequency resource blocks.
  • the periods of the multiple sets of PUSCH time-frequency resource blocks, the configuration information of the time domain resources, and/or the configuration information of the frequency domain resources may be the same or different.
  • the period of the multiple sets of PUSCH time-frequency resource blocks, the configuration information of the time domain resources, and/or the configuration information of the frequency domain resources may default to any one or several parameter configurations. If any one or any of the parameters in the configuration information of a certain group of PUSCH time-frequency resource blocks is defaulted, it can be defaulted that the group of PUSCH time-frequency resource blocks use the corresponding values configured for other groups of PUSCH time-frequency resource blocks. If the configuration information of the multiple sets of PUSCH time-frequency resource blocks are all default, the configuration information of the multiple sets of PUSCH time-frequency resource blocks and the configuration information of the PRACH time-frequency resource can be defaulted.
  • the second configuration information contains the configuration information of 2 groups of PUSCH time-frequency resource blocks, but only one group of PUSCH time-frequency resource blocks is configured with period T2, and the remaining group of PUSCH time-frequency resource blocks has no period in the configuration information.
  • the second configuration information contains the configuration information of two sets of PUSCH time-frequency resource blocks, but the configuration information of the two sets of PUSCH time-frequency resource blocks has no period configuration information, then the periods of the two sets of PUSCH time-frequency resource blocks are both The corresponding PRACH resource period.
  • the second configuration information may also include the information of the DMRS port associated with the PUSCH time-frequency resource block. This is because for PUSCH time-frequency resource blocks with the same time-domain resource and frequency-domain resource, if the associated DMRS port is different, the network device can also recognize that this is a different PUSCH resource. In other words, a PUSCH resource can be determined by using the information of time domain resources, frequency domain resources, and DMRS ports. Therefore, when the network device configures the PUSCH time-frequency resource block, the DMRS information associated with the PUSCH time-frequency resource block may also be configured, that is, the second configuration information includes the DMRS configuration information.
  • the DMRS port information includes any one or several of the following parameters: DMRS type, additional DMRS location, number of time domain symbols occupied by the DMRS, and scrambling code ID.
  • the scrambling code ID or reference signal ID is used to generate DMRS sequences, that is, different scrambling code IDs or reference signal IDs can generate different DMRS sequences.
  • the UE can use the ID of the cell where it is located.
  • the network device can configure one or more scrambling code IDs or reference signal IDs through the indication information to increase the number of DMRS ports associated with the PUSCH time-frequency resource, thereby reducing the probability of DMRS collision.
  • the indication information can be high-level signaling, such as RRC messages, or level 1 and layer 2 indication signaling, such as MAC CE or DCI.
  • the mapping relationship between each PRACH time-frequency resource and the PUSCH time-frequency resource block can be further configured in a mapping period.
  • the second configuration information may further include a parameter N 4 , and the parameter N 4 is used to determine the number of each PRACH time-frequency resource mapped to the PUSCH time-frequency resource block.
  • the second configuration information can establish a mapping relationship between the configured PRACH time-frequency resource and the PUSCH time-frequency resource block through the configuration parameter N 4 and a preset mapping sequence, and then it can be determined according to a predefined rule PRACH time-frequency resource group. Since the PRACH time-frequency resource in the PRACH time-frequency resource group has established a mapping relationship with the PUSCH time-frequency resource block, it is also equivalent to that the PRACH time-frequency resource group has also established a mapping relationship with the PUSCH time-frequency resource block.
  • the predefined rule for determining the PRACH time-frequency resource group may be that each PRACH time-frequency resource is a PRACH time-frequency resource group by default, that is, the PRACH time-frequency resource is used as a unit to map the PUSCH time-frequency resource block. It may also be that PRACH time-frequency resources located in the same PRACH time-domain resource form a PRACH time-frequency resource group, or PRACH time-frequency resources located in the same time slot may form a PRACH time-frequency resource group. It may also be that PRACH time-frequency resources located in multiple consecutive time slots in the time domain form a PRACH time-frequency resource group. It may also be that PRACH time-frequency resources mapped to the same PUSCH time-frequency resource block form a PRACH time-frequency resource group. The embodiment of this application does not specifically limit the rules for determining the PRACH time-frequency resource group.
  • each PRACH time-frequency resource is mapped according to a preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks. For example, in a mapping period, the mapping is performed in the ascending order of the sequence number of the frequency domain resources first and then the ascending sequence of the sequence number of the time domain resources.
  • the sequence equivalent to the PUSCH time-frequency resource block is also determined, which can be determined according to the sequence in which the PUSCH time-frequency resource block occupies time domain resources. For example, it can be sorted according to the ascending order of the time domain resources occupied by the PUSCH time-frequency resource blocks.
  • the mapping is performed according to the preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks, which includes at least two meanings: one is every The sequence of the mapping of PRACH time-frequency resources, that is, which PRACH time-frequency resource is mapped first, and which PRACH time-frequency resource is mapped later.
  • the second is that when each PRACH time-frequency resource is mapped, it is mapped to N 4 PUSCH time-frequency resource blocks in the order of PUSCH time-frequency resource blocks. That is, the N 4 time-frequency resource blocks to which each PRACH time-frequency resource is mapped.
  • a mapping period when the number of PRACH time-frequency resources is greater than the number of PUSCH time-frequency resource blocks, it means that when PRACH time-frequency resources are mapped in a preset mapping order, they will be cyclically mapped to PUSCH time-frequency resources Block until all PRACH time-frequency resources in the mapping period are mapped to at least one PUSCH time-frequency resource block.
  • a mapping period includes PUSCH time-frequency resource block #0 and PUSCH time-frequency resource block #1, PRACH time-frequency resource #0 and PRACH time-frequency resource #3.
  • PRACH time-frequency resource #0 is mapped to PUSCH time-frequency resource block #0
  • PRACH time-frequency resource #1 is mapped to PUSCH time-frequency resource block #1
  • PRACH time-frequency resource #3 is mapped, it will be mapped to PUSCH.
  • Frequency resource block #0 When PRACH time-frequency resource #3 is mapped, it will be mapped to PUSCH time-frequency resource block #1.
  • each PRACH cycle contains 4 PRACH time-frequency resources.
  • the PUSCH time-frequency resource blocks included in each PRACH cycle may be different.
  • one PRACH cycle contains 4 PUSCH time-frequency resource blocks, and another PRACH cycle contains 3 PUSCH time-frequency resource blocks.
  • the sequence of the PUSCH time-frequency resource block may be determined according to the sequence number of the time-domain resources of the PUSCH time-frequency resource block.
  • description is made by taking the order of PUSCH time-frequency resource blocks in ascending order of the time-domain resources of the PUSCH time-frequency resource blocks as an example.
  • Figure 16 shows the mapping relationship between PRACH time-frequency resources and PUSCH time-frequency resource blocks in two mapping periods.
  • the mapping period configured by the network device is the same as the PRACH period.
  • N 4 1/2 configured by the network device, it means that each PRACCH resource is mapped to 1/2 PUSCH time-frequency resource block, that is, every 2 PRACH time-frequency resource is mapped to one PUSCH time-frequency resource block.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 are mapped to PUSCH time-frequency resource block #0 in one mapping period.
  • PRACH time-frequency resource #2 and PRACH time-frequency resource #3 are mapped to PUSCH time-frequency resource block #1.
  • the mapping method in another mapping cycle is similar, and will not be repeated here.
  • the second configuration information may also include information about some mapping rules, that is, the network device may also configure some mapping rules, for example: PRACH time-frequency resources are mapped to PUSCH time-frequency resource blocks corresponding to themselves, in the time domain Can not overlap.
  • the PRACH time-frequency resource and the PUSCH time-frequency resource block corresponding to its own mapping cannot overlap in the frequency domain.
  • the mapping rule may also be predefined, that is, no network device is required to configure it. The embodiments of this application do not limit this.
  • the parameter N 4 is used to determine the number of effective PUSCH time-frequency resource blocks mapped to each PRACH time-frequency resource.
  • the effective PUSCH time-frequency resource block is a PUSCH time-frequency resource block that complies with the mapping rule.
  • the mapping method for mapping each PRACH time-frequency resource to a valid PUSCH time-frequency resource block is the same as the above method, and will not be repeated here.
  • FIG. 17 shows the mapping relationship between PRACH time-frequency resources and PUSCH time-frequency resource blocks in two mapping periods.
  • the mapping period configured by the network device is the same as the PRACH period, and a mapping rule is configured: the PRACH time-frequency resource and the PUSCH time-frequency resource block corresponding to its own mapping cannot overlap in the time domain.
  • N 4 1 configured by the network device, it means that each PRACCH resource is mapped to one PUSCH time-frequency resource block.
  • the PRACH time-frequency resource #0 is mapped to the PUSCH time-frequency resource block #0 in one mapping period.
  • PRACH time-frequency resource #1 is mapped to PUSCH time-frequency resource block #1.
  • the PRACH time-frequency resource #2 should be mapped to the PUSCH time-frequency resource block #2 according to the mapping order. Since PUSCH time-frequency resource block #2 and PRACH time-frequency resource #2 are located in the same time domain, PRACH PUSCH time-frequency resource block #2 is mapped backward and mapped to PUSCH time-frequency resource block #3. PRACH time-frequency resource #3 continues to be mapped to PUSCH time-frequency resource block #0. The mapping method in another mapping cycle is similar, and will not be repeated here.
  • a mapping period includes 5 PUSCH time-frequency resource blocks, and a mapping period includes 2 PRACH time-frequency resources as an example.
  • mapping period configured by the network device is the same as the PRACH period.
  • N 4 2 configured by the network device, it means that each PRACH resource is mapped to 2 PUSCH time-frequency resource blocks.
  • PRACH time-frequency resource #0 is mapped to PUSCH time-frequency resource block #0 and PUSCH time-frequency resource block #1.
  • PRACH time-frequency resource #1 is mapped to PUSCH time-frequency resource block #2 and PUSCH time-frequency resource block #3.
  • the mapping method in another mapping cycle is similar, and will not be repeated here.
  • FIGS. 16 to 18 are all described by taking the same mapping period as the PRACH period (the period of the PRACH time-frequency resource) as an example. It is also mentioned above that the mapping period can also be an integer multiple of the PRACH period. Then, when mapping, all PRACHs in the mapping period are mapped according to the preset mapping order of PRACH time-frequency resources to PUSCH time-frequency resource blocks, and the order of PUSCH time-frequency resource blocks.
  • the mapping method is similar. As an example, the period is twice the PRACH period.
  • mapping period is twice the PRACH period, that is, the mapping period is 20 ms
  • the rest of the configuration information is the same as FIG. 16.
  • sequence number of the PUSCH time-frequency resource block in the second PRACH cycle changes.
  • the mapping relationship of each PRACH time-frequency resource in the first PRACH period is the same as that in FIG. 16, and details are not described again.
  • PRACH time-frequency resource #0 is mapped to time-frequency resource #4 and time-frequency resource #6, and PRACH time-frequency resource #1 is mapped to time-frequency resource #6 and time-frequency resource #7.
  • N 4 when the network device configuration N 4 ⁇ 1, it means Each PRACH time-frequency resource is mapped to one PUSCH time-frequency resource block.
  • N 4 1 configured by the network device, it means that one PRACH time-frequency resource is mapped to one PUSCH time-frequency resource block.
  • N 4 >1 configured by the network device it means that one PRACH time-frequency resource is mapped to N 4 PUSCH time-frequency resource blocks.
  • each PRACH time-frequency resource is a PRACH time-frequency resource group by default, for example: PRACH time-frequency resource #n constitutes a PRACH time-frequency resource group# in Figure 16 to Figure 19 n, the sequence of the PRACH time-frequency resource group is the same as the sequence of the PRACH time-frequency resource.
  • PRACH time-frequency resources located in the same PRACH time-domain resource form a PRACH time-frequency resource group
  • PRACH time-frequency resources located in the same time slot form a PRACH time-frequency resource group
  • PRACH time domain resource #0 and PRACH time domain resource #1 are located in the same PRACH time domain resource and also in the same time slot.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 can form a PRACH time-frequency resource group;
  • PRACH time-domain resource #2 and PRACH time-domain resource #3 are located in the same PRACH time-domain resource and also in the same time slot, then PRACH time-frequency resource #2 and PRACH time-frequency resource #3 can form a PRACH time-frequency resource group.
  • PRACH time-frequency resource #n constitutes PRACH time-frequency resource group #n
  • PRACH time-frequency resources The order of the groups is the same as the order of PRACH time-frequency resources.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 can form a PRACH time-frequency resource group, which is a PRACH time-frequency resource group #0; PRACH time-frequency resource #2 and PRACH time-frequency resource #3 can form a PRACH time-frequency resource group, which is PRACH time-frequency resource group #1.
  • each PRACH time-frequency resource in the mapping period can be a PRACH time-frequency resource group, and the sequence of the PRACH time-frequency resource group is the same as the sequence of the PRACH time-frequency resource .
  • each PRACH time-frequency resource in the mapping period can be a PRACH time-frequency resource group, and the order of the PRACH time-frequency resource group is the same as the order of the PRACH time-frequency resource .
  • the second configuration information may further include a parameter N 5 and a parameter N 6 .
  • the network device can configure the number of PRACH time-frequency resources included in each PRACH time-frequency resource group through the parameter N 5 in the second configuration information. Then the parameter N 6 is used to establish a mapping relationship between the PRACH time-frequency resource group and the PUSCH time-frequency resource block.
  • the parameter N 5 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group. Then, the UE can determine each PRACH time-frequency resource group according to the preset sequence of PRACH time-frequency resources and according to the rule that every N 5 PRACH time-frequency resources constitute a PRACH time-frequency resource group.
  • the sequence of the PRACH time-frequency resource group can be further determined according to the sequence of the PRACH time-frequency resource contained in the PRACH time-frequency resource group. That is, the sequence of the PRACH time-frequency resource group may be determined according to the sequence of the frequency domain resources and the sequence of the time domain resources of the included PRACH time-frequency resources. For example, the sequence of the PRACH time-frequency resource group may be sorted according to the ascending order of the frequency domain resources of the included PRACH time-frequency resources, and then according to the ascending order of the time domain resources of the included PRACH time-frequency resources.
  • the sequence of the PRACH time-frequency resource group is similar to the sequence of the PRACH time-frequency resource, and will not be repeated here.
  • the parameter N 6 is used to determine the number of each PRACH time-frequency resource group mapped to the PUSCH time-frequency resource block.
  • each PRACH time-frequency resource group is mapped according to a preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks.
  • the preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks may be mapped according to the sequence number of the PRACH time-frequency resource group.
  • the sequence equivalent to the PUSCH time-frequency resource block is also determined, which can be determined according to the sequence in which the PUSCH time-frequency resource block occupies time domain resources. For example, it can be sorted according to the ascending order of the time domain resources occupied by the PUSCH time-frequency resource blocks.
  • mapping is performed according to the preset mapping sequence of PRACH time-frequency resources to PUSCH time-frequency resource blocks, which includes at least two meanings: one is The mapping sequence of each PRACH time-frequency resource group, that is, which PRACH time-frequency resource group is mapped first, and which PRACH time-frequency resource group is mapped later. The second is that when each PRACH time-frequency resource group is mapped, it is mapped to N 6 PUSCH time-frequency resource blocks in the order of PUSCH time-frequency resource blocks. That is, which N 6 PUSCH time-frequency resource blocks are specifically mapped to when each PRACH time-frequency resource is mapped.
  • mapping period when the number of PRACH time-frequency resource groups is greater than the number of PUSCH time-frequency resource blocks, it means that when PRACH time-frequency resource groups are mapped according to the preset mapping order, they will be cyclically mapped to PUSCH. Frequency resource block until all PRACH time-frequency resource groups in the mapping period are mapped to at least one PUSCH time-frequency resource block.
  • the second configuration information may also include information about some mapping rules, that is, the network device may also configure some mapping rules, for example: the PRACH time-frequency resource group is mapped to the PUSCH time-frequency resource block corresponding to itself, in the time domain The above cannot overlap.
  • the PRACH time-frequency resource group and the PUSCH time-frequency resource block corresponding to its mapping cannot overlap in the frequency domain.
  • the mapping rule may also be predefined, that is, no network device is required to configure it. The embodiments of this application do not limit this.
  • the parameter N 5 is used to determine the number of effective PUSCH time-frequency resource blocks mapped to each PRACH time-frequency resource group.
  • the effective PUSCH time-frequency resource block is a PUSCH time-frequency resource block that complies with the mapping rule.
  • the mapping method of each PRACH time-frequency resource group to a valid PUSCH time-frequency resource block is the same as the above method, and will not be repeated here.
  • PRACH time-frequency resource #0 and PRACH time-frequency resource #1 constitute PRACH time-frequency resource group #0
  • PRACH time-frequency resource #2 and PRACH time-frequency resource #3 constitute PRACH time-frequency resource group #1.
  • PRACH time-frequency resource group #0 is mapped to PUSCH time-frequency resource block #0
  • PRACH time-frequency resource group #2 is mapped to PUSCH time-frequency resource block #1.
  • the mapping situation in the second mapping cycle is similar, and will not be repeated here.
  • PRACH time-frequency resource #1 constitutes PRACH time-frequency resource group #1, and is mapped to PUSCH time-frequency resource block #1.
  • PRACH time-frequency resource #2 constitutes PRACH time-frequency resource group #2, and is mapped to PUSCH time-frequency resource block #3.
  • PRACH time-frequency resource #3 constitutes PRACH time-frequency resource group #3, and is mapped to PUSCH time-frequency resource block #1.
  • the mapping situation in the second mapping cycle is similar, and will not be repeated here.
  • each PRACH time-frequency resource constitutes a PRACH time-frequency resource group, and each resource group is mapped to 2 PUSCH time-frequency resource blocks. Therefore, it can be determined that in the first mapping period, PRACH time-frequency resource #0 constitutes PRACH time-frequency resource group #0, and is mapped to PUSCH time-frequency resource block #0 and PUSCH time-frequency resource block #2.
  • PRACH time-frequency resource #1 constitutes PRACH time-frequency resource group #1, and is mapped to PUSCH time-frequency resource block #1 and PUSCH time-frequency resource block #3.
  • the mapping situation in the second mapping cycle is similar, and will not be repeated here.
  • the second configuration information may further include information including the parameter N 7 and the second mapping pattern.
  • the network device can configure the number of PRACH time-frequency resources included in each PRACH time-frequency resource group through the parameter N 7 in the second configuration information.
  • the second mapping pattern is then used to establish a mapping relationship between the PRACH time-frequency resource group and the PUSCH time-frequency resource block.
  • the parameter N 7 is used to determine the number of PRACH time-frequency resources included in each PRACH time-frequency resource group. 7 the parameters N and the meaning and role of the above-described implementations same parameters N 5, will not be repeated here.
  • the second mapping pattern is used to determine at least one PUSCH time-frequency resource block.
  • the second mapping pattern may be one or more sequence number sets, and each sequence number set includes one or more sequence numbers of PUSCH time-frequency resource blocks.
  • each sequence number set includes one or more sequence numbers of PUSCH time-frequency resource blocks.
  • the sequence of each time-frequency resource block is also determined.
  • the sequence number of the PUSCH time-frequency resource block can be determined according to the sequence of the PUSCH time-frequency resource block.
  • the sequence numbers of the PUSCH time-frequency resource blocks can be sorted according to the ascending order of the PUSCH time-frequency resource blocks on the time domain resources.
  • each PRACH time-frequency resource constitutes a PRACH time-frequency resource group, which is PRACH time-frequency resource group #0 to PRACH time-frequency resource group #3. Then, the mapping is performed in the order of the mapping sequence number in the second mapping pattern.
  • PRACH time-frequency resource group #0 uses the first sequence number set and is mapped to PUSCH time-frequency resource block #0 and PUSCH time-frequency resource block #2;
  • PRACH time-frequency resource group #1 uses the second sequence number set and is mapped to PUSCH time-frequency resource block #1 and PUSCH time-frequency resource block #3;
  • PRACH time-frequency resource group #2 uses the third sequence number set, mapped to PUSCH time-frequency resource block #4 and PUSCH time-frequency resource block #5;
  • PRACH time Frequency resource group #3 uses the fourth sequence number set and is mapped to PUSCH time-frequency resource block #6 and PUSCH time-frequency resource block #7.
  • the mapping relationship between the PRACH time-frequency resource group and the PUSCH time-frequency resource block can be finally determined according to the first configuration information and the second configuration information. Further, the network device may establish a mapping relationship between the preamble sequence in the PRACH time-frequency resource group and each PUSCH time-frequency resource in the PUSCH time-frequency resource block by configuring the third configuration information. Since the PRACH time-frequency resource group may include one or more PRACH time-frequency resources, the number of preamble sequences included in each PRACH time-frequency resource group may also have various situations. Therefore, by using this method to configure the third configuration information, the mapping relationship between the preamble sequence and the PUSCH time-frequency resource can be established more flexibly to meet various requirements.
  • the mapping relationship between the PRACH time-frequency resource and the PUSCH time-frequency resource block can be determined according to the first configuration information and the second configuration information. Then, the network device may also directly establish a mapping relationship between the preamble sequence included in each PRACH time-frequency resource and the PUSCH time-frequency resource through the third configuration information.
  • the specific configuration method of the third configuration information is similar.
  • the network device configures the mapping relationship between the preamble sequence in the PRACH time-frequency resource group and each PUSCH time-frequency resource in the PUSCH time-frequency resource block as an example to illustrate the configuration method of the third configuration information.
  • the preamble sequence included in each PRACH time-frequency resource group and the PUSCH time-frequency resource included in each PUSCH time-frequency resource block need to be determined first.
  • the preamble sequence set in each PRACH time-frequency resource can be determined according to the first configuration information, that is, the preamble sequence contained in each PRACH time-frequency resource.
  • the PRACH time-frequency resources included in each PRACH time-frequency resource group may also be determined according to the second configuration information. Then, the information of the preamble sequence contained in each PRACH time-frequency resource group can be determined.
  • the third configuration information may include size information of each PUSCH time-frequency resource in the PUSCH time-frequency resource block.
  • the size information of each PUSCH time-frequency resource may be, for example, the number of consecutive symbols occupied by each PUSCH time-frequency resource and the number of consecutive RBs occupied. Then, according to the size of each PUSCH time-frequency resource, each PUSCH time-frequency resource can be determined according to the sequence of time-domain resources and frequency-domain resources.
  • the third configuration information may also include a time domain interval or a frequency domain interval between adjacent PUSCH time-frequency resources.
  • the third configuration information may also configure whether the PUSCH time-frequency resources in the PUSCH time-frequency resource block are continuous, and the size of the interval when they are not continuous.
  • the time domain interval and the frequency domain interval are both zero, or there is no time domain interval and frequency domain interval information in the third configuration information, it can be considered that the PUSCH time-frequency resource is continuous in the time domain and the frequency domain.
  • the time domain interval is zero or the default time domain interval information
  • it can be considered that the PUSCH time-frequency resources are continuous in the time domain.
  • the frequency domain interval is zero or the default frequency domain interval information, it can be considered that the PUSCH time-frequency resources are continuous in the frequency domain.
  • the terminal can determine each PUSCH time-frequency resource according to the time-domain resource and frequency-domain resource order according to the size information of the PUSCH time-frequency resource configured in the third configuration information, the time-domain interval and the frequency-domain interval.
  • the third configuration information may include the number of PUSCH time-frequency resources included in each PUSCH time-frequency resource block.
  • the number of PUSCH time-frequency resources included in each PUSCH time-frequency resource block may be, for example, the number in the time domain and the number in the frequency domain. Then, according to the quantity in the time domain and the quantity in the frequency domain, each PUSCH time-frequency resource can be determined according to the order of the time domain resource and the frequency domain resource.
  • the embodiment of the present application does not limit the method for determining the PUSCH time-frequency resource in each PUSCH time-frequency resource block.
  • the second configuration information may include the number of DMRS ports associated with each PUSCH time-frequency resource block. If there is no DMRS port number in the second configuration information, the number of DMRS ports associated with the PUSCH time-frequency resource block may also be 1 by default.
  • the number of DMRS ports can be determined according to parameters such as the DMRS configuration type and the number of time-domain symbols occupied by the DMRS. In other words, there may be no need to configure the network device, which is not limited in the embodiment of the present application.
  • each preamble sequence and each PUSCH time-frequency resource may be further combined according to the third configuration information Establish a mapping relationship.
  • the third configuration information includes the size of a time-frequency resource, that is, the size of the PUSCH time-frequency resource included in all PUSCH time-frequency resource blocks is the same. Then, the third configuration information may include mapping every N 8 preamble sequences to one PUSCH time-frequency resource.
  • N 8 ⁇ 1 it is equivalent to a preamble sequence mapped to PUSCH time-frequency resources with consecutive serial numbers.
  • N 8 >1 it is equivalent to mapping N 8 preamble sequences to 1 PUSCH time-frequency resource with continuous sequence numbers.
  • the preamble sequence in each PRACH time-frequency resource is mapped to the PUSCH time-frequency resource in the corresponding PUSCH time-frequency resource block, it can be performed according to the parameter N 8 , the order of the preamble sequence and the order of the PUSCH time-frequency resource Mapping.
  • the sequence of the preamble sequence can be understood as the sequence of frequency domain resources and time-frequency resources occupied by the preamble sequence.
  • the order of the preamble sequence may be in the ascending order of the frequency domain resource number first, and then the ascending order of the time domain resource number.
  • the sequence of time-frequency resources can be understood as the sequence of frequency-domain resources occupied by the time-frequency resources, the sequence of time-domain resources, and the sequence of the sequence numbers of the DMRS ports associated with the time-frequency resources.
  • the order of the time-frequency resources may be in the ascending order of the sequence numbers of the DMRS ports associated with the time-frequency resources, then in the ascending order of the frequency domain resources, and then in the ascending order of the time domain resources.
  • the order of the time-frequency resources may be in the ascending order of the sequence numbers of the DMRS ports associated with the time-frequency resources, then in the ascending order of the time-domain resources, and then in the ascending order of the frequency-domain resources.
  • a PRACH time-frequency resource group contains 10 preamble sequences, which are preamble sequence #0 to preamble sequence #9.
  • the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource includes 6 PUSCH time-frequency resources of the same size, and the number of DMRS ports associated with the PUSCH time-frequency resource block is 8.
  • N 8 2 in the third configuration information, that is, every two preamble sequences are mapped to one PUSCH time-frequency resource. Then, the specific mapping relationship is as follows:
  • the preamble sequence #0 is mapped to PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3;
  • the preamble sequence #1 is mapped to the PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7;
  • the preamble sequence #2 is mapped to the PUSCH time-frequency resource #1: DMRS port #0 to DMRS port #3;
  • the preamble sequence #3 is mapped to PUSCH time-frequency resource #1: DMRS port #4 to DMRS port #7;
  • the preamble sequence #8 is mapped to the PUSCH time-frequency resource #4: DMRS port #0 to DMRS port #3;
  • the preamble sequence #9 is mapped to the PUSCH time-frequency resource #4: DMRS port #4 to DMRS port #7.
  • PUSCH time-frequency resource #5 does not participate in the mapping, and will not be used to transmit MsgA messages in the two-step random access process.
  • mapping may be performed in the order of the N 8 preamble sequences and the DMRS port associated with the PUSCH time-frequency resource.
  • the DMRS ports associated with the PUSCH time-frequency resource may be divided into N 8 parts according to the order of the DMRS ports associated with the PUSCH time-frequency resource, each part corresponding to a preamble sequence in turn.
  • the number of DMRS ports associated with each PUSCH time-frequency resource is 8, and the DMRS ports associated with each PUSCH time-frequency resource are divided into 2 parts according to the sequence number of the DMRS port, and each part corresponds to a preamble sequence. That is, preamble sequence #0 is mapped to PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3; preamble sequence #1 is mapped to PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7. The mapping of the remaining preamble sequences is similar and will not be repeated.
  • the preamble sequence #0 is mapped to DMRS port #0
  • the preamble sequence #1 is mapped to DMRS port #1
  • the preamble sequence #4 is mapped to DMRS port #4.
  • the preamble sequence #5 has not yet participated in the mapping. Therefore, cyclic mapping is performed, and the preamble sequence #5 is mapped to the DMRS port #0.
  • the preamble sequence #0 is mapped to the DMRS port #0
  • the preamble sequence #1 is mapped to the DMRS port #1
  • the preamble sequence #2 is mapped to the DMRS port #2.
  • the preamble sequence #0 is mapped to the DMRS port #0
  • the preamble sequence #1 is mapped to the DMRS port #1
  • the preamble sequence #2 is mapped to the DMRS port #2.
  • DMRS port #3 has not yet participated in the mapping. Therefore, cyclic mapping is performed, and the preamble sequence #0 is mapped to the DMRS port #3.
  • the third configuration information may include the parameter N 8 , which is used to indicate the mapping of N 8 preamble sequences to one PUSCH time-frequency resource. That is, the preamble sequence and PUSCH time-frequency resources are mapped. In other embodiments, the preamble sequence and the PUSCH resource unit may also be mapped.
  • the PUSCH resource unit is a unit with a smaller granularity than the PUSCH time-frequency resource. For example, if the number of DMRS associated with one PUSCH time-frequency resource is E, then this PUSCH time-frequency resource can be considered as E PUSCH resource units.
  • the third configuration information may include a parameter F, which is used to indicate that every F preamble sequences are mapped to one PUSCH resource unit.
  • a PUSCH resource unit can be understood as a PUSCH time-frequency resource and a DMRS port corresponding to the PUSCH resource unit.
  • the DMRS port can be understood as different DMRS configurations and/or different DMRS sequences.
  • mapping every N 8 preamble sequences to one PUSCH time-frequency resource is equivalent to mapping every F preamble sequences to one PUSCH resource unit.
  • E represents the number of DMRS ports associated with a PUSCH time-frequency resource.
  • the preamble sequence in each PRACH time-frequency resource group is mapped to the PUSCH time-frequency resource in the corresponding PUSCH time-frequency resource block, it can be performed according to the parameter F, the sequence of the preamble sequence, and the sequence of the PUSCH resource unit Mapping.
  • the preamble sequence sequence can be understood as the default sequence sequence of the preamble sequence in a PRACH time-frequency resource, including The sequence of the PRACH time-frequency resources occupied by the preamble sequence, for example: the sequence of the preamble sequence can be based on the default sequence sequence of the preamble sequence in a PRACH time-frequency resource, and the frequency domain resources according to the PRACH time-frequency resources occupied by the preamble sequence The ascending order of the serial number, then the ascending order of the serial number of the time domain resource.
  • the sequence of PUSCH resource units can be understood as the sequence of PUSCH time-frequency resources and the sequence of the sequence numbers of the DMRS ports associated with the PUSCH time-frequency resources.
  • the order of PUSCH resource units may be in the ascending order of the sequence numbers of the DMRS ports associated with the PUSCH time-frequency resource, and then in the ascending order of the PUSCH time-frequency resource sequence numbers.
  • the order of PUSCH resource units can also be in ascending order of PUSCH time-frequency resource sequence numbers, and then in ascending order of DMRS port sequence numbers.
  • the index of the PUSCH time-frequency resource corresponding to PUSCH resource unit #a for The DMRS port index is a mod E. among them Represents the largest integer less than or equal to X.
  • each PUSCH time-frequency resource corresponds to 2 DMRS ports as an example for description.
  • the 2 PUSCH time-frequency resources have 4 PUSCH resource units.
  • the order of the 4 PUSCH resource units can be as shown in Table 9, and they are numbered in ascending order of DMRS port serial numbers, and then in ascending order of time-frequency resource serial numbers.
  • the index of PUSCH time-frequency resource corresponding to PUSCH resource unit #a is The DMRS port index is a mod L.
  • H is the number of PUSCH time-frequency resources in the PUSCH time-frequency resource block.
  • each PUSCH time-frequency resource corresponding to 2 DMRS ports Take 2 PUSCH time-frequency resources, each PUSCH time-frequency resource corresponding to 2 DMRS ports as an example for description. Then, the 2 PUSCH time-frequency resources have 4 PUSCH resource units.
  • the sequence of the four PUSCH resource units can be as shown in Table 10, first in the ascending order of the time-frequency resource sequence number, and then numbering in the ascending order of the DMRS port sequence number.
  • the order of PUSCH time-frequency resources can be understood as the ascending order of frequency-domain resources first, and then the ascending order of time-domain resources; or the order of PUSCH time-frequency resources can be understood as the ascending order of time-domain resources first, and then the ascending order of frequency-domain resources .
  • the order of PUSCH time-frequency resources can be understood as the ascending order of frequency-domain resources first, and then the ascending order of frequency-domain resources.
  • sequence numbers of the DMRS ports above are described by taking the sequence of antenna port indexes as an example.
  • the serial number of the DMRS port can also be numbered in other order, which is not limited in the embodiment of the present application.
  • the sequence numbers of the DMRS may also be numbered in combination with the index of the scrambling ID or reference signal ID.
  • the order of the DMRS ports can also be understood as first in the ascending order of the scrambling ID or reference signal ID of the generated DMRS sequence, and then in the ascending order of the antenna port index.
  • the order of the DMRS ports can also be understood as first in the ascending order of the antenna port index, and then in the ascending order of the index of the scrambling ID or reference signal ID for generating the DMRS sequence.
  • different antenna ports correspond to different DMRS configurations.
  • a PUSCH resource unit includes two antenna ports, and each antenna port includes two DMRS sequences generated by different IDs as an example. Then, the PUSCH resource unit includes 4 DMRS ports.
  • the order of the 4 DMRS ports can be as shown in Table 11, first according to the ascending order of the index of the scrambling ID for generating the DMRS sequence, and then numbering according to the ascending order of the antenna port index.
  • the PUSCH resource unit includes 4 DMRS ports.
  • the order of the 4 DMRS ports can be as shown in Table 12, first in ascending order of the antenna port index, and then in the ascending order of the index of the scrambling ID that generates the DMRS sequence.
  • the mapping relationship between the preamble sequence and the PUSCH resource unit can be established based on the two.
  • all the preamble sequences are based on the order of the preamble sequence and the PUSCH resource.
  • the order of the units is continuously mapped, and all preamble sequences are mapped to one PUSCH resource unit according to every F preamble sequences with continuous sequence numbers.
  • the number of preamble sequences in a PRACH time-frequency resource group (denoted as P) is not a multiple or submultiple of the number of PUSCH resource units of the corresponding PUSCH time-frequency resource block (ie, H)
  • the PRACH In the time-frequency resource group the number of PUSCH resource units to which a part of the preamble sequence is mapped is different from the number of PUSCH resource units to which another part of the preamble sequence is mapped.
  • a part of the preamble sequence is mapped to one PUSCH resource unit according to F preamble sequences with consecutive sequence numbers.
  • F ⁇ 1 another part of the preamble sequence is mapped to PUSCH resource units.
  • F>1 another part of the preamble sequence is mapped to one PUSCH resource unit according to every F-1 preamble sequence.
  • the number of preamble sequences included in each part can be calculated by the number of preamble sequences in the PRACH time-frequency resource group (P), the number of PUSCH resource units in the PUSCH time-frequency resource block (H), and the parameter F.
  • This mapping method can ensure that all PUSCH resource units in the PUSCH time-frequency resource block are mapped with the preamble sequence, thereby improving the utilization of PUSCH resource units.
  • the first F(PE*H*(F-1)) preamble sequences are mapped to a PUSCH resource unit according to consecutive F preamble sequences, and the last (F-1)*(F*E *HP) preamble sequences are mapped to a PUSCH resource unit according to consecutive F-1 preamble sequences; or the first (F-1)*(F*E*HP) preamble sequences are mapped according to consecutive F-1 preamble sequences To one PUSCH resource unit, the last F (PE*H*(F-1)) preamble sequences are mapped to one PUSCH resource unit according to consecutive F preamble sequences.
  • the network device may not be configured with parameter F. That is, the mapping rule of the preamble sequence to the PUSCH resource unit is predefined. Then, the mapping relationship between the preamble sequence and the PUSCH resource unit can be established directly according to the predefined mapping rule. In other words, the third configuration information may not include the parameter F.
  • F may be calculated first according to the number of preamble sequences in the PRACH time-frequency resource group and the number of PUSCH resource units in the PUSCH time-frequency resource block.
  • mapping method as in the previous embodiment is used to map the preamble sequence to the PUSCH resource unit.
  • the predefined mapping method is: in each PRACH time-frequency resource group, the preamble sequence is mapped to the PUSCH time-frequency resource in the corresponding PUSCH time-frequency resource block according to the order of the preamble sequence. And the sequence of the PUSCH resource units is cyclically mapped in a one-to-one manner until all the preamble sequences in each PRACH time-frequency resource group are mapped to at least one PUSCH resource unit.
  • the preamble sequence #n is mapped to PUSCH resource unit #(n mod(E*H)).
  • the predefined mapping method is: in each PRACH time-frequency resource group, the preamble sequence is mapped to the PUSCH time-frequency resource in the corresponding PUSCH time-frequency resource block according to the order of the preamble sequence. And the sequence of PUSCH resource units is cyclically mapped in a one-to-one manner. When P ⁇ E*H, until each PUSCH resource unit in each PUSCH time-frequency resource block is mapped to at least one preamble sequence.
  • the preamble sequence #n is mapped to PUSCH resource unit #(P*i+n)).
  • the value of i is all greater than or equal to 0 and less than The integer.
  • the third configuration information may also configure different sizes of preamble sequences. PUSCH time-frequency resources.
  • the third configuration information may include two or more PUSCH time-frequency resource size information.
  • the third configuration information may include configuring a parameter N 8 for the preamble of each packet. That is, the third configuration information includes multiple N 8 values.
  • the third configuration information includes multiple N 8 values.
  • the PRACH time-frequency resource group containing multiple sets of preamble sequences is mapped to one PUSCH time-frequency resource block.
  • this PUSCH time-frequency resource block can be configured as PUSCH time-frequency resources of different sizes. That is, the PUSCH time-frequency resource block may include PUSCH time-frequency resources of different sizes.
  • a PRACH time-frequency resource group contains 10 preamble sequences, which are divided into two groups.
  • the first packet has 7 preamble sequences, specifically preamble sequence #0 to preamble sequence #6.
  • the first packet has 2 preamble sequences, specifically preamble sequence #7 to preamble sequence #8.
  • the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource includes 5 PUSCH time-frequency resources (including two PUSCH time-frequency resources of different sizes).
  • the number of DMRS ports associated with the PUSCH time-frequency resource block is 8.
  • N 8 2 in the third configuration information, that is, every two preamble sequences are mapped to one time-frequency resource.
  • the specific mapping relationship is as follows:
  • the preamble sequence #0 is mapped to PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3;
  • the preamble sequence #1 is mapped to the PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7;
  • the preamble sequence #6 is mapped to the PUSCH time-frequency resource #3: DMRS port #0 to DMRS port #3;
  • the preamble sequence #7 is mapped to the PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3;
  • the preamble sequence #8 is mapped to the PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7.
  • PUSCH time-frequency resource #3 DMRS port #4 to DMRS port #7 does not participate in the mapping, which is different from the transmission of the MsgA message in the two-step random access process.
  • the PRACH time-frequency resource group containing multiple sets of preamble sequences is mapped to multiple PUSCH time-frequency resource blocks.
  • PUSCH time-frequency resources of different sizes can be configured for different PUSCH time-frequency resource blocks. That is, the sizes of the time-frequency resources included in different PUSCH time-frequency resource blocks are different, but the time-frequency resources in the same PUSCH time-frequency resource block are the same.
  • a PRACH time-frequency resource group contains 10 preamble sequences, which are divided into two groups.
  • the first packet has 7 preamble sequences, specifically preamble sequence #0 to preamble sequence #6.
  • the first packet has 2 preamble sequences, specifically preamble sequence #7 to preamble sequence #8.
  • the PUSCH time-frequency resource block corresponding to the PRACH time-frequency resource includes PUSCH time-frequency resource block #0 and PUSCH time-frequency resource block #1.
  • PUSCH time-frequency resource block #0 includes 4 PUSCH time-frequency resources
  • PUSCH time-frequency resource block #1 includes 2 PUSCH time-frequency resources.
  • the number of DMRS ports associated with the PUSCH time-frequency resource block is 8.
  • N 8 2 in the third configuration information, that is, every two preamble sequences are mapped to one time-frequency resource. Then, the specific mapping relationship is as follows:
  • Preamble sequence #0 is mapped to PUSCH time-frequency resource block #0, PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3;
  • Preamble sequence #1 is mapped to PUSCH time-frequency resource block #0, PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7;
  • Preamble sequence #6 is mapped to PUSCH time-frequency resource block #0, PUSCH time-frequency resource #3: DMRS port #0 to DMRS port #3;
  • Preamble sequence #7 is mapped to PUSCH time-frequency resource block #1, PUSCH time-frequency resource #0: DMRS port #0 to DMRS port #3;
  • Preamble sequence #8 is mapped to PUSCH time-frequency resource block #0, PUSCH time-frequency resource #0: DMRS port #4 to DMRS port #7.
  • PUSCH time-frequency resource #3 in PUSCH time-frequency resource block #0 DMRS port #4 to DMRS port #7
  • PUSCH time-frequency resource #1 in PUSCH time-frequency resource block #1 DMRS port #1 to DMRS port #7 does not participate in the mapping, which is different from the transmission of MsgA messages in the two-step random access process.
  • the random access method provided in the embodiment of the present application can establish the mapping relationship between the preamble sequence and the PUSCH time-frequency resource.
  • the division of the first configuration information, the second configuration information, and the third configuration information is only for explaining the method of the present application, and does not constitute a specific limitation on the first configuration information, the second configuration information, and the third configuration information.
  • part or all of the content in the first configuration information may be in the second configuration information or the third configuration information
  • part or all of the content in the second configuration information may be in the first configuration information or the third configuration information
  • Part or all of the foregoing third configuration information may be in the first configuration information or the second configuration information.
  • the first configuration information is the same as the first configuration information in the foregoing embodiment, and will not be repeated here.
  • the second configuration information and the third configuration information are slightly different from the second configuration information and the third configuration information in the foregoing embodiment, which will be described in detail below.
  • the network device can determine the PUSCH time-frequency resource block used for uplink transmission by configuring the first mapping pattern, and each PRACH time-frequency resource and the PUSCH time-frequency resource used for uplink transmission Correspondence between frequency resource blocks.
  • the second configuration information includes information of the first mapping image, and the configuration and content of the first mapping pattern are the same as the first method.
  • the difference between the first mapping pattern and the above-mentioned first method is that, in this embodiment, the time domain resource configuration information and the frequency domain resource configuration information determined by each mapping two-tuple in the first mapping pattern are one PUSCH time-frequency resources, and the time-domain resource configuration information and frequency-domain resource configuration information determined by each mapping two-tuple in the above-mentioned first method are for one PUSCH time-frequency resource block. That is, in this embodiment, the PUSCH time-frequency resource can be determined according to the second configuration information.
  • the second configuration information may also include the number M 1 of PUSCH time-frequency resource frequency division multiplexing and/or the number M 2 of PUSCH time-frequency resource time division multiplexing.
  • PUSCH time-frequency resource time-domain resource configuration information and frequency-domain resource configuration information are combined with the number of PUSCH time-frequency resources and frequency division multiplexing M 1 and/or the number of PUSCH time-frequency resources time division multiplexing M 2 to determine a PUSCH time Frequency resource block.
  • the third configuration information may not include the information for determining PUSCH time-frequency resources, that is, it does not include: PUSCH time-frequency resource size information, time-domain interval and frequency-domain interval, each The number of PUSCH time-frequency resources included in the PUSCH time-frequency resource block, etc.
  • the third configuration information may include configuring the mapping relationship between each preamble sequence in the PRACH time-frequency resource and the PUSCH time-frequency resource. That is, the third configuration information may include the number N 8 of preamble sequences mapped to one PUSCH time-frequency resource. For this part of the content, please refer to the above description and will not repeat it.
  • the network device is configured with the PRACH time-frequency resource as shown in FIG. 5A, and the first mapping pattern includes two mapping two-tuples as an example, and an exemplary description is given in conjunction with the accompanying drawings.
  • the first mapped image is
  • mapping two-tuple ( ⁇ 1,2,12 ⁇ 12,2 ⁇ ) is the first mapping two-tuple.
  • the mapping two-tuple represents the first mapped PUSCH time-frequency resource.
  • the time slot in which a symbol is located is in the first time slot after the time slot occupied by the PRACH time-frequency resource, which is a subframe here, and the start symbol is symbol #2, which occupies 12 symbols.
  • the starting RB is #12RB, which occupies 2RB.
  • the number of frequency domain multiplexing is 3, that is, there are 3 PUSCH time-frequency resources and frequency division multiplexing in one time slot.
  • the starting RBs are #12RB, #14RB, and #16RB, each occupying 2RB.
  • the number of time-domain multiplexing is 2, that is, there are 3 PUSCH time-frequency resources in each of two consecutive time slots, and the start symbols are all symbol #2, each occupying 12 symbols. These 6 PUSCH time-frequency resources form one PUSCH time-frequency resource block. ( ⁇ 2,2,12 ⁇ 6,2 ⁇ ) is the second mapping two-tuple, and the corresponding PUSCH time-frequency resource and time-frequency resource block method is the same as the first mapping two-tuple.
  • FIG. 24A when the network device is configured When, it means that a PRACH time-frequency resource mapping is used
  • One mapping two-tuple that is, two PRACH time-frequency resources use one mapping two-tuple.
  • PRACH time-frequency resource #0 uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #1 also uses the first mapping two-tuple for mapping
  • PRACH time-frequency resource #2 uses the second mapping two-tuple for mapping
  • PRACH time-frequency resource #3 also uses the second mapping two-tuple for mapping.
  • the PUSCH time-frequency resource obtained after mapping is then obtained from the PUSCH time-frequency resource block according to M 1 and M 2 , and the corresponding relationship between the PRACH time-frequency resource and the time-frequency resource is shown in Fig. 24A.
  • each network element such as a terminal and a network device, includes a hardware structure and/or software module corresponding to each function.
  • the present application can be implemented in the form of hardware, software or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiment of the present application may divide the terminal and the network device into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation. The following is an example of dividing each function module corresponding to each function:
  • FIG. 24B shows a schematic structural diagram of a device involved in the foregoing embodiment, and the device can implement the function of the terminal in the method provided in the embodiment of the present application.
  • the device may be a terminal or a device that can support the terminal to implement the functions of the terminal in the embodiments of the present application.
  • the device is a chip system applied to the terminal.
  • the device includes: a determining unit 101 and a communication unit 102.
  • the determining unit 101 may be used to support the device shown in FIG. 24B to execute steps S502, S503, and S504 in the foregoing embodiment.
  • the communication unit 102 is used to support the device shown in FIG. 24B to perform steps S501, S505, and S506 in the above-mentioned embodiment. All relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the communication unit in the embodiment of the present application may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can implement communication.
  • the communication unit 102 may be a terminal or a communication interface applied to a chip system in the terminal.
  • the communication interface may be a transceiver circuit
  • the determining unit 101 may be a processing chip integrated in the terminal or applied to the terminal. ⁇ On the device.
  • FIG. 25 shows a schematic diagram of a possible logical structure of the device involved in the foregoing embodiment.
  • the device can implement the function of the terminal in the method provided in the embodiment of the present application.
  • the device may be a terminal or a chip system applied to the terminal.
  • the device includes a processing module 112 and a communication module 113.
  • the processing module 112 is used to control and manage the actions of the device shown in FIG. 25.
  • the processing module 112 is used to execute the steps of message or data processing on the device side shown in FIG. 25.
  • the device shown in FIG. 25 is supported to execute steps S502, S503, and S504 in the foregoing embodiment.
  • the communication module 113 is used to support the device shown in FIG.
  • the device shown in FIG. 25 may further include a storage module 111 for storing program codes and data of the device.
  • the processing module 112 may be a processor or a controller, for example, a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present application.
  • the processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 113 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 111 may be a memory.
  • the processing module 112 is the processor 220
  • the communication module 113 is the communication interface 230 or the transceiver
  • the storage module 111 is the memory 240
  • the device involved in the embodiment of the present application may be the device shown in FIG. 26.
  • the communication interface 230, at least one processor 220, and the memory 240 are connected to each other through a bus 210; the bus 210 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 26, but it does not mean that there is only one bus or one type of bus.
  • the memory 240 is used to store program codes and data of the device.
  • the communication interface 230 is used to support the device to communicate with other devices, and the processor 220 is used to support the device to execute the program code stored in the memory 240 to implement a data channel transmission method provided in an embodiment of the present application.
  • the memory 240 may be included in the processor 220.
  • FIG. 27 shows a schematic diagram of a possible structure of the device involved in the foregoing embodiment, and the device can implement the function of the network device in the method provided in the embodiment of the present application.
  • the device may be a network device or a chip system applied to the network device.
  • the device includes: a communication unit 201 for supporting the device shown in FIG. 27 to perform steps S501, S505, and S506 in the foregoing embodiment.
  • steps S501, S505, and S506 in the foregoing embodiment.
  • All relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, which will not be repeated here.
  • the communication unit 201 may be a network device or a communication interface of a chip system applied to the network device, for example, a transceiver.
  • FIG. 28 shows a schematic diagram of a possible structure of the apparatus involved in the foregoing embodiment, and the apparatus can implement the function of the network device in the method provided in the embodiment of the present application.
  • the device may be a network device or a chip system applied to the network device.
  • the device includes: a processing module 212 and a communication module 213.
  • the processing module 212 is used to control and manage the actions of the device.
  • the processing module 212 is configured to support the device shown in FIG. 28 to perform message or data processing operations on the device side shown in FIG. 28 in the foregoing embodiment.
  • the communication module 213 is configured to support the device shown in FIG.
  • the device shown in FIG. 28 may further include a storage module 211 for program codes and data of the device.
  • the processing module 212 may be a processor or a controller, for example, a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present application.
  • the processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 213 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 211 may be a memory.
  • the processing module 212 is the processor 320
  • the communication module 213 is the communication interface 330 or the transceiver
  • the storage module 211 is the memory 310
  • the data channel receiving device involved in the embodiment of the present application may be the device shown in FIG. 29.
  • the communication interface 330, at least one processor 320, and the memory 310 are connected to each other through a bus 300; the bus 300 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 29, but it does not mean that there is only one bus or one type of bus.
  • the memory 310 is used to store program codes and data of the device.
  • the communication interface 330 is used to support the device to communicate with other devices (for example, the device shown in FIG. 15B-17), and the processor 320 is used to support the device to execute the program code stored in the memory 310 to implement a random interface provided by this application. ⁇ Entry method.
  • the memory 310 may be included in the processor 320.
  • the devices shown in FIGS. 26 and 29 in this application may also be a chip system.
  • the steps performed by each component in the chip system refer to the devices shown in FIGS. 16 and 29 in the above embodiment. The steps performed are not repeated here in this application.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, SSD).
  • a computer-readable storage medium stores instructions, which when run on a computer, cause the computer to execute S501, S502, S503, S504, S505, and S506 in the embodiment. And/or other processes performed by the terminal or the chip system applied in the terminal for the technology described herein.
  • the aforementioned readable storage medium may include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.
  • a computer-readable storage medium stores instructions, which when run on a computer, cause the computer to execute steps S501, S505, and S506 in the embodiment.
  • a computer program product containing instructions which when running on a computer, causes the computer to execute S501, S502, S503, S504, S505, and S506.
  • a computer program product containing instructions is provided.
  • the instructions run on a computer, the computer executes steps S501, S505, and S506 in the embodiment.
  • a chip system includes a processor and may also include a memory for implementing S501, S502, S503, S504, and S505 in the foregoing embodiment.
  • a chip system in yet another aspect, includes a processor and a memory for realizing the functions of the network device in the above-mentioned embodiments.
  • the chip system includes at least one processor and an interface circuit, and the interface circuit and At least one processor is interconnected by wires, and the processor is used to execute instructions to execute steps S501, S505, and S506 in the embodiment of the embodiment.
  • this application also provides a communication system, which includes a terminal as shown in any one of FIGS. 24B to 26 and a network device as shown in any one of FIGS. 27 to 29.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种随机接入方法、设备及系统，涉及通信技术领域，可以降低信令开销，提升资源利用率，该方法包括：终端接收网络设备发送的第一配置信息、第二配置信息和第三配置信息，第一配置信息用于配置PRACH时频资源和前导序列集合；第二配置信息用于配置每个PRACH时频资源所对应的PUSCH时频资源块，第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；发送包含第一前导序列和上行数据的第一消息，其中，第一前导序列承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH时频资源上。

Description

一种随机接入方法、设备及系统
本申请要求于2019年2月15日提交国家知识产权局、申请号为201910118163.2、申请名称为“一种随机接入方法、设备及系统”的中国专利申请的优先权，以及于2019年4月28日提交国家知识产权局、申请号为201910351921.5、申请名称为“一种随机接入方法、设备及系统”的中国专利申请的优先权，两份专利文件的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种随机接入方法、设备及系统。
背景技术
在无线通信过程中，用户设备(user equipment，UE)可以通过随机接入过程(random access procedure)与基站(base station，BS)建立连接并取得上行同步，进而可以向所接入的BS发送上行数据。
目前UE可以通过四步随机接入过程接入BS。四步随机接入过程具体如下：UE向BS发送随机接入前导(random access preamble)，也称为消息一(message1，Msg1)。BS在检测到随机接入前导后向UE发送随机接入响应，也称为消息二(Msg2)。UE根据Msg2的指示在分配的上行资源通过数据信道(例如，物理上行共享信道(physical uplink shared channel，PUSCH))发送上行消息，也称为消息三(Msg3)。Msg3中将携带UE的唯一身份标识信息。由于多个UE可能向BS发送相同的随机接入前导，这些UE将接收到同一Msg2并根据该Msg2的指示向BS发送Msg3，从而多个Msg3之间产生冲突。BS一次最多可以成功接收一个UE发送的Msg3，也可能因为UE之间的干扰无法成功接收任何一个UE发送的Msg3。为了解决冲突，BS成功接收到一个Msg3后，向接入成功的UE返回冲突解决消息(也可以称为Msg4)，该Msg4中携带Msg3中的唯一身份标识以指定接入成功的UE。
在四步随机接入过程中，处于空闲态或非激活(inactive)态的UE想要进行上行数据传输时至少先要完成上述的四次信息交互才能进入无线资源控制(Radio Resource Control，RRC)连接态。对于高可靠低时延通信(ultra-reliable and low latency communications，URLLC)业务来说，四次信息交互会产生较高的时延，不能满足URLLC低时延的要求。对于大规模机器通信(massive machine type communications，mMTC)业务，尤其是业务数据是零星小包的业务来说，四步信息交互不仅会产生较高时延，而且造成较大的信令开销。
为此，业界提出了两步随机接入过程的方法。如图1所示，两步随机接入过程与四步随机接入过程的区别在于，在两步随机接入过程中，UE向BS发送的Msg A中包括随机接入前导和上行数据，即在未完成上行同步之前发送上行数据，从而可以降低上行数据传输的时延。此外，相对于四步随机接入过程，两步随机接入过程中BS向UE发送的Msg B中不需要为UE发送数据信道的调度信息，从而可以降低信令开销。
然而，在两步随机接入过程的具体实现过程中，存在这样的问题：UE在发送MsgA时，在选择了一个物理随机接入信道(physical random access channel，PRACH)前导后，如何选择相应的物理上行共享信道(physical uplink shared channel，PUSCH)资源用于发送上行数据。对于这一技术问题，目前业界尚未给出合适的解决方案。
发明内容
本申请提供一种随机接入方法、设备及系统，可以降低信令开销，提升资源利用率。
为了解决上述技术问题，本申请提供如下技术方案：
第一方面、提供了一种随机接入的方法，包括：终端接收网络设备发送的第一配置信息、第二配置信息和第三配置信息，第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，PUSCH时频资源块包括一个或者多个PUSCH时频资源；第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；根据第一配置信息确定第一PRACH时频资源；确定需要在第一PRACH时频资源上发送的第一前导序列，第一前导序列为前导序列集合中的前导序列；根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源；发送包含第一前导序列和上行数据的第一消息，其中，第一前导序列承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH时频资源上。
由此可见，终端可以根据网络设备配置的第一配置信息、第二配置信息以及第三配置信息，确定出用于前导序列与该前导序列对应的PUSCH时频资源。因此，终端可以直接发送包含第一前导序列和上行数据的第一消息，可以降低上行数据传输的时延。并且，网络设备也不需要向终端的每一次随机接入发送PUSCH时频资源的调度信息，可以降低信令开销。
一种可能的实现方式中，第二配置信息包括用于配置PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
一种可能的实现方式中，第二配置信息包括第一映射图样的配置信息，第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
一种可能的实现方式中，第二配置信息包含用于配置PUSCH时频资源块的周期T1，第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 1，参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，参数N 1和第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 2和参数N 3，参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
一种可能的实现方式中，第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包括参数N 4，参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包含参数N 5和参数N 6，参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 6用于确定周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息还包含参数N 7和第二映射图样的信息，参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，参数N 7和第二映射图样用于确定周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
一种可能的实现方式中，根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH的时频资源包括：根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序、第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源。
一种可能的实现方式中，第三配置信息包含每个PUSCH时频资源的大小和参数N 8，参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
一种可能的实现方式中，根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源包括：根据预设的PRACH时频资源到时频资源块的映射顺序、预设的前导序列到PUSCH时频资源的映射顺序、第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源。
一种可能的实现方式中，方法还包括：根据预设的前导序列到DMRS端口的映射顺序，确定第一PRACH时频资源对应的PUSCH时频资源所关联的DMRS端口。
第二方面、提供了一种随机接入的方法，包括：网络设备向终端发送第一配置信息、第二配置信息和第三配置信息，第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，PUSCH时频资源块包括一个或者多个PUSCH时频资源；第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；接收终端发送的包含第一前导序列和上行数据的第一消息，其中，第一前导序列承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH时频资源上。
由此可见，网络设备配置的第一配置信息、第二配置信息以及第三配置信息，可供终端用于确定出用于前导序列与该前导序列对应的PUSCH时频资源。因此，终端可以直接发送包含第一前导序列和上行数据的第一消息，可以降低上行数据传输的时 延。并且，网络设备也不需要向终端的每一次随机接入发送PUSCH时频资源的调度信息，可以降低信令开销。
一种可能的实现方式中，第二配置信息包括用于配置PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
一种可能的实现方式中，第二配置信息包括第一映射图样的配置信息，第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
一种可能的实现方式中，第二配置信息包含用于配置PUSCH时频资源块的周期T1，第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 1，参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，参数N 1和第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 2和参数N 3，参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
一种可能的实现方式中，第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包括参数N 4，参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包含参数N 5和参数N 6，参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 6用于确定周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息还包含参数N 7和第二映射图样的信息，参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，参数N 7和第二映射图样用于确定周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
一种可能的实现方式中，第三配置信息包含每个PUSCH时频资源的大小和参数N 8，参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
第三方面、提供了一种随机接入装置，包括：通信单元和确定单元；通信单元，用于接收网络设备发送的第一配置信息、第二配置信息和第三配置信息，第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，PUSCH时频资源块包括一个或者多个PUSCH时频资源；第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；确定单元， 用于根据第一配置信息确定第一PRACH时频资源；确定单元，还用于确定需要在第一PRACH时频资源上发送的第一前导序列，第一前导序列为前导序列集合中的前导序列；确定单元，还用于根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源；通信单元，还用于发送包含第一前导序列和上行数据的第一消息，其中，第一前导序列承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH时频资源上。
一种可能的实现方式中，第二配置信息包括用于配置PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
一种可能的实现方式中，第二配置信息包括第一映射图样的配置信息，第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
一种可能的实现方式中，第二配置信息包含用于配置PUSCH时频资源块的周期T1，第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 1，参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，参数N 1和第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 2和参数N 3，参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
一种可能的实现方式中，第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包括参数N 4，参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包含参数N 5和参数N 6，参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 6用于确定周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息还包含参数N 7和第二映射图样的信息，参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，参数N 7和第二映射图样用于确定周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
一种可能的实现方式中，确定单元，还用于根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH的时频资源具体包括：确定单元，具体用于根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序、第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息 确定第一前导序列所对应的PUSCH时频资源。
一种可能的实现方式中，第三配置信息包含每个PUSCH时频资源的大小和参数N 8，参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
一种可能的实现方式中，确定单元，还用于根据第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源包括：确定单元，具体用于根据预设的PRACH时频资源到时频资源块的映射顺序、预设的前导序列到PUSCH时频资源的映射顺序、第一PRACH时频资源、第一前导序列、第二配置信息和第三配置信息确定第一前导序列所对应的PUSCH时频资源。
一种可能的实现方式中，确定单元，还用于根据预设的前导序列到DMRS端口的映射顺序，确定第一PRACH时频资源对应的PUSCH时频资源所关联的DMRS端口。
第四方面、提供了一种随机接入的装置，包括：通信单元，通信单元，用于向终端发送第一配置信息、第二配置信息和第三配置信息，第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，PUSCH时频资源块包括一个或者多个PUSCH时频资源；第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；通信单元，还用于接收终端发送的包含第一前导序列和上行数据的第一消息，其中，第一前导序列承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH时频资源上。
一种可能的实现方式中，第二配置信息包括用于配置PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
一种可能的实现方式中，第二配置信息包括第一映射图样的配置信息，第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
一种可能的实现方式中，第二配置信息包含用于配置PUSCH时频资源块的周期T1，第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 1，参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，参数N 1和第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包含参数N 2和参数N 3，参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
一种可能的实现方式中，第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
一种可能的实现方式中，第二配置信息包括参数N 4，参数N 4用于确定每个PRACH 时频资源所对应的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息包含参数N 5和参数N 6，参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，参数N 6用于确定周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
一种可能的实现方式中，第二配置信息还包含参数N 7和第二映射图样的信息，参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，参数N 7和第二映射图样用于确定周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
一种可能的实现方式中，第三配置信息包含每个PUSCH时频资源的大小和参数N 8，参数N8用于确定每个前导序列所对应的PUSCH时频资源的数量。
第五方面，提供了一种随机接入装置，该随机接入装置包括：处理器；可选的，还包括存储器、至少一个通信接口和通信总线中的一个或多个；存储器用于存储计算机执行指令，处理器、存储器和至少一个通信接口通过通信总线连接，处理器执行存储器存储的计算机执行指令，以使随机接入装置实现第一方面或第二方面提供的方法。该随机接入装置可以以芯片的产品形态存在。
第六方面，提供了一种通信系统，包括：第三方面和第四方面提供的随机接入装置。
第七方面，提供了一种计算机可读存储介质，包括指令，当该指令在计算机上运行时，使得计算机执行第一方面或第二方面中任一方面提供供任一种方法。
第八方面，提供了一种包含指令的计算机程序产品，当该指令在计算机上运行时，使得计算机执行第一方面或第二方面的任一方面提供的任一种方法。
第三方面至第八方面中的任一种设计方式所带来的技术效果可参见第一方面至第二方面中对应设计方式所带来的技术效果，此处不再赘述。
其中，需要说明的是，上述各个方面中的任意一个方面的各种可能的实现方式，在方案不矛盾的前提下，均可以进行组合。
附图说明
图1为现有技术中提供的一种随机接入流程示意图；
图2为本申请实施例提供的一种通信系统的组成示意图；
图3为现有技术中的一种5G NR帧结构的示意图；
图4为现有技术中的又一种5G NR帧结构的示意图；
图5A为本申请实施例提供的一种PRACH时频资源的编号方法的示意图；
图5B为本申请实施例提供的一种随机接入方法的流程示意图；
图5C为本申请实施例提供的一种频域资源的编号方法的示意图；
图5D为本申请实施例提供的一种配置两步随机接入过程PRACH时频资源的方法示意图；
图5E为本申请实施例提供的一种配置映射周期的方法的示意图；
图6为本申请实施例提供的一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图7为本申请实施例提供的另一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图8为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图9为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图10为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图11为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图12为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图13为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图14为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图15A为本申请实施例提供的配置PRACH时频资源的方法的示意图；
图15B为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图16为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图17为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图18为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图19为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图20为本申请实施例提供的又一种PRACH时频资源与PUSCH时频资源块映射方法的示意图；
图21为本申请实施例提供的一种前导序列与PUSCH时频资源映射方法的示意图；
图22为本申请实施例提供的另一种前导序列与PUSCH时频资源映射方法的示意图；
图23为本申请实施例提供的又一种前导序列与PUSCH时频资源映射方法的示意图；
图24A为本申请实施例提供的又一种前导序列与PUSCH时频资源映射方法的示意图；
图24B为本申请实施例提供的一种装置的结构示意图；
图25为本申请实施例提供的另一种装置的结构示意图；
图26为本申请实施例提供的又一种装置的结构示意图；
图27为本申请实施例提供的又一种装置的结构示意图；
图28为本申请实施例提供的又一种装置的结构示意图；
图29为本申请实施例提供的又一种装置的结构示意图。
具体实施方式
为了便于理解本申请，此处对本申请实施例涉及到的部分概念作简单介绍。
1、PRACH时频资源，也称为PRACH机会(occasion)
在5G新空口(new radio，NR)系统中，通常用PRACH机会表示一块用于发送前导的时频资源。每个PRACH时频资源上可以包含有64个前导序列，每个前导序列可以称为一个前导资源。PRACH时频资源根据PRACH时频资源的子载波间隔以及前导格式的不同占用不同大小的时频资源。
2、配置PRACH时频资源
网络侧配置PRACH时频资源具体包括配置时域资源和频域资源。
在网络侧配置PRACH时频资源的时域资源时，网络侧可以配置例如参数PRACH Configuration Index。UE侧可以根据参数PRACH Configuration Index和表一确定PRACH时频资源的时域资源。例如：若PRACH Configuration Index＝87，在所有满足帧号mod16＝0的无线帧的子帧#4(序号为4的子帧)和子帧#9(序号为9的子帧)发送，从符号#0(序号为0的OFDM符号)开始，一个子帧内只有一个PRACH时隙，每个PRACH时隙中有6个连续的PRACH时频资源，每个PRACH时频资源占用2个符号。需要说明的是，表一仅示出了部分PRACH时域资源的配置信息。
表一
Figure PCTCN2020075603-appb-000001
其中，
Figure PCTCN2020075603-appb-000002
为一个PRACH时隙中时域连续的PRACH时频资源的数量，
Figure PCTCN2020075603-appb-000003
为每个PRACH时频资源占用的符号个数。
在网络侧配置PRACH时频资源的频域资源时，网络侧可以配置PRACH时频资源的频域大小、频域起始位置，以及每个PRACH时域机会上有多少个频域连续的PRACH时频资源。
具体的，网络侧可以配置例如参数msg1-FrequencyStart，用于指示PRACH时频资源的频域起始位置。网络侧还可以配置例如参数msg1-FDM，用于指示每个PRACH时域机会有多少个频域连续的PRACH时频资源频分复用。网络侧还可以配置例如参数PRACH Configuration Index，用于指示PRACH时频资源的频域大小。具体的，UE侧可以根据参数PRACH Configuration Index，查找表一便可确定出前导格式(Preamble formats)。然后，根据前导格式、查找表二或表三可确定出前导的长度(L RA)和PRACH 时频资源的子载波间隔(Δf RA)。最后，可以根据前导的长度(L RA)和PRACH时频资源的子载波间隔(Δf RA)以及PUSCH时频资源的子载波间隔Δf，查找表四便可确定出PRACH时频资源的频域大小(即PRACH时频资源所占用的RB的数量
Figure PCTCN2020075603-appb-000004
)。
表二
Figure PCTCN2020075603-appb-000005
表三
Figure PCTCN2020075603-appb-000006
表四
Figure PCTCN2020075603-appb-000007
Figure PCTCN2020075603-appb-000008
3、5G NR的帧结构
5G NR支持多种子载波间隔，但是不同子载波间隔配置下，无线帧和子帧的长度是相同的。无线帧长度为10ms，子帧长度为1ms。
每个子帧中的时隙长度会因为子载波间隔不同而有所不同，一般是随着子载波间隔变大，时隙长度变小。因此，每个子帧中包含的时隙数不同。在正常循环前缀(Cyclic Prefix,CP)情况下，每个时隙包含的符号数相同，且都为14个。
例如：当子载波间隔配置为15Khz(正常CP)时，请参见图3所示，1个无线帧包含10个子帧(子帧的序号分别为#0到#9)，每个子帧仅有1个时隙，所以无线帧包含10个时隙，即子帧的序号与时隙的序号相同，子帧和时隙可以互相代替。每个时隙包含的14个OFDM符号(每个时隙中的OFDM符号的序号分别为#0到#13)。
需要说明的是，本申请中所有序号还可以理解为编号或者索引。
又例如：当子载波间隔配置为30Khz(正常CP)时，请参见图4所示，1个无线帧包含10个子帧(子帧的序号分别为#0到#9)，每个子帧仅有2个时隙(每个子帧中的时隙的序号为#0至#1)，所以无线帧包含20个时隙。每个时隙包含的14个OFDM符号(每个时隙中的OFDM符号的序号分别为#0到#13)。
在本申请实施例中，用“XX#n”的格式表示“序号为n的XX”。其中，n为正整数。“XX”可以为“无线帧”、“子帧”、“时隙”、“符号”、“PRACH时频资源”、“PRACH时频资源组”、“PUSCH时频资源块”、“PUSCH时频资源”等。例如：“子帧#4”表示序号为4的子帧。在此统一说明，以下不再赘述。
4、PRACH时频资源的序号
在本申请实施例中，PRACH时频资源的序号可以根据时域资源的序号和频域资源的序号确定。
其中，结合对5G NR帧结构的描述可知，时域资源的序号可以根据PRACH时频资源所占用的子帧的序号，占用时隙的序号(当占用多个时隙时，可以是起始时隙的序号或结束时隙的序号)、占用符号的序号(当占用多个符号时，可以是起始符号的序号或结束符号的序号)进行确定。
例如：时域资源的序号的升序，可以是按照PRACH时频资源所占用的子帧的序号的升序，占用时隙的序号的升序(当占用多个时隙时，可以是起始时隙的序号或结束时隙的序号的升序)、占用符号的序号的升序(当占用多个符号时，可以是起始符号的序号或结束符号的序号的升序)。
其中，结合对5G NR帧结构的描述可知，频域资源的序号可以根据PRACH时频资源占用RB的序号进行确定。当PRACH时频资源占用多个RB时，频域资源的序号可以根据PRACH时频资源占用的起始RB的序号，或结束RB的序号进行确定。
例如：频域资源序号的升序，可以是按照PRACH时频资源占用RB的序号的升序。当PRACH时频资源占用多个RB时，频域资源序号的升序可以是PRACH时频资源占 用的起始RB的序号或结束RB的序号的升序。
具体的，PRACH时频资源的序号，可以先按照频域资源的序号，再按照时域资源的序号进行确定。或者，PRACH时频资源的序号，也可以先按照时域资源的序号，再按照频域资源的序号进行确定。
例如：PRACH时频资源的序号的升序，可以是先按照频域资源的序号的升序，再按照时域资源序号的升序。
举个例子，请参见图5A所示，假设：PRACH时频资源的子载波间隔为15Khz，即一个子帧仅包含一个时隙。且在一个无线帧中，配置有4个PRACH时频资源，分别配置在子帧#1和子帧#6，且子帧#1和子帧#6上分别频分复用有2个PRACH时频资源。
如果是按照先频域资源的序号的升序，再按照时域资源序号的升序，对PRACH时频资源进行排序。那么，这4个PRACH时频资源的排序为：从最左侧的子帧#1开始，按PRACH时频资源占用的起始RB序号的升序，即子帧#1中下方的PRACH时频资源为PRACH时频资源#0，子帧#1中上方的PRACH时频资源为PRACH时频资源#1。然后，对子帧#6中的下方的PRACH时频资源为PRACH时频资源#2，子帧#6中的上方的PRACH时频资源为PRACH时频资源#3。
5、解调参考信号(Demodulation Reference Signal，DMRS)端口
DMRS端口可以通过天线端口表示，即不同天线端口对应的DMRS配置不同。如表五所示，为PUSCH DMRS配置类型1所对应的参数配置信息。由表五可知，PUSCH DMRS配置类型1最大可以支持8个天线端口，即可对应8种不同的DMRS配置，即8个DMRS端口。如表六所示，为PUSCH DMRS配置类型2所对应的参数配置信息。由表六可知，PUSCH DMRS配置类型2最大可以支持12个天线端口，对应12种不同的DMRS配置，即12个DMRS端口。
表五
Figure PCTCN2020075603-appb-000009
表六
Figure PCTCN2020075603-appb-000010
Figure PCTCN2020075603-appb-000011
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本申请中字符“/”，一般表示前后关联对象是一种“或”的关系。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例提供的技术方案可以应用于各种通信系统。例如，长期演进(long term evolution，LTE)通信系统，采用第五代(5th generation，5G)通信技术的新空口(new radio，NR)通信系统，未来演进系统或者多种通信融合系统等等。
本申请实施例提供的技术方案可以应用于多种通信场景。例如，机器对机器(machine to machine，M2M)、宏微通信、增强型移动宽带(enhanced mobile broadband，eMBB)、超高可靠超低时延通信(ultra-reliable&low latency communication，URLLC)以及海量物联网通信(massive machine type communication，mMTC)等场景。本申请实施例提供的技术方案应用的传输场景包括但不限于半静态调度(semi-persistent scheduling，SPS)、免授权、免调度、免动态调度、免动态授权以及高层配置等传输场景。这些通信场景和传输场景中的通信主体可以包括但不限于：通信设备与通信设备(例如，终端与终端)，网络设备与网络设备(例如，基站与基站)，网络设备与通信设备(例如，基站与终端)之间的通信场景等。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
图2是本申请的实施例应用的移动通信系统的架构示意图。如图2所示，该移动通信系统中包括终端100，终端100接入到无线网络，以通过无线网络获取外网(例如因特网)的服务，或者通过无线网络与其他终端通信。该无线网络包括无线接入网(radio access network，RAN)110。其中，RAN110用于将终端100接入到无线网络。RAN110可以包括无线接入网设备。
终端通过无线方式与无线接入网设备相连，并可以通过无线接入网设备接入到核心网中。终端100可以是固定位置的，也可以是可移动的。图2只是示意图，该通信系统中还可以包括其他网络设备，如还可以包括无线中继设备和无线回传设备，在图2中未画出。本申请的实施例对该移动通信系统中包括的无线接入网设备和终端的数量不做限定。
无线接入网设备和终端可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。本申请的实施例对无线接入网设备和终端的应用场景不做限定。
终端也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端可以是无线局域网(wireless local area networks，WLAN)中的站点(station，STA)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，第五代(fifth-generation，5G)通信网络中的终端或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端等。其中，5G还可以被称为新空口(new radio，NR)。
作为示例，在本申请实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
无线接入网设备可以是用于终端通过无线方式接入到移动通信系统中的接入设备。例如，无线接入网设备可以是网络设备。例如，网络设备可以是WLAN中的接入点(access point，AP)，可以是长期演进(long term evolution，LTE)中的演进型基站((evolved Node B，eNB或eNodeB)，还可以是NR中的基站(next generation Node B，gNB))。或者中继站或接入点，或者车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。
另外，在本申请实施例中，网络设备在小区中提供服务，终端通过该小区的传输资源(例如，频域资源，或者，时频资源)与网络设备进行通信。该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(metro cell)、微小区(micro cell)、微微小区(Pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小和发射功率低的特点，适用于提供高速率的数据传输服务。
本申请实施例提供的随机接入的方法和装置，可以应用于终端中，该终端包括硬 件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、以及即时通信软件等应用。并且，在本申请实施例中，对于随机接入方法的执行主体的具体结构，本申请实施例并未特别限定，只要能够实现本申请实施例的随机接入方法即可。
此外，本申请实施例的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
可以理解的是，本申请中的一种随机接入方法的执行主体可以为终端，或者为支持终端实现该方法的装置，例如应用于终端中的装置，例如，芯片系统。一种随机接入方法的执行主体可以为网络设备，或者为支持网络设备实现该方法的装置，例如应用于网络设备中的装置，例如，芯片系统。下述实施例中将以一种随机接入方法的执行主体为终端，以一种随机接入方法的执行主体为网络设备为例。
如图5B所示，图5B示出了本申请提供的一种随机接入方法，该方法包括：
S501、终端接收网络设备发送的第一配置信息、第二配置信息和第三配置信息。
其中，第一配置信息用于配置一个或多个PRACH时频资源和前导序列集合。其中，前导序列集合中包括一个或多个前导序列。即，网络设备通过第一配置信息，为终端两步随机接入过程中所能使用的PRACH时频资源和前导序列。
其中，第二配置信息用于配置每个PRACH时频资源所对应的PUSCH时频资源块。其中，PUSCH时频资源块中包含一个或多个PUSCH时频资源。即，网络设备通过第二配置信息，为每个PRACH时频资源配置相应的PUSCH时频资源块，该PUSCH时频资源块中的PUSCH时频资源可具体用于终端发送上行数据。
其中，第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH的时频资源的对应关系。即，网络设备通过第三配置信息，将每个PRACH时频资源中的每个前导序列，与PUSCH时频资源块中的每个时频资源进行关联。
这样，当终端在某个PRACH时频资源中选择任一个前导序列发送接入前导时，可以确定出该前导序列对应的PUSCH时频资源，并在对应的PUSCH时频资源上发送上行数据。同样，在网络设备接收到终端发送的一个接入前导时，网络设备可以确定出该接入前导对应的PUSCH时频资源，然后在该PUSCH时频资源上获取上行数据，以便完成该UE的随机接入过程，减少网络设备的盲检。
一些实施例中，网络设备可以通过发送广播消息，例如RRC消息，在RRC消息中携带第一配置信息、第二配置信息和第三配置信息。网络设备可以在一条RRC消息中同时携带第一配置信息、第二配置信息和第三配置信息。也可以在多条RRC消息中携带第一配置信息、第二配置信息和第三配置信息中任一项或任几项的部分或全部信息，本申请实施例对此不做具体限定。
另一些实施例中，网络设备也可以在终端处于RRC连接态时，通过特定的一条或多条消息携带第一配置信息、第二配置信息和第三配置信息。
其中，第一配置信息、第二配置信息以及第三配置信息中包含的具体内容，将在下文中详细说明，这里不再重复赘述。
S502、终端根据所述第一配置信息确定第一PRACH时频资源。
由于第一配置信息中包含有网络设备配置的，用于两步随机接入过程的PRACH时频资源。故终端可以根据第一配置信息确定可以用于随机接入过程的PRACH时频资源，并从中选择第一PRACH时频资源。
S503、终端确定需要在第一PRACH时频资源上发送的第一前导序列。
由于第一配置信息中包含有网络设备配置的，每个PRACH时频资源中用于发送接入前导的前导序列集合。故，终端可以根据第一配置信息，从第一PRACH时频资源上选择第一前导序列，用于随机接入过程。
S504、终端根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源。
由于第二配置信息中包含每个PRACH时频资源与PUSCH时频资源块的对应关系，故终端可以根据第一PRACH时频资源和第二配置信息，确定出第一PRACH时频资源对应的PUSCH时频资源块。进一步的，由于第三配置信息中包含有每个PUSCH时频资源大小，故可以确定出第一PRACH时频资源对应的PUSCH时频资源块包含的PUSCH时频资源。那么，在根据第三配置信息中前导序列与PUSCH时频资源的对应关系，可以确定出第一前导序列对应的PUSCH时频资源。
进一步，终端设备可以根据确定的第一PRACH时频资源，以及第一PRACH时频资源对应的PUSCH时频资源的位置关系确定PUSCH的子载波间隔配置。PUSCH的子载波间隔可以与该PUSCH时频资源所在的上行BWP的子载波间隔相同。在另一些实施例中，当PUSCH的频域资源在PRACH频域资源范围内，且PUSCH时频资源与PRACH时频资源在一个时隙内时，PUSCH的子载波间隔可以为与PRACH的子载波间隔相同。这样，当网络设备在处理PRACH时频资源和PUSCH时频资源上的信号时，可以在一个时隙中采用一个子载波间隔进行处理，有利于提高网络设备处理效率。
S505、终端发送第一前导序列和上行数据的第一消息。
其中，随机接入前导承载在第一PRACH时频资源上，上行数据承载在第一PRACH时频资源所对应的PUSCH的时频资源上。
需要说明的是，本申请方案除应用于两步随机接入场景的MsgA消息外，还可以应用于其他未获得定时同步的情况下发送数据信道的场景。本申请对此不做限定。
S506、终端接收网络设备发送的第二消息。
其中，第二消息为网络设备对第一前导序列和/或第一消息的响应，可以包含UE 标识、随机接入响应、冲突解决信息、TA信息等，本申请对此不做限定。
由此可见，终端可以根据网络设备配置的第一配置信息、第二配置信息以及第三配置信息，确定出用于前导序列与该前导序列对应的PUSCH时频资源。因此，终端可以直接发送包含第一前导序列和上行数据的第一消息，可以降低上行数据传输的时延。并且，网络设备也不需要向终端的每一次随机接入发送PUSCH时频资源的调度信息，可以降低信令开销。
以下，分别对网络设备配置的第一配置信息、第二配置信息和第三配置信息的具体内容进行详细说明。
一、第一配置信息
第一配置信息可以包括PRACH时频资源的时域资源的配置信息，和PRACH时频资源的频域资源的配置信息。
在本申请的一些实施例中，终端在两步随机接入过程中可以使用与四步随机接入过程相同的PRACH时频资源。由于现有系统中，网络设备为四步随机接入过程配置了PRACH时频资源，那么，网络设备不需要为两步随机接入过程另外配置PRACH时频资源。此时，第一配置信息可以理解为网络设备为四步随机接入过程PRACH时频资源的配置信息。具体的四步随机接入方法的PRACH时频资源的配置方法可以参考上文的描述。简单来说，网络设备可以通过向终端发送RRC消息，该RRC消息中的IE携带第一配置信息。例如：第一配置信息可以包括参数prach-ConfigurationIndex、参数Msg 1-FrequencyStart、参数Msg1-FDM等。
在本申请的另一些实施例中，网络设备为两步随机接入过程中Msg A单独配置的PRACH时频资源。网络设备为Msg A配置PRACH时频资源的方法，与现有系统中，网络设备为Msg 1配置的PRACH时频资源的方法相同。换言之，网络设备分别为四步随机接入过程和两步随机接入过程分别配置PRACH时频资源。例如：网络设备可以通过RRC中的两个不同的IE(IE的字段名称不同)分别配置Msg1对应的PRACH时频资源，和MsgA对应的PRACH时频资源。在这种情况下，第一配置信息包括网络设备为MsgA配置PRACH时频资源使用的配置信息。例如：第一配置信息可以包括参数prach-ConfigurationIndex、参数Msg A-FrequencyStart、参数MsgA-FDM等。其中，参数prach-ConfigurationIndex用于指示MsgA对应的PRACH时频资源对应的时域资源。参数Msg A-FrequencyStart用于指示PRACH时频资源对应的频域资源的起始位置。参数MsgA-FDM用于指示同一个时域资源中有多少个PRACH时频资源进行频分复用。
另外，当网络设备为两步随机接入过程Msg A单独配置的PRACH时频资源时，还可以为两步随机接入过程的PRACH单独配置子载波间隔。所述为两步随机接入过程的PRACH配置的子载波间隔可以与四步随机接入过程的PRACH子载波间隔相同，也可以与四步随机接入过程的PRACH子载波间隔不同。可选的，当网络设备没有为两步随机接入过程的PRACH单独配置子载波间隔时，可以默认两步随机接入过程的PRACH使用与四步随机接入过程的PRACH相同的子载波间隔。
需要说明的是，为避免同一时频资源(包括PRACH时频资源的时域资源的起始符号和所在的时隙相同)上，两步随机接入过程中PRACH时频资源的频域资源序号 与四步随机接入过程中PRACH时频资源的频域资源序号相同，进而造成计算PRACH时频资源对应的RA-RNTI时造成混乱。在本申请中，在同一时频资源上，可以将两步随机接入过程的PRACH时频资源的最小的频域资源序号可以设置为等于四步随机接入过程的PRACH时频资源的数量，并按照两步随机接入过程的PRACH时频资源的频域升序进行编号。即，先对四步随机接入过程中的PRACH时频资源的频域资源编号，再对两步随机接入过程的PRACH时频资源的频域资源进行编号。
例如：假设网络设备为四步随机接入过程Msg1配置的PRACH时频资源，以及为两步随机接入过程MsgA配置的PRACH时域资源如图5C所示，其中，为四步随机接入过程Msg1配置的PRACH时频资源的数量为2，则对两步随机接入过程MsgA配置的PRACH时频资源的频域资源进行编号时，将最小的频域资源的序号设置为2。
还需要说明的是，在网络设备单独为两步随机接入过程Msg A配置的PRACH时频资源时，可以配置部分参数，而未配置的参数(或缺省的参数)可以默认与为四步随机接入过程Msg1配置PRACH时频资源时配置的相应参数相同。例如：网络设备为两步随机接入过程配置频分复用参数MsgA-FDM，而没有配置prach-ConfigurationIndex和频域资源起始位置Msg A-FrequencyStart。那么，可认为两步随机接入过程是用和四步随机接入过程相同的时域资源配置prach-ConfigurationIndex和频域资源起始位置Msg 1-FrequencyStart，但使用不同的频域资源。在一些实施例中，在prach-ConfigurationIndex所指示的时域资源和Msg 1-FrequencyStart指示的频域资源起始位置，共有MsgA-FDM个PRACH时频资源，其中前Msg1-FDM个PRACH时频资源用于四步随机额接入，剩余的MsgA-FDM减Msg1-FDM个PRACH时频资源用于两步随机额接入。这样，在同一时域资源上，四步随机接入过程和两步随机接入过程所使用的频域资源不同，且频域资源的序号也不同，有利于后续计算所述PRACH时频资源对应的RA-RNTI。
例如：如图5D所示，假设网络设备为Msg1配置PRACH时频资源的时域资源和频域资源，其中，Msg1-FDM＝2。网络设备为MsgA仅配置了MsgA-FDM＝4。那么，可默认MsgA使用与Msg1的prach-ConfigurationIndex和Msg1FrequencyStart。在频域资源上，则前2个PRACH时频资源用于四步随机额接入，后2个PRACH时频资源用于两步随机额接入。
可以理解的是，网络设备为四步随机接入过程配置的PRACH时频资源，与网络设备为两步随机接入过程配置的PRACH时频资源可以相同，也可以不同。换言之，四步随机接入过程对应的PRACH时频资源与两步随机接入过程对应的PRACH时频资源可以不重叠，也可以全部或部分重叠。
需要说明的是，若两种随机接入过程对应的PRACH时频资源有重叠时，网络设备在接收到终端发送的前导序列后，可以通过盲检该前导序列对应的PUSCH资源(即采用本申请实施例提供的两步随机接入过程时该前导序列对应的PUSCH资源)的位置。如果在该PUSCH资源的位置检测到上行数据，则网络设备认为这是一个两步随机接入过程，否则，则网络设备认为是四步随机接入过程。需要说明的是，本申请实施例对当两种随机接入过程对应的PRACH时频资源有重叠时，网络设备对两种随机接入过程的区分方法不做具体限定。
在本申请的又一些实施例中，网络设备可以从现有系统中为随机接入配置的每一个PRACH时频资源对应的随机接入前导序列集合中，选择一个前导序列子集作为两步随机接入过程的PRACH随机接入前导，剩余前导序列用于四步随机接入过程的PRACH随机接入前导。
例如：PRACH时频资源中包括多个前导序列，其中M个前导序列用于随机接入，同时每个PRACH时频资源对应N个同步信号块(Synchronization Signal BlocQ，SSB)，其中网络设备配置在每个PRACH时频资源上对应于每个SSB的随机接入前导序列集合中有R个前导序列作为基于竞争的随机接入过程使用的PRACH随机接入前导。当N<1时，每个SSB对应于1/N个PRACH时频资源，则与SSB#0对应的每个PRACH时频资源上从前导序列索引#0开始的连续R个前导序列作为与SSB#0对应的基于竞争的随机接入的随机接入前导。当N≥1时，N个SSB对应1个PRACH时频资源，则在这个PRACH时频资源上，从前导索引#(n*M/N)开始的连续R个前导序列作为与SSB#n对应的基于竞争的随机接入的随机接入前导。M通过高层参数totalNumberOfRA-Preambles配置，N和R通过高层参数ssb-perRACH-OccasionAndCB-PreamblesPerSSB配置。
故网络设备可以从上述为基于竞争的随机接入配置的在每个PRACH时频资源上对应于每个SSB的随机接入前导序列集合中选择Q个前导序列作为基于竞争的两步随机接入过程使用的随机接入前导。这是因为：SSB与前导存在映射关系，而UE在选择前导前需先检测SSB的参考信号接收功率(Reference Signal Receiving Power，RSRP)，在RSRP大于阈值的SSB中选择一个SSB，然后从这个SSB对应的前导集合中选择一个前导发送。因此，从映射到同一SSB的前导集合中划分子集，可以保证UE在选择任何一个SSB时都能找到一个对应的两步接入的前导。
可选的，网络设备可以从为基于竞争的随机接入配置的在每个PRACH时频资源上对应于每个SSB的随机接入前导序列集合中选择前Q个前导，或后Q个前导，作为两步随机接入过程的PRACH时频资源。
在网络设备选择前Q个前导作为基于竞争的两步随机接入过程的PRACH时频资源时：当N<1时，每个SSB对应于1/N个PRACH时频资源，则与SSB#0对应的每个PRACH时频资源上从前导索引#0开始的连续Q个前导序列作为与SSB#0对应的基于竞争的两步随机接入的随机接入前导；当N≥1时，N个SSB对应1个PRACH时频资源，则在这个PRACH时频资源上，从前导索引#(n*M/N)开始的连续Q个前导序列作为与SSB#n对应的基于竞争的两步随机接入的随机接入前导。那么，第一配置信息除了包括网络设备为随机接入过程配置PRACH时频资源时使用的参数外，还可以包括参数Q、参数M、参数N和参数R。该参数Q可以用于指示网络设备从为基于竞争的随机接入过程配置的PRACH资源中选择前几个前导作为基于竞争的两步随机接入过程的PRACH时频资源，参数M通过高层参数totalNumberOfRA-Preambles配置，参数N和参数R通过高层参数ssb-perRACH-OccasionAndCB-PreamblesPerSSB配置。
在网络设备选择后Q个前导作为两步随机接入过程的PRACH时频资源时：当N<1时，每个SSB对应于1/N个PRACH时频资源，则与SSB#0对应的每个PRACH时频 资源上从前导索引#(R-Q+1)开始的连续Q个前导序列作为与SSB#0对应的基于竞争的两步随机接入的随机接入前导；当N≥1时，N个SSB对应1个PRACH时频资源，则在这个PRACH时频资源上，从前导索引#(n*M/N+R-Q+1)开始的连续Q个前导序列作为与SSB#n对应的基于竞争的两步随机接入的随机接入前导。那么，第一配置信息除了包括网络设备为随机接入过程配置PRACH时频资源时使用的参数外，还可以包括参数Q、参数M、参数N和参数R。该参数Q可以用于指示网络设备从为基于竞争的随机接入过程配置的PRACH资源中选择后几个前导作为基于竞争的两步随机接入过程的PRACH时频资源，参数M通过高层参数totalNumberOfRA-Preambles配置，参数N和参数R通过高层参数ssb-perRACH-OccasionAndCB-PreamblesPerSSB配置。
可选的，网络设备可以从为随机接入配置的在每个PRACH时频资源上对应于每个SSB的随机接入前导序列集合中选择中间Q个前导，作为两步随机接入过程的PRACH时频资源。N<1时，每个SSB对应于1/N个PRACH时频资源，则与SSB#0对应的每个PRACH时频资源上从前导索引#0开始的连续R个前导序列作为与SSB#0对应的基于竞争的四步随机接入的随机接入前导，从前导索引#R开始的连续Q个前导序列作为与SSB#0对应的两步随机接入的随机接入前导；当N≥1时，N个SSB对应1个PRACH时频资源，则在这个PRACH时频资源上，从前导索引#(n*M/N)开始的连续R个前导序列作为与SSB#n对应的基于竞争的四步随机接入的随机接入前导，从前导索引#(n*M/N+R)开始的连续Q个前导序列作为与SSB#n对应的基于竞争的四步随机接入的随机接入前导。那么，第一配置信息除了包括网络设备为随机接入过程配置PRACH时频资源时使用的参数外，还可以包括参数Q、参数M、参数N和参数R。该参数Q可以用于指示网络设备从为随机接入过程配置的PRACH资源中选择哪个前导作为基于竞争的两步随机接入过程的PRACH时频资源，参数M通过高层参数totalNumberOfRA-Preambles配置，参数N和参数R通过高层参数ssb-perRACH-OccasionAndCB-PreamblesPerSSB配置。
第一配置信息中还可以包括配置PRACH时频资源中的前导序列集合的信息，例如：第一配置信息中包括每个PRACH时频资源中含有前导序列的数量。
示例性的，若两步随机接入过程时使用的PRACH时频资源与四步随机接入过程相同时，每个PRACH时频资源中包含的前导序列的数量可以由高层参数totalNumberOfRA-Preambles确定。那么，前导序列集合为每个PRACH时频资源块中前totalNumberOfRA-Preambles个前导序列。当两步随机接入过程时使用的PRACH时频资源与四步随机接入过程相同时，每个PRACH时频资源中包含的前导序列的数量可以由高层参数totalNumberOfRA-Preambles确定。那么，前导序列集合为每个PRACH时频资源中前totalNumberOfRA-Preambles个前导序列。
若网络设备为两步随机接入过程单独配置了PRACH时频资源时，第一配置信息可以包括每个PRACH时频资源中包含的前导序列的数量U。那么，前导序列集合为每个PRACH时频资源中前U个前导序列。
若网络设备从四步随机接入过程使用的PRACH时频资源中选择了一个子集时，根据上文描述可知，前导序列集合包括Q个前导序列。即，前导序列集合为每个PRACH 时频资源中前Q个、或后Q个前导序列。
二、第二配置信息
一些实施例中，根据第二配置信息建立每个PRACH时频资源与PUSCH时频资源块的映射关系。
另一些实施例中，根据第二配置信息先建立每个PRACH时频资源与PUSCH时频资源块的映射关系，再根据预定义的规则，一个或多个PRACH时频资源组成PRACH时频资源组。由于每个PRACH时频资源组中的各个PRACH时频资源与PUSCH时频资源块已建立了映射关系，故相当于每个PRACH时频资源组也与PUSCH时频资源块建立了映射关系。
另一些实施例中，根据第二配置信息一个或多个PRACH时频资源先组成PRACH时频资源组，然后以PRACH时频资源组为单位，映射到相应的PUSCH时频资源块上。
在本申请实施例中，示例性的列举了两种配置每个PRACH时频资源所对应的用于上行传输的PUSCH时频资源块的方法。以下，结合附图对这两种方法中的各种可能的方式进行详细说明。
第一种方法：网络设备可以通过配置第一映射图样来确定用于上行传输的PUSCH时频资源块，以及每个PRACH时频资源与用于上行传输的PUSCH时频资源块的对应关系。
考虑到网络设备为两步随机接入过程配置的PRACH时频资源具有周期性(即PRACH周期)，网络设备配置的第一映射图样也可以具有周期性(即映射周期)。在本申请实施例中，网络设备可以配置第一映射图样的周期T1，也可理解为映射周期，即使用第一映射图样配置PUSCH资源块的周期。即，第二配置信息可以包括周期T1。其中，周期T1可以与PRACH周期相同，也可以是PRACH周期的整数倍，本申请实施例对此不做具体限定。
需要说明的是，如果网络设备没有配置第一映射图样的周期，即没有配置映射周期时，可以默认映射周期为PRACH的周期。
另外，映射周期的起始位置可以与PRACH周期的起始位置相同或不同。当映射周期的起始位置与PRACH周期不同时，即映射周期的起始位置与PRACH周期的起始位置存在时域偏移。该时域偏移的具体大小可以是网络设备配置的，也可以是预定义的。
如图5E所示，以一个PRACH周期为一个无线帧为例进行说明。映射周期与PRACH周期的时域偏移为1个时隙。图5E中还示出了PRACH周期内的PRACH时频资源，以及与各个PRACH时频资源映射的PUSCH时频资源块。可以看到，位于PRACH周期内最后一个时隙的PRACH时频资源可以与其所映射的PUSCH时频资源块位于同一映射周期内。
需要说明的是，当没有预定义该时域偏移，且网络设备也没有配置该时域偏移时，可以默认该时域偏移为零。
具体的，第二配置信息包括第一映射图像的信息。其中，第一映射图样用于确定至少一个PUSCH时频资源块的时域资源和频域资源。一个第一映射图样为一个映射周期(即周期T1)内包含的映射规则。这里的映射规则包括时域资源的配置信息和频 域资源的配置信息，故也可以称之为映射二元组。换言之，第一映射图样可以包括一个或多个映射二元组。一个映射二元组的每次映射时可以用于确定出一个PUSCH时频资源块的时频资源和频域资源，也就是说，一个映射二元组包括一个PUSCH时频资源块的时频资源的配置信息和频域资源的配置信息。示例性的，一个映射二元组可以表示为({K,S,L},{RB start,L RBs})，本申请实施例对映射二元组的表示形式不做限定。
可以理解的是，一个映射二元组也可以只包含一个PUSCH时频资源块的时域资源的配置信息，那么该PUSCH时频资源块的频域资源可以与PRACN资源的频域资源相同，或者与PRACH时频资源的频域资源具有预设的关系，或者为默认的频域资源。类似的，一个映射二元组也可以只包含一个PUSCH时频资源块的频域资源的配置信息，那么该PUSCH时频资源块的时域资源可以与PRACN资源的时域资源相同，或者与PRACH时频资源的时域资源具有预设的关系，或者为默认的时域资源。本申请实施例对此不做限定。
1、映射二元组用于配置PUSCH时频资源块的时频资源
举例来说，PUSCH时频资源块的时频资源的配置信息可以包括：相对于PRACH时频资源的时间偏移，以及每个PUSCH时频资源块的时域资源的长度。在一个具体的实现中，相对于PRACH时频资源的时间偏移可以是：PUSCH时频资源块的第一个符号所在时隙的序号与对应的PRACH时频资源的所占用的第一个时隙的序号(或最后一个时隙的序号)的差值K，以及PUSCH时频资源块在其起始时隙中的起始符号序号S。每个PUSCH时频资源块的时域资源的长度可以是每个PUSCH时频资源块所占用的连续符号数目L。其中，K值可为正数、负数和零。
其中，PUSCH时频资源块的时域资源配置是以PRACH时频资源的所占用的第一个时隙为参考还是以PRACH时频资源的所占用的最后一个时隙为参考是标准中预定义的，也可以是网络设备和UE事先约定的，还可以是网络设备通过指示信息通知UE的，指示信息可以是高层信令，如RRC消息，还可以层1层2指示信令，如媒体介入控制(media access control，MAC)-控制单元(control element，CE)信令，或下行控制信息(Downlink Control Information，DCI)。
示例性的，标准中可以预定义一个包含K、L和S关系的表格，如表七所示。那么，网络设备向终端发送的PUSCH时频资源块的时域资源的配置信息可以具体为表七中的行序号(row index)。终端在接收到该行序号后，可以根据表七查找该行序号对应的K、S和L的取值，以确定PUSCH时频资源块的时域资源。需要说明的是，表七中的数值仅为示例，K、S和L的取值还可以是其他数值，特此说明。
表七
Figure PCTCN2020075603-appb-000012
Figure PCTCN2020075603-appb-000013
再示例性的，网络设备在向UE发送PUSCH时频资源块的时域资源的配置信息时，也可以在RRC信息单元中至少包括K和startSymbolAndLength两个参数。UE可以根据K值和参数startSymbolAndLength，通过可以如下的规则计算得出S和L的取值。
Figure PCTCN2020075603-appb-000014
再示例性的，网络设备在向UE发送PUSCH时频资源块的时域资源的配置信息时，还可以在RRC信息单元中至少包括K、S和L三个参数。
再示例性的，网络设备在向UE发送PUSCH时频资源块的时域资源的配置信息时，还可以在RRC信息单元中至少包括K、S和L中的一个或多个参数。比如，RRC信息单元只包含S和L，那么可以默认PUSCH时频资源块的第一个符号位于PRACH时频资源所占用的时域资源后的第一个可用时隙。
而后，在UE侧获取了PUSCH时频资源块的时域资源的配置信息K、S和L，可以确定出PUSCH时频资源块的起始时隙的序号，起始符号的序号以及PUSCH时频资源块占用的符号长度。即，可以确定出PUSCH时频资源块对应的时域资源。
其中，上述确定出的PUSCH时频资源块的起始时隙为(n×θ)+K，其中，n为PRACH时频资源所占用的第一个时隙的序号(或最后一个时隙的序号)，这里PRACH时隙的序号指的是按照根据频率范围所假设的子载波间隔计算的。θ为根据PUSCH子载波间隔以及为PRACH时隙编号时假设的子载波间隔计算得到的参数。其中，根据标准文稿3GPP TS 38.211 V15.3.0中关于PRACH时频资源配置的时隙编号描述：当频谱范围为FR1(Frequency range 1)时，PRACH时频资源配置时隙编号所假设的子载波间隔为15kHz；当频谱范围为FR2时，PRACH时频资源配置时隙编号所假设的子载波间隔为60kHz。
示例性的，网络设备可以预先配置一个不同PUSCH子载波间隔与θ取值的对应 关系的表格，如表八所示，UE可以通过查表获取θ的取值。其中，μ msgAPUSCH为PUSCH资源的子载波间隔。
表八
μ msgAPUSCH θfor FR1 θfor FR2
0 1 0.25
1 2 0.5
2 4 1
3 8 2
4 16 4
再示例性的，UE也可以通过公式(1)计算得到θ取值。
Figure PCTCN2020075603-appb-000015
如果PRACH时隙的序号是按照PUSCH子载波间隔计算的，则上述确定出的PUSCH时频资源块的起始时隙为n+K。
2、映射二元组用于配置PUSCH时频资源块的频域资源
在本申请的一些实施例中，在网络设备配置PUSCH时频资源块的频域资源时，可以先配置该PUSCH时频资源块的频域资源的可选范围。例如：PUSCH时频资源块的频域资源的可选范围可以配置在上行BWP的频域资源范围内，也可以配置在与该PUSCH时频资源块关联的PRACH时频资源的频域资源范围内，还可以配置在与该PUSCH时频资源块关联的PRACH时频资源组的频域资源范围内。可选的，PUSCH频域资源的可选范围也可以是预定义的，本申请实施例对此不做限定。
可以理解的是，配置的PUSCH频域资源的可选范围的大小可以影响PUSCH频域资源配置信息的长度。当PUSCH频域资源的可选范围较大时，从该较大范围内确定PUSCH频域资源所需使用的配置信息的长度较大。当PUSCH频域资源的可选范围较小时，从该较小范围内确定PUSCH频域资源所需要使用的配置信息的长度较小。具体的，当PUSCH频域资源的可选范围的RB数量为Y时，共有(Y*(Y+1))/2种不同的起始资源块和连续资源块数量的组合，需要log 2((Y*(Y+1))/2)bits的频域资源配置信息，用于从上述可能的组合中指定其中一种。例如：当可选范围为6RB时，频域配置信息可以指示的频域资源总共有21种组合，那么配置信息需要的比特数至少为5bit。当可选范围为2RB时，频域配置信息可以指示的频域资源总共有3种组合，那么频域配置信息需要的比特数至少为2bit。比较可选范围分别为6RB和2RB时，频域配置信息所需要的比特数大小可知，可选范围较大时，所需要的PUSCH频域资源配置信息的长度较大。可选范围较小时，所需要的PUSCH频域资源配置信息的长度较小。
可选的，当PUSCH频域资源的可选范围不同时，后续对相同的频域资源的配置信息进行不同的解释。例如：当PUSCH频域资源的可选范围配置在上行BWP的频域资源范围内时，频域资源的配置信息的起始资源块(resource block，RB)序号RB start可解释为是当前激活的上行带宽分片(bandwidth part，BWP)的第一个RB开始编号 的。当前激活的BWP可以是初始BWP。又例如：当PUSCH频域资源的可选范围配置在与该PUSCH时频资源块关联的PRACH时频资源的频域资源范围内时，频域资源的配置信息的RB start可解释为与该PUSCH时频资源块关联的PRACH时频资源的第一个RB开始编号。
需要说明的是，当网络设备未配置PUSCH时频资源块的可选范围时，可以默认PUSCH时频资源块的可选范围为上行BWP的频域资源范围内。以下，以PUSCH的频域资源块的可选范围在上行BWP的频域资源范围内为例进行示例性说明。
在本申请一些实施例中，PUSCH时频资源块的频域资源的配置信息包括PUSCH时频资源块的起始资源块(resource block，RB)序号RB start，以及PUSCH时频资源块占用连续的RB的数目L RBs。其中，起始RB是从当前激活的上行带宽分片(bandwidth part，BWP)的第一个RB开始编号的。当前激活的BWP可以是初始BWP。PUSCH时频资源块与PRACH时频资源可以处于同一个BWP上，也可以处于不同BWP上。
示例性的，网络设备配置RB start和L RBs的一种可能的实现方式是，网络设备通过在RRC信息单元中至少包含参数startRBAndLength。
UE可以根据下面的规则计算出RB start和L RBs，如下：
Figure PCTCN2020075603-appb-000016
其中，
Figure PCTCN2020075603-appb-000017
表示当前激活的BWP所包含的RB数。
再示例性的，网络设备配置RB start和L RBs的另一种可能的实现方式是，网络设备通过在RRC信息单元中至少包含参数RB start和L RBs。
在本申请的另一些实施例中，PUSCH时频资源块的频域资源的配置信息包括PUSCH时频资源块起始RB的序号与PRACH时频资源起始RB序号的偏移值RB offset，以及PUSCH时频资源块占用连续的RB的数目L RBs。那么，UE可以根据PRACH时频资源起始RB的序号和RB offset计算得到PUSCH时频资源块的起始RB的序号。即，PUSCH时频资源块频域起始RB序号＝msgAprach-FrequencyStart+RB offset。然后再根据L RBs即可确定出PUSCH时频资源块的频域资源的位置。
在第一种方法的一种可能的实现方式中，第二配置信息还可以包括一个参数N 1，该参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。也就是说，每个PRACH时频资源对应N 1个PUSCH时频资源块。
在该实现方式中，网络设备根据配置的参数N 1，以及预设的PRACH时频资源到PUSCH时频资源块的映射顺序，能够确定出PUSCH时频资源块的位置及大小，且确定出PRACH时频资源与PUSCH时频资源块的映射关系。而后，再根据预定义的规则确定出PRACH时频资源组，确定出各个PRACH时频资源组对应的PUSCH时频资源块，以便后续根据第三配置信息进行PRACH时频资源组内前导与PUSCH时频资源块中的时频资源进行进一步映射。
其中，确定PRACH时频资源组的预定义规则可以是默认为每个PRACH时频资源 为一个PRACH时频资源组，即以PRACH时频资源为单位与PUSCH时频资源块映射。也可以是位于同一PRACH时域资源的PRACH时频资源构成一个PRACH时频资源组，或者可以是位于同一时隙的PRACH时频资源构成一个PRACH时频资源组。还可以是位于在时域连续的多个时隙的PRACH时频资源构成一个PRACH时频资源组。还可以是使用同一个映射二元组的PRACH时频资源构成一个PRACH时频资源组。本申请实施例对确定PRACH时频资源组的预定义规则不做具体限定。
根据上文对映射二元组的描述可知，每个PRACH时频资源使用一个映射二元组进行映射时，得到一个PUSCH时频资源块。那么，每个PRACH时频资源对应N 1个PUSCH时频资源块，也可以理解为，每个PRACH时频资源使用N 1个映射二元组进行映射，故得到该PRACH时频资源对应的N 1个PUSCH时频资源块。在本申请实施例中，用于上行传输的PUSCH时频资源块也可理解为PUSCH资源组，即PRACH时频资源使用N 1个映射二元组进行映射，得到该PRACH时频资源对应的N 1个PUSCH资源组。
那么，每个PRACH时频资源在使用N1个映射二元组进行映射时，根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射。
其中，预设的PRACH时频资源到PUSCH时频资源块的映射顺序可理解为按照PRACH时频资源的序号的顺序进行映射。示例性的，可以按照PRACH时频资源的序号的升序进行映射，其中，PRACH时频资源的序号的升序可以是先按照频域资源的序号的升序，再按照时域资源的序号的升序。
需要说明的是，网络设备在为终端配置第一映射图样时，第一映射图样中包含有一个或多个映射二元组。此时，当第一映射图样中包含多个映射二元组时，相当于网络设备也配置了这多个映射二元组的顺序。
那么，每个PRACH时频资源在使用N 1个映射二元组进行映射时，根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射，至少包含两层意思：一是每个PRACH时频资源映射的顺序，即哪个PRACH时频资源先映射，哪个PRACH时频资源后映射。二是每个PRACH时频资源映射时，按照第一映射图样中映射二元组的顺序，选择N 1个映射二元组进行映射。即每个PRACH时频资源映射时选择哪N 1个映射二元组进行映射。
以下，以网络设备配置如图5A所示的PRACH时频资源，且第一映射图样包含两个映射二元组为例，并结合附图进行示例性说明。
其中，第一映射图像为({K,S,L},{RB start,L RBs})＝{({1,0,14}{12,6}),({2,0,14}{6,6})}。可见，({1,0,14}{12,6})为第一个映射二元组，根据上述对映射二元组的解释可知，该映射二元组表示映射后的PUSCH时频资源块第一个符号所在的时隙位于PRACH时频资源所占用的时隙后的第1个时隙，这里即一个子帧，且起始符号为符号#0，占用14个符号，即一个子帧。起始RB为#12RB，占用6RB。({2,0,14}{6,6})为第二映射二元组。该映射二元组表示映射后的PUSCH时频资源块第一个符号所在的时隙位于PRACH时频资源所占用的时隙后的第2个时隙，这里即一个子帧，且起始符号为符号#0，占用14个符号，即一个子帧。起始RB为#6RB，占用6RB。
需要说明的是，在本示例中，由于PRACH时频资源在时域仅占用一个时隙，即 PRACH时频资源所占用的第一个时隙的序号和最后一个时隙的序号相同。在本申请的后续示例中，都以PRACH时频资源所占用的第一个时隙的序号为参考计算PUSCH时频资源块的时域资源。
例如：请参见图6，当网络设备配置的
Figure PCTCN2020075603-appb-000018
时，表示一个PRACH时频资源映射时使用
Figure PCTCN2020075603-appb-000019
个映射二元组，即两个PRACH时频资源使用一个映射二元组。在具体映射时，PRACH时频资源#0使用第一个映射二元组进行映射，PRACH时频资源#1也使用第一个映射二元组进行映射。PRACH时频资源#2使用第二个映射二元组进行映射，PRACH时频资源#3也使用第二个映射二元组进行映射。映射后得到的PUSCH时频资源块，以及PRACH时频资源与时频资源的对应关系如图6所示。
再例如：请参见图7，当网络设备配置的N 1＝1时，表示一个PRACH时频资源映射时使用1个映射二元组。在具体映射时，PRACH时频资源#0使用第一个映射二元组进行映射，PRACH时频资源#1使用第二个映射二元组进行映射。PRACH时频资源#2循环使用第一个映射二元组进行映射，PRACH时频资源#3使用第二个映射二元组进行映射。映射后得到的PUSCH时频资源块，以及PRACH时频资源与时频资源的对应关系如图7所示。
需要说明的是，网络设备在配置N 1＞1时，通常第一映射图样中包含的映射二元组为N 1的2倍及2倍以上。故这里以第一映射图样包含4个映射二元组为例进行说明。例如：第一映射图样为
({K,S,L},{RB start,L RBs})＝{({1,0,14}{12,6}),({2,0,14}{6,6}),({1,0,14}{18,6}),({1,0,14}{12,6})}。
再例如：请参见图8，当网络设备配置的N 1＝2时，表示一个PRACH时频资源映射时使用2个映射二元组。在具体映射时，PRACH时频资源#0使用第一个和第二个映射二元组进行映射，PRACH时频资源#1使用第三个和第四个映射二元组进行映射。PRACH时频资源#2循环使用第一个和第二个映射二元组进行映射，PRACH时频资源#3使用第三个和第四个映射二元组进行映射。映射后得到的PUSCH时频资源块，以及PRACH时频资源与时频资源的对应关系如图8所示。
以上图6至图8均是以映射周期与PRACH周期(PRACH时频资源的周期)相同为例进行说明的。上文也提到映射周期也可以是PRACH周期整数倍。那么，在映射时，是将映射周期内的全部PRACH按照预设的PRACH时频资源到PUSCH时频资源块的映射顺序，以及第一映射图样中的映射二元组的顺序进行映射，映射方法类似，以下以映射周期为PRACH周期的2倍为例进行说明。
再例如：如图9所示，除了映射周期为PRACH周期的2倍，即映射周期为20ms外，其余配置信息与图6一样。那么，在具体映射时，在第一个PRACH周期内，PRACH时频资源#0和PRACH时频资源#1使用第一个映射二元组进行映射，PRACH时频资源#2和PRACH时频资源#3使用第二个映射二元组进行映射。在第二个PRACH周期内，PRACH时频资源#0和PRACH时频资源#1使用第一个映射二元组进行映射，PRACH时频资源#2和PRACH时频资源#3使用第二个映射二元组进行映射。映射后得到的PUSCH时频资源块，以及PRACH时频资源与时频资源的对应关系如图9所示。
综上，当N 1＜1时，
Figure PCTCN2020075603-appb-000020
个PRACH时频资源使用同一个映射二元组。具体的，PRACH时频资源#
Figure PCTCN2020075603-appb-000021
到PRACH时频资源#
Figure PCTCN2020075603-appb-000022
使用映射二元组#modulo(g，G)，其中，g为映射二元组在第一映射图样中的序号，G表示第一映射图样中映射二元组的个数。当N 1＝1时，一个PRACH时频资源使用一个映射二元组。具体的，PRACH时频资源#g映射到映射二元组#modulo(g，G)。
当N 1＞1时，一个PRACH时频资源使用N 1个映射二元组。具体的，PRACH机会#g映射到映射二元组#modulo(g×N 1，G)到#modulo((g+1)×N 1-1，G)。
当确定PRACH时频资源组的预定义规则是默认为每个PRACH时频资源为一个PRACH时频资源组时，例如：图6至图9中PRACH时频资源#n构成PRACH时频资源组#n，PRACH时频资源组的顺序与PRACH时频资源的顺序相同。
当确定PRACH时频资源组的预定义规则是位于同一PRACH时域资源的PRACH时频资源构成一个PRACH时频资源组，或者可以是位于同一时隙的PRACH时频资源构成一个PRACH时频资源组时，例如：图6至图9中，PRACH时域资源#0和PRACH时域资源#1位于同一PRACH时域资源，也位于同一时隙，那么，PRACH时频资源#0和PRACH时频资源#1可构成一个PRACH时频资源组；PRACH时域资源#2和PRACH时域资源#3位于同一PRACH时域资源，也位于同一时隙，那么，PRACH时频资源#2和PRACH时频资源#3可构成一个PRACH时频资源组；
当确定PRACH时频资源组的预定义规则是使用同一个映射二元组的PRACH时频资源构成一个PRACH时频资源组时，例如：当N 1＜1时，如图6和图9所示，PRACH时频资源#0和PRACH时频资源#1使用同一个映射二元组，那么，PRACH时频资源#0和PRACH时频资源#1可构成一个PRACH时频资源组，为PRACH时频资源组#0；PRACH时频资源#2和PRACH时频资源#3可构成一个PRACH时频资源组，为PRACH时频资源组#1。当N 1＝1时，如图7所示，映射周期内每一个PRACH时频资源可为一个PRACH时频资源组，且PRACH时频资源组的顺序与PRACH时频资源的顺序相同。当N 1＞1时，如图8所示，映射周期内每一个PRACH时频资源可为一个PRACH时频资源组，且PRACH时频资源组的顺序与PRACH时频资源的顺序相同。
在第一种方法的另一种可能的实现方式中，第二配置信息还可以包括参数N 2，以及参数N 3，其中，参数N 2用于配置一个PRACH时频资源组中包含的PRACH时频资源的数量，参数N 3用于确定每个PRACH时频资源组所对应的PUSCH时频资源块的数量。
在该实现方式中，由于第二配置信息中包括了PRACH时频资源组的配置信息，即可以确定出PRACH时频资源组，那么可以使用PRACH时频资源组进行映射，得到每个PRACH时频资源组对应的PUSCH时频资源块。后续可以再根据第三配置信息进行PRACH时频资源组内前导与PUSCH时频资源块中的时频资源进行进一步映射。
需要注意的是，在确定PRACH时频资源组后，可以根据PRACH时频资源组中包含的PRACH时频资源的顺序进一步确定PRACH时频资源组的顺序。即，PRACH时频资源组的顺序可以按照包含的PRACH时频资源的频域资源顺序和时域资源顺序进 行确定。例如：PRACH时频资源组的顺序可以按照包含的PRACH时频资源的频域资源的升序，再按照包含的PRACH时频资源的时域资源的升序进行排序。此处PRACH时频资源组的顺序与PRACH时频资源的顺序类似，不再赘述。
进一步的，在确定PRACH时频资源组后，可以按照PRACH时频资源组到PUSCH时频资源块的映射顺序，以及第一映射图样中映射二元组的顺序进行映射。其中，PRACH时频资源组到PUSCH时频资源块的映射顺序可理解为PRACH时频资源组的顺序。
以下，以网络设备配置如图5A所示的PRACH时频资源为例，并结合附图进行示例性说明。
请参见图10，假设网络设备配置一个PRACH时频资源组包含两个PRACH时频资源，那么，根据PRACH时频资源的顺序可以将一个PRACH周期内的4个PRACH时频资源划分为2个PRACH时频资源组，PRACH时频资源组#0和PRACH时频资源组#1。
后续，PRACH时频资源组#0和PRACH时频资源组#1按照映射顺序使用第一映射图样中的映射二元组。
例如：请参见图11，假设：N 3＝1，映射周期与PRACH周期相同，均为10ms，第一映射图样包含一个映射二元组，例如：({K,S,L},{RB start,L RBs})＝{({1,0,14}{12,6})}。那么，PRACH时频资源组#0和PRACH时频资源组#1都使用该映射二元组进行映射。可见，PRACH时频资源组#0对应PUSCH时频资源块#0，PRACH时频资源组#1对应PUSCH时频资源块#1。
再例如：请参见图12，假设：N 3＝1，映射周期与PRACH周期相同，均为10ms，第一映射图样包含一个映射二元组，例如：({K,S,L},{RB start,L RBs})＝{({1,0,14}{})}。可见，该映射二元组只包含有时域资源的信息，那么可以默认映射后的PUSCH时频资源块的频域资源与PRACH时频资源组的频域资源相同。具体的，PRACH时频资源组#0和PRACH时频资源组#1都使用该映射二元组进行映射。可见，PRACH时频资源组#0对应PUSCH时频资源块#0，PRACH时频资源组#1对应PUSCH时频资源块#1。
再例如：请参见图13，假设：N 3＝1，映射周期与PRACH周期相同，均为10ms，第一映射图样包含两个映射二元组，例如：
({K,S,L},{RB start,L RBs})＝{({1,0,14}{12,6}),({2,0,14}{6,6})}。具体的，PRACH时频资源组#0使用第一个映射二元组进行映射，PRACH时频资源组#1使用第二个映射二元组进行映射。可见，PRACH时频资源组#0对应PUSCH时频资源块#0，PRACH时频资源组#1对应PUSCH时频资源块#1。
再例如：请参见图14，假设：映射周期为PRACH周期的两倍，即为20ms，第一映射图样包含四个映射二元组，例如：
({K,S,L},{RB start,L RBs})＝
{({1,0,14}{12,6}),({2,0,14}{6,6}),({-1,0,14}{12,6},({-1,0,14}{6,6}))}
那么需要将映射周期内包含的所有PRACH时频资源组(即包含两个PRACH周期内所有PRACH时频资源组)按照预设的映射顺序进行映射。具体的，PRACH时频资源组 #0使用第一个映射二元组进行映射，得到PUSCH时频资源块#0。PRACH时频资源组#1使用第二个映射二元组进行映射，得到PUSCH时频资源块#1。PRACH时频资源组#2使用第三个映射二元组进行映射，得到PUSCH时频资源块#2。PRACH时频资源组#3使用第四个映射二元组进行映射，得到PUSCH时频资源块#3。
第二种方法：先配置周期性的PUSCH时频资源块，然后配置周期性的映射规则，即第二映射图样，使得周期性的PRACH时频资源映射到周期性的PUSCH时频资源块。
与第一种方法类似的，考虑到网络设备为两步随机接入过程配置的PRACH时频资源具有周期性(即PRACH周期)，网络设备配置的第二映射图样也可以具有周期性(即映射周期)。在本申请实施例中，网络设备可以配置第二映射图像的周期T3，也可理解为映射周期，即使用第二映射图样配置PUSCH资源块的周期。即，第二配置信息可以包括周期T3。其中，周期T3可以与PRACH周期相同，也可以是PRACH周期的整数倍，本申请实施例对此不做具体限定。
需要说明的是，如果网络设备没有配置映射周期时，可以默认映射周期为PRACH的周期。
其中，映射周期的起始位置可以与PRACH周期的起始位置相同或不同。当映射周期的起始位置与PRACH周期不同时，即映射周期的起始位置与PRACH周期的起始位置存在时域偏移。该时域偏移的具体大小可以是网络设备配置的，也可以是预定义的。当没有预定义该时域偏移，且网络设备也没有配置该时域偏移时，可以默认该时域偏移为零。
在一些实施例中，第二配置信息还可以包括PUSCH时频资源块的周期T2、PUSCH时频资源块的时域资源的配置信息和/或频域资源的配置信息。
其中，在一个PUSCH时频资源块的周期里有一个PUSCH时频资源块。PUSCH时频资源块的时域资源的配置信息至少包括相对于无线帧#0的时域偏移、起始符号序号，以及在一个周期内所占用的连续的符号数量。PUSCH时频资源块的频域资源的配置信息至少包括起始RB序号以及在一个周期占用的连续RB数量。其中，起始RB序号时从当前激活的BWP的第一个RB开始编号的。当前激活的BWP可以是初始BWP。PUSCH时频资源块与PRACH时频资源可以处于同一BWP，也可以处于不同的BWP，本申请实施例对此不做限定。可以理解的是，第二配置信息中也可以有PUSCH时频资源块的时域资源的配置信息，没有频域资源的配置信息，那么，可以默认PUSCH时频资源块的频域资源与PRACH时频资源的频域资源相同，或者，与PRACH时频资源的频域资源具有预设的关系。类似的，第二配置信息中也可以有PUSCH时频资源块的频域资源的配置信息，没有时域资源的配置信息，那么，可以默认PUSCH时频资源块的时域资源与PRACH时频资源的时域资源相同，或者与PRACH时频资源的时域资源具有预设的关系，或者为默认的时域资源。
与第一种方法类似的，网络设备也可以配置PUSCH时频资源的频域资源的可选范围。例如:PUSCH时频资源块的频域资源的可选范围可以配置在上行BWP的频域资源范围内，也可以配置在与该PUSCH时频资源块关联的PRACH时频资源的频域资源范围内，还可以配置在与该PUSCH时频资源块关联的PRACH时频资源组的频域资源范围内。可选的，PUSCH频域资源的可选范围也可以是预定义的，本申请实施例对 此不做限定。其他内容可参考第一种方法中相关内容的描述，这里不再赘述。
以上，是以在配置周期性PUSCH时频资源块时，只配置一组PUSCH时频资源块为例进行说明的。在另一些实施例中，网络设备也可以配置多组(两组以及两组以上)PUSCH时频资源块。即，第二配置信息还可以包括多组PUSCH时频资源块的配置信息，每一组PUSCH时频资源块的配置信息可以包括该组PUSCH时频资源块的周期、PUSCH时频资源块的时域资源的配置信息和/或频域资源的配置信息。也可理解为，第二配置信息可以包括多个PUSCH时频资源块的周期T2、以及每个周期T2内对应的PUSCH时频资源块的时域资源的配置信息和/或频域资源的配置信息。
例如：如图15A所示，配置有两组PUSCH时频资源块。编号为#0的PUSCH时频资源块为第0组PUSCH时频资源块。编号为#1的PUSCH时频资源块为第1组PUSCH时频资源块。
需要说明的是，这多组PUSCH时频资源块的周期、时域资源的配置信息和/或频域资源的配置信息可以相同，也可以不同。
还需要说明的是，这多组PUSCH时频资源块的周期、时域资源的配置信息和/或频域资源的配置信息中可以缺省其中任一项或任几项的参数配置。若某一组PUSCH时频资源块的配置信息中的任一项或任几项参数缺省时，可以默认该组PUSCH时频资源块使用相应的其他组PUSCH时频资源块配置的数值。若这多组PUSCH时频资源块的配置信息都缺省时，可以默认这多组PUSCH时频资源块的配置信息与PRACH时频资源的配置信息。
例如：第二配置信息中包含2组PUSCH时频资源块的配置信息，但只有一组PUSCH时频资源块的配置信息配置了周期T2，其余一组PUSCH时频资源块的配置信息中没有周期配置信息，则这两组PUSCH时频资源块的周期都为T2。
又例如：第二配置信息中包含2组PUSCH时频资源块的配置信息，但两组PUSCH时频资源块的配置信息都没有周期配置信息，则这两组PUSCH时频资源块的周期都为对应的PRACH资源周期。
在另一些实施例中，第二配置信息还可以包括PUSCH时频资源块所关联的DMRS端口的信息。这是因为对于时域资源和频域资源相同的PUSCH时频资源块来说，若其关联的DMRS端口不同，网络设备也可以识别出这是不同的PUSCH资源。也就是说，可以用时域资源、频域资源以及DMRS端口的信息来说确定出一个PUSCH资源。因此，在网络设备配置PUSCH时频资源块时，也可以配置PUSCH时频资源块所关联的DMRS的信息，即第二配置信息中包含DMRS的配置信息。其中，DMRS端口的信息包含以下任一种或任几种参数：DMRS类型、额外的DMRS位置、DMRS占用的时域符号数、扰码ID。其中，扰码ID或参考信号ID用于生成DMRS序列，既不同的扰码ID或参考信号ID可以生成不同的DMRS序列。如果网络未配置扰码ID或参考信号ID，则UE可以使用所在小区的ID。网络设备可以通过指示信息配置一个或者多个扰码ID或参考信号ID来增加PUSCH时频资源所关联的DMRS端口数量，从而减少DMRS碰撞的概率。指示信息可以是高层信令，如RRC消息，还可以层1层2指示信令，如MAC CE或DCI。
在周期性的PUSCH时频资源块的位置确定后，可进一步配置在一个映射周期内， 每个PRACH时频资源与PUSCH时频资源块的映射关系。
在第二种方法的一种可能的实现方式中，第二配置信息还可以包括参数N 4，所述参数N 4用于确定每个PRACH时频资源映射到PUSCH时频资源块的数量。
在该实现方式中，第二配置信息可通过配置参数N 4，以及预设的映射顺序，将配置的PRACH时频资源与PUSCH时频资源块建立映射关系，然后，可根据预定义的规则确定PRACH时频资源组。由于PRACH时频资源组中的PRACH时频资源与PUSCH时频资源块已建立映射关系，那么，也相当于PRACH时频资源组与PUSCH时频资源块也建立了映射关系。
确定PRACH时频资源组的预定义规则可以是默认为每个PRACH时频资源为一个PRACH时频资源组，即以PRACH时频资源为单位与PUSCH时频资源块映射。也可以是位于同一PRACH时域资源的PRACH时频资源构成一个PRACH时频资源组，或者可以是位于同一时隙的PRACH时频资源构成一个PRACH时频资源组。还可以是位于在时域连续的多个时隙的PRACH时频资源构成一个PRACH时频资源组。还可以是映射到同一PUSCH时频资源块的PRACH时频资源构成一个PRACH时频资源组。本申请实施例对确定PRACH时频资源组的规则不做具体限定。
具体的，在一个映射周期内，每个PRACH时频资源按照预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射。例如：在一个映射周期内，按照先频域资源序号的升序再时域资源序号的升序的顺序，进行映射。
可以理解的是，当PUSCH时频资源块确定时，相当于PUSCH时频资源块的顺序也确定，可以按照PUSCH时频资源块占用时域资源的顺序进行确定。例如：可以按照PUSCH时频资源块占用的时域资源的升序进行排序。
那么，在每个PRACH时频资源映射到N 4个PUSCH时频资源块时，根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射，至少包含两层意思：一是每个PRACH时频资源映射的顺序，即哪个PRACH时频资源先映射，哪个PRACH时频资源后映射。二是每个PRACH时频资源映射时，按照PUSCH时频资源块的顺序，映射到N 4个PUSCH时频资源块。即每个PRACH时频资源映射时具体映射到哪N 4个时频资源块。
需要说明的是，在一个映射周期内，PRACH时频资源的数量大于PUSCH时频资源块的数量时，意味着PRACH时频资源按预设的映射顺序映射时，会循环映射到PUSCH时频资源块，直到该映射周期内的所有PRACH时频资源都至少映射到一个PUSCH时频资源块结束。例如：一个映射周期内包含PUSCH时频资源块#0和PUSCH时频资源块#1，包含PRACH时频资源#0只PRACH时频资源#3。那么，在PRACH时频资源#0映射到PUSCH时频资源块#0，PRACH时频资源#1映射到PUSCH时频资源块#1后，PRACH时频资源#3映射时，将映射到PUSCH时频资源块#0。PRACH时频资源#3映射时，将映射到PUSCH时频资源块#1。
以下，结合附图对该实现方式中PRACH时频资源与PUSCH时频资源块的映射关系，进行示例性说明。
假设根据上述PUSCH时频资源块的配置方法，网络设备配置了如图15B所示的PUSCH时频资源块。其中，每个PRACH周期内包含4个PRACH时频资源。而每个 PRACH周期内包含的PUSCH时频资源块可能不同，如图15B中，一个PRACH周期中包含4个PUSCH时频资源块，另一个PRACH周期中包含3个PUSCH时频资源块。根据上文的描述，PUSCH时频资源块的顺序可以根据PUSCH时频资源块的时域资源的序号顺序进行确定。这里以PUSCH时频资源块的顺序按照PUSCH时频资源块的时域资源的序号升序进行排序为例进行说明。
例如：请参见图16所示，示出了两个映射周期中PRACH时频资源与PUSCH时频资源块的映射关系。假设网络设备配置的映射周期和PRACH周期相同。当网络设备配置的N 4＝1/2时，表示每个PRACCH资源映射到1/2个PUSCH时频资源块，也就是每2个PRACH时频资源映射到一个PUSCH时频资源块。在具体映射时，在一个映射周期内PRACH时频资源#0和PRACH时频资源#1映射到PUSCH时频资源块#0。PRACH时频资源#2和PRACH时频资源#3映射到PUSCH时频资源块#1。另一个映射周期内的映射方法类似，不再赘述。
在一些实施例中，第二配置信息还可以包括一些映射规则的信息，即网络设备也可以配置一些映射规则，例如：PRACH时频资源与自身映射对应的PUSCH时频资源块，在时域上不能重叠。又例如：PRACH时频资源与自身映射对应的PUSCH时频资源块，在频域上不能重叠。可以理解的是，该映射规则也可以是预先定义的，即不需要网络设备进行配置。本申请实施例对此不作限定。
那么，在这种情况下，参数N 4用于确定每个PRACH时频资源映射到有效的PUSCH时频资源块的数量。其中，有效的PUSCH时频资源块为符合映射规则的PUSCH时频资源块。每个PRACH时频资源映射到有效的PUSCH时频资源块的映射方法与上述方法相同，这里不再赘述。
再例如：请参见图17所示，示出了两个映射周期中PRACH时频资源与PUSCH时频资源块的映射关系。假设网络设备配置的映射周期和PRACH周期相同，且配置了映射规则：PRACH时频资源与自身映射对应的PUSCH时频资源块，在时域上不能重叠。当网络设备配置的N 4＝1时，表示每个PRACCH资源映射到1个PUSCH时频资源块。在具体映射时，在一个映射周期内，PRACH时频资源#0映射到PUSCH时频资源块#0。PRACH时频资源#1映射到PUSCH时频资源块#1。PRACH时频资源#2根据映射顺序，应该映射到PUSCH时频资源块#2。由于PUSCH时频资源块#2与PRACH时频资源#2位于同一时域上，故PRACHPUSCH时频资源块#2向后映射，映射到PUSCH时频资源块#3。PRACH时频资源#3继续映射到PUSCH时频资源块#0。另一个映射周期内的映射方法类似，不再赘述。
需要说明的是，网络设备在配置N 4＞1时，通常一个映射周内包含的PUSCH时频资源块的数量应为N 4的2倍及2倍以上。因此，为了便于说明，这里以一个映射周期包含5个PUSCH时频资源块，一个映射周期内包含有2个PRACH时频资源为例进行说明。
又例如：请参见图18所示，示出两个映射周期中PRACH时频资源与PUSCH时频资源块的映射关系。假设网络设备配置的映射周期和PRACH周期相同。当网络设备配置的N 4＝2时，表示每个PRACH资源映射到2个PUSCH时频资源块。在具体映射时，在一个映射周期内，PRACH时频资源#0映射到PUSCH时频资源块#0和PUSCH 时频资源块#1。PRACH时频资源#1映射到PUSCH时频资源块#2和PUSCH时频资源块#3。另一个映射周期内的映射方法类似，不再赘述。
以上图16至图18均是以映射周期与PRACH周期(PRACH时频资源的周期)相同为例进行说明的。上文也提到映射周期也可以是PRACH周期整数倍。那么，在映射时，是将映射周期内的全部PRACH按照预设的PRACH时频资源到PUSCH时频资源块的映射顺序，以及PUSCH时频资源块的顺序进行映射，映射方法类似，以下以映射周期为PRACH周期的2倍为例进行说明。
又例如：除了映射周期为PRACH周期的2倍，即映射周期为20ms外，其余配置信息与图16一样。需要注意的是，在第二个PRACH周期内的PUSCH时频资源块的序号发生变化。那么，在具体映射时，第一PRACH周期内，各个PRACH时频资源的映射关系与图16相同，不再赘述。在第二个PRACH周期内，PRACH时频资源#0映射到时频资源#4和时频资源#6，PRACH时频资源#1映射到时频资源#6和时频资源#7。
综上，当网络设备配置的N 4<1时，表示
Figure PCTCN2020075603-appb-000023
个PRACH时频资源映射到一个PUSCH时频资源块。当网络设备配置的N 4＝1时，表示一个PRACH时频资源映射到一个PUSCH时频资源块。当网络设备配置的N 4>1时，表示一个PRACH时频资源映射到N 4个PUSCH时频资源块。
当确定PRACH时频资源组的预定义规则是默认为每个PRACH时频资源为一个PRACH时频资源组时，例如：图16至图19中PRACH时频资源#n构成PRACH时频资源组#n，PRACH时频资源组的顺序与PRACH时频资源的顺序相同。
当确定PRACH时频资源组的预定义规则是位于同一PRACH时域资源的PRACH时频资源构成一个PRACH时频资源组，或者可以是位于同一时隙的PRACH时频资源构成一个PRACH时频资源组时，例如：图16至图17中，PRACH时域资源#0和PRACH时域资源#1位于同一PRACH时域资源，也位于同一时隙，那么，PRACH时频资源#0和PRACH时频资源#1可构成一个PRACH时频资源组；PRACH时域资源#2和PRACH时域资源#3位于同一PRACH时域资源，也位于同一时隙，那么，PRACH时频资源#2和PRACH时频资源#3可构成一个PRACH时频资源组。又例如：图18至图19中，所有PRACH时频资源都位于不同PRACH时域资源，且都位于不同时隙，因此PRACH时频资源#n构成PRACH时频资源组#n，PRACH时频资源组的顺序与PRACH时频资源的顺序相同。
当确定PRACH时频资源组的预定义规则是使用同一个映射二元组的PRACH时频资源构成一个PRACH时频资源组时，例如：当N 1＜1时，如图16所示，PRACH时频资源#0和PRACH时频资源#1映射到同一PUSCH时频资源块，那么，PRACH时频资源#0和PRACH时频资源#1可构成一个PRACH时频资源组，为PRACH时频资源组#0；PRACH时频资源#2和PRACH时频资源#3可构成一个PRACH时频资源组，为PRACH时频资源组#1。又例如：当N 1＝1时，如图17所示，映射周期内每一个PRACH时频资源可为一个PRACH时频资源组，且PRACH时频资源组的顺序与PRACH时频资源的顺序相同。又例如：当N 1＞1时，如图8所示，映射周期内每一个PRACH时频资源可为一个PRACH时频资源组，且PRACH时频资源组的顺序与PRACH时频资源的顺序相同。
在第二种方法的另一种可能的实现方式中，第二配置信息还可以包括含参数N 5和参数N 6。
在该实现方式中，网络设备可以通过第二配置信息中的参数N 5配置每个PRACH时频资源组所包含PRACH时频资源的数量。再通过参数N 6，将PRACH时频资源组与PUSCH时频资源块建立映射关系。
具体的，所述参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量。那么，UE可以根据预设的PRACH时频资源的顺序，按照每N 5个PRACH时频资源构成一个PRACH时频资源组的规则，确定出各个PRACH时频资源组。
需要注意的是，在确定PRACH时频资源组后，可以根据PRACH时频资源组中包含的PRACH时频资源的顺序进一步确定PRACH时频资源组的顺序。即，PRACH时频资源组的顺序可以按照包含的PRACH时频资源的频域资源顺序和时域资源顺序进行确定。例如：PRACH时频资源组的顺序可以按照包含的PRACH时频资源的频域资源的升序，再按照包含的PRACH时频资源的时域资源的升序进行排序。此处PRACH时频资源组的顺序与PRACH时频资源的顺序类似，不再赘述。
所述参数N 6用于确定每个PRACH时频资源组映射到PUSCH时频资源块的数量。
在一个映射周期内，每个PRACH时频资源组按照预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射。其中，预设的PRACH时频资源到PUSCH时频资源块的映射顺序可以是按照PRACH时频资源组的序号进行映射。
可以理解的是，当PUSCH时频资源块确定时，相当于PUSCH时频资源块的顺序也确定，可以按照PUSCH时频资源块占用时域资源的顺序进行确定。例如：可以按照PUSCH时频资源块占用的时域资源的升序进行排序。
那么，在每个PRACH时频资源组映射到N 6个PUSCH时频资源块时，根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序进行映射，至少包含两层意思：一是每个PRACH时频资源组映射的顺序，即哪个PRACH时频资源组先映射，哪个PRACH时频资源组后映射。二是每个PRACH时频资源组映射时，按照PUSCH时频资源块的顺序，映射到N 6个PUSCH时频资源块。即每个PRACH时频资源映射时具体映射到哪N 6个PUSCH时频资源块。
需要说明的是，在一个映射周期内，PRACH时频资源组的数量大于PUSCH时频资源块的数量时，意味着PRACH时频资源组按预设的映射顺序映射时，会循环映射到PUSCH时频资源块，直到该映射周期内的所有PRACH时频资源组都至少映射到一个PUSCH时频资源块结束。
在一些实施例中，第二配置信息还可以包括一些映射规则的信息，即网络设备也可以配置一些映射规则，例如：PRACH时频资源组与自身映射对应的PUSCH时频资源块，在时域上不能重叠。又例如：PRACH时频资源组与自身映射对应的PUSCH时频资源块，在频域上不能重叠。可以理解的是，该映射规则也可以是预先定义的，即不需要网络设备进行配置。本申请实施例对此不作限定。
那么，在这种情况下，参数N 5用于确定每个PRACH时频资源组映射到有效的PUSCH时频资源块的数量。其中，有效的PUSCH时频资源块为符合映射规则的PUSCH时频资源块。每个PRACH时频资源组映射到有效的PUSCH时频资源块的映射方法与 上述方法相同，这里不再赘述。
例如：请参见图16，假设PRACH时频资源和PUSCH时频资源块的配置情况如图16所示。那么，当网络设备配置N 5＝2，N 6＝1时，表示每2个PRACH时频资源构成一个PRACH时频资源组，且每个资源组映射到一个PUSCH时频资源块上。因此，可以确定出：在第一个映射周期内，PRACH时频资源#0和PRACH时频资源#1构成PRACH时频资源组#0，PRACH时频资源#2和PRACH时频资源#3构成PRACH时频资源组#1。在映射时，PRACH时频资源组#0映射到PUSCH时频资源块#0，PRACH时频资源组#2映射到PUSCH时频资源块#1。第二个映射周期内的映射情况类似，不再赘述。
再例如：请参见图17，假设PRACH时频资源和PUSCH时频资源块的配置情况如图17所示，且网络设备配置了映射规则：PRACH时频资源组与其所映射的PUSCH时频资源块不能在同一时域上。那么，当网络设备配置N 5＝1，N 6＝1时，表示每一个PRACH时频资源构成一个PRACH时频资源组，且每个资源组映射到一个PUSCH时频资源块上。因此，可以确定出：在第一个映射周期内，PRACH时频资源#0构成PRACH时频资源组#0，且映射到PUSCH时频资源块#0。PRACH时频资源#1构成PRACH时频资源组#1，且映射到PUSCH时频资源块#1。PRACH时频资源#2构成PRACH时频资源组#2，且映射到PUSCH时频资源块#3。PRACH时频资源#3构成PRACH时频资源组#3，且映射到PUSCH时频资源块#1。第二个映射周期内的映射情况类似，不再赘述。
又例如：请参见图18，假设PRACH时频资源和PUSCH时频资源块的配置情况如图18所示，且网络设备配置了映射规则：PRACH时频资源组与其所映射的PUSCH时频资源块不能在同一时域上。那么，当网络设备配置N 5＝1，N 6＝2时，表示每一个PRACH时频资源构成一个PRACH时频资源组，且每个资源组映射到2个PUSCH时频资源块上。因此，可以确定出：在第一个映射周期内，PRACH时频资源#0构成PRACH时频资源组#0，且映射到PUSCH时频资源块#0和PUSCH时频资源块#2。PRACH时频资源#1构成PRACH时频资源组#1，且映射到PUSCH时频资源块#1和PUSCH时频资源块#3。第二个映射周期内的映射情况类似，不再赘述。
在第二种方法的又一种可能的实现方式中，第二配置信息还可以包括含参数N 7和第二映射图样的信息。
在该实现方式中，网络设备可以通过第二配置信息中的参数N 7配置每个PRACH时频资源组所包含PRACH时频资源的数量。再通过第二映射图样，将PRACH时频资源组与PUSCH时频资源块建立映射关系。
具体的，所述参数N 7用于确定每个PRACH时频资源组包含的PRACH时频资源的数量。参数N 7的含义和作用与上述实现方式中参数N 5相同，这里不再赘述。
在根据参数N 7将配置好的PRACH时频资源划分到各个PRACH时频资源组后，即确定出各个PRACH时频资源组后，可以对各个PRACH时频资源组进行映射。
所述第二映射图样用于确定至少一个PUSCH时频资源块。示例性的，第二映射图样可以是一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号。上文已说明，当各个PUSCH时频资源块确定时，相当于各个时频块的顺 序也确定了，那么该PUSCH时频资源块的序号可根据PUSCH时频资源块的顺序进行确定。例如：PUSCH时频资源块的序号可按照PUSCH时频资源块在时域资源上的升序进行排序。
例如：请参见图20，假设PRACH时频资源和PUSCH时频资源块的配置情况如图20所示，且网络设备配置的映射周期为PRACH周期的两倍。当网络配置的N 7＝1，第二映射图样为{(#0,#2),(#1,#3),(#4,#5),(#6,#7)}。那么，在具体映射时，在一个映射周期内，每个PRACH时频资源都构成一个PRACH时频资源组，分别为PRACH时频资源组#0至PRACH时频资源组#3。而后，按照第二映射图样中的映射序号的顺序进行映射。即，PRACH时频资源组#0使用第一个序号集合，映射到PUSCH时频资源块#0和PUSCH时频资源块#2；PRACH时频资源组#1使用第二个序号集合，映射到PUSCH时频资源块#1和PUSCH时频资源块#3；PRACH时频资源组#2使用第三个序号集合，映射到PUSCH时频资源块#4和PUSCH时频资源块#5；PRACH时频资源组#3使用第四个序号集合，映射到PUSCH时频资源块#6和PUSCH时频资源块#7。
三、第三配置信息
根据上文的描述可知，可以根据第一配置信息和第二配置信息最终确定出PRACH时频资源组和PUSCH时频资源块的映射关系。进一步的，网络设备可以通过配置第三配置信息，将PRACH时频资源组内的前导序列与PUSCH时频资源块中的每个PUSCH时频资源建立映射关系。由于PRACH时频资源组可以包含一个或多个PRACH时频资源，因此，每个PRACH时频资源组中包含的前导序列的数量也可以有多种情况。因此，采用该方法配置第三配置信息，可以更加灵活的建立前导序列与PUSCH时频资源的映射关系，满足多种需求。
当然，可以理解的是，根据上文的描述也可知，可以根据第一配置信息和第二配置信息确定出PRACH时频资源和PUSCH时频资源块的映射关系。那么，网络设备也可以通过第三配置信息，直接将每个PRACH时频资源中包含的前导序列与PUSCH时频资源建立映射关系。第三配置信息的具体配置方法相似。
以下，以网络设备配置PRACH时频资源组内的前导序列与PUSCH时频资源块中的每个PUSCH时频资源的映射关系为例，对第三配置信息的配置方法进行示例性说明。
具体的，需要先确定出每个PRACH时频资源组中包含的前导序列，以及每个PUSCH时频资源块中包含的PUSCH时频资源。
其中，根据上文对第一配置信息的描述可知，根据第一配置信息可以确定出每个PRACH时频资源中的前导序列集合，即每个PRACH时频资源中包含的前导序列。又可以根据第二配置信息可以确定每个PRACH时频资源组中包含的PRACH时频资源。那么，可确定出每个PRACH时频资源组中包含的前导序列的信息。
在一些实施例中，第三配置信息可以包括PUSCH时频资源块中每个PUSCH时频资源的大小信息。每个PUSCH时频资源的大小信息例如可以是每个PUSCH时频资源占用的连续的符号数目，以及占用的连续的RB的数目。那么，根据每个PUSCH时频资源的大小，按照时域资源和频域资源顺序可以确定出各个PUSCH时频资源。
可选的，第三配置信息还可以包括相邻PUSCH时频资源之间的时域间隔或频域 间隔。也就是说，第三配置信息还可以配置PUSCH时频资源块中的PUSCH时频资源是否连续，以及不连续时的间隔大小。示例性的，若时域间隔和频域间隔均为零，或者第三配置信息中没有时域间隔和频域间隔的信息时，都可认为PUSCH时频资源在时域上和频域上连续。或者，仅时域间隔为零或缺省时域间隔的信息，则可认为PUSCH时频资源在时域上连续。或者，仅频域间隔为零或缺省频域间隔的信息，则可认为PUSCH时频资源在频域上连续。
在该实施例中，终端可以根据第三配置信息中配置的PUSCH时频资源的大小信息，时域间隔和频域间隔，按照时域资源和频域资源顺序可以确定出各个PUSCH时频资源。
在另一些实施例中，第三配置信息可以包括每个PUSCH时频资源块包含的PUSCH时频资源的数量。每个PUSCH时频资源块包含的PUSCH时频资源的数量例如可以是时域上的数量和频域上的数量。那么，根据时域上的数量和频域上的数量，再按照时域资源和频域资源顺序可以确定出各个PUSCH时频资源。本申请实施例对确定每个PUSCH时频资源块中的PUSCH时频资源的方法不做限定。
根据上文对第二配置信息的描述可知，第二配置信息可以包括每个PUSCH时频资源块所关联的DMRS端口数目。如果第二配置信息中没有DMRS端口数目，也可以默认PUSCH时频资源块关联的DMRS端口数为1。
其中，DMRS端口数目可以根据DMRS配置类型和DMRS占用的时域符号数等参数进行确定。也就是说，可以不需要网络设备进行配置，本申请实施例对此不做限定。
在分别确定每个PRACH时频资源组包含的前导序列，以及每个PUSCH时频资源块中包含的时频资源后，可以进一步根据第三配置信息将每个前导序列和每个PUSCH时频资源建立映射关系。
在一些实施例中，第三配置信息包括一种时频资源的大小，也就是说，所有PUSCH时频资源块中包含的PUSCH时频资源的大小都相同。那么，第三配置信息可以包含每N 8个前导序列映射到一个PUSCH时频资源。
当N 8<1时，相当于一个前导序列映射到
Figure PCTCN2020075603-appb-000024
个序号连续的PUSCH时频资源。当N 8＝1时，相当于一个前导序列映射到1个序号连续的PUSCH时频资源。当N 8>1时，相当于N 8个前导序列映射到1个序号连续的PUSCH时频资源。
那么，在每个PRACH时频资源内前导序列，与对应的PUSCH时频资源块中的PUSCH时频资源建立映射关系时，可以根据参数N 8，前导序列的顺序以及PUSCH时频资源的顺序进行映射。
其中，前导序列的顺序可理解为前导序列所占用的频域资源和时频资源的顺序。例如：前导序列的顺序可以按照先频域资源序号的升序，再时域资源序号的升序。
其中，时频资源的顺序可理解为时频资源所占用的频域资源的顺序、时域资源的顺序、和时频资源所关联的DMRS端口的序号的顺序。例如：时频资源的顺序可以按照时频资源关联的DMRS端口的序号的升序，再按照频域资源的升序，再时域资源的升序。又例如：时频资源的顺序可以按照时频资源关联的DMRS端口的序号的升序， 再时域资源的升序，再按照频域资源的升序。
例如：请参考图21，假设一个PRACH时频资源组内包含10个前导序列，分别为前导序列#0至前导序列#9。且该PRACH时频资源对应的PUSCH时频资源块包含有大小相同的6个PUSCH时频资源，且该PUSCH时频资源块关联的DMRS端口数为8。且第三配置信息中的N 8＝2，也就是说，每2个前导序列映射到1个PUSCH时频资源。那么，具体映射关系如下：
前导序列#0映射到PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；
前导序列#1映射到PUSCH时频资源#0：DMRS端口#4至DMRS端口#7；
前导序列#2映射到PUSCH时频资源#1：DMRS端口#0至DMRS端口#3；
前导序列#3映射到PUSCH时频资源#1：DMRS端口#4至DMRS端口#7；
……
前导序列#8映射到PUSCH时频资源#4：DMRS端口#0至DMRS端口#3；
前导序列#9映射到PUSCH时频资源#4：DMRS端口#4至DMRS端口#7。
其中，PUSCH时频资源#5没有参与映射，将不用于两步随机接入过程中传输MsgA消息。
在该实施例中，当N 8>1时，即，每N 8个前导序列映射到1个PUSCH时频资源，且该PUSCH时频资源的DMRS端口的数量为E(E为大于1的整数)时，可以按照这N 8个前导序列的顺序与该PUSCH时频资源关联的DMRS端口的顺序进行映射。
在一些示例中，可以按照该PUSCH时频资源关联的DMRS端口的顺序，将该PUSCH时频资源关联的DMRS端口分成N 8份，每份依次对应一个前导序列。
例如：如图21所示的映射方法，N 8＝2，E＝8。即每两个前导序列映射到一个PUSCH时频资源上。每一个PUSCH时频资源关联的DMRS端口的数量为8，按照DMRS端口的序号将每一个PUSCH时频资源关联的DMRS端口分成2份，每一份对应一个前导序列。即，前导序列#0映射到PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；前导序列#1映射到PUSCH时频资源#0：DMRS端口#4至DMRS端口#7。其余前导序列的映射类似，不再赘述。
在另一些示例中，也可以根据前导序列的顺序以及DMRS端口序号的顺序，按照一对一的方式进行循环映射，直到N 8个前导序列中每个前导序列都至少映射到一个DMRS端口序号。即，每N 8个前导序列中，前导序列#n映射到这N 8个前导序列对应的PUSCH时频资源的DMRS端口#(n modE)。
例如：N 8＝5，E＝4。即，每5个前导序列需映射到一个PUSCH时频资源块上，每个PUSCH时频资源块关联4个DMRS端口。具体映射时，前导序列#0映射到DMRS端口#0，前导序列#1映射到DMRS端口#1，……，前导序列#4映射到DMRS端口#4。此时，前导序列#5还未参与映射。因此，进行循环映射，前导序列#5映射到DMRS端口#0。
又例如：N 8＝3，E＝8。即，每3个前导序列需映射到一个PUSCH时频资源块上，每个PUSCH时频资源块关联8个DMRS端口。具体映射时，前导序列#0映射到DMRS端口#0，前导序列#1映射到DMRS端口#1，前导序列#2映射到DMRS端口#2。
在又一些示例中，还可以根据前导序列的顺序以及DMRS端口序号的顺序，按照 一对一的方式进行循环映射，直到每个PUSCH时频资源块中每个DMRS端口都至少映射到一个前导序列。那么，当N 8<E时，每N 8个前导序列中，前导序列#n映射到这N 8个前导序列对应的PUSCH时频资源的DMRS端口#(N 8*i+n))，其中i的取值为所有大于等于0且小于
Figure PCTCN2020075603-appb-000025
的整数。
例如：N 8＝3，E＝4。即，每3个前导序列需映射到一个PUSCH时频资源块上，每个PUSCH时频资源块关联4个DMRS端口。具体映射时，前导序列#0映射到DMRS端口#0，前导序列#1映射到DMRS端口#1，前导序列#2映射到DMRS端口#2。此时，DMRS端口#3还未参与映射。因此，进行循环映射，前导序列#0映射到DMRS端口#3。
根据上文描述可知，第三配置信息中可以包括参数N 8，用于指示将N 8个前导序列映射到一个PUSCH时频资源。即，将前导序列和PUSCH时频资源进行映射。在另一些实施例中，也可以将前导序列和PUSCH资源单元进行映射。其中，PUSCH资源单元为比PUSCH时频资源粒度更小的单位。例如：一个PUSCH时频资源关联的DMRS的数量为E个，那么这一个PUSCH时频资源可认为是E个PUSCH资源单元。
换言之，第三配置信息可以包含参数F，参数F用于指示将每F个前导序列映射到一个PUSCH资源单元。其中，一个PUSCH资源单元可以理解为一个PUSCH时频资源以及该PUSCH资源单元对应的DMRS端口。DMRS端口可以理解为不同的DMRS配置和/或不同的DMRS序列。
可以理解的是，当N 8＝F*E时，每N 8个前导序列映射到一个PUSCH时频资源与每F个前导序列映射到一个PUSCH资源单元是等效的。其中，E表示一个PUSCH时频资源关联的DMRS端口数。
进一步的，在每个PRACH时频资源组内前导序列，与对应的PUSCH时频资源块中的PUSCH时频资源建立映射关系时，可以根据参数F，前导序列的顺序以及PUSCH资源单元的顺序进行映射。
需要注意的是，由于在一个PRACH时频资源内，前导序列本身存在默认的序列顺序，因此前导序列的顺序可以理解为在一个PRACH时频资源内前导序列默认的序列顺序的基础上，还包括前导序列所占用的PRACH时频资源的顺序，例如：前导序列的顺序可以在一个PRACH时频资源内前导序列默认的序列顺序的基础上，按照前导序列所占用的PRACH时频资源先频域资源序号的升序，再时域资源序号的升序。
PUSCH资源单元的顺序可理解为PUSCH时频资源的顺序和PUSCH时频资源所关联的DMRS端口的序号的顺序。例如：PUSCH资源单元的顺序可以按照PUSCH时频资源关联的DMRS端口的序号的升序，再按照PUSCH时频资源序号的升序。又例如：PUSCH资源单元的顺序也可以先按照PUSCH时频资源序号的升序，再按照DMRS端口的序号的升序。
示例性的，当PUSCH资源单元的顺序为先按照PUSCH时频资源关联的DMRS端口的序号的升序，再按照PUSCH时频资源序号的升序时，PUSCH资源单元#a对应的PUSCH时频资源的索引为
Figure PCTCN2020075603-appb-000026
DMRS端口索引为a mod E。其中
Figure PCTCN2020075603-appb-000027
表示小于等于X的最大的整数。
例如：以2个PUSCH时频资源，每个PUSCH时频资源对应2个DMRS端口为 例进行说明。那么，该2个PUSCH时频资源有4个PUSCH资源单元。这4个PUSCH资源单元的顺序可以如表九所示，先按DMRS端口序号的升序，再按照时频资源序号的升序进行编号。
表九
PUSCH资源单元#0 PUSCH时频资源#0 DMRS端口#0
PUSCH资源单元#1 PUSCH时频资源#0 DMRS端口#1
PUSCH资源单元#2 PUSCH时频资源#1 DMRS端口#0
PUSCH资源单元#3 PUSCH时频资源#1 DMRS端口#1
再示例性的，当PUSCH资源单元的顺序为先按照PUSCH时频资源序号的升序，再按照DMRS端口的序号的升序时，PUSCH资源单元#a对应的PUSCH时频资源的索引为
Figure PCTCN2020075603-appb-000028
DMRS端口索引为a mod L。其中H为PUSCH时频资源块中PUSCH时频资源的数量。
例如：以2个PUSCH时频资源，每个PUSCH时频资源对应2个DMRS端口为例进行说明。那么，该2个PUSCH时频资源有4个PUSCH资源单元。这4个PUSCH资源单元的顺序可以如表十所示，先按时频资源序号的升序，再按照DMRS端口序号的升序进行编号。
表十
PUSCH资源单元#0 PUSCH时频资源#0 DMRS端口#0
PUSCH资源单元#1 PUSCH时频资源#1 DMRS端口#0
PUSCH资源单元#2 PUSCH时频资源#0 DMRS端口#1
PUSCH资源单元#3 PUSCH时频资源#1 DMRS端口#1
其中，PUSCH时频资源的顺序可以理解为先按照频域资源的升序，再时域资源的升序；或者PUSCH时频资源的顺序可以理解为先按照时域资源的升序，再频域资源的升序。具体内容可参考前文相关内容的描述，这里不再赘述。
需要说明的是，以上DMRS端口的序号是以天线端口索引的顺序进行编号为例进行说明的。DMRS端口的序号也可以按照其他顺序进行编号，本申请实施例对此不做限定。
示例性的，当网络设备配置了多个用于生成DMRS序列的加扰ID或参考信号ID时，还可以结合加扰ID或参考信号ID的索引对DMRS的序号进行编号。例如：DMRS端口的顺序还可以理解为先按照生成DMRS序列的加扰ID或参考信号ID的索引的升序，再按照天线端口索引的升序。或者，DMRS端口的顺序还可以理解为先按照天线端口索引的升序，再按照生成DMRS序列的加扰ID或参考信号ID的索引的升序。其中，根据前文表五的相关描述可知，不同的天线端口对应不同的DMRS的配置。
例如：以1个PUSCH资源单元包括2个天线端口，每个天线端口包括两个不同ID生成的DMRS序列为例进行说明。那么，该PUSCH资源单元包括4个DMRS端口。这4个DMRS端口的顺序可以如表十一所示，先按照生成DMRS序列的加扰ID的索引的升序，再按照天线端口索引的升序进行编号。
表十一
Figure PCTCN2020075603-appb-000029
又例如：以1个PUSCH资源单元包括2个天线端口，每个天线端口包括两个不同ID生成的DMRS序列为例进行说明。那么，该PUSCH资源单元包括4个DMRS端口。这4个DMRS端口的顺序可以如表十二所示，先按照天线端口索引的升序，再按照生成DMRS序列的加扰ID的索引的升序进行编号。
表十二
Figure PCTCN2020075603-appb-000030
在明确了前导序列的顺序，以及PUSCH资源单元的顺序后，可以根据二者建立前导序列到PUSCH资源单元的映射关系。
在一些实施例中，在每个PRACH时频资源组内前导序列，与对应的PUSCH时频资源块中的PUSCH时频资源建立映射关系时，所有的前导序列都根据前导序列的顺序以及PUSCH资源单元的顺序连续映射，所有的前导序列都按照序号连续的每F个前导序列映射到一个PUSCH资源单元。
例如：当F<1时，相当于一个前导序列映射到1/F个序号连续的PUSCH资源单元，前导序列#n映射到PUSCH资源单元#(n*F)到#((n+1)*F-1)。当F≥1时，前导序列#n映射到PUSCH资源单元#
Figure PCTCN2020075603-appb-000031
需要注意的是，当一个PRACH时频资源组内前导序列的数量(记为P)不是其对应的PUSCH时频资源块的PUSCH资源单元的数量(即H)的倍数或约数时，该PRACH时频资源组中，存在一部分前导序列映射的PUSCH资源单元的数量，与另一部分前导序列映射的PUSCH资源单元的数量不同。
具体来说，此时，一部分前导序列按照序号连续的F个前导序列映射到一个PUSCH资源单元。当F≤1时，另一部分前导序列按照每个前导序列映射到
Figure PCTCN2020075603-appb-000032
个PUSCH资源单元。当F>1时另一部分前导序列按照每F-1个前导序列映射到一个PUSCH资源单元。具体每部分所包含的前导序列数量可由PRACH时频资源组内前导序列的数量 (P)、PUSCH时频资源块内PUSCH资源单元的数量(H)、以及参数F计算得到。这种映射方式可以保证PUSCH时频资源块内的所有PUSCH资源单元都与前导序列进行映射，提高PUSCH资源单元的利用率。
例如：当F≤1时，前
Figure PCTCN2020075603-appb-000033
个前导序列按照每个前导序列映射到
Figure PCTCN2020075603-appb-000034
个序号连续的PUSCH资源单元，后
Figure PCTCN2020075603-appb-000035
个前导序列按照序号每个前导序列映射到
Figure PCTCN2020075603-appb-000036
个序号连续的PUSCH资源单元。或者，前
Figure PCTCN2020075603-appb-000037
个前导序列按照序号每个前导序列映射到
Figure PCTCN2020075603-appb-000038
个序号连续的PUSCH资源单元，后
Figure PCTCN2020075603-appb-000039
个前导序列按照序号每个前导序列映射到
Figure PCTCN2020075603-appb-000040
个序号连续的PUSCH资源单元。
又例如：当F>1时，前F(P-E*H*(F-1))个前导序列按照连续的F个前导序列映射到一个PUSCH资源单元，后(F-1)*(F*E*H-P)个前导序列按照连续的F-1个前导序列映射到一个PUSCH资源单元；或者前(F-1)*(F*E*H-P)个前导序列按照连续的F-1个前导序列映射到一个PUSCH资源单元，后F(P-E*H*(F-1))个前导序列按照连续的F个前导序列映射到一个PUSCH资源单元。
在本申请中，网络设备也可以不配置参数F。即，预定义前导序列到PUSCH资源单元的映射规则。那么，可以直接根据预定义的映射规则可以将前导序列与PUSCH资源单元建立映射关系。换言之，第三配置信息可以不包含参数F。
在一些实施例中，可以先根据PRACH时频资源组内前导序列的数量、PUSCH时频资源块内PUSCH资源单元的数量计算得到F。
例如：当P≤E*H时，
Figure PCTCN2020075603-appb-000041
当P>E*H时，
Figure PCTCN2020075603-appb-000042
其中
Figure PCTCN2020075603-appb-000043
表示大于等于X的最小的整数。
而后，采用与上一实施例中相同的映射方法，将前导序列与PUSCH资源单元进行映射。
在另一些实施例中，预定义的映射方法为：在每个PRACH时频资源组内前导序列，与对应的PUSCH时频资源块中的PUSCH时频资源建立映射关系时，根据前导序列的顺序以及PUSCH资源单元的顺序，按照一对一的方式进行循环映射，直到每个PRACH时频资源组内所有的前导序列都至少映射到一个PUSCH资源单元。
例如：前导序列#n映射到PUSCH资源单元#(n mod(E*H))。
在另一些实施例中，预定义的映射方法为：在每个PRACH时频资源组内前导序列，与对应的PUSCH时频资源块中的PUSCH时频资源建立映射关系时，根据前导序列的顺序以及PUSCH资源单元的顺序，按照一对一的方式进行循环映射，当P<E*H时，直到每个PUSCH时频资源块中每个PUSCH资源单元都至少映射到一个前导序列。
例如：当P<E*H时，前导序列#n映射到PUSCH资源单元#(P*i+n))。其中，i的取值为所有大于等于0且小于
Figure PCTCN2020075603-appb-000044
的整数。
在另一实施例中，针对一个PRACH时频资源组内包含多组前导序列时，且不同分组的前导序列需要使用不同大小的PUSCH时频资源时，第三配置信息中也可以配置不同大小的PUSCH时频资源。
具体的，第三配置信息中可以包括两种及两种以上的PUSCH时频资源的大小信息。
第三配置信息可以包括针对每一个分组的前导配置一个参数N 8。即，第三配置信息中包含有多个N 8值。其他内容可参考上文的描述，这里不再赘述。
在一种情况中，该包含多组前导序列的PRACH时频资源组映射到一个PUSCH时频资源块。那么，可以将这一个PUSCH时频资源块配置为不同大小的PUSCH时频资源。即，该PUSCH时频资源块可以包括不同大小的PUSCH时频资源。
例如：请参考图22，假设一个PRACH时频资源组内包含10个前导序列，分为两组。其中，第一分组有7个前导序列，具体为前导序列#0至前导序列#6。第一分组有2个前导序列，具体为前导序列#7至前导序列#8。且该PRACH时频资源对应的PUSCH时频资源块包含有5个PUSCH时频资源(包含两种大小不同的PUSCH时频资源)。且该PUSCH时频资源块关联的DMRS端口数为8。且第三配置信息中的N 8＝2，也就是说，每2个前导序列映射到1个时频资源。那么，具体映射关系如下：
前导序列#0映射到PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；
前导序列#1映射到PUSCH时频资源#0：DMRS端口#4至DMRS端口#7；
……
前导序列#6映射到PUSCH时频资源#3：DMRS端口#0至DMRS端口#3；
前导序列#7映射到PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；
前导序列#8映射到PUSCH时频资源#0：DMRS端口#4至DMRS端口#7。
由上可见，PUSCH时频资源#3：DMRS端口#4至DMRS端口#7没有参与映射，将不同于两步随机接入过程中传输MsgA消息。
在又一种情况中，该包含多组前导序列的PRACH时频资源组映射到多个PUSCH时频资源块。那么，可以为不同的PUSCH时频资源块配置不同大小的PUSCH时频资源。即，不同PUSCH时频资源块包含的时频资源的大小不同，但同一个PUSCH时频资源块中的时频资源相同。
又例如：请参考图23，假设一个PRACH时频资源组内包含10个前导序列，分为两组。其中，第一分组有7个前导序列，具体为前导序列#0至前导序列#6。第一分组有2个前导序列，具体为前导序列#7至前导序列#8。且该PRACH时频资源对应的PUSCH时频资源块包含PUSCH时频资源块#0和PUSCH时频资源块#1。其中，PUSCH时频资源块#0包含有4个PUSCH时频资源，PUSCH时频资源块#1包含有2个PUSCH时频资源。且该PUSCH时频资源块关联的DMRS端口数为8。且第三配置信息中的N 8＝2，也就是说，每2个前导序列映射到1个时频资源。那么，具体映射关系如下：
前导序列#0映射到PUSCH时频资源块#0，PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；
前导序列#1映射到PUSCH时频资源块#0，PUSCH时频资源#0：DMRS端口#4至DMRS端口#7；
……
前导序列#6映射到PUSCH时频资源块#0，PUSCH时频资源#3：DMRS端口#0至DMRS端口#3；
前导序列#7映射到PUSCH时频资源块#1，PUSCH时频资源#0：DMRS端口#0至DMRS端口#3；
前导序列#8映射到PUSCH时频资源块#0，PUSCH时频资源#0：DMRS端口#4至DMRS端口#7。
由上可见，PUSCH时频资源块#0中PUSCH时频资源#3：DMRS端口#4至DMRS端口#7，以及PUSCH时频资源块#1中PUSCH时频资源#1：DMRS端口#1至DMRS端口#7，均没有参与映射，将不同于两步随机接入过程中传输MsgA消息。
需要说明的是，上述各个实施例在方案不矛盾的前提下，均可以进行任意组合。即，本申请实施例提供的随机接入方法能够建立前导序列和PUSCH时频资源的映射关系。其中，第一配置信息、第二配置信息和第三配置信息的划分仅为了说明本申请的方法，并不构成对第一配置信息、第二配置信息和第三配置信息的具体限定。即，上述第一配置信息中的部分或全部内容可能在第二配置信息或第三配置信息中，上述第二配置信息中的部分或全部内容可能在第一配置信息或第三配置信息中，上述第三配置信息中的部分或全部内容可能在第一配置信息或第二配置信息中。
例如：在一实施例中，第一配置信息与上述实施例中的第一配置信息相同，这里不再赘述。
第二配置信息和第三配置信息，与上述实施例中的第二配置信息和第三配置信息略有不同，以下具体说明。
第二配置信息：与上述第一种方法类似，网络设备可以通过配置第一映射图样来确定用于上行传输的PUSCH时频资源块，以及每个PRACH时频资源与用于上行传输的PUSCH时频资源块的对应关系。
具体的，第二配置信息包括第一映射图像的信息，第一映射图样的配置与内容同第一种方法相同。第一映射图样的作用于上述第一种方法的区别是，在该实施例中，第一映射图样中的每个映射二元组所确定的时域资源配置信息和频域资源配置信息是一个PUSCH时频资源的，而在上述第一种方法中每个映射二元组所确定的时域资源配置信息和频域资源配置信息是一个PUSCH时频资源块的。也就是说，在该实施例中，根据第二配置信息可以确定出PUSCH时频资源。
在该实施例中，第二配置信息还可以包括PUSCH时频资源频分复用的个数M 1和/或PUSCH时频资源时分复用的个数M 2。PUSCH时频资源时域资源配置信息和频域资源配置信息与PUSCH时频资源频分复用的个数M 1和/或PUSCH时频资源时分复用的个数M 2结合可以确定一个PUSCH时频资源块。
相比较于上述实施例，在该实施例中，第三配置信息可以不包含确定PUSCH时频资源的信息，即不包含：PUSCH时频资源的大小信息，时域间隔和频域间隔、每个PUSCH时频资源块包含的PUSCH时频资源的数量等。第三配置信息可以包含配置PRACH时频资源中每个前导序列与PUSCH时频资源的映射关系。即，第三配置信息可以包括映射到一个PUSCH时频资源的前导序列的数量N 8。该部分内容可参考上文描述，不再赘述。
以下，以网络设备配置如图5A所示的PRACH时频资源，且第一映射图样包含两个映射二元组为例，并结合附图进行示例性说明。
其中，第一映射图像为
({K,S,L},{RB start,L RBs})＝{({1,2,12}{12,2}),({2,2,12}{6,2})}，M 1＝3，M 2＝2。
其中，({1,2,12}{12,2})为第一个映射二元组，根据上述对映射二元组的解释可知，该映射二元组表示映射后的PUSCH时频资源第一个符号所在的时隙位于PRACH时频资源所占用的时隙后的第1个时隙，这里即一个子帧，且起始符号为符号#2，占用12个符号。起始RB为#12RB，占用2RB。频域复用个数为3，即在一个时隙内有3个PUSCH时频资源频分复用，起始RB分别为#12RB、#14RB、#16RB，各占用2RB。时域复用个数为2，即在连续两个时隙各有3个PUSCH时频资源，起始符号都为符号#2，各占用12个符号。这6个PUSCH时频资源组成一个PUSCH时频资源块。({2,2,12}{6,2})为第二映射二元组，其对应的PUSCH时频资源及时频资源块的方法与第一映射二元组相同。
例如：请参见图24A所示，当网络设备配置的
Figure PCTCN2020075603-appb-000045
时，表示一个PRACH时频资源映射时使用
Figure PCTCN2020075603-appb-000046
个映射二元组，即两个PRACH时频资源使用一个映射二元组。在具体映射时，PRACH时频资源#0使用第一个映射二元组进行映射，PRACH时频资源#1也使用第一个映射二元组进行映射。PRACH时频资源#2使用第二个映射二元组进行映射，PRACH时频资源#3也使用第二个映射二元组进行映射。映射后得到的PUSCH时频资源，再根据M 1和M 2得到PUSCH时频资源块，既从，以及PRACH时频资源与时频资源的对应关系如图24A所示。
其他内容可以参见上述实施例中相关内容的描述，这里不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如终端、网络设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件、软件或硬件和机软件相结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端、网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明：
图24B示出了上述实施例中所涉及的一种装置的结构示意图，该装置可以实现本申请实施例提供的方法中终端的功能。该装置可以为终端或者为可以支持终端实现本申请实施例中终端的功能的装置，例如该装置为应用于终端中的芯片系统。该装置包括：确定单元101和通信单元102。其中，确定单元101可以用于支持图24B所示的装置执行上述实施例中的步骤S502、S503和S504。通信单元102用于支持图24B所 示的装置执行上述实施例中的步骤S501、S505和S506。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可选的，本申请的实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
可选的，本申请实施例中的通信单元可以为电路、器件、接口、总线、软件模块、收发器或者其它任意可以实现通信的装置。
可选地，通信单元102可以为终端或者应用于终端中的芯片系统的通信接口，例如，该通信接口可以为收发电路，确定单元101可以为集成在终端或者应用于终端中的芯片系统的处理器上。
图25示出了上述实施例中所涉及的装置的一种可能的逻辑结构示意图，该装置可以实现本申请实施例提供的方法中终端的功能。该装置可以为终端或者应用于终端中的芯片系统，该装置包括：处理模块112和通信模块113。处理模块112用于对图25所示的装置的动作进行控制管理，例如，处理模块112用于执行在图25所示的装置侧进行消息或数据处理的步骤。例如，支持图25所示的装置执行上述实施例中的步骤S502、S503和S504。通信模块113用于支持图25所示的装置执行上述实施例中的S501、S505和S506。和/或用于本文所描述的技术的其他由图25所示的装置执行的过程。可选的，图25所示的装置还可以包括存储模块111，用于存储该装置的程序代码和数据。
其中，处理模块112可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块113可以是收发器、收发电路或通信接口等。存储模块111可以是存储器。
当处理模块112为处理器220，通信模块113为通信接口230或收发器时，存储模块111为存储器240时，本申请实施例所涉及的装置可以为图26所示的装置。
其中，通信接口230、至少一个处理器220以及存储器240通过总线210相互连接；总线210可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图26中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器240用于存储装置的程序代码和数据。通信接口230用于支持装置与其他设备通信，处理器220用于支持装置执行存储器240中存储的程序代码以实现本申请实施例提供的一种数据信道传输方法。
可选地，存储器240可以包括于处理器220中。
图27示出了上述实施例中所涉及的装置的一种可能的结构示意图，该装置可以实现本申请实施例提供的方法中网络设备的功能。该装置可以为网络设备或者为应用于网络设备中的芯片系统。该装置包括：通信单元201，用于支持图27所示的装置执行上述实施例中的步骤S501、S505和S506。此外，和/或用于本文所描述的技术的其它过程。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
可选地，通信单元201可以为网络设备或者应用于网络设备中的芯片系统的通信接口，例如，收发器。
图28示出了上述实施例中所涉及的装置的一种可能的结构示意图，该装置可以实现本申请实施例提供的方法中网络设备的功能。该装置可以为网络设备或者为应用于网络设备中的芯片系统。该装置包括：处理模块212和通信模块213。处理模块212用于对该装置的动作进行控制管理。例如，处理模块212用于支持图28示出的装置执行上述实施例中在图28示出的装置侧进行消息或数据处理的操作。通信模块213用于支持图28示出的装置执行上述实施例中在装置侧进行消息或数据接收和发送的操作，例如，上述实施例中的步骤S501、S505和S506。和/或用于本文所描述的技术的其他由图28示出的装置执行的过程。
可选的，图28示出的装置还可以包括存储模块211，用于该装置的程序代码和数据。
其中，处理模块212可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块213可以是收发器、收发电路或通信接口等。存储模块211可以是存储器。
当处理模块212为处理器320，通信模块213为通信接口330或收发器时，存储模块211为存储器310时，本申请实施例所涉及的数据信道接收装置可以为图29所示的装置。
其中，通信接口330、至少一个处理器320以及存储器310通过总线300相互连接；总线300可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图29中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中，存储器310用于存储装置的程序代码和数据。通信接口330用于支持装置与其他设备(例如，图15B-图17所示的装置)通信，处理器320用于支持装置执行存储器310中存储的程序代码以实现本申请提供的一种随机接入方法。
可选地，存储器310可以包括于处理器320中。
一种可能的实现方式，本申请中图26和图29所示的装置还可以为芯片系统，该芯片系统中各个部件所执行的步骤可以参见上述实施例中图16和图29所示的装置所执行的步骤，本申请在此不再赘述。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例描述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计 算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，SSD)等。
一方面，提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行实施例中的S501、S502、S503、S504、S505和S506。和/或用于本文所描述的技术的其他由终端或者应用于终端中的芯片系统执行的过程。前述的可读存储介质可以包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
又一方面，提供计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行实施例中的步骤S501、S505和S506。
一方面，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行S501、S502、S503、S504、S505和S506。
又一方面，提供一种包含指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行实施例中的步骤S501、S505和S506。
一方面，提供一种芯片系统，该芯片系统中包括处理器，还可以包括存储器，用于实现上述实施例中的S501、S502、S503、S504和S505。
又一方面，提供一种芯片系统，该芯片系统中包括处理器，还可以包括存储器，用于实现上述实施例中的网络设备的功能，芯片系统包括至少一个处理器和接口电路，接口电路和至少一个处理器通过线路互联，处理器用于运行指令，以执行实施例中实施例中的步骤S501、S505和S506。
此外，本申请还提供一种通信系统，该通信系统包括如图24B-图26中任一个所示的终端，图27-图29任一个所示的网络设备。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的 部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
以上，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以权利要求的保护范围为准。

Claims (60)

  1. 一种随机接入的方法，其特征在于，包括：
    终端接收网络设备发送的第一配置信息、第二配置信息和第三配置信息，所述第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；所述第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，所述PUSCH时频资源块包括一个或者多个PUSCH时频资源；所述第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；
    根据所述第一配置信息确定第一PRACH时频资源；
    确定需要在第一PRACH时频资源上发送的第一前导序列，所述第一前导序列为所述前导序列集合中的前导序列；
    根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源；
    发送包含所述第一前导序列和上行数据的第一消息，其中，所述第一前导序列承载在所述第一PRACH时频资源上，所述上行数据承载在所述第一PRACH时频资源所对应的PUSCH时频资源上。
  2. 根据权利要求1所述的方法，其特征在于，所述第二配置信息包括用于配置所述PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第二配置信息包括第一映射图样的配置信息，所述第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
  4. 根据权利要求3所述的方法，其特征在于，所述第二配置信息包含用于配置所述PUSCH时频资源块的周期T1，所述第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
  5. 根据权利要求3或4所述的方法，其特征在于，所述第二配置信息包含参数N 1，所述参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  6. 根据权利要求5所述的方法，其特征在于，所述参数N 1和所述第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
  7. 根据权利要求3或4所述的方法，其特征在于，所述第二配置信息包含参数N 2和参数N 3，所述参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  8. 根据权利要求1或2所述的方法，其特征在于，所述第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
  9. 根据权利要求8所述的方法，其特征在于，所述第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二配置信息包括参数N 4，所述参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  11. 根据权利要求8或9所述的方法，其特征在于，所述第二配置信息包含参数N 5和参数N 6，所述参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 6用于确定所述周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  12. 根据权利要求8或9所述的方法，其特征在于，所述第二配置信息还包含参数N 7和第二映射图样的信息，所述参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，所述第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，所述参数N 7和所述第二映射图样用于确定所述周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
  13. 根据权利要求1-12任一项所述的方法，其特征在于，所述根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH的时频资源包括：
    根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序、所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源。
  14. 根据权利要求1到13任一项所述的方法，其特征在于，所述第三配置信息包含每个PUSCH时频资源的大小和参数N 8，所述参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
  15. 根据权利要求14所述的方法，其特征在于，根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源包括：
    根据预设的PRACH时频资源到时频资源块的映射顺序、预设的前导序列到PUSCH时频资源的映射顺序、所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    根据预设的前导序列到DMRS端口的映射顺序，确定所述第一PRACH时频资源对应的PUSCH时频资源所关联的DMRS端口。
  17. 一种随机接入的方法，其特征在于，包括：
    网络设备向终端发送第一配置信息、第二配置信息和第三配置信息，所述第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；所述第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，所述PUSCH时频资源块包括一个或者多个PUSCH时频资源；所述第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；
    接收所述终端发送的包含第一前导序列和上行数据的第一消息，其中，所述第一前导序列承载在第一PRACH时频资源上，所述上行数据承载在所述第一PRACH时频资源所对应的PUSCH时频资源上。
  18. 根据权利要求17所述的方法，其特征在于，所述第二配置信息包括用于配置所述PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
  19. 根据权利要求17或18所述的方法，其特征在于，所述第二配置信息包括第一映射图样的配置信息，所述第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
  20. 根据权利要求19所述的方法，其特征在于，所述第二配置信息包含用于配置所述PUSCH时频资源块的周期T1，所述第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第二配置信息包含参数N 1，所述参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  22. 根据权利要求21所述的方法，其特征在于，所述参数N 1和所述第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
  23. 根据权利要求19或20所述的方法，其特征在于，所述第二配置信息包含参数N 2和参数N 3，所述参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  24. 根据权利要求17或18所述的方法，其特征在于，所述第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
  25. 根据权利要求24所述的方法，其特征在于，所述第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
  26. 根据权利要求23或25所述的方法，其特征在于，所述第二配置信息包括参数N 4，所述参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  27. 根据权利要求24或25所述的方法，其特征在于，所述第二配置信息包含参数N 5和参数N 6，所述参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 6用于确定所述周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  28. 根据权利要求24或25所述的方法，其特征在于，所述第二配置信息还包含参数N 7和第二映射图样的信息，所述参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，所述第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，所述参数N 7和所述第二映射图样用于确定所述周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
  29. 根据权利要求17到28任一项所述的方法，其特征在于，所述第三配置信息包含每个PUSCH时频资源的大小和参数N 8，所述参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
  30. 一种随机接入装置，其特征在于，包括：通信单元和确定单元；
    所述通信单元，用于接收网络设备发送的第一配置信息、第二配置信息和第三配置信息，所述第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；所述第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，所述PUSCH时频资源块包括一个或者多个PUSCH时频资源；所述第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；
    所述确定单元，用于根据所述第一配置信息确定第一PRACH时频资源；
    所述确定单元，还用于确定需要在第一PRACH时频资源上发送的第一前导序列，所述第一前导序列为所述前导序列集合中的前导序列；
    所述确定单元，还用于根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源；
    所述通信单元，还用于发送包含所述第一前导序列和上行数据的第一消息，其中，所述第一前导序列承载在所述第一PRACH时频资源上，所述上行数据承载在所述第一PRACH时频资源所对应的PUSCH时频资源上。
  31. 根据权利要求30所述的装置，其特征在于，所述第二配置信息包括用于配置所述PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
  32. 根据权利要求30或31所述的装置，其特征在于，所述第二配置信息包括第一映射图样的配置信息，所述第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
  33. 根据权利要求32所述的装置，其特征在于，所述第二配置信息包含用于配置所述PUSCH时频资源块的周期T1，所述第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
  34. 根据权利要求32或33所述的装置，其特征在于，所述第二配置信息包含参数N 1，所述参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  35. 根据权利要求34所述的装置，其特征在于，所述参数N 1和所述第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
  36. 根据权利要求31或33所述的装置，其特征在于，所述第二配置信息包含参数N 2和参数N 3，所述参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  37. 根据权利要求30或31所述的装置，其特征在于，所述第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
  38. 根据权利要求37所述的装置，其特征在于，所述第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的 PUSCH时频资源块。
  39. 根据权利要求37或38所述的装置，其特征在于，所述第二配置信息包括参数N 4，所述参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  40. 根据权利要求37或38所述的装置，其特征在于，所述第二配置信息包含参数N 5和参数N 6，所述参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 6用于确定所述周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  41. 根据权利要求37或38所述的装置，其特征在于，所述第二配置信息还包含参数N 7和第二映射图样的信息，所述参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，所述第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，所述参数N 7和所述第二映射图样用于确定所述周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
  42. 根据权利要求30-41任一项所述的装置，其特征在于，所述确定单元，还用于根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH的时频资源具体包括：
    所述确定单元，具体用于根据预设的PRACH时频资源到PUSCH时频资源块的映射顺序、所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源。
  43. 根据权利要求30到42任一项所述的装置，其特征在于，所述第三配置信息包含每个PUSCH时频资源的大小和参数N 8，所述参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
  44. 根据权利要求43所述的装置，其特征在于，所述确定单元，还用于根据所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源包括：
    所述确定单元，具体用于根据预设的PRACH时频资源到时频资源块的映射顺序、预设的前导序列到PUSCH时频资源的映射顺序、所述第一PRACH时频资源、所述第一前导序列、所述第二配置信息和所述第三配置信息确定所述第一前导序列所对应的PUSCH时频资源。
  45. 根据权利要求44所述的装置，其特征在于，
    所述确定单元，还用于根据预设的前导序列到DMRS端口的映射顺序，确定所述第一PRACH时频资源对应的PUSCH时频资源所关联的DMRS端口。
  46. 一种随机接入的装置，其特征在于，包括：通信单元，
    所述通信单元，用于向终端发送第一配置信息、第二配置信息和第三配置信息，所述第一配置信息用于配置一个或者多个物理随机接入信道PRACH时频资源和前导序列集合；所述第二配置信息用于配置每个PRACH时频资源所对应的物理上行共享信道PUSCH时频资源块，所述PUSCH时频资源块包括一个或者多个PUSCH时频资源；所述第三配置信息用于配置每个PUSCH时频资源的大小以及前导序列和PUSCH时频资源的对应关系；
    所述通信单元，还用于接收所述终端发送的包含第一前导序列和上行数据的第一消息，其中，所述第一前导序列承载在第一PRACH时频资源上，所述上行数据承载在所述第一PRACH时频资源所对应的PUSCH时频资源上。
  47. 根据权利要求46所述的装置，其特征在于，所述第二配置信息包括用于配置所述PUSCH时频资源块所关联的解调参考信号DMRS端口的信息。
  48. 根据权利要求46或47所述的装置，其特征在于，所述第二配置信息包括第一映射图样的配置信息，所述第一映射图样包含一个或者多个映射规则，每个映射规则可用于和至少一个PRACH时频资源联合以确定至少一个PUSCH时频资源块的时域资源和频域资源。
  49. 根据权利要求47所述的装置，其特征在于，所述第二配置信息包含用于配置所述PUSCH时频资源块的周期T1，第一映射图样用于确定周期T1内的PRACH时频资源所对应的PUSCH时频资源块。
  50. 根据权利要求48或49所述的装置，其特征在于，所述第二配置信息包含参数N 1，所述参数N 1用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  51. 根据权利要求50所述的装置，其特征在于，所述参数N 1和所述第一映射图样用于确定每个PRACH时频资源所对应的PUSCH时频资源块。
  52. 根据权利要求48或49所述的装置，其特征在于，所述第二配置信息包含参数N 2和参数N 3，所述参数N 2用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 3用于确定周期T1内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  53. 根据权利要求46或47所述的装置，其特征在于，所述第二配置信息包括PUSCH时频资源块的周期T2，PUSCH时频资源块的时域资源配置信息和/或PUSCH时频资源块的频域资源配置信息。
  54. 根据权利要求53所述的装置，其特征在于，所述第二配置信息包括映射周期T3，在每个映射周期T3内使用相同的规则确定配置的各个PRACH时频资源所对应的PUSCH时频资源块。
  55. 根据权利要求52或54所述的装置，其特征在于，所述第二配置信息包括参数N 4，所述参数N 4用于确定每个PRACH时频资源所对应的PUSCH时频资源块的数量。
  56. 根据权利要求51或54所述的装置，其特征在于，所述第二配置信息包含参数N 5和参数N 6，所述参数N 5用于确定每个PRACH时频资源组包含的PRACH时频资源的数量，所述参数N 6用于确定周期T3内的每个PRACH时频资源组所关联的PUSCH时频资源块的数量。
  57. 根据权利要求53或54所述的装置，其特征在于，所述第二配置信息还包含参数N 7和第二映射图样的信息，所述参数N 7用于确定每个PRACH资源组包含的PRACH时频资源的数量，所述第二映射图样包含一个或多个序号集合，每个序号集合包含一个或者多个PUSCH时频资源块的序号，所述参数N 7和所述第二映射图样用于确定所述周期T3内每个PRACH时频资源组所关联的PUSCH时频资源块的序号。
  58. 根据权利要求46到57任一项所述的装置，其特征在于，所述第三配置信息包含每个PUSCH时频资源的大小和参数N 8，所述参数N 8用于确定每个前导序列所对应的PUSCH时频资源的数量。
  59. 一种数据传输装置，其特征在于，包括：存储器和处理器；
    所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述数据传输装置实现如权利要求1至16中的任一项所述的方法；或者，实现如权利要求17至29中的任一项所述的方法。
  60. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至16中的任一项所述的方法；或者，实现如权利要求17至29中的任一项所述的方法。
PCT/CN2020/075603 2019-02-15 2020-02-17 一种随机接入方法、设备及系统 Ceased WO2020164639A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
AU2020220568A AU2020220568B2 (en) 2019-02-15 2020-02-17 Random access method, device, and system
JP2021547715A JP7174859B2 (ja) 2019-02-15 2020-02-17 ランダムアクセス方法、装置、及びシステム
BR112021016150-3A BR112021016150A2 (pt) 2019-02-15 2020-02-17 Método de acesso aleatório, dispositivo, e sistema
KR1020217029802A KR102775331B1 (ko) 2019-02-15 2020-02-17 랜덤 액세스 방법, 디바이스, 및 시스템
EP20756405.5A EP3923652A4 (en) 2019-02-15 2020-02-17 DIRECT ACCESS METHOD, DEVICE AND SYSTEM
CA3130419A CA3130419A1 (en) 2019-02-15 2020-02-17 Random access method, device, and system
US17/402,302 US12052770B2 (en) 2019-02-15 2021-08-13 Random access method, device, and system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201910118163.2 2019-02-15
CN201910118163 2019-02-15
CN201910351921.5 2019-04-28
CN201910351921.5A CN111586861B (zh) 2019-02-15 2019-04-28 一种随机接入方法、设备及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/402,302 Continuation US12052770B2 (en) 2019-02-15 2021-08-13 Random access method, device, and system

Publications (1)

Publication Number Publication Date
WO2020164639A1 true WO2020164639A1 (zh) 2020-08-20

Family

ID=72044556

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075603 Ceased WO2020164639A1 (zh) 2019-02-15 2020-02-17 一种随机接入方法、设备及系统

Country Status (5)

Country Link
EP (1) EP3923652A4 (zh)
JP (1) JP7174859B2 (zh)
CN (1) CN115843116A (zh)
BR (1) BR112021016150A2 (zh)
WO (1) WO2020164639A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220021484A1 (en) * 2020-07-14 2022-01-20 Qualcomm Incorporated Sequence design for noncoherent transmission with frequency and timing errors
CN116458106A (zh) * 2020-11-23 2023-07-18 高通股份有限公司 Rach类型选择和不同的rach参数集

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536418A (zh) * 2019-03-13 2019-12-03 中兴通讯股份有限公司 数据传输方法、装置、用户设备、基站及存储介质
CN117119605A (zh) * 2022-05-11 2023-11-24 华为技术有限公司 通信方法及装置、存储介质
CN117119606A (zh) * 2022-05-11 2023-11-24 华为技术有限公司 通信方法及装置、存储介质
CN117956627A (zh) * 2024-01-12 2024-04-30 中兴通讯股份有限公司 传输资源配置方法、通信装置及存储介质
WO2025210843A1 (ja) * 2024-04-04 2025-10-09 １Ｆｉｎｉｔｙ株式会社 端末装置、基地局装置及び無線通信システム
WO2025222337A1 (zh) * 2024-04-22 2025-10-30 Oppo广东移动通信有限公司 随机接入信道的传输方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107889273A (zh) * 2016-09-30 2018-04-06 北京三星通信技术研究有限公司 随机接入的方法及相应设备
WO2018085726A1 (en) * 2016-11-04 2018-05-11 Intel IP Corporation Performing 2-step random access channel (rach) procedures
WO2018089265A1 (en) * 2016-11-14 2018-05-17 Qualcomm Incorporated Two step random-access channel (rach) procedure in millimeter wave (mmw)
CN108633100A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 随机接入响应的方法和设备以及随机接入的方法和设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6248213B2 (ja) 2014-02-16 2017-12-13 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるデータ送信方法及び装置
WO2018064367A1 (en) 2016-09-28 2018-04-05 Idac Holdings, Inc. Random access in next generation wireless systems
ES2992114T3 (es) * 2019-02-13 2024-12-09 Interdigital Patent Holdings Inc Métodos y aparatos para la transmisión de msg-A en RACH de dos etapas

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107889273A (zh) * 2016-09-30 2018-04-06 北京三星通信技术研究有限公司 随机接入的方法及相应设备
WO2018085726A1 (en) * 2016-11-04 2018-05-11 Intel IP Corporation Performing 2-step random access channel (rach) procedures
WO2018089265A1 (en) * 2016-11-14 2018-05-17 Qualcomm Incorporated Two step random-access channel (rach) procedure in millimeter wave (mmw)
CN108633100A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 随机接入响应的方法和设备以及随机接入的方法和设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3923652A4
ZTE ET AL.: "2-step Random Access Procedure", 3GPP TSG RAN WG1 AH_NR MEETING R1-1700105; HTTPS://WWW.3GPP.ORG/FTP/TSG_RAN/WG1_RL1/TSGR1_AH/NR_AH_1701/DOCS, 10 January 2017 (2017-01-10), XP051202612, DOI: 20200427144836A *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220021484A1 (en) * 2020-07-14 2022-01-20 Qualcomm Incorporated Sequence design for noncoherent transmission with frequency and timing errors
US11777653B2 (en) * 2020-07-14 2023-10-03 Qualcomm Incorporated Sequence design for noncoherent transmission with frequency and timing errors
CN116458106A (zh) * 2020-11-23 2023-07-18 高通股份有限公司 Rach类型选择和不同的rach参数集
CN116458106B (zh) * 2020-11-23 2025-10-28 高通股份有限公司 Rach类型选择和不同的rach参数集

Also Published As

Publication number Publication date
JP7174859B2 (ja) 2022-11-17
EP3923652A4 (en) 2022-04-20
JP2022520468A (ja) 2022-03-30
BR112021016150A2 (pt) 2021-10-13
EP3923652A1 (en) 2021-12-15
CN115843116A (zh) 2023-03-24

Similar Documents

Publication Publication Date Title
KR102775331B1 (ko) 랜덤 액세스 방법, 디바이스, 및 시스템
US11089594B2 (en) Resource allocation method, user equipment, and network device
WO2020164639A1 (zh) 一种随机接入方法、设备及系统
CN104904300B (zh) 无线通信方法、用户设备和网络侧设备
CN110226342B (zh) 发送参考信号的方法和装置及接收参考信号的方法和装置
WO2021032027A1 (zh) 一种随机接入方法、终端设备和网络设备
US12052773B2 (en) Terminal device, network device and methods therein
WO2019192601A1 (zh) 一种通信方法及装置
CN105101431B (zh) 一种设备到设备通信方法、装置及系统
EP3496500A1 (en) Random access method and device
WO2020047922A1 (zh) 配置信息的传输方法和终端设备
CN108605030A (zh) 用户终端、无线基站和无线通信方法
TW202008828A (zh) 資源配置的方法和終端設備
TW202008829A (zh) 資源配置的方法和終端設備
US11394593B2 (en) Data channel transmission method, data channel receiving method, and apparatus
JP2021503791A (ja) 検出ウィンドウ指示方法及び装置
WO2020063479A1 (zh) 由用户设备执行的方法以及用户设备
CN108696890A (zh) 处理测量间距的装置及方法
CN110971362B (zh) 一种发现参考信号发送方法及装置
JP2020530239A (ja) 信号送信方法および信号送信装置、ならびに信号受信方法および信号受信装置
WO2022151171A1 (zh) 随机接入方法及装置
WO2020198962A1 (zh) 无线通信方法、终端设备和网络设备
CN113543324B (zh) 一种目标信息发送方法、接收方法和装置
WO2025026395A1 (zh) 由用户设备执行的方法以及用户设备
CN111556566A (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: 20756405

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021547715

Country of ref document: JP

Kind code of ref document: A

Ref document number: 3130419

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021016150

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20217029802

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020756405

Country of ref document: EP

Effective date: 20210906

ENP Entry into the national phase

Ref document number: 2020220568

Country of ref document: AU

Date of ref document: 20200217

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112021016150

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210816