Patent Description:
In the related art, long term evolution (LTE) protocols adopt a <NUM>-step random access (RA) procedure. However, the <NUM>-step RA procedure would cause significant control plane latency in <NUM>th Generation mobile communication system (<NUM>) New Radio (NR) uplink (UL) multi-beam physical random access channel (PRACH) transmission, thus the low-latency oriented performance target defined for ultra-reliable and low latency communications (URLLC) scenarios cannot be reached. In order to obtain a processing method that effective reduces the control plane processing latency, NR Rel-<NUM> in the related art has set up the work item of <NUM>-step RA procedure.

<FIG> is a schematic diagram showing an NR <NUM>-step RA procedure. The NR <NUM>-step RA procedure differs from the <NUM>-step RA procedure in that a preamble and data are transmitted simultaneously in a message A (MsgA), wherein content of the data corresponds to the content of the message <NUM> (Msg3) of the <NUM>-step RA procedure, and the data is based on a physical uplink shared channel (PUSCH) structure. As such, how to ensure the correctness of the <NUM>-step RA procedure becomes a problem demanding prompt resolution.

<NPL>, provides observations and proposals on the random access principles for the <NUM>-step RACH.

The present invention relates to information transmission methods, a terminal and a network device, as defined in the annexed claims, to ensure the correctness of the <NUM>-step RA procedure.

The foregoing technical solutions of the present disclosure have at least the following beneficial effects.

In the foregoing technical solutions of the embodiments of the present disclosure, a message A (MsgA) of a <NUM>-step random access procedure is sent to a network device according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA; wherein the preamble parameter includes a preamble index and a PRACH time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS. In this way, the correctness of the <NUM>-step RA procedure can be ensured, thus an effect of effectively reducing the control plane processing latency of uplink multi-beam physical random access channel transmission can be achieved.

To describe the technical problem to be solved, the technical solutions and the advantages of the present disclosure more clearly, embodiments are described in detail hereinafter with reference to the accompanying drawings.

As shown in <FIG>, an embodiment of the present disclosure provides an information transmission method. The method is applied to a terminal, and includes a step <NUM>: sending a message A (MsgA) of a <NUM>-step random access procedure to a network device according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA; wherein the preamble parameter includes a preamble index and a physical random access channel (PRACH) time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS.

In this step, the mapping relationship between the preamble parameter and the PUSCH parameter in the MsgA of the <NUM>-step random access procedure is pre-defined in a protocol or is configured by a network.

It is noted, the preamble and the PUSCH in the MsgA adopt the same transmission beam direction.

The parameters related to PUSCH DMRS ports are described hereinafter in detail with reference to the schematic diagram, as shown in <FIG>, illustrating a configuration type of PUSCH DMRS ports when a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform is used.

Here, the diagram is specifically directed to the configuration type <NUM> of PUSCH DMRS ports when a CP-OFDM waveform defined in NR is used. A case in which <NUM> OFDM symbols are occupied in time domain is taken as an example, at this time, a maximum quantity of orthogonal DMRS ports that can be supported is <NUM>. As shown in <FIG>, port <NUM>, port <NUM>, port <NUM> and port <NUM> share the same time-frequency resource, port <NUM>, port <NUM>, port <NUM> and port <NUM> share the same time-frequency resource, and the port <NUM>/<NUM>/<NUM>/<NUM> is separated from the port <NUM>/<NUM>/<NUM>/<NUM> by frequency division multiplex.

Frequency domain orthogonal cover code (FD-OCC) represents that two resource elements (REs) which are spaced apart by one RE in frequency domain are multiplexed in frequency domain by using an orthogonal spread code; time domain orthogonal cover code (TD-OCC) represents that two OFDM symbols which are adjacent in time domain are multiplexed in time domain by using an orthogonal spread code.

