Method performed by a user equipment and the user equipment

Abstract

The present disclosure provides a method performed by a user equipment and the user equipment. The method performed by the user equipment includes: when a media access control (MAC) entity is configured with a configured uplink grant and the configured uplink grant is activated, determining whether the MAC entity is configured to transmit a MAC protocol data unit (MAC PDU) obtained for a low-priority configured uplink grant by using the configured uplink grant; and when the MAC entity is configured to transmit the MAC PDU by using the configured uplink grant, delivering the configured uplink grant to a hybrid automatic repeat request (HARQ) entity. Thereby, problems involved in transmitting low-priority MAC PDUs stored in an HARQ process buffer can be solved, and thus the communication efficiency and reliability of a wireless communication system can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies. More specifically, the present disclosure relates to a method performed by a user equipment and the user equipment. Background Art

[0002] In March 2019, a work item supporting NR Industrial Internet of Things was approved at the 83rd plenary session of the 3rd Generation Partnership Project (3GPP) RAN (see non-patent document: RP-190728: New WID: Support of NR Industrial Internet of Things (IoT)). In industrial application scenarios, a user equipment (UE) needs to simultaneously process data traffic flows from different applications or devices. Therefore, it is necessary to consider priority handling and / or multiplexing when uplink / downlink data channels and control channels conflict within the UE and / or between UEs, and the handling of resource conflicts between dynamic grant (DG) and configured grant (CG) and between two or more configured grants (i.e., conflicts between data channels or between uplink shared channels UL-SCH). Accordingly, one of the purposes of this work item is to enhance the resolution of resource conflicts between dynamic grants and configured grants and between two or more configured grants. If the media access control (MAC) processes grant priorities, the 3GPP Working Group 2 (RAN2) needs to define a physical uplink shared channel (PUSCH) grant priority handling mechanism based on logical channel (LCH) priorities and logical channel priority (LCP) limits.

[0003] The present disclosure solves the problems involved in transmitting low-priority MAC PDUs stored in the HARQ process buffer. Summary of the Invention

[0004] To solve the above problems in the prior art, the present disclosure provides a method performed by a user equipment and the user equipment, which can solve the problems involved in transmitting low-priority MAC PDUs stored in the HARQ process buffer, thereby improving the communication efficiency and reliability of a wireless communication system.

[0005] According to a first aspect of the present disclosure, there is provided a method performed by a user equipment, including: when a Media Access Control (MAC) entity is configured with a configured uplink grant and the configured uplink grant is activated, determining whether the MAC entity is configured to transmit a MAC Protocol Data Unit (MAC PDU) obtained for a low-priority configured uplink grant by using the configured uplink grant; when the MAC entity is configured to transmit the MAC PDU by using the configured uplink grant, delivering the configured uplink grant to a Hybrid Automatic Repeat reQuest (HARQ) entity.

[0006] In the above method, it may be that when the MAC entity is configured with a configured uplink grant and the configured uplink grant is activated, determining whether a first condition is satisfied, where the first condition includes at least one of the following conditions: the MAC entity is configured with lch-basedPrioritization; the Physical Uplink Shared Channel (PUSCH) duration of the configured uplink grant does not overlap with the PUSCH duration of the uplink grant for the serving cell received on a Physical Downlink Control Channel (PDCCH) or in a random access response.

[0007] In the above method, it may be that when the first condition is satisfied, setting the HARQ process number to the HARQ process number associated with the PUSCH duration of the configured uplink grant, and then determining whether a second condition is satisfied, where the second condition includes at least one of the following conditions: the timer configuredGrantTimer for the corresponding HARQ process is not running; the MAC entity is configured with autonomousReTx; the MAC entity is configured with lch-basedPeioritization; the MAC entity is configured with autonomousReTx, the previous configured uplink grant for the corresponding HARQ process is a low-priority configured uplink grant, and a MAC PDU has been obtained for the corresponding HARQ process.

[0008] In the above method, it may be that when the second condition is satisfied, performing at least one of the following operations: considering that the New Data Indicator (NDI) bit for the corresponding HARQ process is flipped; delivering the configured uplink grant and the associated HARQ information to the HARQ entity; and considering that a MAC PDU has been obtained for the configured uplink grant only when the MAC entity is configured with autonomousReTx, the previous configured uplink grant for the corresponding HARQ process is a low-priority configured uplink grant, and a MAC PDU has been obtained for the corresponding HARQ process among the second conditions is satisfied.

[0009] In the above method, it may be that when the configured uplink grant is a low-priority configured uplink grant and a MAC PDU has been obtained for this low-priority configured uplink grant, the timer configuredGrantTimer of the corresponding HARQ process is stopped.

