CN110830181A

CN110830181A - Data processing method and terminal equipment

Info

Publication number: CN110830181A
Application number: CN201811124540.5A
Authority: CN
Inventors: 苗金华; 皮埃尔
Original assignee: China Academy of Telecommunications Technology CATT
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2018-08-09
Filing date: 2018-09-26
Publication date: 2020-02-21
Anticipated expiration: 2038-09-26
Also published as: CN110830181B

Abstract

The embodiment of the invention provides a data processing method and terminal equipment, wherein the method comprises the following steps: and when the HARQ process ID is a first value and data exists in the Msg3 buffer or the contention resolution timer is running or feedback that the Msg3 is correctly received is not received, skipping uplink authorization, so that the problem that the configuration authorization MAC PDU covers the Msg3MAC PDU in the HARQ process buffer is solved.

Description

Data processing method and terminal equipment

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a data processing method and terminal equipment.

Background

Introduction to contention random access procedure:

in a fifth Generation mobile communication technology (5th-Generation, 5G) system, Next Radio (NR) defines two random access procedures, i.e., a non-contention random access procedure and a contention random access procedure. Fig. 1 shows a contention random access procedure, and referring to fig. 1, the contention random access procedure includes the following steps:

step 101: the terminal device selects and transmits a preamble.

The terminal device is referred to as a User Equipment (UE).

Step 102: the UE receives a second Message (Message2, Msg2) sent by the base station, i.e. a Random Access Response (RAR), and includes Uplink (UL) grant information in Msg 2.

Step 103: the UE sends a third Message (Message3, Msg3) on the UL grant included in Msg 2. It is noted here that Msg3 is transmitted through a Hybrid Automatic Repeat reQuest (HARQ) process, with the HARQ process ID fixed to 0.

During UL transmission, when the UE receives a UL grant in the RAR and the Msg3 buffer has data, the MAC PDU is obtained from the Msg 3.

Referring to fig. 2, the data packet is simultaneously placed in the HARQ buffer, and the physical layer is instructed to perform a transmission process according to the UL grant information.

Step 104: the UE receives the fourth information (Message4, Msg 4). The random access is considered successful if the UE receives a corresponding message, such as the fourth message received is scrambled by a scrambling code for the UE, or the fourth message received by the UE contains a message that is identical to the first 40 bits of the third message.

After step 103, the UE turns on a contention resolution timer. If the random access is successful in step 104, the UE will turn off the contention resolution timer. If the contention resolution timer is overtime and the UE still cannot receive the fourth message, the UE considers that the random access fails.

2) Configured Grant type 1/Configured Grant type 2 (configuration Grant type 1 and configuration Grant type 2)

Introduction about configuration Grant type 1 and configuration Grant type 2(Configured Grant type 1/Configured Grant type 2):

in NR, some UL resources are pre-configured on the network side, so that some services with high delay requirements (e.g., Ultra Reliable and Low delay Communication (urlcc)) or services with a relatively regular service format (e.g., Voice over Internet Protocol (VoIP) services) are transmitted on the configured UL resources.

The configuration authorization type 1 and the configuration authorization type 2 are two scheduling modes, the same point of the two scheduling modes is that the base station can allocate a periodic resource position in advance, and the UE can send data according to the base station and the allocated resource position. The difference between the above two scheduling modes is:

the configuration authorization type 1 is contents such as a Radio Resource Control (RRC) configuration Resource location, a Modulation Coding Scheme (MCS) mode, HARQ number, a period, and the like, does not require a physical layer activation and deactivation process, and becomes effective after RRC configuration.

The configured grant type 2 is also the RRC configured resource location, HARQ number and period, but does not configure the MCS. Meanwhile, the physical layer needs to send Downlink Control Information (DCI) to activate and deactivate the resource.

The value range of the HARQ ID in the configuration authorization type 1 and the configuration authorization type 2 is 0 to N-1. Wherein, N is the number of HARQ processes which are configured by RRC and are scheduled aiming at the configuration authorization type 1 and the configuration authorization type 2. It can be seen that the HARQ process IDs of configuration grant type 1 and configuration grant type 2 also include 0.

Referring to fig. 3, fig. 3 illustrates a procedure of configuration grant type 1 and configuration grant type 2 data transmission.

Referring to fig. 4, the collision process of the Msg3 retransmission and the configuration grant includes the following moments:

time t 0: the UE receives a Random Access Responses (RAR) at time t0, where the RAR includes UL grant;

time t 1: the UE sends a new transmission of the Msg3, and the corresponding HARQ process identity identification number is 0;

time t 2: and sending a media access control packet data unit (configured grant MAC PDU) on the configuration grant, and if the HARQ Process Identity number (Identity, ID) is also 0(HARQ Process ID, HP ID ═ 0), overwriting the MAC PDU of the original Msg 3.

time t 3: the base station schedules the Msg3 retransmission;

time t 4: when the retransmission Msg3 is sent at time t4, an error is generated because the Msg3 packet is already replaced by a configured grant MAC PDU, that is, the Msg3MAC PDU cannot be acquired during the retransmission of the Msg 3.

