Method and apparatus for transmission block generation with retransmission for MIMO in wireless communication system

Abstract

Methods, systems, and devices are provided for multiple-input multiple-output (MIMO) transport block generation with retransmission in a wireless communication system, wherein one method includes receiving, from a network node, a first parameter indicating a MIMO layer and a second parameter indicating an uplink (UL) skip having a value higher than four; receiving a first UL grant and a second UL grant on a first physical downlink control channel (PDCCH), wherein the first UL grant is used for retransmission of a first media access control (MAC) protocol data unit (PDU) and the second UL grant is used for a first new transmission; if the first MAC PDU for the first PDCCH is to be retransmitted, generating a second MAC PDU corresponding to a second UL grant indicated by the first PDCCH, where there is no data available for transmission or for any logical channel group; and performing a retransmission of the first MAC PDU using the first UL grant, and performing a first new transmission of the second MAC PDU using the second UL grant.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to U.S. Provisional Patent Application No. 63 / 681,044, filed August 8, 2024, and U.S. Provisional Patent Application No. 63 / 681,054, filed August 8, 2024; each of the applications and publications cited and listed herein is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more specifically, to a method and apparatus for generating transport blocks with retransmissions in multi-input multi-output (MIMO) systems of wireless communication. Background Technology

[0004] With the rapid growth in demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) data packets. This IP data packet communication can provide users of mobile communication devices with IP-bearing voice, multimedia, multicast, and video-on-demand communication services.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). E-UTRAN systems can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing new radio technologies for next-generation technologies (e.g., 5G). Therefore, changes to the current core of the 3GPP standards are currently being submitted and considered to facilitate their evolution and completion. Summary of the Invention

[0006] Methods, systems, and apparatuses for generating transport blocks (TBs) with retransmissions using multiple-input multiple-output (MIMO) are provided, such that, for cases where one TB is used for a new transmission and the other for a retransmission, both TBs are ensured to be available for uplink (UL) spatial multiplexing even if no data is available for transmission.

[0007] In various embodiments, a method for a UE in a wireless communication system includes: receiving from a network node a first parameter indicating a MIMO layer and a second parameter indicating UL skipping, having a value greater than four; receiving a first UL grant and a second UL grant on a first physical downlink control channel (PDCCH), wherein the first UL grant is for retransmission of a first Media Access Control (MAC) Protocol Data Unit (PDU) and the second UL grant is for a first new transmission; generating a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH if the first MAC PDU will be retransmitted, wherein there is no data available for transmission or for any Logical Channel Group (LCG) or in a (data) buffer; and performing a retransmission of the first MAC PDU using the first UL grant and performing a first new transmission of the second MAC PDU using the second UL grant. Attached Figure Description

[0008] Figure 1 A diagram illustrating a wireless communication system according to an embodiment of the present invention is shown.

[0009] Figure 2 This is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention.

[0010] Figure 3 This is a functional block diagram of a communication system according to an embodiment of the present invention.

[0011] Figure 4 This is according to an embodiment of the present invention. Figure 3 Functional block diagram of the program code.

[0012] Figure 5 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes being configured with maxRank>4 and / or maxMIMO-Layers>4 and UL skipping, receiving two UL grants for TTI from a base station, generating two MAC PDUs for TTI when one of the two MAC PDUs is capable of accommodating all available data of the UE, and transmitting the two MAC PDUs to the base station.

[0013] Figure 6 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes being configured with maxRank>4 and / or maxMIMO-Layers>4 and UL skipping, receiving two UL grants for TTI from a base station, generating two MAC PDUs for TTI when one of the two MAC PDUs is to be generated, and transmitting the two MAC PDUs to the base station.

[0014] Figure 7 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes being configured with maxRank>4 and / or maxMIMO-Layers>4 and UL skipping, receiving two UL grants for TTI from a base station, generating two MAC PDUs for TTI and transmitting the two MAC PDUs to the base station when one of the two MAC PDUs is to be generated under a first condition, and generating a single MAC PDU for TTI and transmitting the single MAC PDU to the base station when one of the two MAC PDUs is to be generated under a second condition.

[0015] Figure 8 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes being configured with UL spatial multiplexing and UL skipping, receiving a first UL grant for a new transmission and a second UL grant for a retransmission from a base station for a Time Interruption (TTI), generating a first MAC PDU for a new transmission for a TTI when the UE does not have available data for transmission, and transmitting the first MAC PDU for the new transmission and the second MAC PDU for the retransmission to the base station.

[0016] Figure 9 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes being configured with maxRank>4 or maxMIMO-Layers>4 and UL skipping, receiving a first UL grant from a base station for a new transmission of a first MAC PDU and a retransmission of a second MAC PDU for a HARQ process and / or TTI, generating a first MAC PDU for a new transmission for a HARQ process and / or TTI when the UE does not have available data for transmission, and transmitting the first MAC PDU for a new transmission and the second MAC PDU for a retransmission to the base station.

[0017] Figure 10 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention. The method includes receiving from a network node a first parameter indicating the MIMO layer and a second parameter indicating UL skipping, having a value higher than four; receiving a first UL grant and a second UL grant on a first PDCCH; generating a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH if a first MAC PDU for the first PDCCH will be retransmitted; performing a retransmission of the first MAC PDU using the first UL grant; and performing a first new transmission of the second MAC PDU using the second UL grant. Detailed Implementation

[0018] The invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatus described below. Furthermore, the invention is described primarily in the context of the 3GPP architecture reference model. However, it should be understood that, with the aid of the disclosed information, those skilled in the art can readily adapt and implement aspects of the invention in 3GPP2 network architectures and other network architectures.

[0019] The exemplary wireless communication systems and apparatus described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communication, such as voice and data. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) Radio Access, 3GPP Long Term Evolution Advanced (LTE-A) Radio Access, and 3GPP2 Ultra Mobile Broadband (UMB). 3GPP New Radio (NR), or some other modulation technology.

[0020] Specifically, the exemplary wireless communication systems and apparatus described below can be designed to support one or more standards, such as those provided by the consortium referred to herein as 3GPP, which is named the “Third Generation Partnership Project”, including: [1] 3GPP TS 36.321V15.11.0, “E-UTRA, MAC Protocol Specification”; [2] 3GPP TS 36.331V15.8.0, “E-UTRA, RRC Protocol Specification”; [3] 3GPP TS 38.214V18.2.0, “NR Physical Layer Procedures for Data”; [4] 3GPP TS 38.212V18.2.0, “NR Coding and Multiplexing”; [5] 3GPP TS 38.211V18.2.0, “NR Coding and Multiplexing”; [6] 3GPP TS 36.211V15.8.1, “E-UTRA, Physical Channel and Modulation”; [7] 3GPP TS 36.213V15.8.0, “E-UTRA, Physical Layer Procedure”; [8] 3GPP TS 36.212V15.8.0, “E-UTRA, Multiplexing and Channel Coding”; and [9] 3GPP TS 38.321V18.2.0, “NR MAC Protocol Specification”. The standards and documents listed above are hereby explicitly and fully incorporated herein by reference in their entirety.

[0021] Figure 1 A multiple access wireless communication system according to an embodiment of the present invention is illustrated. Access network 100 (AN) includes multiple antenna groups, one including antennas 104 and 106, another including antennas 108 and 110, and yet another including antennas 112 and 114. Figure 1 In the diagram, only two antennas are shown for each antenna group; however, more or fewer antennas can be used for each antenna group. Access Terminal (AT) 116 communicates with antennas 112 and 114, which transmit information to AT 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, which transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, forward link 120 can use a different frequency than the reverse link 118.

[0022] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with an access terminal in a sector of the area covered by access network 100.

[0023] In communications via forward links 120 and 126, the transmit antennas of access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Furthermore, compared to an access network that transmits to all its access terminals via a single antenna, an access network that uses beamforming to transmit to access terminals randomly distributed throughout its coverage area typically causes less interference to access terminals in adjacent cells.

[0024] An AN can be a fixed station or base station used for communication with a terminal, and can also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. An AT can also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0025] Figure 2 This is a simplified block diagram of an embodiment of the transmitter system 210 (also referred to as the access network) and receiver system 250 (also referred to as the access terminal (AT) or user equipment (UE)) in the MIMO system 200. At the transmitter system 210, service data for multiple data streams is provided from the data source 212 to the transport (TX) data processor 214.

[0026] In one embodiment, each data stream is transmitted via a corresponding transmit antenna. The TX data processor 214 formats, encodes, and interleaves the service data of the data streams based on a specific encoding scheme selected for each data stream to provide encoded data.

[0027] OFDM technology can be used to multiplex the coded data and pilot data of each data stream. The pilot data is typically a known data pattern processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for said data stream are then modulated (e.g., symbol mapping) based on a specific modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for each data stream to provide modulated symbols. The data rate, encoding, and modulation for each data stream can be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0028] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which can further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then... T A modulation symbol stream is provided to N T Transmitters (TMTRs) 222a to 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to symbols of the data stream and the antennas transmitting said symbols therefrom.

[0029] Each transmitter 222 receives and processes a corresponding symbol stream to provide one or more analog signals, and further modulates (e.g., amplifies, filters, and up-converts) the analog signals to provide modulated signals suitable for transmission via a MIMO channel. Then, from N... T Antennas 224a to 224t transmit N from transmitters 222a to 222t. T A modulated signal.

[0030] At receiver system 250, by N R Each antenna 252a to 252r receives the transmitted modulated signal and provides the signal received from each antenna 252 to a corresponding receiver (RCVR) 254a to 254r. Each receiver 254 modulates (e.g., filters, amplifies, and down-converts) the corresponding received signal, digitizes the modulated signal to provide a sample, and further processes the sample to provide a corresponding "received" symbol stream.

[0031] The RX data processor 260 then uses specific receiver processing technology from N R 254 receivers receive and process N R Each received symbol stream provides N T Each detected symbol stream is then demodulated, deinterleaved, and decoded by the RX data processor 260 to recover the service data used for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and TX data processor 214 at the transmitter system 210.

[0032] Processor 270 periodically determines which precoding matrix to use (discussed below). Processor 270 formulates a reverse link message including the matrix index portion and the rank portion.

[0033] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives service data from several data streams from the data source 236), modulated by the modulator 280, regulated by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0034] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Next, processor 230 determines which precoding matrix to use to determine beamforming weights and then processes the extracted message.

[0035] Memory 232 can be used to temporarily store some buffered / calculated data from demodulator 240 or RX data processor 242 via processor 230, some buffered data from 212, or some specific program code. Furthermore, memory 272 can be used to temporarily store some buffered / calculated data from RX data processor 260 via processor 270, some buffered data from 236, or some specific program code.

[0036] Go to Figure 3 This figure illustrates an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. Figure 3 As shown, the communication device 300 in the wireless communication system can be used to achieve... Figure 1 The UE (or AT) 116 and 122 are used, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass received signals to the control circuit 306, and wirelessly output signals generated by the control circuit 306.

[0037] Figure 4 According to an embodiment of the present invention Figure 3The diagram shows a simplified block diagram of program code 312. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 typically performs radio resource control. Layer 2 portion 404 typically performs link control. Layer 1 portion 406 typically performs physical connections.

[0038] For LTE, LTE-A, or NR systems, layer 2, part 404, may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Layer 3, part 402, may include a Radio Resource Control (RRC) layer.

[0039] Any two or more of the following paragraphs, (sub)bullets, points, actions, or claims described in each paragraph or section of the invention may be logically, reasonably, and appropriately combined to form a particular method.

[0040] Any sentence, paragraph, (sub)bullet, point, action, or claim described in each of the following invention paragraphs or sections can be implemented independently and separately to form a particular method or apparatus. Dependencies such as "based on," "more specifically," and "example" in the following invention disclosure are merely one possible embodiment and do not limit the specific method or apparatus.

[0041] In LTE, the MAC in the UE receives UL grant in each TTI, and the HARQ entity identifies the HARQ process for each UL grant. For each HARQ process, the UE obtains a MAC PDU from the multiplexing and combining entity for transmission. When UL grant is available, if there is no uplink data (e.g., MAC SDU) and / or if the MAC PDU contains only MAC CEs (e.g., MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs), the UE may skip UL grant (or not generate a MAC PDU, the so-called uplink skip). The UL transmission procedure is specified in TS 36.321 ([1] 3GPP TS 36.321 V15.11.0) as follows:

[0042] ***********************Quotation begins[1]***********************

[0043] 5.4UL-SCH Data Transmission

[0044] 5.4.1 UL Acceptance

[0045] For transmission on the UL-SCH, the MAC entity must have valid uplink permission (except for non-adaptive HARQ retransmissions), which can be received dynamically on the PDCCH or in a random access response, or can be semi-persistently configured or pre-allocated by the RRC. To execute the requested transmission, the MAC layer receives HARQ information from the lower layer. When the physical layer is configured for uplink spatial multiplexing, the MAC layer can receive up to two permission requests from the lower layer for the same TTI (one per HARQ process).

[0046] If the MAC entity has a C-RNTI, a semi-persistent scheduling C-RNTI, a UL semi-persistent scheduling V-RNTI, an AUL C-RNTI, or a temporary C-RNTI, then the MAC entity will configure for each TTI and for each serving cell belonging to a TAG with a running timeAlignmentTimer, for each grant received for this TTI, and for each SPS indicated by the PDCCH from addressing to the UL semi-persistent scheduling V-RNTI:

[0047] - If the uplink permission for this TTI and this serving cell has already been received on the PDCCH of the C-RNTI or temporary C-RNTI used for the MAC entity; or

[0048] - If uplink permission for this TTI has already been received in the random access response:

[0049] - If uplink grant is used for a C-RNTI of a MAC entity, and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was an uplink grant received by a semi-persistent scheduling C-RNTI for a MAC entity, a UL semi-persistent scheduling V-RNTI for a MAC entity, or the UL HARQ operation is not an autonomous configured uplink grant:

[0050] - Regardless of the value of NDI, NDI is considered to have been switched for use in the corresponding HARQ process.

[0051] - Deliver the uplink grant and associated HARQ information to the HARQ entity used for this TTI.

[0052] …

[0053] 5.4.2 HARQ Operation

[0054] 5.4.2.1 HARQ Entities

[0055] At the MAC entity of each serving cell with a configured uplink, there is a HARQ entity that maintains several parallel HARQ processes to allow transmissions to continue while waiting for HARQ feedback on whether previous transmissions were successfully received.

[0056] The number of parallel HARQ processes per HARQ entity is specified in Clause 8 of TS 36.213. NB-IoT has one or two UL HARQ processes.

[0057] When the physical layer is configured for uplink spatial multiplexing, as specified in TS 36.213, there are two HARQ processes associated with a given TTI. Alternatively, there is one HARQ process associated with a given TTI.

[0058] Given a TTI, if uplink permission is indicated for the TTI, the HARQ entity identifies the HARQ process that should be performed. It will also route the received HARQ feedback (ACK / NACK information), MCS, and resources via physical layer relay to the appropriate HARQ process.

[0059] …

[0060] For each TTI, the HARQ entity will:

[0061] - Identify the HARQ process associated with this TTI, and for each identified HARQ process:

[0062] -If uplink permission has already been indicated for this process and this TTI, then:

[0063] - If the received provisional C-RNTI is not addressed to the PDCCH, and if the NDI provided in the associated HARQ information has been switched compared to the value previously transmitted in this HARQ process; or

[0064] - If uplink permission is received on the PDCCH of C-RNTI, and the HARQ buffer of the identified process is empty; or

[0065] …

[0066] Otherwise, if the MAC entity is configured with a semiPersistSchedIntervalUL of less than 10 subframes, and if uplink permission is configured to be granted, and if the HARQ buffer of the identified HARQ process is not empty, and if the HARQ_FEEDBACK of the identified HARQ process is NACK; or if the MAC entity is configured with an ul-SchedInterval of less than 10 subframes, and if uplink permission is pre-allocated uplink permission, and if the HARQ buffer of the identified HARQ process is not empty, and if the HARQ_FEEDBACK of the identified HARQ process is NACK:

[0067] - Indicates that the identified HARQ process generates non-adaptive retransmissions.

[0068] -otherwise:

[0069] …

[0070] - Obtain the MAC PDU (if it exists) from the "Multiplexing and Combining" entity for transmission;

[0071] -If the MAC PDU for transmission has already been obtained, then:

[0072] -Deliver MAC PDU, uplink permission, and HARQ information to the identified HARQ process;

[0073] - Indicates that the identified HARQ process triggers a new transfer.

[0074] -otherwise:

[0075] - Clear the HARQ buffer of the identified HARQ process.

[0076] -otherwise:

[0077] …

[0078] - Deliver uplink permission and HARQ information (redundant version) to the identified HARQ process;

[0079] - If the ULHARQ operation is autonomous for the identified HARQ process, and if uplink permission is configured by UL permission:

[0080] - Indicates that the identified HARQ process generates non-adaptive retransmissions.

[0081] -otherwise:

[0082] - Indicates that the identified HARQ process generates adaptive retransmissions.

[0083] …

[0084] Each HARQ process is associated with a HARQ buffer.

[0085] For synchronous HARQ, each HARQ process maintains a status variable CURRENT_TX_NB, which indicates the number of transfers made for the MAC PDU currently in the buffer, and a status variable HARQ_FEEDBACK, which indicates the HARQ feedback for the MAC PDU currently in the buffer. When a HARQ process is established, CURRENT_TX_NB should be initialized to 0.

[0086] …

[0087] Perform a new transmission on the resource and using the MCS indicated on the PDCCH or random access response. Perform an adaptive retransmission on the resource (if available) and using the MCS indicated on the PDCCH. Perform a non-adaptive retransmission on the same resource and using the same MCS used for the last transmission attempt.

[0088] …

[0089] If a HARQ entity requests a new transfer, then the HARQ process will:

[0090] -If the UL HARQ operation is synchronous, then:

[0091] - Set CURRENT_TX_NB to 0;

[0092] - Set HARQ_FEEDBACK to NACK;

[0093] - Set CURRENT_IRV to 0;

[0094] -otherwise:

[0095] -If the UL HARQ operation is autonomously asynchronous:

[0096] - Set HARQ_FEEDBACK to NACK.

[0097] -If uplink addressing to AUL C-RNTI is permitted:

[0098] - Set CURRENT_IRV to 0.

[0099] -otherwise:

[0100] - Set CURRENT_IRV to the index corresponding to the redundant version value provided in the HARQ information;

[0101] - Store the MAC PDU in the associated HARQ buffer;

[0102] - Store uplink permissions received from HARQ entities;

[0103] - Generate and transmit as described below.

[0104] If a HARQ entity requests a retransmission, then the HARQ process will:

[0105] -If the UL HARQ operation is synchronous, then:

[0106] -Increment CURRENT_TX_NB by 1;

[0107] -If HARQ entity requests adaptive retransmission, then:

[0108] - Store uplink permissions received from HARQ entities;

[0109] - Set CURRENT_IRV to the index corresponding to the redundant version value provided in the HARQ information;

[0110] -If the UL HARQ operation is synchronous; or

[0111] -If UL HARQ operation is autonomous:

[0112] - Set HARQ_FEEDBACK to NACK;

[0113] - Generate and transmit as described below.

[0114] Otherwise, if the HARQ entity requests a non-adaptive retransmission, then:

[0115] - If the UL HARQ operation is asynchronous or HARQ_FEEDBACK = NACK, then:

[0116] - If skipUplinkTxSPS and fixedRV-NonAdaptive are configured, and the uplink permission for the initial transmission of this HARQ process is granted to the configured permission, and the UL HARQ operation is not autonomous; or

[0117] -If the uplink permission is a pre-allocated uplink permission:

[0118] - Set CURRENT_IRV to 0;

[0119] -Otherwise, if the UL HARQ operation is autonomous:

[0120] - Set CURRENT_IRV to the index corresponding to the redundant version value selected by the UE implementation scheme.

[0121] - Generate and transmit as described below.

[0122] Note 1: When receiving a HARQ ACK alone, the MAC entity keeps the data in the HARQ buffer.

[0123] …

[0124] Note 3: For asynchronous HARQ operations, except for retransmissions within a bundle, UL retransmissions are only triggered by adaptive retransmission.

[0125] In order to generate a transmission, the HARQ process will:

[0126] -If a MAC PDU is obtained from the Msg3 buffer; or

[0127] - If the side link discovery gap used for transmission is not configured by the upper layer, and there is no measurement gap during transmission, and in the case of retransmission, the retransmission does not conflict with the transmission of the MAC PDU obtained from the Msg3 buffer in this TTI; or

[0128] …

[0129] - Instructs the physical layer to allow transmission based on the stored uplink, where the redundant version corresponds to the CURRENT_IRV value;

[0130] - If the UL HARQ operation is not autonomous, increment CURRENT_IRV by 1;

[0131] - If the UL HARQ operation is synchronous, and there is a measurement gap or sidelink discovery gap for receiving when receiving HARQ feedback for this transmission, and if a MAC PDU is not obtained from the Msg3 buffer, then:

[0132] - When receiving a HARQ response for this transmission, set HARQ_FEEDBACK to ACK.

[0133] After performing the above actions, if the UL HARQ operation is synchronous, then the HARQ process will:

[0134] -If CURRENT_TX_NB = maximum number of transmissions - 1, then:

[0135] - Clear the HARQ buffer;

[0136] …

[0137] 5.4.3 Multiplexing and Combining

[0138] 5.4.3.1 Logical Channel Prioritization

[0139] When a new transmission is executed, a logical channel priority sorting procedure is applied.

[0140] RRC controls the scheduling of uplink data for each logical channel by transmitting the following: an increased priority value indicating a lower priority, a prioritized BitRate setting the Prioritized Bit Rate (PBR), a bucketSizeDuration setting the Bucket Size Duration (BSD), and optionally, allowedTTI-Lengths setting the allowed TTI lengths. For NB-IoT, the prioritized BitRate, bucketSizeDuration, and the corresponding steps of the logical channel prioritization procedure (i.e., steps 1 and 2 below) do not apply.

[0141] The MAC entity should maintain a variable Bj for each logical channel j. Bj should be initialized to zero when the relevant logical channel is established and incremented by the product PBR × TTI duration for each TTI, where PBR is the priority bit rate of logical channel j. However, the value of Bj must never exceed the bucket size, and if the value of Bj is greater than the bucket size of logical channel j, it should be set to the bucket size. The bucket size of a logical channel is equal to PBR × BSD, where PBR and BSD are configured by the upper layer.

[0142] When a new transmission is performed on a UL grant with a specific TTI length, the MAC entity will execute the following logical channel priority ordering procedure:

[0143] - The MAC entity will allocate resources to logical channels that allow transmission using the permitted TTI length according to the following steps:

[0144] - Step 1: All allowed logical channels with Bj > 0 are allocated resources in decreasing priority order. If the PBR of a logical channel is set to "infinity", then the MAC entity will allocate resources for all data available for transmission on the logical channel before satisfying the PBR of the lower priority logical channel;

[0145] -Step 2: The MAC entity will reduce the total size of the MAC SDU that served logical channel j in step 1 by Bj;

[0146] Note 1: The value of Bj can be negative.

[0147] Step 3: If any resources remain, serve all allowed logical channels in strict descending order of priority (regardless of the value of Bj) until the data or UL permission for said logical channel is exhausted, whichever comes first. Logical channels configured with the same priority should be provided equally.

[0148] - The UE will also follow the following rules during the above scheduling procedure:

[0149] - If the entire SDU (or a partially transmitted SDU or a retransmitted RLC PDU) is fitted into the remaining resources of the associated MAC entity, then the UE should not segment the RLC SDU (or a partially transmitted SDU or a retransmitted RLC PDU).

[0150] - If the UE segments the RLC SDU from the logical channel, it will maximize the size of the segment to fill as much of the permission of the associated MAC entity as possible;

[0151] - The UE should maximize data transmission.

[0152] - If a MAC entity is given a UL allowance size equal to or greater than 4 bytes and has data available for transmission, then the MAC entity will not transmit only padding BSR and / or padding (unless the UL allowance size is less than 7 bytes and an AMD PDU fragment needs to be transmitted).

[0153] - For transmissions on the serving cell operating according to frame structure type 3, the MAC entity will only consider the logical channels that have been configured in laa-UL-Allowed;

[0154] - If a logical channel is already configured with lch-CellRestriction and if PDCP replication (i.e., CA replication) within the same MAC entity is activated, then for this logical channel, the MAC entity should consider restricting the cell indicated by lch-CellRestriction for transmission.

[0155] - For NB-IoT UEs, BL UEs, or UEs in enhanced coverage, if edt-SmallTBS-Enabled is set to true for the corresponding PRACH resource, then the UE should select a TB size from the set of possible TB sizes, as described in clauses 8.6.2 and 16.3.3 of TS 36.213.

[0156] The MAC entity will not transmit data corresponding to the logical channel of a suspended radio bearer (the conditions for when a radio bearer is considered suspended are defined in TS 36.331).

[0157] If a MAC PDU contains only a MAC CE for filling a BSR or a periodic BSR with zero MAC SDUs and no non-periodic CSI is required for this TTI, as specified in TS 36.213, then the MAC entity will not generate a MAC PDU for the HARQ entity in the following cases:

[0158] -If the MAC entity is configured with skipUplinkTxDynamic and the permission indicated to the HARQ entity is to address to C-RNTI; or

[0159] - In cases where the MAC entity is configured with skipUplinkTxSPS and the permission indicated to the HARQ entity is a configured uplink permission activated by the MAC entity's semi-persistent scheduling C-RNTI or by the MAC entity's UL semi-persistent scheduling V-RNTI; or

