Downlink Control Channel Signaling for Uplink Coexistence of Multiple Service Types

Abstract

The present invention provides a system, apparatus, method, and computer-readable medium for causing a user equipment (UE) device to perform the following operations: receive configuration signaling to monitor for an uplink (UL) cancellation indication; monitor a search space for the UL cancellation indication; detect the UL cancellation indication in the search space; and in response, cancel at least a portion of a scheduled UL transmission.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 717,668, filed on August 10, 2018, entitled "DOWNLINK CONTROL CHANNEL SIGNALING FOR UL COEXISTANCE OF MULTIPLE SERVICE TYPES", U.S. Provisional Patent Application No. 62 / 739,073, filed on September 28, 2018, entitled "DOWNLINK CONTROL CHANNEL SIGNALING FOR UL COEXISTANCE OF MULTIPLE SERVICE TYPES", and U.S. Provisional Patent Application No. 62 / 828,383, filed on April 2, 2019, entitled "SYSTEM AND METHOD OF DOWNLINK CONTROL CHANNEL SIGNALING FOR UL COEXISTANCE OF MULTIPLE SERVICE TYPES", the disclosures of which are hereby incorporated by reference in their entireties for all purposes. BACKGROUND OF THE DISCLOSURE

[0003] Various examples generally relate to the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 An exemplary user equipment device including a cancellation circuit is depicted in accordance with some examples.

[0005] Figure 2 An exemplary timeline of UL cancellation is depicted in accordance with some examples.

[0006] Figure 3 An exemplary search space having a mode for monitoring UL cancellation or rescheduling is depicted in accordance with some examples.

[0007] Figure 4 A flowchart of an exemplary method for canceling UL transmissions is shown in accordance with some examples.

[0008] Figure 5 A flowchart of an exemplary method for controlling the power of UL transmissions is shown in accordance with some examples. DETAILED DESCRIPTION

[0009] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, for purposes of illustration and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, technologies, etc., in order to provide a thorough understanding of various aspects of the examples. However, it will be apparent to those skilled in the art who have benefited from the present disclosure that various aspects of the examples may be practiced in other examples that depart from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various examples with unnecessary detail. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B).

[0010] The NR system will support the coexistence of various services and traffic communications in the common carrier. Since different services have different requirements and characteristics, it is necessary to study multiplexing techniques so that the impact on the packet transmission of each service type is minimized.

[0011] The present disclosure relates to UL multiplexing of transmissions with different reliability and / or latency requirements. Specifically, how can one or more indications of affected resources be sent to one or more UEs so that ongoing or upcoming UL transmissions can be adjusted to avoid adversely affecting other UL transmissions that may occur in the shared resources. The transmission of one service type may be more urgent than that of another service type and may take precedence over other ongoing transmissions.

[0012] Examples herein provide several UE-specific indication mechanisms such that one or more UL transmissions can be performed in the shared resources in an orthogonal or non-orthogonal manner. Orthogonal transmission refers to the case when multiple transmissions are performed in overlapping time-frequency code resources. With non-orthogonal transmission, it is assumed that at least one of the time resource, frequency resource, and code can overlap or be shared among multiple transmissions.

[0013] Examples include UE-specific control channel signaling, particularly DCI format content design and configuration, to convey UL transmission cancellation indications to the UE. Examples also include mechanisms for triggering the UE based on the active BW part using power control parameters. Examples also include UL authorization using a configured RNTI, where one or more transmission parameters can be implicitly obtained based on the detected RNTI.

[0014] Unless otherwise mentioned, the durations mentioned below can be one or more time slots, one or more symbols, or a combination thereof. UL coexistence can occur in licensed and unlicensed bands below or above 6 GHz, in FDD and TDD systems, and in any bandwidth part of a given parameter set, such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, etc. Note that the UL transmission cancellation indication can alternatively be referred to as the UL transmission interruption indication or the UL transmission preemption indication. A CORESET refers to a DL control resource set, which can include a set of contiguous / non-contiguous PRBs and a set of symbols, and the CORESET includes one or more search spaces where DL control channel signaling such as the UL transmission cancellation indication or the UL grant can be monitored / detected.

[0015] Although UE-specific indications are used in the examples, similar PDCCH monitoring behaviors and search space set configurations can also be used for group common indications. For example, the UL cancellation indication can be a group common indication in DCI (e.g., in PDCCH) or using a sequence.

[0016] Indication of UL transmission cancellation

[0017] Figure 1 An exemplary UE 105 including a cancellation circuit 110 and a monitoring circuit 120 is shown. The cancellation circuit 110 is configured to cancel a scheduled UL transmission in response to a UL cancellation indication, as will be described below. The monitoring circuit 120 is configured to monitor for cancellation indications in a specific search space, as will be described below.

[0018] Before receiving a UL grant for PUSCH transmission, the UE may not need to monitor any UL cancellation indications. The UE can be configured to monitor one or more UL grant cancellation indications when a UL grant is successfully detected. Below, examples for the activation, configuration, and content design of such transmission cancellation indications are provided. The following examples are provided in the context of PUSCH transmission cancellation. However, after triggering the UE for such transmission, similar considerations can be made semi-statically, dynamically, or through a combination of such signaling for other ongoing or upcoming UL transmissions, such as PUCCH, PRACH, and SRS.

[0019] Monitoring the activation of UL cancellation indication

[0020] In one example, the UE is configured by RRC signaling to monitor the UL transmission cancellation indication (UL_CI). Specifically, after the UE receives an authorization (e.g., successful decoding of DCI), the monitoring of UL preemption or cancellation indication can be activated using the higher layer parameter UL_CI = ON or OFF. If the cancellation indication is for other UL transmissions, such as PUCCH, PRACH, and SRS, the UE can monitor the UL CI at the configured location after the higher layer parameter triggers the activation of monitoring, e.g., UL_CI = ON. The higher layer parameters providing the trigger for the possible need to monitor the CI can be obtained via one or more of the configuration of the UL BW part for PUSCH transmission, the configuration of the DL BW part for the PDCCH transmission carrying the UL CI, the PUSCH configuration for a given UE, and the common PUSCH configuration in a component carrier. Such characterization may need to consider the UE processing time (i.e., DCI decoding time), e.g., N2 is the number of OFDM symbols required for UE processing from the end of the PDCCH containing the UL authorization to the earliest possible start of the corresponding PUSCH transmission from the UE perspective. In another example, the UL authorization in the PDCCH may include a field for triggering the monitoring of the UL transmission cancellation indication. Specifically, a bit field in the PDCCH containing the UL authorization can be 1 or 0 (or vice versa) to indicate the monitoring or non-monitoring of the PI for UL by the UE. The PI (i.e., preemption indication) can be used interchangeably with the CI in this disclosure.

[0021] Monitoring cancellation indication

[0022] In the first stage, the UE receives the UL authorization. In the second stage, the UE monitors one or more UL_CIs. In this example, the monitoring of UL_CI is triggered after the authorization indicating the PUSCH. The UL_CI can be received in the DCI in the UE-specific PDCCH or only in the UE-specific PDCCH.

