阅读说明：本技术 用于处理重叠的pusch持续时间的方法和装置 (Method and apparatus for processing overlapping PUSCH durations ) 是由 靳亨立 魏嘉宏 郑钰新 林宛臻 于 2020-03-27 设计创作，主要内容包括：提供了一种用于由UE执行的上行链路(UL)传输的方法。该方法包括：在第一PUSCH持续时间期间执行UL传输；接收调度第二PUSCH持续时间的PDCCH；确定第一PUSCH持续时间在时域中与第二PUSCH持续时间重叠；确定第二PUSCH持续时间优先于第一PUSCH持续时间；以及从调度第二PUSCH持续时间的PDCCH结束之后的预配置时间段后开始,取消在第一PUSCH持续时间期间正在进行的UL传输。(A method for Uplink (UL) transmission performed by a UE is provided. The method comprises the following steps: performing UL transmission during a first PUSCH duration; receiving a PDCCH for scheduling a second PUSCH duration; determining that a first PUSCH duration overlaps a second PUSCH duration in a time domain; determining that the second PUSCH duration is prior to the first PUSCH duration; and canceling the ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.)

1. A User Equipment (UE), the UE comprising:

one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and

at least one processor coupled to the one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to:

performing an uplink, UL, transmission during a first physical uplink shared channel, PUSCH, duration;

receiving a Physical Downlink Control Channel (PDCCH) scheduling a second PUSCH duration;

determining that the first PUSCH duration overlaps with the second PUSCH duration in a time domain;

determining that the second PUSCH duration is prioritized over the first PUSCH duration; and

canceling the ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

2. The UE of claim 1, wherein the at least one processor is further configured to execute the computer-executable instructions to determine that the second PUSCH duration begins to be prioritized over the first PUSCH duration after the preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

3. The UE of claim 1, wherein the second PUSCH duration is scheduled for UL retransmission.

4. The UE of claim 3, wherein the at least one processor is further configured to execute the computer-executable instructions to:

obtaining a first set of logical channels, LCHs, from at least one first media access control, MAC, service data unit, SDU, corresponding to the first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set of LCHs;

obtaining a second set of LCHs from at least one second MAC SDU corresponding to the second PUSCH duration, wherein the at least one second MAC SDU comprises data from the second set of LCHs; and

determining that the second set of LCHs includes an LCH having a highest priority among all LCHs in the first set of LCHs and the second set of LCHs.

5. The UE of claim 1, wherein the second PUSCH duration is scheduled for an initial UL transmission.

6. The UE of claim 5, wherein the at least one processor is further configured to execute the computer-executable instructions to:

obtaining a first set of LCHs from at least one first MAC SDU corresponding to the first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set of LCHs;

obtaining a second set of LCHs having data available for transmission, wherein the data from the second set of LCHs is to be mapped to the second PUSCH duration according to logical channel prioritized LCP restrictions configured to the UE; and

determining that the second set of LCHs includes an LCH having a highest priority among all LCHs in the first set of LCHs and the second set of LCHs.

7. The UE of claim 1, wherein the first PUSCH duration corresponds to an activated configuration grant, and wherein the at least one processor is further configured to execute the computer-executable instructions to:

determining that a configured grant timer associated with a hybrid automatic repeat request, HARQ, process of the first PUSCH duration is running.

8. The UE of claim 1, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determining a value for the preconfigured time period based on at least one preconfigured look-up table, wherein the at least one preconfigured look-up table maps different values for the preconfigured time period to different subcarrier spacing, SCS.

9. The UE of claim 8, wherein the at least one lookup table comprises different lookup tables for different UE processing capabilities.

10. The UE of claim 1, wherein the at least one processor is further configured to execute the computer-executable instructions to:

receiving, by a physical layer of the UE, a Transport Block (TB) corresponding to the second PUSCH duration from a MAC entity of the UE; and

canceling the UL transmission that is ongoing during the first PUSCH duration after receiving the TB corresponding to the second PUSCH duration.

11. A method performed by a User Equipment (UE) for Uplink (UL) transmission, the method comprising:

performing UL transmission during a first physical UL shared channel, PUSCH, duration;

receiving a Physical Downlink Control Channel (PDCCH) scheduling a second PUSCH duration;

determining that the first PUSCH duration overlaps with the second PUSCH duration in a time domain;

determining that the second PUSCH duration is prioritized over the first PUSCH duration; and

canceling the ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

12. The method of claim 11, wherein the step of determining that the second PUSCH duration is prioritized over the first PUSCH duration is performed starting after the preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

13. The method of claim 11, wherein the second PUSCH duration is scheduled for UL retransmission.

14. The method of claim 13, wherein the determining the second PUSCH duration over the first PUSCH duration comprises:

obtaining a first set of logical channels, LCHs, from at least one first media access control, MAC, service data unit, SDU, corresponding to the first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set of LCHs;

obtaining a second set of LCHs from at least one second MAC SDU corresponding to the second PUSCH duration, wherein the at least one second MAC SDU comprises data from the second set of LCHs; and

determining that the second set of LCHs includes an LCH having a highest priority among all LCHs in the first set of LCHs and the second set of LCHs.

15. The method of claim 11, wherein the second PUSCH duration is scheduled for an initial UL transmission.

16. The method of claim 15, wherein the step of determining that the second PUSCH duration is prioritized over the first PUSCH duration comprises:

obtaining a first set of LCHs from at least one first MAC SDU corresponding to the first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set of LCHs;

obtaining a second set of LCHs having data available for transmission, wherein the data from the second set of LCHs is to be mapped to the second PUSCH duration according to LCP restrictions configured to the UE; and

determining that the second set of LCHs includes an LCH having a highest priority among all LCHs in the first set of LCHs and the second set of LCHs.

17. The method of claim 11, wherein the first PUSCH duration corresponds to an active configuration grant, and wherein the step of determining that the second PUSCH duration is prioritized over the first PUSCH duration comprises:

determining that a configured grant timer associated with a hybrid automatic repeat request, HARQ, process of the first PUSCH duration is running.

18. The method of claim 11, further comprising:

determining a value for the preconfigured time period based on at least one preconfigured look-up table, wherein the at least one preconfigured look-up table maps different values for the preconfigured time period to different subcarrier spacing SCSs.

19. The method of claim 18, wherein the at least one lookup table comprises different lookup tables for different UE processing capabilities.

20. The method of claim 11, further comprising:

receiving, by a physical layer of the UE, a Transport Block (TB) corresponding to the second PUSCH duration from a MAC entity of the UE;

wherein the step of canceling the UL transmission that is ongoing during the first PUSCH duration is performed after receiving the TB corresponding to the second PUSCH duration.

Technical Field

The present disclosure relates to wireless communications, and more particularly, to a method for handling overlapping Physical Uplink (UL) shared Channel (PUSCH) durations in a cellular wireless communication network.

Background

Various efforts have been made to improve cellular wireless communication systems (e.g., fifth generation (5))^thGeneration, 5G) New Radio (NR)) such as data rate, delay, reliability and mobility. A UL grant sent from a Base Station (BS) to a User Equipment (UE) allocates a PUSCH duration (also referred to as PUSCH resource) for the UE to perform UL data transmission. In the NR, the UL Grant may be a Dynamic UL Grant (also referred to as Dynamic Grant (Dynamic Grant) or DG) or a Configured UL Grant (also referred to as Configured Grant (Configured Grant) or CG). The DG may be referred to as a Downlink (DL) Control Information (DCI) format/message scheduling a PUSCH duration.