In the prior art, when configuration authorization data is sent, if the HARQ process ID is 0, the configuration authorization MAC PDU covers the Msg3MAC PDU in the HARQ process buffer, and the Msg3 retransmission cannot be sent.

Disclosure of Invention

An object of the embodiments of the present invention is to provide a data processing method and a terminal device, so as to solve the problem that an authorized HARQ process covers Msg3 HARQ process data.

In a first aspect, a data processing method is provided, which is applied to a terminal device, and the method includes:

and skipping the uplink grant when the HARQ process ID is a first value and the third message Msg3 has data in a buffer or a contention resolution timer is running or does not receive feedback that the Msg3 is correctly received.

Optionally, the uplink grant is one or more of the following:

configuration authorization;

dynamically scheduling grants;

other uplink grants of non-random access response.

Optionally, the method further comprises:

determining not to acquire MAC PDUs from the MAC multiplexing and aggregation entity when the uplink grant is a configuration grant, or when there is data in the third message Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was correctly received.

Optionally, the method further comprises:

and when the uplink grant is a configuration grant, the HARQ process ID is a first value, and no data exists in the Msg3 buffer or the contention resolution timer does not run or the feedback that the Msg3 is correctly received is received, determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity.

Optionally, before skipping the uplink grant when the uplink grant is a configuration grant, the HARQ process ID is a first value, and there is data in the Msg3 buffer or no feedback that the Msg3 is correctly received is received, the method further includes:

judging whether the uplink authorization is received from the RAR;

when the uplink grant is received from the RAR, judging whether data exist in the Msg3 buffer;

when the Msg3 buffer contains data, acquiring MAC PDU from the Msg3 buffer;

when the uplink grant is not received from the RAR, determining whether the uplink grant is a configuration grant, whether the HARQ process ID is a first value, and whether there is data in the Msg3 buffer or whether the contention resolution timer is running or whether a feedback that Msg3 is correctly received is received.

Optionally, when acquiring the MAC PDU from the Msg3 cache or when acquiring the MAC PDU from the MAC multiplexing and aggregating entity, the method further includes:

and transmitting the MAC PDU and the related information of the uplink authorization to an HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

Optionally, after skipping the uplink grant, the method further includes:

the HARQ process is not cleaned when there is data in the Msg3 buffer, or when the contention resolution timer is running, or when no feedback is received that Msg3 was received correctly.

Optionally, after skipping the uplink grant, the method further includes:

clearing the HARQ process when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was received correctly.

In a second aspect, a terminal device is further provided, including: a processor and a transceiver, wherein,

the processor is configured to: and skipping the uplink grant when the HARQ process ID is a first value and the Msg3 buffer has data or the contention resolution timer is running or does not receive the feedback that the Msg3 is correctly received.

Optionally, the uplink grant is one or more of the following:

configuration authorization;

dynamically scheduling grants;

other uplink grants of non-random access response.

Optionally, the processor is further configured to: when the uplink grant is a configuration grant, or when there is data in the third message Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was correctly received, it is determined not to fetch MAC PDUs from the MAC multiplexing and aggregation entity.

Optionally, the processor is further configured to:

and when the uplink grant is a configuration grant, the HARQ process ID is a first value, and no data exists in the buffer of the third message Msg3 or no contention resolution timer runs or no feedback that the Msg3 is correctly received is received, determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity.

Optionally, the processor is further configured to: judging whether the uplink authorization is received from the RAR; when the uplink grant is received from the RAR, judging whether data exist in the Msg3 buffer; when the Msg3 buffer contains data, acquiring MAC PDU from the Msg3 buffer; when the uplink grant is not received from the RAR, determining whether the uplink grant is a configuration grant, whether the HARQ process ID is a first value, and whether there is data in the Msg3 buffer or whether the contention resolution timer is running or whether a feedback that Msg3 is correctly received is received.

Optionally, the processor is further configured to: and when the MAC PDU is acquired from the Msg3 cache or the MAC PDU is acquired from the MAC multiplexing and aggregation entity, transmitting the MAC PDU and the related information of the uplink authorization to the HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

Optionally, the processor is further configured to: after skipping the uplink grant, when there is data in the Msg3 buffer, or when the contention resolution timer is running, or when no feedback is received that Msg3 was received correctly, the HARQ process is not cleaned.

Optionally, the processor is further configured to: clearing the HARQ process after skipping the uplink grant, when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was correctly received.

In a third aspect, a terminal device is further provided, including: a processor, a memory and a program stored on the memory and executable on the processor, which program, when executed by the processor, carries out the steps of the data processing method according to the first aspect.

In a fourth aspect, there is also provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the data processing method according to the first aspect.

In the embodiment of the invention, when the HARQ process is the first value and data exists in the Msg3 cache or a contention resolution timer runs, uplink authorization is skipped, so that the problem that the HARQ process configured with authorization covers the Msg3 HARQ process data is solved, and the problem that when the configured authorization data is sent, if the HARQ process ID is 0, the configured authorization MAC PDU covers the Msg3MAC PDU in the HARQ process cache, and the Msg3 retransmission cannot be sent is avoided.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a diagram illustrating a contention random access procedure;

FIG. 2 is a schematic diagram of the Msg3 dispatch process;

