Method and apparatus for canceling transmission based on overlapping transmission opportunities

Abstract

The present invention relates to a method and apparatus for canceling transmission based on overlapping transmission opportunities. An indication for scheduling a first uplink channel may be sent, wherein the first uplink channel corresponds to a first transmission opportunity and a first priority. An indication for scheduling a second uplink channel may be sent, wherein the second uplink channel corresponds to a second transmission opportunity and a second priority, wherein the first transmission opportunity overlaps with the second transmission opportunity in time, and the first priority is higher than the second priority. A specific symbol of the second uplink channel from which the transmission of the second uplink channel is canceled by a user equipment may be determined based on the first transmission opportunity that overlaps with the second transmission opportunity in time. Reception of the second uplink channel may be canceled based on the determined specific symbol.

Description

[0001] This application is a divisional application of an application which entered the Chinese national phase on October 8, 2021, with PCT application number PCT / IB2020 / 053036, international application date March 31, 2020, Chinese application number 202080027184.4, and invention name “Method and device for canceling transmission based on overlapping transmission opportunities”. Technical Field

[0002] The present disclosure relates to a method and apparatus for communicating over a wireless network. More particularly, the present disclosure relates to canceling transmissions based on overlapping transmission opportunities. Background Art

[0003] Currently, wireless communication devices such as user equipment (UE) use wireless signals to communicate with other communication devices. In the 3rd Generation Partnership Project (3GPP) Release 15 New Radio (NR), basic support for ultra-reliable and low-latency communication (URLLC) is introduced, as well as a transmission time interval (TTI) structure for low latency and methods to improve reliability. For example, non-slot-based (i.e., micro-slots, such as 2, 4 or 7 symbols, whose duration is shorter than the slot duration of 14 symbols) scheduling or transmission of the physical downlink shared channel (PDSCH) / physical uplink shared channel (PUSCH) is allowed, and PDSCH / PUSCH slot aggregation (i.e., repeating PDSCH / PUSCH over multiple slots) is supported. Other use cases with more stringent latency and reliability requirements have been identified. Another use may include enabling use case improvements for Release 15, which include augmented reality (AR) and virtual reality (VR). Other future use cases may include new Release 16 use cases with higher requirements for factory automation, transportation industry, and power distribution. Summary of the invention

[0004] The present invention relates to a method in a network entity, the method comprising: sending an indication for scheduling a first uplink channel, wherein the first uplink channel corresponds to a first transmission opportunity and a first priority; sending an indication for scheduling a second uplink channel, wherein the second uplink channel corresponds to a second transmission opportunity and a second priority, wherein the first transmission opportunity overlaps with the second transmission opportunity in time, and the first priority is higher than the second priority; determining a specific symbol of the second uplink channel based on the first transmission opportunity overlapping with the second transmission opportunity in time, wherein the transmission of the second uplink channel is canceled by a user equipment starting from the specific symbol of the second uplink channel; and canceling the reception of the second uplink channel based on the specific symbol of the second uplink channel, wherein the indication for scheduling the first uplink channel includes a downlink control information format containing scheduling information for the first uplink channel, and wherein the specific symbol is determined based at least on a timing related to sending the downlink control information format.

[0005] The present invention relates to a network entity, comprising: a transceiver, the transceiver: sending an indication for scheduling a first uplink channel, wherein the first uplink channel corresponds to a first transmission opportunity and a first priority; and sending an indication for scheduling a second uplink channel, wherein the second uplink channel corresponds to a second transmission opportunity and a second priority, wherein the first transmission opportunity overlaps with the second transmission opportunity in time, and the first priority is higher than the second priority; and a controller, the controller being coupled to the transceiver, wherein the controller: determines a specific symbol of the second uplink channel based on the first transmission opportunity overlapping with the second transmission opportunity in time, wherein the transmission of the second uplink channel is canceled by a user equipment starting from the specific symbol of the second uplink channel; and cancels the reception of the second uplink channel based on the specific symbol of the second uplink channel, wherein the indication for scheduling the first uplink channel includes a downlink control information format containing scheduling information for the first uplink channel, and wherein the specific symbol is determined based at least on a timing associated with sending the downlink control information format. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0008] Figure 2 is an example flow chart illustrating the operation of a wireless communication device according to a possible embodiment;

[0009] Figure 3 is an example block diagram of an apparatus according to a possible embodiment; and

[0010] Figure 4 is an example flow chart illustrating the operation of a wireless communication device according to a possible embodiment. DETAILED DESCRIPTION

[0011] Embodiments provide a method and apparatus for communicating on a wireless network. At least some embodiments may provide a method for transmitting uplink control information in ultra-reliable and low-latency communications. At least some embodiments may cancel transmissions based on overlapping transmission opportunities.

[0012] According to a possible embodiment, a first transmission opportunity and a first priority of a first uplink channel may be determined. A second transmission opportunity and a second priority of a second uplink channel may be determined. The first priority may be higher than the second priority. The first transmission opportunity may overlap with the second transmission opportunity in time. A specific symbol of the second uplink channel for canceling the transmission of the second uplink channel may be determined based on the first transmission opportunity that overlaps with the second transmission opportunity in time. The transmission of the second uplink channel may be canceled according to the specific symbol.

[0013] Figure 1 1 is an example block diagram of a system 100 according to a possible embodiment. The system 100 may include a UE 110, at least one network entity 120 and 125, and a network 130. The UE 110 may be a wireless wide area network device, a user equipment, a wireless terminal, a portable wireless communication device, a smart phone, a mobile phone, a flip phone, a personal digital assistant, a smart watch, a personal computer, a tablet, a laptop, a selective call receiver, an Internet of Things (IoT) device, or any other user device capable of sending and receiving communication signals on a wireless network. The at least one network entity 120 and 125 may be a wireless wide area network base station, may be a NodeB, may be an enhanced NodeB (eNB), may be a new radio (NR) NodeB (gNB) (e.g., a fifth generation (5G) NodeB), may be an unlicensed network base station, may be an access point, may be a base station controller, may be a network controller, may be a transmission and reception point (TRP), may be a network entity of a different type from other network entities, and / or may be any other network entity that can provide wireless access between a UE and a network.