[0023] In one example, the monitoring of UL_CI can be performed on a window after the UL authorization. The window can include M≥1 monitoring opportunities for the UL_CI. The position of the first opportunity can be obtained as an offset from the position where the UL authorization is received. A parameter T5 can be identified, which can be measured in symbols or time slots or a combination of a given parameter set that indicates the position of the first monitoring opportunity of the UL_CI as an offset from a known reference point, which can be the start or end of the CORESET where the UL authorization is detected, or an offset from the boundary of the time slot where the UL authorization is detected. In Figure 2 , the parameter T5 is measured from the end of the CORESET where the UL authorization is received to the start of the CORESET where the first UL_CI is monitored. In one example, T5 can be indicated as (number of time slots – 1)*N 符号The starting symbol in a + slot, where the number of slots is counted starting from the position where the UL grant is received, and the starting symbol is the position where the first symbol of the CORESET for monitoring UL_CI is located. One or more parameters related to the indication of T5, such as the number of slots offset from the position where the UL grant is detected or the starting / first symbol of the CORESET for monitoring the first UL_CI, may be included in the UL grant and / or the higher layer configuration. N here 符号 represents the number of symbols in a slot for a given parameter set, and can be 14 for NCP and 12 for ECP.

[0024] In one example, UL_CI is monitored periodically after the first monitoring occasion of UL_CI. The periodicity can be configured as part of the configuration of the search space for monitoring UL CI. A parameter T3 can be identified, which can be used as the monitoring period for consecutive occasions of monitoring UL_CI. For a given parameter set, T3 can be measured in symbols or slots or a combination thereof. The parameter T3 can be configured by the higher layer, or can be implicitly obtained based on the time gap between the end of the UL grant and the end of the scheduled PUSCH or the duration of the scheduled PUSCH.

[0025] In another example, the parameter M can be configured by the higher layer, or can be implicitly derived from the time gap between the end of the UL grant and the end of the scheduled PUSCH or from the duration of the scheduled PUSCH.

[0026] The UE that can receive UL_CI can be indicated with a longer transmission duration of the PUSCH. For example, a UE that receives a transmission with a specific PUSCH mapping type (e.g., mapping type A in the specification), where the starting symbol is symbol index 0 in a slot, and the length of the PUSCH is at least 4 symbols and at most 14 symbols. More generally, if, for example, configured by higher layer signaling, a UE with a PUSCH duration longer than J symbols can monitor UL_CI after the UL grant, where J can be an integer, J = {2, 3, 4, 5, 6, 7, 8, 9, 10, 12, 13, 14}. In one example, a time partition of the PUSCH duration can be obtained (e.g., L ≥ 1 time parts), and one UL_CI can address one time partition of the PUSCH. The UL_CI that addresses the time partition can indicate all or a part of the scheduled resources within the time partition to be cancelled. In one example, each time partition can be further divided in frequency, e.g., J ≥ 1 frequency parts, i.e., the PUSCH BW can be divided into J parts for each time partition. The frequency parts can be counted from the top or bottom of the PUSCH BW. If each UL_CI is detected, the UE is notified to cancel all or a part of the time part.

[0027] In Figure 2 , the UE receives a UL grant that indicates that the PUSCH will start after time T1 from the location where the UL grant is received. In this figure, T1 is measured from the end of the CORESET where the UL grant is detected to the start of the PUSCH. Alternatively, T1 can be measured as (number of slots – 1)*N 符号 + starting symbol in the slot, where the number of slots is counted from the location where the UL grant is received, and the starting symbol is the first symbol of the PUSCH. For the latter example, the slot offset of the PUSCH and / or the number of starting symbols can be dynamically indicated in the UL grant or in the higher layers configured. If configured or indicated, the UE starts monitoring UL_CI after a duration of T5 after detecting the UL grant. The PUSCH duration is divided into L = 3 parts. The UE monitors UL_CI at M = L = 3 occasions. The periodicity of monitoring UL_CI is T3. The application time after detecting UL_CI is identified as T2. T2 can be the same as, greater than, or less than the UE processing capabilities N1 or N2 identified in the R15 specification. In the example considered, UL_CI is detected at the first occasion that triggers the UE to cancel the transmission at the first time of the allocated resources of the PUSCH. UL_CI not being present means that the UE can continue the PUSCH transmission in the remaining time parts. In one example, the UE also discards the remaining part of the PUSCH, i.e., once the UL CI is received, the UE starts discarding the PUSCH from the affected area indicated by the UL CI.

[0028] In one example, the duration of each time part T4 can be equal to or different from the monitoring period T3.

[0029] In one example, the parameter T5 can be implicitly obtained from the parameter T1 or one or more parameters that define T1, such as the number of slots of the slot offset where the UL grant is received (which is identified as the K2 value in the specification). In one example, each of the parameters T1, T2, T3, T5 can be equal to or greater than the minimum UE processing time of the PUSCH preparation process, i.e., can be limited by the UE capabilities.

[0030] In one example, UL_CI can be monitored in a UE-specific or group-common search space associated with one or more CORESETs. The monitoring periodicity, the offset of monitoring UL_CI, etc. can be configured as part of one or more search spaces associated with one or more CORESETs in a given DL BWP. However, the monitoring is only effective when the UE has an upcoming or ongoing UL transmission. UL_CI can be monitored at K => 1 aggregation levels. In one example, as part of the higher layer parameter search space configuration, the UE can be configured for UL_CI as follows:

[0031] ·Associate the DCI format with the search space based on whether the DCI format is a UE-specific search space or a common search space. If it is UE-specific to the search space, the higher layer parameter USS-DCI-Format indicates monitoring of the PDCCH containing the given DCI format with UL_CI. If a common search space is used, the higher layer parameter RNTI-Monitoring may indicate monitoring of the PDCCH with the RNTI for the DCI format containing UL_CI.

[0032] ·According to the number of PDCCH candidates at the supported aggregation levels

[0033] ·Periodicity in PDCCH monitoring symbols or time slots or a combination thereof (e.g., T3)

[0034] ·Offset in PDCCH monitoring symbols or time slots or a combination thereof (e.g., T5 or the number of time slots in the calculation of T5, see the example mentioned above regarding the calculation of T5)

[0035] ·PDCCH monitoring pattern within a time slot, e.g., the position of the first symbol of the CORESET within the time slot for monitoring (e.g., can be used to identify the starting symbol of the CORESET in the calculation of T5, see the example mentioned above for the calculation of T5)

[0036] Note that the monitoring of UL_CI is triggered based on events (such as if the UE receives a UL grant). Thus, although in one example, the monitoring configuration can be obtained as part of the search space configuration associated with one or more CORESETs in the DL BWP, the UE does not always monitor actively based on the parameters. For example, the PDCCH monitoring offset in the configuration of UL_CI can be separate from other PDCCHs monitored in the search space. In the context of PDCCH, the monitoring offset can indicate the time offset between the reception of a UL grant and the start of the CORESET monitoring UL_CI, e.g., Figure 2 T5 in. In one example, the offset only indicates the number of time slots from the position where the UL grant is received, and if the starting symbol of the CORESET containing UL_CI is not symbol #0 in the time slot, the PDCCH monitoring pattern within the time slot can be used to identify the position of the first symbol of the CORESET where UL_CI is monitored