[0160] - In the case where the permission indicated to the HARQ entity is a configured uplink permission activated by the MAC entity's AUL C-RNTI.

[0161] Note 1a: If at least one MAC PDU will be generated for the HARQ entity used for this TTI, the MAC entity generates a MAC PDU corresponding to all UL grants indicated to the HARQ entity for this TTI.

[0162] …

[0163] Note 2: When a requesting MAC entity transmits multiple MAC PDUs in a TTI, steps 1 to 3 and the associated rules can be applied independently to each grant or to the sum of the granted capacities. Furthermore, the processing order of grants depends on the UE implementation scheme. The UE implementation scheme determines which MAC PDU contains the MAC control element when a requesting MAC entity transmits multiple MAC PDUs in a TTI. When a requesting UE generates MAC PDUs in two MAC entities within a TTI, the processing order of grants depends on the UE implementation scheme.

[0164] 5.4.3.2 Multiplexing of MAC Control Elements and MAC SDUs

[0165] The MAC entity will use the MAC control element and MACSDU in the multiplexed MAC PDU according to Clauses 5.4.3.1 and 6.1.2.

[0166] ************************End of quotation*************************

[0167] In addition, the configuration for uplink skipping can be provided by RRC, as specified in TS 36.331 ([2] 3GPP TS36.331V15.8.0) as follows:

[0168] ***********************Quotation begins[2]************************

[0169] The IE MAC-MainConfig is used to specify the main MAC configuration for signaling and data radio bearers. All main MAC configuration parameters can be configured independently for each cell group (i.e., MCG or SCG) unless otherwise explicitly specified.

[0170]

[0171]

[0172]

[0173] ************************End of quotation*************************

