Pruning DCI for NR BWP handover

Abstract

The present disclosure provides systems, devices, apparatuses, and methods, including computer programs encoded on a storage medium, for correct and false recognition detection of DCI requests for switching BWP. A UE may receive a DCI request for switching from a first BWP to a second BWP, and may reject the DCI request for switching from the first BWP to the second BWP based on at least one of a conflict of a TDD mode associated with the DCI request, a DCI decoder metric, or a number of error-corrected modulation symbols indicating a right or wrong recognition detection of the DCI request.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 664,383, filed on May 20, 2022, entitled “PRUNING DCI FOR NR BWP SWITCHING,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to true and false detection of downlink control information (DCI) requests for switching bandwidth parts (BWPs). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may receive a downlink control information (DCI) request for switching from a first bandwidth part (BWP) to a second BWP; and reject the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with a time division duplex (TDD) mode associated with the DCI request, a DCI decoder metric, or a number of error-corrected modulation symbols indicating a true or false detection of the DCI request.

[0008] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0011] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0012] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0013] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0014] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0015] Figure 4A An example resource map with multiple BWPs is illustrated.

[0016] Figure 4B is a call flow diagram illustrating communications between a UE and a network entity.

[0017] Figure 5 is a flow chart of a method of performing wireless communication at a UE.

[0018] Figure 6 is a flow chart of a method of performing wireless communication at a UE.

[0019] Figure 7 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0020] Noise received by a user equipment (UE) may cause the UE to erroneously detect downlink control information (DCI). In some examples, a false positive DCI detection may correspond to a DCI request for switching from a first bandwidth part (BWP) to a second BWP. That is, the UE may erroneously detect a BWP switching request that is not actually sent by the base station. While the impact of a false positive DCI detection associated with procedures other than BWP switching (such as erroneously triggering a physical uplink shared channel (PUSCH) transmission on the uplink or attempting to receive a physical downlink shared channel (PDSCH) that is not sent by the base station) may be limited to 1 timeslot, a false positive DCI detection of a BWP switching request may have a more lasting impact on the UE. For example, based on such a DCI request, the UE and the base station may become unsynchronized, such that the UE and the base station may have to perform a random access channel (RACH) procedure to resynchronize (e.g., after the UE declares a radio link failure (RLF) and possible radio resource control (RRC) reestablishment). Thus, various aspects presented herein enable a UE to verify / confirm whether a detected DCI request for switching a BWP is a true false positive detection (e.g., received in noise) or an actual DCI request sent by a base station. The verification / confirmation of the DCI request for switching the BWP may be based on information consistency within a time division duplex (TDD) mode for PDSCH reception or physical uplink shared channel (PUSCH) transmission, a DCI decoder / energy metric associated with the detected DCI request, and / or the number of error-corrected symbols associated with the DCI decoding.

[0021] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0022] Several aspects of the telecommunication system are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0023] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic components, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0024] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0025] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0026] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0027] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0028] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0029] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0030] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0031] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0032] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0033] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0034] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0035] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0036] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0037] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0038] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0039] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0040] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz–71 GHz), FR4 (71 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0042] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2 and / or FR5, or may be within the EHF band.

[0043] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each base station / UE in the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0044] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0045] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, the LMF 166, the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement results and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0046] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0047] Refer again Figure 1 In certain aspects, the UE 104 may include a DCI accepting component 198 configured to receive a DCI request for switching from a first BWP to a second BWP; and reject the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with the TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating a true or false detection of the DCI request. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0048] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to either DL or UL), or may be TDD (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured through DCI, or semi-statically / statically configured through RRC signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G NR frame structure as TDD.

[0049] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP OFDM (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0050]

[0051] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ*15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different BWPs frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0052] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0054] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0055] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0056] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0057] Figure 3 370 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0058] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0059] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be merged into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0060] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0061] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0062] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0063] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0064] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0065] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The DCI acceptance component 198 combines various aspects.

[0066] Wireless communication systems can be configured to share available system resources and provide various telecommunication services (e.g., telephone, video, data, messaging, broadcast, etc.) based on multiple access technologies that support communication with multiple users (such as CDMA systems, TDMA systems, FDMA systems, OFDMA systems, SC-FDMA systems, and TD-SCDMA systems, etc.). In many cases, common protocols that facilitate communication with wireless devices are adopted in various telecommunication standards. For example, communication methods associated with eMBB, mMTC, and ultra-reliable low-latency communications (URLLC) may be incorporated into the 5G NR telecommunication standard, while other aspects may be incorporated into the 4G LTE standard. Since mobile broadband technology is part of the ongoing evolution, further improvements in mobile broadband remain useful for the continued development of such technology.