FIG. 3 is a schematic diagram of data transmission processes of a configuration authorization type 1 and a configuration authorization type 2;

FIG. 4 is a schematic diagram of Msg3 retransmission collision with configuration grant;

FIG. 5 is a block diagram of a wireless communication system according to an embodiment of the present invention;

FIG. 6 is a diagram illustrating a data processing method according to an embodiment of the present invention;

FIG. 7 is a second schematic diagram of a data processing method according to an embodiment of the present invention;

FIG. 8 is a third schematic diagram of a data processing method according to an embodiment of the present invention;

FIG. 9 is a fourth schematic diagram of a data processing method according to an embodiment of the present invention;

FIG. 10 is a fifth exemplary diagram illustrating a data processing method according to the present invention;

FIG. 11 is a sixth schematic view of a data processing method according to an embodiment of the present invention;

FIG. 12 is a seventh schematic diagram illustrating a data processing method according to an embodiment of the present invention;

FIG. 13 is an eighth schematic diagram of a data processing method according to an embodiment of the invention;

FIG. 14 is a ninth illustration of a data processing method according to an embodiment of the invention;

FIG. 15 is a tenth schematic diagram of a data processing method according to an embodiment of the present invention;

FIG. 16 is an eleventh schematic diagram illustrating a data processing method according to an embodiment of the present invention;

FIG. 17 is a twelfth schematic diagram illustrating a data processing method according to an embodiment of the invention;

FIG. 18 is a thirteen schematic diagrams of a data processing method according to an embodiment of the present invention;

FIG. 19 is a fourteenth embodiment of a data processing method according to the present invention;

FIG. 20 is a fifteen-level diagram illustrating a data processing method according to an embodiment of the present invention;

FIG. 21 is a sixteen schematic diagrams illustrating a data processing method according to an embodiment of the present invention;

fig. 22 is one of schematic diagrams of a terminal device according to an embodiment of the present invention;

fig. 23 is a second schematic diagram of a terminal device according to an embodiment of the invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.

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 invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention 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.

The techniques described herein are not limited to Long Time Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, and may also be used for various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems may implement Radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. UTRA includes Wideband CDMA (Wideband code division Multiple Access, WCDMA) and other CDMA variants. TDMA systems may implement radio technologies such as Global System for Mobile communications (GSM). The OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved-UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g., LTE-A) are new UMTS releases that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation partnership project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies.

Embodiments of the present invention are described below with reference to the accompanying drawings. The data processing method and the terminal equipment provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a fifth-generation mobile communication technology (5G) system, an Evolved Long Term Evolution (lte) system, or a subsequent Evolved communication system.

Fig. 5 is a block diagram of a wireless communication system according to an embodiment of the present invention. As shown in fig. 5, the wireless communication system may include: network device 50 and a terminal device, denoted UE51, UE51 may communicate (transmit signaling or transmit data) with network device 50. In practical applications, the connections between the above devices may be wireless connections, and fig. 5 illustrates the connections between the devices by solid lines for convenience and intuition.

It should be noted that the communication system may include a plurality of UEs 51, and the network device 50 may communicate with a plurality of UEs 51.

The network device 50 in the communication system may be a base station, which may be a commonly used base station, an evolved node base (eNB), or a network device in a 5G system (e.g., a next generation base station (gNB) or a Transmission and Reception Point (TRP)).

The UE51 provided in the embodiment of the present invention may be a Mobile phone, a tablet pc, a notebook pc, an Ultra-Mobile Personal Computer (UMPC), a netbook, a Personal Digital Assistant (PDA), or the like.

Fig. 6 is a schematic diagram of a data processing method according to an embodiment of the present invention, and referring to fig. 6, an execution subject of the method is a terminal device, and the specific steps are as follows:

step 601: when the HARQ process ID is the first value and there is data in the Msg3 buffer or a Contention Resolution timer (Contention Resolution timer) is running or no feedback is received that Msg3 was correctly received, the uplink grant is skipped.

In this embodiment of the present invention, optionally, the uplink grant is one or more of the following: configuration authorization; dynamically scheduling grants; other uplink grants of non-random access response.

It is understood that skipping (skip) upstream grants may also be referred to as not performing upstream grants.

It should be noted that the HARQ process is a process associated with the configuration grant, and the association relationship between the HARQ process and the configuration grant may be one-to-one, many-to-one, one-to-many, or many-to-many.

It should be noted that the contention resolution timer is running, which means that the contention resolution timer is not timed out or opened. The contention resolution timer not running means that the contention resolution timer times out or is not open.

The multiplexing and aggregation entity (multiplexing and aggregation entity) refers to an entity used by the MAC layer to generate the MAC PDU.

In an embodiment of the invention, it is determined not to fetch MAC PDUs from the MAC multiplexing and aggregation entity when the upstream grant is a configuration grant or when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was received correctly. Wherein the first value may be 0.

In the embodiment of the invention, when the uplink grant is the configuration grant, the HARQ process ID is the first value, and data exists in the Msg3 buffer or the contention resolution timer is running or does not receive the feedback that Msg3 is correctly received, the uplink grant is skipped, so that the problem that the HARQ process configured with the grant covers the Msg3 HARQ process data is solved, and the problem that the HARQ process configured with the grant covers the Msg3 HARQ process and cannot send the Msg3 retransmission if the HARQ process ID is 0 when the configuration grant data is sent is avoided.