[0174] UL spatial multiplexing is introduced to improve UL data rates. Multiple layers with different data can be transmitted on the same time / frequency resources (e.g., resource elements or resource blocks), for example, by mapping multiple layers to multiple antenna elements or multiple antenna ports. In the case of UL spatial multiplexing, current UL transmissions for TTI (e.g., subframes) may support up to four layers and up to two transport blocks (codewords). When an uplink transmission mode, such as uplink transmission mode 2, is configured, the UE can utilize UL spatial multiplexing. PDCCH or DCI can be used to enable or disable spatial multiplexing. For example, a DCI format associated with a single antenna port (e.g., DCI format 0) can be used to disable spatial multiplexing. When the UE receives a DCI format associated with a single antenna port, the UE will perform the corresponding PUSCH transmission without spatial multiplexing (with a single antenna port). PUSCH transmissions without spatial multiplexing consist of a single transport block (or a single codeword). A DCI format associated with spatial multiplexing (e.g., DCI format 4) can be used to enable spatial multiplexing. When the UE receives a DCI format associated with spatial multiplexing, the UE will perform a corresponding PUSCH transmission with spatial multiplexing (with multiple antenna ports). A PUSCH transmission with spatial multiplexing may include a single transport block (single codeword) or two transport blocks (two codewords). Information carried on the DCI format associated with spatial multiplexing can be used to disable the transport block of the corresponding PUSCH transmission. Information carried on the DCI format associated with spatial multiplexing can be used to notify the UE that the corresponding PUSCH transmission includes a single transport block (one transport block enabled, one transport block disabled) or two transport blocks (both transport blocks enabled). For example, the resource block assignment field and modulation and coding scheme field associated with the transport block in the DCI format associated with spatial multiplexing can be used to inform the UE whether the transport block is enabled or disabled (e.g., if I send IMCS =0 and N PRB Combinations > 1 or I MCS =28 and N PRB =1 combination, then the transport block is disabled. Further details related to spatial multiplexing are specified in the standards [6] 3GPP TS 36.211V15.8.1, [7] 3GPP TS 36.213V15.8.0 and [8] 3GPP TS36.212V15.8.0, as given below:

[0175] ***********************Quotation begins[6]************************

[0176] 5.3.2A.2 Layer mapping for spatial multiplexing

[0177] For spatial multiplexing, layer mapping will be performed according to Table 5.3.2A.2-1. The number of layers υ is less than or equal to the number of antenna ports P used for physical uplink shared channel transmission. Mapping a single codeword to multiple layers can only be applied when the number of antenna ports used for PUSCH is four, except for slot-PUSCH and subslot-PUSCH transmissions using a single codeword regardless of the number of layers.

[0178] Table 5.3.2A.2-1: Codeword-to-Layer Mapping for Spatial Multiplexing

[0179]

[0180] ************************End of quotation*************************

[0181] **************************Citation begins[7]*********************

[0182] 8. Physical uplink shared channel related procedures

[0183] …

[0184] If the UE is configured by the higher layer to decode the PDCCH using CRC scrambled by C-RNTI, then the UE will decode the PDCCH according to the combination defined in Table 8-3, and transmit the corresponding PUSCH in the case of generating a transport block corresponding to the HARQ process for PUSCH transmission... The scrambling initialization of this PUSCH corresponding to these PDCCHs and the PUSCH retransmission for the same transport block are done through C-RNTI.

[0185] ************************End of quotation*************************

[0186] **************************Citation begins[8]**********************

[0187] 5.3.3.1.8 Format 4

[0188] DCI format 4 is used to schedule PUSCH in a UL cell under multi-antenna port transmission mode.

[0189] …

[0190] Additionally, for transport block 1:

[0191] -Modulation and coding schemes and redundancy versions-5-bit...

[0192] -New data indicator-1 bit

[0193] Additionally, for transport block 2:

[0194] -Modulation and coding schemes and redundancy versions-5-bit...

[0195] -New data indicator-1 bit

[0196] *************************End of quotation************************

[0197] In NR, there are two main types of transmission schemes: book-based and non-book-based. The main difference lies in whether the data stream is pre-coded through multiple antenna ports using entries from a defined book (e.g., entries explicitly indicated by the base station). Furthermore, UL transmission can target one or more UL beams and / or one or more TRPs, which can be equivalent to or represented by SRI and / or TCI states and / or CORESET pools (indexes) and / or SRS resource sets and / or TA groups. 8Tx is introduced to improve data rates and increase reliability. By placing a larger number of antennas, the UE can transmit dual codewords to the base station via the same time-frequency resources. The transmission scheme and / or the number of TB / codewords used will be subject to indication from the base station, for example, via RRC configuration and / or DCI indication and / or the DCI format used. The following section quotes further details about UL transmission schemes for NR and 8Tx from [3] 3GPP TS 38.214V18.2.0, [4] 3GPP TS 38.212V18.2.0, [5] 3GPP TS 38.211V18.2.0 and [9] 3GPP TS 38.321V18.2.0:

[0198] *************************Beginning of quotation[3]***********************

[0199] 6.1 UE program for transmitting physical uplink shared channel

[0200] PUSCH transmissions can be dynamically scheduled by UL grants in the DCI, or the transmissions can correspond to configured grant type 1 or type 2. Configured grant type 1 PUSCH transmissions are semi-statically configured to operate upon receiving a higher-layer parameter `configuredGrantConfig` containing `rrc-ConfiguredUplinkGrant`, without detecting UL grants in the DCI. Upon receiving a higher-layer parameter `configuredGrantConfig` without `rrc-ConfiguredUplinkGrant`, configured grant type 2 PUSCH transmissions are semi-persistently scheduled by a validly active UL grant in the DCI according to clause 10.2 of [TS 38.213]. If `configuredGrantConfigToAddModList` is configured, more than one configured grant type 1 and / or configured grant type 2 can be simultaneously active on the BWP during the serving cell's startup.

[0201] The UE can be configured with a list of up to 64 TCI-UL-State configurations within the higher-layer parameter BWP-UplinkDedicated. Each TCI-UL-State configuration contains parameters for configuring a reference signal, and where applicable, for determining the UL TX spatial filter for dynamically granted and configured-granted PUSCH and PUCCH resources in CC, as well as SRS.

[0202] …

[0203] The UE should transmit the corresponding PUSCH as indicated by the DCI upon detecting a PDCCH with a configured DCI format of 0_0, 0_1, 0_2, or 0_3, unless the UE does not generate a transport block as described in [TS 38.321]. Upon detecting a DCI format of 0_1 or 0_2 with a 'UL-SCH indicator' set to '0' and a non-zero 'CSI request', wherein for all CSI reports triggered by the 'CSI request' in this DCI format 0_1 ​​or 0_2, the associated reportQuantity in CSI-ReportConfig is set to 'None', the UE ignores all fields in this DCI except for the 'CSI request', and the UE should not transmit the corresponding PUSCH indicated by this DCI format 0_1 ​​or 0_2. Upon detecting a DCI format 0_3 with a 'UL-SCH indicator' set to '0' and a non-zero 'CSI request', where the associated reportQuantity in CSI-ReportConfig is set to 'None' for all CSI reports triggered by the 'CSI request' in this DCI format 0_3, the UE ignores all fields in this DCI for the scheduled cell with the minimum serving cell index, except for the 'CSI request', and the UE should not transmit the corresponding PUSCH on the serving cell with the minimum serving cell index indicated by this DCI format 0_3.

[0204] …

[0205] For the uplink, the UE supports 16 HARQ processes per cell, or up to 32 HARQ processes per cell, depending on the UE's capabilities, as defined in [TS 38.306]. The higher-layer parameter nrofHARQ-ProcessesForPUSCH or nrofHARQ-ProcessesForPUSCH-r17 configures the number of most frequently used uplink processes for the UE for each cell. When no configuration is provided, the UE can use the default number of 16 processes.

[0206] 6.1.1 Transmission Scheme

[0207] For PUSCH, two transmission schemes are supported: book-based transmission and non-book-based transmission. When the higher-layer parameter txConfig in pusch-Config is set to 'book', book-based transmission is used to configure the UE; when txConfig is set to 'non-book', non-book-based transmission is used. If the higher-layer parameter txConfig is not configured, the UE is not expected to be scheduled by DCI format 0_1, 0_2, or 0_3. If PUSCH is scheduled using DCI format 0_0, then PUSCH transmission is based on a single antenna port. …

[0208] 6.1.1.1 Codebook-based UL transmission

[0209] For codebook-based transmissions, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 0_3, or semi-statically configured to operate according to clause 6.1.2.3. If this PUSCH is scheduled by DCI format 0_1, DCI format 0_2, or semi-statically configured to operate according to clause 6.1.2.3, then the UE determines its PUSCH transport precoder based on SRI, TPMI, and transport class, wherein SRI, TPMI, and transport class for DCI formats 0_1 and 0_2 are given by one or two SRS resource indicators and one or two DCI fields of precoding information and layer number in clauses 7.3.1.1.2 and 7.3.1.1.3 of [TS 38.212], or by srs-ResourceIndicator and precodingAndNumberOfLayers according to clause 6.1.2.3, or by srs-ResourceIndicator, srs-ResourceIndicator2, precodingAndNumberOfLayers, and precodingAndNumberOfLayers2 according to clause 6.1.2.3. …

[0210] For codebook-based transmissions with two or four antenna ports, the UE determines its codebook subset based on TPMI and based on the higher-layer parameter codebookSubset received in the push-Config for the PUSCH associated with DCI format 0_1 ​​or 0_3 and the higher-layer parameter codebookSubsetDCI-0-2 received in the push-Config for the PUSCH associated with DCI format 0_2. The DCI format may be configured as 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' depending on the UE's capability for two or four antenna ports.

[0211] For codebook-based transmission with eight antenna ports, depending on the UE capability, the UE determines its codebook based on the higher-layer parameter CodebookTypeUL in the pusch-Config received for the PUSCH associated with DCI formats 0_1 and 0_2. According to the configured CodebookTypeUL, coherent UL MIMO operation is applicable within the antenna port groups defined as in Table 6.3.1.5-8 of [TS 38.211].

[0212] …

[0213] The maximum delivery level can be configured via the higher-level parameter maxRank or maxRank-n8 in the pusch-Config for PUSCHs scheduled in DCI format 0_1 ​​or 0_3, and the higher-level parameter maxRankDCI-0-2 for PUSCHs scheduled in DCI format 0_2.

[0214] 6.1.1.2 UL Transmission Based on Non-Codebook

[0215] For non-codebook-based transmissions, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or DCI format 0_3, or semi-statically configured to operate according to clause 6.1.2.3. If this PUSCH is scheduled or semi-statically configured to operate according to clause 6.1.2.3 by DCI format 0_1, DCI format 0_2, or DCI format 0_3, the UE may determine its PUSCH precoder and delivery class based on the SRI when multiple SRS resources are configured, wherein the SRI is given by one or both SRS resource indicators in the DCI according to clauses 7.3.1.1.2 and 7.3.1.1.3 of [38.212] for DCI format 0_1 ​​and DCI format 0_2, or the SRI is given by one SRS resource indicator in the DCI according to clause 7.3.1.1.4 of [38.212] for DCI format 0_3, or the SRI is given by srs-ResourceIndicator according to clause 6.1.2.3, or the SRI is given by srs-ResourceIndicator and srs-ResourceIndicator2 according to clause 6.1.2.3.

[0216] …

[0217] When the UE is configured with a higher-layer parameter txConfig set to 'non-codebook', the UE is configured with at least one SRS resource. Each of the one or two SRIs indicated in slot n is associated with the most recent transmission of an SRS resource in the associated SRS resource set identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI. When two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher-layer parameter usage set to 'non-codebook' in the SRS-ResourceSet, the UE is not expected to have a different number of SRS resources configured in the two SRS resource sets.

[0218] …

[0219] The UE shall transmit PUSCH using the same antenna port as the SRS port in the SRS resource indicated by the SRI given by DCI format 0_1 ​​or 0_2 or according to clause 6.1.2.3 of configuredGrantConfig, where the SRS port of the (i+1)th SRS resource in the SRS resource set is indexed as p. i =1000+i.

[0220] DM-RS antenna port in Clause 6.4.1.1.3 of [TS 38.211] It is determined according to the order of the DM-RS ports given in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 in Clause 7.3.1.1.2 of [TS 38.212].

[0221] …

[0222] 5.1.3.2 Determining the Transport Block Size

[0223] In the PDSCH-config, the higher-level parameter maxNrofCodeWordsScheduledByDCI indicates that two-codeword transmission is enabled, if for the corresponding transport block I MCS =26 and rv id =1, then one of the two transport blocks is disabled by DCI format 1_1 or 1_3. When the higher-level parameter maxNrofCodeWordsScheduledByDCI in pdsch-ConfigMulticast indicates that two-codeword transmission is enabled, if for the corresponding transport block I... MCS =26 and rv id =1, then one of the two transport blocks is disabled by DCI format 4_2. When the UE is configured with the higher-layer parameter pdsch-TimeDomainAllocationListForMultiPDSCH, if for all scheduled PDSCH corresponding transport blocks I MCS =26 and rv id =2, then all first or second transport blocks of scheduled PDSCHs are disabled by DCI format 1_1. If both transport blocks are enabled, transport blocks 1 and 2 are mapped to codewords 0 and 1, respectively. If only one transport block is enabled, the enabled transport block is always mapped to the first codeword.

[0224] ************************End of quotation************************* *************************Beginning of quotation[4]***********************

[0225] 7.3.1.1 DCI Format for PUSCH Scheduling

[0226] 7.3.1.1.1 Format 0_0

[0227] …

[0228] - Modulation and coding scheme - 5 bits, as defined in Clause 6.1.4.1 of [TS 38.214].

[0229] -New data indicator-1 bit

[0230] -Redundant version- 2 digits, as defined in Table 7.3.1.1.1-2

[0231] -HARQ process number-4 digits

[0232] - 2 bits for TPC commands used with scheduled PUSCH, as defined in Clause 7.1.1 of [TS 38.213].

[0233] …

[0234] 7.3.1.1.2 Format 0_1

[0235] …

[0236] For transport block 1:

[0237] - Modulation and coding scheme - 5 bits, as defined in Clause 6.1.4.1 of [TS 38.214].

[0238] -New Data Indicator-…

[0239] -Redundant version--Number of bits…

[0240] For transport block 2 (exists only if maxRank-n8 is configured or maxMIMO-Layers-n8 is configured):

[0241] - Modulation and coding scheme - 5 bits, as defined in Clause 6.1.4.1 of [TS 38.214].

[0242] -New data indicator-1 bit

[0243] -Redundant version- 2 digits, as defined in Table 7.3.1.1.1-2

[0244] …

[0245] -HARQ Process Number- If the higher-level parameter harq-ProcessNumberSizeDCI-0-1 is configured, then it is 5 bits; otherwise, it is 4 bits.

[0246] …

[0247] -SRS Resource Indicator- The number of bits is determined as follows:

[0248] - According to Table 7.3.1.1.2-28 / 28A / 29 / 29B / 30 / 30B / 31 / 31B / 31C / 31D / 31E / 31F, provided that the higher-level parameter txConfig = nonCodebook,...

[0249] - According to Tables 7.3.1.1.2-32, 7.3.1.1.2-32A, and 7.3.1.1.2-32B, the prerequisite is that the higher-level parameter txConfig = codebook, where…

[0250] -Second SRS Resource Indicator- The number of bits is determined as follows:

[0251] - In the case of the same number of layers indicated by the SRS resource set indicator field, according to Tables 7.3.1.1.2-28 / 29A / 30A / 31A, provided that the higher-layer parameter txConfig = nonCodebook, the higher-layer parameter maxMIMO-LayersforSdm is not configured, and the SRS resource set indicator field exists, where N SRS It is the number of configured SRS resources in the second SRS resource set, ...

[0252] - According to Table 7.3.1.1.2-28 / 29, the prerequisites are that the higher-level parameter txConfig = nonCodebook, the higher-level parameter maxMIMO-LayersforSdm is configured, and the SRS resource set indicator field exists…

[0253] Otherwise, it is 0.

[0254] -Number of precoding information and layers--The number of bits is determined by the following:

[0255] - If the higher-level parameter txConfig = nonCodeBook, then 0 bits;

[0256] - For a single antenna port and if the higher-level parameter txConfig = codebook, 0 bits;

[0257] -4, 5, or 6 bits, according to Table 7.3.1.1.2-2 for 4 antenna ports, provided that txConfig = codebook, ul-FullPowerTransmission is not configured or is configured to fullpowerMode2 or is configured to fullpower, the transformation precoder is disabled, and the values ​​of the higher-level parameters maxRank (if multipanelScheme is not configured) or max{maxRank,maxRankSfn} (if multipanelScheme = sfnScheme) or max{maxRank,maxRankSdm} (if multipanelScheme = sdmScheme) and codebookSubset;

[0258] …

[0259] - According to Table 7.3.1.1.2-5B for 8 antenna ports, if CodebookTypeUL = Codebook1, the transformation precoder is disabled, maxRank-n8 = 8, and according to ULcodebookFC-N1N2, 7 bits;

[0260] - According to Table 7.3.1.1.2-5C for 8 antenna ports, if CodebookTypeUL = Codebook1, the transformation precoder is disabled, maxRank-n8 = 7, and according to ULcodebookFC-N1N2, 7 bits;

[0261] - According to Table 7.3.1.1.2-5D for 8 antenna ports, if CodebookTypeUL = Codebook1, the transformation precoder is disabled, maxRank-n8 = 4, 5 or 6, and according to maxRank-n8, 7 bits;

[0262] - According to Table 7.3.1.1.2-5E for 8 antenna ports, if CodebookTypeUL = Codebook1, the transformation precoder is enabled, or if the transformation precoder is disabled, maxRank = 1, 2 or 3, and depending on the transformation precoder and maxRank, 4, 6 or 7 bits;

[0263] …

[0264] -Second precoding information--Number of bits…

[0265] -Antenna Port--Number of Bits…

[0266] ************************End of quotation*************************

[0267] *************************Citation begins[5]*********************

[0268] 6.3.1 Physical Uplink Shared Channel

[0269] 6.3.1.1 Scrambling

[0270] Up to two codewords q∈{0,1} can be transmitted. In the case of single codeword transmission, q=0.

[0271] For each codeword, bit block Scrambling should be applied before modulation, where These are the bits in the codeword q transmitted over the physical channel, from which the scrambling bit block is obtained according to the following pseudocode.

[0272] …

[0273] 6.3.1.3 Layer Mapping

[0274] According to Table 7.3.1.3-1, the complex-valued modulation symbols used for each of the codewords to be transmitted should be mapped to at most four layers. The complex-valued modulation symbols used for codeword q... It should be mapped to layer x(i) = [x (0) (i) … x (v-1) (i)] T superior, Where υ is the number of layers, and It is the number of modulation symbols per layer.

[0275] …

[0276] 6.3.1.5 Precoding

[0277] Vector block [y (0) (i) … y (υ-1) (i)] T It should be precoded according to the following formula

[0278]

[0279] in Antenna port set {p0,…,p ρ-1 It should be determined according to the procedure in [TS38.214].

[0280] For non-codebook-based transmission, the precoding matrix W is equal to the identity matrix.

[0281] For codebook-based transmission, the precoding matrix W depends on the number of antenna ports used for transmission:

[0282] ●For single-layer transmission on a single antenna port, W = 1;

[0283] ● For transmissions using 2 or 4 antenna ports, W is given in Tables 6.3.1.5-1 to 6.3.1.5-7;

[0284] ● For transmission using 8 antenna ports, W is given by the following formula.

[0285] W f(i) =W′ i

[0286] ●Among them

[0287] - The subscripts i and f(i) represent the rows of the corresponding matrix;

[0288] -f(i) is given in Table 6.3.1.5-8;

[0289] - The intermediate precoding matrix W′ is given in Tables 6.3.1.5-9 to 6.3.1.5-24, 6.3.1.5-29 to 6.3.1.5-36, and 6.3.1.5-39 to 6.3.1.5-47, where 0 m×n This represents a zero matrix with m rows and n columns;

[0290] - Submatrix The details are given in Tables 6.3.1.5-25 to 6.3.1.5-28 and 6.3.1.5-37 to 6.3.1.5-38.

[0291] The TPMI index used in the table above is obtained from the DCI or higher-layer parameters of the scheduling uplink transmission according to the procedure in [TS 38.214].

[0292] When the higher-level parameter txConfig is not configured, the precoding matrix W = 1.

[0293] Table 6.3.1.5-1: Precoding matrix W for single-layer transmission using two antenna ports.

[0294]

[0295] Table 6.3.1.5-2: Precoding matrix W for single-layer transmission using four antenna ports with transform precoding enabled.

[0296]

[0297] Table 6.3.1.5-5: Precoding matrix W used for two-layer transmission with four antenna ports when transform precoding is disabled.

[0298]

[0299]

[0300] Table 6.3.1.5-8: Port mapping function f(i) for transmission using 8 antenna ports.

[0301]

[0302] Table 6.3.1.5-9: Intermediate precoding matrix W′ for codebook1 = ng1n4n1 and single-layer transmission using eight antenna ports.

[0303]

[0304] Table 6.3.1.5-12: Intermediate precoding matrix W′ for codebook1 = ng1n4n1 and four-layer transmission using eight antenna ports with transform precoding disabled.

[0305]

[0306] Table 6.3.1.5-14: Intermediate precoding matrix W′ for codebook1 = ng1n4n1 and six-layer transmission using eight antenna ports with transform precoding disabled.

[0307]

[0308] Table 6.3.1.5-16: Intermediate precoding matrix W′ for codebook1 = ng1n4n1 and eight-layer transmission using eight antenna ports with transform precoding disabled.

[0309]

[0310] ************************End of quotation************************* *************************Beginning of quotation[9]**********************

[0311] 5.4UL-SCH Data Transmission

[0312] 5.4.1 UL Acceptance

[0313] Uplink grants are dynamically received on the PDCCH in a random access response, configured semi-persistently via RRC, or determined to be associated with the PUSCH resource of the MSGA, as specified in Clause 5.1.2a. The MAC entity will enable the uplink grant to be transmitted on the UL-SCH. To perform the requested transmission, the MAC layer receives HARQ information from the lower layer. Uplink grants addressed to CS-RNTI with NDI=0 are considered configured uplink grants. Uplink grants addressed to CS-RNTI with NDI=1 are considered dynamic uplink grants.

[0314] …

[0315] If the MAC entity has a C-RNTI, a temporary C-RNTI, or a CS-RNTI, then the MAC entity will grant permission for each PDCCH timing and for each serving cell belonging to a TAG that runs a timeAlignmentTimer or a cg-SDT-TimeAlignmentTimer, and for each grant received for this PDCCH timing:

[0316] 1> If the uplink for this serving cell is already permitted to be received on the PDCCH of the C-RNTI or temporary C-RNTI used for the MAC entity; or

[0317] 1> If uplink permission has already been received in the random access response:

[0318] 2> If the uplink grant is a C-RNTI for a MAC entity and if the previous uplink grant for delivery to the HARQ entity in the same HARQ process was a CS-RNTI received uplink grant or a configured uplink grant for a MAC entity, then:

[0319] 3> Regardless of the value of NDI, NDI is considered to have been switched for use in the corresponding HARQ process.

[0320] …

[0321] 2> Deliver the uplink grant and associated HARQ information to the HARQ entity.

[0322] 1> Otherwise, if the uplink permission for this PDCCH timing has already been received for this serving cell on the PDCCH for the CS-RNTI used for the MAC entity:

[0323] 2> If the NDI in the received HARQ message is 1:

[0324] 3> Treat the NDI used for the corresponding HARQ process as if it has not been switched;

[0325] …

[0326] 3> Deliver the uplink grant and associated HARQ information to the HARQ entity;

[0327] …

[0328] For a MAC entity configured with lch-based Prioritization, the uplink priority is determined by the highest priority among the priorities of logical channels that are multiplexed (i.e., the MAC PDU to be transmitted is already stored in the HARQ buffer) or have multiplexable available data in the MAC PDU (i.e., the MAC PDU to be transmitted is not stored in the HARQ buffer), according to the mapping constraints described in Clause 5.4.3.1.2. No uplink priority for data multiplexed or multiplexable in the MAC PDU for any logical channel is lower than: the uplink priority for data multiplexed or multiplexable in the MAC PDU for any logical channel, or the priority of the logical channel that triggers the SR.

[0329] For a MAC entity configured with lch-based Prioritization, if the corresponding PUSCH transmission configured for uplink prioritization is cancelled by CI-RNTI as specified in Clause 11.2A of TS 38.213, or by a high PHY-priority PUCCH transmission as specified in Clause 9 of TS 38.213, then this configured uplink prioritization is considered a de-prioritized uplink prioritization. If this de-prioritized uplink prioritization is configured with autonomousTx, then the configuredGrantTimer of the corresponding HARQ process for this de-prioritized uplink prioritization should be stopped if it is running. If this de-prioritized uplink prioritization is configured with autonomousTx, then the cg-RetransmissionTimer of the corresponding HARQ process for this de-prioritized uplink prioritization should be stopped if it is running.

[0330] When a MAC entity is configured with lch-based Prioritization, for each uplink granted permission to be delivered to a HARQ entity and whose associated PUSCH can be transmitted by the lower layer, the MAC entity should:

[0331] 1> If this uplink is permitted to be received in a random access response (i.e., in a MAC RAR or fallback RAR), or addressed to a temporary C-RNTI, or as determined for the transmission of the MSGA payload as specified in Clause 5.1.2a:

[0332] 2> Treat this uplink grant as a priority uplink grant.

[0333] …

[0334] 5.4.2 HARQ Operation

[0335] 5.4.2.1 HARQ Entities

[0336] The MAC entity contains a HARQ entity for each serving cell with a configured uplink (including when it is configured with a supplementary uplink), which maintains a number of parallel HARQ processes.

[0337] The number of parallel UL HARQ processes per HARQ entity is specified in TS 38.214.

[0338] Each HARQ process supports one or two TBs.

[0339] Each HARQ process is associated with a HARQ process identifier. HARQ process identifier 0 is used for UL deliveries with UL approval in the RA response or for UL deliveries used for MSGA payloads.

[0340] …

[0341] The maximum number of TBs transmitted within a bundle of uplink-approved uplinks, whether dynamically granted, configured to be granted, or received in the MAC RAR, is given by REPETITION_NUMBER as follows:

[0342] - For dynamic grants, REPETITION_NUMBER is set to a value provided by the underlying layer, as specified in Clause 6.1.2.1 of TS 38.214;

[0343] - For configuration-permitted, REPETITION_NUMBER is set to a value provided by the underlying layer, as specified in Clause 6.1.2.3 of TS 38.214;

[0344] - For uplink grants received in the MAC RAR, REPETITION_NUMBER is set to a value provided by the lower layer, as specified in Clause 6.1.2.1 of TS 38.214.

[0345] If REPETITION_NUMBER > 1, then after the first transmission within the bundle, at most REPETITION_NUMBER-1 HARQ retransmissions follow immediately within the bundle. For dynamic grants, configured uplink grants, and uplink grants received in MAC RAR, the bundling operation relies on the HARQ entity invoking the same HARQ process for each transmission that is part of the same bundle. Within the bundle, HARQ retransmissions are triggered based on REPETITION_NUMBER used for dynamic grants, configured uplink grants, or uplink grants received in MAC RAR without waiting for feedback from previous transmissions, unless they are terminated as specified in Clause 6.1 of TS 38.214. Each transmission within the bundle is a separate uplink grant delivered to the HARQ entity.

[0346] For each transmission within a bundle of uplink-granted data, either dynamically granted or received in the MAC RAR, a redundancy version sequence is determined in accordance with Clause 6.1.2.1 of TS 38.214. For each transmission within a bundle of configured uplink-granted data, a redundancy version sequence is determined in accordance with Clause 6.1.2.3 of TS 38.214.

[0347] For each uplink grant, the HARQ entity will:

[0348] 1> Identify the HARQ process associated with this permission, and for each identified HARQ process:

[0349] 2> If the received provisional C-RNTI is not addressed to the PDCCH, and the NDI provided in the associated HARQ information has been switched compared to the value previously transmitted in this TB for this HARQ process; or

[0350] 2> If uplink permission is received on the PDCCH of C-RNTI, and the HARQ buffer of the identified process is empty; or

[0351] 2> If the uplink is permitted to receive in the random access response (i.e., in the MAC RAR or fallback RAR); or

[0352] 2> If, as specified in Clause 5.1.2a, the uplink for transmitting the MSGA payload is permitted; or

[0353] 2> If uplink permission is received on the PDCCH for the C-RNTI in the ra-ResponseWindow and the PDCCH is successfully completed, then initiate the random access procedure for beam fault recovery; or

[0354] 2> If uplink permission is part of a bundle configured with uplink permission and can be used for initial transmission according to Clause 6.1.2.3 of TS38.214, and if a MAC PDU has not yet been obtained for this bundle:

[0355] …

[0356] 3> Otherwise, if this uplink permission is configured with autonomousTx; and

[0357] 3> If the previously configured uplink in the BWP used for this HARQ process is not prioritized; and

[0358] 3> If a MAC PDU has been obtained for this HARQ process; and

[0359] 3> If the uplink permission size matches the size of the obtained MAC PDU; and

[0360] 3> If the PUSCH transfers of the obtained MAC PDUs are not fully executed:

[0361] 4> It is believed that the MAC PDU has been obtained.

[0362] 3> Otherwise, if the MAC entity is not configured with lch-based Prioritization; or

[0363] 3> If this uplink grant is a prioritized uplink grant:

[0364] 4> Obtain the MAC PDU (if present) from the multiplexing and combining entity for transmission;

[0365] 3> If the MAC PDU for transmission has already been obtained, then:

[0366] 4> If the uplink permission is not configured with autonomousTx; or

[0367] 4> If uplink grant is a prioritized uplink grant:

[0368] 5> Deliver the MAC PDU, uplink permission, and TB HARQ information to the identified HARQ process;

[0369] 5> Instructs the identified HARQ process to trigger a new transfer;

[0370] …

[0371] 3> Otherwise:

[0372] 4> Clear the HARQ buffer of the identified HARQ process.

[0373] 2> Otherwise (i.e., retransmit):

[0374] 3> If the uplink received on the PDCCH is allowed to be addressed to the CS-RNTI and if the HARQ buffer of the identified procedure is empty; or

[0375] 3> If the uplink is permitted as part of a cluster and if a MAC PDU has not yet been obtained for this cluster; or

[0376] 3> If the uplink grant is part of a bundle configured with uplink grants, and the PUSCH duration of the uplink grant overlaps with an uplink grant received in a random access response (i.e., MAC RAR or fallback RAR) or an uplink grant determined for the MSGA payload used for this serving cell as specified in Clause 5.1.2a; or

[0377] 3> If the MAC entity is not configured to have lch-based Prioritization and the BWP is not configured to have an sTx-2 Panel, and if this uplink grant is part of a bundle configured for uplink grants, and the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant received on the PDCCH; or

[0378] 3> If the MAC entity is not configured with lch-based Prioritization and the BWP is configured with an sTx-2 Panel, and if this uplink grant is part of a bundle of configured uplink grants associated with the srs-ResourceSetId corresponding to the coresetPoolIndex, and the PUSCH duration of the uplink grant overlaps with the PUSCH duration of another uplink grant received on the PDCCH associated with the same coresetPoolIndex; or

[0379] 3> If the MAC entity is configured with lch-based Prioritization and this uplink grant is not a prioritized uplink grant:

[0380] 4> Ignore uplink permission.

[0381] 3> Otherwise:

[0382] 4> Deliver the uplink grant and TB HARQ information (redundant version) to the identified HARQ process;

[0383] 4> Instruct the identified HARQ process to trigger a retransmission;

[0384] …

[0385] When determining whether the NDI has been switched compared to the previously transmitted value, the MAC entity will ignore the NDI received in all uplink grants on the PDCCH for its temporary C-RNTI.

[0386] …

[0387] 5.4.2.2 HARQ process

[0388] Each HARQ process is associated with a HARQ buffer.

[0389] A new transmission is performed on the resource by indicating on the PDCCH, or in the random access response (i.e., MAC RAR or fallback RAR), or by sending in the RRC, or as specified in Clause 5.1.2a for the MCS determined for the MSGA payload. A retransmission is performed on the resource and (if available) using the MCS indicated on the PDCCH, or on the same resource and using the same MCS as the last transmission attempt made within the bundle, or on a stored configured uplink granted resource and using a stored MCS when cg-RetransmissionTimer, cg-SDT-RetransmissionTimer, or cg-RRC-RetransmissionTimer is used. If cg-RetransmissionTimer is configured, and if the configured granted configuration has the same TBS, then a retransmission with the same HARQ process can be performed on any configured granted configuration. If cg-SDT-RetransmissionTimer is configured, retransmissions for initial CG-SDT transmissions with the same HARQ process can be performed on any configured configuration with the same TBS.

[0390] …

[0391] If a HARQ entity requests a new transfer for a TB, then the HARQ process will:

[0392] 1> Store the MAC PDU in the associated HARQ buffer;

[0393] 1> Store uplink permission received from the HARQ entity;

[0394] 1> Generate and transmit as described below.

[0395] If the HARQ entity request is used for TB retransmission, then the HARQ process will:

[0396] 1> Store uplink permission received from the HARQ entity;

[0397] 1> Generate and transmit as described below.

[0398] In order to generate a transfer for TB, the HARQ process will:

[0399] …

[0400] 1> If there is no measurement gap during transmission and retransmission occurs, the retransmission will not conflict with the transmission of the MAC PDU obtained from the Msg3 buffer or MSGA buffer:

[0401] 2> If there is neither NR side link transmission nor V2X side link communication during transmission; or

[0402] 2> If the transmission of MAC PDU takes precedence over sidelink transmission or can be performed simultaneously with sidelink transmission:

[0403] 3> Instruct the physical layer to allow the generation of transmissions based on the stored uplink information.

[0404] …

[0405] 5.4.3 Multiplexing and Combining

[0406] 5.4.3.1 Logical Channel Prioritization

[0407] 5.4.3.1.1 General Provisions

[0408] The Logical Channel Prioritization (LCP) procedure is applied whenever a new transmission is executed.

[0409] RRC controls the scheduling of uplink data through signaling for each logical channel per MAC entity:

[0410] -priority, where the increased priority value indicates a lower priority;

[0411] -prioritisedBitRate sets the priority bit rate (PBR);

[0412] -bucketSizeDuration sets the duration of the bucket size (BSD).

[0413] RRC also controls the LCP procedure by configuring mapping limits for each logical channel:

[0414] -allowedSCS-List, which sets the allowed subcarrier spacing for transmission;

[0415] -maxPUSCH-Duration, which sets the maximum allowed PUSCH duration for transmission;

[0416] -configuredGrantType1Allowed, which configures whether type 1 is allowed for transmission;

[0417] -allowedServingCells sets the allowed cells for transmission;

[0418] -allowedCG-List, which sets the configured permissions for transmission;

[0419] -allowedPHY-PriorityIndex sets the dynamically permitted PHY priority index for transmission;

[0420] -allowedHARQ-mode sets the allowed UL HARQ modes for transmission.

[0421] The following UE variables are used in the logical channel priority sorting procedure:

[0422] -Bj, which is maintained for each logical channel j.

[0423] When establishing a logical channel, the MAC entity should initialize the logical channel's Bj value to zero.

[0424] For each logical channel j, the MAC entity should:

[0425] 1> Before each instance of the LCP program, increment Bj by the product PBR×T, where T is the time elapsed since the last increment of Bj;

[0426] 1> If the value of Bj is greater than the bucket size (i.e., PBR × BSD):

[0427] 2> Set Bj to the bucket size.

[0428] Note: The exact time when the UE updates Bj between LCP procedures depends on the UE implementation scheme, as long as Bj is up-to-date at the time permitted by LCP processing.

[0429] 5.4.3.1.2 Selection of Logical Channel

[0430] When executing a new transfer, the MAC entity should:

[0431] 1> For each UL, the selection of a logical channel that meets all of the following conditions is permitted:

[0432] 2> When configured, the set of allowed subcarrier spacing index values ​​in the allowedSCS-List contains subcarrier spacing indices associated with UL-permitted values; and

[0433] 2> When configured, maxPUSCH-Duration is greater than or equal to the UL-approved PUSCH transmission duration; and

[0434] 2> When configured, `configuredGrantType1Allowed` is set to true if the UL grant is configured as grant type 1; and

[0435] 2> When configured, allowedServingCells contains cell information associated with UL-granted cells. When CA replication is reactivated for a DRB within this MAC entity, it does not apply to logical channels associated with a DRB configured with PDCP replication (i.e., CA replication) within the same MAC entity; and

[0436] 2> When configured, allowedCG-List contains a configured permission index associated with UL permissions; and

[0437] 2> When configured, allowedPHY-PriorityIndex contains a priority index associated with dynamic UL grants (as specified in Clause 9 of TS 38.213); and

[0438] 2> When configured, allowedHARQ-mode contains all allowed UL HARQ modes associated with the UL-approved HARQ process.

[0439] Note: Subcarrier spacing index, PUSCH transmission duration, cell information, and priority index are included in the uplink transmission information received from the lower layer corresponding to the scheduled uplink transmission.

[0440] 5.4.3.1.3 Resource Allocation

[0441] Before the successful completion of the random access procedure initiated for DAPS handover, the target MAC entity should not select a logical channel that corresponds to a non-DAPSDRB for uplink grants received in the random access response or for uplink grants for MSGA payload transmission. The source MAC entity should select only the logical channel that corresponds to the DAPSDRB during the DAPS handover.

[0442] When executing a new transfer, the MAC entity should:

[0443] 1> Allocate resources to logical channels as follows:

[0444] 2> Clause 5.4.3.1.2 authorizes the allocation of resources to selected logical channels where Bj>0 in descending priority order for UL. If the PBR of a logical channel is set to infinity, the MAC entity will allocate resources for all data available for transmission on the logical channel before satisfying the PBR of the lower priority logical channel;

[0445] 2> Decrease Bj by the total size of the MAC SDU provided to the above logical channel j;

[0446] 2. If any resources are reserved, all logical channels selected in Clause 5.4.3.1.2 shall be served in strictly descending order of priority (regardless of the value of Bj) until the data or UL granted for said logical channel is exhausted, whichever comes first. Logical channels configured with the same priority shall be provided equally.

[0447] Note 1: The value of Bj can be negative.

[0448] If the requesting MAC entity transmits multiple MAC PDUs simultaneously, or if the MAC entity receives multiple UL grants within one or more overlapping PDCCH moments (i.e., on different serving cells), the UE implementation scheme determines the order in which the grants are processed.

[0449] The UE will also follow the following rules during the above scheduling procedure:

[0450] - If the entire SDU (or a partially transmitted SDU or a retransmitted RLC PDU) is fitted into the remaining resources of the associated MAC entity, then the UE should not segment the RLC SDU (or a partially transmitted SDU or a retransmitted RLC PDU).

[0451] - If the UE segments the RLC SDU from the logical channel, it will maximize the size of the segment to fill as much of the permission of the associated MAC entity as possible;

[0452] - The UE should maximize data transmission;

[0453] - If a MAC entity is given a UL-permitted size of 8 bytes (when eLCID is not used) or 10 bytes (when eLCID is used) and has data available and permitted for transmission (pursuant to Clause 5.4.3.1), the MAC entity should not transmit only padding BSR and / or padding.

[0454] MAC entities will:

[0455] 1> If the MAC entity is configured with enhancedSkipUplinkTxDynamic having a true value and the permission indicated to the HARQ entity is addressing to C-RNTI, or if the MAC entity is configured with enhancedSkipUplinkTxConfigured having a true value and the permission indicated to the HARQ entity is configured uplink permission:

[0456] 2> If there is no UCI for multiplexing on this PUSCH transmission, as specified in TS 38.213; and 2> If there is no non-periodic CSI requested for this PUSCH transmission, as specified in TS 38.212; and

[0457] 2> If the MAC PDU contains a zero MAC SDU; and

[0458] 2> If the MAC PDU contains only periodic BSRs and there is no data available for any LCG, or the MAC PDU contains only padding BSRs:

[0459] 3> No MAC PDU is generated for HARQ entities.

[0460] 1> Otherwise, if the MAC entity is configured with skipUplinkTxDynamic with a value of true, and the permission indicated to the HARQ entity is addressed to C-RNTI, or the permission indicated to the HARQ entity is configured for uplink permission:

[0461] 2> If there is no non-periodic CSI requested for this PUSCH transmission, as specified in TS 38.212; and

[0462] 2> If the MAC PDU contains a zero MAC SDU; and

[0463] 2> If the MAC PDU contains only periodic BSRs and there is no data available for any LCG, or the MAC PDU contains only padding BSRs:

[0464] 3> No MAC PDU is generated for HARQ entities.

[0465] Logical channels should be prioritized according to the following order (highest priority listed first):

[0466] - MAC CE for C-RNTI or data from UL-CCCH;

[0467] - MAC CE for (enhanced) BFR, or for MAC CE with configuration-approved validation, or for MAC CE with multiple entries and configuration-approved validation;

[0468] - MAC CE configured to grant acknowledgment for sidelinks;

[0469] - MAC CE for LBT failure;

[0470] - MAC CE for SL LBT failure according to Clause 5.31.2;

[0471] - MAC CE for advance timing reporting;

[0472] - MAC CE for delay status reporting;

[0473] - MAC CE for SL-BSRs prioritized under Clause 5.22.1.6;

[0474] - MAC CE for (extended) BSR, excluding the BSR included for filling;

[0475] - MAC CE for (enhanced) single-entry PHR, or MAC CE for (enhanced) multi-entry PHR, or MAC CE for single-entry PHR with assumed PUSCH, or MAC CE for multi-entry PHR with assumed PUSCH, or MAC CE for enhanced single-entry PHR for multi-TRP, or MAC CE for enhanced multi-entry PHR for multi-TRP, or MAC CE for enhanced single-entry PHR for multi-TRP STx2P, or MAC CE for enhanced multi-entry PHR for multi-TRP STx2P;

[0476] - MAC CE used to locate the gap activation / deactivation request;

[0477] - MAC CE for the number of symbols to be protected;

[0478] - MAC CE for scenario 6 timing request;

[0479] - MAC CE for (extended) preemptive BSR;

[0480] - MAC CE for SL-BSR, excluding SL-BSRs prioritized under Clause 5.22.1.6 and SL-BSRs included for filling;

[0481] - MAC CE for IAB-MT recommended beam indication, or MAC CE for desired IAB-MT PSD range, or MAC CE for desired DLTx power adjustment;

[0482] - Data from any logical channel, except for data from UL-CCCH;

[0483] - MAC CE used for suggesting bit rate queries;

[0484] - The MAC CE included for filling the BSR;

[0485] - Includes MAC CE for filling SL-BSR.

[0486] Note 2: Prioritization among MAC CEs of the same priority depends on the UE implementation scheme.

[0487] The MAC entity shall prioritize any MAC CE transmitted over the NR side link, ranking it in a higher order than 'data from any logical channel except data from UL-CCCH'.

[0488] 5.4.3.2 Multiplexing of MAC Control Elements and MAC SDUs

[0489] The MAC entity will multiplex the MAC CE and MAC SDU in the MAC PDU in accordance with terms 5.4.3.1 and 6.1.2.

[0490] Note: Regardless of the LBT result, the contents of the MAC PDU will not change after it is constructed for transmission on the dynamic uplink.

[0491] ************************End of quotation*************************

[0492] In TS 38.321 ([9] 3GPP TS 38.321V18.2.0), DL data transmission is described:

[0493] *************************Beginning of quotation[9]***********************

[0494] 5.3DL-SCH Data Transmission

[0495] 5.3.1DL Assignment Reception

[0496] The downlink assignment indication received on the PDCCH is transmitted on the DL-SCH for the specific MAC entity and provides the relevant HARQ information.

[0497] When a MAC entity has a C-RNTI, temporary C-RNTI, CS-RNTI, G-RNTI, or G-CS-RNTI, the MAC entity shall listen to each PDCCH during this period and for each serving cell:

[0498] 1> If the downlink assignment for this PDCCH timing and this serving cell has already been received on the PDCCH of a C-RNTI or temporary C-RNTI used for MAC entities or a G-RNTI configured for multicast MTCH:

[0499] 2> If this is the first downlink assignment used for this temporary C-RNTI:

[0500] 3> Treat NDI as already switched.

[0501] 2> If the downlink assignment is for a C-RNTI of a MAC entity, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a CS-RNTI or G-CS-RNTI received for a MAC entity, or a configured downlink assignment for unicast or MBS multicast; or

[0502] 2> If the downlink assignment is for a MAC entity and is configured for multicast MTCH, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a downlink assignment received for a MAC entity via a CS-RNTI, G-CS-RNTI, or other G-RNTI or C-RNTI, or a configured downlink assignment for unicast or MBS multicast:

[0503] 3> Regardless of the value of NDI, treat NDI as already switched.

[0504] …

[0505] 2> Indicate the existence of downlink assignment and deliver the associated HARQ information to the HARQ entity.

[0506] …

[0507] 5.3.2 HARQ Operation

[0508] 5.3.2.1 HARQ Entities

[0509] The MAC entity contains a HARQ entity for each serving cell, which maintains multiple parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs the HARQ information received on the DL-SCH and the associated TB to the corresponding HARQ process (see Clause 5.3.2.2).

[0510] The number of parallel DL HARQ processes per HARQ entity is specified in TS 38.214. Dedicated broadcast HARQ processes are used for BCCH.

[0511] When the physical layer is not configured for downlink spatial multiplexing, the HARQ process supports one TB. When the physical layer is configured for downlink spatial multiplexing, the HARQ process supports one or two TBs.

[0512] When the MAC entity is configured with pdsch-AggregationFactor > 1, the pdsch-AggregationFactor parameter provides the number of TB transmissions within the bundle allocated for downlink. Bundle operation relies on the HARQ entity to invoke the same HARQ process for each transmission that is part of the same bundle. After the initial transmission, pdsch-AggregationFactor - 1 HARQ retransmissions follow within the bundle.

[0513] MAC entities will:

[0514] 1> If downlink assignment has already been indicated:

[0515] 2> The TB and associated HARQ information received from the physical layer will be assigned to the HARQ process indicated by the associated HARQ information.

[0516] 1> If downlink assignment has already been indicated for the broadcast HARQ process:

[0517] 2> Assign the received TB to the broadcast HARQ process.

[0518] Note: The UE implementation scheme determines whether the received TBs for multicast MCCH, broadcast MCCH, or broadcast MTCH are assigned to a HARQ process.

[0519] 5.3.2.2 HARQ Process

[0520] When transmitting for a HARQ process, one or two (in the case of downlink space multiplexing) TBs and associated HARQ information are received from the HARQ entity.

[0521] For each received TB and associated HARQ message, the HARQ process should:

[0522] 1> If the NDI value has been switched compared to the previous received transmission corresponding to this TB when it is provided; or

[0523] 1> If the HARQ process equals the broadcast process, and this is the first received transmission for TB according to the system information schedule indicated by RRC; or

[0524] 1> If the HARQ process is associated with a transmission indicated by the MCCH-RNTI for MBS broadcast, and this is a transmission scheduled for the first reception of the TB according to the broadcast MCCH indicated by the RRC; or

[0525] 1> If the HARQ process is associated with a transmission indicated by the multicast MCCH-RNTI for MBS multicast in RRC_INACTIVE, and this is a transmission scheduled for the first reception of TB according to the multicast MCCH indicated by RRC; or

[0526] 1> If the HARQ process is associated with a transmission indicated by G-RNTI for MBS broadcast, and this is a transmission for the first reception of the TB according to the MTCH schedule indicated by RRC or according to the schedule indicated by DCI, as specified in TS 38.214; or

[0527] 1> If this is the first transmission for this TB (i.e., there is no previous NDI for this TB):

[0528] 2> Treat this transfer as a new transfer.

[0529] 1> Otherwise:

[0530] 2> Treat this transmission as a retransmission.

[0531] The MAC entity should then:

[0532] 1> If this is a new teleport:

[0533] 2> Attempt to decode the received data.

[0534] 1> Otherwise, if this is a retransmission:

[0535] 2> If this TB of data has not yet been successfully decoded, then:

[0536] 3> Instruct the physical layer to combine the received data with the data currently in the soft buffer for this TB, and attempt to decode the combined data.

[0537] 1> If the MAC entity successfully decodes the data it attempted to decode for this TB; or

[0538] 1> If the data used for this TB was previously successfully decoded:

[0539] 2> If the HARQ process equals the broadcast process:

[0540] 3> Deliver the decoded MAC PDU to the upper layer.

[0541] 2> Otherwise, if this is the first successful decoding of the data used for this TB:

[0542] 3> Pass the decoded MAC PDU to the demultiplexing and multiplexing entity.

[0543] 1> Otherwise:

[0544] 2> Instruct the physical layer to replace the data in the soft buffer used for this TB with the data that the MAC entity attempts to decode.

[0545] 1> If the HARQ process is associated with a transfer indicated by a temporary C-RNTI and contention resolution has not yet been successful (see Clause 5.1.5); or

[0546] 1> If the HARQ process is associated with a transmission indicated by MSGB-RNTI and the random access procedure has not yet completed successfully (see Clause 5.1.4a); or

[0547] 1> If the HARQ process equals the broadcast process; or

[0548] 1> If the HARQ process is associated with a transmission indicated by MCCH-RNTI or G-RNTI for MBS broadcast; or

[0549] 1> If the HARQ process is associated with a transmission via the multicast MCCH-RNTI indication used for MBS multicast; or

[0550] 1> If the HARQ process is associated with a transmission via a G-RNTI or G-CS-RNTI used for MBS multicast or configured with a downlink assignment indication, and HARQ feedback is disabled for this G-RNTI or G-CS-RNTI or the corresponding G-CS-RNTI, as specified in Clause 18 of TS38.213; or

[0551] 1> If the HARQ process is associated with a transmission via G-RNTI or G-CS-RNTI for MBS multicast or with configured downlink assignment indication, and only NACK HARQ feedback is given for this G-RNTI or G-CS-RNTI or corresponding G-CS-RNTI, and the data for this TB is successfully decoded, and the transmission is not the first transmission of a PDSCH that has been (re)initialized with configured downlink assignment; or

[0552] 1> If the timeAlignmentTimer associated with the serving cell containing the TAG that will transmit HARQ feedback stops or expires, and the serving cell is not configured with two TAGs, and if the cg-SDT-TimeAlignmentTimer (if configured) is not running; or

[0553] 1> If the serving cell that transmits HARQ feedback is configured with two TAGs, and if the timeAlignmentTimer of the TAG associated with the TCI state used for transmitting HARQ feedback stops or expires:

[0554] 2> No confirmation is given regarding the physical layer generating the data in this TB.

[0555] 1> Otherwise, if the HARQ process is configured to disable HARQ feedback:

[0556] 2> If harq-FeedbackEnablingforSPSactive is configured with a value of true, and the transmission is the first transmission on the configured downlink assignment after activation by the configured downlink assignment:

[0557] 3> Instruct the physical layer to confirm the generation of data in this TB.

[0558] 2> Otherwise:

[0559] 3> No confirmation is given regarding the physical layer generating the data in this TB.

[0560] 1> Otherwise:

[0561] 2> Instruct the physical layer to confirm the generation of data in this TB.

[0562] When determining whether the NDI on the PDCCH used for its C-RNTI has been switched compared to the value in the previous transmission, the MAC entity should ignore all NDIs received in all downlink assignments on the PDCCH used for its temporary C-RNTI.

[0563] Note: If the MAC entity receives a retransmission of a TB size that is different from the last TB size signaled for this TB, then the UE behavior depends on the UE implementation scheme.

[0564] ************************End of quotation*************************

[0565] When a User Equipment (UE) is configured, scheduled, or instructed to perform dual-codeword transmission (e.g., for spatial multiplexing or 8Tx), the UE may generate (up to) two codewords and / or two transport blocks (TBs) for transmission. It can be determined independently whether to perform a new transmission (e.g., to generate a new codeword / TB and / or perform a transmission with the newly generated codeword / TB) or a retransmission (e.g., to perform a transmission with a previously generated codeword / TB). For example, whether to perform a new transmission or a retransmission for a TB / codeword can be based on the associated New Data Indicator (NDI) in the corresponding (e.g., scheduled) Downlink Control Information (DCI) / Physical Downlink Control Channel (PDCCH). For example, when the associated NDI is switched (e.g., its value changes), the UE will recognize that a new transmission will be performed (or similarly, if the associated NDI is not switched, the UE will recognize that a retransmission will be performed). Because separate NDI bits exist for the two TBs / codewords, it can be determined independently whether to perform a new transmission or a retransmission for each TB / codeword. In other words, when a DCI scheduling two TBs / codewords is received, one TB / codeword can be used for a new transmission, and the other TB / codeword can be used for a retransmission. The UE can generate a Media Access Control (MAC) Protocol Data Unit (PDU) for the new transmission and / or obtain a MAC PDU from the Multiplexing and Combining Entity for the transmission of the one TB / codeword. The UE can instruct (corresponding to / identified) the Hybrid Automatic Repeat Request (HARQ) process to trigger a retransmission of the other / another TB / codeword for retransmission. If the UE does not have any data in the (data) buffer, the UE will not generate or will skip generating the MAC PDU for the new transmission of the one TB / codeword, because the MAC PDU will only contain the MAC control unit (CE) for filling the buffer state report (BSR) or the periodic BSR with zero MAC SDU, and there is no aperiodic channel state information (CSI) and / or no requested uplink control information (UCI) (for this transmission time interval (TTI)) and / or no MAC PDU to be generated for the HARQ entity (for this TTI). The UE will then perform a UL transmission with the one TB / codeword. The UE may not be able to perform the UL transmission correctly because the precoder used is for two TB transmissions. The base station may not be able to receive and / or decode the transmission correctly because the base station will expect / assume that the UE is transmitting two TBs.

[0566] The UE's MAC can dynamically receive UL grants in the Random Access Response (RAR) on the PDCCH, and / or be semi-persistently configured. In the MAC, the HARQ entity maintains multiple parallel HARQ processes. The HARQ entity identifies the HARQ process for each UL grant for a given TTI. The HARQ entity obtains the MAC PDU from the Msg3 buffer for the identified HARQ process and / or the multiplexing and combining entity. If the multiplexing and combining entity does not generate a MAC PDU according to the Logical Channel Prioritization (LCP) procedure, the HARQ entity clears the relevant HARQ buffer. When skipUplinkTxDynamic is configured for dynamic UL grants (addressed to the Cell Radio Network Temporary Identifier (C-RNTI)) and / or skipUplinkTxSPS is configured for configured UL grants (addressed to the semi-persistent scheduling C-RNTI), a MAC PDU may not be generated if no data is available for transmission. Uplink skipping (e.g., skipUplinkTxDynamic and / or skipUplinkTxSPS) is configured by Radio Resource Control (RRC). Throughout this disclosure, skipUplinkTxDynamic and / or skipUplinkTxSPS can be or may be referred to as uplink skipping and / or UL transmission skipping. Throughout this disclosure, one, some, and / or all instances of “UL transmission skipping” may correspond to, may be supplemented with, and / or may be replaced by “uplink skipping,” “skipUplinkTxDynamic,” and / or “skipUplinkTxSPS.”

[0567] In Long Term Evolution (LTE), when the Physical Layer (PHY) is configured for UL spatial multiplexing, the MAC can receive two dynamic UL grants from the lower layer in a given Time Time Interval (TTI). One of these dynamic UL grants can be used for a new transmission. The other dynamic UL grant can be used for a retransmission. The HARQ entity identifies two HARQ processes for a given TTI. The HARQ entity obtains the MAC PDU for the HARQ process used for the new transmission. The HARQ entity instructs the HARQ process used for the retransmission to perform a retransmission. Subsequently, the MAC transmits the MAC PDU used for the new transmission as a TB to the PHY for a given TTI. However, if no data is available in a given TTI and skipUplinkTxDynamic is configured in the UE, the multiplexing and combining entities will not generate the MAC PDU, for example, because when skipUplinkTxDynamic is configured, the UE will not generate a MAC PDU including pure padding (and there is no non-periodic CSI requested for the TTI) and / or the HARQ entity will not generate a MAC PDU for this TTI (for example, because the MAC PDU for retransmission has already been generated previously). In other words, UL skipping for the two UL grants is checked separately. Although the UE receives two UL grants with UL spatial multiplexing, the UE may transmit only one TB (for retransmission). UL skipping may be applied to one UL grant (for new transmission) but not to the other UL grant (for retransmission). When two dynamic UL grants exist in a given TTI, the PHY will expect two TBs (or two codewords). For example, a Layer 4 UL transmission may be indicated for the TTI (e.g., ...).

[0568] In New Radio (NR), when the PHY is configured for UL 8Tx, the MAC can receive from the lower layer a PDCCH indicating one or two dynamically UL-granted protocols, which indicate (at a given TTI) two Transport Blocks (TBs) and associated HARQ information. (For example,) one of the two TBs can be used for a new transmission. (For example,) the other TB can be used for a retransmission. The HARQ entity identifies one or two HARQ processes for UL grant. The HARQ entity obtains the MAC PDU for the one TB of the HARQ process (one of the HARQ processes) used for the new transmission. And the HARQ entity instructs the other HARQ process (the other one) to perform a retransmission for the other TB. The MAC then (for a given TTI) transmits the one MAC PDU used for the new transmission as a TB to the PHY. However, if no data is available and skipUplinkTxDynamic is configured in the UE, the multiplexing and combining entity will not generate the aforementioned MAC PDU, for example, because when skipUplinkTxDynamic is configured, the UE will not generate a MAC PDU including pure padding (and there is no non-periodic CSI requested for the UL transmission) and / or will not generate a MAC PDU for the TB (e.g., because the MAC PDU for retransmission has already been generated previously). In other words, UL skipping for the two TBs is checked separately. Although the UE receives a PDCCH indicating UL permission, which indicates (for 8Tx UL transmission) two TBs, the UE may transmit only one TB (for retransmission). UL skipping may be applied to one TB (for a new transmission) but not to the other TB (for retransmission). The PHY will expect two TBs (or two codewords). For example, UL permission may indicate a Layer 4 UL transmission (e.g., both TBs are enabled), and the PHY will expect to generate two TBs, where each TB maps to two layers. The PHY cannot correctly generate a Layer 4 transport with only one TB, and / or the base station may not be able to correctly receive / decode the PUSCH.

[0569] When the PHY is configured for 8Tx (operation) and / or when maxRank > 4 or maxMIMO-Layers > 4 and / or rank > 4 and / or the number of layers is greater than 4 and / or when dual codewords are indicated, the MAC can receive one (or two) dynamic UL grants from the lower layer (on the PDCCH) for two transport blocks and / or for two codewords (for a given TTI, e.g., a time slot). The one (or two) UL grants can be used for the same time / frequency resource. The one (or two) UL grants can be used for the same (Orthogonal Frequency Division Multiplexing (OFDM)) symbol. The one (or two) UL grants can be used for the same Physical Resource Block (PRB). The one (or two) UL grants can be used for the same Transceiver Point (TRP). The one (or two) UL grants can be used for two separate TRPs. The one (or two) UL grants can be associated with the same UL beam. The one (or two) UL grants can be associated with two separate uplink beams. One (or two) UL grants may be associated with the same Sound Reference Signal Resource (SRS) Indicator (SRI). One (or two) UL grants may be associated with two separate SRIs. One (or two) UL grants may be associated with the same Control Resource Set (CORESET) pool index. One (or two) UL grants may be associated with two separate CORESET pool indices. One (or two) UL grants may be associated with the same SRS resource set. One (or two) UL grants may be associated with two separate SRS resource sets. One (or two) UL grants may be used in a codebook-based UL transmission scheme. One (or two) UL grants may be used in a non-codebook-based UL transmission scheme. The two transport blocks or codewords may be precoded jointly (e.g., with the same precoder). The two transport blocks or codewords may be precoded individually (e.g., with separate / different precoders). One (or two) UL grants may be associated with the same Transmit (Tx) / Receive (Rx) Point (TRP). The one (or two) UL grants can be associated with two TRPs respectively. (For example,) one of the two dynamic UL grants can be used for a new transmission. (For example,) the other dynamic UL grant can be used for a retransmission. The HARQ entity identifies one (or two) HARQ processes (for a given TTI) for the two transport blocks / codewords. The HARQ entity obtains one (or one) MAC PDU for the new transmission for the HARQ process. The HARQ entity instructs the HARQ process to perform a retransmission. The MAC then transmits the one MAC PDU as a TB to the PHY (for a given TTI / symbol / PRB).

[0570] However, if no data is available (in a given TTI) and skipUplinkTxDynamic is configured in the UE, the multiplexing and combining entities will not generate the aforementioned MAC PDU. This is because, for example, when skipUplinkTxDynamic is configured, the UE will not generate a MAC PDU including pure padding (and there is no non-periodic CSI requested for the PUSCH and / or no UCI to be multiplexed on the PUSCH) and / or the HARQ entity (for this TTI) will not generate a MAC PDU (e.g., since the MAC PDU for retransmission has already been generated previously). In other words, the UL skip for the two TBs (e.g., one for a new transmission and / or one for a retransmission) is checked separately. Although the UE receives one (or two) UL grants for two TBs (or two codewords), the UE may transmit only one TB (for retransmission). When one (or two) dynamic UL grants exist for two TBs / codewords for the PUSCH (in a given TTI), the PHY will expect two TBs (or two codewords). For example, for PUSCH (for TTI), an 8-layer UL delivery can be instructed (e.g., both TBs are enabled), and the PHY expects to generate two TBs, each mapped to four layers. The PHY cannot correctly generate an 8-layer delivery with only one TB (e.g., via a precoder for 8 layers). ), and / or the base station may not be able to properly receive / decode the PUSCH.

[0571] If there is insufficient available data (for a given TTI) and skipUplinkTxDynamic is configured in the UE, for example, if one of the UL grants (and / or TBs) contains available data and only padding is left for the other UL grant (and / or TB), the multiplexing and combining entity generates only one MAC PDU, for example, because the UE will not generate a MAC PDU including pure padding when skipUplinkTxDynamic is configured (and there is no aperiodic / periodic CSI requested for the TTI). In other words, UL skipping for the two UL grants (and / or TBs) is checked separately. Although the MAC (for a given TTI) receives two UL grants (and / or TBs) for two transport blocks and / or two codewords, the MAC may transmit only one TB to the PHY. UL skipping may be applied to one UL grant but not the other. However, depending on the transport scheme and / or transport nature, the PHY may expect two TBs (or two codewords) when there are UL grants for two TBs (for the same time / frequency resource) (for a given TTI). For example, a TTI might indicate an 8-layer UL delivery (e.g., both TBs are enabled), and the PHY expects to generate two TBs, each mapping to four layers. In some cases / delivery schemes / delivery characteristics, the PHY may not be able to generate an 8-layer delivery with only one TB. The two UL grants are associated with the same TTI. The two TBs are associated with the same HARQ process and / or UL grant.

[0572] Throughout this disclosure, "8Tx" can be, can be replaced with, can represent, can be called "dual codeword", "maxRank>4" or "maxMIMO-Layers>4". A UE configured with 8Tx can be configured with maxRank>4 and / or maxMIMO-Layers>4.

[0573] In NR R18 MIMO, 8Tx UL is introduced. Depending on the PHY procedure and RRC configuration, maxRank and maxMIMO-Layers can be configured to be higher than 4 (up to 8). Based on the configuration, up to two codewords can exist for PUSCH. That is, the UE can transmit up to two TBs simultaneously (scheduled by a PDCCH or DCI).

[0574] In LTE, when a UE is configured for uplink spatial multiplexing, the MAC can receive two UL grants (for new transmissions) for two TBs for the same TTI. When there is available data but the amount of data is insufficient for two TBs (for a TTI), if at least one MAC PDU (for this TTI) will be generated, the MAC generates MAC PDUs corresponding to all UL grants (for this TTI) (even if UL skipping is configured and / or the conditions for UL skipping may be met).

[0575] However, one scenario exists where one of the two uplink grants is used for retransmission and the other for a new transmission. The first MAC PDU for retransmission has been "previously generated" and is awaiting retransmission. Furthermore, when skipUplinkTxDynamic is configured, the multiplexing and combining entity will not generate a second MAC PDU for the new transmission if at least no data is available. When the MAC generates only one TB for UL spatial multiplexing, the PHY cannot correctly execute the corresponding transmission (e.g., a 2-TB transmission) because the two TB transmissions are scheduled by the DCI and anticipated by the network (NW).

[0576] To address this issue, it is permissible to prevent the network from providing a configuration (or any configuration) that allows the UE to be configured (simultaneously) with both 8Tx and UL transmission skipping. Alternatively and / or additionally, it is permissible to allow the network to provide a configuration (or any configuration) that allows the UE to be configured with 8Tx but not with UL transmission skipping, or the UE to be configured with UL transmission skipping but not with 8Tx.

[0577] If the PHY is configured for 8Tx (or dual codeword) (or if maxRank > 4 or maxMIMO-Layers > 4), the NW may not provide any configuration (or any configuration) that would indicate UL skipping (e.g., skipUplinkTxDynamic set to true). For example, when 8Tx is configured, the NW may not configure the UE to use the parameter indicating UL skipping (e.g., skipUplinkTxDynamic). For example, when 8Tx is configured, the NW may configure the UE to set the value of the parameter indicating UL skipping (e.g., skipUplinkTxDynamic) to false.

[0578] If the parameter in the RRC configuration that indicates UL skipping (e.g., skipUplinkTxDynamic) is set to true, the NW may not provide any configuration (or any configuration) for the PHY to be configured with 8Tx. For example, if the parameter indicating UL skipping (e.g., skipUplinkTxDynamic) is configured, the NW may not configure 8Tx. For example, if the value of the parameter indicating UL skipping (e.g., skipUplinkTxDynamic) is configured to true, the NW may not configure 8Tx.

[0579] The NW can configure 8Tx and UL skipping (simultaneously) for the UE. When the NW configures 8Tx and UL skipping for the UE, it is not permitted (in the DCI) to instruct the UE to perform UL transmission with two transport blocks. When the NW configures 8Tx and UL skipping for the UE, it is not permitted (in the DCI) to instruct the UE to grant one or both ULs for a given TTI and / or for two codewords (transport blocks) for the same time / frequency resource. When the NW configures 8Tx and UL skipping for the UE, it is not permitted (in the DCI) to instruct the UE to enable two transport blocks. When the NW configures 8Tx and UL skipping for the UE, it is not permitted (in the DCI format associated with dual codewords) to instruct both codewords / transport blocks to be enabled. When the NW configures 8Tx and UL skipping for the UE, it is not permitted (in the DCI format associated with dual codewords) to instruct the UE to use I... MCS =0 and N PRB Combinations >1 and I MCS =28 and N PRB =1 combination. When the NW configures 8Tx and UL skipping for the UE, the NW should (in the DCI) instruct the UE to perform UL transmission with a single transport block. When the NW configures 8Tx and UL skipping for the UE, the NW should (in the DCI) instruct the UE to enable a single transport block.

[0580] When the NW configures 8Tx and UL skipping for the UE, the NW should (in the DCI) instruct the UE to disable a transport block. When the NW configures 8Tx and UL skipping for the UE, the NW should (in the DCI format associated with the dual codeword) instruct the UE to use I for the transport block. MCS =0 and N PRB Combinations > 1 or I MCS =28 and N PRB =1 combination. When the NW configures 8Tx and UL skip for the UE, the NW should schedule the UE using DCI format 0 or DCI format associated with the dual codeword, where I is used for the transport block. MCS =0 and N PRB Combinations > 1 or I MCS =28 and N PRBCombinations of =1 are in DCI format associated with dual codewords.

[0581] The NW can configure UL spatial multiplexing and UL skipping for the UE (simultaneously). When the NW configures UL spatial multiplexing and UL skipping for the UE, the NW is not allowed (in the DCI) to instruct the UE to perform UL transmission with one transport block for new transmission and another transport block for retransmission. When the NW configures UL spatial multiplexing and UL skipping for the UE, the NW should (in the DCI) instruct the UE to perform UL transmission with either two transport blocks for new transmission or two transport blocks for retransmission. When the NW configures UL spatial multiplexing and UL skipping for the UE, the NW is not allowed (in the DCI) to instruct the UE to use the first NDI bit for a transport block that has been switched and the second NDI bit for another transport block that has not been switched. When the NW configures UL spatial multiplexing and UL skipping for the UE, the NW should (in the DCI) instruct the UE to use either the first NDI bit for a transport block that has been switched and the second NDI bit for another transport block that has not been switched and the second NDI bit for another transport block that has not been switched. When a single transport block requires retransmission and the NW is configured with UL spatial multiplexing and UL skipping for the UE, the NW should enable a single transport block for the UE (in the DCI). When at least one and / or only one NDI bit (in the DCI) is not switched and the NW is configured with UL spatial multiplexing and UL skipping for the UE, the NW should enable a single transport block for the UE (in the DCI). When two NDI bits (in the DCI) are not switched and the NW is configured with UL spatial multiplexing and UL skipping for the UE, the NW may enable two transport blocks for the UE (in the DCI). When two NDI bits (in the DCI) have been switched and the NW is configured with UL spatial multiplexing and UL skipping for the UE, the NW may enable two transport blocks for the UE (in the DCI).

[0582] The NW can (simultaneously) configure the UE for 8Tx (or dual codeword, or maxRank>4, or maxMIMO-Layers>4) and UL skipping for UL. When the NW configures the UE for 8Tx and UL skipping for UL, the NW is not allowed (in the DCI) to instruct the UE to perform UL transmission with one transport block for new transmission and another transport block for retransmission. When the NW configures the UE for 8Tx and UL skipping for UL, the NW should (in the DCI) instruct the UE to perform UL transmission with either two transport blocks for new transmission or two transport blocks for retransmission. When the NW configures the UE for 8Tx and UL skipping for UL, the NW is not allowed (in the DCI) to instruct the UE to use the first NDI bit for a transport block that has been switched and the second NDI bit for another transport block that has not been switched. When the NW configures the UE for 8Tx and UL skipping for UL, the NW should (in the DCI) instruct the UE to use the first NDI bit for one transport block that has been switched and the second NDI bit for another transport block that has been switched, or the first NDI bit for one transport block that has not been switched and the second NDI bit for another transport block that has not been switched. When a single transport block requires retransmission and the NW configures the UE for 8Tx and UL skipping for UL, the NW should (in the DCI) enable the single transport block for the UE. When at least one and / or only one NDI bit (in the DCI) is not switched and the NW configures the UE for 8Tx and UL skipping for UL, the NW should (in the DCI) enable the single transport block for the UE. When both NDI bits (in the DCI) are not switched and the NW configures the UE for 8Tx and UL skipping for UL, the NW may (in the DCI) enable two transport blocks for the UE. When both NDI bits (in DCI) have been switched and NW is configured for UE to use 8Tx and UL skip for UL, NW can enable two transport blocks for UE (in DCI).

[0583] The NW can configure 8Tx and UL skipping for the UE (simultaneously). When the NW configures 8Tx and UL skipping for the UE, the NW is not allowed to enable 8Tx via DCI. When the NW configures 8Tx and UL skipping for the UE, the NW is not allowed to instruct the UE (in DCI) to perform UL transmission with 8Tx. When the NW configures 8Tx and UL skipping for the UE, the NW is not allowed to schedule the UE with a DCI format associated with dual codewords (e.g., to perform UL transmission with multiple codewords / TB). When the NW configures 8Tx and UL skipping for the UE, the NW should (in DCI) instruct the UE to perform UL transmission without 8Tx. When the NW configures 8Tx and UL skipping for the UE, the NW should (in DCI) instruct the UE to perform UL transmission with a single codeword / TB. When the NW configures 8Tx and UL skipping for the UE, the NW should schedule the UE with DCI format 0 (e.g., to perform UL transmission with a single TB / codeword).

[0584] The above-mentioned restrictions on NW configuration and / or NW indication may apply when the NW is uncertain about the available data at the UE side and / or when the NW recognizes that the amount of available data at the UE side is small. When the NW recognizes that the amount of available data at the UE side is large, the above-mentioned restrictions on NW configuration and / or NW indication shall not apply. For example, the NW may recognize the amount of available data based on a buffer status report from the UE. The above-mentioned restrictions on NW configuration and / or NW indication shall apply when the NW has not received a buffer status report from the UE (for an extended period) and / or the NW does not have the latest buffer status information from the UE and / or when the NW receives a scheduling request from the UE and / or when the NW schedules the UE in response to a scheduling request from the UE and / or when the NW receives a buffer status report indicating a small amount of available data and / or when the NW receives a buffer status report indicating that the amount of available data is less than the size of a transport block and / or when the NW receives a buffer status report indicating that the amount of available data results in data in one transport block but not in data in another transport block. The above restrictions on NW configuration and / or NW indication shall not apply when NW receives a buffer status report indicating a large amount of available data and / or when NW receives a buffer status report indicating that the amount of available data is greater than the size of a transport block and / or when NW receives a buffer status report indicating that the amount of available data results in data in two transport blocks.

[0585] The NW can configure 8Tx and UL skipping (simultaneously) for the UE. The NW can be prevented from executing the first event in response to a third event. The NW can execute the second event in response to a third event. The NW can execute the fourth event in response to a fifth condition.

[0586] The first event can be (at least) one or more of the following:

[0587] -(in DCI) Instructs the UE to perform UL transmission in two transport blocks;

[0588] - (in DCI) Indicate to the UE two UL grants or two TBs of UL grants for a given TTI (or, for example, two TB transmissions, double codeword transmissions, rank > 4, MIMO layer > 4);

[0589] - (in DCI) Instruct the UE to enable two transport blocks (or for example, two TB transport, dual codeword transport, rank > 4, MIMO layer > 4);

[0590] - (in DCI) Instruct the UE to perform UL transmission with a single transport block (or, for example, single TB transmission, single codeword transmission, rank <= 4, MIMO layer <= 4);

[0591] - (in DCI) Instruct the UE to enable a single transport block (or, for example, single TB transport, single codeword transport, rank <= 4, MIMO layer <= 4);

[0592] - (In DCI) Instructs the UE to deactivate a transport block;

[0593] - (in DCI format) indicates the division by I for two transport blocks. MCS =26 and rv id =Combinations other than 1;

[0594] - Enable 8Tx with DCI (or for example, two TB transmission, double codeword transmission, rank > 4, MIMO layer > 4);

[0595] - (in DCI) Instruct the UE to perform UL transmission at 8Tx (or, for example, two TB transmission, dual codeword transmission, rank > 4, MIMO layer > 4); and / or

[0596] - Schedule the UE in the DCI format associated with 8Tx (e.g., to perform UL transmission with multiple antenna ports).

[0597] The second event can be (at least) one or more of the following:

[0598] - (In DCI format) Indicates the I / O used by the UE for a transport block. MCS =26 and rv id =1;

[0599] - Schedule the UE using DCI format 0 or the DCI format associated with 8Tx, wherein I is indicated for the transport block in the DCI format associated with 8Tx. MCS =26 and rv id Combinations equal to 1;

[0600] - (in DCI) Instruct the UE to perform UL transmission without 8Tx (or for example, two TB transmission, dual codeword transmission, rank > 4, MIMO layer > 4);

[0601] - (in DCI) Instruct the UE to perform UL transmission with a single antenna port; and / or

[0602] - Schedule the UE in DCI format 0 (e.g., to perform UL transmission with a single antenna port).

[0603] The third event can be (at least) one or more of the following:

[0604] -NW is uncertain about the available data at the UE side;

[0605] -NW recognizes that the amount of available data at the UE side is small;

[0606] -NW has not received a buffer status report from the UE for an extended period of time;

[0607] -NW does not have the latest buffer status information for the UE;

[0608] -NW receives a scheduling request from the UE;

[0609] -NW schedules the UE in response to a scheduling request from the UE;

[0610] -NW received a buffer status report indicating that a small amount of data was available;

[0611] -NW receives a buffer status report indicating that the amount of available data is less than the size of a transport block; and / or

[0612] - The NW receives a buffer status report indicating the amount of available data that results in data in one transport block but not data in another transport block (and / or when the NW is configured to skip 8Tx and UL for the UE).

[0613] The fourth event can be (at least) one or more of the following:

[0614] - (in DCI) Instruct the UE to perform UL transmission in two transport blocks (e.g., double codeword, rank > 4, MIMO layer > 4);

[0615] - (in DCI) Indicate to the UE two UL grants or two TBs of UL grants for a given TTI (or, for example, two TB transmissions, double codeword transmissions, rank > 4, MIMO layer > 4);

[0616] - (in DCI) Instruct the UE to enable two transport blocks (or for example, two TB transport, dual codeword transport, rank > 4, MIMO layer > 4);

[0617] - (in DCI) Instruct the UE to perform UL transmission with a single transport block (or, for example, single TB transmission, single codeword transmission, rank <= 4, MIMO layer <= 4) or two transport blocks (or, for example, two TB transmission, double codeword transmission, rank > 4, MIMO layer > 4);

[0618] - (in DCI) Instruct the UE to enable a single transport block (or, for example, single TB transmission, single codeword transmission, rank <= 4, MIMO layer <= 4) or two transport blocks (or, for example, two TB transmission, double codeword transmission, rank > 4, MIMO layer > 4);

[0619] - (in DCI) Instruct the UE to disable one transport block or enable two transport blocks (or, for example, two TB transmission, dual codeword transmission, rank > 4, MIMO layer > 4);

[0620] - (In the DCI associated with 8Tx) indicates that for two transport blocks, the I... MCS =26 and rv id =1;

[0621] - (in DCI format) Indicates the UE's use of the difference between two transport blocks. MCS =26 and rv id =Combinations other than 1;

[0622] - Schedule the UE in the DCI format associated with 8Tx, where the division of I for two transport blocks is used. MCS =26 and rv id The combination outside of =1 is transmitted in the DCI format associated with 8Tx;

[0623] - Enable 8Tx with DCI (or for example, two TB transmission, double codeword transmission, rank > 4, MIMO layer > 4);

[0624] - (in DCI) Instruct the UE to perform UL transmission with 8Tx (or, for example, two TB transmission, double codeword transmission, rank > 4, MIMO layer > 4);

[0625] - (in DCI) Instruct the UE to perform UL transmission with or without 8Tx (or, for example, two TB transmission, dual codeword transmission, rank > 4, MIMO layer > 4);

[0626] - (in DCI) Instructs the UE to perform UL transmission with a single antenna port or multiple antenna ports;

[0627] - Schedule the UE in a DCI format associated with 8Tx (e.g., to perform UL transmission with multiple antenna ports); and / or

[0628] - Schedule the UE in the DCI format associated with 8Tx (e.g., to perform UL transmission with multiple antenna ports).

[0629] The fifth event can be (at least) one or more of the following:

[0630] -NW recognizes that there is a large amount of available data on the UE side;

[0631] -NW received a buffer status report indicating a large amount of available data;

[0632] -NW receives a buffer status report indicating that the amount of available data is greater than the size of a transport block; and / or

[0633] - The NW receives an indication of the amount of data available, causing a buffer status report for the data in two transport blocks (and / or when the NW is configured to skip 8Tx and UL for the UE).

[0634] To address this issue, the UE may not skip any UL transmissions used for UL spatial multiplexing. The UE may be configured with UL spatial multiplexing. The UE may not have any available data for transmission. The UE may have (previously) generated a TB or MAC PDU. The UE may receive one UL grant for a new transmission (for the TTI). The UE may receive another UL grant for retransmission (for the TTI). The UL grant for a new transmission and the UL grant for retransmission can be used for UL spatial multiplexing, for example, for transmissions within the same time / frequency resource. The UE may receive one UL grant for a new transmission and another UL grant for retransmission (e.g., a previously generated TB or MAC PDU) (for one TTI). When the UE receives one UL grant for a new transmission and another UL grant for retransmission (for the TTI), the UE may not skip the UL transmission and / or may generate a MAC PDU for the new transmission (for the TTI). Due to or in response to a retransmission (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)) (for the TTI), the UE may not skip a UL transmission and / or may generate a MAC PDU for the new transmission (for the TTI). When the UE receives a UL grant for the new transmission and another UL grant for the retransmission (for the TTI), the UE may generate a MAC PDU containing padding only for the new transmission (e.g., for the TTI). Due to or in response to a retransmission (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)) (for the TTI), the UE may generate a MAC PDU containing padding only for the new transmission. When the UE receives a UL grant for the new transmission and another UL grant for the retransmission (for the TTI), the UE may generate a MAC PDU for the new transmission containing only MAC CE for padding the BSR or a periodic BSR with zero MAC SDU (e.g., for the TTI). Due to or in response to a retransmission (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)) (for the TTI), the UE can generate a single MAC PDU for the new transmission containing only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDUs. The UE can perform a UL transmission in the TTI with one MAC PDU for the new transmission and another MAC PDU for the retransmission. For example, when the UE receives one UL grant for the new transmission and another UL grant for the retransmission (for the TTI), the multiplexing and combining entity can ignore the condition of not generating a MAC PDU.For example, when the UE receives one UL grant for a new transmission and another UL grant for a retransmission (for the TTI), the HARQ entity can instruct the multiplexing and combining entity to generate a padded MAC PDU. For example, when the UE receives one UL grant for a new transmission and another UL grant for a retransmission (for the TTI), the HARQ entity can obtain a MAC PDU from another / other HARQ buffer.