[0067] Noise received by a user equipment (UE) may cause the UE to falsely detect downlink control information (DCI). In some examples, a false positive DCI detection may correspond to a DCI request for switching from a first bandwidth part (BWP) to a second BWP. That is, the UE may falsely detect a BWP switching request that was not actually sent by the base station. The UE may be configured with multiple BWPs. Figure 4A A resource diagram 450 is illustrated with an example of three BWPs (e.g., BWP 1, BWP 2, and BWP 3), each BWP spanning a set of frequency resources (e.g., a set of PRBs). A BWP may be activated for a UE from a set of configured BWPs. It may not be expected that the UE will receive PDSCH, PDCCH, CSI-RS, TRS, etc. outside of an active downlink BWP. The UE may not send PUSCH or PUCCH outside of an active uplink BWP. The UE may receive an indication from the network to switch from a first active BWP to a second active BWP, the first active BWP and the second active BWP being from the set of configured BWPs. As Figure 4A As illustrated, each downlink BWP may include a control resource set (CORESET) corresponding to a configurable set of time-frequency physical resources, which the UE uses to monitor PDCCH / DCI when the corresponding BWP is activated. For example, if the UE receives an indication for switching to BWP 1, the UE may monitor control signaling in the corresponding CORESET in BWP 1. If the UE receives an indication for switching to BWP 2, the UE may monitor control signaling in the CORESET in BWP 2.

[0068] While the impact of a false positive DCI detection associated with procedures other than BWP switching (such as erroneously sending a PUSCH transmission on the uplink or attempting to receive a PDSCH that was not sent by the base station) may be limited to 1 timeslot, a false positive DCI detection of a BWP switching request may have a more lasting impact on the UE. For example, based on such a DCI request, the UE and the base station may become desynchronized, such that the UE and the base station may have to perform a random access channel (RACH) procedure to resynchronize (e.g., after the UE declares a radio link failure (RLF) and possible radio resource control (RRC) reestablishment). As an example, if the UE detects a false positive DCI detection from a BWP switching request, the UE and the base station may become desynchronized. Figure 4A In an embodiment, the UE performs a BWP switch from BWP 1 to BWP 2 in a BWP 1-to-BWP 2, the UE will monitor further control signaling and communication scheduling in the CORESET in BWP 2. If the detection is a false detection, the base station may continue to transmit control signaling in the CORESET in BWP 1, which the UE does not monitor. Similarly, the UE may attempt to communicate with the base station in an uplink BWP in which the base station does not expect to receive PUCCH or PUSCH from the UE. As an example, the UE may transmit a scheduling request for uplink resources in BWP 2 based on a false detection of DCI, which indicates to the UE to switch to BWP2, and the base station may continue to monitor BWP 1 to obtain such scheduling request from the UE. Various aspects presented herein enable the UE to verify / confirm whether a detected DCI request for switching BWP is a true false detection. In some aspects, verification may be referred to as pruning DCI for BWP switching.

[0069] Figure 4B4 is a call flow diagram 400 illustrating communication between a UE 402 and a network entity 404. The network entity 404 may correspond to a base station or an entity at a base station, such as a CU, DU, RU, etc. Noise received by the UE 402 may cause the UE 402 to detect a true false DCI. In some examples, the true false DCI detection may correspond to a DCI request received (e.g., at 406) for switching from a first BWP to a second BWP. Therefore, the UE 402 may be configured to verify / confirm whether the DCI request received at 406 is associated with a true false detection, so that the UE 402 may discard or "prune" the DCI request associated with switching BWP, or verify / confirm whether the DCI request received at 406 for switching BWP is an actual DCI sent from the network entity 404. The UE 402 may use various information logs to infer that the DCI request detected by the UE 402 is not sent by the base station / network entity 404, but is a true false detection of the DCI. In the case where the UE 402 does not perform an acknowledgement procedure, the DCI request detected / received by the UE 402 (e.g., at 406) may be accepted / acted upon by the UE 402 so that the UE may switch BWPs and become unsynchronized with the base station / network entity 404. Since the UE 402 and the base station / network entity 404 may have to perform a RACH procedure to resynchronize, it may be a relatively slow process for the UE 402 and the base station / network entity 404 to recover from an out-of-sync scenario. If the UE 402 and the base station / network entity 404 are out-of-sync due to the UE 402 switching BWPs, the base station / network entity 404 may not decode a scheduling request (e.g., a CSI request) received from the UE 402 without performing a RACH procedure with the UE 402.

[0070] Although false positive DCI detections may occur with some regularity statistically, the impact of some false positive DCI detections may be greater than the impact of other false positive DCI detections. For example, if the DCI request that causes the UE 402 to switch the active BWP is a false positive DCI request that is not transmitted by the base station / network entity 404, the DCI request may cause the UE 402 to miss one or more grants because the UE 402 and the base station / network entity 404 may have conflicting understandings of which BWP is the active BWP. Based on the conflict, the base station / network entity 404 may not be able to decode the scheduling request, CSI report, SRS, etc. received from the UE 402. If the UE 402 and the base station / network entity 404 do not agree on the current / active BWP, the UE 402 may also be unable to decode the DCI transmitted by the base station / network entity 404. A recovery procedure may follow the RLF detected by the UE 402 and the RRC re-establishment procedure.

[0071] UE 402 may be configured to perform PDCCH blind detection for decoding a DCI request at 408, which may be used to generate a DCI decoder metric. The DCI may be protected based on a 24-bit cyclic redundancy check (CRC). However, 3 CRC bits may be used by the Polar code decoder for error correction, where, for example, 8 best paths / channels may be stored for selecting a path / channel through the CRC. At 410, the remaining 21 bits of the CRC may be used to estimate the number of errors associated with the DCI. In the case where UE 402 decodes an increased amount of information (e.g., every millisecond), the PDCCH error detection probability may be higher. A time slot corresponding to a 15KHz SCS may be decoded once per millisecond.