[0014] The network 130 may include any type of network capable of sending and receiving wireless communication signals. For example, the network 130 may include a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), a long term evolution (LTE) network, a NR network, a network based on the third generation partnership project (3GPP), a 5G network, a satellite communication network, a high altitude platform network, the Internet, and / or other communication networks.

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

[0016] One of the potential physical layer operations of URLLC can be to support more than one physical uplink control channel (PUCCH) transmission from the UE for hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback within a time slot. Non-time slot-based scheduling and multiple HARQ-ACK feedback opportunities within a time slot can reduce the HARQ-ACK round trip time (RTT) of URLLC.

[0017] At least some embodiments may provide methods for supporting more than one PUCCH for HARQ-ACK transmission within a time slot. At least some embodiments may also provide methods for supporting at least two HARQ-ACK codebooks constructed simultaneously, which are intended to support different service types of UEs. At least some embodiments may also provide methods for supporting processing uplink (UL) data / control and control / control resource conflicts, such as methods for resolving resource conflicts between scheduling requests (SRs) associated with high priority traffic and uplink data of lower priority traffic for situations where the media access control (MAC) determines optimization. The method for supporting processing UL data / control and control / control resource conflicts may also include optimization and / or multiplexing behavior among HARQ-ACK / SR / channel state information (CSI) and PUSCH for traffic with different priorities, including cases of uplink control information (UCI) on PUCCH and UCI on PUSCH.

[0018] According to Technical Specification (TS) 38.214 V15.4.0, a UE may be configured by higher layers with a list of up to M transmission configuration index (TCI)-state configurations to decode the PDSCH intended for UEs in a serving cell, where M may depend on the capabilities of the UE.

[0019] Each TCI state may contain parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH. The quasi-co-location relationship may be configured by the high-level parameter qcl-Type1 of the first DL RS and the qcl-Type2 of the second DLRS (if configured). For the case of two DL RSs, the QCL type may be different regardless of whether the same DLRS or different DL RSs are referenced. The quasi-co-location type corresponding to each DL RS is given by the high-level parameter qcl-Type in QCL-Info, which may take one of the following values:

[0020] 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

[0021] 'QCL-TypeB': {Doppler shift, Doppler spread}

[0022] 'QCL-TypeC': {Doppler shift, average delay}

[0023] 'QCL-TypeD': {spatial reception parameters}

[0024] Rules may be specified to send different UCI in PUCCH and / or PUSCH. One rule for sending different UCI in PUCCH and / or PUSCH may include multiple PUCCH-based CSI reports with discarding and multiplexing rules for multiple CSI reports in one time slot. For example, if the UE is not provided with a multi-CSI-PUCCH-ResourceList or if the PUCCH resources used for CSI report transmission do not overlap in a time slot, the long PUCCH carrying the CSI report (i.e., PUCCH formats 3 and 4) may be time domain multiplexed with the short PUCCH (i.e., PUCCH format 2) carrying the CSI report in the time slot. If a multi-CSI-PUCCH-ResourceList is provided to the UE and if any of the multiple PUCCH resources overlap, the UE may multiplex all CSI reports from the resources provided by the multi-CSI-PUCCH-ResourceList.

[0025] Another rule for transmitting different UCI in PUCCH and / or PUSCH may include PUCCH and / or PUSCH overlapping with PUCCH and / or PUSCH resources that do not meet the timing condition. For example, 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 specified timing condition.

[0026] Another rule for sending different UCI in PUCCH and / or PUSCH may include sending HARQ-ACK and CSI in multiple PUCCHs. For example, if simultaneous HARQ-ACK-CSI is not provided to the UE, and if the UE will send HARQ-ACK information in a long PUCCH (PUCCH format 1, 3, or 4) in a given time slot, the UE may not send 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 the time slot. As another example, if simultaneous HARQ-ACK-CSI is not provided to the UE, and if the UE will send HARQ-ACK information with PUCCH format 0 or PUCCH format 2, the UE may not send any PUCCH with PUCCH format 2, PUCCH format 3, or PUCCH format 4 for transmission of CSI reporting if they overlap with any resources from the resources used to transmit HARQ-ACK information.

[0027] Another rule for sending different UCI in PUCCH and / or PUSCH may include UCI multiplexing on PUSCH with an uplink shared channel (UL-SCH). For example, if the PUCCH resources overlap in time with the PUSCH transmission, the UE may multiplex HARQ-ACK information and / or CSI reports in the PUSCH and may not send the SR. In the case where the PUCCH resources overlap in time with multiple PUSCH transmissions, the PUSCH for multiplexing the HARQ-ACK information and / or CSI is selected based on a given criterion. If the UE's PUSCH transmission is not responsive to DCI format detection and the UE only multiplexes CSI reports, the timing condition may not apply. As another example, if the resource is obtained from a set of resources that do not overlap with the second resource, the UE may not expect the resource to overlap with the second resource of the PUCCH transmission on multiple time slots.

[0028] Another rule for transmitting different UCI in PUCCH and / or PUSCH may include a condition on when PUSCH without UL-SCH overlaps with PUCCH including a positive SR on the serving cell, which may be based on Table 1, where the symbol "*" in SR indicates that the SR is positive.

[0029] Table 1

[0030]

[0031] For timing conditions, if the UE will transmit multiple overlapping PUCCHs in a timeslot or transmit overlapping PUCCHs and PUSCHs in a timeslot, and when the UE can be configured to multiplex different UCI types in one PUCCH, and at least one of the multiple overlapping PUCCHs or PUSCHs can respond to DCI format detection by the UE, the UE can multiplex all corresponding UCI types if the following conditions are met. If one of the PUCCH transmissions or PUSCH transmissions is responsive to DCI format detection by the UE, the UE can expect the first symbol S of the earliest PUCCH or PUSCH in the group of overlapping PUCCHs and PUSCHs in the timeslot 0 The following timeline conditions are met, where different variables may be defined in TS38.213.