Fig. 7 is a schematic diagram of another data processing method according to an embodiment of the present invention, and referring to fig. 7, an execution main body of the method is a terminal device, and the method includes the following specific steps:

step 701: judging whether the uplink authorization is received from the RAR; if yes, go to step 702; otherwise, go to step 704;

Step 702: judging whether data exist in the Msg3 cache; if yes, go to step 703; otherwise, go to step 704;

step 703: acquiring the MAC PDU from the Msg3 buffer, and then executing step 708;

it is understood that when the upstream grant is received from the RAR and there is data in the Msg3 buffer, the MAC PDU is retrieved from the Msg3 buffer.

Step 704: and judging whether the uplink grant is a configured (configured) grant, whether the HARQ process ID is a first value, and whether data exists in the Msg3 cache or whether a contention resolution timer is running or whether correct feedback of the Msg3 is received.

Wherein, when the uplink grant is a configuration grant, the HARQ process ID is a first value, and there is data in the Msg3 buffer or the contention resolution timer is running or no feedback that the Msg3 is correctly received is received, execute step 705;

Wherein step 707 is performed when the upstream grant is a configuration grant, or when there is data in the Msg3 cache, or when a contention resolution timer is running, or when there is no feedback correctly received by Msg 3.

Step 705: when the uplink grant is a configuration grant, the HARQ process ID is a first value, and there is data in the Msg3 buffer or no feedback that the Msg3 is correctly received is received, skip the uplink grant, and then execute

step

709 or 710.

Step 706: when the uplink grant is a configuration grant, the HARQ process ID is a first value, and there is no data in the Msg3 buffer or the contention resolution timer is not running or a feedback that Msg3 is correctly received is received, it is determined to obtain the MAC PDU from the multiplexing aggregation entity, and then step 708 is performed.

Step 707: determining not to fetch MAC PDUs from the MAC multiplexing and aggregation entity when the upstream grant is a configuration grant, or when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was received correctly.

Step 708: and transmitting the MAC PDU and the related information of the uplink authorization to the HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

Step 709: HARQ processes are not cleaned when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was received correctly.

Step 710: the HARQ process is cleared when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was received correctly.

In the embodiment of the invention, when the uplink grant is the configuration grant, the identification number of the HARQ process is the first value (for example, 0), and data exists in the Msg3 buffer or the contention resolution timer is running or the feedback that the Msg3 is correctly received is not received, the uplink grant is skipped, the problem that the HARQ process 0 of the configuration grant covers the Msg3 HARQ process is solved, and the problem that when the configuration grant data is sent, if the HARQ process ID is 0, the configuration grant MAC PDU covers the Msg3MAC PDU in the HARQ process buffer, and the Msg3 retransmission cannot be sent is avoided.

Referring to fig. 8 and fig. 9, an embodiment of the present invention provides a schematic diagram of another data processing method, where an execution subject of the method is a terminal device, and the method includes the following specific steps:

step 901: receiving an uplink authorization;

wherein, the process of the current uplink authorization is a newly transmitted process; the uplink grant may be any one of a configuration grant and a grant for dynamic scheduling of a Physical Downlink Control Channel (PDCCH) received by the RAR;

step 902: judging whether the uplink authorization is received from the RAR; if yes, go to step 903; otherwise, go to step 905;

step 903: judging whether data exist in the Msg3 cache; if yes, go to step 904; otherwise, go to step 905;

it can be understood that the determination of whether there is data in the Msg3 buffer is to determine whether the Msg3 buffer is empty, and if the Msg3 buffer is not empty, there is a MAC PDU in the Msg3 buffer.

Step 904: acquiring MAC PDU from the Msg 3;

step 905: judging whether the uplink authorization is configuration authorization, whether the HARQ process ID is 0 and whether MAC PDU exists in the Msg 3;

when the uplink grant is the configuration grant, the HARQ process ID is 0, and there is a MAC PDU in the Msg3, execute step 906; when the uplink grant is a configuration grant, the HARQ process ID is 0, and there is no MAC PDU in the Msg3 buffer, execute step 907;

step 906: skipping the uplink grant;

step 907: determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity.

It can be understood that when the uplink grant is received through the RAR and there is a MAC PDU in the current Msg3 buffer, the MAC PDU is obtained from the Msg3 buffer; otherwise, judging whether the uplink authorization is the configuration authorization, whether the HARQ process ID is 0 and whether data exists in the Msg3 cache; and when the HARQ process is 0 and the current Msg3 buffer has the MAC PDU, acquiring the MAC PDU from the MAC multiplexing and aggregation entity. Otherwise, it is determined that the MAC PDU will be acquired from the multiplexing and aggregation entity.

In this embodiment of the present invention, when determining not to acquire a MAC PDU from the MAC multiplexing and aggregating entity, or when determining to acquire a MAC PDU from the Msg3 or the MAC multiplexing and aggregating entity, the method flow shown in fig. 9 may further include the steps shown in fig. 10, where the specific steps are as follows:

step 1001: judging whether the MAC PDU is acquired; if yes, go to step 1002; otherwise, go to step 1003;

the MAC PDU acquisition may refer to data acquired from the Msg3 buffer or data acquired from the MAC multiplexing aggregation entity.

Step 1002: submitting the MAC PDU and the UL authorization information to an HARQ entity;

step 1003: judging whether the Msg3 cache has the MAC PDU or not; if yes, go to step 1004; otherwise, go to step 1005;

step 1004: not cleaning the HARQ cache and corresponding HARQ process;

when the MAC PDU is not acquired and the Msg3 cache is not empty, namely the MAC PDU exists in the Msg3 cache, the HARQ cache and the corresponding HARQ process are not cleaned;

step 1005: and cleaning the HARQ buffer and the corresponding HARQ process.

It can be understood that when the MAC PDU cannot be acquired and the Msg3 buffer is not empty, that is, there is a MAC PDU in the Msg3 buffer, the HARQ buffer and the corresponding HARQ process are not cleaned; and when the MAC PDU cannot be acquired but the Msg3 buffer is empty, cleaning the HARQ buffer and the corresponding HARQ process.

It can be understood that clearing the HARQ process means clearing data in the HARQ process, and turning off a timer associated with the HARQ process.

Referring to fig. 11 and 12, an embodiment of the present invention provides a schematic diagram of another data processing method, where an execution subject of the method is a terminal device, and the method includes the following specific steps:

step 1101: receiving an uplink authorization;

the process of the current uplink authorization is a newly transmitted process, and the uplink authorization can be any one of the authorization received by the RAR, the configuration authorization and the authorization dynamically scheduled by the PDCCH;

step 1102: judging whether the uplink authorization is received from the RAR; if yes, go to step 1103; otherwise, go to step 1105;

step 1103: judging whether data exist in the Msg3 cache; if yes, go to step 1104; otherwise, go to step 1105;

Step 1104: acquiring MAC PDU from the Msg 3;

step 1105: judging whether the uplink authorization is the configuration authorization, whether the HARQ process ID is 0 and whether a contention resolution timer is running; if the uplink grant is a configuration grant, the HARQ process ID is 0, and the contention resolution timer is running, go to step 1106; if the uplink grant is the configuration grant, the HARQ process ID is 0, and the contention resolution timer is not running, step 1107 is executed;

step 1106: skipping the uplink grant;

step 1107: and acquiring the MAC PDU from the MAC multiplexing and aggregation entity.

It can be understood that when the uplink grant is received through the RAR and there is a MAC PDU in the current Msg3 buffer, it is determined to obtain the MAC PDU from the Msg3 buffer; otherwise, if the uplink authorization is the configuration authorization, judging whether the HARQ process ID is 0 and whether the contention resolution timer runs; and when the HARQ process ID is 0 and the contention resolution timer is not running, determining to acquire data from the MAC multiplexing entity. If the uplink grant is the configuration grant, the HARQ ID process ID is 0, and the contention resolution timer is running, the uplink grant is skipped.

When determining not to acquire the MAC PDU from the MAC multiplexing and aggregating entity, or when determining to acquire the MAC PDU from the MAC multiplexing and aggregating entity, the method flow shown in fig. 11 may further include the steps shown in fig. 13, and the specific steps are as follows:

step 1301: judging whether the MAC PDU is acquired; if yes, go to step 1302; otherwise, go to step 1303;

Step 1302: submitting the MAC PDU and the UL authorization information to an HARQ entity;

step 1303: judging whether the competition resolving timer is not operated; if the contention resolution timer is not running, go to step 1304; if the contention resolution timer is running, go to step 1305;

it should be noted that the contention resolution timer is not running, which means that the contention resolution timer is timed out or not opened.

Step 1304: cleaning an HARQ cache and a corresponding HARQ process;

step 1305: the HARQ buffer and corresponding HARQ process are not cleaned.

It can be understood that when the MAC PDU cannot be acquired and the contention resolution timer is running, the HARQ buffer and the corresponding HARQ process are not cleaned; and when the MAC PDU cannot be acquired but the contention resolution timer does not run, cleaning the HARQ buffer and the corresponding HARQ process.

Fig. 14 is a schematic diagram of a data processing method according to an embodiment of the present invention, and referring to fig. 14, an execution subject of the method is a terminal device, and the method includes the following specific steps:

step 1401: when the uplink grant is a dynamic scheduling grant, where the dynamic scheduling grant is a grant manner of a Physical Downlink Control Channel (PDCCH) dynamic scheduling, the HARQ process ID is a first value, and a Contention Resolution timer (Contention Resolution timer) is running or does not receive a feedback that the Msg3 is correctly received, the uplink grant is skipped.

It should be noted that the HARQ process is a process associated with the dynamic scheduling grant, and the association relationship between the HARQ process and the dynamic scheduling grant may be one-to-one, many-to-one, one-to-many, or many-to-many.

In the embodiment of the present invention, when the uplink grant is a dynamic scheduling grant, when a contention resolution timer is running, or when feedback that Msg3 is correctly received is not received, it is determined not to acquire the MAC PDU from the MAC multiplexing and aggregation entity. Wherein the first value may be 0.

