CN113677038A

CN113677038A - Random access processing method and terminal

Info

Publication number: CN113677038A
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: 2021-11-19
Anticipated expiration: 2040-05-15
Also published as: CN116634597A; WO2021228226A1; CN113677038B

Abstract

The application provides a random access processing method and a terminal, wherein the method comprises the following steps: sending a random access preamble; under the condition that the random access preamble is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource, 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; wherein 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 application relates to the field of communications technologies, and in particular, to a random access processing method and a terminal.

Background

As is known, in the current 2-step Random Access (RA) process, 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 a Fallback Random Access Response (Fallback rar) which is included in the MsgB and matches the index value of the transmitted MsgA Random Access preamble (preamble), the UE will take the MsgA payload (payload) from the MsgA buffer and store it in the Msg3 buffer. Then, the UE sends Msg3 to the network side, and then performs contention resolution. For the 2-step RA procedure, the MsgA preamble may not map with a 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 a subsequent fallback process cannot be ensured, which results in low reliability of a random access process.

Disclosure of Invention

The embodiment of the application provides a random access processing method and a terminal, so as to solve the problem of low reliability in a random access process.

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

sending a random access preamble;

under the condition that the random access preamble is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource, 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;

wherein 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 sending module, configured to send a random access preamble;

a data generation module, 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, when the random access preamble is not mapped with an effective PUSCH resource of a physical uplink shared channel;

In a third aspect, an embodiment of the present application provides a terminal, including: a memory, a processor and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps in the random access processing method described above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instructions are stored, and the program or instructions, when executed by a processor, implement the steps of the above random access processing method.

The embodiment of the application sends the random access lead code; under the condition that the random access preamble is not mapped with an effective Physical Uplink Shared Channel (PUSCH) resource, 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; wherein the first PUSCH resource set is used for carrying the first uplink data. Therefore, 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 needed to be used 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 it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a block diagram of a network system to which an embodiment of the present application is applicable;

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

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

fig. 4 is a structural diagram of another terminal provided in the embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "comprises," "comprising," or any other variation thereof, in the description and claims of this application, 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, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related 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 (lte) system, or a subsequent Evolved communication system.

Referring to fig. 1, fig. 1 is a structural diagram of a network system to which an 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 devices, for example: it should be noted that, in the embodiment of the present application, a specific type of the terminal 11 is not limited, and the terminal may be a terminal-side Device such as a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal digital assistant (PDA for short), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device). The network device 12 may be a 5G base station, a later-version base station, or a base station in another communication system, or referred to as a node B, an evolved node B, or a Transmission Reception Point (TRP), an Access Point (AP), or another vocabulary in the field, and the network device is not limited to a specific technical vocabulary 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 the 5G base station is taken as an example, but the specific type of the network device is not limited.

For convenience of understanding, some contents related to the embodiments of the present application are described below:

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

In order to transmit UL-SCH Data, a terminal must have a corresponding uplink grant (UL grant) and corresponding HARQ information including a HARQ process identification (HARQ process id), a Redundancy Version (RV), a New Data Indicator (NDI), a Transport Block Size (TBS), and the like. For example, to transmit MsgA payload, the network device needs to indicate, through Radio Resource Control (RRC) signaling, a configuration related to PUSCH resources for carrying MsgA payload transmission, such as: a UL grant for MsgA payload transmission (MsgA UL grant), which may include a time-frequency code spatial resource allocation.

When the terminal receives an MsgA UL grant, the Media Access Control (MAC) entity may instruct the multiplexing and assembling entity of the MAC layer to generate a MAC Protocol Data Unit (PDU), i.e., MsgA payload, according to HARQ information corresponding to the MsgA UL grant, and store the PDU in the MsgA buffer.

Next, the MAC entity will forward the MsgA UL grant and the corresponding HARQ information to the HARQ entity (entity). Then, the HARQ entity obtains the MsgA payload to be transmitted from the MsgA buffer. Then, the HARQ entry may indicate that the corresponding HARQ process triggers transmission of a new data, for example, indicate that the HARQ process id 0 triggers transmission of a new 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 the newly transmitted 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, and as shown in fig. 2, the method includes the following steps:

step 201, sending a random access lead code;

