CN113677038B

CN113677038B - Random access processing method and terminal

Info

Publication number: CN113677038B
Application number: CN202010415407.6A
Authority: CN
Inventors: 莫毅韬; 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-05-15
Filing date: 2020-05-15
Publication date: 2023-07-25
Anticipated expiration: 2040-05-15
Also published as: CN116634597A; CN113677038A; WO2021228226A1

Abstract

The application provides a random access processing method and a terminal, wherein the method comprises the following steps: transmitting a random access preamble; generating first uplink data according to a first PUSCH resource set associated with the random access preamble code or generating first uplink data according to a rollback random access response under the condition that the random access preamble code is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource; the first PUSCH resource set is used for carrying the first uplink data. The embodiment of the application improves the reliability of the random access process.

Description

Random access processing method and terminal

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a random access processing method and a terminal.

Background

As is well known, the 2-step (step) Random Access (RA) procedure is that a terminal sends a message a (MsgA) to a network device, and the network device sends a message B (MsgB) to the terminal after receiving the MsgA. If the terminal receives that the MsgA random access response (Fallback Random Access Response, fallback rar) matched with the preamble index value of the transmitted MsgA random access preamble is included in the MsgA, the UE will take out the MsgA load (payload) from the MsgA buffer (buffer) and store the MsgA load (payload) in the Msg3 buffer. Then, the UE sends Msg3 to the network side for contention resolution. For the 2-step RA procedure, the MsgA preamble may not be mapped with one valid physical uplink shared channel (Physical Uplink Shared Channel) resource. At this time, after the UE selects the MsgA preamble, since an uplink grant (UL grant) for carrying MsgA payload transmission cannot be obtained, an MsgA payload cannot be generated, and smooth proceeding of the subsequent fallback procedure cannot be ensured, resulting in lower reliability of the random access procedure.

Disclosure of Invention

The embodiment of the application provides a random access processing method and a terminal, which are used for solving the problem of low reliability of a random access process.

In a first aspect, an embodiment of the present application provides a random access processing method, including:

transmitting a random access preamble;

generating first uplink data according to a first PUSCH resource set associated with the random access preamble code or generating first uplink data according to a rollback random access response under the condition that the random access preamble code is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource;

the first PUSCH resource set is used for carrying the first uplink data.

In a second aspect, an embodiment of the present application provides a terminal, including:

a transmitting module, configured to transmit a random access preamble;

the data generation module is used for generating first uplink data according to a first PUSCH resource set associated with the random access preamble code or generating first uplink data according to a back-off random access response under the condition that the random access preamble code is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource;

the first PUSCH resource set is used for carrying the first uplink data.

In a third aspect, an embodiment of the present application provides a terminal, including: the random access processing method comprises a memory, a processor and a program or instructions stored on the memory and capable of running on the processor, wherein the program or instructions realize the steps in the random access processing method when being executed by the processor.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps of the random access processing method described above.

The embodiment of the application sends the random access preamble; generating first uplink data according to a first PUSCH resource set associated with the random access preamble code or generating first uplink data according to a rollback random access response under the condition that the random access preamble code is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource; the first PUSCH resource set is used for carrying the first uplink data. In this way, the terminal can still generate the first uplink data and store the data in the MsgA buffer under the condition that the random access preamble is not mapped with the effective physical uplink shared channel PUSCH resource, so that the smooth proceeding of the subsequent fallback process can be ensured. Therefore, the embodiment of the application improves the reliability of the random access process.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a block diagram of a network system to which embodiments of the present application are applicable;

fig. 2 is a flowchart of a random access processing method provided in an embodiment of the present application;

fig. 3 is a block diagram of a terminal according to an embodiment of the present application;

fig. 4 is a block diagram of another terminal according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means at least one of the connected objects, e.g., a and/or B, meaning that it includes a single a, a single B, and that there are three cases of a and B.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Embodiments of the present application are described below with reference to the accompanying drawings. The random access processing method and the terminal provided by the embodiment of the application can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved long term evolution (Evolved Long Term Evolution, elet) system, or a subsequent evolved communication system.

Referring to fig. 1, fig. 1 is a block diagram of a network system to which the embodiment of the present application is applicable, and as shown in fig. 1, the network system includes a terminal 11 and a network device 12, where the terminal 11 may be a user terminal or other terminal side device, for example: terminal-side devices such as a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer), a personal digital assistant (personal digital assistant, PDA for short), a mobile internet Device (Mobile Internet Device, MID) or a Wearable Device (wearmable Device), it should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network device 12 may be a 5G base station, or a later version of a base station, or a base station in other communication systems, or referred to as a node B, an evolved node B, or a transmitting/receiving Point (TransmissionReception Point, TRP), or an Access Point (AP), or other words in the field, and the network device is not limited to a specific technical word as long as the same technical effect is achieved. In addition, the network device 12 may be a Master Node (MN) or a Secondary Node (SN). It should be noted that, in the embodiment of the present application, only a 5G base station is taken as an example, but the specific type of the network device is not limited.

