Prioritization within the UE during uplink transmission

Abstract

To provide an apparatus for Intra-UE Prioritization in uplink (UL) transmissions.SOLUTION: An apparatus is configured to: receive first information indicating a first uplink grant associated with a first transmission and second information indicating a second uplink grant associated with a second transmission; determine, based on the first information and the second information, that the first transmission and the second transmission overlap at least partially in time; determine a first priority associated with the first transmission and a second priority associated with the second transmission; and cause, based at least in part on the first priority and the second priority, at least one of prioritization of one transmission over another transmission and preemption of the first transmission by the second transmission.SELECTED DRAWING: None

Description

[Technical Field]

[0001] (Cross-reference of related applications) This application is U.S. Provisional Patent Application No. 62 / 805,614, filed on 14 February 2019. , and the use of U.S. Provisional Patent Application No. 62 / 824,701 filed on March 27, 2019 We claim the benefits, and all of them are incorporated herein by reference. [Background technology]

[0002] To support various applications, it supports transmission at various priority levels. It may be desirable to do so. The priority is Medium Access Control. While it may be possible to identify the priority at the MAC layer, sometimes the physical layer itself can enable priority identification. This can be beneficial. This can happen when physical transmission begins, but pre- It must be emptied. Therefore, the priority must be identified at the physical layer, and the user terminal A collision within the (User Equipment:UE) physical downlink shared channel (Physical Downl Defines UE behavior and handles collisions when they occur on an ink-shared channel (PDSCH). To that end, a UE procedure is defined, enabling the UE to determine priorities in the MAC layer. It is necessary. [Overview of the Initiative]

[0003] This overview presents a simplified version of the concept, which is further detailed below. This is provided to introduce the selection. This summary outlines the main mechanisms or essential aspects of the requested subject. It is not intended to identify the mechanism, but rather to limit the scope of the requested subject matter. It is not intended to be done. Furthermore, the requested subject matter is not described in any part of this disclosure. The constraints are not limited to resolving any or all of the drawbacks.

[0004] Methods and apparatus for prioritizing within a UE during transmission are described herein. Identify transmission priority at the Uplink (UL) and handle PDSCH collisions within the UE. Supports multiple Hybrid ARQ (HARQ) ACK codebooks. And, regarding multiple priorities, Physical Uplink Shar ed Channel:PUSCH), enable UCI with repeated PUSCH, and configure the graphics HARQ ID conflicts regarding configured grants (CG) and dynamic grants. This document describes how to enable the MAC layer to handle spurious events and conflicts within the UE.

[0005] In one example, the device indicates a first uplink grant associated with a first transmission. Information 1, and a second uplink grant corresponding to the second transmission Information can be received. The device performs a first transmission and based on the first information and the second information. The device may determine that the second transmission overlaps with the first transmission in at least partially in time. Determine the first priority associated with the transmission and the second priority associated with the second transmission. The device then obtains, at least partially based on the first priority and the second priority. Prioritizing one transmission over the other, or the first transmission by the second transmission This could result in at least one of the preemptions. [Brief explanation of the drawing]

[0006] The above overview and the following detailed explanation will be better understood when read in conjunction with the attached diagrams. Various aspects of this disclosure are shown to illustrate it. However, this disclosure is not limited to, It is not limited to the specific aspects discussed. [Figure 1] Figure 1 is a diagram of the enabled DCI that changes the priority of a Type 2 configured grant. [Figure 2] Figure 2 shows PUSCH and Physical Uplink Control Channel (PUCCH) with the Cell Radio-Network Temporary Identifier (C-RNTI) masked by the priority level RNTI. [Figure 3A] Figure 3A illustrates the preemption of a low-priority PDSCH within the UE by a high-priority PDSCH in a resource element (RE) collision between PDSCHs. [Figure 3B] Figure 3B illustrates the preemption of a low-priority PDSCH within the UE by a high-priority PDSCH without RE collisions between PDSCHs. [Figure 4A] Figure 4A shows preemption by PDSCHURLLC and preemption within the UE only; the New Radio (NR) Node B (gNB) does not need to transmit a preemption indication. [Figure 4B] Figure 4B is a diagram of preemption by PDSCHURLLC, between UEs and within UEs, where gNB transmits a preemption indicator. [Figure 5] Figure 5 shows a diagram of a UE procedure for flowing a soft buffer for low-priority HARQ processes in the event of preemption. [Figure 6] Figure 6 shows that UE2 preempts the PDSCHs of the lower-priority UE0 and UE1, but does not preempt the PDSCH of the higher-priority UE3. [Figure 7] Figure 7 shows a diagram of a UE procedure for flowing a soft buffer with priority indicated through an RNTIp mask. [Figure 8A] Figure 8A shows HARQ-ACK UCI transmission with PUCCH M=1 and a single UCI feedback opportunity in a slot. [Figure 8B] Figure 8B shows HARQ-ACK UCI transmission with PUCCH M=2 and multiple UCI feedback opportunities in the slot. [Figure 9A] Figure 9A shows a sub-slot configuration M=1, with one sub-slot / slot. [Figure 9B] Figure 9B shows a sub-slot configuration M=2, with two sub-slots / slot. [Figure 10] Figure 10 shows how K1 is incremented at the finest granularity of subslots (two per slot) for the lowest priority (enhanced Mobile Broadband (eMBB)). [Figure 11] Figure 11 shows that K1 represents the slot for PUCCH and K1a represents the sub-slot. [Figure 12] Figure 12 shows separate HARQ ACK codebooks for p=0 (eMBB) and p=1 (Ultra-Reliable and Low Latency Communications (URLLC)). [Figure 13] Figure 13 shows a PUCCH transmission to multiple transmission and reception points (TRPs). [Figure 14] Figure 14 shows a diagram of PUCCH transmission to multiple TRPs. A PUCCH Resource Indicator (PRI) of 0 is configured for PUCCH transmission to TRP0 on B0, and PRI=1 is configured for PUCCH transmission to TRP1 on B0. [Figure 15]Figure 15 is a diagram of the PUCCH spatial orientation based on TRP recognition (derived from CORESET in this example). [Figure 16] Figure 16 shows multiple HARQ ACK codebooks piggybacked onto a single PUSCH in a slot. [Figure 17] Figure 17 shows the UCIm mapping over different hops in PUSCH. [Figure 18] Figure 18 shows how UCI0 is divided and mapped on the PUSCH hop. [Figure 19] Figure 19 shows the UE procedure for mapping UCI0. When M=1, UCI0 is mapped to each hop. When M>1, UCI0 is mapped to hop #0, UCI1 is mapped to hop #1, and so on. [Figure 20A] Figure 20A shows the mapping of HARQ-ACK and CSI for UCIm on PUSCH, which is multiplexed using PUSCH resources. [Figure 20B] Figure 20B shows the mapping of HARQ-ACK and CSI for UCIm on PUSCH only in UCI on PUSCH. [Figure 21A] Figure 21A shows a HARQ-ACK UCI mapping resource where there is no Demodulation Reference Signal (DMRS) near UCI1. [Figure 21B] Figure 21B shows the HARQ-ACK UCI mapping resources for the additional DMRS being introduced near UCI1. [Figure 22A] Figure 22A shows the UCIURLLC and UCIeMBB, with UCIeMBB being piggybacked to PUSCH, which precedes UCIURLLC. [Figure 22B] Figure 22B shows the UCIURLLC and UCIeMBB, with UCIURLLC being piggybacked to PUSCH, which precedes UCIeMBB. [Figure 22C]Figure 22C shows UCIURLLC and UCIeMBB being piggybacked into PUSCH, where UCIeMBB and UCIURLLC are mapped to the same sub-slot of PUSCH. [Figure 22D] Figure 22D is a diagram of UCIURLLC and UCIeM BB where the UCIURLLC resource is mapped first and the UCIeMBB is piggybacked to PUSCH. [Figure 23A] Figure 23A shows the iteration of the HARQ process with repeated pushes in a mini-slot, and the UCI partition between iterations. [Figure 23B] Figure 23B shows the iteration of the HARQ process for multiple segment transmissions between slot boundaries, and the UCI partitioning between iterations. [Figure 23C] Figure 23C shows the iteration of a mini-slot HARQ process with frequency hopping, and the UCI partitioning between iterations. [Figure 23D] Figure 23D shows the iteration of the HARQ process for multiple segment transmissions with hopping, and the UCI partitioning between iterations. [Figure 24A] Figure 24A shows how each segment is mapped proportionally to the PUSCH resource, and how the modulated UCI symbols between repetitions of the co-generated UCI symbols are divided between repetitions. [Figure 24B] Figure 24B shows how the modulated UCI symbols between repetitions of the jointly generated UCI symbols are mapped almost equally between PUSCH segments. [Figure 24C] Figure 24C is a diagram showing the division of modulated UCI symbols between repetitions of separately generated UCI modulated symbols for each repetition. [Figure 25A] Figure 25A shows UCI transmission via PUSCH repetition, which maps UCI to PUSCH with minimal delay. [Figure 25B] Figure 25B shows UCI transmission via a pusher repeater, where UCI is mapped to pushers aligned at the edge. [Figure 25C] Figure 25C illustrates UCI transmission via a repeating PUSCH, where PUCCH(D) maps UCI to a PUSCH that overlaps with a first PUSCH that maps UCI to a PUSCH depending on the UE capability. [Figure 25D] Figure 25D is another diagram of UCI transmission via PUSCH repetition. [Figure 26] Figure 26 shows the transmission of repeated pushes to different TRPs. [Figure 27A] Figure 27A shows the UCI mapping to target push iterations for different TRPs in separate HARQ-ACK codebooks for each TRP. [Figure 27B] Figure 27B is a diagram of the UCI mapping to target push iterations for different TRPs in UCI, with a common codebook repeated for each TRP. [Figure 28A] Figure 28A shows a PUSCH iteration with a Scheduling Request Indicator (SRI) cycle. [Figure 28B] Figure 28B shows a PUSCH iteration where SRI is fixed to a time resource. [Figure 28C] Figure 28C is a diagram of a PUSCH iteration with SRI as a feature of the iterative instance. [Figure 29A] Figure 29A shows the PUSCH iterations in multiple TRP scenarios, each with four sets of iterations for the PUSCH HARQ ID. [Figure 29B] Figure 29B shows the PUSCH iteration in multiple TRP scenarios with Early Termination Indication (ETI) indicators for terminating transmissions 3 and 4. [Figure 29C] Figure 29C shows the PUSCH iteration in multiple TRP scenarios, where the UCI is only on PUSCH at the end of the PUSCH iteration. [Figure 29D]Figure 29D shows the PUSCH iteration in multiple TRP scenarios with delayed termination of the iterations. [Figure 29E] Figure 29E shows PUSCH iterations in multiple TRP scenarios with override grants indicating early termination. [Figure 29F] Figure 29F shows the PUSCH iteration in multiple TRP scenarios with the transmission of NAC-enhanced Code Block Groups (CBGs) in subsequent iterations. [Figure 29G] Figure 29G shows the PUSCH iteration in multiple TRP scenarios with early termination timer-based termination of the PUSCH iteration. [Figure 29H] Figure 29H shows the PUSCH iteration in multiple TRP scenarios with selective termination of the iteration. [Figure 30] Figure 30 illustrates the retransmission to TRPs within a TRP group when one TRP from the group responds negatively to the transmission. [Figure 31A] Figure 31A shows how the UE flows its HARQ buffer when it receives ACKs from all TRP groups. [Figure 31B] Figure 31B shows that the UE identifies ACKs from all TRP groups upon receiving at least one ACK, and the HARQ buffer flows after the timer expires. [Figure 32A] Figure 32A illustrates a collision within the UE between a low-priority PUSCH grant and a high-priority PUSCH grant, where the eMBB PUSCH resource is punctured at the location of the URLLC resource. [Figure 32B] Figure 32B illustrates a collision within the UE between a low-priority push grant and a high-priority push grant, where eMBB transmission is completely canceled. [Figure 32C] Figure 32C illustrates a collision within the UE between a low-priority PUSCH grant and a high-priority PUSCH grant, where the eMBB PUSCH resource is punctured on a symbol where the collision occurs with a URLLC PUSCH. [Figure 33] Figure 33 shows that PUSCHURLLC and PUSCHeMBB have the same HARQ-ID D (note that there is no conflict in the PUSCH resources). [Figure 34] Figure 34 illustrates collisions within the UE of CG PUSCH. Lower-priority CG PUSCHs are canceled or punctured by higher-priority CG PUSCHs. [Figure 35A] Figure 35A illustrates the retransmission of a preempted low-priority CG pusher within the UE when receiving a dynamic grant from a gNB. [Figure 35B] Figure 35B is a diagram illustrating the retransmission of a preempted low-priority CG PUSCH retransmission within a UE as a CG PUSCH. [Figure 36A] Figure 36A shows downlink (DL) and UL collisions, low-priority PDSCH and high-priority PUSCH collisions within the UE. [Figure 36B] Figure 36B shows DL and UL collisions, low-priority PDSCH and high-priority PUCCH collisions within the UE. [Figure 36C] Figure 36C shows DL and UL collisions, low-priority PUSCH and high-priority PDSCH collisions within the UE. [Figure 37A] Figure 37A shows an exemplary communication system in which the methods and apparatus described and claimed herein may be embodied. [Figure 37B] Figure 37B is a block diagram of an exemplary apparatus or device configured for wireless communication. [Figure 37C] Figure 37C is a system diagram of an exemplary Radio Access Network (RAN) and core network. [Figure 37D] Figure 37D is a system diagram of another exemplary RAN and core network. [Figure 37E] Figure 37E is a system diagram of another exemplary RAN and core network. [Figure 37F]Figure 37F is a block diagram of an exemplary computing system. [Figure 37G] Figure 37G is a block diagram of another exemplary communication system. [Modes for carrying out the invention]

[0007] Methods and apparatus for prioritizing within a UE during transmission are described herein. In the embodiments described in detail, the user terminal (UE), wireless communication device, and wireless transmission The term Wireless Transmit / Receive Unit (WTRU) is particularly used. Unless otherwise specified, they may be used interchangeably without restriction.

[0008] The following abbreviations and definitions may be used herein. BWP: Bandwidth Part cDAI:counter-DownLink Assignment Index (x) CA: Carrier Aggregation CBG: Code Block Group CG: Configured Grant CNGTI: Code Block Group Transmission Index (x) C-RNTI: Cell Radio-Network Temporary Identifier child) CS-RNTI:Configured Schedule Radio-Network Temporary Identifier (Scheduled wireless network temporary identifier) CSI-RS: Channel State Information Reference Signal ) DAI: Downlink Assignment Index DC: Dual Connectivity DL:Downlink DL-SCH: Downlink Shared Channel DMRS: Demodulation Reference Signal eMBB: Enhanced Mobile Broadband eNB: Evolved Node B FDD: Frequency Division Duplex FR1: Frequency region 1 (sub 6GHz) FR2: Frequency region 2 (mmWave) gNB:NR NodeB (NR Node B) HARQ: Hybrid ARQ IE: Information Element IIoT: Industrial Internet of Things KPI: Key Performance Indicators L1:Layer 1 L2:Layer 2 L3:Layer 3 LAA: License Assisted Access LTE: Long Term Evolution MAC: Medium Access Control MCS: Modulation Coding Scheme MCS-C-RNTI:Modulation Coding Scheme Cell Radio Network Temporary Identif IER (Modulation Coding Scheme Cell Radio Network Temporary Identifier) MIB: Master Information Block MTC: Machine-Type Communications mMTC: Massive Machine Type Communication NR:New Radio NR-U: NR Unlicensed OS: OFDM Symbol OFDM: Orthogonal Frequency Division Multiplexing PCell: Primary Cell PHY:Physical Layer PRACH: Physical Random Access Channel PRI: PUCCH Resource Indicator RACH: Random Access Channel RAN: Radio Access Network RAP: Random Access Preamble RAR: Random Access Response RAT: Radio Access Technology RRC: Radio Resource Control RS:Reference signal SCell: Secondary Cell SI: System Information SR: Scheduling Request tDAI:total-DownLink Assignment Index (Kus) TB: Transport Block TCI: Transmission Configuration Indicator TDD: Time Division Duplex TRP: Transmission and Reception Point TTI: Transmission Time Interval UE: User Equipment UL: Uplink UL-SCH: Uplink Shared Channel URLLC: Ultra-Reliable and Low Latency Communications

[0009] In industrial Internet of Things (IIoT) applications, multiple data The stream can be generated by a sensor or actuator. The data can be transmitted to the gNB through a common UE. The data stream has low latency and reliability. They differ in terms of payload size, quality of service (QoS), and other factors. Requirements may exist. The network will have gNB and UE data storage according to those requirements. It must be possible to prioritize Ream. A simple example is when UE is eMBB and This is the case when both URLLC operation are supported. For example, a drone has eMBB capability. It may be necessary to support video transmission, but URLLC capability is real time. It may require being rigged rather than eMBB transmission, PDSCH, PUSCH, and Physical Downlink Control Channel (PDCCH), Prioritizing URLLC transmission, such as PUCCH, may be necessary.

[0010] Several scenarios where prioritization must occur due to resource contention between priorities O refers to the following: high-priority PDSCs that take precedence over low-priority PUSCH grants. Prioritizing H grants within UE, there are resource conflicts between CG and dynamic grants. Prioritizing PUSCH requests within the UE, prioritizing dynamic low-priority PUSCH grants. When there is a resource contention between dynamic high-priority PUSCH grants within the PUSCH UE Prioritization, UL control information when there is resource contention between control information transmissions of different priorities Prioritization of reports within the UE, as well as control channels and data channels with different priorities. This includes, but is not limited to, prioritizing within the UE when there are resource contentions between resources. In addition, when UE is composed of multiple CGs, the following scenarios occur, namely different Prioritization within the UE (Unified Reality) is possible for multiple CG pushes with different priorities.