[0037] In one example, the UE can monitor UL_CI with a CORESET that is the same as or different from the CORESET in which it receives the scheduling transmission's UL grant.

[0038] In one example, the scheduled PUSCH duration may include one or more repetitions. An implicit way to trigger the UE to monitor UL_CI is whether the number of repetitions K exceeds a given / configured value. For example, if K is equal to or greater than 2, the UE may monitor UL_CI.

[0039] The above monitoring configuration applies to any DCI format that includes UL_CI.

[0040] DCI format example

[0041] In one example, UE-specific DCI scrambled by C-RNTI or another configured RNTI can be used for DCI formats that include UL_CI. In one example, one or more reserved fields can be used for UL authorization, such as in DCI format 0_0 or 0_1, which can be used for UL_CI. For example, a one-bit field can be used, which, if it is 1 (or vice versa), can indicate that a certain time-frequency portion or all of the PUSCH needs to be cancelled by the UE. Thus, if this bit field contains a given value that triggers cancellation, one or more of the remaining fields in the DCI format may be invalid. For example, such a DCI format may not allocate any resource allocation. For example, in Figure 2 the context of each in the L portion, the UE monitors the UL authorization to see if the bit value in the field indicates cancellation. J portions of the PUSCH can be configured in frequency to facilitate partial cancellation of the PUSCH in the frequency domain.

[0042] In another example, the DCI format for UL_CI is scrambled with an RNTI different from the RNTI used for UL authorization. The UE can monitor UL authorization or any other DCI format, such as a compact DCI format with an RNTI, at one or more occasions. Thus, detecting an identified DCI format with a configured new RNTI indicates cancellation of a part or all of the PUSCH scheduled by the original UL authorization. In Figure 2 the context of, detecting a DCI with a given RNTI indicates cancellation of the first portion, and for the second and third time portions, no DCI is sent. The content of the DCI is invalid.

[0043] In one example, the values of L and J are configured by a higher layer. In another example, the values of J and L are implicitly derived from the set or number of PRBs and the number of scheduled symbols, respectively. A table configured by a higher layer can be used for the UE, where the UE can obtain the values of J and / or L based on the range of values of the number of PRBs and the range of values of the number of symbols, and an example is shown in Table 1.

[0044] Table 1

[0045]

[0046]

[0047] In one example, the values of L and J depend on a parameter set. The UE can obtain the configuration of the values of L and J based on the active BW part.

[0048] In one example, the DCI format of UL_CI can include a bitmap of X*Y bits, where X≥1 indicates the number of time partitions within each time part, and Y≥1 indicates the number of frequency parts. The time and frequency granularity can be configured by a higher layer or obtained implicitly from the allocated resources of the PUSCH. In Figure 3 it, it is assumed that X = 1 and Y = 1. X and Y can be configured or obtained in a parameter set specific manner, i.e., depending on the active BW part.

[0049] In one example, a compact DCI format can be envisioned for UL_CI. The compact DCI can be monitored with a C-RNTI or any other configured RNTI. The compact DCI can indicate one or more of the following:

[0050] · A header / flag if multiple DCI formats have the same size

[0051] · A field containing XY≥1 bits to indicate the area to cancel transmission

[0052] ο can be a bitmap including X*Y bits

[0053] · HARQ ID

[0054] ο In this case, the UE can have multiple UL transmissions in parallel

[0055] · Carrier indicator

[0056] · BWP indicator

[0057] · Zero padding, etc.

[0058] In one example, one or more of the UL - authorized NDI bit - field, HARQ ID bit - field, MCS indication field, time / frequency resource allocation field, such as DCI format 0_0 or 0_1 can be used to identify that the DCI actually indicates a transmission cancellation rather than an authorization. For example, for a given HARQ ID, if the NDI bit is toggled, it can refer to a new transmission. However, certain sets of entries in the MCS table are reserved for re - transmissions, for example, MCS with indices 28 to 31. Now, one of those reserved entries that can indicate the MCS can be toggled for the NDI bit for the same HARQ process ID, and this can be used as a notification of the UL_CI for a packet scheduled using the HARQ process ID. The time / frequency resource allocation bit - field can be used to indicate the time / frequency region for which the transmission is to be cancelled and can span physical resources that exceed the previously allocated PUSCH. Thus, it can be desirable for the UE to cancel all UL transmissions that overlap with the resource region identified by the resource allocation information in the UL_CI. In one example, if the time / frequency resource allocation uses a total of L≥1 bits, then K<=L bits can be used for cancellation indication. As another example, the time - domain and frequency - domain RA bit - fields can be combined and reinterpreted to determine the time - frequency resources for cancellation, or the time - domain and frequency - domain RA fields can be interpreted for a regular UL authorization.

[0059] Re-scheduling / modifying grant for the same HARQ process ID

[0060] In one example, no new physical channel or DCI format design may be required. The first UL authorization schedules a packet with a specific state of the NDI bit for a given HARQ process. If the UE receives a subsequent UL authorization for the same HARQ process (or transport block) with the same or different NDI bit state within a configured window or a set of monitoring occasions, referring to the configuration considered above for monitoring before or during the ongoing PUSCH transmission scheduled by the first UL authorization, the UE can discard the ongoing transmission and instead follow the updated authorization for the same HARQ process. This method essentially "shifts" the PUSCH resource allocation to, for example, a later time, or alternatively updates the UL authorization with a new resource allocation. The updated authorization can also be referred to as a modified or re - scheduled authorization.

[0061] In the context of this example, the subsequent authorization performs both the operation of cancelling a transmission and scheduling a transmission. Additionally, if the UE has been configured with re - transmissions through an earlier configuration, such subsequent authorizations can serve the role of performing repeated cancellations as well as scheduling a new transmission. The UE can be configured to monitor subsequent UL authorizations at one or more occasions. If a subsequent authorization is not received within the configured multiple occasions, the UE continues with the existing operation or follows the original authorization. The configured multiple occasions can be obtained by configuring a time window or duration that includes these occasions.

[0062] Even though the network scheduler can flexibly transmit the original grant at any time, the transmission timing of the modified grant and how frequently the network can send such modified grants may be different from the situation when the UE monitors the first grant.

[0063] An important aspect is to avoid excessive delays in UL grant reception and UL transmission, which is particularly important for UEs supporting low-latency traffic, while taking into account the processing time required for the UE to detect and act on the modified UL grant.

[0064] Thus, in an extended example, upon detecting a UL grant, the UE monitors potential subsequent updated grants, possibly with a finer monitoring granularity and within a time window. Such monitoring periodicity and the time window duration can be configured or predefined and can be obtained based on the initial (before receiving the UL grant) monitoring timing, periodicity, symbols, time slots, etc. Alternatively, the window length can be determined based on the scheduled PUSCH (or PUSCH in the case of configured repetitions) duration. For example, the UE can monitor or not monitor after the end of the PUSCH transmission (transmission in the case of repetitions). As yet another alternative, the time window duration can be configured as part of the search space set configuration for the UE via higher layers (UE-specific RRC signaling).

