Method and apparatus for downlink control information signaling for partial bandwidth switching

Abstract

Different sets of downlink control information (DCI) fields can be configured for the DCI, which includes indications for triggering bandwidth portion switching at the user equipment (UE). For example, the UE can receive a DCI that triggers it to switch its operation from a first bandwidth portion to a second bandwidth portion. The UE can also identify a set of variable and a set of non-variable DCI fields within the DCI. The UE can then determine the updated content of the DCI to apply to the second bandwidth portion based on whether the DCI fields are included in the variable or non-variable field set. In some cases, the UE can identify an empty allocation in the received DCI and can switch its operation from the first bandwidth portion to the second bandwidth portion based on this empty allocation.

Description

[0001] This application is a divisional application of the invention patent filed on February 13, 2019, with application number 201980013208.8 and invention title "Downlink Control Information Signaling Scheme for Partial Bandwidth Switching".

[0002] Cross-references

[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 710,474, filed February 16, 2018, entitled “Downlink Control Information Signaling Schemes for Bandwidth Part Switching”, and U.S. Patent Application No. 16 / 273,564, filed February 12, 2019, entitled “Downlink Control Information Signaling Schemes for Bandwidth Part Switching”; each of these applications is assigned to its assignee. Technical Field

[0004] The following generally pertains to wireless communications, and more specifically to downlink control information (DCI) signaling schemes for bandwidth portion (BWP) handover. Background Technology

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Spread Spectrum Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include multiple base stations or access network nodes, each supporting communication for multiple communication devices simultaneously, which may also be referred to as User Equipment (UE).

[0006] In some wireless communication systems, wireless devices can operate within different portions of a channel or carrier. For example, a UE can operate within one or more BWPs of a channel used for wireless communication. In this case, the UE can switch between different BWPs, for example, to save energy by tuning the radio unit to a smaller BWP (e.g., compared to other BWPs). Therefore, techniques are needed to ensure reduced BWP handover latency and proper interpretation of control information in each BWP to ensure effective communication. Summary of the Invention

[0007] The described technology relates to methods, systems, devices, or apparatuses that support improved downlink control information (DCI) signaling schemes for bandwidth portion (BWP) handover. Generally, the described technology provides configuration for different sets of DCI fields for a DCI that includes an indication triggering a BWP handover at a user equipment (UE). For example, the UE may receive a DCI that triggers the UE to switch operation from a first BWP to a second BWP. The UE may also identify a set of transformable DCI fields and another set of DCI fields (e.g., non-transformable DCI fields) within the DCI. The set of transformable DCI fields may include DCI fields having content that can be updated from the first BWP to the second BWP (e.g., by zero-padding or truncating) according to transformation rules (e.g., utilizing various parameters regarding the content within each DCI field). Additionally, the set of non-transformable fields may include DCI fields with exceptions to the transformation rules and may have content that is not updated between BWPs according to the transformation rules. The UE may determine the updated content of the DCI to apply to the second BWP based on whether the DCI field is included in the set of transformable fields or the set of non-transformable fields. In some examples, the UE can determine different sizes of the DCI field in two or more BWPs. In other examples, the DCI may include an empty allocation (e.g., an allocation for which no resources are currently allocated for communication), and the UE can use this empty allocation to identify a BWP handover trigger. In this case, the UE can avoid attempting to update the DCI content of the non-transformable field used for the second BWP.

[0008] A method for wireless communication is described. The method may include: receiving, while operating in a first BWP, a DCI having a plurality of DCI fields from a base station, each of the plurality of DCI fields having a corresponding first size based on the first BWP; receiving, as part of the DCI, an indication that a UE will switch from operating in the first BWP to operating in a second BWP; identifying a first set of DCI fields from the plurality of DCI fields, the content of the DCI fields in the first set in the first BWP being updatable by a transformation rule to a DCI field having a corresponding second size in the second BWP; identifying a second set of DCI fields from the plurality of DCI fields, the content of the DCI fields in the second set in the first BWP being downdatable by a transformation rule; and determining, at least in part, the updated content of the plurality of DCI fields to be applied to the second BWP based on whether each DCI field comes from the first set of DCI fields or the second set of DCI fields.

[0009] An apparatus for wireless communication is described. The apparatus may include: a unit for receiving, while operating in a first BWP, a DCI having a plurality of DCI fields from a base station, each of the plurality of DCI fields having a corresponding first size based on the first BWP; a unit for receiving, as part of the DCI, an indication that a UE will switch from operating in the first BWP to operating in a second BWP; a unit for identifying a first set of DCI fields from the plurality of DCI fields, the content of the DCI fields in the first set of DCI fields in the first BWP being updatable by a transformation rule to a DCI field having a corresponding second size in the second BWP; a unit for identifying a second set of DCI fields from the plurality of DCI fields, the content of the DCI fields in the second set of DCI fields in the first BWP not being updatable by a transformation rule; and a unit for determining, at least in part, the updated content of the plurality of DCI fields to be applied to the second BWP based on whether each DCI field comes from the first set of DCI fields or the second set of DCI fields.

[0010] Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are operable to cause the processor to: receive, while operating in a first BWP, a DCI having a plurality of DCI fields from a base station, each of the plurality of DCI fields having a corresponding first size based on the first BWP; receive, as part of the DCI, an indication that the UE will switch from operating in the first BWP to operating in a second BWP; identify a first set of DCI fields from the plurality of DCI fields, the content of which the DCI fields in the first set have in the first BWP being updatable by a transformation rule to a DCI field having a corresponding second size in the second BWP; identify a second set of DCI fields from the plurality of DCI fields, the content of which the DCI fields in the second set have in the first BWP being downdatable by a transformation rule; and determine, at least in part, the updated content of the plurality of DCI fields to be applied to the second BWP based on whether each DCI field comes from the first set of DCI fields or the second set of DCI fields.

[0011] A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: receive, while operating in a first BWP, a DCI having a plurality of DCI fields from a base station, each of the plurality of DCI fields having a corresponding first size based on the first BWP; receive, as part of the DCI, an indication that a UE will switch from operating in the first BWP to operating in a second BWP; identify a first set of DCI fields from the plurality of DCI fields, the content of which the DCI fields in the first set have in the first BWP being updatable by a transformation rule to a DCI field having a corresponding second size in the second BWP; identify a second set of DCI fields from the plurality of DCI fields, the content of which the DCI fields in the second set have in the first BWP being downdatable by a transformation rule; and determine, at least in part, the updated content of the plurality of DCI fields to be applied to the second BWP based on whether each DCI field comes from the first set of DCI fields or the second set of DCI fields.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for updating the contents of a first DCI field set via transformation rules. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining the updated contents of the first DCI field set, at least in part, based on a second BWP.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying an empty allocation for a second BWP within a received DCI. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for switching operation from a first BWP to a second BWP, at least partially based on an empty allocation. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for avoiding determination of the contents of at least the second set of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, identifying an empty allocation for a second BWP includes detecting an empty allocation within a resource allocation field of the plurality of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an empty allocation may trigger a switch from a first BWP to a second BWP, at least partially based on a DCI.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for detecting empty allocations within a resource allocation field of the plurality of DCI fields. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for detecting a BWP identifier (ID) indicating a switch from a first BWP to a second BWP. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining a timing value indicating the time difference between a received DCI and the start of a second BWP. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for avoiding detection of the remaining set of DCI fields from the plurality of DCI fields, at least in part based on the detected empty allocations.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for detecting a BWP ID indicating a switch from a first BWP to a second BWP within a DCI. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining a timing value indicating the time difference between the received DCI and the start of the second BWP, at least in part based on the DCI.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying a minimum size for each DCI field in a second set of DCI fields, wherein the content within a DCI field having the minimum size can be updated to the DCI field in a second BWP. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the size of the content within the DCI may be a static size greater than or equal to the minimum size.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying a DCI field to be truncated from a first set of DCI fields, based at least in part on the fact that a corresponding first size of the DCI field in a first BWP may be greater than a corresponding second size in a second BWP. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that the content within the DCI field may have a predetermined value. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for truncating the DCI field, at least in part based on determining that the content may have the predetermined value. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the predetermined value may be zero.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first DCI field set includes the plurality of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a second DCI field set includes the plurality of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration of the first DCI field set and the second DCI field set can be pre-configured. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration of the first DCI field set and the second DCI field set can be received via higher-layer signaling.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining whether the aggregate first size of the second DCI field set in the first BWP is different from the aggregate second size of the second DCI field set in the second BWP.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that a total first size may differ from a total second size, wherein the total second size may be greater than the total first size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying in a first BWP a set of partial size qualification bits that includes the difference between the total first size and the total second size, wherein the total size of this set of partial size qualification bits in the first BWP and the set of second DCI fields may be equal to the total second size of the set of second DCI fields in the second BWP.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for updating the contents of a second DCI field set at least in part based on the portion-size-equalized bit set. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining a second DCI field set at least in part based on a second BWP to identify a corresponding second size, order, packing, content, or combination thereof of the DCI fields.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that a total first size may differ from a total second size, wherein the total second size may be smaller than the total first size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying in a second BWP a set of partially size-equalized bits that includes the difference between the total first size and the total second size, wherein the total size of this partially size-equalized bit set in the first BWP and the second DCI field set may be equal to the total second size of the second DCI field set in the second BWP.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for updating the contents of a second DCI field set at least in part based on the portion-size-equalized bit set. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining the updated contents of the second DCI field set at least in part based on a second BWP to identify a corresponding second size, order, packing, content, or combination thereof of the DCI fields.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that a aggregate first size may be less than a aggregate second size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining whether the corresponding aggregate sizes of each DCI field in a second set of DCI fields in a plurality of BWPs are the same, wherein the plurality of BWPs includes at least a first BWP and a second BWP.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that the total first size of the second DCI field set in the first BWP may differ from at least one corresponding total size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying a partially size-equalized bit set in the first BWP that includes the difference between the maximum corresponding total size and the total first size, wherein the total size of this partially size-equalized bit set and the second DCI field set in the first BWP may be equal to the maximum corresponding total size.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for determining that the total second size of the second DCI field set in the second BWP may differ from at least one corresponding total size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying a partially size-equalized bit set in the second BWP that includes the difference between the maximum corresponding total size and the total second size, wherein the total size of this partially size-equalized bit set and the second DCI field set in the second BWP may be equal to the maximum corresponding total size.

[0027] A method for wireless communication is described. The method may include: receiving a Direct Current Interface (DCI) from a base station during a first Time Interval (TTI) while operating in a first Base Mobile Terminal (BWP); receiving, as part of the DCI, an indication that the UE will switch from operating in the first BWP to operating in a second BWP; determining that the second BWP begins at a second TTI following the first TTI; and triggering a handover from the first BWP to the second BWP, at least in part, based on the received DCI, to avoid monitoring the Physical Downlink Control Channel (PDCCH).

[0028] An apparatus for wireless communication is described. The apparatus may include: a unit for receiving a Direct Communication Interface (DCI) from a base station during a first Time Interval (TTI) while operating in a first Base Window (BWP); a unit for receiving, as part of the DCI, an indication that the UE will switch from operating in the first BWP to operating in the second BWP; a unit for determining the start of the second BWP at a second TTI following the first TTI; and a unit for triggering a handover from the first BWP to the second BWP, at least in part, based on the received DCI, to avoid monitoring the PDCCH.

[0029] Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are operable to cause the processor to: receive a DCI from a base station during a first TTI while operating in a first BWP; receive, as part of the DCI, an indication that the UE will switch from operating in the first BWP to operating in a second BWP; determine that the second BWP begins at a second TTI following the first TTI; and trigger a handover from the first BWP to the second BWP, at least in part based on the received DCI, to avoid monitoring the PDCCH.

[0030] A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: receive a DCI from a base station during a first TTI while operating in a first BWP; receive, as part of the DCI, an indication that the UE will switch from operating in the first BWP to operating in a second BWP; determine that the second BWP begins at a second TTI following the first TTI; and trigger a handover from the first BWP to the second BWP, at least in part based on the received DCI, to avoid monitoring the PDCCH.

[0031] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the second TTI immediately follows either a physical downlink shared channel (PDSCH) transmission scheduled by the received DCI or a physical uplink shared channel (PUSCH) transmission scheduled by the received DCI.

[0032] A method for wireless communication is described. The method may include: determining to switch the operation of a UE from a first BWP to a second BWP; generating a DCI having a plurality of DCI fields, each of the plurality of DCI fields having a corresponding first size based on the first BWP; configuring the DCI with a first set of DCI fields, wherein the content of the DCI fields in the first set in the first BWP can be updated via a transformation rule to a DCI field having a corresponding second size in the second BWP; configuring the DCI with a second set of DCI fields, wherein the content of the DCI fields in the second set in the second set in the first BWP cannot be updated via a transformation rule to a DCI field having a corresponding second size in the second BWP; configuring the DCI with an indication that the UE will switch from operation in the first BWP to operation in the second BWP; and transmitting the DCI to the UE.

[0033] An apparatus for wireless communication is described. The apparatus may include: a unit for determining to switch the operation of a UE from a first BWP to a second BWP; a unit for generating a DCI having a plurality of DCI fields, each of the plurality of DCI fields having a corresponding first size based on the first BWP; a unit for configuring the DCI with a first set of DCI fields, the content of the DCI fields in the first set in the first BWP being updatable by a transformation rule to a DCI field having a corresponding second size in the second BWP; a unit for configuring the DCI with a second set of DCI fields, the content of the DCI fields in the second set in the second BWP not being updatable by a transformation rule; a unit for configuring the DCI with an indication that the UE will switch from operation in the first BWP to operation in the second BWP; and a unit for transmitting the DCI to the UE.

[0034] Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are operable to cause the processor to: determine to switch the operation of the UE from a first BWP to a second BWP; generate a DCI having a plurality of DCI fields, each of the plurality of DCI fields having a corresponding first size based on the first BWP; configure the DCI with a first set of DCI fields, the contents of which in the first BWP are updatable via a transformation rule to DCI fields having a corresponding second size in the second BWP; configure the DCI with a second set of DCI fields, the contents of which in the first BWP are not updatable via a transformation rule; configure the DCI with an indication that the UE will switch from operation in the first BWP to operation in the second BWP; and transmit the DCI to the UE.

[0035] A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: determine to switch the operation of a UE from a first BWP to a second BWP; generate a DCI having a plurality of DCI fields, each of the plurality of DCI fields having a corresponding first size based on the first BWP; configure the DCI with a first set of DCI fields, the contents of which in the first BWP are updatable via a transformation rule to DCI fields having a corresponding second size in the second BWP; configure the DCI with a second set of DCI fields, the contents of which in the first BWP are not updatable via a transformation rule; configure the DCI with an indication that the UE will switch from operation in the first BWP to operation in the second BWP; and transmit the DCI to the UE.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for sending an empty allocation for a second BWP, at least in part based on the premise that the aggregate first size is less than the aggregate second size. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the empty allocation for the second BWP includes sending the empty allocation within a resource allocation field of the plurality of DCI fields.

[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for generating a BWP ID indicating a switch from a first BWP to a second BWP. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for transmitting the BWP ID as part of the DCI, wherein a timing value indicating the time difference between the transmitted DCI and the start of the second BWP may be at least partially based on the DCI.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring a minimum size for each DCI field in the second DCI field set, wherein the content within a DCI field having the minimum size can be updated to the DCI field in the second BWP. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the size of the content within the DCI may be a static size greater than or equal to the minimum size.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for identifying a DCI field to be truncated from a first set of DCI fields, based at least in part on the premise that a corresponding first size of the DCI field in a first BWP may be greater than a corresponding second size in a second BWP. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the content within the DCI field using predetermined values.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the total first size of the second DCI field set in the first BWP to be different from the total second size of the second DCI field set in the second BWP, wherein the total second size may be greater than the total first size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for inserting a partially size-equalized bit set in the first BWP that includes the difference between the total first size and the total second size, wherein the total size of the partially size-equalized bit set for the first BWP and the second DCI field set may be equal to the total second size of the second DCI field set in the second BWP.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the total first size of the second DCI field set in the first BWP to be different from the total second size of the second DCI field set in the second BWP, wherein the total second size may be smaller than the total first size. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for inserting a partially size-equalized bit set in the second BWP that includes the difference between the total first size and the total second size, wherein the total size of the partially size-equalized bit set for the first BWP and the second DCI field set may be equal to the total second size of the second DCI field set in the second BWP.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the total first size of the second DCI field set in a first BWP to be different from at least one corresponding total size of the corresponding non-transitory DCI field sets in a plurality of BWPs. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for inserting a partially size-equalized bit set in the first BWP that includes the difference between the maximum corresponding total size and the total first size, wherein the total size of the partially size-equalized bit set in the first BWP and the second DCI field set may be equal to the maximum corresponding total size.

[0043] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the total second size of the second DCI field set in the second BWP to be different from at least one corresponding total size of the corresponding non-transitory DCI field sets in a plurality of BWPs. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for inserting a partially size-equalized bit set in the second BWP that includes the difference between the maximum corresponding total size and the total second size, wherein the total size of the partially size-equalized bit set in the second BWP and the second DCI field set may be equal to the maximum corresponding total size.

[0044] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for configuring the aggregate first size of the second DCI field set in the first BWP to be smaller than the aggregate second size of the second DCI field set in the second BWP.

[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the predetermined value may be zero. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include processes, features, units, or instructions for sending an empty allocation within the resource allocation field of the plurality of DCI fields, wherein the empty allocation may trigger a switch from a first BWP to a second BWP at least in part based on the DCI.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first DCI field set includes the plurality of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a second DCI field set includes the plurality of DCI fields. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration of the first DCI field set and the second DCI field set can be pre-configured. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the configuration of the first DCI field set and the second DCI field set can be transmitted via higher-layer signaling. Attached Figure Description

[0047] Figure 1 An example of a system for wireless communication that supports a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown.

[0048] Figure 2 An example of a wireless communication system that supports a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown.

[0049] Figure 3 An example of a transmission timeline supporting a DCI signaling scheme for BWP handover, based on various aspects of this disclosure, is shown.

[0050] Figure 4A An example of a downlink transmission timeline for a DCI signaling scheme supporting BWP handover, based on various aspects of this disclosure, is shown.

[0051] Figure 4B An example of an uplink transmission timeline supporting a DCI signaling scheme for BWP handover, in accordance with various aspects of this disclosure, is shown.

[0052] Figure 4C An example of a discontinuous reception (DRX) timeline supporting a DCI signaling scheme for BWP handover, in accordance with various aspects of this disclosure, is shown.

[0053] Figure 4DExamples of uplink and downlink transmission timelines supporting DCI signaling technologies for active BWP handover are shown in accordance with various aspects of this disclosure.

[0054] Figure 4E Examples of uplink and downlink transmission timelines supporting DCI signaling technologies for active BWP handover are shown in accordance with various aspects of this disclosure.

[0055] Figure 5 An example of a transport scheme supporting a DCI signaling scheme for BWP handover is shown, based on various aspects of this disclosure.

[0056] Figure 6 An example of a processing scheme supporting the DCI signaling scheme for BWP handover is shown, based on various aspects of this disclosure.

[0057] Figure 7 An example of the process flow in a system that supports a DCI signaling scheme for BWP handover in accordance with various aspects of this disclosure is shown.

[0058] Figures 8 to 10 A block diagram of an apparatus supporting a DCI signaling scheme for BWP handover is shown, in accordance with various aspects of this disclosure.

[0059] Figure 11 A block diagram of a system including a UE supporting a DCI signaling scheme for BWP handover is shown, according to various aspects of this disclosure.

[0060] Figures 12 to 14 A block diagram of an apparatus supporting a DCI signaling scheme for BWP handover is shown, in accordance with various aspects of this disclosure.

[0061] Figure 15 A block diagram of a system including a base station supporting a DCI signaling scheme for BWP handover is shown, according to various aspects of this disclosure.

[0062] Figures 16 to 22 A method for a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Detailed Implementation

[0063] In some wireless communication systems, the size of the downlink control information (DCI) (e.g., bit length) can be based on the size of the associated bandwidth portion (BWP) (e.g., bandwidth). Furthermore, different BWPs can be used for wireless communication, and handover between individual BWPs can be controlled via downlink signaling (such as DCI), which can implement various schemes for resource allocation and triggering BWP handover. That is, DCI signaling can be used to control and facilitate handover between a current BWP of a first size and a target BWP of a second size during a BWP handover event.

[0064] In some cases, cross-slot scheduling and cross-BWP scheduling can be used to accommodate latency during handover between narrow and wide BWPs. For example, DCI signaling can be used to control handover from a first BWP format (e.g., a narrow or smaller BWP) in a first time slot to a second BWP format (e.g., a relatively wider or larger BWP than the first BWP format) in a second time slot, or vice versa, where different BWP formats can have different DCI field sizes. In some cases, BWP handover can be triggered without cross-BWP scheduling. For example, after a first time slot with a first BWP format (the first BWP format has a DCI corresponding to the payload in the first time slot), a transition can be made to a second time slot with a second BWP format (the second BWP format has a DCI corresponding to the payload in the second time slot). In some cases, the base station can signal to the user equipment (UE) about transmission delays associated with downlink and uplink transmissions. When transitioning from the first BWP format to the second BWP format, the DCI size can be determined based on the maximum DCI size across all configured BWPs. Alternatively, the size of one or more or all DCI bit fields can be determined based on the current BWP. As another alternative, the UE can perform a BWP handover without data transmission scheduled for an upcoming slot allocation.

[0065] This paper describes a transmission scheme that includes transformation rules that can be applied to the DCI field of the current BWP (e.g., having a first size) to transform the DCI field size to the target DCI field size of the target BWP (e.g., having a second size). The transformation rules can distinguish between transformable and non-transformable fields and include transformation and interpretation algorithms to facilitate switching of BWP sizes.

[0066] First, various aspects of this disclosure are described within the context of a wireless communication system. Then, additional aspects are described with reference to transmission timelines and transmission schemes. Further aspects of this disclosure are described with reference to apparatus diagrams, system diagrams, and flowcharts relating to the DCI signaling scheme used for BWP handover.

[0067] Figure 1 An example of a wireless communication system supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (i.e., mission-critical) communication, low-latency communication, and communication with low-cost and low-complexity devices.

[0068] Base station 105 can wirelessly communicate with UE 115 via one or more base station antennas. Base station 105 described herein may include, or may be referred to by those skilled in the art as, a base station transceiver, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or giga-NodeB (both can be referred to as gNB), home NodeB, home eNodeB, or some other suitable term. Wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). UE 115 described herein is capable of communicating with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0069] Each base station 105 may be associated with a specific geographic coverage area 110 in which communication with various UEs 115 is supported. Each base station 105 may provide communication coverage to the corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include uplink transmission from the UE 115 to the base station 105, or downlink transmission from the base station 105 to the UE 115. Downlink transmission may also be referred to as forward link transmission, and uplink transmission may also be referred to as reverse link transmission.

[0070] The geographic coverage area 110 of base station 105 can be divided into sectors that constitute only a part of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, base station 105 can be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and overlapping geographic coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. Wireless communication system 100 can include, for example, heterogeneous LTE / LTE-A / LTE-A Pro or NR networks, wherein different types of base stations 105 provide coverage for various geographic coverage areas 110.

[0071] The term "cell" refers to a logical communication entity used to communicate with base station 105 (e.g., via a carrier) and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells and may be configured with different cells based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographical coverage area 110 on which the logical entity operates.

[0072] UE 115 can be distributed throughout the wireless communication system 100, and each UE 115 can be fixed or mobile. UE 115 can also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where "device" can also be referred to as a unit, station, terminal, or client. UE 115 can also be a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 can also refer to a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device, which can be implemented in various items such as home appliances, vehicles, meters, etc.

[0073] Some UE 115 devices, such as MTC or IoT devices, can be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base stations without human intervention. In some examples, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application, which can then utilize the information or present it to people interacting with the program or application. Some UE 115 devices can be designed to collect information or enable automated machine behavior. Some application examples of MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, medical monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0074] Some UEs 115 can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, but not simultaneously via both). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving "deep sleep" mode when not actively communicating, or operating on limited bandwidth (e.g., according to narrowband communication). In some cases, UE 115 can be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 can be configured to provide ultra-reliable communication for these functions.