For ease of understanding, some of the matters related to the embodiments of the present application are described below:

uplink shared channel (Uplink shared channel, UL-SCH) data (data) transmission.

For UL-SCH data transmission, the terminal must have a corresponding uplink grant (UL grant) and corresponding HARQ information including HARQ process identification number (HARQ process id), redundancy version (Redundancy Version, RV), new data indication (New Data Indicator, NDI), transport block size (Transport Block Size, TBS), etc. For example, to transmit an MsgA payload, the network device needs to indicate PUSCH resource related configuration for carrying the MsgA payload transmission through radio resource control (Radio Resource Control, RRC) signaling, such as: UL grant for MsgA payload transmission (MsgA UL grant), which may include time-frequency code space domain resource allocation.

When the terminal receives an MsgA UL grant, the media access control (Medium Access Control, MAC) entity instructs the multiplexing and assembling entity of the MAC layer to generate a MAC protocol data unit (Protocol Data Unit, PDU) according to the HARQ information corresponding to the MsgA UL grant, i.e. the MsgA payload, and store it in the MsgA buffer.

Next, the MAC entity gives the MsgA UL grant and its corresponding HARQ information to the HARQ entity (entity). Then, the HARQ entity acquires the MsgA payload to be transmitted from the MsgA buffer. The HARQ entity may then indicate that the corresponding HARQ process triggers the transmission of a new transmission of data, e.g., HARQ process id 0 triggers the transmission of a new transmission of data. Specifically, the HARQ process stores the MsgA payload in the HARQ buffer corresponding to the HARQ process id 0, and finally triggers the physical layer to send new transmission data.

Referring to fig. 2, fig. 2 is a flowchart of a random access processing method provided in an embodiment of the present application, where the method is applied to a terminal, as shown in fig. 2, and includes the following steps:

step 201, transmitting a random access preamble;

in this embodiment of the present application, the random access preamble may be referred to as a preamble, further may be a contended preamble (content-based random access preamble), or a non-contended preamble (content-free random access preamble). The terminal may select an efficient physical random access channel (Physical Random Access Channel, PRACH) resource for transmitting the random access preamble while performing the random access procedure. In this embodiment, the random access procedure may be understood as a 2-step RA procedure, the contended preamble may be understood as a 2-step RA contended preamble, and the uncompetitive preamble may be understood as a 2-step RA uncompetitive preamble. In the 2-step RA procedure described above, the terminal will first send an MsgA, which carries the random access preamble.

Step 202, generating first uplink data according to a first PUSCH resource set associated with the random access preamble, or generating first uplink data according to a fallback random access response, when the random access preamble is not mapped with an effective physical uplink shared channel PUSCH resource; the first PUSCH resource set is used for carrying the first uplink data.

In general, if the random access preamble is not mapped with an effective physical uplink shared channel PUSCH resource, the terminal may transmit MsgA on a selected one of the effective PRACH transmission opportunities (occalaons). Further, the fact that the random access preamble is not mapped to the effective physical uplink shared channel PUSCH resources may be understood that the preamble of the 2-step RA contention is not mapped to the effective physical uplink shared channel PUSCH resources within one association pattern period (Association Pattern Period). For example, in one association pattern period, the PUSCH resources selected by the terminal in the first PUSCH resource set associated with the random access preamble are invalid PUSCH resources. Specifically, part or all of PUSCH resources in the first PUSCH resource set associated with the random access preamble may be invalid PUSCH resources. The first PUSCH resource set may include one PUSCH resource, or may include one or more PUSCH resources that are time division multiplexed (Time Division Multiplexing) or frequency division multiplexed (Frequency Division Multiplexing), and the one PUSCH resource may also be periodic. Each PUSCH resource includes at least one PUSCH transmission opportunity and demodulation reference signal (Demodulation Reference Signal, DMRS) resource.

The first uplink data may be understood as uplink data that is subsequently transmitted in an uplink direction, and may also be referred to as MsgA payload. After the first uplink data is generated, the first uplink data may be stored in an MsgA buffer.

It should be understood that the types of the random access preambles are different, and the definitions of the corresponding first PUSCH resource sets are also different, for example, in an embodiment, the first PUSCH resource sets include any one of the following:

In the case that the random access preamble is a competing random access preamble, a PUSCH resource set associated with a random access preamble group to which the random access preamble belongs;

and in the case that the random access preamble is a non-competitive random access preamble, the random access preamble is associated with a PUSCH resource set.

Further, the first PUSCH resource set may be configured by the network device through RRC signaling, for example, may be configured through a broadcasted system message, for example, and may also be configured through RRC dedicated signaling. In other words, in this embodiment, before the random access preamble is sent, the method further includes:

and receiving the PUSCH configuration information sent by the network equipment, wherein the PUSCH configuration information is used for configuring a PUSCH resource set, and the PUSCH resource set comprises the first PUSCH resource set.

Still further, it should be understood that the association relationship between the random access preamble and the first PUSCH resource set may be known through the resource configuration indicated in the RRC signaling. For example, in the case that the network device configures the random access preamble as a contended random access preamble, the network device may configure a random access preamble group a, where the random access preamble group a includes at least one contended random access preamble, and the network device configures a corresponding one PUSCH resource set a for the random access preamble group a, and at the same time, the network device may configure a random access preamble group B, and the network device configures a corresponding another different PUSCH resource set B for the random access preamble group B. At this time, the random access preamble group and the PUSCH resource group have a one-to-one association relationship. Specifically, if the contention random access preamble selected by the terminal belongs to the random access preamble group a, the associated first PUSCH resource set is PUSCH resource set a. If the contention random access preamble selected by the terminal belongs to the random access preamble group B, the associated first PUSCH resource set is PUSCH resource set B. For another example, in the case that the network device configures the random access preamble as a non-contention random access preamble, the network device may configure one or more non-contention random access preambles while the network device configures a corresponding one of the PUSCH resource sets for the one or more non-contention random access preambles. At this time, the non-contention random access preamble and the PUSCH resource set have a one-to-one or many-to-one association relationship. Specifically, if the terminal selects the non-contention random access preamble, the associated first PUSCH resource set is a PUSCH resource set configured only in the RRC dedicated signaling.

In an embodiment, the generating the first uplink data according to the first PUSCH resource set associated with the random access preamble includes:

determining hybrid automatic repeat request (HARQ) information according to a first Physical Uplink Shared Channel (PUSCH) resource set associated with the random access preamble, wherein the HARQ information comprises Transport Block Size (TBS) information;

and generating the first uplink data according to the TBS information.

Further, the generating the first uplink data according to the TBS information means that the multiplexing and assembling entity of the MAC layer can generate the first uplink data according to the TBS information when the random access preamble is not mapped to the PUSCH resource of the effective physical uplink shared channel.

It should be understood that, in this embodiment, when the random access preamble is a contention random access preamble, hybrid automatic repeat request HARQ information is determined according to a first PUSCH resource set associated with a random access preamble group to which the random access preamble belongs; and when the random access preamble is a non-competitive random access preamble, determining hybrid automatic repeat request (HARQ) information according to a first Physical Uplink Shared Channel (PUSCH) resource set associated with the random access preamble. The HARQ information may further include HARQ process id, RV, NDI, and the like.

In another embodiment, the generating the first uplink data according to the first PUSCH resource set associated with the random access preamble includes:

determining a first PUSCH resource from a first PUSCH resource set which is stored by the MAC layer and is associated with the random access preamble;

determining HARQ information corresponding to the first PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

and generating the first uplink data according to the first PUSCH resource and the HARQ information.

Optionally, before the random access preamble is sent, the method further includes:

after the random access process is triggered, configuring an allocation parameter, wherein the allocation parameter is used for determining the PUSCH resource which is carried by the first uplink data in the first PUSCH resource set. For example, after the random access procedure is triggered, the RRC layer configures allocation parameters of resources related to carrying the first uplink data in the PUSCH resource set.

and after the random access process is triggered, storing the PUSCH resource set to a Media Access Control (MAC) layer.

It should be understood that the above-mentioned resource allocation parameters related to carrying the first uplink data in the PUSCH resource set at least include at least one of the following:

Time domain resource allocation parameters of the PUSCH resource;

offset values in the time domain of PUSCH resources;

multiplexing factors on the frequency domain of PUSCH resources;

a configuration period of PRACH resources;

and (3) configuration period of the PUSCH resource.

Further, it should be understood that the PUSCH resources in the first PUSCH resource set described above are PUSCH resources that have been uplink authorized. Determining a first PUSCH resource from the first PUSCH resource set stored in the MAC layer and associated with the random access preamble, or determining a UL grant from the first PUSCH resource set stored in the MAC layer and associated with the random access preamble. Corresponding HARQ information may be obtained based on the first PUSCH resource. At this time, the first PUSCH resource and the HARQ information may be handed to the HARQ entity, and thus the first uplink data may be generated according to the first PUSCH resource and the HARQ information.

In this embodiment, the manner of determining the first PUSCH resources may be set according to actual needs, for example, in an embodiment, the first PUSCH resources may be determined, for example, by an equal probability random selection manner, or may be determined according to an instruction of the network device.

Optionally, after the random access preamble is sent, the method further includes:

And clearing the PUSCH resource set stored by the MAC layer under the condition that the random access process is finished or the random access type is changed from the 2-step type to the 4-step type.

In this embodiment, the PUSCH resource set may be understood as a PUSCH resource set for carrying MsgA payload in a 2-step RA procedure. After the 2-step RA type is changed into the 4-step RA type, the PUSCH resource set is not required to be used, so that after the PUSCH resource set is cleared, the occupation of the MAC layer cache can be effectively reduced, and the system performance is improved.

