Method and apparatus for transmitting information on an uplink channel

Abstract

A first information for DL assignment of a first PDSCH for a serving cell can be received (410). A first PUCCH resource and a second PUCCH resource can be identified (420) for HARQ‑ACK feedback of the first PDSCH. A starting symbol of the second PUCCH resource can be later than a starting symbol of the first PUCCH resource. A second information for DL assignment of a second PDSCH for the serving cell can be received (430). A starting symbol of the second PDSCH can be later than a starting symbol of the first PDSCH. A determination can be made (440) as to whether to delay HARQ‑ACK feedback of the first PDSCH for processing of the second PDSCH. In response to determining to delay HARQ‑ACK feedback of the first PDSCH, HARQ‑ACK information for the first PDSCH can be transmitted (450) on the second PUCCH resource.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting information on an uplink channel. Background Art

[0002] Currently, wireless communication devices such as user equipment (UE) use wireless signals to communicate with other communication devices. In Release 15 New Radio (NR), if the UE must send uplink control information (UCI) and the physical uplink control channel (PUCCH) resources used for UCI that does not include a scheduling request (SR), such as hybrid automatic repeat request acknowledgement (HARQ-ACK), periodic channel state information (P-CSI) and / or semi-persistent CSI (SP-CSI), collide with the physical uplink shared channel (PUSCH) (with or without the uplink shared channel (UL-SCH)), the physical layer (PHY) at the UE multiplexes the UCI in the PUSCH. Depending on the presence of uplink (UL) data transport blocks (TBs) (i.e., UL-SCH), the rate matching of the UCI changes. If the PUCCH collides with multiple PUSCH grants, there are clear PHY rules to determine which PUSCH is used for UCI multiplexing, without the PHY knowing which logical channel is mapped to which PUSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] In order to illustrate the manner in which the advantages and features of the present disclosure can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the present disclosure that are illustrated in the accompanying drawings. These drawings depict only example embodiments of the present disclosure and, therefore, should not be considered as limiting the scope thereof. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0004] Figure 1 is an example block diagram of a system according to a possible embodiment;

[0005] Figure 2 is an example illustration of an example scenario requiring a UE to handle two unicast physical downlink shared channels (PDSCHs) according to a possible embodiment;

[0006] Figure 3 is an example flow chart illustrating the operation of the apparatus according to a possible embodiment;

[0007] Figure 4 is an example flow chart illustrating the operation of the apparatus according to a possible embodiment; and

[0008] Figure 5 is an example block diagram of an apparatus according to a possible embodiment. DETAILED DESCRIPTION

[0009] Embodiments provide a method and apparatus for transmitting information on an uplink channel. At least some embodiments can provide methods for handling UL data / control and control / control resource conflicts. At least some embodiments can provide methods for resolving resource conflicts between SR associated with high-priority traffic and uplink data for low-priority traffic. At least some embodiments can provide prioritization and / or multiplexing behavior among HARQ-ACK / SR / CSI and PUSCH for traffic with different priorities, including cases with UCI on PUCCH and UCI on PUSCH.

[0010] At least some embodiments can provide methods for handling multiple unicast data channels associated with different traffic types.

[0011] At least some embodiments can provide information for a UE to receive two PUCCH resources (an earlier PUCCH resource and a later PUCCH resource) for HARQ-ACK feedback for a first PDSCH (potentially, a low priority PDSCH) and if the UE must delay processing of the first PDSCH due to a later received second PDSCH (potentially, a high priority PDSCH), the later PUCCH resource is used for HARQ-ACK feedback for the first PDSCH. In addition, embodiments can provide HARQ-ACK codebook construction methods for the earlier PUCCH and the later PUCCH. Providing two PUCCH resources for the low priority PDSCH can be used to minimize eMBB throughput degradation due to URLLC traffic and is expected to be resource efficient compared to frequent retransmissions of the eMBB PDSCH caused by dropping eMBB PDSCH processing.

[0012] At least some embodiments can provide detailed rules for discarding or multiplexing CSI reports with other UCI and / or UL data based on the physical layer priority of the PUCCH resources indicated for CSI reporting. This priority indication can be used by network entities to maintain the latest CSI information for the PCell of the UE or for the TRP or serving cell serving the URLLC service of the UE.

[0013] According to a possible embodiment, a PUCCH configuration including information about at least one PUCCH resource can be received at a UE. A UL grant for at least one high-priority PUSCH can be received. The UL grant can instruct the UE to include a CSI report in the at least one high-priority PUSCH. A specific PUSCH of the at least one high-priority PUSCH can overlap with a PUCCH resource of the at least one PUCCH resource. A determination can be made as to whether UCI is available for transmission on the PUCCH resource. When UCI is available for transmission on the PUCCH resource, the specific PUSCH can be transmitted according to the UL grant by including the CSI report in the specific PUSCH.

[0014] According to a possible embodiment, first information of DL assignment for a first PDSCH of a serving cell can be received. A first PUCCH resource and a second PUCCH resource can be identified for HARQ-ACK feedback of the first PDSCH. A starting symbol of the second PUCCH resource can be later than a starting symbol of the first PUCCH resource. Second information of DL assignment for a second PDSCH of a serving cell can be received. A starting symbol of the second PDSCH can be later than a starting symbol of the first PDSCH. A determination can be made as to whether to delay HARQ-ACK feedback of the first PDSCH for processing the second PDSCH. In response to determining to delay HARQ-ACK feedback of the first PDSCH, HARQ-ACK information of the first PDSCH can be transmitted on the second PUCCH resource.

[0015] Figure 1 1 is an example block diagram of a system 100 according to a possible embodiment. System 100 can include a UE 110, at least one network entity 120 and 125, and a network 130. UE 110 can be a wireless wide area network device, a user equipment (UE), a wireless terminal, a portable wireless communication device, a smartphone, a cellular phone, a flip phone, a personal digital assistant (PDA), a smartwatch, a personal computer, a tablet computer, a laptop computer, a selective call receiver, an Internet of Things (IoT) device, or any other user equipment capable of sending and receiving communication signals over a wireless network. At least one network entity 120 and 125 can be a wireless wide area network base station, a NodeB, an enhanced NodeB (eNB), a new radio (NR) NodeB (gNB), such as a fifth generation (5G) NodeB, an unlicensed network base station, an access point, a base station controller, a network controller, a transmission and reception point (TRP), a network entity of a different type than other network entities, and / or any other network entity capable of providing wireless access between a UE and a network.

[0016] The network 130 can include any type of network capable of sending and receiving wireless communication signals. For example, the network 130 can include a wireless communication network, a cellular telephone network, a time division multiple access (TDMA)-based network, a code division multiple access (CDMA)-based network, an orthogonal frequency division multiple access (OFDMA)-based network, a long term evolution (LTE) network, a NR network, a 3rd Generation Partnership Project (3GPP)-based network, a 5G network, a satellite communication network, a high altitude platform network, the Internet, and / or other communication networks.

[0017] In operation, UE 110 can communicate with network 130 via at least one network entity 120. For example, UE 110 can send and receive control signals on a control channel and send and receive user data signals on a data channel.

[0018] If a PUCCH collides with multiple PUSCH grants, PHY rules can be used to determine which PUSCH is used for UCI multiplexing without the PHY knowing which logical channel is mapped to which PUSCH. Similar principles can be applied in Release 16 NR intra-UE multiplexing for ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB). For example, if a PUCCH resource for eMBB UCI collides with two non-overlapping PUSCHs, such as one PUSCH with a URLLC TB and another PUSCH with an eMBB TB, the PHY can multiplex the eMBB UCI in the PUSCH with the eMBB TB. To let the PHY at the UE and at the gNB know which PUSCH has the eMBB TB, a PHY level indication (e.g., via an indication in UL / downlink (DL) downlink control information (DCI)) can be used.

[0019] In Release 15 NR (3GPP TS 38.213), rules are specified to transmit different UCI in PUCCH and / or PUSCH at the UE. However, the Release 15 NR specification does not provide a method for handling the collision of UCI and UL-SCH for different traffic types.

[0020] For multiple PUCCH-based CSI reporting for dropping and multiplexing rules for multiple CSI reports in a slot, if the UE is not provided with a multi-CSI-PUCCH-ResourceList or if the PUCCH resources used for transmission of the CSI reports do not overlap in the slot, the long PUCCH (i.e., PUCCH formats 3 and 4) carrying the CSI reports can be time-domain multiplexed with the short PUCCH (i.e., PUCCH format 2) carrying the CSI reports in the slot. If the UE is provided with a multi-CSI-PUCCH-ResourceList and if any of the multiple PUCCH resources overlap, the UE can multiplex all CSI reports in resources from the resources provided by the multi-CSI-PUCCH-ResourceList, as described in subclause 9.2.5.2 of TS 38.213.

[0021] For PUCCH and / or PUSCH overlapping with PUCCH and / or PUSCH resources that do not meet the timing conditions, the UE may not expect the PUCCH or PUSCH detected in response to DCI format to overlap with any other PUCCH or PUSCH that does not meet the timing conditions described in subclause 9.2.5 of TS 38.213.