The UE may receive the DCI format/message on a Physical Downlink Control Channel (PDCCH). The DCI scheduling the PUSCH duration may contain information such as a Hybrid Automatic Repeat reQuest (HARQ) process Identifier (ID) and a New Data Indicator (NDI). The CGs may correspond to one or more PUSCH durations.

The multiple PUSCH durations allocated to the UE may overlap in the time domain. The PUSCH duration allocated by an active CG may completely or partially overlap with another PUSCH duration allocated by a DG in the same serving cell of the UE. There is a need in the art for an improved efficient mechanism for a UE to handle overlap between multiple PUSCH durations.

Disclosure of Invention

The present disclosure relates to a method for performing UL transmissions by a UE in a cellular wireless communication network.

According to an aspect of the disclosure, there is provided a UE comprising one or more non-transitory computer-readable media having computer-executable instructions embodied thereon, and at least one processor coupled to the one or more non-transitory computer-readable media, the at least one processor configured to execute the computer-executable instructions to: performing an uplink, UL, transmission during a first PUSCH duration; receiving a PDCCH for scheduling a second PUSCH duration; determining that the first PUSCH duration overlaps with the second PUSCH duration in a time domain; determining that the second PUSCH duration is prioritized over the first PUSCH duration; and canceling the ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

According to another aspect of the present disclosure, a method for performing UL transmission by a UE is provided. The method comprises the following steps: performing UL transmission during a first PUSCH duration; receiving a PDCCH for scheduling a second PUSCH duration; determining that the first PUSCH duration overlaps with the second PUSCH duration in a time domain; determining that the second PUSCH duration is prioritized over the first PUSCH duration; and canceling the ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends.

Drawings

The aspects of the present exemplary disclosure are best understood from the following detailed description when read with the accompanying figures. Various features are not drawn to scale. The dimensions of the various features may be arbitrarily increased or decreased for clarity of discussion.

Fig. 1 includes a scenario diagram illustrating that a PUSCH duration indicated by a DG overlaps with another PUSCH duration of a CG according to an exemplary embodiment of the present disclosure.

Fig. 2 includes a diagram illustrating prioritization decisions related to overlapping PUSCH durations, according to an example embodiment of the present disclosure.

Fig. 3 includes a diagram illustrating times at which prioritization decisions in fig. 2 are made according to an example embodiment of the present disclosure.

Fig. 4 includes a diagram illustrating time periods for making the prioritization decision in fig. 2 according to an example embodiment of the present disclosure.

Fig. 5 includes a diagram illustrating a second time period for making the prioritization decision in fig. 2 according to an example embodiment of the present disclosure.

Fig. 6 includes a diagram illustrating a third time period for making the prioritization decision in fig. 2 according to an example embodiment of the present disclosure.

Figure 7 includes a scenario diagram of an LCP process according to an exemplary embodiment of the present disclosure.

Fig. 8 includes a scenario diagram of discarding a previously received Transport Block (TB) in accordance with an example embodiment of the present disclosure.

Fig. 9 includes a scenario diagram of cancelling an ongoing UL transmission according to an example embodiment of the present disclosure.

Fig. 10 is a flowchart of a method for UL transmission according to an example embodiment of the present disclosure.

Fig. 11 is a flowchart of a method for prioritizing a second PUSCH duration for UL retransmission scheduling according to an example embodiment of the present disclosure.

Fig. 12 is a flowchart of a method for prioritizing a second PUSCH duration for initial UL transmission scheduling according to an example embodiment of the present disclosure.

Fig. 13 is a block diagram illustrating a node for wireless communication in accordance with various aspects of the disclosure.

Detailed Description

The following contains specific information pertaining to the embodiments of the present disclosure. The drawings and their accompanying detailed description are directed to embodiments only.

However, the present disclosure is not limited to these embodiments. Other variations and implementations of the present disclosure will be apparent to those skilled in the art.

Unless otherwise indicated, similar or corresponding elements in the drawings may be denoted by similar or corresponding reference numerals. Furthermore, the drawings and illustrations in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

For consistency and ease of understanding, similar features (although not shown in some examples) may be identified with the same numbers in the drawings. However, features in different embodiments may differ in other respects and should not be narrowly limited to the features shown in the drawings.

The phrases "one embodiment" or "some embodiments" may each refer to one or more of the same or different embodiments. The term "coupled" is defined as directly or indirectly connected through intervening elements, and is not necessarily limited to physical connections. The term "comprising" means "including, but not necessarily limited to," and specifically means the open inclusion or membership in a disclosed combination, group, series or equivalent. The phrase "at least one of A, B and C" or "at least one of: A. b and C "means" only a, or only B, or only C, or any combination of A, B and C ".

The terms "system" and "network" may be used interchangeably. The term "and/or" is used merely to describe an associative relationship of associated objects and means that there may be a plurality of relationships such that a and/or B may indicate that a exists alone, that a and B exist simultaneously, or that B exists alone. The character "/" typically indicates that the associated object is in an "or" relationship.

For purposes of explanation and not limitation, specific details are set forth, such as functional entities, techniques, protocols, and standards in order to provide an understanding of the present disclosure. In other instances, detailed descriptions of well-known methods, techniques, systems and architectures are omitted so as not to obscure the description with unnecessary detail.

Those skilled in the art will recognize that any of the network functions or algorithms disclosed may be implemented in hardware, software, or a combination of software and hardware. The disclosed functionality may correspond to modules, which may be software, hardware, firmware, or any combination thereof.

Software implementations may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. One or more microprocessors or general purpose computers having communications processing capabilities may be programmed with corresponding computer executable instructions and perform the disclosed network functions or algorithms.

Microprocessors or general purpose computers may include Application Specific Integrated Circuits (ASICs), programmable logic arrays, and/or use one or more Digital Signal Processors (DSPs). Although some of the disclosed embodiments are oriented to software installed and executing on computer hardware, alternative embodiments implemented as firmware or as hardware or as a combination of hardware and software are within the scope of the present disclosure. The computer-readable medium may include, but is not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory, Compact Disc Read-Only Memory (CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage devices, or any other equivalent medium capable of storing computer-readable instructions.

A wireless communication Network architecture, such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-a) system, an LTE-Pro-Advanced system, or a 5G NR Radio Access Network (RAN), may generally include at least one Base Station (BS), at least one UE, and one or more optional Network elements that provide connectivity in the Network. The UE communicates with a Network (e.g., a Core Network (CN), an Evolved Packet Core (EPC), an Evolved Universal Terrestrial RAN (E-UTRAN), a 5G Core (5G Core, 5GC), or the internet) via a RAN established by one or more BSs.

The UE may include, but is not limited to, a mobile station, mobile terminal or device, or a user communications radio terminal. The UE may be a portable radio including, but not limited to, a mobile phone with wireless communication capability, a tablet computer, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA). The UE may be configured to receive and transmit signals to one or more cells in the RAN over an air interface.