Optionally, in this embodiment, the HARQ entity does not submit the first PUSCH resource and the HARQ information to a target HARQ process, where the target HARQ process is agreed by a protocol or indicated by HARQ information. For example, the protocol agrees to assign an identification number of 0 for the HARQ process.

Further, the generating the first uplink data according to the information carried by the fallback random access response includes:

and under the condition that a rollback random access response is received and no uplink data exists in the MsgA buffer, indicating a multiplexing and assembling entity to generate the first uplink data according to the rollback random access response.

In this embodiment, the backoff random access response carries related information for generating the first uplink data, for example, uplink grant information and corresponding HARQ information. After receiving the fallback random access response, if the MsgA buffer is found to be empty, the multiplexing and assembling entity may be instructed to generate the first uplink data, and store the first uplink data in the MsgA buffer. Specifically, the multiplexing and assembling entity may generate the first uplink data based on the related information carried by the fallback random access response.

Optionally, the method further comprises:

in case the logical channel carrying the first uplink data is not a common control channel (Common Control Channel, CCCH), the first uplink data comprises a cell radio network temporary identity (Cell Radio Network Temporary Identifier, C-RNTI) media access control element (Medium Access Control Control Element, MAC CE).

In this embodiment, that the logical channel carrying the first uplink data is not CCCH may be understood that this MsgA transmission or the current random access procedure is not for CCCH logical channels. In case the logical channel carrying the first uplink data is the common control channel CCCH, the first uplink data does not include C-RNTI MAC CE.

Optionally, after generating the first uplink data according to the fallback random access response, the method further includes:

when the first uplink data exists in the MsgA cache and the TBS corresponding to the second PUSCH resource in the second PUSCH resource set is not matched with the first uplink data in size, indicating a multiplexing and assembling entity to reconstruct or reorganize the first uplink data existing in the MsgA cache to obtain second uplink data;

And storing the second uplink data in an MsgA cache.

In this embodiment, the multiplexing and assembling entity may reconstruct (rebuild) the first uplink data existing in the MsgA buffer according to the TBS corresponding to the second PUSCH resource, to obtain second uplink data. Thus, the second upstream data can be obtained from the multiplexing and assembling entity and stored in the MsgA buffer. The second PUSCH resource set may be the same as or different from the first PUSCH resource set, and is not limited herein. The TBS corresponding to the second PUSCH resource not matching the first uplink data size may be understood as the TBS corresponding to the second PUSCH resource being different from the first uplink data size.

and under the condition that the random access type is changed from the 2-step type to the 4-step type, if the first uplink data exists in the Msg A cache and the uplink data does not exist in the Msg3 cache, storing the first uplink data in the Msg A cache into the Msg3 cache.

In this embodiment, the first uplink data in the MsgA cache may be first acquired, and then the acquired first uplink data may be stored in the Msg3 cache. Thus, when Msg3 is transmitted, the first uplink data can be carried.

Further, after the random access preamble is sent, the method further includes:

and under the condition that the random access preamble is mapped with the effective PUSCH resource and the random access preamble is a non-competitive random access preamble, generating third uplink data according to a third PUSCH resource set associated with the random access preamble.

The third uplink data may be understood as uplink data that is subsequently transmitted in an uplink direction, or may be referred to as MsgA payload, and after the third uplink data is generated, the third uplink data may be stored in the MsgA buffer.

Since in this embodiment, a manner of generating the third uplink data is defined in the case where the random access preamble is mapped to the valid PUSCH resource and the random access preamble is a non-contention random access preamble. Thereby further ensuring the smooth proceeding of the subsequent fallback process. The reliability of the random access procedure can be further improved.

The third PUSCH resource set is used to carry the third uplink data. Specifically, the third PUSCH resource set may be the same as or different from the first PUSCH resource set; meanwhile, the third PUSCH resource set may be the same as or different from the second PUSCH resource set; and are not further limited herein.

Optionally, the generating third uplink data according to the third PUSCH resource set associated with the random access preamble includes:

determining a third PUSCH resource in a third PUSCH resource set associated with the random access preamble;

determining HARQ information corresponding to the third PUSCH resource;

submitting the third PUSCH resource and the HARQ information to an HARQ entity;

and generating the third uplink data according to the third PUSCH resource and the HARQ information.

The third PUSCH resource set may include one PUSCH resource, or may include one or more PUSCH resources that are time division multiplexed (Time Division Multiplexing) or frequency division multiplexed (Frequency Division Multiplexing), and the one PUSCH resource may be periodic. Each PUSCH resource includes at least one PUSCH transmission opportunity and a DMRS resource.