[0022] For transmission of HARQ-ACK and CSI in multiple PUCCHs, if simultaneous HARQ-ACK-CSI is not provided to the UE and if the UE will transmit HARQ-ACK information in a given time slot on a long PUCCH (PUCCH format 1, 3, or 4), the UE may not transmit a long PUCCH (PUCCH format 3 or 4) for CSI reporting and the UE may not transmit an overlapping short PUCCH (PUCCH format 2) for CSI reporting in that time slot. If they overlap with any resources from the resources used for transmission of HARQ-ACK information, if simultaneous HARQ-ACK-CSI is not provided to the UE and if the UE will transmit HARQ-ACK information with PUCCH format 0 or PUCCH format 2, the UE may not transmit any PUCCH with PUCCH format 2, PUCCH format 3, or PUCCH format 4 for transmission of CSI reporting.

[0023] For UCI multiplexing on PUSCH with UL-SCH, if the PUCCH resources overlap in time with the PUSCH transmission, the UE can multiplex HARQ-ACK information and / or CSI reports in the PUSCH as described in subclause 9.3 of TS 38.213 and may not transmit an SR. In the case where the PUCCH resources overlap in time with multiple PUSCH transmissions, the PUSCH for multiplexing HARQ-ACK information and / or CSI can be selected as described in subclause 9 of TS 38.213. If the PUSCH transmission by the UE is not responsive to DCI format detection and the UE multiplexes only CSI reports, the timing conditions may not apply.

[0024] If a PUSCH without UL-SCH overlaps with a PUCCH including a positive SR on the serving cell, where the symbol "*" in the SR means when the SR is positive,

[0025]

[0026] Table 1: PUSCH without UL-SCH overlaps with PUCCH including positive SR

[0027] Based on the Release 15 3GPP NR specification (3GPP TS 38.213 V15.6.0), the UE is able to generate HARQ-ACK information in response to receiving a PDSCH associated with DCI format 1_0 or DCI format 1_1 whose CRC is scrambled with C-RNTI, MCS-C-RNTI or CS-RNTI. If the UE receives a PDSCH but does not receive the corresponding PDCCH, or if the UE receives a PDCCH indicating an SPS PDSCH release, the UE is able to generate one corresponding HARQ-ACK information bit. If the PDSCH-CodeBlockGroupTransmission is not provided to the UE, the UE is able to generate one HARQ-ACK information bit per transport block. For the HARQ-ACK information bit, the UE is able to generate an ACK if it detects DCI format 1_0 providing an SPS PDSCH release or decodes the transport block correctly, and is able to generate a NACK if the UE does not decode the transport block correctly. To transmit multiple HARQ-ACK bits in one PUCCH or PUSCH resource, the UE can construct a HARQ-ACK codebook according to the rules defined in subclause 9.1 of 3GPP TS 38.213 V15.6.0.

[0028] Based on 3GPP TS 38.321, a Scheduling Request (SR) can be used to request UL-SCH resources for a new transmission. Each SR configuration can correspond to one or more logical channels. Each logical channel can be mapped to zero or one SR configuration, which can be configured by Radio Resource Control (RRC). The SR configuration of the logical channel that triggered the BSR (if such a configuration exists) can be considered as the corresponding SR configuration for the triggered SR.

[0029] At least some embodiments can provide for handling UL data / control and control / control resource conflicts for traffic having different priorities.

[0030] For example, at least some embodiments can provide various methods for a UE to transmit UCI and / or UL-SCH when multiple PUSCHs and / or PUCCHs for the UE overlap.

[0031] Assuming that the UL DCI and / or RRC configuration indicates the priority of the corresponding UL grant of PUSCH and the priority of the configured PUCCH resources and the DL DCI and / or RRC configuration indicates the priority of the corresponding DL assignment of PDSCH and the priority of the associated HARQ-ACK feedback, the UE can determine which PUSCH or PUCCH it will transmit among the conflicting PUSCH and PUCCH according to the PHY drop / multiplexing rules. In one example, the lower priority uplink channels (i.e., PUSCH and PUCCH) can include Release 15 NR uplink channels that are dynamically scheduled or semi-persistently activated based on the Release 15 NR DCI format or configured based on Release 15 NR RRC parameters.

[0032] In one implementation, if a lower priority PUCCH overlaps with a higher priority PUCCH, the UE can drop / cancel the transmission of the lower priority PUCCH. Similarly, if a lower priority PUSCH overlaps with a higher priority PUSCH, the UE can drop / cancel the transmission of the lower priority PUSCH.

[0033] In another implementation, if a high priority PUCCH carrying URLLC HARQ-ACK information, URLLC SR and / or URLLC CSI report overlaps in time with a high priority PUSCH with UL-SCH and satisfies one or more timing conditions for multiplexing (if applicable), the UE is able to multiplex the URLLC HARQ-ACK information and / or URLLC CSI report in the high priority PUSCH with UL-SCH and may not transmit the high priority PUCCH including the URLLC SR. An example of a URLLC CSI report may be an indication of a CQI offset / adjustment to be transmitted on the high priority PUCCH together with the URLLC HARQ-ACK. In addition, if the UE is instructed to send a semi-persistent or aperiodic CSI report in a high priority PUSCH with UL-SCH, the UE is able to multiplex only the URLLC HARQ-ACK information in the high priority PUSCH and may not multiplex the URLLC CSI report to be transmitted on the high priority PUCCH. This may be because a semi-persistent or aperiodic CSI report triggered by a network entity and to be transmitted on a high-priority PUSCH may include more important CSI than a URLLC CSI report to be transmitted on a high-priority PUCCH. If a high-priority PUCCH resource temporally overlaps with multiple high-priority PUSCHs that meet the timing conditions for UCI multiplexing, the high-priority PUSCH carrying aperiodic CSI can be selected for UCI multiplexing. If there is no high-priority PUSCH carrying aperiodic CSI, a high-priority PUSCH scheduled by a dynamic UL grant, located in the serving cell with the smallest ServCellIndex, and started earlier in a given serving cell can be selected for UCI multiplexing.

[0034] In other implementations, if the UE is to transmit a high priority PUCCH without UL-SCH that overlaps with a high priority PUCCH transmission including positive SR information (e.g., URLLC SR), the UE may not transmit a high priority PUSCH. If a high priority PUCCH carrying URLLC HARQ-ACK information but not including URLLC SR information overlaps in time with a high priority PUSCH without UL-SCH and meets one or more timing conditions for multiplexing (if applicable), the UE can multiplex the URLLC HARQ-ACK information in the high priority PUSCH without UL-SCH and may not transmit the high priority PUCCH. For both cases, the high priority PUSCH without UL-SCH can include semi-persistent or aperiodic CSI reports.

[0035] In one embodiment, the UE is capable of receiving an indication of the physical layer priority of the PUCCH resources configured for the CSI report, and is capable of determining whether to multiplex the CSI report with other UCI and / or UL data or discard the CSI report based on the physical layer priority of the indication of the PUCCH resources for the CSI report. In one example, the network entity is capable of configuring a high priority PUCCH resource for the UE in the CSI reporting configuration of the primary cell (PCell) so that the network entity can maintain the latest CSI information for the PCell of the UE even when the UE has URLLC service. In another example, the network entity is capable of configuring a high priority PUCCH resource for the UE in the CSI reporting configuration of one or more transmission and reception points (TRPs) or serving cells serving the URLLC service of the UE. The CSI report can be transmitted periodically or semi-persistently, where the semi-persistent CSI report is activated or deactivated via a medium access control (MAC) control element (CE) in the PDSCH. In one implementation, if the physical layer priority is not explicitly included in the PUCCH resource configuration for CSI reporting, the UE can assume that the PUCCH resource for CSI reporting is configured as low priority in the physical layer.

[0036] In one example, if the PUCCH resource for CSI reporting is configured as a high-priority PUCCH and overlaps with the PUCCH for URLLC SR information, the CSI report and the URLLC SR information can be multiplexed in the high-priority PUCCH no later than the end of the PUCCH resource for URLLC SR information. If the PUCCH resource for CSI reporting is configured as a low-priority PUCCH and overlaps with the PUCCH for URLLC SR information, the UE may not transmit the CSI report.

[0037] In one example, if the PUCCH resources for CSI reporting are configured as high priority PUCCH and overlap with PUCCH for URLLC SR information, the CSI report and URLLC SR information can be multiplexed in the high priority PUCCH, where inter-slot hopping is enabled for the high priority PUCCH including the CSI report and URLLC SR information (e.g., via the RRC parameter interslotFrequencyHopping defined in TS 38.331) and the first hop of the high priority PUCCH ends no later than the PUCCH resources for URLLC SR information.

[0038] In another example, if the PUCCH resources for CSI reporting are configured as high-priority PUCCHs and overlap with PUCCH resources for URLLC HARQ-ACK information, the CSI report and URLLC HARQ-ACK information can be multiplexed in the high-priority PUCCH that ends no later than the end of the PUCCH resources for URLLC HARQ-ACK information. If the PUCCH resources for CSI reporting are configured as low-priority PUCCHs and overlap with PUCCH resources for URLLC HARQ-ACK information, the UE may not transmit the CSI report.

