Patent Description:
Demands for the 4th Generation Mobile Communication Technology (<NUM>), Long-Term Evolution (LTE), Advanced LTE (LTE-Advanced or LTE-A), and the 5th Generation Mobile Communication Technology (<NUM>) are increasing at a rapid pace. Developments are taking place to provide enhanced mobile broadband, ultra-high reliability, ultra-low-latency transmission, and massive connectivity in <NUM> and <NUM> systems.

3GPP Draft R1-<NUM>, 3GPP TS <NUM> V15. <NUM> and 3GPP Draft R1-<NUM> are related prior art documents.

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein.

In wireless communication systems, different types of uplink services with different transmission delay reliability requirements and different priority channels for the same service can be transmitted. In some cases, a first service with one or more of higher priority, higher reliability, or shorter transmission time can preempt (communication resources of) a second service with one or more of lower priority, lower reliability, or longer transmission time. The embodiments described herein relate to the manner in which the network side indicates or signals a transmission mechanism of an uplink service and the manner in which the terminal side monitors the indication signaling.

Developments in <NUM> wireless communication systems are directed to achieving higher data communicate rate (e.g., in Gbps), massive number of communication links (e.g., <NUM>/Km<NUM>), ultra-low latency (e.g., under <NUM>), higher reliability, and improved energy efficiency (e.g., at least <NUM> times more efficient than previous systems). For improved coverage, <NUM> systems can implement slot-based aggregation and slot-based repetitions. The slot-based aggregation is based on dynamic grant. The slot-based repetitions are based on configured grant. For example, a user equipment (UE) (e.g., a terminal, a mobile device, a mobile user, a wireless communication device, and so on) can repeatedly transmit (retransmit) a transport block (TB) across multiple (consecutive) slots. The TB is allocated the same time resource (e.g., the same symbol(s)) in each of the multiple slots. In order to support ultra-high reliability and ultra-low latency transmission, low-latency and high-reliability services need to be transmitted within a short transmission time interval. To achieve that, uplink aggregated transmission (based on dynamic grant) and uplink repetitive transmission (based on configured grant) need to be improved. In that regard, in some cases, the same TB is repeatedly transmitted in a same time slot, or the same TB is repeatedly transmitted (one or more times) across a slot boundary of a plurality of consecutive available slots.

Furthermore, in order to support ultra-high reliability and ultra-low latency transmission, a low-latency and high-reliability service that needs to be transmitted within a short transmission time interval can preempt resources that may be used by or allocated to other services with longer transmission time (before the other services are transmitted or while the other services are being transmitted). In some cases, preemptive transmission can occur for a same UE in multiple uplink transmissions/retransmissions and for multiple UEs in a single uplink transmission. In such situations, the UE that has its resources preempted may not be aware of the preemption. To minimize the performance impact in this situation, preemption indication information needs to be conveyed to the UE that has its transmission resources preempted. Based on such preemption indication information, uplink transmissions of services that have a relatively low priority can accordingly be canceled (if not yet transmitted) or stopped (while being transmitted), thus avoiding performance degradation resulting from simultaneously transmitting both types of services using the same uplink transmission resource.

Currently, with respect to downlink transmission resource preemption, a base station (e.g., BS, gNB, eNB, and so on) uses downlink control information (DCI) to indicate the preempted resources in a reference downlink resource (RDR). In particular, configured RDR is partitioned into <NUM> blocks by the base station, for example, using {M, N}={<NUM>, <NUM>} or {<NUM>, <NUM>}. A bitmap maps bits (indicative of preemption status) unto the blocks. The bitmap is used to indicate whether each of the blocks is preempted. M represents a number of partitions of the RDR in the time domain. N represents a number of partitions of the RDR in the frequency domain.

When preemption occurs, the base station can send a downlink preemption indication (DL PI) at a specific monitoring occasion after the end of the preemptive downlink transmission. The DL PI is a type of "after-the-fact" indication. The terminal further completes the reception of the downlink transmission. The UE monitors the DL PI after receiving the downlink transmission to determine whether the previous downlink transmission is preempted and processes the downlink data in response to determining that the downlink transmission has not been preempted.

With respect to uplink service cancelation, a similar indication can be defined, e.g., for uplink time-frequency domain resources. In contract with the DL PI, in order to prevent uplink transmission of the UE, the UE needs to be notified of the preemption via a UL CI before transmission of the uplink service.

In order to transmit the uplink preemption information (e.g., the UL CI) in a timely manner, the network side (including the base stations and other network functions of a network) configures monitoring occasions for the uplink preemption information in a high density (e.g., more frequently). The network side only sends the UL CI in response to a cancelation event, which can be relatively infrequent. In order not to miss any UL CI, the UE needs to blind check for the indication information on all downlink control channels or all monitoring occasions of the downlink control channels, thus increasing complexity and power consumption. In that regard, embodiments of the present disclosure allow effective detection of information indicating the preemption or cancelation of resources.

<FIG> is a schematic diagram illustrating a process <NUM> by which a physical uplink shared channel (PUSCH) uplink transmission resource is canceled, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the process <NUM> involves a UE <NUM>, a base station <NUM> (e.g., a BS, gNB, eNB, and so on), and a UE <NUM>. An uplink transmission diagram <NUM> illustrates uplink activities for the UE <NUM>. An uplink transmission diagram <NUM> illustrates uplink transmission activities for the UE <NUM>. A downlink transmission diagram <NUM> illustrates downlink activities of the base station <NUM>. The diagrams <NUM>, <NUM>, and <NUM> show slots divided in the time domain (denoted by the x-axis). In some examples, the dimension or axis of each of the diagrams <NUM>, <NUM>, and <NUM> that is perpendicular to the time domain axis represents frequency such as but not limited to, a bandwidth, an active uplink bandwidth part (BWP), and so on, although frequency is discontinuous across the different diagrams <NUM>, <NUM>, and <NUM>.