[0075] In some cases, UE 115 can also communicate directly with other UE 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more of a group of UE 115s utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UE 115s in the group may be outside the geographic coverage area 110 of base station 105, or may be unable to receive transmissions from base station 105 for other reasons. In some cases, the group of UE 115s communicating via D2D communication can use a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some cases, base station 105 implements the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UE 115s without involving base station 105.

[0076] Base station 105 can communicate with core network 130 and with each other. For example, base station 105 can be connected to core network 130 via backhaul link 132 (e.g., via S1 or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) via backhaul link 134 (e.g., via X2 or other interfaces).

[0077] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with the EPC. User IP packets can be delivered through the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be connected to network operator IP services. Operator IP services may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), and packet-switched (PS) streaming services.

[0078] At least some of the network devices, such as base station 105, may include sub-components such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity may communicate with UE 115 through multiple other access network transport entities, which may be referred to as radio headends, smart radio headends, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio headends and access network controllers) or combined into a single network device (e.g., base station 105).

[0079] Wireless communication system 100 can operate using one or more frequency bands typically in the 300MHz to 300GHz range. The region from 300MHz to 3GHz is generally referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features. However, these waves are sufficient to penetrate structures to enable macrocells to provide service to UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300MHz, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100km).

[0080] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) using frequency bands from 3 GHz to 30 GHz. The SHF region includes frequency bands such as the 5 GHz Industrial, Scientific and Medical (ISM) band, which can be used opportunistically by devices capable of tolerating interference from other users.

[0081] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the individual devices can be even smaller and more closely spaced than UHF antennas. In some cases, this can be advantageous for using antenna arrays within the UE 115. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater atmospheric attenuation and shorter distances during propagation. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary by country or regulatory body.

[0082] In some cases, wireless communication system 100 may utilize licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), unlicensed LTE (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz ISM band. When operating in unlicensed radio spectrum bands, wireless devices such as base station 105 and UE 115 may employ a pre-call listening (LBT) procedure to ensure the frequency channel is clear before data transmission. In some cases, operation in unlicensed bands may be based on CA configuration combined with CC (e.g., LAA) operation in licensed bands. Operation in unlicensed spectrum may include downlink transmission, uplink transmission, peer-to-peer transmission, or a combination thereof. Duplexing in unlicensed spectrum may be based on Frequency Division Duplex (FDD), Time Division Duplex (TDD), or a combination of both.

[0083] In some examples, base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), wherein the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. For example, multiple signals may be transmitted by the transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO technology includes: single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0084] Beamforming, also known as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to shape or guide antenna beams (e.g., transmit or receive beams) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that signals propagating relative to the antenna array in a particular direction undergo constructive interference, while other signals undergo destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting or receiving device applying certain amplitude and phase offsets to the signals transmitted via each antenna element associated with the device. The adjustment associated with each antenna element can be defined by a beamforming weight set associated with a particular direction (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other direction).

[0085] In one example, base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions, which may include transmitting signals according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions can be used (e.g., by base station 105 or receiving devices, such as UE 115) to identify the beam direction for subsequent transmission and / or reception by base station 105. Some signals, such as data signals associated with a particular receiving device, may be transmitted by base station 105 in a single beam direction (e.g., the direction associated with a receiving device such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined at least in part based on signals transmitted in different beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions, and UE 115 may report to base station 105 an indication that it received a signal with the highest signal quality or other acceptable signal quality. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0086] A receiving device (e.g., UE 115, which may be an example of an mmW receiving device) may attempt multiple receive beams when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receiving directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receive beamforming weights applied to the signals received at multiple antenna elements of the antenna array, or by processing the received signals according to different sets of receive beamforming weights applied to the signals received at multiple antenna elements of the antenna array, any of which can be referred to as “listening” according to different receive beams or receiving directions. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving data signals). The single receive beam may be aligned at least in part based on a beam direction determined by listening according to different receive beam directions (e.g., a beam direction determined at least in part based on listening according to multiple beam directions to have the highest signal strength, highest signal-to-noise ratio, or other acceptable signal quality).

[0087] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be located together at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with multiple rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations.

[0088] In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may, in some cases, perform packet segmentation and reassembly for communication on logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use Hybrid Automatic Repeat Request (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections between UE 115 and base station 105 or core network 130 to support radio bearers of user plane data. At the physical layer (PHY), transport channels can be mapped to physical channels.

[0089] In some cases, UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique to increase the likelihood of correct data reception via communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise ratio conditions). In some cases, the radio device can support simultaneous time-slot HARQ feedback, where the device can provide HARQ feedback in a specific time slot for data received in a previous symbol within that time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0090] The time interval in LTE or NR can be expressed in a basic time unit (e.g., it can be called T). sIt is expressed as a multiple of the sampling period (1 / 30,720,000 seconds). The time interval of communication resources can be organized according to radio frames, each with a duration of 10 milliseconds (ms), where the frame period can be expressed as T. f =307,200T s Radio frames can be identified by System Frame Numbers (SFNs) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. Subframes may be further divided into two time slots, each with a duration of 0.5 ms, and each time slot contains 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). Without the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the minimum scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in a burst of shortened TTI (sTTI) or in selected component carriers using sTTI).

[0091] In some wireless communication systems, time slots can be further divided into multiple hourly slots containing one or more symbols. In some cases, the symbol or hourly slot of an hourly slot can be the smallest scheduling unit. For example, the duration of each symbol can vary depending on the subcarrier spacing or operating frequency band. Furthermore, some wireless communication systems can implement time slot aggregation, where multiple time slots or hourly slots are aggregated together and used for communication between UE 115 and base station 105.

[0092] The term "carrier" refers to a set of radio spectrum resources with a defined physical layer structure used to support communication on communication link 125. For example, a carrier of communication link 125 may include a portion of a radio spectrum band operating according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. Carriers may be associated with predefined frequency channels (e.g., E-UTRA Absolute Radio Frequency Channel Number (EARFCN)) and can be located according to a channel grid for discovery by UE 115. Carriers may be downlink or uplink (e.g., in FDD mode), or configured to carry both downlink and uplink communication (e.g., in TDD mode). In some examples, the signal waveform transmitted on a carrier may consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

[0093] The carrier organization structure can vary depending on the radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR, etc.). For example, communication on a carrier can be organized according to TTI or time slots, each of which can include user data and control information or signaling to support decoding the user data. A carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling to coordinate carrier operation. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers.

[0094] Physical channels can be multiplexed on carriers using various techniques. Physical control channels and physical data channels can be multiplexed on downlink carriers, for example, using time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. In some examples, control information transmitted in the physical control channel can be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0095] The Physical Downlink Control Channel (PDCCH) or shortened PDCCH (sPDCCH) can carry the Direct Frequency Information (DCI) within Control Channel Elements (CCEs). A CCE can, for example, consist of nine logically contiguous Resource Groups (REGs), each containing four Resource Elements (REs). The DCI includes information about downlink scheduling allocation, uplink resource granting, transmission schemes, uplink power control, HARQ information, modulation and coding schemes (MCS), and other information. The size and format of the DCI message can vary depending on the type and amount of information carried. For example, if spatial multiplexing is supported, the DCI message size is larger than that of a contiguous frequency allocation. Similarly, for systems employing MIMO, the DCI may include additional signaling information. The size and format of the DCI can depend on the amount of information and factors such as bandwidth, the number of antenna ports, and the duplex mode.

[0096] The PDCCH can carry DCI messages associated with multiple users, and each UE 115 can decode the DCI messages for it. For example, a Cell Random Network Temporary Identifier (C-RNTI) can be assigned to each UE 115, and the Cyclic Redundancy Check (CRC) bits appended to each DCI can be scrambled based on the C-RNTI. To reduce power consumption and overhead at UE 115, a limited set of Control Channel Elements (CCE) locations can be specified for the DCIs associated with a particular UE 115. CCEs can be grouped (e.g., into groups containing 1, 2, 4, and 8 CCEs), and the set of CCE locations in which the user equipment can find the associated DCI can be specified. These CCEs can be referred to as the search space. The search space can be divided into two areas: a common CCE area or search space and a UE-specific (dedicated) CCE area or search space. The common CCE area is monitored by all UEs 115 served by base station 105 and can include information such as paging information, system information, and random access procedures. The UE-specific search space can include user-specific control information. CCEs can be indexed, and the common search space can start from CCE 0. The starting index of a UE-specific search space can depend on the C-RNTI, subframe index, CCE aggregation level, and random seed. UE 115 can attempt to decode DCIs by performing a process called blind decoding, during which the search space is decoded randomly until a DCI is detected. During blind decoding, UE 115 can attempt to descramble all potential DCI messages using its C-RNTI and perform a CRC check to determine if the attempt was successful.

[0097] A carrier can be associated with a specific bandwidth of the radio spectrum, and in some examples, the carrier bandwidth can be referred to as the “system bandwidth” of the carrier of the wireless communication system 100. For example, the carrier bandwidth can be one of several predetermined bandwidths of a carrier used for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined portion or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., “in-band” deployment of a narrowband protocol type).

[0098] In systems employing MCM technology, a resource element can consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate UE 115 can achieve. In MIMO systems, wireless communication resources can refer to a combination of radio spectrum resources, temporal resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate used for communication with UE 115.

[0099] The devices of the wireless communication system 100 (e.g., base station 105 or UE 115) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configured to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include base station 105 and / or UE 115 that support simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0100] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers; this feature can be referred to as carrier aggregation (CA) or multi-carrier operation. The UE 115 can be configured with multiple downlink CCs and one or more uplink CCs depending on the carrier aggregation configuration. Carrier aggregation can be used with both FDD and TDD component carriers.

[0101] In some cases, the wireless communication system 100 may use enhanced component carriers (eCC). eCC can be characterized by one or more features, including wider carrier or frequency channel bandwidth, shorter symbol duration, shorter TTI duration, or modified control channel configuration. In some cases, eCC may be associated with carrier aggregation configurations or dual connectivity configurations (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). eCC can also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is permitted to use the spectrum). eCC characterized by wide carrier bandwidth may include one or more segments that can be used by a UE 115 that is unable to monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to save power).

[0102] In some cases, eCC can use a different symbol duration than other CCs, which may include using a reduced symbol duration compared to other CCs. A shorter symbol duration can be associated with an increased spacing between adjacent subcarriers. Devices utilizing eCC (such as UE 115 or base station 105) can transmit wideband signals (e.g., based on frequency channels or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds (μs)). The TTI in eCC can consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) can be variable.

[0103] Wireless communication systems such as NR systems can utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility in eCC symbol duration and subcarrier spacing allows for the use of eCC across multiple spectrums. In some examples, NR spectrum sharing can increase spectral utilization and efficiency, specifically through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

[0104] The wireless communication system 100 can support the configuration of different sets of DCI fields, which include indications for triggering BWP handover at UE 115. For example, UE 115 can receive a DCI that triggers UE 115 to switch operation from a first BWP to a second BWP. UE 115 can also identify a set of variable and a set of non-variable DCI fields within the DCI. The set of variable DCI fields can include fields that can be updated from the first BWP to the second BWP (e.g., by padding with zeros) according to transformation rules (e.g., various levels of restrictions on the content within each DCI field). Additionally, the set of non-variable fields can include DCI fields that cannot be updated between BWPs according to transformation rules. UE 115 can then determine the updated content of the DCI to apply to the second BWP, which can be based on whether the DCI field is included in the set of variable or non-variable fields.