[0039] In one example, if the PUCCH resources for CSI reporting are configured as high priority PUCCH and overlap with the PUCCH for URLLC HARQ-ACK information, the CSI report and the URLLC HARQ-ACK information can be multiplexed in the high priority PUCCH, where inter-slot hopping is enabled for the high priority PUCCH including the CSI report and the URLLC HARQ-ACK information (e.g., via the RRC parameter interslotFrequencyHopping defined in TS 38.331) and the first hop of the high priority PUCCH ends no later than the PUCCH resources for the URLLC HARQ-ACK information.

[0040] In other examples, if the PUCCH resource for CSI reporting is configured as a high priority PUCCH and overlaps with the URLLC PUSCH, and if the UE does not multiplex aperiodic or semi-persistent CSI reporting in the URLLC PUSCH, the UE may be able to multiplex the CSI report in the URLLC PUSCH. If the PUCCH resource for CSI reporting is configured as a low priority PUCCH or if the UE multiplexes aperiodic or semi-persistent CSI reporting in the URLLC PUSCH, the UE may not transmit the CSI report.

[0041] In other examples, if the PUCCH resources for CSI reporting are configured as high-priority PUCCH and overlap with PUCCH resources for eMBB SR and / or eMBB HARQ-ACK, the UE may not transmit eMBB SR and / or eMBB HARQ-ACK. If the PUCCH resources for CSI reporting are configured as low-priority PUCCH, the UE may be able to multiplex CSI reporting with eMBB SR and / or eMBB HARQ-ACK as specified in 3GPP TS 38.213. Alternatively, it may not be expected that the UE is configured with a high-priority PUCCH for CSI reporting that overlaps with a PUCCH including eMBB SR and / or eMBB HARQ-ACK.

[0042] In other examples, if the PUCCH resource for CSI reporting is configured as a high-priority PUCCH and overlaps with a low-priority PUSCH (including eMBB UL-SCH), the UE may not transmit or cancel transmission of the low-priority PUSCH including the eMBB UL-SCH. If the PUCCH resource for CSI reporting is configured as a low-priority PUCCH, the UE can multiplex the CSI report in the low-priority PUSCH as specified in 3GPP TS 38.213 (if applicable timing conditions are met) or can consider it as an error case (if applicable timing conditions are not met). Alternatively, it may not be expected that the UE is configured with a high-priority PUCCH for CSI reporting that overlaps with a PUSCH including an eMBB UL-SCH.

[0043] In other examples, the UE can prioritize PUCCH resources based on one or more of: a slot index; a subslot index (e.g., in a subslot-based HARQ-ACK feedback process, where, for a given subslot configuration, the UE can be configured with a PUCCH resource set and can define the starting symbol of the PUCCH resource relative to the first symbol of the subslot); a control resource set (CORESET) index, e.g., a CORESET index for transmitting a corresponding DCI, such as DCI for A-CSI triggering, DCI for SP-CSI activation, or DCI for PDSCH scheduling; and a higher layer signaling index per CORESET, which is used to generate a positive acknowledgement (ACK) / negative acknowledgement (NACK) codebook identified by the index (e.g., in the case of multi-TRP operation).

[0044] In another embodiment, if the UE is instructed to multiplex semi-persistent or aperiodic CSI reports into a high priority PUSCH overlapping with a low priority PUCCH including positive SR information (e.g., eMBB SR) and the UE will transmit a high priority PUSCH without UL-SCH on the serving cell, the UE is capable of performing at least one of the following methods.

[0045] According to a first possible approach, the UE can transmit a high-priority PUSCH including a semi-persistent or aperiodic CSI report and may not transmit a low-priority PUCCH including a positive SR. That is, regardless of the actual content in the physical uplink channel, the UE can always prioritize the physical uplink channel indicated as a higher priority.

[0046] According to a second possible approach, the UE can transmit a low-priority PUCCH including a positive SR and may not transmit a high-priority PUSCH without UL-SCH but including a semi-persistent or aperiodic CSI report. That is, regardless of the priority of the corresponding physical channel, the UE can prioritize SR information over semi-persistent or aperiodic CSI reports. Note that in addition to the eMBB SR, the low-priority PUCCH can also include eMBB HARQ-ACK.

[0047] According to a third possible approach, the UE can multiplex semi-persistent or aperiodic CSI reports and low-priority (e.g., eMBB) SR information (and additionally eMBB HARQ-ACK information, if included in the low-priority PUCCH) into a high-priority PUCCH without UL-SCH and may not transmit the low-priority PUCCH. If the network entity explicitly instructs the UE not to include UL-SCH (e.g., the UL-SCH indicator field in the DCI format 0_1 of Release 15 NR is set to 0), the network entity can assume that the eMBB SR information (i.e., an indication of positive or negative SR) is multiplexed in the high-priority PUSCH to perform decoding of the semi-persistent or aperiodic CSI report. If the UE is also adapted for HARQ-ACK reporting with overlapping low-priority PUCCH, the network entity can additionally consider the potential presence of eMBB HARQ-ACK in the high-priority PUSCH.

[0048] In an example, the UE can determine to apply spatial bundling of eMBB HARQ-ACK in the high priority PUSCH regardless of the harq-ACK-SpatialBundlingPUSCH setting for the high priority PUSCH. In one implementation, spatial bundling of eMBB HARQ-ACK can be performed even when the number of layers that can be scheduled is equal to or less than 4 layers.

[0049] In another implementation, eMBB HARQ-ACK information can be multiplexed into the high-priority PUSCH assuming that the maximum number of code block groups (CBGs) reaches a predetermined number (e.g., 1 or 2). In another implementation, if the maximum number of CBGs is less than a predetermined number (e.g., 1 or 2), eMBB HARQ-ACK information can be multiplexed into the high-priority PUSCH.

[0050] According to a third possible approach, if the UE is instructed to include only aperiodic CSI reports without UL-SCH in the URLLC PUSCH, the UE may consider the URLLC PUSCH overlapping with the low priority PUCCH configured for eMBB SR and / or eMBB HARQ-ACK to be an error case.

[0051] If the UE is instructed to multiplex semi-persistent or aperiodic CSI reports into a high priority PUSCH overlapping with a low priority PUCCH including eMBB HARQ-ACK information without eMBB SR and the UE will transmit a high priority PUSCH without UL-SCH on the serving cell, the UE performs at least one of the following methods.

[0052] According to a first possible approach, the UE can transmit a high-priority PUSCH including semi-persistent or aperiodic CSI reporting and may not transmit a low-priority PUCCH including eMBB HARQ-ACK.

[0053] According to a second possible approach, the UE can multiplex semi-persistent or aperiodic CSI reporting and eMBB HARQ-ACK information into a high priority PUSCH without UL-SCH and may not transmit a low priority PUCCH.

[0054] If the UE is to transmit a high-priority PUSCH with UL-SCH, the UE may not transmit a low-priority PUCCH including SR information (e.g., eMBB SR) and / or eMBB HARQ-ACK.

[0055] In other embodiments, the UE is respectively and capable of receiving information of a plurality of β value sets for UCI multiplexing in PUSCH, and capable of determining which β value set to use based on UCI priority and PUSCH priority, wherein and is a parameter used to determine the number of coded modulation symbols per layer within the PUSCH for HARQ-ACK, CSI-part1, and CSI-part2, respectively, as defined in subclause 6.3.2.4 (Rate Matching) of 3GPP TS 38.212. Additionally, it is possible to define To determine the number of coded modulation symbols per layer in the PUSCH used for SR. or The first set of β values can be used for URLLC UCI multiplexing in low priority PUSCH. or The second set of β values can be used for eMBB UCI multiplexing in high priority PUSCH. or The third set of β values can be used for eMBB UCI multiplexing in low-priority PUSCH. or The fourth beta value set is used for URLLC UCI multiplexing in high priority PUSCH. In one example, the network entity can configure the UE with a larger value for the first beta value set and a smaller value for the second beta value set to ensure that more resource elements are provided for URLLC UCI and URLLC UL-SCH, respectively.

[0056] In one implementation, one or more of the set of beta values may be different for different numbers of URLLC / high priority PUSCH repetitions. In another implementation, one or more of the set of beta values may be different for different numbers of URLLC / high priority PUSCH symbols / REs.

[0057] In other embodiments, if the UE does not have high priority data to transmit on the high priority PUSCH but has low priority data associated with a certain logical channel and the high priority PUSCH meets the mapping restrictions of the logical channel prioritization process configured for the logical channel, the UE can transmit the high priority PUSCH together with the low priority data. In this case, at the UE, the MAC can indicate to the PHY that the TB delivered to the PHY is actually lower priority data, so that the PHY can multiplex the eMBB UCI on the high priority PUSCH carrying the low priority data (assuming that multiplexing the eMBB UCI on the PUSCH carrying URLLC (i.e., high priority) data is not allowed to ensure the reliability of URLLC data delivery). In addition, the UE may need to indicate to the network entity that the high priority PUSCH carries lower priority data. With this indication, the network entity (e.g., gNB) can expect that the eMBB UCI is multiplexed in the high priority PUSCH and can correctly determine the first set of resource elements associated with the TB in the PUSCH and the second set of resource elements associated with the eMBB UCI. In one example, the UE can indicate low or high priority UL-SCH in the high PUSCH by using different scrambling sequences for the UL-SCH. Alternatively or additionally, the gNB can perform decoding twice, assuming that the eMBB UCI is multiplexed.