[0065] Note that if the network configures a UE with a fine monitoring granularity, for example, without any changes before and after receiving the grant, the UE may be burdened with unnecessary frequent monitoring, for example, when no rescheduling needs to be performed. This illustrates the need for a proper selection of the window length and monitoring periodicity.

[0066] In another example, the UE can be configured with a monitoring periodicity for general scheduling transmissions and an additional set of DCI monitoring configuration parameters corresponding to potential rescheduling operations. These additional configurations can be activated / triggered based on events (such as the reception of a UL grant) and can be associated with a specific search space set configuration.

[0067] The PDCCH monitoring periodicity, offset, and pattern within a time slot are currently indicated as part of the configuration of a given search space set. Then, the rescheduling grant can be monitored in the same or a different search space set as the search space set in which the original grant was received, and the rescheduling grant may have some additional parameters (such as a different monitoring periodicity), for example, when the UE monitors the rescheduling grant based on a triggering event.

[0068] For example, a given search space and CORESET may have two monitoring periodicities, one as a default monitoring periodicity, and the other may be triggered / activated only when certain events (e.g., receipt of a scheduling grant) occur. An additional set of parameters may include different monitoring periodicities, offsets, or patterns relative to the original UL grant.

[0069] Currently, monitoring-related parameters and configurations are configured semi-statically. Generally speaking, in one implementation of the present disclosure, dynamic updates of search space monitoring configurations may be considered. In the above specific example, such dynamic updates may not require any dynamic indication and may be implicitly activated / deactivated.

[0070] Such dynamic updates of the configuration may enable a situation where the UE does not monitor candidate objects in some monitoring opportunities, while in some other opportunities the UE monitors very few additional candidate objects. In other words, with this additional monitoring setting, the UE may monitor candidate objects more frequently but less, e.g., a subset of the candidate objects it may monitor for full-fledged periodic monitoring.

[0071] In one example, specifying such additional monitoring behavior may be triggered only when a valid UL grant for data transmission in the scheduled UL is detected.

[0072] Considering the time required for the UE to detect and decode a modified grant and the time the UE needs to take action on it (e.g., cancel an earlier grant and PUSCH preparation and transmit according to the modified grant), the minimum PUSCH preparation time for subsequent UL grants depends on the UE processing time capability and UE implementation. For example, N2 is defined as the number of OFDM symbols required for UE processing from the end of the PDCCH containing the UL grant to the earliest possible start of the corresponding PUSCH transmission from the UE's perspective.

[0073] Activating additional UE monitoring upon receipt of a UL grant may also be extended for the case of UL updated grants with different HARQ process IDs. Thus, according to the HARQ process, if the latter is a rescheduling grant that does not switch the NDI compared to the first grant, the UE cancels the transmission of the PUSCH corresponding to the previous grant.

[0074] In another example, the UE may continue to transmit the PUSCH according to two grants for the same HARQ process, regardless of the NDI switching phase, as long as the PUSCH is TDM-ed, i.e., there is no time-domain overlap between the resource allocations by the first grant and the second grant. Thus, the UE follows the scheduling grant and continues the transmission, where each grant follows its own HARQ timeline.

[0075] Search space set configuration

[0076] As described above, one aspect of updating / rescheduling authorization is the dynamic adaptation in the UE monitoring behavior. Some examples on how to implement dynamic PDCCH monitoring are discussed below, where the monitored PDCCH can change / update / cancel the resource allocation made by the previous PDCCH. For example, assume that the UE is configured with S search space sets in a given DL BWP, where the search space sets are indexed by s. The UL cancellation indication UL_CI or the updated authorization / rescheduling authorization can be configured to be transmitted on at least one search space set. The DCI format for the UL cancellation or rescheduling authorization can be referred to as DCI format x-y, where x can be 0 as selected for UL authorization in the specification, and y can be 0 or 1. Alternatively, if it is transmitted in the common DCI in the PDCCH selected for the common PDCCH in this specification, x can be 2, and y => 1 can be an integer, such as y can be 1 or 4. If y = 1, it can imply that the DL preemption indication DCI format 2_1 can also be reused for UL cancellation. In addition, the size of the DCI format can be one of the following: (i) the same as DCI format 0_0, (ii) the same as the latter if DCI format 2_1 is configured in the same search space, and (iii) configured by UE-specific RRC signaling.

[0077] In a first example, for the search space set s that can monitor UL_CI or the rescheduling authorization, the UE can be provided with an indication by the higher layer parameter dci-Formatx-y as part of the higher layer configuration of the search space. If there is an indication, the UE can monitor DCI format x-y in the search space set s.

[0078] In a second example, the UE monitors the search space set s only after being triggered (such as after detecting a valid UL authorization or starting from a specified number of symbols (Ns) before some UL transmission opportunities), such as for DCI format x-y. The UL transmission opportunities can include one or more of the following: type 1 or 2 CG PUSCH transmission, SRS transmission, semi-statically configured PUCCH transmission (e.g., for scheduling request (SR), periodic or semi-persistent CSI feedback).

[0079] In one example, the monitoring pattern within a time slot can be configured for search space set s by the higher layer parameter monitoringSymbolsWithinSlot. Additionally, the UE can also be configured with a higher layer parameter duration (or monitoring window) for search space set s, where the duration can be indicated in time slots or symbols. Note that this parameter duration can be the same as or separately configured from the duration parameter that optionally configures the CSS in the Rel-15 NR specification. The monitoring offset can indicate the position where the duration starts. In one example, search space set s can also be configured to be periodic, however, the periodicity may not be used for monitoring UL_CI or re-scheduling grants. In other words, the UE can monitor DCI format x-y in search space set s only within the duration and not periodically. Alternatively, the UE can monitor DCI format x-y in search space set s according to the configured monitoring periodicity but within the time period defined by the duration parameter.

[0080] In a third example, once the UE detects DCI format x-y in one of the monitoring occasions in search space s, the UE skips monitoring the remaining occasions within the time slot. In another example, the UE skips monitoring the remaining occasions of search space set s within this duration.

[0081] In a fourth example, the UE monitors search space set s only based on a trigger such as an allocation received from the network. In one example, the expected search space set s can be indexed lower than other existing search space sets, such that the UE attempts search space set s with a higher priority. This is because each search space set can have a given number of PDCCH candidates, and the UE may not exceed the total number of blind detection attempts within a time slot across all search space sets configured for the UE. In one example, if search space set s is used on a demand basis, it can be identified as a higher priority search space set (regardless of the search space set index), and if needed, one or more other search space sets can be placed in a given time slot. This can be achieved by configuring an additional flag / parameter as part of the search space set configuration. In another example, search space set s can also be used to periodically monitor other DCI formats, however, if a trigger is received, the UE can monitor search space set s in consecutive time slots, even though it may have a periodicity greater than a time slot. If a trigger is received, only the parameter duration can be used, otherwise the UE follows the search space set s configuration periodically.