The BS may be configured to provide communication services according to at least one Radio Access Technology (RAT): such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) (commonly referred to as 2G), GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GSM Evolution Radio Access Network, GERAN), General Packet Radio Service (GPRS), Universal Mobile telecommunications System (Universal Mobile telecommunications System, UMTS) (commonly referred to as 3G-based basic Wideband Code Division Multiple Access (W-CDMA)), High Speed Packet Access (HSPA), LTE-a, LTE (LTE-a) (LTE connected to 5GC), NR (commonly referred to as 5G) and Pro/or LTE-a. However, the scope of the present disclosure is not limited to these protocols.

The BS may include, but is not limited to, a Node B (nb) in UMTS, an evolved Node B (eNB) in LTE or LTE-a, a Radio Network Controller (RNC) in UMTS, a BS Controller (BSC) in GSM/GERAN, an ng-eNB in E-UTRA BS linked with a 5GC, a next generation Node B (gNB) in 5G-RAN, and any other device capable of controlling Radio communication and managing Radio resources within a cell. A BS may serve one or more UEs via a radio interface.

The BS is operable to provide radio coverage to a particular geographical area using a plurality of cells forming a RAN. The BS may support the operation of the cell. Each cell may be operable to provide service to at least one UE within its radio coverage.

Each cell (often referred to as a serving cell) may provide services to serve one or more UEs within its radio coverage area, such that each cell schedules Downlink (DL) and Uplink (UL) resources to at least one within its radio coverage area for DL and optional UL packet transmissions. A BS may communicate with one or more UEs in a radio communication system via a plurality of cells.

A cell may allocate Sidelink (SL) resources to support Proximity Service (ProSe) or LTE/NR internet of Vehicle (V2X) services. Each cell may have a coverage area that overlaps with other cells.

As previously described, the frame structure of the NR supports flexible configurations for accommodating various next generation (e.g., 5G) Communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mtc), and Ultra-Reliable and Low-delay Communication (URLLC), while satisfying high reliability, high data rate, and Low delay requirements. Orthogonal Frequency-Division Multiplexing (OFDM) techniques in the third Generation Partnership Project (3 GPP) may be used as a baseline for the NR waveform. Scalable OFDM parameter sets such as adaptive subcarrier spacing, channel bandwidth, and Cyclic Prefix (CP) may also be used.

Two NR coding schemes are considered, namely a Low-Density Parity-Check (LDPC) code and a polar code. Coding scheme adaptation may be configured based on channel conditions and/or service application.

At least DL transmission data, a guard period, and UL transmission data should be included in a Transmission Time Interval (TTI) of a single NR frame. The various parts of DL transmission data, guard period and UL transmission data should also be configured based on network dynamics, e.g., NR. SL resources may also be provided in the NR frame to support ProSe service or V2X service.

In one embodiment, when the PUSCH duration allocated by the DG overlaps with another PUSCH duration allocated by the CG in the time domain, the PUSCH duration allocated by the DG may be prioritized over the PUSCH duration allocated by the CG. In this embodiment, the UE may apply the PUSCH duration indicated by the DG to a Media Access Control (MAC) Protocol Data Unit (PDU) transmission and skip the transmission on the PUSCH duration indicated by the CG.

However, when considering an Industrial Internet of Things (IIoT) scenario, the priority of PUSCH indicated by DG may not always be higher than the PUSCH duration of active CG. For example, an industrial node (e.g., autonomous robot) may generate periodic delay sensitive packets.

The delay requirements may be very strict and may not be met by a DG, which may want the UE to inform the network of the need for UL resource(s), e.g. PUSCH resource(s), via Scheduling Request (SR)/Buffer Status Report (BSR) and the corresponding DG allocated by the network. Thus, the BS (e.g., the gNB) may activate a CG configuration with short periodicity if it has knowledge about when periodic delay sensitive packets arrive. Thus, the UE may not need to inform the network of the need for UL resources (e.g., PUSCH resources) via the SR/BSR, which may result in additional delay. In this case, the PUSCH duration of the CG may have a higher priority than the PUSCH duration indicated by the DG whenever a resource collision occurs. In the present disclosure, resource collision occurs when two or more PUSCH durations partially or completely overlap in the time domain. In this sense, the periodic delay sensitive packet may be transmitted on the PUSCH duration indicated by the CG. Based on the above example scenario, some prioritized rules may be needed in the MAC and/or Physical (PHY) layer of the UE so that the UE can determine whether to skip the PUSCH duration corresponding to the CG or the PUSCH duration indicated by the DG when a resource collision occurs.

Case 1: determining conditions for PUSCH duration conflicts

The conditions in cases 1-1 to 1-3 allow the MAC entity or HARQ entity of the UE to identify whether a collision occurs between PUSCH durations in the time domain. Subsequently, prioritization decisions between conflicting PUSCH durations may be performed. This prioritization may also be referred to as intra-UE UL prioritization.

Case 1-1: MAC entity determining resource conflicts

When a DG for initial transmission is received on a PDCCH (e.g., DCI) (e.g., the NDI provided in the DCI has been toggled compared to a value of a previous transmission using the same HARQ process as the received DG), the MAC entity may then determine whether a PUSCH duration for initial transmission indicated by the DG collides in the time domain with a PUSCH duration for an activated CG for initial transmission or retransmission in the same serving cell. In one embodiment, the PUSCH duration for the retransmitted activated CG may be scheduled via a DG (e.g., a DCI addressed to a configured scheduling radio network temporary identifier (CS-RNTI) and NDI is not toggled compared to a value of a previous transmission using the same HARQ process indicated in the DCI) or via a Radio Resource Control (RRC) signaling configuration (e.g., if a repeated Information Element (IE) of the PUSCH duration(s) of the activated CG is enabled is configured and has a value greater than 1).

If the MAC entity determines that a resource conflict has occurred, the MAC entity may prioritize one of the conflicting PUSCH durations. Only the prioritized PUSCH durations are available for transmission.

Cases 1-2: HARQ entity determining resource conflicts

After the HARQ entity receives a DG for retransmission (e.g., DCI addressed to a cell-RNTI (C-RNTI)) from the MAC entity on the PDCCH, the HARQ entity may then determine whether the PUSCH duration for retransmission indicated by the DG conflicts with the PUSCH duration for the activated CG for initial transmission or retransmission in the same serving cell. In one embodiment, the PUSCH duration for the active CG for retransmission may be scheduled by the DG (e.g., DCI addressed to the CS-RNTI and NDI not toggled compared to the value of the previous transmission using the same HARQ process indicated in the DCI) or configured via RRC signaling (e.g., if the repetition of PUSCH duration(s) for the IE active CG is configured and has a value greater than 1).

If the HARQ entity determines that a resource collision has occurred, the HARQ entity may prioritize one of the collided PUSCH durations. Only the prioritized PUSCH durations may be used for transmission.

Cases 1 to 3: HARQ entity determining resource conflicts