[0058] In other embodiments, if a high-priority PUSCH with a low-priority UL-SCH on the serving cell overlaps with a high-priority PUCCH including a positive SR, the UE may not transmit the high-priority PUSCH. If the UE is configured to be able to skip UL grants and aperiodic CSI reporting is not triggered, the gNB will blindly detect the transmission of the high-priority PUSCH and the high-priority PUCCH anyway. If a high-priority PUCCH carrying URLLC HARQ-ACK information but not including URLLC SR information overlaps in time with a high-priority PUSCH with a low-priority UL-SCH and one or more timing conditions for multiplexing are met (if applicable), the UE can multiplex the URLLC HARQ-ACK information in the high-priority PUSCH with the low-priority UL-SCH and may not transmit the high-priority PUCCH.

[0059] In other embodiments, if the UE is indicated with a first PUCCH and a second PUCCH for eMBB HARQ-ACK, where the first PUCCH starts earlier than the second PUCCH, and the first PUCCH overlaps with a high priority PUCCH including URLLC SR and / or URLLC HARQ-ACK, the UE is able to transmit eMBB HARQ-ACK on the second PUCCH that does not overlap with the high priority PUCCH.

[0060] In other embodiments, if a newly received UL grant without a high priority indication (or with a low priority indication) overlaps with a high priority physical channel and does not meet the timeline requirements for the overlapping channel (as described in subclause 9.2.5 of TS 38.213), the PHY may not deliver the UL grant to the MAC layer of the UE.

[0061] In one embodiment, if a first SR configuration (e.g., RRC parameter SchedulingRequestConfig) associated with a first SR resource configuration corresponds to a logical channel with a high priority, e.g., a logical channel with a priority value of '1', where increasing priority values among the priority values of {1, 2, 3, ..., 16} indicate a lower priority level, then the UE's PHY can consider that the first PUCCH resource configured in the first SR resource configuration (e.g., in the RRC parameter SchedulingRequestResourceConfig) is set to a high priority. If a second SR configuration associated with a second SR resource configuration corresponds only to one or more logical channels with a low priority (e.g., with a priority value of 2, 3, .. or 16), then the UE's PHY can consider that the second PUCCH resource configured in the second SR resource configuration is set to a low priority.

[0062] In another embodiment, the priority level of the PUCCH resources configured in the SR resource configuration can be based on (e.g., the same as) the highest priority logical channel corresponding to (or mapped to) the SR resource configuration. For example, if logical channels with priority values 1, 2, and 3 respectively correspond to a first SR configuration with a first PUCCH resource, the priority of the first PUCCH resource can be '1', which corresponds to the highest priority level '1' (out of levels '1', '2', and '3') of the logical channels corresponding to the first SR configuration. Logical channels with priority values 5, 6, and 7 respectively correspond to a second SR configuration with a second PUCCH resource, and the priority level of the second PUCCH resource can be '5', which corresponds to the highest priority level '5' (out of levels '5', '6', and '7') of the logical channels corresponding to the second SR configuration. The second PUCCH resource with priority level '5' has a lower priority than the first PUCCH resource with priority level '1'.

[0063] Table 2 shows exemplary conflict handling rules for UCI and UL data.

[0064]

[0065]

[0066]

[0067] Table 2: Example conflict handling rules for UCI and UL data

[0068] At least some embodiments can provide for handling multiple unicast data channels associated with different traffic types. If a UE must handle more than one unicast PDSCH at a given time (for overlapping or non-overlapping unicast PDSCHs), it may be useful to ensure that the UE processing pipeline (i.e., one processing block is used to process one physical channel at a time) while ensuring that all physical channels can meet their processing timelines.

[0069] In one implementation, the minimum processing time of the PDSCH at the UE can be determined based on the use case / service type. For example, a longer minimum PDSCH processing time (e.g., the PDSCH processing time shown in Table 5.3-1 of TS38.214) can be applied to PDSCH carrying eMBB services and / or PDSCH with a symbol number greater than a certain threshold (e.g., the symbol number is greater than 4), whereas a shorter minimum PDSCH processing time (e.g., the PDSCH processing time shown in Table 5.3-2 of TS38.214) can be allocated to PDSCH carrying URLLC services and / or PDSCH with a symbol number less than a threshold. If a service-specific (or service-specific) minimum PDSCH processing time is allowed for a UE in a given serving cell, the PDSCH to HARQ-ACK feedback can be unordered or ordered, depending on the corresponding service types of the first PDSCH and the second PDSCH. Out-of-order PDSCH to HARQ-ACK feedback is the ability to send a HARQ-ACK associated with a second PDSCH with HARQ process ID 'x' received after the first PDSCH with HARQ process ID 'y' before the HARQ-ACK of the first PDSCH. In-order PDSCH to HARQ-ACK feedback is the ability to send a HARQ-ACK associated with a second PDSCH with HARQ process ID 'x' received after the first PDSCH with HARQ process ID 'y' after the HARQ-ACK of the first PDSCH. In another implementation, a minimum processing time can be configured for a UE in a given serving cell for all service types.

[0070] In order to guarantee the UE processing pipeline for the UE processing time implementation mentioned above, the UE may have to buffer the received symbols (and / or demodulated data, i.e., log-likelihood ratio (LLR)) of the PDSCH and / or the corresponding HARQ-ACK feedback information and also postpone decoding the received PDSCH and / or transmitting the HARQ-ACK feedback. If the UE postpones decoding the received PDSCH and / or delays transmitting the corresponding HARQ-ACK feedback compared to the originally indicated HARQ-ACK transmission time in order to process the later received PDSCH with higher priority, new PUCCH resources may need to be provided to the UE for the delayed HARQ-ACK feedback transmission.

[0071] Figure 2200 is an example illustration of an example scenario requiring a UE to handle two unicast PDSCHs according to a possible embodiment. The UE is capable of receiving first information of a dynamic or semi-persistent DL assignment for a first PDSCH of a serving cell and is capable of identifying first and second PUCCH resources and / or first and second PUCCH resources associated with the first and second PUCCH resources, respectively, for HARQ-ACK feedback of the first PDSCH. In addition, the UE is capable of receiving second information of a dynamic or semi-persistent DL assignment for a second PDSCH of the serving cell, wherein a start symbol of the second PDSCH is later than a start symbol of the first PDSCH, and is capable of determining whether to delay HARQ-ACK feedback of the first PDSCH for processing the second PDSCH. In response to determining to delay HARQ-ACK feedback of the first PDSCH, the UE may transmit HARQ-ACK feedback of the first PDSCH on the second PUCCH resource. In response to determining not to delay HARQ-ACK feedback for the first PDSCH, the UE can transmit HARQ-ACK feedback for the first PDSCH on the first PUCCH resource.In one implementation, the second PDSCH can be explicitly indicated as a high priority PDSCH.

[0072] The first PUCCH resource can start earlier than the second PUCCH resource, and the first PDSCH to HARQ timing indicator value k1 can be no greater than the second PDSCH to HARQ timing indicator value k2. In one example, for a PDSCH reception ending in slot n, the UE can start in slot n+k. i ——where k i (i=1, 2) The first PUCCH or the second PUCCH is transmitted in units of time slots and can be provided by DCI and / or can be configured by higher layers. In another example, for sub-slot-based HARQ-ACK feedback, the UE can receive a PDSCH in sub-slot n+k in response to the PDSCH reception that ends in sub-slot n. i The first PUCCH or the second PUCCH for HARQ-ACK feedback is transmitted in i (i=1, 2) The unit is sub-slot.

[0073] In one implementation, the first PUCCH resource and the second PUCCH resource (e.g., as PUCCH resource indices) and the associated first PDSCH to HARQ timing indicator value and the PDSCH to HARQ timing indicator value can be explicitly indicated via RRC signaling and / or DCI signaling. For example, each element of a PUCCH resource set can consist of or include one or more PUCCH resource indices, and thus, the code point of a PUCCH resource indicator (PRI) field in the DCI can indicate one or more PUCCH resources. In addition, each element of a higher layer parameter "dl-DataToUL-ACK" for a set of number of time slots (or a set of number of sub-time slots) can consist of or include one or more values of the number of time slots (or number of sub-time slots), and the code point of a PDSCH to HARQ timing-indicator field in the DCI can indicate one or more values of the number of time slots (or number of sub-time slots).

[0074] In another implementation, the first PUCCH resource and the associated first PDSCH-to-HARQ timing indicator value can be explicitly indicated via RRC signaling and / or DCI signaling for scheduling the first PDSCH. The RRC signaling or DCI for scheduling the second PDSCH can include the second PUCCH resource and the associated second PDSCH-to-HARQ timing indicator value for HARQ-ACK feedback of the first PDSCH.