[0635] The NW can configure UL spatial multiplexing and parameters to indicate UL skipping (e.g., skipUplinkTxDynamic) for the UE. The UE can receive two UL grants (for a given TTI) (on the PDCCH / DCI). One of the two UL grants can be used for a new transmission. The other of the two UL grants can be used for a retransmission.

[0636] In one instance, when the UE receives (or is scheduled by the PDCCH) one UL grant for a new transmission and another UL grant for a retransmission for a given TTI, the UE may generate a MAC PDU for that given TTI (or for the UL grant), regardless of whether the UE has available data. The UE may generate a MAC PDU for that given TTI (or for the UL grant) when the UE does not have available data for transmission and / or when the UE receives one UL grant for a new transmission and another UL grant for a retransmission for a given TTI. In the case of the LCP procedure, if the UE does not have available data for transmission, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), and / or the grant is addressed to the C-RNTI, and / or the UE does not have two UL grants for a given TTI and / or the UE has two UL grants for a given TTI, both for new transmissions, then the UE may not generate a MAC PDU.

[0637] In one instance, when the UE is configured for UL spatial multiplexing, the UE can generate a MAC PDU regardless of whether the UE has available data. In the case of the LCP procedure, if the UE does not have data available for transmission, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), and / or is allowed to address to C-RNTI, and / or the PHY is not configured for UL spatial multiplexing, the UE may not generate a MAC PDU.