After the HARQ entity receives from the MAC entity a DG (i.e., DG1) that schedules resources for CG retransmission (e.g., DCI addressed to a CS-RNTI and NDI is not toggled compared to a value of a previous transmission using the same HARQ process indicated in the DCI), the HARQ entity may then determine whether the PUSCH duration indicated by that DG (i.e., DG1) conflicts with a PUSCH duration indicated by another DG (i.e., DG2) for initial transmission or retransmission in the same serving cell. DG2 scheduled for PUSCH duration for initial transmission may be addressed to C-RNTI and the NDI provided in the DCI has been toggled compared to the value of the previous transmission using the same HARQ process as DG 2. In another embodiment, DG2 scheduling PUSCH duration for retransmission may be addressed to the C-RNTI and the NDI provided in the DCI is not toggled compared to the value of the previous transmission using the same HARQ process as DG 2. Only the prioritized PUSCH durations are available for transmission.

In the embodiments of case 1-1 to case 1-3, one of the colliding resources is a PUSCH indicated by a DG, and another one of the colliding resources is a PUSCH with CG activated. Embodiments similar to cases 1-1 to 1-3 may also be applied when both colliding resources are PUSCHs indicated by different DGs or both colliding resources are PUSCHs configured by different CGs.

Case 2 prioritization of MAC entity/HARQ entity execution

The prioritization performed by the MAC entity/HARQ entity may take into account at least one of a number of factors. These factors include Logical Channel Prioritization (LCP) mapping constraints for Logical Channels (LCHs) (e.g., parameters allowedServingCells, allowedSCS-List, maxPUSCH-Duration, configurable grant type1Allowed configured in IE logicalchannelconfiguration), priority configured in IE logicalchannelconfiguration, data availability, data rate provided to one logical channel before any resources are allocated to a lower priority logical channel (e.g., parameter prioritdbratete), whether the UE supports UL transmission that skips UL grants indicated on the PDCCH (e.g., parameter skiplinktxynamic) if no data is available for transmission, the number of repetitions configured for Duration (e.g., parameters PUSCH-to-agent and agent), whether Control elements (MAC Control Element, LCP) are running priority constraints for PUSCH, MAC CE, and running priority constraints for PUSCH, and operating priority limits for MAC CE_j(variables maintained for each logical channel in the LCP procedure) and Packet Data Convergence Protocol (PDCP) replication.

Case 2-1: prioritization based on configuration grant timers

If the MAC entity/HARQ entity recognizes that a resource collision occurs between the PUSCH duration for the active CG and the PUSCH duration indicated by the DG, the MAC entity/HARQ entity may determine whether a configured grant timer (e.g., configuredGrantTimer) corresponding to the active CG has been configured. If the configured grant timer (also referred to as CG timer) has been configured, the MAC entity/HARQ entity may then check if the CG timer corresponding to the HARQ process activating the PUSCH duration for CG is running. If the CG timer corresponding to the activated CG's PUSCH duration HARQ process has been configured and is running, the MAC entity/HARQ entity may prioritize the DG indicated PUSCH duration since the activated CG's PUSCH duration HARQ process cannot be used for initial transmission before the configured grant timer expires.

Fig. 1 includes a diagram 100 illustrating a scenario in which a PUSCH duration indicated by a DG overlaps with another PUSCH duration with a CG activated, according to an exemplary embodiment of the present disclosure. The CG-activated PUSCH duration 110 is associated with HARQ process ID # 1. The PUSCH duration 120 indicated by DG is associated with HARQ process ID # 2. The PUSCH duration 110 overlaps with the PUSCH duration 120 in the time domain.

The MAC entity/HARQ entity can confirm that the initial/new transmission of PUSCH with HARQ process ID #1 on the active CG is prohibited because the CG timer corresponding to HARQ process ID #1 is still running. In this case, the MAC entity/HARQ entity may prioritize the PUSCH 120 indicated by the DG. In contrast, if the MAC entity/HARQ entity acknowledges that the CG timer for HARQ process ID #1 is not running or not configured, further prioritization may be made based on implementation in case 2-2.

In one embodiment, the MAC entity/HARQ entity may directly determine whether a CG timer for a HARQ process activating a CG PUSCH duration is running, and the CG-activated PUSCH duration collides with (e.g., partially or completely overlaps in the time domain) the DG indicated PUSCH duration. The MAC entity/HARQ entity may prioritize the PUSCH duration indicated by the DG if the CG timer for the HARQ process for the activated CG PUSCH duration is running. Conversely, if the MAC entity/HARQ entity confirms that the CG timer for the HARQ process activating the PUSCH duration for CG is not running when a collision occurs, further prioritization may be based on the implementation in case 2.2. In one embodiment, when the MAC entity/HARQ entity recognizes that a resource collision occurs between the CG-activated PUSCH duration and the DG-indicated PUSCH duration, the prioritization decision performed by the MAC entity/HARQ entity may directly follow the embodiment in case 2.2 without performing the method in case 2.1.

Case 2-2: prioritization based on logical channel priority

If the MAC entity/HARQ entity recognizes that a resource collision in a time domain occurs between a PUSCH duration for which CG is activated and a PUSCH duration indicated by a DG in the same serving cell, the MAC entity/HARQ entity may perform prioritization in order to perform prioritizationOne of the conflicting PUSCH durations is selected for transmission. Can be classified as LCH by comparison_{conflictingPUSCH}The LCH priorities (e.g., parameter priorities configured in IE logical channelconfig, with increasing priority values indicating lower priority levels) in all of the LCHs to perform the prioritization decision.

The LCH can be classified as LCH if the LCH includes available data and can be mapped to at least one of the conflicting PUSCH durations_{conflictingPUSCH}. Any LCH with available data that satisfies LCP mapping restrictions to (DG or CG) UL grant indicating or corresponding to a conflicting PUSCH duration may be classified as LCH in this disclosure_{conflictingPUSCH}. For example, two PUSCH durations, specifically PUSCH #1 and PUSCH #2, from the same serving cell overlap in the time domain. Furthermore, in the LCH selection phase of the LCP procedure, LCH #1 and LCH #2 can satisfy the LCP mapping restrictions of PUSCH #1 and PUSCH #2, respectively. In this case, if both LCH #1 and LCH #2 contain available data, they can both be classified as LCHs_{conflictingPUSCH}. PUSCH #1 and PUSCH #2 can be said to map to LCH #1 and LCH #2, respectively. Each configured LCH can be associated with one or more LCP mapping restrictions via a configuration from the BS (e.g., in the IE LogicalChannelConfig). Data from the LCH can only be sent on the PUSCH duration corresponding to a UL grant that satisfies all LCP mapping restrictions associated with the LCH.

In one embodiment, the MAC entity/HARQ entity may be preferentially mapped to a class classified as LCH_{conflictingPUSCH}Of all LCHs having the highest priority. In one embodiment, a UE may acquire a set of LCHs with data available for transmission before the UE generates a MAC PDU for transmission on a PUSCH duration (e.g., the PUSCH duration is scheduled for initial transmission), wherein the data from the set of LCHs will map to the PUSCH duration according to the LCP restriction(s) configured to the UE.

Table 1 shows the mapping between PUSCH duration and LCH. PUSCH #1 maps to two LCHs with available data, including LCH #1 and LCH #3, with priority values of 1 and 3, respectively. PUSCH #2 maps to two LCHs with available data, including LCH #2 and LCH #4, with priority values of 2 and 4, respectively.