[0075] In another implementation, the UE can receive an explicit indication of a first PUCCH resource and / or an associated first PDSCH to HARQ timing indicator value via RRC and / or DCI signaling, and can derive a second PUCCH resource and / or a second PDSCH to HARQ timing indicator value based on the first PUCCH resource and / or the first PDSCH to HARQ timing indicator value. In one example, an offset value of the second PDSCH to HARQ timing indicator value relative to the first PDSCH to HARQ timing indicator value can be configured by a higher layer, dynamically signaled, or predetermined, and the PUCCH resource index of the second PUCCH resource can be the same as the PUCCH resource index of the first PUCCH resource. In another example, the UE can determine the PDSCH to HARQ timing indicator value by applying the offset value by the number of time slots (or sub-time slots) relative to the time slot (or sub-time slot) at which the second PDSCH ends (or the second PDSCH starts). The offset value can be configured by a higher layer, dynamically signaled, or predetermined, and the PUCCH resource index of the second PUCCH resource can be the same as the PUCCH resource index of the first PUCCH resource.The offset value may depend on the minimum processing time of the second PDSCH.

[0076] If it is necessary to postpone decoding of the first PDSCH (which may be a PDSCH with a low priority, such as a PDSCH carrying eMBB services) according to a predefined or configured condition, the UE can transmit the corresponding HARQ-ACK on the second PUCCH resource with the second PDSCH to HARQ timing value. Otherwise, the UE can transmit the corresponding HARQ-ACK on the first PUCCH resource with the first PDSCH to HARQ timing value.

[0077] The UE is capable of processing both the first PDSCH and the second PDSCH under some conditions such as scheduling conditions and / or reported UE capability information. The scheduling conditions can include at least one of the number of RBs, the transport block size (TBS), the number of layers, the time gap between the first PDSCH and the second PDSCH, and the time gap between two PUCCHs carrying HARQ-ACK for the first PDSCH and the second PDSCH. Exemplary UE capability information can include the number of high priority PDSCHs and the number of low priority PDSCHs that the UE can handle on a given frequency band of the frequency band combination. If the received scheduling information for the first PDSCH and the second PDSCH does not meet those conditions, the UE can postpone or skip decoding the first PDSCH.

[0078] An exemplary condition for postponing the decoding of the first PDSCH may be that the time difference between the end of the low-priority first PDSCH and the start of the high-priority second PDSCH is less than the minimum processing time of the low-priority first PDSCH (i.e., the PDSCH that started earlier). In other words, the UE is capable of processing both the low-priority PDSCH and the high-priority PDSCH and if the time gap between the first symbol of the high-priority PDSCH and the last symbol of the low-priority PDSCH includes at least N1 symbols, the HARQ-ACK feedback of the low-priority PDSCH is reported on the first PUCCH resource (i.e., the PUCCH resource that started earlier). N1 may be the minimum processing time or a configured or predefined value for the low-priority PDSCH. Otherwise, the UE is able to postpone or skip decoding the low-priority PDSCH. If the UE is provided with a first PUCCH resource and a second PUCCH resource for HARQ-ACK feedback of a low-priority PDSCH (i.e., the first PDSCH), the UE can postpone decoding the low-priority PDSCH and can transmit HARQ-ACK feedback of the low-priority PDSCH on the second PUCCH resource (i.e., the PUCCH resource that starts later). If the UE is provided with only one PUCCH resource (i.e., the first PUCCH resource) for HARQ-ACK feedback of a low-priority PDSCH, the UE can skip decoding the low-priority PDSCH and can transmit HARQ-ACK feedback of the low-priority PDSCH on the first PUCCH resource. If decoding of the low-priority PDSCH is skipped, the UE can generate NACK as HARQ-ACK feedback.

[0079] In one implementation, the first PUCCH resource and the second PUCCH resource are in the same serving cell (e.g., PCell, PSCell, or PUCCH-SCell). The PCell may be the primary cell of a primary cell group (MCG). When the UE is configured with dual connectivity, the PSCell may be the primary cell of a secondary cell group (SCG). The PUCCH-SCell may be a secondary cell having an uplink carrier configured to carry the PUCCH. In another implementation, if the UE is configured with a PUCCH-SCell, the first PUCCH resource and the second PUCCH resource may be in the same serving cell or in different serving cells.

[0080] In another embodiment, if the UE determines to delay or skip decoding the first PDSCH and transmit HARQ-ACK feedback of the first PDSCH on the first PUCCH resource for processing the second PDSCH according to one or more configurations or predefined rules and will transmit HARQ-ACK feedback of the first PDSCH on the second PUCCH resource, the UE is able to maintain the original size of the HARQ-ACK codebook for HARQ-ACK transmission on the first PUCCH taking into account the HARQ-ACK bit field associated with the first PDSCH. That is, the HARQ-ACK codebook size of the first PUCCH in response to determining to delay or skip HARQ-ACK feedback of the first PDSCH can be the same as the HARQ-ACK codebook size of the HARQ-ACK feedback in response to determining not to delay or skip the first PDSCH. The first PDSCH may be a lower priority PDSCH than the second PDSCH, and the first PDSCH can start earlier than the second PDSCH.

[0081] In the HARQ-ACK codebook of the first PUCCH, the UE can set the HARQ-ACK bit field associated with the first PDSCH to a known value, such as NACK or ACK. In the HARQ-ACK codebook of the second PUCCH, the UE can append the HARQ-ACK information bits of the first PDSCH to the end of the HARQ-ACK codebook of the second PUCCH.

[0082] In one embodiment, the UE's physical layer can instruct the MAC entity whether to attempt to decode received data (e.g., LLRs of channel bits). If the UE decides to skip decoding the first PDSCH due to processing the second PDSCH, the PHY can instruct the MAC not to attempt to decode the received data if the first PDSCH has a lower priority than the second PDSCH. In addition, the UE can decide whether to replace the data in the soft buffer for this TB with the received data depending on the timing conditions (whether the UE can perform demodulation).

[0083] If the UE decides to skip decoding the first PDSCH, then in one implementation, the UE can invalidate the detected DCI format for the first PDSCH. In another implementation, if the UE has generated useful / meaningful LLRs for some or all channel bits (even if the UE does not proceed with decoding), it may be better to use them rather than discard them completely. Therefore, whether to update the soft buffer for the first PDSCH whose decoding is skipped can be left to the UE implementation.

[0084] According to a possible embodiment, the HARQ process can be modified as follows, where the double dashes "--" indicate additions:

[0085] 5.3.2.2 HARQ Process

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

[0087] For each received TB and associated HARQ information, the HARQ process shall:

[0088] 1> if, when NDI is provided, it has switched compared to the value corresponding to the previously received transmission for this TB; or

[0089] 1> If the HARQ process is equal to the broadcast process and this is the first received transmission for the TB according to the system information scheduling indicated by RRC; or

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

[0091] 2> Consider this transfer as a new transfer.

[0092] 1> Otherwise:

[0093] 2> Consider this transmission as a retransmission.

[0094] The MAC entity shall then:

[0095] 1> If this is a new transfer:

[0096] --2>If the physical layer instructs the MAC entity to attempt to decode the received data:

[0097] 3>Try to decode the received data. --

[0098] 1> Else if this is a retransmission:

[0099] 2> If the data for this TB has not yet been successfully decoded:

[0100] 3> Instructs the physical layer to combine the received data with the data currently in the soft buffer for this TB

[0101] --3>If the physical layer instructs the MAC entity to attempt to decode the received data:

[0102] 4>Try to decode the combined data. --

[0103] 1> if the data that the MAC entity attempted to decode was successfully decoded for this TB; or

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

[0105] 2> If the HARQ process is equal to the broadcast process:

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

[0107] 2> Else if this is the first successful decoding of data for this TB:

[0108] 3> Deliver the decoded MAC PDU to the decomposition and demultiplexing entity.

[0109] --1> Otherwise if the physical layer instructs the MAC entity to attempt to decode the received data:

[0110] 2> Instructs the physical layer to replace the data in the soft buffer for this TB with the data that the MAC entity is trying to decode. --

[0111] 1> if the HARQ process is associated with the transmission indicated by the Temporary C-RNTI and contention resolution remains unsuccessful (see subclause 5.1.5); or

[0112] 1> If the HARQ process is equal to the broadcast process; or

[0113] 1> If the timeAlignmentTimer associated with the TAG containing the serving cell on which HARQ feedback is to be transmitted is stopped or expires:

[0114] 2>Does not instruct the physical layer to generate a positive acknowledgement of the data in this TB.

[0115] 1> Otherwise:

[0116] 2> Instructs the physical layer to generate a positive response to the data in this TB.

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

[0118] NOTE: If the MAC entity receives a retransmission with a TB size different from the last TB size signaled for this TB, the UE behavior is left to the UE implementation.

[0119] --Note: If the physical layer instructs the MAC entity not to attempt to decode the received data, it is up to the UE to instruct the physical layer to replace the data in the soft buffer for this TB with the received data. --

[0120] Figure 3 300 is an example flow chart illustrating the operation of a wireless communication device, such as UE 110, according to a possible embodiment. At 310, a PUCCH configuration including information about at least one PUCCH resource can be received. At 320, an UL grant for at least one high-priority PUSCH can be received. The UL grant can instruct the UE to include a CSI report in the at least one high-priority PUSCH. A specific PUSCH of the at least one high-priority PUSCH can overlap with a PUCCH resource of the at least one PUCCH resource. At 330, a determination can be made as to whether UCI is available for transmission on the PUCCH resource. At 340, when UCI is available for transmission on the PUCCH resource, the specific PUSCH can be transmitted according to the UL grant by including the CSI report in the specific PUSCH.

[0121] According to a possible embodiment, UCI transmission on PUCCH resources can be cancelled.

