CORESET and search space correlation with resource bandwidth

Abstract

A user equipment (UE) communicates with a base station operating in a sub-band frequency division duplex (FDD) mode. The UE receives downlink transmissions in an available bandwidth (BW) of an active downlink bandwidth part (BWP) in a sub-band full duplex (SBFD) time slot, wherein the available BW does not include frequency resources used for guard bands and uplink transmissions. The UE monitors one or more control resource sets (CORESETs) configured by the base station within the active downlink BWP during a monitoring opportunity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application Serial No. 63 / 040,992, filed on June 18, 2020, and entitled “CORESET AND SEARCHSPACE ASSOCIATION WITH RESOURCE BANDWIDTH,” and claims the benefit of U.S. Provisional Application Serial No. 63 / 040,957, filed on June 18, 2020, and entitled “CORESET AND SEARCH SPACE ENHANCEMENTS FOR USABLE BANDWIDTH OF ABANDWIDTH PART IN SUB-BAND FULL-DUPLEX,” and U.S. Patent Application No. 17 / 324,454, filed on May 19, 2021, and entitled “CORESET AND SEARCH SPACE ASSOCIATE WITH RESOURCE BANDWIDTH,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to control transmission for resource bandwidth. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communications 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 a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released 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 communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need to further improve 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards using these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not a general summary of all expected aspects and is not intended to identify key or important elements of all aspects or describe the scope of any or all aspects. Its purpose is only to serve as a prelude to the more detailed description given later, giving some concepts of one or more aspects in a simplified form.

[0007] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus may communicate with a base station operating in a sub-band frequency division duplex (FDD) mode. The apparatus may receive downlink transmissions within one or more resource bandwidths (RBWs) of an active bandwidth part (BWP). The apparatus monitors control transmissions from the base station within the one or more RBWs of the active BWP.

[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The apparatus may communicate with a UE in a sub-band FDD mode. The apparatus may send a downlink transmission in one or more RBWs of an active BWP. The apparatus may configure the UE to monitor control transmissions from the base station within the one or more RBWs of the active BWP.

[0009] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and access network according to some aspects.

[0011] Figure 2A , 2B , 2C and 2D are schematic diagrams showing examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively, according to some aspects.

[0012] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network according to some aspects.

[0013] Figure 4A , 4B 4C are schematic diagrams showing examples of full-duplex communication between a base station and a UE and associated interference.

[0014] Figure 5A and 5B is a schematic diagram showing examples of different types of full-duplex communications.

[0015] Figure 6 is a schematic diagram illustrating example leakage and mitigation between a downlink and an uplink for full-duplex communications.

[0016] Fig. 7A is a schematic diagram showing example RBWs within a BWP.

[0017] Figure 7B is a schematic diagram showing an example of a downlink / uplink BWP configuration for SBFD operation.

[0018] Figure 8 is a diagram showing an example format for a sub-band full-duplex (SBFD) time slot.

[0019] Fig. 9 is a schematic diagram showing an example of a plurality of BWPs and a CORESET for each BWP.

[0020] Fig.10 is a schematic diagram showing example CORESET configurations for half-duplex (HD) and SBFD time slots.

[0021] Fig.11 is a schematic diagram showing an example CORESET configuration.

[0022] Fig. 12A and 12B is a diagram showing an example of a bitmap for a CORESET.

[0023] Fig.13 is a schematic diagram showing an example CORESET configuration.

[0024] Fig.14 is a schematic diagram showing an example CORESET configuration.

[0025] Fig.15 is a schematic diagram showing an example CORESET configuration.

[0026] Fig.16 is a schematic diagram showing an example communication flow between a UE and a base station.

[0027] Fig.17 is a flow chart of a method of wireless communication.

[0028] Fig.18 is a flow chart of a method of wireless communication.

[0029] Fig.19 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus.

[0030] Fig. 20 is a flow chart of a method of wireless communication.

[0031] Fig.21 is a flow chart of a method of wireless communication.

[0032] Fig. 22 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus.

[0033] Fig.23 is a flow chart of a method of wireless communication.

[0034] Fig.24 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus.

[0035] Fig.25 is a flow chart of a method of wireless communication.

[0036] Fig.26 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0037] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in the form of block diagrams in order to avoid obscuring such concepts.

[0038] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the detailed description below 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0039] For example, an element, or any part of an element, or any combination of elements, can be implemented as a "processing system" including 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, gated logic, 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 names, 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, executable files, execution threads, processes, functions, etc.

[0040] Accordingly, in one or more example embodiments, the described functions can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can 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 computer-readable media types, or any other media that can be used to store computer executable code that can be accessed by a computer in the form of instructions or data structures.

[0041] Although various aspects and implementations are described in this application by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, implementation and / or use can be generated via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, equipment enabling artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) equipment or systems incorporating one or more aspects of the described innovations. In some actual settings, the equipment incorporating the described aspects and features may also include additional components and features for the implementation and implementation of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., having different sizes, shapes, and configurations.

[0042] Figure 1 1 is a diagram showing an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). 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). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0043] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can be connected to the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can be connected to the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transfer of user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and transmission of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0044] The base station 102 can communicate wirelessly with the UE 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services for a restricted group called a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other or may not be adjacent. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for 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).

[0045] 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 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 various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE 802.11) standard, LTE, or NR.

[0046] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi base station (STA) 152 via a communication link 154, such as in a 5 GHz unlicensed spectrum. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether a channel is available.

[0047] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0048] 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 with the frequency range names 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. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0049] 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 names FR3 (7.125GHz-24.25GHz). The bands falling into FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore 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 beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls into the EHF band.

[0050] In view of the above, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0051] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distance. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0052] Base station 180 may send beamformed signals to the UE in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also send beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction for base station 180 may or may not be the same. The transmit direction and receive direction for UE 104 may or may not be the same.

[0053] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides IP address allocation and other functions for the UE. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service setup and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to allocate MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting charging information related to eMBMS.

[0054] The core network 190 may include an access and mobility management function unit (AMF) 192, other AMFs 193, a session management function unit (SMF) 194, and a user plane function unit (UPF) 195. The AMF 192 may communicate with a unified data management unit (UDM) 196. The AMF 192 is a control node for processing signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides IP address allocation and other functions to the UE. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) stream (PSS) service, and / or other IP services.

[0055] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a heart monitor, etc.). UE 104 may also be referred to by those skilled in the art as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handheld device, a user agent, a mobile client, a client or some other appropriate terminology.

[0056] Reference again Figure 1 In some aspects, the UE 104 may include a monitoring component 198 configured to monitor the CORESET and SS configured by the base station in half-duplex operation or full-duplex operation, wherein the monitoring component 198 may monitor control transmissions from the base station within one or more RBWs of the active BWP, and apply different CORESET monitoring rules based on whether the base station is operating in full-duplex mode and based on the configuration sent by the base station. In some aspects, the base station may include a configuration component 199 configured to communicate with the UE 104 in sub-band FDD mode. For example, the configuration component 199 may send a downlink transmission in one or more RBWs of the active BWP. The configuration component 199 may configure the UE to monitor the control transmissions within one or more RBWs of the active BWP.

[0057] In certain aspects, the monitoring component 198 can be configured to monitor the CORESETs and SSs configured by the base station in half-duplex operation and full-duplex operation, wherein the monitoring component 198 can apply different CORESET monitoring rules based on whether the base station is operating in full-duplex mode. In certain aspects, the base station can include a configuration component 199 configured to communicate with the UE 104 in sub-band FDD mode using SBFD time slots. For example, the configuration component 199 can send a downlink transmission in an available BW of an active downlink BWP in the SBFD time slot, wherein the available BW does not include frequency resources for guard bands and uplink transmissions. The configuration component 199 can configure the UE to monitor one or more CORESETs within the active downlink BWP.

[0058] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0059] Figures 2A-2D Included are diagrams of example frame structures and resources that may be utilized in communications between base stations 102, UEs 104, and / or secondary UEs (or sidelink UEs) 110 as described in the present disclosure. Figure 2A FIG200 is a diagram showing an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram showing an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to both DL and UL). Figure 2A , 2CIn the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown using slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full 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 through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure as TDD.

[0060] Figures 2A-2D The frame structure is shown, and various aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of equal size. 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 7 or 14 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 7 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (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 referred to 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 may be based on the CP and numerology. The digital scheme defines the subcarrier spacing (SCS) and, in effect, the symbol length / duration (which is equal to 1 / SCS).

[0061]

[0062] For normal CP (14 symbols / slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, digital scheme 2 allows 4 slots per subframe. Accordingly, for normal CP and digital scheme μ, there are 14 symbols / slot and 2 μThe subcarrier spacing may be equal to 2μ*15kHz, where μ is a digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D Examples are provided for a normal CP (with 14 symbols per slot) and a digital scheme μ=2 (with 4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific number scheme and CP (normal or extended).

[0063] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0065] Figure 2BExamples of various DL channels within a subframe of a frame are shown. 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 larger and / or lower frequencies across 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 identity. 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), which carries the master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent via the PBCH (e.g., system information block (SIB)), and paging messages.

[0066] like Figure 2C As shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may send DM-RS for a physical uplink control channel (PUCCH) and 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. The PUCCH DM-RS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and on the specific PUCCH format used. Although not shown, the UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of the subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs in the comb. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0067] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned 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 buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0068] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. 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 functions 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 functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission 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 functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), and MAC Demultiplexing of SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

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

[0070] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream going to the UE 350. If multiple spatial streams go to the UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. Subsequently, the RX processor 356 uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. 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 the channel estimate 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 base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0071] 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 and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0072] Similar to the functions described in conjunction with the DL transmission by the base station 310, the controller / processor 359 provides: RRC layer functions, which are associated with the following: system information (e.g., MIB, SIB) acquisition, RRC connection and test reporting; PDCP layer functions, which are associated with the following: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions, which are associated with the following: transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions, which are associated with the following: 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.

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

[0074] 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 respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0075] 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 and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0076] 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 198 related aspects.

[0077] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 199 related aspects.

[0078] In addition to half-duplex operation, a communication network (such as a communication network based on 5G NR) can also support full-duplex operation. Full-duplex operation can effectively increase the capacity of the communication network. The base station and UE in the communication network can support full-duplex operation respectively. For example, a base station in a communication network can support full-duplex operation, and one or more UEs in the communication network can support half-duplex operation without supporting full-duplex operation. In another example, a base station in a communication network can support full-duplex operation, and one or more UEs in the communication network can also support full-duplex operation. In another example, a base station in a communication network can support half-duplex operation without supporting full-duplex operation, and one or more UEs in the communication network can support full-duplex operation.

[0079] Regardless of whether the base stations and UEs in the communication network individually support full-duplex operation, interference may be a problem for full-duplex operation. Figure 4AAs shown in the schematic diagram 400 in FIG. 4 , two base stations 404A and 404B operating in full-duplex mode and two UEs (UE1 402A and UE2 402B) operating in half-duplex mode are shown in the depicted example. Although the base station 404A can simultaneously send downlink data to UE1 402A and receive uplink data from UE2 402B, self-interference between uplink reception and downlink transmission may occur at the base station 404A. For example, a receiver at the base station may receive the transmitted downlink signal as interference to the uplink signal from UE2 402B. In addition, because UE1 402A may be receiving downlink data and UE2 402B may be sending uplink data at the same time, the transmission from UE2 402B may interfere with the downlink signal being received by UE1 402A. Furthermore, because base station 404B may also be receiving uplink data from UE2 402B and sending downlink data to UE1 402A, interference between base stations 404A and 404B may occur.

[0080] Similarly, if Figure 4B As shown in the schematic diagram 410 in FIG. 4 , when two base stations 404A and 404B and two UEs (UE1 402A and UE2 402B) may each operate in full-duplex mode, self-interference from uplink transmission to downlink reception at the UE (UE1 in the example shown) may also occur. Even when the base station is not operating in full-duplex mode, self-interference from uplink transmission of the UE to downlink reception at the same UE may also occur. Figure 4C As shown in diagram 420 in FIG. 4 , when two base stations 404A and 404B operate in half-duplex mode, and UEs (UE1 402A and UE2 402B) operate in full-duplex mode, self-interference may occur from uplink transmission of UE1 to downlink reception at UE1 402A.