[0011] 3rd Generation Partnership Project: 3GPP) NR Release 15 introduces a group-wide PDCCH-based preemption An indicator (DCI in format 2_1 in INT-RNTI) has been introduced. This indicates that a specific resource in the eMBB UE group will be preempted during DL. The UE then used DCI for the serving cell from the configured set of serving cells. -When mat2_1 is detected, the UE will transmit to the UE the set of PRB and the last From the set of symbols for the monitoring period, PRB is shown in DCI format 2_1. It can be assumed that the symbol does not exist. The set of PRBs is the active DLB. It may be equivalent to WP. Preempted resources have a coarse granularity (slots or The preemption state for that group can be represented by a 14-bit code. The affected resources are at most half of the BWP or the entire BWP. Preemption markings at frequency are particularly important because they can be indicated even when the bandwidth is not reached. It may be rough. Preemption markings are in the eMBB UE, and its PDSCH resource It could be proposed to allow the buffer to flow if it is affected by preemption. The UE is affected by the soft bits in its HARQ buffer, or the affected P Soft bits / symbols from several other buffers that process DSCH may be streamed. For example, the HARQ buffer may already contain soft bits from the previous eMBB reception, pre The emptied transmission is an eMBB retransmission. The soft coupling of the retransmission with the previous transmission. Previously, typically, the UE first receives the signal into the receive buffer, and then the result is HAR Q Before coupling to the soft bit buffer, various operations are performed on the received signal (e.g., F Perform FT, channel estimation, and demodulation. In this case, the HARQ soft bit buffer is flowing. It does not need to be done. However, another intermediate buffer(s) including the affected retransmission Flushing can occur. Therefore, the locations where flushing occurs are collectively referred to as buffers.

[0012] In 3GPP NR Release 16, preemption markings are considered for UL. Furthermore, in eMBB UE, some of its resources are preempted by URLLC transmission. A possible indication is provided. Therefore, eMBB UE transmits on those resources. You mustn't do that.

[0013] 3GPP NR Release 15 is per PUCCH resource set and per resource set. It defines multiple PUCCH resource configurations. The UE is based on its UCI payload. Determine the PUCCH resource set and schedule grants from DCI to PUCCH. The CH Resource Indicator (PRI) can be determined. Spatial direction for PUCCH transmission. This can be configured per PUCCH resource, and is a list of RRC configuration RSs indicating beam correspondence. These can be enabled by MAC control elements (CEs).

[0014] 3GPP NR Release 15 is a semi-static codebook for HARQ ACK transmission. It also supports dynamic codebooks. UE will use one of the codebooks. It can be configured as follows. A semi-static codebook may have a fixed size. UE is PD Even if you don't receive a grant for SCH, HARQ for all slots It can transmit an ACK. It can transmit a NACK for that slot. Therefore The payload can be large for semi-static codebooks. The HARQ AC may have a variable size and is only available for scheduled grants. It may support the transmission of K. The scheduling DCI is about its codebook. cDAI and tDAI are shown in UE to indicate the number of scheduled grants. DAI is incremented each time a scheduling DCI is transmitted, while tDAI is ( Maintain the total number of DAIs in the codebook (including scheduling between carriers) It will hold. If DCI is not received, the difference between cDAI and tDAI is which DCI This may indicate that it was not received. For this reason, the UE may ambiguously indicate that the scheduled PDSCH was not received. It is possible to make a decision without much thought and to respond negatively to DCIs that were not received.

[0015] If a UE has a PUSCH transmission that overlaps with a specific PUSCH transmission, the UE will... Puncture SCH or PUSCH resources around UCI By rate matching, it may be possible to piggyback on UCI on PUSCH. The encoded HARQ-ACK bit can be mapped immediately after the first DMRS. When PUSCH uses frequency hopping, the HARQ-ACK modulation symbol is, It can be divided between wavenumber hops. The encoded CSI bits are the first non- It can be mapped starting from the DMRS symbol.

[0016] Multiple traffic types with different latency, reliability requirements, cycles, and payloads. This may be supported for a single UE. Multiple configured Grants (CGs) may differ. The UE can be configured to support various traffic types and priorities.

[0017] 3GPP NR Release 15 introduced CG PUSCH. Grant, RR Can be configured (Type 1), or can be enabled / disabled via DCI (Type 2) The configured grant timer is initiated during the transmission of the HARQ process from the UE. This could prevent new transmissions of the same HARQ process. CG PUSCH correctly debits gNB. If not coded, gNB will provide a dynamic grant for retransmission in CS-RNTI. Send to E.

[0018] Code Block Groups (CBGs) allow UEs to ACK TB at a finer granularity. Introduced in 3GPP NR Release 15 to enable the transmission of / NACK. B is the Code Block Group Transm Index in DCI. The CBG index is indicated through the (Issay Index:CBGTI) field. Therefore, retransmission can be scheduled for specific CBGs.

[0019] The embodiments described herein address the problems associated with transmission at different priority levels. In the examples described herein, URLLC traffic represents high-priority transmission. eMBB traffic can be used to represent low-priority transmissions. However, However, the technologies described herein are supported by UE with more than two priorities. It can be applied to any possible transmission type.

[0020] To support various applications, it supports transmission at various priority levels. It may be desirable to do so. Transmission priority may be identifiable at the MAC layer, but not at the physical layer. It may be beneficial to enable priority identification. For example, physical transmission has already started. They may exist, but they must be preempted at the physical layer. Methods of identification are described herein.

[0021] For example, in the event of a PDSCH collision within the UE, the UE receives a preemption indication. In doing so, both eMBB and URLLC traffic can be routed. This is because URLLC Conflicts within the UE must be avoided to maintain service reliability and latency. This specification describes a method for defining UE behavior when occurring on a DSCH.

[0022] HARQ ACK transmission can be used for multiple priorities. In conventional systems, The UE transmits ACK / NACK for both colliding PDSCH grants. It does not have a defined mechanism. The HARQ codebook has different reliability and delay requirements. The transmission can be extended to support UCI. When a data entry is returned, the priority levels of the UCI and PUSCH may be taken into consideration.

[0023] The procedure described herein is for handling the prioritization of PUSCH grants within the UE. This is described as follows: For example, between dynamic grants or high-priority configured grants, UL If a collision occurs within the UE and a dynamic grant occurs, the UE procedure described herein The server handles collisions. The MAC layer procedure for prioritizing within the UE is U This specification describes how E can enable prioritization in the MAC layer.

[0024] According to one embodiment, gNB is RNTI, DCI length, field at DCI, PD Using one of the CCH resources and grant durations, grants are processed through DCI. Priority can be indicated. UE uses PUSCH data or RNTI used in PUSCH. Priority can be indicated via UL transmission. In the case of preemption within UE, preemption When no indicator is received, the UE is preempted by its high-priority PDSCH. The option allows the resources of that low-priority buffer to be streamed. Preemption within the UE In the case of a preemption indicator, when the preemption indicator is received, the UE preempts The RNTI indicator can be used to determine the priority of the buffers being flowed. The ARQ ACK codebook may support multiple priorities. RRC signal The ring can consist of UEs with codebooks used for each priority. Multiple HARs QACK codebooks can be transmitted via slots. Each codebook is transmitted via slots It can be transmitted via buslots. Subslots can be transmitted at a finer granularity by the K1 parameter. The additional field K1a may be shown as a sub-slot offset within the slot. This can be introduced in DCI to demonstrate that when multiple dynamic codebooks are configured, UE This uses cDAI, tDAI, and priority markings for PDSCH grants, The codebook to which ACK / NACK belongs can be determined. For multiple TRP transmissions, the UE This allows HARQ ACK feedback to be transmitted to each TRP in different codebooks. ORESET DMRS or another configured RS is spatially oriented for PUCCH transmission. This may indicate that UE may override the spatial orientation configured through MAC CE, Space indicated by CORESET or configured RS for PUCCH transmission Direction can be used. Multiple HARQ ACK codebooks are piggyback on PUSCH transmission. It can be reversed. Each codebook is mapped to one sub-slot of PUSCH. Obtain. Different codebooks that carry UCIs with different priorities, different PUSCH transmissions. It can be mapped to a hop. A beta offset value of 0 is a piggyback on the push. It may be possible to remove the affected UCI resources. HARQ ACK codebook The 'k' can be mapped to multiple repetitions of the PUSCH transmission. Higher priority CG group When the HARQ process ID of a runt conflicts with that of a lower-priority dynamic grant... UE may ignore low-priority grants when multiple CG grants conflict in UE. The UE can retransmit preempted CG grants on the CG resources. The E push iteration is an early termination recognized by one TRP, timer-based It may be subject to termination, or selective termination depending on which TRP recognized the transmission.

[0025] Some of the examples described herein may be for unpaired spectra, and some figures The y-axis does not explicitly include the "frequency" label. This is mainly because the time domain (x-axis) is... This is because they are relevant in those figures. However, the principles / examples described herein are also It can be applied to the spectra of pairs.

[0026] Grant priority PHY layer identification is described herein. The UE receives PDSCH. To do so, or to schedule or configure to transmit PUSCH or PUCCH It can be done. However, gNB will override that transmission with a higher priority transmission. It is possible. For example, eMBB PDSCH is URLLC PDSCH for its UE. It can be preempted by URLLC. In another example, eMBB PUSCH is URLLC It can be preempted by PUSCH. URLLC PUCCH is eMBB It may clash with PUCCH. If there is enough time to react to Grant, UE's MA Layer C may prioritize higher-priority transmissions, and MAC delivers the prioritized transmissions to the UE. Lower priority transmissions can be canceled. On the UL, the UE has already started transmission at the PHY layer. If this is the case, identify that another transmission may be more important and stop the lower-priority transmission. This allows for the transmission of higher priority signals. For this purpose, the PHY layer recognizes the transmission priority. It may be desirable to have this. For example, if the priority of the DL PDSCH grant is PH If recognized as Y, the UE will accordingly prioritize its HA over other lower-priority UL transmissions. RQ-ACK UCI transmission may be prioritized. Prioritization can be set by one of the following methods. It may be beneficial to show this.

[0027] RNTI is used to scramble the grant's DCI and indicate priority to the UE. It is possible. If eMBB and URLLC only have two priority levels, then the higher trust Regarding reliability, RNTI (MCS-C-RNTI) which indicates MCS, indicates URLLC. It can be interpreted as follows. However, multiple priorities such as priority within URLLC itself support When used, multiple RNTIs can be used to indicate priority. gNBs are as follows: As shown in the example in Table 1, UEs are configured with different RNTIs, and their relative priority levels It can indicate priority level. Priority level "0" can correspond to the lowest priority, and priority is priority level It increases in ascending order of the letter "Ru".

[0028] [Table 1]

[0029] The exemplary RNTIs shown in Table 1 can be used to mask the C-RNTI of the UE. Upon receiving the grant, the UE will use DCI for all possible masked RNTIs. You can check the CRC and select the one that the CRC will pass through.

[0030] Regarding dynamic grants, RNTI can do so by blindly decoding DCI. It can be detected by E and given by C-RNTI “Equation 1 below” RNTIp Here, RNTIp can be a masked RNTI from Table 1 with priority level p. In these examples, the RNTI mask can generally be configured for multiple UEs. This configuration is, This can occur through SI or in UE-specific ways, and multiple UEs may have different priorities. It can be composed of RNT Ip values.

[0031]

number

[0032] In one example, instead of a mask, the gNB uses multiple C-RNs for multiple priority levels. TI (C-RNTI1, C-RNTI2, etc.) can be provided to the UE. The configuration is UE-specific. It can be done in this way.

[0033] Alternatively, or furthermore, RNTI can provide multiple UEs through a group-common PDCCH. It may be provided.

[0034] For grants configured as Type 1UL, the priority level for the grant is R It can be configured through RC. For example, to distinguish between different configured grants, configuration If a grant is given an ID "Configured Grant ID", the ID is priority level It may be equivalent to a bell. For a specific application, multiple configured grants It may be useful to provide the same priority to them. For example, in an NR-U application Traffic with a specific priority may be given multiple configured grants. E selects grants based on channel availability. In this case, the field "Preference" The "degree level" can be configured in addition to the configured grant ID.

[0035] For Type 2 configured grants, the enabled DCI is the target priority in Table 1. CS-RNTI can be used, masked by the RNTI level. Activated DCI is CS- RNTI" can be scrambled using the above formula 1"RNTIp". Disable D CI can also use CS-RNTI masked with RNTIp. This is particularly advantageous. If the previously configured grant ID can be the same for the grant, It may be suitable. Alternatively or further, disabling DCI can be done using only CS-RNTI. Grants to UE can be disabled, simplifying the procedure and disabling DCI's rigidity. To improve security, UE uses the configured grant ID to eliminate type 2 grants. We will decide to make it effective.

[0036] Figure 1 shows that the priority of a configured grant can be changed by another enabled DCI. Figure 50 is shown. Figure 1 shows PDCCH 51, other signals 52, and gap 55. Figure 1 also shows the CS-RNTI" formula 1"RNTI2 for priority level 2. CS can use the enabled DCI56 and priority level 4 to scramble. -RNTI”The above formula 1”RNTI4 can be used to enable DCs that can be scrambled. I57 is shown. PUSCH53 includes a configured grant with priority level 2. PUSCH54 includes configured grants with priority level 4. Alternatively, Furthermore, MAC CE from gNB is used to set the priority level to UE. It is possible.

[0037] The explicit field "Priority Level" in DCI can indicate the priority of a grant.

[0038] The DCI length for a grant may indicate the grant's priority. Compact DCI While this can be used for URLLC, using this method, a larger DCI length is preferable. It needs to be designed to support multiple levels as described above.

[0039] One or more characteristics of the PDCCH, such as the start PRB of the DCI's CCE, are priority level This can indicate a value. For example, (start PRB mod priority level maximum) is about grants. The priority level can be set. The start symbol of PDCCH may indicate priority. The Aggregation Level (AL) of CH can indicate priority, UR Because LLC DCI may require a higher priority compared to eMBB DCI, Higher AL may be used. ref,p The set of reference ALs, represented as ", is each priority The degree can be configured in UE. If the received AL is in its set, UE is superior Previously, PDCCH can be identified as belonging to level p.

[0040] HARQ processes can be configured for specific priority levels. They have high processing power. Regarding the UE, this is because the typical delay for HARQ-ACK can be small. Therefore, it can function perfectly well. Thus, most HARQ processes use URLLC cases. There may be cases where it is not necessary to support it.

[0041] The number of resources in a grant can indicate the priority level. For example, between 2OS and 4OS. Push transmission in the mini-slot of the intermediate length may have the highest priority, while 10OS Push transmission in a mini-slot between 14OS may indicate the lowest priority. The time resource range and corresponding priority table are shown to the UE via RRC signaling. It is possible. When receiving a grant, the UE prioritizes it based on the amount of time resources available to it. The degree can be identified. Grant's MCS can indicate priority levels and require higher reliability. High-priority transmission may have an MCS value with lower spectral efficiency.

[0042] gNB can configure multiple DMRS sequences into UEs corresponding to different priority levels. The UE, upon receiving a PDSCH grant, detects the DMRS sequence of the PDSCH. It is possible to recognize priority levels. For example, an RNTI mask can be used to distinguish between different priority levels. It can be used to generate DMRS sequences.

[0043] The arrival time of a DCI can determine its priority level. The latest DCI has a higher priority. This can represent DCI. However, this does not necessarily apply to all scenarios. For example, in some scenarios, the UE receives DL signals / channels from multiple TRPs in a cell. It can receive and / or transmit UL signals / channels in a cell to multiple TRPs. In a multiple TRP case, one TRP may provide an eMBB grant. P may provide a URLLC grant. The eMBB grant follows the URLLC grant. It may arrive, but the PDSCH resource may collide, causing a collision within the UE. Therefore, the latest DCI does not necessarily have to be a high-priority indicator.

[0044] UCI priorities can be mapped to grant priorities. For example, PDSCH has priority. If a degree level p is present, the HARQ ACK feedback has a priority p. Periodic CSI reports are BLER targets for specific priority p>plow reports. Even when corresponding, a lower priority level p configured by gNB low And to UE It can be transmitted. This generally means that periodic CSI reports have a lower priority than most transmissions. It may be for the purpose of having all periodic CSIs (for eMBB and URLLC). The reports can be transmitted at the same frequency. However, between two priority periodic CSI reports In case of a conflict, reports about higher-priority BLERs may take precedence over lower-priority reports. Reports on BLER levels may be omitted. On the other hand, A-CSI reports on the corresponding troughs It may be transmitted at the priority level of the hack, and the priority indicated by DCI that schedules it. The previous level can be used.

[0045] It is useful to indicate the priority of UL transmission, such as PUSCH or PUCCH, during transmission. For example, UE uses URLLC and eM in separate codebooks for ACK / NACK. BB PDSCH can provide the delay and reliability for each priority, These are achieved through appropriate scheduling and coding rates in PUCCH. Obtain. PUCCH HARQ-ACK resources are obtained using both URLLC and eMBB. It can be used as such.

[0046] Figure 2 shows PUSCH and PUC with C-RNTI masked by priority level RNTI. CH example 200 is shown. UE is used to scramble UL UCI. Priority is indicated through RNTI (=C-RNTI) “RNTIp” in the above formula 1. gNB RNTI recognizes the priority level at which a PUCCH HARQ-ACK was received. This can be identified. Figure 2 shows PDCCH201, other signal 206, and gap 205. Figure 2 also shows DC in slot #0 being scrambled with mask RNTIp1. I210 indicates scheduling PUSCH0 203 in slot #2. USCH may also be transmitted with priority level mask RNTIp1 203. Mask RN DCI, which can be scrambled in TIp1, schedules PDSCH0 in slot #1. ールし得る(220). The corresponding PUCCH can be transmitted on slot #3. Here , the UCI can be scrambled with the mask of RNTIp2 204.

[0047] The preemption indication for a given priority is described herein according to another embodiment. When DL preemption occurs in the UE, the grant of the low-priority PDSCH to UE1 can be preempted by the grant to UE1 with a higher priority.

[0048] Figure 3A shows an example 300 of preemption in a UE of a low-priority PDSCH by a high-priority PDSCH with a resource element (RE) collision between PDSCHs. Figure 3A shows PDCCH3 01, PDSCH for slot #0 312 to slot #2 313 regarding frequency 3 14, PDSCH eMBB 302, PDSCH URLLC 303, and other signals 304 In the example of Figure 3A, the low-priority PDSCH eMBB can be scheduled for slot #2 by DCI in slot #0 (310). Subsequently, the D CI in slot #2 schedules the high-priority URLLC PDSCH in slot #2 URLLC (311). As a result, the resources collide for the PDSCH.

[0049] Figure 3B shows an example of preemption in a UE of a low-priority PDSCH by a high-priority PDSCH when PDSCH eMBB and PDSCH URLLC do not collide in frequency but overlap in time. Figure 3B shows PDCCH305, PDSCH for slot #0 322 to slot #2 323 regarding frequency 324, PDSCH #0 322, PDSCH eMBB306, PDSCH U RLLC 307 and other signals 308 are shown. In the example in Figure 3B, the low-priority PDSCH e MBB It can be scheduled for slot #2 by DCI in slot #0 ( 320). Next, DCI in slot #2 is high priority URLLC P DSCH URLLC Schedule (321). The UE processes both PDSCH. If it has the ability to do so, it may do so. Otherwise, the UE shall not perform its PDSCH eMB B It can be assumed that it was preempted by its own PDSCH URLLC.

[0050] Figure 4A shows PDSCH URLLC Figure 4A shows 400 examples of preemption. PDCCH401, PDSCH for slot 410 regarding frequency 411 eM BB 402 and 403, as well as UE1PDSCH URLLC Shows 404. Plié If the impending is entirely a preemption within the UE, that is, if other UEs are affected If it may not be accepted, gNB will use INT-RNTI for scrambling. Send preemption signals via group-common DCI in format 2_1. It is not necessary. In this case, UE1 will have conflicts regarding low-priority and high-priority grants. When recognizing resources, DL preemption can be identified. UE1 is a low-priority PDS. For each buffer of CH, the soft bit corresponding to the affected RE is It will run automatically.

[0051] Figure 4B shows PDSCH URLLC Another example of preemption is shown in Figure 4B. PDCCH405, PDSCH for slot 420 related to frequency 421 eMB B 406 and 407, as well as UE1PDSCH URLLC This shows 408. Preempted resources may include resources from other UEs. Here, The eMBB PDSCH406 in UE2 may be preempted. In this case, the gNB is The UE may send a preemption indication for scrambling. Sent via group-common DCI in format 2_1 using INT-RNTI. This may occur. When UE1 receives a preemption indication, it will send low-priority and high-priority PDs. The buffer can be used for both SCH. However, in this case, it is the high-priority buffer. You shouldn't run buffers. Instead, UE1 only runs low-priority buffers. You may use one of the following pieces of information. (1) UE1 assumes that the most recent transmission (PDSCH1) has a higher priority. To obtain it, the buffer corresponding to the transmission (PDSCH0) received earlier in time flows through it. It is possible.

[0052] UE1 uses priority level information in grants to prioritize higher-priority HARQ processes. The system can determine which buffer to prioritize and send the data to the buffer with lower priority.

[0053] Figure 5 shows a UE having a collision between low-priority PDSCH and high-priority PDSCH. The following is an example procedure 500 for running a low-priority HARQ buffer. When Rosilla starts (step 501), the UE will check for PDSCH collisions within the UE. It can be monitored (step 502). The UE can determine if there is a collision in the UE of the PDSCH. It can be determined (step 503). If no collision is detected in the UE of the PDSCH, the UE will You can return to step 502. If a collision is detected in the UE of the PDSCH, the UE will pre It is possible to determine whether an emptiness indicator has been received for a conflicting resource (step (P504). Regarding preemption within UE, which grant has a higher priority? UE blocks that indicate which resources will be diverted to lower priority buffers. A preemption indicator may be sent to the UE by the gNB. DCI may carry a set of priorities in its payload, and regarding that, UE A buffer can be used if the resource experiences preemption. If a preemption notification is received for a conflicting resource, the UE will preempt the resource. Lower priority buffers may be routed to resources indicated by the dicator (Step 5) 05) If a preemption indication is not received for a conflicting resource, U E is a soft bit in a lower priority buffer that is affected by a high priority PDSCH. The procedure can then be terminated (step 506). In the alternative procedure, the UE performs a plié within the UE (due to the arrival of the colliding grant). If both the impending and preemption indicators are detected, the UE will... The indication indicator can be ignored. It is controlled by the PDSCH with higher priority. And in the preempted RE, only the bits of the lower-priority PDSCH are passed. Obtained.

[0054] FIG. 6 shows an example 600 in which a UE pre-empts the PDSCH of another UE. FIG. 6 is regarding the slot 610 for frequency 611, PDCCH 601, UE1 PDSC H priority level 1 602, UE0 PDSCH priority level 0 603, UE2 PDSC H priority level 2 605, and UE3 PDSCH priority level 3 604 are shown. When multiple priority levels can be supported by a UE, it may be necessary to indicate the priority level that must be flushed. For example, consider that UE2 has a PDSCH transmission with priority level = 2 605. It pre-empts specific resources of UE1 with priority level = 1 602 and UE0 with priority level = 0 603. However, it does not pre-empt the resources of UE3 with priority level = 3 604 (since the priority of UE3 may be higher than that of UE2). However, since the priority of UE3 may be higher than that of UE2, it does not pre-empt the resources of UE3 with priority level = 3 604.

[0055] Format 2_1 DCI can indicate, at a coarse level, the REs affected in time and frequency. However, the indication does not have a granularity that indicates that the resources of UE3 may not be pre-empted. Therefore, according to the Release 15 procedure, UE0, UE 1, and UE3 can all flush their buffers. However, the intention is to enable only UE0 and UE1 to flush their buffers without affecting the buffer of UE3. For this reason, in the embodiments described herein, the INT- RNTI can be masked with a priority level mask. The pre-emption indicator DC RNTI can be masked with a priority level mask. The pre-emption indicator DC The UE receiving I can detect the mask and determine the priority level to send. In the current example, The gNB sends DCI with the RNTI1 mask. Therefore, the UE receives priority level It can be recognized that the buffer must be passed if it has an ≤ 1 value. Only UE0 and UE1 will run those buffers, while UE3 will not.

[0056] Figure 7 shows RNTI p UE for sending a soft buffer with priority indicated through a mask An exemplary procedure 700 for use in is shown. In the example in Figure 7, the UE is priority Level <= Reception priority indication via preemption indicator, affected battery The process is initiated. When the procedure starts (step 701), the UE preempts The indicator can be monitored (step 702). The UE indicates priority level p. It can be determined whether a reemption indication has been received (step 703). Priority level If a preemption indication showing p is received, the UE will check the priority level <= p. The buffer can be run with preempted resources (step 704). Priority If no preemption indication indicating level p is received, the UE proceeds to step 702 It can return to the previous state. Then the procedure terminates (step 705).

[0057] Alternatively, or furthermore, a UE can preempt other UEs through a preemption indicator. Preemption indicator may indicate the priority level of a transmission that is being reempted. U has resources that have been preempted with a lower priority than the priority indicated by E flows through that buffer.

[0058] Procedures for high-priority and low-priority control signaling are described herein. Generally, high-priority transmissions may take precedence over low-priority transmissions. UE is high-priority transmission To support this, low-priority transmissions may be canceled or punctured. Scenarios that include but are not limited to these may be supported. (1) The UE prioritizes high-priority PUSCH and drops low-priority PUCCH. (2) The UE prioritizes high-priority PUCCH and drops low-priority PUSCH. (3) UE prioritizes high-priority UCIs and drops low-priority UCIs. (4) The UE prioritizes high-priority PUCCHs and drops low-priority PUCCHs. (5) The UE prioritizes high-priority pushes and drops low-priority pushes.

[0059] Other methods for accepting transmissions with different priorities are also described below. It may be ported.

[0060] Multiple PUCCH transmission opportunities in a slot are described herein. The UCI is in the slot Each can be transmitted once. M per slot for low-latency, high-priority PDSCH (M It may be desirable to provide UCI feedback opportunities ≥1). The more, the greater the number of feedback opportunities within the slot. The time resources for each opportunity can be called sub-slots. Therefore, there are M sub-slots. The slot may support UCI transmission.

[0061] Figure 8A shows HARQ-ACK UC on PUCCH with single UCI feedback. An example of I transmission 800 is shown. Figure 8A shows PDCCH801, P for multiple slots. DSCH0 K1 = 4, PRI = 0, 802; PDSCH1 K1 = 3, PRI = 1, 8 03; PDSCH2 K1 = 4, PRI = 0, 804; PDSCH3 K1 = 2, PRI <1 808; PUCCH 01 PRI = 1, 807; PUCCH 23 PRI = 1, 8 09; Other DL signals 810; Other UL signals 805; and Gap 806 are shown. Figure 8A As shown, for multiple PDSCHs, HARQ - ACK can be jointly transmitted in a slot using a single - time HARQ codebook. Here, for PDSCH0 802 and PDS CH1 803, the ACK / NACK can be transmitted on PUCCH 807 such that the corresponding K1 value represents slot #4 for UCI feedback, and PRI = 1 can be used such that PRI is from the latest scheduling DCI. Similarly, for P 01 DSCH2 804 and PDSCH3 ⑧, the ACK / NACK can be transmitted on PUCCH 80 9 such that the corresponding K 1 value represents slot #5 for UCI feedback 23 80 and can be transmitted on PUCCH 809.

[0062] Figure 8B shows an example of HARQ - ACK UCI transmission on PUCCH with multiple UCI feedback opportunities in a slot. Figure 8B shows PDCCH 811, PDSCH0 812, PDS CH1 813, PDSCH2 814, PDSCH3 815, PUCCH 819, PU CCH 01 819, PU CCH 23 820, other UL signals 816, and gap 817 for multiple sub - slots (e.g., sub - slots 821 and 822). As shown in Figure 8B Therefore, multiple opportunities can be provided for UCI feedback in the slot. Here are two PUCCH transmission can be supported in the slot (M=2). PDSCH is in the slot It can be received in the 2OS mini-slot 813 at #0. PDSCH0 and PDSCH1 Regarding ACK / NACK, the PUCCH for OS#6 and 7 is located in slot #1. 01 819 It can be transmitted in sub-slot #1, while for PDSCH2 and PDSCH3... The ACK / NACK is PUCCH in slot #1 823, extending to OS #12 and 13. 23 It can be transmitted as 820 via sub-slot #2.

[0063] The number of sub-slots can be configured in the UE by the gNB through RRC signaling. Furthermore, sub-slots can handle different types of traffic, their priority, and latency. Ports can be of different lengths. The gNB uses subslots in a way that does not overlap. It can be configured as E, and as a result, there may be no collisions between transmissions on the subslot. Alternatively, gNB can configure subslots in UE with overlapping resources. If it is identified that transmission can be scheduled to occur on a sub-slot, then the transmission One of them may be dropped. A lower priority transmission may be dropped, or a later sub-slot may be dropped. This could be the case, or the previous sub-0 slot could be dropped.

[0064] The following method is used for PUCCH transmission when the subslot is M>1. It can be used to indicate something. If M subslots are permitted for PUCCH transmission, K1 is a subslot This may be shown regarding the number of sub-slots per slot for each priority level. It can be done. K1 can be interpreted accordingly for each priority level, so each priority The level is interpreted as K1 according to the number of sub-slots configured within each slot. This configuration can be provided to the UE through RRC signaling. Table 2 below shows what K1 is Here's an example of how it can be configured with a different number of sub-slots per slot. give.

[0065] Figure 9A shows that each slot has one sub-slot and the slot is incremented by a unit. Exemplary subslot configuration 900 with eMBB PDSCH configured for K1 Figure 9A shows PDSCH0902 with PDCCH901, gap 905, and K1=2. And, PDSCH1903 with K1=1 and PUCCH 01 904 and multiple slots This indicates slots (for example, slot #0 910 and slot #2 911). K1=2 PDSCH0902 and PDSCH1903 with K1=1 are in slot #2 911. It can be recognized jointly.

[0066] Figure 9B shows the increments of two sub-slots and half a unit of the slot for each slot. Another exemplary sub-slot having a URLLC PDSCH configured for K1. The configuration is shown. Figure 9B shows multiple slots, namely sub-slots 0, 930 and , Slot #0 936 with main slot 1 931, sub-slot 0 932 and Slot #1 937 with bus slot 1 933, and sub-slot 0 934 And slot #2 938 with sub-slot 1 935 is shown. Figure 9B also shows P DCCH920, gap 925, other signal 926, K1=3 PDSCH0921, K PDSCH1939 with 1=2, PDSCH2922 with K1=2, PUCCH 01 923, And PUCCH2924 is shown. In the example in Figure 9B, DSCH0 and K1=3 PDSCH2 of slot #1 can be jointly recognized as sub-slot #1 of slot #1. PDSCH2 in sub-slot #0 of slot #1 with K1=2 is sub-slot #2 It can be recognized as slot #0.

[0067] Figure 10 shows K1 being incremented at the finest granularity of the subslots for the lowest priority. It shows 1000. Figure 10 is PDS with PDCCH1001, gap 1005, K1=4. CH01002, PDSCH11003 with K1=2, and PUCCH 01 1004 and, It has multiple slots (for example, slot #0 1010 and slot #2 101) 1) is shown. PDSCH01002 with K1=4 and PDSCH11003 with K1=2 are In slot #2 1011, it can be jointly recognized. In this alternative, K1 is the finest. It can be interpreted according to the granularity, that is, according to the maximum number of sub-slots per slot. UE may determine which K1 to use based on the priority level signaled in the grant. Figure 10 shows that the maximum number of sub-slots per slot for UE can be 2. Assuming this is the case, the eMBB user increments K1 by the maximum number of sub-slots per slot. This shows the case. Therefore, only K1 values ​​such as 2, 4, and 6 are used for the slots of eMBB. Regarding the PUCCH resource, it may be effective for eMBB.

[0068] [Table 2]

[0069] Figure 11 shows that K1 represents the slot for PUCCH, and K1a represents the sub-slot. Example 1100 is shown. Figure 11 shows multiple slots, i.e., sub-slots 0 1110 Slot #0 1116, which has sub-slot 1 1111, and sub-slot 0 11 Slot #1 1117 with 12 and sub-slot 1 1113, and sub Slot #2 1118 with lot 0 1114 and sub-slot 1 1115 Figure 11 also shows PDCCH1101, gap 1108, other signals 1107, K1 PDSCH01102 with =1 and K1a=1, PDSCH with K1=1 and K1a=1 11103, PDSCH21104, PUCCH with K1=1 and K1a=0 01 110 5, and PUCCH21106. Additional bits indicate sub-bits for PUCCH. A slot can be introduced in the scheduling DCI with the field "K1a". K1 can be incremented with respect to the slot, and K1a is the offset of the number of sub-slots within the slot. It may provide a slot. In Figure 11, K1 indicates the slot offset, and K1a is PUC This shows the sub-slot offset within that slot for the CH resource. Each slot has M=2 sub-slots.

[0070] HARQ codebooks for different priority transmissions are described herein. gNB is , HARQ ACK bits for different priorities are co-encoded, or It can be determined whether they are encoded separately. If they are encoded separately, different code Codebooks can be used for different priority levels. gNB is RRC signaling This can indicate the codebook type for each priority level. For example, eMBB Transmission can use a semi-static codebook, while URLLC uses a dynamic codebook. It can be used. Overhead in UCI may be lower, and smaller payloads are possible. Because it can be transmitted with fewer resources and with greater reliability, dynamic codebooks are used in URLLC. It is quite suitable. Furthermore, it is expected that URLLC HARQ-ACK can be transmitted with low latency. This is possible. Therefore, many PDSCHs do not need to be multiplexed with the same PUCCH. Therefore, semi-static codebooks are particularly problematic when URLLC traffic is sudden. It may be unnecessary in some cases.

[0071] Separate PUCCH resource sets for different priorities, or each resource set It may be desirable to configure additional PUCCH resources. For example, eMBB Raffic may have a PUCCH resource at the last symbol of the slot, on the other hand, U RLLC minimizes delay by including resources in the leading symbol of the slot. Multiple PUCCH resources may be required in the set. RRC signaling is PUCCH Recognition through resource sets and PUCCH resources in the PUCCH resource set. The corresponding priority levels of the possible PDSCH can be configured.

[0072] PUCCH resource sets differ for different priority levels, HAR You may use separate codebooks for QACK. The PUCCH resource set is different. If two transmissions with the same priority level can be the same, then the HARQ-ACK is: Can they be co-encoded and transmitted in a single codebook, or in separate codebooks? It can be transmitted over the network. Whether HARQ-ACKs of different priorities can be transmitted together. This behavior can be configured in the UE by gNB through RRC signaling.

[0073] Figure 12 shows separate HARQs for p=0 (eMBB) and p=1 (URLLC). An example 1200 from the ACK codebook is shown. Figure 12 shows PDCCH. 01 p=0 and K1 =3 1201, PDCCH 00 p=1 1202, PDCCH 11 p=1 1203, PDCCH 22 p=1 1204, PDCCH 33 p=1 1205, PDCCH 34 p =0 and K1=1 1208, PDCCH 11 p=0 and K1=3 1211, PD CCH 23 p=0 and K1=2 1212, and PDCCH 34 p=0 and K1= 1 1213, gap 1218, other DL signal 1206, PUCCG 1207, and This shows PUCCH1210. Multiple dynamic codebooks for multiple priority levels. When used, counters cDAI and tDAI are set separately for each priority level. It is possible. The codebook for priority level p has parameters cDAIp and tDAIp These dynamic codebooks can be determined using cDAIp and tDAIp. The scheduling can be shown in DCI, where p is DCI (through one of the methods described above). Alternatively, it can be determined by the UE from the priority level embedded in the PDCCH. Therefore The UE can then prepare a codebook for transmitting about priority level p. Figure 12 In this example, the cDAI and tDAI values ​​are related to eMBB and URLLC PDSCH. It can be incremented independently. The eMBB PDCCH is PUCC in slot #3 1217. It may indicate an H1210 resource. As a result, those HARQ-ACKs are one code The data can be combined in a book and transmitted on PUCCH1210 in slot #3 1217. URLLC PDCCH may indicate a PUCCH resource in slot #1 1215, U The RLLC HARQ-ACK is combined into one codebook and slot #1 120 7. It can be transmitted over PUCCH. tDAI and cDAI are shared between priorities. In total, those codebooks cannot be easily separated. This is because DCI is overlooked. In that case, the difference between cDAI and tDAI indicates this, but UE is URLLC or e It was not possible to determine whether the MBB transmission scheduling had been overlooked, therefore Then, the overlooked PDSCH in the eMBB codebook or URLLC codebook This is because it does not recognize whether or not to respond negatively.

[0074] The codebook may be determined based on the PUCCH resource. HARQ-ACK transmission may be possible in PUCCH resources, and URLLC delay requirements may be met. This can be beneficial. Multiple PDSCHs with different priority levels point to the same PUCCH resource, U If E is allowed to multiplex HARQ-ACKs for different priority levels, UEs can jointly transmit HARQ-ACKs for those transmissions using the same PUCCH resource. In this case, cDAI can be reset after each PUCCH resource transmission opportunity.

[0075] Multiple TRP PUCCH transmissions are described herein. Multiple TRP transmissions are supported. When this happens, the UE will take the first PDCCH and the corresponding first PDSCH from the first TRP. Upon receiving, the second TRP receives the second PDCCH and the corresponding second PDSCH. Obtain. The time-frequency resources for the first and second PDSCHs are either overlapping or They may not overlap or may partially overlap. For example, PDSCH may be in the same slot. Alternatively, it may be received in a different slot. PDSCH may, for example, have duplicate PRBs or duplicates. It may be received on a PRB that does not perform this function.

[0076] In some scenarios, the UE is a PDS in which the first set of layers originates from the first TRP. CH, and a second set of layers may receive PDSCH originating from the second TRP. So, the first and second sets of layers transmit different codewords or transport blocks. It can be used to do so. In another example, a single codeword or transport block is the first It can be transmitted over layers of a second set of data.

[0077] Signals / channels transmitted / received from / to different TRPs within a cell are different It can be associated with an application, thereby allowing it to be associated with different priority levels. It is possible. For example, the macro TRP has the best connection to the core network, so U It can be used for RLLC, but on the other hand, the UE location involves an unideal backhaul. Nearby low-power TRPs can be used for eMBB traffic.

[0078] Figure 13 shows an example 1300 in which the UE transmits to multiple TRPs. Figure 13 shows slot 13 PDCCH1310 in 14, gap 1311, and PUCCH1312 and 1 It shows 313. UE1303 is on beam B01304, with PUCCH1312 of UCI0. Transmit to TRP01301 and send PUCCH1313 of UCI1 on beam B11305 Transmits to TRP11302. UE1303 transmits separate UCIs to each TRP1301 and It may be provided to 1302. Each UCI corresponds to a specific TRP (e.g., the 1st or the 1st). CSI report (corresponding to layers of 2 PDSCH or the first or second set of PDSCH) This may include the notice and HARQ-ACK. As a result, UE1303 is P in the appropriate spatial direction. UCCH1312 and 1313 can be transmitted to TRP1301 and 1302 respectively. In other words, for PUCCH transmissions corresponding to QCL with DL RS or UL RS The beam can differ for each TRP.

[0079] Figure 14 shows an example of PUCCH transmission to multiple TRPs 1400. Figure 14 is PDCC. H1405, Gap 1409, Other signal 1408, Slot #0 1420 in TRP i PDSCH01406, TRP, with K1=4 and PRI=0 transmitted by j by The PDSCH11407 and PUCCH UCI are transmitted with K1=2 and PRI=1. 01410, and PUCCH UCI11411 are indicated. The spatial direction is UCI0 and Since each UCI1 can be different, different PUCCH resources are available for each PUCCH resource. For UCI0 and UCI1, the source can be identified in a specific spatial direction. As shown in Figure 14, UCI0 and UCI1 are PUCCH1410 And it is transmitted via PUCCH1411.

[0080] Figure 14 also shows TRP i and TRP j These are PRI=0 and PRI=1 respectively. PDSCH01406 and PDSCH11 on beams B01401 and B11402 This indicates that 407 will be transmitted to the UE. The UE is PUCCH1410 on UCI0, and the beam Responding to TRP0 in slot #2 1421 on B01403, PUCCH1 of UCI1 411 responds to TRP1 in slot #3 on beam B11404. P with PRI=0 The UCCH resource may be configured for transmission on beam B01403, with PRI=1. The source can be configured for transmission on beam B11404. (PUCCH resource availability) This configuration in the interdirectional direction can be achieved through MAC CE activation. Multiple TRPs are supported. If this occurs, multiple PUCCH resources will be configured for different spatial directions.

[0081] To overcome the activation overhead, the following alternatives are possible: UE is TRP It can be configured to use spatial orientation based on recognition. TRP recognition is SSB or This can be expressed in the form of a spatial relationship to CSI-RS or UL SRS. For example, T RP recognition can be linked to CORESET. For example, TRPi is linked to CORESE T i It can be scheduled using CORESET. i The TCI configuration is TRP i This may indicate the spatial direction used for PUCCH. In this case, UE is MA The spatial orientation of the C CE activation can be ignored. Instead, it recognizes and corresponds to TRP. The spatial direction can be used.

[0082] Figure 15 shows an example of PUCCH spatial orientation 1500 based on TRP recognition. Figure 15 shows P DCCH1509, Gap 1511, Other signal 1510, Slot #0 1520 TRP i PDSCH01506, TRP, with K1=4 and PRI=0 transmitted by j PDSCH11508, slot #2, with K1=2 and PRI=1 transmitted by PUCCH UCI01512 and PUCCH UCI1151 in 1521 Figure 3 is shown. Figure 15 shows CORESET transmitted via PDCCH1505. i TRP i nitsu This shows the possible configurations. i It can be scheduled with PDSCH with PRI=0. However, UE is TRP i Regarding this, beam B01501 can be used. CORESET j teeth , transmitted via PDCCH1507, TRP j It can be composed of the following: TRP j , PRI It can be scheduled with PDSCH = 0, but UE is TRP j Regarding beam B1150 2 can be used. Another alternative is to use the TCI state of CORESET instead of S Spatial direction based on SB, CSI-RS, or SRS is used for signaling at higher layers. Each TRP can be assigned to a UE through this process.

[0083] Please note that TRP recognition does not necessarily have to be explicitly used in any configuration information. Instead, TRP can be identified indirectly through spatial direction. Different PUCCH Can the spatial direction for this be explicitly configured through DL RS or UL RS? , or to the DL channel, for example, CORESET as described above i different PDSCH Connected to the TCI state of transmission, or to different TCI states of different layers in PDSCH transmission. obtain.

[0084] UCI on PUSCH is described herein. Piggyback on low-priority PUSCH. The high-priority UCIs described herein are those for URLLC. When there is an overlap with PUSCH for BB, URLLC UCI is eMBB PUSC It is proposed that H can be piggybacked. Because multiple instances or codebooks of UCI can be piggybacked on PUSCH. It could go back.

[0085] Figure 16 shows multiple HARQ ACK codebooks on a single PUSCH in a slot. An example of piggybacking, 1600, is shown. Figure 16 shows PDCCH1601, gap 160 7 and other signals 1602 are shown. The eMBB PUSCH1608 is in slot #3 It can be scheduled for 1623. URLLC PDSCH1603, 1604, 1605 and 1606 are in slot #1 1621 and slot #2 1622. It can be scheduled. Regarding PDSCH0 and PDSCH1 (represented as UCI0) ACK / NACK1609 is the first half of slot #3 (sub-slot #0 16 24) In which, they may be jointly encoded and transmitted, while PDSC (represented as UCI1) ACK / NACK1610 for H2 and PDSCH3 is half after slot #3. It can be jointly encoded and transmitted in minutes (sub-slot #1 1625).

[0086] eMBB PUSCH is a UCI-accepted rate matching or puncture This may be possible, depending on the UE's capabilities and latency when processing PDSCH, including the following: However, methods that are not limited to this include mapping UCI0 and UCI1 on PUSCH. It can be used for that purpose. (1) PUSCH enables UCI0 and UCI1 mapping of punctures It can be changed. (2) PUSCH ratematches resources around UCI0 and UCI1 It is possible to be chung. (3) PUSCH may rate match around resources about UCI0, It can be punctured by resources about UCI1. In this case, PUSCH The delay is sufficient to allow rate matching to accept UCI1. This may apply if it does not apply.

[0087] A similar principle can be applied to the UCI that carries the CSI. The URLLC, slot by slot If multiple UCI measurements and reports are required, the report should include UCI0 and in Figure 16. Similar to UCI1, it can be piggybacked on PUSCH.

[0088] Alternatively, an instance of UCI transmission on a slot could be a HARQ ACK. On the other hand, other instances may only carry CSI. For example, UCI0 is HARQ -ACK may include, while UCI1 may include CSI reports.

[0089] Alternatively, M UCI feedback opportunities in a slot are each HARQ-ACK It can transport both CSI and other related information.

[0090] The number of REs for UCI is DCI or higher tier that schedules PUSCH. The beta offset factor that can be shown through signaling is given by the following equation 2, and the following number The beta offset factor can be determined by Equation 3 and Equation 4 below. This represents some of the PUSCH resources that can be used for UE, each of the UCI's support advantages. It is proposed herein that the offsets should consist of different sets of offsets for the preceding time. The mth signaling opportunity of the UCI on PUSCH is the UCI m Represented by It is possible. For example, in Figure 16, m=0 and m=1 can be supported. It consists of the values ​​of Formula 5, Formula 6, and Formula 7 below for each opportunity. This is proposed to be the case. This is the target for different UCIs. It provides greater flexibility to gNB when configuring reliability. The configuration can be at a higher layer or This can occur through DCI scheduling PUSCH, and the feel indicates a beta offset. D can consist of one of the following methods: (1) The beta offset indicator may be available for each of the m UCI opportunities. If 2 bits are used for each opportunity, the total number of bits required is the number of opportunities. It is the same amount, and in some cases it may be larger.

[0091]

number

[0092]

number

[0093]

number

[0094]

number

[0095]

number

[0096]

number

[0097] (2) The beta offset indicator can be 2 bits regardless of the number of opportunities. Therefore, the DCI size does not need to be changed when m changes. In this case, beta offset The indicator shows the offset index for each of the m opportunities. Example This is shown in Table 3. Here, UE is the following four equations for each of the m opportunities. It can consist of a set of indices. Equation 9 below is the basis for Equation 10 below. This can be an index to a table of offset values. Here, i is the pin of the target UCI. Represents i load. For example, i=0 means that the UE has a maximum of 2 HARQ-ACK information bits. This represents the case of overlapping, where i=1 means there are more than 2 UEs, up to a maximum of 11 HARQ-ACK information. This represents the case where the reward bits are multiplexed, and i=2 means that the UE is greater than 11 in HARQ-ACK. This represents the case where many bits are multiplexed. DCI is a base that shows the sequence of offsets used. It carries 2 bits of the offset indicator. For example, URLLC UCI The following equation 11 is used to provide greater reliability to URLLC UCI, e It is possible that the value is greater than that given by equation 12 below for MBB UCI.

[0098]

number

[0099]

number

[0100]

number

[0101]

number

[0102]

number

[0103] [Table 3]

[0104] If push hopping is configured for UE, UCI m eMBB PUS It can be mapped to different hops in CH. This is because the UCI divides each hop in PUSCH This may differ from other systems that can be partitioned and mapped.

[0105] Figure 17 shows the UCI on different hops in Push. m An example of mapping 1700 is shown. Figure 17 is PDCCH1701 in slot 1710 with respect to frequency 1711, gap This shows 1702. As can be seen in the example in Figure 17, the eMBB PUSCH is in two hops. If configured, ACK-NACK1707 for PDSCH0 and PDSCH1 UCI01703, which includes PUSCH1704, can be transmitted at hop 1. UCI11706, including ACK-NACK1708 for 2 and PDSCH3, It can be transmitted at hop 2 of PUSCH1705.

[0106] Only a single HARQ-ACK codebook is required to be mapped on PUSCH. In the case where M=1, encoding, rate matching, and modulation are required. The URLLC UCI vector is split into both eMBB PUSCH hops. It can be mapped. Figure 18 shows UCI0 divided and mapped on the PUSCH hop. An example 1800 is shown. This configuration is used when the delay from the later hop is acceptable. It can be used. The UE is specific to each PUSCH hop, or (to limit the delay) UCI for hops only m It can be configured to support mapping. Figure 18 shows PDCCH1801, gap 1802 in slot 1810 for frequency 1811 This shows the results for PDSCH0 and PDSCH1. As can be seen in the example in Figure 18, UCI01083, which includes the coded ACK-NACK portion 1807, is PUSCH It can be transmitted at hop 1 of 1804. Encoding for PDSCH0 and PDSCH1 UCI01806, including the remaining part of ACK-NACK 1808, is PUSC It can be transmitted at hop 2 of H1805.

[0107] If UE has only one instance of UCI (M=1), then as shown in Figure 18. Therefore, the UCI can be divided and mapped to both hops. However, it is the UCI If you need to transmit an instance of M>1, then as shown in Figure 17, use UCI Instead of hopping, instances can be mapped. Alternatively, URLLC UCI can be transmitted over eMBB PUSCH resources, while eMBB data can be transmitted Not sent, that is, only URLLC UCI can access those resources. It is transmitted over the SCH.

[0108] Figure 19 shows an exemplary procedure 1900 for mapping UCI0. In example 19, UCI0 maps to multiple hops when M=1 (example in Figure 18). It is possible. If M > 1, each instance of UCI corresponds to the hop (example in Figure 17). It can be multiplexed internally. When the procedure starts (step 1901), the UE is slot The value of M for #i (the number of UCI instances to map) can be determined. (Step 1902). Next, UE can determine whether M is greater than 1 ( (Step 1903). If M is greater than 1, UE is UCI m Top Hop #m It may be possible to ping (step 1904). If M is 1 or less, UE is H PUSCH The UCI corresponding to each hop is divided, and a portion of the UCI is mapped on each push hop. Obtain (step 1905). Then the procedure may terminate (step 1906).

[0109] Figure 20A shows UCI on PUSCH, which is multiplexed with PUSCH resources. m H about An exemplary mapping of ARQ-ACK and CSI is shown in Figure 2000. An example in Figure 20A is M UCI on PUSCH for =2 m The mapping is shown in Figure 20A. PDCCH2 001, Gap 2002, PUSCH2007, OFDM symbol #3DMRS200 3. OFDM symbol #11DMRS2004, CSI2009, and HARQ AC This indicates K2008. UCI m This can be mapped in the time domain as follows: Modulated HA RQ-ACK symbols can be mapped near DMRS. For example, they are On the first available non-DMRS symbol after a set of adjacent DMRS symbols It can be initiated. For PUSCH with Type A DMRS, the mapping is to the DMRS. It may start from a preceding symbol if that symbol is available. Modulated CSI The symbol can be started and mapped on the first available non-DMRS symbol.

[0110] In the frequency domain, UCI m The modulation symbol is determined as follows between consecutive REs The distribution method at distance d can be mapped to the RE of symbol i. (1) d=1, the initial mapping of the OFDM symbol i to its UCI The number of non-modulated symbols may be greater than or equal to the number of available REs in this OFDM symbol. In this case, the HARQ-ACK of UCI12006 in Figure 20A shows the mapping for d=1. It indicates a 'g'.

[0111] (2) d = floor (number of available REs on the i-th OFDM symbol / OFDM symbol (Number of unmapped modulation symbols for the initial UCI of the 'nvol i') Figure 2 The HARQ-ACK in UCI02005 at 0A shows the mapping for d>1. This makes it possible to maximize the allocation of frequency resources to take advantage of frequency diversity.

[0112] UCI can be mapped to all layers of the transport block on PUSCH.

[0113] Figure 20B shows the UCI on PUSCH only. m Exemplary map Figure 20B shows PDCCH2020, Gap 2021, OFDM symbol # 3DMRS2022, OFDM symbol #11DMRS2023, UCI02024, This refers to UCI12025. UCI is transmitted only over PUSCH resources. For example, UCI for multiple URLLC PDSCHs is one eMBB P It can be transmitted separately via resources about USCH. URLLC about UCI If the required resources exceed a certain threshold, eMBB PUSCH may be shut down. RE can be used fully for UCI. UCI02024 and UCI1202 The number of symbols for 5 is how the beta offset is configured for each UCI It can vary depending on how it is done.

[0114] For eMBB PUSCH transporting multiple instances of UCI, sufficient DMR If the S symbol does not exist, all instances of UCI will map to DMRS next. It is not possible to map it. Then, U is mapped away from the DMRS symbol. There may be performance loss related to CI. This can be handled in the following ways:

[0115] Figure 21A shows the HARQ-ACK UCI mapping where there is no DMRS near UCI1. An example of source 2100 is shown. Figure 21A shows PDCCH2101, gap 2102, OF DM symbol #3 DMRS2104, PUSCH2106, OFDM symbol #3 21 03, OFDM symbol #8 2108, UCI02105, UCI12107, HAR Q ACK2109 and other UL signals 2110 are shown. Beta offset parameters The value of, for example, formula 13 below, may be for UCI instances that are not close to DMRS. It can be set to be sufficiently large. In the example in Figure 21A, PUSCH is the length of seven symbols This is possible, and only one DMRS symbol is composed. Here, UCI12107 is, Compared to UCI02105, it may be able to use more resources, but both have the same payload Transport the code. Additional resources for UCI12107 are available. This can help compensate for poor channel estimation quality. DMRS can help compensate for HARQ-ACK UCI If the next mapping position is not available, the UE will be beta off in the following equation 14. The set value can be increased. Here, equation 14 below shows that UE through RRC signaling It can be constructed as follows. UE uses factor 13 below instead of formula 14 below. The number of -s can be calculated. Therefore, >1 is an additional resource for UCI mapping. This can be provided to the UE.

[0116]

number

[0117]

number

[0118] Figure 21B shows HARQ-ACK U with additional DMRS introduced near UCI1. An example of a CI mapping resource is shown. Figure 20B shows PDCCH2120, gap 212 1. OFDM symbol #3DMRS2123, PUSCH2125, OFDM symbol # 3 2122, OFDM symbol #8 2127, UCI02124, UCI12126 This shows DMRS2128, HARQ ACK2130, and other UL signals 2129. UE is a DMRS symbol in the vicinity of UCI m It may be available for mapping To ensure this, the DMRS configuration for PUSCH is modified, as shown in Figure 21B. Thus, OS#3 consists of seven symbols PUSCH with one DMRS. However, UE generates a PUSCH of 7 symbol length with an additional DMRS in OS#7. And as a result, UCI1 can be mapped in the vicinity of additional DMRS symbols. E requires the piggybacked UCI in that sub-slot via RRC signaling. Where necessary, it may be expected that additional positions regarding DMRS will be included.

[0119] Lower-priority UCIs can be piggybacked on higher-priority PUSCHs. If the beta offset value can be equal to 0, U can be piggybacked on PUSCH. There is no CI. A value less than 1 is some for low-priority UCI on high-priority PUSCH. It may be supported to enable piggyback resources.

[0120] UE is in slot #3 in the manner shown in Figures 22A-22B, UCI eMBBand UCI U RLLC Both can be transmitted. Figure 22A shows UCI eMBB UCI URLLC Preceding The UCI will be piggybacked to PUSCH. URLLC and UCI eMBB Example 2200 Figure 22A shows PDCCH2201, other UL signals 2202, DMRS2210, HARQ ACK UCI2260 and gap 2208 are shown. Figure 22A also shows Slot #0 2212, Slot #1 2213, Slot #2 2214, and Slot #3 22 has sub-slot 0 2206 and sub-slot 1 2207. Shows 15. In some scenarios, the UE uses URLLC and eMBB during the slot. It may be possible to have HARQ-ACKs for transmission for both. In the example in Figure 22A, eMBB PDSCH02202 and PDSCH12203 are S It may be scheduled in lot #0 2212 and slot #1 2213, UCI eM BB HARQ-ACK report 2210 is scheduled for slot #3 2215. This is possible. URLLC PDSCH22204 and URLLC PDSCH32205 It may be scheduled for UE in slot #3 2215, UCI URLLC twenty two The 09 HARQ-ACK report is also scheduled for slot #3 2215. Obtain. UE has PUSCH2212 scheduled in slot #3 2215. Therefore, in slot #3 2215, it is possible to piggyback on UCI on PUSCH. UE is in the first sub-slot 2206 of slot #3 2205, UCI eMBB2 210, and UCI in sub-slot 2207 after slot #3 2205 URLL C piggybacks on 2209. This can be possible when the latency requirement for URLLC is such that transmission at the end of slot # 3 2215 is allowed.

[0121] Figure 22B shows UCI URLLC piggybacking on PUSCH that precedes UCI eMBB and examples of UCI that is piggybacked URLLC and UCI<​​​​​​​​​​​​​​​​​​​​​​​​​​​​can be jouled. The UE schedules PUSCH2 at slot #3 2237 has 232, and thus can piggyback UCI on PUSCH2232 at slot #3 In FIG. 22B, the UE is UCI at the first sub-slot 22 of slot #3 2237 2228 URLLC 2230, and UCI at the sub-slot 223 after slot 2237 1 eMBB 2231. This enables URLLC UCI to be time-prioritized if the UE has the ability to process URLLC grants within a given time line

[0122] FIG. 22C shows an example of UCI URLLC and UCI eMBB piggybacked on a PUSCH mapped to the same sub-slot of the PUSCH UCI URLLC and UCI eM BB FIG. 22C shows slot 2248 including PDCCH2240, gap 2241, PUSCH22 43, OFDM symbol #3 2242, DMRS2245, OFDM symbol #11 2244, HARQ ACK UCI URLLC 2246, and HARQ ACK U CI eMBB 2247. In FIG. 22C, both UCI eMBB 2 247 and UCI URLLC 2246 can be mapped following the first DMRS of PUSCH2243 2245. UCI URLLC 2246 is first mapped and UCI eMBB 2247 can follow with the benefit of latency and resources provided by it to the next DMRS2245

[0123] ​​​ Figure 22D is UCI URLLC Resources are first mapped to UCI eMBB But later The UCI then piggybacks on Push. URLLC and UCI eMBB Here is an example. Figure 22D shows PDCCH2250, Gatcha 2251, PUSCH2255, OFDM. Mbol #3 2252, DMRS2256, OFDM symbol #11 2254, HAR Q ACK UCI URLLC 2257, and HARQ ACK UCI eMBB twenty two This shows slot 2259, which includes 58. UCI URLLC 2257 is next to DMRS2256 If all resources are occupied on the symbol, UCI eMBB 2258 is shown in Figure 22D As shown in the example, it can be mapped with the following symbols.

[0124] Joint transmission of UCI with multiple priorities is described herein. UE has multiple priorities It can support joint transmission of multiple UCIs, i.e., the UE can support multiple priority HAs. The RQ ACK bits are jointly encoded and transmitted. The UE then performs the necessary operations on the PUSCH. When transmitting UCI, UE beta-off the highest priority HARQ-ACK in UCI. Applying set values ​​is proposed herein. Higher priority UCI beta off The set value provides the UCI with more resources on PUSCH, and therefore, higher Considering that a lower priority can provide higher reliability, a lower priority HARQ- ACK can also receive higher reliability.

[0125] UE is B low thresh In this case, priority level p low ​B low H The ARQ-ACK bit is set to priority level p high B high HARQ-ACK bit It can be duplicated. Here, B thresh This is a threshold that can be determined by one of the following methods. It is possible. (1)B thresh It is configured in UE by gNB through RRC signaling. obtain.

[0126] (2)B thresh Blow and B high It can be a function of B. l ow / B high <= There are cases where V is configured in UE by gNB. It can be a constant or a parameter.

[0127] (3)B thresh It can be a function of the beta offset value. For example, beta off The set value can correspond to the highest priority level that is multiplexed in UCI.

[0128] (4)B thresh This is the beta offset value, B low and B high It is a function of It is possible. For example, for a beta offset of 1, B low / B high <=V1, BetaO Regarding set 2, B low / B high <=V2 etc. Here, V1, V2 etc. This can be a constant or parameter configured in the UE by the gNB.

[0129] UCI mapping involving iterations of the HARQ process is described herein. High priority For each PUSCH, the gNB can schedule iterations. One UL grant For reliability reasons, two or more transmissions of the same HARQ process may be scheduled. Multiple transmissions in the RQ process may be within a single slot or available consecutively. It can be between slot boundaries in a slot. If the repetition is in a different slot, It may have different start symbols and / or time lengths. Each PUSCH transmission is a PUSCH transmission. These can be referred to as segments. Each PUSCH segment may have a different number of resources. UCI is such a repeating or segment as shown in some examples in Figures 23A-23B It can be mapped on the URLLC. Here, the label rep represents a repetition. Both eMBB UCI and PUSCH are piggybacked on PUSCH through the methods discussed below. It is possible.

[0130] Figure 23A shows the iteration of PUSCH in a minislot with UCI partitioning between iterations. An example of the iteration of the associated HARQ process, 2300, is shown. Figure 23A shows PDCCH2301 Slot 23, including gap 2302, PUSCH2303, and DMRS2306 This indicates 08. In the example in Figure 23A, the PUSCH repetition occurs within the slot, and PUSCH0 2304 and 2305 may be transmitted twice in the minislot, UCI modulation symbol 23 07 (HARQ-ACK in this example) is split into two and each mini-slot is mapped It may be punctured. In this case, rate matching or puncturing in a single iteration The amount of this can be reduced, thereby limiting the performance loss of a given push transmission.

[0131] Figure 23B shows multiple segment transmissions between slot boundaries with UCI partitioning between repetitions. An example of iteration of the HARQ process with the following is shown. Figure 23B shows PDCCH2310, gear P2311, other UL signals 2312, PUSCH2316, and DMRS2317 This includes slot #0 2318 and slot #1 2319. In the example in Figure 23B, Repeats may occur between slots, and each transmission within a repeat may have a different time length and start time. It has the OFDM symbol. PUSCH02313 and 2314 are located between two slots. It can be transmitted multiple times. UCI2315 is divided into two and each of the PUSCH segments It can be added.

[0132] Figure 23C shows a minislot with frequency hopping with UCI splitting between iterations. An example of HARQ process iteration is shown. Figure 23C shows PDCCH2320, gap 2 321, PUSCH2322 and 2330, and DMRS2323 and 2329 This shows slot #0 2325 related to frequency 2331, including P USCH repetitions 2326 and 2327 occur within slot 2325, but each repetition It has 2321 different frequency hops that provide frequency diversity to the transmission. Here again The UCI2324 can be divided into two parts, each part on one PUSCH transmission. It can be added.

[0133] Figure 23D shows multiple segment transmissions with hopping accompanied by UCI splitting between repetitions. An example of the HARQ process iteration is shown. Figure 23D shows PDCCH2340, gap 2341, other UL signals 2342, PUSCH 2347 and 2350, and DMR Slot #0 2345 and related to frequency 2353, including S2342 and 2349 This shows slot #1 2352. In the example in Figure 23D, the PUSCH segment is slot Between the transmissions, each transmission in repetitions 2346 and 2348 of the PUSCH sequence has a different time length. and has an initiating OFDM symbol. Here again, UCI2344 is divided into two parts. Each segment can be divided and each part can benefit from the diversity of frequencies 2353. It can be mapped to a ment.

[0134] UCI encoding between repeating minislots or repeating segments and The division of modulated symbols can be performed in the following ways:

[0135] Modulated UCI symbols are co-generated between repetitions, and resources are allocated in each repetition. It can be divided according to the amount of s. This results in less performance loss from rate matching. This ensures that the PUSCH performance for iterations with resources is not affected. For example, in Figures 23B and 23D, the first PUSCH segment could be 7OS. On the other hand, the second segment may consist of only 5OS and have fewer resources than the first segment. In this case, UCI maps each segment in proportion to the resources in that segment. It is possible.

[0136] A single DCI can schedule repetitions / segments. It's R PUSC Beta offset used for UCI mapping across sets of H repeats / segments This may indicate a set. The beta offset is between R PUSCH repetitions or R segments. This can be applied to the total number of available resources, expressed as formula 15 below, HARQ-A The number of coded modulation symbols per layer for CK transmission is given by R, as shown in Equation 1. This can be determined based on the total number of PUSCH resources available between repetitions / segments. (See formula 16 below).

[0137]

number

[0138]

number

[0139] Here, The following equation 17 can represent the number of HARQ-ACK bits. If equation 18 is true, then equation 19 is true; otherwise, equation 20 is true. This could be the number of CRC bits for HARQ-ACK (see formula 21 below). The following equation 22 is the code block for UL-SCH in PUSCH transmission. It can be a number. The DCI format for scheduling push transmissions is used when the UE is the rth co If it includes a CBGTI field indicating that a code block may not be transmitted, K r = 0, otherwise K r This is the rth co for UL-SCH of PUSCH transmission. It could be block-sized. The following equation 23 represents the number of subcarriers in a PUSCH transmission schedule. It could be a ripped bandwidth. The following equation 24 shows the OFDM symbol l that carries PTRS in PUSCH transmission. This could be the number of subcarriers. The following equation 25 is for repeated PUSCH transmission of rep and the following equation 26 The OFDM symbol l can be the number of resource elements that can be used for UCI transmission, below Formula 27 shown below contains all OFDM symbols used for DMRS in PUSC. This could be the total number of OFDM symbols in H. For any OFDM symbol that carries PUSCH's DMRS, the following formula applies: The number is 28. For any OFDM symbol that does not carry PUSCH's DMRS, the following number Equation 29 = Equation 30 below - Equation 31 below. α can be constructed by scaling the parameters of higher layers. The following equation 32 shows the first DMRS signal in the PUSCH transmission of replication rep. The first OFDM symbol that does not carry PUSCH's DMRS after VOL(or multiple) It could be a Volindex. α can be configured separately for each priority level. For URLLC, more A higher alpha value may provide more resources for UCI. The symbols in the following formula 33 are generated based on the PUSCH resource in each iteration. It can be split between returns. Formula 34 below maps to the PUSCH iteration "rep". This can be the number of modulation symbols, and can be given by Equation 2 (Equation 35 below).

[0140]

number

[0141]

number

[0142]

number

[0143]

number

[0144]

number

[0145]

number

[0146]

number

[0147]

number

[0148]

number

[0149]

number

[0150]

number

[0151]

number

[0152]

number

[0153]

number

[0154]

number

[0155]

number

[0156]

number

[0157]

number

[0158]

number

[0159] Figure 24A shows how each segment is mapped proportionally to the PUSCH resource, and iteratively... Between them, the modulated UCI symbols between repetitions have jointly generated UCI symbols. An example procedure 2400 for division is shown. UCI can be encoded (step (P2401), then using beta offset 2403, rate matching is performed, R It is executed repeatedly with a set of PUSCH resources based on the total PUSCH resources ( Step 2402). The UCI is modulated (Step 2404), and then the UCI R UC It can be divided into I segments, UCI segments rep The length is PUSCH rep Riso It is proportional to the number of -s (step 2405). Next, UCI segment rep PUS CH repIt can be mapped to (step 2406).

[0160] The UCI modulation symbol in equation 36 below can be generated as described in equation 1, and in equation 3. As shown, the PUSCH can be divided almost equally between repeats or segments. Figure 23A The example in ~23D shows an equal distribution of UCI resources between two iterations (see formula below). 37).

[0161]

number

[0162]

number

[0163] Figure 24B shows that the PUSCH segments are mapped almost equally between iterations. To split modulated UCI symbols between repetitions that have jointly generated UCI symbols An example procedure is shown below. UCI can be encoded (step 2411), next Then, using a beta offset of 2413, rate matching is performed, R repeated PUSC Executed based on the total PUSCH resources with a set of H resources (step 2412) The UCI is modulated (step 2414), and then the UCI is in the R UCI segment. They can be divided equally (step 2415). Then, the UCI segment rep , PU SCH rep It can be mapped to (step 2416).

[0164] The modulation symbol in the following equation 38 of the UCI is, as shown in equation 4, for each PUSCH repetition Each can be generated separately, based on the beta offset value for that PUSCH. It can be mapped to a repeat / segment. Here, formula 39 below is PUSCH's This could be the beta offset value for each iteration.

[0165]

number

[0166]

number

[0167] Figure 24C shows the modulation with separately generated UCI modulation symbols for each repetition. An exemplary procedure for splitting UCI symbols is shown. UCI is encoded (Step 2421), then use the beta offset 2423 for rate matching. PUSCH rep This is performed (step 2422). The UCI is modulated. (Step 2423), then UCI segment rep PUSCH rep ni Mappi It can be done (step 2424) (formula 40 below).

[0168]

number

[0169] Alternatively, UCI is not split between repetitions, but rather PUSCH repetitions. It can be perfectly mapped to one of the following. A repetition that can carry the UCI is that UCI This may overlap with the corresponding PUCCH. The start of the return may coincide with the end of PUCCH, or the end of PUCCH may coincide with the end of the PUCCH iteration. It is possible. In this case, UE maps UCI to that particular iteration of PUSCH. Figures 25A-25D show how to drop UCI by piggybacking it on PUSCH. This provides an example in which a possible PUCCH transmission is shown together with PUSCH.

[0170] Figure 25A shows how to map UCI to PUSCH with minimal delay via PUSCH iteration. An example of UCI transmission 2500 is shown. Figure 25A shows PDCCH2501, gap 250 2. DMRS2504, PUSCH2503, and HARQ ACK UCI0250 Slot #0 2509 shows mini-slots 2506 and 2507, including 5. In the example in Figure 25A, the starting position of 12-OS PUCCH2508 is PUSCH250 3 can be aligned to the starting position of the first transmission. As a result, the UCI2505 can be aligned to its mini-throttle The 2506 can be piggybacked, and the PUCCH2508 can be dropped.

[0171] Figure 25B maps UCI to PUSCH, aligned with the end of the PUSCH segment. This shows an example of UCI transmission via PUSCH repetition. Figure 25B shows PDCCH251 0, Gap 2511, DMRS 2513, PUSCH 2512, and HARQ AC Slot # featuring mini-slots 2515 and 2516, including K UCI02514 This indicates 0 2518. In the example in Figure 25B, the end of 8-OS PUCCH2517 is PUS It can be aligned with the end of the second segment of CH2512. As a result, UCI2514 is the It can be piggybacked onto two segments, and PUCCH2517 can be dropped.

[0172] Figure 25C shows the UCI marking the first PUSCH aligned with the end of the PUSCH segment. An example of UCI transmission via pinging PUSCH repetitions is shown. Figure 25C shows PDCCH 2520, Gap 2521, DMRS2522, PUSCH2523, and HARQ Slots featuring mini-slots 2525 and 2526, including ACK UCI02524. This shows #0 2528. In the example in Figure 25C, the starting position of 4-OS PUCCH is P It is delayed from the start of the first mini-slot of USCH2525. However, UE has made it the first If it has the ability to map to the mini slot 2525, then do it, PUCCH2 527 could be shot down.

[0173] Figure 25D shows the PUSCH operation that maps UCI to PUSCH according to the capabilities of UE. An example of UCI transmission via a return signal is shown. Figure 25D shows PDCCH2530, gap 253 1. DMRS2532, PUSCH2533, and HARQ ACK UCI0253 Slot #0 2538 shows mini-slots 2535 and 2536, including 4. In the example in Figure 25D, PUCCH2537 could be the same as PUCCH in Figure 25C. However, UE experiences delays when processing piggybacked UCI2534. , it does not have the ability to map it to the first mini-slot 2535. Therefore, U E maps it on the repeating second mini-slot 2536 and PUCCH25 Number 37 could be dropped.

[0174] Figure 26 shows an example of transmission of PUSCH repetitions to different TRPs. Mini slots 2603 and 26, including PDCCH2601 and gap 2602. This shows slot 2605 with 04. In the case of multiple TRP operations, UE2603 is used for each rotation. The return or segment can be transmitted to a different TRP, i.e., DL RS or UL The spatial orientation or correspondence of a beam with QCL accompanied by RS is for each repeat / segment. They are different. In the example in Figure 26, PUSCH is in the minislot 2605. This can be repeated in T2603 and 2604. TRP02601 and TRP12602 Transmission to these two beams can be transmitted over beams B02604 and B12605, respectively.

[0175] Different Push repetitions can also hop in frequency, as shown in Figure 23C. Similarly, different segments of PUSCH transmission, such as the segments in Figures 23B and 23D The TRP can also be transmitted to different TRPs.

[0176] A solution for piggybacking the UCI on multiple TRP PUSCHs This will be discussed below. The UCI for each TRP is the target TRP and its associated UCI. It can be mapped to different repetitions / segments to receive each UCI. The HARQ ACK codebook is about HARQ PDSCH from its TRP. Q may contain only the ACK bit. For example, the first UCI may contain the ACK of the first PDSCH. Includes the / NACK bit(s). Repeats the first UCI and the first PUSCH. The components share spatial relationships. For example, the TCI state of the first PDSCH (or the first RS in the TCI state of a set of 1 PDSCH layers is the first PUSCH repeat / set It can be the same as RS in the spatial relations of the ligment. For example, UE is the T of the first PDSCH. RS in CI state to the spatial relationship of the first PUSCH repeat / segment This can be derived.

[0177] Alternatively, or furthermore, UE uses TRP for transmission in a specific spatial direction, UCI It may be configured to report those TTRs. In this case, the UCI codebook will report those TTRs. This may include only HARQ-ACK bits or CSI reports for P.

[0178] Figure 27A shows different TRPs in separate HARQ-ACK codebooks for each TRP. This example shows how to map UCI to target push iterations for 2700. Figure 27A shows PDCCH2701, Gap2702, DMRS2704, and PUSCH 2703, HARQ ACK UCI02705 (transmitted via beam B02709), and includes HARQ ACK UCI12706 (transmitted via beam B12710). Figure 27A shows an example of slot 2713, which includes mini-slots 2707 and 2708. So, UCI transmission is (beam B PUCCH (Transmitted via 2711) on PUCCH2711 If this occurs, the codebook for HARQ-ACK is UCI Total It is expressed as It may include bits for both TRP0 and TRP1. However, PUSCH2 When 703 is available for transmission to TRP0 and TRP1 respectively, the UE will use UCI Total The payload can be split into UCI02705 and UCI12706. Therefore, UCI02705 may include a HARQ-ACK bit for TRP0, UCI 12706 may contain bits for TRP1, UCI02705, and UCI1 2706 is encoded, modulated, and mapped to each repeat or segment. It can be done. In other words, different codebooks are piggybacked UCIs for each T It can be used to transmit to the RP.

[0179] In some cases, PDSCH repetition (from multiple TRPs) and (to multiple TRPs) Both push and repeating can be used. RRC corresponds to HARQ-ACK. To piggyback on the push, specific PDSCH repetitions and specific PU A beam / space correspondence can be established between SCH repetitions. In addition, the spatial relationship of different PUSCH repeats is RS in the TCI state of PDSCH repeats. It can be composed as (plural), or alternatively or additionally, from RS(plural) It can be derived. For example, the first PUSCH repeating spatial relation is the first PDSCH repeating PDSCH and PUSCH iterations are used so that the return TCI state can be equivalent to the above. There is a continuous correspondence between them. For example, R in the first PUSCH repeating space relation. S is RS in the TCI state of the first PDSCH repeat, for example, QCL type D (space R PDS is equivalent to RS in a TCI state with QCL (QCL related to x parameter), A continuous correspondence between CH repeats and PUSCH repeats is possible.

[0180] Figure 27B shows the different UCIs, which have a common codebook that is repeated for each TRP. This example shows how to map UCI to target push iterations for TRP. Figure 27B shows PDCCH2711, Gap2712, DMRS2714, and PUSCH 2713, HARQ ACK UCI02715 (transmitted via beam B02719), and includes HARQ ACK UCI12716 (transmitted via beam B12720). Figure 27B shows an example of slot 2723, which includes mini-slots 2717 and 2718. So, another solution for piggybacking UCI on multiple TRP PUSCHs? n is shown, and here, (beam B PUCCH (Transmitted via 2722) PUCCH2721 UCI Total However, in each of the PUSCH mini slots 2717 and 2718 It can be coded, modulated, and repeated. Therefore, each TRP receives the entire UCI. Then, only the relevant HARQ-ACK bits can be selected. Alternatively or further, TRP communicates through backhaul and uses multiple TRPs to improve robustness. CI Total This could enable the joining of these elements.

[0181] The beta offset is applied to each beam (which may depend on channel conditions in different spatial directions). To enable different levels of protection, separate push repetitions are used for different push repetitions. It can be configured as follows. Therefore, the number of resources is within the replication set, for each PUSCH The above may differ regarding the UCI.

[0182] PUSCH iterations for CG or dynamic grants are described herein. G PUSCH is used in multiple TRP operations, or in a given HARQ process. When dynamic grants are used to provide PUSCH resources to multiple TRPs, The following configurations are possible.

[0183] Figure 28A shows the PU with a scheduling request indicator (SRI) cycle. An example of SCH repeat 2800 is shown. Figure 28A shows PDCCH2801, gap 280 2. SRI12803, SRI22804, SRI32806, and SRI42807 Slots 2810 and 2811 are shown, including the example in Figure 28A. The example in Figure 28A shows CG or dynamic Each iteration within the set of 2805 iterations in the grant is a different SRI (e.g., SR I2803, SRI2804, SRI2806, and SRI2807), TCI status, Furthermore / or it may correspond to a precoder, and as a result the UE may be in different spatial directions (different Each push can be transmitted within a repeating sequence (in TRP). Therefore, the UE can transmit different SRIs. , TCI state, and / or repeat through the precoder to complete the repeating set It is possible. In the example in Figure 28A, SRI for repetition (e.g., SRI2803, SR) I2804, SRI2806, and SRI2807), TCI status, and / or P The recorder (at least for Type 1CG, and possibly for Type 2CG) (and) can be configured about UE through RRC. Alternatively, SRI about repetition. , TCI status, and / or precoder are enabled for type 2CG through DCI It can be signaled.

[0184] Figure 28B shows an example of a PUSCH iteration where SRI is fixed to a time resource. Figure 2 8B consists of PDCCH2820, Gap 2821, Other Signals 2822, SRI22823 Slots 2827 and 2828, including SRI32825 and SRI42826. This shows the SRI and TCI for transmission in repeat set 2824 in the example in Figure 28B. The state and / or precoder may be tied to the grant's time resources. Therefore, depending on when the UE starts its CG transmission, as shown in the example in Figure 28B, It can start with different SRI, TCI states, and / or precoders. Here, UE It may be possible to transmit PUSCH only three times within the repeat set 2824, Transmission 1 begins in the second half of the slot. However, SRI is (symbol or minis (This may relate to lots or slots) and may be tied to the transmission time, therefore, 1 The transmission will use SRI22823.

[0185] Figure 28C shows an example of a Push repeat with SRI as a function of repeat analysis. Figure 28C shows PDCCH2830, gap 2831, other signals 2832, and SRI1. Slots 2837 and 2833, SRI22835, and SRI32836 are included. Figure 28C shows an example where SRI, TCI status, and / or P The recorder may be linked to the r-th transmission within repeat set 2834. Figure 28C In this example, the UE can transmit PUSCH only three times within a set of repetitions, and the first The transmission begins in the latter half of the slot. The first transmission may use the SRI12833. TRP is a multiple SRI, TCI status, and / or precoder at each iteration opportunity. The possibility can be monitored.

[0186] In some cases, the number of repetitions is different for the configured / shown SRI, TCI state. and / or may be greater than the number of precoders. In some cases, the UE first, Each different SRI, TCI state, and / or precoder can transmit one repetition. Subsequently, it may wrap around the first SRI, TCI state, and / or precoder Therefore, the following iterations will use different SRI, TCI states, and / or pre Coda can be used. Alternatively, UE can use the same SRI, TCI in several subsequent iterations. The state and / or precoder can be used, therefore all SRI, TCI states, And / or a precoder may be used between repetitions, but without wraparound. It can be used.

[0187] Different SRI, TCI states, and / or precoders in CG with PUSCH HAR As an alternative to transmitting Q process iterations, the UE has multiple CGs configured therein Obtained. Here, each CG corresponds to one SRI, TCI state, and / or precoder. Therefore, the repetitions within the CG are the same SRI, TCI state, and / or pleco Use a CG. For Type 1, and possibly Type 2 CG, multiple CGs are, It can be constructed through RRC. Here, each CG has a different SRI, TCI state, and / or have a precoder. All except SRI, TCI status, and / or precoder. The parameters may be the same for these CGs. Therefore, DMRS is this These CGs may be the same. Spatial direction can distinguish one CG from another. Alternatively, DMRS may differ for each CG. For Type 2 CG, SRI, The TCI status and / or precoder may be indicated through the enabled DCI. It is generally configured through RRC (thereby reducing configuration overhead), and A single DCI can be enabled and disabled collectively, and a single configured Grant Group It can be combined with P.

[0188] Supporting early termination of PUSCH transmissions within a repeating set may be beneficial. This applies to both configured grants and dynamically scheduled grants. If the TRP correctly decodes the PUSCH, the UE will get the rest of that PUSCH. There is no need to transmit the repetition to other TRPs. Therefore, the TRP does not need to transmit the early termination indicator (E The TI can be provided to the UE, and the remaining iterations can be terminated. This results in a better spec. This could enable better utilization of the void, less interference, and reduced power consumption for the UE.

[0189] Figures 29A-29H present examples of PUSCH iterations in multiple TRP scenarios. Provided. Figure 29A shows PDCCH2901, gap 2902, S directed towards TRP1. RI12903, SRI22904 directed towards TRP2, SRI22904 directed towards TRP3 Slot 2908 includes 32906 and SRI42907 directed towards TRP4. This refers to 2909. In the example in Figure 29A, UE is set 29, which is a set of 4 PUSCH iterations. It has 05. Here, each PUSCH transmission has 4 TRPs, namely TRP1, TR It is directed towards P2, TRP3, and TRP4.

[0190] Figure 29B shows SRI1 directed towards PDCCH2910, gap 2911, and TRP1. 2912, SRI22913 directed to TRP2, terminated SR directed to TRP3 Slots including I32918 and the terminated SRI42919 directed to TRP4. Figures 29B show repeating sets 291. In step 4, the first transmission 2903 of PUSCH is successfully decoded, and the next slot in the repeating set Then, on the PDCCH, ETI2915 is sent to the UE via DCI. The UE then... Identify the end and repeat the third and fourth transmissions in set 2917 (directed to TRP3) The terminated SRI32918 and the terminated SRI42919 directed to TRP4 Cancel.

[0191] Figure 29C shows SRI1 directed towards PDCCH2930, Gap 2931, and TRP1. 2935, SRI directed to TRP2; 22936, terminated SR directed to TRP3. I32940, the terminated SRI42941 directed towards TRP4, and UCI2933 This shows slots 2942 and 2943, including the example in Figure 29C, where UE is PUSC. If UCI2933 must be transmitted simultaneously with H transmission repeat set 2932, UCI2933 can be piggybacked on PUSCH. Early termination of PUSCH transmission Cancel part of it (as indicated to the UE on PDCCH by ETI2937) ) In this case, UCI2933 is only on PUSCH during repeated set 2939 In form, those PUSCH resources (terminated SRI32940 directed to TRP3, And it can be transmitted over the terminated SRI42941 directed to TRP4.

[0192] Figure 29D shows SRI1 directed towards PDCCH2950, ​​Gap 2951, and TRP1. 2952, SRI22953 directed to TRP2, SRI329 directed to TRP3 Slot 2959, including 57 and the terminated SRI42958 directed to TRP4. And 2960 is shown. In the example in Figure 29D, ETI2946DCI is repeated set 2 If a TRP is a UE on a PDCCH that has received at least one transmission from 954, DCI can be a form of override grant for another HARQ process. The UE can identify the ID of the TRP transmitting the ETI DCI, and the new grant is the same as the previous one. Prioritizing the possibility of the previous grant ending earlier, as decided in 2946. This is possible. Here, the UE receives a duplicate grant for HARQ ID#1. HARQ ID#0 terminates at 2956. Therefore, the override grant is Implicitly terminate the loop.

[0193] DCI carrying ETI can be transmitted in the following ways: (1) ETI DCI may be UE-specific, and may be UE's C-RNTI or CS-RNT It could be scrambled in I.

[0194] (2) ETI DCI is common to the group, and scrambling is done with ETI-RNTI. It can be rejected. UE can be composed of ETI-RNTI through RRC signaling. D CI may indicate a UE-ID to which early termination may be applicable. Alternatively, ETI DCI is This can occur in the form of a loop-common UL preemption marking PDCCH. Here, UE is It is preempted from transmissions on specific resources.

[0195] (3) The UE provides the ACK to the UE on one or more HARQs being processed. - The ETI can be implicitly identified from the DCI.

[0196] ETI DCI may provide the following information to the UE, either explicitly or implicitly: (1) The PUSCH HARQ process to be terminated, i.e., this is when ACK-DCI This can implicitly indicate whether or not an ACK will be issued for a given HARQ process.

[0197] (2) The number of iterations after which the PUSCH iteration may terminate. Non-ideal backhaul. Because conditions may exist, early termination does not have to occur immediately after receiving the ETI, but K times This may be desired after the iteration is complete. This time allows TRP to complete its HARQ process. This makes it possible to communicate the ACK status.

[0198] Figure 29E shows SRI1 directed towards PDCCH2961, Gap 2962, and TRP1. 2963, SRI22964 directed to TRP2, and SRI329 directed to TRP3. Slot 2971, including 68 and the terminated SRI42969 directed to TRP4. And 2972 ​​is shown. In the example in Figure 29E, ETI2970 is repeated set 2965 or If the UE receives the ETI on at least one of the PDCCH transmissions, the UE transmits the ETI. The ID of the TRP can be identified, and it is determined that HARQ ID#0 is ending 2966 297 It can be 0.

[0199] Figure 29F shows SRI1 directed towards PDCCH2973, Gap 2974, and TRP1. 2975, SRI22976 directed to TRP2, modified S directed to TRP3 Slots including RI32979 and the modified SRI42980 directed towards TRP4 Figures 2982 and 2983 are shown. In the example in Figure 29F, the ETI to UE on PDCCH is shown. 2981DCI can fix the PUSCH grant for the remaining 2978 iterations. For example, TRP1 receives the first PUSCH transmission of HARQ ID#0, and CBG1 If one is NACK, while another CBG is observed to be ACK, then ETI298 1DCI indicates that the UE needs to transmit only CBG1 from the r-th repeat. It is possible. Figure 29F shows that the third and fourth transmissions exhibit a NACK on CBG1. When receiving 81, indicate that UE2981 will correct 2979 and 2980. .

[0200] Figure 29G shows SRI1 directed towards PDCCH2984, Gap 2985, and TRP1. 2986, SRI22987 directed to TRP2, and SRI329 directed to TRP3. Slot 2994, including 91 and the terminated SRI42992 directed to TRP4. And 2995 is shown. In the example in Figure 29G, the timer-based early termination is directed toward TRP4. This is indicated by the terminated SRI42992. Alternatively, to support early termination... The gNB can configure the UE with a timer, an early termination timer. The UE is on the PDCCH. When ETI2933 is received, set timer 2988 and decrease it, or Reset the timer. When timer 2988 is reset or expires, the UE will respond accordingly. Terminates the remaining 2989 PUSCH repetitions for the HARQ ID. Timer The value may be constructed for the UE through RRC signaling, and for the backhaul between TRPs. This can be determined by gNB based on the UE's ability to respond to changes due to delay and ETI. .

[0201] Selective terminations are described herein. ETI may indicate a selective termination, i.e. (For example, if TRP1 and TRP3 have an ideal backhaul) a specific recurrence The return signal may be dropped. If TRP1 successfully decodes the first transmission, only the third transmission will be processed. Send an ETI to TRP3 to terminate. TRP1 will respond to PUSCH within the minimum delay. The ACK status is communicated to TRP3.

[0202] Figure 29H shows SRI1 directed towards PDCCH2996, Gap 2997, and TRP1. 2998, SRI22999 directed to TRP2, SRI329 directed to TRP3 Slots 2944 and 26, including SRI42927 directed towards TRP4. This indicates 945. SRI12998 is directed to TRP1, and SRI2 is directed to TRP2. 2999, SRI32926 directed to TRP3 is transmitted repeatedly during 2923. However, in the example in Figure 29H, TRP4 and TRP1 are non-dealback. It may have holes. As a result, the ACK from TRP1 is sent to TRP4 within an acceptable delay. No communication occurred (for example, HARQ ID#0 terminates at timer expiration 2925), TR It is desirable that P4 receive a PUSCH from the UE. ETI to the UE on PDCCH. 2922 terminates transmission to TRP3. As a result, UE terminates transmission to TRP3. Complete the process and perform the fourth push transmission to TRP4.

[0203] To enable this operation, a TRP group is composed of a specific TRP. The concept of a "loop" is introduced. gNB uses RRC signaling to connect multiple TRP groups. A UE can be formed by a group. A TRP group is a group with at least one other T It is expected that the TRP will have ideal backhaul conditions with respect to the RP. If TRP in the TRP group gives an affirmative response to the HARQ process, then the ideal backho The condition is expected to enable inter-TRP communication of ACKs within that TRP group. Therefore, UE transmits the iteration of its HARQ process to other TRPs in that group. The transmission can be terminated.

[0204] Figure 30 shows the TRP group when one TRP from the group responds negatively to transmission. Figure 30 shows an exemplary retransmission 3000 to the TRP. Figure 30 shows PDCCH3001, gap 3002, and during the transmitted repetition 3006, i.e., directed to TRP1 SRI13003, directed towards TRP2; SRI23004, directed towards TRP3. Slot 3014 includes I33008 and SRI43009 directed to TRP4. Figures 3015 and 3016 show that TRP is re-propagated in the TRP group. If delivery is required, the UE will send HARQ Pro to one or more TRPs within that group. Only retransmission of the signal is possible. TRP1 and TRP3 are in TRP group 1, but On the other hand, assume that TRP2 and TRP4 are in TRP group 2. UE is HAR Q ID#0 may have a UL grant for PUSCH repeats. TRP1 is P USCH detects ACK3005 for HARQ ID#0, while TRP2 This detects NACK3007 (TRP1 is explicitly or implicitly on PDCCH). UE may indicate ACK3005, and TRP2 explicitly or implicitly indicates U on PDCCH. E may indicate NACK3007). Dynamic grants for retransmission are based on the TRP. Retransmission 3011 to one or more TRPs in the loop (for example, directed to TRP2) SRI23012 and SRI43013 directed towards TRP4 can be scheduled. Alternatively, for CG, the UE will only re-attempt to TRP groups for which an ACK was not received. It can be transmitted. In this example, the UE is TRP2 3012 and within TRP group 2. / or HARQ ID#0 can only be retransmitted to TRP4 3013. UE is RRC The signaling mechanism is configured to retransmit signals to specific TRPs within the target TRP group. This can be achieved. This allows for signaling at DCI when scheduling retransmission. Barhead can be reduced.

[0205] Figures 31A-31B show example UE 3100, which identifies ACKs from all TRP groups. This indicates that the UE receives an ACK from at least one TRP within each TRP group. And, or the timer, until the ackTRP timer expires, the HAR for ID#0 You don't need to clear the Q buffer. This is because all target TRPs (or TRs) The P group receives an ACK status, and / or TRP (or TRP group) Transferring data and / or ACK status of recognized HARQ processes between (P) This is to ensure that there is sufficient time available.

[0206] Figure 31A shows PDCCH3101, gap 3102, and transmitted repeat 3 During 107, that is, SRI13103 directed to TRP1, and directed to TRP2 SRI23104, SRI33109 directed towards TRP3, and directed towards TRP4 Slots 3113 and 3114, including SRI43110, are shown. Figure 31A shows AC This shows an example where K is received from each TRP group. The UE is (for example, HARQ ID# ACK3105 from TRP1 for 0 and TRP for HARQ ID#0 ACK3106 from 2 on PDCCH) AC from TRP in TRP group Upon receiving K, the ackTRP timer 3108 may be set and begin to decrease. The UE then If ACKs are received from all other TRP groups before IMER 3108 expires, The HARQ buffer for ID#0 can be cleared.

[0207] Figure 31B shows PDCCH3120, gap 3121, and transmitted repeat 3 Between 126, that is, SRI13122 directed to TRP1, and directed to TRP2 SRI23123, SRI33129 directed to TRP3, and directed to TRP4 Figure 3 shows slots 3131, 3132, and 3133, including SRI43130. 1B provides an alternative example. (For example, AC from TRP1 for HARQ ID#0) (On the PDCCH receiving the K3124) All ACKs are T for HARQ ID#0 If the UE's ackTRP timer 3126 expires before it is received from the RP group, As shown in Figure 31B, the UE receives a NACK (e.g., HARQ) from another TRP group. Even when receiving a NACK3127 from TRP2 for ID#0, HARQ The buffer for ID#0 can be cleared 3134. This is because TRP is connected ACK status and / or PUSCH data are transmitted between connected TRPs or TRP groups. This is because it is expected that there will be sufficient time to believe.

[0208] ACK implicitly sends the UE to the TRP through a grant for the same HARQ ID. While this can be shown, please note that the NDI set represents a new transmission method.

[0209] In the example shown in Figures 31A-31B, the timer is the first for its HARQ process. It can be set upon receipt of ACK. Other alternatives presented herein also include setting a timer. This can be considered a starting point for determining the location.

[0210] The timer is triggered when the first transmission of a push occurs in a repeating set of its HARQ IDs. It can be set at times.

[0211] The timer is triggered when the last transmission from PUSCH occurs in a repeating set of its HARQ ID. It can be set at times.

[0212] The value for the ackTRP timer can be configured in the UE through RRC signaling. This can depend on delays in a less-than-ideal backhaul.

[0213] Prioritization within PUSCH's UE is described herein. Prioritization over dynamic grants. The prioritization of the configured grants is described herein. UE is a high-priority configuration. It may have a grant that has been made, but a low-priority PUSCH may conflict with the configured grant. You may receive a dynamic grant for this. In this case, the UE will provide the dynamic grant. Instead, it may simply transmit the configured grant. Alternatively or further, UE If capable, it can puncture the dynamic grant push and available resources Dynamic PUSCH can be transmitted over the system. The gNB monitors the DMRS of the configured grants. If it is possible and receives it, it will process the configured high-priority grant push. It is foreseeable.

[0214] Figures 32A to 32C show low-priority PUSCH grants and high-priority PUSCH grants. Figure 32A shows an example of a collision within the UE between frequencies 3200 and 3208. Slots 3207 and 3209 are shown, including CH3201 and gap 3202. In the example in Figure 32A, the UE receives dynamic data for eMBB PUSCH13204. CG PUSCH URLLC opportunity 3203 with grant and resource conflict 3206 It can be transmitted. Here, the UE is overloaded with PUSCH13210 in RE where there is a resource contention. I chatted.

[0215] Figure 32A shows PDCCH3211 and gap 3212 for frequency 3218. Includes slots 3217 and 3219. UE is eMBB PUSCH1321 CG PUSCH URLs with dynamic grants and resource contention received for 4 LC opportunity 3213 can be transmitted. In the alternative example in Figure 32B, the UE is eMBB3214 There are cases where it is not possible to process both and URLLC PUSCH3216 simultaneously. Therefore, cancel PUSCH13214.

[0216] Figure 32C shows PDCCH3220 and gap 3221 with respect to frequency 3229. Includes slots 3227 and 3228. UE is eMBB PUSCH1322 CG PUSCH URLs with dynamic grants and resource contention received for 4 LC opportunity 3222 can be transmitted. In an alternative example in Figure 32C, PUSCH13223 is, It can only be transmitted on symbols that do not overlap with CG PUSCH3223, i.e., PUS CH13224 can be punctured with symbols that overlap with CG PUSCH3225. .

[0217] Similar behavior occurs when high-priority dynamic UL grants are compared to low-priority dynamic UL grants. - Support may be available in cases where there are conflicts. This scenario is when gNB is low priority U It transmits an L grant, followed by a higher priority UL grant that will collide with a lower priority grant. This can occur when transmitting to the same UE. Alternatively, or further, in multiple TRP cases For example, one TRP may schedule a high-priority grant, while another TRP may... Low-priority UL grants that could result in resource contention can be scheduled in E.

[0218] Figure 33 shows that PUSCH URLLC and PUSCH eMBB have the same HARQ ID. An example 3300 is shown. Figure 33 shows PDCCH3301 for frequency 3308. This shows slots 3306 and 3307, including gap 3302. UE is CG PUSCH URLLC opportunity 3303 can transmit, UE HARQ-ID "H" 330 Receive a UL grant for PUSCH eMBB transmission having 5. UE also, Grant PUSCH configured with the same HARQ-ID URLLC Transmission 3304 In this case, the transmission buffer of the UE having ID H contains URLLC data. The UE recognizes that the RLLC HARQ transmission was not properly received by the gNB. In some cases, it is preferable not to pass this until then. In this case, the same HARQ ID If a dynamic grant for a lower-priority PUSCH is received, the UE The resource is PUSCH URLLC and PUSCH eMBB In cases where there is no conflict between them However, that low-priority grant can be ignored.

[0219] A URLLC PUSCH response may implicitly occur, i.e., the UE is a timer, constructor Before the grant timer expires, D indicates a higher priority (URLLC priority). CI does not receive a rescheduling for HARQ-ID H. Therefore, P USCH eMBB One of the following is PUSCH URLLC Following the transmission, the configured Gran If it occurs within the timer duration, UE will PUSCH eMBB All of Grant or Remove a portion of it.

[0220] If the PUSCH grants collide again in time, it is determined which PUSCH was transmitted. To enable NB to correctly identify the PUSCH, the priority level of the transmitted PUSCH is set. It may be desirable to indicate this. Here, the UE is the RNTI corresponding to its priority level. p The RNTI can be masked in that push transmission using [a specific method / tool].

[0221] If the gNB explicitly indicates a response to the CG, the UE will continue to do so until a response is received. It is not necessary to pass through the transmission buffer H. gNB is ambiguous in the HARQ ID collision event. This specification may indicate the priority of recognized PUSCH processes in order to avoid certain issues. This is proposed.

[0222] Figure 34 shows an example of collision 3400 in CG PUSCH's UE. The UE has different priorities. If it can consist of multiple configured grants of different degrees, the CG PU with lower priority will be used. SCH transmission can be initiated, but it will be preempted and a higher priority CG P will be used. It may be necessary to transmit USCH. Figure 34 shows PDCCH3 for frequency 3411. Slots 3408, 3409, and 3410, including 401 and gap 3402 As shown, the UE may transmit the CG PUSCH URLLC opportunity 3403. Alternative in Figure 34. In a typical example, the UE has two CGs, a low-priority PUSCH3404 called eMBB. This includes a device that has a high-priority PUSCH3403 called URLLC. This can be done. When the UE receives URLLC TB about the transmission via CG, eM BB PUSCH transmission 3405 can be initiated. Therefore, UE transmission is eMBB transmission 34 06 may be canceled or punctured, and URLLC PUSCH3407 may be transmitted. gNB can monitor DMRS for both CG PUSCH of both priority levels, URL It may be possible to detect that the LC CG PUSCH has punctured the eMBB CG PUSCH. gNB uses its soft buffer to handle the punctured parts of eMBB CG PUSCH. It can flow for minutes.

[0223] CGs with different priorities configure the grant timer duration of their respective configurations. It is proposed herein that different time lengths may be achieved. For low-priority transmission, P The USCH time length may be longer than that of high-priority transmission. Therefore, low-priority CG PU Having a longer time duration for the configured grant timer for SCH It may be desirable in some cases.

[0224] Figure 35A shows preemption within the UE when receiving a dynamic grant from the gNB. This shows an example of retransmission of a low-priority CG PUSCH, eMBB CG PUSCH. If it becomes punctured, the mode of operation will be that the gNB will retransmit it using CS-RNTI. This can make it possible to schedule dynamic grants. In the example in Figure 35A, UE3 502 transmits HARQ ID D3504 to gNB3501 in slot 3503. The configured grant timer starts at 3503. The configured grant timer expires. After 3506, UE3502 receives a dynamic grant 3507 about ID D. Next, UE3502 retransmits HARQ ID D3509 on the dynamic grant. However, in this case, the delay for retransmission may be high.

[0225] Figure 35B shows an example of retransmission as a CG PUSCH. In the example in Figure 35B, UE3 522 transmits HARQ ID D3524 to gNB3521 in slot 3526. The configured grant timer starts at 3523. In this alternative example, retransmission is configured It may occur before the expiration of the granted timer, and instead, the UE may use its own UR The PUSCH in slot 3528 is being overloaded by LLC traffic. Retransmission 3529. During retransmission, the UE restarts the configured grant timer 325 7. The UE will perform a dynamic gran about HARQ ID D3530 after CG retransmission. When receiving a signal, dynamic grants can be ignored.

[0226] Furthermore, retransmission may only include canceled or punctured CBGs. UE , all CBGs in low-priority pushes, or affected in low-priority pushes It may be an RRC configured to retransmit only CBGs. gNB is which CBG To recognize if the first transmission was affected, retransmissions can be properly soft-coupled. However Therefore, in retransmission, it is not necessary to show the transmitted CBGTI.

[0227] Prioritization within the UE between DL and UL is described herein. Conflicts can arise between DL transmission and UL transmission in the UE. The configuration is a format 2_0 glue that can be scrambled with SFI-RNTI. RRC is configured or can be indicated through DCI such as a common DCI. It can be represented as "X" in format. In the case of a conflict within the UE between DL and UL, the following scenario Rio could occur.

[0228] Figure 36A shows DL and UL collisions within the UE, low-priority PDSCH and high-priority PUS. Figure 3600 shows a CH collision. Figure 36A shows PDCCH3601 and another DL signal 3602. , and slot #0 3607, slot #1 3608, including gap 3606, Slot #2 3609 is shown. In the example in Figure 36A, one or more flexible singles Bol can use a grant (e.g., eMBB PDSCH3603) to access low-priority PDSCs. H can be scheduled. High priority UL grants are also among the same symbols It can be scheduled on one or more devices (e.g., URLLC PUSCH3605). In this case, the UE may interrupt the PDSCH3604 and transmit a PUSCH.

[0229] Figure 36B shows DL and UL collisions within the UE, low-priority PDSCH and high-priority PUC. This is a diagram of a CH collision. Figure 36B shows PDCCH3610, another DL signal 3611, and Slot #0 3617, Slot #1 3618, including Gap 3612, Slot #0 3617, Slot #1 3618, Slot #2 shows 3619. In the example in Figure 36B, one or more flexible symbols are Regarding low-priority PDSCHs via grants (e.g., eMBB PDSCH3614) It can be scheduled. High priority UL grants (e.g., UR on PUCCH3615) LLC UCI 3616) also states that its PUCCH is among the same flexible symbols It can be scheduled to be on one or more of the following. In this case, the UE is PDS CH3620 may be interrupted, and PUCCH3615 may be transmitted.

[0230] Figure 36C shows DL and UL collisions within the UE, low-priority PUSCH and high-priority PDS. This is a diagram of a CH collision. Figure 36C shows PDCCH3630, other DL signals 3631, and Slot #0 3636, Slot #1 3637, including Gap 3632, Slot #0 3636, Slot #1 3637, Slot #2 shows 3638. In the example in Figure 36C, one or more flexible symbols are Regarding low-priority pushers via grants (e.g., eMBB PUSCH3633) It can be scheduled as follows: High-priority DL grants (e.g., URLLC PDSCH36) 34) also, that PDSCH is on one or more of the same flexible symbols It can be scheduled as possible. In this case, the UE will interrupt PUSCH3635. Received PDSCH3634.

[0231] MAC layer prioritization and preemption for uplink transmission are described herein. Regarding UL transmission, the MAC layer of the UE has enough time to respond to the grant. In some cases, higher priority transmissions may be given priority. MAC transmission is a partial transmission of physical transmissions over time. A conflict can be considered to occur when there is a complete overlap. UE's MAC is a new conflict. Prioritize the transmission and / or preempt existing transmissions that have already reached the physical layer. It is possible.

[0232] If there is enough time to respond to available competing grants, MAC will MAC Before a Protocol Data Unit (PDU) reaches the physical layer, Prioritizing push transmissions is possible. One or more MAC PDUs reach the physical layer. Previously, if there wasn't enough time to prioritize a competing grant, MAC would have already given the physical layer The transmission of the MAC PDU provided may be preempted, or appropriate for each transmission Relative priority information can be provided to the physical layer for processing.

[0233] MAC also handles conflicting scheduling requests (SRs) and push transmissions. This may take precedence. Similar to competing PUSCH transmissions, the MAC procedure for SR transmissions... The process is affected by the minimum processing time and / or when notifying the physical layer of the transmission. Keru.

[0234] For configured or dynamic grants, UE will handle each individual grant accordingly. MAC PDU multiplexing and assembly can be delayed to the minimum processing time requirement. Similarly, MAC SR processing and transmission marking to the physical layer (for example, associated PU) It may be delayed (until CCH resources become available). Existing competing grants or SRs Before the minimum processing requirements for that are determined, new competing grants are determined, or competing grants are determined. If an SR is triggered, the UE may perform MAC transmission prioritization operations.

[0235] MAC transmission prioritization may include the following actions: MAC states that for each prominent grant, the first grant is responsible for each grant. Before processing needs to be done considering the minimum processing requirements, which logical channel each... It can be determined whether significant grants can be multiplexed to each PDU. Each logical channel is A logical channel that can consist of one or more priorities and is multiplexed into a MAC PDU. The highest priority selected can determine the transmission priority. MAC control element (CE) Priority may also be considered. Each MAC CE type (i.e., PHR, BSR, ...) ) may have known priorities used to determine the priority of PUSCH transmission. Example For example, the highest priority of the logical channels and MAC CEs multiplexed into the MAC PDU is This can be used to determine the PUSCH transmission priority. This operation is similar to that of existing MAC P DU multiplexing and assembly procedures can be effectively divided into two-step procedures. Existing Logical Channel Prioritization (LCP) When Rosilla multiplexes and assembles each MAC PDU for transmission, The priority of available data can be determined. In this procedure, priority of available data Before MAC PDU multiplexing and assembly and MAC CE generation begin This is determined in the first step.

[0236] Alternatively, priority is assigned to each configured grant and / or dynamic grant. It may be rejected. In this case, the priority of the logical channels multiplexed on the MAC PDU is taken into consideration. This is not necessary. Normal logical channel prioritization for data multiplexing can be performed. The PUSCH transmission priority can be determined by the grant. The available data for transmission and And / or the priority assigned to each grant, or multiplexed to each MAC PDU Priority associated with the logical channel, or priority of the logical channel that triggered the SR. Depending on the degree, MAC may determine the priority of each transmission and retransmission.

[0237] PUSCH transmission priority is also multiplexed within grant priority and MAC PDU. This can be determined by the combination of data priorities. For example, multiplexed data or graphs. The highest priority of the input can be used to determine the PUSCH transmission priority.

[0238] When transmission prioritization is applied, a lower priority grant(s) or SR(S) will be prioritized. Transmission may not be necessary, or additional information may be physically prioritized to appropriately prioritize transmission. It can be provided to layers. Grants can be used to provide data, for example, MAC service data. Multiple units (Service Data Unit: SDU) or MAC CEs to MAC PDUs Includes the reloading and assembly, and the transmission of its MAC PDU associated with the grant. This includes the transmission of SRs associated with grants. When grants are not available. , data multiplexing or assembly to the MAC PDU is not performed, and SR transmission is not performed. I can't.

[0239] If MAC determines that a grant will not be used due to transmission prioritization, This is because, in order to properly handle higher-priority transmissions that have not been canceled, the MAC This can notify the physical layer of transmissions that are to be canceled. Unused grants are gNB schedule It can be signaled to the Jurger directly or indirectly. For example, if it is not canceled Priority transmissions may provide transmission cancellation indicators.

[0240] When a lower priority transmission is not canceled by MAC, the MAC determines The relative priority assigned is provided to the physical layer along with each MAC PDU and / or SR transmission. It is possible. In addition to processing each transmission uniquely, some degree of indicating the relative priority of each transmission. Ensuring reliable information directly or indirectly signals to the gNB scheduler. It is possible.

[0241] How MAC transmission prioritization is determined (i.e., LCP or grant Regardless of the base, when a grant is not used due to prioritization, the MAC is lost. This procedure may allow the lost grant to be recovered. The configured SR resource is associated with the logical channel(s) provided by Therefore, by triggering SR and / or maintaining the SR pending state Therefore, this can be achieved. Buffer status reports are also generated as a result of lost grants. Obtain. When MAC determines that a grant may not be used, this action is performed by M It can be inside AC. When the physical layer decides that grants will not be used, MAC You may be notified that a procedure will be initiated to recover the lost grant.

[0242] After the minimum processing requirements for existing competing grants or competing SR transmissions, a new competition If a grant is determined or a conflicting SR is triggered, the UE will MAC Transmission preemption operation may be performed.

[0243] MAC transmission preemption operations may include the following: MAC is based on existing grants (i.e., grant or logical channel-based) or If a new grant or SR transmission is determined before the minimum grant processing time for an SR transmission, Transmission priority can be determined in the same way that priority is determined in other contexts.

[0244] New grant or SR transmissions have higher priority than existing grant or SR transmissions. If a decision is made, MAC will perform normal multiplexing and assembly of MAC PDUs. It may perform the following: MAC PDU and / or SR processing. When delivered to lower layers, preemption markings may be included. The markings may identify MAC PDU or SR transmissions that are being preempted.

[0245] When the physical layer detects a preemption indication, the preempted transmission is given priority. To ensure more reliable and correct transmission, the transmitted data is either discarded or adjusted (i.e., panned). (Cutting may occur.) If the transmission is dropped by the physical layer, the MAC may be notified. Regarding discarded MAC PDU transmissions, MAC will not attempt to recover the lost data. It can perform actions. For example, HARQ NACK can receive information about a cancelled transmission. If so, similar behavior may occur. The maximum number of HARQ retransmissions is when a transmission is canceled. It can be incremented to allow the same number of actual transmissions that would be permitted if it were not present. For abandoned SR transmissions, MAC cancels the SR pending state and / or S R can be re-triggered. If a MAC PDU containing MAC CE is discarded, MAC will Operation to recover and retransmit lost MAC CEs (i.e., BSR, PHR) This can be done. This re-triggers MAC CE and / or the associated prohibited This can be achieved by clearing the Immer.

[0246] When an existing transmission is preempted, a new preemption transmission is preempted. This may directly or indirectly provide indications to the gNB scheduler of the transmitted data. As a result, gNB will either reschedule the discarded transmission or assign it to a lower priority. This could result in the system behaving as if an SR (Signal Reception) signal had been received.

[0247] New Grant or SR transmission is inferior to existing MAC PDU or SR transmission. If it is determined that this is the priority, the MAC will not interrupt the current higher-priority transmission. To decide what to do, we may discard the new grant or SR transmission, or It provides relative priority information to the physical layer. MAC breaks new grant or SR transmissions. If discarded, MAC PDU multiplexing and assembly, and / or SR transmission processing The principle does not need to be executed. This operation effectively enables MAC PDU multiplexing and assembly. The yellowtail and SR processing are performed in a two-step process where prioritization is determined in the first step. This will enable Seeja. The cancellation may also be notified to the physical layer.

[0248] If physical layer preemption is applicable, the MAC layer will have the canceled transmission. Notification may be given. In this case, the MAC will cancel the transmission with the next available grant. The transmission can be resumed. This action is performed when HARQ is received for the canceled transmission. This can trigger a procedure similar to receiving a NAK. The maximum number of HARQ retransmissions is... To allow the same number of actual transmissions as would be permitted if the cancellation had not occurred. It can be incremented. The PHY performs grant preemption or grant prioritization. Examples of scenarios in which this might be practical include one or more of the following: . The physical layer can detect preemption indications from the MAC.

[0249] The MAC may instruct the PHY regarding transmissions with transmission priority. The PHY then communicates to the MAC. Therefore, transmission preemption can be performed based on the provided transmission priority.

[0250] MAC is a traffic control system for de-prioritized and / or preempted transmissions. The lock can be maintained. De-prioritized transmissions and / or preempted transmissions. If the number of failures exceeds a threshold, MAC will report the failure of lower-priority transmissions and take corrective action. The following actions can be performed: Thresholds for reduced-priority transmissions and / or preempted transmissions. When a value occurs for a logical channel or a specific grant, it more efficiently corrects transmission failures. To perform the necessary actions, higher priority levels may be notified. The actions performed are NBs Reporting status to the scheduler, and / or the relative priority of the grant's logical channel. It could be adjusted.

[0251] The Third Generation Partnership Project (3GPP) focuses on wireless access, core transformers, and more. Port network and service capabilities (codecs, security, and services) Technologies for cellular telecommunications network technology, including those that affect the quality of [the network]. They are developing the latest standards. The latest Wireless Access Technology (RAT) standards are (commonly referred to as 3G) Wideband CDMA (WCDMA®), and (generally 4G) This includes LTE (also known as LTE Advanced Standard) and LTE Advanced Standard. 3GPP also refers to it as "5G". They have begun working on standardizing the next-generation cellular technology called New Radio (NR). The GPP NR standard development includes defining next-generation wireless access technologies (new RATs). This is expected, and it will provide new flexible wireless access below 6GHz. This includes providing new ultra-mobile broadband wireless access beyond 6GHz, It is expected that flexible wireless access will be available in new frequencies below 6GHz. It is expected that the new non-backward compatible wireless access will be configured in the same spectrum. Within the framework, multiplexing occurs, and a wide range of 3GPP NR use cases with diverse requirements are met. It is expected to include different operating modes that can handle the issue. Roadband refers to ultra-mobile broadband access, for example, for indoor and outdoor use. It is expected that centimeter-wave and millimeter-wave spectra will be included, providing opportunities for hotspots. In particular, ultra-mobile broadband has a design specific to centimeter wave and millimeter wave. With optimization, a common design framework for flexible wireless activity below 6GHz It is expected to be shared with Seth.

[0252] 3GPP addresses various user experience requirements for data rate, latency, and mobility. This helps identify the various use cases that NR is expected to support. Use cases fall into the following general categories, namely, advanced mobile broadband (examples) For example, broadband access in densely populated areas, indoor ultra-high broadband access Seth, broadband access in crowded places, 50+Mbps everywhere, ultra-low cost Street broadband access, mobile broadband in vehicles, critical communications, large-scale Thin-type communication, network operations (e.g., network slicing, routing) (Transition and interworking, energy saving), and extended vehicle-to-everyday This includes SING (enhanced Vehicle-To-Everything: eV2X) communication, and eV2X communication is, Vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure Vehicle-to-Infrastructure (V2I) communication, Vehicle-to-Network (Veh Vehicle-to-Network (V2N) communication, Vehicle-to-Pedestrian (V2P) This may include any of the following: communications and vehicle communications with other entities. Specific services and applications in this category include, for example, a few examples. And, monitoring and sensor networks, device remote control, bidirectional remote control, personal Loud computing, video streaming, wireless cloud-based office, 1-person connectivity, car e-call, disaster warning, real-time games, multiplayer This includes Deocall, autonomous driving, augmented reality, haptic internet, and virtual reality. All of the use cases and others are discussed herein.

[0253] Figure 37A illustrates how the methods and apparatus described and claimed herein may be embodied. An embodiment of a typical communication system 100 is shown. As illustrated, an exemplary communication system 1 00 is a wireless transmission / receiving unit (which may be generally or collectively referred to as WTRU102) (WTRU) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g and Wireless Access Network (RAN) 103 / 104 / 105 / 1 03b / 104b / 105b, core network 106 / 107 / 109, and public exchange Public Switched Telephone Network (PSTN) 108 and Network 110, other network 112, and V2X server (or ProSe function) The disclosed embodiments may include, but any number of WTRUs, It will be understood that we will be considering base stations, networks, and / or network elements. WTRU102a, 102b, 102c, 102d, 102e, 102f, 102g Each of these is any type of device configured to operate and / or communicate in a wireless environment. or it may be a device. Each WTRU102a, 102b, 102c, 102d, 102 e, 102f, and 102g are depicted in Figures 37A to 37E as handheld wireless communication devices. However, with the various use cases being considered for 5G wireless communication, each WTRU will be... This is just one example, but it includes user terminals (UEs), mobile stations, and fixed or mobile subscribers. Knitwear, pagers, cellular phones, personal digital assistants (Personal Digital Assistants): PDA, smartphone, laptop, tablet, netbook, notebook computer Computers, personal computers, wireless sensors, mass consumer electronics, smartwatches Wearable devices such as smart clothing, medical or e-health devices, robots This includes industrial equipment, drones, and vehicles such as cars, trucks, trains, or airplanes. any type of device or device configured to transmit and / or receive wireless signals Please understand that devices may be available or can be embodied through them.

[0254] The communication system 100 may also include base station 114a and base station 114b. Station 114a communicates wirelessly with at least one of WTRU 102a, 102b, or 102c. Interface taken, core network 106 / 107 / 109, internet 1 10, and / or one or more communication networks such as 112 This could be any type of device configured to facilitate access to base station 1. 14b is a Remote Radio Head (RRH) 118a, 118b, TR P (transmit / receive points) 119a, 119b, and / or roadside units (Ro adside Unit (RSU) 120a and 120b, at least one of them, and wired and / Alternatively, take a wireless interface to core network 106 / 107 / 109, Network 110, other networks 112, and / or V2X servers (or ProSe function and server) Access to one or more communication networks such as 113 It could be any type of device configured to facilitate the process. RRH118a, 118b wirelessly interfaces with at least one of the WTRU102c , core network 106 / 107 / 109, internet 110, and / or others Facilitating access to one or more communication networks, such as network 112. It can be any type of device configured as follows. TRP119a, 119b are W Interfacing wirelessly with at least one of the TRU102d, core network -106 / 107 / 109, Internet 110, and / or other networks It is configured to facilitate access to one or more communication networks such as 112. It can be any type of device. RSU120a and 120b are WTRU10 It wirelessly interfaces with at least one of 2e or 102f, and core network Twerk 106 / 107 / 109, Internet 110, Other networks 112, Rabini / or one of the V2X servers (or ProSe functionality and server) such as 113 or any type configured to facilitate access to multiple communication networks It can be a device. For example, base stations 114a and 114b are transceiver base stations (Base Transceiver Station (BTS), Node B, eNode B, Home Node B, Home e Node B, Site Controller, Access Point (AP), Wireless Router It could be something like this. Base stations 114a and 114b are each described as a single element. However, base stations 114a and 114b can connect to any number of interconnected base stations and / or It should be understood that it may include networking elements.

[0255] Base station 114a may be part of RAN103 / 104 / 105, and those RANs are Also, Base Station Controller (BSC), Wireless Network Controller Radio Network Controller (RNC), relay nodes and other base stations and It may also include and / or network elements (not shown). Base station 114b is RAN103 It may be part of b / 104b / 105b, and those RANs are also base station controllers (B SC), Wireless Network Controller (RNC), other base stations such as relay nodes and / or may include network elements (not shown). Base station 114a is located in a specific geographical area. It may be configured to transmit and / or receive radio signals within its geographical area, It may be referred to as a base station (not shown). Base station 114b has wired and / or or it may be configured to transmit and / or receive wireless signals, and its geographical area is a cell. It may be referred to as (not shown). A cell can be further divided into cell sectors. For example, a base station. The cell associated with 114a can be divided into three sectors. Therefore, one implementation form In this configuration, the base station 114a includes, for example, three transceivers, one for each cell sector. In one embodiment, the base station 114a is a Multiple-Input Multiple Output: MIMO technology can be employed, and therefore multiple transceivers can be used for each sector of the cell. It can be used.

[0256] Base station 114a connects to any suitable wireless communication link (for example, radio frequency (Radio Frequ RF (radiofrequency), microwave, infrared (IR), ultraviolet (UV) Air interface 115 / 116 / 1 (possibly for visible light, centimeter wave, millimeter wave, etc.) It may communicate with one or more of WTRU102a, 102b, and 102c via 17. The air interface 115 / 116 / 117 can be used with any suitable wireless access technology. This can be established using RAT.

[0257] Base station 114b uses any suitable wired connection (e.g., cable, fiber optic, etc.) or Wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet) It can be wired or air interface (UV, visible light, centimeter wave, millimeter wave, etc.). RRH118a, 118b, TRP119a, 1 via 115b / 116b / 117b 19b, and / or one or more of RSU120a and 120b communicate with each other. It is possible. The air interface 115b / 116b / 117b can be any suitable wireless interface. This can be established using RAT (Real-Action Technique).

[0258] RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b is any suitable wireless communication link (e.g., radio frequency (RF), microwave Waves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. WTRU102c, 102d via interface 115c / 116c / 117c It can communicate with one or more of 102e and 102f. Air interface 11 5c / 116c / 117c can be established using any suitable radio access technology (RAT). It is possible.

[0259] WTRU102a, 102b, 102c, 102d, 102e, 102f, and / or 102g is any suitable wireless communication link (e.g., radio frequency (RF), microwave). Waves, infrared (IR), ultraviolet (UV), visible light, centimeter waves, millimeter waves, etc. They can communicate with each other via interface 115d / 116d / 117d (not shown). The Air Interface 115d / 116d / 117d is suitable for any suitable wireless access. It can be established using RAT technology.

[0260] More specifically, as described above, the communication system 100 is a multiple access system. It is possible to obtain one of the following: CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. It can employ multiple channel access schemes. For example, RAN103 / 104 / 10 Base stations 114a and WTRU102a, 102b, 102c, or RAN10 within 5 RRH118a, 118b, TRP119a, 119b within 3b / 104b / 105b, and RSU120a, 120b, and WTRU102c, 102d, 102e, 1 02f is Universal Mobile Telecommunications System tions System: UMTS), Universal Terrestrial Radio Access Wireless technologies such as cess:UTRA can be implemented, thereby enabling wideband CDMA (WCDMA). ) Use the air interface 115 / 116 / 117 or 115c / 116c / 117c can be established in each case. WCDMA is a high-speed packet access protocol. Packet Access (HSPA) and / or Evolved HSPA (HSPA) It may include communication protocols such as +). HSPA stands for High-Speed ​​Downlink Packet Access. (High-Speed ​​Downlink Packet Access: HSDPA) and / or high-speed uplink This may include High-Speed ​​Uplink Packet Access (HSUPA).

[0261] In one embodiment, base station 114a and WTRU 102a, 102b, 102c, and RRH118a, 118b, TRP119a within RAN103b / 104b / 105b , 119b, and / or RSU120a, 120b, and WTRU102c, 102d is an evolved UMTS terrestrial radio access system. Wireless technologies such as Access (E-UTRA) can be implemented, thereby enabling long-term evolution. LTE and / or LTE-Advanced (LTE-A ) Use the air interface 115 / 116 / 117 or 115c / 116c / 117c can be established respectively. In the future, air interfaces 115 / 116 / 117 It can implement 3GPP NR technology. LTE and LTE-A technologies are (sidelink) Includes LTE D2D and V2X technologies and interfaces (for communications, etc.). 3GP P NR technology is NR V2X technology and interface (such as sidelink communication). Includes.

[0262] In one embodiment, base stations 114a and WTRU1 within RAN103 / 104 / 105 RRH1 in 02a, 102b, 102c, or RAN103b / 104b / 105b 18a, 118b, TRP119a, 119b, and / or RSU120a, 12 0b, as well as WTRU102c, 102d, 102e, and 102f, are IEEE 802. 16 (For example, worldwide interoperability for microwaves) Access (Worldwide Interoperability For Microwave Access: WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, provisional standard 2000 (Interim Standard 2000:IS-2000), Interim Standard 95 (IS-95) , Provisional Standard 856 (IS-856), Global System for Mobile Communications (Global System) em for Mobile Communications: GSM (registered trademark), GSM evolved high-speed data Enhanced Data Rates For GSM Evolution:EDGE, GSM EDGE( It can implement wireless technologies such as GERAN.

[0263] In Figure 37A, base station 114c is, for example, a wireless router, home node B, home e node. It could be a B or an access point, such as a company, home, vehicle, campus, etc. Any suitable RAT can be used to facilitate wireless connectivity within the local area. In one embodiment, the base station 114c and WTRU102e are connected to IEEE802.11 By implementing wireless technologies such as these, a Wireless Local Area Network (Wireless Local Area) A network (WLAN) can be established. In one embodiment, a base station 114c and a WTRU can be established. The 102d implements wireless technologies such as IEEE 802.15, enabling wireless personal area networking. A network (Wireless Personal Area Network: WPAN) can be established. In this embodiment, the base station 114c and WTRU102e are cellular-based RAT( For example, using WCDMA, CDMA2000, GSM, LTE, LTE-A, etc. A picocell or femtocell can be established. As shown in Figure 37A, base station 114b , it may have a direct connection to the Internet 110. Therefore, base station 114c is core It is necessary to access the Internet 110 via networks 106 / 107 / 109. It may not be available.

[0264] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b are It can communicate with core networks 106 / 107 / 109, and that core network is voice , data, applications, and / or Voice over Internet Protocol (Voice over Internet Protocol: VoIP) service WTRU102a, 102 Any tie configured to provide one or more of b, 102c, and 102d It could be a network of multiple components. For example, the core network 106 / 107 / 109 is a network of multiple components. Call control, billing services, mobile location-based services, prepaid calls, internet It provides internet connectivity, video streaming, and / or advanced features such as user authentication. It can perform level security functions.

[0265] Although not shown in Figure 37A, RAN103 / 104 / 105 and / or RA N103b / 104b / 105b and / or core network 106 / 107 / 1 09 is RAN103 / 104 / 105 and / or RAN103b / 104b / 1 05b can communicate directly or indirectly with other RANs employing the same or different RATs. It will be understood that, for example, RAN103 / 10 which can utilize E-UTRA wireless technology. In addition to being connected to 4 / 105 and / or RAN103b / 104b / 105b Furthermore, the core network 106 / 107 / 109 also employs another R that uses GSM radio technology. It can communicate with AN (not shown).

[0266] Core networks 106 / 107 / 109 also include WTRU102a, 102b, and 10 2c, 102d, 102e are PSTN 108, Internet 110, and / or others. It can function as a gateway to access network 112. PSTN1 08 is the number that provides Plain Old Telephone Service (POTS). This may include a line-switched telephone network. The Internet 110 is a transmission control protocol (Tr User Datagram Protocol (TCP), User Datagram Protocol (User Datagram Protocol) The Graph Protocol (UDP), and the TCP / IP Internet Protocol Suite Common communication protocols such as the Internet Protocol (IP) The global system of interconnected computer networks and devices used May include. Network 112 is owned and / or owned by other service providers. This may include wired or wireless networks that are operated. For example, network 1 12 is RAN103 / 104 / 105 and / or RAN103b / 104b / 1 Connected to one or more RANs that may employ the same RAT as 05b or a different RAT. It may include another core network.

[0267] Some of WTRU102a, 102b, 102c, and 102d within the communication system 100 All of these may include multimode capability, for example, WTRU102a, 102b, 102 c, 102d, and 102e connect to different wireless networks via different wireless links. It may include multiple transceivers for communication. For example, the WTRU102e shown in Figure 37A is , base stations 114a that can employ cellular-based wireless technology, and IEEE 802 wireless technology It can be configured to communicate with base station 114c that may employ the technique.

[0268] Figure 37B shows, for example, a device without a WTRU102, as shown in the embodiments described herein. This is a block diagram of an exemplary apparatus or device configured for line communication. Figure 37B shows As shown, the exemplary WTRU102 includes a processor 118, a transceiver 120, and a transmission / receiving element 122, speaker / microphone 124, keypad 126, display Ray / Touchpad / Indicator 128, Non-removable memory 130, Removable Memory 132, power supply 134, and Global Positioning System : May include a GPS chipset 136 and other peripherals 138. WTRU102 This may include any secondary combination of the elements described above, while remaining consistent with the embodiment. It should be understood. Also, although not limited to, in particular, the transceiver base station (BTS) and node B Site controller, access point (AP), home node B, advanced home node Node-B (eNode-B), Home evolved Node-B (HeNB), Ho Base stations 114a and 1, such as the Node-Advanced Node B gateway and proxy node. 14b, and / or the nodes that base stations 114a and 114b may represent, are shown in Figure 37B. Embodiments may include some or all of the elements shown and described herein. It will be done.

[0269] Processor 118 is a general-purpose processor, special-purpose processor, conventional processor, digital processor Digital Signal Processor (DSP), multiple microprocessors S, one or more microprocessors, controllers, associated with the DSP core. Microcontrollers, Application Specific Integrated Circuits ircuit (ASIC), Field Programmable Gate Array (Field Programmable G FPGA (Array of Generators / Graphics Arrays), any other type of integrated circuit (Integrated Circuit: Array of Generators / Graphics Arrays), etc. C) This could be a state machine, etc. Processor 118 is responsible for signal coding, data processing. Power control, input / output processing, and / or WTRU102 operating in a wireless environment Processor 118 can perform any other functions that enable it. It can be connected to the transceiver 120 which can be connected to 2. Figure 37B shows the individual components and The processor 118 and the transceiver 120 are depicted, but the processor 118 and It is understood that the transceiver 120 may be integrated together in an electronic package or chip. Hey.

[0270] The transmission / reception element 122 connects to the base station via air interfaces 115 / 116 / 117. To transmit a signal to a station (for example, base station 114a) or to receive a signal from there It can be configured as follows. For example, in one embodiment, the transmission / receiving element 122 transmits an RF signal. It may be an antenna configured to transmit and / or receive. In one embodiment, transmission / reception The signal element 122 transmits and / or receives, for example, IR, UV, or visible light signals. It may be an emitter / detector configured as such. In a further embodiment, a transmission / receiving element 122 can be configured to transmit and receive both RF and optical signals. The signal element 122 is configured to transmit and / or receive any combination of radio signals. It will be understood that this is possible.

[0271] In addition, although the transmission / reception element 122 is depicted as a single element in Figure 37B, W TRU102 may include any number of transmission / reception elements 122. More specifically, WTR U102 may employ MIMO technology. Therefore, in one embodiment, WTRU102 It transmits and receives radio signals via air interfaces 115 / 116 / 117. It may include two or more transmission / reception elements 122 (e.g., multiple antennas) for this purpose.

[0272] The transceiver 120 modulates the signal that will be transmitted by the transmission / receiving element 122. The transmission / reception element 122 may be configured to demodulate the signal received by the transmission / reception element. Thus, the WTRU102 may have multimode capability. Therefore, the transceiver 120 WTRU102 supports multiple RAs, such as UTRA and IEEE802.11. It may include multiple transceivers to enable communication via T.

[0273] The WTRU102 has a processor (118), a speaker / microphone (124), and a keypad (1). 26, and / or display / touchpad / indicator 128 (e.g., LCD) Display (Liquid Crystal Display: LCD) Display unit or organic Light-emitting diode (OLED) display unit It is connected to and can receive user input data from there. Processor 118 also user The data is transmitted to the speaker / microphone 124, keypad 126, and / or display. It can output to the I / touchpad / indicator 128. In addition, the processor 118 takes Any type of non-removable memory 130 and / or removable memory 132 Information can be accessed from a suitable memory location, and data can be stored there. Non-removable memory 1 30 is Random-Access Memory (RAM), read-only memory Read-Only Memory (ROM), hard disk, or any other type of memory It may include a memory device. Removable memory 132 is a subscriber identification module (Su bscriber Identity Module: SIM card, memory stick, secure digital This may include a Secure Digital (SD) memory card, etc. In one embodiment, a processor 1 18 is physically located on WTRU102, such as on a server or home computer (not shown). It is possible to access information from memory that is not located in the target area and store data there.

[0274] The processor 118 can receive power from the power supply 134, and other components within the WTRU 102 Power supply 134 may be configured to distribute and / or control power to the conductor. Any suitable device for supplying power to TRU102 may be. For example, power supply 134 is This may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0275] The processor 118 also provides location information (e.g., longitude) regarding the current location of the WTRU 102. It can be connected to a GPS chipset 136 which may be configured to provide (and latitude). In addition to, or instead of, information from GPS chipset 136, WTRU102 , via air interfaces 115 / 116 / 117 to a base station (e.g., base station 114 Location information is received from a, 114b) and / or from two or more nearby base stations. Based on the timing of the signal being transmitted, its position can be determined. WTRU102 implements The ability to acquire location information by any suitable positioning method while maintaining consistency with the form. Let's be understood.

[0276] The 118 processor also includes additional features, functions, and / or wired or wireless connectivity. One or more software and / or hardware components that provide the activity. It may be connected to other peripheral devices 138, which may include modules. For example, peripheral device 138 is , various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, e-compass , satellite transceiver, digital camera (for photos or video), universal serial bus ( Universal Serial Bus (USB) port or other interconnection interface, vibration Vice, TV transmitter / receiver, hands-free headset, Bluetooth® (registered trademark) Module, frequency modulation (FM) wireless unit, digital music player Layer, media player, video game player module, internet browser This may include the following.

[0277] WTRU102 is a sensor, consumer electronics, smartwatch or smart clothing. Wearable devices such as medical or e-health devices, robots, industrial equipment, and drawers. For example, in other vehicles or devices such as cars, trucks, trains, or airplanes. It can be realized. WTRU102 may have one of the peripheral devices 138 interconnection The device can access the device via one or more interconnection interfaces, such as an interface. Alternatively, it may connect to other components, modules, or systems of the device.

[0278] Figure 37C shows a system of RAN103 and core network 106 according to one embodiment. This is a diagram. As shown above, RAN103 employs UTRA wireless technology and air interface - It can communicate with WTRU102a, 102b, and 102c via face 115. RAN103 can also communicate with core network 106. As shown in Figure 37C, R AN103 is connected to WTRU102a, 102b, 10 via air interface 115. Node B140a, 1 may each include one or more transceivers for communicating with 2c. May include 40b and 140c. Nodes B140a, 140b, and 140c are each in RAN1 It can be associated with a specific cell (not shown) within 03. RAN103 is also RNC14 2a and 142b may be included. RAN103 remains consistent with the embodiment, with any number of no It will be understood that this may include Code B and RNC.

[0279] As shown in Figure 37C, nodes B140a and B140b can communicate with RNC142a. Furthermore, node B140c can communicate with RNC142b. Nodes B140a, 14 0b and 140c are connected via the Iub interface to the respective RNC142a and 14 It can communicate with 2b. RNC142a and 142b communicate with each other via the Iur interface. They can communicate with each other. Each of the RNC142a and 142b is connected to the respective node. It can be configured to control B140a, 140b, and 140c. In addition, RNC14 2a and 142b each handle outer loop power control, load control, reception control, and packet scheduling. Jouring, handover control, macro diversity, security features, data encryption It may be configured to perform or support other functions, such as numbering.

[0280] The core network 106 shown in Figure 37C includes a media gateway. MGW)144, Mobile Switching Center (MSC)146, Sa 148 Serving GPRS Support Nodes (SGSN) and / or Gateway GPRS Support Node: It may include GGSN)150. Each of the above elements is part of the core network 106. As shown, any one of these elements is the core network operator. It will be understood that it may be owned and / or operated by an external entity.

[0281] RNC142a within RAN103 connects to the core network via the IuCS interface. It can be connected to MSC146 in workpiece 106. MSC146 is connected to MGW144. MSC146 and MGW144 are compatible with WTRU102a, 102b, and 102c. , provides access to circuit-switched networks such as PSTN108, and WTRU102a This can facilitate communication between 102b, 102c and conventional terrestrial communication devices.

[0282] RNC142a within RAN103 also communicates via the IuPS interface to the core network. It can be connected to SGSN148 in network 106. SGSN148 is GGSN15 It can be connected to 0. SGSN148 and GGSN150 are WTRU102a, 102 b, 102c provides access to packet-switched networks such as the Internet 110. Provides and facilitates communication between WTRU102a, 102b, 102c and IP-enabled devices. It is possible.

[0283] As mentioned above, core network 106 is also owned by other service providers. Network 11 may include other wired or wireless networks that are operated by it. It can be connected to 2.

[0284] Figure 37D shows a system of RAN104 and core network 107 according to one embodiment. This is a diagram. As described above, RAN104 adopts E-UTRA wireless technology and air intake It can communicate with WTRU102a, 102b, and 102c via surface 116. RAN104 can also communicate with core network 107.

[0285] RAN104 may include e-nodes B160a, 160b, and 160c, but RAN10 It will be understood that 4 may include any number of enodes B, while remaining consistent with the embodiment. eNodes B160a, 160b, and 160c each connect via the air interface 116. to communicate with WTRU102a, 102b, and 102c, one or more transceivers It may include. In one embodiment, e-nodes B160a, 160b, 160c are MIMO technology This can be implemented. Therefore, the e-node B160a can, for example, use multiple antennas. , transmits a wireless signal to WTRU102a and can receive a wireless signal from WTRU102a ru.

[0286] Each of the e-nodes B160a, 160b, and 160c is located in a specific cell (not shown). Correspondence, wireless resource management decision, handover decision, uplink and / or Alternatively, it may be configured to handle user scheduling and other tasks in the downlink. (Figure) As shown in 37D, e-nodes B160a, 160b, and 160c are X2 interfaces. They can communicate with each other via S.

[0287] The core network 107 shown in Figure 37D is a mobility management gateway. Management Gateway (MME) 162, Serving Gateway 164, and packets Including a data network (Packet Data Network: PDN) gateway 166, Obtain. Each of the above elements is shown as part of the core network 107, but this Any one of these elements is by an entity other than the core network operator. It will be understood that they may be owned and / or operated by them.

[0288] MME162 connects to e-node B160 in RAN104 via the S1 interface. a, 160b, and 160c can each be connected and function as a control node. For example, MME162 authenticates users of WTRU102a, 102b, and 102c. Bearer activation / deactivation, initial activation of WTRU102a, 102b, 102c It can play a role such as selecting a specific serving gateway between touches. MME16 2 also employs other R technologies such as RAN104 and GSM or WCDMA. It may provide control plane functionality for switching between AN (not shown) and AN.

[0289] The serving gateway 164, via the S1 interface, connects to RAN104. It can be connected to enode B160a, 160b, and 160c, respectively. Serving game WTRU164 generally uses WTRU102a, 102b, and 10 Routing and forwarding from WTRU102a, 102b, and 102c to 2c is possible. The moving gateway 164 also handles the user plane during handover between enode B. Anchor and downlink data are available for WTRU102a, 102b, and 102c. Paging triggers when in operation, context of WTRU102a, 102b, 102c It can perform other functions such as managing and storing data.

[0290] Serving gateway 164 also provides to WTRU102a, 102b, and 102c. It provides access to packet-switched networks such as Internet 110, and WTRU1 PDN gates can facilitate communication between 02a, 102b, 102c and IP-enabled devices. It can be connected to Way 166.

[0291] The core network 107 can facilitate communication with other networks. For example, the core network Network 107 is compatible with WTRU102a, 102b, 102c, and PSTN108, etc. It provides access to circuit-switched networks, including WTRU102a, 102b, and 102c. It can facilitate communication with conventional terrestrial communication devices. For example, the core network 107 It functions as an interface between the core network 107 and the PSTN 108. IP gateway (for example, IP Multimedia Subsystem) tem:IMS) server) includes or can communicate with it. In addition, core network 107 is WTRU102a, 102b, 102c, by other service providers A network that may include other wired or wireless networks owned and / or operated by the network. It may provide access to 112.

[0292] Figure 37E shows the system of RAN105 and core network 109 according to one embodiment. This is a diagram. RAN105 adopts IEEE802.16 wireless technology and air interface Access to communicate with WTRU102a, 102b, and 102c via face 117 It could be an Access Service Network (ASN). Further details below As discussed, WTRU102a, 102b, 102c, RAN105, and core Communication links between different functional entities in network 109 are defined as reference points. It is possible.

[0293] As shown in Figure 37E, RAN105 is connected to base stations 180a, 180b, and 180c, and A SN gateway 182 may be included, but RAN105 remains consistent with the embodiment. It will be understood that this may include any number of base stations and ASN gateways. Base station 1 80a, 180b, and 180c can each be associated with a specific cell within RAN105, To communicate with WTRU102a, 102b, and 102c via interface 117 It may include one or more transceivers. In one embodiment, base stations 180a, 180b 180c can implement MIMO technology. Therefore, base station 180a can, for example, multi Using a number of antennas, a radio signal is transmitted to the WTRU102a, and the WTRU102a Radio signals can be received from. Base stations 180a, 180b, and 180c also receive handoffs. Riga, tunnel establishment, wireless resource management, traffic classification, quality of service (QoS) It can provide mobility management functions such as policy enforcement. The ASN Gateway 182 is It can function as a graphical aggregation point, paging, subscriber profiles It can serve roles such as caching and routing to core network 109.

[0294] Air interface between WTRU102a, 102b, 102c and RAN105 117 can be designated as an R1 reference point implementing the IEEE 802.16 specification. In addition Then, WTRU102a, 102b, and 102c each connect to the core network 109 and A logical interface (not shown) can be established. WTRU102a, 102b, 10 The logical interface between 2c and core network 109 is used for authentication, authorization, and IP hosting. R2 reference points and fixed configurations can be used for configuration management and / or mobility management. It is possible.

[0295] The communication links between base stations 180a, 180b, and 180c are connected to WTRU Hankham. R8 reference protocol includes protocols for facilitating data transfer between base stations and overloads. It can be defined as an input. Base stations 180a, 180b, 180c and ASN gateway 18 The communication link between 2 and WT may be defined as the R6 reference point. The R6 reference point is WT Based on mobility events corresponding to RU102a, 102b, and 102c respectively This may include protocols to facilitate mobility management.

[0296] As shown in Figure 37E, RAN105 can be connected to the core network 109. The communication link between AN105 and the core network 109 is, for example, used for data transfer and R3 reference points may be designated, including protocols for promoting mobility management capabilities. Core network 109 is a mobile IP home agent. ent:MIP-HA)184 and authentication, authorization, and accounting (Authentication Authorization) This may include server 186 and gateway 188 (regization Accounting:AAA). Each of the elements described above is shown as part of the core network 109, but these elements Any one of the elements is owned by an entity other than the core network operator. It will be understood that and / or it may be operated.

[0297] MIP-HA can perform the role of IP address management, including WTRU102a and 102b. and 102c roam between different ASNs and / or different core networks This can make it possible to do so. MIP-HA184 is compatible with WTRU102a, 102b, and 102 c provides access to packet-switched networks such as the Internet 110, and W This can facilitate communication between TRU102a, 102b, 102c and IP-enabled devices. AA server 186 can serve the role of supporting user authentication and user services. Gateway 188 can facilitate interaction with other networks. For example, Gateway 188 connects to WTRU102a, 102b, 102c, and PSTN108. Which circuit-switched network does it provide, WTRU102a, 102b, 102 c can facilitate communication between and conventional terrestrial communication devices. In addition, gateway 188 WTRU102a, 102b, 102c, owned by other service providers Network 112 may include and / or other wired or wireless networks being operated. It may provide access to it.

[0298] Although not shown in Figure 37E, RAN105 may be connected to other ASNs, core network It will be understood that Twork 109 can be connected to other core networks. RAN1 The communication link between 05 and other ASNs is WTRU1 between RAN105 and other ASNs. R4 reference may include protocols for coordinating the mobility of 02a, 102b, and 102c. It can be designated as an illumination point. Communication between core network 109 and other core networks. ShinLink is an interface between the home core network and the core network of the visited location. R5 reference may be defined as including protocols to promote kingship.

[0299] The core described herein and shown in Figures 37A, 37C, 37D, and 37E Network entities are given to those entities in certain existing 3GPP specifications. They are identified by the names they are given, but in the future, those entities and functions may be named by other names. A specific entity or function may be identified by a name, and may be subject to future 3GPP NR specifications. It is understood that this may be combined in future specifications published by 3GPP, including Therefore, as shown and illustrated in Figures 37A, 37B, 37C, 37D, and 37E The specific network entities and functions described are provided as examples only and are not included in this specification. Is the subject matter to be disclosed and requested in the document currently defined, or will be defined in the future? Regardless of the circumstances, it is understood that this can be embodied or implemented in any similar communication system. sea ​​bream.

[0300] Figure 37F is a block diagram of an exemplary computing system 90, where, RAN103 / 104 / 105, Core Network 106 / 107 / 109, PSTN108 , a specific node or function on the Internet 110, or other network 112 Communications networks such as NTIT, as shown in Figures 37A, 37C, 37D, and 37E One or more of the devices can be realized. The computing system 90 is It may include a computer or server, and in the form of software (the software is stored (or whatever the location or means of access) It can be primarily controlled by computer-readable instructions. These computer-readable instructions are computer-readable instructions. The system 90 may be run within the processor 91. 1 refers to general-purpose processors, special-purpose processors, conventional processors, and digital signal processors. DSP (DSP), multiple microprocessors, one or more associated with DSP cores Microprocessors, controllers, microcontrollers, application-specific integrated circuits ( ASICs, field-programmable gate array (FPGA) circuits, any other type This could be an integrated circuit (IC), a state machine, etc. The processor 91 is a signal coding machine. Data processing, power control, input / output processing, and / or computing systems The Mu90 may perform any other functions that enable it to operate within a communication network. The coprocessor 81 is an optional processor that is distinctly different from the main processor 91. Yes, it may perform additional functions or assist processor 91. and / or coprocessor 81 provides data related to the methods and apparatus disclosed herein. It can receive, generate, and process data.

[0301] The processor 91, when operating, fetches, decodes, and executes instructions, and the computer... Information is transferred to other systems via the system bus 80, which is the main data transfer path of the system. Transfer to the source and transfer from other resources. The system bus is a computer The components within the 90 system are connected to each other, and a medium for data exchange is defined. The system bus 80 typically has data lines for transmitting data and addresses The address line for sending, the interrupt for sending, and the system bus Includes control lines for operation. An example of the system bus 80 is peripheral components It is a Peripheral Component Interconnect (PCI) bus.

[0302] The memory connected to the system bus 80 consists of random access memory (RAM) 82 and, Includes a read-only memory (ROM) 93, which stores and reads information. Includes a circuit that allows it to be extracted. ROM93 is generally easy to modify. This includes data that cannot be stored. Data stored in RAM82 is processed by processor 91 RAM may be read from or modified by other hardware devices. Access to 82 and / or ROM93 is controlled by the memory controller 92. When an instruction is executed, the memory controller 92 converts the virtual address to the physical address. It can provide an address translation function to convert to [the specified address]. The memory controller 92 also provides a system Memory protection feature that isolates internal processes and separates system processes from user processes. This may provide a process. Therefore, a program running in the first mode can provide its own process. Only memory mapped by the virtual address space can be accessed, and inter-process access is possible. Unless memory sharing is configured, memory in another process's virtual address space will not be accessible. It is not possible to access it.

[0303] In addition, the computing system 90 includes a processor 91, a printer 94, and a key It communicates commands to peripherals such as board 84, mouse 95, and disk drive 85. It may include a peripheral device controller 83 that performs a specific role.

[0304] The display 86, controlled by the display controller 96, is a computer It is used to display the visual output generated by the display system 90. The output may include text, graphics, video graphics, and video. The visual output is a graphical user interface (G). It may be provided in the form of a UI. Display 86 is a CRT-based video display. LCD-based flat panel displays, gas plasma-based flat panel displays It can be implemented using a display or touch panel. Display controller 96 The electronic components required to generate the video signal transmitted to the display 86 Includes Nent.

[0305] Furthermore, the computing system 90 will RA N103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108 , Internet 110, or other figures 37A, 37B, 37C, 37D, and 37E It can be used to connect to external communication networks such as network 112, for example The computing system 90 includes communication circuits such as a network adapter 97. This enables communication with other nodes or functional entities in those networks. The communication circuit, either alone or in combination with the processor 91, is described herein. to perform transmission and reception steps for a specific device, node, or functional entity. It can be used for that purpose.

[0306] Figure 37G illustrates how the methods and apparatus described and claimed herein may be embodied. An embodiment of the typical communication system 111 is shown. As illustrated, the exemplary communication system 1 11 consists of Wireless Transmission / Receiving Units (WTRUs) A, B, C, D, E, F, and the base station, and V The disclosed embodiments may include a 2X server and RSUs A and B, but any number Consider the WTRU, base station, network, and / or network elements. Let it be understood. One or some or all WTRU A, B, C, D, E This is outside the network's coverage area (for example, the cell coverage boundary shown as a dashed line in the diagram). It can be outside of WTRU A, B, and C, with WTRU A being the group lead and W TRU B and C form a V2X group of group members. WTRU A B, C, D, E, F are Uu interfaces or sidelink (PC5) interfaces. Communication is possible via the face.

[0307] Any of the apparatus, systems, methods, and processes described herein or All of these are computer executable instructions stored on a computer-readable storage medium (for example) It may be embodied in the form of program code, and its instructions are on processor 118 or 91 When executed by a processor such as the system described herein, the processor will be given the system described herein. Please understand the methods and processes for executing and / or implementing them. Specifically Any of the steps, operations, or functions described herein may be performed by the computer. It is implemented in the form of executable instructions and is designed for wireless and / or wired network communications. It can be executed on the processor of a device or computing system. A computer-readable storage medium is any non-temporary (e.g., tangible or physical) medium for storing information. Volatile and non-volatile media implemented by methods or techniques, removable and removable This includes non-transmittable media, but the computer-readable storage medium does not contain signals. Readable storage media include RAM, ROM, EEPROM, flash memory, or other memory. Technology, CD-ROMs, and Digital Versatile Discs (DVDs) are also included. or other optical disc storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices A magnetic storage device or other magnetic storage device, or can be used to store desired information, Any other tangible or physical medium that may be accessed by the computing system This includes, but is not limited to, those listed above.

Claims

1. Receiving a radio resource control (RRC) signaling that includes configuration information constituting a first hybrid ARQ (HARQ) codebook and a second HARQ codebook, wherein the RRC signaling indicates that the first HARQ codebook is associated with a first subslot length for physical uplink control channel (PUCCH) feedback and the second HARQ codebook is associated with a second subslot length for PUCCH feedback. The process involves receiving first Downlink Control Information (DCI), the first DCI scheduling a first Physical Downlink Shared Channel (PDSCH) transmission, and To determine whether the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook or the second HARQ codebook, If the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook, the first HARQ feedback is transmitted at a first time determined based on the first subslot length, or if the first HARQ feedback for the first PDSCH transmission is associated with the second HARQ codebook, the first HARQ feedback is transmitted at a second time determined based on the second subslot length. A wireless transceiver unit (WTRU) including a processor configured to perform the following actions.

2. The WTRU according to claim 1, wherein the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook, and the first time is further determined based on the field of the first DCI.

3. The WTRU according to claim 2, wherein the field of the first DCI corresponds to the K1 field.

4. The WTRU according to claim 3, wherein the K1 field indicates the first time in units of the first sub-slot length.

5. The WTRU according to claim 1, wherein the first HARQ codebook is associated with a first priority, and the second HARQ codebook is associated with a second priority.

6. The WTRU according to claim 5, wherein the first DCI includes a field indicating either the first priority or the second priority.

7. The processor is configured to determine whether the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook or the second HARQ codebook. The aforementioned processor, If the field indicates the first priority, it is determined that the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook. If the field indicates the second priority, it is determined that the first HARQ feedback for the first PDSCH transmission is associated with the second HARQ codebook. The WTRU according to claim 6, which is configured in such a way.

8. The WTRU according to claim 1, wherein the first HARQ feedback is transmitted by PUCCH transmission.

9. The WTRU according to claim 1, wherein the RRC signaling indicates a first number of symbols in the first subslot length for a PUCCH feedback associated with at least a first PUCCH transmission, and a second number of symbols in the second subslot length for a PUCCH feedback associated with at least a second PUCCH transmission, and the first number of symbols is different from the second number of symbols.

10. The WTRU according to claim 9, wherein the processor is configured to determine that the first PUCCH transmission and the second PUCCH transmission overlap in time at least partially.

11. Receiving a radio resource control (RRC) signaling that includes configuration information constituting a first hybrid ARQ (HARQ) codebook and a second HARQ codebook, wherein the RRC signaling indicates that the first HARQ codebook is associated with a first subslot length for physical uplink control channel (PUCCH) feedback and the second HARQ codebook is associated with a second subslot length for PUCCH feedback. The process involves receiving first Downlink Control Information (DCI), the first DCI scheduling a first Physical Downlink Shared Channel (PDSCH) transmission, and To determine whether the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook or the second HARQ codebook, If the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook, the first HARQ feedback is transmitted at a first time determined based on the first subslot length, or if the first HARQ feedback for the first PDSCH transmission is associated with the second HARQ codebook, the first HARQ feedback is transmitted at a second time determined based on the second subslot length. A method performed by a wireless transceiver unit (WTRU), including the following.

12. The method according to claim 11, wherein the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook, and the first time is further determined based on the field of the first DCI.

13. The method according to claim 12, wherein the first DCI field corresponds to the K1 field.

14. The method according to claim 13, wherein the K1 field indicates the first time in units of the first sub-slot length.

15. The method according to claim 11, wherein the first HARQ codebook is associated with a first priority, and the second HARQ codebook is associated with a second priority.

16. The method according to claim 15, wherein the first DCI includes a field indicating either the first priority or the second priority.

17. Determining whether the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook or the second HARQ codebook is: If the field indicates the first priority, it is determined that the first HARQ feedback for the first PDSCH transmission is associated with the first HARQ codebook. If the field indicates the second priority, it is determined that the first HARQ feedback for the first PDSCH transmission is associated with the second HARQ codebook. The method according to claim 16, further comprising the following:

18. The method according to claim 11, wherein the first HARQ feedback is transmitted by PUCCH transmission.

19. The method according to claim 11, wherein the RRC signaling indicates a first number of symbols in the first subslot length for a PUCCH feedback associated with at least a first PUCCH transmission, and a second number of symbols in the second subslot length for a PUCCH feedback associated with at least a second PUCCH transmission, and the first number of symbols is different from the second number of symbols.

20. The method according to claim 19, further comprising determining that the first PUCCH transmission and the second PUCCH transmission overlap in time at least partially.

Images