The UE <NUM> sends a scheduling request (SR) <NUM> to the base station <NUM>. The SR <NUM> requests the base station <NUM> for uplink transmission resource for uplink service such as but not limited to, an enhanced mobile broadband (eMBB) service. The base station <NUM> allocates the uplink transmission resource (e.g., a PUSCH <NUM>) for the UE <NUM> via uplink grant (UL grant) <NUM>. The base station <NUM> sends the UL grant <NUM> to the UE <NUM> to notify the UE <NUM> that the UE <NUM> can transmit the uplink service using the PUSCH <NUM>.

After the UE <NUM> sends the SR <NUM> to the base station <NUM>, and after the base station <NUM> sends the UL grant <NUM> to the UE <NUM>, the UE <NUM> sends an SR <NUM> to the base station <NUM>. The SR <NUM> requests the base station <NUM> for uplink transmission resource for uplink service such as but not limited to, an ultra-reliable low latency communications (URLLC) service. Given that the uplink service (e.g., the URLLC service) of the UE <NUM> has ultra-high reliability and ultra-low-latency transmission requirements, the base station <NUM> allocates uplink transmission resource that is as early in time as possible. The base station <NUM> determines that the uplink transmission resource (e.g., a PUSCH <NUM>) that satisfies the ultra-high reliability and ultra-low-latency transmission requirements may have already been allocated to the UE <NUM>. That is, the base station <NUM> determines that at least a portion of the PUSCH <NUM> collides (e.g., overlaps in time) with at least a portion of the PUSCH <NUM>. In response to determining that the priority of the uplink service (e.g., the URLLC service) of the UE <NUM> is higher than the priority of the uplink service (e.g., the eMBB service) of the UE <NUM>, the base station <NUM> cancels the transmission of the UE <NUM> on the previously allocated uplink transmission resource (e.g., the PUSCH <NUM>).

The low-priority uplink transmission can be canceled using various methods. In one example, the base station <NUM> reschedules a new uplink transmission resource (e.g., PUSCH <NUM>) for the UE <NUM> and then cancels the uplink transmission on the originally allocated uplink transmission resource (e.g., the PUSCH <NUM>). The base station <NUM> can retransmit a UL grant <NUM> to the UE <NUM> to notify the UE <NUM> that the UE <NUM> can transmit the uplink service using the PUSCH <NUM> (e.g., the transmission is rescheduled to another uplink transmission resource PUSC <NUM>). In some examples, the base station <NUM> can transmit the UL grant <NUM> at the same time (e.g., within a same time slot) as the UL grant <NUM>, using different frequency resources. The HARQ process identifier (ID) of the UL grant <NUM> is the same as the HARQ process ID of the UL grant <NUM>. A new data indicator (NDI) field of the UL grant <NUM> is toggled, thus indicating that the uplink grant <NUM> corresponds to the uplink service (e.g., the eMBB service) for which uplink transmission resource (e.g., the PUSCH <NUM>) was previously allocated and that the previously allocated uplink transmission resource (e.g., the PUSCH <NUM>) is released. In some examples, the entire originally allocated uplink transmission resource (e.g., the PUSCH <NUM>) or a portion thereof can be rescheduled and released using such method. Also, an entire transport block (TB) or a portion thereof can be transmitted using the new uplink transmission resource (e.g., the PUSCH <NUM>).

In another example, the base station <NUM> can notify the UE <NUM> that the originally allocated uplink transmission resource (e.g., the PUSCH <NUM>) is preempted by the high-priority service transmission using cancelation indication signaling (e.g., the UL CI). Accordingly, the UE <NUM> cancels the transmission on the preempted resource (e.g., the PUSCH <NUM>) in response to receiving the cancelation indication signaling. The cancelation indication signaling can be carried in the physical DCI on the downlink control channel or another specific signal sequence.

The cancelation indication signaling is signaling used to indicate or otherwise identify time-frequency domain resource to be canceled. Indication methods such as but not limited to, Method <NUM> and Method <NUM> can be implemented for indicating the time-frequency domain resource.

In some examples, <MAT> bits of a field in UL CI (e.g., in DCI format 2_4) have one-to-one mapping with NSI groups of symbols, where each of the first NSI - TCI + <MAT> groups includes <MAT> symbols, and each of the remaining <MAT> NSI groups includes <MAT> symbols. A UE does not expect <MAT>.

In some examples, MCI groups of symbols from NSI groups of symbols contain cancelation resource. MCI sets of <MAT> bits of a field in UL CI have one-to-one mapping with MCI groups of symbols.

For a symbol group, NBI bits in each set of bits have one-to-one mapping with NBI groups of PRBs, where each of the first <MAT> groups includes <MAT> PRBs, and each of the remaining <MAT> groups includes <MAT> PRBs.

NSI bits of a field in UL CI (e.g., in DCI format 2_4) have one-to-one mapping with NSI groups of symbols where each of the first <MAT> groups includes <MAT> symbols and each of the remaining <MAT> groups includes <MAT> symbols. A UE does not expect NSI < NCI.

In yet another example, the base station <NUM> can instruct the UE <NUM> to reduce transmission power to zero on the entire originally allocated uplink transmission resources (e.g., the PUSCH <NUM>) or a portion thereof, to indirectly cancel the transmission on the entire originally allocated uplink transmission resource (e.g., the PUSCH <NUM>) or a portion thereof, respectively. Accordingly, in response to receiving transmission power reduction commands/signals from the base station <NUM>, the UE <NUM> cancels transmission on the entire originally allocated uplink transmission resource (e.g., the PUSCH <NUM>) or a portion thereof.

In some embodiments, the PUSCH (e.g., the PUSCH <NUM>) is an example of uplink transmission resources capable of carrying data for both low-priority services and high-priority services. A scheme similar to the scheme for canceling uplink transmission on the PUSCH <NUM> can be implemented for canceling one or more other types of uplink transmissions with lower priority such as but not limited to, those uplink transmissions on a physical uplink control channel (PUCCH), Sounding Reference Signal (SRS), Physical Random Access Channel (PRACH), and so on, due to preemption in favor of one or more other types of uplink transmissions with higher priority. The other types of uplink transmissions can be uplink transmissions communicated on the PUCCH, SRS, PRACH, and so on.