In the embodiment of the invention, when the uplink grant is the dynamic scheduling grant, the ID of the HARQ process is the first value, and the contention resolution timer is running or does not receive the feedback that the Msg3 is correctly received, the uplink grant is skipped, so that the problem that the HARQ process for sending the dynamic uplink data covers the Msg3 HARQ process data is solved, and the problem that the HARQ process for sending the dynamic scheduling grant covers the Msg3 HARQ process and cannot send the Msg3 retransmission when the uplink dynamic scheduling data is sent is avoided.

Fig. 15 is a schematic diagram of another data processing method according to an embodiment of the present invention, and referring to fig. 15, an execution main body of the method is a terminal device, and the method includes the following specific steps:

step 1501: judging whether the uplink authorization is received from the RAR; if yes, go to step 1502; otherwise, go to step 1504;

step 1502: judging whether data exist in the Msg3 cache; if yes, go to step 1503; otherwise, go to step 1504;

step 1503: obtaining the MAC PDU from the Msg3 buffer, and then performing step 1508;

Step 1504: and judging whether the uplink authorization is a dynamic scheduling authorization, whether the HARQ process ID is a first value, and whether data or a contention resolution timer is running or whether correct feedback of the Msg3 is received in the Msg3 cache.

Wherein, when the uplink grant is a dynamic scheduling grant, the HARQ process ID is a first value, and the Msg3 buffer has data or the contention resolution timer is running or does not receive the feedback that the Msg3 is correctly received, step 1505 is executed;

Wherein step 1507 is performed when the upstream grant is a dynamic scheduling grant, or when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when there is no feedback correctly received by Msg 3.

Step 1505: when the uplink grant is a dynamic scheduling grant, the HARQ process ID is a first value, and there is data in the Msg3 buffer or no feedback that the Msg3 is correctly received is received, the uplink grant is skipped, and then step 1509 or 1510 is performed.

Step 1506: when the uplink grant is a dynamic scheduling grant, the HARQ process ID is a first value, and there is no data in the Msg3 buffer or the contention resolution timer is not running or a feedback that Msg3 is correctly received is received, it is determined to obtain the MAC PDU from the MAC multiplexing aggregation entity, and then step 1508 is performed.

Step 1507: determining not to fetch MAC PDUs from the MAC multiplexing and aggregation entity when the uplink grant is a dynamic scheduling grant, or when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was correctly received.

Step 1508: and transmitting the MAC PDU and the related information of the uplink authorization to the HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

Step 1509: HARQ processes are not cleaned when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was received correctly.

Step 1510: the HARQ process is cleared when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was received correctly.

In the embodiment of the invention, when the uplink grant is a dynamic scheduling grant, the identification number of the HARQ process is a first value (for example, 0), and data exists in the Msg3 cache or a contention resolution timer is running or feedback that Msg3 is correctly received is not received, the uplink grant is skipped, so that the problem that the HARQ process 0 of the dynamic scheduling grant covers the Msg3 HARQ process is solved, and the problem that when the dynamic scheduling grant data is sent, if the ID of the HARQ process is 0, the dynamic scheduling grant MAC PDU covers the Msg3MAC PDU in the HARQ process cache, and the Msg3 retransmission cannot be sent is avoided.

Referring to fig. 16 and fig. 17, an embodiment of the present invention provides a schematic diagram of another data processing method, where an execution subject of the method is a terminal device, and the method includes the following specific steps:

step 1701: receiving an uplink authorization;

step 1702: judging whether the uplink authorization is received from the RAR; if yes, go to step 1703; otherwise, go to step 1705;

step 1703: judging whether data exist in the Msg3 cache; if yes, go to step 1604; otherwise, go to step 1705;

Step 1704: acquiring MAC PDU from the Msg 3;

step 1705: judging whether the uplink authorization is a dynamic scheduling authorization, whether the HARQ process ID is 0 and whether the Msg3 has an MAC PDU;

when the uplink grant is the dynamic scheduling grant, the HARQ process ID is 0, and there is a MAC PDU in the Msg3, execute step 1706; when the uplink grant is a dynamic scheduling grant, the HARQ process ID is 0, and there is no MAC PDU in the Msg3 buffer, execute step 1707;

step 1706: skipping the uplink grant;

step 1707: determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity.

It can be understood that when the uplink grant is received through the RAR and there is a MAC PDU in the current Msg3 buffer, the MAC PDU is obtained from the Msg3 buffer; otherwise, judging whether the uplink authorization is a dynamic scheduling authorization, whether the HARQ process ID is 0, and whether data exists in the Msg3 cache; and when the HARQ process is 0 and the current Msg3 buffer has the MAC PDU, acquiring the MAC PDU from the MAC multiplexing and aggregation entity. Otherwise, it is determined that the MAC PDU will be acquired from the multiplexing and aggregation entity.

In this embodiment of the present invention, when determining not to acquire a MAC PDU from the MAC multiplexing and aggregating entity, or when determining to acquire a MAC PDU from the Msg3 or the MAC multiplexing and aggregating entity, the method flow shown in fig. 17 may further include the steps shown in fig. 18, where the specific steps are as follows:

step 1801: judging whether the MAC PDU is acquired; if yes, go to step 1802; otherwise, go to step 1803;

Step 1802: submitting the MAC PDU and the UL authorization information to an HARQ entity;

step 1803: judging whether the Msg3 cache has the MAC PDU or not; if yes, go to step 2004; otherwise, go to step 1805;

step 1804: not cleaning the HARQ cache and corresponding HARQ process;

step 1805: and cleaning the HARQ buffer and the corresponding HARQ process.

Referring to fig. 19 and fig. 20, an embodiment of the present invention provides a schematic diagram of another data processing method, where an execution subject of the method is a terminal device, and the method includes the following specific steps:

step 2001: receiving an uplink authorization;

step 2002: judging whether the uplink authorization is received from the RAR; if yes, go to step 2003; otherwise, go to step 2005;

step 2003: judging whether data exist in the Msg3 cache; if yes, go to step 2004; otherwise, go to step 2005;

Step 2004: acquiring MAC PDU from the Msg 3;

step 2005: judging whether the uplink authorization is a dynamic scheduling authorization, whether the HARQ process ID is 0 and whether a contention resolution timer is running; if the uplink grant is a dynamic scheduling grant, the HARQ process ID is 0, and the contention resolution timer is running, execute step 2006; otherwise, go to step 2007;

step 2006: skipping the uplink grant;

step 2007: and acquiring the MAC PDU from the MAC multiplexing and aggregation entity.

It can be understood that when the uplink grant is received through the RAR and there is a MAC PDU in the current Msg3 buffer, it is determined to obtain the MAC PDU from the Msg3 buffer; otherwise, if the uplink authorization is the dynamic scheduling authorization, judging whether the HARQ process ID is 0 and whether the contention resolution timer runs; and when the HARQ process ID is 0 and the contention resolution timer is not operated, determining to acquire the MAC PDU from the MAC multiplexing entity. The HARQ ID process ID is 0 and the contention resolution timer is running, skipping the uplink grant.

When determining not to acquire the MAC PDU from the MAC multiplexing and aggregating entity, or when determining to acquire the MAC PDU from the MAC multiplexing and aggregating entity, the method flow shown in fig. 20 may further include the steps shown in fig. 21, and the specific steps are as follows:

step 2101: judging whether the MAC PDU is acquired; if yes, go to step 2102; otherwise, go to step 2103;

Step 2102: submitting the MAC PDU and the UL authorization information to an HARQ entity;

step 2103: judging whether the competition resolving timer is not operated; if the contention resolution timer is not running, go to step 2104; if the contention resolution timer is running, go to step 2105;

Step 2104: cleaning an HARQ cache and a corresponding HARQ process;

step 2105: the HARQ buffer and corresponding HARQ process are not cleaned.

The embodiment of the invention also provides the terminal equipment, and as the principle of solving the problems of the terminal equipment is similar to the data processing method in the embodiment of the invention, the implementation of the terminal equipment can refer to the implementation of the method, and repeated parts are not repeated.

Referring to fig. 22, an embodiment of the present invention further provides a terminal device, where the terminal device 2200 includes: a processor 2201 and a transceiver 2202, wherein,

the transceiver 2202 may be a plurality of elements including a transmitter and a receiver providing a means for communicating with various other apparatus over a transmission medium;

the processor 2201 is configured to: and skipping the uplink grant when the HARQ process ID is a first value and the third message Msg3 has data in a buffer or a contention resolution timer is running or does not receive feedback that the Msg3 is correctly received.

Optionally, the uplink grant is one or more of the following:

configuration authorization;

dynamically scheduling grants;

other uplink grants of non-random access response.

Optionally, the processor 2201 is further configured to: determining not to fetch MAC PDUs from the MAC multiplexing and aggregation entity when the upstream grant is a configuration grant, or when there is data in the Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was received correctly.

Optionally, the processor is further configured to: and when the uplink grant is a configuration grant, the HARQ process ID is a first value, and no data exists in the buffer of the third message Msg3 or the contention resolution timer does not run or the feedback that the Msg3 is correctly received is received, determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity. Optionally, the processor 2201 is further configured to: judging whether the uplink authorization is received from the RAR; when the uplink grant is received from the RAR, judging whether data exist in the Msg3 buffer; when the Msg3 buffer contains data, acquiring MAC PDU from the Msg3 buffer; when the uplink grant is not received from the RAR, determining whether the uplink grant is a configuration grant, whether the HARQ process ID is a first value, and whether there is data in the Msg3 buffer or whether the contention resolution timer is running or whether a feedback that Msg3 is correctly received is received.

Optionally, the processor 2201 is further configured to: and when the MAC PDU is acquired from the Msg3 cache or the MAC PDU is acquired from a MAC multiplexing and aggregation entity, transmitting the MAC PDU and the related information of the uplink authorization to an HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

Optionally, the processor 2201 is further configured to: after skipping the uplink grant, when there is data in the Msg3 buffer, or when the contention resolution timer is running, or when no feedback is received that Msg3 was received correctly, the HARQ process is not cleaned.

Optionally, the processor 2201 is further configured to: clearing the HARQ process after skipping the uplink grant, when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was correctly received.