[0032] A timeline condition can be S 0 Not after the last symbol of any corresponding PDSCH and before a symbol with a cyclic prefix (CP) starting thereafter, where μ corresponds to the minimum SCS configuration of the SCS configuration of the PDCCH that schedules the PDSCH, the SCS configuration of the PDSCH, and the minimum SCS configuration of the group of overlapping PUCCH and PUSCH in which the UE sends HARQ-ACK information in response to reception of the PDSCH.

[0033] Another timeline condition could be S 0 Not after the last symbol of any corresponding SPS PDSCH release Before the start of a symbol with CP, where N is described in subclause 10.2 of TS38.213 and μ corresponds to: the SCS configuration of the PDCCH providing an SPS PDSCH release; and, the minimum SCS configuration of an overlapping PUCCH or a group of overlapping PUCCH and PUSCH, where the UE sends HARQ-ACK information in response to detecting an SPS PDSCH release.

[0034] Another timeline condition may be that if there is no aperiodic CSI report multiplexed in the PUSCH in the group of overlapping PUCCH and PUSCH, then S 0 Not after the last symbol of any PDCCH scheduling PDSCH or SPS PDSCH release with a PDCCH with DCI format scheduling PUSCH and corresponding HARQ-ACK information in the overlapping PUCCH in the slot Before the symbol with CP starting after, where μ corresponds to the minimum SCS configuration of the PDCCH and the minimum SCS of the overlapped PUCCH and PUSCH, and if there is no overlapping PUSCH, then d 2,1 =d 2,2 =0.

[0035] Another timeline condition may be that if there is an aperiodic CSI report multiplexed in the PUSCH in a group of overlapping PUCCH and PUSCH, then S 0 Not after the last symbol of a PDCCH with DCI format that schedules a PUSCH and any PDCCH that schedules a PDSCH or SPS PDSCH release with corresponding HARQ-ACK information in an overlapping PUCCH in a slot before the symbol with CP starting thereafter, where μ corresponds to the minimum SCS configuration in: the SCS configuration of the PDCCH, the minimum SCS configuration of the group of overlapping PUCCH and PUSCH, and the minimum SCS configuration of the non-periodic CSI-RS associated with the DCI format scheduling PUSCH, and for μ=0,1, d=2, for μ=2, d=3 and for μ=3, d=4.

[0036] Another timeline condition could be N 1 , N 2 , d 1，1 , d 2，1 , d 2，2 , and Z is defined in TS38.214, and κ and T are defined in TS38.211 C .

[0037] If the UE will send multiple overlapping PUCCHs in a slot or will send overlapping PUCCH and PUSCH in a slot, then in response to SPS PDSCH reception, one of the PUCCHs includes HARQ-ACK information, and any PUSCH does not respond to DCI format detection, the UE may expect the first symbol S of the earliest PUCCH or PUSCH. 0 The first of the previous timeline conditions is met, except that the component associated with the SCS configuration of the PDCCH scheduling the PDSCH or PUSCH is not in the timeline condition.

[0038] At least some embodiments may provide for URLLC PUCCH / PUSCH overlapping with PUSCH / PUCCH. According to a possible embodiment, if URLLC PUCCH resources or URLLC PUSCH / PUCCH resources for URLLC HARQ-ACK information, URLLC CSI reporting and / or URLLC SR overlap in time with non-URLLC PUSCH (with or without UL-SCH) or non-URLLC PUCCH transmission, where the non-URLLC PUSCH / PUCCH starts earlier than the URLLC PUCCH / PUSCH and does not meet the timing conditions described in subclause 9.2.5 of 3GPP TS 38.213, and the first symbol S of the URLLC PUCCH / PUSCH is overlapped with the URLLC PUCCH / PUSCH. 0 If the timing conditions described in subclause 9.2.5 of TS38.213 are met, the UE may send URLLC PUCCH / PUSCH and may not send non-URLLC PUSCH / PUCCH.

[0039] If a non-URLLC PUSCH / PUCCH transmission has already started, the UE may not expect to cancel the non-URLLC PUSCH / PUCCH transmission URLLC in symbols after a number of symbols less than the first number of symbols relative to the last symbol of the CORESET of the DCI format in which the UE detects a request for URLLC PUCCH / PUSCH transmission (e.g., URLLC HARQ-ACK feedback, URLLC CSI report). In one example, for the most stringent PUSCH processing capability supported by the UE in a given cell, the duration of the first number of symbols may correspond to the PUSCH preparation time T defined in 3GPP Rel-15 TS38.214. proc，2 In another example, the duration of the first number of symbols may correspond to the PUSCH preparation time T of the PUSCH processing capability that the UE is configured to use in a given cell. proc，2 .

[0040] According to a possible implementation, if non-URLLC PUSCH / PUCCH transmission has started, the UE may start from a PUSCH preparation time T corresponding to the PUSCH timing capability after the last symbol of the CORESET of the DCI format in which the UE detects the request for URLLC PUCCH / PUSCH transmission. proc，2The UE may perform this implementation if the duration between the start of the URLLCPUCCH / PUSCH and the end of the non-URLLC PUSCH / PUCCH transmission is longer than a certain threshold, for example, x percentage or y symbols of the non-URLLC PUSCH / PUCCH duration. That is, if the portion of the non-URLLC PUSCH / PUCCH that needs to be canceled is large, the non-URLLC PUSCH / PUCCH may be canceled as soon as possible for UE power saving. The threshold may be configured by RRC or dynamically selected from a set of configuration values, and may be indicated by a network entity or derived by the UE based on the duration of the non-URLLC PUSCH / PUCCH.

[0041] According to another possible implementation, if non-URLLC PUSCH / PUCCH transmission has begun, the UE may cancel starting from the symbol where the URLLC PUCCH resource transmission starts, for example, the non-URLLC PUSCH / PUCCH transmission may not be sent. This implementation may be used in conjunction with other conditions. For example, if the duration between the start of the URLLC PUCCH and the end of the non-URLLC PUSCH / PUCCH transmission is shorter than a certain threshold, for example, x percentage or y symbols of the non-URLLC PUSCH / PUCCH duration, the UE may perform this implementation. That is, if the portion of the non-URLLC PUSCH / PUCCH that needs to be canceled is small, the non-URLLC PUSCH / PUCCH may be transmitted as much as possible to minimize the impact on the demodulation performance of the non-URLLC PUSCH / PUCCH.