[0072] The PDCCH false detection probability may be approximated based on: Num_blind_Decodes*Num_RNTIs*2^-effective_CRC_length, where Num_blind_decodes corresponds to the number of blind decoding hypotheses. For example, 44 blind decoding hypotheses may be associated with an SCS of 15kHz. Num_RNTI corresponds to the number of radio network temporary identifiers (RNTIs) associated with each blind decoding attempt. For example, in the case where UE 402 is associated with a cell RNTI (C-RNTI), Num_RNTIs may be equal to 1. Effective_CRC_length may be equal to 21, which may be based on the number of CRC bits used for false detection. Therefore, in the example where Num_blind_Decodes=44, Num_RNTIs=1, and effective_CRC_length=21, the PDCCH false detection probability may be equal to 44*1*2^-21. Based on performing a decoding attempt once per millisecond, a true false DCI may be detected approximately every 60 seconds (e.g., once per minute).

[0073] At 412, a false positive DCI detection may be rejected based on inconsistency with associated content and / or certain reserved values ​​to prevent the UE 402 from attempting to decode content associated with a false positive DCI request. The UE procedure for receiving control information may be that if the UE 402 detects a DCI format with inconsistent information, the UE 402 discards the information in the DCI format. Some false positive DCIs accepted by the UE 402 may have different effects on the UE 402 based on whether the false positive DCI is associated with a switching BWP or whether the false positive DCI is associated with a different procedure. The effect of a false positive DCI associated with a different procedure may be limited to a triggered PUSCH transmission on the uplink, which may generate interference, but is limited to 1 time slot. If the false positive DCI is associated with a PDSCH reception, the effect on the UE 402 may be limited to decoding noise and triggering a NACK. Although the UE 402 may generate interference based on transmitting a NACK that is not associated with a transmission by the base station / network entity 404, the interference will again be limited to 1 time slot. Therefore, the impact of a false positive DCI detection not associated with a request to switch BWP may be limited to one unnecessary PUSCH transmission or one unnecessary PDSCH reception.

[0074] The DCI pruning / elimination procedure based on information consistency may not be sufficient for DCI requests associated with BWP switching. A false positive DCI detection corresponding to a request for switching a BWP may have a lasting impact on the UE 402 that is longer than 1 time slot. For example, a false positive DCI requesting the UE 402 to switch the BWP may cause the UE 402 and the base station / network entity 404 to become out of sync with each other. The UE 402 may miss the correct DCI transmitted by the base station / network entity 404 because the base station / network entity 404 may be scheduling the UE 402 on a BWP that is not switched. The UE 402 may also attempt to communicate with the base station / network entity 404 via SRS, sending feedback, etc. However, the attempt to communicate with the base station / network entity 404 may be considered as noise by the base station / network entity 404 and no action will be taken on it. In order to resynchronize with the base station / network entity 404, the UE 402 may have to trigger a RACH procedure with the base station / network entity 404.

[0075] Accordingly, at 412, the DCI request associated with the BWP switching received at 406 may be rejected based on information consistency, DCI decoder / energy metric, and / or the number of corrected symbols. Information consistency may be based on consistency with the TDD mode used for PDSCH reception or PUSCH transmission. Such a procedure may be performed for a TDD cell. BWP switching may be performed for a larger BWP (e.g., 100 MHz) because a smaller BWP (e.g., 20 MHz to 40 MHz) may not have multiple BWPs configured for FDD operation. The TDD mode may include time slots reserved for the downlink, time slots reserved for the uplink, and flexible time slots. When the UE 402 receives the DCI associated with the request for switching the BWP at 406, the UE 402 may verify the consistency of the information included in the DCI with the TDD mode. For example, if UE 402 receives DCI 1_1 indicating a BWP switch, but the time slot for PDSCH reception does not correspond to a downlink time slot, UE 402 may reject the DCI based on lack of consistency with TDD mode at 412. In an example, UE 402 may determine that the DCI request corresponds to a true or false DCI detection based on at least one symbol for PDSCH reception not corresponding to a downlink symbol.

[0076] UE 402 may also verify the number of corrected symbols during Polar decoding of the DCI decoder metric / energy metric generated based on decoding the DCI request at 408 and / or estimated in association with the DCI at 410. Compared to other DCIs for the current channel, the reduced DCI decoding / energy metric may indicate that the DCI request corresponds to an increased probability of a positive false positive detection. A noise-based positive false positive detection may have a reduced DCI decoding / energy metric (e.g., a lower energy metric). The energy metric may be associated with a Polar decoding procedure. The energy metric may be determined based on the relationship between the expected path and the actual path of the received DCI. The increased number of corrected Rx symbols may correspond to a lower energy metric. The energy metric may be determined based on comparing the best path / channel and the suboptimal path / channel. If the detected DCI corresponds to the actual DCI sent by the base station / network entity 404, the best path / channel may have a much higher energy metric than the suboptimal path / channel. However, if the detected DCI corresponds to a positive false positive DCI, the energy metrics of the best path / channel and the suboptimal path / channel may be close to the same. In some cases, the suboptimal path / channel may even have a higher energy metric than the best path / channel, but may be rejected based on a failed CRC for the suboptimal path / channel. Therefore, the UE 402 may determine whether to reject the detected DCI at 412 based on the energy metric information. For TDD, both the information consistency and the energy metric may be verified by the UE 402. For FDD, the UE 402 may verify the energy metric but may not verify the information consistency.