LCH #1, LCH #2, LCH #3, and LCH #4 can all be classified as LCH_{conflictingPUSCH}. If PUSCH #1 and PUSCH #2 collide, PUSCH #1 may take precedence over PUSCH #2 because LCH #1 is classified as LCH_{conflictingPUSCH}Has the highest priority among all LCHs.

TABLE 1 mapping between PUSCH duration and LCH

PUSCH duration	Mapping to LCH with available data
		PUSCH#1	LCH#1(priority＝1)，LCH#3(priority＝3)
PUSCH#2	LCH#2(priority＝2)，LCH#4(priority＝4)

In one embodiment, the MAC entity/HARQ entity may prioritize a PUSCH duration corresponding to a MAC Service Data Unit (SDU) (e.g., the MAC SDU is from a MAC PDU that may be transmitted over the PUSCH duration) that contains data from an LCH classified as LCH_{conflictingPUSCH}Has the highest priority among all LCHs. In one embodiment, when prioritization needs to be performed, a MAC PDU (which may include one or more MAC SDUs) for transmission on a PUSCH duration may have been generated (e.g., the PUSCH duration is scheduled for retransmission, and the MAC PDU has been generated and stored for that PUSCH durationIn the HARQ buffer of the identified HARQ process). In one embodiment, the UE may obtain a set of LCHs from at least one MAC SDU corresponding to a PUSCH duration, where the at least one MAC SDU includes data from the set of LCHs.

In one example, the PUSCH durations, both scheduled for retransmission, overlap in the time domain. Further, when the MAC entity/HARQ entity needs to perform prioritization, MAC PDUs corresponding to two PUSCH durations may have been generated and stored in the associated HARQ buffer. Further, one or more MAC SDUs may be included in a MAC PDU corresponding to an overlapping PUSCH duration. In this example, the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to a MAC SDU containing data from all LCHs with the highest priority (e.g., LCHs configured with the lowest priority value) included in MAC SDUs that overlap the PUSCH duration.

In another example, PUSCH #1 is mapped to two LCHs with available data, including LCH #1 and LCH #3, with priority values of 1 and 3, respectively. PUSCH #2 maps to two LCHs with available data, including LCH #2 and LCH #4, with priority values of 2 and 4, respectively. In this example, LCH #1, LCH #2, LCH #3, and LCH #4 may all be classified as LCH_{conflictingPUSCH}. However, the MAC PDU to be transmitted on PUSCH #1 may not include a MAC SDU including data from two associated LCHs (i.e., LCH #1 and LCH #3), since PUSCH #1 may include neither data from LCH #1 nor data from LCH #3 due to the limited grant size.

Further, the MAC PDU to be transmitted on PUSCH #2 may include a MAC SDU containing data from LCH # 2. In this example, PUSCH #2 may then be prioritized over PUSCH #1 because PUSCH #2 includes MAC SDUs, which are from being classified as LCH_{conflictingPUSCH}Has the highest priority (LCH #2) among all LCHs. In one embodiment, if the MAC PDU to be transmitted on the PUSCH duration does not include any MAC SDUs (e.g., the MAC PDU does not include data from any LCHs), the PUSCH duration may be used when the MAC entity/HARQ entity performs prioritizationIs considered to have the lowest priority.

Fig. 2 includes a diagram 200 illustrating prioritization decisions between two overlapping PUSCH durations, according to an example embodiment of the present disclosure. PUSCH # 1210 overlaps PUSCH # 2202 in the time domain. In one example, both PUSCH # 1210 and PUSCH # 2220 may be used for initial transmission.

At time t₂₀Previously, the UE did not generate MAC PDUs for any PUSCH duration. At time t₂₀The UE may prioritize the mapping into a category of LCH_{conflictingPUSCH}Of all LCHs having the highest priority (e.g., PUSCH # 1210). At time t₂₁The UE may generate a new MAC PDU for the initial transmission on PUSCH # 1210.

In another example, both PUSCH # 1210 and PUSCH # 2220 may be used for retransmission. The MAC PDUs corresponding to PUSCH # 1210 and PUSCH # 2220 have been at time t₂₀Previously generated, and each MAC PDU has been transmitted on a previously scheduled PUSCH in the same HARQ process as PUSCH # 1210 and PUSCH # 2220, respectively. At time t₂₀The UE may prioritize the PUSCH duration for transmitting a MAC PDU including a MAC SDU containing data from a packet classified as LCH_{conflictingPUSCH}Of all LCHs having the highest priority. In this example, PUSCH # 2220 may be prioritized. At time t₂₁The UE may request retransmission of the MAC PDU on the prioritized PUSCH duration (e.g., PUSCH # 2220).

Cases 2 to 3: other prioritization methods

There may be no data available in any LCH mapped into at least one conflicting PUSCH duration (e.g., no LCH is classified as LCH), possibly due to limited grant size_{conflictingPUSCH}) And no MAC PDU transmitted on the conflicting PUSCH duration includes the MAC SDU. If skippilinkttxynamic is configured with a TRUE (and skippilinkttxsps is not configured) value, the MAC entity/HARQ entity may prioritize the PUSCH duration indicated by DG.

If the UE is configured with skippalinktxsps and there is no data available for transmission in the UE buffer, the UE may skip UL transmissions for UL grants other than the configured UL grant. On the other hand, if skippalinkttxsps is configured to a TRUE value (and skippalinktxdynamic is not configured), the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to the active CG.

In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration allocated for aperiodic Channel State Information (CSI) transmission. In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to the minimum configured number of repetitions. In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to the maximum configured number of repetitions. The number of repetitions may be configured via RRC signaling or dynamically indicated in the UL grant. For example, when further prioritization is required between the PUSCH duration indicated by DG and the PUSCH duration activating CG, and repK from IE ConfiguredGrantConfig and PUSCH-aggregomentfactor from IE PUSCH-Config are configured as n4 and n8, respectively (n4< n8), the UE may prioritize the PUSCH duration activating CG.

In one embodiment, the MAC entity/HARQ entity may prioritize a PUSCH duration that can accommodate a particular type of MAC CE (e.g., if a MAC PDU to be transmitted over the PUSCH duration includes a particular type of MAC CE). The specific type of MAC CE may be preconfigured or indicated by the BS. In one embodiment, the specific type of MAC CE may be a BSR MAC CE. In one embodiment, the specific type of MAC CE may be a Beam Failure Recovery Request (BFRQ) MAC CE, which may be an UL MAC CE transmitted from the UE to the BS for indicating Beam Failure related information (of a secondary cell (SCell)). Upon triggering the (SCell) beam failure recovery procedure, the MAC entity of the UE may send a BFRQ MAC CE to the serving BS via the PUSCH resource. In one embodiment, the specific MAC CE may be the MAC CE having the highest configuration priority. The priority of the MAC CE may be configured by the network via RRC messages or DCI signaling.

In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to the minimum payload size or TB size. In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration corresponding to the minimum PUSCH duration.

In one embodiment, the MAC entity/HARQ entity may prioritize the PUSCH duration with the earliest start time or earliest end time. It should be noted that case 2-3 may also be applied to prioritize one for transmitting PUSCH whenever the UE determines that a resource collision occurs as described in case 1-1 to case 1-3.