Here, the port <NUM>, port <NUM>, port <NUM> and port <NUM> share the same time-frequency resource, occupy even-numbered REs in one physical resource block (PRB) in frequency domain, occupy two OFDM symbols in time domain, and are further distinguished from each other by FD-OCC with a length of <NUM> and TD-OCC with a length of <NUM>, specifically as follows:.

The port <NUM>, port <NUM>, port <NUM> and port <NUM> share the same time-frequency resource, occupy odd-numbered REs in one PRB in frequency domain, occupy two OFDM symbols in time domain, and are further distinguished from each other by FD-OCC with a length of <NUM> and TD-OCC with a length of <NUM>, specifically as follows:.

It can be seen that, the PUSCH DMRS ports have orthogonal cover code (OCC) parameters.

In the information transmission method according to the embodiment of the present disclosure, a message A (MsgA) of a <NUM>-step random access procedure is sent to a network device according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA; wherein the preamble parameter includes a preamble index and a PRACH time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS. In this way, the correctness of the <NUM>-step RA procedure can be ensured, thus an effect of effectively reducing the control plane processing latency of uplink multi-beam physical random access channel transmission can be achieved.

On the basis of the embodiment as shown in <FIG>, in the present invention the mapping relationship includes at least one of:.

Specifically, the mapping relationship includes the first mapping relationship; and
the first mapping relationship includes:.

Here, the first mapping relationship is a mapping from the preamble index to {PUSCH time-frequency resource, PUSCH DMRS}.

It is noted, when receiving a MsgA, firstly the base station needs to perform UE activation detection based on preamble, next uniquely determines a PUSCH channel based on the detected preamble, and then detects the PUSCH channel. In order for the base station to uniquely determine the PUSCH channel based on the detected preamble, thereby avoiding vagueness in detection, the mapping from the preamble index to {PUSCH time-frequency resource, PUSCH DMRS}has to be a one-to-one mapping or a N1(N1 is a positive integer greater than <NUM>)-to-one mapping, instead of a one-to-many mapping.

Additionally, the N1 preamble indexes in the mapping from the N1 preamble indexes to one PUSCH time-frequency resource may be N1 preamble indexes include by the same Zadoff-Chu (ZC) root sequence, or may be any N1 preamble indexes sequentially numbered.

The first mapping relationship is described in detail below with reference to some examples.

Example <NUM>, one preamble index is mapped to one PUSCH time-frequency resource and one PUSCH DMRS, that is, one preamble index to {PUSCH time-frequency resource, PUSCH DMRS}.

As shown in <FIG>, preamble#<NUM> is mapped to a combination {PUSCH #<NUM>, DMRS#<NUM>}, and preamble#<NUM> is mapped to a combination {PUSCH #<NUM>, DMRS#<NUM>}.

The preamble#<NUM> and preamble#<NUM> denote a preamble index numbered as <NUM> and a preamble index numbered as <NUM>, respectively; the PUSCH#<NUM> and PUSCH#<NUM> denote a PUSCH time-frequency resource numbered as <NUM> and a PUSCH time-frequency resource numbered as <NUM>, respectively; the DMRS#<NUM> and DMRS#<NUM> denote a PUSCH DMRS numbered as <NUM> and a PUSCH DMRS numbered as <NUM>, respectively.

Example <NUM>, N1 preamble indexes to one {PUSCH time-frequency resource, PUSCH DMRS}.

It is noted, in NR Rel-<NUM> protocols, one PRACH time-frequency resource supports <NUM> preamble indexes, as a result, <NUM><N1<<NUM>, and the value of parameter N1 should be determined taking account of a mapping from a synchronization signal block (SSB) to a PRACH time-frequency resource RACH occasion (RO). When N1 preamble indexes are mapped to one PUSCH time-frequency resource, the mapping from N1 preamble indexes to a PUSCH DMRS needs to be further taken account of.