It should be understood that the PUSCH resources in the third PUSCH resource set described above are PUSCH resources that have been uplink authorized. Determining a third PUSCH resource in the third PUSCH resource set associated with the random access preamble may also be understood as determining a UL grant in the third PUSCH resource set associated with the random access preamble. Corresponding HARQ information may be obtained based on the third PUSCH resource. At this time, the third PUSCH resource and the HARQ information may be handed to the HARQ entity, and the third uplink data may be generated from the third PUSCH resource and the HARQ information.

In this embodiment, the manner of determining the third PUSCH resources may be set according to actual needs, for example, in an embodiment, the determination may be performed by, for example, an equal probability random selection manner, or may be determined according to an instruction of the network device.

Further, the third PUSCH resource set may be configured by the network device through RRC signaling, for example, in this embodiment, before the sending the random access preamble, the method further includes:

and receiving the PUSCH configuration information sent by the network equipment through the RRC dedicated signaling, wherein the PUSCH configuration information is used for configuring a PUSCH resource set, and the PUSCH resource set comprises the third PUSCH resource set.

Still further, it should be understood that the association relationship between the random access preamble and the third PUSCH resource set may be known through the resource configuration indicated in the RRC dedicated signaling. For example, in the case that the network device configures the random access preamble as a non-contention random access preamble, the network device may configure one or more non-contention random access preambles while the network device configures a corresponding one of the PUSCH resource sets for the one or more non-contention random access preambles. At this time, the non-contention random access preamble and the PUSCH resource set have a one-to-one or many-to-one association relationship. Specifically, if the terminal selects the non-contention random access preamble, the associated first PUSCH resource set is a PUSCH resource set configured only in the RRC dedicated signaling.

For better understanding of the present application, the following describes specific implementation procedures of the present application in detail for different application scenarios.

Example 1

1. The network device configures the UE with 2-step RA related resource configurations through RRC signaling. The 2 random access may include a 2-step Contention random access (Contention Based Random Access, CBRA) and a 2-step non-Contention random access (content-Free Random Access, CFRA).

2. The terminal triggers a 2-step RA procedure.

3. In this 2-step RA attempt, if the 2-step RA preamble selected by the MAC entity is a 2-step RA non-contention preamble, and if the 2-step RA preamble or its corresponding PRACH octasion is mapped with PUSCH (MsgA PSUCH) resources of a valid bearer MsgA payload transmission, the terminal performs the following steps:

and obtaining the UL grant and corresponding HARQ information according to the MsgA PUSCH resource configuration associated with the selected 2-step RA non-contention preamble. The MsgA PUSCH resource configuration is configured through RACH-Config-dedicatedly;

and giving the UL grant and the HARQ information to the HARQ entity.

4. If the 2-step RA preamble selected by the MAC entity is a 2-step RA contention preamble and the 2-step RA preamble or its corresponding PRACH occalation is not mapped with a valid MsgA PUSCH resource, the terminal performs the following steps:

And acquiring HARQ information (such as TBS) according to the MsgA PUSCH resource configuration associated with the random access preamble group to which the selected 2-step RA contended preamble belongs, and then indicating a multiplexing and assembling entity to generate MsgA payload according to the TBS information, and storing the MsgA payload in an MsgA buffer. The MsgA PUSCH resource configuration is configured through SIB1 information.

5. If the 2-step RA preamble selected by the MAC entity is a 2-step RA non-contention preamble, and the 2-step RA preamble or its corresponding PRACH occalation is not mapped with a valid MsgA PUSCH resource, the terminal performs the following steps:

HARQ information (e.g., TBS) is obtained from the MsgA PUSCH resource configuration associated with the selected 2-step RA non-contention preamble, and then the multiplexing and assembling entity is instructed to generate an MsgA payload from the TBS information, and store it in the MsgA buffer. The MsgA PUSCH resource configuration is configured through RACH-Config-dedicatedly.

Example two

1. The network device configures the UE with 2-step RA related resource configurations through RRC signaling. The 2-step RA may include a 2-step CBRA and a 2-step CFRA.

2. The terminal triggers a 2-step RA procedure. The RRC layer of the UE first configures the MsgA PUSCH related resource allocation parameters, for example: msgA-PUSCH-timedomainalllocation and startsymbolandLengthmsga-PO. Upon triggering the 2-step RA procedure to initialize, the UE saves the MsgA PUSCH resources (e.g., UL grant) configured in RRC in the MAC entity, where the UL grant is a non-dynamic UL grant through which the UE may transmit MsgA payload.

and obtaining the UL grant and corresponding HARQ information according to the MsgA PUSCH resource configuration associated with the selected 2-step RA non-contention preamble. The MsgA PUSCH resource configuration is configured through RACH-Config-dedicatedly.

And giving the UL grant and the HARQ information to the HARQ entity.

roughly randomly selecting one UL grant and corresponding HARQ information from the MsgA PUSCH resource configuration associated with the random access preamble group to which the selected 2-step RA contended preamble belongs;