It should be noted that the terminal device provided in the embodiment of the present invention can implement each process in the method embodiments of fig. 6 to fig. 21, and the implementation principle and the technical effect are similar, which are not described herein again.

As shown in fig. 23, the terminal device 2300 shown in fig. 23 includes: at least one processor 2301, memory 2302, at least one network interface 2304 and a user interface 2303. The various components in the end device 2300 are coupled together by a bus system 2305. It is understood that the bus system 2305 is used to enable connected communication between these components. The bus system 2305 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are designated as bus system 2305 in fig. 23.

The user interface 2303 may include, among other things, a display, a keyboard, or a pointing device (e.g., a mouse, trackball, touch pad, or touch screen, among others.

It is to be appreciated that memory 2302 can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory in embodiments of the present invention. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double data rate Synchronous Dynamic random access memory (ddr DRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 2302 of the systems and methods described in connection with embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 2302 holds the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof: an operating system 23021 and application programs 23022.

The operating system 23021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 23022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. A program for implementing the methods of embodiments of the present invention may be included in the application 23022.

In one embodiment of the present invention, each step in the data processing method is implemented by calling a program or an instruction stored in the memory 2302, which may be specifically a program or an instruction stored in the application 23022, and executing the program or the instruction.

The terminal device provided by the embodiment of the present invention may execute the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware or in software instructions executed by a processor. The software instructions may consist of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable hard disk, a compact disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a core network interface device. Of course, the processor and the storage medium may reside as discrete components in a core network interface device.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.

Claims

1. A data processing method is applied to terminal equipment, and is characterized in that the method comprises the following steps:

and skipping the uplink grant when the hybrid automatic repeat request HARQ process identification number ID is a first value and the third message Msg3 cache has data or the contention resolution timer is running or does not receive the feedback that the Msg3 is correctly received.

2. The method of claim 1,

the uplink grant is one or more of the following:

configuration authorization;

dynamically scheduling grants;

other uplink grants of non-random access response.

3. The method of claim 1, further comprising:

4. The method of claim 1, further comprising:

5. The method of claim 1, wherein before skipping the uplink grant when the HARQ process ID is a first value and there is data in the Msg3 buffer or no feedback is received that the Msg3 is correctly received, the method further comprises:

judging whether the uplink authorization is received from the RAR;

when the Msg3 buffer contains data, acquiring MAC PDU from the Msg3 buffer;

6. The method according to claim 4 or 5, wherein when the MAC PDU is obtained from the Msg3 cache or when the MAC PDU is obtained from a MAC multiplexing and aggregation entity, the method further comprises:

7. The method of claim 1, wherein after skipping an uplink grant, the method further comprises:

8. The method of claim 1, wherein after skipping an uplink grant, the method further comprises:

9. A terminal device, comprising: a processor and a transceiver, wherein,

10. The terminal device according to claim 9, wherein the uplink grant is one or more of:

configuration authorization;

dynamically scheduling grants;

other uplink grants of non-random access response.

11. The terminal device of claim 9, wherein the processor is further configured to: when the uplink grant is a configuration grant, or when there is data in the third message Msg3 buffer, or when a contention resolution timer is running, or when no feedback is received that Msg3 was correctly received, it is determined not to fetch MAC PDUs from the MAC multiplexing and aggregation entity.

12. The terminal device of claim 9, wherein the processor is further configured to: and when the uplink grant is a configuration grant, the HARQ process ID is a first value, and no data exists in the buffer of the third message Msg3 or no contention resolution timer runs or no feedback that the Msg3 is correctly received is received, determining to acquire the MAC PDU from the MAC multiplexing and aggregation entity.

13. The terminal device of claim 9, wherein the processor is further configured to: judging whether the uplink authorization is received from the RAR; when the uplink grant is received from the RAR, judging whether data exist in the Msg3 buffer; when the Msg3 buffer contains data, acquiring MAC PDU from the Msg3 buffer; when the uplink grant is not received from the RAR, determining whether the uplink grant is a configuration grant, whether the HARQ process ID is a first value, and whether there is data in the Msg3 buffer or whether the contention resolution timer is running or whether a feedback that Msg3 is correctly received is received.

14. The terminal device of claim 12 or 13, wherein the processor is further configured to: and when the MAC PDU is acquired from the Msg3 cache or the MAC PDU is acquired from the MAC multiplexing and aggregation entity, transmitting the MAC PDU and the related information of the uplink authorization to the HARQ process, and executing the transmission of the MAC PDU through the HARQ process.

15. The terminal device of claim 9, wherein the processor is further configured to: after skipping the uplink grant, when there is data in the Msg3 buffer, or when the contention resolution timer is running, or when no feedback is received that Msg3 was received correctly, the HARQ process is not cleaned.

16. The terminal device of claim 9, wherein the processor is further configured to: clearing the HARQ process after skipping the uplink grant, when there is no data in the Msg3 buffer, or when the contention resolution timer is not running, or when feedback is received that Msg3 was correctly received.

17. A terminal device, comprising: processor, memory and program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the data processing method according to any of claims 1 to 8.

18. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the data processing method according to any one of claims 1 to 8.