[0082] In one example, the duration of the search space set configuration can be active only after receiving an allocation (such as an authorization). The UE can still monitor the search space set s after the configured periodicity. In one example, the search space set s has a periodicity of K = 5 time slots and a duration of 2 time slots. The UL authorization is received in the DL time slot n corresponding to the UL transmission starting in the UL time slot n+K2, where K2 indicates the time between the UL authorization and the UL data transmission, which can be represented in time slots or symbols. For example, K2 = 2 time slots. In one example, the offset to the start position of the duration can be obtained based on the (minimum) UE processing time of the NR PDCCH. The parameter N3 can be recognized to define the PDCCH processing time in a time slot or symbol for a given parameter set. N3 can be less than N2, which is the number of OFDM symbols required for the UE to start processing from the end of the NR-PDCCH containing the UL authorization to the earliest possible start of the corresponding NR PUSCH transmission from the UE's perspective. N3 can be a UE capability parameter and be reported by the UE, for example, as part of the RRC connection setup. In one example, the duration can start after an offset of one time slot (i.e., offset from DL time slot n+1) and end at time slot n+2. The UE can monitor the search space set s according to the pattern given by the parameter monitoringSymbolsWithinSlot or the parameters configured separately within time slots n+1 and n+2. The UE can resume monitoring the search space set s at the next configured periodic occasion. However, the duration parameter can be used only after allocation and not always. Note that here, a part of the search space set configuration is dynamically indicated / activated, which is different from the fully semi-static search space set configuration in the current specification.

[0083] In another example, the search space set s is not configured with a duration. The UE can implicitly obtain the duration for monitoring the search space set s after a trigger. In one example, the UE can identify the position where the duration ends according to the length of the PUSCH transmission. In one example, the UE can monitor the set s after an offset with a periodicity of one time slot according to the pattern given by the parameter monitoringSymbolsWithinSlot and not monitor after the UL transmission ends.

[0084] In one example, the number of blind decoding attempts and / or CCEs for channel estimation within a time slot can be dynamically increased after a trigger. When following the trigger, the search space set s can be used, which may require a larger number of blind decoding attempts and / or CCEs for channel estimation within a time slot compared to the existing number of blind decoding attempts and / or CCEs used for channel estimation before receiving the trigger. If the UE can support such behavior, the UE can report it in terms of UE-NR-capability.

[0085] In one example, Figure 2 the UL grant in Figure 2 can be replaced by a DL grant, and the UL data / PUSCH can alternatively be a PUCCH. In other words, if the UE is configured with a feature that can cancel / discard part or all of the PUCCH transmission (including any repetitions) after an indication, a similar monitoring behavior can also be used.

[0086] In one example, the UE may not expect to monitor a cancellation indication to discard a periodically configured UL transmission, such as SRS or CSI feedback reports in the PUCCH.

[0087] In one example, a UE configured with a type 1 or type 2 UL configuration grant can also monitor the UL_CI or a rescheduling grant or more generally a UL grant according to the above behavior. The starting position of the duration or the offset of the starting position of the monitoring occasion can be counted from a reference point, such as a position with respect to time, which is a number of slots and / or symbols before the UL transmission with the configured grant starts, or a number of slots and / or symbols before the boundary of the slot where the transmission opportunity starts. Alternatively, for a type 2 UL configuration grant, the starting position of the duration or the offset of the starting position of the monitoring occasion can be counted from the slot in which the DCI for activating the type 2 UL configuration transmission is received.

[0088] Which transmissions are subject to preemption / cancellation and / or re-scheduling

[0089] Another aspect to consider in the context of preemption / cancellation and rescheduling is whether the applicability of such an indication to other UL transmissions can be extended beyond dynamically scheduled PUSCH transmissions. Alternatively, it may be necessary to specify that only certain transmissions are subject to PI / CI or rescheduling.

[0090] Such details include, for example, in the case of UL grant-free transmission where the transmission opportunity is semi-statically configured, whether the gNB can cancel / reschedule the PUSCH transmission opportunity (some or all) / how to cancel / reschedule the PUSCH transmission opportunity (some or all), or whether the PUCCH transmission opportunity (another example of a semi-statically configured transmission opportunity) can be subject to PI / CI / rescheduling indications.

[0091] In one example, in the case of a configured grant UL transmission (where the duration of each transmission opportunity is known), some specific thresholds can be defined such that if the transmission duration is longer than the threshold, the UE needs to monitor PI / CI / rescheduling. Therefore, if the transmission occupies a relatively long duration, the UE may need to cancel the transmission and start a higher-priority transmission.

[0092] In one example, considering PUCCH transmission, depending on the duration of the configured PUCCH (e.g., long PUCCH format), the UE may need to monitor any preemption / cancellation / rescheduling indication.

[0093] Thus, short transmissions, e.g., when there is no repetition configured, SRS or for short PUCCH formats, may not be subject to PI / CI / rescheduling indication. Whether a given PUCCH transmission can be cancelled can be identified by a higher layer parameter. The higher layer parameter can be obtained as part of one or more RRC configurations related to the PUCCH transmission, such as the PUCCH configuration for a given UE, the common PUCCH configuration in a component carrier, the PUCCH format configuration, the PUCCH resource configuration corresponding to a given PUCCH resource ID.

[0094] Alternatively, it can be specified that only PUSCH transmissions (including both dynamically scheduled PUSCH and type 1 and 2 CG PUSCH) can be subject to preemption / cancellation / rescheduling. Alternatively, only dynamically scheduled PUSCH can be subject to PI / CI / rescheduling indication. These can be further extended by restricting the applicability of the PI / CI / rescheduling indication to PUSCH transmissions with a total duration (including any repetition) longer than 2 or 4 symbols. Similar rules based on the transmission duration can be applied to SRS as well as PUCCH transmissions.

[0095] In another example, rescheduling can be performed for both grant-based UL transmissions and grant-free UL transmissions. Thus, as long as the same HARQ PID is referenced, the UE can switch between these operations, and GF UL transmissions can be subject to the same rescheduling mechanism as described above (while different scrambling RNTIs can be used for GB and GF). Specifically, a rescheduling grant can trigger the UE to switch between GF operation and GB operation. Note that if the UE has not transmitted any information, the use of a rescheduling grant can impose additional burden / overhead; thus, other forms of indication may be preferred.

[0096] In one example, when the UE receives a rescheduling grant before completing its current transmission in GF operation, the GFPUSCH transmission opportunity can be overwritten by a GB transmission opportunity.

[0097] UL grant prioritization

[0098] Unless otherwise specified, the PUSCH can be based on a dynamic grant or a configured grant, and can be cancelled / dropped by a UL CI. The UL CI can be transmitted by a UE-specific DCI such as a UL grant or a group common DCI format.

[0099] In one example, the UL cancellation indication can apply to dynamically grant - based PUSCH or configured grant PUSCH, such as type 1 or type 2. Alternatively, even if the cancellation indication is based on resources where the configured grant indication overlaps with the PUSCH transmission occasion, the higher - layer configuration of the configured grant PUSCH can include an indication that the PUSCH based on the configured grant is prioritized.