the UL grant and the HARQ information are handed to an HARQ entity;

the instruction multiplexing and assembling entity generates an MsgA payload according to the UL grant and the HARQ information, and stores it in the MsgA buffer.

roughly randomly selecting one UL grant and corresponding HARQ information from the MsgA PUSCH resource configuration associated with the selected 2-step RA non-contention preamble;

and giving the UL grant and the HARQ information to the HARQ entity.

6. If the 2-step RA procedure is completed or the UE transitions the random access type from 2-step RA to 4-step RA, the UE clears all the MsgA PUSCH resources stored by the MAC layer for MsgA payload transmission.

Example III

2. The terminal triggers a 2-step RA procedure.

and giving the UL grant and the HARQ information to the HARQ entity.

4. If the UE receives a fallback rar and if the MsgA buffer is empty at this time, the terminal has the following actions:

if the transmission is not for data in the CCCH logical channel, then

Instruct the multiplexing and assembling entity to include a C-RNTI MAC CE in subsequent upstream transmissions;

5. the multiplexing and assembling entity generates an MsgA buffer based on the related information carried by the Fallback RAR, and obtains an MsgA payload from the multiplexing and assembling entity, and stores the MsgA payload in the MsgA buffer.

6. In the next 2-step RA attempt (e.g., UE prepares for the next transmission of MsgA), if data has been buffered in the MsgA buffer and the UL grant received at this time is an MsgA UL grant for MsgA payload transmission, and the TBS corresponding to the MsgA UL grant at this time is different from the size of the MAC PDU buffered in the MsgA buffer, the terminal has the following actions:

the multiplexing and assembling entity is instructed to reconstruct or reorganize the MAC PDU in the MsgA buffer;

The MsgA payload is obtained from the multiplexing and assembling entity and stored in the MsgA buffer.

6. If the UE transitions the random access type from 2-step RA to 4-step RA, and if the MsgA buffer is not empty, and if the Msg3 buffer is not empty, the terminal has the following behavior:

the MsgA payload is obtained from the MsgA buffer and stored in the Msg3 buffer.

Referring to fig. 3, fig. 3 is a block diagram of a terminal according to an embodiment of the present application, as shown in fig. 3, a terminal 300 includes:

a transmitting module 301, configured to transmit a random access preamble;

a data generating module 302, configured to generate, when the random access preamble is not mapped to an effective physical uplink shared channel PUSCH resource, first uplink data according to a first PUSCH resource set associated with the random access preamble, or generate first uplink data according to a fallback random access response;

the first PUSCH resource set is used for carrying the first uplink data.

Optionally, the first PUSCH resource set includes any one of the following:

Optionally, the terminal further includes:

a receiving module, configured to receive PUSCH configuration information sent by a network device, where the PUSCH configuration information is used to configure a PUSCH resource set, and the PUSCH resource set includes the first PUSCH resource set.

Optionally, the data generating module 302 is specifically configured to perform the following operations:

and generating the first uplink data according to the TBS information.

determining HARQ information corresponding to the first PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

The terminal further comprises:

And the configuration module is used for configuring an allocation parameter after the random access process is triggered, wherein the allocation parameter is used for determining the PUSCH resource which is carried by the first uplink data in the first PUSCH resource set.

Optionally, the terminal further includes:

and the storage module is used for storing the PUSCH resource set to a Media Access Control (MAC) layer after the random access process is triggered.

Optionally, the terminal 300 further includes:

and the clearing module is used for clearing the PUSCH resource set stored by the MAC layer under the condition that the random access process is finished or the random access type is changed from the 2-step type to the 4-step type.

Optionally, the HARQ entity does not submit the first PUSCH resource and the HARQ information to a target HARQ process, where the target HARQ process is agreed by a protocol or indicated by HARQ information.

Optionally, the data generating module 302 is specifically configured to: and under the condition that a rollback random access response is received and no uplink data exists in the MsgA buffer, indicating a multiplexing and assembling entity to generate the first uplink data according to the rollback random access response.

Optionally, in the case that the logical channel carrying the first uplink data is not the common control channel CCCH, the first uplink data includes a cell radio network temporary identifier media access control unit C-RNTI MAC CE.

Optionally, the terminal further includes: a memory module, wherein,

the data generating module is further configured to instruct a multiplexing and assembling entity to reconstruct or reorganize the first uplink data existing in the MsgA buffer to obtain second uplink data when the first uplink data exists in the MsgA buffer and a TBS corresponding to a second PUSCH resource in the second PUSCH resource set is not matched with the first uplink data in size;

the storage module is used for storing the second uplink data in an MsgA cache.

Optionally, the terminal further includes:

the storage module is configured to store, when the random access type is changed from the 2-step type to the 4-step type, the first uplink data in the MsgA cache to the Msg3 cache if the first uplink data exists in the Msg3 cache and no uplink data exists in the Msg3 cache.