Case 3: time to perform prioritization decisions

The prioritization decisions in case 2-1 through case 2-3 may take into account the data availability of LCH(s) mapped to conflicting PUSCH durations. The exact point in time at which the prioritization decision is made may directly affect the prioritization results.

Fig. 3 includes a graph 300 illustrating the timing of prioritization decisions in accordance with an exemplary embodiment of the present disclosure. The UE receives on PDCCH301 DG allocated PUSCH # 2302 that collides with PUSCH # 1303 activating CG. If the MAC entity ensures that there is sufficient time for the generation of MAC PDUs after the prioritization decision is made (regardless of DCI decoding time), the UE may be in the time period T shown in fig. 3_PAt any point in time within the time period.

In this example, LCH #1(priority 1) and LCH #3(priority 3) are mapped to PUSCH # 1303. LCH #2(priority 2) and LCH #4(priority 4) are mapped to PUSCH # 2302. If LCH #2 is at time t₃₀Previously there was pending data available for transmission, and the data corresponding to LCH #1 was at t₃₀And t₃₁Is reached at time t₃₀And t₃₁Prioritization decisions made may have different outcomes. In this example, if at time t₃₀A prioritization decision is made, the MAC entity/HARQ entity may prioritize PUSCH # 2302 indicated by PDCCH 301. However, if at time t₃₁The prioritization decision is made, the MAC entity/HARQ entity can preferentially activate CG PUSCH # 1303.

In case 3, timing information related to when to make a prioritization decision may be preconfigured, indicated by the BS via RRC signaling configuration, or via a DCI field. The timing information may indicate a time period or an exact point of time when the MAC entity/HARQ entity may perform a prioritization decision when a resource collision occurs between a plurality of PUSCHs. In one embodiment, if the timing information is configured by the BS, the timing information may be configured in terms of a UL/DL Bandwidth Part (BWP), per serving cell group, or per UE. The MAC entity/HARQ entity may acquire/generate MAC PDUs from the multiplexing and assembly process after a prioritization decision has been made.

Case 3-1: after T1 after the end of PDCCH scheduling PUSCH

Fig. 4 includes a graph 400 illustrating a time-dependent time period T1 for making prioritization decisions according to an exemplary embodiment of the present disclosure. The UE receives on PDCCH 401 a DG allocated PUSCH # 2402 which collides with PUSCH # 1403 (e.g., PUSCH duration with CG activated).

In one embodiment, the MAC entity/HARQ entity may be at time t₄₁Performing a prioritization determination at time t₄₁Is PDCCH 403 (at time t) carrying DCI scheduling PUSCH # 2402₄₀) After a time period T1 after the reception ends. In one embodiment, the MAC entity/HARQ entity may start from a time period T1 after the end of the reception of PDCCH 403 (e.g., from time T)₄₁Start) to perform a prioritization decision. In one embodiment, the MAC entity/HARQ entity may perform multiple prioritization decisions during time period T1. In one embodiment, the MAC entity/HARQ entity may acquire/generate MAC PDUs from the multiplexing and assembly process after a prioritization decision has been made.

In one embodiment, the value of the time period T1 may be determined based on at least one preconfigured look-up table. The lookup table may map different values of T1 to different UL subcarrier spacing (SCS) corresponding to the indicated PUSCH duration or different DL SCS corresponding to PDCCH scheduling PUSCH duration. In one embodiment, there may be different look-up tables corresponding to different UE processing capabilities. In one embodiment, the UE processing capability may be a PUSCH timing capability. In one embodiment, the time period T1 may be configured in units of symbols, time slots, or milliseconds. Tables 2-a and 2-B illustrate two look-up tables for two different UE processing capabilities, where each table has a mapping between different T1 values and different SCS's.

In one embodiment, the value of T1 may be based on the type of service. The BS may configure a plurality of T1 values corresponding to a plurality of service types to the UE supporting the plurality of service types. For example, a BS may configure a set of T1 values including a T1 value for URLLC and a T1 value for eMBB to a UE that supports both eMBB and URLLC services. The UE may determine the timing of the prioritization decision based on the largest or smallest service-based T1 value in the set configured by the BS.

Case 3-2: before T2 before transmission on earliest PUSCH duration

Fig. 5 includes a diagram 500 illustrating a time-dependent time period T2 for making prioritization decisions according to an exemplary embodiment of the present disclosure. The UE receives a DG on PDCCH 501, which allocates PUSCH # 2502, which collides with PUSCH # 1503 (e.g., PUSCH duration with CG activated).

In one embodiment, the MAC entity/HARQ entity may be at time t₅₀Prioritization is performed, at time t₅₀Is the earliest start time (time t) among all conflicting PUSCH durations in the same cell₅₁) Before a time period T2 before transmission on the PUSCH duration. In one embodiment, the MAC entity/HARQ entity may perform multiple prioritization decisions during time period T2. In one embodiment, the MAC entity/HARQ entity may acquire/generate MAC PDUs from the multiplexing and assembly process after a prioritization decision has been made.

In one embodiment, the value of time period T2 may be determined in a similar manner as time period T1. For example, the time period T2 may depend on at least one of SCS, UE processing capability, and service type. The time period T2 may be configured in units of symbols, time slots, or milliseconds.

Case 3-3: before T3 before transmission on last PUSCH duration

Fig. 6 includes a graph 600 of the time period T3 associated with the time shown for making a prioritization decision in accordance with an exemplary embodiment of the present disclosure. The UE receives on PDCCH 601 a DG allocated PUSCH # 2602, which collides with PUSCH # 1603 (e.g., PUSCH duration with CG activated).

In one embodiment, the MAC entity/HARQ entity may be at time t₆₀Performing a prioritization determination at time t₆₀Is to have the last start time (at time t) in all conflicting PUSCH durations in the same cell₆₁) Before a time period T3 before transmission on the PUSCH duration. In one embodiment, the MAC entity/HARQ entity may perform multiple prioritization decisions during time period T3. In one embodiment, the MAC entity/HARQ entity may acquire/generate MAC PDUs from the multiplexing and assembly process after a prioritization decision has been made. In one embodiment, the value of time period T3 may be determined in a similar manner as time period T1. For example, the time period T3 may depend on at least one of SCS, UE processing capability, and service type. The time period T3 may be configured in units of symbols, time slots, or milliseconds.

Case 4: UE behavior based on intra-UE UL prioritization

In one embodiment, if two PUSCH durations from the same serving cell partially/completely overlap in the time domain, the LCP process may start after the MAC entity/HARQ entity selects a PUSCH duration based on the prioritization decision in cases 2-1 to 2-3. The LCP process may be performed in a multiplexing and assembly entity. After the LCP procedure, the MAC entity/HARQ entity generates/acquires MAC PDU/TB from the multiplexing and assembling entity.

When data becomes available at the LCH mapped to at least one conflicting PUSCH duration, the MAC entity/HARQ entity may perform prioritization by comparing "priority of LCH with incoming data" and "priority of highest priority data already included in the generated MAC PDU" (or "priority of highest priority data to be included in the MAC PDU"). The priority of the data may be indicative of the priority of the LCH from which the data came.