in this embodiment of the present application, the random access preamble may be referred to as a preamble, and further may be a contention-based preamble or a non-contention preamble. When the terminal performs the Random Access procedure, an effective Physical Random Access Channel (PRACH) resource may be selected for transmitting the Random Access preamble. 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 non-contended preamble may be understood as a 2-step RA non-contended preamble. In the 2-step RA procedure, the terminal first sends MsgA, which carries a random access preamble.

Step 202, in a case that the random access preamble is not mapped with an effective physical uplink shared channel, PUSCH, resource, 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; wherein the first PUSCH resource set is used for carrying the first uplink data.

Generally, if the random access preamble is not mapped with a valid Physical Uplink Shared Channel (PUSCH) resource, the terminal may send MsgA on a selected one valid PRACH transmission opportunity (occasion). Further, the fact that the random access preamble does not map with the effective PUSCH resource of the physical uplink shared channel may be understood as that the preamble contended by the 2-step RA in one Association Pattern Period (Association Pattern Period) does not map with the effective PUSCH resource of the physical uplink shared channel. For example, in one association pattern period, the PUSCH resource selected by the terminal in the first PUSCH resource set associated with the random access preamble is an invalid PUSCH resource. Specifically, part or all of the 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 Time Division Multiplexing (Time Division Multiplexing) or Frequency Division Multiplexing (Frequency Division Multiplexing) PUSCH resources, and the one PUSCH resource may also be periodic. Each PUSCH resource includes at least one PUSCH transmission opportunity and Demodulation Reference Signal (DMRS) resource.

The first uplink data may be understood as uplink data to be subsequently transmitted in an uplink, and may also be referred to as MsgA payload. After the first uplink data is generated, the first uplink data may be stored in the 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 different, for example, in an embodiment, the first PUSCH resource set includes any one of the following:

under the condition that the random access preamble code is a competitive random access preamble code, a PUSCH resource set associated with a random access preamble code group to which the random access preamble code belongs;

and under the condition that the random access preamble code is a non-competitive random access preamble code, the PUSCH resource set associated with the random access preamble code.

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, and may also be configured through RRC dedicated signaling. In other words, in this embodiment, before the sending the random access preamble, the method further includes:

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

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 a 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 configure 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 configure 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 set 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 the PUSCH resource set a. If the contended random access preamble selected by the terminal belongs to the random access preamble group B, the associated first PUSCH resource set is the PUSCH resource set B. For another example, in a 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, and configure a corresponding PUSCH resource set for the one or more non-contention random access preambles at the same time. 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 uniquely configured 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 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 of the first uplink data according to the TBS information means that the multiplexing and assembling entity in the MAC layer can generate the first uplink data according to the TBS information when the random access preamble is not mapped to a valid PUSCH resource.

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 code is a non-competitive random access preamble code, determining hybrid automatic repeat request (HARQ) information according to a first PUSCH resource set associated with the random access preamble code. The HARQ information may further include HARQ process id, RV, NDI, and the like.

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

determining a first PUSCH resource from a first PUSCH resource set stored by a MAC layer and 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 a HARQ entity;

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

Optionally, before the sending the random access preamble, the method further includes:

and after a random access process is triggered, configuring an allocation parameter, wherein the allocation parameter is used for determining that the first PUSCH resource set carries PUSCH resources of the first uplink data. For example, after the random access process is triggered, the RRC layer configures an allocation parameter of a resource related to the first uplink data carried 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 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 PUSCH resources;

an offset value in the time domain of the PUSCH resource;

multiplexing factors in the frequency domain of the PUSCH resources;

a configuration period of PRACH resources;

and configuration period of PUSCH resources.

Further, it should be understood that the PUSCH resources in the first PUSCH resource set described above are PUSCH resources that have been granted uplink. Determining a first PUSCH resource from the first PUSCH resource set associated with the random access preamble stored by the MAC layer, which may also be understood as determining a UL grant from the first PUSCH resource set associated with the random access preamble stored by the MAC layer. Corresponding HARQ information may be obtained based on the first PUSCH resource. In this case, the first PUSCH resource and the HARQ information may be handed to the HARQ entity, and the first uplink data may be generated based on the first PUSCH resource and the HARQ information.

In this embodiment, the manner of determining the first PUSCH resource may be set according to actual needs, for example, in an embodiment, the first PUSCH resource may be determined in 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:

clearing the PUSCH resource set stored by the MAC layer in case that a random access procedure is completed or a random access type is changed from a 2-step type to a 4-step type.