Case <NUM>: as shown in <FIG>, preamble index values numbered as <NUM> to <NUM> (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), and the four preamble indexes (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are separately mapped to four DMRSs (DMRS#<NUM>/<NUM>/<NUM>/<NUM>) in a one-to-one manner.

In this way, both the PUSCH time-frequency resource numbered as <NUM> and the PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM> and PUSCH#<NUM>) can support virtual uplink multi-user multiple-input multiple-output (MU-MIMO) of <NUM> UEs. In other words, one preamble index is mapped to one PUSCH DMRS, and one PUSCH time-frequency resource can support N1 users, i.e., virtual uplink MU-MIMO of N1 users is supported.

Case <NUM>: as shown in <FIG>, N1=<NUM>, preamble index values numbered as <NUM> to <NUM> (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), and the four preamble indexes (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a DMRS numbered as <NUM> (DMRS#<NUM>); preamble index values numbered as <NUM> to <NUM> (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), and the four preamble indexes (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a DMRS numbered as <NUM> (DMRS#<NUM>).

In this way, both the PUSCH time-frequency resource numbered as <NUM> and the PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM> and PUSCH#<NUM>) can support uplink PUSCH transmission of one UE.

Case <NUM>: ceil(N1/T) preamble indexes to one PUSCH DMRS (that is, N1 preamble indexes are further divided into T subgroups each including N1/T preamble indexes). In this case, one PUSCH time-frequency resource can support ceil(N1/T) users, that is, the virtual uplink MU-MIMO of ceil(N1/T) users is supported, wherein T is a positive integer greater than or equal to <NUM>. It is noted, ceil() is a round-up function.

As shown in <FIG>, N1=<NUM>, T=<NUM>, preamble index values numbered as <NUM> to <NUM> (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), two preamble indexes (preamble#<NUM> and preamble#!) are mapped to DMRS#<NUM>, and two preamble indexes (preamble#<NUM> and preamble#<NUM>) are mapped to DMRS#<NUM>; preamble index values numbered as <NUM> to <NUM> (preamble#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), two preamble indexes (preamble#<NUM> and preamble#<NUM>) are mapped to DMRS#<NUM>, and two preamble indexes (preamble#<NUM> and preamble#<NUM>) are mapped to DMRS#<NUM>. In this way, both the PUSCH time-frequency resource numbered as <NUM> and the PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM> and PUSCH#<NUM>) can support virtual uplink MU-MIMO of two UEs.

Specifically, the mapping relationship includes the second mapping relationship; and
the second mapping relationship includes:.

It is noted, the frequency domain offset ΔF is pre-defined in a protocol or notified by signaling; the time offset ΔT is pre-defined in a protocol or notified by signaling.

Here, the second mapping relationship is a mapping from the PRACH time-frequency resource to {PUSCH time-frequency resource, PUSCH DMRS}.

It is noted, when receiving a MsgA, firstly the base station needs to perform UE activation detection based on preamble, next uniquely determines a PUSCH channel based on the detected preamble, and then detects the PUSCH channel. In order for the base station to uniquely determine the PUSCH channel based on the detected preamble, thereby avoiding vagueness in detection, the mapping from the PRACH time-frequency resource to {PUSCH time-frequency resource, PUSCH DMRS}has to be a one-to-one mapping or a N2 (N2 is a positive integer greater than <NUM>)-to-one mapping, instead of a one-to-many mapping.

The second mapping relationship is described in detail below with reference to some examples.

Example <NUM>, one PRACH time-frequency resource is mapped to one PUSCH time-frequency resource and one PUSCH DMRS, that is, one PRACH time-frequency resource to {PUSCH time-frequency resource, PUSCH DMRS}.

As shown in <FIG>, PRACH#<NUM> is mapped to a combination {PUSCH #<NUM>, DMRS#<NUM>}, and PRACH#<NUM> is mapped to a combination {PUSCH #<NUM>, DMRS#<NUM>}.

The PRACH#<NUM> and PRACH#<NUM> denote a PRACH time-frequency resource numbered as <NUM> and a PRACH time-frequency resource numbered as <NUM>, respectively; the PUSCH#<NUM> and PUSCH#<NUM> denote a PUSCH time-frequency resource numbered as <NUM> and a PUSCH time-frequency resource numbered as <NUM>, respectively; the DMRS#<NUM> and DMRS#<NUM> denote a PUSCH DMRS numbered as <NUM> and a PUSCH DMRS numbered as <NUM>, respectively.

It is noted, the PRACH preamble format <NUM> defined in NR Rel-<NUM> and a PUSCH channel structure with a subcarrier spacing (SCS) of <NUM> are shown in <FIG>. Referring to <FIG>, more specifically, a relationship between the PRACH time-frequency resource and the PUSCH time-frequency resource includes (as shown in <FIG>):.

Additionally, as shown in <FIG>, a relationship between the PRACH time-frequency resource and the PUSCH time-frequency resource may further include: in frequency domain, the PRACH time-frequency resource and the PUSCH time-frequency resource have different bandwidths, have unaligned starting PRB locations, and have a fixed frequency domain offset ΔF, and in time domain, the PRACH time-frequency resource and the PUSCH time-frequency resource have a fixed time offset ΔT.

Here, in the relationship between the PRACH time-frequency resource and the PUSCH time-frequency resource as shown in <FIG>, the PRACH time-frequency resource and the PUSCH time-frequency resource are consecutive in time domain, and there is not time offset between the PRACH time-frequency resource and the PUSCH time-frequency resource. In the relationship between the PRACH time-frequency resource and the PUSCH time-frequency resource as shown in <FIG>, the starting PRB location of the PRACH time-frequency resource is spaced from the starting PRB location of the PUSCH time-frequency resource in frequency domain by a fixed frequency domain offset ΔF, and the ending time of the preamble time-frequency resource in the MsgA is spaced from the ending time of the PUSCH time-frequency resource in the MsgA in time domain by a fixed time offset ΔT, where ΔT is not <NUM>.

Example <NUM>, N2 PRACH time-frequency resources are mapped to one {PUSCH time-frequency resource, PUSCH DMRS}.

As shown in <FIG>, N2=<NUM>, PRACH time-frequency resources numbered as <NUM> to <NUM> (PRACH#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), and the four PRACH time-frequency resources (PRACH#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a DMRS numbered as <NUM> (DMRS#<NUM>); PRACH time-frequency resources numbered as <NUM> to <NUM> (PRACH#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM>), and the four PRACH time-frequency resources (PRACH#<NUM>/<NUM>/<NUM>/<NUM>) are simultaneously mapped to a DMRS numbered as <NUM> (DMRS#<NUM>).

In this way, both the PUSCH time-frequency resource numbered as <NUM> and the PUSCH time-frequency resource numbered as <NUM> (PUSCH#<NUM> and PUSCH#<NUM>) can support virtual uplink MU-MIMO of one UE.

Specifically, the mapping relationship includes the third mapping relationship; and
in a case that one synchronization signal block (SSB) is mapped to <NUM>/Y RACH occasions (ROs), the third mapping relationship includes:.

Here, the third mapping relationship is a mapping from {preamble index, PRACH time-frequency resource} to {PUSCH #<NUM>, DMRS#<NUM>}, in consideration of a mapping from SSB to RO.

It is noted, in a case that one SSB is mapped to <NUM>/Y ROs, when the third mapping relationship includes that Q preamble indexes in one RO are mapped to one PUSCH time-frequency resource and one PUSCH DMRS, optionally, a value of Q is a positive integer selected from <NUM> to <NUM>; optionally, the value of Q is an integral multiple of <NUM>, or an integral multiple of <NUM>.

Additionally, it needs to be explained that, in a case that W SSBs are mapped to one RO, the third mapping relationship includes: S preamble indexes are divided into F second index groups, each of the F second index groups is associated with one SSB and is mapped to one PUSCH time-frequency resource and one PUSCH DMRS, and each of the F second index groups includes one or more consecutive CBRA preamble indexes.

In other words, a number fix(S/F) of consecutive CBRA preamble indexes are associated with one SSB, and are mapped to one PUSCH time-frequency resource and one PUSCH DMRS. It is noted, fix(x) is a rounding function, which obtains an integer part of x directly.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, prior to the step <NUM>, the method may further include:.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, the step <NUM> may specifically include:.

Here, based on the specific implementation step in the previous step, the step of sending the MsgA to the network device based on the target PUSCH time-frequency resource and the target PUSCH DMRS may further include:
sending the MsgA to the network device based on the one target PRACH time-frequency resource, the one target preamble index, the target PUSCH time-frequency resource and the target PUSCH DMRS.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, subsequent to the step <NUM>, the method may further include:
receiving a random access response message sent by the network device.

As shown in <FIG>, an embodiment of the present disclosure provides an information transmission method. The method is applied to a network device, and includes a step <NUM>: receiving a message A (MsgA) of a <NUM>-step random access procedure sent by a terminal according to a mapping relationship between a preamble parameter and a physical uplink shared channel (PUSCH) parameter in the MsgA; wherein the preamble parameter includes a preamble index and a physical random access channel (PRACH) time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH demodulation reference signal (DMRS).

In the information transmission method according to the embodiment of the present disclosure, a message A (MsgA) of a <NUM>-step random access procedure sent by a terminal according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA is received; wherein the preamble parameter includes a preamble index and a PRACH time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS. In this way, the correctness of the <NUM>-step RA procedure can be ensured, thus an effect of effectively reducing the control plane processing latency of uplink multi-beam physical random access channel transmission can be achieved.

According to the invention, the mapping relationship includes at least one of:.

Here, the first mapping relationship is a mapping from the preamble index to {PUSCH time-frequency resource, PUSCH DMRS}.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, prior to the step <NUM>, the method may further include:
sending the mapping relationship between the preamble parameter and the PUSCH parameter in the MsgA of the <NUM>-step random access procedure to the terminal via broadcast signaling or radio resource control signaling.

In this step, the network device notifies UE in an idle (RRC_IDLE) state or an inactive (RRC_INACTIVE) state by using a broadcast message SIB1 (system information block1); the network device notifies UE in a connected (RRC_CONNECTED) state by using RRC signaling.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, subsequent to the step <NUM>, the method may further include:.

On the basis of the embodiment as shown in <FIG>, as an optional implementation, subsequent to the step <NUM>, the method may further include:
sending a random access response message to the terminal.

As shown in <FIG>, an embodiment of the present disclosure further provides a terminal. The terminal includes: a memory <NUM>, a processor <NUM>, a transceiver <NUM>, a bus interface and a computer program stored in the memory <NUM> and configured to be executed by the processor <NUM>, wherein the processor <NUM> is configured to read the computer program in the memory <NUM> to implement following process:.

In <FIG>, a bus architecture may include any number of interconnected buses and bridges, and connects various circuits including one or more processors represented by the processor <NUM> and memory represented by the memory <NUM>. The bus architecture may also connect various other circuits such as peripherals, voltage regulators and power management circuits, which is well known in the art. Therefore, a detailed description thereof is omitted herein. A bus interface provides an interface. The transceiver <NUM> may be multiple elements, such as a transmitter and a receiver, to allow for communication with various other apparatuses on the transmission medium. For different user equipment, the user interface <NUM> may be an interface capable of externally or internally connecting a required device, and the connected device includes, but is not limited to: a keypad, a display, a speaker, a microphone, a joystick and the like.

The processor <NUM> is responsible for supervising the bus architecture and normal operation and the memory <NUM> may store the data being used by the processor <NUM> during operation.

Optionally, the mapping relationship includes the first mapping relationship; and
the first mapping relationship includes:.

Optionally, the mapping relationship includes the second mapping relationship; and
the second mapping relationship includes:.

Optionally, the mapping relationship includes the third mapping relationship; and
in a case that one synchronization signal block (SSB) is mapped to <NUM>/Y RACH occasions (ROs), the third mapping relationship includes:.

Optionally, the processor <NUM> is further configured to execute the computer program to implement following steps:.

Optionally, the transceiver <NUM> is configured to: receive a random access response message sent by the network device.

As shown in <FIG>, an embodiment of the present disclosure further provides a terminal. The terminal includes:.

The terminal according the embodiment may further include:.

In the terminal according the embodiment, the first sending module <NUM> may include:.

In the terminal according the embodiment, the processing unit is specifically configured to:.

The terminal according the embodiment further includes: a third receiving module, configured to receive a random access response message sent by the network device.

In the terminal according to the embodiment of the present disclosure, a message A (MsgA) of a <NUM>-step random access procedure is sent by the first sending module to a network device according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA; wherein the preamble parameter includes a preamble index and a PRACH time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS. In this way, the correctness of the <NUM>-step RA procedure can be ensured, thus an effect of effectively reducing the control plane processing latency of uplink multi-beam physical random access channel transmission can be achieved.

In some embodiments of the present disclosure, a computer readable storage medium storing thereon a computer program is further provided, wherein the computer program is configured to be executed by a processor to implement following steps:.

When the computer program is executed by a processor, all implementations of the method embodiments applied to the terminal side as shown in <FIG> may be implemented. To avoid repetition, a detailed description thereof is omitted herein.

As shown in <FIG>, an embodiment of the present disclosure further provides a network device. The network device includes: a transceiver <NUM>, a memory <NUM>, a processor <NUM> and a computer program stored in the memory and configured to be executed by the processor, wherein the transceiver <NUM> is configured to:.

In <FIG>, a bus architecture may include any number of interconnected buses and bridges, and connects various circuits including one or more processors represented by the processor <NUM> and memory represented by the memory <NUM>. The bus architecture may also connect various other circuits such as peripherals, voltage regulators and power management circuits, which is well known in the art. Therefore, a detailed description thereof is omitted herein. A bus interface provides an interface. The transceiver <NUM> may be multiple elements, such as a transmitter and a receiver, to allow for communication with various other apparatuses on the transmission medium. The processor <NUM> is responsible for supervising the bus architecture and normal operation and the memory <NUM> may store the data being used by the processor <NUM> during operation.

Optionally, the transceiver <NUM> is further configured to:
send the mapping relationship between the preamble parameter and the PUSCH parameter in the MsgA of the <NUM>-step random access procedure to the terminal via broadcast signaling or radio resource control signaling.

Optionally, the processor <NUM> is configured to execute the computer program to implement following steps:.

Optionally, the transceiver <NUM> is further configured to: send a random access response message to the terminal.

As shown in <FIG>, an embodiment of the present disclosure further provides a network device. The network device includes:.

The network device according to the embodiment of the present disclosure may further include:
a second sending module, configured to send the mapping relationship between the preamble parameter and the PUSCH parameter in the MsgA of the <NUM>-step random access procedure to the terminal via broadcast signaling or radio resource control signaling.

The network device according to the embodiment of the present disclosure may further include:.

The network device according to the embodiment of the present disclosure may further include: a third sending module, configured to send a random access response message to the terminal.

In the network device according to the embodiment of the present disclosure, a message A (MsgA) of a <NUM>-step random access procedure sent by a terminal according to a mapping relationship between a preamble parameter and a PUSCH parameter in the MsgA is received by a first receiving module; wherein the preamble parameter includes a preamble index and a PRACH time-frequency resource, and the PUSCH parameter includes a PUSCH time-frequency resource and a PUSCH DMRS. In this way, the correctness of the <NUM>-step RA procedure can be ensured, thus an effect of effectively reducing the control plane processing latency of uplink multi-beam physical random access channel transmission can be achieved.

When the computer program is executed by a processor, all implementations of the method embodiments applied to the network device side as shown in <FIG> may be implemented. To avoid repetition, a detailed description thereof is omitted herein.

The computer readable medium includes permanent and non-permanent, removable and non-removable media, and may achieve information storage by any means or techniques. Information may be computer readable instruction, data structure, program module or other data. Computer storage medium may, for example, include, but is not limited to: phase change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storages, cassette tape, magnetic tape, magnetic disk or other magnetic storage device or any other non-transmitting medium, which is configured to store information accessible by a computing device. According to the definition herein, the computer readable medium does not include transitory media, such as modulated data signals and carriers.

It is further noted, the terminal described in this description includes, but is not limited to: a smart phone, tablet computer or the like, and many described functional parts are referred to as a module, to emphasize the independence of their implementations.

In the embodiments of the present disclosure, a module may be implemented in software, so as to be executed by various types of processors. For example, an identified executable code module may include one or more physical or logical blocks of computer instructions, for example, they may be built as objects, processes or functions. Nevertheless, the executable codes of the identified module need not to reside in a same location; rather, the identified module may include different instructions stored at different locations, and when combined logically, these instructions form the module and fulfill the specified purpose of the module.

In practice, the executable code module may be an instruction or multiple instructions, and may even be distributed over multiple distinct code segments, over different programs, or over multiple storage devices. Similarly, operation data may be identified in the module, implemented in any suitable manner and organized in any suitable type of data structure. The operation data may be gathered as a single data set, or may be distributed over different locations (including different storage devices), and at least a part of the operation data may only reside in a system or network as an electronic signal.

In the case that a module may be implemented in software, considering the hardware process level in the related art, a person skilled in the art may construct hardware corresponding to all modules that can be implemented in software, to achieve corresponding functions, if cost is not considered. The hardware circuit includes normal very large scale integration (VLSI) circuit or gate array, and semiconductor devices in the relate art such as logic chip or transistor, or other discrete devices. The module may also be implemented with a programmable hardware device, such as field program gate array, programmable logic array or programmable logic device.

It may be understood that these embodiments described in this disclosure may be implemented by hardware, software, firmware, middleware, microcode or a combination thereof. For hardware implementation, a module, unit, sub-module or subunit may be implemented in one or more application specific integrated circuits (ASICs), a digital signal processor (DSP), a DSP device (DSPD), a programmable logic device (PLD), a field-programmable gate array (FPGA), a general-purpose processor, a controller, a microcontroller, a microprocessor, other electronic unit configured to perform the functions in the present disclosure or a combination thereof.

For a software implementation, the techniques in some embodiments of the present disclosure may be implemented by modules (for example, processes or functions) performing the functions described in embodiments of the present disclosure. Software codes may be stored in a memory and executed by a processor. The memory may be implemented internal or external to a processor.

Claim 1:
An information transmission method, comprising:
sending (<NUM>) a message A, MsgA, of a <NUM>-step random access procedure to a network device according to a mapping relationship between a preamble parameter and a physical uplink shared channel, PUSCH, parameter in the MsgA;
wherein the preamble parameter comprises a preamble index and a physical random access channel, PRACH, time-frequency resource, characterized in that the PUSCH parameter comprises a PUSCH time-frequency resource and a PUSCH demodulation reference signal, DMRS;
and further characterized in that the mapping relationship comprises at least one of:
a first mapping relationship of the preamble index to the PUSCH time-frequency resource and the PUSCH DMRS;
a second mapping relationship of the PRACH time-frequency resource to the PUSCH time-frequency resource and the PUSCH DMRS;
wherein the mapping relationship comprises the first mapping relationship; and
the first mapping relationship comprises:
M preamble indexes are mapped to one PUSCH DMRS on one PUSCH time-frequency resource;
wherein, M is a positive integer greater than <NUM>.