[0010] In the above method, it may be that when the MAC entity is configured with lch-basedPrioritization, for each uplink grant for a cell radio network temporary identifier C-RNTI or a configured scheduling radio network temporary identifier CS-RNTI, when the physical uplink shared channel PUSCH duration of this uplink grant does not overlap with the PUSCH duration of a configured uplink grant with a higher priority than this uplink grant, and the PUSCH duration of this uplink grant does not overlap with the physical uplink control channel PUCCH resources for a scheduling request SR transmission triggered by a logical channel with a higher priority than this uplink grant, at least one of the following operations is performed: consider the uplink grant as a high-priority uplink grant; when the uplink grant is a high-priority uplink grant for a CS-RNTI, consider that the MAC PDU obtained for the uplink grant or the MAC PDU stored in the HARQ buffer of the HARQ process identified for the uplink grant has been transmitted; consider other overlapping uplink grants as low-priority uplink grants; when the low-priority uplink grant is an uplink grant for a C-RNTI, the HARQ process identified for the uplink grant is a HARQ process configured for a configured uplink grant, and a MAC PDU has not been obtained for the low-priority uplink grant, stop the timer configuredGrantTimer of the corresponding HARQ process; when the low-priority uplink grant is a configured uplink grant and the MAC entity is configured with autonomouResTx, stop the timer configuredGrantTimer of the HARQ process corresponding to the low-priority uplink grant and / or consider that the MAC PDU obtained for the uplink grant or the MAC PDU corresponding to the uplink grant has not been transmitted.

[0011] In the above method, it may be that when the MAC entity is configured with lch-basedPrioritization, for each configured uplink grant, when the physical uplink shared channel (PUSCH) duration of the uplink grant does not overlap with the PUSCH duration of another configured uplink grant with a higher priority than the uplink grant, the PUSCH duration of the uplink grant does not overlap with the PUSCH duration of an uplink grant for a cell radio network temporary identity (C-RNTI) or a configured scheduling radio network temporary identity (CS-RNTI) with a priority higher than the uplink grant, and the PUSCH duration of the uplink grant does not overlap with the physical uplink control channel (PUCCH) resource for a scheduling request (SR) transmission triggered by a logical channel with a higher priority than the uplink grant, at least one of the following operations is performed: consider the uplink grant as a high-priority uplink grant; when the uplink grant is a high-priority uplink grant, consider that the MAC PDU obtained for the uplink grant or the MAC PDU corresponding to the uplink grant has been transmitted; consider other overlapping uplink grants as low-priority uplink grants; when the low-priority uplink grant is a configured uplink grant and the MAC entity is configured with autonomousReTx, stop the timer configuredGrantTimer of the HARQ process corresponding to the low-priority uplink grant, and / or consider that the MAC PDU obtained for the low-priority uplink grant or the MAC PDU corresponding to the low-priority uplink grant has not been transmitted.

[0012] In the above method, it may be that when a MAC PDU is obtained for a low-priority uplink grant, the timer configuredGrantTimer of the HARQ process corresponding to the configured uplink grant is not started.

[0013] In the above method, it may be that when a MAC PDU for transmission is obtained, the HARQ entity delivers the MAC PDU, the corresponding uplink grant, and the associated HARQ information to the identified HARQ process. When the uplink grant is not a configured uplink grant, or is not for a configured scheduling radio network temporary identity (CS-RNTI), or is a high-priority configured uplink grant, or is a high-priority uplink grant for a CS-RNTI, the following operations are performed: instruct the identified HARQ process to trigger a new transmission; when the uplink grant is for a CS-RNTI, or is a configured uplink grant, or is an uplink grant for a cell radio network temporary identity (C-RNTI) and the identified HARQ process is the HARQ process configured for the configured uplink grant, start or restart the configuredGrantTimer of the corresponding HARQ process when transmission is performed.

[0014] According to a second aspect of the present disclosure, there is provided a user equipment, including: a processor; and a memory storing instructions; wherein, when the instructions are run by the processor, the above-mentioned method is executed.

[0015] Advantages of the Invention

[0016] The method executed by the user equipment and the user equipment according to the present disclosure can solve the problems involved in transmitting low-priority MAC PDUs stored in the HARQ process buffer, thereby improving the communication efficiency and reliability of the wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Through the following detailed description in conjunction with the drawings, the above and other features of the present disclosure will become more obvious, wherein:

[0018] Figure 1 A flowchart showing a method executed by a user equipment according to an embodiment of the present disclosure;

[0019] Figure 2 A schematic flowchart showing a method according to Embodiment 1 of the present disclosure;

[0020] Figure 3 A schematic flowchart showing a method according to Embodiment 3 of the present disclosure;

[0021] Figure 4 A block diagram showing a user equipment according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0022] The present disclosure will be described in detail below in conjunction with the drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, the detailed description of well-known technologies not directly related to the present disclosure is omitted to prevent confusion in the understanding of the present disclosure.

[0023] Some terms related to the present disclosure are described below. Unless otherwise specified, the terms are the same as those used in the latest version of the 3GPP protocol, and are excerpted as follows.

[0024] RRC: Radio Resource Control, radio resource control.

[0025] MAC: Medium Access Control, medium access control.

[0026] PDCCH: Physical Downlink Control Channel, physical downlink control channel.

[0027] PUCCH: Physical Uplink Control Channel, the physical uplink control channel.

[0028] PUSCH: Physical Uplink Shared Channel, the physical uplink shared channel.

[0029] UL-SCH: Uplink Shared Channel, the uplink shared channel

[0030] SDU: Service Data Unit, the service data unit.

[0031] PDU: Protocol Data Unit, the protocol data unit.

[0032] SR: Scheduling Request, the scheduling request.

[0033] CG: Configured uplink Grant, the configured grant.

[0034] UL Grant: Uplink grant.