[0100] In one example, if a subsequent cancellation indication is received and it indicates resources that overlap with the resources of the scheduled PUSCH, the UL grant such as format 0_0 or format 0_1 includes a field (such as including 1 bit) that indicates whether the corresponding scheduled PUSCH can be preempted or cancelled. In other words, this indication identifies whether the transmission scheduled by the UL grant is prioritized, i.e., the transmission can not be discarded based on other control signaling. For example, a bit value of 0 can indicate that the transmission is prioritized and cannot be preempted / cancelled by another L1 signaling such as a UL grant or cancellation indication, or vice versa. In one example, if the UE identifies that the first PUSCH is prioritized and / or cannot be cancelled by another L1 indication and / or if there is no other scheduled PUSCH that is not prioritized (i.e., indicated in the UL grant or higher - layer configuration) within the configured or identified duration after the DCI that schedules the first PUSCH, the UE does not monitor the cancellation indication, at least until / near the end of the scheduled first PUSCH. In one example, the duration can start after the UL scheduling DCI that schedules the first PUSCH and end at the end of the first PUSCH+Ta, where in one example Ta can be the cancellation time based on the cancellation indication, or the minimum of N2 or the higher - layer configured K2 (the time offset between the UL grant and the PUSCH).

[0101] In one example, if monitoring is enabled, for example, via an indication in the higher - layer configuration or based on the grant, the UE can increase its monitoring activity / budget. The UE can monitor the UL CI only within a configured or identified monitoring duration or period (e.g., after the UL grant or higher - layer configuration). One or more of the following options can be considered.

[0102] Activation of a search space (SS) set s, for the duration configured by the higher - layer, indicating T of the multiple symbols / time slots where the search space set s exists p,s For the duration of the configured monitoring duration and / or mode, for example, the UE receives a UL grant in symbol 0 of time slot n, starts monitoring the PI from symbol k>0 in time slot n, every p>0 symbols, until symbol m =>0 in time slot n + d, d>0. The starting position of the duration can be configured or implicitly obtained based on the offset between the UL grant and the PUSCH. The SS set is activated in an aperiodic manner, i.e., monitored only when the UE expects a cancellation indication.

[0103] Alternatively, the SS set configuration of R15 can be used. The UE only monitors the SS sets with DCI formats configured with cancellation indications or UL grants that can cancel transmissions during the monitoring duration or cycle when they are active.

[0104] Alternatively, for a given budget of the maximum number of PDCCH candidates monitored when the monitoring duration of the UL CI is active, the UE can prioritize the SS sets associated with the DCI format of the UL CI over other SS sets.

[0105] In one example, the CBGTI field in the UL grant scheduling the initial transmission can be used to indicate that all transmissions of the HARQ process indicated in the UL grant are protected / prioritized and cannot be cancelled or discarded.

[0106] In one example, the activation of monitoring the UL CI can be obtained implicitly based on the length of the PUSCH. For example, if the scheduled or configured PUSCH duration / length is less than K symbols, the UE expects that the transmission will not be cancelled or discarded. For a given parameter set, K = {4, 7, 14} symbols.

[0107] In one example, a re-scheduled DCI, such as a UL grant, such as a fallback or non-fallback DCI for UL scheduling (including new DCI formats if introduced), can be used for UL cancellation, for example, where the NDI bit is not toggled.

[0108] The UE can discard one or more PUSCH opportunities / repetitions after the application / ready time, e.g., Tproc,2 time (see 38.214), from the end of the PDCCH carrying the re-scheduled DCI, where the PUSCH transmission is identified by the HARQ PID used in the re-scheduled DCI.

[0109] If the application time corresponds to the middle of the PUSCH transmission, the UE can discard a part of the PUSCH transmission.

[0110] The UE can discard the first PUSCH opportunity / repetition after the application / ready time Tproc,2 time from the end of the PDCCH carrying the re-scheduled DCI.

[0111] If the application time corresponds to the middle of the PUSCH transmission, the UE can discard a part of the PUSCH transmission.

[0112] The UE can still continue the transmission of the remaining part of the PUSCH transmission after cancelling or the remaining PUSCH repetitions.

[0113] In one example, for the first HARQ PID (the PID indicated in the grant), if the UL-SCH indicator bit in the first UL grant = 0 and the CSI request field = all zeros (such as format 0_1), it may indicate the cancellation of the UL transmission associated with the first HARQ PID. A UL grant transmission with UL-SCH indicator bit = 0 and CSI request field = all zeros may be referred to as a null grant, that is, the UL grant does not schedule any transmission. In one example, if the UL transmission of the first HARQ PID was previously scheduled, the first UL grant may only cancel the previously scheduled UL transmission and not reschedule any transmission of the HARQ PID. The UE may or may not flush the transmission buffer of the cancelled transmission for the HARQ PID. In one example, the NDI bit is not toggled in the first UL grant because this is not a new transport block for the HARQ PID. In another example, the NDI bit may be a fixed value, or toggled or not toggled, and the UE may identify the cancellation of the previously scheduled UL transmission of a given HARQ PID based on the bit value of the UL-SCH indicator bit and the CSI request, that is, if the UL-SCH indicator bit = 0, then the CSI request field = all zeros.

[0114] In one example, if the UE receives a UL grant with UL-SCH indicator bit = 0 and CSI request field = all zeros, the UE may assume that the UL grant is a cancellation indication, and the UE may identify the time-frequency region for UL transmission cancellation based on the time-domain resource allocation and frequency-domain resource allocation fields. The UE may cancel one or more UL transmissions, including one or more subsequent / ongoing scheduled or configured authorized PUSCH, SRS, PUCCH transmissions that overlap with the indicated time-frequency region. In one example, the UE ignores the HARQ PID in this case because the cancellation can be applied to a set of UL transmissions that overlap with the indicated region.

[0115] In one example, if a UL grant is received for a given HARQ PID, the UE may cancel the CG PUSCH transmission or the first CG PUSCH repetition or all subsequent PUSCH repetitions at least Tproc,2 time before the PUSCH or the first PUSCH repetition transmission opportunity of the CGPUSCH for that HARQ ID, and follow the allocation in the UL grant. In one example, for the first HARQ PID (the PID indicated in the grant), if the UL-SCH indicator bit in the first UL grant = 0 and the CSI request field = all zeros (such as format 0_1), it may indicate that the cancellation of the CG PUSCH UL transmission or the first PUSCH repetition or all subsequent PUSCH repetitions associated with the first HARQ PID and the UE will not re-transmit the PUSCH or PUSCH repetition. In one example, the UE cancels only the first PUSCH repetition (i.e., the next PUSCH repetition after the indication of cancellation) and still transmits subsequent PUSCH repetitions.

[0116] In one example, a new UE-specific DCI format can be used for UL CI, which can be received together with a newly configured RNTI or C-RNTI. The size of the new DCI format can match the fallback DCI format. The new DCI format can be or can not be a scheduling DCI. If the new DCI format can be a scheduling DCI, one of the examples mentioned above can apply here, where the scheduling DCI is a null grant and the UE identifies the time-frequency region to be cancelled based on the time and frequency resource indication.

[0117] The new DCI format can have one or more of the following configurable fields (this list is not exhaustive):

[0118] Header / flag, if multiple DCI formats have the same size