[0042] According to another possible implementation, if non-URLLC PUSCH / PUCCH transmission has begun, if frequency hopping of non-URLLC PUSCH / PUCCH is supported and if the time-domain overlapping URLLC PUCCH / PUSCH is within one or several hops of non-URLLC PUCCH / PUCCH, the UE can send a hop of non-URLLC CPUSCH / PUCCH that does not overlap with the URLLC PUCCH / PUSCH. If non-URLLC HARQ-ACK information is multiplexed in the non-URLLC PUSCH so that the non-URLLC HARQ-ACK channel bits are segmented and transmitted in a self-decodable manner in each frequency hop of the non-URLLC PUSCH, this can be used to transmit some non-URLLC HARQ-ACK information even if resource overlap occurs.

[0043] At least some embodiments may provide multiple HARQ-ACK transmissions within a time slot. According to a possible embodiment, if a UE detects a first DCI format, wherein the first DCI format schedules URLLC PDSCH reception or URLLC SPS PDSCH release, and wherein the first DCI format indicates a first resource for a first PUCCH transmission with corresponding first HARQ-ACK information in a time slot, wherein the UE previously detected a second DCI format scheduling a PUSCH transmission in the time slot and the UE multiplexes the second HARQ-ACK information in the PUSCH transmission, at least one of the following cases may be used. For example, the UE may send a HARQ-ACK in response to receiving a DCI format indicating an SPS PDSCH release.

[0044] According to the first possible scenario, the PUSCH may be a URLLC PUSCH and the first PUCCH may overlap in time with the PUSCH in the time slot. In one possible implementation, if the UE previously detected a DCI format that scheduled a URLLC PUSCH transmission in the time slot and if the UE multiplexes HARQ-ACK information in the URLLC PUSCH transmission, the UE may not expect to detect a DCI format that schedules URLLC PDSCH reception or URLLC SPS PDSCH release and indicates resources for PUCCH transmission, where the corresponding URLLC HARQ-ACK information overlaps with the URLLC PUSCH in the time slot.

[0045] According to the second possible scenario, the PUSCH may be a URLLC PUSCH or a non-URLLC PUSCH, and the first PUCCH may not overlap with the PUSCH in time in the time slot. The UE may send both the first PUCCH including the first HARQ-ACK information and the PUSCH including the second HARQ-ACK information in the time slot.

[0046] According to a third possible scenario, the PUSCH may be a non-URLLC PUSCH and the first PUCCH may overlap in time with the PUSCH in a time slot. In one possible implementation, the UE may include the first and second HARQ-ACK information in the first PUCCH, and may send the first PUCCH. The UE may not send, or may cancel the PUSCH transmission. In one example, if the UE is not in a power-limited state and therefore an increased number of resource blocks may be used to send the first PUCCH, the UE may perform this implementation. In a possible implementation, the UE may send a first PUCCH with the first HARQ-ACK information but not including the second HARQ-ACK information. The UE may not send, or may cancel the PUSCH transmission. In one example, if the UE is in a power-limited state, the UE may perform this implementation. In order to avoid ambiguity between the network entity and the UE, the UE may determine whether to include the second HARQ-ACK information in the first PUCCH based on the most recently reported power headroom report. In other implementations, the network entity may indicate to the UE whether to multiplex the second HARQ-ACK information in the first PUCCH.

[0047] At least some embodiments may provide HARQ-ACK mapping on PUSCH for UEs supporting URLLC PUCCH / PUSCH. According to a possible embodiment, if a UE supporting URLLC PUCCH / PUSCH transmission (carrying URLLC HARQ-ACK information, URLLC CSI report and / or URLLC SR) multiplexes HARQ-ACK information on PUSCH, and if frequency hopping is supported for PUSCH, the coded HARQ-ACK bits may be divided in a self-decodable manner, and each group of self-decodable HARQ-ACK channel bits may be transmitted in each frequency hop of PUSCH.

[0048] At least some embodiments may provide HARQ-ACK feedback for a PDSCH with transport block (TB) repetition based on multiple transmission and reception points (TRPs). According to a possible embodiment, if the UE receives more than one codeword (e.g., 2 codewords) in the PDSCH, where the more than one codeword is transmitted from different TRPs with multiple TCI states and is encoded from the same TB, the UE may generate extended HARQ-ACK feedback information by including a preferred TCI state in addition to an indication of (un)successful decoding of the TB, and may send the extended HARQ-ACK feedback information. In one example, for 2 codewords generated from 1TB, the 2-bit HARQ-ACK information indicates one of the following:

[0049] 00: Acknowledgement (ACK), if TB is decoded successfully;

[0050] 01: non-acknowledgement (NACK), preferably the first TCI state;

[0051] 11: NACK, preferably the second TCI state; or

[0052] 10: NACK, preferred first and second TCI states

[0053] The above-mentioned extended HARQ-ACK feedback information can be used to immediately indicate the short-term channel congestion of a certain TRP to the network entity. By indicating that a specific TCI state from two TCI states rather than both TCI states is preferred, the UE can implicitly indicate the temporary poor channel condition of one TCI state.

[0054] Figure 2 200 is an example flow chart illustrating the operation of a wireless communication device such as UE 110 according to a possible embodiment. At 210, a first transmission opportunity and a first priority of a first uplink channel may be determined. The first uplink channel may be a first physical uplink channel. The first uplink channel may include URLLC data and / or URLLC UCI. For example, the UE may send / communicate URLLC data / UCI on / via the first uplink channel. The first uplink channel may carry URLLC data / UCI.

[0055] At 220, a second transmission opportunity and a second priority for a second uplink channel may be determined. The second uplink channel may be a second physical uplink channel. The first priority may be higher than the second priority. The first transmission opportunity may overlap at least partially in time with the second transmission opportunity. The second transmission opportunity may start earlier than the first transmission opportunity.

[0056] URLLC PUSCH / PUCCH may be equivalent to a high priority uplink channel carrying high priority traffic. Non-URLLC PUSCH / PUCCH may be equivalent to a low priority uplink channel carrying low priority traffic.