[0077] In one example, UE 402 may have a currently active BWP=1 and may receive DCI 0_1 with BWP indicator=0 and k2=10 at time slot 6. K2 corresponds to the offset between the reception of the DCI and the associated PUSCH transmission. The DCI request received by UE 402 at 406 may correspond to a true false detection of DCI from noise that does not correspond to the actual DCI sent by the base station / network entity 404. In order to make k2 large enough to switch the BWP, at 416, the PUSCH transmission may not be performed until after time slot 16. However, the TDD mode may indicate that time slot 16 is a full downlink time slot. If the DCI is the actual DCI sent by the base station / network entity 404, the base station / network entity 404 will not request the UE 402 to send PUSCH on the downlink time slot. Therefore, UE 402 may reject the DCI as a true false detection of DCI at 412.

[0078] If UE 402 were to take action based on DCI 0_1 and perform a BWP switch from BWP identifier (ID) 1 to BWP ID 2, UE 402 and base station / network entity 404 may become unsynchronized with each other based on UE 402 and base station / network entity 404 operating according to different BWP IDs. For example, UE 402 may not receive a grant transmitted by base station / network entity 404 on BWP ID 1, or base station / network entity 404 may attempt to decode a periodic SRS / CQI that is not sent by UE 402 on BWP ID 1. After performing a RACH procedure and possibly an RRC re-establishment procedure with base station / network entity 404, UE 402 may recover / resynchronize with base station / network entity 404.

[0079] UE 402 may verify the information consistency for a TDD cell. Although BWP switching may also be applied to an FDD cell, a TDD cell may be associated with a larger bandwidth. For FR1, a TDD cell may include a channel bandwidth of 100 MHz, while an FDD cell may include a channel bandwidth of 20 MHz. At 412, UE 402 may reject the DCI request for BWP switching received at 406 based on a PDSCH reception timing or a PUSCH transmission timing (e.g., at least 1 symbol) that is inconsistent with the TDD mode. If at least 1 symbol in the requested PUSCH transmission or PDSCH reception does not match the TDD mode, UE 402 may prune / reject the DCI at 412 as a true false detection.

[0080] The time domain resource allocation (TDRA) for the BWP switching request based on DCI 1_1 may indicate a k0 value, a starting symbol, a number of symbol combinations (where k0 may be valid for the UE switching timer for BWP), and / or a PDSCH symbol (which is a downlink symbol or a flexible symbol that leaves enough time to perform a downlink / uplink switch). K0 corresponds to an offset between DCI reception and PDSCH reception. K0 may not be equal to 0 because k0 should correspond to a valid value of the UE switching timer. If at least one symbol corresponds to an uplink symbol, the UE 402 may determine that the DCI request for BWP switching received at 406 should be pruned / rejected at 412. The TDRA for the BWP switching request based on DCI 0_1 may indicate a k2 value, a starting symbol, a number of symbol combinations (where k2 may be valid for the UE switching timer for BWP), and / or a PUSCH symbol (which is an uplink symbol or a flexible symbol that leaves enough time to perform an uplink / downlink switch). Similarly, k2 corresponds to an offset between the reception of the DCI and the transmission of the PUSCH. K2 may not be equal to 0, because k2 should correspond to the valid value of the uplink switching timer for BWP switching. The PUSCH symbol should be an uplink symbol or a flexible symbol. The UE 402 may verify that no PUSCH symbol is a downlink symbol, or the UE 402 may prune / reject the DCI at 412.

[0081] UE 402 can also verify the energy metric associated with the DCI decoder. The Polar decoder can be used to calculate the path / channel metric based on the log likelihood ratio (LLR) of the channel symbol and the consistency between the sign of the LLR of the path / channel and the path / channel symbol. In the case of a CRC pass, UE 402 can confirm that the energy metric is also at a sufficient level. For example, UE 402 can determine an SNR-based threshold for retaining or rejecting the DCI. The optimal energy metric can be adjusted based on the aggregation level and / or radio conditions. UE 402 can re-encode the DCI data and calculate / estimate the number of error-corrected symbols at 410 based on the number of LLRs with signs inconsistent with the re-encoded data.

[0082] UE 402 may utilize one or more metrics to determine whether the detected DCI is a false positive DCI or an actual DCI sent by base station / network entity 404. For example, UE 402 may determine whether the detected DCI is a false positive DCI based on the path metric of the best path / channel that passed the CRC. A threshold based on SNR may be used to retain or reject the DCI request decoded by UE 402 at 408. The path metric may be adjusted based on the aggregation level. UE 402 may also determine whether the detected DCI is a false positive DCI based on the difference in path metric between the best path / channel and the second-best path / channel. If the DCI corresponds to the actual DCI sent by base station / network entity 404, the difference between the best path energy and the second-best path energy may be large. In addition, UE 402 may determine whether the detected DCI is a false positive DCI based on the number of corrected symbols estimated in association with the DCI at 410. In an average to high SNR configuration, the detected DCI may be associated with a reduced number of corrected symbols.