[0105] For example, UE 115 can determine the total size of each set of non-transformable DCI fields in two or more BWPs. Where the corresponding total size of the non-transformable DCI fields differs between the two or more BWPs, the non-transformable DCI fields can be configured to undergo partial size equalization, thereby including additional bits based on the maximum total size of the non-transformable field set for a given BWP (e.g., making the corresponding total size of the non-transformable fields equal across multiple BWPs). In other examples, the difference in total size can indicate the need to send an empty allocation in the DCI, and UE 115 can recognize a BWP handover trigger but avoid attempting to update the DCI content of the non-transformable fields based on a second BWP. In other cases, the minimum size of the DCI fields in the set of non-transformable DCI fields can be used, which further enables content updates between individual BWPs without issues. The described techniques can provide configuration-based transformation rules that reduce complexity and improve efficiency when updating content between BWPs. For example, the techniques described herein can reduce decoding failures at UE 115 that might be caused by padding some non-transformable fields with zeros.

[0106] In other examples, the wireless communication system 100 may support DCI signaling, which enables the UE 115 to postpone monitoring the PDCCH after receiving a DCI that includes an indication of BWP handover. In this case, the UE 115 may receive the DCI in a first TTI and determine the start of the second BWP in a subsequent TTI based on the timeline used for handover operations between different BWPs. This subsequent TTI may be the TTI immediately following the transmission of the Physical Downlink Shared Channel (PDSCH) / Physical Uplink Shared Channel (PUSCH) scheduled by the received DCI. In any case, the UE 115 may avoid monitoring the PDCCH based on the indication of BWP handover. Such a technique enables efficient wake-up schemes (e.g., two-phase wake-up schemes) and can further enhance energy efficiency at the UE 115.

[0107] Base station 105 and UE 115 can be configured to communicate using BWP and DCI, wherein the size of the DCI varies based on the size of the corresponding BWP. The varying size of the DCI can introduce complexity during BWP handover events and when using a fallback DCI. To address these issues, techniques for generating and interpreting resource allocation information in the DCI during BWP handover events are described. Furthermore, techniques for providing a fallback DCI of constant size associated with a reference BWP are also described.

[0108] Figure 2An example of a wireless communication system 200 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a and a UE 115-a that can use a carrier 205 to transmit information. The wireless communication system 200 may be configured to transmit information on the carrier 205 using one or more BWPs 210.

[0109] BWP 210 can be a set of contiguous physical resource blocks (PRBs). The bandwidth of BWP 210 can be equal to or less than the maximum bandwidth capability supported by UE115-a or the bandwidth of the entire carrier 205. In some cases, the bandwidth of BWP 210 can be at least as large as the bandwidth of the synchronization signal (SS) block.

[0110] In some cases, BWP 210 may be a dynamically configured (or semi-statically configured) portion of carrier 205. BWP 210 may include multiple dynamically (or semi-statically) configurable parameters. Examples of these parameters may include frequency location (e.g., center frequency), bandwidth (e.g., number of PRBs), digital scheme (e.g., subcarrier spacing and / or cyclic prefix type), or combinations thereof. These parameters of BWP 210 may be transmitted using DCI, Medium Access Control (MAC) control elements (CE), Radio Resource Control (RRC) signaling, and / or timing patterns (e.g., in the case of discontinuous reception). The granularity of some parameters may be the size of a PRB (e.g., bandwidth granularity may be one PRB, and frequency location granularity may be one PRB).

[0111] BWP 210 can be configured for both downlink and uplink. BWP 210 can be configured independently for each cell (e.g., primary cell and / or secondary cell). In this case, if the SCell is disabled, the BWP for that cell can also be disabled. In some cases, UE 115-a can be configured to communicate using one or more downlink BWPs and / or one or more uplink BWPs simultaneously. In some cases, at a given time, for a serving cell, there can be at most one active downlink BWP and at most one active uplink BWP. The primary cell (PCell) can be the serving cell handling the RRC connection between UE 115-a and base station 105-a, while the secondary cell (SCell) can be any other serving cell established between UE 115-a and base station 105-a.

[0112] BWP 210 can be used in both paired and unpaired spectrum. In paired spectrum, a first spectrum band can be allocated (e.g., dedicated to) downlink communication, and a second spectrum band can be allocated (e.g., dedicated to) uplink communication. Paired spectrum can be used with an FDD system to establish bidirectional communication between nodes. In unpaired spectrum, the same spectrum band can be used for both uplink and downlink communication. Unpaired spectrum can be used with a TDD system to establish bidirectional communication between nodes. In some cases, such as for paired spectrum, the maximum number of BWPs configured can include four downlink BWPs and four uplink BWPs. In other cases, such as for unpaired spectrum, the maximum number of BWPs configured can include four downlink / uplink BWP pairs. For FDD, BWPs for downlink and BWPs for uplink can be configured independently on a per component carrier (CC) basis. For TDD, a combined set of downlink and uplink BWPs can be configured on a per CC basis.

[0113] In some cases, the active BWP 210 of UE 115-a may not span a spectrum band larger than the bandwidth of the CC used for UE 115-a. The configuration of the downlink BWP may include at least one control resource set (CORESET). In some cases, at least one configured downlink BWP may include a CORESET with a control search space in the primary component carrier (PCC). In some cases, a control search space may be configured in each BWP 210 within the PCell used for UE 115-a. In some cases, each configured downlink BWP may include at least one CORESET with a UE-specific search space (UE-SS) for a single active BWP case at a given time. In some cases, if the active downlink BWP does not include a control search space, UE 115-a may not monitor control searches. The control search space may include communication resources at which UE 115-a can be configured to search for a physical downlink control channel (PDCCH) carrying DCI as its payload.

[0114] When establishing an RRC connection, UE 115-a or base station 105-a may enable the default configuration of one or more BWP 210s (e.g., downlink BWP and uplink BWP). UE 115-a and base station 105-a may use those default BWP 210s until the BWP 210s are explicitly configured or reconfigured.

[0115] The wireless communication system 200 can also support BWP handover events. In some cases, UE 115-a (or base station 105-a) can be configured to use one BWP 210 on carrier 205 at a time, where the BWPs can have different sizes. In this case, if UE 115-a (or base station 105-a) wants to use a different BWP on carrier 205, UE 115-a (or base station 105-a) can reconfigure its BWP 210. As part of a BWP handover event, UE 115-a (or base station 105-a) can hand over the active BWP to a target BWP within a given serving cell. BWP handover events can be signaled using DCI. In some cases, downlink scheduling DCI can be used to hand over downlink BWPs, and uplink scheduling DCI can be used to hand over uplink BWPs. In some cases, either downlink DCI or uplink DCI can be used to hand over either downlink BWP or uplink BWP. In some cases, the wireless communication system 200 can support a timer for timer-based BWP switching. In this time-based configuration, BWP 210 can switch from the active BWP to the default BWP based on the timer expiring.

[0116] As described in further detail below, various techniques can be used to perform efficient BWP handover in the wireless communication system 200. For example, the configuration of different DCI field sets can include a set of transformable DCI fields and a set of non-transformable DCI fields within the DCI. The set of transformable DCI fields can include DCI fields having content that can be updated from the first BWP to the second BWP (e.g., by padding or truncating, etc.) according to transformation rules (e.g., various levels of restrictions on the content within each DCI field). Additionally, the set of non-transformable fields can include DCI fields having content that cannot be updated between BWPs according to transformation rules. That is, non-transformable fields can be used as DCI fields that include exceptions to the transformation rules used for transformable fields. In some cases, non-transformable fields can be a subset of transformable fields. UE115-a determines the updated content of the DCI to be applied to the second BWP based on whether the DCI field is included in the set of transformable fields or the set of non-transformable fields. For example, UE115-a can determine the updated content between BWPs based on a partial equalization scheme for different sets of non-transformable DCI fields. Alternatively, UE 115-a can identify empty allocations and avoid interpreting at least one set of non-transformable DCI fields. In some cases, UE 115-a can also identify the minimum total size of certain non-transformable DCI fields. In other examples, UE 115-a can postpone monitoring the PDCCH after receiving a DCI that includes an indication of BWP handover. In this case, UE 115-a can receive the DCI in the first TTI and determine that the second BWP begins in a subsequent TTI based on the timeline used for handover operations between different BWPs.

[0117] Figure 3 An example of a transmission timeline 300 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, the transmission timeline 300 can implement various aspects of wireless communication systems 100 and 200. The transmission timeline 300 illustrates the technique used by UE 115 to handover between narrow BWP and wide BWP based on control channel signaling transmitted by base station 105.

[0118] Transmission timeline 300 includes several time slots, for example, including time slots n Time slot n+1 Time slot n+2 Time slot m+1 Time slot m+2 Time slot xEach time slot may include a control channel (CCH) 305 transmitted from base station 105 and received at UE 115. In some wireless communication systems, the amount of radio frequency bandwidth used to receive the control channel 305 may be less than the amount of radio frequency bandwidth used to receive data. In this case, the receive bandwidth can be adjusted by switching the active BWP between a narrow BWP (e.g., for the control channel 305) and a wide BWP (e.g., for data). The DCI may trigger the BWP to switch between narrow and wide BWPs, or vice versa. The DCI may include one or more BWP identifier (BWP ID) fields (with BWP IDs equal to, for example, 1 or 2) corresponding to different BWP formats (e.g., narrow BWP and wide BWP respectively). That is, for example, a narrow BWP format may be identified by a BWP ID with a value of "1", while a wide BWP format may be identified by a BWP ID with a value of "2".

[0119] In some cases, such as Figure 3 As shown, cross-slot scheduling and cross-BWP scheduling can help accommodate the waiting time during handover between narrow and wide BWPs. The DCI can also include additional scheduling information for specific slots, such as information for cross-slot and cross-BWP scheduling. For example, scheduling information in the DCI can include a k0 value, which can indicate a scheduling delay indicating the number of slots that can arrive after receiving control channel 305. Figure 3 As shown, the value of k0 is expressed as 1, indicating the scheduling delay of one time slot between control channel 305 and the corresponding PDSCH. For example, corresponding to time slot n+1 Control channel 305-b may not provide downlink grant, and therefore region 310 may be suitable for the sleep or micro-sleep periods of UE115. (Corresponding time slot) n+2 The control channel 305-c can provide downlink grant, which includes, for example, a BWP ID with a value of 1, indicating a narrow BWP (e.g., a relatively small data transmission) for data transmission 315. Therefore, it is possible that there is no need to [follow the time slot]. n+1 Time slot n+2 BWP switching.

[0120] Alternatively, or alternatively, corresponding to the time slot m+1 The control channel 305-d can provide downlink grant, which includes, for example, a BWP ID with a value of 2, indicating a time slot for accommodating data transmission 320 (e.g., a larger data transmission than data transmission 315). m+2 The wide BWP format. Therefore, BWP can be switched, for example, where execution can be performed from a time slot. m+1 Narrow BWP to time slot m+2The receive bandwidth conversion of the wide BWP in the middle. In some cases, data transmission 320 may not be scheduled by control channel 305-d. Instead, UE 115 can listen for downlink grants for data transmission 320 at control channel 305-e. In this case, due to the time slot m+2 With a wide BWP, control channel 305-e can have full scheduling capabilities. In some cases, and as discussed further below, the DCI may include a field (e.g., a frequency domain resource allocation field) with a bit field size proportional to the corresponding BWP.

[0121] In some cases, the BWP timer can be used to indicate periods of inactivity. That is, the BWP can be set to expire after a period of scheduled inactivity. When the BWP timer expires, the active BWP can then be switched (e.g., autonomously) to a narrower bandwidth, such as for reception on control channel 305. Illustratively, this is in... Figure 3 The middle is shown as a time slot m+2 and time slot x The time period between. During the BWP timer slot. x When it expired previously, in the time slot x A transition from a wide BWP back to a narrow BWP may occur during this period. In some cases, the BWP timer may be a timer separate from the DRX timer (e.g., for low-latency data). In some cases, the BWP scheduling information may be dedicated signaling for BWP handover between different BWPs. For example, BWP handover may be based on a scheduled DCI without allocation.

[0122] In some cases, the DCI may not contain a BWP ID field, in which case the DCI may not be used to trigger a BWP handover. However, alternatively, this paper describes several techniques in which DCI signaling can be used to trigger a BWP handover, for example, from a narrow BWP to a wide BWP, or vice versa. Thus, Figure 3 The transmission timeline 300 shown can switch BWPs between various BWP sizes using the described techniques, which can be based on DCI fields that can be transformed at least in part based on their content.

[0123] Figure 4A An example of a downlink transmission timeline 400 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, the downlink transmission timeline 400 can implement various aspects of wireless communication systems 100 and 200. The downlink transmission timeline 400 can illustrate a first technique for UE 115 to handover between, for example, narrow BWP and wide BWP based on control channel signaling from base station 105.

[0124] Downlink transmission timeline 400-a shows an example of a downlink transmission timeline with a delay of k0 = 0 – that is, downlink transmission timeline 400-a can show a transmission with a scheduling delay of zero slots between the control channel and PDSCH 410. Downlink transmission timeline 400-b shows an example of a downlink transmission timeline 400 with a delay of k0 = 1 – that is, downlink transmission timeline 400-b can show a transmission with a scheduling delay of one slot after the control channel until PDSCH 410 is scheduled relative to DCI 405. Downlink transmission timeline 400-c shows another example of a downlink transmission timeline with a delay of k0 = 1.

[0125] According to a first technique for DCI signaling used to trigger BWP handover, BWP handover can be triggered without cross-BWP scheduling. According to the first technique, the DCI information can correspond to the current BWP size, and the DCI size can be determined based on the current BWP format. In this case, PDSCH can be received in the same time slot after the control channel, or alternatively, if the control channel provides cross-time slot scheduling, PDSCH can be received in a later time slot. DCI 405 can include a BWP index for the upcoming time slot. For example, if the BWP index enables a BWP format different from the current BWP, a BWP handover can be triggered to switch to the target BWP (e.g., from a narrow BWP to a wide BWP, or vice versa). In this case, the new BWP can be enabled after X μs, where X can be based on the BWP transition wait time and / or delay, for example, represented by a k0 value. Therefore, the current DCI can schedule future DCIs with a BWP format different from the current DCI's BWP format.

[0126] In the example of downlink transmission timeline 400-a, the first time slot (e.g., time slot) n This can include DCI405-a, and due to the k0=0 delay, it can be implemented in a time slot after DCI 405-a. n Immediately schedule PDSCH 410-a. First time slot (time slot) n The first BWP format (e.g., narrow BWP format) can be used. DCI 405-a can include slots for upcoming timeslots (shown here as slots). n+2 The BWP index indicates that the BWP format used for a later time slot is a second BWP format (e.g., a wide BWP format). In some cases, within a time slot... n After that, time slot n+1 It can provide a conversion time slot from the first BWP format to the second BWP format. Then, in the time slot... n+2At this point, it has already switched to the second BWP format, and due to the delay of k0=0, DCI 405-b can immediately be used in the same time slot. n+2 Data transmission in PDSCH 410-b is scheduled in the middle. In some cases, the downlink transmission timeline 400-a may also include a positive acknowledgment (ACK) transmission 415-a (i.e., HARQ-ACK transmission) after a delay of one time slot (e.g., denoted by k1).

[0127] In the second example, the transmission delay can be set to k0 = 1. For example, as shown in the example of downlink transmission timeline 400-b, the first time slot (e.g., time slot) n This can include DCI 405-c, and based on a k0=1 delay set throughout the downlink transmission timeline 400-b, it can be transmitted in the next time slot (e.g., time slot n) after the time slot n of DCI 405-c. n+1 In this case, the first time slot (time slot 410-c) is scheduled. n The first BWP format can be used (e.g., narrow BWP format). DCI 405-c can include slots for upcoming events (shown here as slots). n+3 The BWP index indicates that the BWP format used for the upcoming time slot is a second BWP format (e.g., a wide BWP format). In the time slot... n and time slot n+1 After that, time slot n+2 It can provide a conversion time slot from the first BWP format to the second BWP format. Then, in the time slot... n+3 At this point, it has been converted to the second BWP format, and due to the k0=1 delay, DCI 405-d can be used in the time slot. n+4 Data transmission in PDSCH 410-d is scheduled in the middle. In some cases, downlink transmission timeline 400-b may also include ACK transmission 415-b (i.e., HARQ-ACK transmission) after a delay of one time slot (e.g., denoted by k1). Therefore, in downlink transmission timeline 400-b with k0=1, a delay of one time slot can be introduced before ACK transmission 415-b.

[0128] As another example, as shown in the example of downlink transmission timeline 400-c, with delay k0 = 1, the time slot n It can include DCI 405-e, and due to the k0=1 delay on the entire downlink transmission timeline 400-c, it can be transmitted in the time slot of DCI 405-e. n Subsequent time slots n+1In the example of downlink transmission timeline 400-c, ACK transmission 415-c can also be scheduled for the first data transmission in PDSCH 410-e. Here, it can be done in the time slot. n+3 The ACK transmission is sent in the first time slot. In this case, the first time slot (time slot) n It can have a first BWP format (e.g., a narrow BWP format). DCI 405-e can include slots for upcoming events (shown here as slots). n+5 The BWP index indicates that the BWP format used for the upcoming time slot is the second BWP format (e.g., wide BWP format).