[0057] At 230, a specific symbol of the second uplink channel for canceling transmission of the second uplink channel may be determined. According to a possible embodiment, a DCI format including scheduling information for the first uplink channel may be detected, and the specific symbol may be determined based at least on timing associated with the detected DCI format.

[0058] At 240, transmission of the second uplink channel may be canceled from the specific symbol. Canceling transmission of the second uplink channel from the specific symbol may include stopping transmission of the second uplink channel from the specific symbol. The specific symbol may not be a start symbol of the second uplink channel. For example, transmission of the second uplink channel may be stopped after it has already started.

[0059] According to a possible embodiment, the start time of the specific symbol may not be later than the start time of the first transmission opportunity. According to a possible embodiment, the specific symbol may not be the start symbol of the second uplink channel. For example, the UE may not be able to perform simultaneous transmission of the first and second uplink channels. Therefore, the cancellation of the second uplink channel may not be later than the start time of the first transmission opportunity.

[0060] According to a possible embodiment, the specific symbol may be determined based on the PUSCH timing capability.If the first uplink channel is dynamically scheduled by a PDCCH carrying a DCI format, the start time of cancellation may be determined based on the timing of DCI detection and the timing capability of the PUSCH.

[0061] According to a possible embodiment, the first uplink channel may be a PUCCH carrying the first HARQ-ACK information. The second uplink channel may be a PUSCH carrying at least the second HARQ-ACK information. The second HARQ-ACK information may be multiplexed with the first HARQ-ACK information in the first uplink channel. For example, an embodiment may provide multiple HARQ-ACK transmissions within a time slot. According to a possible embodiment, the number of resource blocks used to transmit a PUCCH transmission including the first HARQ-ACK information and the second HARQ-ACK information may be greater than the number of resource blocks used to transmit a PUCCH transmission including only the first HARQ-ACK information. According to a possible implementation, the number of resource blocks used for PUCCH transmission may be determined based on the UCI payload size. For example, the number of resource blocks used for PUCCH transmission may increase with a larger payload size.

[0062] According to a possible implementation, the first HARQ-ACK information may have a higher priority than the second HARQ-ACK information. For example, the first HARQ-ACK may be a URLLC HARQ-ACK, and the second HARQ-ACK may be a non-URLLC HARQ-ACK.

[0063] According to a possible implementation, an indication may be received. The indication may indicate multiplexing the second HARQ-ACK information and the first HARQ-ACK information in the first uplink channel. For example, the network entity may indicate to the UE whether to multiplex the second HARQ-ACK information in the first PUCCH.

[0064] According to a possible implementation, it may be determined whether the UE is in a power limited state. In response to determining that the UE is not in a power limited state, the second HARQ-ACK information may be multiplexed by multiplexing the second HARQ-ACK information with the first HARQ-ACK information in the first uplink channel.

[0065] For example, if the second HARQ-ACK is multiplexed in the first uplink channel, the number of RBs used for the first uplink channel may be increased. A larger number of RBs used for uplink transmission may require higher transmit power than a smaller number of RBs used for uplink transmission. If the UE is in a power-limited state, such as when the required transmit power is higher than the maximum configured power, increasing the number of RBs may degrade demodulation performance. If the UE is not in a power-limited state, such as when the required transmit power is lower than the maximum configured power, increasing the number of RBs may not degrade demodulation performance.

[0066] As a further example, the UE may include the first and second HARQ-ACK information in the first PUCCH and may send the first PUCCH. The UE may not send or may cancel the PUSCH transmission. In an example, if the UE is not in a power limited state, the UE may perform this implementation and may therefore use an increased number of resource blocks to send the first PUCCH.

[0067] According to a possible embodiment, a specific symbol can be determined based on the number of symbols during the duration between the start time of the first transmission opportunity and the end time of the second transmission opportunity. For example, the UE can cancel from the symbol at the beginning of the URLLC PUCCH resource transmission, for example, not sending a non-URLLC PUSCH / PUCCH transmission. According to a possible example, if the duration from the start of the URLLC PUCCH to the end of the non-URLLC PUSCH / PUCCH transmission is shorter than a certain threshold, such as x percentage or y symbols of the non-URLLC PUCCH transmission duration, the UE can perform this implementation. That is, if the portion of the non-URLLC PUSCH / PUCCH that needs to be canceled is small, the non-URLLC PUSCH / PUCCH can be transmitted as much as possible to minimize the impact on the demodulation performance of the non-URLLC PUSCH / PUCCH. According to a possible implementation, if the number of symbols is less than the threshold, the time interval of the specific symbol may include the start time of the first transmission opportunity.

[0068] According to a possible embodiment, the second uplink channel may include multiple frequency hopping. Each of the multiple frequency hopping may include a set of self-decoding coded HARQ-ACK bits. For example, if frequency hopping of non-URLLC PUSCH / PUCCH is enabled, and if the URLLC PUCCH / PUSCH overlapping in the time domain is located within one or several hops of the non-URLLC PUSCH / PUCCH, the UE may send a hop of non-URLLC PUSCH / PUCCH that does not overlap with the URLLC PUCCH / PUSCH. If non-URLLC HARQ-ACK information is multiplexed in the non-URLLC PUSCH so that the non-URLLC HARQ-ACK channel bits are segmented and transmitted in each frequency hopping of the non-URLLC PUSCH in a self-decoding manner, this can be used to send some of the non-URLLC HARQ-ACK information, even when resource overlap occurs.

[0069] According to a possible implementation, canceling the transmission of the second uplink channel may include canceling the transmission of the first at least one hopping frequency of the second uplink channel. The third transmission opportunity of the first at least one hopping frequency may overlap with the first transmission opportunity in time. The second at least one hopping frequency of the second uplink channel may be transmitted. The fourth transmission opportunity of the second at least one hopping frequency may not overlap with the first transmission opportunity in time.

[0070] It should be understood that, despite the specific steps shown, a variety of additional or different steps may be performed depending on the embodiment, and one or more specific steps may be rearranged, repeated, or completely eliminated depending on the embodiment. In addition, certain steps may be performed repeatedly on an ongoing or continuous basis while performing other steps. In addition, different steps may be performed by different elements or in a single element of the disclosed embodiments.