[0035] configuredGrantTimer: This is a timer. The initial value of the timer is configured by the base station for each CG of the UE through RRC signaling, and its value is several times the corresponding CG period. For the configuration of this timer, refer to the information element configuredGrantTimer defined in TS38.331. The start and stop operations of this timer are described in TS38.321. In the embodiments of the present disclosure, additional start or stop conditions for this timer are added.

[0036] RNTI: Radio Network Temporary Identifier, the radio network temporary identifier.

[0037] CS-RNTI: Configured Scheduling RNTI, the configured scheduling RNTI.

[0038] DG: Dynamic Grant, which refers to the uplink grant dynamically received on the PDCCH. In other words, the uplink grant for the C-RNTI or TC-RNTI (Temporary C-RNTI) of the MAC entity received on the PDCCH or the uplink grant for the CS-RNTI of the MAC entity received on the PDCCH. The uplink grant for the CS-RNTI of the MAC entity can be used to configure the retransmission of the MAC PDU transmitted on the uplink grant. In this case, when the received New Data Indicator (NDI) value is 1, it is considered that the NDI does not flip. The uplink grant for the C-RNTI or TC-RNTI or CS-RNTI of the MAC entity received on the PDCCH is the uplink grant indicated by the PDCCH scrambled by the C-RNTI or TC-RNTI or CS-RNTI of the MAC entity, and these two expressions can be used interchangeably.

[0039] HARQ information: HARQ information transmitted on the DL-SCH or UL-SCH consists of NDI, Transport Block size (TBS), Redundancy Version (RV), and HARQ process ID. Other information may also be included in the HARQ information.

[0040] ra-ResponseWindow: the time window to monitor RA response(s).

[0041] lch-basedPrioritization: Used to indicate that the MAC entity determines the priority of uplink grants and / or scheduling requests (SRs) based on the priorities of logical channels. That is, for a MAC entity configured with lch-basedPrioritization, the priority of an uplink grant is determined by the highest priority among the priorities of the logical channels with data available that are multiplexed or can be multiplexed according to the logical channel prioritization procedure (LCP) defined in TS38.321 (For the MAC entity configured with lch-basedPrioritization, priority of an uplink grant is determined by the highest priority among priorities of the logical channels with data available that are multiplexed or can be multiplexed in the MAC PDU, according to the mapping restrictions as described in clause 5.4.3.1.2.); the priority of an SR is determined by the priority of the logical channel that triggers the SR. In other words, the priority of an uplink grant is the highest priority of the logical channels that meet the conditions, and the priority of an SR is the priority of the logical channel that triggers the SR. A MAC entity being configured with lch-basedPrioritization means that the received RRC message contains this parameter and / or the value of this parameter is set to TRUE or Support or 1, etc. The operations performed by the MAC entity when this parameter is configured are described in detail in the embodiments of the present disclosure.

[0042] autonomousReTx: Used to indicate whether to support transmitting low-priority MAC PDUs using the same HARQ process configured with an uplink grant (e.g., the same configured uplink grant), or used to indicate that the MAC entity transmits low-priority MAC PDUs using the same HARQ process configured with an uplink grant (e.g., the same configured uplink grant). A MAC entity being configured with autonomousReTx means that the MAC entity is configured to transmit MAC PDUs obtained for a low-priority configured uplink grant using the configured uplink grant, and / or the received RRC message contains this parameter and / or the value of this parameter is set to TRUE or Support or 1, etc. The operations performed by the MAC entity when this parameter is configured are described in detail in the embodiments of the present disclosure.

[0043] The signaling elements ra-ResponseWindow, lch-basedPrioritization, and autonomousReTx are configured by the base station for the user equipment via RRC signaling or system information messages. lch-basedPrioritization and autonomousReTx can be configured separately by the base station for each MAC entity of the UE.

[0044] In the present disclosure, a MAC PDU obtained for uplink grant acquisition for a low priority is referred to as a low priority MAC PDU. Optionally, a MAC PDU (or the MAC PDU corresponding to a transport block) discarded due to the physical layer transmitting a high priority channel state indication CSI or HARQ ACK / NACK (acknowledgment / negative acknowledgment) or due to receiving an uplink cancellation indication is also referred to as a low priority MAC PDU. The uplink cancellation indication is an indication for the physical layer not to transmit the PUSCH or to interrupt the current PUSCH transmission, etc.