[0129] According to the first technique used for DCI signaling to trigger BWP handover, the transition can not occur until after the transmitted ACK transmission 415-c, in the time slot. n+4 It can provide a conversion time slot from the first BWP format to the second BWP format. Then, in the time slot... n+5 It has been converted to the second BWP format, and DCI 405-f can be used in time slots. n+6 Data transmission in PDSCH 410-f is scheduled in the middle. In some cases, downlink transmission timeline 400-c may also include a second ACK transmission 415-d (i.e., HARQ-ACK transmission) following a time slot delay (represented by, for example, k1). Therefore, in downlink transmission timeline 400-c with k0=1, a time slot delay can be triggered before each of ACK transmissions 415-c and ACK transmissions 415-d. In some cases, the first technique of DCI signaling used to trigger BWP handover may mean that network scheduling in the current BWP triggers BWP handover. However, this may conflict with situations, for example, where the current BWP is a narrow BWP and the network does not intend to schedule data transmission in the current BWP (i.e., the network intends to schedule the next data transmission in a wide BWP in a later time slot).

[0130] Furthermore, with a longer k0 delay (and for example, if the transition does not occur until after ACK transmission 415), the transmission timeline can introduce a relatively long total delay. That is, for the first technique, the total delay can be equal to the k0 delay setting plus the PDSCH transmission time plus the k1 delay plus the transition time. Moreover, in some cases (e.g., when the k0 transmission delay equals 2), the first technique for DCI signaling used to trigger BWP handover may introduce further delays during BWP handover. However, as described herein, other techniques for DCI signaling can be used to trigger BWP handover, and in some cases, the aforementioned delays during BWP handover can be avoided. For example, by using an empty allocation in the DCI that triggers BWP handover, the total timeline for BWP handover and subsequent communication can be reduced, because the lack of resource allocation can, for example, have a longer total delay than... Figure 4A The example shown has a shorter timeline, even when using a larger k0 value (e.g., k0 = 2).

[0131] Figure 4B An example of an uplink transmission timeline 420 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, the uplink transmission timeline 420 can implement various aspects of wireless communication systems 100 and 200. The uplink transmission timeline 420 illustrates a first technique for UE 115 to handover between narrow BWP and wide BWP based on control channel signaling from base station 105.

[0132] Similar to a reference Figure 4A The described downlink transmission timeline 400 can set the delay value (e.g., k2 delay) of the uplink transmission timeline 420 to a specific value that defines the number of time slots from the start of DCI 405 indicating BWP switching to the start of the later time slot of the different BWP format. Uplink transmission timeline 420-a shows an example of an uplink transmission timeline with a k2=1 delay—that is, uplink transmission timeline 420-a shows a transmission with a scheduling delay of one time slot between the receive control channel and the receive PUSCH 425. Uplink transmission timeline 420-b shows an example of an uplink transmission timeline with a k2=2 delay—that is, uplink transmission timeline 420-b shows a transmission with a scheduling delay of two time slots after the control channel until PUSCH 425 can be transmitted.

[0133] In the example of uplink transmission timeline 420-a, the first time slot (e.g., time slot) n This can include DCI405g, and due to the k2=1 delay set throughout the uplink transmission timeline 420-a, it can be transmitted in the time slot of DCI405g. nThe next time slot (i.e., time slot) n+1 PUSCH 425-a is scheduled in the first time slot. In this case, the first time slot (time slot) n It can have a first BWP format (e.g., narrow BWP format). DCI 405g can include slots for upcoming events (shown here as slots). n+3 The BWP index indicates that the BWP format used for the upcoming time slot is a second BWP format (e.g., a wide BWP format). In the time slot... n and time slot n+1 After that, time slot n+2 It can provide a conversion time slot from the first BWP format to the second BWP format. Then, in the time slot... n+3 It has been converted to the second BWP format, and due to the k2=1 delay, DCI 405h can be used in the time slot. n+4 Data transmission in the PUSCH 425-b is scheduled.

[0134] As per the above reference Figure 4A The first technique used for DCI signaling to trigger BWP handover may introduce further delays at the BWP handover point in some cases (e.g., when the transmission delay of k2 equals 2). For example, as shown in the example of uplink transmission timeline 400-b, in the case of delay k2 = 2, the first time slot (time slot) n This can include DCI 405-i, and due to the k2=2 delay set across the entire uplink transmission timeline 400-b, it can be used in time slots. n+2 The PUSCH425-c is scheduled in the time slot for transmitting DCI 405-b. n Subsequent time slots n+1 There is a time slot delay at this point. In this case, the first time slot (time slot) n The DCI 405-i may have a first BWP format (e.g., a narrow BWP format). The DCI 405-i may include slots for upcoming events (shown here as slots). n+4 The BWP index indicates that the BWP format used for the upcoming time slot is the second BWP format (e.g., a wide BWP format). Uplink transmission timeline 420-b can provide the transition period from the first BWP format to the second BWP format. Then, in the time slot... n+4 It has been converted to the second BWP format, and DCI 405-j can be used in time slots. n+6 Data transmission in PUSCH 425-d is scheduled.

[0135] Therefore, with a relatively long k2 time, the transmission timeline may introduce a relatively long total delay (e.g., compared to a shorter k2 value). For example, with a relatively low latency, a transition according to the first technique may introduce an additional time-slot delay due to the scheduling scheme and the need for transmission and time-slot boundary alignment. In this case, if the wireless communication system can provide an additional latency of less than one time slot, it may be additionally possible to perform all Physical Downlink Control Channel (PDCCH) or Physical Uplink Control Channel (PUCCH) processing (e.g., in half a time slot or less), radio frequency switching delay, and transition (e.g., also in half a time slot or less) within a single time slot. However, this is not possible due to the additional potential delay introduced by the first technique described herein, thus potentially increasing the latency at the BWP handover. Therefore, for uplink transmission, it may be difficult to achieve a K2=0 delay due to the potential delay. However, in some cases, the techniques described herein (e.g., including the use of empty allocation within the DCI) can be used to enhance the BWP handover scheme to achieve efficient BWP handover.

[0136] Figure 4C An example of a DRX timeline 450 supporting DCI signaling technology for active BWP handover, according to various aspects of this disclosure, is shown. In some examples, the DRX timeline 450 can implement various aspects of wireless communication systems 100 and 200. An example of a two-stage pickup scheme is shown for the DRX timeline 450.

[0137] DRX Timeline 450-a can show an example of DRX Timeline 450 when there is no data in the current DRX period. In some examples, DRX Timeline 450-a can show the first stage of a two-stage picking scheme. DRX Timeline 450-b can show an example of DRX Timeline 450 where data exists in the current DRX period. In some cases, DRX Timeline 450-b can show the second stage of a two-stage picking scheme.

[0138] In some cases, UE 115 can receive indications about the values ​​of k0 and / or k2 via signaling from base station 105, as described above. In some cases, it can provide the benefit of configuring the values ​​of k0 and / or k2 to be relatively large. For example, during DRX timeline 450-a, UE 115 may not receive any data, and after the “on” period 455-a, UE 115 may determine to enter a low-power mode (e.g., sleep mode), thereby conserving power until future DRX cycles. Therefore, in this first phase of the two-phase pickup scheme, UE 115 can use minimal power to receive control information only during the “on” period 455-a.

[0139] In some cases, UE 115 may wish to configure a larger k0 or k2 delay to accommodate modem warm-up time and transition time. DRX timeline 450-b can, for example, be configured with a k0 value equal to 4, thereby providing four-slot scheduling time between control channel and data transmission. A relatively long k0 value (e.g., k0 = 4) can provide additional time to accommodate a relatively long modem warm-up time. In this second phase of the two-phase pickup scheme, UE 115 can use more power to receive control information and data transmission than in the first phase of the two-phase pickup scheme. In the second phase of the two-phase pickup scheme, DRX timeline 450-b can provide a BWP timer 457 and an inactive timer 458, which can return to, for example, the first phase of the two-phase pickup scheme upon expiration. Figure 4C As shown, BWP timer 457 can provide the following: monitoring a certain number of time slots (e.g., five time slots) in a specific BWP mode (e.g., BWP2 mode or a wider BWP mode) to locate the PDCCH. UE 115 can monitor the PDCCH in a BWP1 mode, optimized for, for example, larger k0 (or k2) values, during the duration of the inactive timer 458 or until its expiration.

[0140] However, the first technique for triggering BWP handover using DCI signaling may not provide the network with the flexibility to configure larger values ​​because once the DCI indicating BWP handover is decoded, it can be assumed that the timeline only provides k0 or k2 time slots for the transition time (for downlink and uplink respectively) (e.g., the k0 and / or k2 delays can be hard-coded into the wireless communication system and / or configured based on the capabilities of UE 115). Therefore, the first technique may not be able to configure relatively long k0 and / or k2 times to accommodate modem warm-up times. As described herein, in some cases, other techniques for triggering BWP handover using DCI signaling can avoid some of these additional induced delays and provide the flexibility to configure additional modem warm-up times.

[0141] In some cases, the techniques described herein can provide improvements over the first techniques described herein. For example, in some cases, to accommodate modem warm-up time, constraints can be applied such that UE 115 does not monitor PDCCH after receiving a DCI indicating a BWP handover in a later time slot. In some cases (e.g., in the case of additional downlink scheduling), the later time slot used for this purpose can be one or more time slots immediately following the PDSCH scheduled by the current DCI (i.e., the one or more time slots include the k0 delay plus the PDSCH transmission time plus the transition time). Thus, UE 115 can receive grants during this time period, in which case UE 115 can apply the current k0 and / or k2 delays to the current BWP, rather than to a potentially expiring BWP (e.g., a larger BWP) from which the handover is indicated. Alternatively or additionally, UE 115 can restrict the BWP handover DCI to time slot-based scheduling, similarly helping to eliminate this conflict. In some cases, if a PDSCH or PUSCH is scheduled by a previous authorization for the current BWP (i.e., the scheduled transmission occurs before the DCI indicating the BWP handover), UE 115 can still transmit if the scheduled timing is before the BWP transition. In this case, if the scheduled timing is after the BWP transition, the PDSCH / PUSCH can be cancelled.

[0142] In some cases, if the content of a DCI field becomes meaningless (i.e., no longer applicable) after applying transformation rules, the UE 115 may discard the field. This could be the case, for example, if the Sounding Reference Signal (SRS) resource indicator points to a resource that no longer exists. If a field with meaningless content is critical, the UE 115 may determine that the DCI is invalid, in which case the UE 115 may determine whether the BWP ID and k0 and / or k2 fields should still be interpreted.

[0143] Figure 4D An example of uplink and downlink transmission timelines supporting DCI signaling technology for active BWP handover, according to various aspects of this disclosure, is shown. Specifically, Figure 4D An example of downlink transmission timeline 400-d supporting a DCI signaling scheme for BWP handover, according to various aspects of this disclosure, is shown. Figure 4DAn example of uplink transmission timeline 420-c supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is also shown. In some examples, downlink transmission timeline 400-d and uplink transmission timeline 420-c can implement various aspects of wireless communication systems 100 and 200. Downlink transmission timeline 400-d and uplink transmission timeline 420-c illustrate second, third, and fourth techniques for UE 115 to handover between narrow BWP and wide BWP based on control channel signaling from base station 105.

[0144] Downlink transmission timeline 400-d can illustrate an example of a downlink transmission timeline with a delay of k0 = 2 – that is, downlink transmission timeline 400-d shows a transmission with a scheduling delay of one time slot from the control channel until PDSCH 410 can arrive relative to DCI 405. Uplink transmission timeline 420-c can illustrate an example of an uplink transmission timeline with a delay of k2 = 2 – that is, uplink transmission timeline 420-c shows a transmission with a scheduling delay of two time slots from the control channel until PUSCH 425 can be transmitted.

[0145] In a second technique for DCI signaling used to trigger BWP switching, the size of one or more or all DCI bit fields can be determined based on the current BWP. In this case, data can be transmitted using a BWP format as indicated by the corresponding BWP index. If the BWP index used for the upcoming time slot enables a different BWP format, a BWP switching can be triggered to switch to the target BWP (e.g., from a narrow BWP to a wide BWP, or vice versa). In this case, the DCI of the current BWP can schedule data transmission for the upcoming time slot with a different DCI format (e.g., the DCI of the current time slot of a narrow BWP can be scheduled to follow the large data transmission in the upcoming time slot with a wide BWP after the control channel of that upcoming time slot). However, in some cases, the DCI may include bit fields with a bit field size different from the bit field size of the target BWP. For example, the DCI may include fields with a bit field size of 9 (e.g., 9 bits), while the target BWP may support a size of 16 (e.g., 16 bits). In this case, a transformation rule can be applied to the DCI field, to which zero padding can be applied, to match the size of the target BWP. Alternatively, the DCI can have a bit field size larger than the bit field size supported by the target BWP. In this case, one or more bit fields of the DCI can be truncated (e.g., by using the most significant bit (MSB)) so that the bit field size of the truncated DCI matches the bit field size of the target BWP.

[0146] In the second technique for DCI signaling used to trigger BWP handover, a delay of k2=2 can provide a delay relatively similar to that of k2=0 (as described in the first technique for DCI signaling used to trigger BWP handover). Furthermore, according to the second technique, all PDCCH or PUCCH processing performed within a single time slot (e.g., in half a time slot or less), software delays, and transitions (e.g., also in half a time slot or less) can be performed.

[0147] Alternatively, a third technique for triggering BWP switching using DCI signaling can be performed similarly to that described for the second technique. However, according to the third technique, the DCI size can be determined globally based on the maximum DCI size among all configured BWPs. Therefore, a transformation can be applied to zero-padded the DCI to the determined maximum DCI size. The size and position of the DCI field can then be specifically interpreted based on the target BWP. In some cases, the third technique can be based on equalization of the entire DCI size. In some cases, the third technique can be combined with the second technique described herein (i.e., creating a hybrid technique) for cross-BWP scheduling. This will be described in further detail below, as referenced. Figure 5-6 As described.

[0148] Alternatively, in a fourth technique for DCI signaling used to trigger BWP switching, the size of one or more or all DCI bit fields can be determined based on the current BWP. In this case, data is transmitted using the BWP format indicated by the corresponding BWP index. If the BWP index enables a different BWP format, a BWP switching can be triggered to switch to the target BWP (e.g., from a narrow BWP to a wide BWP, or vice versa). However, according to the fourth technique, if the DCI includes bit fields with bit field sizes different from those of the target BWP, the DCI of the current time slot may not schedule data transmission for the upcoming time slot and may not apply zero-padding or truncation as described herein with respect to the second technique. In this case, an assumption can be made that BWP switching can occur without scheduled data, and that the DCI of the upcoming time slot provides scheduling information for the data in that time slot. As described herein with respect to the second technique for DCI signaling used to trigger BWP switching, according to the fourth technique, a delay of k2=2 can provide a delay relatively similar to a delay of k2=0 according to the first technique for DCI signaling used to trigger BWP switching. That is, the fourth technique can provide similar latency to the second technique, but without scheduled payload. Furthermore, according to the fourth technique, all PDCCH or PUCCH processing can be performed within a single time slot (e.g., in half a time slot or less), software latency can be added, and transitions (e.g., also in half a time slot or less) can be implemented.

[0149] Figure 4E Examples of uplink and downlink transmission timelines supporting DCI signaling technologies for active BWP handover, according to various aspects of this disclosure, are shown. Specifically, Figure 4E An example of downlink transmission timeline 400-e supporting a DCI signaling scheme for BWP handover, in accordance with various aspects of this disclosure, is shown. Figure 4E An example of uplink transmission timeline 420-d supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is also shown. In some examples, downlink transmission timeline 400-e and uplink transmission timeline 420-d can implement various aspects of wireless communication systems 100 and 200. Downlink transmission timeline 400-e and uplink transmission timeline 420-d illustrate another example of the fourth and fifth techniques described herein for UE 115 to handover between narrow BWP and wide BWP based on control channel signaling from base station 105.

[0150] Downlink transmission timeline 400-d can illustrate an example of a downlink transmission timeline with a delay of k0 = 2 – that is, downlink transmission timeline 400-e shows a transmission with a scheduling delay of one time slot from the control channel until PDSCH 410 can arrive relative to DCI 405. Uplink transmission timeline 420-c can illustrate an example of an uplink transmission timeline with a delay of k2 = 2 – that is, uplink transmission timeline 420-b shows a transmission with a scheduling delay of two time slots from the control channel until PUSCH 425 can arrive relative to DCI 405.

[0151] Regarding the fourth technology, see the references in this article. Figure 4D Instead of applying the aforementioned transformation, an empty allocation can be applied, indicating that the DCI in the upcoming control channel of the upcoming time slot will provide scheduling information. That is, instead of the current time slot authorizing data for the upcoming time slot, the DCI of the upcoming time slot can have full scheduling capabilities and can accordingly schedule data transmission for its own time slot. In some cases, for timing consistency in the empty allocation case, the same timeline can be assumed during the PUSCH and / or PDSCH transmission times, but without corresponding payloads.

[0152] Alternatively, the fifth technique for DCI signaling to trigger BWP handover can be performed similarly to that described for the fourth technique. However, according to the fifth technique, the UE can always perform BWP handover without scheduled data transmission for the upcoming time slot. That is, according to the fifth technique, empty allocation can be used for the DCI of each control channel for the upcoming time slot, such that each DCI will schedule data transmission for its own time slot. According to the fifth technique, a delay of k2=2 can provide a timing similar to or smaller than the timing of k2=0 according to the first technique for DCI signaling to trigger BWP handover. That is, the fifth technique can provide a delay similar to the second technique, but without scheduled payload. Furthermore, according to the fifth technique, all PDCCH or PUCCH processing performed within a single time slot (e.g., in half a time slot or less), software delays, and transitions (e.g., also in half a time slot or less) can be performed.

[0153] Figure 5 An example of a transmission scheme 500 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, transmission scheme 500 may implement various aspects of wireless communication systems 100 and 200. Transmission scheme 500 shows DCI fields according to the transition from the first BWP to the second BWP.