[0071] Figure 3 3 is an example block diagram of an apparatus 300 according to a possible embodiment, the apparatus 300 being, for example, a UE 110, a network entity 120, or any other wireless communication device disclosed herein. The apparatus 300 may include a housing 310, a controller 320 coupled to the housing 310, an audio input and output circuit 330 coupled to the controller 320, a display 340 coupled to the controller 320, a memory 350 coupled to the controller 320, a user interface 360 ​​coupled to the controller 320, a transceiver 370 coupled to the controller 320, at least one antenna 375 coupled to the transceiver 370, and a network interface 380 coupled to the controller 320. The apparatus 300 may not necessarily include all of the elements of the different embodiments of the present disclosure shown. The apparatus 300 may perform the methods described in all embodiments.

[0072] The display 340 may 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 that displays information. The transceiver 370 may be one or more transceivers, which may include a transmitter and / or a receiver. The audio input and output circuit 330 may include a microphone, a speaker, a transducer, or any other audio input and output circuit. The user interface 360 ​​may include a keypad, a keyboard, a button, a touch pad, a joystick, a touch screen display, another additional display, or any other device for providing an interface between a user and an electronic device. The network interface 380 may 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, a device, and / or a computer and can send and receive data communication signals. The memory 350 may include a random access memory (RAM), a read-only memory (ROM), an optical memory, a solid-state memory, a flash memory, a removable memory, a hard drive, a cache, or any other memory that can be coupled to the device.

[0073] The device 300 or the controller 320 may implement any operating system, such as Microsoft Android TM or any other operating system. The device operating software can be written in any programming language, such as C, C++, Java or Visual Basic. The device software can also run on an application framework, such as frame, Framework or any other application framework. The software and / or operating system may be stored in the memory 350, elsewhere on the device 300, in the cloud storage and / or anywhere else where the software and / or operating system may be stored. The device 300 or the controller 320 may also use hardware to implement the disclosed operations. For example, the controller 320 may be any programmable processor. In addition, the controller 320 may perform some or all of the disclosed operations. For example, at least some operations may be performed using cloud computing and the controller 320 may perform other operations. At least some operations may also be performed by computer executable instructions executed by at least one computer processor. The disclosed embodiments may also be implemented on general or special computers, programmable microprocessors or microprocessors, peripheral integrated circuit elements, application specific integrated circuits or other integrated circuits, hardware / electronic logic circuits (e.g., discrete element circuits), programmable logic devices (e.g., programmable logic arrays or field programmable gate arrays), etc. In general, the controller 320 may be any controller or one or more processor devices capable of operating the device and implementing the disclosed embodiments. Some or all of the additional elements of the device 300 may also perform some or all of the operations of the disclosed embodiments.

[0074] In operation, the apparatus 300 may perform the methods and operations of the disclosed embodiments. The transceiver 370 may send and receive signals, including data signals and control signals that may include corresponding data and control information. The controller 320 may generate and process the transmitted and received signals and information.

[0075] In operation according to a possible embodiment, the transceiver 370 can communicate on a wireless communication network. The controller 320 can determine a first transmission opportunity and a first priority of a first uplink channel. According to a possible embodiment, the first uplink channel can include URLLC data and / or URLLC uplink control information.

[0076] The controller 320 may determine a second transmission opportunity and a second priority for the second uplink channel. The first priority may be higher than the second priority. According to a possible embodiment, the first transmission opportunity may overlap at least partially with the second transmission opportunity in time. According to a possible embodiment, the second transmission opportunity may start earlier than the first transmission opportunity.

[0077] The controller 320 may determine a specific symbol of the second uplink channel for canceling the transmission of the second uplink channel. The controller 320 may cancel the transmission of the second uplink channel from the specific symbol. According to a possible embodiment, canceling the transmission of the second uplink channel from the specific symbol may include stopping the transmission of the second uplink channel from the specific symbol. The specific symbol may not be the start symbol of the second uplink channel. According to another possible embodiment, the start time of the specific symbol may not be later than the start time of the first transmission opportunity. According to a possible embodiment, the specific symbol may not be the start symbol of the second uplink channel.

[0078] The controller 320 may detect a downlink control information format including scheduling information for the first uplink channel, and may determine a specific symbol based at least on timing associated with detecting the downlink control information format. According to a possible embodiment, the specific symbol is determined based on a physical uplink shared channel timing capability.

[0079] Figure 4 4 is an example flow chart 400 illustrating the operation of a wireless communication device, such as network entity 120, according to a possible embodiment. At 410, an indication for scheduling a first uplink channel may be sent. The first uplink channel may correspond to a first transmission opportunity and a first priority. At 420, an indication for scheduling a second uplink channel may be sent. The second uplink channel may correspond to a second transmission opportunity and a second priority. The first transmission opportunity may overlap in time with the second transmission opportunity. The first priority may be higher than the second priority.

[0080] At 430, a specific symbol of the second uplink channel may be determined based on the first transmission opportunity that overlaps with the second transmission opportunity in time, wherein the transmission of the second uplink channel is canceled by the user equipment starting from the specific symbol of the second uplink channel. At 440, the reception of the second uplink channel may be canceled based on the determined specific symbol.

[0081] According to a possible embodiment, when the network entity accurately cancels the reception of the second uplink channel, it may depend on the network entity implementation. According to a possible example, the network entity may stop receiving the second uplink channel from a specific symbol. According to another possible example, the network entity may stop receiving the second uplink channel before a specific symbol.

[0082] According to a possible embodiment, the first uplink channel may include at least one of URLLC data and URLLC uplink control information.

[0083] According to a possible embodiment, the first transmission opportunity may partially overlap with the second transmission opportunity in time, and the second transmission opportunity may start earlier than the first transmission opportunity.

[0084] According to a possible embodiment, the user equipment may stop transmission of the second uplink channel from a specific symbol, wherein the specific symbol may not be a start symbol of the second uplink channel.

[0085] According to a possible embodiment, the start time of the specific symbol may be no later than the start time of the first transmission opportunity.