[0045] At the 3GPP RAN2 #105bis meeting held in April 2019, it was agreed that when multiple configured grants (CGs) or downlink semi-persistent scheduling (SPS) are configured, an offset for calculating the hybrid automatic repeat request (HARQ) process number is configured for each CG or SPS. The purpose of this conclusion is to map different configured uplink grants (or downlink SPSs) to different HARQ processes, so that the HARQ processes associated with, mapped to, or used by the configured uplink grants (or downlink SPSs) are different or non-overlapping. At the 3GPP RAN2 #106 meeting held in May 2019, it was agreed that for the dynamic grant of low-priority PUSCH, the UE stores the corresponding low-priority MAC PDU in the HARQ buffer, so that the gNB can schedule retransmission using the same HARQ process (For de-prioritized PUSCH on dynamic grant, the UE should store the de-prioritized MAC PDU in the HARQ buffer, to allow gNB to schedule re-transmission using the same HARQ process); for the configured uplink grant of low-priority PUSCH, a) the UE stores the corresponding low-priority MAC PDU in the HARQ buffer, so that the gNB can schedule retransmission, b) Whether the UE can retransmit on subsequent radio resources requires further discussion, such as using radio resources subsequently associated with the same HARQ process (For de-prioritized PUSCH on configured grants, a) the UE could store the de-prioritized MAC PDU in the HARQ buffer, to allow gNB to schedule re-transmission. b) FFS if the UE could transmit it using the subsequent radio resources e.g. associated with the same HARQ proces); the above conclusions apply at least to the case where the MAC entity has generated a MAC PDU for the dynamic grant or configured uplink grant of low priority.Agreed at RAN2 #107 meeting: For CG-CG conflicts, the same priority scheme as for CG-DG conflicts is adopted (i.e., both are based on the same method of determining priorities); the same priority scheme is adopted for resource conflicts between new transmissions (i.e., generating new MAC PDUs for uplink grants) and for resource conflicts between new transmissions and retransmissions (i.e., retransmissions of MAC PDUs); the recovery mechanism for low-priority MAC PDUs when there are conflicts among PUSCHs (i.e., how to retransmit the low-priority MAC PDUs saved in the HARQ process buffer when there is a conflict) is also applied to conflicts between PUSCH and scheduling request SR; when there is a conflict between DG and CG, if the priorities of these two grants are the same (i.e., the priorities or the highest priorities of the MAC PDUs generated for these two uplink grants are the same), then the MAC PDU generated for DG is considered to have a higher priority (i.e., the MAC layer instructs the physical layer to transmit the MAC PDU generated for DG); when there is a conflict between two uplink grants, if no MAC PDUs have been generated for these two uplink grants, then only one of the uplink grants will have a MAC PDU generated for it; if the PUCCH used to transmit SR overlaps with the UL-SCH, then it is determined whether to transmit SR by comparing the priority of the logical channel that triggers SR with the priority of the UL-SCH. If the priority of the logical channel that triggers SR is higher, then SR is transmitted; if SR occurs before the MAC PDU for the UL-SCH is generated and there is a conflict between the PUCCH used to transmit SR and the UL-SCH of the MAC PDU (i.e., they cannot be transmitted simultaneously) and the priority of the UL-SCH is lower, then no MAC PDU is generated for the UL-SCH. Agreed at RAN2 #108 meeting: The UE transmits low-priority (de-prioritized) MAC PDUs in a new transmission manner on the same HARQ process of the same CG; whether to use CG to transmit low-priority MAC PDUs is configured by the network (i.e., the base station); and if the network schedules a retransmission of a low-priority MAC PDU, then this MAC PDU cannot be transmitted on the CG anymore.

[0046] In the present disclosure, on a serving cell, the conflict or overlap between the PUSCH duration of an uplink grant (i.e., dynamic grant DG or configured uplink grant or UL-SCH) on a certain HARQ process and the scheduling request SR (i.e., the PUCCH of SR or the PUCCH duration of SR or the PUCCH where SR occurs or the PUCCH for transmitting SR) is referred to as the conflict between the uplink grant and SR (in other words, UL-SCH or PUSCH and SR cannot both be transmitted or cannot be transmitted simultaneously). On a serving cell, the overlap between the PUSCH duration of the dynamic grant DG on a certain HARQ process and the PUSCH duration of the configured grant CG on another HARQ process is referred to as the DG / CG PUSCH conflict. On a serving cell, the overlap between the PUSCH duration of the configured grant CG on a certain HARQ process and the PUSCH duration of the configured grant CG on another HARQ process is referred to as the CG / CG PUSCH conflict. The DG / CG PUSCH conflict includes the case where there is a conflict between the PUSCH durations of one DG and multiple CGs on different HARQ processes; similarly, the CG / CG PUSCH conflict also includes the case where there is a conflict between the PUSCH durations of multiple CGs; and the conflict between the uplink grant and SR also includes the case where there are multiple conflicts between the uplink grant and SR. Unless otherwise specified, the DG / CG or CG / CG conflicts described in the embodiments of the present disclosure include the above various conflicts, and the conflicts refer to the DG and CG in conflict and the two or more CGs or SRs in conflict being on the same serving cell. In the present disclosure, the PUSCH overlap (or conflict) between different uplink grants or the overlap (or conflict) between PUSCH and SR can be that different uplink grants overlap in the time domain, in other words, they cannot both be transmitted or cannot be transmitted simultaneously.

[0047] If a MAC PDU is generated for a CG where a DG / CG or CG / CG conflict or an uplink grant and SR conflict occurs, and the MAC PDU is stored in the HARQ buffer of the corresponding HARQ process (i.e., the HARQ process corresponding to the CG or the HARQ process identified for the CG) without being transmitted (e.g., due to its low priority), the non - transmission can be that it is not indicated to the physical layer, or it has been indicated to the physical layer but is not transmitted or the transmission is interrupted or not transmitted on the corresponding uplink grant due to a conflict with a MAC PDU or SR with a higher priority, or due to receiving an uplink cancellation indication, etc., or it has been indicated to the physical layer but conflicts with the PUCCH for transmitting CSI (Channel State Information) or HARQ ACK or HARQ NACK with a higher transmission priority. Optionally, when the physical layer discards a transport block TB or stops a PUSCH transmission that is about to occur or interrupts the current PUSCH transmission due to transmitting the PUCCH for high - priority CSI (Channel State Information) or HARQ ACK or HARQ NACK, or due to receiving an uplink cancellation indication, a transport block discard indication or a transport block discard indication for the corresponding HARQ process is sent to the upper layer. Sending a transport block discard indication or a transport block discard indication for the corresponding HARQ process to the upper layer is sending a MAC PDU discard indication or a MAC PDU discard indication for the corresponding HARQ process to the upper layer.