[0122] According to a possible embodiment, a determination can be made as to whether a UL-SCH is present for a PUSCH. The UCI can include at least an SR. The PUCCH resource can be a low-priority PUCCH resource. Transmitting the PUSCH can include transmitting the PUSCH without including UCI when no UL-SCH is present for the PUSCH. For example, if the UE has only an SR or an SR and HARQ-ACK information to transmit on a PUCCH resource and the PUCCH resource is a low-priority PUCCH resource, the UE can transmit a high-priority PUSCH based on the UL grant, regardless of whether a UL-SCH is present. The UL-SCH can be, such as can include, user data.

[0123] According to a possible embodiment, a determination can be made as to whether the UCI includes SR and / or HARQ-ACK information. When the UCI includes SR and / or HARQ-ACK information, the UCI can be multiplexed into the transmitted PUSCH. The PUCCH resource may be a low-priority PUCCH resource. For example, the UE can multiplex semi-persistent or aperiodic CSI reports and low-priority SR information (and eMBB HARQ-ACK information, if included in the low-priority PUCCH) into a high-priority PUSCH without UL-SCH and may not transmit the low-priority PUCCH.

[0124] According to a possible implementation, the CSI report may be a first CSI report. The UCI may include a second CSI report. Multiplexing the UCI may include multiplexing the UCI excluding the second CSI report into the transmitted PUSCH.

[0125] According to a possible implementation, a determination can be made as to whether a UL-SCH is present for the PUSCH.Multiplexing can include multiplexing SR and / or HARQ-ACK information into the transmitted PUSCH when no UL-SCH is present for the PUSCH.

[0126] According to a possible embodiment, the CSI report may be an aperiodic CSI report in at least one high priority PUSCH.

[0127] According to a possible embodiment, the CSI report may be a semi-persistent CSI report. The at least one high priority PUSCH may include a semi-persistent PUSCH resource. Transmitting may include transmitting the CSI report on a semi-persistent PUSCH resource among the semi-persistent PUSCH resources.

[0128] According to a possible embodiment, the PUCCH resource can correspond to a high priority PUCCH. Transmitting the PUSCH can include transmitting the PUSCH when the PUCCH resource corresponds to the high priority PUCCH.

[0129] According to a possible implementation, the transmitted PUSCH may include a UL-SCH. Transmitting the PUSCH may include transmitting the PUSCH when the PUSCH includes a UL-SCH and the PUCCH resource corresponds to a high-priority PUCCH. According to a possible implementation, the CSI report may be a first CSI report. The UCI may be an SR, HARQ-ACK information, and / or a second CSI report. Transmitting the PUSCH may include multiplexing the HARQ-ACK information into the PUSCH if the UCI includes HARQ-ACK information, excluding the SR from the PUSCH when the UCI includes the SR, and excluding the second CSI report from the PUSCH when the UCI includes the second CSI report.

[0130] For example, if a high priority PUCCH carrying URLLC HARQ-ACK information, URLLC SR and / or URLLC CSI report overlaps in time with a high priority PUSCH with UL-SCH and meets one or more timing conditions for multiplexing, the UE can multiplex the URLLC HARQ-ACK information and / or URLLC CSI report in the high priority PUSCH with UL-SCH and may not transmit the high priority PUCCH including the URLLC SR. An example of a URLLC CSI report may be an indication of a CQI offset / adjustment to be transmitted on the high priority PUCCH together with the URLLC HARQ-ACK. In addition, if the UE is instructed to send a semi-persistent or aperiodic CSI report in a high priority PUSCH with UL-SCH, the UE can multiplex only the URLLC HARQ-ACK information in the high priority PUSCH and may not multiplex the URLLC CSI report to be transmitted on the high priority PUCCH. This may be because the semi-persistent or aperiodic CSI report triggered by the network entity and to be transmitted on the high-priority PUSCH may include more important CSI than the URLLC CSI report to be transmitted on the high-priority PUCCH. If the high-priority PUCCH resource overlaps in time with multiple high-priority PUSCHs that meet the timing conditions for UCI multiplexing, the high-priority PUSCH carrying aperiodic CSI can be selected for UCI multiplexing. If there is no high-priority PUSCH carrying aperiodic CSI, the high-priority PUSCH scheduled by the dynamic UL grant, in the serving cell with the smallest ServCellIndex, and starting earlier in the given serving cell is selected for UCI multiplexing.

[0131] According to a possible embodiment, UCI can include at least HARQ-ACK information. A specific PUSCH can be transmitted by including HARQ-ACK information for a low-priority UL-SCH and UCI on a specific PUSCH. According to a possible implementation, an indication can be sent indicating that a low-priority UL-SCH is to be transmitted on a specific PUSCH. According to a possible implementation, the indication can include applying a scrambling sequence to the specific PUSCH, where the scrambling sequence corresponds to the low-priority UL-SCH. For example, different scrambling sequences can be used to indicate different priorities of the UL-SCH.

[0132] According to a possible embodiment, a PUCCH configuration can include an SR resource configuration. The SR resource configuration can include PUCCH resources and can be associated with the SR configuration. The SR configuration can correspond to at least one logical channel. The method can include determining a priority of the PUCCH resources based on at least one priority of the at least one logical channel.

[0133] For example, each logical channel can have a priority, an SR configuration can correspond to multiple logical channel priorities, and the priority of the PUCCH can be determined based on the multiple logical channel priorities. If a first SR configuration (e.g., RRC parameter SchedulingRequestConfig) associated with a first SR resource configuration corresponds to a logical channel with a high priority, such as a logical channel with a priority value of '1', where increasing priority values among the priority values of {1, 2, 3, ..., 16} can indicate a lower priority level, the UE's PHY can consider the first PUCCH resource configured in the first SR resource configuration (e.g., in the RRC parameter SchedulingRequestResourceConfig) to be set to a high priority. If a second SR configuration associated with a second SR resource configuration corresponds only to one or more logical channels with a low priority (e.g., having a priority value of 2, 3, .. or 16), the UE's PHY can consider the second PUCCH resource configured in the second SR resource configuration to be set to a low priority.

[0134] Figure 4 4 is an example flow chart 400 illustrating the operation of a wireless communication device, such as UE 110, according to a possible embodiment. At 410, first information of a DL assignment for a first PDSCH of a serving cell can be received. At 420, a first PUCCH resource and a second PUCCH resource can be identified for HARQ-ACK feedback of the first PDSCH. A starting symbol of the second PUCCH resource can be later than a starting symbol of the first PUCCH resource. At 430, second information of a DL assignment for a second PDSCH of the serving cell can be received. A starting symbol of the second PDSCH can be later than a starting symbol of the first PDSCH. At 440, a determination can be made as to whether to delay HARQ-ACK feedback for the first PDSCH for processing the second PDSCH. At 450, HARQ-ACK information for the first PDSCH can be transmitted on the second PUCCH resource in response to determining to delay HARQ-ACK feedback for the first PDSCH.

[0135] According to a possible embodiment, the first PDSCH can be associated with a lower priority than the second PDSCH.

[0136] According to a possible embodiment, the first PUCCH resource can be determined based on the first PUCCH resource index and the first PDSCH to HARQ timing indicator value.The second PUCCH resource can be determined based on the second PUCCH resource index and the second PDSCH to HARQ timing indicator value.

[0137] According to a possible embodiment, HARQ-ACK information of the second PDSCH can be transmitted on a third PUCCH resource. The starting symbol of the third PUCCH resource can be earlier than the starting symbol of the first PUCCH resource. For example, as shown in diagram 200, PUCCH3 can start earlier than PUCCH1.

[0138] According to a possible embodiment, HARQ-ACK information of the first PDSCH can be transmitted on the first PUCCH resource in response to determining not to delay HARQ-ACK feedback of the first PDSCH.

[0139] According to a possible embodiment, in response to determining to delay the HARQ-ACK feedback of the first PDSCH, a first HARQ-ACK codebook can be transmitted on a first PUCCH resource and a second HARQ-ACK codebook can be transmitted on a second PUCCH resource. The HARQ-ACK information of the first PDSCH can be included in the second HARQ-ACK codebook. According to a possible implementation, the HARQ-ACK information of the first PDSCH can be appended to other HARQ-ACK information of the second HARQ-ACK codebook. According to a possible implementation, the first HARQ-ACK codebook can include a bit field for HARQ-ACK feedback of the first PDSCH. According to a possible implementation, the bit field for HARQ-ACK feedback of the first PDSCH can include one or more known values. According to a possible implementation, the width of the bit field for HARQ-ACK feedback of the first PDSCH can be the same size as the size of the HARQ-ACK information of the first PDSCH.

[0140] According to a possible embodiment, the first PUCCH resource and the second PUCCH resource can be in the same cell.According to a possible embodiment, the first PUCCH resource and the second PUCCH resource can be in different cells.

[0141] According to a possible embodiment, the DL assignment of the first PDSCH may be a dynamic or semi-persistent assignment.

[0142] According to a possible embodiment, the first PUCCH resource may overlap with a PUCCH including URLLC SR information and / or URLLC HARQ-ACK information. The second PUCCH resource may not overlap with the PUCCH. The HARQ-ACK information of the first PDSCH may be transmitted on the second PUCCH resource.