In other examples, slot format can be configured in different ways. For example, a base station can configure a semi-static slot format via suitable Radio Resource Control (RRC) signaling (e.g., TDD-UL-DL-ConfigCommon or TDD-UL-DL-ConfigDedicated). The TDD-UL-DL-ConfigCommon is a cell-specific parameter. The TDD-UL-DL-ConfigCommon parameter is adapted for and effective to all or a group of UEs in a same cell, such that all or a group of UEs in the same cell can configure the same slot format according to the same TDD-UL-DL-ConfigCommon parameter. TDD-UL-DL-ConfigDedicated is a UE-specific parameter. Different UEs can configure different slot formats according to different TDD-UL-DL-ConfigDedicated parameters.

Resource types in semi-static slot formats include semi-static downlink resources (e.g., semi-static downlink slots and/or symbols), semi-static flexible resources (semi-static flexible slots and/or symbols), and semi-static uplink resources (semi-static uplink slots and/or symbols). Semi-static flexible resource can be further configured by the base station as uplink resource or downlink resource by dynamic slot format configuration. In other words, uplink transmission (e.g., PUSCH) or downlink transmission (e.g., PDSCH) can be scheduled on the semi-static flexible resource. The UE still needs to monitor the PDCCH in the corresponding PDCCH monitoring occasions scheduled or located at the semi-static flexible resource.

In another examples, the base station can configure a dynamic slot format via PDCCH (e.g., in the DCI format <NUM>-<NUM>). Resource types in dynamic slot formats include dynamic downlink resources (e.g., dynamic downlink slots and/or symbols), dynamic flexible resources (e.g., dynamic flexible slots and/or symbols), and dynamic uplink resources (dynamic uplink slots and/or symbols). The UE does not need monitoring the PDCCH in the corresponding PDCCH monitoring occasions scheduled or located at the dynamic flexible resource.

The disclosed embodiments define a mechanism for the UE to determine the UL CI to monitor in connection with the slot format.

<FIG> is a schematic diagram illustrating a method <NUM> for determining a UL CI monitoring occasion, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the method <NUM> is performed by a UE. In some embodiments, a base station can configure a semi-static slot format <NUM> via suitable RRC signaling (e.g., TDD-UL-DL-ConfigCommon). As shown, the semi-static slot format <NUM> includes <NUM> slots <NUM>-<NUM> within a slot configuration period <NUM>. In other words, the slot configuration period <NUM> is divided (in the time domain, denoted by the horizontal axis as shown) into the slots <NUM>-<NUM>. The dimension or axis of <FIG> that is perpendicular to the time domain axis represents frequency such as but not limited to, a bandwidth, an active BWP, and so on. The resource types of the slots <NUM>-<NUM> are configured as "DDFFUUUUUU," where "D" denotes semi-static downlink slots <NUM> and <NUM>, "F" denotes semi-static flexible slots <NUM> and <NUM>, and "U" denotes semi-static uplink slots <NUM>-<NUM>.

In some examples, all symbols in each of the slots <NUM>-<NUM> have a unified type. For example, all symbols in the slots <NUM> and <NUM> are downlink symbols. All symbols in the slots <NUM> and <NUM> are flexible symbols. All symbols in the slots <NUM>-<NUM> are uplink symbols. In other examples, one or more of the slots <NUM>-<NUM> can each contain two or more types of symbols. That is, the symbols in a given slot can be configured as different symbol types. For example, some symbols in a slot are configured as one of downlink symbols, flexible symbols, and uplink symbols while other symbols in the same slot can be configured as other ones of the downlink symbols, flexible symbols, and uplink symbols.

The semi-static slot format <NUM> includes UL CI monitoring occasions denoted as CI1, CI2, CI3, and CI4. Each of the UL CI monitoring occasions CI1-CI4 corresponds to one or more symbols. Low-priority uplink transmission (e.g., PUSCH <NUM>) is scheduled via DCI (received from the base station) or configured via RRC signaling. As shown, the PUSCH <NUM> is scheduled in the semi-static uplink slot <NUM>.

The UE can monitor one or more of the UL CI monitoring occasions CI1-CI4 for the UL CI, which indicates whether the uplink transmission (e.g., the PUSCH <NUM>) is canceled. The UL CI monitoring occasions CI1-CI4 are all available monitoring occasions in the slot configuration period <NUM> for receiving the UL CI. The UE selects one of the UL CI monitoring occasions CI1-CI4 (referred to as a beginning UL CI monitoring occasion) to begin monitoring for the UL CI.

In some embodiments, the UE begins the monitoring in an UL CI monitoring occasion that is the latest UL CI monitoring occasion located in a downlink symbol (e.g., as indicated by the TDD-UL-DL-ConfigCommon) that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH <NUM>. The predetermined number of symbols (e.g., a predetermined time interval) corresponds to a UL CI processing time (e.g., a time interval needed by the UE to decode the UL CI and cancel the corresponding UL transmission). The predetermined time interval can be defined in the specification or can also be configured by the base station. In other words, the UE monitors the UL CI in one or more UL CI monitoring occasions including a beginning UL CI monitoring occasion and one or more UL CI monitoring occasions (if any) within the slot configuration period <NUM> that are after the beginning UL CI monitoring occasion.

The base station may not transmit the UL CI located at a semi-static flexible resource (e.g., the UL CI monitoring occasions CI3 and CI4 in the slots <NUM> and <NUM>, respectively) given that the semi-static flexible resource can be configured as uplink resource instead of a downlink resource. Accordingly, in some embodiments, the UL CI monitoring occasions CI3 and CI4 located in the flexible slots <NUM> and <NUM> cannot be the beginning UL CI monitoring occasion.

As shown, the ending positions of all of the UL CI monitoring occasions CI1-CI4 are no later than X symbols before the start of the UL transmission of the PUSCH <NUM>. In the examples in which the TDD-UL-DL-ConfigCommon indicates that the UL CI monitoring occasions CI1 and CI2 are located in downlink symbols, the UL CI monitoring occasion CI2 is the latest UL CI monitoring occasion in a downlink symbol. Accordingly, the UE determines that the UL CI monitoring occasion CI2 is the beginning UL CI monitoring occasion given that the UL CI monitoring occasion CI2 satisfies the conditions.

