Intra-UE prioritization in uplink transmissions

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 TO RELATED APPLICATIONS) This application is a continuation of U.S. Provisional Patent Application No. 62 / 805,614, filed February 14, 2019. and U.S. Provisional Patent Application No. 62 / 824,701, filed March 27, 2019. and the entirety of which are incorporated herein by reference. [Background technology]

[0002] Supports transmission of various priority levels to support different applications. Priority is determined by the Medium Access Control : MAC) layer, but sometimes the physical layer itself allows priority identification. This can happen when the physical transmission begins, but it can also happen at the physical layer. Therefore, the priority must be identified at the physical layer and the user terminal must Collisions within the User Equipment (UE) cause the physical downlink shared channel Define UE behavior and handle collisions when they occur on the PDSCH (Pass Shared Channel) Defines UE procedures for enabling the UE to resolve prioritization at the MAC layer. It is necessary. Summary of the Invention

[0003] This Summary is an introduction to concepts in a simplified form that are further described below in the Detailed Description. This Summary is provided to introduce a selection. It does not identify key features or essential aspects of the claimed subject matter. It is not intended to identify any particular mechanism, nor is it intended to be used to limit the scope of the claimed subject matter. Moreover, claimed subject matter is not intended to be a substitute for any part of this disclosure. The present invention may be implemented without limitation to solve any or all of the shortcomings.

[0004] A method and apparatus for prioritization within a transmitting UE is described herein. Identifies the priority of transmissions on the Uplink (UL) and handles PDSCH collisions within the UE. Supports multiple Hybrid ARQ (HARQ) ACK codebooks. Physical Uplink Shared Channel for multiple priorities ed Channel (PUSCH), UCI enabled with PUSCH repetition and configured graph HARQ ID conflicts for Configured Grant (CG) and dynamic grants A method is described for handling conflicts and enabling a MAC layer to handle contention in a UE.

[0005] In one example, the device may receive a first uplink grant indicating a first uplink grant associated with the first transmission. and a second uplink grant indicating a second uplink grant associated with the second transmission. The device may receive the first transmission and the second transmission based on the first information and the second information. The device may determine that the second transmission overlaps at least partially in time. determining a first priority associated with the first transmission and a second priority associated with the second transmission; The device then determines, based at least in part on the first priority and the second priority, , prioritization of one transmission over another, or the first transmission over the second transmission. This may cause at least one of the following preemptions: [Brief explanation of the drawings]

[0006] The foregoing summary, as well as the following detailed description, will be better understood when read in conjunction with the appended drawings. In order to illustrate the present disclosure, various aspects of the present disclosure are shown. However, the present disclosure It is not limited to the particular embodiments discussed. [Figure 1] FIG. 1 is a diagram of an enabling DCI changing the priority of a Type 2 configured grant. [Figure 2] FIG. 2 is a diagram of a PUSCH and a Physical Uplink Control Channel (PUCCH) with the Cell Radio-Network Temporary Identifier (C-RNTI) masked with the priority level RNTI. [Figure 3A] FIG. 3A is a diagram of preemption in a UE of a lower priority PDSCH by a higher priority PDSCH with Resource Element (RE) collisions between PDSCHs. [Figure 3B] FIG. 3B is a diagram of preemption in a UE of a lower priority PDSCH by a higher priority PDSCH without RE collision between the PDSCHs. [Figure 4A] FIG. 4A illustrates preemption with PDSCHURLLC, preemption only within the UE; the New Radio (NR) NodeB (gNB) does not need to send a preemption indication. [Figure 4B] Figure 4B is a diagram of preemption via PDSCHURLLC, inter-UE and intra-UE preemption, where the gNB sends a preemption indication. [Figure 5] FIG. 5 is a diagram of a UE procedure for flushing the soft buffer of a low priority HARQ process in the event of preemption. [Figure 6] FIG. 6 shows UE2 preempting the PDSCHs of UE0 and UE1, which have lower priority, but not the PDSCH of UE3, which has higher priority. [Figure 7] FIG. 7 is a diagram of a UE procedure for flushing soft buffers of priority indicated through an RNTIp mask. [Figure 8A] FIG. 8A is a diagram of HARQ-ACK UCI transmission with PUCCH M=1, a single UCI feedback opportunity in a slot. [Figure 8B] FIG. 8B is a diagram of HARQ-ACK UCI transmission with PUCCH M=2, multiple UCI feedback opportunities in a slot. [Figure 9A] FIG. 9A is a diagram of a subslot configuration M=1, 1 subslot / slot. [Figure 9B] FIG. 9B is a diagram of a subslot configuration M=2, 2 subslots / slot. [Figure 10] FIG. 10 is a diagram where K1 is incremented at the finest granularity of sub-slots (two per slot) for lowest priority (enhanced Mobile Broadband (eMBB)). [Figure 11] FIG. 11 shows K1 indicating a slot for PUCCH, and K1a indicating a sub-slot. [Figure 12] FIG. 12 is a diagram of separate HARQ ACK codebooks for p=0 (eMBB) and p=1 (Ultra-Reliable and Low Latency Communications (URLLC)). [Figure 13] FIG. 13 is a diagram of PUCCH transmission to multiple Transmission and Reception Points (TRPs). [Figure 14] 14 is a diagram of PUCCH transmission to multiple TRPs, where PUCCH Resource Indicator (PRI)=0 is configured for PUCCH transmission to TRP0 on B0, and PRI=1 is configured for PUCCH transmission to TRP1 on B0. [Figure 15]FIG. 15 is a diagram of PUCCH spatial orientation based on TRP awareness (derived from CORESET in this example). [Figure 16] FIG. 16 is a diagram showing multiple HARQ ACK codebooks piggybacked on a single PUSCH in a slot. [Figure 17] FIG. 17 is a diagram of UCIm mapping on different hops of PUSCH. [Figure 18] FIG. 18 is a diagram showing how UCI0 is divided and mapped onto hops of the PUSCH. [Figure 19] 19 is a diagram of the UE procedure for mapping UCI0. If M=1, UCI0 is mapped to each hop. If M>1, UCI0 is mapped to hop #0, UCI1 is mapped to hop #1, etc. [Figure 20A] FIG. 20A is a diagram of mapping of HARQ-ACK and CSI for UCIm on PUSCH multiplexed with PUSCH resources. [Figure 20B] FIG. 20B is a diagram of HARQ-ACK and CSI mapping for UCIm on PUSCH with UCI only on PUSCH. [Figure 21A] FIG. 21A is a diagram of HARQ-ACK UCI mapping resources where there is no Demodulation Reference Signal (DMRS) in the vicinity of UCI1. [Figure 21B] FIG. 21B is a diagram of HARQ-ACK UCI mapping resources for an additional DMRS introduced near UCI1. [Figure 22A] FIG. 22A is a diagram of UCIURLLC and UCIeMBB where UCIeMBB is piggybacked onto a PUSCH preceding UCIURLLC. [Figure 22B] FIG. 22B is a diagram of UCIURLLC and UCIeMBB where UCIURLLC is piggybacked onto a PUSCH preceding UCIeMBB. [Figure 22C]FIG. 22C is a diagram of UCIURLLC and UCIeMBB piggybacked onto a PUSCH in which UCIeMBB and UCIURLLC are mapped to the same subslot of the PUSCH. [Figure 22D] FIG. 22D is a diagram of UCIURLLC and UCIeMBB where UCIURLLC resources are mapped first and piggybacked onto PUSCH followed by UCIeMBB. [Figure 23A] FIG. 23A is a diagram of HARQ process repetitions of PUSCH repetitions in a minislot and UCI partitioning between repetitions. [Figure 23B] FIG. 23B is a diagram of a HARQ process repetition of multiple segment transmissions between slot boundaries, with UCI partitioning between repetitions. [Figure 23C] FIG. 23C is a diagram of HARQ process repetitions of a minislot with frequency hopping and UCI partitioning between repetitions. [Figure 23D] FIG. 23D is a diagram of HARQ process repetitions for multiple segment transmissions with hopping, and UCI partitioning between repetitions. [Figure 24A] FIG. 24A is a diagram illustrating the division of modulated UCI symbols between repetitions of jointly generated UCI symbols, with proportional mapping to PUSCH resources in each segment. [Figure 24B] FIG. 24B is a diagram of dividing modulated UCI symbols between repetitions of jointly generated UCI symbols, with approximately equal mapping between PUSCH segments. [Figure 24C] FIG. 24C is a diagram illustrating the division of modulated UCI symbols between repetitions of separately generated UCI modulation symbols for each repetition. [Figure 25A] FIG. 25A is a diagram of UCI transmission via PUSCH repetition, which maps UCI to PUSCH with minimal delay. [Figure 25B] FIG. 25B is a diagram of UCI transmission via PUSCH repetition that maps UCI to an edge-aligned PUSCH. [Figure 25C] FIG. 25C is a diagram of UCI transmission via PUSCH repetition, which maps UCI to a first PUSCH that overlaps with a PUCCH(D), which maps UCI to a PUSCH according to UE capabilities. [Figure 25D] FIG. 25D is another illustration of UCI transmission via PUSCH repetition. [Figure 26] FIG. 26 is a diagram of PUSCH repetition transmission to different TRPs. [Figure 27A] FIG. 27A is a diagram of UCI mapping to target PUSCH repetitions for different TRPs with separate HARQ-ACK codebooks for each TRP. [Figure 27B] FIG. 27B is a diagram of UCI mapping to target PUSCH repetitions for different TRPs of UCI with a common codebook repeated for each TRP. [Figure 28A] FIG. 28A is a diagram of PUSCH repetition with Scheduling Request Indicator (SRI) cycles. [Figure 28B] FIG. 28B is a diagram of PUSCH repetition with SRI fixed to time resources. [Figure 28C] FIG. 28C is a diagram of PUSCH repetition with SRI as a function of repetition instance. [Figure 29A] FIG. 29A is a diagram of PUSCH repetition in a multiple TRP scenario with four repetition sets for the PUSCH HARQ ID. [Figure 29B] FIG. 29B is a diagram of PUSCH repetition in a multiple TRP scenario with Early Termination Indication (ETI) indications to terminate transmissions 3 and 4. [Figure 29C] FIG. 29C is a diagram of PUSCH repetition in a multiple TRP scenario with UCI only on the PUSCH at the end of the PUSCH repetition. [Figure 29D]FIG. 29D is a diagram of PUSCH repetition in a multiple TRP scenario with delayed end of repetition. [Figure 29E] FIG. 29E is a diagram of PUSCH repetition in a multiple TRP scenario with an override grant indicating early termination. [Figure 29F] FIG. 29F is a diagram of PUSCH repetitions in a multiple TRP scenario with transmission of NACed Code Block Groups (CBGs) in later repetitions. [Figure 29G] FIG. 29G is a diagram of PUSCH repetition in a multiple TRP scenario with early termination timer-based termination of PUSCH repetition. [Figure 29H] FIG. 29H is a diagram of PUSCH repetition in a multiple TRP scenario with selective termination of repetition. [Figure 30] FIG. 30 is a diagram of retransmissions to TRPs within a TRP group when one TRP from the group negatively acknowledges a transmission. [Figure 31A] FIG. 31A is a diagram of a UE flushing its HARQ buffer upon receiving ACKs from all TRP groups. [Figure 31B] FIG. 31B illustrates a diagram in which the UE identifies ACKs from all TRP groups upon receipt of at least one ACK and the HARQ buffer flows after the timer expires. [Figure 32A] FIG. 32A is an illustration of intra-UE collision between low and high priority PUSCH grants where eMBB PUSCH resources are punctured at the location of URLLC resources. [Figure 32B] FIG. 32B is an illustration of intra-UE collision between low and high priority PUSCH grants resulting in complete cancellation of eMBB transmissions. [Figure 32C] FIG. 32C is an illustration of intra-UE collision between low and high priority PUSCH grants where the eMBB PUSCH resource is punctured on the symbol where collision occurs with the URLLC PUSCH. [Figure 33] FIG. 33 is a diagram in which PUSCHURLLC and PUSCHHeMBB have the same HARQ-ID D (note that PUSCH resources do not collide). [Figure 34] 34 is a diagram of intra-UE collision of CG PUSCHs, where a lower priority CG PUSCH is cancelled or punctured by a higher priority CG PUSCH. [Figure 35A] Figure 35A is a diagram of retransmission of a preempted low priority CG PUSCH in a UE upon receiving a dynamic grant from a gNB. [Figure 35B] FIG. 35B is a diagram of a retransmission of a preempted lower priority CG PUSCH retransmission in a UE as a CG PUSCH. [Figure 36A] FIG. 36A is a diagram of downlink (DL) and UL collisions, low priority PDSCH and high priority PUSCH collisions within a UE. [Figure 36B] FIG. 36B is a diagram of DL and UL collisions, low priority PDSCH and high priority PUCCH collisions within a UE. [Figure 36C] FIG. 36C is a diagram of DL and UL collisions, low priority PUSCH and high priority PDSCH collisions within a UE. [Figure 37A] FIG. 37A illustrates an exemplary communication system in which the methods and apparatus described and claimed herein may be implemented. [Figure 37B] FIG. 37B is a block diagram of an exemplary apparatus or device configured for wireless communication. [Figure 37C] FIG. 37C is a system diagram of an example Radio Access Network (RAN) and core network. [Figure 37D] FIG. 37D is a system diagram of another example RAN and core network. [Figure 37E] FIG. 37E is a system diagram of another example RAN and core network. [Figure 37F]FIG. 37F is a block diagram of an exemplary computing system. [Figure 37G] FIG. 37G is a block diagram of another exemplary communication system. DETAILED DESCRIPTION OF THE INVENTION

[0007] A method and apparatus for prioritization within a transmitting UE is described herein. In the embodiments described herein, a user equipment (UE), a wireless communication device, and a wireless transmission The term Wireless Transmit / Receive Unit (WTRU) is used specifically to refer to 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 sex) CA: Carrier Aggregation CBG: Code Block Group CG: Configured Grant CNGTI: Code Block Group Transmission Index sex) 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 (Cus) 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 applications such as the Industrial Internet of Things (IIOT), multiple data The data streams can be generated by sensors or actuators. The data streams can be transmitted to the gNB through a common UE. The data streams are tuned for latency, reliability, and They differ in payload size, quality of service (QoS), etc. The network may have requirements for the gNB and UE to stream data according to those requirements. A simple example is when a UE is configured for eMBB and For example, a drone may have eMBB capability and support both URLLC operation. It may be necessary to support video transmission, but URLLC capability is not required to provide real-time status. PDSCH, PUSCH, and physical Physical Downlink Control Channel (PDCCH), It may be necessary to prioritize URLLC transmissions such as PUCCH.

[0010] There are several scenarios where resource conflicts between priorities require prioritization. The PUSCH grants are: Prioritization of H-grant within the UE, there is resource contention between CG and dynamic grants Prioritization within the UE of PUSCH when a PUSCH is Intra-UE PUSCH resource contention between dynamic high priority PUSCH grants Prioritization of UL control information when there is resource contention between control information transmissions of different priorities. Prioritization within the UE of information and control and data channels of different priority including, but not limited to, prioritization within the UE when there is resource contention between In addition, when a UE is configured with multiple CGs, the following scenarios are possible: Prioritization within the UE between multiple CG PUSCHs of priority may be considered.

[0011] 3rd Generation Partnership Project: In 3GPP) NR Release 15, group-wide PDCCH-based preemption is A DCI indicator (DCI in format 2_1 in INT-RNTI) was introduced, Indicate to a group of eMBB UEs that certain resources will be preempted in DL The UE selects a DCI form for the serving cell from the configured set of serving cells. If the UE detects the UE's 2_1, the UE determines that the transmission to the UE is From the set of symbols in the monitoring period, the PRB and and symbols. The set of PRBs is the active DL B Preempted resources are allocated at a coarse granularity (slot or Preemption can be indicated by 14 bits indicating the preemption status of the chunk. The affected resources are at most half the BWP or the entire BWP. Preemption indication in frequency is particularly important because it can be indicated even when the bandwidth is not reached. The preemption indication may be very coarse. If a service is affected by preemption, it may offer to flush its buffer. The UE will then report the affected soft bits or affected P bits in its HARQ buffer. It may stream soft bits / symbols from some other buffer that processes DSCH. For example, the HARQ buffer may already contain soft bits from a previous eMBB reception. The empty transmission is an eMBB retransmission. Soft combining of the retransmission with the previous transmission Typically, the UE first receives the signal into a receive buffer and then transmits the result to the HAR. Q Various operations on the received signal (e.g., F In this case, the HARQ soft bit buffer is used for However, the other intermediate buffer(s) containing the affected retransmissions need not be The locations where flushing occurs are therefore collectively referred to as buffers.

[0012] In 3GPP NR Release 16, preemption indication is considered for UL. and the eMBB UE has some of its resources preempted by URLLC transmissions. Therefore, eMBB UEs can transmit on those resources. You must not do that.

[0013] 3GPP NR Release 15 supports PUCCH resource sets and per-resource-set The UE can select the PUCCH resource configuration based on the payload of its UCI. Determines the PUCCH resource set and schedules the grant from DCI to PUCCH The spatial direction for PUCCH transmission may be determined. can be configured per PUCCH resource and is derived from a list of RRC-configured RSs that indicate beam support. It can be enabled by the MAC Control Element (CE) of the

[0014] 3GPP NR Release 15 supports semi-static codebooks for HARQ ACK transmission. and dynamic codebooks. The UE can be configured to use one of the codebooks. The semi-static codebook may have a fixed size. HARQ for all slots even if no grant for SCH is received It may transmit an ACK for that slot. It may transmit a NACK for that slot. Therefore, the payload may be large for semi-static codebooks. The block may have a variable size and is used for HARQ AC only for scheduled grants. The scheduling DCI can support the transmission of K codebooks. cDAI and tDAI are presented to the UE to indicate the number of scheduled grants. DAI is incremented every time a scheduling DCI is transmitted, while tDAI is incremented every time a scheduling DCI is transmitted. Maintain a count of the total number of DAIs in the codebook (including scheduling between carriers) If DCI is not received, the difference between cDAI and tDAI determines which DCI is present. Therefore, the UE may indicate that the scheduled PDSCH was not received. It may decide ambiguously and negatively acknowledge any DCI that was not received.

[0015] If the UE has a PUSCH transmission that overlaps with a particular PUCCH transmission, the UE Puncturing the SCH or dividing the PUSCH resources around the UCI resources By rate-matching the PUSCH, UCI can be piggybacked on the PUSCH. The encoded HARQ-ACK bits may be mapped immediately after the first DMRS. If the PUSCH uses frequency hopping, the HARQ-ACK modulation symbol is The encoded CSI bits may be split across the first non-PUSCH hops. The mapping may start from the DMRS symbol.

[0016] Multiple traffic types with different delay, reliability requirements, periodicity, and payload Multiple configured grants (CGs) can be supported for a single UE. The UE may be configured to support different traffic types and priorities.

[0017] 3GPP NR Release 15 introduced CG PUSCH. Can be configured (Type 1) or enabled / disabled through DCI (Type 2) The configured grant timer is started with the transmission of the HARQ process and This may prevent new transmissions for the same HARQ process. If not coded, the gNB shall provide dynamic grants for retransmissions in the CS-RNTI. Send to E.

[0018] Code Block Group (CBG) allows the UE to acknowledge TBs at a finer granularity. It was introduced in 3GPP NR Release 15 to allow transmission of / NACK. B is the Code Block Group Transmission Index (CBLG) in DCI. By indicating the CBG index through the CBGTI field. Therefore, retransmissions can be scheduled for a particular CBG.

[0019] The embodiments described herein address the issues associated with transmission of different priority levels. In the examples described herein, URLLC traffic is marked with a '0' to represent high priority transmission. may be used, and eMBB traffic may be used to represent low priority transmissions. However, the techniques described herein may be used when more than two priorities are supported by the UE. It can be applied to any type of transmission that can be performed.