[0143] It should be understood that regardless of the specific steps shown in the various figures, various additional or different steps can be performed depending on the embodiment, and one or more of the specific steps can be rearranged, repeated, or completely eliminated depending on the embodiment. In addition, some of the steps performed can be repeated simultaneously on an ongoing or continuous basis while other steps are performed. In addition, different steps can be performed by different elements or different steps can be performed in a single element of the disclosed embodiments. In addition, network entities such as base stations, transmission and reception points, or other network entities can perform interchange operations for UEs. For example, a network entity can transmit signals received by a UE and can receive signals transmitted by a UE. The network entity can also process and operate on the transmitted and received signals.

[0144] Figure 5 1 is an example block diagram of an apparatus 500, such as a UE 110, a network entity 120, or any other wireless communication device disclosed herein, according to possible embodiments. Apparatus 500 can include a housing 510, a controller 520 coupled to housing 510, audio input and output circuitry 530 coupled to controller 520, a display 540 coupled to controller 520, a memory 550 coupled to controller 520, a user interface 560 coupled to controller 520, a transceiver 570 coupled to controller 520, at least one antenna 575 coupled to transceiver 570, and a network interface 580 coupled to controller 520. Apparatus 500 may not necessarily include all illustrated elements for different embodiments of the present disclosure. Apparatus 500 can perform the methods described in all embodiments.

[0145] The display 540 can be a viewfinder, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a plasma display, a projection display, a touch screen, or any other device displaying information. The transceiver 570 can be one or more transceivers that can include a transmitter and / or a receiver. The audio input and output circuit system 530 can include a microphone, a loudspeaker, a transducer, or any other audio input and output circuit system. The user interface 560 can include a keypad, a keyboard, a button, a touch pad, a joystick, a touch screen display, another additional display, or any other device that can be used to provide an interface between a user and an electronic device. The network interface 580 can be a universal serial bus (USB) port, an Ethernet port, an infrared transmitter / receiver, an IEEE 1394 port, a wireless transceiver, a WLAN transceiver, or any other interface that can connect the device to a network, equipment, and / or a computer and can transmit and receive data communication signals. Memory 550 can include random access memory (RAM), read only memory (ROM), optical memory, solid-state memory, flash memory, removable memory, a hard drive, cache, or any other memory capable of being coupled to the device.

[0146] The device 500 or the controller 520 may implement any operating system, such as Microsoft Android TM , or any other operating system. For example, the device operating software can be written in any programming language such as C, C++, Java or Visual Basic. The device software can also be written in a language such as frame, The disclosed embodiments may be implemented on a general-purpose or special-purpose computer, a programmed microprocessor or microprocessor, a peripheral integrated circuit component, an application-specific integrated circuit or other integrated circuit, hardware / electronic logic circuitry such as discrete component circuitry, or a programmable logic device such as a programmable logic array or field programmable gate array. In general, the controller 520 may be any controller or processor device capable of operating the apparatus and implementing the disclosed embodiments. Some or all of the additional components of the apparatus 500 may also be capable of performing some or all of the operations of the disclosed embodiments.

[0147] In operation, the apparatus 500 is capable of performing the methods and operations of the disclosed embodiments. The transceiver 570 is capable of transmitting and receiving signals, including data signals and control signals that can include corresponding data and control information. The controller 520 is capable of generating and processing the transmitted and received signals and information.

[0148] According to a possible embodiment, the transceiver 570 can receive a PUCCH configuration including information about at least one PUCCH resource. The transceiver 570 can receive an UL grant for at least one high-priority PUSCH. The UL grant can instruct the UE to include a CSI report in the at least one high-priority PUSCH. A specific PUSCH of the at least one high-priority PUSCH can overlap with a PUCCH resource of the at least one PUCCH resource. The controller 520 can determine whether there is UCI to be transmitted on the PUCCH resource. When there is UCI to be transmitted on the PUCCH resource, the transceiver 570 can transmit the specific PUSCH in accordance with the UL grant by including the CSI report in the specific PUSCH.

[0149] According to a possible embodiment, the controller 520 can cancel UCI transmission on PUCCH resources.

[0150] According to a possible embodiment, the controller 520 can determine whether a UL-SCH exists for the PUSCH. The UCI can include at least the SR. The PUCCH resource can be a low-priority PUCCH resource. When there is no UL-SCH for the PUSCH, the transceiver 570 can transmit the PUSCH without including the UCI.

[0151] According to a possible embodiment, the controller 520 can determine whether the UCI includes SR and / or HARQ-ACK information. When the UCI includes SR and / or HARQ-ACK information, the controller 520 can multiplex the UCI into the transmitted PUSCH. The PUCCH resource can be a low-priority PUCCH resource.

[0152] According to a possible embodiment, the CSI report may be an aperiodic CSI report in at least one high priority PUSCH.

[0153] According to a possible embodiment, the CSI report may be a semi-persistent CSI report. The at least one high-priority PUSCH may include a semi-persistent PUSCH resource. The transceiver 570 may transmit the CSI report on a semi-persistent PUSCH resource among the semi-persistent PUSCH resources.

[0154] According to a possible embodiment, the PUCCH resource can correspond to a high priority PUCCH.When the PUCCH resource corresponds to a high priority PUCCH, the transceiver 570 can transmit a PUSCH.

[0155] According to a possible implementation, the transmitted PUSCH can include UL-SCH. When the PUSCH includes UL-SCH and the PUCCH resource corresponds to a high-priority PUCCH, the transceiver 570 can transmit the PUSCH. According to a possible implementation, the CSI report can be a first CSI report. The UCI can be an SR, HARQ-ACK information and / or a second CSI report. The controller 520 can multiplex the HARQ-ACK information into the PUSCH when the UCI includes HARQ-ACK information, exclude the SR from the PUSCH when the UCI includes the SR, and exclude the second CSI report from the PUSCH when the UCI includes the second CSI report.

[0156] According to a possible embodiment, UCI can include at least HARQ-ACK information. A specific PUSCH can be transmitted by including HARQ-ACK information for a low-priority UL-SCH and UCI on a specific PUSCH. According to a possible implementation, an indication can be sent indicating that a low-priority UL-SCH is to be transmitted on a specific PUSCH. According to a possible implementation, the indication can include applying a scrambling sequence to the specific PUSCH, where the scrambling sequence corresponds to the low-priority UL-SCH. For example, different scrambling sequences can be used to indicate different priorities of the UL-SCH.

[0157] According to a possible embodiment, the PUCCH configuration can include an SR resource configuration. The SR resource configuration can include PUCCH resources and can be associated with the SR configuration. The SR configuration can correspond to at least one logical channel. The controller 520 can determine the priority of the PUCCH resources based on at least one priority of the at least one logical channel.

[0158] According to a possible embodiment, the transceiver 570 is capable of receiving first information of DL assignment for a first PDSCH of a serving cell. The controller 520 is capable of identifying a first PUCCH resource and a second PUCCH resource for HARQ-ACK feedback of the first PDSCH. The starting symbol of the second PUCCH resource can be later than the starting symbol of the first PUCCH resource. The transceiver 570 is capable of receiving second information of DL assignment for a second PDSCH of a serving cell. The starting symbol of the second PDSCH can be later than the starting symbol of the first PDSCH. The controller 520 is capable of determining whether to delay the HARQ-ACK feedback of the first PDSCH for processing the second PDSCH. The transceiver 570 is capable of transmitting HARQ-ACK information of the first PDSCH on the second PUCCH resource in response to determining to delay the HARQ-ACK feedback of the first PDSCH.

[0159] According to a possible embodiment, the first PDSCH can be associated with a lower priority than the second PDSCH.

[0160] According to a possible embodiment, the first PUCCH resource can be determined based on the first PUCCH resource index and the first PDSCH to HARQ timing indicator value.The second PUCCH resource can be determined based on the second PUCCH resource index and the second PDSCH to HARQ timing indicator value.

[0161] According to a possible embodiment, the transceiver 570 can transmit the HARQ-ACK information of the second PDSCH on the third PUCCH resource.The starting symbol of the third PUCCH resource can be earlier than the starting symbol of the first PUCCH resource.

[0162] According to a possible embodiment, the transceiver 570 can transmit HARQ-ACK information of the first PDSCH on the first PUCCH resource in response to the controller determining not to delay HARQ-ACK feedback of the first PDSCH.

[0163] According to a possible embodiment, the transceiver 570 can transmit a first HARQ-ACK codebook on a first PUCCH resource and a second HARQ-ACK codebook on a second PUCCH resource in response to the controller determining to delay HARQ-ACK feedback for the first PDSCH. The HARQ-ACK information for the first PDSCH can be included in the second HARQ-ACK codebook.

[0164] According to a possible embodiment, the method at the UE may include receiving first information of a DL assignment for a first PDSCH of a serving cell. The method may include identifying a first PUCCH resource and a second PUCCH resource for HARQ-ACK feedback of the first PDSCH. The method may include receiving second information of a DL assignment for a second PDSCH of a serving cell. The method may include determining whether to delay the HARQ-ACK feedback of the first PDSCH for processing of the second PDSCH. The method may include transmitting HARQ-ACK information of the first PDSCH on a second PUCCH resource in response to determining to delay the HARQ-ACK feedback of the first PDSCH. The starting symbol of the second PDSCH may be later than the starting symbol of the first PDSCH, and the starting symbol of the second PUCCH resource may be later than the starting symbol of the first PUCCH resource.