[0083] The energy metric pruning determination of the UE 402 may be less flexible for DCI requesting BWP switching than for other types of DCI because a false positive detection of a DCI request for BWP switching has a more persistent impact (e.g., RLF, RACH procedure, RRC reestablishment, etc.) than a DCI with a BWP indicator corresponding to the current BWP ID. A false positive detection of a DCI not requesting BWP switching may generate interference, but only for 1 time slot. Although the UE 402 may prune / reject the actual DCI sent by the base station / network entity 404 at 412 under certain radio fading conditions, if the base station / network entity 404 does not detect the corresponding PUSCH (e.g., based on DCI 0_1 requesting BWP switching) or the corresponding PUCCH HARQ ACK / NACK for PDSCH (e.g., based on DCI 1_1 requesting BWP switching), the base station / network entity 404 may resend one or more subsequent DCI requests for switching BWP to the UE 402 at 414.

[0084] The base station / network entity 404 may expect to receive an ACK from the UE 402. For example, the UE 402 may be expected to receive the PDSCH and send PUCCH information based on the DCI 1_1. Therefore, the base station / network entity 404 may monitor the PUCCH, and if the energy associated with the PUCCH is low due to the UE 402 not receiving the PDSCH, the base station / network entity 404 may resend one or more subsequent DCI requests for switching the BWP at 414. For example, the base station / network entity 404 may resend the DCI four times for the BWP switching request at 414. Therefore, when the radio fading is not relevant, the UE 402 may accept the subsequent DCI request reception for the BWP switching at 414, and may switch the BWP based on the one or more subsequent DCI requests at 416. The initial rejection of the actual DCI sent by the base station / network entity 404 as a false positive DCI at 412 may therefore be limited to delaying the actual BWP switching by the UE 402 at 416.

[0085] Figure 5 500 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 402, device 704, etc.), which may include a memory 360 and may correspond to the entire UE 104, 350, 402 or device 704 or a component of the UE 104, 350, 402 or device 704 (such as a TX processor 368, an RX processor 356, a controller / processor 359, a cellular baseband processor 724, and / or an application processor 706).

[0086] At 502, the UE may receive a DCI request for switching from a first BWP to a second BWP. Figure 4B , UE 402 may receive a DCI request for switching BWP (e.g., switching from a current BWP ID to a different BWP ID) at 406. In some examples, the DCI request for switching BWP received at 406 may correspond to a true or false detection of the DCI request by UE 402 (e.g., received in noise). In other examples, UE 402 may detect / receive an actual DCI request sent from network entity 404. The reception at 502 may be caused by Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0087] At 504, the UE may reject the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with the TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating a true or false detection of the DCI request. Figure 4B, UE 402 may reject the DCI request for switching BWP received at 406 at 412. The rejection at 412 may be based on the TDD mode, DCI decoder metrics, and / or the number of error-corrected symbols associated with the DCI received by UE 402 at 406. The rejection at 608 may be based on Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0088] Figure 6 600 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 402, device 704, etc.), which may include a memory 360 and may correspond to the entire UE 104, 350, 402 or device 704 or a component of the UE 104, 350, 402 or device 704 (such as a TX processor 368, an RX processor 356, a controller / processor 359, a cellular baseband processor 724, and / or an application processor 706).

[0089] At 602, the UE may receive a DCI request for switching from a first BWP to a second BWP. Figure 4B , UE 402 may receive a DCI request for switching BWP (e.g., switching from a current BWP ID to a different BWP ID) at 406. In some examples, the DCI request for switching BWP received at 406 may correspond to a true or false detection of the DCI request by UE 402 (e.g., received in noise). In other examples, UE 402 may detect / receive an actual DCI request sent from network entity 404. The reception at 602 may be caused by Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0090] At 604, the UE may decode the DCI request based on at least one of the LLR of the modulation symbol or the sign of the modulation symbol to generate a DCI decoder metric. Figure 4B , UE 402 may decode the DCI request received at 406 at 408. The decoding at 408 may be performed to generate DCI decoder metrics associated with the DCI request received at 406. The decoding at 604 may be performed by Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0091] At 606, the UE may estimate the number of errors associated with the encoded DCI based on a comparison between one or more received modulation symbols. Figure 4B , UE 402 may estimate at 410 the number of errors associated with the DCI received by UE 402 at 406. The estimate at 606 may be Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0092] At 608, the UE may reject the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with the TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating a true or false detection of the DCI request. Figure 4B , UE 402 may reject the DCI request for switching BWP received at 406 at 412. The rejection at 412 may be based on the TDD mode, DCI decoder metrics, and / or the number of error-corrected symbols associated with the DCI received by UE 402 at 406. The rejection at 608 may be based on Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0093] At 610, the UE may receive a subsequent DCI request for switching from a first BWP to a second BWP. Figure 4B , UE 402 may receive one or more subsequent DCI requests for switching BWP from network entity 404 at 414. For example, the DCI request for switching BWP received at 406 may be an actual DCI request sent from network entity 404, as opposed to a false positive detection of the DCI request (e.g., received in noise). Thus, the one or more subsequent DCI requests for switching BWP received from network entity 404 at 414 may correspond to one or more retransmissions of the DCI request for switching BWP received by UE 402 at 406. The reception at 610 may be caused by Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0094] At 612, the UE may switch from the first BWP to the second BWP based on a subsequent DCI request. Figure 4B , UE 402 may switch the BWP at 416 based on one or more subsequent DCI requests received from network entity 404 at 414. For example, if UE 402 erroneously determines / rejects an initial DCI request received at 406 as a false positive detection, UE 402 may reverse the determination to reject the DCI request received at 406 based on one or more retransmissions of the DCI request received from network entity 404 (e.g., at 414). The switch at 612 may be caused by Figure 7 The DCI receiving component 198 of the device 704 is executed.