In this embodiment, the PUSCH resource set may be understood as a transmission PUSCH resource set carrying an MsgA payload in a 2-step RA process. After the 2-step RA type is changed into the 4-step RA type, the PUSCH resource set does not need 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 stipulates that the identification number of the HARQ process is 0.

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 fallback random access response is received and no uplink data exists in the MsgA cache, instructing a multiplexing and assembling entity to generate the first uplink data according to the fallback random access response.

In this embodiment, the backoff random access response carries relevant information used 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 relevant information carried by the fallback random access response.

Optionally, the method further includes:

when the logical Channel carrying the first uplink data is not a Common Control Channel (CCCH), the first uplink data includes a Cell Radio Network Temporary Identifier (C-RNTI) Medium Access Control Element (MAC CE).

In this embodiment, it may be understood that the logical channel carrying the first uplink data is not a CCCH logical channel, and the MsgA transmission or the current random access process is not a CCCH logical channel. And in the case that the logical channel carrying the first uplink data is a 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 recombine the first uplink data existing in the MsgA cache to obtain second uplink data;

and storing the second uplink data in an MsgA buffer.

In this embodiment, the multiplexing and assembling entity reconstructs or reassembles (rebuilds) the first uplink data existing in the MsgA cache according to the TBS corresponding to the second PUSCH resource to obtain the second uplink data. Thus, the second upstream data can be retrieved from the multiplexing and assembly 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 above mismatch between the TBS corresponding to the second PUSCH resource and the first uplink data size may be understood as that the TBS corresponding to the second PUSCH resource is different from the first uplink data size.

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 MsgA cache and no uplink data exists in the Msg3 cache, storing the first uplink data in the MsgA cache into the Msg3 cache.

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

Further, after the sending the random access preamble, the method further includes:

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

It should be noted that the third uplink data may be understood as uplink data to be subsequently transmitted in an uplink, which may also 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.

In this embodiment, a manner of generating the third uplink data is defined when the random access preamble is mapped with an effective PUSCH resource and the random access preamble is a non-contention random access preamble. Therefore, the smooth proceeding of the subsequent fallback process can be further ensured. The reliability of the random access procedure can thus be further improved.

And the third PUSCH resource set is used for bearing 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 a 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 Time Division Multiplexing (Time Division Multiplexing) or Frequency Division Multiplexing (Frequency Division Multiplexing) PUSCH resources, and the one PUSCH resource may also be periodic. Each PUSCH resource includes at least one PUSCH transmission opportunity and DMRS resource.

It should be understood that the PUSCH resources in the third PUSCH resource set described above are PUSCH resources that have been granted uplink. Determining a third PUSCH resource in the third PUSCH resource set associated with the random access preamble, which 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. In this case, the third PUSCH resource and the HARQ information may be handed to the HARQ entity, and the third uplink data may be generated based on the third PUSCH resource and the HARQ information.

In this embodiment, the manner of determining the third PUSCH resource may be set according to actual needs, for example, in an embodiment, the third PUSCH resource may be determined in 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 PUSCH configuration information sent by the network equipment through 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.

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 a case where 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, and configure a corresponding one of 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 uniquely configured in the RRC dedicated signaling.

For better understanding of the present application, specific implementation processes of the present application are described in detail below for different application scenarios.

Example one

1. The network equipment configures 2-step RA related resource configuration for the UE through RRC signaling. The 2 Random Access may include 2-step Contention Based Random Access (CBRA) and 2-step non-Contention Random Access (CFRA).

2. The terminal triggers the 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 opportunity is mapped with a valid pusch (MsgA psuch) resource for carrying MsgA payload transmission, the terminal performs the following steps:

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

and handing 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 competitive preamble and the 2-step RA preamble or the corresponding PRACH event is not mapped with a valid MsgA PUSCH resource, the terminal executes the following steps:

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

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

and obtaining HARQ information (such as TBS) according to the MsgA PUSCH resource configuration associated with the selected 2-step RA non-competitive preamble, and then instructing the multiplexing and assembling entity to generate MsgA payload according to the TBS information and store the MsgA payload in the MsgA buffer. The MsgA PUSCH resource configuration is configured through RACH-Config-Dedicated.

Example two

1. The network equipment configures 2-step RA related resource configuration for the UE through RRC signaling. The 2-step RA may include a 2-step CBRA and a 2-step CFRA.