[0020] Supports transmission of various priority levels to support various applications. Transmission priority may be identifiable at the MAC layer, but not at the physical layer. For example, it may be useful to allow for priority identification in the physical transmission. However, 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. When using URLLC, both eMBB and URLLC traffic can be transmitted. Collisions within the UE must be avoided to maintain service reliability and latency. Methods for determining UE behavior when occurring on DSCH are described herein.

[0022] HARQ ACK transmissions can be used for multiple priorities. The UE shall use the ACK / NACK for transmitting both colliding PDSCH grants. HARQ codebooks have different reliability and delay requirements. This can be extended to support UCI for transmission in the PUSCH. When subscribed, the priority levels of the UCI and PUSCH may be taken into consideration.

[0023] A procedure for handling intra-UE prioritization of PUSCH grants is provided herein. For example, between dynamic grants or high priority configured grants, When there is intra-UE collision and dynamic grants occur, the UE procedures described herein The MAC layer procedure for prioritization within the UE is E is described herein to allow prioritization to be resolved at the MAC layer.

[0024] According to one embodiment, the gNB may receive the RNTI, the DCI length, the fields in the DCI, the PD CCH resources, grant duration, through DCI. The UE may specify the RNTI used for PUSCH data or PUCCH. In case of preemption within the UE, the priority of the preemption When the preemption indicator is not received, the UE shall preempt the high priority PDSCH. The preemption in the UE may drain the resources of the low priority buffer. In this case, when a preemption indicator is received, the UE The RNTI of the indicator may be used to determine the priority of the buffer to be streamed. ARQ ACK codebooks can be supported for multiple priorities. The ring may configure the UE with the codebook to be used for each priority. Q ACK codebooks can be transmitted in slots. Each codebook is a sub-codebook for a slot. A sub-slot can be transmitted at a finer granularity by the K1 parameter. Alternatively, an additional field K1a may be indicated, which indicates the sub-slot offset within the slot. If multiple dynamic codebooks are configured, the UE uses the cDAI, tDAI, and priority indication for the PDSCH grant For multiple TRP transmissions, the UE may determine the codebook to which the ACK / NACK belongs. may transmit HARQ ACK feedback to each TRP with different codebooks. The ORESET DMRS or another configured RS is used for PUCCH transmission in the spatial direction. The UE may override the spatial direction configured through the MAC CE, Space indicated by CORESET or configured RS for transmitting PUCCH Multiple HARQ ACK codebooks may be piggybacked on the PUSCH transmission. Each codebook is mapped to one sub-slot of the PUSCH. Different codebooks carrying UCI with different priorities result in different PUSCH transmissions. A beta offset value of 0 can be used to piggyback on the PUSCH. It can also support removing reserved UCI resources. A CG group with higher priority can be mapped to multiple repetitions of a PUSCH transmission. If the HARQ process ID of the runt collides with that of a lower priority dynamic grant, When multiple CG grants collide at a UE, the UE may ignore the low priority grant. , the UE may retransmit the preempted CG grant on the CG resource. E PUSCH repetitions are timer-based with early termination acknowledged by one TRP. It may be subject to termination, or selective termination depending on which TRP acknowledged the transmission.

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

[0026] PHY layer identification of grant priority is described herein. or scheduled or configured to transmit PUSCH or PUCCH. However, the gNB may override that transmission with a higher priority transmission. For example, the eMBB PDSCH may be transmitted over the URLLC PDSCH for that UE. In another example, the eMBB PUSCH may be preempted by URLLC PUCCH can be preempted by eMBB PUSCH. If there is enough time to react to the grant, the UE MA The C layer may prioritize higher priority transmissions, and the MAC may deliver the prioritized transmissions to the UE and On the UL, the UE may cancel a transmission of a lower priority if the UE has already started a transmission at the PHY layer. If so, it identifies that another transmission may be more important and stops the lower priority transmission. For this purpose, the PHY layer recognizes the priority of the transmission. For example, it may be desirable to have a DL PDSCH grant priority of PH Y, the UE shall accordingly prioritize that HA over other lower priority UL transmissions. The UE may prioritize RQ-ACK UCI transmissions through one of the following methods: It may be useful to show

[0027] The RNTI is used to scramble the DCI in the grant to indicate priority to the UE. If eMBB and URLLC are the only two priority levels, The RNTI indicating MCS for reliability (MCS-C-RNTI) is used to indicate URLLC. However, multiple priorities, such as priorities within the URLLC itself, are supported. If supported, multiple RNTIs may be used to indicate priority. As shown in the example in Table 1, UEs can be configured with different RNTIs and their relative priority levels. A priority level of "0" may correspond to the lowest priority, and the priority may be The number increases in ascending order.

[0028] [Table 1]

[0029] The example RNTI shown in Table 1 may be used to mask the UE's C-RNTI Upon receiving the grant, the UE performs DCI masking for all possible masked RNTIs. and select the one that the CRC passes.

[0030] For dynamic grants, the RNTI is obtained by blindly decoding the DCI. E, and C-RNTI (Equation 1 below) can be given by RNTIp where RNTIp can be a masked RNTI from Table 1 with priority level p In these examples, the RNTI mask may generally be configured for multiple UEs. This can occur through SI or in a UE specific manner, and multiple UEs may have the same priority for different priorities. It may consist of the same RNTIp value.

[0031]

number

[0032] In one example, instead of a mask, the gNB may use multiple C-RNs for multiple priority levels. The UE may be provided with a TI (C-RNTI1, C-RNTI2, etc.). The configuration is UE specific. It can be carried out in a manner.

[0033] Alternatively or additionally, the RNTI may be transmitted to multiple UEs via a group-common PDCCH. It can be provided.

[0034] For Type 1UL configured grants, the priority level for the grant is R For example, to distinguish between different configured grants, If the configured grant is given the ID "configured grant ID", the ID is used to For a particular application, multiple configured grants may be For example, in NR-U applications, ,Traffic with a particular priority may be given multiple configured grants, U 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 enabling DCI is based on the target priority in Table 1. The enabling DCI may use the CS-RNTI masked with the RNTI of the CS- The RNTI may be scrambled using the RNTIp in Equation 1 above. The CI may also use the CS-RNTI masked with the RNTIp. This is especially important for Preferred when the priority level and configured grant ID can be the same for grants. Alternatively or additionally, the invalidation DCI may be , the grant to the UE may be revoked, which simplifies the procedure and improves the robustness of the revoked DCI. The UE will use the configured grant ID to invalidate the Type 2 grant. Decide to enable it.

[0036] Figure 1 shows that the priority of a configured grant can be changed by another enabling DCI. FIG. 1 shows a PDCCH 51, other signals 52, and gaps 55. Figure 1 also shows that for priority level 2, CS-RNTI (Equation 1 above) is used to calculate RNTI2. CS for priority level 4 and enabled DCI 56, which can be scrambled using -RNTI” Equation 1 above “RNTI4” is used to scramble the enabled DC PUSCH 53 contains configured grants with priority level 2. , PUSCH 54 contains configured grants with priority level 4. Alternatively, Additionally, the MAC CE from the gNB is used to set the priority level to the UE. It is possible.

[0037] An explicit field "priority level" in the DCI may indicate the priority of the grant.

[0038] The DCI length for a grant may indicate the priority of the grant. Although DCI lengths can be used for URLLC, more DCI lengths can be used with this method. It needs to be defined to support multiple levels of advancement.

[0039] One or more characteristics of the PDCCH, such as the starting PRB of the CCE of the DCI, may be determined by the priority level. For example, (starting PRB mod priority level max) indicates the maximum priority level for a grant. The priority level of the PDCCH may be set. The starting symbol of the PDCCH may indicate the priority. The aggregation level (AL) of the CH may indicate the priority, and the UR As LLC DCI may require higher priority, it may be more A higher AL may be used. ref,p The set of reference ALs, denoted as ", is If the received AL is within that set, the UE will The PDCCH may be identified as belonging to a priority level p.

[0040] HARQ processes can be configured for specific priority levels. For UEs with HARQ-ACK, this is because the typical delay for HARQ-ACK may be small. Therefore, most HARQ processes are suitable for the URLLC case. may not need to be supported.

[0041] The number of resources in a grant may indicate a priority level, e.g., 2OS vs. 4OS. PUSCH transmissions in minislots of length 10OS may have the highest priority, while PUSCH transmissions in minislots of length 10OS may have the highest priority. PUSCH transmissions in minislots with lengths between 0 and 14OS may indicate the lowest priority. The time resource ranges and the corresponding priority list are indicated to the UE through RRC signaling. Upon receiving the grant, the UE may prioritize the amount of time resources available to it. The MCS of a grant may indicate a priority level, requiring higher reliability. A higher priority transmission may have an MCS value with a lower spectral efficiency.

[0042] The gNB may configure multiple DMRS sequences to the UE corresponding to different priority levels. When the UE receives the PDSCH grant, it detects the DMRS sequence of the PDSCH. For example, the RNTI mask may be used to identify different priority levels. The DMRS sequence may be used to generate a DMRS sequence for the

[0043] The arrival time of the DCI may determine the priority level. The latest DCI may be of higher priority. This may represent a DCI, however, this may not apply to all scenarios. For example, in some scenarios, the UE may receive DL signals / channels from multiple TRPs in a cell. and / or transmit UL signals / channels in a cell to multiple TRPs. In the multiple TRP case, one TRP may provide the eMBB grant. P may provide a URLLC grant. The eMBB grant is provided after the URLLC grant. However, the PDSCH resources may collide, resulting in intra-UE collisions. In this case, the most recent DCI may not be a good indicator of priority.

[0044] The priority of the UCI may be mapped to the priority of the grant. For example, If a HARQ ACK feedback has a priority level p, then the HARQ ACK feedback has a priority p. Periodic CSI reporting is performed by reporting to a BLER target for a particular priority. Even in the corresponding case, the lower priority level p configured by the gNB low to UE This means that periodic CSI reports generally have a lower priority than most transmissions. All periodic CSI (for eMBB and URLLC) The reports may be transmitted with the same periodicity. However, between the periodic CSI reports of the two priorities, In the event of a collision, a report on a higher priority BLER may take precedence, and a report on a lower priority BLER may take precedence. The report of the BLER of the corresponding trough may be dropped. It may be transmitted at the priority level of the packet, with the priority indicated by the DCI that schedules it. Priority levels may be used.

[0045] It is useful to indicate the priority of UL transmissions such as PUSCH or PUCCH in a transmission. For example, the UE may send ACK / NACK to URLLC and eM with separate codebooks. BB PDSCH, so that the delay and reliability for each priority are Each is achieved through appropriate scheduling and coding rate of PUCCH. PUCCH HARQ-ACK resources are shared by both URLLC and eMBB. It can be used as follows.

[0046] Figure 2 shows the PUSCH and PUCCH where the C-RNTI is masked with the priority level RNTI. 2 shows an example CH 200. The UE uses the UL UCI to scramble the The priority is indicated through RNTI (=C-RNTI) in the above formula 1 "RNTIp". gNB uses RNTI to know the priority level at which the PUCCH HARQ-ACK was received. FIG. 2 shows a PDCCH 201, other signals 206, and gaps 205. Figure 2 also shows the DC signal in slot #0 scrambled with the mask RNTIp1. I 210 indicates to schedule PUSCH0 203 in slot #2. The USCH may also be transmitted with a priority level mask RNTIp1 203. DCI scrambled in TIp1 schedules PDSCH0 in slot #1. The corresponding PUCCH may be transmitted on slot #3 (220). , UCI may be scrambled with a mask in RNTIp2 204.

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

[0048] FIG. 3A illustrates a high priority PDSCH with resource element (RE) collisions between PDSCHs. An example 300 of preemption in a UE for a low priority PDSCH is shown in FIG. PDCCH3 for slot #0 312 to slot #2 313 for 14 01, PDSCH eMBB 302, PDSCH URLLC 303, and other signals 304 In the example of FIG. 3A, a low-priority PDSCH eMBB is triggered by DCI on slot #0. 310) for slot #2. CI transmits high priority URLLC PDSCH in slot #2. URLLC Schedule (311). As a result, resources collide for the PDSCH.

[0049] Figure 3B shows the PDSCH eMBB and PDSCH URLLC When there is no frequency conflict Preemption in UE of lower priority PDSCH by higher priority PDSCH when overlapping between FIG. 3B shows an example of a slot #2 to slot #3 on frequency 324. #0 322, PDCCH305, PDSCH eMBB306, PDSCH U RLLC 3B shows a low priority PDSCH 307, and other signals 308. In the example of FIG. e MBB can be scheduled for slot #2 by DCI in slot #0 ( 320). Then, the DCI in slot #2 sends a high priority URLLC P DSCH URLLC The UE processes both PDSCHs. If the UE has the capability to do so, it may do so. Otherwise, the UE may eMB B It can be assumed that the PDSCH URLLC has been preempted by its own PDSCH URLLC.

[0050] Figure 4A shows the PDSCH URLLC FIG. 4A shows an example 400 of preemption by , PDCCH 401, PDSCH for slot 410 on frequency 411 eM BB 402 and 403, and UE1PDSCH URLLC Shows 404. If the preemption is entirely intra-UE, i.e., other UEs are not affected, If the gNB receives a BERT signal, the gNB may use the INT-RNTI for scrambling. Send a preemption indication over the group-wide DCI in format 2_1. In this case, UE1 does not need to When recognizing resources, it can identify DL preemption. UE1 can use the low priority PDS In its respective buffer for CH, the soft bits corresponding to the affected RE are automatically flush.

[0051] Figure 4B shows the PDSCH URLLC Figure 4B shows another example of preemption by PDCCH 405, PDSCH for slot 420 on frequency 421 eMB B 406 and 407, and UE1PDSCH URLLC 408. In this example The preempted resources may include resources from other UEs, where: The eMBB PDSCH 406 of UE2 may be preempted. In this case, the gNB , may transmit a preemption indication to the UE. For example, the indication may be Transmitted via group-wide DCI in format 2_1 using INT-RNTI When UE1 receives a preemption indication, it may However, in this case, it is the high priority buffer. Instead, UE1 should only stream low priority buffers. may use one of the following pieces of information: (1) UE1 assumes that the most recent transmission (PDSCH1) is of higher priority. To obtain the PDSCH0, the buffer corresponding to the transmission received earlier in time (PDSCH0) is streamed. possible.

[0052] UE1 uses the priority level information in the grant to select a higher priority HARQ process. The FIFO may decide to stream buffers at a lower priority.

[0053] FIG. 5 shows the UE with intra-UE collisions for low-priority PDSCH and high-priority PDSCH. 5 shows an example procedure 500 for flushing low priority HARQ buffers. When the loss begins (step 501), the UE checks for PDSCH collisions within the UE. The UE may monitor (step 502) whether there is an intra-UE collision of the PDSCH. If no PDSCH intra-UE collision is detected, the UE may: If a PDSCH intra-UE collision is detected, the UE may return to step 502. It may be determined whether an emption indication has been received for the conflicting resource (step Step 504). Regarding preemption within the UE, which grant has higher priority? UE specific buffers that indicate which resources are used and which resources are diverted for lower priority buffers A preemption indication may be sent by the gNB to the UE. The DCI may carry a set of priorities in its payload, for which the UE may A buffer may be flushed if its resources experience preemption. If a preemption indication is received for a conflicting resource, the UE shall A lower priority buffer may be streamed using the resource indicated by the indicator (step 5 05). If no preemption indication is received for the conflicting resource, U E is the number of soft bits in the lower priority buffers affected by the high priority PDSCH. The procedure then ends (step 507). In an alternative procedure, the UE may receive a preemption request (due to the arrival of conflicting grants) within the UE. If the UE detects both the preemption and preemption indicators, it The PDSCH may ignore the PDSCH interruption indicator, which is overridden by the higher priority PDSCH. Only the lower priority PDSCH bits are transmitted in the RE that was preempted. obtain.

[0054] FIG. 6 shows an example 600 of a UE preempting the PDSCH of another UE. , PDCCH 601, UE1 PDSC for slot 610 on frequency 611 H Priority level 1 602, UE0 PDSCH Priority level 0 603, UE2 PDSC UE3 PDSCH priority level 2 605, and UE3 PDSCH priority level 3 604. When several priority levels can be supported by the UE, the priority that must be passed For example, if UE2 has priority level=2 605, Consider that UE1 has a PDSCH transmission with priority level 1 602 and preempts certain resources of UE0 with priority level=0 603. However, it is possible that the priority of UE3 is higher than that of UE2. E3 priority level=3 604 resources are not preempted.

[0055] Format 2_1DCI provides, at a coarse level, the affected RE in time and frequency. However, the indication is that UE3 resources may not be preempted. Therefore, according to the Release 15 procedure, UE0, UE UE0, UE1, and UE3 can all stream their buffers. However, the intention is that UE0 and UE1 only streams its buffers without affecting UE3's buffers. To this end, in the embodiments described herein, the INT- The RNTI can be masked with a priority level mask. Preemption indicator DC A UE receiving I can detect the mask and determine the priority level to stream. , the gNB transmits DCI with a mask of RNTI1. Therefore, the UE receives DCI with priority level It can be seen that if we have ≤ 1 then we must flush the buffer. , UE0 and UE1 only flush their buffers, UE3 does not flush its buffer.

[0056] Figure 7 shows the RNTI p UE to stream soft buffers of priority indicated through mask 7 illustrates an example procedure 700 for use in a UE with a priority Level <= Receive priority indication via preemption indicator, affected buffer When the procedure starts (step 701), the UE The UE may monitor for an indicator (step 702). It may be determined whether a reemption indication has been received (step 703). If a preemption indication is received indicating priority level p, the UE shall The buffer may be streamed on all preempted resources (step 704). If a preemption indication indicating level p is not received, the UE proceeds to step 702. The procedure then ends (step 705).

[0057] Alternatively or additionally, the UE may preempt other UEs via a preemption indicator. It may indicate the priority level of the transmission it is preempting. U has a preempted resource with a lower priority than the priority indicated by E flushes the buffer.

[0058] Procedures for high priority and low priority control signaling are described herein. In general, high priority transmissions may be prioritized over low priority transmissions. The UE may may cancel or puncture lower priority transmissions to support Scenarios may be supported, including but not limited to: (1) The UE prioritizes the high-priority PUSCH and drops the low-priority PUCCH. (2) The UE prioritizes the high-priority PUCCH and drops the low-priority PUSCH. (3) The UE prioritizes high-priority UCIs and drops low-priority UCIs. (4) The UE prioritizes the high priority PUCCH and drops the low priority PUCCH. (5) The UE prioritizes the high-priority PUSCH and drops the low-priority PUSCH.

[0059] Other methods for accepting transmissions at different priorities are also supported, as described below. It can be ported.