In some embodiments, the beginning UL CI monitoring occasion CI2 can indicate canceled transmissions on all of the semi-static flexible resources (e.g., slots <NUM> and <NUM>) and uplink resources (e.g., slots <NUM>-<NUM>) within the slot configuration period <NUM>.

Accordingly, the method <NUM> allow the UE to monitor a minimum number of UL CI occasions while not missing any UL CI.

In some embodiments, the base station can configure the semi-static slot format <NUM> via suitable RRC signaling. The RRC signaling includes TDD-UL-DL-ConfigCommon, the TDD-UL-DL-ConfigDedicated, or a combination thereof. That is, the semi-static slot format <NUM> can be configured according to both the TDD-UL-DL-ConfigCommon and the TDD-UL-DL-ConfigDedicated in some embodiments. For example, in some embodiments, the UE begins the monitoring in an UL CI monitoring occasion that is the latest UL CI monitoring occasion located in a downlink symbol (e.g., as indicated by the TDD-UL-DL-ConfigCommon and/or the TDD-UL-DL-ConfigDedicated) that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH <NUM>. In that regard, the UE can determine that the ending positions of all of the UL CI monitoring occasions CI1-CI4 are no later than X symbols before the start of the UL transmission of the PUSCH <NUM>. In the examples in which the TDD-UL-DL-ConfigCommon and/or the TDD-UL-DL-ConfigDedicated indicates that the UL CI monitoring occasions CI1 and CI2 are located in downlink symbols, the UL CI monitoring occasion CI2 is the latest UL CI monitoring occasion in a downlink symbol. Accordingly, the UE determines that the UL CI monitoring occasion CI2 is the beginning UL CI monitoring occasion.

In some embodiments, the UE begins the monitoring in an UL CI monitoring occasion that is the latest UL CI monitoring occasion that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH <NUM>. The beginning UL CI monitoring occasion is selected from the available UL CI monitoring occasions CI1-CI4 without considering the resource type for the beginning UL CI monitoring occasion. That is, the beginning UL CI monitoring occasion is selected without considering whether the beginning UL CI monitoring occasion is located in a downlink symbol. In that regard, as shown, the UE can determine that the ending positions of all of the available UL CI monitoring occasions CI1-CI4 are no later than X symbols before the start of the UL transmission of the PUSCH <NUM>. Accordingly, the UE determines that the UL CI monitoring occasion CI4, which can be in a flexible symbol, is the beginning UL CI monitoring occasion.

In this case, given that the UE does not monitor the UL CI monitoring occasions CI1-CI3, the base station is configured to send the UL CI on the UL CI monitoring occasion CI4 to ensure that the UE is notified of the cancelation of the uplink transmission. Therefore, in such embodiments, the network side cannot configure the flexible symbol corresponding to the UL CI monitoring occasion CI4 to be an uplink symbol and cannot schedule uplink transmission in the flexible symbol corresponding to the UL CI monitoring occasion CI4. In other words, the UE does not expect the flexible symbol corresponding to the monitoring occasion to be configured as an uplink symbol. The UE does not expect uplink transmission to be scheduled in the flexible symbol corresponding to the monitoring occasion, meaning that from the perspective of the UE, transmission other than uplink transmission can be scheduled in the flexible symbol corresponding to the monitoring occasion.

<FIG> is a schematic diagram illustrating a method <NUM> for determining a UL CI monitoring occasion, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the method <NUM> is performed by a UE. In some embodiments, a base station can configure a semi-static slot format <NUM> via suitable RRC signaling. The RRC signaling includes TDD-UL-DL-ConfigCommon, the TDD-UL-DL-ConfigDedicated, or a combination thereof. As shown, the semi-static slot format <NUM> includes <NUM> slots <NUM>-<NUM> within a slot configuration period <NUM>. In other words, the slot configuration period <NUM> is divided (in the time domain, denoted by the horizontal axis as shown) into the slots <NUM>-<NUM>. The dimension or axis of <FIG> that is perpendicular to the time domain axis represents frequency such as but not limited to, a bandwidth, an active BWP, and so on. The resource types of the slots <NUM>-<NUM> are configured as "DDFFUUUUUU," where "D" denotes semi-static downlink slots <NUM> and <NUM>, "F" denotes semi-static flexible slots <NUM> and <NUM>, and "U" denotes semi-static uplink slots <NUM>-<NUM>.

The semi-static slot format <NUM> includes UL CI monitoring occasions denoted as CI1, CI2, CI3, and CI4. Each of the UL CI monitoring occasions CI1-CI4 corresponds to one or more symbols. Low-priority uplink transmission (e.g., PUSCH <NUM>) is scheduled via a scheduling DCI <NUM>. The scheduling DCI <NUM> is received from the base station within the downlink slot <NUM>. As shown, the PUSCH <NUM> is scheduled in the semi-static uplink slot <NUM> according to the scheduling DCI <NUM>. A DCI processing time T corresponds to a time interval needed by the UE to decode the scheduling DCI <NUM>.

With reference to <FIG> and <FIG>, the UE can monitor one or more of the UL CI monitoring occasions CI1-CI4 for the UL CI, which indicates whether the uplink transmission (e.g., the PUSCH <NUM> or <NUM>) is canceled. The UL CI monitoring occasions CI1-CI4 are all available monitoring occasions in the slot configuration period <NUM> or <NUM> for receiving the UL CI. The UE selects one of the UL CI monitoring occasions CI1-CI4 (referred to as a beginning UL CI monitoring occasion) to begin monitoring for the UL CI. In other words, the UE monitors the UL CI in one or more UL CI monitoring occasions including a beginning UL CI monitoring occasion and one or more UL CI monitoring occasions (if any) within the slot configuration period <NUM> or <NUM> that are after the beginning UL CI monitoring occasion.