2. The terminal triggers the 2-step RA procedure. The RRC layer of the UE first configures resource allocation parameters related to the MsgA PUSCH, for example: msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO. When the 2-step RA procedure is triggered to initialize, the UE stores MsgA PUSCH resources (e.g., UL grant) configured in the RRC in the MAC entity, where the UL grant is a non-dynamic UL grant through which the UE can send MsgA payload.

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

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

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 preamble contended by the 2-step RA belongs;

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

and indicating the multiplexing and assembling entity to generate MsgA payload according to the UL grant and the HARQ information, and storing the MsgA payload in the MsgA buffer.

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

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

6. If the 2-step RA procedure is complete, or the UE changes 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 the 2-step RA procedure.

and handing 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

Instructing the multiplexing and assembly entity to include a C-RNTI MAC CE in the subsequent upstream transmission;

5. the multiplexing and assembling entity generates an MsgA buffer based on the related information carried by the Fallbacrar, acquires the 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., the UE is ready for the next MsgA transmission), if data is already buffered in the MsgA buffer and the received UL grant is a MsgA UL grant for MsgA payload transmission, and the TBS corresponding to the MsgA UL grant is different from the MAC PDU size buffered in the MsgA buffer, the terminal has the following actions:

indicating a multiplexing and assembling entity to reconstruct or recombine the MAC PDU in the MsgA buffer;

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

6. If the UE changes 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:

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

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

a sending module 301, configured to send a random access preamble;

a data generating module 302, 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, when the random access preamble is not mapped with an effective PUSCH resource of a physical uplink shared channel;

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

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 a HARQ entity;

The terminal further comprises:

a configuration module, configured to configure a distribution parameter after a random access process is triggered, where the distribution parameter is used to determine that the first PUSCH resource set carries PUSCH resources of the first uplink data.

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 completed 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 fallback random access response is received and no uplink data exists in the MsgA cache, instructing a multiplexing and assembling entity to generate the first uplink data according to the fallback random access response.

Optionally, in a case that the logical channel carrying the first uplink data is not a 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 generation module is further configured to instruct the multiplexing and assembling entity to reconstruct or reassemble the first uplink data existing in the MsgA cache to obtain second uplink data 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 does not match the size of the first uplink data;

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 the first uplink data in the MsgA buffer into the Msg3 buffer if the first uplink data exists in the MsgA buffer and no uplink data exists in the Msg3 buffer when the random access type is changed from the 2-step type to the 4-step type.

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

determining HARQ information corresponding to the third PUSCH resource;

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

Optionally, the terminal further includes:

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

The terminal provided in the embodiment of the present application can implement each process implemented by the terminal in the method embodiment of fig. 2, and is not described here again to avoid repetition.

Figure 4 is a schematic diagram of a hardware structure 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 supply 411. Those skilled in the art will appreciate that the terminal configuration shown in fig. 4 is not intended to be limiting, and that the terminal may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present application, the terminal includes, 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, configured to send 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, when the random access preamble is not mapped with a valid PUSCH resource of a physical uplink shared channel;

It should be understood that, in this embodiment, the processor 410 and the radio frequency unit 401 may implement each process implemented by the terminal in the method embodiment of fig. 2, and are not described herein again to avoid repetition.

It should be understood that, in the embodiment of the present application, the radio frequency unit 401 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 410; in addition, the uplink data is transmitted to the base station. Typically, radio 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. Further, the radio unit 401 can also communicate with a network 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 send and receive e-mails, browse web pages, and access streaming media.

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 related to a specific function performed by the terminal 400 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 403 includes a speaker, a buzzer, a receiver, and the like.