Optionally, the data generating module 302 is further configured to: and under the condition that the random access preamble is mapped with the effective PUSCH resource and the random access preamble is a non-competitive random access preamble, generating third uplink data according to a third PUSCH resource set associated with the random access preamble.

determining HARQ information corresponding to the third PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

Optionally, the terminal further includes:

and the receiving module is used for receiving the PUSCH configuration information sent by the network equipment through the RRC dedicated signaling, wherein the PUSCH configuration information is used for configuring a PUSCH resource set, and the PUSCH resource set comprises the third PUSCH resource set.

The terminal provided in this embodiment of the present application can implement each process implemented by the terminal in the method embodiment of fig. 2, and in order to avoid repetition, a description is omitted here.

Figure 4 is a schematic diagram of a hardware architecture of a terminal implementing various embodiments of the present application,

the terminal 400 includes, but is not limited to: radio frequency unit 401, network module 402, audio output unit 403, input unit 404, sensor 405, display unit 406, user input unit 407, interface unit 408, memory 409, processor 410, and power source 411. Those skilled in the art will appreciate that the terminal structure shown in fig. 4 is not limiting of the terminal and that the terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. In the embodiment of the application, the terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.

A radio frequency unit 401 for transmitting a random access preamble;

a processor 410, configured to generate first uplink data according to a first PUSCH resource set associated with the random access preamble, or generate first uplink data according to a fallback random access response, if the random access preamble is not mapped with an effective physical uplink shared channel PUSCH resource;

the first PUSCH resource set is used for carrying the first uplink data.

It should be understood that, in this embodiment, the processor 410 and the radio frequency unit 401 can implement each process implemented by the terminal in the method embodiment of fig. 2, and in order to avoid repetition, a description is omitted here.

It should be understood that, in the embodiment of the present application, the radio frequency unit 401 may be used to receive and send information or signals during a call, specifically, receive downlink data from a base station, and then process the downlink data with the processor 410; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 401 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 401 may also communicate with networks and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 402, such as helping the user to send and receive e-mail, browse web pages, access streaming media, etc.

The audio output unit 403 may convert audio data received by the radio frequency unit 401 or the network module 402 or stored in the memory 409 into an audio signal and output as sound. Also, the audio output unit 403 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the terminal 400. The audio output unit 403 includes a speaker, a buzzer, a receiver, and the like.

The input unit 404 is used to receive an audio or video signal. The input unit 404 may include a graphics processor (Graphics Processing Unit, GPU) 4041 and a microphone 4042, the graphics processor 4041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 406. The image frames processed by the graphics processor 4041 may be stored in memory 409 (or other storage medium) or transmitted via the radio frequency unit 401 or the network module 402. The microphone 4042 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 401 in the case of a telephone call mode.