[0154] Transmission scheme 500 includes current DCI fields 505-a, 505-b, 505-c, and 505-d, which may be examples of DCI configured according to a first BWP format. The first BWP format may be, for example, a narrow BWP format. Transmission scheme 500 includes target DCI fields 510-a, 510-b, 510-c, and 510-d, which may be examples of DCI configured according to a second BWP format. The second BWP format may be, for example, the narrow BWP format that UE 115 wants to switch to.

[0155] The transformation rule can first be applied to the current DCI field 505-a (e.g., a packaged set of DCI fields). For example, when transforming a smaller resource allocation to a larger resource allocation, such as... Figure 5As shown (e.g., when a resource allocation based on a narrow BWP is scheduled to switch to a wide BWP), techniques can be provided for configuring a BWP of a first format (e.g., type 0) and a BWP of a second format (e.g., type 1). In this case, the MSB can be used to indicate which type to use. Furthermore, in some cases, zero padding may not be used. Instead, a type 1 allocation can be, for example (assuming zero padding of the MSB): a large resource allocation of 16 bits corresponding to 270 PRBs; and a small resource allocation of 9 bits corresponding to 25 PRBs. In this case, to schedule a relatively large number of PRBs, a relatively large Resource Indicator Value (RIV) can be used, for example, a value equal to 511 represented in 9 bits, which can be considered a 16-bit value. In some cases, the number of PRBs can be set as follows: Floor(511 / 270) + 1 = 2. In some cases, the starting PRB can be set as follows: 511 mod 270 = 241.

[0156] In some cases, mapping rules can also be defined. In some cases, resource allocation can be interpreted based on the current BWP (e.g., a narrow BWP), and then the resource can be physically converted to a new BWP. In some cases, fixed alignment rules can be defined (e.g., aligned to a smaller frequency, or aligned to a smaller frequency). Alternatively, the physical location of a resource can be directly mapped to its physical location, and if it is not entirely within the overlap, it can be interpreted as an empty allocation. Alternatively, a combination of the previous two methods can be applied; for example, direct mapping can be used if the PRB is entirely within the overlap, otherwise fixed alignment rules can be used.

[0157] Alternatively, for example, when transforming a larger resource allocation into a smaller one (e.g., scheduling a narrow BWP based on a wide BWP), truncation can be applied when both type 0 and type 1 are configured and the MSB is used to indicate the type. In some cases, base station 105 can ensure that the value of each truncated field is zero (or another predetermined value), allowing UE 115 to perform error checking.

[0158] In some cases, according to the described techniques for DCI signaling used to trigger BWP handover, the network (e.g., via base station 105) can support the transition from a larger BWP to a smaller BWP by ensuring that the transformation (e.g., resource allocation truncation) results in an appropriate allocation of the DCI size for the BWP size. However, in some cases, not all PRBs of the BWP can be addressed via the transformation for a transition from a smaller BWP to a larger BWP. For example, the network may allocate allocation options other than those it can determine are appropriate. To remedy this potential conflict, the techniques described herein describe the use of empty allocations. That is, the resource allocation field can be filled with an empty allocation, and when UE 115 detects an empty allocation, UE 115 can ignore other DCI fields, some other defined fields (e.g., BWP ID, which is used to trigger BWP handover; and the k0 and / or k2 parameters in the time-domain resource allocation, which are used to determine the expected timing for the BWP handover). In some cases, further restrictions can be applied, wherein an empty allocation can be indicated in the DCI indicating the BWP handover. In some cases, these transformation considerations can be applied to DCI field 505, resource allocation field, and / or other fields within the DCI.

[0159] In some cases, an algorithm can be provided during BWP configuration or during RRC reconfiguration, affecting parameters that are related to the DCI field size. For each configured BWP, the DCI payload size can be calculated, and the size of a subset of the payload containing the non-transformable field 515 can be represented as X(i), where i = 0.numConfigudBWPs-1.

[0160] like Figure 5 As shown, the current DCI field 505-a can be configured according to the narrow BWP format, and the target DCI field 510 can be configured according to the wide BWP format. The current DCI field 505-a and the current DCI field 505-b can be examples of packaged DCI fields in the DCI format before the transformation rules are applied.

[0161] In some cases, the described techniques (e.g., as referenced) Figure 4E The third technique described herein can be based on full DCI size equalization. In some cases, the third technique can be combined with the second technique described herein (i.e., creating a hybrid technique) for use across BWP scheduling. This can, for example, avoid potential bit waste caused by DCI size differences on configured BWPs due to the application of a "one size fits all" transformation rule.

[0162] In some examples, a specific DCI field can be designated as "transformable" or "non-transformable." A transformable field can refer to the ability to transform a field with fewer bits into a field with more bits. A non-transformable field can refer to a field where the zero-padding rule does not apply. That is, a non-transformable field can correspond to a field that is an exception to the transformation rule and is therefore non-transformable. A transformable DCI field can be, for example, an empty set (i.e., all fields are non-transformable), or it can be the entire set of DCI fields. In some cases, whether a field is transformable can be configured via higher-layer signaling. In some cases, the truncation rule for transforming a field with more bits into a field with fewer bits can always be "transformable."

[0163] In some cases, as shown in the table below, the size can be defined according to one of two formats, depending on the transformation rules of the BWP's DCI field.

[0164] Table 1. Format 1_1

[0165]

[0166]

[0167] Table 2. Format 0_1

[0168]

[0169]

[0170] For frequency domain resource allocation, the transformation rules can be defined according to Table 3:

[0171] Table 3. Frequency Domain Resource Allocation

[0172]

[0173] In the first example, each field, except those that may be directly related to bandwidth (e.g., frequency domain resource allocation), can have the same size from the current DCI field 505 to the target DCI field 510. The current DCI field 505-b and the target DCI field 510-b can be an example where the total size of the non-transformable field 515-a of the current DCI field 505-b is equal to the total size of the non-transformable fields of the target DCI field 510-b. The current DCI field 505-b and the target DCI field 510-b can also include a transformable field 520-a (e.g., a bit field). When the size of the non-transformable field 515-a of the current DCI field 505-b matches the size of the non-transformable field 515-a of the target DCI field 510-b, the DCI field size and content can be interpreted according to the BWP format of the target DCI field 510-b. This is in... Figure 5 The diagram illustrates the transformation of the current DCI field 505-b into the target DCI field 510-b. In some cases, this technique can facilitate cross-BWP scheduling.

[0174] However, in some cases, DCI field sizes may not match, in which case the truncation or zero-padding rules described in this article can be applied. For some fields, such as time-domain resource allocation, a smaller field size can support fewer addressable rows in their corresponding table. In such cases, the network can typically be configured across the configured BWP application configuration in lower indexed rows.

[0175] In some cases, the described techniques for triggering DCI signaling for BWP handover can provide relatively improved robustness of DCI pruning and a relatively reduced probability of false detection. When a larger DCI field is truncated into a smaller DCI field (e.g., after a transition from a wide BWP to a narrow BWP), base station 105 can ensure that the content of each truncated field has a zero value (or any other predetermined value). In this case, if UE 115 detects a non-zero value in a truncated field, the UE can determine that the truncating process may be invalid and therefore may not process the DCI as valid.

[0176] The current DCI field 505-c and the target DCI field 510-c can be illustrated as follows: the size of the non-transformable field 515-b is mismatched, but the size of the transformable field 520-b can be modified using transformation rules. In this case, when X(i) is not the same across all configured BWPs (i.e., i = 0.numConfigudBWPs-1), partial size equalization can be applied. For example, for i = 0.numConfigudBWPs-1, for BWP oi, the DCI payload size can be increased by the difference of max{X} - X(i).

[0177] In the case of the current DCI field 505-c to the target DCI field 510-c, the total size of the non-transformable field 515-b of the current DCI field 505-c can be padded to make the size of the non-transformable field 515-b equal to that of the target DCI field 510-c. This is illustrated by adding padding bits 525. However, in some cases, for a BWP with the largest size, this difference can be zero, which can make the size of the payload subset containing only the non-transformable field 515-b equal.

[0178] Alternatively, a minimum size threshold can be defined for each of the non-transformable fields 515 of the current DCI field 505-b and the target DCI field 510-b. DCI content with at least the minimum size threshold defined for the corresponding field can then be defined as compatible with any BWP format. For example, a rate match indicator field can have a size of 0, 1, or 2 bits. If the minimum size threshold for the rate match indicator field is defined as 1 bit, the content of the rate match indicator field can be compatible with a BWP format that nominally requires 2 bits for the rate match indicator field. Similarly, if the minimum size threshold for the rate match indicator field is defined as 2 bits, the content of the rate match indicator field can again be compatible with a BWP format that requires 2 bits for that field. In some cases, the minimum size threshold for a particular DCI can be specified or configured via higher-layer signaling.

[0179] Alternatively, in some cases where the size of the non-transformable field 515 is mismatched, scheduling may not be applied for BWP switching from one BWP format to another. This can be achieved by... Figure 5 The diagram illustrates the current DCI field 505-d to the target DCI field 510-d. The current DCI field 505-d and the target DCI field 510-d may also include a transformable field 520-c. In this case, since X(a) (i.e., the size of the non-transformable bits of the current DCI field 505-d) can be smaller than X(b) (i.e., the size of the non-transformable bits of the target DCI field 510-d), the network can be expected to avoid scheduling (e.g., providing an empty allocation), but BWP handover can still be triggered. In this case, processing of the non-transformable field 515-c can be skipped during each time slot operation. Alternatively, the resource allocation field can be filled with an empty allocation, and when UE 115 detects an empty allocation, UE 115 can ignore other DCI fields, some other defined fields (e.g., the BWP ID, which is used to trigger BWP handover; and the k0 and / or k2 parameters in the time-domain resource allocation, which are used to determine the expected timing of the BWP handover). In some cases, further restrictions may be applied, where empty allocation can only be indicated in the DCI that indicates BWP switching.

[0180] Figure 6 An example of a processing scheme 600 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, processing scheme 600 can implement various aspects of wireless communication systems 100 and 200. Processing scheme 600 can illustrate the DCI field according to the transition from the first BWP to the second BWP.

[0181] Processing scheme 600 includes current DCI fields 605-a and 605-b, which may be examples of DCI configured according to a first BWP format. The first BWP format may be, for example, a narrow BWP format. Processing scheme 600 includes target DCI fields 610-a and 610-b, which may be examples of DCI configured according to a second BWP format, and may correspond to the corresponding current DCI field 605. The second BWP format may be, for example, the narrow BWP format that UE 115 wants to switch to.

[0182] In some cases, for DCI processing, signaling notifications can be sent within the DCI regarding BWP changes from the current BWP to the new BWP, for example, for cross-BWP scheduling. In this case, each DCI field can be processed. If the field is transformable, its size can be determined based on the current BWP, and transformation rules can be applied to the field for interpretation and transformation for the new BWP. If the field is not transformable, its size can be determined based on the new BWP, and the field content can be interpreted according to the new BWP. Otherwise (e.g., in the case of same-BWP scheduling), there may be no BWP change, and the DCI field can be processed according to the current BWP.

[0183] like Figure 6 As shown, the current DCI field 605-a can be switched to the target DCI field 610-a. The transformable bits of the current DCI field 605-a can be parsed to obtain the parsed DCI field 615-a. The parsed DCI field 615-a can then be transformed to obtain the transformed DCI field 620-a. The size of the non-transformable bits of the current DCI field 605-a can be determined based on the target DCI field 610-a, and their corresponding contents can be interpreted according to the target BWP. This could be an example of a transformation used for cross-scheduling switching from a narrow BWP to a wide BWP.

[0184] Similarly, the current DCI field 605-b can be switched to the target DCI field 610-b. The transformable bits of the current DCI field 605-b can be parsed to obtain the parsed DCI field 615-b. The parsed DCI field 615-b can then be transformed to obtain the transformed DCI field 620-b. The size of the non-transformable bits of the current DCI field 605-b can be determined based on the target DCI field 610-b, and their corresponding contents can be interpreted according to the target BWP. This could be an example of a transformation used for cross-scheduling switching from a wide BWP to a narrow BWP.

[0185] Figure 7An example of process flow 700 in a system supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. In some examples, process flow 700 may implement various aspects of wireless communication system 100. For example, process flow 700 includes UE 115-b and base station 105-b, which may be references Figure 1 Examples of the corresponding devices are described. The process flow can illustrate an example of a DCI configuration that enables efficient updating of DCI fields between different BWPs. For example, a DCI can be configured with a set of transformable DCI fields and a set of non-transformable fields, and UE 115-b can update the content of each DCI field in the DCI based on whether the DCI field is transformable or non-transformable.

[0186] UE 115-b can operate in multiple BWPs, and at 705, it can operate in the first BWP. For example, the first BWP can enable UE 115-b to monitor a relatively narrow BWP for energy saving. In other examples, UE 115-b can operate in the first BWP to receive or transmit a relatively large amount of data, and the first BWP can have an appropriate width sufficient to enable such data reception / transmission.

[0187] At 710, base station 105-b can determine to switch the operation of UE 115-b from the first BWP to the second BWP. For example, base station 105-b may have data to be transmitted to UE 115-b in the second BWP, which has a bandwidth greater than that of the first BWP. Alternatively, base station 105-b may complete the data transmission to UE 115-b in the first BWP, and UE 115-b can therefore save energy by tuning its radio unit to the narrower second BWP.

[0188] At point 715, base station 105-b can generate a DCI with multiple DCI fields, each of which can have a corresponding first size based on a first BWP. Base station 105-b can then configure the DCI using a set of transformable DCI fields and a set of non-transformable DCI fields. In some cases, the content of the transformable fields included in the first BWP can be updated via transformation rules to a DCI field having a corresponding second size in a second BWP. Conversely, the content of the non-transformable DCI fields in the first BWP cannot be updated via transformation rules. In some cases, the transformable fields can be the entire set of DCI fields, or they can be an empty set (e.g., non-transformable fields include the entire set of DCI fields).

[0189] In some examples, base station 105-b may optionally configure the total first size of the set of non-transformable DCI fields in the first BWP to be different from the total second size of the set of non-transformable DCI fields in the second BWP, wherein the total second size is greater than the total first size. In this case, base station 105-b may insert a partially size-equalized bit set into the first BWP, which includes the difference between the total first size and the total second size, wherein the total size of this partially size-equalized bit set and the set of non-transformable DCI fields used for the first BWP is equal to the total second size of the set of non-transformable DCI fields in the second BWP. However, in some cases, multiple BWPs may be configured for UE 115-b, and base station 105-b may therefore configure the total first size of the set of non-transformable DCI fields in the first BWP to be different from at least one corresponding total size of the corresponding set of non-transformable DCI fields in the multiple BWPs. As a result, base station 105-b can insert a partially size-equalized bit set into the first BWP. This partially size-equalized bit set includes the difference between the maximum corresponding total size and the total first size, such that the total size of this partially size-equalized bit set and the non-transformable DCI field set in the first BWP can be equal to the maximum corresponding total size.

[0190] Alternatively, base station 105-b may configure the total first size of the non-transformable DCI field set in the first BWP to be different from the total second size of the non-transformable DCI field set in the second BWP, wherein the total second size is smaller than the total first size. In this case, base station 105-b may insert a portion of the size-equalized bit set into the second BWP, the portion of the size-equalized bit set including the difference between the total first size and the total second size, wherein the total size of the portion of the size-equalized bit set and the non-transformable DCI field set of the first BWP is equal to the total second size of the non-transformable DCI field set in the second BWP. In the case of multiple BWPs, base station 105-b may configure the total second size of the non-transformable DCI field set in the second BWP to be different from at least one corresponding total size of the corresponding non-transformable DCI field set in the multiple BWPs. Base station 105-b can then insert a partially size-equalized bit set into the second BWP. This partially size-equalized bit set includes the difference between the maximum total response size and the total second size, such that the total size of this partially size-equalized bit set and the set of non-transformable DCI fields in the second BWP can be equal to the maximum total response size. In any of the examples above, the size of the set of non-transformable DCI fields across different BWPs can be equalized, allowing UE 115-b to update the content of the DCI fields in the new BWP.

[0191] In other examples, base station 105-b can configure a minimum size for each DCI field in the set of non-mutable DCI fields, wherein the content within the DCI field with the minimum size can be updated to the DCI fields in the second BWP. Alternatively, base station 105-b can configure the total first size of the set of non-mutable DCI fields in the first BWP to be smaller than the total second size of the set of non-mutable DCI fields in the second BWP, and send empty allocations (e.g., within DCIs) for the second BWP based on the total first size being smaller than the total second size.

[0192] At 720, while UE 115-b is operating in the first BWP, base station 105-b transmits a DCI, and UE 115-b receives the DCI. Additionally, UE 115-b can receive, as part of the DCI, an indication of switching from operation in the first BWP to operation in the second BWP. At 725, UE 115-b can identify a configured set of transformable DCI fields from multiple DCI fields, the content of which in the first BWP can be updated via transformation rules to a DCI field of a corresponding second size in the second BWP. UE 115-b can also identify a configured set of non-transformable DCI fields from multiple DCI fields, the content of which in the first BWP cannot be updated via transformation rules to a DCI field of a corresponding second size in the second BWP.

[0193] After identifying the convertible and non-convertible DCI fields, at 730, UE 115-b may optionally determine whether the total first size of the set of non-convertible DCI fields in the first BWP is different from the total second size of the set of non-convertible DCI fields in the second BWP. If the total size of the non-convertible DCI fields is the same across multiple BWPs, UE 115-b may continue to process the DCI fields based on the second BWP. In other cases, there may be sets of non-convertible DCI fields with sizes different from other sets of non-convertible DCI fields. Therefore, UE 115-b can utilize various DCI configurations to interpret the DCI used for the second BWP.