The input unit 404 is used to receive audio or video signals. The input Unit 404 may include a Graphics Processing Unit (GPU) 4041 and a microphone 4042, and the Graphics processor 4041 processes image data of a still picture or video obtained by an image capturing apparatus (such as 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 graphic processor 4041 may be stored in the 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 transmittable to a mobile communication base station via the radio frequency unit 401 in case of the phone call mode.

The terminal 400 also includes at least one sensor 405, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 4061 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 4061 and/or a backlight when the terminal 400 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 405 may also 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 will not be described in detail herein.

The display unit 406 is used to display information input by the 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 (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 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. Touch panel 4071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 4071 using a finger, a stylus, or any suitable object or attachment). The touch panel 4071 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction 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 sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 410, receives a command from the processor 410, and executes the command. In addition, the touch panel 4071 can be implemented by using various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 4071, the user input unit 407 may include other input devices 4072. Specifically, the other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a track ball, a mouse, and a joystick, which are not described herein again.

Further, the touch panel 4071 can be overlaid on the display panel 4061, and when the touch panel 4071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 410 to determine the type of the touch event, and then the processor 410 provides a corresponding visual output on the display panel 4061 according to the type of the 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 and the display panel 4061 may be integrated to implement the input and output functions of the terminal, which is not limited herein.

The interface unit 408 is an interface for connecting an external device to the terminal 400. For example, the external device may include a wired or wireless headset port, an external power supply (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.

The memory 409 may be used to store software programs as well as various data. The memory 409 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the 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 operating or executing software programs and/or modules stored in the memory 409 and calling data stored in the memory 409, thereby integrally monitoring the terminal. Processor 410 may include one or more processing units; preferably, the processor 410 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly 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 supply 411 (e.g., a battery) for supplying power to various components, and preferably, the power supply 411 may be logically connected to the processor 410 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.

In addition, the terminal 400 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present application further provides a terminal, which includes a processor 410, a memory 409, and a program or an instruction stored in the memory 409 and executable on the processor 410, where the program or the instruction is executed by the processor 410 to implement each process of the foregoing random access processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiments of the present application further provide a computer-readable storage medium, where a program or an instruction is stored in the computer-readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the method for processing random access at a terminal side provided in the embodiments of the present application, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a base station) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for processing random access, comprising:

sending a random access preamble;

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

3. The method of claim 1 or 2, wherein prior to the sending the random access preamble, the method further comprises:

4. The method of claim 3, wherein the generating first uplink data according to the first set of PUSCH resources 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 first uplink data according to the first set of PUSCH resources associated with the random access preamble comprises:

determining a first PUSCH resource from a first PUSCH resource set stored by a Media Access Control (MAC) layer and 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 a HARQ entity;

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

and after a random access process is triggered, configuring an allocation parameter, wherein the allocation parameter is used for determining that the first PUSCH resource set carries PUSCH resources of the first uplink data.

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

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

8. The method of claim 7, wherein after the sending 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, wherein the target HARQ process is agreed by a protocol or indicated by HARQ information.

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

11. The method according to claim 10, wherein in case that the logical channel carrying the first uplink data is not a Common Control Channel (CCCH), the first uplink data comprises a cell Radio Network Temporary Identity (RNTI) Medium Access Control (MAC) element (C-RNTI MAC CE).

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

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

and storing the second uplink data in an MsgA buffer.

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

14. The method of claim 1, wherein after the sending the random access preamble, the method further comprises:

15. The method of claim 14, wherein the generating third uplink data according to a third set of PUSCH resources associated with the random access preamble comprises:

determining HARQ information corresponding to the third PUSCH resource;

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

16. The method according to claim 14 or 15, wherein before the sending the random access preamble, the method further comprises:

17. A terminal, comprising:

a sending module, configured to send a random access preamble;

18. The terminal of claim 17, wherein the first set of PUSCH resources comprises any of:

19. The terminal according to claim 17 or 18, characterized in that the terminal further comprises:

20. The terminal of claim 19, wherein the data generation module is specifically configured to perform the following operations:

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

21. The terminal of claim 19, wherein the data generation module is specifically configured to perform the following operations:

determining HARQ information corresponding to the first PUSCH resource;

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

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

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

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

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

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

26. The terminal of claim 17, wherein the data generation module is specifically configured to: and under the condition that a fallback random access response is received and no uplink data exists in the MsgA cache, instructing a multiplexing and assembling entity to generate the first uplink data according to the fallback random access response.

27. The terminal of claim 26, wherein in a case that the logical channel carrying the first uplink data is not a Common Control Channel (CCCH), the first uplink data comprises a cell Radio Network Temporary Identity (RNTI) Medium Access Control (MAC) element (C-RNTI MAC CE).

28. The terminal of claim 26, further comprising a storage module, wherein,

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

29. The terminal of claim 26, wherein the terminal further comprises:

30. A terminal, comprising: memory, processor and program or instructions stored on the memory and executable on the processor, which when executed by the processor implement the steps in the random access processing method according to any of claims 1 to 16.

31. 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 one of claims 1 to 16.