[0095] Figure 7700 is a diagram illustrating an example of a hardware implementation for an apparatus 704. The apparatus 704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 704 may include a cellular baseband processor 724 (also referred to as a modem) coupled to one or more transceivers 722 (e.g., a cellular RF transceiver). The cellular baseband processor 724 may include on-chip memory 724'. In some aspects, the apparatus 704 may also include one or more subscriber identity module (SIM) cards 720 and an application processor 706 coupled to a secure digital (SD) card 708 and a screen 710. The application processor 706 may include on-chip memory 706'. In some aspects, the device 704 may also include a Bluetooth module 712, a WLAN module 714, an SPS module 716 (e.g., a GNSS module), one or more sensor modules 718 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; a light detection and ranging (LIDAR), a radio-aided detection and ranging (RADAR), a sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional module for a memory 726, a power source 730, and / or a camera 732. The Bluetooth module 712, the WLAN module 714, and the SPS module 716 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 712, the WLAN module 714, and the SPS module 716 may include their own dedicated antennas and / or communicate using an antenna 780. The cellular baseband processor 724 communicates with the UE 104 and / or the RU associated with the network entity 702 through the transceiver 722 via one or more antennas 780. The cellular baseband processor 724 and the application processor 706 may each include a computer-readable medium / memory 724', 706', respectively. The additional modules of the memory 726 may also be considered as computer-readable media / memory. Each computer-readable medium / memory 724', 706', 726 may be non-transitory. The cellular baseband processor 724 and the application processor 706 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 724 / application processor 706 to perform the various functions described above when executed by the cellular baseband processor 724 / application processor 706. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 724 / application processor 706 when executing the software. The cellular baseband processor 724 / application processor 706 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368 , the RX processor 356 , and the controller / processor 359 .In one configuration, the device 704 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 724 and / or the application processor 706, while in another configuration, the device 704 may be an entire UE (eg, see. Figure 3 350) and includes additional modules of device 704.

[0096] As discussed above, the DCI acceptance component 198 is configured to receive a DCI request for switching from a first BWP to a second BWP; and to reject the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with the TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating a true or false detection of the DCI request. The DCI acceptance component 198 may be within the cellular baseband processor 724, the application processor 706, or both the cellular baseband processor 724 and the application processor 706. The DCI acceptance component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The DCI acceptance component 198 and / or another component of the cellular baseband processor 724 and the application processor may be configured to perform in conjunction with the process / algorithm. Figure 5 , Figure 6 Aspects described and / or Figure 4B Any of the aspects performed by the UE in.

[0097] As shown, the device 704 may include multiple components configured for various functions. In one configuration, the device 704 (and in particular the cellular baseband processor 724 and / or the application processor 706) includes a component for receiving a DCI request for switching from a first BWP to a second BWP; and a component for rejecting the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with the TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating a true or false detection of the DCI request. The device 704 also includes a component for decoding the DCI request based on at least one of the LLR of the modulation symbol or the sign of the modulation symbol to generate the DCI decoder metric. The device 704 also includes a component for estimating the number of errors associated with the encoded DCI based on a comparison between one or more received modulation symbols, and the DCI request for switching from the first BWP to the second BWP is rejected based on the number of errors associated with the one or more received modulation symbols. The device 704 also includes a means for switching from the first BWP to the second BWP for a subsequent DCI request; and means for switching from the first BWP to the second BWP based on the subsequent DCI request. The means may be the DCI accepting component 198 of the device 704 configured to perform the functions recited by the means. As described above, the device 704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.

[0098] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.

[0099] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having an advantage over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0100] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0101] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0102] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving a DCI request for switching from a first BWP to a second BWP; and rejecting the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with a TDD mode associated with the DCI request, a DCI decoder metric, or a number of corrected modulation symbols indicating true or false detection of the DCI request.

[0103] Aspect 2 may be combined with Aspect 1 and includes rejecting the DCI request for switching from the first BWP to the second BWP based on the conflict with the TDD mode, and includes the true or false detection of the DCI request based on at least one of: PDSCH reception or PUSCH transmission associated with the switch including a timing conflict with the TDD mode.

[0104] Aspect 3 may be combined with any one of aspects 1 to 2, and includes that the timing conflict with the TDD mode corresponds to at least one of the PDSCH reception or the PUSCH transmission being offset by at least one symbol within the TDD mode.

[0105] Aspect 4 can be combined with any one of Aspects 1 to 3, and includes rejecting the DCI request for switching from the first BWP to the second BWP based on the conflict with the TDD mode, and includes receiving the DCI request for switching from the first BWP to the second BWP based on at least one of DCI 1_1 or DCI0_1, and includes a first TDRA associated with the DCI 1_1 indicating at least one of a first offset, a starting symbol, or a number of symbol combinations between DCI reception and PDSCH reception, and includes a second TDRA associated with the DCI 0_1 indicating at least one of a second offset, a starting symbol, or a number of symbol combinations between the DCI reception and PUSCH transmission.