[0638] In one instance, when UL is permitted for spatial multiplexing transmission, the UE can generate a MAC PDU regardless of whether it has data available for retransmission. In the case of LCP procedures, if the UE does not have data available for retransmission, and / or the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), and / or is permitted to address to a C-RNTI not used for UL spatial multiplexing, the UE may not generate a MAC PDU.

[0639] In one instance, when a UE has one UL grant for a new transmission and another UL grant for a retransmission for a given TTI, if the UE has not obtained a MAC PDU for the new transmission in said TTI, the UE may generate a padding MAC PDU. If a MAC PDU for the new transmission in a given TTI has not yet been obtained, and a MAC PDU for retransmission has been generated, the UE may instruct the multiplexing and combining entity to generate a padding MAC PDU for the new transmission. A padding MAC PDU may not be generated when both UL grants for a new transmission in a TTI are received.

[0640] In one instance, when a UE has one UL grant for a new transmission and another UL grant for a retransmission for a TTI, if the UE does not obtain a MAC PDU for the new transmission for the TTI, the UE can obtain a MAC PDU from another HARQ buffer. If a MAC PDU to be transmitted for the new transmission has not yet been obtained, and the UE has one UL grant for a new transmission and another UL grant for a retransmission for the TTI, the UE can obtain a MAC PDU from another HARQ buffer associated with the TTI. When a UE has two UL grants for a new transmission for a TTI, the UE may not obtain a MAC PDU from another / other HARQ buffer. When a UE has two UL grants for a new transmission for a TTI, for example, if no data is available for transmission, the UE may not obtain a MAC PDU for the new transmission.

[0641] One or both of the MAC PDUs associated with a given TTI may contain only padding, padding BSRs and / or periodic BSRs with zero MAC SDUs.

[0642] The following textual proposals (TPs) may be considered examples of the present invention:

[0643]

[0644] For example, if at least one MAC PDU (e.g., the first MAC PDU) for a HARQ entity (for a TTI) is to be retransmitted, the UE (its MAC entity) may generate a MAC PDU (e.g., the second MAC PDU) corresponding to one of the UL permissions indicated to the HARQ entity (for the TTI). If at least one MAC PDU (e.g., the first MAC PDU) for a PDCCH is to be retransmitted, the UE (its MAC entity) may generate a MAC PDU (e.g., the second UL permission) corresponding to one of the UL permissions indicated by the PDCCH (e.g., the second UL permission). Alternatively and / or additionally, if at least one MAC PDU (e.g., the first MAC PDU) has been generated for a HARQ entity (for a TTI) and / or has been stored in the associated HARQ buffer (e.g., when a retransmission of the first MAC PDU is requested), the UE (its MAC entity) may generate a MAC PDU (e.g., the second MAC PDU) corresponding to one of the UL permissions indicated to the HARQ entity (for the TTI). If at least one MAC PDU (e.g., the first MAC PDU) has been generated for the PDCCH, the UE (its MAC entity) can generate a MAC PDU (e.g., the second MAC PDU) corresponding to one of the UL grants indicated to the PDCCH (e.g., the second UL grant). The UE can receive two UL grants indicated to the HARQ entity (for the TTI). The first UL grant of the two UL grants can be used for retransmission. The second UL grant of the two UL grants can be used for new transmission. The UE can receive a PDCCH indicating the two UL grants. The PDCCH can indicate a first UL grant for retransmission of the first MAC PDU and a second UL grant for new transmission. The UE can retransmit the first MAC PDU using the first UL grant (for the TTI). There may not be available data for the new transmission (for the TTI). The second MAC PDU for the new transmission may only contain padding, a padding BSR, and / or a periodic BSR with zero MAC SDUs. The UE can generate a second MAC PDU (corresponding to the second UL grant) based on the retransmission of the first MAC PDU. The UE can generate a second MAC PDU based on the first MAC PDU that has already been generated.

[0645] To address this issue, the UE can generate a MAC PDU corresponding to the UL grant indicated by the PDCCH based on the retransmission of another MAC PDU for the PDCCH. The UE can receive a first parameter (e.g., maxMIMO-Layers) > 4 and a second parameter (e.g., skipUplinkTxDynamic). The UE may not have available data for the new transmission. The UE can receive a first UL grant for retransmission and a second UL grant for the new transmission on the first PDCCH. The UE can generate a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH based on the retransmission of the first MAC PDU for the first PDCCH, wherein the second MAC PDU includes zero MAC SDUs and / or no data available for transmission. The UE can use the two UL grants to perform a retransmission of the first MAC PDU and a new transmission of the second MAC PDU.

[0646] In one instance, the UE can receive from the network node a first parameter indicating the MIMO layer (e.g., maxRank or maxMIMO-Layers) with a value greater than 4. The UE can receive from the network node a second parameter indicating UL skipping (e.g., skipUplinkTxDynamic). The UE can be configured with 8Tx transmission. The UE can be configured with UL skipping. The UE can receive a first UL grant and a second UL grant on the first PDCCH. The first UL grant can be used for retransmission of the first MAC PDU. The second UL grant can be used for a first new transmission. If, when, and / or based on (at least) the first MAC PDU for the first PDCCH will be retransmitted and / or (where) there is no data available for transmission and / or no data available for any Logical Channel Group (LCG) and / or no available data in the (data) buffer, the UE can generate a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH. The UE can use the first UL grant to perform a retransmission for the first MAC PDU and use the second UL grant to perform a first new transmission for the second MAC PDU. The second MAC PDU may include a zero MAC SDU. The first MAC PDU may have been generated before receiving the first PDCCH. The first PDCCH may indicate a first NDI for the first UL grant and a second NDI for the second UL grant. The first PDCCH may indicate UL transmissions for two TBs. The first NDI may not be switched. The second NDI may be switched. There may be no aperiodic CSI requested for the PUSCH transmission for the first new transmission and retransmission. There may be no UCI for multiplexing the PUSCH transmission for the first new transmission and retransmission. The UE may receive a third UL grant for the second new transmission of the first MAC PDU on the second PDCCH before receiving the first PDCCH. The second PDCCH may indicate a third NDI for the third UL grant. The third NDI may be switched. The UE may receive a fourth UL grant for the third new transmission and a fifth UL grant for the fourth new transmission on the third PDCCH. If, when, and / or based on the absence of data available for transmission and / or the absence of data available for any LCG and / or the absence of available data in the (data) buffer and / or the absence of a MAC PDU for the third PDCCH, the UE may not generate a MAC PDU for the fourth UL permission and the fifth UL permission. The UE may (for the fourth UL permission and the fifth UL permission) not generate a MAC PDU containing zero MAC SDU (either of these).

[0647] In one instance, the UE can receive from the network node a first parameter indicating the MIMO layer (e.g., maxRank or maxMIMO-Layers) with a value greater than 4. The UE can receive from the network node a second parameter indicating UL skipping (e.g., skipUplinkTxDynamic). The UE can be configured with 8Tx transmission. The UE can be configured with UL skipping. The UE can receive a first UL grant and a second UL grant on the first PDCCH. The first UL grant can be used for a first new transmission. The second UL grant can be used for a second new transmission. The UE can use the first UL grant to perform a first new transmission for a first MAC PDU and use the second UL grant to perform a second new transmission for a second MAC PDU. The UE can receive a third UL grant and a fourth UL grant on the second PDCCH. The third UL grant can be used for retransmission of the first MAC PDU. The fourth UL grant can be used for a third new transmission. If, when, and / or based on a (at least) first MAC PDU to be retransmitted for the second PDCCH, there is no data available for transmission and / or no data available for any LCG and / or no available data in the (data) buffer, the UE may generate a third MAC PDU in response to a fourth UL grant indicated by the second PDCCH. The UE may use the third UL grant to perform a retransmission for the first MAC PDU and use the fourth UL grant to perform a third new transmission for the third MAC PDU. The first PDCCH may indicate a first NDI for the first UL grant, where the first NDI is switched. The first PDCCH may indicate a second NDI for the second UL grant, where the second NDI is switched. The second PDCCH may indicate a third NDI for the third UL grant, where the third NDI is not switched. The second PDCCH may indicate a fourth NDI for the fourth UL grant, where the fourth NDI is switched. The third MAC PDU may include a zero MAC SDU. The non-periodic CSI requested for the PUSCH transmission for the third new transmission and retransmission may not exist. There may be no UCI for multiplexing the PUSCH transmission for the third new transmission and retransmission. The first PDCCH may indicate a UL transmission for two TBs. The second PDCCH may indicate another / another UL transmission for two TBs. The UE may receive a fifth UL grant for the fourth new transmission and a sixth UL grant for the fifth new transmission on the third PDCCH. If, when, and / or based on the absence of data available for transmission, and / or the absence of data available for any LCG and / or the absence of available data in the (data) buffer and / or the absence of a MAC PDU for the third PDCCH, the UE may not generate a MAC PDU for the fifth UL grant and the sixth UL grant.The UE may (for both the fifth UL grant and the sixth UL grant) not generate a MAC PDU containing a zero MAC SDU (either of these).

[0648] To address this issue, the UE can skip two UL transmissions for a given TTI (Time-of-Transmission) spatial multiplexing. When the UE receives one UL grant for a new transmission and another UL grant for a retransmission for a given TTI, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for that given TTI. When the UE is configured for UL spatial multiplexing, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for that given TTI. When the UL grant associated with the TTI is for a UL spatial multiplexed transmission, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for that given TTI.

[0649] When a UE receives one UL grant for a new transmission and another UL grant for a retransmission, and the MAC PDU for the new transmission contains only padding, the UE can skip the two UL transmissions for a given TTI that are UL spatially multiplexed. When a UE receives one UL grant for a new transmission and another UL grant for a retransmission for a TTI, and the MAC PDU for the new transmission contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDU, the UE can skip the two UL transmissions for a given TTI that are UL spatially multiplexed. When a UE receives one UL grant for a new transmission and another UL grant for a retransmission for a TTI, and the MAC PDU for the new transmission (or a MAC PDU associated with one of the UL grants) contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDU, and the MAC for the retransmission has been generated, the UE can skip the two UL transmissions for a given TTI that are UL spatially multiplexed.

[0650] For example, when there is no data available for transmission and / or data for any LCG and / or no data in the (data) buffer and the UE receives one UL grant for a new transmission and another UL grant for a retransmission for a given TTI, the multiplexing and combining entity may not generate any MAC PDU. For example, if another MAC PDU for a new transmission for a given TTI is not obtained, the HARQ entity may discard the MAC PDU for retransmission (e.g., one previously generated). For example, if no MAC PDU for a new transmission for a given TTI is obtained and a MAC PDU for retransmission has been generated, the HARQ entity may not instruct the PHY to generate a transmission. If no MAC PDU for a new transmission for a TTI is obtained and a MAC PDU for a retransmission for a TTI has been generated, the UE may not perform a transmission in that TTI.

[0651] NW can configure UL spatial multiplexing and a second parameter (e.g., skipUplinkTxDynamic) for the UE. The UE can receive one UL grant for a new transmission and another UL grant for a retransmission.

[0652] In one instance, if the UE does not receive another MAC PDU for the TTI when it receives one UL grant for a new transmission and another UL grant for a retransmission, the UE may discard the MAC PDU for the TTI retransmission or clear the HARQ buffer associated with the MAC PDU for the TTI retransmission. If no MAC PDU for the TTI new transmission is received, the UE may discard another MAC PDU for the TTI retransmission. The UE may clear the relevant HARQ buffer associated with the TTI and / or not indicate that the identified HARQ process for the TTI triggers a retransmission.

[0653] In one instance, if the UE does not obtain a MAC PDU for the new transmission for the TTI when it receives one UL grant for a new transmission and another UL grant for a retransmission for the TTI, the UE may not instruct the PHY in the UE to generate a transmission. If the UE receives one UL grant for a new transmission and another UL grant for a retransmission for the TTI and obtains a MAC PDU for the new transmission for the TTI, the UE may instruct the generation of a transmission for the MAC PDU. Otherwise, the UE may clear the relevant HARQ buffer.

[0654] When scheduling a UE for new transmissions and retransmissions for a TTI, the NW may request a non-periodic CSI for the TTI.

[0655] The following TPs can be considered examples of the present invention:

[0656]

[0657] To address this issue, the UE may not skip any UL transmissions (or dual codewords or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layers>4) for 8Tx. The UE may be configured with 8Tx (or dual codewords or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layers>4). The UE may not have any available data for the (new) transmission. The UE may have (previously) generated a (second) TB or MAC PDU. The UE may receive one UL grant for a new transmission of a TB / MAC PDU for a HARQ process and / or time slot, and receive UL grants for retransmissions of another TB / MAC PDU (e.g., a second TB / MAC PDU) for the (same) HARQ process and / or said time slot. UL grants for new transmissions and retransmissions can be used for UL spatial multiplexing and / or for transmissions in the same time / frequency resource. UL grants for new transmissions and retransmissions can be used for 8Tx or two TB transmissions.

[0658] The UE may receive a UL grant (for a TTI) for a new transmission of a (first) (e.g., a TB / MAC PDU to be generated) and a UL grant (for a TTI) for a retransmission of a (second) (e.g., a previously generated) TB or MAC PDU. When the UE receives a UL grant for a new transmission and another UL grant (for a TTI) for a retransmission and / or when no data is available for transmission and / or for any LCG and / or in the (data) buffer, the UE may not skip the UL transmission and / or may generate a MAC PDU for the new transmission for the HARQ process and / or the TTI. Due to or in response to a retransmission (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)) (for a TTI), the UE may not skip the UL transmission and / or may generate a MAC PDU for the new transmission for the HARQ process and / or the TTI. When the UE receives a UL grant for a new transmission for retransmission in relation to the HARQ process and / or TTI, the UE can generate a single MAC PDU containing only padding for the new transmission (e.g., for the HARQ process and / or TTI). Due to or in response to a retransmission (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)) (for the TTI), the UE can generate a single MAC PDU containing only padding for the new transmission. When the UE receives a UL grant for both a new transmission and a retransmission in relation to the HARQ process and / or TTI, the UE can generate a single MAC PDU for the new transmission containing only a MAC CE for padding the BSR or a periodic BSR with zero MACSDU (e.g., for the HARQ process and / or TTI). Due to or in response to a retransmission for a HARQ process and / or TTI (e.g., triggered) (e.g., for another MAC PDU (e.g., previously generated)), the UE can generate a MAC PDU for the new transmission, which contains only MAC CEs for filling the BSR or for a periodic BSR with zero MAC SDUs (e.g., for the HARQ process and / or TTI). The UE can perform a UL transmission for the HARQ process and / or in the TTI with one MAC PDU for the new transmission and another MAC PDU for the retransmission. For example, when the UE receives a UL grant for the HARQ process and / or TTI for both the new transmission and the retransmission, the multiplexing and combining entity can ignore the condition of not generating a MAC PDU. For example, when the UE receives a UL grant for the HARQ process and / or TTI for both the new transmission and the retransmission, the HARQ entity can instruct the multiplexing and combining entity to generate a filling MAC PDU.For example, when the UE receives a UL grant for a HARQ process and / or a TTI for a new transmission and a retransmission, the HARQ entity can obtain a MAC PDU from another / other HARQ buffer. The NW can configure the UE with 8Tx (or dual codewords or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layers>4) and a second parameter (e.g., skipUplinkTxDynamic) to indicate UL skipping. The UE can receive the second parameter (e.g., skipUplinkTxDynamic) for UL skipping from the NW. The UE can receive a first parameter (e.g., maxRank, maxMIMO-Layers) from the NW as a value greater than 4 to indicate the MIMO layer. For a given HARQ process and / or for a given TTI, the UE can receive a UL grant indicated by the PDCCH for a new transmission of one TB / MAC PDU and a retransmission of another TB / MAC PDU.

[0659] In one instance, when the UE receives a UL grant for both new transmission and retransmission for a HARQ process and / or a TTI, the UE can generate a MAC PDU for the HARQ process and / or the TTI, regardless of whether the UE has available data. When the UE does not have data available for transmission and / or when the UE receives a UL grant for both new transmission and retransmission for a HARQ process and / or a TTI, the UE can generate a MAC PDU for a given TTI. In the case of the LCP procedure, if the UE does not have data available for transmission, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic) granting addressing to the C-RNTI, and / or the UE does not have a UL grant for both TBs for the HARQ process and / or the TTI, and / or the UE has a UL grant for both TBs for new transmission for both the HARQ process and / or the TTI, then the UE may not generate a MAC PDU.

[0660] In one instance, when the UE is configured for 8Tx, the UE can generate a MAC PDU regardless of whether the UE has available data. In the case of the LCP procedure, if the UE does not have data available for transmission, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic) to allow addressing to C-RNTI, and / or the PHY is not configured for 8Tx, the UE may not generate a MAC PDU.

[0661] In one instance, when UL permission is granted for 8Tx, the UE can generate a MAC PDU regardless of whether it has data available for transmission. In the case of the LCP procedure, if the UE does not have data available for retransmission, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), and / or permission is granted to address to a C-RNTI not used for 8Tx, then the UE may not generate a MAC PDU.