In some embodiments, the UE first determines whether any of the available UL CI monitoring occasions are in semi-static downlink symbols that are after the decoding of the scheduling DCI. For example, decoding of the scheduling DCI <NUM> ends at <NUM>. Decoding of the scheduling DCI <NUM> ends at <NUM>. That is, the UE first determines whether any of the available UL CI monitoring occasions in a semi-static downlink symbols has a start position that is after T after the end position of the scheduling DCI. In some embodiments, the semi-static downlink symbols are downlink symbols indicated by RRC signaling TDD-UL-DL-ConfigCommon. In other embodiments, the semi-static downlink symbols are downlink symbols indicated by RRC signaling TDD-UL-DL-ConfigCommon or TDD-UL-DL-ConfigDedicated.

In response to determining that at least one of the available UL CI monitoring occasions is in a semi-static downlink symbol that is after the decoding of the scheduling DCI, the UE begins the monitoring in an UL CI monitoring occasion that is the latest UL CI monitoring occasion located in a downlink symbol (e.g., as indicated by the TDD-UL-DL-ConfigCommon) that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH <NUM> or <NUM>. The predetermined number of symbols (e.g., a predetermined time interval) corresponds to a UL CI processing time (e.g., a time interval needed by the UE to decode UL CI and cancel the corresponding UL transmission). The predetermined time interval can be defined in the specification or can also be configured by base station.

On the other hand, in response to determining that none of the available UL CI monitoring occasions is in a semi-static downlink symbol that is after the decoding of the scheduling DCI, the UE begins the monitoring in an UL CI monitoring occasion that is the latest one of the available UL CI monitoring occasions that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH. In other words, the beginning UL CI monitoring occasion is selected from the available UL CI monitoring occasions CI1-CI4 without considering the resource type for the beginning UL CI monitoring occasion. That is, in response to determining that none of the available UL CI monitoring occasions is in a semi-static downlink symbol that is after decoding the scheduling DCI, the beginning UL CI monitoring occasion is selected without considering whether the beginning UL CI monitoring occasion is located in a downlink symbol.

As shown in <FIG>, decoding of the scheduling DCI <NUM> ends at <NUM>. In the embodiments in which none of the available UL CI monitoring occasions CI1-CI4 is in a semi-static downlink symbol that is after the decoding of the scheduling DCI <NUM> completes at <NUM>, the UE determines that the UL CI monitoring occasion CI4 is the latest one of the available UL CI monitoring occasions CI1-CI4 that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH <NUM>. Accordingly, the UE determines that the UL CI monitoring occasion CI4, which can be in a flexible symbol, is the beginning UL CI monitoring occasion.

In this case, given that the UE does not monitor the UL CI monitoring occasions CI1-CI3, the base station is configured to send the UL CI on the UL CI monitoring occasion CI4 to ensure that the UE is notified of the cancelation of the uplink transmission. Therefore, in such embodiments, the network side cannot configure the flexible symbol corresponding to the UL CI monitoring occasion CI4 to be an uplink symbol and cannot schedule uplink transmission in the flexible symbol corresponding to the UL CI monitoring occasion CI4.

A shown in <FIG>, decoding of the scheduling DCI <NUM> ends at <NUM>. The UL CI monitoring occasion CI2 is in a semi-static downlink symbol (in slot <NUM>) that is after the decoding of the scheduling DCI <NUM>. Accordingly, the UE begins the monitoring in the UL CI monitoring occasion CI2, which is the latest UL CI monitoring occasion (out of the available UL CI monitoring occasions CI1-CI4) that is located in a downlink symbol (e.g., as indicated by the TDD-UL-DL-ConfigCommon) that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before the start position of the uplink transmission of the PUSCH <NUM>. The predetermined number of symbols (e.g., a predetermined time interval) corresponds to a UL CI processing time (e.g., a time interval needed by the UE to decode the UL CI and cancel the corresponding UL transmission).

In some embodiments, the UE first determines whether any of the available UL CI monitoring occasions are in semi-static downlink symbols that are after the decoding of the scheduling DCI. That is, the UE first determines whether any of the available UL CI monitoring occasions in a semi-static downlink symbols has a start position that is after T after the end position of the scheduling DCI.

In response to determining that at least one of the available UL CI monitoring occasions is in a semi-static downlink symbol that is after the decoding of the scheduling DCI, the UE begins the monitoring in an UL CI monitoring occasion (e.g., the UL CI monitoring occasion CI2 in <FIG>) that is the latest UL CI monitoring occasion located in a downlink symbol (e.g., as indicated by the TDD-UL-DL-ConfigCommon) that ends (e.g., having an end position that is) no later than a predetermined number (e.g., X) of symbols before a start position of the uplink transmission of the PUSCH.

On the other hand, in response to determining that none of the available UL CI monitoring occasions is in a semi-static downlink symbol that is after the decoding of the scheduling DCI <NUM>, the UE begins the monitoring in an UL CI monitoring occasion that is the earliest one of the available UL CI monitoring occasions that starts after the decoding of the scheduling DCI <NUM>.

As shown in <FIG>, decoding of the scheduling DCI <NUM> ends at <NUM>. In the embodiments in which none of the available UL CI monitoring occasions CI1-CI4 is in a semi-static downlink symbol that is after the decoding of the scheduling DCI <NUM> completes at <NUM>, the UE determines that the UL CI monitoring occasion CI3 is the earliest one of the available UL CI monitoring occasions CI1-CI4 that starts (e.g., having a start position that is) after the decoding of the scheduling DCI <NUM> completes at <NUM>. Accordingly, the UE determines that the UL CI monitoring occasion CI3, which can be in a flexible symbol, is the beginning UL CI monitoring occasion.

In this case, given that the UE does not monitor the UL CI monitoring occasions CI1-CI2, the base station is configured to send the UL CI on one or both of the UL CI monitoring occasion CI3 or CI4 to ensure that the UE is notified of the cancelation of the uplink transmission. Therefore, in such embodiments, the network side cannot configure the flexible symbol corresponding to one or both of the UL CI monitoring occasion CI3 or CI4 to be an uplink symbol and cannot schedule uplink transmission in the flexible symbol corresponding to one or both of the UL CI monitoring occasion CI3 or CI4.