The terminal 400 also includes at least one sensor 405, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 4061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 4061 and/or the backlight when the terminal 400 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when the accelerometer sensor is stationary, and can be used for recognizing the terminal gesture (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 405 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which are not described herein.

The display unit 406 is used to display information input by a user or information provided to the user. The display unit 406 may include a display panel 4061, and the display panel 4061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 407 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 407 includes a touch panel 4071 and other input devices 4072. The touch panel 4071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 4071 or thereabout using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 4071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 410, and receives and executes commands sent from the processor 410. In addition, the touch panel 4071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 407 may include other input devices 4072 in addition to the touch panel 4071. In particular, other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 4071 may be overlaid on the display panel 4061, and when the touch panel 4071 detects a touch operation thereon or thereabout, the touch operation is transferred to the processor 410 to determine the type of touch event, and the processor 410 then provides a corresponding visual output on the display panel 4061 according to the type of touch event. Although in fig. 4, the touch panel 4071 and the display panel 4061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 4071 may be integrated with the display panel 4061 to implement the input and output functions of the terminal, which is not limited herein.

The interface unit 408 is an interface through which an external device is connected to the terminal 400. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 408 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 400 or may be used to transmit data between the terminal 400 and an external device.

Memory 409 may be used to store software programs as well as various data. The memory 409 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 409 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 410 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 409 and calling data stored in the memory 409, thereby performing overall monitoring of the terminal. Processor 410 may include one or more processing units; preferably, the processor 410 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 410.

The terminal 400 may further include a power source 411 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 411 may be logically connected to the processor 410 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.

In addition, the terminal 400 includes some functional modules, which are not shown, and will not be described herein.

Preferably, the embodiment of the present application further provides a terminal, including a processor 410, a memory 409, and a program or an instruction stored in the memory 409 and capable of running on the processor 410, where the program or the instruction implements each process of the embodiment of the random access processing method when executed by the processor 410, and the same technical effects can be achieved, and for avoiding repetition, a description is omitted herein.

The embodiment of the application further provides a computer readable storage medium, on which a program or an instruction is stored, where the program or the instruction implements each process of the embodiment of the random access processing method at the terminal side provided by the embodiment of the application when being executed by a processor, and the same technical effect can be achieved, so that repetition is avoided, and no detailed description is given here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. A random access processing method, comprising:

transmitting a random access preamble;

the first PUSCH resource set is used for carrying the first uplink data;

wherein after the random access preamble is sent, the method further comprises:

generating third uplink data according to a third PUSCH resource set associated with the random access preamble under the condition that the random access preamble is mapped with the effective PUSCH resource and the random access preamble is a non-competitive random access preamble;

Wherein the generating third uplink data according to the third PUSCH resource set associated with the random access preamble includes:

determining HARQ information corresponding to the third PUSCH resource;

submitting the third PUSCH resource and the HARQ information to an HARQ entity;

2. The method of claim 1, wherein the first set of PUSCH resources comprises any one of:

3. The method according to claim 1 or 2, characterized in that before the sending of the random access preamble, the method further comprises:

4. The method of claim 3, wherein the generating the first uplink data from the first PUSCH resource set associated with the random access preamble comprises:

and generating the first uplink data according to the TBS information.

5. The method of claim 3, wherein the generating the first uplink data from the first PUSCH resource set associated with the random access preamble comprises:

determining a first PUSCH resource from a first PUSCH resource set which is stored by a Media Access Control (MAC) layer and is associated with the random access preamble;

determining HARQ information corresponding to the first PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

6. The method of claim 5, wherein prior to the transmitting the random access preamble, the method further comprises:

after the random access process is triggered, configuring an allocation parameter, wherein the allocation parameter is used for determining the PUSCH resource which is carried by the first uplink data in the first PUSCH resource set.

7. The method of claim 5, wherein prior to the transmitting the random access preamble, the method further comprises:

and after the random access process is triggered, storing the PUSCH resource set to the MAC layer.

8. The method of claim 7, wherein after the transmitting the random access preamble, the method further comprises:

9. The method of claim 5, wherein the HARQ entity does not submit the first PUSCH resource and the HARQ information to a target HARQ process, the target HARQ process being agreed upon by a protocol or indicated by HARQ information.

10. The method of claim 1, wherein the generating the first uplink data from the fallback random access response comprises:

11. The method of claim 10, wherein the first uplink data comprises a cell radio network temporary identity medium access control unit C-RNTI MAC CE in the case where the logical channel carrying the first uplink data is not a common control channel CCCH.

12. The method of claim 10, wherein after generating the first uplink data from the fallback random access response, the method further comprises:

and storing the second uplink data in an MsgA cache.

13. The method of claim 10, wherein after generating the first uplink data from the fallback random access response, the method further comprises:

14. The method of claim 1, wherein prior to the transmitting the random access preamble, the method further comprises:

15. A terminal, comprising:

a transmitting module, configured to transmit a random access preamble;

the first PUSCH resource set is used for carrying the first uplink data;

wherein, the data generation module is further used for: generating third uplink data according to a third PUSCH resource set associated with the random access preamble under the condition that the random access preamble is mapped with the effective PUSCH resource and the random access preamble is a non-competitive random access preamble;

the data generation module is specifically configured to perform the following operations:

Determining HARQ information corresponding to the third PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

16. The terminal of claim 15, wherein the first set of PUSCH resources comprises any one of:

17. A terminal according to claim 15 or 16, characterized in that the terminal further comprises:

18. The terminal of claim 17, wherein the data generation module is specifically configured to:

And generating the first uplink data according to the TBS information.

19. The terminal of claim 17, wherein the data generation module is specifically configured to:

determining HARQ information corresponding to the first PUSCH resource;

submitting the first PUSCH resource and the HARQ information to an HARQ entity;

20. The terminal of claim 19, wherein the terminal further comprises:

21. The terminal of claim 19, wherein the terminal further comprises:

and the storage module is used for storing the PUSCH resource set to the MAC layer after the random access process is triggered.

22. The terminal of claim 21, wherein the terminal further comprises:

23. The terminal of claim 19, wherein the HARQ entity does not submit the first PUSCH resource and the HARQ information to a target HARQ process, the target HARQ process being agreed upon by a protocol or indicated by HARQ information.

24. The terminal according to claim 15, wherein the data generation module is specifically configured to: and under the condition that a rollback random access response is received and no uplink data exists in the MsgA buffer, indicating a multiplexing and assembling entity to generate the first uplink data according to the rollback random access response.

25. The terminal of claim 24, wherein the first uplink data includes a cell radio network temporary identity medium access control unit C-RNTI MAC CE in the case where the logical channel carrying the first uplink data is not a common control channel CCCH.

26. The terminal of claim 24, further comprising a memory module, wherein,

the storage module is used for storing the second uplink data in an MsgA cache.

27. The terminal of claim 24, wherein the terminal further comprises:

28. A terminal, comprising: memory, a processor and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the random access processing method according to any of claims 1 to 14.

29. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the random access processing method according to any of claims 1 to 14.