[0119] A field for indicating which time / frequency region to cancel / avoid, including XY≥1 bits to indicate the region where the transmission is to be cancelled. This can be a bitmap including X*Y bits, where X indicates the number of time partitions and Y indicates the number of frequency partitions within the configured region. The field can include a rough indication, 1 bit: whether to discard the remaining PUSCH / repetition opportunities or only the affected opportunities. The UE can identify the affected opportunities based on a configured offset from the position of the DCI, or only identify the first PUSCH / repetition to be discarded after Tproc,2 time of the DCI. The field can include a CBG level indication: which CBGs are discarded or the typical time-domain or frequency-domain allocation in the grant.

[0120] HARQ ID or ID

[0121] Carrier indicator

[0122] BWP indicator

[0123] Power control parameters if the UE needs to adjust the transmission power in the affected area. This can be, for example, two bits: 00 → cancel, 01 / 10 / 11 → adjust the power on the overlapping transmission.

[0124] Indicates whether to transmit UCI if UCI is initially selected to be multiplexed onto the overlapping PUSCH. Although the PUSCH needs to be discarded, the UE can still transmit UCI on the PUCCH

[0125] Zero padding

[0126] In one example, group common DCI formats can be considered for UL CI, which can indicate one or more of the following:

[0127] Common fields to indicate which time domain / frequency domain to cancel / avoid. In one example, this area contains XY≥1 bits to indicate the area where transmission is to be cancelled. The indication can be a bitmap including X*Y bits, where X indicates the number of time partitions and Y indicates the number of frequency partitions within the configured area. The configured area is referred to as the time-frequency resource addressed by the CI. Configurable time / frequency indication granularity. Such as via higher layer RRC signaling. In one example, this field has carrier-specific common fields, each common field including XY bits. Where X = {1,2,3}, Y = {1,2,3,4,5,6,7}. In one example, the time domain granularity can be 1 to 14 symbols, and the frequency domain granularity can be 1 / 2, 1 / 4, 1 / 8, 1 / 16 of the active BW part. Here, the BW part refers to the active UL BW part in the carrier. The reference configured area can be a continuous symbol group and a continuous PRB group. Multiple sets of time-frequency granularities can be configured / supported in the specification, such as two sets, and one time-frequency granularity is identified for use via higher layer signaling when transmitting UL CI. Alternatively, one of the multiple sets of time-frequency granularities can be dynamically indicated in the DCI carrying the UL CI. UE-specific fields with a rough indication. In one example, the rough indication includes 1 bit in each UE-specific field, indicating whether to cancel transmission or not.

[0128] For example, the offset from the last symbol of the PDCCH carrying the CI (if not configured by the higher layer) to the start position of the configured area in time. The reference configured area will start after the offset, where the frequency range of this area can be the whole or a part of the active UL BW part in the carrier. If the offset is not dynamically indicated, a pre-configured offset is used, which can be configured per component carrier or per BW part. The offset can be parameter set-related and can be obtained in multiple time slots or symbols.

[0129] In one example, if the UE is provided with higher layer parameters enabling monitoring, such as the presence of configured UL preemption or UL Cancellation in the PDCCH configuration, the UE monitors the UL CI in the GC DCI format. The configured UL preemption or UL Cancellation may provide one or more of the relevant higher layer parameters, such as the configured RNTI, the time / frequency indication granularity, the payload size of the DCI carrying the UL CI, the configuration for each serving cell in the case where the DCI provides UL CL for a set of cells, the location of the serving cell configured in the DCI, the time / frequency region addressed by the cancellation indication, etc.

[0130] In one example, if the UL CI is transmitted in the GC DCI, the UE cancels only the PUSCH or PUSCH repetitions that overlap with the indicated region and may still transmit the remaining PUSCH repetitions.

[0131] In one example, if the UE multiplexes the UCI onto the PUSCH in a time slot and the UE receives a UL CI indicating cancellation of the PUSCH, the UE may still transmit the UCI in the initial PUCCH resource if the PUCCH resource does not overlap with the indicated time / frequency region to be avoided by the UL CI. This is assuming that the UE has an applicable time available for mapping the UCI onto the PUCCH, where the UCI was initially intended to be carried via the PUSCH transmission. In one example, a higher layer parameter may be configured that identifies whether the PUSCH carrying the UCI can be cancelled / dropped.

[0132] In one example, if the PUCCH resource of the first UCI overlaps with the first PUSCH and the second PUSCH and the first PUSCH in the time slot are located before the second PUSCH, the UE multiplexes the UCI onto the first PUSCH, and unless it receives a UL CI cancelling the first PUSCH, the UE multiplexes the UCI onto the second PUSCH if the UL CI does not overlap with the indicated region.

[0133] Figure 4 A flowchart outlining a method for cancelling scheduled UL transmissions is shown. The method includes receiving configuration signaling at 402 to monitor for an uplink (UL) cancellation indication. The method includes monitoring a search space for the UL cancellation indication at 404. The method includes detecting the UL cancellation indication in the search space at 406. The method includes cancelling at least a portion of the scheduled UL transmission in response to the UL cancellation indication at 408.

[0134] Power control for overlapping transmissions

[0135] The network can use a given bandwidth portion in a carrier to overlap transmissions of multiple service types. For example, a 60 kHz bandwidth portion that can benefit from low-latency transmission can be used. To facilitate overlapping transmissions such that one or more of the overlapping transmissions are not adversely affected, if the network anticipates subsequent overlapping transmissions, it can indicate some parameters, such as power control parameters, to the UE. In other words, if overlapping transmissions are not expected, the UE can operate using existing power control parameters or according to other indicated power control parameters. When the overlapping transmissions involve infrequent bursty communications spanning a small duration, the dynamic indication of power control parameters to one or more UEs can be rather costly. For this reason, the UE can be instructed with power control parameters as part of a BW portion configuration or a stand-alone configuration or other UL-related configuration, which can be turned off by default. When such overlapping transmissions are expected, the parameter values can be turned on. This parameter can be indicated by UE-specific RRC signaling.

[0136] RNTI-based parameter identification

[0137] The UE can be configured with one or more RNTIs, where the RNTIs can be used to scramble the CRC appended to the DCI format. In one example, the UE is configured with RNTI A and RNTI B. One or more parameters related to UL transmissions using the RNTI can be obtained implicitly. For example, if RNTI A is used, a first set of power control parameters can be assumed, and if RNTI B is used, a second set of power control parameters can be assumed. For example, when the UL grant provides resources in an overlapping manner with other transmissions, RNTI B can be used by the network having that grant, such that the UE can use appropriate power to control UL interference at the gNB and thus affect one or more overlapping transmissions.

[0138] Figure 5 A flowchart outlining a method for controlling the power for transmission is shown. The method includes, at 502, receiving power control signaling specifying a power control parameter value. The method includes, at 504, controlling the power level of subsequent transmissions based on that value.

[0139] For one or more examples, at least one of the components shown in one or more of the foregoing figures can be configured to perform one or more operations, techniques, processes, and / or methods described in the example section below. For example, the baseband circuitry described above in connection with one or more of the foregoing figures can be configured to operate according to one or more of the following embodiments. As another example, the circuitry associated with the UE, base station, network element, etc. described above in connection with one or more of the foregoing figures can be configured to operate according to one or more of the examples shown in the example section below.