[0662] In one instance, when the UE has one UL grant for both the new transmission and the retransmission for the HARQ process and / or TTI, if the UE has not received a MAC PDU for the new transmission for the HARQ process and / or TTI, the UE can generate a padding MAC PDU. If a MAC PDU for the new transmission to be transmitted has not yet been received for the HARQ process and / or TTI, and a MAC PDU for the retransmission has been generated, the UE can instruct the multiplexing and combining entity to generate a padding MAC PDU for the new transmission. When a UL grant for both TBs for the new transmission for the HARQ process and / or TTI is received, a padding MAC PDU may not be generated.

[0663] In one instance, when the UE has a UL grant for the HARQ process and / or TTI for new transmission and for retransmission, if the UE does not obtain a MAC PDU for the new transmission of the HARQ process and / or TTI, the UE can obtain a MAC PDU from another / other HARQ buffer.

[0664] If a MAC PDU for a new transmission has not yet been obtained, and the UE has a UL grant for both the new transmission and the retransmission for the HARQ process and / or TTI, the UE can obtain a MAC PDU from another HARQ buffer associated with the HARQ process and / or TTI. When the UE has a UL grant for both the HARQ process and / or TTI for the new transmission (both TBs), the UE may not obtain a MAC PDU from another / other HARQ buffer. When the UE has a UL grant for both the HARQ process and / or TTI for the new transmission (both TBs), for example, if no data is available for transmission, the UE may not obtain a MAC PDU for the new transmission.

[0665] In the above examples, one or both of the MAC PDUs associated with a given TTI may contain only padding, padding BSRs and / or periodic BSRs with zero MAC SDUs.

[0666] The following TPs can be considered examples of the present invention:

[0667]

[0668] For example, if at least one MAC PDU (e.g., a first MAC PDU) will be retransmitted for the HARQ process, the UE (its MAC entity) can generate a MAC PDU (e.g., a second MAC PDU) corresponding to the UL permission indicated to the HARQ process. Alternatively and / or additionally, if at least one MAC PDU (e.g., a first MAC PDU) has already been generated for the HARQ process, the UE (its MAC entity) can generate a MAC PDU (e.g., a second MAC PDU) corresponding to the UL permission indicated to the HARQ process. The UE can receive the UL permission indicated to the HARQ process. The UL permission can be associated with or indicate two TBs. The HARQ process can support two TBs. The first TB of the two TBs can be used for retransmission. The second TB of the two TBs can be used for new transmission. The UL permission can indicate both retransmission and new transmission. The UE can use the UL permission to retransmit the first MAC PDU for the first TB. There may not be available data for the new transmission (for the second TB). The second MAC PDU used for a new transmission may contain only padding, a padding BSR, and / or a periodic BSR with zero MAC SDUs. The UE may generate the second MAC PDU based on the first MAC PDU to be retransmitted. The UE may also generate the second MAC PDU based on the first MAC PDU already generated.

[0669] For example, if at least one MAC PDU (e.g., a first MAC PDU) will be generated for a HARQ process, the UE (its MAC entity) can generate two MAC PDUs (e.g., a first MAC PDU and a second MAC PDU) in response to a UL grant indicated to the HARQ process. The UE can receive the UL grant indicated to the HARQ process. The UL grant can be associated with or indicate two TBs. The HARQ process can support two TBs for a new transmission. The UL grant can indicate two new transmissions. There may not be available data for one of the new transmissions. The first MAC PDU for one of the new transmissions can be generated using available data. The second MAC PDU for one of the new transmissions may only contain padding, padding BSRs, and / or periodic BSRs with zero MAC SDUs. The UE can generate the second MAC PDU based on the first MAC PDU to be generated.

[0670] To address this issue, the UE can skip two UL transmissions for the HARQ process and / or for the TTI in 8Tx. When the UE receives one UL grant for a new transmission and one for a retransmission for the HARQ process and / or for the TTI, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for the HARQ process for a given TTI. When the UE is configured for 8Tx, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for the HARQ process and / or the TTI. When the UL grant associated with the HARQ process and / or the TTI is for an 8Tx transmission, if the UE does not have data available for transmission, the UE can skip the UL transmission and / or not generate any MAC PDU for the HARQ process and / or the TTI.

[0671] When the UE receives a UL grant for both new transmission and retransmission, and the MAC PDU for new transmission contains only padding, the UE can skip two UL transmissions for the HARQ process and / or for the TTI (Time To Experience). When the UE receives a UL grant for both new transmission and retransmission for both HARQ process and / or for TTI, and the MAC PDU for new transmission contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDU, the UE can skip two UL transmissions for both HARQ process and / or for TTI (Time To Experience). When the UE receives a UL grant for both new transmission and retransmission for both HARQ process and / or for TTI (Time To Experience), and the MAC PDU for new transmission contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDU, and the MAC for retransmission has been generated, the UE can skip two UL transmissions for both HARQ process and / or for TTI (Time To Experience).

[0672] For example, when no data is available for transmission and the UE receives a UL grant for both new transmission and retransmission for the HARQ process and / or TTI, the multiplexing and combining entity may not generate any MAC PDU. For example, if no other MAC PDU for new transmission in the HARQ process and / or TTI is obtained, the HARQ entity may discard the MAC PDU for retransmission (e.g., one previously generated). For example, if no MAC PDU for new transmission in the HARQ process and / or TTI is obtained and a MAC PDU for retransmission has been generated, the HARQ entity may not instruct the PHY to generate a transmission. If no MAC PDU for new transmission in the HARQ process and / or TTI is obtained and a MAC PDU for retransmission has been generated, the UE may not perform a transmission in the HARQ process and / or TTI.

[0673] The NW can configure the UE for UL using 8Tx (or dual codeword or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layers>4) and a second parameter (e.g., skipUplinkTxDynamic). The UE can receive a UL grant for a new transmission for one TB / MAC PDU and a retransmission for another TB / MAC PDU.

[0674] In one instance, when the UE receives a UL grant for both new transmission and retransmission for a HARQ process and / or TTI, if no further MAC PDU will be obtained for the HARQ process and / or TTI, the UE may discard the MAC PDU for retransmission for the HARQ process and / or TTI, or clear the HARQ buffer associated with the MAC PDU for retransmission for the HARQ process for the TTI. If no MAC PDU for new transmission is obtained for the HARQ process and / or TTI, the UE may discard the other MAC PDU for retransmission for the HARQ process for the TTI. The UE may clear the associated HARQ buffer associated with the HARQ process and / or TTI and / or not indicate that the identified HARQ process (e.g., for the TTI) triggers a retransmission.

[0675] In one instance, when the UE receives a UL grant for a new transmission and a retransmission for the HARQ process and / or TTI, if it does not obtain a MAC PDU for a new transmission for the HARQ process and / or TTI, the UE may not instruct the PHY in the UE to generate a transmission. If the UE receives a UL grant for a new transmission and a retransmission for the HARQ process and / or TTI and obtains a MAC PDU for a new transmission for the HARQ process and / or the TTI, the UE may instruct the generation of a transmission for the MAC PDU. Otherwise, the UE may clear the relevant HARQ buffer.

[0676] When scheduling new transmissions and retransmissions permitted for HARQ processes and / or ULs for the UE, the NW may request aperiodic CSI and / or UCI for HARQ processes and / or UL transmissions.

[0677] The following TPs can be considered examples of the present invention:

[0678]

[0679] To address this issue, the UE may not skip any UL transmissions for 8Tx. When the UE receives (for a TTI) one or both UL grants for two TBs, the UE may (for a given TTI) not skip UL transmissions and / or may generate two MAC PDUs. The two MAC PDUs may correspond to a double codeword and / or 8Tx and / or maxRank > 4 and / or maxMIMO-Layers > 4 and / or rank > 4 and / or MIMO layers > 4. The two MAC PDUs may be indicated by the (same) DCI / PDCCH. When the UE receives (for a given TTI) UL grants for two TBs and / or when at least one of the two MAC PDUs is about to be generated, the UE may not skip UL transmissions and / or may (for the TTI) generate two MAC PDUs for one or both UL grants. When the UE is configured for 8Tx, the UE may not skip UL transmissions and / or may (for a given TTI) generate two MAC PDUs for one or both UL grants. When the UL grant (as associated with a TTI) is for 8Tx, the UE may not skip the UL transmission and / or may (for a given TTI) generate two MAC PDUs for one or both UL grants. When the UE receives (for a given TTI) an indication (or associated with) a UL grant for two TBs and one of the two TBs is capable of accommodating (all) of the UE's available data (e.g., if one MAC PDU contains (all) available data and only padding is left for the other MAC PDUs), the UE may not skip the UL transmission and / or may (for the TTI) generate two MAC PDUs for one or both UL grants. When the UE receives (for a TTI) an indication (or associated with) a UL grant for two TBs and one of the MAC PDUs (or TBs) contains only padding, the UE may (for a given TTI) not skip the UL transmission and / or may generate two MAC PDUs. When a UE receives (for a given TTI) an indication (or associated with) two TBs of UL permission and one of the MAC PDUs (or TBs) contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDUs, the UE may not skip the UL transmission and / or may (for the TTI) generate two MAC PDUs for one or both UL permission. When a UE receives (for a given TTI) an indication (or associated with) two TBs of UL permission and one of the two TBs is capable of accommodating all available data of the UE (e.g., if one MAC PDU contains available data and only fills for the other MAC PDUs), the UE may not skip the UL transmission and / or may (for the TTI) generate two MAC PDUs for one or both UL permission.When a UE receives (for a given TTI) an indication (or association with) two TBs of UL permission, one of the MAC PDUs (or TBs) contains only a MAC CE for filling a BSR or a periodic BSR with zero MAC SDUs, and the other of the MAC PDUs (or TBs) contains data or a MAC SDU, the UE may not skip the UL transmission and / or may (for the TTI) generate two MAC PDUs for one or both UL permission. “8Tx” can be referred to, replaced with, or supplemented with “Dual Codeword”, “maxRank>4”, “maxMIMO-Layers>4”, “Rank>4”, “MIMO Layer>4”, and / or “UL Spatial Multiplexing”.

[0680] For example, multiplexing and combining entities can separate or split available data into MAC PDUs associated with UL approval (and / or HARQ process). The UE can separate or split padding (and / or MAC CEs for filling only the BSR and / or periodic BSRs with zero MAC SDUs) into MAC PDUs associated with UL approval (and / or HARQ process). The UE ensures that both MAC PDUs include UE data. The UE ensures that both MAC PDUs include MAC SDUs. The UE ensures that both MAC PDUs include data (and padding). The UE ensures that both MAC PDUs include the MAC PDU and (at least) one of padding, MAC CEs for filling the BSR, and periodic BSRs with zero MAC SDUs. The UE ensures that the two MAC PDUs do not only include padding. The UE ensures that the two MAC PDUs do not only include MAC CEs for filling only the BSR and / or periodic BSRs with zero MAC SDUs. A single MAC PDU can hold the UE's available data. Even if one MAC PDU can hold the available data, the UE ensures that both MAC PDUs include UE data. The UE generates two PDUs because both PDUs include UL data. The UE generates two PDUs because both PDUs do not only include padding. The UE generates two PDUs because both PDUs do not only include MAC CEs used for padding BSRs or periodic BSRs with zero MAC SDUs. If UL skip is configured, the UE can separate or split the available data into MAC PDUs associated with UL approval (and / or HARQ process). If UL skip is configured, the UE can separate or split the available data into MAC PDUs for UL approval (and / or HARQ process). If UL skip is configured, the UE can separate or split the padding into MAC PDUs associated with UL approval (and / or HARQ process). If UL skip is configured, the UE can separate or split the padding into MAC PDUs for UL approval (and / or HARQ process).

[0681] If a MAC PDU cannot contain the UE's available data, the UE will not separate or split the available data into MAC PDUs associated with UL approval (and / or the HARQ process). If a MAC PDU cannot contain the UE's available data, the UE will not separate or split the available data into MAC PDUs for UL approval (and / or the HARQ process). If a MAC PDU cannot contain the UE's available data, the UE will not separate or split padding (and / or MAC CEs used to pad BSRs and / or periodic BSRs with zero MAC SDUs) into MAC PDUs associated with UL approval (and / or the HARQ process). If a MAC PDU cannot contain the UE's available data, the UE will not separate or split padding (and / or MAC CEs used to pad BSRs and / or periodic BSRs with zero MAC SDUs) into MAC PDUs for UL approval (and / or the HARQ process). If one MAC PDU cannot hold the UE's available data, the UE can place the data in one MAC PDU and the data and padding (and / or MAC CE for padding BSR and / or periodic BSR with zero MAC SDU) in another MAC PDU. If both MAC PDUs can hold the UE's available data, the UE can place the data in one MAC PDU and the data and padding in another MAC PDU. If UL skip is not configured, the UE does not separate or split the available data into MAC PDUs associated with UL grant (and / or HARQ process). If UL skip is not configured, the UE does not separate or split the available data into MAC PDUs for UL grant (and / or HARQ process). If UL skip is not configured, the UE does not separate or split the padding into MAC PDUs associated with UL grant (and / or HARQ process). If UL skip is not configured, the UE does not separate or split the padding into MAC PDUs for UL grant (and / or HARQ process).

[0682] For example, multiplexing and combining entities can ignore conditions that prevent the generation of MAC PDUs. For example, HARQ entities can instruct multiplexing and combining entities to generate populated MAC PDUs. For example, HARQ entities can obtain MAC PDUs from another / other HARQ buffer.

[0683] NW can configure UEs with 8Tx (or dual codewords or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layers>4) and parameters to indicate UL skipping (e.g., skipUplinkTxDynamic). A UE configured with 8Tx can receive UL grants indicating two TBs (for a given TTI).

[0684] In one instance, when UL grants permission indicating two TBs, the UE can generate a MAC PDU associated with the UL grant (for a single HARQ process or for two associated or paired HARQ processes), regardless of whether the UE has sufficient available data. The UE can generate a MAC PDU associated with the UL grant as long as available data exists and / or if one of the MAC PDUs will be generated when the UE receives UL grant indicating two TBs. When the UE receives UL grant indicating two TBs, the UE can generate a MAC PDU for the UL grant regardless of whether the UE has sufficient available data. In the case of the LCP procedure, if the UE does not have available data, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), grants addressing to the C-RNTI, and the UE is not granted permission for two TBs for the UL grant, the UE may not generate a MAC PDU.

[0685] In one instance, when the UE is configured for 8Tx, the UE can generate a MAC PDU regardless of whether the UE has sufficient available data. When the UE is configured for 8Tx, the UE can generate a MAC PDU as long as available data exists and / or if / if a MAC PDU will be generated. In the case of the LCP procedure, if the UE does not have available data, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic) to allow addressing to C-RNTI, and the UE is not configured for 8Tx, then the UE may not generate a MAC PDU.

[0686] In one instance, when UL permission is for 8Tx, the UE can generate a MAC PDU regardless of whether it has sufficient available data. When UL permission is for 8Tx, the UE can generate a MAC PDU as long as available data exists and / or if / would generate one of the MAC PDUs, regardless of whether the UE has sufficient available data. In the case of the LCP procedure, if the UE does not have available data, the MAC entity is configured with a second parameter (e.g., skipUplinkTxDynamic), and permission is granted to address a C-RNTI not used for 8Tx, then the UE may not generate a MAC PDU.

[0687] In one instance, when the UE has UL permission indicating two TBs, if the UE does not obtain a MAC PDU for UL permission, the UE can generate a padding MAC PDU. If the MAC PDU to be transmitted has not yet been obtained and the UE has UL permission indicating two TBs, the UE can instruct the multiplexing and combining entity to generate a padding MAC PDU.

[0688] In one instance, when the UE has a UL grant indicating two TBs, if the UE does not obtain a MAC PDU for the UL grant, the UE can obtain a MAC PDU from another / other HARQ buffer. If the MAC PDU to be transmitted has not yet been obtained and the UE has a UL grant indicating two TBs, the UE can obtain a MAC PDU from another HARQ buffer associated with the UL grant.

[0689] One or both of the MAC PDUs associated with UL approval may contain only filler, filler BSR and / or periodic BSR with zero MAC SDU.

[0690] To address the issue, under a first condition (or in response to the first condition), the UE may not skip any UL transmissions for 8Tx. Under a second condition, the UE skips one TB of UL transmissions for 8Tx. Under the first condition (or in response to the first condition), when the UE receives UL grant indicating two TBs, the UE may not skip UL transmissions and / or may generate two MAC PDUs for the UL grant. Under the second condition (or in response to the second condition), when the UE receives UL grant indicating two TBs, the UE may skip UL transmissions for (a single) TB and / or may generate (e.g., a) (single) MAC PDUs for the UL grant. The two MAC PDUs may correspond to a double codeword and / or 8Tx. Under the first condition (or in response to the first condition), when the UE receives UL grant indicating two TBs and / or when at least one of two MAC PDUs will be generated, the UE may not skip UL transmissions and / or may generate two MAC PDUs for the UL grant. Under the second condition, when the UE receives a UL grant indicating two TBs and / or when at least one of two MAC PDUs will be generated, the UE may skip the UL transmission for the (single) TB and / or may generate (e.g., a) (single) MAC PDU for the UL grant. Under the first condition (or in response to the first condition), when the UE is configured for 8Tx, the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant. Under the second condition (or in response to the second condition), when the UE is configured for 8Tx, the UE may skip the UL transmission for the (single) TB and / or may generate (e.g., a) (single) MAC PDU for the UL grant. Under the first condition (or in response to the first condition), when the UL grant is for 8Tx, the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant. Under the second condition (or in response to the second condition), when the UL grant is for 8Tx, the UE may skip the UL transmission for (a single) TB and / or may generate (e.g., a single) MAC PDU for the UL grant. Under the first condition (or in response to the first condition), when the UE receives a UL grant indicating two TBs and one of them is capable of accommodating (all) of the UE's available data (e.g., if one of the MAC PDUs accommodates (all) available data and only fills for the other MAC PDUs), the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant.Under the second condition (or in response to the second condition), when the UE receives a UL grant indicating two TBs and one of them is capable of containing (all) available data of the UE (e.g., if one of the MAC PDUs contains (all) available data and only padding is left for the other MAC PDUs), the UE may skip the UL transmission for the (single) TB and / or may generate (e.g., a (single) MAC PDU containing all available data) for the UL grant. Under the first condition (or in response to the first condition), when the UE receives a UL grant indicating two TBs and one of the MAC PDUs (associated with the UL grant) contains only padding, the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant. Under the second condition (or in response to the second condition), when the UE receives a UL grant indicating two TBs and one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only padding, the UE may skip the UL transmission for the (single) TB (e.g., with only padding) and / or may generate (e.g., a (single) MAC PDU for the UL grant (e.g., a (single) MAC PDU containing data) for the UL grant. Under a first condition (or in response to a first condition), when the UE receives a UL grant indicating two TBs and one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDUs, the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant. Under a second condition (or in response to a second condition), when the UE receives a UL grant indicating two TBs and one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDUs, the UE may skip the UL transmission for a (single) TB (e.g., a MAC CE containing only a BSR or a periodic BSR with zero MAC SDUs) and / or may generate a (single) MAC PDU for the UL grant (e.g., a MAC PDU including data). Under the first condition (or in response to the first condition), when the UE receives a UL grant indicating two TBs and one of them is capable of accommodating all available data of the UE (e.g., if one of the MAC PDUs contains available data and only fills for the other MAC PDUs), the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant.Under the second condition (or in response to the second condition), when the UE receives a UL grant indicating two TBs and one of them is capable of accommodating all available data of the UE (e.g., if one of the MAC PDUs contains available data and only filler is left for the other MAC PDUs), the UE may skip the UL transmission for the (single) TB (with only filler) and / or may generate (e.g., a (single) MAC PDU for the UL grant, such as one containing data in a MAC PDU). Under the first condition (or in response to the first condition), when the UE receives a UL grant indicating two TBs, one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDUs, and the other MAC PDU (associated with the UL grant) contains data or a MAC SDU, the UE may not skip the UL transmission and / or may generate two MAC PDUs for the UL grant. Under the second condition (or in response to the second condition), when the UE receives a UL grant indicating two TBs, one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for filling a BSR or a periodic BSR with zero MAC SDUs, and the other MAC PDU (or the MAC PDU associated with the UL grant) contains data or a MAC SDU, the UE may skip the UL transmission for a (single) TB (e.g., with zero MAC SDUs) and / or may generate a (single) MAC PDU for the UL grant (e.g., in a MAC PDU containing data). The UL grant may be used for a single HARQ process or for two associated (or paired) HARQ processes. A UL grant indicating two TBs may not be associated with different HARQ entities. A UL grant may be associated with a single HARQ process ID. A UL grant may be associated with two (associated or paired) HARQ processes for 8Tx.

[0691] Additionally and / or alternatively, a UL transmission may contain a new transmission and a retransmission corresponding to a single HARQ process (at the appropriate time). Under the first condition, the UE may perform two UL transmissions for 8Tx (e.g., generate a MAC PDU or TB for the new transmission and perform a retransmission). Under the first condition, the UE may not (is not permitted to) skip either of the UL transmissions for 8Tx. Under the second condition, the UE may not perform or may (is permitted to) skip (a portion) of the UL transmission (e.g., not generate a MAC PDU or TB for the new transmission and / or not perform a retransmission). For example, if at least one of the second conditions is met, the UE may not perform or may (is permitted to) skip the new transmission and may perform (only) a retransmission. For example, if at least one of the second conditions is met, the UE may not perform or may (is permitted to) skip the retransmission and may perform (only) a new transmission. For example, if at least one of the second conditions is met, the UE may not perform or may (is permitted to) skip both the retransmission and the new transmission.

[0692] The first condition can be one or more of the following and / or may include the following:

[0693] -If / when the two TBs and / or the two codewords are used for the same transceiver point (TRP);

[0694] -If / when the two TBs and / or the two codewords are pre-encoded jointly and / or together;

[0695] -If / when the two TBs and / or the two codewords are pre-encoded with the same pre-encoder;

[0696] - If / when the two TBs and / or the two codewords are associated with the same Transport Configuration Indicator (TCI) state and / or the same SRI and / or the same beam and / or the same UE beam and / or the same NW beam;

[0697] -If / when the two TBs and / or the two codewords are for codebook-based transmission;

[0698] -If / when the two TBs and / or the two codewords are associated with the same timing advance (TA);

[0699] -If / when neither of the two TBs and / or the two codewords is self-decoding;

[0700] -If / when the two TBs and / or the two codewords are jointly and / or encoded together (e.g., via channel coding);

[0701] -If / when the two TBs and / or the two codewords are used for different TRPs;

[0702] -If / when the two TBs and / or the two codewords are pre-encoded individually or independently;

[0703] -If / when the two TBs and / or the two codewords are pre-encoded with different pre-encoders;

[0704] -If / when the two TBs and / or the two codewords are associated with different TCI states and / or different SRIs and / or different beams and / or different UE beams and / or different NW beams;

[0705] -If / when the two TBs and / or the two codewords are used for non-codebook-based transmission;

[0706] -If / when the two TBs and / or the two codewords are associated with different TAs;

[0707] -If / when both TBs and / or both codewords are self-decoding; and / or

[0708] -If / when the two TBs and / or the two codewords are encoded individually or independently (e.g., via channel coding).

[0709] The second condition can be one or more of the following and / or may include the following:

[0710] -If / when the two TBs and / or the two codewords are used for different TRPs;

[0711] -If / when the two TBs and / or the two codewords are pre-encoded individually or independently;

[0712] -If / when the two TBs and / or the two codewords are pre-encoded with different pre-encoders;

[0713] -If / when the two TBs and / or the two codewords are associated with different TCI states and / or different SRIs and / or different beams and / or different UE beams and / or different NW beams;

[0714] -If / when the two TBs and / or the two codewords are used for non-codebook-based transmission;

[0715] -If / when the two TBs and / or the two codewords are associated with different TAs;

[0716] -If / when both TBs and / or both codewords are self-decoding;

[0717] -If / when the two TBs and / or the two codewords are encoded individually or independently (e.g., via channel coding);

[0718] -If / when the two TBs and / or the two codewords are used for the same TRP;

[0719] -If / when the two TBs and / or the two codewords are pre-encoded jointly and / or together;

[0720] -If / when the two TBs and / or the two codewords are pre-encoded with the same pre-encoder;

[0721] -If / when the two TBs and / or the two codewords are associated with the same TCI state and / or the same SRI and / or the same beam and / or the same UE beam and / or the same NW beam;

[0722] -If / when the two TBs and / or the two codewords are for codebook-based transmission;

[0723] -If / when the two TBs and / or the two codewords are associated with the same TA;

[0724] -If / when neither of the two TBs and / or neither of the two codewords is self-decoding; and / or

[0725] - If / when the two TBs and / or the two codewords are jointly and / or encoded together (e.g., via channel coding).

[0726] Allowing skipping a single TB under certain conditions can avoid transmissions with only padding (e.g., reducing unnecessary power consumption / interference / resource consumption), and also avoid problems with transmission generation / reception (e.g., decoding on the NW side). Skip transmissions of TBs with only padding. Skip transmissions of TBs without data. The UE does not generate MAC PDUs with only padding. The UE does not generate MAC PDUs without data.

[0727] To address this issue, the UE can skip two UL transmissions for 8Tx UL grants. When the UE receives a UL grant indicating two TBs, if the UE does not have sufficient available data, the UE can skip the UL transmission and / or not generate any MAC PDU for the UL grant. When the UE is configured with 8Tx, if the UE does not have sufficient available data, the UE can skip the UL transmission and / or not generate any MAC PDU for the UL grant. When the UL grant is for 8Tx transmissions, if the UE does not have sufficient available data, the UE can skip the UL transmission and / or not generate any MAC PDU for the UL grant.