[0086] According to a possible embodiment, the indication of scheduling the first uplink channel may be a DCI format comprising scheduling information for the first uplink channel, wherein the specific symbol may be determined based at least on a timing associated with transmitting the DCI format.

[0087] According to a possible embodiment, the specific symbol may be determined based on the PUSCH timing capability of the UE.

[0088] According to a possible embodiment, the first uplink channel may be a PUCCH carrying first HARQ-ACK information, the second uplink channel may be a PUSCH carrying at least second HARQ-ACK information, and the first and second HARQ-ACK information may be received in the first uplink channel.

[0089] According to a possible embodiment, the first HARQ-ACK information may have a higher priority than the second HARQ-ACK information.

[0090] According to a possible embodiment, an indication may be transmitted. The indication may indicate that the second HARQ-ACK information and the first HARQ-ACK information are multiplexed in the first uplink channel.

[0091] According to a possible embodiment, it may be determined whether the UE is in a power limited state. Receiving the first and second HARQ-ACK information may include receiving the first and second HARQ-ACK information in a first uplink channel in response to determining that the UE is not in a power limited state.

[0092] According to a possible embodiment, the specific symbol may be determined based on the number of symbols during a duration between a start time of the first transmission opportunity and an end time of the second transmission opportunity.

[0093] According to a possible embodiment, if the number of symbols is less than a threshold, the time interval of a specific symbol may include a start time of the first transmission opportunity.

[0094] According to a possible embodiment, the second uplink channel may include a plurality of hopping frequencies, wherein each of the plurality of hopping frequencies may include a set of self-decodable coded HARQ-ACK bits. According to a possible embodiment, cancelling reception of the second uplink channel may include cancelling reception of a first at least one hopping frequency of the second uplink channel, wherein a third transmission opportunity of the first at least one hopping frequency may overlap in time with the first transmission opportunity. A second at least one hopping frequency of the second uplink channel may be received, wherein a fourth transmission opportunity of the second at least one hopping frequency may not overlap in time with the first transmission opportunity.

[0095] According to a possible embodiment, if the UE detects a first DCI format for scheduling URLLC PDSCH reception or URLLC SPS PDSCH release and indicates a first resource for a first PUCCH transmission, wherein the corresponding first HARQ-ACK information overlaps with a non-URLLC PUSCH in a time slot, wherein the UE previously detected a second DCI format for scheduling non-URLLC PUSCH transmission in the time slot and the UE multiplexed the second HARQ-ACK information in the non-URLLC PUSCH transmission, then the non-power-limited UE may include the first and second HARQ-ACK information in the first PUCCH and send the first PUCCH. The UE may not send or may cancel the non-URLLC PUSCH transmission. The UE may not be in a power-limited state, and therefore may use an increased number of resource blocks to send the first PUCCH. If the UE is in a power-limited state, the UE may send a first PUCCH with the first HARQ-ACK information but not including the second HARQ-ACK information. In order to avoid ambiguity between the network entity and the UE, the UE may determine whether to include the second HARQ-ACK information in the first PUCCH based on the most recently reported power headroom report.

[0096] If the UE multiplexes HARQ-ACK information on PUSCH and if frequency hopping is enabled for PUSCH, the coded HARQ-ACK bits can be divided in a self-decodable manner and each group of self-decodable HARQ-ACK channel bits can be transmitted in each frequency hop of PUSCH. With this scheme, a portion of the HARQ-ACK information can still be transmitted even when part of the PUSCH transmission (e.g., the first hop or the second hop) needs to be canceled to avoid conflict with the URLLC PUCCH / PUSCH.

[0097] According to at least some embodiments, a method may be performed in a UE. The method may include receiving downlink shared channel data including URLLC data. The method may include determining a first transmission opportunity for sending a PUCCH transmission including at least a first HARQ-ACK information in response to receiving the downlink shared channel data. The method may include receiving scheduling information for an uplink shared channel transmission that does not include URLLC data at a second transmission opportunity, wherein the uplink shared channel may include a second HARQ-ACK information, and wherein the first transmission opportunity may overlap with the second transmission opportunity. The method may include determining not to transmit or cancel an uplink shared channel transmission in response to the first transmission opportunity overlapping with the second transmission opportunity. The method may include determining whether the UE is in a power-limited state. The method may include, in response to determining that the UE is not power-limited, sending a first PUCCH transmission including a first HARQ-ACK information and a second HARQ-ACK information. The method may include, in response to determining that the UE is in a power-limited state, sending a first PUCCH transmission including only the first HARQ-ACK information.

[0098] According to a possible implementation, the number of resources used to send the first PUCCH transmission may include the first HARQ-ACK information, and the second HARQ-ACK information may be greater than the number of resources used to send the first PUCCH transmission including only the first HARQ-ACK information.

[0099] According to at least some additional embodiments, a method may be performed in a UE. The method may include receiving a first codeword including a transport block associated with a first TCI state in a first transmission opportunity. The method may include receiving a second codeword including a transport block associated with a second TCI state in a second transmission opportunity, wherein the second transmission opportunity may overlap with the first transmission opportunity. The method may include determining HARQ-ACK feedback information in response to receiving the first codeword and the second codeword. The method may include sending at least one preferred TCI state for retransmission of the transport block in the HARQ-ACK feedback information in response to determining a NACK for the transport block.

[0100] According to a possible implementation, the first codeword may be sent from the first TRP and the second codeword may be sent for the second TRP. According to a possible implementation, the method may include determining a preferred TCI state in the first TCI state and the second TCI state based on link quality with respect to the received first codeword and the second codeword, respectively. According to a possible implementation, the link quality may be based on one or more of a signal-to-interference-plus-noise ratio (SINR), a reference signal received power, a channel quality metric, a log-likelihood ratio (LLR), and / or a mean mutual information associated with the codeword (MMIB).

[0101] At least some of the methods of the present disclosure may be implemented on a programmed processor. However, the controller, flow charts, and modules may also be implemented on a general or special purpose computer, a programmable microprocessor or microcontroller and peripheral integrated circuit components, an integrated circuit, a hardware electronic or logic circuit (e.g., a discrete component circuit), or 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 figures may be used to implement the processor functions of the present disclosure.

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