In some embodiments, enabling indicator can be introduced to indicate whether to use one of the mechanisms (described herein with reference to <FIG>) the UE needs to adopt for determining the beginning UL CI monitoring occasion to be monitored. In some examples, the network side (including the base station) can send the enabling indicator to the UE in a system broadcast message(e.g. in system information block <NUM>) or UE-specific RRC signaling. In response to receiving the enabling indicator which indicates one of the mechanisms described herein is enabled (e.g., on the network side), the UE determines the beginning UL CI monitoring occasion to be monitored using that mechanism. Accordingly, both the terminal side and the network side are in agreement as to the mechanism used to determine the beginning UL CI monitoring occasion. The UE does not monitor any of the UL CI monitoring occasions before the beginning UL CI monitoring occasion.

In some embodiments, if the mechanism is not enabled, the behavior of the UE to monitor the UL CI is not limited. In some examples, the UE monitors the UL CI monitoring occasions that are after the PDCCH on which the PUSCH is scheduled is decoded. Alternatively, in some examples, the UE monitors all UL CI monitoring occasions corresponding to a RUR where the PUSCH is located.

<FIG> is a flowchart diagram illustrating an example method <NUM> for monitoring UL CI, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the methods <NUM>-<NUM> can be particular implementations of the method <NUM>. The method <NUM> can be performed on a UE.

At <NUM>, the UE determines a monitoring occasion (e.g., an UL CI monitoring occasion) for monitoring UL CI indicating that uplink transmission on an uplink resource is canceled. An end position of the monitoring occasion is no later than a predetermined time interval before a start position of the uplink transmission. The predetermined time interval corresponds to a time interval needed by the UE to process the UL CI.

In some embodiments, the monitoring occasion is configured to be in a downlink symbol according to RRC signaling. In some examples, the RRC signaling includes a cell-specific parameter that configures a same slot format for a plurality of UEs in a same cell. The plurality of UEs includes the UE. For instance, the RRC signaling includes TDD-UL-DL-ConfigCommon. In some examples, the RRC signaling includes a UE-specific parameter that configures a slot format for the UE. For instance, the RRC signaling includes TDD-UL-DL-ConfigDedicated.

In some embodiments, a plurality of monitoring occasions is in downlink symbols. The monitoring occasion is the latest one of the plurality of monitoring occasions that ends no later than the predetermined time interval before the start position of the uplink resource. In some embodiments, the UL CI indicates canceled transmissions on all flexible slots and uplink slots within a slot configuration period.

In some embodiments, the monitoring occasion is configured to be in a downlink symbol according to RRC signaling. In some embodiments, the monitoring occasion is configured to be in a flexible symbol according to RRC signaling.

In some embodiments, the UE does not expect the flexible symbol corresponding to the monitoring occasion to be configured as an uplink symbol. The UE does not expect to be scheduled uplink transmission in the flexible symbol corresponding to the monitoring occasion.

In some embodiments, determining the monitoring occasion by the UE includes receiving by the UE from a base station, a scheduling DCI and determining, by the UE, whether at least one of a plurality of available monitoring occasions is in a semi-static downlink symbol that is after decoding of the scheduling DCI. In some examples, in response to determining that at least one of the plurality of available monitoring occasions is in the semi-static downlink symbol that is after the decoding of the scheduling DCI, the monitoring occasion is determined to be the latest one of the at least one of the plurality of monitoring occasions in the semi-static downlink symbol that ends no later than the predetermined time interval before the start position of the uplink resource.

In some examples, in response to determining that none of the plurality of available monitoring occasions is in the semi-static downlink symbol that is after the decoding of the scheduling DCI, the monitoring occasion is determined to be the latest one of the plurality of available monitoring occasions that ends no later than a predetermined time interval before the start position of the uplink resource. In other examples, in response to determining that none of the plurality of available monitoring occasions is in the semi-static downlink symbol that is after the decoding of the scheduling DCI, the monitoring occasion is determined to be the earliest one of the plurality of available monitoring occasions that starts after the decoding of the scheduling DCI.

In some embodiments, the UE receives from a base station enabling indicator indicating whether one of a plurality of mechanisms is used to determine the monitoring occasion. The enabling indicator is transmitted via a RRC signaling.

At <NUM>, the UE monitors the UL CI in at least the monitoring occasion.

In some embodiments, the UL CI corresponds to a reference uplink time-frequency resource region (e.g., the RUR). In particular, the UL CI is used to indicate or otherwise identify a canceled uplink resource (e.g., PUSCH) within the RUR corresponding to the UL CI. Some embodiments relate to methods for configuring a location of the RUR time-frequency resource.

The location of the canceled RUR time-frequency resource can be determined based on at least one of a time-domain starting point of the RUR, a time-domain duration of the RUR, and a frequency-domain range of the RUR.

With regard to the time-domain starting point of the RUR, the RUR starts from a number of symbols after an ending symbol of the PDCCH CORESET which carries the UL CI. The number of symbols corresponds to a minimum processing time for UL cancelation (canceling the uplink transmission). The minimum processing time for the uplink cancelation depends on subcarrier spacing. For example, for a subcarrier spacing of <NUM>, the minimum processing time is equal to <NUM> symbols at <NUM>. For subcarrier spacing of <NUM>, the minimum processing time is equal to <NUM> symbols at <NUM>, and so on. Therefore, in response to the UE detecting the UL CI, the UE determines the time-domain starting point of the corresponding RUR based on the subcarrier spacing. The subcarrier spacing can be one of the subcarrier spacing of the ULCI, determined based on frequency range (FR) (e.g., the subcarrier spacing is <NUM> for FR1, <NUM> for FR2, and so on), the minimum of the subcarrier spacing of the UL CI and the subcarrier spacing of the PUSCH (e.g., the canceled resource) of the UE, or the subcarrier spacing configured by the base station.

With regard to the time-domain duration of the RUR, the base station configures a number of symbols, types of symbols, and so on included in the RUR as RRC layer parameters. The UE determines the time domain duration of the RUR based on the specified subcarrier spacing. The subcarrier spacing can be one of the subcarrier spacing of the ULCI, determined based on FR, the minimum of the subcarrier spacing of the UL CI and the subcarrier spacing of the PUSCH of the UE, or the subcarrier spacing configured by the base station.