In one embodiment, the prioritization decisions in case 2-1 through case 2-3 may be performed multiple times before actual transmission on the selected PUSCH duration. In one embodiment, if the MAC entity/HARQ entity determines that the prioritization result is changed, the MAC entity may send an indication to the multiplexing and assembling entity to cancel (drop/de-prioritize/puncture) the ongoing LCP procedure and reinitialize the new LCP procedure, which results in another PUSCH duration being reselected for transmission.

Fig. 7 includes a diagram 700 illustrating a scenario of a cancel LCP process according to an exemplary embodiment of the present disclosure. In this example, LCH #1(priority 1) and LCH #3(priority 3) are mapped to PUSCH # 1701. LCH #2(priority 2) and LCH #4(priority 4) are mapped to PUSCH # 2702. PUSCH # 1701 overlaps PUSCH # 2702 in the time domain. Data at time t₇₀To LCH # 2. At time t₇₁The MAC entity/HARQ entity may prioritize PUSCH # 2702 over PUSCH # 1701 because LCH #2 is classified as LCH_{conflictingPUSCH}Has the highest priority among all LCHs (LCH #1 at time t)₇₁No data is available). The UE may perform LCP procedure 712 to generate a MAC PDU corresponding to PUSCH # 2702. When the data is at time t₇₂Upon arrival at LCH #1, the MAC entity/HARQ entity can prioritize PUSCH # 1701 over PUSCH # 2702, since LCH #1 is now classified as LCH_{conflictingPUSCH}Has the highest priority among all LCHs. As the prioritization result is changed, the UE may cancel the ongoing LCP procedure 712 and reinitialize the new LCP procedure 711 to generate the MAC PDU corresponding to PUSCH # 1701.

In one embodiment, if the PHY layer receives a TB (denoted as TB1) or a MAC PDU from the MAC entity/HARQ entity of the UE, the PHY layer may check whether the corresponding PUSCH duration (denoted as PUSCH1) for TB1 partially or completely overlaps in the time domain with any other PUSCH duration scheduled by the BS in the same serving cell. In one embodiment, after the MAC entity/HARQ entity obtains/generates MAC PDUs or TBs 1 from the multiplexing and assembly entity and instructs the PHY layer to perform transmission of MAC PDUs or TBs 1, the PHY layer may receive TB1/MAC PDUs from the MAC entity/HARQ entity.

If there are overlapping PUSCH durations, the PHY layer may check if TB(s) corresponding to PUSCH duration(s) that conflict with PUSCH1 have been received from the MAC entity. If so, the PHY layer may discard the TB(s) that have been received other than TB 1.

Fig. 8 includes a diagram 800 illustrating a scenario of discarding a previously received TB according to an exemplary embodiment of the present disclosure. In this example, LCH #1(priority 1) and LCH #3(priority 3) are mapped to PUSCH # 1801. LCH #2(priority 2) and LCH #4(priority 4) are mapped to PUSCH # 2802. PUSCH # 1801 overlaps PUSCH # 2802 in the time domain.

Data at time t₈₀To LCH # 2. At time t₈₁The MAC entity/HARQ entity may prioritize PUSCH # 2802 over PUSCH # 1801.

The UE (e.g., a MAC entity of the UE) may perform LCP procedure 812 to generate a MAC PDU corresponding to PUSCH # 2802. The MAC entity may transfer the generated MAC PDU to the PHY layer after the LCP procedure 812 is completed.

PHY layer at time t₈₂TB #2 corresponding to the MAC PDU generated in the LCP procedure 812 is received. When the data is at time t₈₃Upon reaching LCH #1, the MAC entity/HARQ entity may then prioritize PUSCH # 1801 over PUSCH # 2802. The UE (e.g., a MAC entity of the UE) may perform LCP procedure 811 to generate a MAC PDU corresponding to PUSCH # 1801.

PHY layer at time t₈₄TB #1 corresponding to the MAC PDU generated in the LCP procedure 811 is received. The PHY layer may check that TB #2 corresponding to PUSCH # 2802 colliding with PUSCH # 1801 has been received from the MAC entity, and the PHY layer may discard the TB #2 at time t₈₂Received TB # 2.

In one embodiment, if a DG indicating a PUSCH duration is received on the PDCCH, and the indicated PUSCH duration partially or completely overlaps in the time domain with an ongoing PUSCH transmission in the same serving cell, the MAC entity/HARQ entity may ignore the prioritization and directly generate a MAC PDU corresponding to the PUSCH duration indicated by the DG. In one embodiment, the DGs may be addressed to C-RNTI, Modulation Coding Scheme Cell RNTI (MCS-C-RNTI), temporary C-RNTI, CS-RNTI or other types of RNTI.

In one embodiment, if the PHY layer receives a MAC PDU/TB from the MAC entity/HARQ entity of the UE after the MAC entity/HARQ entity acquires/generates the MAC PDU/TB from the multiplexing and assembling entity and instructs the PHY layer to perform transmission of the MAC PDU/TB, the PHY layer may check whether the received MAC PDU/TB corresponds to a PUSCH partially or completely overlapping with an ongoing PUSCH transmission in the same serving cell in the time domain. If there is an overlapping PUSCH duration, the PHY layer may immediately cancel (drop/deprioritize/puncture) the ongoing PUSCH transmission. In one embodiment, if the PHY layer receives an UL grant indicating a PUSCH duration that partially or completely overlaps in the time domain with an ongoing PUSCH transmission in the same serving cell, the PHY layer may immediately cancel (drop/deprioritize/puncture) the ongoing PUSCH transmission.

Fig. 9 includes a diagram 900 illustrating a scenario of canceling an ongoing UL transmission according to an example embodiment of the present disclosure. PUSCH # 2902 may correspond to an activated CG or may be scheduled by a DG. In this example, LCH #1(priority 1) and LCH #3(priority 3) are mapped to PUSCH # 1901. LCH #2(priority 2) and LCH #4(priority 4) are mapped to PUSCH # 2902.

Data at time t₉₀To LCH # 2. At time t₉₁The UE may determine that PUSCH # 2902 is prioritized.

The UE may then perform LCP procedure 912 to generate a MAC PDU corresponding to PUSCH # 2902. The MAC entity may transfer the generated MAC PDU to the PHY layer after completing the LCP procedure 912 and instruct the PHY to perform transmission of the generated MAC PDU. PHY layer at time t₉₂TB #2 corresponding to the MAC PDU generated in the LCP procedure 912 is received.

The UE receives a DG scheduling PUSCH #1901 on PDCCH 910. The UE may then determine that PUSCH #1901 overlaps PUSCH # 2902 in the time domain. The prioritization decision between PUSCH #1901 and PUSCH # 2902 may involve case 2-1 through case 2-3.

In one embodiment, PUSCH #1901 may be scheduled for retransmission. The UE may acquire a first set of LCHs from at least one first MAC SDU corresponding to PUSCH # 2902, wherein the at least one first MAC SDU comprises data from the first set of LCHs (e.g., LCH #2 and LCH # 4). The UE may also acquire a second set of LCHs from at least one second MAC SDU corresponding to PUSCH #1901, where the at least one second MAC SDU includes data from the second set of LCHs (e.g., LCH #1 and LCH # 3).