[0728] When the UE receives a UL grant indicating two TBs, and one of them is capable of accommodating the UE's available data, the UE can skip the two UL transmissions for the 8Tx UL grant. The UE can skip the two UL transmissions for the 8Tx UL grant. When the UE receives a UL grant indicating two TBs, and one of the MAC PDUs associated with the UL grant contains only padding, the UE can skip the two UL transmissions for the 8Tx UL grant. When the UE receives a UL grant indicating two TBs, and one of the MAC PDUs (associated with the UL grant) contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDUs, the UE can skip the two UL transmissions for the 8Tx UL grant. When the UE receives a UL grant indicating two TBs, one of the MAC PDUs (associated with the UL grant) contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDUs, and the other MAC PDU contains data or a MAC SDU, the UE can skip the two UL transmissions for the 8Tx UL grant.

[0729] The UE may skip UL transmission and / or not generate any MAC PDU for UL grant when the following occurs: the UE receives a UL grant indicating two TBs, one of which is capable of holding the UE's available data; the UE receives a UL grant indicating two TBs and the MAC PDU associated with the UL grant contains only padding; the UE receives a UL grant indicating two TBs and one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDUs; and / or the UE receives a UL grant indicating two TBs, one of the MAC PDUs (or the MAC PDU associated with the UL grant) contains only a MAC CE for padding the BSR or a periodic BSR with zero MAC SDUs, and the other MAC PDU contains data or a MAC SDU.

[0730] For example, when the available data is insufficient for the two TBs required for UL approval, the multiplexing and combining entity may not generate any MAC PDU. For example, if no other MAC PDU is available for UL approval, the HARQ entity may discard the MAC PDU. For example, if none of the MAC PDUs associated with UL approval are available, the HARQ entity may not instruct the PHY to generate a transmission.

[0731] NW can configure 8Tx and a second parameter (e.g., skipUplinkTxDynamic) for the UE. The UE can be instructed (at the same TTI) for two TBs UL-approved.

[0732] In one instance, when the UE receives a UL grant indicating two TBs, if no other MAC PDU associated with the UL grant is obtained, the UE can discard the MAC PDU. The UE can also clear the associated HARQ buffer for the UL grant and not deliver the MAC PDU associated with the UL grant used for the identified HARQ process.

[0733] In one instance, when the UE receives a UL grant indicating two TBs, if it does not obtain the two MAC PDUs associated with the UL grant, the UE may not instruct the PHY in the UE to generate a transmission. If the UE receives a UL grant indicating two TBs and obtains another MAC PDU associated with the UL grant, the UE may instruct the generation of a transmission for the MAC PDU. Otherwise, the UE may clear the relevant HARQ buffer.

[0734] The UE can be configured with 8Tx (e.g., by receiving parameters indicating the MIMO layer with a value greater than 4) and UL skipping (e.g., by receiving parameters indicating UL skipping). The UE can receive a DCI / PDCCH indicating UL transmission for two transport blocks. The DCI can be in the DCI format associated with 8Tx. The DCI can be DCI format 4. The DCI enables two transport blocks. The DCI does not indicate I / O for two transport blocks. MCS =0 and N PRB Combinations >1 and I MCS =28 and N PRB =1 combination. UE (MAC) generates one PDU for one of the two transport blocks. UE (MAC) does not generate one PDU for the other of the two transport blocks. UE (MAC) does not generate one PDU for the other of the two transport blocks due to UL skipping. UE (MAC) does not generate one PDU for the other of the two transport blocks because one PDU is sufficient to hold the UE's available data. UE (MAC) does not generate the one PDU for the other of the two transport blocks because the one PDU for the other of the two transport blocks only includes padding. UE (MAC) does not generate the one PDU for the other of the two transport blocks because the one PDU for the other of the two transport blocks only includes MAC CE for padding BSR or periodic BSR with zero MAC SDU.

[0735] The UE (PHY) does not respond to the DCI and performs a UL (PUSCH) transmission. If a MAC PDU is generated, the UE (PHY) does not respond to the DCI and performs a PUSCH transmission. If no MAC PDU (or another) is generated, the UE (PHY) does not respond to the DCI and performs a PUSCH transmission. If only one MAC PDU is generated, the UE (PHY) does not respond to the DCI and performs a PUSCH transmission. If two MAC PDUs are generated, the UE (PHY) responds to the DCI and performs a PUSCH transmission. The UE (PHY) only responds to the DCI and performs a PUSCH transmission when two MAC PDUs are generated. If no MAC PDU is generated or only one MAC PDU is generated, the UE (PHY) does not respond to the DCI and performs a PUSCH transmission.

[0736] The UE (PHY) disables the TB used for UL (PUSCH) transmission. Even if the DCI does not disable the TB, the UE (PHY) disables the TB used for PUSCH transmission. Since there is no MAC PDU, the UE (PHY) disables the TB used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) disables the TB used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) enables the TB used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) disables a specific or predefined TB used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) disables TB1 used for PUSCH transmission. If a MAC PDU is generated, the UE PHY disables TB2 used for PUSCH transmission. The UE (PHY) enables another TB. If a MAC PDU is generated, the UE (PHY) disables a specific or predefined codeword used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) disables codeword 1 used for PUSCH transmission. If a MAC PDU is generated, the UE (PHY) disables codeword 0 for PUSCH transmission. The UE (PHY) enables another codeword. The UE uses an enabled TB to carry the generated PDU. The UE (PHY) uses an enabled codeword to carry the generated PDU. The UE (PHY) uses a certain number of layers to perform UL transmission, which is different from the number of layers indicated by the DCI. The UE (PHY) may determine the number (for transmission) based on the DCI's "Precoding Information and Number of Layers" field. The UE (PHY) may determine the number (for transmission) based on the DCI's "Precoding Information and Number of Layers" field and assume one TB / codeword is disabled. The UE (PHY) may determine the number (for transmission) from a column of a codeword (even if the DCI indicates that two codewords are enabled). The UE (PHY) may determine the precoder based on the DCI's "Precoding Information and Number of Layers" field and use a column of a codeword (even if the DCI indicates that two codewords are enabled). The UE (PHY) can determine the precoder from a column of one codeword (even if the DCI indicates that two codewords are enabled). The difference in the number of layers is due to the UE (itself) disabling one TB (not by the DCI). The UE (PHY) uses the precoder to perform UL transmission, where the precoder is different from the precoder indicated by the DCI. The UE (PHY) uses precoding to perform UL transmission based on the DCI's "Precoding Information and Number of Layers" field. The UE (PHY) determines the precoder based on the DCI's "Precoding Information and Number of Layers" field and assumes that one TB / codeword is disabled. The UE (PHY) can determine the precoder based on the DCI's "Precoding Information and Number of Layers" field and use a column of one codeword (even if the DCI indicates that two codewords are enabled).The UE (PHY) can determine the precoder from a column of a codeword (even if the DCI indicates that two codewords are enabled). The difference in the precoder is due to the UE (itself) deactivating a TB (not deactivated by the DCI). If no MAC PDU (or another) is generated, the UE (PHY) deactivates the TB used for PUSCH transmission. If only one MAC PDU is generated, the UE (PHY) deactivates the TB used for PUSCH transmission. If two MAC PDUs are generated, the UE (PHY) does not deactivate the TB used for UL (PUSCH) transmission. If two MAC PDUs are generated, the UE (PHY) enables both TBs for UL (PUSCH) transmission. PUSCH can be a new transmission. Since the number of codewords (or TBs) is the same as the number of MAC PDUs generated (e.g., after deactivating one TB), the UE is able to perform the corresponding PUSCH transmission.

[0737] The following is an example of a four-antenna-port configuration:

[0738]

[0739] Conventionally, when the DCI indicates that two codewords are enabled, the UE determines the number of layers and the precoder (Transmission Precoding Matrix Indicator (TPMI)) based on the column associated with the two codewords (the rightmost column) and also based on the DCI's "Precoding Information and Number of Layers" field. For example, when "Precoding Information and Number of Layers" equals 1 and the DCI enables two codewords, the UE will perform UL transmission with 2 TBs, 2 layers, and TPMI = 1. The above embodiments suggest using a combination of columns associated with one codeword. For example, the UE can perform UL transmission with 1 TB, 1 layer, and TPMI = 1 (e.g., based on "Precoding Information and Number of Layers" equal to 1). Alternatively, specific entries of the column can be used. For example, the UE can perform UL transmission with 1 TB, 1 layer, and TPMI = 0 (e.g., the lowest entry or a predefined entry, or a specific entry of the one codeword column).

[0740] The UE (PHY) performs UL transmission for a (generated) MAC PDU. If a MAC PDU is generated, the UE (PHY) performs UL transmission for that MAC PDU. The UE (PHY) does not perform UL transmission for another MAC PDU not generated by the MAC. The UE (PHY) performs UL transmission with a codeword (or TB). The codeword can be codeword 0. The codeword can be codeword 1. The UE (PHY) uses a certain number of layers to perform UL transmission, where the number differs from the number of (layers) indicated by the DCI. The UE (PHY) may determine the number (for transmission) based on the "Precoding Information and Number of Layers" field of the DCI. The UE (PHY) may determine the number (for transmission) based on the "Precoding Information and Number of Layers" field of the DCI and assume that one TB / codeword is disabled. The UE (PHY) may determine the number (for transmission) from a column of a codeword (even if the DCI indicates that two codewords are enabled). The UE (PHY) can determine the precoder based on the "Precoding Information and Number of Layers" field of the DCI and use a column of one codeword (even if the DCI indicates that two codewords are enabled). The UE (PHY) can determine the precoder from a column of one codeword (even if the DCI indicates that two codewords are enabled). The difference in the number of layers is due to the UE (itself) disabling one TB (not by the DCI). The UE (PHY) uses the precoder to perform UL transmission, where the precoder is different from the precoder indicated by the DCI. The UE (PHY) uses the precoder to perform UL transmission based on the "Precoding Information and Number of Layers" field of the DCI. The UE (PHY) determines the precoder based on the "Precoding Information and Number of Layers" field of the DCI and assumes that one TB / codeword is disabled. The UE (PHY) can determine the precoder based on the "Precoding Information and Number of Layers" field of the DCI and use a column of one codeword (even if the DCI indicates that two codewords are enabled). The UE (PHY) can determine the precoder from a column of one codeword (even if the DCI indicates that two codewords are enabled). The difference in the precoder is due to the UE (itself) disabling a TB (rather than being disabled by the DCI).

[0741] If two MAC PDUs are generated, the UE (PHY) performs UL transmission for both MAC PDUs. The UE (PHY) performs UL transmission with two codewords. The UE (PHY) uses a certain number of layers and / or precoders to perform UL transmission, wherein the number of layers and precoders are determined based on the DCI. The UE (PHY) uses the number of layers and / or precoders from the columns of the two codewords to perform UL transmission. In other words, if two MAC PDUs are generated, the UE follows the conventional method to determine the number of layers and / or precoders to perform UL transmission.

[0742] The NW may need to try different decoding hypotheses because it may not know the number of TBs and / or layers and / or precoder used. This may be because the NW may not know whether the UE will generate one or two MAC PDUs (related to the UE's buffer state). The NW may need to blindly decode different hypotheses. For example, the NW could decode using one hypothesis that generates two MAC PDUs and another hypothesis that generates one MAC PDU.

[0743] The UE (PHY) performs a UL transmission for one MAC PDU. If a MAC PDU is generated, the UE (PHY) performs a UL transmission for that MAC PDU. The UE (PHY) does not perform a UL transmission for another MAC PDU not generated by the MAC. If a MAC PDU is generated, the UE (PHY) performs a UL transmission for that MAC PDU. The UE (PHY) performs a UL transmission using two codewords (or TBs). One of the two codewords (or TBs) carries the (generated) MAC PDU. The other of the two codewords (or TBs) carries a set of bits. The set of bits can be randomly generated. The set of bits can have specific values ​​or predefined values, for example, all 0s or all 1s or 0101, ... The set of bits can be padding bits or dummy bits. The set of bits can be generated by the PHY. The set of bits is not received from the MAC. One of the two codewords (or TBs) includes data from the UE. The other of the two codewords (or TBs) does not include data from the UE. The other of the two codewords (or TBs) is a special codeword (or TB). The other of the two codewords (or TBs) is a predefined codeword (or TB). The other of the two codewords (or TBs) is a dummy codeword (or TB). The other of the two codewords (or TBs) is filled with pre-known or random information.

[0744] The above solutions may apply under certain conditions but not under others. These conditions may be one or more of the first conditions described above. These other conditions may be one or more of the second conditions described above.

[0745] In the above embodiments, the pre-encoder can be used for 8Tx.

[0746] Throughout this disclosure, one or more of the embodiments / concepts / methods / examples may be combined in whole or in part.

[0747] Throughout this disclosure, if / when a TB / codeword is self-decoding, then the decoding of a TB / codeword can be successfully accomplished on its own without requiring and / or depending on the decoding of another TB / codeword and / or any other TB / codeword.

[0748] Throughout this disclosure, "8Tx" can be referred to as, replaced by, or supplemented with "double codeword" or "two TB transmission" or "double codeword transmission" or "maxRank>4" or "maxMIMO-Layers>4" or "rank>4" or "MIMO layer>4" or "UL spatial multiplexing". "8Tx" or "double codeword" or "two TB transmission" or "double codeword transmission" or "maxRank>4" or "maxMIMO-Layers>4" or "rank>4" or "MIMO layer>4" can be used interchangeably.

[0749] Throughout this disclosure, TTI can be or referred to as a time slot, subframe, micro-time slot, sub-time slot, sTTI, symbol, 2 symbols, 3 symbols, 7 symbols, or the duration of a data channel. TTI can be or referred to as a (specific) moment, duration, and / or point in time, such as indicated by DCI / PDCCH.

[0750] Throughout this disclosure, UL transmission can be PUSCH transmission.

[0751] Throughout this disclosure, "not permitted" can be replaced with "blocked" or "prohibited".

[0752] Throughout this disclosure, “NW is / may not be allowed to be configured” can be replaced with “UE is / may not be expected to be configured”.

[0753] Throughout this disclosure, “NW not allowed indication” can be replaced with “UE not expected to be indicated”.

[0754] Throughout this disclosure, the UE can be configured by the NW using a single cell.

[0755] Throughout this disclosure, UL grants associated with a TTI, UL grants for a given TTI, and / or UL grants for a given TTI can be used interchangeably. UL grants associated with a TTI, UL grants for a given TTI, and / or UL grants for a given TTI are (for a serving cell) (for a HARQ entity) UL grants received for the same TTI.

[0756] Throughout this disclosure, the MAC PDU associated with a TTI, the MAC PDU for a given TTI, and / or the MAC PDU for a given TTI can be used interchangeably. The MAC PDU associated with a TTI, the MAC PDU for a given TTI, and / or the MAC PDU for a given TTI are MAC PDUs that are authorized to be generated (and transmitted) for UL reception for the same TTI.

[0757] Throughout this disclosure, the terms used for, at, and / or associated with TTI can be used interchangeably.

[0758] Throughout this disclosure, two TBs and / or two MAC PDUs may be associated with one UL grant or two UL grants.

[0759] Throughout this disclosure, a UL permits the use of a new transmission for one TB / MAC PDU and a transmission for another TB / MAC PDU.

[0760] Throughout this disclosure, non-periodic CSI is not requested for PUSCH and / or for PUSCH transmissions and / or for TTI, and / or multiplexing UCI will not be used. A PUSCH transmission can be, for example, a two-TB transmission of a new transmission and a retransmission.

[0761] Throughout this disclosure, UL grants can be indicated via a DCI (e.g., DCI_format 0_1). One UL grant can be indicated via a first NDI associated with a first transport block (TB). Another UL grant can indicate a second NDI associated with a second transport block (TB). One UL grant can indicate whether the first TB is a new transmission or a retransmission based on the first NDI. The other UL grant can indicate whether the second TB is a new transmission or a retransmission based on the second NDI.

[0762] Throughout this disclosure, the soft buffer is associated with the (DL)HARQ process, and the HARQ buffer is associated with the (UL)HARQ process.

[0763] The UE can receive configurations related to 8Tx (or dual-codeword or two-TB transmission or dual-codeword transmission or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layer>4). The UE can be configured by the NW for 8Tx (or dual-codeword or two-TB transmission or dual-codeword transmission or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layer>4). The UE can, for example, dynamically receive UL permission on the PDCCH for 8Tx (or dual-codeword or two-TB transmission or dual-codeword transmission or maxRank>4 or maxMIMO-Layers>4 or rank>4 or MIMO layer>4). The UE can be referred to as the UE, the UE's MAC, the UE's PHY, the UE's HARQ entity, the UE's multiplexing and combining entity, or the UE's HARQ process.

[0764] A UE can be referred to as a UE or a MAC entity of a UE.

[0765] The UE can be an LTE device. The UE can be an NR device. The UE can be a lightweight NR device. The UE can be a device with insufficient capabilities. The UE can be a mobile phone. The UE can be a wearable device. The UE can be a sensor. The UE can be a fixed device.

[0766] NW can be a base station. NW can be an access point. NW can be an evolved Node B (eNB). NW can be an NR Node B (gNB). Throughout this disclosure, network, network node, base station, access point, eNB and / or gNB can be used interchangeably.

[0767] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0768] See Figure 5 Regarding such and other concepts, systems and methods of the present invention, method 1000 for a UE in a wireless communication system includes being configured with maxRank>4 and / or maxMIMO-Layers>4 and UL skipping (step 1002), receiving two UL grants for a TTI from a base station (step 1004), generating two MAC PDUs for the TTI when one of the two MAC PDUs is capable of accommodating all available data of the UE (step 1006), and transmitting the two MAC PDUs to the base station (step 1008).

[0769] In various embodiments, a UE configured with maxRank>4 and / or maxMIMO-Layers>4 receives up to two UL grants for TTI.

[0770] In various embodiments, if no data is available for MAC PDU transmission, a UE configured with UL skipping is allowed not to generate a MAC PDU for dynamic UL.

[0771] In various embodiments, the two UL grants are dynamic UL grants for HARQ entities.

[0772] In various embodiments, there is no non-periodic CSI requested for TTI.

[0773] In various embodiments, one of the two MAC PDUs contains only a MAC CE for filling the BSR or a periodic BSR with zero MACSDU.

[0774] In various embodiments, the method further includes the UE not generating any MAC PDU for TTI when neither of the two MAC PDUs contains available data or when both MAC PDUs contain only MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs.

[0775] Backtracking Reference Figure 3 and Figure 4In one or more embodiments from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) be configured with maxRank > 4 and / or maxMIMO-Layers > 4 and UL skip; (ii) receive two UL grants for TTI from the base station; (iii) generate two MAC PDUs for the TTI when one of the two MAC PDUs is capable of accommodating all available data of the UE; and (iv) transmit the two MAC PDUs to the base station. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0776] See Figure 6 Regarding such and other concepts, systems and methods of the present invention, method 1010 for a UE in a wireless communication system includes being configured with maxRank > 4 and / or maxMIMO-Layers > 4 and UL skipping (step 1012), receiving two UL grants for a TTI from a base station (step 1014), generating two MAC PDUs when one of two MAC PDUs will be generated for the TTI (step 1016), and transmitting the two MAC PDUs to the base station (step 1018).

[0777] In various embodiments, a UE configured with maxRank>4 and / or maxMIMO-Layers>4 receives up to two UL grants for TTI.

[0778] In various embodiments, if no data is available for MAC PDU transmission, a UE configured with UL skipping is allowed not to generate a MAC PDU for dynamic UL.

[0779] In various embodiments, the two UL grants are dynamic UL grants for HARQ entities.

[0780] In various embodiments, there is no non-periodic CSI requested for TTI.

[0781] In various embodiments, the method further includes the UE not generating any MAC PDU for TTI when neither of the two MAC PDUs contains available data or when both MAC PDUs contain only MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs.

[0782] Backtracking Reference Figure 3 and Figure 4In one or more embodiments from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) be configured with maxRank > 4 and / or maxMIMO-Layers > 4 and UL skip; (ii) receive two UL grants from the base station for the TTI; (iii) generate two MAC PDUs when one of two MAC PDUs will be generated for the TTI; and (iv) transmit the two MAC PDUs to the base station. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0783] See Figure 7 Regarding such and other concepts, systems, and methods of the present invention, method 1020 for a UE in a wireless communication system includes being configured with maxRank > 4 and / or maxMIMO-Layers > 4 and UL skipping (step 1022), receiving two UL grants for a TTI from a base station (step 1024), generating two MAC PDUs when one of two MAC PDUs will be generated for the TTI under a first condition, and transmitting the two MAC PDUs to the base station (step 1026), and generating a single MAC PDU when one of two MAC PDUs will be generated for the TTI under a second condition, and transmitting the single MAC PDU to the base station (step 1028).

[0784] In various embodiments, a UE configured with maxRank>4 and / or maxMIMO-Layers>4 receives up to two UL grants for TTI.

[0785] In various embodiments, if no data is available for MAC PDU transmission, a UE configured with UL skipping is allowed not to generate a MAC PDU for dynamic UL.

[0786] In various embodiments, the two UL grants are dynamic UL grants for HARQ entities.

[0787] In various embodiments, there is no non-periodic CSI requested for TTI.

[0788] In various embodiments, the method further includes the UE not generating any MAC PDU for TTI when neither of the two MAC PDUs contains available data or when both MAC PDUs contain only MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs.

[0789] In various embodiments, the first condition includes one or more of the following: if / when the two TBs and / or the two codewords are used for the same TRP; if / when the two TBs and / or the two codewords are jointly and / or precoded together; if / when the two TBs and / or the two codewords are precoded with the same precoder; if / when the two TBs and / or the two codewords are associated with the same TCI state and / or the same SRI and / or the same beam and / or the same UE beam and / or the same NW beam; if / when the two TBs and / or the two codewords are used for codebook-based transmission; if / when the two TBs and / or the two codewords are associated with the same TA; if / when neither of the two TBs and / or the two codewords is self-decoding; and / or if / when the two TBs and / or the two codewords are jointly and / or co-coded (e.g., via channel coding).

[0790] In various embodiments, the second condition includes one or more of the following: if / when the two TBs and / or the two codewords are used for different TRPs; if / when the two TBs and / or the two codewords are precoded individually or independently; if / when the two TBs and / or the two codewords are precoded with different precoders; if / when the two TBs and / or the two codewords are associated with different TCI states and / or different SRIs and / or different beams and / or different UE beams and / or different NW beams; if / when the two TBs and / or the two codewords are used for non-codebook-based transmission; if / when the two TBs and / or the two codewords are associated with different TAs; if / when the two TBs and / or the two codewords are both self-decoding; and / or if / when the two TBs and / or the two codewords are encoded individually or independently (e.g., via channel coding).

[0791] Backtracking Reference Figure 3 and Figure 4In one or more embodiments from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) be configured with maxRank > 4 and / or maxMIMO-Layers > 4 and UL skip; (ii) receive two UL grants from the base station for TTI; (iii) generate two MAC PDUs when one of two MAC PDUs will be generated for the TTI under a first condition, and transmit the two MAC PDUs to the base station; and (iv) generate a single MAC PDU when one of two MAC PDUs will be generated for the TTI under a second condition, and transmit the single MAC PDU to the base station. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0792] See Figure 8 Regarding such and other concepts, systems, and methods of the present invention, method 1030 for a UE in a wireless communication system includes being configured with UL spatial multiplexing and UL skipping (step 1032), receiving a first UL grant for a new transmission and a second UL grant for a retransmission for a TTI from a base station (step 1034), generating a first MAC PDU for a new transmission for the TTI when the UE does not have available data for transmission (step 1036), and transmitting the first MAC PDU for the new transmission and the second MAC PDU for the retransmission to the base station (step 1038).

[0793] In various embodiments, a UE configured with UL spatial multiplexing receives up to two UL grants for TTI.

[0794] In various embodiments, if no data is available for transmission, the UE configured to skip UL does not generate a MAC PDU for the dynamic UL grant when it receives one or a single dynamic UL grant.

[0795] In various embodiments, if no data is available for transmission, a UE configured to skip UL does not generate two dynamically UL-granted MAC PDUs, both for new transmissions.

[0796] In various embodiments, the two UL grants are dynamic UL grants for HARQ entities.

[0797] In various embodiments, there is no non-periodic CSI requested for the TTI and / or no UCI to be multiplexed on the PUSCH (e.g., for the TTI and / or for the first MAC PDU and the second MAC PDU).

[0798] In various embodiments, the first MAC PDU contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDU.

[0799] In various embodiments, the method further includes, when neither the third MAC PDU nor the fourth MAC PDU contains available data, or when the third MAC PDU and the fourth MAC PDU contain only MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs, if the UE receives two UL grants for a new transmission of the third MAC PDU and the fourth MAC PDU for the second TTI, then the UE does not generate any MAC PDU for the second TTI.