With regard to the frequency-domain range of the RUR, the base station configures a frequency-domain start point of the RUR and a number of radio bearers (RBs) included in the RUR via RRC parameter. The frequency-domain start point and the number of RBs can be defined as independent parameters and indicated/signaled separately, in some examples. In other examples, the frequency-domain start point and the number of RBs can be defined as a joint parameter.

The frequency-domain start point can be defined as a frequency-domain offset from a frequency-domain reference point. In one example, the frequency-domain reference point is defined as point A, which is the frequency-domain center point of subcarrier <NUM> of RB0 for all subcarrier spacing within the carrier. Alternatively, the frequency-domain reference point is defined as the lowest usable subcarrier of subcarrier spacing <NUM>.

The number of RBs can be determined based on the subcarrier spacing <NUM>. The subcarrier spacing <NUM> and the subcarrier spacing <NUM> can each be determined by determining the subcarrier spacing of the ULCI, in some examples. In some examples, the subcarrier spacing <NUM> and the subcarrier spacing <NUM> can each be determined based on FR. In some examples, the subcarrier spacing <NUM> and the subcarrier spacing <NUM> can each be the minimum of the subcarrier spacing of the UL CI and the subcarrier spacing of the PUSCH of the UE. In some examples, the subcarrier spacing <NUM> and the subcarrier spacing <NUM> can each be configured by the base station.

In that regard, <FIG> is a flowchart diagram illustrating an example method <NUM> for determining a location of canceled uplink resource.

Referring to <FIG>, the method <NUM> is performed by the UE.

At <NUM>, a UE detects UL CI indicating that uplink transmission on an uplink resource within a RUR is canceled. At <NUM>, the UE determines the RUR based on at least one of a time-domain starting point of the RUR, a time-domain duration of the RUR, or a frequency-domain range of the RUR.

In some embodiments, each of the time-domain starting point of the RUR, the time-domain duration of the RUR, and the frequency-domain range of the RUR is determined based on subcarrier spacing. The subcarrier spacing can be one of a subcarrier spacing of the UL CI, determined based on FR, a minimum of the subcarrier spacing of the UL CI and a subcarrier spacing of the canceled uplink transmission, or a subcarrier spacing configured by a base station.

In <NUM> systems, repetition transmissions have been introduced for coverage enhancement and transmitting ultra-low latency and high-reliability service within a short time interval. In Release <NUM> Specification, slot-based repetitions have been defined. For example, a same TB is transmitted in multiple slots repeatedly. The TB can be transmitted once in one slot, and a same time domain resource assignment can be used for the TB transmission in each slot of the multiple slots.

For further improving performance of ultra-low latency and high-reliability services, further enhancement on repetition of one TB transmission will be done in Release <NUM> Specification, introducing mini-slot based repetition. That is, there can be one or more repetitions of a same TB within one slot. In some examples, one TB is transmitted repeatedly in several consecutive slots in a slot-boundary crossing manner.

In some embodiments, the serving node can indicate to the UE to transmit physical channel using one of two transmission modes. Taking PUSCH as an example, the first transmission mode is the transmission mode defined in Release <NUM>, e.g., repetition transmission with granularity of slot. Then, slot-based aggregation can be implemented in dynamic grant cases, or slot-based repetition can be implemented in configured grant cases. The second transmission mode is the transmission mode defined in Release <NUM>, e.g., repetition transmission of dynamic grant PUSCH or configured grant PUSCH with granularity of mini-slot. More specifically, the scheduling information of PUSCH is indicated by DCI in dynamic grant cases. The configured grant PUSCH can be further divided into two types. For Type <NUM> PUSCH, the scheduling information of PUSCH is indicted via RRC signaling. For Type <NUM> PUSCH, the scheduling information of PUSCH is indicated in the activate DCI.

In some embodiments, same information of time domain resource assignment (TDRA) can be shared by the two transmission modes described herein, e.g., the two transmission modes can correspond to a TDRA table. The TDRA table is showed in Table <NUM>, including PUSCH mapping type, K2, Start and Length Indicator Value (SLIV), values of S and L, repetition number, and so on.

More specifically, PUSCH mapping type contains PUSCH mapping type A and PUSCH mapping type B. A difference between the two mapping types is different requirement of starting symbol position and length of time domain duration. Mini-slot repetition transmission is not supported in PUSCH mapping type A. K2 is slot offset between scheduling DCI and corresponding PUSCH. SLIV is an indicator of start symbol and number of symbols. The UE can determine a start symbol index and a number of symbols of PUSCH from the SLIV indication. S and L represent start symbol and number of symbols, respectively, and S+L can be larger than <NUM>. The repetition number represents a number of PUSCH repetition transmissions. In some embodiments, the TDRA table is configured by a high layer. The specific time-domain scheduling information is indicated by RRC signaling or one entry indicated by DCI from the TDRA table. Another indication field can also be included in TDRA table as configured by high layer.

to the present embodiment allow determination of the time-domain allocation information of the repetition transmission PUSCH corresponding to different transmission modes according to a TDRA table by the UE.

In response to the second transmission mode being indicated to a UE, the mapping type of PUSCH transmission is determined according to at least one of the following methods:.

When the second transmission mode is indicated to a UE, the time domain position of PUSCH is determined according to at least one of the following methods:
Method <NUM>: in response to determining that the SLIV in the TDRA information in the PUSCH scheduling information received by a UE is an invalid value, the UE determines the time-domain position of PUSCH according to the values of S and L.

In some examples, the invalid value of the SLIV refers to a value beyond the valid range of the SLIV or a value that equals to a specific value.

Method <NUM>: in response to determining that the S and/or L in the TDRA information in the PUSCH scheduling information received by a UE is not configured, the UE determines the time-domain position of PUSCH according to SLIV.

Method <NUM>: in response to determining that the S and/or L in the TDRA information in the PUSCH scheduling information received by a UE is an invalid value, the UE determines the time-domain position of PUSCH according to SLIV.

In some embodiments, the invalid values of the S and L refer to values beyond the valid range of the S and L or values that equal to specific values.

Method <NUM>: for the second transmission mode, in response to a UE receiving the PUSCH scheduling information in which the S and L in the TDRA information are configured with valid values and the SLIV in the TDRA information is configured with a valid value, the UE determines the time domain position of PUSCH according to SLIV. Alternatively, the UE determines the time-domain position of PUSCH according to the values of S and L.