[0140] Embodiment

[0141] Example 1 is one or more computer-readable media having instructions that, when executed, cause a user equipment (UE) device to perform the following operations: receive configuration signaling to monitor an uplink (UL) cancellation indication; monitor a search space for the UL cancellation indication; detect the UL cancellation indication in the search space; and in response, cancel at least a portion of a scheduled UL transmission.

[0142] Example 2 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: monitor for the UL cancellation indication in a UE-specific search space associated with a control resource set (CORESET).

[0143] Example 3 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: cancel a scheduled physical uplink shared channel (PUSCH) transmission scheduled by a UL grant in response to detecting the cancellation indication.

[0144] Example 4 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: monitor for the UL cancellation indication in a group common search space associated with a control resource set (CORESET).

[0145] Example 5 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: cancel a configured UL transmission not associated with a UL grant in response to detecting the cancellation indication.

[0146] Example 6 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: cancel an entire scheduled UL transmission.

[0147] Example 7 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine that the cancellation indication specifies a portion of a scheduled UL transmission to cancel; and in response, cancel the specified portion of the scheduled UL transmission.

[0148] Example 8 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine the physical resources specified in the UL cancellation indication; and cancel all scheduled UL transmissions that overlap with the specified physical resources.

[0149] Example 9 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: detect that a trigger condition has been met; and in response, start monitoring for cancellation indications in the search space.

[0150] Example 10 includes the subject matter of Example 9, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: detect that a trigger condition has been met when receiving a UL grant for scheduling a PUSCH transmission.

[0151] Example 11 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: receive a second UL grant for a transport block (TB) associated with a scheduled UL transmission resulting from a first UL grant; and in response, cancel the scheduled UL transmission.

[0152] Example 12 includes the subject matter of Example 11, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: transmit the TB according to the second UL grant.

[0153] Example 13 includes the subject matter of Example 11, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine that the second UL grant and the first UL grant have the same hybrid automatic repeat request (HARQ) process identifier associated with the TB, and in response, cancel the scheduled UL transmission.

[0154] Example 14 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: receive the configuration signaling via higher layer radio resource control (RRC) signaling.

[0155] Example 15 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine a monitoring duration and a monitoring mode for the search space based on higher layer signaling.

[0156] Example 16 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine the length of the scheduled UL transmission; and refrain from monitoring the search space when the length drops below a threshold.

[0157] Example 17 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine the physical resources specified by the UL cancellation indication; and transmit a portion of the scheduled UL transmission that does not overlap with the specified physical resources.

[0158] Example 18 includes the subject matter of Example 1, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: receive a UL grant; schedule the UL transmission based on the UL grant; determine that the UL grant is prioritized based on the UL grant; and receive the cancellation indication for the scheduled UL transmission; and transmit the scheduled UL transmission.

[0159] Example 19 includes the subject matter of Example 18, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: in response to receiving the cancellation indication, cancel subsequent scheduled repeated UL transmissions derived from the UL grant.

[0160] Example 20 includes the subject matter of Example 18, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine that the UL grant is prioritized based on the value of the DCI field of the UL grant.

[0161] Example 21 is one or more computer-readable media having instructions that, when executed, cause a user equipment (UE) device to perform the following operations: receive power control signaling specifying a power control parameter value; and in response, control the power level of subsequent transmissions based on the value.

[0162] Example 22 includes the subject matter of Example 21, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: store the power control parameter; and in response to receiving an activation indication from higher layer signaling, control the power level of subsequent transmissions based on the value.

[0163] Example 23 includes the subject matter of Example 21, including or omitting optional elements, wherein the instructions further include instructions that, when executed, cause the UE to perform the following operations: determine a plurality of power control parameters mapped to respective radio network temporary identifiers (RNTIs); store the power control parameters; and control the power level of subsequent transmissions based on the current RNTI for the UE device.

[0164] Unless otherwise expressly stated, any one of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the examples to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practice of the various examples.

Claims

1. A computer-readable medium having instructions that, when executed, cause a user equipment UE to perform the following operations: Receive configuration signaling to monitor an uplink UL cancellation indication; Based on the configuration signaling, monitor a search space for the UL cancellation indication; Detect a UL cancellation indication in the search space, where the UL cancellation indication identifies physical resources spanning a scheduled physical uplink shared channel PUSCH transmission; and In response, cancel a UL transmission overlapping with the physical resources identified by the UL cancellation indication, the UL transmission including at least a portion of the scheduled PUSCH transmission, and where the instructions further cause the UE to perform the following operations: Determine the length of the scheduled PUSCH transmission; and Suppress monitoring the search space for the UL cancellation indication when the length drops below a threshold.

2. The computer-readable medium according to claim 1, wherein the scheduled PUSCH transmission is associated with a type 1 or type 2 configured grant.

3. The computer-readable medium according to claim 1, wherein the UL cancellation indication includes an X*Y-bit bitmap of physical resources, where X is greater than or equal to 1 and indicates the number of time partitions within each time portion, and Y is greater than or equal to 1 and indicates the number of frequency partitions within a configured region.

4. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to monitor for the UL cancellation indication in a search space shared by a group associated with a control resource set CORESET.

5. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Cancel a portion of the scheduled PUSCH transmission specified by the UL cancellation indication.

6. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Cancel all scheduled UL transmissions overlapping with the physical resources specified by the UL cancellation indication.

7. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Detect that a trigger condition has been met; and In response, start monitoring the search space for the UL cancellation indication.

8. The computer-readable medium according to claim 7, wherein the instructions further cause the UE to detect that the trigger condition has been met when receiving a UL grant for scheduling a PUSCH transmission.

9. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Receive a second UL grant for a transport block TB associated with a scheduled UL transmission generated by a first UL grant; and In response, cancel the scheduled UL transmission.

10. The computer-readable medium according to claim 9, wherein the instructions further cause the UE to cause the TB to be transmitted according to the second UL grant.

11. The computer-readable medium according to claim 9, wherein the instructions further cause the UE to determine that the second UL grant and the first UL grant have the same hybrid automatic repeat request (HARQ) process identifier associated with the transport block, and in response, cancel the scheduled UL transmission.

12. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Transmit a portion of the scheduled PUSCH transmission that does not overlap with the physical resources specified by the UL cancellation indication.

13. The computer-readable medium according to claim 1, wherein the instructions further cause the UE to perform the following operations: Receive a UL grant; Schedule the PUSCH transmission based on the UL grant; Determine that the UL grant is prioritized based on the UL grant; and Receive the UL cancellation indication for the scheduled PUSCH transmission; and Cause the scheduled PUSCH transmission to be transmitted.

14. The computer-readable medium according to claim 13, wherein the instructions further cause the UE to perform the following operation: in response to receiving the UL cancellation indication, cancel subsequent scheduled repeated UL transmissions resulting from the UL grant.

15. The computer-readable medium according to claim 13, wherein the instructions further cause the UE to determine that the UL grant is prioritized based on the value of the DCI field of the UL grant.

Images