[0048] Figure 1 The flowchart of the method performed by a user equipment according to an embodiment of the present disclosure is shown.

[0049] As Figure 1 shown, the method performed by the user equipment of the present disclosure includes step S1 and step S2.

[0050] In step S1, if the MAC entity is configured with a configured uplink grant and is activated, it is determined whether the MAC entity is configured to transmit the MAC PDU obtained for the low - priority configured uplink grant using the configured uplink grant.

[0051] In step S2, if the MAC entity is configured to transmit the MAC PDU using the configured uplink grant, the configured uplink grant is delivered to the HARQ entity.

[0052] According to the above method, the problems involved in transmitting low - priority MAC PDUs stored in the HARQ process buffer can be solved, thereby improving the communication efficiency and reliability of the wireless communication system.

[0053] Embodiment 1: For each serving cell and each configured uplink grant, if configured and activated (i.e., the MAC entity is configured with an uplink grant and the uplink grant is activated), if the MAC entity is configured to transmit the MAC PDU obtained by the configured uplink grant with low priority using the configured uplink grant, then the configured uplink grant is delivered to the HARQ entity (even if the configuredGrantTimer of the corresponding HARQ process is running).

[0054] The following is a specific description:

[0055] Figure 2 Fig. shows a schematic flowchart of the method according to Embodiment 1.

[0056] For each serving cell and each configured uplink grant, if configured and activated (i.e., the MAC entity is configured with an uplink grant and the uplink grant is activated), the MAC entity performs the following operations:

[0057] In step 1001, if condition 1a or condition 1b is satisfied, then step 1002 is executed:

[0058] Condition 1a: The MAC entity is configured with lch-basedPrioritization (the MAC entity is configured with lch-basedPrioritization);

[0059] Condition 1b: The PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of the uplink grant received on the PDCCH or in a Random Access Response for this serving cell (

[0060] the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant received on the PDCCH or in a Random Access Response for this Serving Cell);

[0061] In step 1002, set the HARQ process number to the HARQ process number associated with this PUSCH duration (set the HARQ Process ID to the HARQ Process ID associated with this PUSCH duration); if one of the following conditions 1c to 1f is satisfied, then step 1003 is executed:

[0062] Condition 1c: The timer configuredGrantTimer corresponding to the HARQ process is not running;

[0063] Condition 1d: The MAC entity is configured with autonomousReTx;

[0064] Condition 1e: The MAC entity is configured with lch-basedPeioritization;

[0065] Condition 1f: The MAC entity is configured with autonomousReTx, and this configured uplink grant is a high-priority configured uplink grant (this condition is optional), and the previous configured uplink grant corresponding to the HARQ process is a low-priority configured uplink grant, and a MAC PDU has been obtained for the corresponding HARQ process, and this obtained MAC PDU has not been transmitted or a discard indication for this MAC PDU has not been received (this condition is optional);

[0066] In step 1003, perform at least one of the following operations 1A-1C:

[0067] Operation 1A. Consider the new data indication NDI bit for the corresponding HARQ process to have been toggled;

[0068] Operation 1B. Deliver the configured uplink grant and the associated HARQ information to the HARQ entity;

[0069] Operation 1C. Consider that a MAC PDU has been obtained for this configured uplink grant (this operation is optional and only applicable when condition 1f is satisfied).

[0070] It should be noted that conditions 1a to 1f do not all have to appear. One or several of these conditions can be selected to form different embodiments.

[0071] Embodiment 2: When a configured uplink grant is a low-priority configured uplink grant and a MAC PDU has been obtained for this low-priority configured uplink grant, stop the timer configuredGrantTimer (if a timer configuredGrantTimer is configured for the configured grant and is running).

[0072] The following is a specific description:

[0073] When the MAC entity is configured with lch-basedPrioritization, for each uplink grant addressed to C-RNTI or CS-RNTI (if the uplink grant is addressed to C-RNTI or CS-RNTI): If the PUSCH duration of this uplink grant does not overlap with the PUSCH duration of a configured uplink grant whose priority is higher than the priority of this uplink grant (if there is no overlapping PUSCH duration of a configured uplink grant whose priority is higher than the priority of the uplink grant), and if the PUSCH duration of this uplink grant does not overlap with the PUCCH resource of an SR transmission where the priority of the logical channel that triggered the SR is higher than the priority of this uplink grant (if there is no overlapping PUCCH resource with an SR transmission where the priority of the logical channel that triggered the SR is higher than the priority of the uplink grant), then perform at least one of the following operations 2A to 2E:

[0074] Operation 2A: Consider this uplink grant as a high-priority uplink grant (this uplink grant is a prioritized uplink grant);

[0075] Operation 2B: If this uplink grant is a high-priority uplink grant addressed to CS-RNTI, consider that the MAC PDU obtained for this uplink grant has been transmitted or consider that the MAC PDU stored in the HARQ buffer of the HARQ process identified by this uplink grant has been transmitted (this operation is only performed if there is such a MAC PDU);