[0194] For example, at 735, UE 115-b can identify a partially equalized bit set in either the first BWP or the second BWP. In this case, UE 115-b can update the contents of the non-transformable DCI field set based on this partially equalized bit set. UE 115-b can also determine the non-transformable DCI field set based on the second BWP to identify the corresponding second size, order, packing, content, or a combination thereof of the DCI fields.

[0195] Alternatively or concurrently, at 740, UE 115-b may identify an empty allocation for the second BWP in the DCI. In some examples, the empty allocation may be based on the total first size being less than the total second size. Upon receiving an empty allocation, UE 115-b may switch operation from the first BWP to the second BWP based on the empty allocation, avoiding determination of at least the contents of the non-transformable DCI field set. In some cases, identifying an empty allocation for the second BWP may include detecting an empty allocation within the resource allocation field of multiple DCI fields. In some cases, when UE 115-b detects an empty allocation in the resource allocation field from multiple DCI fields, UE 115-b may also detect a BWP ID indicating a switch from the first BWP to the second BWP. In some examples, UE 115-b may also determine a timing value indicating the time difference between the received DCI and the start of the second BWP (which may be implicitly or explicitly indicated), and avoid detecting the remaining DCI field set from multiple DCI fields based on the detected empty allocation.

[0196] In some examples, at 745, UE 115-b can identify the minimum size of each DCI field in the set of non-transformable DCI fields. In this case, the content within the DCI field with the minimum size can be updated to the DCI field in the second BWP. In some cases, the size of the content within the DCI is a static size greater than or equal to that minimum size (e.g., some content can always be configured to have the same size to eliminate errors when the content is interpreted for different BWPs).

[0197] At 750, UE 115-b can then determine, at least in part, the updated content of multiple DCI fields to be applied to the second BWP based on whether each DCI field is a transformable DCI field or a non-transformable DCI field. For example, UE 115-b can update the content of the transformable DCI field set via transformation rules and determine the updated content of the transformable DCI field set based on the second BWP. In some examples, UE 115-b can identify a DCI field to be truncated from the transformable DCI field set based on the fact that a certain DCI field in the transformable DCI field set has a corresponding first size in the first BWP that is greater than a corresponding second size in the second BWP. In this case, UE 115-b can determine that the content within the DCI field has a predetermined value (e.g., zero) and can truncate the DCI field at least in part based on the determination that the content has a predetermined value. In some cases, UE 115-b may assume that base station 105-b configures the DCI field to be truncated with a predetermined value, and if UE 115-b determines that the content is not equal to the predetermined value, it may determine that the DCI is invalid.

[0198] Figure 8 A block diagram 800 of a wireless device 805 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. The wireless device 805 may be an example of various aspects of a user equipment (UE) 115 as described herein. The wireless device 805 may include a receiver 810, a UE communication manager 815, and a transmitter 820. The wireless device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0199] Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to the DCI signaling scheme used for BWP handover). This information can be transmitted to other components of the device. Receiver 810 can be a reference. Figure 11 Examples of various aspects of the transceiver 1135 are described. The receiver 810 can utilize a single antenna or a set of antennas.

[0200] UE Communication Manager 815 can be used as a reference. Figure 11Examples of various aspects of the described UE communication manager 1115. At least some of the UE communication manager 815 and / or its various sub-components can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functionality of at least some of the UE communication manager 815 and / or its various sub-components can be performed by a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this disclosure.

[0201] At least some of the UE communication manager 815 and / or its various sub-components may be physically located in various locations, including being distributed such that portions of the functionality are implemented by one or more physical devices in different physical locations. In some examples, according to various aspects of this disclosure, at least some of the UE communication manager 815 and / or its various sub-components may be separate and distinct components. In other examples, according to various aspects of this disclosure, at least some of the UE communication manager 815 and / or its various sub-components may be combined with one or more other hardware components, including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0202] The UE communication manager 815 can receive a DCI with a set of DCI fields from the base station 105 while operating in the first BWP, each DCI field in the set having a corresponding first size based on the first BWP. In some cases, the UE communication manager 815 can receive, as part of the DCI, an indication that the UE 115 will switch from operating in the first BWP to operating in the second BWP. Additionally, the UE communication manager 815 can: identify a set of transformable DCI fields from the set of DCI fields, the content of which in the first BWP can be updated via transformation rules to DCI fields having a corresponding second size in the second BWP; and identify a set of non-transformable DCI fields from the set of DCI fields, the content of which in the first BWP cannot be updated via transformation rules to DCI fields having a corresponding second size in the second BWP. The UE communication manager 815 can determine the update content of the DCI field set to apply to the second BWP based on whether each DCI field is a transformable or non-transformable DCI field.

[0203] In some examples, the UE communication manager 815 may also: during the first TTI, while operating in the first BWP, receive a DCI from the base station 105; and receive, as part of the DCI, an indication that the UE 115 will switch from operating in the first BWP to operating in the second BWP. The UE communication manager 815 may also determine that the second BWP begins at a second TTI following the first TTI, and trigger a handover from the first BWP to the second BWP based on the received DCI, thereby avoiding PDCCH monitoring.

[0204] Transmitter 820 can transmit signals generated by other components of the device. In some examples, transmitter 820 can be co-located with receiver 810 in a transceiver module. For example, transmitter 820 can be a reference... Figure 11 Examples of various aspects of the transceiver 1135 are described. The transmitter 820 can utilize a single antenna or a set of antennas.

[0205] Figure 9 A block diagram 900 is shown of a wireless device 905 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure. The wireless device 905 may be as described in the reference. Figure 8 Examples of various aspects of the described wireless device 805 or UE 115. Wireless device 905 may include a receiver 910, a UE communication manager 915, and a transmitter 920. Wireless device 905 may also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0206] Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to the DCI signaling scheme used for BWP handover). This information can be transmitted to other components of the device. Receiver 910 can serve as a reference. Figure 11 Examples of various aspects of the transceiver 1135 are described. The receiver 910 can utilize a single antenna or a set of antennas.

[0207] UE Communication Manager 915 can be used as a reference. Figure 11 Examples of various aspects of the described UE communication manager 915 are provided. The UE communication manager 915 may also include a UE DCI manager 925, a bandwidth portion switching manager 930, a DCI field identification component 935, and a content manager 940.

[0208] The UE DCI manager 925 can receive a DCI with a set of DCI fields from the base station 105 while operating in the first BWP, each DCI field in the set having a corresponding first size based on the first BWP. In some examples, the UE DCI manager 925 can identify a partially size-equalized bit set in the first BWP that includes the difference between the total first size and the total second size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the total second size of the non-transformable DCI field set in the second BWP. Alternatively or additionally, the UE DCI manager 925 can identify a partially size-equalized bit set in the second BWP that includes the difference between the total first size and the total second size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the total second size of the non-transformable DCI field set in the second BWP.

[0209] In some examples, the UE DCI manager 925 can identify a partially size-equalized bit set in the first BWP, which includes the difference between the maximum corresponding total size and the total first size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the maximum corresponding total size. Alternatively, the UE DCI manager 925 can identify a partially size-equalized bit set in the second BWP, which includes the difference between the maximum corresponding total size and the total second size, wherein the total size of the partially size-equalized bit set in the second BWP and the non-transformable DCI field set is equal to the maximum corresponding total size. In some examples, the UE DCI manager 925 can avoid detecting the remaining DCI field set from the DCI field set based on detected empty allocations. In some cases, the UE DCI manager 925 can receive DCI from the base station 105 during the first TTI, while operating in the first BWP. In some examples, the UE DCI manager 925 can trigger a switch from the first BWP to the second BWP based on the received DCI to avoid monitoring the PDCCH.

[0210] The bandwidth portion switching manager 930 can receive, as part of the DCI, an indication that UE 115 will switch from operating in a first bandwidth portion to operating in a second bandwidth portion. In some cases, the bandwidth portion switching manager 930 can switch operation from the first bandwidth portion to the second bandwidth portion based on an empty allocation. In other examples, the bandwidth portion switching manager 930 can detect the bandwidth portion ID indicating the switch from the first bandwidth portion to the second bandwidth portion and can determine a timing value indicating the time difference between the received DCI and the start of the second bandwidth portion. In some examples, the bandwidth portion switching manager 930 can determine that the second bandwidth portion begins at a second TTI following the first TTI. In some cases, the second TTI immediately follows a PDSCH transmission scheduled by the received DCI or a PUSCH transmission scheduled by the received DCI.

[0211] The DCI field identification component 935 can identify a set of transformable DCI fields from the DCI field set. The content of the transformable DCI fields in the first BWP can be updated to a DCI field of a corresponding second size in the second BWP via transformation rules. Additionally, the DCI field identification component 935 can identify a set of non-transformable DCI fields from the DCI field set. The content of the non-transformable DCI fields in the first BWP cannot be updated to a DCI field of a corresponding second size in the second BWP via transformation rules. In some cases, the DCI field identification component 935 can determine the set of non-transformable DCI fields based on the second BWP to identify the corresponding second size, order, packing, content, or combination thereof of the DCI fields.

[0212] Content Manager 940 can determine the updated content of the DCI field set to apply to the second BWP based on whether each DCI field is a transformable DCI field or a non-transformable DCI field. In some examples, Content Manager 940 can update the content of the non-transformable DCI field set based on a partially size-equalized bit set. In some cases, Content Manager 940 can avoid determining the content of at least the non-transformable DCI field set. Alternatively or alternatively, Content Manager 940 can update the content of the transformable DCI field set via transformation rules and determine the updated content of the transformable DCI field set based on the second BWP.

[0213] Transmitter 920 can transmit signals generated by other components of the device. In some examples, transmitter 920 can be co-located with receiver 910 in a transceiver module. For example, transmitter 920 can be a reference... Figure 11 Examples of various aspects of the transceiver 1135 are described. The transmitter 920 can utilize a single antenna or a set of antennas.

[0214] Figure 10 A block diagram 1000 is shown of a UE communication manager 1015 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure. The UE communication manager 1015 may be a reference... Figure 8 , 9 Examples of aspects of the UE communication manager 815, UE communication manager 915, or UE communication manager 1115 described in section 11. The UE communication manager 1015 may include a UE DCI manager 1020, a bandwidth portion switching manager 1025, a DCI field identification component 1030, a content manager 1035, a DCI field size manager 1040, an allocation component 1045, and a DCI truncation manager 1050. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0215] The UE DCI manager 1020 can receive a DCI with a set of DCI fields from the base station 105 while operating in the first BWP, each DCI field in the set having a corresponding first size based on the first BWP. In some examples, the UE DCI manager 1020 can identify a partially size-equalized bit set in the first BWP, which includes the difference between a total first size and a total second size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the total second size of the non-transformable DCI field set in the second BWP. Alternatively or additionally, the UE DCI manager 1020 can identify a partially size-equalized bit set in the second BWP, which includes the difference between a total first size and a total second size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the total second size of the non-transformable DCI field set in the second BWP.

[0216] In some examples, the UE DCI manager 1020 may identify a partially size-equalized bit set in a first BWP, which includes the difference between the maximum corresponding total size and the total first size, wherein the total size of the partially size-equalized bit set in the first BWP and the non-transformable DCI field set is equal to the maximum corresponding total size. Alternatively, the UE DCI manager 1020 may identify a partially size-equalized bit set in a second BWP, which includes the difference between the maximum corresponding total size and the total second size, wherein the total size of the partially size-equalized bit set in the second BWP and the non-transformable DCI field set is equal to the maximum corresponding total size. In some examples, the UE DCI manager 1020 may avoid detecting the remaining DCI field set from the DCI field set based on detected empty allocations. In some cases, the UE DCI manager 1020 may receive DCI from the base station 105 during the first TTI, while operating in the first BWP. In some examples, the UE DCI manager 1020 can trigger a switch from the first BWP to the second BWP based on the received DCI to avoid monitoring the PDCCH.

[0217] The bandwidth portion switching manager 1025 can receive, as part of the DCI, an indication that the UE 115 will switch from operating in the first BWP to operating in the second BWP. In some cases, the bandwidth portion switching manager 1025 can switch operation from the first BWP to the second BWP based on an empty allocation. In other examples, the bandwidth portion switching manager 1025 can detect the BWP ID indicating the switch from the first BWP to the second BWP and can determine a timing value indicating the time difference between the received DCI and the start of the second bandwidth portion. In some examples, the bandwidth portion switching manager 1025 can determine that the second BWP starts at a second TTI following the first TTI. In some cases, the second TTI immediately follows a PDSCH transmission scheduled by the received DCI or a PUSCH transmission scheduled by the received DCI.

[0218] The DCI field identification component 1030 can identify a set of transformable DCI fields from the DCI field set. The content of the transformable DCI fields in the first BWP can be updated to a DCI field of a corresponding second size in the second BWP via transformation rules. Additionally, the DCI field identification component 1030 can identify a set of immutable DCI fields from the DCI field set. The content of the immutable DCI fields in the first BWP cannot be updated to a DCI field of a corresponding second size in the second BWP via transformation rules. In some cases, the DCI field identification component 1030 can determine the set of immutable DCI fields based on the second BWP to identify the corresponding second size, order, packing, content, or combinations thereof of the DCI fields. In some cases, the transformable DCI field set includes the entire set of DCI fields (e.g., the transformable DCI fields are the complete set of DCI fields). Alternatively, the immutable DCI field set includes the entire set of DCI fields (e.g., the transformable DCI fields are an empty set of DCI fields, where the immutable DCI fields are the complete set of DCI fields). In some cases, the configuration of the variable and non-variable DCI field sets is pre-configured. In other cases, the configuration of the variable and non-variable DCI field sets is received via higher-layer signaling (e.g., RRC signaling).

[0219] Content Manager 1035 can determine the updated content of the DCI field set to apply to the second BWP based on whether each DCI field is a transformable DCI field or a non-transformable DCI field. In some examples, Content Manager 1035 can update the content of the non-transformable DCI field set based on a partially size-equalized bit set. In some cases, Content Manager 1035 can avoid determining the content of at least the non-transformable DCI field set. Alternatively or alternatively, Content Manager 1035 can update the content of the transformable DCI field set via transformation rules and determine the updated content of the transformable DCI field set based on the second BWP.

[0220] The DCI field size manager 1040 can determine whether the total first size of the set of non-transformable DCI fields in the first BWP is different from the total second size of the set of non-transformable DCI fields in the second BWP. In this case, the DCI field size manager 1040 can determine that the total first size is different from the total second size, where the total second size is greater than the total first size. In other examples, the DCI field size manager 1040 can determine that the total first size is different from the total second size, where the total second size is less than the total first size. Alternatively or additionally, the DCI field size manager 1040 can determine that the total first size is less than the total second size and determine whether the corresponding total size of each set of non-transformable DCI fields in the BWP set is the same, where the BWP set includes at least the first BWP and the second BWP.

[0221] In some examples, the DCI field size manager 1040 can determine that the total first size of the set of non-mutable DCI fields in the first BWP differs from at least one corresponding total size. In some cases, the DCI field size manager 1040 can determine that the total second size of the set of non-mutable DCI fields in the second BWP differs from at least one corresponding total size, and identify the minimum size of each DCI field in the set of non-mutable DCI fields, wherein the content within the DCI field with the minimum size can be updated to the DCI fields in the second BWP. In some cases, the size of the content within the DCI is a static size greater than or equal to the minimum size.

[0222] The allocation component 1045 can identify an empty allocation for the second BWP within the received DCI based on the fact that the total first size is less than the total second size. Alternatively, the allocation component 1045 can detect an empty allocation within a resource allocation field from the DCI field set. In some cases, identifying an empty allocation for the second BWP includes detecting an empty allocation within a resource allocation field in the DCI field set. In some cases, the empty allocation is based on a DCI-triggered switch from the first BWP to the second BWP.

[0223] The DCI truncation manager 1050 can: identify a DCI field to be truncated from the transformable DCI field set based on the fact that a certain DCI field in the transformable DCI field set has a corresponding first size in the first BWP that is greater than a corresponding second size in the second BWP; determine that the content within the DCI field has a predetermined value; and truncate the high DCI field based on the determination that the content has a predetermined value. In some cases, the predetermined value is zero.

[0224] Figure 11A diagram of a system 1100 including a device 1105 supporting a DCI signaling scheme for BWP handover is shown according to various aspects of this disclosure. Device 1105 may be, for example, as referenced herein. Figure 8 and 9 Examples of wireless devices 805, 905, or UE 115 described may include or include components thereof. Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a UE communication manager 1110, a processor 1120, a memory 1125, software 1130, a transceiver 1135, an antenna 1140, and an I / O controller 1145. These components may communicate electronically via one or more buses (e.g., bus 1110). Device 1105 may communicate wirelessly with one or more base stations 105.

[0225] Processor 1120 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, central processing units (CPUs), microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1120 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1120. Processor 1120 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks supporting DCI signaling schemes for BWP handover).

[0226] Memory 1125 may include random access memory (RAM) and read-only memory (ROM). Memory 1125 may store computer-readable, computer-executable software 1130 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1125 may include a basic input / output system (BIOS), which controls basic hardware or software operations such as interaction with peripheral components or devices.

[0227] Software 1130 may include code for implementing various aspects of this disclosure, including code for supporting a DCI signaling scheme for BWP handover. Software 1130 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, software 1130 may not be directly executable by a processor, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0228] Transceiver 1135 can communicate bidirectionally via one or more antennas, wired or wireless links as described herein. For example, transceiver 1135 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1135 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna. In some cases, the wireless device may include a single antenna 1140. However, in some cases, the device may have more than one antenna 1140, which is capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0229] I / O controller 1145 can manage the input and output signals of device 1105. I / O controller 1145 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1145 can represent a physical connection or port to an external peripheral component. In some cases, I / O controller 1145 can utilize, for example... The operating system or other known operating system. In other cases, the I / O controller 1145 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1145 may be implemented as part of a processor. In some cases, a user may interact with device 1105 via the I / O controller 1145 or hardware components controlled by the I / O controller 1145.