[0106] Aspect 5 may be combined with any one of aspects 1 to 4, and includes that the first offset and the second offset are based on a BWP switching time.

[0107] Aspect 6 can be combined with any one of Aspects 1 to 5, and includes rejecting the DCI request for switching from the first BWP to the second BWP based on the DCI decoder metric, and the aspect also includes decoding the DCI request based on the LLR associated with the error-corrected modulation symbol to generate the DCI decoder metric, wherein the error-corrected modulation symbol corresponds to the OFDM symbol associated with the DCI request.

[0108] Aspect 7 can be combined with any one of Aspects 1 to 6, and also includes estimating a number of errors associated with the encoded DCI based on a comparison between one or more received modulation symbols, and the DCI request for switching from the first BWP to the second BWP is rejected based on the number of errors associated with the one or more received modulation symbols.

[0109] Aspect 8 may be combined with any one of Aspects 1 to 7, and includes rejecting the DCI request for switching from the first BWP to the second BWP based on the DCI decoder metric, and includes the DCI decoder metric corresponding to at least one of the highest SNR, the difference between the highest SNR and the second highest SNR, or the number of error-corrected modulation symbols.

[0110] Aspect 9 may be combined with any one of Aspects 1 to 8 and includes rejecting the DCI request for switching from the first BWP to the second BWP based on the DCI decoder metric, wherein the DCI decoder metric is based on a first false positive detection threshold associated with the BWP switching DCI, and the first false positive detection threshold is lower than a second false positive detection threshold associated with the non-BWP switching DCI.

[0111] Aspect 10 may be combined with any one of aspects 1 to 9, and further comprises receiving a subsequent DCI request for switching from the first BWP to the second BWP; and switching from the first BWP to the second BWP based on the subsequent DCI request.

[0112] Aspect 11 may be combined with any one of aspects 1 to 10, and includes receiving the DCI request based on blind decoding of the PDCCH.

[0113] Aspect 12 may be combined with any one of aspects 1 to 11, and comprises that the false positive detection of the DCI request is based on at least one of a reserved value associated with the DCI request or an inconsistent value in the DCI request.

[0114] Aspect 13 is an apparatus for wireless communication, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to execute the method as described in any one of aspects 1 to 12.

[0115] Aspect 14 is an apparatus for wireless communication, the apparatus comprising means for implementing the method as described in any one of aspects 1 to 12.

[0116] Aspect 15 may be combined with any of aspects 13 to 14 and further include at least one of a transceiver or an antenna coupled to at least one processor of the apparatus.

[0117] Aspect 16 is a non-transitory computer readable medium storing computer executable code, which, when executed by at least one processor, causes the at least one processor to implement the method as described in any one of aspects 1 to 12.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving a downlink control information (DCI) request for switching from a first bandwidth part (BWP) to a second BWP; as well as The DCI request for switching from the first BWP to the second BWP is rejected based on at least one of: a conflict with a time division duplex (TDD) mode associated with the DCI request, a DCI decoder metric, or a number of error-corrected modulation symbols indicating true or false detections of the DCI request.

2. The apparatus of claim 1 , wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the conflict with the TDD mode, and wherein the true or false detection of the DCI request is based on at least one of: a physical downlink shared channel (PDSCH) reception or a physical uplink shared channel (PUSCH) transmission associated with the switching including a timing conflict with the TDD mode. 3 . The apparatus of claim 2 , wherein the timing conflict with the TDD mode corresponds to at least one of the PDSCH reception or the PUSCH transmission being offset by at least one symbol within the TDD mode.

4. The apparatus of claim 1 , wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the conflict with the TDD mode, and wherein the DCI request for switching from the first BWP to the second BWP is received based on at least one of DCI 1_1 or DCI 0_1, wherein a first time domain resource allocation (TDRA) associated with the DCI 1_1 indicates at least one of a first offset, a starting symbol, or a number of symbol combinations between DCI reception and a physical downlink shared channel (PDSCH) reception, and wherein a second TDRA associated with the DCI 0_1 indicates at least one of a second offset, the starting symbol, or the number of symbol combinations between the DCI reception and a physical uplink shared channel (PUSCH) transmission. The apparatus of claim 4 , wherein the first offset and the second offset are based on a BWP switching time.

6. The apparatus of claim 1 , wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, and the at least one processor is further configured to: decode the DCI request to generate the DCI decoder metric based on a log likelihood ratio (LLR) associated with the error-corrected modulation symbol, the error-corrected modulation symbol corresponding to an orthogonal frequency division multiplexing (OFDM) symbol associated with the DCI request.

7. The apparatus of claim 6, wherein the at least one processor is further configured to estimate a number of errors associated with the encoded DCI based on a comparison between one or more received modulation symbols, and the DCI request for switching from the first BWP to the second BWP is rejected based on the number of errors associated with the one or more received modulation symbols.

8. The apparatus of claim 1 , wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, and wherein the DCI decoder metric corresponds to at least one of a highest signal-to-noise ratio (SNR), a difference between the highest SNR and a second highest SNR, or the number of error-corrected modulation symbols.

9. The apparatus of claim 1 , wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, the DCI decoder metric being based on a first false positive detection threshold associated with a BWP switching DCI, the first false positive detection threshold being lower than a second false positive detection threshold associated with a non-BWP switching DCI.

10. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a subsequent DCI request for switching from the first BWP to the second BWP; and Switching from the first BWP to the second BWP is requested based on the subsequent DCI.

11. The apparatus of claim 1, wherein the DCI request is received based on blind decoding of a physical downlink control channel (PDCCH).

12. The apparatus of claim 1, wherein the false positive detection of the DCI request is based on at least one of a reserved value associated with the DCI request or an inconsistent value in the DCI request.

13. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

14. A method of wireless communication at a user equipment (UE), the method comprising: receiving a downlink control information (DCI) request for switching from a first bandwidth part (BWP) to a second BWP; as well as The DCI request for switching from the first BWP to the second BWP is rejected based on at least one of: a conflict with a time division duplex (TDD) mode associated with the DCI request, a DCI decoder metric, or a number of error-corrected modulation symbols indicating true or false detections of the DCI request.

15. The method of claim 14, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the conflict with the TDD mode, and wherein the true or false detection of the DCI request is based on at least one of: a physical downlink shared channel (PDSCH) reception or a physical uplink shared channel (PUSCH) transmission associated with the switch including a timing conflict with the TDD mode. 16 . The method of claim 15 , wherein the timing conflict with the TDD mode corresponds to at least one of the PDSCH reception or the PUSCH transmission being offset by at least one symbol within the TDD mode.

17. The method of claim 14, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the conflict with the TDD mode, and wherein the DCI request for switching from the first BWP to the second BWP is received based on at least one of DCI 1_1 or DCI 0_1, wherein a first time domain resource allocation (TDRA) associated with the DCI 1_1 indicates at least one of a first offset, a starting symbol, or a number of symbol combinations between DCI reception and a physical downlink shared channel (PDSCH) reception, and wherein a second TDRA associated with the DCI 0_1 indicates at least one of a second offset, the starting symbol, or the number of symbol combinations between the DCI reception and a physical uplink shared channel (PUSCH) transmission. The method of claim 17 , wherein the first offset and the second offset are based on a BWP switching time.

19. The method of claim 14, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, the method further comprising: The DCI request is decoded based on a log likelihood ratio (LLR) associated with the error-corrected modulation symbol to generate the DCI decoder metric, the error-corrected modulation symbol corresponding to an orthogonal frequency division multiplexing (OFDM) symbol associated with the DCI request.

20. The method according to claim 19, further comprising: A number of errors associated with the encoded DCI is estimated based on a comparison between one or more received modulation symbols, and the DCI request for switching from the first BWP to the second BWP is rejected based on the number of errors associated with the one or more received modulation symbols.

21. The method of claim 14, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, and wherein the DCI decoder metric corresponds to at least one of a highest signal-to-noise ratio (SNR), a difference between the highest SNR and a second highest SNR, or the number of error-corrected modulation symbols.

22. The method of claim 14, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, the DCI decoder metric being based on a first false positive detection threshold associated with a BWP switching DCI, the first false positive detection threshold being lower than a second false positive detection threshold associated with a non-BWP switching DCI.

23. The method according to claim 14, further comprising: receiving a subsequent DCI request for switching from the first BWP to the second BWP; as well as Switching from the first BWP to the second BWP is requested based on the subsequent DCI.

24. The method of claim 14, wherein the DCI request is received based on blind decoding of a physical downlink control channel (PDCCH).

25. The method of claim 14, wherein the false positive detection of the DCI request is based on at least one of a reserved value associated with the DCI request or an inconsistent value in the DCI request.

26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving a downlink control information (DCI) request for switching from a first bandwidth part (BWP) to a second BWP; and Means for rejecting the DCI request for switching from the first BWP to the second BWP based on at least one of: a conflict with a time division duplex (TDD) mode associated with the DCI request, a DCI decoder metric, or a number of error corrected modulation symbols indicating true or false detections of the DCI request.

27. An apparatus according to claim 26, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the conflict with the TDD mode, and wherein the true or false detection of the DCI request is based on at least one of: a physical downlink shared channel (PDSCH) reception or a physical uplink shared channel (PUSCH) transmission associated with the switch including a timing conflict with the TDD mode.

28. The apparatus of claim 26, wherein the DCI request for switching from the first BWP to the second BWP is rejected based on the DCI decoder metric, the apparatus further comprising: Means for decoding the DCI request to generate the DCI decoder metric based on a log likelihood ratio (LLR) associated with the error-corrected modulation symbol, the error-corrected modulation symbol corresponding to an orthogonal frequency division multiplexing (OFDM) symbol associated with the DCI request.

29. The apparatus according to claim 28, further comprising: means for estimating a number of errors associated with the encoded DCI based on a comparison between one or more received modulation symbols, the DCI request for switching from the first BWP to the second BWP being denied based on the number of errors associated with the one or more received modulation symbols.

30. A non-transitory computer readable medium storing computer executable code at a user equipment (UE), which, when executed by at least one processor, causes the at least one processor to: receiving a downlink control information (DCI) request for switching from a first bandwidth part (BWP) to a second BWP; and The DCI request for switching from the first BWP to the second BWP is rejected based on at least one of: a conflict with a time division duplex (TDD) mode associated with the DCI request, a DCI decoder metric, or a number of error-corrected modulation symbols indicating true or false detections of the DCI request.

Images