[0076] Operation 2C: Consider the other overlapping uplink grant(s), if any, as a deprioritized uplink grant; in other words, consider the other uplink grant(s) (if any) that overlap with the PUSCH duration of this uplink grant as a deprioritized uplink grant;

[0077] Operation 2D: If the deprioritized uplink grant is an uplink grant for a C-RNTI, and the HARQ process identified for this uplink grant is the HARQ process configured for a configured uplink grant, and no MAC PDU has been obtained for the deprioritized uplink grant, stop the configuredGrantTimer for the corresponding HARQ process;

[0078] Operation 2E: If the deprioritized uplink grant is a configured uplink grant and the MAC entity is configured with autonomouResTx, stop the configuredGrantTimer (if configured and running) for the HARQ process corresponding to this deprioritized uplink grant (i.e., the HARQ process identified for this uplink grant), and / or consider the MAC PDU obtained for this uplink grant as not transmitted or consider the MAC PDU corresponding to this uplink grant as not transmitted.

[0079] When the MAC entity is configured with lch-basedPrioritization, for each configured uplink grant:

[0080] If the PUSCH duration of this uplink grant does not overlap with the PUSCH duration of another configured uplink grant whose priority is higher than the priority of this uplink grant, and if the PUSCH duration of this uplink grant does not overlap with the PUSCH duration of an uplink grant addressed to C-RNTI or CS-RNTI whose priority is higher than or equal to the priority of this uplink grant, and if the PUSCH duration of this uplink grant does not overlap with the PUCCH resource of an SR transmission where the priority of the logical channel that triggered the SR is higher than the priority of this uplink grant, then at least one of the following operations 2F - 2I is performed:

[0081] Operation 2F: Consider this uplink grant as a high-priority uplink grant;

[0082] Operation 2G: If this uplink grant is a high-priority uplink grant, consider that the MAC PDU obtained for this uplink grant has been transmitted or consider that the MAC PDU corresponding to this uplink grant has been transmitted (this operation is only performed if there is such a MAC PDU);

[0083] Operation 2H: Consider other overlapping uplink grants as low-priority uplink grants; in other words, consider other uplink grants (if any) whose PUSCH duration overlaps with the PUSCH duration of this uplink grant as low-priority uplink grants;

[0084] Operation 2I: If the low-priority uplink grant is a configured uplink grant and the MAC entity is configured with autonomousReTx, optionally, further satisfying that if a MAC PDU is obtained for this low-priority uplink grant, stop the timer configuredGrantTimer of the HARQ process corresponding to this low-priority uplink grant (i.e., the HARQ process identified for this uplink grant) (if configured and running), and / or consider that the MAC PDU obtained for this low-priority uplink grant is not transmitted or consider that the MAC PDU corresponding to this low-priority uplink grant is not transmitted.

[0085] When the MAC entity receives a transport block (or MAC PDU) discard indication (from the physical layer) for a certain HARQ process, it performs at least one of the following Operations 2J to 2K:

[0086] Operation 2J: Consider that this uplink grant is a de-prioritized uplink grant

[0087] Operation 2K: If the MAC entity is configured with autonomousReTx, optionally, further satisfying that if a MAC PDU is obtained for this low-priority uplink grant, stop the timer configuredGrantTimer of the HARQ process corresponding to this low-priority uplink grant (i.e., the HARQ process identified for this uplink grant) (if configured and running), and / or consider that the MAC PDU obtained for this low-priority uplink grant is not transmitted or consider that the MAC PDU corresponding to this low-priority uplink grant is not transmitted.

[0088] Embodiment 3: If a MAC PDU is obtained for the low-priority uplink grant, do not start the timer configuredGrantTimer of the HARQ process corresponding to this uplink grant (i.e., the HARQ process identified for this uplink grant).

[0089] The following is a specific description:

[0090] Figure 3 A schematic flowchart of the method according to Embodiment 3 is shown.

[0091] For each uplink grant, the HARQ entity identifies the HARQ process associated with this uplink grant and performs the following steps for each identified HARQ process:

[0092] In step 3001: If one of the following conditions 3a to 3e is satisfied, then perform step 3002:

[0093] Condition 3a: The received uplink grant is not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process (if the received grant was not addressed to a Temporary C-RNTI on PDCCH, and the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this TB of this HARQ process):

[0094] Condition 3b: If the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty (if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty);

[0095] Condition 3c: If the uplink grant was received in a Random Access Response (if the uplink grant was received in a Random Access Response);

[0096] Condition 3d:: If the uplink grant was received on PDCCH for the C-RNTI in ra-Response Window and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery (if the uplink grant was received on PDCCH for the C-RNTI in ra-Response Window and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery);

[0097] Condition 3e: If the uplink grant is part of a bundle of the configured uplink grant, and maybe used for initial transmission according to clause 6.1.2.3 of TS 38.214[7], and if no MAC PDU has been obtained for this bundle.

[0098] In step 3002, if condition 3f or 3g is satisfied, perform the following operations 3A and 3B; otherwise, perform step 3003;

[0099] Condition 3f: If there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response;

[0100] Condition 3g: If there is a MAC PDU in the Msg3 buffer and the uplink grant was received on PDCCH for the C-RNTI in ra-Response Window and this PDCCH successfully completed the Random Access procedure initiated for beam failure recovery;