[0060] Multiple PUCCH transmission opportunities in a slot are described herein. M (M It may be desirable to provide UCI feedback opportunities (≥ 1). The larger the number of feedback opportunities in a slot, the greater the number of UCI transmissions in a slot. The time resource for each opportunity can be referred to as a sub-slot. A number of slots may be supported for UCI transmission in a slot.

[0061] Figure 8A shows the HARQ-ACK UC on PUCCH with single UCI feedback. FIG. 8A shows an example of a PDCCH 801, PDCCH 802, PDCCH 803, PDCCH 804, PDCCH 805, PDCCH 806, PDCCH 807, PDCCH 808, PDCCH 809, PDCCH 810, PDCCH 811, PDCCH 812, PDCCH 813, PDCCH 814, PDCCH 8 DSCH0K1=4 PRI=0 802, PDSCH1K1=3 PRI=1 8 03, PDSCH2K1=4 PRI=0 804, PDSCH3K1=2 PRI <1 808, PUCCH 01 PRI=1 807, PUCCH 23 PRI=1 8 8A shows the DL signal 810, the UL signal 805, and the gap 806. As shown in the figure, HARQ-ACK for multiple PDSCHs is sent only once in a slot. ARQ codebooks, where PDSCH0802 and PDS For ACK / NACK on CH1803, the corresponding K1 value is added to the UCI feedback. Regarding slot #4, PUCCH 01 807, PRI=1 can be used so that the PRI is from the latest scheduling DCI. ACK / NACK for DSCH2804 and PDSCH3808 is PUCCH, so that a value of 1 represents slot #5 for UCI feedback 23 80 9.

[0062] FIG. 8B shows the HAR over PUCCH with multiple UCI feedback opportunities in a slot. FIG. 8B shows an example of a Q-ACK UCI transmission. PDCCH811, PDSCH0812, PDS CH1813, PDSCH2814, PDSCH3815, PUCCH 01 819, PU CCH 23 820, other UL signals 816, and gaps 817. As shown in FIG. As such, multiple opportunities can be provided for UCI feedback in slots. Here, two PUCCH transmissions can be supported in a slot (M=2). It can be received in the 2OS minislot 813 on PDSCH0 and PDSCH1. The ACK / NACK for this is PUCCH #6, #7 in slot #1. 01 819 , while for PDSCH2 and PDSCH3, ACK / NACK is sent in slot #1 823 on PUCCH #12, 13. 23 820 may be transmitted in subslot #2.

[0063] The number of subslots may be configured to the UE by the gNB through RRC signaling. Furthermore, sub-slots can support different types of traffic, their priorities, and delays. The gNB allocates the sub-slots in a non-overlapping manner to the U E, so that there may be no collisions between transmissions on a sub-slot. The gNB may configure the UE with sub-slots with overlapping resources. If it identifies that a subslot can be scheduled to transmit on that subslot, A lower priority transmission may be dropped, or a later sub-slot may be dropped. or the previous sub-0 slot may be dropped.

[0064] The following method shall be used for PUCCH transmission when subslots M>1: can be used to indicate If M subslots can be allowed for PUCCH transmission, K1 is the number of subslots The number of subslots per slot can be configured for each priority level. K1 can be interpreted accordingly for each priority level, so that The level interprets K1 according to the number of subslots configured in it per slot. This configuration may be provided to the UE through RRC signaling. Table 2 below shows how K1 An example of how this can be configured for different numbers of sub-slots per slot is shown below. give.

[0065] Figure 9A shows the time slots incremented by one sub-slot per slot and in units of slots. Example Subslot Configuration 900 with eMBB PDSCH Configured for K1 FIG. 9A shows a PDCCH 901, a gap 905, and a PDSCH 902 with K1=2. and PDSCH1903 with K1=1 and PUCCH 01 904, and a plurality of slots (e.g., slot #0 910 and slot #2 911). PDSCH0902 and PDSCH1903 with K1=1 are in slot #2 911, They can be jointly recognized.

[0066] Figure 9B shows two sub-slots per slot and half-slot increments. Another exemplary subslot with URLLC PDSCH configured for K1 FIG. 9B shows a sub-slot configuration with multiple slots, namely sub-slot 0 930 and sub-slot 1 931. Slot #0 936 with subslot 1 931, subslot 0 932 and subslot Slot #1 937 with sub-slot 1 933, and sub-slot 0 934 and slot #2 938 with sub-slot 1 935. FIG. 9B also shows P DCCH 920, Gap 925, Other signals 926, PDSCH 0921 with K1=3, K PDSCH1939 with 1=2, PDSCH2922 with K1=2, PUCCH 01 923, In the example of FIG. 9B, DSCH0 with K1=3 and PUCCH2 with K1= Two PDSCHs 1 may be jointly acknowledged in subslot #1 of slot #1; and , PDSCH2 in sub-slot #0 of slot #1 with K1=2 is It can be seen in slot #0.

[0067] FIG. 10 shows the K1 10 shows a PDS with PDCCH 1001, gap 1005, and K1=4. CH01002, PDSCH11003 with K1=2, and PUCCH 01 1004 and, 1010 and slot #2 1011. 1) PDSCH01002 with K1=4 and PDSCH11003 with K1=2 are , slot #2 1011. In this alternative, K1 is the finest It can be interpreted according to granularity, i.e. according to the maximum number of sub-slots per slot. The UE may decide 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 a UE can be two. The eMBB user increments K1 by the maximum number of sub-slots per slot, assuming Therefore, only K1 values ​​such as 2, 4, 6, etc. are used for slots for eMBB. This may be useful for eMBB as an indication of PUCCH resources for the

[0068] [Table 2]

[0069] In FIG. 11, K1 indicates a slot for PUCCH and K1a indicates a sub-slot. FIG. 11 shows an example 1100 of a plurality of slots, namely sub-slots 0 1110 and Slot #0 1116 with subslot 0 1111 and subslot 1 1111 Slot #1 1117 with slot 12 and sub-slot 1 1113, and sub-slot Slot #2 1118 with slot 0 1114 and subslot 1 1115 FIG. 11 also shows the PDCCH 1101, gap 1108, other signals 1107, K1 PDSCH01102 with K1=1 and K1a=1, PDSCH with K1=1 and K1a=1 11103, PDSCH with K1=1 and K1a=0 21104, PUCCH 01 110 5, and PUCCH21106. Additional bits are used to indicate sub-channels for PUCCH. A field "K1a" may be introduced in the scheduling DCI to indicate the slot. K1 may be incremented with respect to a slot, and K1a may be an offset in the number of subslots within a slot. In FIG. 11, K1 indicates the slot offset, and K1a indicates the PUC This indicates the sub-slot offset within that slot for the CH resource. M=2 subslots per every slot.

[0070] HARQ codebooks for different priority transmissions are described herein. , the HARQ ACK bits for different priorities are jointly encoded, or If it is encoded separately, it may determine whether the different components are encoded separately. The hardware can be used for different priority levels. The gNB can then use RRC signaling. For example, eMBB may indicate the codebook type for each priority level through The transmission may use a semi-static codebook, while URLLC uses a dynamic codebook. The overhead in the UCI can be lower and the smaller payload can be used Dynamic codebooks are used in URLLC because they can be transmitted reliably and with fewer resources. It is also expected that URLLC HARQ-ACK can be transmitted with low delay. Therefore, many PDSCHs do not have to be multiplexed on the same PUCCH. For this reason, semi-static codebooks are particularly useful for URLLC traffic, which can be bursty. In some cases, it may not be necessary.

[0071] Separate PUCCH resource sets for different priorities or in each resource set It may be desirable to configure additional PUCCH resources for eMBB transmissions. traffic may have PUCCH resources in the last symbol of the slot, while U RLLC allocates slots containing resources at the first symbols of a slot to minimize delay. RRC signaling may require multiple PUCCH resources in a PUCCH Recognition through resource set and PUCCH resources in PUCCH resource set The priority level of the PDSCH that may be transmitted may be configured.

[0072] If the PUCCH resource sets are different for different priority levels, A separate codebook for Q-ACK may be used. If the priority levels of two transmissions can be the same, the HARQ-ACK is They can be jointly encoded and transmitted in one codebook, or in separate codebooks. Whether HARQ-ACKs with different priorities can be transmitted jointly is unclear. This behavior can be configured in the UE by the gNB through RRC signaling.

[0073] Figure 12 shows separate HARQ for p=0 (eMBB) and p=1 (URLLC). An example ACK codebook 1200 is shown in FIG. 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 signals 1206, PUCCG 1207, and Figure 1 shows PUCCH 1210. Multiple dynamic codebooks are used for multiple priority levels. If used, counters cDAI and tDAI are defined separately for each priority level. The codebook for priority level p can be calculated using the parameters cDAIp and tDAIp The dynamic codebooks cDAIp and tDAIp can be determined using scheduling DCI, and p is the DCI (through one of the methods described above). Or it can be determined by the UE from the priority level embedded in the PDCCH. Thus, the UE may prepare a codebook for transmission for priority level p. In this example, the cDAI and tDAI values ​​are The eMBB PDCCH is incremented by PUCC in slot #3 1217. H1210 resources, so that those HARQ-ACKs are The packets may be combined in a book and transmitted on the PUCCH 1210 in slot #3 1217. The URLLC PDCCH may indicate PUCCH resources in slot #1 1215, RLLC HARQ-ACK is combined into one codebook and stored in slot #1 120 7, can be transmitted on the PUCCH. If tDAI and cDAI are shared between priorities, In this case, the codebooks cannot be easily separated. This is because DCI is overlooked. If so, the difference between cDAI and tDAI indicates that, but the UE does not It is not possible to determine whether the scheduling of MBB transmissions has been overlooked, and therefore to detect the overlooked PDSCH in the eMBB codebook or URLLC codebook. This is because it does not know whether a negative response will be given.

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

[0075] Multiple TRP PUCCH transmissions are described herein. Supports multiple TRP transmissions When the first TRP is received, the UE receives the first PDCCH and the corresponding first PDSCH. and receiving a second PDCCH and a corresponding second PDSCH from the second TRP. The time-frequency resources for the first and second PDSCHs are either overlapping or They may be non-overlapping or partially overlapping. For example, PDSCHs may be in the same slot or The PDSCH may be received in different slots, for example, overlapping PRBs or overlapping PRBs. may not be received on a PRB.

[0076] In some scenarios, the UE may receive a PDS with a first set of layers originating from a first TRP. A second set of layers may receive a PDSCH originating from a second TRP. In this case, the first and second sets of layers carry different codewords or transport blocks. In another example, a single codeword or transport block may be used for the first and second and a second set of layers.

[0077] Signals / channels transmitted / received from / to different TRPs in a cell are different applications, and thereby different priority levels. For example, a macro TRP may be selected as the U because it has the best connection to the core network. It can be used for RLLC, while for UE locations with non-ideal backhaul. A nearby low power TRP may be used for eMBB traffic.

[0078] Figure 13 shows an example 1300 of a UE transmitting to multiple TRPs. PDCCH1310, GAP1311, and PUCCH1312 and 1 in 14 UE 1303 transmits PUCCH 1312 of UCI0 on beam B0 1304. Transmit to TRP01301 of UCI1 and PUCCH1313 of UCI1 on beam B11305 The UE 1303 transmits a separate UCI to each TRP 1301 and Each UCI may be provided to 1302. Each UCI corresponds to a particular TRP (e.g., the first or second CSI report (corresponding to the PDSCH of the second layer or the first or second set of PDSCH) As a result, the UE 1303 can receive P UCCHs 1312 and 1313 may be transmitted to the respective TRPs 1301 and 1302. In other words, for PUCCH transmission corresponding to QCL with DL RS or UL RS: The beams may be different for each TRP.

[0079] Figure 14 shows an example 1400 of PUCCH transmission to multiple TRPs. H 1405, Gap 1409, Other Signals 1408, TRP in Slot #0 1420 i PDSCH01406 with K1=4 and PRI=0 transmitted by TRP j By PDSCH11407 with K1=2 and PRI=1 transmitted by 01410, and PUCCH UCI11411. Since the PUCCH resource may be different for each UCI, a different PUCCH resource may be allocated for each PUCCH resource. The values ​​shown for UCI0 and UCI1 are used to identify sources in specific spatial directions. As shown in FIG. 14, UCI0 and UCI1 are respectively and transmitted on PUCCH1411.

[0080] Figure 14 also shows the TRP i and TRP j are PRI=0 and PRI=1, respectively. PDSCH01406 and PDSCH11 on beams B01401 and B11402 407 to the UE. The UE transmits the beam on PUCCH 1410 of UCI0. Responds to TRP0 in slot #2 1421 on B01403 and PUCCH1 on UCI1 411 responds to TRP1 in slot #3 on beam B1 1404. P with PRI=0 UCCH resources may be configured for transmission on beam B01403, with PRI=1. The source may be configured for transmission on beam B 11404. This configuration in the inter-direction can be done through MAC CE enablement. Multiple TRPs are supported. If so, multiple PUCCH resources are configured for different spatial directions.

[0081] To overcome the activation overhead, the following alternatives can be considered: The UE The TRP recognition may be configured to use spatial orientation based on SSB or can be expressed in the form of a spatial relationship to the CSI-RS or UL SRS. For example, T The recognition of RP can be linked to CORESET. For example, TRPi can be linked to CORESET. T i Then, CORESET i The TCI configuration of TRP i In this case, the UE may indicate the spatial direction to be used for the PUCCH for the MA. CCE-enabled spatial direction can be ignored. Instead, it focuses on TRP recognition and corresponding The spatial direction may be used.

[0082] Figure 15 shows an example 1500 of PUCCH spatial direction based on TRP recognition. DCCH 1509, Gap 1511, Other Signals 1510, Slot #0 1520 TRP i PDSCH01506 with K1=4 and PRI=0 transmitted by TRP j PDSCH 11508 with K1=2 and PRI=1 transmitted by, slot #2 PUCCH UCI01512 and PUCCH UCI1151 in 1521 3. FIG. 15 shows the CORESET transmitted on the PDCCH 1505. i is TRP i Two This shows the cases where TRP can be configured. i can be scheduled on a PDSCH with PRI=0. However, UE is i Beam B01501 can be used for CORESET. j teeth , transmitted on PDCCH1507, TRP j TRP j PRI = 0, but the UE may be scheduled on a PDSCH with TRP j About Beam B1150 2. As another alternative, instead of using the TCI state of CORESET, S SB or spatial direction based on CSI-RS or SRS, higher layer signaling A TRP may be assigned to the UE for each TRP via

[0083] Note that TRP recognition does not have to be explicitly used in any configuration information. Alternatively, the TRPs can be indirectly identified through spatial orientation. Can the spatial direction for be explicitly configured via DL RS or UL RS? , or on the DL channel, for example, CORESET as described above i , different PDSCH connected to the TCI state of the transmission, or to different TCI states of different layers of the PDSCH transmission. obtain.

[0084] UCI on PUSCH is described herein. Piggybacking on low priority PUSCH The high priority UCI for URLLC is described herein. When overlapping with the PUSCH for BB, the URLLC UCI is used for the eMBB PUSC. It is proposed that M>1 can be piggybacked on H. Therefore, multiple instances or codebooks of UCI can be piggybacked on the PUSCH. It can be backed up.

[0085] Figure 16 shows the case where multiple HARQ ACK codebooks are used on a single PUSCH in a slot. FIG. 16 shows an example of a PDCCH 1601, a gap 1602, and a 7, and other signals 1602. eMBB PUSCH 1608 is shown in slot #3 1623. URLLC PDSCH 1603, 1604, 1605 and 1606 are in slot #1 1621 and slot #2 1622 For PDSCH0 and PDSCH1 (denoted as UCI0), All ACK / NACKs 1609 are sent in the first half of slot #3 (subslot #0 16 24), which can be jointly encoded and transmitted, while PDSC (denoted as UCI1) ACK / NACK 1610 for H2 and PDSCH3 occurs in the second half of slot #3. The 1625 subslots may be jointly encoded and transmitted in the same time slot (subslot #1 1625).

[0086] eMBB PUSCH requires rate matching or puncturing to accommodate UCI. Depending on the UE capabilities and delay in processing the PDSCH, this may include: A method for mapping UCI0 and UCI1 on the PUSCH includes, but is not limited to, It can be used for (1) PUSCH is punctured to allow mapping of UCI0 and UCI1. It can be cha. (2) PUSCH is rate-mapped around the resources for UCI0 and UCI1. It can be checked. (3) The PUSCH may be rate-matched around the resources for UCI0; In this case, the PUSCH can be punctured by the resources for UCI1. The delay is sufficient to allow it to be rate matched to accommodate UCI1. It may be applicable when there is no

[0087] A similar principle can be applied to UCI carrying CSI. If multiple UCI measurements and reports are required, the reports will be based on UCI 0 and 1 in Figure 16. Like UCI1, it can be piggybacked on PUSCH.

[0088] Alternatively, some instances of UCI transmission on a slot may be HARQ ACKs. , while other instances may carry only CSI. For example, UCI0 is HARQ. -ACK, while UCI1 may contain a CSI report.

[0089] Alternatively, the M UCI feedback opportunities in a slot may be HARQ-ACK and It may carry both the CSI and the CSI.

[0090] The number of REs for a UCI is determined by the DCI or higher layer that schedules the PUSCH. The beta offset factor that can be indicated through signaling is expressed as follows: The beta offset factor can be determined by Equation 3 and Equation 4 below. The UE supports each supported priority of UCI. It is proposed herein that the offsets should be configured with different sets of offsets for the The m-th signaling opportunity for UCI on the PUSCH is m Represented by For example, in FIG. 16, m=0 and m=1 can be supported. It consists of the values ​​of Equation 5 below, Equation 6 below, and Equation 7 below for each opportunity. It is proposed herein that this should be done. It provides gNBs with greater flexibility in configuring their reliability. The configuration can be tailored to higher tiers or A field indicating a beta offset may occur through DCI scheduling a PUSCH. The code can be configured in one of the following ways: (1) A 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. and in some cases 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 change when m changes. In this case, the beta offset The bit indicator indicates the offset index for each of the m opportunities. is shown in Table 3. Here, the UE calculates the four values ​​of Equation 8 for each of the m opportunities. Equation 9 below is the basis for Equation 10 below. It can be an index into a table of offset values, where i is the number of pairs of the target UCI. For example, i=0 indicates that the UE sends up to two HARQ-ACK information bits. i=1 indicates that the UE receives more than two HARQ-ACK information, up to a maximum of 11. i=2 indicates that the UE receives more than 11 bits of HARQ-ACK. DCI represents the case where many bits are multiplexed. DCI is a base that indicates the sequence of offsets used. It carries two bits of the data offset indicator. Equation 11 below shows how to provide greater reliability for URLLC UCI by using e It can be larger than Equation 12 below for MBB UCI.

[0098]

number

[0099]

number

[0100]

number

[0101]

number

[0102]

number

[0103] [Table 3]

[0104] If PUSCH hopping is configured for the UE, UCI m eMBB PUS This means that the UCI can be mapped to each hop of the PUSCH. This may differ from other systems in that the data may be partitioned and mapped.

[0105] Figure 17 shows the UCI on different hops of the PUSCH. m An example of a mapping 1700 is shown. 17 is a PDCCH 1701, a gap in slot 1710 on frequency 1711. As can be seen in the example in Figure 17, eMBB PUSCH is transmitted over two hops. ACK-NACK 1707 for PDSCH0 and PDSCH1, if configured The UCI 1703 including the PDSCH 1704 may be transmitted on hop 1 of the PUSCH 1704. UCI11706 containing ACK-NACK1708 for 2 and PDSCH3 It can be transmitted on hop 2 of PUSCH 1705.

[0106] Only a single HARQ-ACK codebook is required to be mapped on the PUSCH. If M=1, the encoding, rate matching, and modulation are The URLLC UCI vector is split across both eMBB PUSCH hops. FIG. 18 shows how UCI0 can be divided and mapped over the hops of the PUSCH. This configuration is suitable for cases where the delay from later hops is acceptable. The UE may use a specific PUSCH on each PUSCH hop or (to limit delay) Hop-Only to UCI m 18 can be configured to support the mapping of PDCCH 1801, gap 1802 in slot 1810 on frequency 1811 As can be seen in the example in FIG. 18, the encoding for PDSCH0 and PDSCH1 is UCI01083, which contains the coded ACK-NACK portion 1807, The encoding for PDSCH0 and PDSCH1 can be transmitted on hop 1 of 1804. The UCI0 1806, which contains the remaining part 1808 of the loaded ACK-NACK, is It can be transmitted on hop 2 of H1805.

[0107] If the UE has only one instance of UCI (M=1), then it will use the following as shown in Figure 18: However, it is possible to split and map the UCI to both hops. If M>1 instances of the UCI must be transmitted, then the UCI is Instead of hopping, the instance may be mapped. UCI may be transmitted on eMBB PUSCH resources, while eMBB data may be transmitted only the URLLC UCI for those resources is sent. It is transmitted on SCH.

[0108] FIG. 19 shows an example procedure 1900 for mapping UCI0. In the example in Figure 19, UCI0 is mapped to multiple hops when M=1 (example in Figure 18). If M>1, each instance of UCI can be assigned to the corresponding hop (example in Figure 17). When the procedure starts (step 1901), the UE The value of M (the number of UCI instances to map) for point #i can be determined by (Step 1902). The UE may then determine whether M is greater than 1 (step Step 1903). If M is greater than 1, the UE m Map top hop #m If M is less than or equal to 1, the UE may ping the H PUSCH host (step 1904). Divide the UCI corresponding to each PUSCH hop and map a portion of the UCI onto each PUSCH hop. (step 1905). The procedure may then end (step 1906).

[0109] FIG. 20A shows the UCI on the PUSCH multiplexed with the PUSCH resource. m About H 20A shows an example mapping 2000 of ARQ-ACK and CSI. UCI on PUSCH for =2 m Figure 20A shows the mapping of PDCCH2 001, Gap 2002, PUSCH 2007, OFDM Symbol #3 DMRS 200 3, OFDM Symbol #11DMRS2004, CSI2009, and HARQ AC K2008. UCI m can be mapped in the time domain as follows: The RQ-ACK symbols may be mapped near the DMRS. on the first available non-DMRS symbol after a set of adjacent DMRS symbols For PUSCH with Type A DMRS, the mapping can start with It may start from the previous symbol if that symbol is available. The symbols may be mapped starting on the first available non-DMRS symbol.

[0110] In the frequency domain, UCI m The modulation symbols are spaced between consecutive REs, which are determined as follows: The symbols i can be mapped to the REs of the symbols i in a distributed manner with a distance d. (1) d=1, the mapped UCI for the beginning of OFDM symbol i The number of modulation symbols not available may be equal to or greater than the number of available REs in this OFDM symbol. In the case of Figure 20A, the HARQ-ACK of UCI12006 is the mapping for d=1. Indicates the tag.

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

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

[0113] FIG. 20B shows the UCI on PUSCH in the case of UCI only on PUSCH. m Example map of FIG. 20B shows the PDCCH 2020, gap 2021, OFDM symbol # 3DMRS2022, OFDM symbol #11DMRS2023, UCI02024, and and UCI12025. UCI is only transmitted on PUSCH resources. For example, UCI for multiple URLLC PDSCHs can be obtained by one eMBB P The URLLC UCI can be transmitted separately via the resources for the USCH. If the required resources exceed a certain threshold, the eMBB PUSCH may be dropped. , RE can be fully used for UCI. UCI02024 and UCI1202 The number of symbols about 5 determines how the beta offset is configured for each of the UCIs. The number of times the ...

[0114] For eMBB PUSCH carrying multiple instances of UCI, sufficient DMR is required. If the S symbol is not present, all instances of UCI are mapped next to the DMRS. Then, U that is mapped away from the DMRS symbol There may be a performance loss for CI, which can be handled in the following ways:

[0115] Figure 21A shows a HARQ-ACK UCI mapping link with no DMRS in the vicinity of UCI1. FIG. 21A shows an example of a source 2100. The source 2100 includes a PDCCH 2101, a gap 2102, and an OF DM Symbol #3DMRS2104, PUSCH2106, OFDM Symbol #3 21 03, OFDM symbol #8 2108, UCI02105, UCI12107, HAR Q ACK 2109, and other UL signals 2110. Beta Offset Parameter The value of, for example, Equation 13 below, is used for UCI instances that may not be close to DMRS. In the example of FIG. 21A, the PUSCH is seven symbols long. where UCI12107 is Compared to UCI02105, it may use more resources, but both have the same payload. Additional resources for UCI12107 can be found at This can help compensate for poor channel estimation quality. If the next mapping position is not available, the UE may factor out the beta by the following Equation 14: Here, the following Equation 14 can be used to inform the UE of the set value through RRC signaling. The UE may be configured to use the factor Equation 13 below instead of Equation 14 below to Therefore, >1 is the number of additional resources for UCI mapping. may be provided to the UE.

[0116]

number

[0117]

number

[0118] FIG. 21B shows the HARQ-ACK U with additional DMRS introduced near UCI1. 20B shows an example of CI mapping resources. 1, OFDM symbol #3DMRS2123, PUSCH2125, OFDM symbol # 3 2122, OFDM symbol #8 2127, UCI02124, UCI12126 , DMRS 2128, HARQ ACK 2130, and other UL signals 2129. The UE detects UCI in its vicinity as a DMRS symbol. m may be used to map The DMRS configuration for the PUSCH is modified to ensure that the As shown in Fig. 1, a 7-symbol PUSCH with one DMRS is configured in OS#3. However, the UE generates a PUSCH with a length of 7 symbols with an additional DMRS in OS#7. As a result, UCI1 may be mapped near an additional DMRS symbol. E requires piggybacked UCI in the corresponding sub-slot via RRC signaling. It may be expected that additional locations for DMRS may be configured if necessary.

[0119] A lower priority UCI may be piggybacked on a higher priority PUSCH. If the beta offset value can be equal to 0, U can be piggybacked on the PUSCH. There is no CI. A value less than 1 indicates some low-priority UCI on a high-priority PUSCH. may be supported to allow piggybacked resources.

[0120] The UE transmits the UCI in slot #3 in the manner shown in FIGS. eMBBand UCI U RLLC FIG. 22A shows the UCI eMBB UCI URLLC precedes UCI piggybacks on PUSCH URLLC and UCI eMBB Example 2200 FIG. 22A shows PDCCH 2201, other UL signals 2202, DMRS 2210, HARQ ACK UCI 2260, and gap 2208. FIG. 22A also shows Slot #0 2212, Slot #1 2213, Slot #2 2214, and Slot #3 22 with subslot 0 2206 and subslot 1 2207 15. In some scenarios, the UE may transmit URLLC and eMBB during a slot. It may be possible to have a HARQ-ACK to transmit for both In the example of Figure 22A, eMBB PDSCH02 202 and PDSCH12 203 are May be scheduled in slot #0 2212 and slot #1 2213, UCI eM BB The HARQ-ACK report of 2210 is scheduled for slot #3 2215 URLLC PDSCH22204 and URLLC PDSCH32205 may be scheduled for the UE in slot #3 2215, and UCI URLLC twenty two The HARQ-ACK report for 09 is also scheduled for slot #3 2215. The UE has a PUSCH 2212 scheduled in slot #3 2215. , and therefore, in slot #3 2215, UCI may be piggybacked on the PUSCH. The UE transmits the UCI in the first sub-slot 2206 of slot #3 2205. eMBB2 210, and UCI in subslot 2207 after slot #3 2205 URLL C 2209. This means that the latency requirement for URLLC is 3 This may be possible when transmission at the edge of 2215 is permitted.

[0121] Figure 22B shows the UCI URLLC UCI eMBB Piggyback on the preceding PUSCH UCI URLLC and UCI eMBB Figure 22B shows an example of PDCCH22 20, showing other UL signals 2222, DMRS 2233, and gaps 2227. 2B also has slot #0 2234, slot #1 2235, slot #2 223 6, and a slot with subslot 0 2228 and subslot 1 2229 In some scenarios, the UE may receive URLLC and It is possible that LTE may have HARQ-ACK to transmit for both eMBB and eMBB. In the example of Figure 22B, eMBB PDSCH02221 and PDSCH12 223 may be scheduled in slot #0 2234 and slot #1 2235. , UCI eMBB The HARQ-ACK report for 2231 is for slot #3 2237 URLLC PDSCH22225 and URLLC PDSC can be scheduled. H3 2226 may be scheduled for the UE in slot #3 2237, and UCI U RLLC The HARQ-ACK report in 2230 is also scheduled for slot #3 2237. The UE receives PUSCH2, which is scheduled in slot #3 2237. 232, and therefore piggybacks UCI on PUSCH2232 in slot #3. In FIG. 22B, the UE may receive a signal in the first sub-slot 2237 of slot #3. UCI at 28 URLLC 2230, and subslot 223 after slot 2237 UCI at 1 eMBB 2231. This allows the UE to If the system has the ability to process URLLC grants within the system, URLLC UCI will have priority in time. It will be possible to do this.

[0122] Figure 22C shows the UCI URLLC and UCI eMBB is the same sub-slot of PUSCH UCI piggybacked on PUSCH mapped to URLLC and UCI eM BB FIG. 22C shows an example of PDCCH 2240, GAP 2241, and PUSCH 22. 43, OFDM symbol #3 2242, DMRS2245, OFDM symbol #11 2244, HARQ ACK UCI URLLC 2246, and HARQ ACK U CI eMBB In FIG. 22C, a slot 2248 containing UCI 2247 is shown. eMBB 2 247 and UCI URLLC 2246, the first DMRS of PUSCH2243 It can be mapped following 2245. UCI URLLC 2246 was mapped first UCI eMBB DMRS2245 followed by 2247 will be the next in line for delayed benefits and resources. The service can be provided to it.

[0123] Figure 22D shows the UCI URLLC Resources are first mapped and then UCI eMBB But later UCI piggybacks on PUSCH URLLC and UCI eMBB Here is an example of Figure 22D shows the PDCCH 2250, GAP 2251, PUSCH 2255, and OFDM signal. Symbol #3 2252, DMRS 2256, OFDM Symbol #11 2254, HAR QACK UCI URLLC 2257, and HARQ ACK UCI eMBB twenty two Shows slot 2259 containing 58. UCI URLLC 2257 is next after DMRS2256 If you occupy all resources on the symbol, UCI eMBB 2258 is Figure 22D As shown in the example, it can be mapped with the following symbols:

[0124] Joint transmission of UCI of multiple priorities is described herein. The UE may support joint transmission of UCIs of multiple priorities, i.e., the UE may support joint transmission of UCIs of multiple priorities. The UE then jointly encodes the RQ ACK bit and transmits it. When transmitting UCI, the UE may be configured to bet-off the HARQ-ACK with the highest priority for UCI. It is proposed here to apply a set value. The set value provides more resources for UCI on the PUSCH and therefore a higher Considering that a higher priority can provide higher reliability, ACKs may also be received with greater reliability.

[0125] UE is B low thresh If low ​B low H ARQ-ACK bit to the priority level p high B high HARQ-ACK bit where B thresh is a threshold that can be determined in one of the following ways: It could be. (1)B thresh is configured in the UE by the gNB through RRC signaling. obtain.

[0126] (2)B thresh Blow and B high For example, B l ow / B high <= V, where V is configured in the UE by the gNB. It can be a constant or a parameter.

[0127] (3)B thresh can be a function of the beta offset value. The set value may correspond to the highest priority level multiplexed in the UCI.

[0128] (4)B thresh is the beta offset value, B low and B high is a function of For example, for a beta offset of 1, low / B high <=V1, Betao About Set 2 B low / B high <=V2, etc. where V1, V2, etc. may be a constant or a parameter configured in the UE by the gNB.

[0129] UCI mapping with repetition of HARQ process is described herein. For each PUSCH, the gNB may schedule repetitions of one UL grant. may schedule two or more transmissions for the same HARQ process for reliability. Multiple transmissions of the RQ process can be within one slot or in consecutive available slots. If the repetitions are in different slots, Each PUSCH transmission may have a different starting symbol and / or time length. Each PUSCH segment may have a different number of resources. The UCI is a sequence of the repeats or segments, as shown in some examples in Figures 23A-23B. Here, the label rep represents repetition. Both the eMBB UCI and the eMBB UCI piggyback on the PUSCH through the methods discussed below. It can be done.

[0130] Figure 23A shows the repetition of PUSCH in a minislot with UCI split between repetitions. FIG. 23A shows an example 2300 of the HARQ process repetition involved in the PDCCH 2301. , Slot 23, including Gap 2302, PUSCH 2303, and DMRS 2306 In the example of FIG. 23A, PUSCH repetitions occur within a slot, and PUSCH0 2304 and 2305 may be transmitted twice in a minislot, and UCI modulation symbol 23 07 (HARQ-ACK in this example) is divided into two and mapped in each mini-slot. In this case, rate matching or puncturing can be performed in a single iteration. The amount of σ can be reduced, thereby limiting the performance loss for a given PUSCH transmission.

[0131] FIG. 23B illustrates multiple segment transmissions between slot boundaries with UCI splitting between repetitions. FIG. 23B shows an example of a repeating HARQ process with PDCCH 2310, Gamma 2311, other UL signals 2312, PUSCH 2316, and DMRS 2317 In the example of FIG. 23B, slot #0 2318 and slot #1 2319 are shown. ,Repetitions can occur between slots, and each transmission within a repetition may have a different time length and starting time. PUSCH02313 and 2314 have OFDM symbols. The UCI 2315 is divided into two parts and transmitted in each PUSCH segment. It can be pinned.

[0132] Figure 23C shows the UCI splitting in a minislot with frequency hopping between repetitions. An example of a repeating HARQ process is shown in Figure 23C. 321, PUSCH2322 and 2330, and DMRS2323 and 2329 In the example of FIG. 23C, slot #0 2325 for frequency 2331 is shown, which includes USCH repetitions 2326 and 2327 occur within slot 2325, but each repetition It has hops to different frequencies 2321, which provides frequency diversity to the transmission. , UCI 2324 may be split into two parts, each part being mapped onto one PUSCH transmission. It can be pinned.

[0133] Figure 23D shows multiple segment transmission with hopping with UCI splitting between repetitions. FIG. 23D shows an example of a repeat of the HARQ process. 2341, other UL signals 2342, PUSCH 2347 and 2350, and DMR Slot #0 2345 and 2349 on frequency 2353, including S2342 and 2349 In the example of FIG. 23D, the PUSCH segment is Each transmission in PUSCH repetitions 2346 and 2348 occurs between the and the starting OFDM symbol. Again, UCI2344 is split into two parts: Each PUSCH segment can be divided into parts so that it can benefit from frequency 2353 diversity. can be mapped to a statement.

[0134] Encoding UCI between repeated minislots or between repeated segments and The division of the modulated symbols may be performed in the following manner.

[0135] The modulated UCI symbols are generated jointly between repetitions, using the resources in each repetition. This means that the performance loss from rate matching is less. This ensures that the PUSCH performance for repetitions with resources is not affected. For example, in Figures 23B and 23D, the first PUSCH segment may be 7OS. ,On the other hand, the second segment may only be 5OS and has fewer resources than the first. In this case, UCI is mapped to each segment in proportion to the resources in that segment. It can be done.

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

[0137]

number

[0138]

number

[0139] where: The following Equation 17 may be the number of HARQ-ACK bits. If the following formula 18 is true, the following formula 19 is true, otherwise the following formula 20 is true: It can be the number of CRC bits for HARQ-ACK (Equation 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 PUSCH transmission is If it contains a CBGTI field indicating that it may not transmit a code block, r =0, otherwise, K r is the rth control for the UL-SCH of the PUSCH transmission. It can be the code block size. Equation 23 below shows the schedule of the PUSCH transmission, expressed as the number of subcarriers. The bandwidth may be a fixed bandwidth. Equation 24 below expresses the OFDM symbol l carrying the PTRS in PUSCH transmission. may be the number of subcarriers in The following Equation 25 is expressed as follows for the following Equation 26 in the case of repeated PUSCH transmission (rep): is the number of resource elements that can be used for transmission of UCI in OFDM symbol l, Equation 27 above is a PUSC that includes all OFDM symbols used for DMRS. It can be the total number of OFDM symbols in H. For any OFDM symbol carrying the DMRS of PUSCH, the following equation It is 28. For any OFDM symbol that does not carry a PUSCH DMRS, Equation 29 = Equation 30 below - Equation 31 below. α can be configured by scaling the parameters of higher layers. The following Equation 32 is the first DMRS symbol in the PUSCH transmission with the replication rep. The first OFDM symbol after the symbol(s) that does not carry a DMRS for PUSCH. It may be a ball index. α can be configured separately for each priority level. A larger α value may give more resources for UCI. The symbols in Equation 33 below are repeated based on the PUSCH resource in each repetition. The following Equation 34 is mapped to the PUSCH repetition "rep": The number of modulation symbols to be transmitted may 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 PUSCH resources are proportionally mapped to each segment. The modulated UCI symbols between the repetitions are divided into UCI symbols jointly generated between the repetitions. 24 shows an example procedure 2400 for dividing a UCI into 24 bits. 2401), and then rate matching is performed using a beta offset 2403. The repetition is performed based on the total PUSCH resources in the set of PUSCH resources (scheduled The UCI is modulated (step 2404), and then the UCI is converted to RUC I segment, UCI segment rep The length is PUSCH rep Litho in The number of UCI segments is proportional to the number of segments (step 2405). rep is PUS CH rep(step 2406).

[0160] The UCI modulation symbol in Equation 36 below can be generated as described in Equation 1 and expressed in Equation 3 as follows: The PUSCH signal may be split approximately equally among the PUSCH repetitions or segments as shown in FIG. The example in ∼23D shows an equal division of UCI resources between two iterations (the equation below) 37).

[0161]

number

[0162]

number

[0163] FIG. 24B shows a roughly equal mapping between PUSCH segments, with To divide the modulated UCI symbols between repetitions with jointly generated UCI symbols, An exemplary procedure for this is shown in Figure 24. The UCI may be encoded (step 2411), and then Then, using a beta offset of 2413, rate matching is performed for R iterations of PUSC. Based on the total PUSCH resources in the set of H resources (step 2412) The UCI is modulated (step 2414), and then the UCI is approximately The UCI segments can then be divided approximately equally (step 2415). rep PU SCH rep (step 2416).

[0164] The modulation symbol of the UCI in Equation 38 is expressed as Equation 4 for each PUSCH repetition. and each PUSCH may be generated separately based on the beta offset value for that PUSCH. Here, Equation 39 below can be used to map the PUSCH to repetitions / segments. It can be a beta offset value for each iteration.

[0165]

number

[0166]

number

[0167] FIG. 24C shows a modulation scheme with separately generated UCI modulation symbols for each repetition. 1 illustrates an exemplary procedure for splitting a UCI symbol. (step 2421), and then the beta offset 2423 is used to perform rate matching. The PUSCH rep The UCI is modulated (step 2422). (Step 2423), then the UCI segment rep is PUSCH rep Nimappi The result can be calculated (step 2424) (Equation 40 below).

[0168]

number

[0169] Another alternative is to split the UCI among the PUSCH repetitions rather than splitting it among the repetitions. A repeat that can carry a UCI can be mapped completely to one of the The start of the PUCCH may overlap with the PUCCH corresponding to the PUSCH repeat. The end of a PUCCH may coincide with the start of a PUSCH repetition, or the end of a PUCCH may coincide with the end of a PUSCH repetition. In this case, the UE maps the UCI to that particular repetition of the PUSCH. Figures 25A-25D show the results of the UCI piggybacking on the PUSCH. 1 provides an example in which a PUCCH transmission (which may be used) is shown together with a PUSCH.

[0170] Figure 25A shows a PUSCH repetition scheme that maps UCI to PUSCH with minimum delay. FIG. 25A shows an example 2500 of UCI transmission. 2, DMRS2504, PUSCH2503, and HARQ ACK UCI0250 Shows slot #0 2509 with minislots 2506 and 2507, including 5 In the example of FIG. 25A, the start position of 12-OS PUCCH 2508 is PUSCH 250 3. As a result, the UCI2505 will 2506 and PUCCH 2508 may be dropped.

[0171] FIG. 25B shows a diagram of a PUSCH in which UCI is mapped to a PUSCH that is aligned with the edge of a segment of the PUSCH. FIG. 25B shows an example of UCI transmission via PUSCH repetition. 0, GAP2511, DMRS2513, PUSCH2512, and HARQ AC K Slot # with minislots 2515 and 2516, including UCI02514 In the example of Figure 25B, the end of the 8-OS PUCCH 2517 indicates the PUS The UCI 2514 can be aligned with the end of the second segment of the CH 2512. It can be piggybacked onto the 2 segment and PUCCH2517 can be dropped.

[0172] FIG. 25C shows a case where UCI is mapped to the first PUSCH that is aligned with the end of a segment of the PUSCH. Figure 25C shows an example of UCI transmission via PUSCH repetitions. 2520, GAP 2521, DMRS 2522, PUSCH 2523, and HARQ Slot with minislots 2525 and 2526, including ACK UCI02524 In the example of FIG. 25C, the start position of the 4-OS PUCCH is P However, the UE will not consider it as the first If the system has the capability to map PUCCH2 to minislot 2525, it will do so. 527 can be dropped.

[0173] FIG. 25D shows a PUSCH repeater that maps UCI to PUSCH according to UE capabilities. FIG. 25D shows an example of UCI transmission via PDCCH 2530, gap 253 1, DMRS2532, PUSCH2533, and HARQ ACK UCI0253 Shows slot #0 2538 with minislots 2535 and 2536, including 4 In the example of Figure 25D, PUCCH 2537 may be similar to PUCCH in Figure 25C However, the UE may experience delays in processing the piggybacked UCI2534. , does not have the ability to map it into the first minislot 2535. Therefore, U E maps it on the second minislot 2536 of the repeat, PUCCH25 37 can be dropped.

[0174] Figure 26 shows an example 2600 of PUSCH repetition transmission to different TRPs. , PDCCH 2601 and gap 2602, minislots 2603 and 26 04. In case of multiple TRP operation, the UE 2603 Repeats or segments may be transmitted to different TRPs, i.e., DL RS or UL The spatial direction or correspondence of the beam with the QCL with RS is given for each repetition / segment. In the example of FIG. 26, the PUSCH is transmitted in a mini-slot within slot 2605. TRP02601 and TRP12602 may be repeated in TRP02603 and TRP12604. Transmissions to may be transmitted on beams B02 604 and B12 605, respectively.

[0175] The different PUSCH repetitions may also hop in frequency as shown in FIG. 23C. Similarly, different segments of PUSCH transmission, such as those in Figures 23B and 23D, The event may also be transmitted to a different TRP.

[0176] A solution for piggybacking UCI on multiple TRP PUSCHs is available. The UCI for each TRP is determined by the number of TRPs that the target TRP has associated with its UCI. For each UCI, The codebook for all HARQ ACKs is the HARQ ACK codebook for PDSCH from that TRP. For example, the first UCI may include only the ACK bit of the first PDSCH. / NACK bit(s). First UCI and first PUSCH repetition / sec. The segments share a spatial relationship. In one example, the TCI state of the first PDSCH (or The RS in the TCI state of the PDSCH layer set of 1 is the first PUSCH repetition / sec. For example, the UE may use the T RS for the spatial relationship of the first PUSCH repeat / segment from RS in the CI state can be derived.

[0177] Alternatively or additionally, the UE may determine UCI for T TRP for transmission in a particular spatial direction. In this case, the UCI codebook may be configured to report their TTR It may contain only HARQ-ACK bits or CSI reports for P.

[0178] FIG. 27A shows the different TRPs with separate HARQ-ACK codebooks for each TRP. 27 shows an example 2700 of mapping UCI to target PUSCH repetitions for FIG. 27A shows PDCCH 2701, GAP 2702, DMRS 2704, and PUSCH 2703, HARQ ACK UCI02705 (transmitted on beam B02709); and HARQ ACK UCI12706 (transmitted on beam B12710) , slot 2713 with mini-slots 2707 and 2708. So, UCI transmission (Beam B PUCCH (Transmitted on PUCCH 2711) , the codebook for HARQ-ACK is Total It is expressed as However, the PUSCH2 703 is available for transmission to each of TRP0 and TRP1, the UE Total The payload of can be divided into UCI02705 and UCI12706. , UCI02705 may include the HARQ-ACK bit for TRP0, UCI 12706 may contain bits for TRP1. UCI02705 and UCI1 2706 is encoded, modulated and mapped into each repetition or segment. In other words, a different codebook can be used to encode the piggybacked UCI into each T It can be used to transmit to the RP.

[0179] In some cases, PDSCH repetition (from multiple TRPs) and Both PUSCH repetitions (HARQ-ACK and HARQ-ACK) can be used. The specific PDSCH repetition and the specific PU are piggybacked on the PUSCH. A beam / spatial mapping may be configured between SCH repetitions. If the UE has a beam mapping, In this case, the spatial relationship of different PUSCH repetitions is different from the RS in the TCI state of PDSCH repetitions. (s) or alternatively or additionally from RS(s) In one example, the spatial relationship of the first PUSCH repetition can be derived as follows: PDSCH repetition and PUSCH repetition can be equivalent to the TCI state of the For example, the spatial relationship between the first PUSCH iteration and the R S is the RS in the TCI state of the first PDSCH repetition, e.g., QCL type D (spatial R The PDS is equivalent to the RS in the TCI state with the QCL (with respect to the x parameter) There can be a continuous mapping between CH repetitions and PUSCH repetitions.

[0180] Figure 27B shows the different UCIs with a common codebook repeated for each TRP. An example of mapping UCI to target PUSCH repetitions for a given TRP is shown below. Figure 27B shows PDCCH 2711, GAP 2712, DMRS 2714, and PUSCH 2713, HARQ ACK UCI02715 (transmitted on beam B02719), and HARQ ACK UCI12716 (transmitted on beam B12720) , slot 2723 with mini-slots 2717 and 2718. The example of FIG. So, we present another solution for piggybacking UCI on multiple TRP PUSCHs. where (beam B PUCCH (Transmitted by 2722) PUCCH2721 UCI in Total However, in each of the PUSCH minislots 2717 and 2718 It can be coded, modulated and repeated, so that each TRP receives the entire UCI. Alternatively or additionally, TRPs communicate through backhaul and can be configured to support U-Trace from multiple TRPs for improved robustness. CI Total This may allow for the binding of

[0181] The beta offset is the sum of the beta offsets for each beam (which may depend on the channel conditions in different spatial directions). Separate PUSCH repetitions are used for different PUSCH repetitions to allow different levels of protection for Therefore, the number of resources in the replication set for each PUSCH The above may differ for UCI.

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

[0183] FIG. 28A shows a PU with a scheduling request indicator (SRI) cycle. An example of SCH repetition 2800 is shown in FIG. 28A. 2, SRI12803, SRI22804, SRI32806, and SRI42807 In the example of FIG. 28A, slots 2810 and 2811 are shown, which contain CG or dynamic Each iteration in the set of iterations 2805 in a grant has a different SRI (e.g., SR I2803, SRI2804, SRI2806, and SRI2807), TCI state, and / or precoders, so that the UE can receive the Therefore, the UE may transmit each PUSCH within a repetition of SRI. Repeat through the TCI state and / or precoder to complete the repeat set. In the example of FIG. 28A, the SRI for the repetition (e.g., SRI2803, SR I2804, SRI2806, and SRI2807), TCI state, and / or The recorder (at least for Type 1 CG, and possibly for Type 2 CG) Alternatively, the SRI for repetition can be configured for the UE through RRC. , TCI state, and / or precoder enabled through DCI for Type 2 CG It can be signaled as follows:

[0184] Figure 28B shows an example of PUSCH repetition with SRI fixed to the time resource. 8B shows PDCCH 2820, gap 2821, other signals 2822, and SRI 2823. , SRI32825, and SRI42826, including slots 2827 and 2828 In the example of FIG. 28B, SRI, TCI for transmission in repetition set 2824 are shown. The state and / or precoder may be tied to the time resource of the grant. Therefore, depending on when the UE starts its CG transmission, as shown in the example in Figure 28B, may start with different SRI, TCI state, and / or precoder. may transmit PUSCH only three times within the repetition set 2824, The transmission of 1s begins in the second half of the slot. However, the SRI is The first Transmission uses SRI22823.

[0185] FIG. 28C shows an example of PUSCH repetition with SRI as a function of repetition analysis. Figure 28C shows the PDCCH 2830, gap 2831, other signals 2832, and SRI1. Slots 2837 and 2833, SRI22835, and SRI32836 2838. In the example of FIG. 28C, alternatively, the SRI, TCI state, and / or P The recorder may be tied to the rth transmission in the repetition set 2834. In this example, the UE can transmit PUSCH only three times within the repetition set, and the first The transmission begins in the second half of the slot. The first transmission may use SRI12833. TRP is a set of SRI, TCI state, and / or precoder states at each repetition opportunity. The possibility of

[0186] In some cases, the number of repeats may vary depending on the different SRI, TCI conditions configured / shown. and / or may be greater than the number of precoders. In some cases, the UE first may transmit one repetition with each different SRI, TCI state, and / or precoder; It may then wrap around and return the first SRI, TCI state, and / or precoder Therefore, the next iteration may use different SRI, TCI states, and / or pre- Alternatively, the UE may use the same SRI, TCI coder for several subsequent iterations. states, and / or precoders, so that all SRI, TCI states, and / or a precoder may be used between repetitions, but without wraparound It can be used.

[0187] PUSCH HAR with different SRI, TCI state, and / or precoder in CG As an alternative to transmitting Q process iterations, the UE may have multiple CGs configured on it. where each CG corresponds to one SRI, TCI state, and / or precoder. Therefore, repeats within a CG are likely to have the same SRI, TCI state, and / or plecotype. For Type 1 and possibly Type 2 CGs, multiple CGs are Each CG can be configured through RRC, where each CG can have a different SRI, TCI state, and / or or precoder. All except SRI, TCI state, and / or precoder All parameters can be the same for these CGs. The spatial direction may be the same for these CGs. Alternatively, the DMRS may be different for each of the CGs. For Type 2 CGs, the SRI, The TCI status and / or precoder may be indicated through an enable DCI. is typically configured through RRC (thereby reducing configuration overhead), and are a single DCI with a single configured grant group that can be jointly enabled and disabled. The group can be combined.

[0188] It may be beneficial to support early termination of PUSCH transmission within a repetition set. This applies to both configured and dynamically scheduled grants. If the TRP correctly decodes the PUSCH, the UE receives the remaining There is no need to transmit the repetition to other TRPs. Therefore, the TRP can use the early termination indicator (E TI) to the UE to terminate the remaining iterations. This allows for better spectrum This may enable higher capacity utilization, less interference, and reduced power consumption for the UE.

[0189] 29A-29H provide an example 2900 of PUSCH repetition in multiple TRP scenarios. FIG. 29A shows PDCCH 2901, GAP 2902, and S directed against TRP1. RI12903, SRI22904 directed to TRP2, SRI directed to TRP3 32906, and SRI42907, which is directed to TRP4. In the example of FIG. 29A, the UE transmits four PUSCH repetition sets 2909. 05, where each PUSCH transmission has four TRPs, namely, TRP1, TRP2, TRP3, TRP4, TRP5, TRP6, TRP7, TRP8, TRP9, TRP10, TRP11, TRP12, TRP13, TRP14, TRP15, TRP16, TRP17, TRP18, TRP19, TRP19, TRP110, TRP111, TRP12, directed to P2, TRP3, and TRP4.

[0190] Figure 29B shows PDCCH 2910, GAP 2911, and SRI1 directed to TRP1. 2912, SRI2 directed to TRP2 2913, terminated SR directed to TRP3 slots, including I32918, and the terminated SRI42919, which is directed to TRP4. 2920 and 2921. In the example of FIG. 29B, TRP1 is represented by repeat set 291 4 successfully decodes the first transmission 2903 of the PUSCH and the next slot in the repetition set. In this case, the UE transmits ETI2915 to the UE via DCI on the PDCCH. Identify the end and the third and fourth transmissions in repeat set 2917 (directed to TRP3 and SRI42919, which is directed against TRP4. Cancel.

[0191] Figure 29C shows PDCCH2930, GAP2931, and SRI1 directed to TRP1. 2935, SRI2 directed to TRP2 2936, terminated SR directed to TRP3 I32940, terminated SRI42941, and UCI2933, which are directed against TRP4 In the example of FIG. 29C, the UE includes slots 2942 and 2943. If UCI 2933 must be transmitted simultaneously with H transmission repeat set 2932, The UCI 2933 can be piggybacked on the PUSCH. Early termination of the PUSCH transmission Cancel part of the PDCCH 2937 (indicated to the UE by ETI 2937) ) In this case, UCI 2933 is the UCI only on PUSCH during the repetition set 2939. The PUSCH resource (TRP3) is targeted to the SRI32940 gene. and terminated SRI42941, which is directed against TRP4.

[0192] Figure 29D shows PDCCH2950, ​​GAP2951, and SRI1 directed to TRP1. 2952, SRI22953 directed to TRP2, SRI329 directed to TRP3 57, and slot 2959, including terminated SRI42958, which is directed to TRP4. In the example of FIG. 29D, ETI 2946DCI is in repeat set 2 954, if the UE has received at least one transmission from the TRP on the PDCCH; The DCI may be in the form of an override grant for another HARQ process. The UE may identify the ID of the TRP carrying the ETI DCI and determine whether the new grant is different from the previous one. that is, the previous grant will be terminated early. Here, since the UE receives a duplicate grant for HARQ ID#1, , HARQ ID#0 is terminated 2956. Therefore, the override grant is Implicitly terminates the loop.

[0193] The DCI carrying the ETI may be transmitted in the following ways: (1) The ETI DCI may be UE-specific and may be the UE's C-RNTI or CS-RNTI Can be scrambled with I.

[0194] (2) ETI DCI is common to the group and is scrambled by ETI-RNTI. The UE may be configured with the ETI-RNTI through RRC signaling. The CI may indicate the UE-ID for which early termination may apply. Alternatively, the ETI DCI may indicate the This can occur in the form of a loop-wide UL preemption indication PDCCH, where the UE Preemption from transmission on a particular resource.

[0195] (3) The UE receives an ACK signal from the AK that provides the UE with an ACK on one or more HARQs that are processed. - The ETI may be identified implicitly from the DCI.

[0196] The ETI DCI may explicitly or implicitly provide the following information to the UE: (1) A PUSCH HARQ process that is terminated, i.e., this is the process where ACK-DCI is It may implicitly indicate whether to indicate an ACK for a given HARQ process.

[0197] (2) The number of repetitions after which the PUSCH repetition can be completed. Because conditions may exist, early termination does not have to occur immediately after the receipt of the ETI, but after K This time may be desired after the iterations are completed. It is possible to communicate the ACK status of

[0198] Figure 29E shows PDCCH2961, GAP2962, and SRI1 directed to TRP1. 2963, SRI22964 directed to TRP2, SRI329 directed to TRP3 68, and slot 2971, including terminated SRI42969, which is directed to TRP4. In the example of Figure 29E, ETI 2970 is If the ETI is received by the UE on at least one of the PDCCH transmissions, the UE shall transmit the ETI. The ID of the TRP to be used can be identified, and the HARQ ID #0 can be determined to be terminated 2966. 0 possible.

[0199] Figure 29F shows PDCCH2973, GAP2974, and SRI1 directed against TRP1. 2975, SRI2 directed to TRP2; 2976, modified S directed to TRP3 SRI32979, and the modified SRI42980, which is directed against TRP4. In the example of Figure 29F, the ETI to the UE on the PDCCH is shown as bits 2982 and 2983. The 2981 DCI may modify the PUSCH grant for the remaining repetitions 2978 For example, TRP1 receives the first PUSCH transmission of HARQ ID#0 and CBG1 If we observe that the CBG is NACK while the other CBG is ACK, then ETI298 1DCI indicates that the UE should transmit only CBG1 from the rth iteration onwards. FIG. 29F shows that the third and fourth transmissions indicate a NACK on CBG1. 81, the UE 2981 will be corrected 2979 and 2980 upon receiving .

[0200] Figure 29G shows PDCCH2984, GAP2985, and SRI1 directed to TRP1. 2986, SRI22987 directed to TRP2, SRI329 directed to TRP3 91, and slot 2994, including the terminated SRI42992 directed to TRP4. In the example of Figure 29G, timer-based early termination is directed towards TRP4. Alternatively, to support early termination, The gNB may then configure the UE with a timer, the early termination timer. When ETI2933 is received, timer 2988 is set and it is decremented or When timer 2988 is reset or expires, the UE Finish the remaining PUSCH repetitions 2989 for the HARQ ID. The value can be configured for the UE through RRC signaling and is used for backhaul between TRPs. May be determined by the gNB based on the UE's ability to react to changes in delay and ETI .

[0201] Optional termination is described herein. The ETI may exhibit optional termination, i.e. ,(e.g., TRP1 and TRP3 have ideal backhauls) If TRP1 successfully decodes the first transmission, it will only decode the third transmission. TRP1 sends an ETI to TRP3 to terminate the PUSCH within the minimum delay. The status of all ACKs is communicated to TRP3.

[0202] Figure 29H shows PDCCH2996, GAP2997, and SRI1 directed against TRP1. 2998, SRI22999 directed to TRP2, and SRI329 directed to TRP3 26, and SRI42927, which is directed to TRP4, including slots 2944 and 2 945. SRI12998 directed to TRP1, SRI2 directed to TRP2 2999, SRI32926 directed to TRP3 is transmitted between repeats 2923 However, in the example of Figure 29H, TRP4 and TRP1 are non-dealbacks. As a result, the ACK from TRP1 is sent to TRP4 within an acceptable delay. No communication is made (for example, HARQ ID#0 ends at timer expiration 2925), and TR It is desired that P4 should receive the PUSCH from the UE. 2922 terminates transmission to TRP3. As a result, the UE terminates transmission to TRP3. The fourth PUSCH transmission to TRP4 is then performed.

[0203] To enable this behavior, a TRP group is a "TRP group" consisting of specific TRPs. The concept of "TRP group" is introduced. A gNB can establish multiple TRP groups through RRC signaling. A TRP group may consist of UEs that are connected to at least one other TRP in that group. It is expected to include a TRP with ideal backhaul conditions relative to the RP, where If the TRP in the TRP group acknowledges the HARQ process, the ideal backhaul It is expected that the routing conditions will allow inter-TRP communication of ACKs within that TRP group. Therefore, the UE must not transmit repetitions of that HARQ process to other TRPs in that group. The transmission may be terminated.

[0204] Figure 30 shows the TRP group status when one TRP from the group negatively acknowledges a transmission. FIG. 30 shows an example retransmission 3000 of the PDCCH 3001, the gap 3002, as well as during transmitted repetition 3006, i.e., directed to TRP1 SRI13003, directed to TRP2; SRI23004, directed to TRP3; Slot 3014, including I33008 and SRI43009 directed to TRP4 , 3015, and 3016. In the example of Figure 30, the TRP in the TRP group is retransmitted. If a UE needs to transmit a HARQ protocol to one or more TRPs in that group, the UE TRP1 and TRP3 are in TRP group 1, but On the other hand, it is assumed that TRP2 and TRP4 are in TRP group 2. The UE TRP1 may have an UL grant for PUSCH repetition of Q ID#0. ACK3005 for USCH HARQ ID#0 is detected, while TRP2 detects NACK 3007 (TRP1 is explicitly or implicitly transmitted on the PDCCH) ACK 3005 to the UE, and TRP2 may explicitly or implicitly indicate ACK 3005 to the UE on the PDCCH. (The dynamic grant for retransmission is given by the TRP group.) Retransmission 3011 to one or more TRPs in the loop (e.g., directed to TRP2) SRI23012 and SRI43013, which are directed against TRP4 Alternatively, for CG, the UE may retransmit only TRP groups for which no ACK was received. In this example, the UE may transmit TRP2 3012 and TRP3 3013, which are in TRP group 2. and / or may retransmit HARQ ID#0 only on TRP4 3013. Configured to retransmit to a specific TRP within the target TRP group through signaling. This allows for signaling over the DCI when scheduling retransmissions. The bar head can be reduced.

[0205] 31A-31B show an example UE 3100 that identifies ACKs from all TRP groups. The UE continues to transmit until it receives an ACK from at least one TRP in each TRP group. or timer, ackTRP timer expires for ID#0. It is not necessary to clear the Q buffer. This is because all target TRPs (or TRs) P group) receives an ACK status and / or the TRP (or TRP group) Transferring data and / or ACK status of acknowledged HARQ processes between the This is to ensure that there is sufficient time for

[0206] FIG. 31A shows a PDCCH 3101, a gap 3102, and transmitted repetitions 3103. 107, i.e., SRI13103 directed to TRP1, SRI13103 directed to TRP2 SRI23104, SRI33109 directed against TRP3, and SRI33109 directed against TRP4 FIG. 31A shows slots 3113 and 3114, each containing an SRI43110. In this example, K TRPs are received from each TRP group. The UE receives the K TRPs (e.g., HARQ ID# ACK3105 from TRP1 for 0 and TRP for HARQ ID#0 2) on the PDCCH receiving ACK 3106 from the TRP group Upon receiving K, the UE may set and begin decrementing the ackTRP timer 3108. If ACKs are received from all other TRP groups before timer 3108 expires, The HARQ buffer for ID#0 may be cleared 3111.

[0207] FIG. 31B shows the PDCCH 3120, the gap 3121, and the transmitted repetitions 3122. 126, i.e., SRI13122 directed to TRP1, and SRI13122 directed to TRP2 SRI23123, SRI33129 directed against TRP3, and SRI33129 directed against TRP4 Slots 3131, 3132, and 3133 are shown, each containing an SRI43130. 1B shows an alternative example (e.g., TRP1 to AC for HARQ ID#0). All ACKs are received for HARQ ID#0 (on PDCCH receiving K3124). If the UE's ackTRP timer 3126 expires before a TRP is received from the RP group, The UE receives a NACK (e.g., HARQ) from another TRP group as shown in FIG. 31B. Even when receiving NACK3127 from TRP2 for ID#0, HARQ It may clear 3134 its buffer for ID#0. This is because the TRP Communicate ACK status and / or PUSCH data between the associated TRPs or TRP groups. This is because it is expected that there will be sufficient time to trust the

[0208] The ACK is implicitly sent to the UE by the TRP through a grant for the same HARQ ID. Note that the NDI set indicates a new transmission, although it may be indicated explicitly.

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

[0210] The timer is set when the first PUSCH transmission occurs for that HARQ ID repetition set. Sometimes it can be set.

[0211] The timer is set to 0 if the last PUSCH transmission occurs for that HARQ ID repetition set. Sometimes it can be set.

[0212] The value for the ackTRP timer may be configured in the UE through RRC signaling. , which may depend on the delay in the backhaul, which is not ideal.

[0213] Prioritization within the UE for PUSCH is described herein. A prioritization of configured grants is described herein. The UE may prioritize configured grants with higher priority. A PUSCH with a lower priority that conflicts with the configured grant may have a configured grant. In this case, the UE may receive a dynamic grant for providing the dynamic grant. Alternatively or additionally, the UE may only transmit the configured grant instead of If it has the capability, it may puncture the dynamic grant PUSCH and use the available resources. The gNB may transmit dynamic PUSCH over the DMRS of the configured grant. and if it receives it, it will process the configured grant PUSCH of high priority. It is predictable.

[0214] 32A to 32C show a low-priority PUSCH grant and a high-priority PUSCH grant. FIG. 32A shows an example 3200 of intra-UE collisions between PDC Slots 3207 and 3209 are shown, including CH 3201 and gap 3202. In the example of FIG. 32A, the UE receives dynamic PUSCH 13204. CG PUSCH URLLC Opportunity 3203 with Grant and Resource Competition 3206 Here, the UE may puncture the PUSCH 13210 in the RE where there is resource contention. I chatted.

[0215] FIG. 32A shows a PDCCH 3211 and a gap 3212 for a frequency 3218. The UE receives the eMBB PUSCH 1321 from slots 3217 and 3219. CG PUSCH URL with dynamic grants and resource contention received for 4 In the alternative example of FIG. 32B, the UE may transmit an LC opportunity 3213. and URLLC PUSCH3216 may not be able to process both simultaneously. Therefore, PUSCH13214 is cancelled.

[0216] FIG. 32C shows the PDCCH 3220 and gap 3221 for frequency 3229. The UE receives the eMBB PUSCH 1322 from slots 3227 and 3228. CG PUSCH URL with dynamic grants and resource contention received for 4 In the alternative example of FIG. 32C, the PUSCH 13223 may transmit an LC opportunity 3222. CG may only be transmitted on symbols that do not overlap with PUSCH 3223, i.e., PUS CH13224 may be punctured with symbols that overlap with CG PUSCH3225 .

[0217] Similar behavior occurs when a high priority dynamic UL grant is used in conjunction with a low priority dynamic UL grant. This scenario can be supported when the gNB has low priority U transmit an L grant followed by a higher priority UL grant that collides with the low priority grant. Alternatively or additionally, in the case of multiple TRPs, In other words, one TRP may schedule a high priority grant, while another TRP may schedule a U E may schedule low priority UL grants that may result in resource contention.

[0218] Figure 33 shows that PUSCH URLLC and PUSCH eMBB are FIG. 33 shows an example 3300 having PDCCH 3301 and The UE shows slots 3306 and 3307, including gaps 3302. The UE may transmit a PUSCH URLLC opportunity 3303, and the UE may transmit a HARQ-ID "H" 330 5. The UE also receives an UL grant for PUSCH eMBB transmission with Configured grant PUSCH with the same HARQ-ID URLLC Transmission 3304 available In this case, the transmission buffer of the UE with ID H contains URLLC data. The UE recognizes that the RLLC HARQ transmission was not correctly received by the gNB In this case, it may be desirable not to send this until the same HARQ ID is used. If a dynamic grant for a PUSCH of lower priority is received, the UE The resource is PUSCH URLLC and PUSCH eMBB If there is no conflict between However, the low priority grant may be ignored.

[0219] The URLLC PUSCH response can occur implicitly, i.e., the UE must configure the timer. D indicating a higher priority (URLLC priority) before the expiration of the granted timer CI does not receive rescheduling for HARQ-ID H. Therefore, P USCH eMBB Either of the following is PUSCH URLLC Following transmission, the configured grand If this occurs within the PUSCH timer period, the UE eMBB All of the grants or Drop some.

[0220] If PUSCH grants collide in time, the PUSCHs transmitted are identified by g To enable the NB to correctly identify the priority level of the transmitted PUSCH, Here, it may be desirable for the UE to indicate the RNTI corresponding to that priority level. p may be used to mask the RNTI in the PUSCH transmission.

[0221] If the gNB explicitly indicates a response to the CG, the UE shall wait until the response can be received. The transmission buffer H does not need to be flushed. The gNB can resolve the ambiguity in the event of HARQ ID collision. It is noted herein that the priority of a recognized PUSCH process can be indicated to avoid is proposed.

[0222] Figure 34 shows an example 3400 of intra-UE collisions for CG PUSCH. UEs may have different priority If a grant can consist of multiple configured grants at a higher priority level, the lower priority CG PU SCH transmission, but preempts it and transmits the higher priority CG P 34 shows the PDCCH3 for frequency 3411. 401 and gap 3402, including slots 3408, 3409, and 3410. The UE may transmit a CG PUSCH URLLC opportunity 3403. In a typical example, the UE receives two CGs, one for a low priority PUSCH 3404 called eMBB, and one for a low priority PUSCH 3404 called eMBB. and those with high priority PUSCH 3403 called URLLC. When the UE receives the URLLC TB for transmission via the CG, it BB PUSCH transmission 3405. Thus, the UE transmission may start eMBB transmission 3406. 06 may be cancelled or punctured to transmit URLLC PUSCH 3407. The gNB may monitor DMRS for both CG PUSCHs of both priorities, and It can be detected that the LC CG PUSCH has punctured the eMBB CG PUSCH. The gNB stores the punctured portion of the eMBB CG PUSCH in its soft buffer. minutes can be passed.

[0223] CGs with different priorities may be configured with respect to their configured grant timer lengths. It is proposed herein to have different lengths of time for low priority transmissions. The USCH duration may be longer than that of high priority transmissions. It is possible to have a longer time length for the configured grant timer for the SCH. This may be desirable.

[0224] Figure 35A shows the preempted state in the UE when receiving a dynamic grant from the gNB. 35 shows an example of a retransmission of a low priority CG PUSCH. If the CS-RNTI is punctured, the mode of operation is such that the gNB uses the CS-RNTI for its retransmissions. In the example of FIG. 35A, UE3 502 transmits HARQ ID D 3504 to gNB 3501 in slot 3503. The configured grant timer starts 3503. The configured grant timer expires. After 3506, the UE 3502 receives a dynamic grant 3507 for ID D. Then, the UE 3502 retransmits the HARQ ID D 3509 on the dynamic grant. However, in this case the delay for retransmissions can be high.

[0225] Figure 35B shows an example of retransmission as CG PUSCH. In the example of Figure 35B, UE3 522 transmits HARQ ID D 3524 to gNB 3521 in slot 3526. In this alternative example, retransmissions are initiated 3523 after the configured grant timer. This may occur before the expiration of the granted timer, and instead the UE may issue its own UR PUSCH is punctured by LLC traffic in slot 3528. Upon retransmission, the UE restarts the configured grant timer 325 7. After the CG retransmission, the UE If a dynamic grant is received, the dynamic grant may be ignored.

[0226] Furthermore, the retransmission may include only the cancelled or punctured CBG. , all CBGs on low priority PUSCHs or affected by low priority PUSCHs The RRC may be configured to retransmit only the CBGs that have been Retransmissions can be soft-combined correctly to recognize which were affected in the first transmission. Thus, retransmissions may not need to indicate the transmitted CBGTI.

[0227] Prioritization within the UE between DL and UL is described herein. In this case, contention may occur between DL and UL transmissions at the UE. The configuration for all is Format 2_0 group scrambled with SFI-RNTI. A slot frame that can be configured or indicated by RRC through DCI, such as a group-common DCI. In case of intra-UE contention between DL and UL, the following scenarios are considered: Rio may occur.

[0228] FIG. 36A illustrates the DL and UL collisions within a UE, the low priority PDSCH and the high priority PUS FIG. 36A shows a diagram of a channel collision 3600. , and gap 3606, including slot #0 3607, slot #1 3608, Slot #2 3609 is shown. In the example of FIG. 36A, one or more flexible thin The PBX receives a low priority PDSC through a grant (e.g., eMBB PDSCH3603). High priority UL grants may also be scheduled for H in the same symbol. May be scheduled on one or more (e.g., URLLC PUSCH 3605) In this case, the UE may discontinue the PDSCH 3604 and transmit the PUSCH.

[0229] FIG. 36B illustrates the DL and UL collisions within a UE, the low priority PDSCH and the high priority PUC FIG. 36B shows a diagram of a PDCCH 3610, other DL signals 3611, and Gap 3612, including slot #0 3617, slot #1 3618, slot In the example of FIG. 36B, one or more flexible symbols are For low priority PDSCH through grants (e.g. eMBB PDSCH3614) High priority UL grants (e.g., UR on PUCCH 3615) can be scheduled. LLC UCI 3616) also indicates that the PUCCH is In this case, the UE may be scheduled on one or more of the PDS The PUCCH 3620 may be interrupted and the PUCCH 3615 transmitted.

[0230] FIG. 36C illustrates DL and UL collisions within a UE, a low priority PUSCH and a high priority PDS FIG. 36C shows a diagram of a PDCCH 3630, other DL signals 3631, and Slot #0 3636, Slot #1 3637, Slot #1 3638, Slot #2 3639, Slot #3 3640, Slot #4 3641, Slot #5 3642, Slot #6 3643, Slot #7 3644, Slot #8 3645, Slot #9 3646, Slot #10 3647, Slot #11 In the example of FIG. 36C, one or more flexible symbols are For low priority PUSCH through grants (e.g., eMBB PUSCH3633) High priority DL grants (e.g., URLLC PDSCH36) can be scheduled. 34) also indicates that the PDSCH is transmitted on one or more of the same flexible symbols. In this case, the UE suspends the PUSCH 3635. and receives PDSCH3634.

[0231] MAC layer prioritization and preemption of uplink transmissions is described herein. For UL transmissions, the UE MAC layer has enough time to react to the grant. If a higher priority transmission is available, it may take precedence over a higher priority transmission. MAC transmissions are performed when physical transmissions are partially available at the time. The UE MAC is considered to be in conflict when the new conflicting Prioritize incoming transmissions and / or preempt existing transmissions already delivered to the physical layer possible.

[0232] If there is enough time to react to the available competing grants, the MAC Before a Protocol Data Unit (PDU) reaches the physical layer, it is divided into individual One or more MAC PDUs arrive at the physical layer, which may determine the priority of the PUSCH transmission. If there is insufficient time to prioritize competing grants before the MAC receives the grants already in the physical layer, may preempt transmission of MAC PDUs provided to the Relative priority information may be provided to the physical layer for processing.

[0233] The MAC also handles the scheduling between competing scheduling requests (SRs) and PUSCH transmissions. Similar to competing PUSCH transmissions, the MAC procedure for SR transmissions is The device is affected by minimal processing time and / or when notifying the physical layer of a transmission. can.

[0234] For configured or dynamic grants, the UE shall The MAC PDU multiplexing and assembly may be delayed up to the minimum processing time requirement of all the packets. Similarly, MAC SR processing and transmission indication to the physical layer (e.g., associated PU may be delayed (until CCH resources are available). New competing grants are awarded or become competing before the minimum processing requirements for If an SR is triggered, the UE may perform MAC transmission prioritization operations.

[0235] MAC transmission prioritization may include the following operations. MAC will issue a first grant for each outstanding grant. Which logical channels are used for each before they need to be processed taking into account minimum processing requirements? Each logical channel may determine whether an outstanding grant can be multiplexed into each PDU. For logical channels that may be configured with one or more priorities and are multiplexed into a MAC PDU The highest priority selected among them may determine the priority of the transmission. Priority may also be considered. Each MAC CE type (i.e., PHR, BSR,...) ) may have a known priority that is used to determine the priority of the PUSCH transmission. For example, the highest priority of a logical channel and MAC CE that is multiplexed into a MAC PDU is , can be used to determine PUSCH transmission priority. This operation is similar to the existing MAC P The DU multiplexing and assembly procedure can be effectively split into a two-step procedure. The existing Logical Channel Prioritization (LCP) protocol The processor multiplexes and assembles each MAC PDU for transmission. In this procedure, the priority available data is , before the multiplexing and assembly of MAC PDUs and the generation of MAC CEs begins. is determined in the first step.

[0236] Alternatively, a priority may be associated with each configured and / or dynamic grant. In this case, the priority of the logical channels multiplexed on the MAC PDU is not taken into account. Normal logical channel prioritization for data multiplexing may be performed. PUSCH transmission priority may be determined by the grant. and / or the priority associated with each grant, or the number of frames multiplexed in each MAC PDU. The priority associated with the logical channel that triggered the SR or the priority of the logical channel that triggered the SR. Depending on the degree, the MAC may determine the priority of each transmission and retransmission.

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

[0238] When transmission prioritization is applied, the lower priority grant(s) or SR Transmission may not be utilized or additional information may be required to properly prioritize transmission. The grant may be used to provide data, e.g., MAC service data. Unit (Service Data Unit: SDU) or MAC CE's MAC PDU and transmission of the MAC PDUs associated with the grant. When a grant is not used, the SR associated with the grant is transmitted. , no multiplexing or assembly of data into MAC PDUs is performed, and SR transmission is performed. I can't.

[0239] If the MAC determines that the grant will not be utilized due to transmission prioritization, the MAC is used by the MAC to properly handle higher priority transmissions that have not been cancelled. Unused grants can be sent to the gNB scheduler. This can be signaled directly or indirectly to the scheduler. In other words, prioritized transmissions may provide transmission cancellation indications.

[0240] Determined by the MAC when a lower priority transmission is not canceled by the MAC The relative priority of the assigned MAC PDU is provided to the physical layer with each MAC PDU and / or SR transmission. In addition to treating each transmission uniquely, some degree of priority may be assigned to indicate the relative priority of each transmission. Guaranteed trust information is signaled directly or indirectly to the gNB scheduler. It can be done.

[0241] How MAC transmission prioritization is determined (i.e., LCP or grant) Regardless of the priority base, when a grant is not utilized due to prioritization, the MAC is lost. This allows the procedure to recover lost grants. to the configured SR resources that are mapped to the logical channel(s) provided by By triggering an SR and / or by keeping an SR pending Buffer status reports may also be generated as a result of lost grants. When the MAC determines that the grant may not be used, this action When the physical layer determines that a grant is not available, the MAC , may be notified to initiate procedures to recover the lost grant.

[0242] After the minimum processing requirements of existing competing grants or competing SR transmissions, new competing If a grant to be sent is determined or a conflicting SR is triggered, the UE A transmission preemption operation may be performed.

[0243] The MAC transmission preemption operations may include the following operations. The MAC can be based on existing grants (i.e., grant or logical channel based) or If a new grant or SR transmission is decided before the minimum grant processing time for the SR transmission, The transmission priority may be determined similarly to how prioritization is determined when

[0244] New grants or SR transmissions are given higher priority than existing grants or SR transmissions. If it is determined that there is a and / or SR processing. When delivered to a lower tier, a preemption indication may be included. The indication may identify a MAC PDU or SR transmission that is preempted.

[0245] When the physical layer detects a preemption indication, the preempted transmission is given priority. The received transmission is discarded or adjusted (i.e., panned) to ensure proper transmission. If a transmission is discarded by the physical layer, the MAC can be notified. For discarded MAC PDU transmissions, the MAC must use a For example, if a HARQ NACK is received for a canceled transmission, The maximum number of HARQ retransmissions is 100% when a transmission is cancelled. may be incremented to allow as many actual transmissions as would otherwise be permitted. For an abandoned SR transmission, the MAC cancels the SR pending state and / or If a MAC PDU containing a MAC CE is discarded, the MAC may Actions to recover and retransmit lost MAC CEs (i.e., BSR, PHR) This may re-trigger the MAC CE and / or the associated forbidden tag. This can be achieved by clearing the timer.

[0246] If an existing transmission is preempted, the new preemption transmission will be The UE may directly or indirectly provide an indication to the gNB scheduler of the scheduled transmission. This allows the gNB to reschedule the discarded transmission or to assign a lower priority It may act as if an SR was received.

[0247] If a new grant or SR transmission has lower priority than an existing MAC PDU or SR transmission, When a higher priority transmission is determined to be the priority, the MAC will not interrupt the current higher priority transmission. To determine the possible disposition of the new grant or SR transmission, or provides relative priority information to the physical layer. The MAC can then abort a new grant or SR transmission. If discarded, the MAC PDU multiplexing and assembly and / or SR transmission process This operation effectively performs MAC PDU multiplexing and assembling. Bridging and SR processing are handled in a two-step process where the prioritization is determined in the first step. The physical layer may also be notified of the cancellation.

[0248] If physical layer preemption is applicable, the MAC layer will receive the cancelled transmission. In this case, the MAC will notify the cancelled transmission at the next available grant. This operation may resume the transmission of the HARQ received for the canceled transmission. Receipt of a NAK may trigger a similar procedure. The maximum number of HARQ retransmissions is to allow as many actual transmissions as would be permitted if the If the PHY performs grant preemption or grant prioritization, Examples of scenarios in which it may be practical to do so include one or more of the following: . The physical layer may detect a preemption indication from the MAC.

[0249] The MAC may instruct the PHY on transmissions with transmission priority. Transmission preemption may be performed based on the transmission priority provided thereby.

[0250] The MAC handles traffic for deprioritized and / or preempted transmissions. Deprioritized and / or preempted transmissions If a threshold number of transmissions can be exceeded, the MAC takes action to report and correct the failure of lower priority transmissions. Thresholds for deprioritized and / or preempted transmissions When a value occurs for a logical channel or a specific grant, the transmission failure can be corrected more efficiently. A higher priority layer may be notified to take action to Reporting status to the scheduler and / or the relative priority of logical channels for grants It could be an adjustment.

[0251] The 3rd Generation Partnership Project (3GPP) is a global leader in wireless access, core transceiver, and Port network and service capabilities (codec, security, and service technologies for cellular telecommunications network technologies, including those affecting the quality of The latest Radio Access Technology (RAT) standards (commonly referred to as 3G) Wideband CDMA (WCDMA (registered trademark)) and 4G (generally referred to as 4G) LTE (also known as "LTE") and LTE-Advanced standards. 3GPP also calls it "5G." The United States has begun standardizing the next generation of cellular technology known as New Radio (NR). GPP NR standards development may include the definition of next generation radio access technologies (new RATs). This is expected to provide new flexible wireless access below 6 GHz. , providing new ultra-mobile broadband wireless access above 6 GHz, including Flexible wireless access is expected to expand in new spectrum below 6 GHz. It is expected that new non-backward compatible wireless access will be configured in the same spectrum. are multiplexed together in a single vector to support a wide range of 3GPP NR use cases with diverse requirements. It is anticipated that the technology will include different modes of operation that can accommodate ultra-mobile devices. Broadband is an ultra-mobile broadband access, e.g. for indoor use and home It is expected to include centimeter-wave and millimeter-wave spectrum, offering opportunities for hotspots. In particular, ultra-mobile broadband is designed specifically for centimeter-wave and millimeter-wave. A common design framework for flexible wireless access below 6GHz, with optimizations It is expected that he will share it with Seth.

[0252] 3GPP has defined various user experience requirements for data rate, latency, and mobility. This results in identifying various use cases that NR is expected to support. Use cases fall into the following general categories: enhanced mobile broadband (e.g. For example, broadband access in densely populated areas, indoor ultra-high-speed broadband access, Access, broadband access in crowds, 50+Mbps everywhere, ultra-low cost broadband access in vehicles), critical communications, large-scale mass transit Synthetic communication, network operation (e.g., network slicing, routing) , migration and interworking, energy saving), and enhanced vehicle-to-everywhere This includes enhanced Vehicle-To-Everything (eV2X) communication, which includes: Vehicle-to-Vehicle (V2V) communication, vehicle-to-infrastructure Vehicle-To-Infrastructure (V2I) communication, Vehicle-to-Network (Vehicle-to-Network) Vehicle-To-Network (V2N) communication, Vehicle-To-Pedestrian (V2P) ) communications with other entities, and vehicular communications with other entities. Specific services and applications in the category include, for example, and monitoring and sensor networks, device remote control, two-way remote control, personal computers Cloud computing, video streaming, wireless cloud-based office, 1. Responder connectivity, car e-call, disaster warning, real-time gaming, multiplayer video These include deodorant, autonomous driving, augmented reality, tactile internet, and virtual reality. All of these use cases, and others, are contemplated herein.

[0253] FIG. 37A is an exemplary diagram in which the methods and apparatus described and claimed herein may be implemented. 1 illustrates an embodiment of an exemplary communication system 100. As shown, the exemplary communication system 1 00 is a wireless transmit / receive unit (which may be generally or collectively referred to as a WTRU 102). WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g and Radio 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 The V2X server (or ProSe function) is a V2X network 110, another network 112, and a V2X server (or ProSe function). and server) 113, although the disclosed embodiments may include any number of WTRUs, It will be appreciated that the present invention contemplates base stations, networks, and / or network elements. WTRU102a, 102b, 102c, 102d, 102e, 102f, 102g Each may be any type of device or network configured to operate and / or communicate in a wireless environment. Each of the WTRUs 102a, 102b, 102c, 102d, 102 37A-37E are handheld wireless communication devices. However, with the various use cases being considered for 5G wireless communications, each WTRU By way of example only, a user equipment (UE), mobile station, fixed or mobile subscriber unit (UE) Knits, pagers, cellular phones, personal digital assistants (PDAs) PDAs), smartphones, laptops, tablets, netbooks, notebook computers computers, personal computers, wireless sensors, consumer electronics, smartwatches Wearable devices such as smart phones or smart clothing, medical or e-health devices, robots, vehicles, such as cars, trucks, trains, or airplanes. Any type of device or equipment configured to transmit and / or receive radio signals, including It should be understood that the present invention may comprise or be embodied in a device.

[0254] The communications system 100 may also include a base station 114a and a base station 114b. The station 114a is in wireless communication with at least one of the WTRUs 102a, 102b, and 102c. Interfaces with core network 106 / 107 / 109 and Internet 1 10, and / or one or more communication networks, such as other networks 112. The base station 1 may be any type of device configured to facilitate access to 14b includes remote radio heads (RRH) 118a, 118b, TR P (transmitting and receiving points) 119a, 119b and / or roadside units (Ro and / or or wirelessly interfaced to the core network 106 / 107 / 109, the internet 110, other networks 112, and / or the V2X server (or Access to one or more communication networks, such as ProSe Functions and Servers 113 The RRH 118a may be any type of device configured to facilitate the process. 118b wirelessly interfaces with at least one of the WTRUs 102c. , core network 106 / 107 / 109, Internet 110, and / or others facilitating access to one or more communications networks, such as network 112 of The TRPs 119a and 119b may be any type of device configured to and wirelessly interfaces with at least one of the TRUs 102d to form a core network. Network 106 / 107 / 109, Internet 110, and / or other networks 112, The RSUs 120a and 120b may be any type of device. It interfaces wirelessly with at least one of 102e or 102f and is compatible with the core network. Network 106 / 107 / 109, Internet 110, other networks 112, etc. and / or one of the V2X servers (or ProSe functions and servers) 113, etc. or any type of device configured to facilitate access to multiple communications networks As an example, the base stations 114a, 114b may be base transceiver stations. Transceiver Station (BTS), Node B, eNode B, Home Node B, Home e Node B, site controller, access point (AP), wireless router The base stations 114a, 114b are each depicted as a single element. However, the base stations 114a, 114b may be connected to any number of interconnected base stations and / or networks. It will be appreciated that the network components may be included.

[0255] The base station 114a may be part of the RANs 103 / 104 / 105, which may also be In addition, the Base Station Controller (BSC), the wireless network controller, other base stations and relay nodes such as Radio Network Controller (RNC), The base station 114b may also include other network elements (not shown). b / 104b / 105b, which may also be part of a base station controller (B Other base stations and The base station 114a may also include a network element (not shown). The geographic area may be configured to transmit and / or receive wireless signals within the geographic area. The base station 114b may be referred to as a wired and / or wireless base station (not shown) within a particular geographic area. or may be configured to transmit and / or receive radio signals, and the geographic area may be (not shown). The cell may be further divided into cell sectors. For example, a base station The cell associated with 114a may be divided into three sectors. In one embodiment, the base station 114a may include, for example, three transceivers, one for each sector of the cell. In one embodiment, the base station 114a is a multiple-input multiple-output (MIM) Multiple Output (MIMO) technology may be employed, thus providing multiple transceivers per sector of a cell. It can be used.

[0256] The base station 114a may be connected to any suitable wireless communication link (e.g., radio frequency). RF, microwave, IR, UV , visible light, centimeter wave, millimeter wave, etc.) 17 may communicate with one or more of the WTRUs 102a, 102b, 102c. The air interface 115 / 116 / 117 may be implemented using any suitable radio access technology (e.g., RAT).

[0257] The base station 114b may be connected via any suitable wired (e.g., cable, fiber optic, etc.) or Wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet ( UV, visible light, centimeter-wave, millimeter-wave, etc.), wired or air interface RRH118a, 118b, TRP119a, 1 via 115b / 116b / 117b 19b, and / or one or more of RSUs 120a and 120b. The air interfaces 115b / 116b / 117b may be any suitable wireless access point. The method can be established using the RAT.

[0258] RRH118a, 118b, TRP119a, 119b, and / or RSU120 a, 120b may be any suitable wireless communication link (e.g., radio frequency (RF), microwave Wave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc. WTRUs 102c and 102d via the air interfaces 115c / 116c / 117c , 102e, 102f. 5c / 116c / 117c can be established using any suitable radio access technology (RAT). It can be done.

[0259] WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or or 102g may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, Wave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc. can communicate with each other via the air interfaces 115d / 116d / 117d (not shown). The air interface 115d / 116d / 117d may be any suitable wireless access point. This can be established using the RAT technology.

[0260] More specifically, as noted above, communication system 100 is a multiple access system. and one or more of CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. may employ multiple channel access schemes. For example, RAN103 / 104 / 10 5, the base station 114a and the WTRUs 102a, 102b, 102c, or the RAN 10 RRH118a, 118b, TRP119a, 119b in 3b / 104b / 105b, and RSUs 120a and 120b, and WTRUs 102c, 102d, 102e, 1 02f is a Universal Mobile Telecommunications System (UMTS) tions System (UMTS), Universal Terrestrial Radio Access cess (UTRA), thereby implementing wireless technologies such as Wideband CDMA (WCDMA), ) using the air interface 115 / 116 / 117 or 115c / 116c WCDMA is a high-speed packet access (HSPA) technology. Packet Access (HSPA) and / or Evolved HSPA (HSPA) 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, the base station 114a and the WTRUs 102a, 102b, 102c, and RRH118a, 118b, and TRP119a in RAN103b / 104b / 105b , 119b, and / or RSUs 120a, 120b, and WTRU 102c, 102d is Evolved UMTS Terrestrial Radio Access Wireless technologies such as E-UTRA (Evolutionary Unmanned Aeronautical Technology Transfer Protocol) may be implemented, thereby enabling long-term Evolutionary LTE and / or LTE-Advanced (LTE-A ) using the air interface 115 / 116 / 117 or 115c / 116c In the future, air interfaces 115 / 116 / 117 / 117c may be established. may implement 3GPP NR technology. LTE and LTE-A technologies include (sidelink) Includes LTE D2D and V2X technologies and interfaces, such as 3GPP PNR technology is based on NR V2X technology (e.g., sidelink communication) and interfaces. Includes.

[0262] In one embodiment, the base station 114a and the WTRU 114b in the RAN 103 / 104 / 105 RRH1 in 02a, 102b, 102c, or RAN103b / 104b / 105b 18a, 118b, TRP119a, 119b, and / or RSU120a, 12 0b, and WTRUs 102c, 102d, 102e, and 102f comply with IEEE 802. 16 (e.g., Worldwide Interoperability for Microwave 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) , Interim Standard 856 (IS-856), Global System for Mobile Communications (GSMC) GSM (German for Mobile communications), GSM evolution high-speed data rate Enhanced Data Rates For GSM Evolution:EDGE, GSM EDGE( The wireless technology may be implemented using a wireless technology such as GERAN.

[0263] The base station 114c in FIG. 37A may be, for example, a wireless router, a Home Node B, a Home eNodeB, or a It can be a wireless network or an access point, such as a workplace, home, vehicle, campus, etc. Any suitable RAT for facilitating wireless connectivity within a local area may be utilized. In one embodiment, the base station 114c and the WTRU 102e are IEEE 802.11 Wireless local area networks (WLANs) are implemented using wireless technologies such as In one embodiment, the base station 114c and the WTRU may establish a wireless local area network (WLAN). 102d implements wireless technologies such as IEEE802.15 to provide wireless personal area networks. A Wireless Personal Area Network (WPAN) can be established. In this embodiment, the base station 114c and the WTRU 102e communicate with a cellular-based RAT ( For example, using WCDMA, CDMA2000, GSM, LTE, LTE-A, etc. , picocells, or femtocells. As shown in FIG. 37A, the base station 114b , may have a direct connection to the Internet 110. Thus, the base station 114c may Need to access the Internet 110 through networks 106 / 107 / 109 may not be available.

[0264] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , may communicate with the core network 106 / 107 / 109, which may , data, applications, and / or voice over Internet Protocol (Voice over Internet Protocol: VoIP) service to WTRU 102a, 102 b, 102c, 102d, or any other For example, the core network 106 / 107 / 109 may be a Call control, billing services, mobile location-based services, prepaid calls, internet Provides network connectivity, video distribution, etc., and / or provides advanced features such as user authentication. 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 may communicate directly or indirectly with other RANs employing the same or different RATs. For example, a RAN 103 / 10 that may utilize E-UTRA radio technology may be used. In addition to being connected to RAN 4 / 105 and / or RAN 103b / 104b / 105b The core network 106 / 107 / 109 also includes another R It may communicate with an AN (not shown).

[0266] The core network 106 / 107 / 109 also includes the WTRUs 102a, 102b, 10 2c, 102d, and 102e are connected to the PSTN 108, the Internet 110, and / or other 112. 08 is a line that provides Plain Old Telephone Service (POTS). The Internet 110 may include a line-switched telephone network. Transmission Control Protocol (TCP), User Datagram Protocol (User Data UDP), and the TCP / IP Internet Protocol suite Common communication protocols such as the Internet Protocol (IP) a global system of interconnected computer networks and devices that Network 112 may include systems owned and / or managed by other service providers. For example, Network 1 may include a wired or wireless communication network operated by a 12 is RAN103 / 104 / 105 and / or RAN103b / 104b / 1 05b is connected to one or more RANs that may employ the same RAT or different RATs. The core network may include another core network.

[0267] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 All of the WTRUs 102a, 102b, 102c may include multi-mode capabilities, e.g., c, 102d, and 102e are connected to different wireless networks via different wireless links. For example, the WTRU 102e shown in FIG. , a base station 114a, which may employ cellular-based wireless technology, and a base station 114b, which may employ IEEE 802.11 wireless technology. The wireless LAN may be configured to communicate with a base station 114c that may employ the wireless LAN technology.

[0268] FIG. 37B illustrates a wireless network according to embodiments presented herein, such as the WTRU 102. FIG. 37B is a block diagram of an exemplary apparatus or device configured for wired communication. As shown, the exemplary WTRU 102 includes a processor 118, a transceiver 120, and a transmitter. / receiving element 122, speaker / microphone 124, keypad 126, and display 128, non-removable memory 130, and removable a functional memory 132, a power supply 134, and a Global Positioning System (GPS) The WTRU 102 may include a GPS chipset 136 and other peripherals 138. may include any subcombination of the above elements while remaining consistent with an embodiment. It will be appreciated that the present invention may also be implemented in various other applications, including, but not limited to, base transceiver stations (BTSs), Node Bs, and the like. , Site Controller, Access Point (AP), Home Node B, Advanced Home Node eNodeB, Home evolved Node-B (HeNB), Base stations 114a and 114b, such as a system evolved Node B gateway, and a proxy node 14b, and / or base stations 114a and 114b may represent nodes as shown in FIG. It is contemplated that the embodiments may include some or all of the elements shown in and described herein. will be done.

[0269] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors one or more microprocessors associated with the DSP cores; a controller; Microcontrollers, Application Specific Integrated Circuits ASIC, Field Programmable Gate Array FPGA (Field Programmable Gate Array) circuits, any other type of Integrated Circuit (IC) C), a state machine, etc. The processor 118 may be used for signal coding, data processing, etc. , power control, input / output processing, and / or operation of the WTRU 102 within the wireless environment. The processor 118 may perform any other function that enables the transmit / receive element 12 37B shows the individual components and the transceiver 120 which can be connected to the 2. Although the processor 118 and the transceiver 120 are depicted as a It will be appreciated that the transceiver 120 may be integrated together in an electronic package or chip. Hello.

[0270] The transmit / receive element 122 communicates with the base station via the air interface 115 / 116 / 117. 114a) to transmit signals to or receive signals from a station (e.g., base station 114a). For example, in one embodiment, the transmit / receive element 122 may be configured to transmit and receive RF signals. In one embodiment, the antenna may be configured to transmit and / or receive. The receiving element 122 may transmit and / or receive, for example, IR, UV, or visible light signals. In a further embodiment, the transmit / receive element may be an emitter / detector configured to 122 may be configured to transmit and receive both RF and optical signals. The receiving element 122 is configured to transmit and / or receive any combination of wireless signals. It will be understood that this can be done.

[0271] Additionally, although the transmit / receive element 122 is depicted in FIG. 37B as a single element, The TRU 102 may include any number of transmit / receive elements 122. More specifically, the WTR The WTRU 102 may employ MIMO technology. transmits and receives radio signals via the air interface 115 / 116 / 117. The transmitter / receiver element 122 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting the received signal.

[0272] The transceiver 120 modulates the signal to be transmitted by the transmit / receive element 122. , may be configured to demodulate signals received by the transmit / receive element 122. Thus, the WTRU 102 may have multi-mode capabilities. The WTRU 102 may be configured to support multiple RAs, such as UTRA and IEEE 802.11. The device may include multiple transceivers to enable communication via T.

[0273] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 1 26, and / or a display / touchpad / indicator 128 (e.g., LCD Display (Liquid Crystal Display: LCD) display unit or organic Organic Light-Emitting Diode (OLED) display unit The processor 118 may be connected to and receive user input data therefrom. The data is transmitted to a speaker / microphone 124, a keypad 126, and / or a display. In addition, the processor 118 may output the Any type of memory, such as non-removable memory 130 and / or removable memory 132 Information may be accessed from and data may be stored in suitable memory. 30 is Random-Access Memory (RAM), Read-Only Memory Read-Only Memory (ROM), hard disk, or any other type of memory The removable memory 132 may include a memory storage device. Subscriber Identity Module (SIM) cards, memory sticks, Secure Digital ( In one embodiment, the processor 1 may include a Secure Digital (SD) memory card. 18 is physically located on the WTRU 102, such as on a server or home computer (not shown). The information may be accessed from and data may be stored in memory that is not locally located.

[0274] The processor 118 may receive power from the power supply 134 and may also receive power from the other components within the WTRU 102. The power supply 134 may be configured to distribute and / or control power to the components. The power supply 134 may be any suitable device for powering the TRU 102. For example, the power supply 134 may be , may include one or more dry batteries, solar cells, fuel cells, etc.

[0275] The processor 118 also generates location information (e.g., longitude, and latitude). In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 , via air interfaces 115 / 116 / 117 to a base station (e.g., base station 114 a, 114b) and / or from two or more nearby base stations. The WTRU 102 may determine its location based on the timing of the signals being transmitted. Position information may be obtained by any suitable position determination method while remaining consistent with the morphology. Let it be understood.

[0276] The processor 118 may further include additional features, functionality, and / or wired or wireless connections. One or more pieces of software and / or hardware that provide the activity The peripherals 138 may be connected to other peripherals 138, which may include modules. For example, the peripherals 138 may be ,various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, and e-compasses. , satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus ( Universal Serial Bus (USB) port or other interconnection interface, vibration device devices, TV receivers, hands-free headsets, Bluetooth (registered trademark) Module, Frequency Modulated (FM) radio unit, digital music player Layer, Media Player, Video Game Player Module, Internet Browser etc.

[0277] The WTRU102 is ideal for sensors, consumer electronics products, smart watches, or smart clothing. Wearable devices, medical or e-health devices, robots, industrial equipment, other apparatus or device, such as a car, truck, train, or airplane vehicle. The WTRU 102 may be embodied in an interconnection interface that may comprise one of the peripherals 138. the device or devices via one or more interconnection interfaces, such as a or other components, modules, or systems of the device.

[0278] FIG. 37C illustrates a system of the RAN 103 and the core network 106 according to one embodiment. As mentioned above, the RAN 103 employs UTRA radio technology to The WTRUs may communicate with the WTRUs 102a, 102b, and 102c via an interface 115. The RAN 103 may also communicate with the core network 106. As shown in FIG. The AN 103 communicates with the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102i, 102j ... Node Bs 140a, 140b, 140c, 140d, 140e, 140f ... Each of the Node Bs 140a, 140b, and 140c may include a RAN1 RAN 103 may be associated with a particular cell (not shown) within RNC 14. RAN 103 may include any number of nodes while remaining consistent with the embodiment. It will be understood that the RNC may include a node B and an RNC.

[0279] As shown in FIG. 37C, Node Bs 140a, 140b may communicate with an RNC 142a. Additionally, Node B 140c may communicate with RNC 142b. 0b, 140c communicate with the respective RNCs 142a, 142b, 142c via the Iub interface. RNCs 142a and 142b can communicate with each other via the Iur interface. Each of the RNCs 142a, 142b can communicate with the respective nodes to which it is connected. In addition, the RNC 14 2a, 142b each perform outer loop power control, load control, admission control, packet scheduling, and the like. Judging, handover control, macro diversity, security function, data encryption It may be configured to perform or support other functions, such as encryption.

[0280] The core network 106 shown in FIG. 37C includes a media gateway (MG). MGW) 144, Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148; and / or Gateway GPRS Support Node (GGPRS Support Node: Each of the above elements may be part of the core network 106. Although shown as a separate entity, any one of these elements may be part of a larger network than the core network operator. It will be understood that the information contained herein may be owned and / or operated by an outside entity.

[0281] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may , providing access to a circuit-switched network such as the PSTN 108; , 102b, 102c and conventional terrestrial communication devices.

[0282] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 15 in the network 106. 0. The SGSN 148 and the GGSN 150 may be connected to the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102i, 102m .... b, 102c to provide access to packet-switched networks such as the Internet 110 and facilitates communication between the WTRUs 102a, 102b, and 102c and IP-enabled devices. possible.

[0283] As noted above, the core network 106 may also be owned by other service providers. and / or other wired or wireless networks operated by It can be connected to 2.

[0284] FIG. 37D illustrates a system of the RAN 104 and the core network 107 according to one embodiment. As mentioned above, the RAN 104 employs E-UTRA radio technology and is may communicate with the WTRUs 102a, 102b, and 102c via the interface 116. The RAN 104 may also be in communication with a core network 107.

[0285] The RAN 104 may include eNodeBs 160a, 160b, and 160c. It will be appreciated that 4 may include any number of eNodeBs while remaining consistent with the embodiment. Each of the eNodeBs 160a, 160b, and 160c communicates over the air interface 116. and one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c. In one embodiment, the eNodeBs 160a, 160b, 160c may include MIMO technology. Thus, the eNodeB 160a may implement, for example, , may transmit wireless signals to and receive wireless signals from the WTRU 102a. do.

[0286] Each of the eNodeBs 160a, 160b, and 160c is associated with a particular cell (not shown). Radio resource management decisions, handover decisions, uplink and / or The UE may be configured to handle scheduling of users on the downlink or the UE. As shown in 37D, the eNodeBs 160a, 160b, and 160c communicate over the X2 interface. They can communicate with each other via the

[0287] The core network 107 shown in FIG. 37D includes a mobility management gateway (Mobility Management Gateway). Management Gateway (MME) 162, a serving gateway 164, and a packet a Packet Data Network (PDN) gateway 166; Each of the above elements is shown as part of the core network 107, which Any one of these elements may be provided by an entity other than the core network operator. It will be understood that the information contained herein may be owned and / or operated by a third party.

[0288] The MME 162 communicates with the eNodeB 160 in the RAN 104 via the S1 interface. a, 160b, and 160c, and can function as control nodes. For example, the MME 162 may authenticate users of the WTRUs 102a, 102b, and 102c. Bearer activation / deactivation, initial activation of WTRUs 102a, 102b, and 102c It may play a role in selecting a specific Serving Gateway during touchdown. 2 also includes the RAN 104 and other RANs employing other wireless technologies such as GSM or WCDMA. It may provide a control plane function for switching between an AN (not shown).

[0289] The serving gateway 164 communicates with the RAN 104 via the S1 interface. A serving gateway may be connected to each of the eNodeBs 160a, 160b, and 160c. The gateway 164 generally transmits user data packets to the WTRUs 102a, 102b, 10 2c. The serving gateway 164 also controls the user plane during inter-eNodeB handover. anchor, downlink data is available for WTRUs 102a, 102b, and 102c triggering paging when the WTRUs 102a, 102b, and 102c are enabled, It may also perform other functions such as managing and storing records.

[0290] The serving gateway 164 also notifies the WTRUs 102a, 102b, and 102c provides access to packet-switched networks such as the Internet 110, and PDN gateways that can facilitate communication between 102a, 102b, 102c and IP-enabled devices It may be connected to way 166.

[0291] The core network 107 may facilitate communication with other networks. The network 107 provides the WTRUs 102a, 102b, and 102c with a PSTN 108, etc. providing access to a circuit-switched network and For example, the core network 107 may facilitate communication between conventional terrestrial communication devices. , which acts as an interface between the core network 107 and the PSTN 108; IP gateways (e.g., IP Multimedia Subsystems) In addition, the core network may include or communicate with an IMS (Intermediate System) server. 107 is configured to transmit the WTRUs 102a, 102b, and 102c to the WTRUs 102a, 102b, and 102c by other service providers. Networks that may include other owned and / or operated wired or wireless networks 112.

[0292] FIG. 37E illustrates a system of the RAN 105 and the core network 109 according to one embodiment. The RAN 105 uses IEEE802.16 wireless technology and has an air interface. and an access point 117 for communicating with the WTRUs 102a, 102b, and 102c. It can be an Access Service Network (ASN). As discussed, the WTRUs 102a, 102b, 102c, the RAN 105, and the core The communication links between different functional entities of the network 109 are defined as reference points. It is possible.

[0293] As shown in FIG. 37E, the RAN 105 includes base stations 180a, 180b, and 180c. SN gateway 182, while RAN 105 remains consistent with the embodiment. It will be appreciated that the base station 1 may include any number of base stations and ASN gateways. 80a, 180b, 180c may each be associated with a particular cell within the RAN 105, to communicate with the WTRUs 102a, 102b, and 102c via the air interface 117. In one embodiment, the base stations 180a, 180b , 180c may implement MIMO technology. A number of antennas are used to transmit wireless signals to the WTRU 102a and The base stations 180a, 180b, and 180c may also receive radio signals from Triggering, tunnel establishment, radio resource management, traffic classification, Quality of Service (QoS) The ASN gateway 182 may provide mobility management functions such as policy enforcement. It can act as a traffic aggregation point, paging, subscriber profile The network controller 104 may play a role in caching the traffic, routing to the core network 109, etc.

[0294] Air interface between the WTRUs 102a, 102b, 102c and the RAN 105 117 may be defined as the R1 reference point that implements the IEEE 802.16 specification. Each of the WTRUs 102a, 102b, and 102c communicates with the core network 109. A logical interface (not shown) may be established between the WTRUs 102a, 102b, and 102c. The logical interface between 2c and the core network 109 provides authentication, authorization, IP hosting, Defined as an R2 reference point that may be used for network configuration management, and / or mobility management. It can be considered.

[0295] The communication link between each of the base stations 180a, 180b, and 180c is R8 Reference Protocol, which contains protocols for facilitating handover and the transfer of data between base stations. The base stations 180a, 180b, and 180c and the ASN gateway 18 The communication link between the WT 2 and the R6 reference point may be defined as the R6 reference point. Based on the mobility events associated with each of the RUs 102a, 102b, and 102c, It may include protocols for facilitating mobility management through

[0296] As shown in FIG. 37E, the RAN 105 may be connected to a core network 109. The communication link between the AN 105 and the core network 109 is used for, e.g., data transfer and May be defined as an R3 reference point containing protocols to facilitate mobility management capabilities The core network 109 includes a Mobile IP Home Agent (MHA). ent:MIP-HA) 184 and Authentication, Authorization, and Accounting (Authentication Autho The authentication and accounting (AAA) server 186 and the gateway 188 may be included. Although each of the above elements is shown as part of the core network 109, these elements Any one of the elements may be owned by an entity other than the core network operator. and / or operated by the

[0297] The MIP-HA may be responsible for IP address management, and 102c roaming between different ASNs and / or different core networks MIP-HA184 may enable WTRUs 102a, 102b, and 102b to c to a packet-switched network such as the Internet 110, This may facilitate communication between the TRUs 102a, 102b, and 102c and IP-enabled devices. The AA server 186 may be responsible for user authentication and support of user services. The gateway 188 may facilitate interworking with other networks, for example The gateway 188 provides the WTRUs 102a, 102b, and 102c with a PSTN 108 or other which provides access to the circuit-switched network, and In addition, the gateway 188 may facilitate communication between the , WTRUs 102a, 102b, 102c may be connected to other networks owned and operated by other service providers. to a network 112, which may include other wired or wireless networks operated by the may provide access to

[0298] Although not shown in FIG. 37E, the RAN 105 may be connected to other ASNs, forming a core network. It will be appreciated that the RAN1 network 109 may be connected to other core networks. The communication link between the RAN 105 and other ASNs is the WTRU 1 R4 references may include protocols for coordinating mobility between R2a, 102b, and 102c. The communication between the core network 109 and other core networks can be defined as a reference point. The communication link is the interworking between the home core network and the visited core network. An R5 reference may be defined which may include protocols for facilitating the king.

[0299] The core described herein and shown in Figures 37A, 37C, 37D, and 37E Network entities may be subject to certain existing 3GPP specifications. Although these entities and functions are identified by the names given, in the future, these entities and functions may be identified by other names. The specific entity or function may be identified by its name in future 3GPP NR specifications. It is understood that this specification may be combined in future specifications published by 3GPP, including Therefore, the structures described and shown in Figures 37A, 37B, 37C, 37D, and 37E The specific network entities and functions shown are provided by way of example only and are not intended to be limiting of the scope of this specification. Is the subject matter disclosed and claimed in the document currently defined or hereafter defined? It is understood that the present invention may be embodied or implemented in any similar communication system, regardless of whether it is implemented in a wireless communication system. sea ​​bream.

[0300] FIG. 37F is a block diagram of an exemplary computing system 90, in which: RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108 , a particular node or function entity on the Internet 110 or other network 112 37A, 37C, 37D, and 37E, such as the The computing system 90 may be implemented as one or more of the following devices: The software may be stored in a computer or server. or accessed from any computer (wherever or by whatever means) The computer readable instructions may be primarily controlled by the computer. The processor 91 may execute the program 90 to run the operating system 90. 1 is a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, DSP, multiple microprocessors, one or more associated DSP cores Microprocessors, controllers, microcontrollers, application specific integrated circuits ( ASIC), Field Programmable Gate Array (FPGA), any other type The processor 91 may be a signal coding integrated circuit (IC), a state machine, etc. programming, data processing, power control, input / output processing, and / or computing systems It may also perform any other function that enables system 90 to operate within a communications network. The coprocessor 81 is an optional processor that is distinct from the main processor 91. and may perform additional functions or assist processor 91. and / or co-processor 81 for processing data related to the methods and apparatus disclosed herein. The device may receive, generate, and process data.

[0301] In operation, the processor 91 fetches, decodes, and executes instructions to perform the computer's The information is transmitted to other routers via the system bus 80, which is the main data transfer path of the operating system. The system bus transfers data to and from other resources. It connects the components within the operating system 90 and defines the medium for data exchange. The system bus 80 typically includes data lines for transmitting data and addresses. Address lines for sending, interrupts, and the system bus and control lines for operating the peripheral components. The PCI bus is a Peripheral Component Interconnect (PCI) bus.

[0302] The memories connected to the system bus 80 include a random access memory (RAM) 82 and and a read only memory (ROM) 93. The memory is a memory in which information is stored and read. ROM 93 generally contains circuitry that allows it to be easily modified. The data stored in RAM 82 is stored in the processor 91. RAM or other hardware devices. Access to the ROM 82 and / or ROM 93 is controlled by a memory controller 92. When an instruction is executed, the memory controller 92 converts the virtual address into a physical address. The memory controller 92 may also provide an address translation function that converts the Memory protection features that isolate processes within the system and isolate system processes from user processes Thus, a program running in the first mode may provide its own process Only memory mapped by the virtual address space can be accessed, and Unless memory sharing is configured, a process cannot access memory in the virtual address space of another process. cannot access.

[0303] In addition, the computing system 90 may include a processor 91, a printer 94, a keyboard 96, and a keyboard 98. communicates commands to peripheral devices such as the board 84, mouse 95, and disk drive 85 The peripheral controller 83 may also serve as a

[0304] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the display system 90. Output can include text, graphics, animated graphics, and video. The visual output is called a Graphical User Interface (G The display 86 may be provided in the form of a CRT-based video display. , LCD-based flat panel displays, gas plasma-based flat panel displays The display controller 96 may be implemented using a display or a touch panel. The electronic components required to generate the video signal that is sent to the display 86 are Includes components.

[0305] Furthermore, the computing system 90 may be configured to N103 / 104 / 105, Core Network 106 / 107 / 109, PSTN108 , Internet 110, or other of Figures 37A, 37B, 37C, 37D, and 37E. 112, for example. For example, the computing system 90 includes communication circuitry such as a network adapter 97. to communicate with other nodes or functional entities of their network. The communication circuitry, alone or in combination with the processor 91, may include any of the components described herein. A particular device, node, or functional entity performs the transmitting and receiving steps. It can be used for

[0306] FIG. 37G illustrates an exemplary system in which the methods and apparatus described and claimed herein may be implemented. 1 illustrates an embodiment of an exemplary communication system 111. As shown, the exemplary communication system 111 11 is a diagram showing wireless transmission / reception units (WTRUs) A, B, C, D, E, and F, a base station, and V 2X server and RSUs A and B, but the disclosed embodiments may be implemented with any number of The WTRU, base station, network, and / or network elements may be considered. It will be understood that one or some or all of the WTRUs A, B, C, D, E is outside the range of the network (e.g., the cell coverage boundary shown as a dashed line in the figure). WTRUs A, B, and C can be in the W TRUs B and C form a V2X group of which they are group members. WTRU A , B, C, D, E, F are Uu interface or side link (PC5) interface They may communicate via an interface.

[0307] Any of the devices, systems, methods, and processes described herein or All are implemented as computer-executable instructions (e.g., , program code), the instructions of which may be implemented by the processor 118 or 91. When executed by a processor such as It is understood that the methods and processes may be performed and / or implemented. Any of the steps, acts, or functions described herein may be implemented by the computer. implemented in the form of computer-executable instructions and configured for wireless and / or wired network communication. The program may be executed on a processor of a computer-implemented device or computing system. A computer-readable storage medium is any non-transitory (e.g., tangible or physical) medium for storing information. Volatile and non-volatile media, removable and detachable, implemented in any method or technology The computer-readable storage medium includes a computer-readable medium, but does not include a signal. The readable storage medium may be a RAM, a ROM, an EEPROM, a flash memory, or other memory. technology, CD-ROMs, and Digital Versatile Disks (DVDs) or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage device, or may be used to store desired information; and Any other tangible or physical medium that can be accessed by a computing system Including, but not limited to:

Claims

1. An apparatus comprising one or more processors and a memory, wherein the memory of the apparatus further comprising computer executable instructions stored in memory, said computer executable instructions The instructions, when executed by the one or more processors of the device, On the chair, receiving first information indicating a first uplink grant associated with the first transmission; 、 receiving second information indicating a second uplink grant associated with the second transmission; 、 The first transmission and the second transmission are performed based on the first information and the second information. determining that the transmissions at least partially overlap in time; a first priority associated with the first transmission and a second priority associated with the second transmission; Determine the second priority, based at least in part on the first priority and the second priority; the first transmission having priority over the other of the first transmission and the second transmission; prioritizing one of the second transmissions; or preemption of the first transmission by the second transmission; An apparatus for producing at least one of the following:

2. Determining the first priority includes: performing a logical channel prioritization procedure to determine whether data is being sent to the first uplink; Grant Medium Access Control (MAC) layer protocol data Selecting logical channels to be multiplexed into a Protocol Data Unit (PDU) and, The first priority has the highest priority logical channel among the logical channels. and determining:

3. Determining the second priority includes: performing a logical channel prioritization procedure to determine whether data is being transmitted to the second uplink; Grant Medium Access Control (MAC) layer protocol data Selecting logical channels to be multiplexed into a Protocol Data Unit (PDU) and, The second priority has the highest priority logical channel among the logical channels. and determining:

4. The computer-executable instructions are executed by the one or more processors. The device then further comprises: The first priority is a priority associated with the first uplink grant. The apparatus of claim 1 , wherein the apparatus determines:

5. The computer-executable instructions are executed by the one or more processors. The device then further comprises: The second priority is a priority associated with the second uplink grant. The apparatus of claim 1 , wherein the apparatus determines:

6. causing the prioritization of one transmission over the other transmission comprises: If the first priority is higher than the second priority, the second transmission is prioritized. Prioritizing transmission of 1, or The second priority is higher than the first priority, and the data associated with the second transmission If no data is submitted to the physical layer, the second transmission is prioritized over the first transmission. The apparatus of claim 1 , further comprising:

7. The computer-executable instructions are executed by the one or more processors. The device then further comprises: transmitting data for the prioritized first transmission or the prioritized second transmission to the physical layer; 7. The apparatus of claim 6 .

8. The data for the prioritized first or second transmission may include one or more Medium Access Control (MAC) Service Data Unit a QoS Data Unit (SDU), or one or more MAC Control Elements (Control Elements). nt:CE).

9. The data for the prioritized first transmission or the prioritized second transmission is stored in a scheduling list.

8. The device of claim 7, wherein the request is a Scheduling Request (SR).

10. The computer-executable instructions are executed by the one or more processors. The device then further comprises: giving priority to the first transmission; canceling the second transmission; notifying the physical layer of the cancellation of the second transmission; notifying the network that the second uplink grant is not in use; The device according to claim 6 .

11. The computer-executable instructions are executed by the one or more processors. The device then further comprises: giving priority to the second transmission; canceling the first transmission; notifying the physical layer of the cancellation of the first transmission; Informing the network that the first uplink grant is not in use 7. The apparatus of claim 6 .

12. Informing the network that the second uplink grant is not in use. That is, Scheduling Request (SR) or Buffer Status Report to the network to receive a new uplink grant for the second transmission. The apparatus of claim 10 , further comprising: requesting

13. The second uplink grant is a scheduling request est: SR), and the SR pending state is for the second uplink grant.

11. The device of claim 10, wherein the device is maintained by

14. Informing the network that the first uplink grant is unused. What is that? Scheduling Request (SR) or Buffer Status Report to the network to receive a new uplink grant for the first transmission. The apparatus of claim 11 , further comprising: requesting

15. The first uplink grant is a scheduling request est: SR), and the SR pending state is for the first uplink grant.

12. The device of claim 11, wherein the device is maintained by

16. The computer-executable instructions are executed by the one or more processors. The device then further comprises: transmitting first data for the first transmission having the first priority to a physical layer; 、 transmitting second data for the second transmission having the second priority to the physical layer; The device of claim 1 .

17. causing the preemption of the first transmission by the second transmission comprises: The second priority is higher than the first priority, and the data for the first transmission is The second transmission preempts the first transmission if it has already been transmitted to the physical layer. The apparatus of claim 1 , further comprising:

18. The computer-executable instructions are executed by the one or more processors. The device then further comprises: Indicating to the physical layer to preempt the first transmission and The apparatus of claim 17 , further comprising: causing the physical layer to transmit second data.

19. Determining the first priority and the second priority includes determining the first priority and the second priority based on downlink control information ( The method according to claim 1, based on third information indicated by Downlink Control Information (DCI). The apparatus described.

20. The apparatus of claim 1 , wherein the apparatus comprises a User Equipment (UE). 。

Images