[0230] Figure 12 A block diagram 1200 of a wireless device 1205 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Wireless device 1205 may be an example of various aspects of base station 105 as described herein. Wireless device 1205 may include a receiver 1210, a base station communication manager 1215, and a transmitter 1220. Wireless device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0231] Receiver 1210 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to the DCI signaling scheme used for BWP handover). The information can be transmitted to other components of the device. Receiver 1210 can be a reference. Figure 15 Examples of various aspects of the transceiver 1535 are described. The receiver 1210 can utilize a single antenna or a set of antennas.

[0232] Base station communication manager 1215 can be used as a reference. Figure 15Examples of various aspects of the described base station communication manager 1515. At least some of the base station communication manager 1215 and / or its various sub-components can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functionality of at least some of the base station communication manager 1215 and / or its various sub-components can be performed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0233] At least some of the base station communication manager 1215 and / or its various sub-components may be physically located in various locations, including being distributed such that portions of the functionality are implemented by one or more physical devices in different physical locations. In some examples, according to various aspects of this disclosure, at least some of the base station communication manager 1215 and / or its various sub-components may be separate and distinct components. In other examples, according to various aspects of this disclosure, at least some of the base station communication manager 1215 and / or its various sub-components may be combined with one or more other hardware components, including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0234] The base station communication manager 1215 can determine to switch the operation of UE 115 from a first BWP to a second BWP; generate a DCI with a set of DCI fields, each DCI field in the set having a corresponding first size based on the first BWP; configure the DCI using a set of transformable DCI fields, the content of which the transformable DCI fields have in the first BWP can be updated to a DCI field with a corresponding second size in the second BWP via a transformation rule; configure the DCI using a set of non-transformable DCI fields, the content of which the non-transformable DCI fields have in the first BWP cannot be updated to a DCI field with a corresponding second size in the second BWP via a transformation rule; configure the DCI using an indication that UE 115 will switch from operating in the first BWP to operating in the second BWP; and send the DCI to UE 115.

[0235] Transmitter 1220 can transmit signals generated by other components of the device. In some examples, transmitter 1220 can be co-located with receiver 1210 in a transceiver module. For example, transmitter 1220 can be a reference. Figure 15 Examples of various aspects of the transceiver 1535 are described. The transmitter 1220 can utilize a single antenna or a set of antennas.

[0236] Figure 13A block diagram 1300 of a wireless device 1305 supporting a DCI signaling scheme for BWP handover, according to various aspects of this disclosure, is shown. The wireless device 1305 may be as described in the reference... Figure 12 Examples of various aspects of the described wireless device 1205 or base station 105. Wireless device 1305 may include a receiver 1310, a base station communication manager 1315, and a transmitter 1320. Wireless device 1305 may also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0237] Receiver 1310 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to the DCI signaling scheme used for BWP handover). This information can be transmitted to other components of the device. Receiver 1310 can be a reference. Figure 15 Examples of various aspects of the transceiver 1535 are described. The receiver 1310 may utilize a single antenna or a set of antennas.

[0238] Base station communication manager 1315 can be used as a reference. Figure 15 Examples of various aspects of the described base station communication manager 1315 are provided. The base station communication manager 1315 may also include a bandwidth portion switching component 1325, a base station DCI component 1330, and a DCI configuration manager 1335.

[0239] The bandwidth partial handover component 1325 can: determine to switch the operation of UE 115 from a first BWP to a second BWP; generate a BWP ID indicating the handover from the first BWP to the second BWP; and transmit the BWP ID as part of the DCI. In some cases, a timing value indicating the time difference between the transmitted DCI and the start of the second BWP is based on this DCI. The base station DCI component 1330 can: generate a DCI having a set of DCI fields, each DCI field in the set having a corresponding first size based on the first BWP; and transmit the DCI to UE 115.

[0240] The DCI configuration manager 1335 can configure DCI using a variable DCI field set, the content of which in the first BWP can be updated via transformation rules to have a corresponding second-size DCI field in the second BWP. Alternatively, the DCI configuration manager 1335 can configure DCI using a non-variable DCI field set, the content of which in the first BWP cannot be updated via transformation rules to have a corresponding second-size DCI field in the second BWP. In some cases, the DCI configuration manager 1335 can configure DCI using an instruction regarding the UE 115 switching from operation in the first BWP to operation in the second BWP. In some cases, the variable DCI field set includes the entire set of DCI fields. In some cases, the non-variable DCI field set includes the entire set of DCI fields. In some cases, the configuration of the variable and non-variable DCI field sets is pre-configured. In some cases, the configuration of the variable and non-variable DCI field sets is sent via higher-layer signaling.

[0241] Transmitter 1320 can transmit signals generated by other components of the device. In some examples, transmitter 1320 can be co-located with receiver 1310 in a transceiver module. For example, transmitter 1320 can be a reference... Figure 15 Examples of various aspects of the transceiver 1535 are described. The transmitter 1320 can utilize a single antenna or a set of antennas.

[0242] Figure 14 A block diagram 1400 is shown of a base station communication manager 1415 supporting a DCI signaling scheme for BWP handover according to various aspects of this disclosure. The base station communication manager 1415 may be a reference... Figure 12 , 13 Examples of various aspects of the base station communication manager 1415 described in section 15 are provided. The base station communication manager 1415 may include a bandwidth portion switching component 1420, a base station DCI component 1425, a DCI configuration manager 1430, a DCI field configuration component 1435, an empty allocation manager 1440, and a DCI content component 1445. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0243] The bandwidth partial handover component 1420 can: determine to switch the operation of UE 115 from a first BWP to a second BWP; generate a BWP ID indicating the handover from the first BWP to the second BWP; and transmit the BWP ID as part of a DCI, wherein a timing value indicating the time difference between the transmitted DCI and the start of the second BWP is based on the DCI. The base station DCI component 1425 can: generate a DCI having a set of DCI fields, each DCI field in the set having a corresponding first size based on the first BWP; and transmit the DCI to UE 115.

[0244] DCI configuration manager 1430 can configure DCI using a variable DCI field set, the content of which in the first BWP can be updated via transformation rules to have a corresponding second-size DCI field in the second BWP. Alternatively, DCI configuration manager 1430 can configure DCI using a non-variable DCI field set, the content of which in the first BWP cannot be updated via transformation rules to have a corresponding second-size DCI field in the second BWP. In some cases, DCI configuration manager 1430 can configure DCI using an instruction regarding UE 115 switching from operation in the first BWP to operation in the second BWP. In some cases, the variable DCI field set includes the entire set of DCI fields. In some cases, the non-variable DCI field set includes the entire set of DCI fields. In some cases, the configuration of the variable and non-variable DCI field sets is pre-configured. In some cases, the configuration of the variable and non-variable DCI field sets is sent via higher-layer signaling.

[0245] The DCI field configuration component 1435 can configure the total first size of the set of non-transformable DCI fields in the first BWP to be different from the total second size of the set of non-transformable DCI fields in the second BWP, wherein the total second size is greater than the total first size. In some cases, the DCI field configuration component 1435 can identify the DCI field to be truncated from the set of transformable DCI fields based on the fact that a certain DCI field in the set of transformable DCI fields has a corresponding first size in the first BWP that is greater than a corresponding second size in the second BWP. In some examples, the DCI field configuration component 1435 can configure the total first size of the set of non-transformable DCI fields in the first BWP to be different from the total second size of the set of non-transformable DCI fields in the second BWP, wherein the total second size is less than the total first size. In some cases, the DCI field configuration component 1435 may insert a partially size equalized bit set into the second BWP, the partially size equalized bit set including the difference between the total first size and the total second size, wherein the total size of the partially size equalized bit set of the first BWP and the non-transformable DCI field set is equal to the total second size of the non-transformable DCI field set in the second BWP.

[0246] Alternatively, the DCI field configuration component 1435 may configure the total first size of the non-transformable DCI field set in the first BWP to be different from at least one corresponding total size of the corresponding non-transformable DCI field set in the BWP set. In some examples, the DCI field configuration component 1435 may insert a partially size-equalized bit set into the first BWP, which includes the difference between the maximum corresponding total size and the total first size, wherein the total size of the partially size-equalized bit set and the non-transformable DCI field set in the first BWP is equal to the maximum corresponding total size. In some cases, the DCI field configuration component 1435 may insert a partially size-equalized bit set into the first BWP, which includes the difference between the total first size and the total second size, wherein the total size of the partially size-equalized bit set and the non-transformable DCI field set in the first BWP is equal to the total second size of the non-transformable DCI field set in the second BWP.

[0247] In other examples, the DCI field configuration component 1435 may insert a partially size-equalized bit set into the second BWP, the partially size-equalized bit set comprising the difference between the maximum corresponding total size and the total second size, wherein the total size of the partially size-equalized bit set in the second BWP and the non-transformable DCI field set is equal to the maximum corresponding total size. The DCI field configuration component 1435 may configure a minimum size for each DCI field in the non-transformable DCI field set, wherein the content within the DCI field with the minimum size can be updated to the DCI field in the second BWP. In some cases, the DCI field configuration component 1435 may configure the total first size of the non-transformable DCI field set in the first BWP to be less than the total second size of the non-transformable DCI field set in the second BWP. Alternatively or additionally, the DCI field configuration component 1435 may configure the total second size of the non-transformable DCI field set in the second BWP to be different from at least one corresponding total size of the corresponding non-transformable DCI field set in the BWP set. In some cases, the size of the content within the DCI is a static size greater than or equal to the minimum size.

[0248] The empty allocation manager 1440 can send an empty allocation for a second BWP based on the premise that the total first size is less than the total second size. In some cases, the empty allocation manager 1440 can send an empty allocation within a resource allocation field of a DCI field set, wherein the empty allocation is triggered by a DCI triggering a switch from the first BWP to the second BWP. In some cases, sending an empty allocation for the second BWP includes sending an empty allocation within a resource allocation field of a DCI field set. The DCI content component 1445 can configure the content within the DCI fields using predetermined values. In some cases, the predetermined value is zero.

[0249] Figure 15 A diagram of a system 1500 including a device 1505 supporting a DCI signaling scheme for BWP handover is shown according to various aspects of this disclosure. Device 1505 may be, for example, as referenced herein. Figure 1 The described base station 105 may include examples or components thereof. Device 1505 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a base station communication manager 1515, a processor 1520, a memory 1525, software 1530, a transceiver 1535, an antenna 1540, a network communication manager 1545, and an inter-station communication manager 1550. These components may communicate electronically via one or more buses (e.g., bus 1510). Device 1505 may wirelessly communicate with one or more UEs 115.

[0250] Processor 1520 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1520 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1520. Processor 1520 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks supporting DCI signaling schemes for BWP handover).

[0251] Memory 1525 may include RAM and ROM. Memory 1525 may store computer-readable, computer-executable software 1530 including instructions that, when executed, cause a processor to perform the various functions described herein. In some cases, memory 1525 may include a BIOS, which controls basic hardware or software operations such as interaction with peripheral components or devices.

[0252] Software 1530 may include code for implementing various aspects of this disclosure, including code for supporting a DCI signaling scheme for BWP handover. Software 1530 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, software 1530 may not be directly executable by a processor, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0253] Transceiver 1535 can communicate bidirectionally via one or more antennas, wired or wireless links as described herein. For example, transceiver 1535 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1535 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna. In some cases, the wireless device may include a single antenna 1540. However, in some cases, the device may have more than one antenna 1540, which is capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0254] The network communication manager 1545 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1545 can manage the delivery of data communication for client devices (such as one or more UEs 115).

[0255] Inter-site communication manager 1550 can manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1550 can coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1550 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0256] Figure 16 A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by the UE 115 or its components as described herein. For example, operation of method 1600 can be performed by, as referenced... Figures 8 to 11 The UE communication manager described herein is executed. In some examples, the UE 115 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, the UE 115 may use dedicated hardware to perform aspects of the functions described herein.

[0257] At 1605, UE 115 can receive a DCI having multiple DCI fields from base station 105 while operating in the first BWP, each of the multiple DCI fields having a corresponding first size based on the first BWP. The operation at 1605 can be performed according to the method described herein. In some examples, aspects of the operation at 1605 can be derived from references. Figures 8 to 11 The UE DCI manager described is used to perform this.

[0258] At 1610, UE 115 may receive, as part of the DCI, an instruction regarding a switch from operation in the first BWP to operation in the second BWP. The operation at 1610 can be performed according to the methods described herein. In some examples, aspects of the operation at 1610 may be derived from references... Figures 8 to 11 The bandwidth portion is switched to the manager for execution.

[0259] At point 1615, UE 115 can identify a first set of DCI fields from multiple DCI fields. The content of the DCI fields in the first set of DCI fields in the first BWP can be updated via transformation rules to DCI fields (e.g., transformable DCI fields) having a corresponding second size in the second BWP. The operation at point 1615 can be performed according to the method described herein. In some examples, aspects of the operation at point 1615 can be derived from references. Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0260] At 1620, UE 115 can identify a second set of DCI fields from multiple DCI fields, where the content of the DCI fields in the second set of DCI fields in the first BWP cannot be updated via transformation rules (e.g., non-transformable DCI fields). The operation at 1620 can be performed according to the method described herein. In some examples, aspects of the operation at 1620 can be derived from references. Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0261] At point 1625, UE 115 can determine, at least in part, the update content of multiple DCI fields to be applied to the second BWP based on whether each DCI field comes from a first DCI field set or a second DCI field set. The operation at point 1625 can be performed according to the method described herein. In some examples, aspects of the operation at point 1625 can be derived from references... Figures 8 to 11 The described content manager is used to execute this.

[0262] Figure 17 A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by the UE 115 or its components as described herein. For example, operation of method 1700 can be performed by, as referenced... Figures 8 to 11 The UE communication manager described herein is executed. In some examples, the UE 115 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, the UE 115 may use dedicated hardware to perform aspects of the functions described herein.

[0263] At 1705, UE 115 can receive a DCI having multiple DCI fields from base station 105 while operating in the first BWP, each of the multiple DCI fields having a corresponding first size based on the first BWP. The operation at 1705 can be performed according to the method described herein. In some examples, aspects of the operation at 1705 can be derived from references Figures 8 to 11 The UE DCI manager described is used to perform this.

[0264] At 1710, UE 115 may receive, as part of the DCI, an instruction regarding a switch from operation in the first BWP to operation in the second BWP. The operation at 1710 can be performed according to the methods described herein. In some examples, aspects of the operation at 1710 may be derived from references... Figures 8 to 11 The bandwidth portion is switched to the manager for execution.

[0265] At point 1715, UE 115 can identify a first set of DCI fields from multiple DCI fields. The content of the DCI fields in the first set of DCI fields in the first BWP can be updated via transformation rules to DCI fields with a corresponding second size in the second BWP. The operation at point 1715 can be performed according to the method described herein. In some examples, aspects of the operation at point 1715 can be derived from references. Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0266] At 1720, UE 115 can identify a second set of DCI fields from multiple DCI fields, the content of which in the first BWP cannot be updated via transformation rules. The operation at 1720 can be performed according to the method described herein. In some examples, aspects of the operation at 1720 can be derived from references... Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0267] At 1725, UE 115 can determine that the total first size of the set of non-transformable DCI fields in the first BWP differs from at least one corresponding total size. The operation at 1725 can be performed according to the method described herein. In some examples, aspects of the operation at 1725 can be derived from references... Figures 8 to 11 The described DCI field size manager is used to perform this.

[0268] At 1730, UE 115 can identify a partially size-equalized bit set in the first BWP, which includes the difference between the maximum response total size and the total first size, wherein the total size of the partially size-equalized bit set and the non-transformable DCI field set in the first BWP is equal to the maximum response total size. The operation at 1730 can be performed according to the method described herein. In some examples, aspects of the operation at 1730 can be derived from references... Figures 8 to 11 The UE DCI manager described is used to perform this.

[0269] At point 1735, UE 115 can determine, at least in part, the update content of multiple DCI fields to be applied to the second BWP based on whether each DCI field comes from a first DCI field set or a second DCI field set. The operation at point 1735 can be performed according to the method described herein. In some examples, aspects of the operation at point 1735 can be derived from references... Figures 8 to 11 The described content manager is used to execute this.

[0270] Figure 18A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by the UE 115 or its components as described herein. For example, operation of method 1800 can be performed by, as referenced... Figures 8 to 11 The UE communication manager described herein is executed. In some examples, the UE 115 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, the UE 115 may use dedicated hardware to perform aspects of the functions described herein.

[0271] At 1805, UE 115 can receive a DCI having multiple DCI fields from base station 105 while operating in the first BWP, each of the multiple DCI fields having a corresponding first size based on the first BWP. The operation at 1805 can be performed according to the method described herein. In some examples, aspects of the operation at 1805 can be derived from references Figures 8 to 11 The UE DCI manager described is used to perform this.

[0272] At 1810, UE 115 may receive, as part of the DCI, an instruction regarding a switch from operation in the first BWP to operation in the second BWP. The operation at 1810 can be performed according to the methods described herein. In some examples, aspects of the operation at 1810 may be derived from references... Figures 8 to 11 The bandwidth portion is switched to the manager for execution.