[0101] Operation 3A: Obtain the MAC PDU from the Msg3 buffer for transmission;

[0102] Operation 3B: If the uplink grant size does not match with size of the obtained MAC PDU, and if the Random Access procedure was successfully completed upon receiving the uplink grant, then indicate to the Multiplexing and assembly entity to include MAC subPDU(s) carrying MAC SDU from the obtained MAC PDU in the subsequent uplink transmission.

[0103] In step 3003, if one of the conditions 3h to 3j is satisfied, it is considered that a MAC PDU has been obtained; otherwise, step 3004 is executed.

[0104] Condition 3h: If the MAC entity is configured with autonomousReTx, and if this uplink grant is a configured grant which is a prioritized uplink grant, and if the previous configured uplink grant for this HARQ process was de-prioritized, and if a MAC PDU had already been obtained for this HARQ process, and if a transmission of the obtained MAC PDU has not been performed;

[0105] Condition 3i: If the MAC entity is configured with autonomousReTx, and this uplink grant is a high-priority configured uplink grant, and the previous configured uplink grant for this HARQ process is a low-priority uplink grant, and a MAC PDU has been obtained for this HARQ process, and an indication that the transport block (or MAC PDU) corresponding to this HARQ process has been discarded is received.

[0106] Condition 3j: If the MAC entity is configured with autonomousReTx, and this uplink grant is a high-priority configured uplink grant, and the previous configured uplink grant for this HARQ process is a low-priority uplink grant, and a MAC PDU has been obtained for this HARQ process, and the MAC PDU has not been transmitted or an indication that the transport block (or MAC PDU) corresponding to this HARQ process has been discarded is received.

[0107] In step 3004, if the uplink grant is a configured uplink grant and the configuredGrantTimer for the corresponding HARQ process is running, then this uplink grant is ignored; otherwise, step 3005 is executed.

[0108] Alternatively, in step 3004, if the uplink grant is a configured uplink grant and the configuredGrantTimer for the corresponding HARQ process is running, and the previous uplink grant for this HARQ process is not for C-RNTI, then this uplink grant is ignored; otherwise, step 3005 is executed.

[0109] In step 3005, if the MAC entity is not configured with lch-basedPrioritization, or this uplink grant is a high-priority uplink grant, then obtain the MAC PDU to transmit from the Multiplexing and assembly entity, if any.

[0110] For a detailed description of the generation of the MAC PDU by the multiplexing and assembly entity described in this disclosure, see TS38.321. This entity generates the MAC PDU according to the logical channel priority rules and MAC control elements, etc.

[0111] The following describes the operations performed by the HARQ entity after obtaining the MAC PDU for the uplink grant.

[0112] If the MAC PDU for transmission is obtained, then perform the following operations:

[0113] Deliver the MAC PDU, the corresponding uplink grant, and the HARQ information of the transport block to the identified HARQ process (the HARQ process identified for the corresponding uplink grant).

[0114] If the uplink grant is not a configured uplink grant, or if the uplink grant is not for a CS-RNTI, or if the uplink grant is a high-priority configured uplink grant, or if the uplink grant is a high-priority uplink grant for a CS-RNTI, then perform the following Operations 3C and 3D:

[0115] Operation 3C: Indicate that the identified HARQ process triggers a new transmission.

[0116] Operation 3D: If the uplink grant is for a CS-RNTI, or if the uplink grant is a configured uplink grant, or if the uplink grant is an uplink grant for a C-RNTI and the identified HARQ process is the HARQ process configured for the configured uplink grant, then when the transmission is performed, start or restart the configuredGrantTimer of the corresponding HARQ process.

[0117] In the embodiments of the present disclosure, the uplink grant for a C-RNTI or CS-RNTI or TC-RNTI refers to the uplink grant for the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity, or the uplink grant received on the PDCCH for the C-RNTI or CS-RNTI or TC-RNTI of the MAC entity, or the uplink grant indicated by the PDCCH scrambled by the C-RNTI or CS-RNTI or TC-RNTI.

[0118] For a MAC entity configured with lch-based Prioritization, the priority of an uplink grant is determined by the highest priority among the priorities of the logical channels with data available that are multiplexed or can be multiplexed in the MAC PDU, according to the logical channel prioritization procedure LCP (see specifically TS 38.321 5.4.3.1.2, the latest version is R2-1916352). For example, an uplink grant CG1 is received, and this uplink grant can transmit data from logical channels LCH1, LCH2, and LCH3, where the priority of LCH1 is 1 and the highest, the priority of LCH2 is 2, and the priority of LCH3 is 3 (assuming that the larger the number, the lower the priority). Assume that at this time, only LCH2 and LCH3 have data to send, then the priority of CG1 is 2. If the priority of the uplink grant also considers the priority of the MAC control element, then the priority of the uplink grant is jointly determined according to the priority of the MAC control element and the logical channel with data to be sent.

[0119] Unless otherwise specified, the uplink grant described in the embodiments of the present disclosure may be a DG or a CG.

[0120] Figure 4 A block diagram of a user equipment UE40 according to an embodiment of the present disclosure is shown. As Figure 4 shown, the UE40 includes a processor 410 and a memory 420. The processor 410 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 420 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories. Program instructions are stored on the memory 420. When executed by the processor 410, these instructions can perform the above methods in the user equipment described in detail in the present disclosure.