The UE may determine that the second set of LCHs includes an LCH having a highest priority (e.g., LCH #1) among all LCHs in the first and second sets of LCHs. Therefore, the UE may determine that PUSCH #1901 takes precedence over PUSCH # 2902.

In one embodiment, PUSCH #1901 may be scheduled for initial transmission. For example, data at time t₉₃To LCH # 1. The UE may acquire a first set of LCHs from at least one first MAC SDU corresponding to PUSCH # 2902, wherein the at least one first MAC SDU comprises data from the first set of LCHs (e.g., LCH #2 and LCH # 4). The UE may acquire a second set of LCHs (e.g., LCH #1 and LCH #3) having data available for transmission, wherein the data from the second set of LCHs maps to PUSCH #1901 according to LCP restrictions configured for the UE. The UE may determine that the second set of LCHs includes an LCH having a highest priority (e.g., LCH #1) among all LCHs in the first and second sets of LCHs. Therefore, the UE may determine that PUSCH #1901 takes precedence over PUSCH # 2902.

In one embodiment, PUSCH # 2902 may be scheduled by the CG. The UE may determine that a configured grant timer associated with the HARQ process of PUSCH # 2902 is running, and thus determine that PUSCH #1901 takes precedence over PUSCH # 2902.

In one embodiment, the UE may determine that PUSCH #1901 takes precedence over PUSCH # 2902 from a preconfigured time period T1 after PDCCH 910 scheduling PUSCH #1901 ends. The preconfigured time period T1 corresponds to case 3-1.

After prioritizing PUSCH #1901, the UE may perform LCP procedure 911 to generate a MAC PDU corresponding to PUSCH # 1901. PHY layer at time t₉₄TB #1 corresponding to the MAC PDU generated by the LCP procedure 911 is received. The UE (e.g., PHY layer of the UE) may then cancel the ongoing UL transmission on PUSCH # 2902.

In one embodiment, the UE may cancel the ongoing UL transmission on PUSCH # 2902 from a preconfigured time period T1 after PDCCH 910 scheduling PUSCH 1901 ends. The preconfigured time period T1 corresponds to case 3-1.

Fig. 10 is a flow chart of a method 1000 for UL transmission in accordance with an example embodiment of the present disclosure. In act 1002, the UE may perform UL transmission on a first PUSCH duration. In act 1004, the UE may receive a PDCCH scheduling a second PUSCH duration. In act 1006, the UE may determine that the first PUSCH duration overlaps with the second PUSCH duration in the time domain. In act 1008, the UE may determine that the second PUSCH duration is prioritized over the first PUSCH duration. The prioritization decision made in act 1008 may depend on case 2-1 through case 2-3. An embodiment of act 1008 is provided in the flow diagrams shown in fig. 11 and 12.

In act 1010, the UE may cancel an ongoing UL transmission during the first PUSCH duration starting after a preconfigured time period after the PDCCH scheduling the second PUSCH duration ends. The preconfigured time period in act 1010 may be according to scenario 3-1.

Fig. 11 is a flowchart of a method 1100 for prioritizing a second PUSCH duration when scheduled for retransmission according to an example embodiment of the present disclosure. In act 1102, the UE may obtain a first set(s) of LCHs from at least one first MAC SDU corresponding to a first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set(s) of LCHs. In act 1104, the UE may retrieve a second set(s) of LCHs from at least one second MAC SDU corresponding to a second PUSCH duration, wherein the at least one second MAC SDU comprises data from the second set of LCHs. In act 1106, the UE may determine that the second set(s) of LCHs includes the LCH having the highest priority among all LCHs in the first and second sets(s).

Fig. 12 is a flowchart of a method 1200 for prioritizing a second PUSCH duration when scheduled for initial transmission according to an example embodiment of the present disclosure. In act 1202, the UE may obtain a first set (plurality) of LCHs from at least one first MAC SDU corresponding to a first PUSCH duration, wherein the at least one first MAC SDU comprises data from the first set (plurality) of LCHs. In act 1204, the UE may acquire a second set(s) of LCHs having data available for transmission, wherein the data from the second set(s) of LCHs is to be mapped to a second PUSCH duration in accordance with the LCP restrictions configured for the UE. In act 1206, the UE may determine that the second set(s) of LCHs includes the LCH having the highest priority among all LCHs in the first and second sets(s).

Fig. 13 is a block diagram illustrating a node 1300 for wireless communication according to the present disclosure. As shown in fig. 13, node 1300 may include a transceiver 1320, a processor 1328, a memory 1334, one or more presentation components 1338, and at least one antenna 1336. Node 1300 may also include an RF band module, a BS communication module, a network communication module and system communication management module, input/output (I/O) ports, I/O elements, and a power supply (not shown).

Each of the components may communicate with each other, directly or indirectly, over one or more buses 1340. Node 1300 may be a UE or a BS performing the various functions disclosed herein with reference to fig. 1-12.

The transceiver 1320 has a transmitter 1322 (e.g., transmitting/transmitting circuit) and a receiver 1324 (e.g., receiving/receiving circuit), and may be configured to transmit and/or receive time and/or frequency resource partitioning information. The transceiver 1320 may be configured to transmit in different types of subframes and slots including, but not limited to, available, unavailable, and flexibly used subframe and slot formats. The transceiver 1320 may be configured to receive data and control channels.

Node 1300 may include a variety of computer-readable media. Computer readable media can be any available media that can be accessed by node 1300 and includes both volatile and nonvolatile media, removable and non-removable media.

Computer-readable media may include computer storage media and communication media. Computer storage media includes volatile and/or nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or data.

Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Computer storage media does not include a propagated data signal. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.

The term "modulated data signal" may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode data in the signal. Communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.

Memory 1334 may include computer storage media in the form of volatile and/or nonvolatile memory. Memory 1334 may be removable, non-removable, or a combination thereof.

Example memory includes solid state memory, hard disks, optical drives, and the like. As shown in fig. 13, the memory 1334 may store computer-readable, computer-executable instructions 1332 (e.g., software code) configured to cause the processor 1328 to perform the various disclosed functions with reference to fig. 13, with reference to fig. 1-12. Alternatively, the instructions 1332 may not be directly executable by the processor 1328, but be configured to cause the node 1300 (e.g., when compiled and executed) to perform various functions disclosed herein.

The processor 1328 (e.g., with Processing circuitry) may include intelligent hardware devices such as a Central Processing Unit (CPU), microcontroller, ASIC, and the like. The processor 1328 may include a memory.

The processor 1328 may process the data 1330 and the instructions 1332 received from the memory 1334 as well as information sent and received via the transceiver 1320, the baseband communication module, and/or the network communication module. The processor 1328 may also process information to be sent to the transceiver 1320 for transmission via the antenna 1336 to a network communications module for transmission to a core network.

One or more presentation components 1338 present data to a person or another device. Examples of presentation components 1338 include a display device, speakers, a printing component, and a vibrating component.

In view of the present disclosure, it will be apparent that various techniques can be used to implement the concepts in the present disclosure without departing from the scope of these concepts. Moreover, although the concepts have been disclosed with specific reference to certain embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the scope of the concepts.

The described embodiments are, therefore, to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular embodiments disclosed, and that many rearrangements, modifications, and substitutions may be made without departing from the scope of the disclosure.