[0081] Full-duplex operation can be in the form of in-band full-duplex (IBFD) or sub-band frequency division duplex (FDD) (also known as "flexible duplex"). Figure 5A As shown in the schematic diagram 500 in FIG. 5 , for IBFD, transmission and reception may occur simultaneously (eg, overlapping in time) and on the same frequency resources (eg, using overlapping frequency resources). Figure 5A As shown, in some examples, the IBFD time / frequency resources for downlink 502A and the IBFD time / frequency for uplink 504A can completely overlap. In other examples, such as Figure 5AAs shown, the IBFD time / frequency resources for the downlink 502B and the IBFD time / frequency resources for the uplink 504B may partially overlap.

[0082] For sub-band FDD, if Figure 5B As shown in the schematic diagram 510 in FIG. 5 , transmission and reception may occur simultaneously (e.g., at least partially overlapping in time) but on different frequency resources. The downlink resources 502C may be separated from the uplink resources 504C in the frequency domain. For example, such separation may be referred to as a guard band 506 and may provide a frequency gap or frequency separation between the downlink frequency resources 502C and the uplink frequency resources 504C.

[0083] Figure 6 An example 600 depicting half-duplex communications and full-duplex communications is shown. Figure 6 Half-duplex communications during time periods 602 and 606 and full-duplex communications during time period 604 are shown. Without a mechanism for mitigating interference between full-duplex uplink and downlink communications, leakage between downlink and uplink communications can severely degrade communications. Full-duplex operation can be based on two separate antenna panels at a UE or base station. A first panel (panel #1) for downlink transmissions can be provided. For example, a base station can use the first panel to send downlink transmissions, while a UE can use the first panel to receive downlink transmissions. Downlink communications can be sent / received at both edges of the frequency band, such as at Figure 6 The second panel (panel #2) may be used for uplink reception / transmission. For example, the base station may use the second panel to receive uplink transmissions, while the UE may use the second panel to send uplink transmissions. Uplink communications may be provided in the middle of the frequency band, such as Figure 6 In addition, for sub-band full-duplex, downlink communications and uplink communications may not be in different parts of the frequency band and may be separated in frequency by a guard band.

[0084] To provide better isolation between downlink and uplink communications, in one example, receive time-domain windowed overlap and add (Rx-WOLA) can be used on the downlink signal to reduce adjacent channel leakage ratio (ACLR) leakage to the uplink signal. In another example, an analog low-pass filter (LPF) can be used to improve the (analog-to-digital conversion) ADC dynamic range. In yet another example, the receive (Rx)-automatic gain control (AGC) state can be improved to improve the noise factor (NF). In addition, a digital integrated circuit for ACLR leakage can be provided, and a nonlinear model can be provided for each receive-transmit pair.

[0085] The communication network may support the use of bandwidth parts (BWPs), where a BWP may be a set of continuous PRBs on a given component carrier (CC). In other words, a BWP may be continuous in frequency. Data channels and control channels may be received and / or sent within a BWP. A BWP may provide the network with more flexibility in assigning resources in a given CC, because a BWP may implement multiplexing of different signals and signal types to more efficiently use spectrum and UE power. A CC may be divided into multiple BWPs (e.g., one to four BWPs per CC) for uplink transmission and / or downlink transmission. For example, for each serving cell, a UE may be configured with up to four downlink BWPs and up to four uplink BWPs. Although multiple BWPs may be defined in the downlink and uplink, in some aspects, at a given time on an active serving cell, one active BWP may exist in the downlink and one active BWP may exist in the uplink. An active BWP may define the operating bandwidth of a UE within the operating bandwidth of a cell. The UE may not send or receive data using a BWP that is configured for the UE but is not activated (eg, deactivated or otherwise inactive).

[0086] Since the UE can have one active BWP in the uplink and one active BWP in the downlink at a time, in order to switch from one BWP to another, the UE can deactivate the current active BWP and activate the next BWP. This can be referred to as "BWP activation / deactivation" and / or "BWP switching". There may be a delay time for the UE to switch from one BWP to another, and the switching delay time may sometimes be very long. There are multiple ways for the UE to initiate or perform BWP switching. For example, BWP switching can be configured to the UE via DCI, where a specific BWP can be activated by a BWP indicator in the DCI (e.g., a BWP activation or deactivation command). For a downlink BWP, BWP switching can be activated by a timer, such as a BWP inactivity timer (e.g., Bwp-InactivityTimer: ServingCellConfig.bwp-InactivityTimer, etc.). BWP switching can also be activated by RRC signaling and / or by a MAC entity (e.g., MAC CE). In time division duplex (TDD), the UE may perform downlink BWP switching and uplink BWP switching simultaneously, whereas in frequency division duplex (FDD), the UE may perform downlink BWP switching and uplink BWP switching independently.

[0087] Since BWPs may be continuous in frequency (e.g., continuous RB allocations), and resources for sub-band full-duplex (SBFD) operation may have disjoint downlink or uplink bandwidths (BWs), aspects presented herein may enable active uplink / downlink BWPs to be used for SBFD operation. When separate BWPs are defined for TDD and SBFD time slots, aspects presented herein may avoid or reduce BWP switching delays.

[0088] Fig. 7A 7 is a diagram 700 illustrating example RBWs within a BWP 704 . Fig. 7A It is shown that there are 4 RBWs within the active BWP, namely, RBW1 706, RBW2 708, RBW3 710A and 710B, and RBW4 712. Uplink communications and downlink communications can have different RBW configurations and can utilize different RBWs. Each of these RBWs can have its corresponding resources defined or configured separately. For example, a resource block group (RBG) can be configured and optimized separately for each of the RBWs. In addition, a frequency domain resource assignment (FDRA) can be determined for each of the RBWs, and the FDRA can be defined using a smaller number of bits. The RBWs used for the uplink and downlink can be non-overlapping or partially overlapping. In some aspects, the RBWs used for the uplink and downlink can be non-overlapping for SBFD and can be partially overlapping for IBFD, such as in conjunction with Figure 5A and 5B As described. The active resource bandwidth may be dynamically indicated from a base station to a UE (such as in a DCI). In some aspects, the DCI indication may be slot-based, i.e., all symbols within a slot may have the same active RBW. In some aspects, symbols may be grouped into bundles of N symbols. In some aspects, a time domain resource assignment (TDRA) may be indicated per resource in the DCI.

[0089] Since BWPs may be continuous in frequency (e.g., continuous RB allocations), and resources for sub-band full-duplex (SBFD) operation may have disjoint downlink or uplink bandwidths (BWs), aspects presented herein may enable active uplink / downlink BWPs to be used for SBFD operation. When separate BWPs are defined for TDD and SBFD time slots, aspects presented herein may avoid or reduce BWP switching delays. Figure 7B7 is a schematic diagram 750 showing an example downlink / uplink BWP configuration for SBFD operation. Since not all BWPs or all BWs within a BWP may be available at a given time under SBFD operation, it may be further defined or configured for the UE which BWs within the active BWP will be used by the UE for uplink and / or downlink. For example, the UE may be configured to use BWs 756 and 758 within a downlink BWP 752 for downlink, and may use BW 760 within an uplink BWP 754 for uplink. BWs 756, 758 may be referred to as subsets of BWPs or available BWs in a DL BWP. The available BWs in each BWP may be segmented as shown in FIG. 7, wherein each available BW may occupy a different frequency range in an uplink / downlink BWP. A guard band 762 (e.g., a gap) may also be provided between the available BWs of the active downlink and uplink BWPs to reduce or prevent interference. Thus, the available BW in the downlink BWP may be a subset of the downlink BWP (e.g., 756) that does not include frequency resources used as a guard band (e.g., 762) or frequency resources used for uplink transmission (e.g., 760). This configuration of the BWP may enable implicit switching between half-duplex mode and full-duplex mode based on the duplex characteristics of a time slot or symbol.

[0090] Figure 8 8 is a diagram 800 illustrating an example format for an SBFD timeslot 802, wherein the SBFD timeslot may include both downlink resource allocations and uplink resource allocations for wireless devices and, for purposes of the present disclosure, may be referred to as a "D+U timeslot." Although referred to as an SBFD timeslot, in some examples, 802 may correspond to one or more timeslots in a time period. In one aspect, a D+U timeslot may be a timeslot in which a frequency band is used for both uplink transmissions and downlink transmissions. Uplink transmissions and downlink transmissions may occur in overlapping frequency bands (e.g., intra-band full-duplex) or in adjacent frequency bands (e.g., sub-band full-duplex), such as in conjunction with Figure 5A and 5BAs described. For example, in one or more given symbols within the D+U time slot, a half-duplex UE may send data in an uplink frequency band or receive data in a downlink frequency band, while a full-duplex UE may send data in an uplink frequency band and / or receive data in a downlink frequency band. Therefore, a "D+U" time slot may contain downlink symbols, uplink symbols, or full-duplex symbols (e.g., a combination of both uplink symbols and downlink symbols). For example, a full-duplex UE may use symbols within the SBFD time slot 802 to send and receive data, while a half-duplex UE may send or receive data at symbols within the SBFD time slot 802. Other time periods may also be included, such as a time slot that may be used for downlink data (such as 806), or a time slot that may be used for uplink data (such as 804).

[0091] The BWP may also be configured with various parameters, which may include a digital scheme, frequency location, bandwidth size, and / or a control resource set (CORESET). A CORESET may define the frequency domain resource blocks (RBs) and time domain duration (i.e., the number of consecutive symbols) of the control region of the PDCCH. For example, a CORESET may correspond in time and frequency to a set of physical resources used by a UE to monitor PDCCH / DCI, wherein each CORESET may include one or more resource blocks in the frequency domain and one or more symbols in the time domain. As an example, a CORESET may include multiple RBs in the frequency domain and 1, 2, or 3 consecutive symbols in the time domain. A resource element (RE) is a unit used to indicate one subcarrier in frequency within a single symbol in time. A control channel element (CCE) includes a resource element group (REG) (e.g., 6 REGs), wherein a REG may correspond to one RB (e.g., 12 REs) during one OFDM symbol. REGs within a CORESET may be numbered in ascending order in a time-first manner, starting from 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set. A UE may be configured with multiple CORESETs (e.g., up to three), each CORESET being associated with a mapping of CCEs to REGs. Each CORESET may be assigned a CORESET identifier (ID). Since each UE may use up to four BWPs in transmission, a UE may be configured with up to 12 CORESETs on a serving cell, each of which may be assigned an index of 0-11 (e.g., CORESET#0, CORESET#1, CORESET#2). A CORESET with ID=0 (e.g., CORESET#0) may be configured by a master information block (MIB).

[0092] A UE can perform blind decoding on a PDCCH candidate set, where the PDCCH candidates to be monitored for the UE can be configured via a search space (SS) set. Thus, the SS set associated with a CORESET can be used to define the time slot pattern and the starting symbol of the control region in each time slot of the pattern. The UE can determine the time slots for monitoring the SS set based on (period k, offset o, duration T<k). There can be one or more types of SS sets, such as a common SS (CSS) set that is typically monitored by a group of UEs in a cell, and there can be a UE-specific SS set monitored by a specific UE, etc. For example, a type 0-PDCCH CSS set can be used for the PDCCH that schedules system information block 1 (SIB1), a type 0A-PDCCH CSS set can be used for the PDCCH that schedules other system information (OSI), a type 1-PDCCH CSS can be used for the PDCCH related to random access, a type 2-PDCCH CSS set can be used for the PDCCH that schedules paging messages, a type 3-PDCCH CSS set can be used for all other PDCCHs monitored in the CSS, a UE-specific search space (USS) set can be used for the PDCCH that schedules UE-specific data, and so on.

[0093] A CORESET can be defined at the cell level, and the list of CORESETs to be monitored by the UE can be indicated in the active BWP. The base station can configure multiple CORESETs and multiple SS sets for the UE in the active BWP. For example, the base station can configure up to three CORESETs and 10 SS sets per BWP for the UE. Since the UE can be configured for multiple BWPs (e.g., up to four BWPs), the UE can be configured with up to 40 SS sets and 12 CORESETs, where each SS set can be assigned an index from 0 - 39, and each CORESET can be assigned an index from 0 - 11. Each SS set can be associated with a CORESET. For example, each CORESET ID of the CORESETs configured for the UE can be mapped to a specific BWP, and each SS set ID of the multiple SS sets configured for the UE can be mapped to a specific BWP. Fig. 9 An example time and frequency diagram 900 depicting multiple BWPs and the CORESETs for each BWP is shown. The SS can include a set of CCEs (e.g., at different aggregation levels). For example, the SS can indicate the number of candidates to be decoded (e.g., where the UE performs decoding).

[0094] The frequency domain resources of a CORESET may be defined by a bit string (i.e., a bitmap), where each bit in the bit string may map or correspond to 6 RBs in a BWP (e.g., frequencyDomainResources, BIT STRING(SIZE(45)), etc.), and the UE may monitor the CORESETs defined within the active BWP. However, since not every portion of the BW is available in a BWP in a SBFD timeslot (i.e., a subset of the BWP may be available in a SBFD timeslot, such as illustrated by FIG. 7 ), a CORESET associated with a BWP may partially or completely fall outside of the available BW in a SBFD timeslot. For example, Fig.10 1 is a diagram 1000 showing an example CORESET configuration for HD and D+U timeslots (e.g., SBFD timeslots) for a UE. At 1002, CORESET#2 may be monitored in a downlink regular HD timeslot 1006. However, when CORESET#2 is monitored in a D+U timeslot 1008 at 1004, CORESET#2 may overlap or intersect with both the downlink BWP (e.g., 1012, 1016) and the uplink (1014) BWP, such as shown at 1010. Since the UE may be configured to monitor a CORESET defined within an active BWP (e.g., UL BWP), the UE may not be able to monitor CORESET#2 at 1004 in this case.

[0095] Aspects presented herein may provide more flexibility for configuration of CORESET frequency domain resources. For example, some aspects may provide more flexibility for configuration of CORESET frequency domain resources, wherein overlap or intersection between downlink BWP and uplink BWP in CORESET and SBFD time slots may be reduced or avoided.

[0096] In some aspects, the CORESETs may be defined at the cell level and the CORESETs to be monitored may be indicated in the active BWP. In some examples, a full-duplex aware UE (a UE that is aware of full-duplex operation within the communication system but is not configured to perform full-duplex operation) may be configured to exclude monitoring opportunities for CORESETs that fall partially or completely outside of the active RBWs of one or more RBWs 1018A, 1018B, and 1018C (such as by Fig.10 1004 as shown in CORESET#2).

[0097] To allow more flexibility and compensate for the limitation of eliminating monitoring opportunities, in one set of aspects, such as in Fig.11As shown in the example 1100 in FIG. 1 , a CORESET may be configured to be associated with each of one or more RBWs 1108A and 1108B. For example, CORESET #1, #2, and #3 1102 may be associated with RBW1 1118A, and CORESET #4 and #5 1104 may be associated with RBW2 1118B. In some aspects, the CORESETs to be monitored may be indicated in the active RBW, and the UE may not monitor CORESETs outside of the active RBW. For example, if RBW2 1118B is the active RBW, the UE may monitor CORESET #4 and #5 1104. Thus, the UE may have more flexibility in receiving downlink transmissions and / or monitoring CORESETs.

[0098] The UE may monitor monitoring opportunities for CORESETs within an active RBW in one or more RBWs, regardless of whether the base station is operating in half-duplex mode or full-duplex mode. The CORESETs to be monitored may be indicated in the active RBW using a maximum number of CORESETs per BWP (e.g., 4 or another number). In some aspects, the UE is still configured to exclude monitoring opportunities for CORESETs that fall partially or completely outside of the active RBW.

[0099] In some aspects, a configuration of a bitmap of frequency resources corresponding to resource blocks (RBs) in one or more RBWs may be sent to the UE. In some aspects, the UE may also receive a configuration of one or more search space (SS) sets in the RBW and a SS set for defining one or more monitoring opportunities for a CORESET in the RBW.

[0100] In another set of aspects, a CORESET may be associated with a BWP instead of one or more RBWs. The interpretation of a bitmap / bit string (such as a bitmap frequencyDomainResources) may be different for each RBW. For example, in some aspects, a UE may map a usable subset of the configured bitmap of frequency domain resources and may map bits to each of one or more RBWs (RBW_i) instead of the entire BWP.

[0101] In some aspects, a field or indication may be added to an information element (IE) defined by the SS. For example, a field such as a mode field may be added to the IE of the SS to indicate whether a bitmap associated with a BWP is to be interpreted in half-duplex mode or in full-duplex mode. When the mode field indicates half-duplex mode, the bitmap may be interpreted as mapping the entire BWP, and when the mode field indicates full-duplex mode, the bitmap may be interpreted as mapping active RBWs in one or more RBWs without mapping inactive RBWs. In other words, when the SS is defined to monitor a CORESET in an SBFD timeslot and in full-duplex mode, the UE may interpret the bitmap as corresponding to the RBs in the active RBWs of the BWP. Thus, one type of SS may be used for HD timeslots (e.g., in half-duplex mode), while another type of SS may be used for D+U timeslots (e.g., in full-duplex mode), and so on.

[0102] In one aspect, a full-duplex aware UE (e.g., a UE that can perceive full-duplex operation present in the communication system but is unable to perform full-duplex operation) can be configured to exclude monitoring opportunities for the CORESET that fall partially or completely outside of the available BW in the SBFD time slot when the base station is operating in full-duplex mode (such as by Fig.10 2 at 1004 in FIG. 10A ). However, the UE may continue monitoring opportunities for CORESETs within the available BW. Additionally or alternatively, to compensate for this configuration or limitation, the maximum number of CORESETs in a BWP may be increased so that additional CORESETs may be configured for the UE (e.g., via SS sets) to allow for more flexibility in the frequency location of monitoring opportunities. For example, Fig.11 As shown in the schematic diagram 1100 in FIG. 1 , an additional CORESET #4 may be configured to the UE for monitoring (e.g., in addition to CORESET #1 to #3), such as shown at 1104. Since CORESET #2 (e.g., 1102) may not be used in the S+D timeslot 1108 due to overlap, the UE may have more flexibility in receiving downlink transmissions and / or monitoring CORESETs by having an additional CORESET configured in the BWP (e.g., SBFD timeslot). The configuration for the SS may also remain unchanged, where each SS set may still be associated with a CORESET. In addition, the base station may configure the UE to avoid monitoring more than a certain number of CORESETs in a given timeslot. For example, the UE may be configured to avoid monitoring more than four CORESETs in any given timeslot. Therefore, returning to reference Fig.11, the UE may monitor CORESET#2 (e.g., 1102) and a new additional CORESET#4 (e.g., 1104) at different time slots. Since the CORESETs are not allocated in the same time slot, increasing the maximum number of CORESETs and / or configuring additional CORESETs for the UE may not increase the complexity of the system and / or implementation. In another example, when the base station is operating in half-duplex mode, the base station may configure the UE to monitor up to four CORESETs in the active downlink BWP, and when the base station is operating in full-duplex mode, the base station may configure the UE to monitor additional CORESETs (e.g., in addition to the four CORESETs). Therefore, when the base station is operating in full-duplex mode, the UE may monitor more than four CORESETs (e.g., five, six CORESETs, etc.). The base station may configure the UE via an SS set, wherein the SS set may be associated with a CORESET, and the SS may also define the monitoring timing for the CORESETs in the available BW.

[0103] In another aspect, in full-duplex operation, the UE may apply additional or different interpretations / configurations of the bitmap / bit string (e.g., frequencyDomainResources) corresponding to the CORESET at monitoring opportunities (e.g., CORESET monitoring) in SBFD timeslots, e.g., when the maximum number of CORESETs remains the same (e.g., up to three). In one example, in half-duplex operation where there are no D+U timeslots, the bits of the bitmap for the CORESET may be mapped to the entire BWP (such as by Fig. 12A 1200A in FIG. 1200A ), and each bit of the bitmap may correspond to 6 RBs in the BWP. On the other hand, during full-duplex operation involving D+U time slots, if the size of the available BW is equal to 'd' RBs ('d' is a value), a subset (e.g., a portion) of the bitmap may be used, wherein the bits of the bitmap may be mapped to the available BW (e.g., 'd' RBs) instead of the entire BWP. For example, as described by Fig. 12B As shown in the schematic diagram 1200B in FIG. Fig. 12A As shown mapping the bitmap to the entire BWP, the bitmap 1202 for monitoring opportunities in full-duplex operation (eg, in a SBFD timeslot) may be configured to map to available BWs (eg, 1204 and 1206), and mapping to unavailable BWs may be excluded.

[0104] For UE Fig. 12A The bitmap (e.g., frequencyDomainResources) for half-duplex operation (e.g., a base station operating in half-duplex mode) described in Fig. 12BIn order to interpret the bitmap for full-duplex operation (e.g., a base station operating in full-duplex mode) described in , a field or indication may be added to the information element (IE) defined by the SS. For example, a field (e.g., a mode field) may be added to the IE of the SS to indicate whether the bitmap associated with the BWP is to be interpreted in half-duplex mode or in full-duplex mode. When the mode field indicates half-duplex mode, the bitmap may be interpreted as mapping the entire BWP, and when the mode field indicates full-duplex mode, the bitmap may be interpreted as mapping the available BW without mapping the unavailable BW. In other words, when the SS is defined to monitor a CORESET in an SBFD timeslot and in full-duplex mode, the UE may interpret the bitmap as corresponding to RBs in the available BW of the BWP. Thus, one type of SS may be used for half-duplex timeslots (e.g., in half-duplex mode), and another type of SS may be used for D+U timeslots (e.g., in full-duplex mode), and so on.

[0105] In another aspect, instead of applying different interpretations or configurations to the bitmap / bit string (e.g., frequencyDomainResources) of the CORESET at the monitoring opportunity in the SBFD timeslot, the UE may receive two frequency domain resource definitions for the CORESET in the configuration from the base station. In this example, the maximum number of CORESETs may remain the same (e.g., up to three) for either the SBFD timeslot or the half-duplex timeslot. In one example, a new field (e.g., frequencyDomainResources_FD) may be used to define the frequency domain resources of the CORESET in the SBFD timeslot (e.g., D+U timeslot) of the communication system. Thus, for a half-duplex timeslot (e.g., under half-duplex operation), the CORESET may be defined by a first frequency domain definition (e.g., frequencyDomainResources), while for a SBFD timeslot, the CORESET may be defined by a second frequency domain definition (e.g., frequencyDomainResources_FD), and so on. Similarly, in order for the UE to determine which frequency domain definition to use for the CORESET, a field or indication may be added to the IE defined by the SS. For example, a mode field may be added to the IE of the SS to indicate to the UE whether to use a frequency domain definition associated with a half-duplex mode (e.g., a half-duplex time slot) or a frequency domain definition associated with a full-duplex mode. Thus, when the IE of the SS indicates the half-duplex mode, the UE may use a frequency domain definition associated with the half-duplex mode (e.g., frequencyDomainResources), and when the IE of the SS indicates the full-duplex mode, the UE may use a frequency domain definition associated with the full-duplex mode (e.g., frequencyDomainResources_FD).

[0106] Fig.13 1300 is a diagram illustrating an example implementation of two frequency domain interpretations. A first SS (SS1 1306) may define monitoring opportunities in a regular HD time slot and may be associated with a CORESET defined by RBW1 at 1302. Similarly, a second SS (SS2 1308) may define monitoring opportunities in a SBFD time slot and may be associated with a CORESET defined by RBW2 at 1304.

[0107] In another set of aspects, a CORESET may still be associated with a BWP, and instead of defining different interpretations or configurations for a bitmap / bit string (e.g., frequencyDomainResources) for a CORESET, a bitmap list (such as frequencyDomainResources_RBW_i) may be provided that may each define frequency domain resources for each of the different RBWs. The SS for a CORESET in RBW_i may monitor the frequency domain resources indicated by frequencyDomainResources_RBW_i. In one example, a new field (e.g., frequencyDomainResources_RBW_i) may be used to define the RBW associated with a CORESET in a SBFD timeslot (e.g., D+U timeslot) for the communication system. Thus, for a conventional HD timeslot (in half-duplex operation), a CORESET may be defined by a first frequency domain definition (e.g., frequencyDomainResources), while for a SBFD timeslot, a CORESET may be defined by a second frequency domain definition (e.g., frequencyDomainResources_RBW_i) based on the active RBW.

[0108] Fig.141400 is a diagram illustrating an example implementation of two frequency domain definitions, wherein a first frequency domain definition (e.g., frequencyDomainResources_RBW_1) may be provided for a CORESET (e.g., CORESET#1 at 1402) in a first RBW (e.g., under full-duplex operation), and a second frequency domain definition (e.g., frequencyDomainResources_RBW_2) may be provided for a CORESET (e.g., CORESET#1 at 1404) in a second RBW (e.g., also under full-duplex operation). In addition, a first SS (e.g., SS1 1406) may be configured to define monitoring opportunities associated with CORESET#1 at 1402. Similarly, a second SS (e.g., SS2 1408) may be configured to define monitoring opportunities associated with CORESET#2 at 1404. In some aspects, a first frequency domain definition (e.g., frequencyDomainResources) may be provided for a CORESET (e.g., CORESET#1 at 1402) in a half-duplex time slot (e.g., in half-duplex operation), and a second frequency domain definition (e.g., frequencyDomainResources_FD) may be provided for a CORESET (e.g., CORESET#1 at 1404) in a SBFD time slot (e.g., in full-duplex operation). In addition, a first SS (e.g., SS1 1406) may be configured to define monitoring opportunities in a half-duplex time slot and may be associated with CORESET#1 at 1402. Similarly, a second SS (e.g., SS2 1408) may be configured to define monitoring opportunities in a SBFD time slot (e.g., D+U time slot) and may be associated with CORESET#1 at 1304. Thus, when the UE receives SS1 1406, the UE may be configured to monitor CORESET#1 in a half-duplex time slot, such as CORESET#1 at 1402. When the UE receives SS2 1408, the UE may be configured to monitor CORESET#1 in a SBFD timeslot, such as CORESET#1 at 1404, and so on.

[0109] Fig.151500 is a diagram illustrating an example implementation of two frequency domain definitions, wherein a first frequency domain definition (e.g., frequencyDomainResources) is provided for a CORESET (e.g., CORESET#1 at 1502) in a half-duplex time slot (e.g., under half-duplex operation), and a second frequency domain definition (e.g., frequencyDomainResources_FD) is provided for a CORESET (e.g., CORESET#1 at 1504) in a SBFD time slot (e.g., under full-duplex operation). In addition, a first SS (e.g., SS1 1506) can be configured to define monitoring opportunities in half-duplex time slots and can be associated with CORESET#1 at 1302. Similarly, a second SS (e.g., SS2 1508) can be configured to define monitoring opportunities in SBFD time slots (e.g., D+U time slots) and can be associated with CORESET#1 at 1504. Thus, when the UE receives SS1 1506, the UE may be configured to monitor CORESET#1 in a half-duplex timeslot, such as CORESET#1 at 1502. When the UE receives SS2 1508, the UE may be configured to monitor CORESET#1 in a SBFD timeslot, such as CORESET#1 at 1504, and so on.

[0110] Fig.16 1600 is an example communication flow between UE 1602 and base station 1604. In some aspects, at 1606, UE 1602 and base station 1604 may communicate with each other in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B. During the communication, the base station 1404 sends / receives downlink / uplink transmissions 1608 in one or more RBWs of the active BWP. At 1610, the base station 1604 may configure the UE 1602 to monitor one or more CORESETs configured by the base station within the active BWP. In response to the configuration, at 1612, the UE 1602 may monitor one or more CORESETs within the active downlink BWP during the monitoring opportunity based on the configuration received at 1610.

[0111] In some aspects, based on the configuration at 1610, a CORESET is associated with an RBW, and the UE 1602 is configured to exclude monitoring opportunities for CORESETs that fall partially or completely outside of an active RBW. The CORESETs to be monitored by the UE 1602 may be indicated using a maximum number of CORESETs per BWP in an active RBW in one or more RBWs.

[0112] In some aspects, based on the configuration at 1610, a CORESET may be associated with a BWP instead of one or more RBWs. For each RBW, the interpretation of a bitmap / bit string (such as a bitmap frequencyDomainResources) may be different. For example, in some aspects, a subset of a bitmap may be used, and a bit may be mapped to each of one or more RBWs (RBW_i) instead of the entire BWP. In some aspects, a field or indication may be added to an information element (IE) defined by the SS. For example, a field such as a mode field may be added to the IE of the SS to indicate whether the bitmap associated with the BWP is to be interpreted in half-duplex mode or in full-duplex mode. When the mode field indicates half-duplex mode, the bitmap may be interpreted as mapping the entire BWP, and when the mode field indicates full-duplex mode, the bitmap may be interpreted as mapping active RBWs in one or more RBWs without mapping inactive RBWs. In other words, when the SS is defined as monitoring a CORESET in an SBFD slot and in full-duplex mode, the UE may interpret the bitmap as an RB in an active RBW corresponding to the BWP. Thus, one type of SS may be used for HD timeslots (eg, in half-duplex mode) and another type of SS may be used for D+U timeslots (eg, in full-duplex mode). The UE 1602 may monitor the CORESET based on different interpretations and IEs.

[0113] In another set of aspects, based on the configuration at 1610, a CORESET may still be associated with a BWP, and instead of defining different interpretations or configurations for a bitmap / bit string (e.g., frequencyDomainResources) for a CORESET, a bitmap list (such as frequencyDomainResources_RBW_i) may be provided, each defining a frequency domain resource for each of the different RBWs. The SS for a CORESET in RBW_i may monitor the frequency domain resources indicated by frequencyDomainResources_RBW_i. In one example, a new field (e.g., frequencyDomainResources_RBW_i) may be used to define the RBW associated with a CORESET in a SBFD timeslot (e.g., D+U timeslot) for a communication system. Thus, for a conventional HD timeslot (e.g., in half-duplex operation), a CORESET may be defined by a first frequency domain definition (e.g., frequencyDomainResources), while for a SBFD timeslot, a CORESET may be defined by a second frequency domain definition (e.g., frequencyDomainResources_RBW_i) according to the active RBW.

[0114] In some aspects, at 1606, UE 1606 and base station 1604 may communicate with each other in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B. During the communication, the base station 1604 may send a downlink transmission 1608 in the available BW of the active downlink BWP in the SBFD time slot (such as described in conjunction with Figures 7 and 8), wherein the available BW may not include frequency resources for guard bands and uplink transmissions. At 1610, the base station 1604 may configure the UE to monitor one or more CORESETs configured by the base station within the active downlink BWP. In response, the UE 1602 may monitor one or more CORESETs within the active downlink BWP during the monitoring period based on the configuration received at 1610.

[0115] In one example, when the base station is operating in full-duplex mode, the UE 1602 can determine whether the monitoring opportunity for the CORESET falls partially or completely outside the available BW. The UE 1602 can be configured to ignore the monitoring opportunities that fall partially or completely outside the available BW in the SBFD time slot. However, the UE 1602 can continue to monitor the CORESETs that do not fall outside the available BW or intersect with the unavailable BW. In addition, if the UE 1402 is configured not to monitor the CORESETs that fall partially or completely outside the available BW, the base station 1604 can also configure or indicate additional CORESETs to the UE at 1610, such as in conjunction with Fig.11 As described. In one example, when the base station 1604 is operating in half-duplex mode, the base station 1604 may configure the UE 1602 to monitor up to four CORESETs within the active downlink BWP, and when the base station is operating in full-duplex mode, the base station 1604 may configure the UE 1602 to monitor additional CORESETs (e.g., in addition to the four CORESETs). Thus, the base station 1404 may configure the UE 1602 to avoid monitoring a certain number of CORESETs in a given timeslot. In order for the UE 1602 to determine whether to apply a monitoring rule for a SBFD timeslot or whether the base station is operating in half-duplex mode or full-duplex mode, the base station 1604 may configure the UE 1602 with one or more SS sets associated with one or more CORESETs, wherein each SS set may define a monitoring opportunity in an available BW of an active downlink BWP in a SBFD timeslot.

[0116] In another example, the configuration at 1610 may further include a bitmap of frequency domain resources corresponding to the CORESET. Thus, at 1412, the UE 1602 may determine the frequency resources for the monitoring opportunity of the CORESET based at least in part on the bitmap, and may also be based on whether the UE is monitoring the CORESET in a SBFD time slot or in a downlink time slot (e.g., a half-duplex time slot), such as in combination with Fig. 12A and 12B as described. For example, the UE 1602 may determine, based on the bitmap, a first set of frequency resources within an active downlink BWP for monitoring a CORESET in a downlink timeslot, and a second set of frequency resources within the active downlink BWP for monitoring a CORESET in a SBFD timeslot. When the base station 1604 is operating in full-duplex mode, a subset of the bitmap may be used, wherein the bits of the subset may be mapped to an available BW instead of the entire BWP. In other words, the UE 1602 may apply a subset of the bitmap to resource blocks in an available BW of the BWP. In order for the UE 1602 to determine whether the base station 1604 is operating in half-duplex mode or full-duplex mode, the base station 1404 may send an indication of an operating mode in the SS set at 1610, such that the UE 1602 may monitor the CORESET based on the indication by mapping the bitmap to resource blocks in the active downlink BWP or mapping a subset of the bitmap to resource blocks in the available BW of the active downlink BWP, such as in combination with Fig. 12A and 12B For example, if the indication is used to indicate half-duplex mode for the SS set, the UE 1602 may map the bitmap to the full BWP, or if the indication is used to indicate full-duplex mode, the UE may map a subset of the bitmap to the available BW, and so on.

[0117] In another example, the configuration and / or indication may include a first bitmap of frequency domain resources for half-duplex operation and a second bitmap of frequency domain resources for full-duplex operation, wherein the UE 1402 may be configured to monitor the CORESET using the second bitmap of frequency domain resources during the SBFD time slot (e.g., full-duplex operation) and to monitor the CORESET using the first bitmap of frequency domain resources during the half-duplex time slot (e.g., half-duplex operation), such as in combination with Fig.15For example, at 1610, the base station 1604 may also indicate to the UE 1602 a full-duplex mode for the SS set associated with the first frequency domain resource, so that the UE 1602 may monitor one or more CORESETs using the second bitmap of the frequency domain resources based on the indication of the full-duplex mode for the SS set. Similarly, the base station 1604 may indicate to the UE 1602 a half-duplex mode for the SS set associated with the bitmap of the first frequency domain resource, so that the UE 1602 may monitor the CORESETs using the first bitmap of the frequency domain resources in the downlink time slot based on the indication of the half-duplex mode for the SS set.

[0118] Fig.17 1 is a flow chart of a method 1700 of wireless communication. The method may be performed by a UE or a component of a first UE (e.g., UE 104, 350, apparatus 1902; a processing system, which may include a memory 360, and may be the entire UE 350 or a component of the UE 350, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359). Optional aspects are shown with dashed lines. The method may enable the UE to apply different monitoring rules for a CORESET.

[0119] At 1702, a UE may communicate with a base station operating in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B and 16. For example, UE 1602 can communicate with base station 1604 operating in sub-band FDD mode. In addition, 1702 can be Fig.19 The monitoring component 1940 in is used to execute.

[0120] At 1704, the UE may receive a downlink transmission within one or more RBWs of an active downlink BWP. Fig. 7A Example 700 or Figure 7B In the example 750 of FIG. 1 , the UE may receive a downlink transmission within one or more RBWs 706, 708, 710A, 710B of an active downlink BWP, such as in conjunction with Fig. 7A / 7B-8. In addition, 1704 can be Fig.19 The monitoring component 1940 in is used to execute.

[0121] At 1706, the UE may monitor control transmissions configured by the base station, such as one or more CORESETs, within one or more RBWs of the active downlink BWP during a monitoring opportunity. Fig.16 UE 1602 in the embodiment may monitor the active downlink BWP within one or more RBWs during the monitoring opportunity. Fig.16One or more CORESETs configured in the base station 1604, such as in combination with Figures 9 to 15 In addition, 1706 can be Fig.19 The monitoring component 1940 in is used to execute.

[0122] Fig.18 1800 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a first UE (e.g., UE 104, 350, apparatus 1902; a processing system, which may include memory 360, and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). Optional aspects are shown with dashed lines. The method may enable the UE to apply different monitoring rules for a CORESET.

[0123] At 1802, a UE may communicate with a base station operating in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B and 16. For example, UE 1602 can communicate with base station 1604 operating in sub-band FDD mode. In addition, 1802 can be Fig.19 In addition, 1801 can be performed by the monitoring component 1940 in Fig.19 The monitoring component 1940 in is used to execute.

[0124] At 1804, the UE may receive a downlink transmission within one or more RBWs of an active downlink BWP. Fig. 7A Example 700 or Figure 7B In the example 750 of FIG. 1 , the UE may receive a downlink transmission within one or more RBWs 706, 708, 710A, 710B of an active downlink BWP, such as in conjunction with Fig. 7A In some aspects, one or more RBWs correspond to the available BW of an active BWP, the active BWP is in a SBFD time slot, and the available BW does not include frequency resources used for guard bands and uplink transmissions. For example, in Figure 7B In example 750 of FIG. 1 , the UE may receive a downlink transmission in an available BW 756 or 758 of the active downlink BWP. In addition, 1804 may be performed by Fig.19 The monitoring component 1940 in is used to execute.

[0125] At 1806, the UE may monitor one or more CORESETs configured by the base station within one or more RBWs of the active downlink BWP during a monitoring opportunity. Fig.16UE 1602 in the embodiment may monitor the active downlink BWP within one or more RBWs during the monitoring opportunity. Fig.16 One or more CORESETs configured in the base station 1604, such as in combination with Figures 9 to 15 In some aspects, the one or more CORESETs may correspond to a control transmission CORESET configured by the base station. In some aspects, the UE may monitor the one or more CORESETs configured by the base station within the active downlink BWP during the monitoring opportunity. In addition, 1806 may be Fig.19 The monitoring component 1940 in is used to execute.

[0126] In some aspects, to support monitoring at 1806, at 1812, the UE may receive a configuration of one or more CORESETs for each of the one or more RBWs. For example, the UE may receive a configuration of one or more CORESETs 1002 for each of the one or more RBWs, such as in conjunction with Fig.10 As described. In some aspects, the configuration may include a bitmap of frequency domain resources corresponding to RBs in the RBW. In some aspects, at 1814, the UE may receive a configuration of one or more SS sets in the RBW and a SS set for defining a monitoring opportunity for a CORESET in the RBW. For example, UE 1602 may receive a configuration of one or more SS sets in the RBW and a SS set for defining a monitoring opportunity for a CORESET in the RBW.

[0127] As part of 1806, at 1808, the UE may determine one or more monitoring opportunities for the CORESET that fall partially or completely outside of an active RBW in one or more RBWs. For example, Fig.16 The UE 1602 in the embodiment may determine one or more monitoring opportunities where a portion or all of a CORESET falls outside of an active RBW of one or more RBWs, such as in combination with Fig.10 described, such as by Fig.10 As shown in CORESET#2 at 1004 in .

[0128] After determining that one or more monitoring opportunities of the CORESET partially or completely fall outside of the active RBWs in the one or more RBWs, the UE may ignore the one or more monitoring opportunities of the CORESET partially or completely fall outside of the active RBWs in the one or more RBWs at 1810. For example, the UE may ignore the one or more monitoring opportunities of the CORESET partially or completely fall outside of the active RBWs in the one or more RBWs, such as by combining Fig.10 The description is shown in CORESET#2 at 1004.

[0129] In some aspects, to support monitoring at 1806, at 1816, the UE may receive a bitmap of frequency domain resources for a CORESET associated with the BWP, such as in conjunction with Fig.13 For example, UE 1602 may receive a bitmap of frequency domain resources for a CORESET associated with a BWP from base station 1604.

[0130] To support monitoring at 1806, in some aspects, at 1818, the UE may receive an indication of half-duplex mode or full-duplex mode in the SS set associated with the CORESET, such as in conjunction with Fig.13 As described. For example, UE 1602 may receive an indication of a full-duplex mode or a half-duplex mode in a SS set associated with CORESET 1302 / 1304. The UE may monitor the CORESET based on the indication by mapping a bitmap to resource blocks in an active BWP or mapping a subset of the bitmap to resource blocks in an active RBW in one or more RBWs in the BWP. For example, in some aspects, the UE determines a frequency resource for a monitoring opportunity of the CORESET based on the bitmap and based on whether the monitoring opportunity of the CORESET is in a SBFD time slot or a downlink time slot, such as in combination with Fig.13 In some aspects, the UE may determine frequency resources by determining a first set of frequency resources for one or more monitoring opportunities of the CORESET in one or more downlink time slots within an active BWP based on the bitmap, and determining a second set of frequency resources for one or more monitoring opportunities of the CORESET in one or more SBFD time slots within an active RBW in one or more RBWs in the active BWP based on the bitmap. In some aspects, the UE applies a subset of the bitmap to resource blocks in an RBW in one or more RBWs of the BWP for monitoring control transmissions during the SBFD time slots, such as in conjunction with Fig.13 In some aspects, if the indication is used to indicate half-duplex mode for the SS set, the UE maps the bitmap to the full BWP, or if the indication is used to indicate full-duplex mode, the UE maps a subset of the bitmap to an active RBW in one or more RBWs in the BWP.

[0131] In some aspects, to support monitoring at 1806, at 1820, the UE may receive a configuration for a CORESET associated with the BWP, the configuration comprising a bitmap of frequency domain resources associated with the entire BWP for half-duplex operation and one or more additional bitmaps of frequency domain resources associated with RBWs in one or more RBWs, each for full-duplex operation associated with one RBW in the BWP. For example, UE 1802 may receive a configuration for a CORESET associated with the BWP, the configuration comprising a bitmap of frequency domain resources for half-duplex operation associated with the entire BWP and one or more additional bitmaps of frequency domain resources associated with RBWs in one or more RBWs, each for full-duplex operation associated with one RBW in the BWP. The UE may monitor control transmissions from the base station using the bitmap associated with the RBW during the SBFD time slot. In some aspects, at 1822, the UE may receive an indication of a full-duplex mode for the SS set associated with the frequency domain resources for full-duplex operation. For example, the UE 1602 may receive an indication of a full-duplex mode for a SS set associated with frequency domain resources for full-duplex operation. The UE may monitor control transmissions from a base station based on the indication of the full-duplex mode for the SS set using one or more additional bitmaps each associated with an RBW in one or more RBWs. In some aspects, at 1822, the UE may receive an indication of a half-duplex mode for a SS set associated with a bitmap of frequency domain resources in a CORESET configuration. For example, the UE 1602 may receive an indication of a half-duplex mode for a SS set associated with a bitmap of frequency domain resources in a CORESET configuration. The UE may monitor control transmissions from a base station using a bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set.

[0132] Fig.1919 is a schematic diagram 1900 showing an example of a hardware implementation for an apparatus 1902. The apparatus 1902 is a UE and may include a cellular baseband processor 1904 (also referred to as a modem) coupled to a cellular RF transceiver 1922 and one or more subscriber identity modules (SIM) cards 1920, an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910, a Bluetooth module 1912, a wireless local area network (WLAN) module 1914, a global positioning system (GPS) module 1916, and a power supply 1918. The cellular baseband processor 1904 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 1922. The cellular baseband processor 1904 may include a computer-readable medium / memory. The cellular baseband processor 1904 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1904, the software causes the cellular baseband processor 1904 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1904 when executing the software. The cellular baseband processor 1904 also includes a receiving component 1930, a communication manager 1932, and a transmitting component 1934. The communication manager 1932 includes one or more of the components shown. The components within the communication manager 1932 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1904. The cellular baseband processor 1904 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 1902 may be a modem chip and include only the baseband processor 1904, and in another configuration, the device 1902 may be the entire UE (e.g., see Figure 3 350) and includes the additional modules discussed above of apparatus 1902. The receiving component 1930 and the transmitting component 1934 may be configured to communicate with a base station operating in a sub-band FDD mode, such as in conjunction with Fig.17 1702 and Fig.18 The receiving component 1930 may be configured to receive downlink transmissions within one or more RBWs of the active BWP, such as in conjunction with Fig.17 1704 and Fig.18 Described in 1804.

[0133] The communication manager 1932 includes a monitoring component 1940 configured to monitor control transmissions from a base station within one or more RBWs of an active BWP, such as in conjunction with Fig.18 1806 and Fig.17 Described in 1706.

[0134] The apparatus may include executing Fig.17 and 18 Each of the boxes in the algorithm in the above flowchart has an additional component. Therefore, Fig.17 and 18 Each of the blocks in the above flowchart may be performed by a component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof. In one configuration, the apparatus 1902 (and specifically, the cellular baseband processor 1904) includes: a unit for communicating with a base station operating in a sub-band FDD mode; a unit for receiving a downlink transmission within one or more RBWs of an active BWP; and a unit for monitoring a control transmission from a base station within one or more RBWs of an active BWP.

[0135] The aforementioned means may be one or more of the aforementioned components of the apparatus 1902 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1902 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned means may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0136] Fig. 20 2000 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 1404; which may include memory 376 and may be the entire base station 310 or a component of the base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). Optional aspects are shown with dashed lines. The method may enable the base station to configure the UE with different CORESET monitoring rules, enabling the UE to have more flexibility in monitoring the CORESET.

[0137] At 2002, the base station may communicate with the UE in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A, 5B and 16. For example, base station 1604 can communicate with UE 1602 in sub-band FDD mode. In addition, 2002 can be Fig. 22 The configuration component 2240 in is executed.

[0138] At 2004, the base station may send a downlink transmission within one or more RBWs of the active downlink BWP. For example, the base station may send a downlink transmission within one or more RBWs of the active downlink BWP, as described in conjunction with FIGS. 7-8. Fig. 7A Example 700 or Figure 7B In the example 750 of FIG. 1 , the base station may send a downlink transmission within one or more RBWs 706, 708, 710A, 710B of an active downlink BWP, such as in conjunction with Fig. 7A / 7B-8. In addition, 2004 can be Fig. 22 The configuration component 2240 in is executed.

[0139] At 2006, the base station may configure the UE to monitor control transmissions configured by the base station, such as one or more CORESETs, within one or more RBWs of the active downlink BWP during the monitoring opportunity. Fig.16 UE 1602 in the embodiment may monitor the active downlink BWP within one or more RBWs during the monitoring opportunity. Fig.16 One or more CORESETs configured in the base station 1604, such as in combination with Figures 9 to 15 In addition, 2006 can be Fig. 22 The configuration component 2240 in is executed.

[0140] Fig.21 2100 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 1404; which may include memory 376 and may be the entire base station 310 or a component of the base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). Optional aspects are shown with dashed lines. The method may enable the base station to configure the UE with different CORESET monitoring rules, enabling the UE to have more flexibility in monitoring the CORESET.

[0141] At 2102, the base station may communicate with the UE in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A, 5B and 16. For example, base station 1604 can communicate with UE 1602 in subband FDD mode. In addition, 2102 can be Fig. 22 The configuration component 2240 in is executed.

[0142] At 2104, the base station may send a downlink transmission within one or more RBWs of the active downlink BWP. For example, the base station may send a downlink transmission within one or more RBWs of the active downlink BWP as described in conjunction with FIGS. 7-8. Fig. 7A Example 700 or Figure 7B In the example 750 of FIG. 1 , the base station may send a downlink transmission within one or more RBWs 706, 708, 710A, 710B of an active downlink BWP, such as in conjunction with Fig. 7A / 7B-8. In addition, 2104 can be Fig. 22 The configuration component 2240 in is executed.

[0143] At 2106, the base station may configure the UE to monitor control transmissions configured by the base station, such as one or more CORESETs, within one or more RBWs of the active downlink BWP during the monitoring opportunity. Fig.16 UE 1602 in the embodiment may monitor the active downlink BWP within one or more RBWs during the monitoring opportunity. Fig.16 One or more CORESETs configured in the base station 1604, such as in combination with Figures 9 to 15 In addition, 2106 can be Fig. 22 The configuration component 2240 in is executed.

[0144] In some aspects, as part of the configuration at 2106, at 2112, the base station may send a configuration of one or more CORESETs for each of the one or more RBWs. For example, the base station may send a configuration of one or more CORESETs 1002 for each of the one or more RBWs, such as in conjunction with Fig.10 As described. In some aspects, the configuration may include a bitmap of one or more frequency resources corresponding to one or more RBs in one or more RBWs. In some aspects, at 2114, the base station may send one or more SS sets in the RBW and a configuration of the SS set for defining the monitoring opportunity of the CORESET in the RBW. For example, the base station 1604 may send one or more SS sets in the RBW and a configuration of the SS set for defining the monitoring opportunity of the CORESET in the RBW.

[0145] In some aspects, as part of configuring at 2106, at 2116, the base station may send a bitmap of frequency domain resources for the CORESET associated with the BWP, such as described in conjunction with FIG. 12. For example, the base station 1604 may send a bitmap of frequency domain resources for the CORESET associated with the BWP. As part of configuring at 2106, in some aspects, at 2118, the base station sends an indication of half-duplex mode or full-duplex mode in the SS set associated with the CORESET, such as described in conjunction with FIG. 12. For example, the base station 1604 may send an indication of half-duplex mode or full-duplex mode in the SS set associated with the CORESET, such as described in conjunction with FIG. 12. The UE may monitor the CORESET based on the indication by mapping the bitmap to resource blocks in an active BWP or mapping a subset of the bitmap to resource blocks in an active RBW in one or more RBWs in the BWP. For example, in some aspects, the UE determines frequency resources for monitoring occasions of the CORESET based on the bitmap and based on whether the monitoring occasions of the CORESET are in SBFD time slots or downlink time slots, such as described in conjunction with FIG. 12. In some aspects, the UE may determine the frequency resources by determining a first set of frequency resources for one or more monitoring occasions of the CORESET in one or more downlink time slots within an active BWP based on the bitmap, and determining a second set of frequency resources for monitoring occasions of the CORESET in one or more SBFD time slots within an active RBW in one or more RBWs in the active BWP based on the bitmap. In some aspects, the UE applies a subset of the bitmap to resource blocks in a RBW in one or more RBWs of the BWP for monitoring control transmissions during the SBFD time slot, such as described in conjunction with FIG. 12. In some aspects, the UE maps the bitmap to a full BWP if the indication is to indicate half-duplex mode for the SS set, or maps the subset of the bitmap to an active RBW in one or more RBWs in the BWP if the indication is to indicate full-duplex mode.

[0146] In some aspects, as part of configuring at 2106, at 2120, the base station may send a configuration for a CORESET associated with the BWP, the configuration including a bitmap of frequency domain resources for half-duplex operation associated with the entire BWP, and one or more additional bitmaps of frequency domain resources each associated with an RBW in one or more RBWs for full-duplex operation each associated with one RBW in the BWP. For example, the UE may use the bitmap associated with the RBW during the SBFD time slot to monitor control transmissions from the base station. In some aspects, at 2122, the base station may send an indication of full-duplex mode for the SS set associated with the frequency domain resources for full-duplex operation. The UE may use the one or more additional bitmaps each associated with the RBW in one or more RBWs to monitor control transmissions from the base station based on the indication of full-duplex mode for the SS set. In some aspects, at 2122, the base station may send an indication of half-duplex mode for the SS set associated with the bitmap of frequency domain resources in the CORESET configuration. The UE may monitor control transmissions from the base station using a bitmap of frequency domain resources in a downlink time slot based on an indication of half-duplex mode for a set of SSs. For example, the base station 1604 may send an indication of full-duplex mode or half-duplex mode.

[0147] Fig. 22 2200 is a schematic diagram showing an example of a hardware implementation for an apparatus 2202. The apparatus 2202 is a base station and may include a baseband unit 2204. The baseband unit 2204 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2204 may include a computer-readable medium / memory. The baseband unit 2204 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 2204, causes the baseband unit 2204 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2204 when executing the software. The baseband unit 2204 also includes a receiving component 2230, a communication manager 2232, and a sending component 2234. The communication manager 2232 includes one or more of the components shown. The components within the communication manager 2232 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2204. The baseband unit 2204 may be a component of the BS 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376. The receiving component 2230 and the transmitting component 2234 may be configured to communicate with a UE operating in a sub-band FDD mode, such as in conjunction with Fig. 20 2002 and Fig.21The transmitting component 2234 may be configured to transmit downlink transmissions within one or more RBWs of the active BWP, such as in conjunction with Fig. 20 2004 and Fig.21 As described in 2104.

[0148] The communication manager 2232 includes a configuration component 2240 configured to configure the UE to monitor control transmissions from the base station within one or more RBWs of the active BWP, such as in conjunction with Fig. 20 2006 and Fig.21 As described in 2106.

[0149] The apparatus may include executing Fig. 20 and 21 Each of the boxes in the algorithm in the above flowchart has an additional component. Therefore, Fig. 20 and 21 Each block in the above flowchart of can be performed by a component, and the device can include one or more of those components. The component can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof. In one configuration, the device 2202 (and specifically, the baseband unit 2204) includes: a unit for communicating with a UE operating in a sub-band FDD mode; a unit for sending a downlink transmission within one or more RBWs of an active BWP; and a unit for configuring the UE to monitor a control transmission from a base station within one or more RBWs of an active BWP. The above-mentioned units can be one or more of the above-mentioned components of the device 2202 configured to perform the functions recorded by the above-mentioned units. As described above, the device 2202 can include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the above-mentioned units can be a TX processor 316, an RX processor 370, and a controller / processor 375, which are configured to perform the functions recorded by the above-mentioned units.

[0150] Fig.23 2300 is a flow chart of a method of wireless communication. The method may be performed by a UE or a component of a first UE (e.g., UE 106, 350, 1402; a processing system, which may include a memory 360, and may be the entire UE 350 or a component of the UE 350, such as a TX processor 368, an RX processor 356, and / or a controller / processor 359). Optional aspects are shown with dashed lines. The method may enable the UE to apply different monitoring rules for a CORESET based at least in part on whether the base station is operating in a half-duplex mode or a full-duplex mode.

[0151] At 2302, the UE may communicate with a base station operating in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B. For example, UE 1602 can communicate with base station 1604 operating in sub-band FDD mode. In addition, 2302 can be Fig.24 The communication component 2440 in is executed.

[0152] At 2304, the UE may receive a downlink transmission in an available BW of an active downlink BWP in a SBFD time slot, wherein the available BW does not include frequency resources used for a guard band and uplink transmissions, such as described in conjunction with FIGS. 7-8. Figure 7B In example 750 of FIG. 1 , the UE may receive a downlink transmission in an available BW 756 or 758 of the active downlink BWP. In addition, 2304 may be performed by Fig.24 It is executed by the BWP component 2442 in.

[0153] At 2306, the UE may monitor one or more CORESETs configured by the base station within the active downlink BWP during a monitoring opportunity, such as in conjunction with Figures 9 to 13 For example, UE 1602 may monitor one or more CORESETs configured by base station 1604 within an active downlink BWP during a monitoring opportunity. In addition, 2306 may be configured by Fig.24 The monitoring component 2444 in is used to execute.

[0154] At 2308, when the base station is operating in full-duplex mode, the UE may determine whether the monitoring opportunities of the CORESET fall partially or completely outside the available BW, and the UE may ignore the monitoring opportunities of the CORESET that fall partially or completely outside the available BW in the SBFD time slot, such as in conjunction with Fig.10 For example, the UE may receive configurations of one or more CORESETs 1002 for each of one or more RBWs, such as in conjunction with Fig.10 In addition to monitoring one or more CORESETs during a downlink timeslot, the UE may also receive a configuration or indication for monitoring additional CORESETs, such as in conjunction with Fig.11As described. For example, the configuration or indication may configure the UE to monitor up to four CORESETs or more CORESETs within an active downlink BWP, or to avoid monitoring up to a certain number of CORESETs. For example, when the base station is operating in half-duplex mode, the UE may receive from the base station a configuration for monitoring up to four CORESETs in an active downlink BWP, and when the base station is operating in full-duplex mode, the UE may receive a configuration for monitoring an additional CORESET, and so on. The UE may receive the configuration in a search space (SS) set, where an SS set may be associated with one or more CORESETs and may define a monitoring opportunity in an available BW. In addition, 2308 may be performed by Fig.24 The monitoring component 2444 in is used to execute.

[0155] At 2310, the UE may receive a bitmap of frequency domain resources corresponding to the CORESET, and the UE may determine frequency resources for monitoring opportunities for the CORESET based on the bitmap and based on whether the UE is monitoring the CORESET in a SBFD timeslot or a downlink timeslot, such as in conjunction with Fig. 12A and 12B For example, based on the bitmap, the UE may determine a first set of frequency resources within the active downlink BWP for monitoring CORESETs in downlink time slots, and the UE may also determine a second set of frequency resources within the active downlink BWP for monitoring CORESETs in SBFD time slots. The UE may then apply a subset of the bitmap to resource blocks in the available BW of the BWP, such as in combination with Fig. 12B As described. The UE may receive an indication of a half-duplex mode or a full-duplex mode in a search space (SS) set, wherein the UE may monitor the CORESET based on the indication by mapping a bitmap to resource blocks in an active downlink BWP, or mapping a subset of the bitmap to resource blocks in an available BW of the active downlink BWP. For example, if the indication is used to indicate a half-duplex mode for the SS set, the UE may map the bitmap to the full BWP, or if the indication is used to indicate a full-duplex mode, the UE may map a subset of the bitmap to the available BW, and so on. In addition, 2310 may be performed by Fig.24 The monitoring component 2444 in is used to execute.

[0156] At 2312, the UE may receive a configuration for monitoring the CORESET in half-duplex operation and in full-duplex operation. For example, the UE 1602 may receive a configuration for monitoring the CORESET in half-duplex operation and in full-duplex operation. The configuration may include a first bitmap of frequency domain resources for half-duplex operation and a second bitmap of frequency domain resources for full-duplex operation, and the UE may monitor the CORESET using the second bitmap of frequency domain resources during the SBFD time slot, such as in conjunction with Fig.13 As described. For example, the UE may receive an indication of a full-duplex mode for an SS set associated with a first frequency domain resource, wherein the UE may be configured to monitor one or more CORESETs using a second bitmap of frequency domain resources based on the indication of the full-duplex mode for the SS set. The UE may receive an indication of a half-duplex mode for an SS set associated with a bitmap of the first frequency domain resource, wherein the UE may monitor one or more CORESETs using a first bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set. In addition, 2312 may be performed by Fig.24 The monitoring component 2444 in is used to execute.

[0157] Fig.2424 is a schematic diagram 2400 showing an example of a hardware implementation for an apparatus 2402. The apparatus 2402 is a UE and may include a cellular baseband processor 2404 (also referred to as a modem) coupled to a cellular RF transceiver 2422 and one or more subscriber identity modules (SIM) cards 2420, an application processor 2406 coupled to a secure digital (SD) card 2408 and a screen 2410, a Bluetooth module 2412, a wireless local area network (WLAN) module 2414, a global positioning system (GPS) module 2416, and a power supply 2418. The cellular baseband processor 2404 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 2422. The cellular baseband processor 2404 may include a computer-readable medium / memory. The cellular baseband processor 2404 is responsible for general processing, including executing software stored on a computer-readable medium / memory. When executed by the cellular baseband processor 2404, the software causes the cellular baseband processor 2404 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 2404 when executing the software. The cellular baseband processor 2404 also includes a receiving component 2430, a communication manager 2432, and a transmitting component 2434. The communication manager 2432 includes one or more of the components shown. The components within the communication manager 2432 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 2404. The cellular baseband processor 2404 may be a component of the UE 350 and may include at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 and / or the memory 360. In one configuration, the device 2402 may be a modem chip and include only the baseband processor 2404, and in another configuration, the device 2402 may be the entire UE (e.g., see Figure 3 350) and includes the additional modules discussed above of device 2402.

[0158] The communication manager 2432 includes a communication component 2440 configured to communicate with a base station operating in a sub-band FDD mode, for example, as described in conjunction with Fig.23 The communication manager 2432 also includes a BWP component 2442 configured to receive a downlink transmission in an available BW of an active downlink BWP in a SBFD time slot, wherein the available BW does not include frequency resources for a guard band and uplink transmissions, for example, as combined Fig.23 The communication manager 2432 also includes a monitoring component 2444, which is configured to monitor one or more CORESETs configured by the base station within the active downlink BWP during the monitoring opportunity, for example, as described in conjunction with Fig.23As described in 2306.

[0159] The apparatus may include executing Fig.23 Each of the boxes in the algorithm in the above flowchart has an additional component. Therefore, Fig.23 Each block in the above flowchart of can be performed by a component, and the device can include one or more of those components. The component can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof. In one configuration, the device 2402 (and specifically, the cellular baseband processor 2404) includes: a unit for communicating with a base station operating in a sub-band FDD mode; a unit for receiving a downlink transmission in an available BW of an active downlink BWP in an SBFD time slot, wherein the available BW does not include frequency resources for guard bands and uplink transmissions; and a unit for monitoring one or more CORESETs configured by the base station within the active downlink BWP during a monitoring opportunity. The above-mentioned units can be one or more of the above-mentioned components of the device 2402 configured to perform the functions recorded by the above-mentioned units. As described above, the device 2402 can include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359, which are configured to perform the functions recited by the aforementioned means.

[0160] Fig.25 2500 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102, 260, 310, 1404; which may include memory 376, and may be the entire base station 310 or a component of the base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). Optional aspects are shown with dashed lines. The method may enable the base station to configure the UE with different CORESET monitoring rules, enabling the UE to have more flexibility in monitoring the CORESET.

[0161] At 2502, the base station may communicate with the UE in a sub-band FDD mode, such as in conjunction with Figure 4A , 4B , 4C, 5A and 5B. For example, base station 1604 can communicate with UE 1602 in sub-band FDD mode. In addition, 2502 can be Fig.26 The communication component 2640 in is executed.

[0162] At 2504, the base station may send a downlink transmission in an available BW of an active downlink BWP in a SBFD time slot, wherein the available BW may not include frequency resources used for a guard band and uplink transmissions, such as described in conjunction with FIGS. 7 and 8. For example, in Figure 7B In example 750 of FIG. 1 , base station 1604 may send a downlink transmission in available BW 756 or 758 of the active downlink BWP. In addition, 2504 may be Fig.26 It is executed by the BWP component 2642 in.

[0163] At 2506, the base station may configure the UE to monitor one or more CORESETs configured by the base station within the active downlink BWP during the monitoring opportunity, such as in conjunction with Figures 8 to 13 For example, base station 1604 may configure UE 1602 to monitor one or more CORESETs configured by the base station within an active downlink BWP during a monitoring opportunity. In addition, 2506 may be configured by Fig.26 The monitoring component 2644 in is used to execute.

[0164] At 2508, when the base station operates in half-duplex mode, the base station may configure the UE to monitor up to four CORESETs in the active downlink BWP, and when the base station operates in full-duplex mode, the base station may configure the UE to monitor additional CORESETs, such as in conjunction with Fig.11 As described. For example, when the base station operates in full-duplex mode, the base station may configure up to four or more CORESETs for the UE, which may compensate for the UE's inability to monitor a CORESET that is partially or completely outside the available BW in the SBFD timeslot. The base station may configure the UE with an SS set, where the SS set may be associated with a CORESET, so that the UE does not monitor more than a given number of CORESETs (e.g., four) in a downlink timeslot or a SBFD timeslot. In addition, 2508 may be configured by Fig.26 The monitoring component 2644 in is used to execute.

[0165] At 2510, the base station may send a bitmap corresponding to the CORESET, wherein the frequency resources for monitoring occasions for the CORESET are determined based on the bitmap and based on whether the UE is monitoring the CORESET in a SBFD timeslot or a downlink timeslot, such as in conjunction with FIG. Fig. 12A and 12B For example, the base station may send an indication of a half-duplex mode or a full-duplex mode for a set of SSs, wherein the bitmap 1202 or a subset of the bitmap is mapped to a resource block in an active downlink BWP or a resource block in an available BW of an active downlink BWP. In addition, 2510 may be Fig.26 The monitoring component 2644 in is used to execute.

[0166] At 2512, the base station may send a configuration for monitoring one or more CORESETs in half-duplex operation and in full-duplex operation, wherein the configuration includes a first bitmap of frequency domain resources for half-duplex operation and a second bitmap of frequency domain resources for full-duplex operation, and the UE monitors the CORESETs during the SBFD time slot using the second bitmap of frequency domain resources, such as in conjunction with Fig.15 For example, the base station may send a configuration for an SS set associated with one or more CORESETs, wherein the configuration may indicate a full-duplex mode to associate the SS set with a first frequency domain resource bitmap. The configuration may also indicate a half-duplex mode to associate the SS set with a second frequency domain resource bitmap, such as in combination with Fig.15 In addition, the 2512 can be Fig.26 The monitoring component 2644 in is used to execute.

[0167] Fig.26 2600 is a schematic diagram showing an example of a hardware implementation for an apparatus 2602. The apparatus 2602 is a base station and may include a baseband unit 2604. The baseband unit 2604 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 2604 may include a computer-readable medium / memory. The baseband unit 2604 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 2604, causes the baseband unit 2604 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 2604 when executing the software. The baseband unit 2604 also includes a receiving component 2630, a communication manager 2632, and a sending component 2634. The communication manager 2632 includes one or more of the components shown. The components within the communication manager 2632 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 2604. The baseband unit 2604 may be a component of the BS 310 and may include at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 , and / or the memory 376 .

[0168] The communication manager 2632 includes a communication component 2640 configured to communicate with the UE in the sub-band FDD mode, for example, as described in conjunction with Fig.25 The communication manager 2632 also includes a BWP component 2642 configured to send a downlink transmission in an available BW of an active downlink BWP in a SBFD time slot, wherein the available BW does not include frequency resources used for a guard band and uplink transmissions, for example, as described in conjunction with Fig.25 The communication manager 2632 also includes a configuration component 2644, which is configured to configure the UE to monitor one or more CORESETs configured by the base station within the active downlink BWP during the monitoring opportunity, for example, as described in conjunction with Fig.25 2506 as described.

[0169] The apparatus may include executing Fig.25 Each of the boxes in the algorithm in the above flowchart has an additional component. Therefore, Fig.25 Each box in the above flowchart of can be performed by a component, and the device can include one or more of those components. The component can be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium to be implemented by a processor, or some combination thereof. In one configuration, the device 2602 (and specifically, the baseband unit 2604) includes: a unit for communicating with the UE in a sub-band FDD mode; a unit for sending a downlink transmission in an available BW of an active downlink BWP in an SBFD time slot, wherein the available BW does not include frequency resources for guard bands and uplink transmissions; and a unit for configuring the UE to monitor one or more CORESETs configured by the base station within the active downlink BWP during a monitoring opportunity. The above-mentioned units can be one or more of the above-mentioned components of the device 2602 configured to perform the functions recorded by the above-mentioned units. As described above, the device 2602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375, which are configured to perform the functions recited by the aforementioned means.

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

[0171] The foregoing description is provided so that any person skilled in the art can implement 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 intended to be limited to the aspects shown herein, but to conform to the full range consistent with the content expressed by the claims, wherein, unless explicitly stated as such, reference to the singular element is not intended to mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while ..." should be interpreted as "under the condition of ...", rather than implying an immediate time relationship or reaction. That is, these phrases (e.g., "when ...") do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that the action will occur if the condition is met, but do not require a specific or immediate time constraint for the occurrence of the action. The word "exemplary" used herein means "as an example, instance or illustration". Any aspect described as "exemplary" herein need not be interpreted as being preferred to or having advantages over other aspects. Unless otherwise explicitly stated, 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 multiples of A, multiples of B, or multiples of 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 include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "unit." Likewise, no claim element is to be interpreted as a functional unit unless the element is explicitly recorded using the phrase "unit for..."

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

[0173] Aspect 1 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to: communicate with a base station operating in a subband FDD mode; receive downlink transmissions within one or more RBWs of an active BWP; and monitor control transmissions from the base station within the one or more RBWs of the active BWP.

[0174] Aspect 2 is an apparatus according to aspect 1, wherein the one or more RBWs correspond to an available BW of the active BWP, the active BWP is in a SBFD time slot, and wherein the available BW does not include frequency resources for a guard band and uplink transmission.

[0175] Aspect 3 is an apparatus according to any one of aspects 1-2, wherein the control transmission corresponds to one or more CORESETs configured by the base station.

[0176] Aspect 4 is an apparatus according to any one of Aspects 1-3, wherein, in order to monitor the control transmission from the base station within the one or more RBWs of the active BWP, the at least one processor coupled to the memory is also configured to: monitor the one or more CORESETs configured by the base station within the active downlink BWP during a monitoring opportunity.

[0177] Aspect 5 is an apparatus according to any one of Aspects 1-4, wherein the at least one processor coupled to the memory is further configured to: when the base station operates in half-duplex mode, receive from the base station a configuration for monitoring up to four CORESETs in the active downlink BWP, and when the base station operates in the FDD mode, receive from the base station a configuration for monitoring an additional CORESET.

[0178] Aspect 6 is the apparatus according to any one of aspects 1-5, wherein the at least one processor coupled to the memory is further configured to: avoid monitoring more than four CORESETs in a given time slot.

[0179] Aspect 7 is an apparatus according to any one of Aspects 1-6, wherein the at least one processor coupled to the memory is also configured to: receive a configuration of one or more CORESETs for each of the one or more RBWs; determine one or more monitoring opportunities of the CORESET that partially or completely fall outside the active RBWs of the one or more RBWs; and ignore the one or more monitoring opportunities of the CORESET that partially or completely fall outside the active RBWs of the one or more RBWs.

[0180] Aspect 8 is an apparatus according to any one of aspects 1-7, wherein the configuration includes a bitmap of frequency domain resources corresponding to RBs in the RBW.

[0181] Aspect 9 is an apparatus according to any one of aspects 1-8, wherein the UE receives a search space configuration for one or more SS sets in an RBW and an SS set for defining a monitoring opportunity of a CORESET in the RBW.

[0182] Aspect 10 is an apparatus according to any one of Aspects 1-9, wherein the at least one processor coupled to the memory is further configured to: receive a bitmap of frequency domain resources for the CORESET associated with the active BWP; and determine the frequency resources for the monitoring opportunity of the CORESET based on the bitmap and based on whether the monitoring opportunity of the CORESET is in a SBFD time slot or in a downlink time slot.

[0183] Aspect 11 is an apparatus according to any one of Aspects 1-10, wherein, in order to determine the frequency resources, the at least one processor coupled to the memory is also configured to: determine, based on the bitmap, a first set of frequency resources within the active BWP for one or more monitoring opportunities of the CORESET in one or more downlink time slots; and determine, based on the bitmap, a second set of frequency resources within an active RBW in the one or more RBWs in the active BWP for monitoring opportunities of the CORESET in one or more SBFD time slots.

[0184] Aspect 12 is an apparatus according to any one of aspects 1-11, wherein the UE applies a subset of the bitmap to resource blocks in the active RBW in the one or more RBWs of the BWP for monitoring the control transmission during the SBFD timeslot.

[0185] Aspect 13 is an apparatus according to any one of Aspects 1-12, wherein the at least one processor coupled to the memory is further configured to: receive an indication of a half-duplex mode or a full-duplex mode in an SS set associated with the CORESET, wherein the UE monitors the CORESET based on the indication by: mapping the bitmap to resource blocks in the active BWP, or mapping a subset of the bitmap to resource blocks in the active RBW of the one or more RBWs in the BWP.

[0186] Aspect 14 is an apparatus according to any one of Aspects 1-13, wherein, if the indication is used to indicate the half-duplex mode for the SS set, the UE maps the bitmap to a full BWP, or if the indication is used to indicate the full-duplex mode, the UE maps a subset of the bitmap to an active RBW in the one or more RBWs in the BWP.

[0187] Aspect 15 is an apparatus according to any one of Aspects 1-14, wherein the at least one processor coupled to the memory is further configured to: receive a configuration for a CORESET associated with the active BWP, the configuration comprising: a bitmap for frequency domain resources in a half-duplex mode associated with the BWP, and one or more additional bitmaps for frequency domain resources in a full-duplex mode each associated with an RBW in the BWP, wherein the UE uses the bitmap associated with the one or more RBWs to monitor the control transmission from the base station during one or more SBFD time slots.

[0188] Aspect 16 is an apparatus according to any one of Aspects 1-15, wherein the at least one processor coupled to the memory is also configured to: receive an indication of a full-duplex mode for a SS set associated with the frequency domain resources for full-duplex operation, wherein the UE uses the one or more additional bitmaps to monitor the control transmission from the base station based on the indication of the full-duplex mode for the SS set and the active RBW for monitoring opportunities in one or more SBFD time slots.

[0189] Aspect 17 is an apparatus according to any one of Aspects 1-16, wherein the at least one processor coupled to the memory is also configured to: receive an indication of a half-duplex mode for an SS set associated with the bitmap of frequency domain resources in the CORESET configuration, wherein the UE monitors the control transmission from the base station using the bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set.

[0190] Aspect 18 is the apparatus of any one of aspects 1-17, further comprising a transceiver coupled to the at least one processor.

[0191] Aspect 19 is an apparatus for wireless communication at a BS, comprising: a memory; and at least one processor coupled to the memory and configured to: communicate with a UE when operating in a subband FDD mode; send a downlink transmission within one or more RBWs of an active BWP; and configure the UE to monitor control transmissions from the base station within the one or more RBWs of the active BWP.

[0192] Aspect 20 is an apparatus according to aspect 19, wherein the one or more RBWs correspond to an available BW of the active BWP, the active BWP is in a SBFD time slot, and wherein the available BW does not include frequency resources for a guard band and uplink transmission.

[0193] Aspect 21 is an apparatus according to any one of aspects 19-20, wherein the at least one processor coupled to the memory is further configured to: send a configuration of one or more CORESETs for each of the one or more RBWs.

[0194] Aspect 22 is an apparatus according to any one of aspects 19-21, wherein the configuration comprises a bitmap of frequency domain resources corresponding to RBs in the RBW.

[0195] Aspect 23 is an apparatus according to any one of aspects 19-22, wherein the base station sends a search space configuration for one or more SS sets in an RBW and an SS set for defining a monitoring opportunity of a CORESET in the RBW.

[0196] Aspect 24 is the apparatus according to any one of aspects 19-23, wherein the at least one processor coupled to the memory is further configured to: send a bitmap of frequency domain resources for the CORESET associated with the BWP.

[0197] Aspect 25 is an apparatus according to any one of Aspects 19-24, wherein the at least one processor coupled to the memory is further configured to: send an indication of a half-duplex mode or a full-duplex mode in an SS set associated with the CORESET, wherein the UE monitors the CORESET based on the indication by: mapping the bitmap to resource blocks in the active BWP, or mapping a subset of the bitmap to resource blocks in the active RBW of the one or more RBWs in the BWP.

[0198] Aspect 26 is an apparatus according to any one of Aspects 19-25, wherein the at least one processor coupled to the memory is further configured to: send a configuration for the CORESET associated with the active BWP, the configuration comprising: a bitmap for frequency domain resources for half-duplex mode, and one or more additional bitmaps for frequency resources for full-duplex mode each associated with an RBW in the BWP, wherein the UE uses the bitmap associated with the RBW to monitor the control transmission from the base station during one or more SBFD time slots.

[0199] Aspect 27 is an apparatus according to any one of Aspects 19-26, wherein the at least one processor coupled to the memory is also configured to: send an indication of a full-duplex mode for a SS set associated with the frequency domain resources for full-duplex operation, wherein the UE uses the one or more additional bitmaps to monitor the control transmission from the base station based on the indication of the full-duplex mode for the SS set and the active RBW for the monitoring opportunity in the SBFD time slot.

[0200] Aspect 28 is an apparatus according to any one of Aspects 19-27, wherein the at least one processor coupled to the memory is also configured to: send an indication of a half-duplex mode for an SS set associated with a bitmap of frequency domain resources in the CORESET configuration, wherein the UE monitors the control transmission from the base station using the bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set.

[0201] Aspect 29 is a method for wireless communication implementing any one of aspects 1 to 18.

[0202] Aspect 30 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 18.

[0203] Aspect 31 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 18.

[0204] Aspect 32 is a method for wireless communication implementing any one of aspects 19 to 28.

[0205] Aspect 33 is an apparatus for wireless communication, comprising means for implementing any one of aspects 19 to 28.

[0206] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 19 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as at least one processor coupled to the memory and configured to: communicating with a base station operating in a sub-band frequency division duplex (FDD) mode; receiving a downlink transmission within one or more resource bandwidths (RBWs) of an active bandwidth part (BWP); receiving a bitmap of frequency domain resources for a control resource set (CORESET) associated with the active BWP; determining a frequency resource for the monitoring occasion of the CORESET based on the bitmap and based on whether the monitoring occasion of the CORESET is in a sub-band full duplex (SBFD) timeslot or in a downlink timeslot; as well as Monitoring for control transmissions from the base station within the one or more RBWs of the active BWP.

2. The device according to claim 1, wherein: The one or more RBWs correspond to an available bandwidth (BW) of the active BWP, the active BWP being in a sub-band full duplex (SBFD) time slot, and wherein the available BW does not include frequency resources for a guard band and uplink transmission.

3. The device according to claim 2, wherein: The control transmission corresponds to one or more control resource sets (CORESETs) configured by the base station.

4. The device according to claim 3, wherein: To monitor the control transmission from the base station within the one or more RBWs of the active BWP, the at least one processor coupled to the memory is further configured to: During a monitoring opportunity, the one or more CORESETs configured by the base station are monitored within the active BWP for downlink.

5. The device according to claim 4, wherein: The at least one processor coupled to the memory is further configured to: A configuration is received from the base station for monitoring up to four CORESETs in the active BWP for downlink when the base station operates in half-duplex mode, and a configuration is received from the base station for monitoring an additional CORESET when the base station operates in the FDD mode.

6. The device according to claim 5, wherein: The at least one processor coupled to the memory is further configured to: Avoid monitoring more than four CORESETs in a given time slot.

7. The device according to claim 1, wherein: The at least one processor coupled to the memory is further configured to: receiving a configuration of one or more control resource sets (CORESETs) for each of the one or more RBWs; determining one or more monitoring opportunities of the CORESET that fall partially or completely outside of an active RBW of the one or more RBWs; as well as The one or more monitoring opportunities of the CORESET that fall partially or completely outside the active RBW of the one or more RBWs are ignored.

8. The device according to claim 7, wherein: The configuration includes a bitmap of frequency domain resources corresponding to resource blocks (RBs) in the RBW.

9. The device according to claim 7, wherein: The UE receives a search space configuration for one or more search space (SS) sets in a RBW and a SS set for defining monitoring occasions of a CORESET in the RBW.

10. The device according to claim 1, wherein: To determine the frequency resources, the at least one processor coupled to the memory is further configured to: determining, based on the bitmap, a first set of frequency resources within the active BWP for one or more monitoring occasions of the CORESET in one or more downlink time slots; as well as Based on the bitmap, a second set of frequency resources within an active RBW in the one or more RBWs in the active BWP for monitoring opportunities of the CORESET in one or more SBFD time slots is determined.

11. The device according to claim 1, wherein: The UE applies a subset of the bitmap to resource blocks in an active RBW of the one or more RBWs of the BWP for monitoring the control transmission during the SBFD timeslot.

12. The device according to claim 1, wherein: The at least one processor coupled to the memory is further configured to: Receiving an indication of half-duplex mode or full-duplex mode in a search space (SS) set associated with the CORESET, wherein the UE monitors the CORESET based on the indication by mapping the bitmap to resource blocks in the active BWP or mapping a subset of the bitmap to resource blocks in an active RBW of the one or more RBWs in the BWP.

13. The device according to claim 12, wherein: The UE maps the bitmap to a full BWP if the indication is for indicating the half-duplex mode for the SS set, or maps a subset of the bitmap to an active RBW of the one or more RBWs in the BWP if the indication is for indicating the full-duplex mode.

14. The device according to claim 1, wherein: The at least one processor coupled to the memory is further configured to: Receive a configuration for a control resource set (CORESET) associated with the active BWP, the configuration comprising: a bitmap for frequency domain resources for half-duplex mode associated with the BWP, and one or more additional bitmaps for frequency domain resources for full-duplex mode each associated with an RBW in the BWP, wherein the UE uses the bitmap associated with the one or more RBWs to monitor the control transmission from the base station during one or more sub-band full-duplex (SBFD) time slots.

15. The device according to claim 14, wherein: The at least one processor coupled to the memory is further configured to: Receive an indication of a full-duplex mode for a search space (SS) set associated with the frequency domain resources for full-duplex operation, wherein the UE uses the one or more additional bitmaps to monitor the control transmission from the base station based on the indication of the full-duplex mode for the SS set and an active RBW for monitoring opportunities in one or more sub-band full-duplex (SBFD) time slots.

16. The device according to claim 14, wherein: The at least one processor coupled to the memory is further configured to: An indication of a half-duplex mode for a search space (SS) set associated with the bitmap of frequency domain resources is received in the CORESET configuration, wherein the UE monitors the control transmission from the base station using the bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set.

17. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor.

18. An apparatus for wireless communication at a base station (BS), comprising: Memory; as well as at least one processor coupled to the memory and configured to: communicating with a user equipment (UE) when operating in a sub-band frequency division duplex (FDD) mode; Sending downlink transmissions within one or more resource bandwidths (RBWs) of an active bandwidth part (BWP); Sending a bitmap of frequency domain resources for a control resource set (CORESET) associated with the BWP; wherein the frequency resources for the monitoring occasion of the CORESET are determined based on the bitmap and based on whether the monitoring occasion of the CORESET is in a sub-band full duplex (SBFD) timeslot or in a downlink timeslot; as well as The UE is configured to monitor for control transmissions from the base station within the one or more RBWs of the active BWP.

19. The device according to claim 18, wherein: The one or more RBWs correspond to an available bandwidth (BW) of the active BWP, the active BWP being in a sub-band full duplex (SBFD) time slot, and wherein the available BW does not include frequency resources for a guard band and uplink transmission.

20. The device according to claim 18, wherein The at least one processor coupled to the memory is further configured to: A configuration of one or more control resource sets (CORESETs) for each of the one or more RBWs is transmitted.

21. The device according to claim 18, wherein The configuration includes a bitmap of frequency domain resources corresponding to resource blocks (RBs) in an RBW.

22. The device according to claim 21, wherein The base station sends a search space configuration for one or more search space (SS) sets in a RBW and the SS set for defining a monitoring opportunity of a CORESET in the RBW.

23. The device according to claim 18, wherein The at least one processor coupled to the memory is further configured to: Sending an indication of half-duplex mode or full-duplex mode in a search space (SS) set associated with the CORESET, wherein the UE monitors the CORESET based on the indication by mapping the bitmap to resource blocks in the active BWP or mapping a subset of the bitmap to resource blocks in an active RBW of the one or more RBWs in the BWP.

24. The device according to claim 18, wherein The at least one processor coupled to the memory is further configured to: Sending a configuration for a control resource set (CORESET) associated with the active BWP, the configuration comprising: a bitmap of frequency domain resources for half-duplex mode, and one or more additional bitmaps of frequency resources for full-duplex mode each associated with an RBW in the BWP, wherein the UE uses the bitmap associated with the RBW to monitor the control transmission from the base station during one or more SBFD time slots.

25. The device according to claim 24, wherein: The at least one processor coupled to the memory is further configured to: sending an indication of a full-duplex mode for a search space (SS) set associated with the frequency domain resources for full-duplex operation, wherein the UE uses the one or more additional bitmaps to monitor the control transmission from the base station based on the indication of the full-duplex mode for the SS set and an active RBW for a monitoring opportunity in an SBFD time slot.

26. The device according to claim 20, wherein: The at least one processor coupled to the memory is further configured to: An indication of a half-duplex mode for a search space (SS) set associated with a bitmap of frequency domain resources is sent in the CORESET configuration, wherein the UE monitors the control transmission from the base station using the bitmap of frequency domain resources in a downlink time slot based on the indication of the half-duplex mode for the SS set.

27. A method of wireless communication at a user equipment (UE), comprising: communicating with a base station operating in a sub-band frequency division duplex (FDD) mode; receiving a downlink transmission within one or more resource bandwidths (RBWs) of an active bandwidth part (BWP); receiving a bitmap of frequency domain resources for a control resource set (CORESET) associated with the active BWP; determining a frequency resource for the monitoring occasion of the CORESET based on the bitmap and based on whether the monitoring occasion of the CORESET is in a sub-band full duplex (SBFD) time slot or in a downlink time slot; and Monitoring for control transmissions from the base station within the one or more RBWs of the active BWP.

28. A method for wireless communication at a base station, comprising: communicating with a user equipment (UE) when operating in a sub-band frequency division duplex (FDD) mode; Sending downlink transmissions within one or more resource bandwidths (RBWs) of an active bandwidth part (BWP); Sending a bitmap of frequency domain resources for a control resource set (CORESET) associated with the BWP; wherein the frequency resources for the monitoring occasion of the CORESET are determined based on the bitmap and based on whether the monitoring occasion of the CORESET is in a sub-band full duplex (SBFD) timeslot or in a downlink timeslot; as well as The UE is configured to monitor for control transmissions from the base station within the one or more RBWs of the active BWP.

Images