[0121] Computer-executable instructions or programs running on a device according to the present disclosure may be programs that enable a computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or the information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0122] The computer-executable instructions or programs for implementing the functions of the embodiments of the present disclosure may be recorded on a computer-readable storage medium. The corresponding functions may be implemented by causing a computer system to read the programs recorded on the recording medium and execute these programs. The so-called "computer system" here may be a computer system embedded in the device and may include an operating system or hardware (such as peripherals). The "computer-readable storage medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for temporarily storing a dynamic program, or any other recording medium readable by a computer.

[0123] The various features or functional modules of the devices used in the above embodiments may be implemented or executed by circuits (for example, single-chip or multi-chip integrated circuits). The circuits designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuits may be digital circuits or analog circuits. In the case where new integrated circuit technologies that replace existing integrated circuits emerge due to the progress of semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

[0124] In addition, the present disclosure is not limited to the above embodiments. Although various examples of the embodiments have been described, the present disclosure is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors may be used as terminal devices or communication devices, such as AV devices, kitchen devices, cleaning devices, air conditioners, office devices, vending machines, and other household appliances.

[0125] As described above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present disclosure also includes any design modifications that do not deviate from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and the embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. In addition, the components having the same effect described in the above embodiments can be substituted for each other.

Claims

1. A method performed by a user equipment UE, the method comprising: In the following cases, consider the uplink grant for a C-RNTI or CS-RNTI that is one of the uplink grants whose respective Physical Uplink Shared Channel PUSCH durations overlap as a high-priority uplink grant, and consider the other overlapping uplink grants as low-priority uplink grants: (i) the PUSCH duration of the uplink grant for the C-RNTI or CS-RNTI does not overlap with the PUSCH duration of a configured uplink grant whose priority is higher than that of the uplink grant for the C-RNTI or CS-RNTI, and (ii) the PUSCH duration of the uplink grant for the C-RNTI or CS-RNTI does not overlap with the Physical Uplink Control Channel PUCCH resources for scheduling request SR transmission, where the priority of the logical channel triggering the SR transmission is higher than the priority of the uplink grant for the C-RNTI or CS-RNTI; In the following cases, consider the configured uplink grant that is one of the uplink grants whose respective PUSCH durations overlap as a high-priority uplink grant, and consider the other overlapping uplink grants as low-priority uplink grants: (a) the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of another configured uplink grant whose priority is higher than that of the configured uplink grant, (b) the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of the uplink grant for a C-RNTI or CS-RNTI whose priority is higher than or equal to that of the configured uplink grant, and (c) the PUSCH duration of the configured uplink grant does not overlap with the PUCCH resources for SR transmission, where the priority of the logical channel triggering the SR transmission is higher than the priority of the configured uplink grant; In the case where the autonomousReTx information element is configured and the configured uplink grant is one of the low-priority uplink grants, stop the configuredGrantTimer of the Hybrid Automatic Repeat reQuest HARQ process corresponding to the configured uplink grant; and If the autonomousReTx information element is configured, use the high-priority uplink grant to transmit the Media Access Control protocol data unit MAC PDU that has been obtained for the HARQ process associated with the previous low-priority configured uplink grant but has not been fully transmitted.

2. A user equipment, comprising: A processor; And A memory storing instructions, Wherein, the processor is configured based on the instructions to: An uplink grant for a C-RNTI or CS-RNTI is considered a high-priority uplink grant among one of the uplink grants whose respective Physical Uplink Shared Channel (PUSCH) durations overlap, and other overlapping uplink grants are considered low-priority uplink grants in the following cases: (i) the PUSCH duration of the uplink grant for the C-RNTI or CS-RNTI does not overlap with the PUSCH duration of a configured uplink grant whose priority is higher than that of the uplink grant for the C-RNTI or CS-RNTI, and (ii) the PUSCH duration of the uplink grant for the C-RNTI or CS-RNTI does not overlap with the Physical Uplink Control Channel (PUCCH) resources for a Scheduling Request (SR) transmission, where the priority of the logical channel triggering the SR transmission is higher than the priority of the uplink grant for the C-RNTI or CS-RNTI; A configured uplink grant is considered a high-priority uplink grant among one of the uplink grants whose respective PUSCH durations overlap, and other overlapping uplink grants are considered low-priority uplink grants in the following cases: (a) the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of another configured uplink grant whose priority is higher than that of the configured uplink grant, (b) the PUSCH duration of the configured uplink grant does not overlap with the PUSCH duration of an uplink grant for a C-RNTI or CS-RNTI whose priority is higher than or equal to that of the configured uplink grant, and (c) the PUSCH duration of the configured uplink grant does not overlap with the PUCCH resources for an SR transmission, where the priority of the logical channel triggering the SR transmission is higher than the priority of the configured uplink grant; In the case where the autonomousReTx information element is configured and the configured uplink grant is one of the low-priority uplink grants, stop the configuredGrantTimer of the Hybrid Automatic Repeat reQuest (HARQ) process corresponding to the configured uplink grant; and If the autonomousReTx information element is configured, use a high-priority uplink grant to transmit the Media Access Control Protocol Data Unit (MAC PDU) that has been obtained for the HARQ process associated with the previous low-priority configured uplink grant but has not been fully transmitted.

Images