[0103] In this document, relative terms such as "first" and "second" can be used alone to distinguish one entity or action from another entity or action, without requiring or implying any actual such relationship or order between these entities or actions. The phrases "at least one", "at least one selected from the group of..." or "at least one selected from..." followed by a list are defined to represent one, some or all, but not necessarily all, of the elements in the list. The terms "comprise", "contain", "include" or any other variation thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device containing the list of elements includes not only those elements, but also other elements that are not explicitly listed or inherent to such processes, methods, articles or devices. An element preceded by "one" or "an" does not exclude the presence of additional identical elements in the process, method, article or device including the element without more restrictions. In addition, the term "another" is defined as at least the second or more. The terms "comprise" and "have" as used herein are defined as "include". In addition, the background section is written as the inventor's own understanding of the context of some embodiments when filing the application, and includes the inventor's own recognition of any problems with the prior art and / or problems encountered in the inventor's own work.

Claims

1. A method in a network entity, the method comprising: sending an indication for scheduling a first uplink channel, wherein the first uplink channel corresponds to a first transmission opportunity and a first priority; sending an indication for scheduling a second uplink channel, wherein the second uplink channel corresponds to a second transmission opportunity and a second priority, wherein the first transmission opportunity overlaps with the second transmission opportunity in time, and the first priority is higher than the second priority; determining a specific symbol of the second uplink channel based on the first transmission opportunity that overlaps with the second transmission opportunity in time, wherein the transmission of the second uplink channel is cancelled by the user equipment starting from the specific symbol of the second uplink channel; as well as canceling reception of the second uplink channel based on the specific symbol of the second uplink channel, wherein the indication for scheduling the first uplink channel comprises a downlink control information format including scheduling information for the first uplink channel, and The specific symbol is determined based at least on a timing associated with sending the downlink control information format.

2. The method according to claim 1, wherein: The first uplink channel includes at least one of ultra-reliable low-delay communication data and ultra-reliable low-delay communication uplink control information.

3. The method according to claim 1, wherein: The first transmission opportunity partially overlaps with the second transmission opportunity in time, wherein the second transmission opportunity starts earlier than the first transmission opportunity.

4. The method according to claim 1, wherein: The user equipment stops transmission of the second uplink channel from the specific symbol, wherein the specific symbol is not a start symbol of the second uplink channel.

5. The method according to claim 1, wherein: The start time of the specific symbol is no later than the start time of the first transmission opportunity.

6. The method of claim 1, wherein the specific symbol is determined based on a physical uplink shared channel timing capability for the user equipment.

7. The method according to claim 1, wherein: The first uplink channel comprises a physical uplink control channel carrying first hybrid automatic repeat request confirmation information; The second uplink channel includes a physical uplink shared channel carrying at least second hybrid automatic repeat request confirmation information, and The method further includes: receiving the first hybrid automatic repeat request confirmation information and the second hybrid automatic repeat request confirmation information in the first uplink channel.

8. The method according to claim 7, wherein: The priority of the first hybrid automatic repeat request confirmation information is higher than the priority of the second hybrid automatic repeat request confirmation information.

9. The method according to claim 7, further comprising: An indication is sent in the first uplink channel to multiplex the second hybrid automatic repeat request confirmation information with the first hybrid automatic repeat request confirmation information.

10. The method according to claim 7, further comprising: determining whether the user equipment is in a power limited state, Wherein, receiving the first hybrid automatic repeat request confirmation information and the second hybrid automatic repeat request confirmation information includes receiving the first hybrid automatic repeat request confirmation information and the second hybrid automatic repeat request confirmation information in the first uplink channel in response to determining that the user equipment is not in the power limited state.

11. The method according to claim 1, wherein: The specific symbol is determined based on the number of symbols during a duration between a start time of the first transmission opportunity and an end time of the second transmission opportunity.

12. The method according to claim 11, wherein: If the number of the symbols is less than a threshold, the time interval of the specific symbols includes a start time of the first transmission opportunity.

13. The method according to claim 1, wherein: The second uplink channel comprises a plurality of hopping frequencies, wherein each of the plurality of hopping frequencies comprises a set of self-decodable coded hybrid automatic repeat request acknowledgement bits.

14. The method according to claim 13, wherein: cancelling reception of the second uplink channel comprises cancelling reception of a first at least one hopping frequency of the second uplink channel, wherein a third transmission opportunity of the first at least one hopping frequency overlaps in time with the first transmission opportunity, and The method further includes: receiving at least one second frequency hopping of the second uplink channel, wherein a fourth transmission opportunity of the at least one second frequency hopping does not overlap with the first transmission opportunity in time.

15. A network entity, comprising: a transceiver, the transceiver: sending an indication for scheduling a first uplink channel, wherein the first uplink channel corresponds to a first transmission opportunity and a first priority; as well as sending an indication for scheduling a second uplink channel, wherein the second uplink channel corresponds to a second transmission opportunity and a second priority, wherein the first transmission opportunity overlaps with the second transmission opportunity in time, and the first priority is higher than the second priority; as well as a controller coupled to the transceiver, wherein the controller: determining a specific symbol of the second uplink channel based on the first transmission opportunity temporally overlapping with the second transmission opportunity, wherein transmission of the second uplink channel is cancelled by the user equipment starting from the specific symbol of the second uplink channel; and canceling reception of the second uplink channel based on the specific symbol of the second uplink channel, wherein the indication for scheduling the first uplink channel comprises a downlink control information format including scheduling information for the first uplink channel, and The specific symbol is determined based at least on a timing associated with sending the downlink control information format.

16. The network entity according to claim 15, wherein: The first uplink channel includes at least one of ultra-reliable low-delay communication data and ultra-reliable low-delay communication uplink control information.

17. The network entity according to claim 15, wherein: The first transmission opportunity partially overlaps with the second transmission opportunity in time, wherein the second transmission opportunity starts earlier than the first transmission opportunity.

18. The network entity according to claim 15, wherein: The start time of the specific symbol is no later than the start time of the first transmission opportunity.

Images