Upon the first transmission mode being indicated to a UE, the time-domain position of PUSCH is determined by the UE according to at least one of the following methods:
Method <NUM>: in response to determining that the SLIV in the TDRA information in the PUSCH scheduling information received by a UE is not configured or the configured value is invalid, the UE determines the time-domain position of PUSCH according to S and L.

Further, a UE does not expect that a sum of S and L indicated in the TDRA information in the PUSCH scheduling information received is greater than <NUM>.

In some embodiments, the sum of S and L indicated in the TDRA information in the PUSCH scheduling information notified by a network node is no larger than <NUM>.

In some embodiments, in response to determining that the sum of S and L indicated in the TDRA information in the PUSCH scheduling information received by a UE is greater than <NUM>, the UE transmits PUSCH according to the sum of S and L less than or equal to <NUM>.

Further, the invalid value of the SLIV refers to a value beyond the valid range of the SLIV or a value that equals to a specific value.

While the present embodiments are described with reference to uplink PUSCH as an example, the repetition transmission information can also be carried in PDSCH, PDCCH, and so on.

<FIG> illustrates a block diagram of an example base station <NUM>, in accordance with some embodiments of the present disclosure. <FIG> illustrates a block diagram of an example UE <NUM>, in accordance with some embodiments of the present disclosure. Referring to <FIG>, the UE <NUM> (e.g., a wireless communication device, a terminal, a mobile device, a mobile user, and so on) is an example implementation of the UEs described herein, and the base station <NUM> is an example implementation of the base station described herein.

The base station <NUM> and the UE <NUM> can include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the base station <NUM> and the UE <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, as described above. For instance, the base station <NUM> can be a base station (e.g., gNB, eNB, and so on), a server, a node, or any suitable computing device used to implement various network functions.

The base station <NUM> includes a transceiver module <NUM>, an antenna <NUM>, a processor module <NUM>, a memory module <NUM>, and a network communication module <NUM>. The module <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are operatively coupled to and interconnected with one another via a data communication bus <NUM>. The UE <NUM> includes a UE transceiver module <NUM>, a UE antenna <NUM>, a UE memory module <NUM>, and a UE processor module <NUM>. The modules <NUM>, <NUM>, <NUM>, and <NUM> are operatively coupled to and interconnected with one another via a data communication bus <NUM>. The base station <NUM> communicates with the UE <NUM> or another base station via a communication channel, which can be any wireless channel or other medium suitable for transmission of data as described herein.

As would be understood by persons of ordinary skill in the art, the base station <NUM> and the UE <NUM> can further include any number of modules other than the modules shown in <FIG>. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. The embodiments described herein can be implemented in a suitable manner for each particular application, but any implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some embodiments, the UE transceiver <NUM> includes a radio frequency (RF) transmitter and a RF receiver each including circuitry that is coupled to the antenna <NUM>. A duplex switch (not shown) may alternatively couple the RF transmitter or receiver to the antenna in time duplex fashion. Similarly, in accordance with some embodiments, the transceiver <NUM> includes an RF transmitter and a RF receiver each having circuity that is coupled to the antenna <NUM> or the antenna of another base station. A duplex switch may alternatively couple the RF transmitter or receiver to the antenna <NUM> in time duplex fashion. The operations of the two transceiver modules <NUM> and <NUM> can be coordinated in time such that the receiver circuitry is coupled to the antenna <NUM> for reception of transmissions over a wireless transmission link at the same time that the transmitter is coupled to the antenna <NUM>.

The UE transceiver <NUM> and the transceiver <NUM> are configured to communicate via the wireless data communication link, and cooperate with a suitably configured RF antenna arrangement <NUM>/<NUM> that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver <NUM> and the transceiver <NUM> are configured to support industry standards such as the Long Term Evolution (LTE) and emerging <NUM> standards, and the like.

The transceiver <NUM> and the transceiver of another base station (such as but not limited to, the transceiver <NUM>) are configured to communicate via a wireless data communication link, and cooperate with a suitably configured RF antenna arrangement that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver <NUM> and the transceiver of another base station are configured to support industry standards such as the LTE and emerging <NUM> standards, and the like. Rather, the transceiver <NUM> and the transceiver of another base station may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various embodiments, the base station <NUM> may be a base station such as but not limited to, an eNB, a serving eNB, a target eNB, a femto station, or a pico station, for example. The base station <NUM> can be an RN, a regular , a DeNB, a gNB, or an IAB donor.

Furthermore, the method or algorithm disclosed herein can be embodied directly in hardware, in firmware, in a software module executed by processor modules <NUM> and <NUM>, respectively, or in any practical combination thereof.

The network communication module <NUM> generally represents the hardware, software, firmware, processing logic, and/or other components of the base station <NUM> that enable bidirectional communication between the transceiver <NUM> and other network components and communication nodes in communication with the base station <NUM>. For example, the network communication module <NUM> may be configured to support internet or WiMAX traffic. In a deployment, without limitation, the network communication module <NUM> provides an <NUM> Ethernet interface such that the transceiver <NUM> can communicate with a conventional Ethernet based computer network. In some embodiments in which the base station <NUM> is an IAB donor, the network communication module <NUM> includes a fiber transport connection configured to connect the base station <NUM> to a core network.

Claim 1:
A wireless communication method, comprising:
determining, by a wireless communication device, a monitoring occasion for monitoring uplink cancelation indication, UL CI, indicating that uplink transmission on an uplink resource is canceled, wherein an end position of the monitoring occasion is no later than a predetermined time interval before a start position of the uplink transmission; and
monitoring, by the wireless communication device, the UL CI in at least the monitoring occasion, wherein:
a plurality of monitoring occasions are in downlink symbols; and
the monitoring occasion is a latest one of the plurality of monitoring occasions that ends no later than the predetermined time interval before the start position of the uplink resource,
wherein the predetermined time interval corresponds to a time interval needed by the wireless communication device to process the UL CI that indicates canceled transmissions on all flexible slots and uplink slots within a slot configuration period.