[0273] At point 1815, UE 115 can identify a first set of DCI fields from multiple DCI fields. The content of the DCI fields in the first set of DCI fields in the first BWP can be updated via transformation rules to have DCI fields of a corresponding second size in the second BWP. The operation at point 1815 can be performed according to the method described herein. In some examples, aspects of the operation at point 1815 can be derived from references. Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0274] At point 1820, UE 115 can identify a second set of DCI fields from multiple DCI fields, the content of which in the first BWP cannot be updated via transformation rules. The operation at point 1820 can be performed according to the method described herein. In some examples, aspects of the operation at point 1820 can be derived from references... Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0275] At point 1825, UE 115 can determine that the total first size is less than the total second size. The operation at point 1825 can be performed according to the method described herein. In some examples, aspects of the operation at point 1825 can be derived from references. Figures 8 to 11 The described DCI field size manager is used to perform this.

[0276] At 1830, UE 115 may, at least in part, identify an empty allocation for the second BWP within the received DCI based on the fact that the total first size is less than the total second size. The operation at 1830 can be performed according to the method described herein. In some examples, aspects of the operation at 1830 can be derived from references... Figures 8 to 11 The described allocation component is used for execution.

[0277] At 1835, UE 115 can switch operation from the first BWP to the second BWP, at least partially based on an empty allocation. The operation at 1835 can be performed according to the method described herein. In some examples, aspects of the operation at 1835 can be derived from references... Figures 8 to 11 The described BWP switching manager is used to perform this.

[0278] At 1840, UE 115 can avoid determining the contents of at least the non-transformable DCI field set. The operation at 1840 can be performed according to the method described herein. In some examples, aspects of the operation at 1840 can be derived from references... Figures 8 to 11 The described content manager is used to execute this.

[0279] Figure 19 A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by the UE 115 or its components as described herein. For example, operation of method 1900 can be performed by, as referenced... Figures 8 to 11 The UE communication manager described herein is executed. In some examples, the UE 115 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, the UE 115 may use dedicated hardware to perform aspects of the functions described herein.

[0280] At 1905, UE 115 can receive a DCI having multiple DCI fields from base station 105 while operating in the first BWP, each of the multiple DCI fields having a corresponding first size based on the first BWP. The operation at 1905 can be performed according to the method described herein. In some examples, aspects of the operation at 1905 can be derived from references. Figures 8 to 11 The UE DCI manager described is used to perform this.

[0281] At 1910, UE 115 may receive, as part of the DCI, an instruction regarding a switch from operation in the first BWP to operation in the second BWP. The operation at 1910 can be performed according to the methods described herein. In some examples, aspects of the operation at 1910 can be derived from references... Figures 8 to 11 The bandwidth portion is switched to the manager for execution.

[0282] At point 1915, UE 115 can identify a first transformable DCI field set from multiple DCI fields. The content of the DCI fields in the first DCI field set that exists in the first BWP can be updated via transformation rules to DCI fields with a corresponding second size in the second BWP. The operation at point 1915 can be performed according to the method described herein. In some examples, aspects of the operation at point 1915 can be derived from references. Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0283] At point 1920, UE 115 can identify a second set of non-transformable DCI fields from multiple DCI fields, the contents of which in the first BWP cannot be updated via transformation rules. The operation at point 1920 can be performed according to the method described herein. In some examples, aspects of the operation at point 1920 can be derived from references... Figures 8 to 11 The described DCI field recognition component is used to perform this.

[0284] At 1925, UE 115 can identify the DCI field to be truncated from the set of transformable DCI fields, at least in part, based on the fact that a certain DCI field in the set of transformable DCI fields has a corresponding first size in the first BWP that is greater than a corresponding second size in the second BWP. The operation at 1925 can be performed according to the method described herein. In some examples, aspects of the operation at 1925 can be derived from references... Figures 8 to 11 The described DCI truncation manager is used to perform this.

[0285] At point 1930, UE 115 can determine that the content within the DCI field has a predetermined value. The operation at point 1930 can be performed according to the method described herein. In some examples, aspects of the operation at point 1930 can be referenced. Figures 8 to 11 The described DCI truncation manager is used to perform this.

[0286] At point 1935, UE 115 can truncate the DCI field, at least in part, based on the determination that the content has a predetermined value. The operation at point 1935 can be performed according to the method described herein. In some examples, aspects of the operation at point 1935 can be derived from references... Figures 8 to 11The described DCI truncation manager is used to perform this.

[0287] At point 1940, UE 115 can determine, at least in part, the update content of multiple DCI fields to be applied to the second BWP based on whether each DCI field comes from a first DCI field set or a second DCI field set. The operation at point 1940 can be performed according to the method described herein. In some examples, aspects of the operation at point 1940 can be derived from references... Figures 8 to 11 The described content manager is used to execute this.

[0288] Figure 20 A flowchart illustrating a method 2000 for a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 2000 can be implemented by the UE 115 or its components as described herein. For example, operation of method 2000 can be performed by, as referenced... Figures 8 to 11 The UE communication manager described herein is executed. In some examples, the UE 115 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, the UE 115 may use dedicated hardware to perform aspects of the functions described herein.

[0289] At point 2005, UE 115 can receive DCI from base station 105 during the first TTI, while operating in the first BWP. The operation at point 2005 can be performed according to the method described herein. In some examples, aspects of the operation at point 2005 can be referenced. Figures 8 to 11 The UE DCI manager described is used to perform this.

[0290] At point 2010, UE 115 can receive, as part of the DCI, an instruction regarding the UE's switch from operation in the first BWP to operation in the second BWP. The operation at point 2010 can be performed according to the method described herein. In some examples, aspects of the operation at point 2010 can be referenced... Figures 8 to 11 The bandwidth portion is switched to the manager for execution.

[0291] At point 2015, UE 115 can determine that the second BWP begins at the second TTI following the first TTI. The operation at point 2015 can be performed according to the method described herein. In some examples, aspects of the operation at point 2015 can be derived from references... Figures 8 to 11 The described BWP switching manager is used to perform this.

[0292] At point 2020, UE 115 can at least partially trigger a handover from the first BWP to the second BWP based on the received DCI to avoid monitoring the PDCCH. The operation at point 2020 can be performed according to the method described herein. In some examples, aspects of the operation at point 2020 can be derived from references... Figures 8 to 11 The UE DCI manager described is used to perform this.

[0293] Figure 21 A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 2100 can be implemented by the base station 105 or its components as described herein. For example, operation of method 2100 can be performed by, as referenced... Figures 12 to 15 The described base station communication manager is executed. In some examples, base station 105 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, base station 105 may use dedicated hardware to perform aspects of the functions described herein.

[0294] At point 2105, base station 105 can determine to switch the operation of UE 115 from the first BWP to the second BWP. The operation at point 2105 can be performed according to the method described herein. In some examples, aspects of the operation at point 2105 can be derived from references. Figures 12 to 15 The described BWP switching component is used for execution.

[0295] At 2110, base station 105 can generate a DCI with multiple DCI fields, each of the multiple DCI fields having a corresponding first size based on a first BWP. The operation at 2110 can be performed according to the method described herein. In some examples, aspects of the operation at 2110 can be derived from references... Figures 12 to 15 The base station DCI component described herein is used to perform this.

[0296] At point 2115, base station 105 can configure DCI using a first DCI field set. The content of the DCI fields in the first DCI field set that exists in the first BWP can be updated via transformation rules to have DCI fields of a corresponding second size in the second BWP. The operation at point 2115 can be performed according to the method described herein. In some examples, aspects of the operation at point 2115 can be referenced. Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0297] At point 2120, base station 105 can configure DCI using a second DCI field set, where the content of the DCI fields in the second DCI field set that exists in the first BWP cannot be updated via transformation rules to a DCI field of the corresponding second size in the second BWP. The operation at point 2120 can be performed according to the method described herein. In some examples, aspects of the operation at point 2120 can be referenced... Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0298] At 2125, base station 105 can configure DCI using an instruction regarding UE 115 switching from operation in the first BWP to operation in the second BWP. The operation at 2125 can be performed according to the method described herein. In some examples, aspects of the operation at 2125 can be derived from references... Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0299] At point 2130, base station 105 can send DCI to UE 115. The operation at point 2130 can be performed according to the method described herein. In some examples, aspects of the operation at point 2130 can be derived from references... Figures 12 to 15 The base station DCI component described herein is used to perform this.

[0300] Figure 22 A flowchart illustrating a DCI signaling scheme for BWP handover according to various aspects of this disclosure is shown. Operation of method 2200 can be implemented by the base station 105 or its components as described herein. For example, operation of method 2200 can be performed by, as referenced... Figures 12 to 15 The described base station communication manager is executed. In some examples, base station 105 may execute a set of code to control the functional elements of the device to perform the functions described herein. Alternatively or alternatively, base station 105 may use dedicated hardware to perform aspects of the functions described herein.

[0301] At point 2205, base station 105 can determine to switch the operation of UE 115 from the first BWP to the second BWP. The operation at point 2205 can be performed according to the method described herein. In some examples, aspects of the operation at point 2205 can be derived from references. Figures 12 to 15 The bandwidth portion is switched to perform the operation.

[0302] At 2210, base station 105 can generate a DCI with multiple DCI fields, each of the multiple DCI fields having a corresponding first size based on a first BWP. The operation at 2210 can be performed according to the method described herein. In some examples, aspects of the operation at 2210 can be derived from references... Figures 12 to 15 The base station DCI component described herein is used to perform this.

[0303] At 2215, base station 105 can configure DCI using a first DCI field set. The content of the DCI fields in the first DCI field set that exists in the first BWP can be updated via transformation rules to have DCI fields of a corresponding second size in the second BWP. The operation at 2215 can be performed according to the method described herein. In some examples, aspects of the operation at 2215 can be referenced. Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0304] At 2220, base station 105 can configure DCI using a second DCI field set, where the content of the DCI fields in the second DCI field set that exists in the first BWP cannot be updated via transformation rules to have DCI fields of a corresponding second size in the second BWP. The operation at 2220 can be performed according to the method described herein. In some examples, aspects of the operation at 2220 can be referenced... Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0305] At 2225, base station 105 can configure DCI using an indication that UE 115 will switch from operating in the first BWP to operating in the second BWP. The operation at 2225 can be performed according to the method described herein. In some examples, aspects of the operation at 2225 can be derived from references... Figures 12 to 15 The described DCI configuration manager is used to execute this.

[0306] At 2230, base station 105 can configure a minimum size for each DCI field in the second DCI field set, wherein the content within the DCI field with the minimum size can be updated to the DCI fields in the second BWP. The operation at 2230 can be performed according to the method described herein. In some examples, aspects of the operation at 2230 can be referenced... Figures 12 to 15 The described DCI field configuration component is used to perform this.

[0307] At point 2235, base station 105 can send DCI to UE 115. The operation at point 2235 can be performed according to the method described herein. In some examples, aspects of the operation at point 2235 can be derived from references... Figures 12 to 15 The base station DCI component described herein is used to perform this.

[0308] It should be noted that the methods described herein depict possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0309] The techniques described in this article can be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and others. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 encompasses the IS-2000, IS-95, and IS-856 standards. Versions of IS-2000 may commonly be referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High-Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0310] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the systems and radio technologies mentioned above, as well as other systems and radio technologies. While various aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein can be applied beyond LTE, LTE-A, LTE-A Pro, or NR applications.

[0311] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 115 with a service subscription to a network provider. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. Depending on various examples, small cells can include picocells, femtocells, and microcells. For example, a picocell can cover a smaller geographic area and can allow unrestricted access for UE 115 with a service subscription to a network provider. A femtocell can also cover a smaller geographic area (e.g., a home) and can provide restricted access for UE 115 associated with a femtocell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 for a user in a home, etc.). An eNB used for a macro cell can be referred to as a macro eNB. An eNB used for a small cell can be referred to as a small cell eNB, pico eNB, femtocell eNB, or home eNB. eNB can support one or more (e.g., two, three, four, etc.) cells, and can also support communication using one or more component carriers.

[0312] One or more wireless communication systems 100 described herein can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0313] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned in all of the above descriptions can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0314] The various illustrative boxes and modules described in conjunction with the disclosure herein may be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0315] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in multiple locations, including portions distributed such that functions are implemented in different physical locations.

[0316] Computer-readable media includes non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium accessible by a general-purpose or special-purpose computer. Exemplarily, and not limitingly, a non-transitory computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium capable of carrying or storing required program code modules in the form of instructions or data structures and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include CDs, laser discs, optical discs, DVDs, floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these are also included within the scope of computer-readable media.

[0317] As used herein, the word "or," as in the claims, such as in a list of items (e.g., a list of items beginning with phrases such as "at least one" or "one or more"), indicates an inclusive list such that a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on conditions A and B without departing from the scope of this disclosure. That is, as used herein, the phrase "based on" will be interpreted in the same manner as the phrase "at least partially based on".

[0318] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, multiple components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description applies to any similar component having the same first reference numeral, regardless of the second reference numeral.

[0319] This document describes exemplary configurations in conjunction with the accompanying drawings, but does not represent all examples that can be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "superior to other examples." Detailed descriptions include specific details to provide an understanding of the techniques. However, these techniques can be implemented without these specific details. In some cases, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concepts of the examples.

[0320] This disclosure is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for conducting wireless communication at a user equipment (UE), the method comprising: During a first transmission time interval, while operating in a first bandwidth portion, downlink control information (DCI) is received from a network device, wherein the DCI includes an indication of a duration starting from a time slot including the first transmission time interval, the duration corresponding to the number of time slots between a physical shared channel and a control channel including the DCI, and wherein the DCI includes an indication that the UE will switch from operating in the first bandwidth portion to operating in a second bandwidth portion, the second bandwidth portion starting at a second transmission time interval following the first transmission time interval. The DCI has multiple DCI fields, one or more of which have a corresponding first size based on the first bandwidth portion, and the multiple DCI fields have: A first set of DCI fields corresponding to the first bandwidth portion, wherein each DCI field in the first set of DCI fields can be updated from a DCI field of a corresponding first size to a DCI field of a corresponding second size corresponding to the second bandwidth portion via the same transformation rule; and A second set of DCI fields corresponding to the first bandwidth portion, wherein the second set of DCI fields includes exceptions to the transformation rule; and After the switch from the first bandwidth portion to the second bandwidth portion and after the duration, the physical downlink control channel (PDCCH) is monitored.

2. The method according to claim 1, wherein, The duration includes the number of symbol cycles following the received DCI.

3. The method according to claim 1, wherein, The first transmission time interval includes a first time slot, and the second transmission time interval includes a second time slot that is different from the first time slot.

4. The method according to claim 1, wherein, The physical shared channel includes the physical downlink shared channel (PDSCH).

5. The method according to claim 1, wherein, The physical shared channel includes the physical uplink shared channel (PUSCH).

6. An apparatus for wireless communication, the apparatus comprising: processor; as well as A memory coupled to the processor, wherein the processor and the memory are configured as follows: During a first transmission time interval, while operating in a first bandwidth portion, downlink control information (DCI) is received from the network device, wherein the DCI includes an indication of a duration from a time slot including the first transmission time interval, the duration corresponding to the number of time slots between the physical shared channel and the control channel including the DCI, and wherein the DCI includes an indication of switching from operation in the first bandwidth portion to operation in a second bandwidth portion, the second bandwidth portion starting at a second transmission time interval following the first transmission time interval. The DCI has multiple DCI fields, one or more of which have a corresponding first size based on the first bandwidth portion, and the multiple DCI fields have: A first set of DCI fields corresponding to the first bandwidth portion, wherein each DCI field in the first set of DCI fields can be updated from a DCI field of a corresponding first size to a DCI field of a corresponding second size corresponding to the second bandwidth portion via the same transformation rule; and A second set of DCI fields corresponding to the first bandwidth portion, wherein the second set of DCI fields includes exceptions to the transformation rule; and After the switch from the first bandwidth portion to the second bandwidth portion and after the duration, the physical downlink control channel (PDCCH) is monitored.

7. The apparatus according to claim 6, wherein, The duration includes the number of symbol cycles following the received DCI.

8. The apparatus according to claim 6, wherein, The first transmission time interval includes a first time slot, and the second transmission time interval includes a second time slot that is different from the first time slot.

9. The apparatus according to claim 6, wherein, The physical shared channel includes the physical downlink shared channel (PDSCH).

10. The apparatus according to claim 6, wherein, The physical shared channel includes the physical uplink shared channel (PUSCH).

11. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code including instructions executable by a processor to perform the following operations: During the first transmission time interval, while operating in the first bandwidth portion, downlink control information (DCI) is received from the network device, wherein, The DCI includes an indication of a duration starting from a time slot including the first transmission time interval, the duration corresponding to the number of time slots between the physical shared channel and the control channel including the DCI, and wherein the DCI includes an indication of a switch from operation in the first bandwidth portion to operation in a second bandwidth portion, the second bandwidth portion starting at a second transmission time interval after the first transmission time interval. The DCI has multiple DCI fields, one or more of which have a corresponding first size based on the first bandwidth portion, and the multiple DCI fields have: A first set of DCI fields corresponding to the first bandwidth portion, wherein each DCI field in the first set of DCI fields can be updated from a DCI field of a corresponding first size to a DCI field of a corresponding second size corresponding to the second bandwidth portion via the same transformation rule; and A second set of DCI fields corresponding to the first bandwidth portion, wherein the second set of DCI fields includes exceptions to the transformation rule; and After the switch from the first bandwidth portion to the second bandwidth portion and after the duration, the physical downlink control channel (PDCCH) is monitored.

12. The non-transitory computer-readable medium according to claim 11, wherein, The duration includes the number of symbol cycles following the received DCI.

13. The non-transitory computer-readable medium of claim 11, wherein the first transmission time interval includes a first time slot, and wherein, The second transmission time interval includes a second time slot that is different from the first time slot.

14. The non-transitory computer-readable medium according to claim 11, wherein, The physical shared channel includes the physical downlink shared channel (PDSCH).

15. The non-transitory computer-readable medium according to claim 11, wherein, The physical shared channel includes the physical uplink shared channel (PUSCH).

Images