[0165] The first PDSCH can be associated with a lower priority than the second PDSCH.

[0166] A first PUCCH resource can be determined based on a first PUCCH resource index and a first PDSCH-to-HARQ-timing indicator value, and a second PUCCH resource can be determined based on a second PUCCH resource index and a second PDSCH-to-HARQ timing indicator value.

[0167] According to a possible implementation, the method can include transmitting HARQ-ACK information of the second PDSCH on a third PUCCH resource, wherein a starting symbol of the third PUCCH resource is earlier than a starting symbol of the first PUCCH resource.

[0168] According to a possible implementation, the method can include transmitting HARQ-ACK information of the first PDSCH on the first PUCCH resource in response to determining not to delay HARQ-ACK feedback of the first PDSCH.

[0169] The first PUCCH resource and the second PUCCH resource can be in the same cell. The first PUCCH resource and the second PUCCH resource can be in different cells. The DL assignment of the first PDSCH can be a dynamic or semi-persistent assignment.

[0170] The first PUCCH resource may overlap with a PUCCH including URLLC SR information and / or URLLC HARQ-ACK information, while the second PUCCH resource may not overlap with the PUCCH, and the method may include transmitting HARQ-ACK information of the first PDSCH on the second PUCCH resource.

[0171] According to a possible implementation, the method may include transmitting a first HARQ-ACK codebook on a first PUCCH resource and transmitting a second HARQ-ACK codebook on a second PUCCH resource in response to determining to delay the HARQ-ACK feedback of the first PDSCH, wherein the HARQ-ACK information of the first PDSCH is included in the second HARQ-ACK codebook. The HARQ-ACK information of the first PDSCH can be appended to other HARQ-ACK information of the second HARQ-ACK codebook. The first HARQ-ACK codebook can include a bit field for HARQ-ACK feedback of the first PDSCH. The bit field for HARQ-ACK feedback of the first PDSCH can include one or more known values. The width of the bit field for HARQ-ACK feedback of the first PDSCH can be the same as the size of the HARQ-ACK information of the first PDSCH.

[0172] At least some of the methods of the present disclosure can be implemented on a programmed processor. However, the controller, flow charts, and modules can also be implemented on a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, hardware electronic or logic circuits (such as discrete component circuits), a programmable logic device, etc. In general, any device on which resides a finite state machine capable of implementing the flow charts shown in the various figures can perform the processor functions of the present disclosure.

[0173] At least some embodiments can improve the operation of the disclosed device. In addition, although the present disclosure has been described using specific embodiments of the present disclosure, it is apparent that many alternatives, modifications and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added or substituted in other embodiments. In addition, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, it will enable those of ordinary skill in the art of the disclosed embodiments to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Therefore, the embodiments of the present disclosure as set forth herein are intended to be illustrative, not restrictive. Various changes can be made without departing from the spirit and scope of the present disclosure.

[0174] In this document, relational terms such as "first", "second", etc. may be used solely to distinguish one entity or action from another, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The phrases "at least one of...", "at least one selected from a group of...", or "at least one selected from..." followed by a list are defined to mean one, some, or all, but not necessarily all, of the elements in the list. The terms "include," "comprises," "includes," or any other variant thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or device that includes a list of elements includes not only those elements, but may also include other elements that are not explicitly listed or that are inherent to such process, method, article, or device. In the absence of further constraints, an element followed by "a," "an," etc. does not exclude the presence of additional identical elements in the process, method, article, or device that includes the element. In addition, the term "another" is defined as at least the second or more. As used herein, the terms "includes," "has," etc. are defined as "includes." In addition, the background section is not admitted to be prior art and is written as the inventor's own understanding of the context of some embodiments at the time of filing, and includes the inventor's own recognition of any problems with the prior art and / or problems experienced in the inventor's own work.

Claims

1. A method in a user equipment, the method comprising: receiving first information of downlink assignment for a first physical downlink shared channel of a serving cell; identifying a first physical uplink control channel resource and a second physical uplink control channel resource for hybrid automatic repeat request acknowledgement feedback of the first physical downlink shared channel; receiving second information of downlink assignment for a second physical downlink shared channel of the serving cell; determining whether to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel for processing of the second physical downlink shared channel; as well as transmitting hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel on the second physical uplink control channel resource in response to determining to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel, The starting symbol of the second physical downlink shared channel is later than the starting symbol of the first physical downlink shared channel, and The starting symbol of the second physical uplink control channel resource is later than the starting symbol of the first physical uplink control channel resource. transmitting a first hybrid automatic repeat request acknowledgment codebook on the first physical uplink control channel resources and transmitting a second hybrid automatic repeat request acknowledgment codebook on the second physical uplink control channel resources in response to determining to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel, The hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel is included in the second hybrid automatic repeat request acknowledgment codebook.

2. The method according to claim 1, wherein The first physical downlink shared channel is associated with a lower priority than the second physical downlink shared channel.

3. The method according to claim 1, in, The first physical uplink control channel resource is determined based on a first physical uplink control channel resource index and a first physical downlink shared channel to hybrid automatic repeat request timing indicator value, and The second physical uplink control channel resource is determined based on a second physical uplink control channel resource index and a second physical downlink shared channel to hybrid automatic repeat request timing indicator value.

4. The method according to claim 1 , further comprising transmitting hybrid automatic repeat request acknowledgment information of the second physical downlink shared channel on a third physical uplink control channel resource, in, A starting symbol of the third physical uplink control channel resource is earlier than a starting symbol of the first physical uplink control channel resource.

5. The method of claim 1 , further comprising sending the hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel on the first physical uplink control channel resource in response to determining not to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel.

6. The method according to claim 1, wherein The HARQ ACK information of the first PDSCH is appended to other HARQ ACK information of the second HARQ codebook.

7. The method according to claim 1, wherein The first hybrid automatic repeat request acknowledgment codebook includes a bit field for the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel.

8. The method according to claim 7, wherein: The bit field for the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel includes one or more known values.

9. The method according to claim 7, wherein: A width of the bit field for the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel is the same as a size of the hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel.

10. The method according to claim 1, wherein The first physical uplink control channel resources and the second physical uplink control channel resources are in the same cell.

11. The method according to claim 1, wherein The first physical uplink control channel resource and the second physical uplink control channel resource are in different cells.

12. The method according to claim 1, wherein The downlink assignment of the first physical downlink shared channel is a dynamic or semi-persistent allocation.

13. The method according to claim 1, in, The first physical uplink control channel resource overlaps with a physical uplink control channel including at least one selected from ultra-reliable low-latency communication scheduling request information and ultra-reliable low-latency communication hybrid automatic repeat request positive acknowledgement information, wherein the second physical uplink control channel resource does not overlap with the physical uplink control channel, and The method further includes transmitting the hybrid automatic repeat request positive acknowledgement information of the first physical downlink shared channel on the second physical uplink control channel resource.

14. A device comprising: a transceiver that receives first information of downlink assignment for a first physical downlink shared channel of a serving cell; and a controller coupled to the transceiver, wherein The controller identifies a first physical uplink control channel resource and a second physical uplink control channel resource for hybrid automatic repeat request acknowledgement feedback of the first physical downlink shared channel, The transceiver receives second information of downlink assignment for a second physical downlink shared channel of the serving cell, wherein the controller determines whether to delay the hybrid automatic repeat request positive acknowledgement feedback of the first physical downlink shared channel for processing of the second physical downlink shared channel, wherein the transceiver transmits hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel on the second physical uplink control channel resource in response to determining to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel, The starting symbol of the second physical downlink shared channel is later than the starting symbol of the first physical downlink shared channel. The starting symbol of the second physical uplink control channel resource is later than the starting symbol of the first physical uplink control channel resource. wherein the transceiver transmits a first hybrid automatic repeat request acknowledgment codebook on the first physical uplink control channel resource and transmits a second hybrid automatic repeat request acknowledgment codebook on the second physical uplink control channel resource in response to the controller determining to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel, and The hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel is included in the second hybrid automatic repeat request acknowledgment codebook.

15. The device according to claim 14, wherein The first physical downlink shared channel is associated with a lower priority than the second physical downlink shared channel.

16. The device according to claim 14, in, The first physical uplink control channel resource is determined based on a first physical uplink control channel resource index and a first physical downlink shared channel to hybrid automatic repeat request timing indicator value, and The second physical uplink control channel resource is determined based on a second physical uplink control channel resource index and a second physical downlink shared channel to hybrid automatic repeat request timing indicator value.

17. The device according to claim 14, in, The transceiver transmits hybrid automatic repeat request positive acknowledgement information of the second physical downlink shared channel on a third physical uplink control channel resource, and The starting symbol of the third physical uplink control channel resource is earlier than the starting symbol of the first physical uplink control channel resource.

18. The device according to claim 14, wherein The transceiver sends the hybrid automatic repeat request acknowledgment information of the first physical downlink shared channel on the first physical uplink control channel resource in response to the controller determining not to delay the hybrid automatic repeat request acknowledgment feedback of the first physical downlink shared channel.

Images