[0800] Backtracking Reference Figure 3 and Figure 4 In one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) be configured with UL spatial multiplexing and UL skipping; (ii) receive from the base station a first UL grant for a new transmission and a second UL grant for a retransmission for a TTI; (iii) generate a first MAC PDU for a new transmission for the TTI when the UE does not have available data for transmission; and (iv) transmit the first MAC PDU for the new transmission and the second MAC PDU for the retransmission to the base station. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0801] See Figure 9 Regarding such and other concepts, systems, and methods of the present invention, method 1040 for a UE in a wireless communication system includes being configured with maxRank>4 or maxMIMO-Layers>4 and UL skipping (step 1042), receiving a first UL grant from a base station for a new transmission of a first MAC PDU and a retransmission of a second MAC PDU for a HARQ process and / or TTI (step 1044), generating a first MAC PDU for a new transmission for a HARQ process and / or TTI when the UE does not have available data for transmission (step 1046), and transmitting the first MAC PDU for a new transmission and the second MAC PDU for a retransmission to the base station (step 1048).

[0802] In various embodiments, a UE configured with maxRank>4 or maxMIMO-Layers>4 is granted UL permission for HARQ process and / or TTI reception for up to two TB or MAC PDUs.

[0803] In various embodiments, if no data is available for transmission, the UE configured to skip UL does not generate a MAC PDU for the dynamic UL grant when it receives a dynamic UL grant for a single TB / MAC PDU.

[0804] In various embodiments, if no data is available for transmission, a UE configured to skip UL does not generate a dynamically UL-granted MAC PDU for both TB or MAC PDUs used for the new transmission.

[0805] In various embodiments, the first UL grant is a dynamic UL grant for the HARQ entity.

[0806] In various embodiments, there is no non-periodic CSI requested for the TTI and / or no UCI to be multiplexed on the PUSCH (e.g., for the HARQ process and / or for the TTI and / or for the first MACPDU and the second MAC PDU).

[0807] In various embodiments, the first MAC PDU contains only a MAC CE for filling the BSR or a periodic BSR with zero MAC SDU.

[0808] In various embodiments, the method further includes that when neither the third MAC PDU nor the fourth MAC PDU contains available data, or when the third MAC PDU and the fourth MAC PDU contain only MAC CEs for filling BSRs or periodic BSRs with zero MAC SDUs, if the UE receives a second UL grant for a new transmission of the third MAC PDU and the fourth MAC PDU for the second TTI, the UE does not generate any MAC PDU for the second TTI.

[0809] Backtracking Reference Figure 3 and Figure 4In one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) be configured with maxRank > 4 or maxMIMO-Layers > 4 and UL skip; (ii) receive a first UL grant from the base station for a new transmission of a first MAC PDU and a retransmission of a second MAC PDU for a HARQ process and / or TTI; (iii) generate a first MAC PDU for a new transmission for a HARQ process and / or TTI when the UE does not have available data for transmission; and (iv) transmit the first MAC PDU for the new transmission and the second MAC PDU for the retransmission to the base station. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0810] Another concept of this invention is that if a first uplink grant associated with a HARQ process has been received, the UE can determine whether to consider the first and second NDIs of the HARQ process as having been switched, based at least on the previous uplink grant associated with the HARQ process. The previous uplink grant may address the UE's Configuration Scheduling (CS) - Radio Network Temporary Identifier (RNTI) MAC entity. The previous uplink grant may be a configured uplink grant.

[0811] If the previous uplink grants addressing to the CS-RNTI of the MAC entity or is configured to grant uplink access, the UE may consider both the first NDI and the second NDI as having been switched (regardless of the value of the NDI).

[0812] A previous uplink grant or a configured uplink grant can indicate the transmission of a single TB.

[0813] The first uplink permission can indicate or schedule two TBs (including the first TB and the second TB).

[0814] The first NDI can be associated with the first TB associated with the HARQ process.

[0815] The second NDI can be associated with the second TB that is linked to the HARQ process.

[0816] The first TB and the second TB can be contained in a single HARQ buffer.

[0817] Additionally and / or alternatively, the UE may determine whether to consider the second NDI as having been handed over without relying on a previous uplink grant. When a previous uplink grant does not indicate or schedule multiple TBs, the UE does not determine whether the second NDI has been handed over based on the previous uplink grant. The UE may consider the first NDI as having been handed over in response to or due to a previous uplink grant (and not determine whether the second NDI has been handed over or not based on the previous uplink grant). The UE may determine whether the second NDI has been handed over based on a second previous uplink grant (the NDI value). A second previous uplink grant may indicate or schedule multiple TBs. A second previous uplink grant may address to a C-RNTI.

[0818] Alternatively, when or if the preceding uplink grants scheduling or indicates a single TB (transmission), the UE can determine whether to consider both the first NDI and the second NDI as having been switched based on the preceding uplink grant.

[0819] Additionally and / or alternatively, if a first downlink assignment associated with a HARQ process has been received, the UE may determine whether to consider the first and second NDIs of the HARQ process as having been switched, at least based on the previous downlink assignment associated with the HARQ process. The previous downlink assignment may address the MAC entity of the UE's CS-RNTI. The previous downlink assignment may be a configured downlink assignment or a multicast and broadcast service (MBS) multicast. The previous downlink assignment may be based on a semi-persistent scheduling (SPS) configuration.

[0820] If the previous downlink assignment addresses the CS-RNTI of the MAC entity or is configured via downlink assignment or MBS multicast, the UE can consider both the first NDI and the second NDI as having been switched (regardless of the value of the NDI).

[0821] The previous downlink assignment or configured downlink assignment can indicate the transmission / reception of a single TB.

[0822] The first downlink assignment can indicate or schedule two TBs (including the first TB and the second TB).

[0823] The first NDI can be associated with the first TB associated with the HARQ process.

[0824] The second NDI can be associated with the second TB that is linked to the HARQ process.

[0825] The first TB and the second TB can be contained in a single soft buffer.

[0826] Additionally and / or alternatively, the UE may determine whether to consider the second NDI as having been handed over without relying on the previous downlink assignment. When the previous downlink assignment does not indicate or schedule multiple TBs, the UE does not determine whether the second NDI has been handed over based on the previous downlink assignment. The UE may consider the first NDI as having been handed over in response to or due to the previous downlink assignment (and not determine whether the second NDI has been handed over or not based on the previous downlink assignment). The UE may determine whether the second NDI has been handed over based on the second previous downlink assignment (the NDI value). The second previous downlink assignment may indicate or schedule multiple TBs. The second previous downlink assignment may address to the C-RNTI.

[0827] Additionally and / or alternatively, the UE may determine whether to consider the second NDI (other than the first NDI) as having been switched based at least on the TB size of a single TB associated with the previous uplink grant or the previous downlink assignment. Additionally and / or alternatively, the UE may determine whether to consider the second NDI (other than the first NDI) as having been switched based at least on whether a single TB shares the same portion or overlaps (in the HARQ / soft buffer storage) with the second TB associated with the second NDI.

[0828] For example, if or when the second TB will overwrite a single TB in the HARQ / soft buffer during the HARQ process or may overlap with said single TB, the UE may consider the second NDI (e.g., both the first and second NDIs) to have been switched in response to a previous uplink grant or a previous downlink assignment. If or when the second TB will not overlap with a single TB in the HARQ / soft buffer during the HARQ process, the UE may consider the second NDI (e.g., both the first and second NDIs) to have been switched in response to a previous uplink grant or a previous downlink assignment.

[0829] In one instance, the UE can use a first UL grant for a TB transmission. The UE can use the first UL grant with a first HARQ process to transmit a third TB at a first opportune time. The first UL grant can be a UL grant for CS-RNTI reception or a configured UL grant. The UE can store the third TB in a HARQ buffer used for the first HARQ process. Subsequently, the UE can receive a second UL grant indicating the transmission of two TBs. The UE can receive a second UL grant with a first NDI value and a second NDI value. The UE can use the second UL grant with a first HARQ process to transmit the first TB and the second TB at a second opportune time. The UE can consider the first NDI as switched based on the first TB overwriting the third TB in the HARQ buffer of the first HARQ process or possibly overlapping with the third TB. The UE can consider the second NDI as switched based on the second TB overwriting the third TB in the HARQ buffer of the first HARQ process or possibly overlapping with the third TB.

[0830] In one instance, the UE can use a first DL assignment for a TB transmission. The UE can use the first DL assignment with a first HARQ process to receive a third TB at a first opportune time. The first DL assignment can be a DL assignment for CS-RNTI or Group (G)-CS-RNTI reception or a configured downlink assignment for unicast or MBS multicast. The UE can store the third TB in a soft buffer for the first HARQ process. The UE can then receive a second DL assignment indicating the transmission of two TBs. The UE can receive a second DL assignment with a first NDI value and a second NDI value. The UE can use the second DL assignment with the first HARQ process to transmit the first TB and the second TB at a second opportune time. The UE can consider the first NDI as switched based on the first TB overwriting the third TB in the soft buffer of the first HARQ process or potentially overlapping with the third TB. The UE can consider the second NDI as switched based on the second TB overwriting the third TB in the soft buffer of the first HARQ process or potentially overlapping with the third TB.

[0831] Various examples and embodiments of the invention are described below. The following aspects and embodiments are possible in relation to the methods, alternatives, concepts, examples, and embodiments detailed above and herein.

[0832] The UE can be configured with uplink spatial multiplexing (or 8Tx) and / or downlink spatial multiplexing. Throughout this disclosure, uplink spatial multiplexing and / or 8Tx can be, can be replaced with, can be represented as, and can be referred to as "dual codewords", "maxRank>4", or "maxMIMO-Layers>4". When the UE is configured with uplink spatial multiplexing (or 8Tx UL), the UE can be configured with maxRank>4 and / or maxMIMO-Layers>4.

[0833] The UE can be configured with semi-persistent scheduling and / or configured with UL permission.

[0834] The first TB (associated with the second UL grant) may share the same storage space in the HARQ buffer with the third TB (e.g., stored partially or completely overlapping). Alternatively and / or, the second TB associated with the second UL grant may not share the same storage space in the HARQ buffer with the third TB (stored separately).

[0835] Additionally and / or alternatively, the first TB may be indicated by the DCI format 0_1 ​​(indicated in the second) UL approval, which specifies the modulation and coding scheme, new data indicator, and / or redundant version associated with transport block 1, and / or the transport block 2 associated therewith. The modulation and coding scheme, new data indicator, and / or redundant version associated with transport block 1 may be the first HARQ information.

[0836] Additionally and / or alternatively, the second TB may be indicated by the DCI format 0_1 ​​associated with (second) UL approval (indicating the modulation and coding scheme, new data indicator, and / or redundant version associated with transport block 2) and / or the transport block 2 (or transport block 1) associated therewith. The modulation and coding scheme, new data indicator, and / or redundant version associated with transport block 2 may be second HARQ information.

[0837] The following shows an example text proposal of [1] 3GPP TS 36.321V15.11.0, and the present invention may be implemented using one or more text proposals (underlined to indicate additions / modifications):

[0838] ---------------------------Start of Example 1--------------------

[0839] 5.3.1 DL Assignment Reception

[0840] The downlink assignment indication received on the PDCCH is transmitted on the DL-SCH for the specific MAC entity and provides the relevant HARQ information.

[0841] …

[0842] When a MAC entity has a C-RNTI, temporary C-RNTI, CS-RNTI, G-RNTI, or G-CS-RNTI, the MAC entity shall listen to each PDCCH during this period and for each serving cell:

[0843] 1> If the downlink assignment for this PDCCH timing and this serving cell has already been received on the PDCCH of a C-RNTI or temporary C-RNTI used for MAC entities or a G-RNTI configured for multicast MTCH:

[0844] 2> If this is the first downlink assignment used for this temporary C-RNTI:

[0845] 3> Treat NDI as already switched.

[0846] 2> If the downlink assignment is for a C-RNTI of a MAC entity, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a CS-RNTI or G-CS-RNTI received for a MAC entity, or a configured downlink assignment for unicast or MBS multicast; or

[0847] 2> If the downlink assignment is for a MAC entity and is configured for multicast MTCH, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a downlink assignment received for a MAC entity via a CS-RNTI, G-CS-RNTI, or other G-RNTI or C-RNTI, or a configured downlink assignment for unicast or MBS multicast:

[0848] 3> Regardless of the value of NDI, (Multiple) NDI is considered to have been switched.

[0849] ---------------------------End of Example 1--------------------

[0850] ---------------------------Start of Example 2--------------------

[0851] 5.3.1DL Assignment Reception

[0852] The downlink assignment indication received on the PDCCH is transmitted on the DL-SCH for the specific MAC entity and provides the relevant HARQ information.

[0853] …

[0854] When a MAC entity has a C-RNTI, temporary C-RNTI, CS-RNTI, G-RNTI, or G-CS-RNTI, the MAC entity shall listen to each PDCCH during this period and for each serving cell:

[0855] 1> If the downlink assignment for this PDCCH timing and this serving cell has already been received on the PDCCH of a C-RNTI or temporary C-RNTI used for MAC entities or a G-RNTI configured for multicast MTCH:

[0856] 2> If this is the first downlink assignment used for this temporary C-RNTI:

[0857] 3> Treat NDI as already switched.

[0858] 2> If the downlink assignment is for a C-RNTI of a MAC entity, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a CS-RNTI or G-CS-RNTI received for a MAC entity, or a configured downlink assignment for unicast or MBS multicast; or

[0859] 2> If the downlink assignment is for a MAC entity and is configured for multicast MTCH, and if the previous downlink assignment indicated to a HARQ entity in the same HARQ process was a downlink assignment received for a MAC entity via a CS-RNTI, G-CS-RNTI, or other G-RNTI or C-RNTI, or a configured downlink assignment for unicast or MBS multicast:

[0860] 3> Regardless of the value of NDI, (corresponding to the previous downlink assignment) TB NDI is considered to have been switched.

[0861] ---------------------------End of Example 2--------------------

[0862] ---------------------------Start of Example 3--------------------

[0863] 5.4.1 UL Acceptance

[0864] 1> If the uplink for this serving cell is already permitted to be received on the PDCCH of the C-RNTI or temporary C-RNTI used for the MAC entity; or

[0865] 1> If uplink permission has already been received in the random access response:

[0866] 2> If the uplink grant is a C-RNTI for a MAC entity and if the previous uplink grant for delivery to the HARQ entity in the same HARQ process was a CS-RNTI received uplink grant or a configured uplink grant for a MAC entity, then:

[0867] 3> Regardless of the value of NDI, (Multiple) NDI is considered to have been switched to be used for the corresponding HARQ process.

[0868] ---------------------------End of Example 3--------------------

[0869] ---------------------------Start of Example 4--------------------

[0870] 5.4.1 UL Acceptance

[0871] 1> If the uplink for this serving cell is already permitted to be received on the PDCCH of the C-RNTI or temporary C-RNTI used for the MAC entity; or

[0872] 1> If uplink permission has already been received in the random access response:

[0873] 2> If the uplink grant is a C-RNTI for a MAC entity and if the previous uplink grant for delivery to the HARQ entity in the same HARQ process was a CS-RNTI received uplink grant or a configured uplink grant for a MAC entity, then:

[0874] 3> Regardless of the value of NDI, (corresponding to the TB granted by the previous uplink) NDI is considered to have been switched to be used for the corresponding HARQ process.

[0875] ---------------------------End of Example 4--------------------

[0876] All concepts, instances, aspects, alternatives, and embodiments described above (e.g., for the first concept) may be combined, in whole or in part, to form one or more new concepts, instances, aspects, alternatives, and embodiments.

[0877] See Figure 10Regarding such and other concepts, systems, and methods of the present invention, method 1050 for a UE in a wireless communication system includes receiving from a network node a first parameter having a value greater than four indicating a MIMO layer and a second parameter indicating UL skipping (step 1052); receiving a first UL grant and a second UL grant on a first PDCCH, wherein the first UL grant is used for retransmission of a first MAC PDU and the second UL grant is used for a first new transmission (step 1054); generating a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH if the first MAC PDU will be retransmitted, wherein there is no data available for transmission or for any LCG (step 1056); and performing a retransmission of the first MAC PDU using the first UL grant and performing a first new transmission of the second MAC PDU using the second UL grant (step 1058).

[0878] In various embodiments, the second MAC PDU includes a zero MAC SDU.

[0879] In various embodiments, the first MAC PDU is generated before the first PDCCH is received.

[0880] In various embodiments, the first PDCCH indicates a first NDI for a first UL-approved NDI, a second NDI for a second UL-approved NDI, and / or a UL transmission for two TBs.

[0881] In various embodiments, the first NDI is not switched, and the second NDI is switched.

[0882] In various embodiments, there is no aperiodic CSI requested for the first new transmission and retransmission of PUSCH, and / or no UCI for multiplexing the first new transmission and retransmission of PUSCH.

[0883] In various embodiments, the first parameter indicating the MIMO layer is maxRank or maxMIMO-Layers, and the second parameter indicating UL skipping is skipUplinkTxDynamic or enhancedSkipUplinkTxDynamic.

[0884] In various embodiments, the method further includes receiving a third UL grant on a second new transmission of the first MAC PDU on a second PDCCH prior to receiving the first PDCCH.

[0885] In various embodiments, the second PDCCH indicates a third NDI for a third UL-approved third NDI, wherein the third NDI is switched.

[0886] In various embodiments, the method further includes: receiving a fourth UL grant for a third new transmission and a fifth UL grant for a fourth new transmission on a third PDCCH, and not generating one or more MAC PDUs for the fourth UL grant and the fifth UL grant if no data is available for transmission or for any LCG.

[0887] Backtracking Reference Figure 3 and Figure 4 In one or more embodiments from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) receive from a network node a first parameter indicating a MIMO layer and a second parameter indicating UL skipping, having a value greater than four; (ii) receive a first UL grant and a second UL grant on a first PDCCH, wherein the first UL grant is used for retransmission of a first MAC PDU and the second UL grant is used for a first new transmission; (iii) if the first MAC PDU for the first PDCCH is to be retransmitted, generate a second MAC PDU corresponding to the second UL grant indicated by the first PDCCH, wherein there is no data available for transmission or for any LCG; and (iv) perform a retransmission of the first MAC PDU using the first UL grant and perform a first new transmission of the second MAC PDU using the second UL grant. Furthermore, CPU 308 can execute program code 312 to perform all the actions, steps, and methods described above, below, or otherwise herein.

[0888] Any combination of the concepts or teachings above or herein may be combined, either wholly or in part, together or to form new embodiments. The disclosed details and embodiments may be used to solve at least (but not limited to) the problems mentioned above and herein.

[0889] It should be noted that any of the methods, alternatives, steps, examples, and embodiments presented herein may be used independently, individually, and / or in combination with multiple methods, alternatives, steps, examples, and embodiments.

[0890] Various aspects of this disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any particular structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will understand that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in different ways. For example, any number of aspects set forth herein can be used to implement an apparatus or practice. Furthermore, this apparatus or practice can be implemented or practiced by using other structures, functions, or structures and functions other than or different from one or more aspects set forth herein. As examples of some of the foregoing concepts, in some aspects, a parallel channel can be established based on a pulse repetition frequency. In some aspects, a parallel channel can be established based on a pulse position or offset. In some aspects, a parallel channel can be established based on a time-hopping sequence. In some aspects, a parallel channel can be established based on a pulse repetition frequency, a pulse position or offset, and a time-hopping sequence.

[0891] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0892] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of both, designed using source coding or some other technique) and have instructions in various forms of program or design code (which, for convenience, may be referred to herein as "software" or "software module"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as a departure from the scope of this disclosure.

[0893] Furthermore, the various illustrative logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or executed by an integrated circuit (“IC”), access terminal, or access point. An IC 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 device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

[0894] It should be understood that any particular order or hierarchy of steps in any disclosed process is an instance of a sample method. It should be understood that the specific order or hierarchy of steps in a process can be rearranged based on design preferences, while remaining within the scope of this disclosure. The appended method claims present the elements of the various steps in a sample order and are not intended to be limited to any particular order or hierarchy presented.

[0895] The steps of the methods or algorithms described in conjunction with the aspects disclosed herein can be implemented directly in hardware, with software modules executed by a processor, or a combination of both. Software modules (e.g., containing executable instructions and associated data) and other data can reside in data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. The sample storage medium can be coupled to a machine such as a computer / processor (for convenience, this machine may be referred to herein as a "processor"), such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The sample storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user equipment. Alternatively, the processor and storage medium can reside as discrete components in a user equipment. Furthermore, in some aspects, any suitable computer program product may include a computer-readable medium comprising code associated with one or more aspects of this disclosure. In some aspects, the computer program product may include packaging material.

[0896] While the invention has been described in conjunction with various aspects and examples, it should be understood that further modifications can be made to the invention. This application is intended to cover any changes, uses, or adaptations to the invention that generally follow the principles of the invention and include such deviations from this disclosure that fall within the scope of known and customary practice in the art to which this invention pertains.

Claims

1. A method for a user equipment, characterized in that, include: Receive a first parameter indicating a multiple-input multiple-output layer with a value greater than four from the network node, and a second parameter indicating uplink skipping; A first uplink grant and a second uplink grant are received on a first physical downlink control channel, wherein the first uplink grant is used for retransmission of a first media access control protocol data unit and the second uplink grant is used for a first new transmission; If the first Media Access Control Protocol (MAC) data unit for the first physical downlink control channel is retransmitted, then the second uplink indicated by the first physical downlink control channel grants permission to generate a second MAC data unit, in which there is no data available for transmission or for any logical channel group. as well as The first uplink is used to allow the retransmission of the first Media Access Control Protocol (MAC) data unit, and the second uplink is used to allow the first new transmission of the second MAC data unit.

2. The method according to claim 1, characterized in that, The second media access control protocol data unit includes a zero media access control service data unit.

3. The method according to claim 1, characterized in that, The first Media Access Control Protocol (MAC) data unit is generated before receiving the first physical downlink control channel.

4. The method according to claim 1, characterized in that, The first physical downlink control channel indicates a first new data indicator for the first uplink grant, a second new data indicator for the second uplink grant, and / or uplink transmission for two transport blocks.

5. The method according to claim 4, characterized in that, The first new data indicator was not switched and the second new data indicator was switched.

6. The method according to claim 1, characterized in that: There is no aperiodic channel state information requested for the physical uplink shared channel transmission of the first new transmission and the retransmission, and / or There is no uplink control information that needs to be multiplexed for the physical uplink shared channel transmission of the first new transmission and the retransmission.

7. The method according to claim 1, characterized in that, The first parameter indicating the multiple input multiple output layer is maxRank or maxMIMO-Layers, and the second parameter indicating uplink skipping is skipUplinkTxDynamic.

8. The method according to claim 1, characterized in that, It also includes receiving a third uplink grant on a second physical downlink control channel for a second new transmission of the first media access control protocol data unit before receiving the first physical downlink control channel.

9. The method according to claim 8, characterized in that, The second physical downlink control channel indicates a third new data indicator for the third uplink grant, wherein the third new data indicator is switched.

10. The method according to claim 1, characterized in that, Also includes: Receive a fourth uplink grant for the third new transmission and a fifth uplink grant for the fourth new transmission on the third physical downlink control channel; as well as If no data is available for transmission or for any logical channel group, then no one or more Media Access Control (MAC) data units are generated for the fourth uplink grant and the fifth uplink grant.

11. A user equipment, characterized in that, include: Memory; as well as A processor, operably coupled to the memory, wherein the processor is configured to execute program code to: Receive a first parameter indicating a multiple-input multiple-output layer with a value greater than four from the network node, and a second parameter indicating uplink skipping; A first uplink grant and a second uplink grant are received on a first physical downlink control channel, wherein the first uplink grant is used for retransmission of a first media access control protocol data unit and the second uplink grant is used for a first new transmission; If the first Media Access Control Protocol (MAC) data unit for the first physical downlink control channel is retransmitted, then the second uplink indicated by the first physical downlink control channel grants permission to generate a second MAC data unit, in which there is no data available for transmission or for any logical channel group. as well as The first uplink is used to allow the retransmission of the first Media Access Control Protocol (MAC) data unit, and the second uplink is used to allow the first new transmission of the second MAC data unit.

12. The user equipment according to claim 11, characterized in that, The second media access control protocol data unit includes a zero media access control service data unit.

13. The user equipment according to claim 11, characterized in that, The first Media Access Control Protocol (MAC) data unit is generated before receiving the first physical downlink control channel.

14. The user equipment according to claim 11, characterized in that, The first physical downlink control channel indicates a first new data indicator for the first uplink grant, a second new data indicator for the second uplink grant, and / or uplink transmission for two transport blocks.

15. The user equipment according to claim 14, characterized in that, The first new data indicator was not switched and the second new data indicator was switched.

16. The user equipment according to claim 11, characterized in that: There is no aperiodic channel state information requested for the physical uplink shared channel transmission of the first new transmission and the retransmission, and / or There is no uplink control information that needs to be multiplexed for the physical uplink shared channel transmission of the first new transmission and the retransmission.

17. The user equipment according to claim 11, characterized in that, The first parameter indicating the multiple input multiple output layer is maxRank or maxMIMO-Layers, and the second parameter indicating uplink skipping is skipUplinkTxDynamic.

18. The user equipment according to claim 11, characterized in that, The processor is also configured to execute the program code to: receive a third uplink grant on a second new transmission of the first Media Access Control Protocol data unit on a second physical downlink control channel before receiving the first physical downlink control channel.

19. The user equipment according to claim 18, characterized in that, The second physical downlink control channel indicates a third new data indicator for the third uplink grant, wherein the third new data indicator is switched.

20. The user equipment according to claim 11, characterized in that, The processor is also configured to execute the program code to: Receive a fourth uplink grant for the third new transmission and a fifth uplink grant for the fourth new transmission on the third physical downlink control channel; as well as If no data is available for transmission or for any logical channel group, then no one or more Media Access Control (MAC) data units are generated for the fourth uplink grant and the fifth uplink grant.

Images