Time division duplex (TDD) carrier aggregation (CA) with non-cell definition (NCD) signaling

Abstract

An apparatus may include one or more memories having instructions individually or in combination. The apparatus may further include one or more processors, individually or in combination, configured to execute the instructions and cause the apparatus to: output, for transmission, an indication of whether the apparatus is capable of supporting half-duplex communication via time division duplex (TDD) carrier aggregation (CA); and obtaining a command configured to enable conflict handling by the apparatus, the command based on capabilities supported by the apparatus.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 447,841, filed August 10, 2023, entitled “TIME-DIVISION DUPLEX (TDD) CARRIER AGGREGATION (CA) WITH NON-CELL DEFINING (NCD) SIGNALING”, the entire contents of which are incorporated herein by reference. background Technical Field

[0003] This disclosure relates generally to wireless communication systems, and more specifically to communication of non-cell defined synchronization signal blocks (NCD-SSB) in inter-band time division duplex (TDD) carrier aggregation (CA). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd 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 are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a broad overview of all anticipated aspects, nor is it intended to identify key or essential elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0007] Some aspects relate to an apparatus for wireless communication, the apparatus comprising: one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the apparatus to: output an indication of whether the apparatus is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; and obtain a command configured to enable collision handling by the apparatus based on the capabilities supported by the apparatus.

[0008] Some aspects relate to an apparatus for wireless communication, the apparatus comprising: one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the apparatus to: obtain from a user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); and output a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE.

[0009] Some aspects relate to a method for wireless communication at a device, the method comprising: outputting an indication of whether the device is capable of supporting half-duplex communication via time division duplex (TDD) carrier aggregation (CA) for transmission; and obtaining a command configured to enable collision handling by the device, the command being based on the capabilities supported by the device.

[0010] Some aspects relate to a method for wireless communication at a device, the method comprising: obtaining from a user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time division duplex (TDD) carrier aggregation (CA); and outputting a command configured to enable collision handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE.

[0011] Some aspects relate to an apparatus comprising: a component for outputting an indication of whether the apparatus is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; and a component for obtaining a command configured to enable conflict resolution by the apparatus, the command being based on the capabilities supported by the apparatus.

[0012] Some aspects relate to an apparatus comprising: components for obtaining from a user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); and components for outputting a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE.

[0013] Some aspects relate to a non-transitory computer-readable medium comprising: instructions that, when executed by a device, cause the device to perform operations including: outputting an indication of whether the device is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; and obtaining a command configured to enable collision handling by the device based on capabilities supported by the device.

[0014] Some aspects relate to a non-transitory computer-readable medium comprising: instructions that, when executed by a device, cause the device to perform the following operations: obtaining from a user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); and outputting a command configured to enable conflict resolution at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE.

[0015] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only 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. Attached Figure Description

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

[0017] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0018] Figure 2B This is a diagram illustrating examples of DL channels within a subframe according to various aspects of this disclosure.

[0019] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0020] Figure 2D This is a diagram illustrating examples of UL channels within a subframe according to various aspects of this disclosure.

[0021] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0022] Figure 4 This is a block diagram illustrating an example decomposed base station architecture.

[0023] Figure 5 This is a block diagram conceptually illustrating an example set of BWPs, including a first bandwidth portion (BWP) and a second BWP, that a UE can be configured to perform monitoring.

[0024] Figure 6 This is an example. NonCellDefiningSSB A diagram of an information element (IE).

[0025] Figure 7 This is a block diagram that conceptually illustrates an example of a UE operating under an exception rule and communicating with a set of multiple serving cells.

[0026] Figure 8 This is a flowchart of a wireless communication method.

[0027] Figure 9 This is a flowchart of a wireless communication method.

[0028] Figure 10 This is a flowchart of a wireless communication method.

[0029] Figure 11 This is a flowchart of a wireless communication method.

[0030] Figure 12 This is a flowchart of a wireless communication method.

[0031] Figure 13 This is a flowchart of a wireless communication method.

[0032] Figure 14 This is a diagram illustrating an example of a hardware implementation used in an example device.

[0033] Figure 15 This is a flowchart of a wireless communication method.

[0034] Figure 16 This is a diagram illustrating another example of a hardware implementation used in the example device. Detailed Implementation

[0035] The detailed description below, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0036] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can 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 system as a whole.

[0037] As an example, an element, any part of an element, or any combination of elements may 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the 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, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0038] Therefore, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code in the form of computer-accessible instructions or data structures.

[0039] Figure 1 This is an illustration of 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, user equipment (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 macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0040] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio 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), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base stations 102 can communicate directly or indirectly with each other via a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0041] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to restricted groups referred to as closed subscriber groups (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For the total maximum amount used for sending in each direction, up to Yx MHz ( x For each carrier allocated in carrier aggregation (multiple component carriers), base station 102 / UE104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0042] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0043] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0044] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network.

[0045] 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 designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the extremely high frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0046] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0047] 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, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0048] Base station 180 may transmit beamformed signals to UE 104 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 transmit 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 optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0049] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmission, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base station 102 within a Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to a broadcast-specific service, and is responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0050] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are delivered via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IMS, packet switching (PS) streaming services, and / or other IP services.

[0051] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable terminology. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term. A radio node may include a UE, a base station, or a network entity of that base station.

[0052] Refer again Figure 1 UE 104 may include NCD-SSB module 198. As described in more detail elsewhere herein, NCD-SSB module 198 may be configured to output an indication of whether the device is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; and to obtain a command configured to enable collision handling by the device based on the capabilities supported by the device. Additionally or alternatively, NCD-SSB module 198 may perform one or more other operations described herein.

[0053] Base station 102 / 180 may include NCD-SSB module 199. As described in more detail elsewhere herein, NCD-SSB module 199 may be configured to receive from user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); and to output a command configured to enable conflict handling at the UE for transmission to the UE, the command being based on the capabilities supported by the UE. Additionally or alternatively, NCD-SSB module 199 may perform one or more other operations described herein.

[0054] Figure 2AFigure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the process of... Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 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 both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0055] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10-millisecond (ms) frame may be divided into 10 equal-sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL may be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets µ 0 to 4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter set µ, there are 14 symbols per slot and 2 per subframe. µ Each time slot. Subcarrier spacing and symbol length / duration are functions of the parameter set. Subcarrier spacing can be equal to... kilohertz (kHz), where The parameter sets are 0 to 4. Therefore, the subcarrier spacing for parameter set µ=0 is 15kHz, and the subcarrier spacing for parameter set µ=4 is 240kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples are provided for slot configuration 0 with 14 symbols per slot and parameter set µ=2 with 4 slots per subframe. Slot duration is 0.25 ms, subcarrier spacing is 60 kHz, and symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters.

[0056] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0057] like Figure 2AAs illustrated, some REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0058] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). Additional BWPs may be located at higher and / or lower frequencies in the channel bandwidth. The Primary Synchronization Signal (PSS) is located within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) is located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0059] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0060] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) / negative acknowledgment (NACK) feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0061] Figure 3This is a block diagram illustrating communication between base stations 102 / 180 and UE 104 in the access network. In the DL, IP packets from EPC 160 can be provided to one or more controllers / processors 375. Controllers / processors 375 implement Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0062] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. 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-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 are used to determine the decoding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 104. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0063] At UE 104, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 104. If multiple spatial streams are destined for UE 104, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then 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, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base stations 102 / 180. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by base stations 102 / 180 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

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

[0066] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the base station 102 / 180 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme, and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0067] UL transmission is processed at base station 102 / 180 in a manner similar to that described in conjunction with the receiver function at UE 104. Each receiver 318RX receives the signal via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0068] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the UE 104. 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 operation.

[0069] Figure 4 This is a block diagram illustrating an example decomposed base station 400 architecture. The decomposed base station 400 architecture may include one or more CUs 410, which may communicate directly with the core network 420 via a backhaul link, or indirectly with the core network 420 via one or more decomposed base station units, such as near real-time (RT) RICs 425 via E2 links, or non-RT RICs 415 associated with a Service Management and Orchestration (SMO) framework 405, or both. CUs 410 may communicate with one or more DUs 430 via corresponding midhaul links, such as F1 interfaces. DUs 430 may communicate with one or more RUs 440 via corresponding fronthaul links. RUs 440 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 440. As used herein, network entities may correspond to base stations or decomposed aspects of base stations (e.g., CU / DU / RU, etc.).

[0070] Each of the units, namely CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO frame 405, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals or transmit signals to one or more other units via wireless transmission media, or both.

[0071] In some respects, the CU 410 can host higher-level control functions. These control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 410. The CU 410 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 410 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 410 can be implemented to communicate with the DU 430 for network control and signaling, as needed.

[0072] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 440s. In some aspects, DU 430 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 430 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 430 or with control functions hosted by CU 410.

[0073] Lower-layer functionality can be implemented by one or more RU 440s. In some deployments, an RU440 controlled by a DU 430 may correspond to a logical node that is at least partially based on functional decomposition, such as lower-layer functional decomposition, to host RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both). In this architecture, the RU 440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration allows the DU 430 and CU 410 to be implemented in cloud-based RAN architectures such as Virtual RAN (vRAN) architectures.

[0074] SMO framework 405 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 405 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 405 can be configured to interact with cloud computing platforms such as Open Cloud (O-cloud) 490 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 410, DU 430, RU 440, and near-RT RIC 425. In some implementations, SMO framework 405 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 411) via the O1 interface. Additionally, in some implementations, SMO framework 405 can communicate directly with one or more RU 440s via the O1 interface. SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of SMO framework 405.

[0075] The non-RT RIC 415 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 425. The non-RT RIC 415 can be coupled to or communicate with the near-RT RIC 425, such as via an A1 interface. The near-RT RIC 425 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on interfaces connecting one or more CU 410s, one or more DU 430s, or both, and O-eNBs to the near-RT RIC 425, such as via an E2 interface.

[0076] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 425, the non-RT RIC 415 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 425 and may be received from non-network data sources or network functions at the SMO framework 405 or the non-RT RIC 415. In some examples, the non-RT RIC 415 or near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 415 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 405 (e.g., via O1 reconfiguration) or via the creation of RAN management policies (e.g., A1 policies).

[0077] For non-cell defined synchronization signal blocks ( NCD-SSB Introduction

[0078] Non-Cell Defined SSB (NCD-SSB) was initially introduced for Reduced Capability (RedCap) User Equipment (UE). As the name suggests, the purpose of NCD-SSB is not to identify a specific cell, but to provide the UE with synchronization signaling for channel measurement, channel quality, beam management, etc. In contrast, Cell Defined SSB (CD-SSB) is configured to provide the UE with synchronization signaling and an indication of the identity of the cell from which it sends the synchronization signaling. Therefore, NCD-SSB is the ideal synchronization signal for RedCap UEs that do not require cell identification information.

[0079] The base station can configure or schedule the transmission of one or more dedicated downlink bandwidth portions (BWPs) of NCD-SSB or CD-SSB. For example, each BWP may include at most one SSB (e.g., CD-SSB or NCD-SSB). Therefore, the UE can be configured (e.g., by the base station and / or the radio standard) to have two different BWPs for monitoring: a first BWP and a second BWP.

[0080] Figure 5 This is a block diagram conceptually illustrating an example set of BWPs 500, including a first BWP 502 and a second BWP 504, that a UE can be configured to monitor. Here, CD-SSB 506 is transmitted by a cell within the first BWP 502, and NCD-SSB 508 is transmitted by a cell within the second BWP 504. The UE can be configured for dynamic BWP activation, which allows the UE to activate any of the BWPs. In some examples, the first BWP 502 and the second BWP 504 can be different BWPs carrying the same component carrier (CC).

[0081] As used herein, a “dedicated BWP” refers to a BWP that the UE has configured (e.g., by a base station) for use, and that BWP can be a UE-specific BWP (e.g., signaling dedicated to a specific UE). A “public BWP” refers to a cell-specific BWP used for signaling that is not dedicated to a specific UE. An “initial BWP” refers to a BWP that the UE can use to initially access the cell and that can be advertised to the UE via the SIB or MIB. Typically, an initial BWP is configured such that it includes a CD-SSB. An “active BWP” can refer to a BWP that is configured / reconfigured by a base station via Radio Resource Control (RRC) for UE monitoring and can be configured to include a CD-SSB and / or an NCD-SSB.

[0082] Figure 6This is an example of configuring a UE to receive NCD-SSB. NonCellDefiningSSB Illustration of Information Element (IE) 600. The base station can send information containing... NonCellDefiningSSB The IE 600 RRC message configures the UE to monitor NCD-SSB in the initial BWP or a dedicated BWP. For example, this can be configured for each downlink BWP. NonCellDefiningSSB IE 600 (for example, via BWP-DownlinkDedicated (IE configuration). In other words, for each BWP that has a UE configured for it, NonCellDefiningSSB IE 600 may differ. If NonCellDefiningSSB If the IE 600 is configured for a specific BWP, the UE can monitor NCD-SSB instead of CD-SSB.

[0083] NonCellDefiningSSB The IE 600 may include three main components: the absolute radio frequency channel number (ARFCN) configured to provide the frequency domain location of the NCD-SSB, the periodicity of the NCD-SSB, and the time offset of the NCD-SSB. (Re-reference) Figure 5 , NonCellDefiningSSB IE 600 can configure the UE to receive the NCD-SSB 508 of the second BWP 504 by providing ARFCN, periodicity and offset information associated with the NCD-SSB 508.

[0084] In certain scenarios, the UE can be configured to have the capability for dynamic active BWP handover. That is, the UE can dynamically switch from one BWP to another by changing which BWP is active. In one example, the UE can be configured for restricted dynamic BWP handover. In this case, the UE can dynamically switch the active BWP from multiple configured BWPs, where each of the multiple BWPs contains CD-SSB signaling within its corresponding bandwidth.

[0085] Alternatively, the UE can be configured for unrestricted dynamic BWP handover. In this case, the UE can dynamically switch the active BWP from multiple configured BWPs, and any of the multiple BWPs can be configured such that the BWP does not contain a CD-SSB within the bandwidth of the corresponding BWP. However, a problem arises because when a CD-SSB is not transmitted within the UE's active BWP, it is unclear how the UE should behave for channel measurement operations (e.g., beam management, radio link monitoring, beam fault recovery, beam fault detection, etc.).

[0086] One solution to this problem involves allowing non-RedCap UEs to receive and use NCD-SSB within an active BWP. Often referred to as "Option C," this allows a base station or cell to configure a non-RedCap UE for unrestricted dynamic BWP handover, provided the UE can receive and use NCD-SSB within an active BWP that may not include CD-SSB. Therefore, the non-RedCap UE can perform channel measurement operations based on the NCD-SSB signal within the active BWP. Consequently, the base station or cell can configure the UE for unrestricted BWP handover as long as the BWP used by the UE is configured by the base station or cell to include at least one of CD-SSB signaling and / or NCD-SSB signaling.

[0087] For time division duplex (TDD) TDD Carrier aggregation CA Introduction to half-duplex operation

[0088] It should be noted that Option C capability is per-band capability. That is, if a UE declares support for Option C in a specific frequency band, then the UE should be able to perform Option C communication on that band in any carrier aggregation (CA) band combination that includes that band. For example, a UE may send an indication of its support for Option C in the 3.5 GHz band and its support for CA via a combination of the 3.5 GHz and 4.5 GHz bands. In this case, if the UE and the base station communicate via CA using a combination of the 3.5 GHz and 4.5 GHz bands, then the UE should be able to use Option C in the 3.5 GHz band with CA using a combination of the 3.5 GHz and 4.5 GHz bands. Inter-band CA involves communication scenarios where the Option C carrier aggregation (CA) carriers belong to different operating bands. Some operator frequency allocation scenarios may require this type of communication.

[0089] For a UE using option C for half-duplex communication via inter-band time division duplex (TDD) CA, the UE may indicate to the cell its preference for half-duplex communication via TDD CA (e.g., half-DuplexTDD-CA-SameSCS-r16 Support for ) and, in response, the cell can configure the UE to perform conflict resolution at the UE for multiple cells in the CA (e.g., enable ). directionalCollisionHandling-r16 (Fields). It should be noted that... half-DuplexTDD-CA-SameSCS-r16 It also instructs the UE not to transmit via one CC and receive simultaneously via another CC, even if the two CCs are inter-band CCs. Therefore, the enabled... directionalCollisionHandling-r16 This enables the UE to handle potential conflicts (e.g., downlink on the first CC and uplink on the second CC, both during the same symbol period).

[0090] If the UE is not configured to monitor the PDCCH for DCI (e.g., DCI format 2_0) on any of multiple cells and the UE cannot simultaneously transmit and receive with multiple cells (e.g., a UE using half-duplex TDD CA), the UE can select the reference cell for each symbol as the active cell by choosing the cell with the smallest cell index among one or more cells. Based on the selected reference cell, the UE can perform directional conflict handling between CCs on a symbol-by-symbol basis. This can be illustrated with an example in Table 1 below.

[0091]

[0092] Table 1

[0093] The term "semi-SFI D / U" is defined as a semi-static slot format indicator (SFI) for the downlink (D) or uplink (U). Semi-SFI D / U can be generated by the cell or base station using higher-layer signaling (e.g., tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigDedicated The term "RRC D / U" is defined as a semi-static configuration of the downlink / uplink for PDCCH, PDSCH, CSI-RS, PUCCH, PUSCH, SRS, and / or any other suitable signaling. The term "Dynamic D / U" refers to the downlink / uplink symbol corresponding to dynamic grant. It should be noted that while the granularity of collision handling has been described according to the symbol, any suitable granularity level, including slots and frames, may also be used.

[0094] Table 1 defines a set of directional conflict rules that typically prioritize a reference cell. The reference cell column may correspond to a CC of a reference cell, and another cell column may correspond to a CC of another cell. In row 1 (e.g., the first rule), the reference cell may be a first CC (e.g., the CC with the smallest relative cell ID) configured using a TDD downlink slot or symbol that overlaps in the time domain with a TDD uplink slot or symbol of a second CC identified as another cell (e.g., one or more symbols). A downlink symbol (e.g., a half-SFI U) overlapping with an uplink symbol (half SFI U) introduces a directional conflict for the UE because the UE cannot simultaneously receive downlink signaling on the first CC and transmit uplink signaling on the second CC. Therefore, according to Table 1, the UE may prioritize downlink signaling from the reference cell and discard uplink transmissions (e.g., discard the entire uplink slot or only discard uplink symbols that overlap with the downlink slot in the time domain). It should be noted that Table 1 is an example set of rules for directional conflict management by the UE, and the UE may use any suitable set of rules and / or condition sets to select a reference cell.

[0095] In some examples, a UE that is not capable of or configured to simultaneously transmit and receive with multiple cells and is configured for targeted conflict resolution (e.g., a UE operating in half-duplex mode) can receive from a base station or one or more cells a signal indicating that an SSB is being transmitted by the corresponding cell or base station (e.g., ...). ServingCellConfigCommonSIB within ssb-PositionsInBurst For example, a value of "0" in the bitmap indicates that the corresponding SSB will not be sent, while a value of "1" indicates that the corresponding SSB will be sent. However, the direction conflict rule may not consider SSBs sent by multiple cells. Therefore, the UE can handle SSBs independently of the direction conflict rule.

[0096] In one example, it is configured to handle potential conflicts and is configured for half-duplex CA (e.g., UE indication). half- DuplexTDD-CA-SameSCS-r16 ) and UEs not configured to monitor PDCCH for DCI can operate under exceptions to one or more directional conflict rules (e.g., Figure 7 Here, for one of them ssb-PositionsInBurst The symbol indicating that the first serving cell among multiple serving cells is transmitting an SSB (Service Subsystem for Backlink) allows the UE to prioritize receiving the SSB and discard uplink transmissions (e.g., PUSCH, PUCCH, PRACH, or SRS) that conflict with the downlink SSB symbol. In other words, if any symbol used for uplink transmission overlaps with the SSB symbol, the UE can discard uplink transmissions from all serving cells among the multiple serving cells.

[0097] Figure 7 This is a block diagram conceptually illustrating an example of a UE operating under exceptional rules and communicating with a set of multiple serving cells. Here, the UE (e.g., Figure 1 and Figure 3 UE 104 is configured to communicate via a first serving cell (e.g., CC1706), a second serving cell (e.g., CC2708), a third serving cell (e.g., CC3710), and a fourth serving cell (e.g., CC4712) using half-duplex communication utilizing inter-band TDD CA. Both the first and second serving cells can be the first base station 702 (e.g., Figure 1 and Figure 3 Base station 102; Figure 4 The second base station 704 is a discrete component of the decomposed base station 400, and both the third and fourth serving cells can be discrete components of the second base station 704. Alternatively, each serving cell can be associated with a different base station or network entity. It can be assumed that the UE is configured for inter-band TDD CA, configured for targeted conflict resolution for serving cells, and supports... half-DuplexTDD-CA-SameSCS-r16 The capability, and is not configured to monitor the PDCCH for DCI from any serving cell in the serving cell.

[0098] exist Figure 7 In the example, the UE can communicate with the first base station 702 via the first CC 706 and the second CC 708 in the 3.5 GHz operating band. The UE can also communicate with the second base station 704 via the third CC and the fourth CC in the 4.5 GHz operating band. In this example, because there is insufficient frequency gap between the two operating bands, the UE may not be able to use the same time-domain resources (e.g., symbols, time slots, etc.) to transmit to one base station while simultaneously receiving signaling from the other. In other words, the UE may not be able to simultaneously transmit to one cell and receive from another cell without significant interference or path loss. It should be noted that various factors, including environmental factors and UE capabilities, may prevent the UE from transmitting and receiving simultaneously. Although Figure 7 This example illustrates only the communication between a UE and two base stations and four serving cells, but the UE can use the same techniques and methods described herein to communicate with any suitable number of base stations and cells (including more or fewer base stations and / or cells).

[0099] Therefore, if the UE is notified that one or more symbols will be used by each cell to transmit an SSB, the UE will not transmit uplink communication via any symbol in any of the one or more symbols of any of the CCs (e.g., the UE may discard uplink transmissions). Thus, downlink SSBs are given higher priority than uplink opportunities sharing the same time-domain resources as SSBs.

[0100] The first base station 702 may utilize a first SSB 722 transmitted via a first CC 706, a second SSB 726 transmitted via a second CC 708, and a third SSB 730 transmitted via the first CC 706 to (e.g., using the first CC 706) ssb- PositionsInBurst Configure the UE. Similarly, the second base station 704 can utilize the fourth SSB 724 via the third CC 710 and the fifth SSB 728 via the fourth CC 712 to (e.g., using the second ssb-PositionsInBurst Configure the UE.

[0101] Here, the first SSB 722 and the fourth SSB 724 overlap in the time domain, with the first SSB 722 occupying more time domain resources compared to the fourth SSB 724. Therefore, the UE can avoid using any CC to send any uplink communication to either serving cell during the first set 714 of time domain resources. Here, the first set 714 of time domain resources is primarily defined by the time domain resources used for the first SSB 722.

[0102] The second SSB 726 uses the time-domain resources in the second CC 708. Although no other CC is used for the downlink SSB during this time period, the UE may avoid sending any uplink communication to either serving cell during the second set 716 of time-domain resources defined by the time-domain resources used for the second SSB 726.

[0103] The fifth SSB 728 uses the time-domain resources in the third CC 710. Although no other CC is used for the downlink SSB during this time period, the UE may avoid sending any uplink communication to any serving cell during the third set 718 of time-domain resources defined by the time-domain resources used for the fifth SSB 728.

[0104] Finally, the third SSB 730 uses the time-domain resources in the first CC 706. Although no other CC is used for the downlink SSB during this time period, the UE can avoid sending any uplink communication to either serving cell during the fourth set 720 of time-domain resources defined by the time-domain resources used for the third SSB 730.

[0105] Therefore, the rules for downlink SSB communication can be exceptions to one or more of the rules described above in conjunction with Table 1, because the UE can prioritize SSB reception over uplink transmission by discarding uplink transmissions that use the same time-domain resources as the SSB. Thus, the UE can use the received SSB to perform channel measurement operations and reduce interference or path loss caused by simultaneous downlink reception and uplink transmission.

[0106] It should be noted that the UE is executable. Figure 7 The illustrated exception SSB handling is an extension of its directed conflict handling procedure. For example, the UE can: (1) based on all relevant cells and CCs ssb-PositionsInBurst To identify the UL prohibited resources of all cells, and then (2) perform the binding based on which cell is the reference cell. Figure 5 The described directional conflict handling. The first procedure (1) may not depend on which serving cell is active / inactive or which downlink BWP of each CC is active / inactive. Therefore, if the active BWP of a CC changes, or if another serving cell (e.g., another CC) becomes active, the UE may not need to perform the first procedure of identifying UL to prohibit resources again.

[0107] However, whenever the active BWP of the UE's CC changes, the UE may need to perform one or more of the first procedure (1) and the second procedure (2). For example, if the UE is configured for option C of the CC, the UE may receive the NCD-SSB configuration for each dedicated downlink BWP configuration of the CC. The NCD-SSB configuration may differ for different dedicated downlink BWP configurations of the CC. Therefore, depending on which BWP of the CC is active, the NCD-SSB position (e.g., periodic and / or offset) may change, causing the UE to re-perform based on ssb-PositionsInBurst The first process is to identify the UL-restricted resources for all cells. Additionally, whenever a UE changes its active BWP, the UE may need to perform a second process to determine the handling of orientation conflicts, because the rules controlling UE behavior (e.g., Figure 7 The rules shown can be changed depending on which BWP is active for each serving cell. Therefore, whenever a UE switches the active BWP of any of the multiple cells with which it communicates, it may take the UE a relatively large amount of time to perform procedures (1) and (2).

[0108] Example techniques for reducing processing time associated with the first and second processes.

[0109] The following is a solution for reducing the number of instances where the UE must perform either the first procedure (1) or the second procedure (2) described above. For the following purposes, it can be assumed that the UE is utilizing an enabled... directionalCollisionHandling-r16 It is configured using half-duplex bandwidth TDD CA.

[0110] In some respects, based on conflict resolution performed by the UE, the UE may not be expected to be configured for unrestricted dynamic active BWP handover and / or Option C. In other words, if the UE supports... half-DuplexTDD-CA-SameSCS-r16 Furthermore, if the network is configured to perform targeted conflict resolution, it can restrict the UE's use of the NCD-SSB in option C. In one example, the network can configure the UE for restricted dynamic active BWP handover, causing the UE to use the CD-SSB instead of the NCD-SSB for channel measurements. If necessary, the network can alternatively configure the UE for one of options A, B-1-1, or B-1-2. Therefore, when handover an active BWP in any of multiple serving cells, the UE does not need to re-execute the first or second procedure because the CD-SSB location is known to the UE.

[0111] In some respects, the network can restrict the transmission of NCD-SSBs to the same time-domain resources or a subset of the same time-domain resources used for transmitting CD-SSBs. It should be noted that the transmissions from each serving cell... ssb-PositionsInBurstThe UE is provided with the location of the CD-SSB for each CC used by the corresponding serving cell. Therefore, while each of the multiple serving cells can transmit the NCD-SSB via any one or more corresponding CCs, the network can restrict the transmission of the NCD-SSB to the time-domain resources used by the CD-SSB. For example, if the CD-SSB periodicity is 20ms for one or more serving cells, the NCD-SSB transmitted for any active BWP of any serving cell in the multiple serving cells can have a periodicity of 20ms, 40ms, 80ms, or 160ms, and / or an offset of 0ms, 20ms, 40ms, or 80ms. Although the NCD-SSB location may differ across different BWPs for any serving cell in the multiple serving cells, the UE does not need to repeat the first process to identify uplink prohibited resources because all NCD-SSB locations are within the known uplink prohibited resources identified by the CD-SSB of the serving cell.

[0112] In some respects, if a UE switches its active BWP from a first BWP to a second BWP for a first serving cell, and the second BWP uses an NCD-SSB, the UE can expect that each NCD-SSB symbol of the first serving cell is also a downlink symbol of the reference cell. For example, an NCD-SSB symbol used by a serving cell in a CC can be the same symbol used for downlink transmission by another CC and / or another serving cell. In some examples, the downlink transmission symbols are based on the reference cell. tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated This is configured because, according to the example rules shown in Table 1 above, the downlink symbol of the reference cell can typically have a higher priority than the cell, and therefore, if the same symbol used by the downlink symbol of the reference cell is used to transmit the NCD-SSB symbol, the UE can receive the NCD-SSB and is prevented from transmitting on the uplink symbol associated with another cell during the downlink symbol of the reference cell.

[0113] In some respects, the reference cell can be configured to be located on its downlink symbol (e.g., via...). tdd-UL-DL- ConfigurationCommon or tdd-UL-DL-ConfigurationDedicatedDuring the configured downlink symbol period, the NCD-SSB is transmitted. Therefore, because the TDD downlink slot or symbol of the reference cell has the highest priority according to Table 1 above, the UE will prefer the downlink symbol of the reference cell to the same symbol of another cell. Therefore, in the second process, the UE can always receive the NCD-SSB from the reference cell, as this NCD-SSB will have a higher priority than symbols from other cells. In some examples, when the UE performs the first process, the UE may not consider the NCD-SSB (e.g., the UE may only consider the CD-SSB). Therefore, if the NCD-SSB symbol of another cell conflicts with the TDD uplink slot or symbol of the reference cell, the UE may discard or ignore the NCD-SSB transmitted by a cell other than the reference cell.

[0114] In some examples, the UE may consider the NCD-SSB location for the second process and treat the NCD-SSB location as “RRC D” (e.g., RRC downlink), which is relative to the path via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated The configured downlink symbols have lower priority. Therefore, in this example, the UE has a greater chance to discard the NCD-SSB signal in the event of a directional conflict. Similarly, if a reference cell is transmitting an NCD-SSB, that reference cell may have higher priority relative to another cell. In another cell, or in the reference cell, the NCD-SSB may be discarded when it overlaps with the dynamic U of another cell.

[0115] In some respects, the UE can be configured to consider the NCD-SSB in its active downlink BWP for the first process (e.g., the UE can be based on...). ssb-PositionsInBurst(To identify uplink prohibited resources in the cell). Because the UE may need to perform a first procedure each time it changes its active BWP, the UE can be configured to utilize a relatively long handover delay, which is configured to provide the UE with additional time to perform the first procedure. For example, if the UE switches its active BWP from the first BWP to the second BWP, but does not need to consider the NCD-SSB (e.g., the UE does not need to perform the first procedure), the UE can use the first handover delay. However, if the UE switches its active BWP from the third BWP to the fourth BWP, and must consider the NCD-SSB (e.g., the UE can perform the first procedure to determine the uplink prohibited resources), the UE can use a second handover delay with a longer duration relative to the first handover delay. As used herein, “non-legacy handover delay” or “second handover delay” is defined by the handover delay provided by the 3GPP Release 18 radio standard and future releases. “Legacy handover delay” or “first handover delay” may correspond to the handover delay as defined by the 3GPP standard Release 17 and earlier.

[0116] Figure 8 This is a flowchart of a wireless communication method 800. Method 800 can be performed by a UE (e.g., UE 104; device 1402). In some examples, method 800 may include a combination of... Figures 9 to 13 One or more aspects illustrated and described. Method 800 may be processed by one or more processors (e.g., Figure 3 The controller / processor 359, RX processor 356, TX processor 368, memory 360, etc. in the system are used to execute the commands.

[0117] At point 802, the UE can output an indication of whether the device supports half-duplex communication via Time Division Duplex (TDD) carrier aggregation (CA) for transmission. For example, 802 can be performed by the transmitting component 1440. Here, the UE can transmit its capabilities to the base station or network entity, allowing the base station to adjust how it communicates with the UE. For example, the UE can indicate its capabilities for... half- DuplexTDD-CA-SameSCS-r16 Capability support. In some respects, the capability of half-duplex communication is associated with inter-band TDD CA.

[0118] At 804, the UE may receive a command configured to enable conflict resolution by the device, based on capabilities supported by the device. For example, 804 may be executed by receiving component 1442. Here, the base station or network node may configure the UE for targeted conflict resolution of a set of cells in the CA (e.g., directionalCollisionHandling-r16 =Enabled). The base station can configure the UE for targeted conflict resolution based on UE communications at 802.

[0119] At 806, the UE may optionally receive signaling configuring the device for dynamic active BWP handover between multiple bandwidth portions (BWPs), wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SSB). For example, 806 may be performed by receiving component 1442. Here, the base station may configure the UE such that the UE can dynamically handover active BWPs between multiple BWPs. In some examples, each of the multiple BWPs includes a CD-SSB. In some examples, one or more of the multiple BWPs include an NCD-SSB instead of a CD-SSB. In other words, at 806, if directionalCollisionHandling-r16 =When enabled, the base station can avoid configuring the UE to use a BWP that includes NCD-SSB.

[0120] Figure 9 This is a flowchart illustrating a wireless communication method 800, including as Figure 8 and Figures 10 to 13 These are supplementary and / or alternative aspects to those aspects shown. In combination with these aspects, the network may not transmit NCD-SSBs outside of the time resources used by CD-SSBs. For example, NCD-SSBs may use CD-SSB time resources for transmission, but may not be transmitted outside of those time resources.

[0121] At 902, the UE can communicate with multiple cells using half-duplex inter-band TDD CA via multiple component carriers (CCs). For example, 902 can be performed by transmitting component 1440 and receiving component 1442. Here, the UE can transmit signaling and receive signaling from multiple base stations using half-duplex TDD CA via multiple CCs. If the UE is configured for directed collision handling, the UE can base its actions on... ssb-PositionsInBurst To identify all prohibited resources for CC (e.g., first process).

[0122] At 904, the UE can obtain a Cell Defined Synchronization Signal Block (CD-SSB) via the first CC among a plurality of CCs within a first set of time-domain resources. For example, 904 can be performed by the receiving component 1442.

[0123] At 906, the UE can obtain a non-cell-defined synchronization signal block (NCD-SSB) via a second CC among a plurality of CCs within a first set of time-domain resources or within a subset of time-domain resources in the first set. For example, 906 can be performed by the receiving component 1442.

[0124] In some respects, NCD-SSB is obtained via the downlink bandwidth portion (BWP) of the second CC.

[0125] Figure 10 This is a flowchart illustrating a wireless communication method 800, including as Figure 8, Figure 9 and Figures 11 to 13 These are supplementary and / or alternative aspects to those aspects shown. In conjunction with these aspects, any CC's NCD-SSB resource is a semi-static downlink symbol for the reference cell.

[0126] At 1002, the UE can communicate with multiple cells via a plurality of CCs, including a first component carrier (CC) and a second CC, using half-duplex inter-band TDD CA, wherein the plurality of cells includes a reference cell and another cell. For example, 1002 can be performed by a transmitting component 1440 and a receiving component 1442.

[0127] At 1004, the UE can obtain a first non-cell defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via a first CC associated with a reference cell or another cell. For example, 1004 can be performed by the receiving component 1442.

[0128] In some respects, the first CC is associated with a reference cell, and the first one or more symbols are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0129] In some respects, the first CC is associated with another cell and the second CC is associated with a reference cell, and the first one or more symbols of the second CC are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0130] Figure 11 This is a flowchart illustrating a wireless communication method 800, including as Figures 8 to 10 , Figure 12 and Figure 13 These are supplementary and / or alternative aspects to those aspects shown. In combination with these aspects, the NCD-SSB has the highest priority when transmitted from the reference cell.

[0131] At 1102, the UE can communicate with multiple cells, including a reference cell and another cell, via multiple component carriers (CCs) using half-duplex inter-band TDD CA, wherein the multiple CCs include a first CC associated with the reference cell and a second CC associated with the other cell. For example, 1102 can be performed by a transmitting component 1440 and a receiving component 1442.

[0132] At 1104, the UE can obtain a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via the first CC. For example, 1104 can be performed by the receiving component 1442.

[0133] At 1106, the UE may discard at least the first symbol of one or more symbols of the second CC based on at least one of the following: the NCD-SSB occupies one or more symbols, or at least the first symbol is an uplink symbol. For example, 1106 may be performed by signal processing component 1444. As used herein, discarding a symbol may involve the UE not monitoring or receiving the symbol. In some examples, the UE may discard the symbol by avoiding transmission via the symbol.

[0134] Figure 12 This is a flowchart illustrating a wireless communication method 800, including as Figures 8 to 11 and Figure 13 These are supplementary and / or alternative aspects to those aspects shown. In combination with these aspects, the UE can be configured to utilize a longer handover delay.

[0135] At 1202, the UE can communicate with multiple cells, including a reference cell and another cell, via a plurality of CCs, including a first component carrier (CC) and a second CC, using half-duplex inter-band TDD CA, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell. For example, 1202 can be performed by a transmitting component 1440 and a receiving component 1442.

[0136] At 1204, the UE may discard a Non-Cell Defined Synchronization Signal Block (NCD-SSB) occupying one or more symbols of the first CC, wherein the NCD-SSB is discarded based on one or more symbols of the second CC being configured as a semi-static uplink or a Radio Resource Control (RRC) uplink. For example, 1214 may be performed by signal processing component 1444. In some aspects, the NCD-SSB may be further discarded based on the second CC being associated with a reference cell and the reference cell having a higher priority than another cell (e.g., a non-reference cell).

[0137] Figure 13 This is a flowchart illustrating a wireless communication method 800, including as Figures 8 to 12 These are supplementary and / or alternative aspects to those aspects shown. In conjunction with these aspects, for example, if the UE switches its active BWP from a first BWP to a second BWP, but does not need to consider the NCD-SSB (e.g., the UE does not need to perform the first procedure), the UE can use the first handover delay. However, if the UE switches its active BWP from a third BWP to a fourth BWP, and must consider the NCD-SSB of the fourth BWP (e.g., the UE can perform the first procedure to determine uplink prohibited resources), the UE can use a second handover delay with a longer duration relative to the first handover delay to perform the first procedure.

[0138] At 1302, the UE can communicate with multiple cells via multiple component carriers (CCs) using half-duplex inter-band TDD CA. For example, 1302 can be performed by transmitting component 1440 and receiving component 1442.

[0139] At 1304, the UE output device is configured to indicate a non-legacy bandwidth portion (BWP) handover delay for transmission in response to a command to enable conflict handling. For example, 1304 may be performed by the transmission component 1440.

[0140] At 1306, the UE may optionally monitor the first bandwidth portion (BWP) of one or more of a plurality of CCs. For example, 1306 may be performed by monitoring component 1446.

[0141] At 1308, the UE may optionally hand over from the first BWP to the second BWP within a non-legacy BWP handover delay. For example, 1308 may be performed by handover component 1448. The non-legacy BWP handover delay may be a longer duration than the non-legacy handover delay to allow the UE to perform the first procedure (e.g., based on...). ssb-PositionsInBurst (To identify prohibited resources). Therefore, the handover latency of non-legacy BWPs can have a longer duration compared to the handover latency of legacy BWPs.

[0142] Figure 14Figure 1400 illustrates an example of a hardware implementation for device 1402. Device 1402 is a UE and includes a cellular baseband processor 1404 (also referred to as a modem) coupled to a cellular RF transceiver 1422 and one or more Subscriber Identity Module (SIM) cards 1420, an application processor 1406 coupled to a Secure Digital Card (SD) card 1408 and a screen 1410, a Bluetooth module 1412, a Wireless Local Area Network (WLAN) module 1414, a Global Positioning System (GPS) module 1416, and a power supply 1418. The cellular baseband processor 1404 communicates with the UE 104 and / or BS 102 / 180 via the cellular RF transceiver 1422. The cellular baseband processor 1404 may include computer-readable media / memory. This computer-readable media / memory may be non-transitory. The cellular baseband processor 1404 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1404, the software causes the cellular baseband processor 1404 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1404 during software execution. The cellular baseband processor 1404 further includes a receiving component 1430, a communication manager 1432, and a transmitting component 1434. The communication manager 1432 includes one or more of the illustrated components. The components within the communication manager 1432 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 104 and may include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, the device 1402 may be a modem chip and include only the baseband processor 1404, and in another configuration, the device 1402 may be the entire UE (e.g., see...). Figure 3 UE 104) and includes the additional modules previously discussed for device 1402. In various examples, device 1402 may be a chip, SoC, chipset, package, or device that may include: one or more modems (such as a Wi-Fi (IEEE 802.11) modem or a cellular modem such as a 3GPP 4G LTE or 5G compatible modem); one or more processors, processing blocks, or processing elements (collectively, “processors”); one or more radio components (collectively, “radio components”); and one or more memories or blocks of memory (collectively, “memory”).

[0143] The communication manager 1432 includes a transmission component 1440 configured to output an indication of whether the device can support half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; communicating with multiple cells via multiple component carriers (CCs) using half-duplex inter-band TDD CA; communicating with multiple cells via multiple CCs including a first component carrier (CC) and a second CC, wherein the multiple cells include a reference cell and another cell; communicating with multiple cells including a reference cell and another cell via multiple component carriers (CCs) using half-duplex inter-band TDD CA, wherein the multiple CCs include a first CC associated with the reference cell and a second CC associated with the other cell; communicating with multiple cells including a reference cell and another cell via multiple CCs including a first component carrier (CC) and a second CC using half-duplex inter-band TDD CA, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell; and communicating with multiple cells including a reference cell and another cell via multiple component carriers (CCs) using half-duplex inter-band TDD CA. CA to communicate with multiple cells; and output devices configured to indicate non-legacy bandwidth portion (BWP) handover delay for transmission in response to a command to enable conflict handling; for example, as described in combination with 802, 902, 1002, 1102, 1202, 1302 and 1304.

[0144] Communication manager 1432 further includes receiving component 1442 configured to receive a command configured to enable collision handling by the device, the command being based on capabilities supported by the device; receive signaling configuring the device for dynamic active BWP handover between multiple bandwidth portions (BWPs), wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SSB); communicate with multiple cells via multiple component carriers (CCs) using half-duplex inter-band TDD CA; obtain a cell-defined synchronization signal block (CD-SSB) via a first CC of the multiple CCs within a first set of time-domain resources; obtain a non-cell-defined synchronization signal block (NCD-SSB) via a second CC of the multiple CCs within the first set of time-domain resources or within a subset of time-domain resources within the first set; and use half-duplex inter-band TDD CA via multiple CCs including the first component carrier (CC) and the second CC. CA communicates with multiple cells, including a reference cell and another cell; obtains a first non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via a first CC associated with the reference cell or another cell; uses half-duplex inter-band TDD CA to communicate with multiple cells including a reference cell and another cell via multiple component carriers (CCs), wherein the multiple CCs include a first CC associated with the reference cell and a second CC associated with the other cell; obtains a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via the first CC; uses half-duplex inter-band TDD CA to communicate with multiple cells including a reference cell and another cell via multiple CCs including a first component carrier (CC) and a second CC, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell; and uses half-duplex inter-band TDD CA via multiple component carriers (CCs). CA is used to communicate with multiple cells, such as those described in combination with 804, 806, 902, 904, 906, 1002, 1004, 1102, 1104, 1202, 1302 and 1304.

[0145] The communication manager 1432 further includes a signal processing component 1444 configured to discard at least a first symbol of one or more symbols of the second CC based on at least one of the following: the NCD-SSB occupies one or more symbols, or at least the first symbol is an uplink symbol; and to discard a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC, wherein the NCD-SSB is discarded based on one or more symbols of the second CC being configured as a semi-static uplink or a radio resource control (RRC) uplink, for example, as described in conjunction with 1106 and 1204.

[0146] The communication manager 1432 further includes a monitoring component 1446 configured to monitor a first bandwidth portion (BWP) of one or more of a plurality of CCs, for example, as described in conjunction with 1306.

[0147] The communication manager 1432 further includes a switching component 1448 configured to switch from a first BWP to a second BWP within a non-legacy BWP switching delay, for example, as described in conjunction with 1308.

[0148] The device may include execution Figures 8 to 13 The additional components of each box in the algorithm's box in the aforementioned flowchart. Therefore, Figures 8 to 13 Each block in the aforementioned flowchart may be executed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0149] In one configuration, device 1402 (and specifically, cellular baseband processor 1404) includes components for outputting an indication of whether the device is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; components for obtaining a command configured to enable collision handling by the device, the command being based on capabilities supported by the device; components for obtaining signaling configuring the device for dynamic active BWP handover between multiple bandwidth portions (BWPs), wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SSB); and components for using half-duplex inter-band TDD via multiple component carriers (CCs). The CA is a component for communicating with multiple cells; a component for obtaining a cell-defined synchronization signal block (CD-SSB) via a first CC among multiple CCs within a first set of time-domain resources; a component for obtaining a non-cell-defined synchronization signal block (NCD-SSB) via a second CC among multiple CCs within the first set of time-domain resources or within a subset of time-domain resources within the first set; and a component for using half-duplex inter-band TDD via multiple CCs including a first component carrier (CC) and a second CC. The components for communication with multiple cells via CA, including a reference cell and another cell; components for obtaining a first or more symbols of a non-cell-defined synchronization signal block (NCD-SSB) occupying the first CC via a first CC associated with the reference cell or another cell; components for communication with multiple cells including a reference cell and another cell via half-duplex inter-band TDDCA using multiple component carriers (CCs), wherein the multiple CCs include a first CC associated with the reference cell and a second CC associated with the other cell; components for obtaining a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via the first CC; components for discarding at least a first symbol of one or more symbols of the second CC based on at least one of the following: the NCD-SSB occupies one or more symbols, or at least the first symbol is an uplink symbol; and components for using half-duplex inter-band TDDCA via multiple CCs including the first component carrier (CC) and the second CC. The components include: a CA for communicating with multiple cells, including a reference cell and another cell, wherein a first CC is associated with the other cell and a second CC is associated with the reference cell; a component for discarding a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC, wherein the NCD-SSB is discarded based on one or more symbols of the second CC being configured as a semi-static uplink or a radio resource control (RRC) uplink; a component for communicating with multiple cells via a half-duplex inter-band TDD CA using multiple component carriers (CCs); and a component for outputting an indication of non-legacy bandwidth portion (BWP) handover delay for transmission in response to a command to enable collision handling.A component for monitoring the first bandwidth portion (BWP) of one or more of a plurality of CCs; and a component for switching from the first BWP to the second BWP within a non-legacy BWP handover delay.

[0150] The aforementioned components may be one or more of the aforementioned components of the device 1402 configured to perform the functions described therein. As described above, the device 1402 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described therein.

[0151] In some cases, a device may have an interface (output component) for outputting frames for transmission, rather than actually transmitting the frames. For example, a processor may output frames to a radio frequency (RF) front end for transmission via a bus interface. Similarly, a device may have an interface (acquisition component) for receiving frames from another device, rather than actually receiving the frames. For example, a processor may acquire (or receive) frames from an RF front end for receiving via a bus interface.

[0152] Figure 15 This is a flowchart of a wireless communication method 1500. The method can be executed by a network entity or a base station (e.g., base station 102 / 180; device 1602). Method 1500 can be executed by one or more processors (e.g., Figure 3 The controller / processor 375, RX processor 370, TX processor 316, memory 376, etc. are used to execute the commands.

[0153] At 1502, the network entity can obtain from the user equipment (UE) an indication of whether the UE can support half-duplex communication via time-division duplex (TDD) carrier aggregation (CA). For example, 1502 can be performed by the receiving component 1640.

[0154] At 1504, the network entity can output a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE. For example, 1504 can be executed by the transmitting component 1642.

[0155] At 1506, a network entity can avoid configuring a UE for unrestricted dynamic active bandwidth portion (BWP) handover based on a command that enables conflict handling at the UE. For example, 1504 can be performed by avoidance component 1644.

[0156] At 1508, the network entity may output signaling configuring the UE for dynamic active BWP handover between multiple bandwidth portions (BWPs) for transmission to the UE, wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SSB). For example, 1504 may be performed by the transmitting component 1642.

[0157] At 1510, the network entity may output a cell definition synchronization signal block (CD-SSB) via a first CC of multiple component carriers (CCs) for transmission to the UE, wherein the CD-SSB is output for transmission within a first set of time-domain resources. For example, 1510 may be performed by transmission component 1642.

[0158] At 1512, the network entity may output a Non-Cell Defined Synchronization Block (NCD-SSB) via a second CC of a plurality of CCs within a first set of time-domain resources or a subset of time-domain resources within the first set for transmission to the UE. For example, 1512 may be performed by the transmitting component 1642.

[0159] At 1514, a network entity can prevent the transmission of non-cell-defined synchronization signal blocks (NCD-SSBs) outside the time-domain resources configured for cell-defined synchronization signal blocks (CD-SSBs) based on a command that enables conflict handling at the UE. For example, 1514 can be performed by avoidance component 1644.

[0160] At 1516, the network entity can communicate with the UE using half-duplex inter-band TDD CA via multiple CCs, including a first component carrier (CC) and a second CC. For example, 1516 can be performed by a receiving component 1640 and a transmitting component 1642.

[0161] At 1518, the network entity may output a non-cell-defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC and the second CC for transmission via the first CC corresponding to a reference cell or another cell. For example, 1518 may be performed by the transmission component 1642.

[0162] In some respects, the capability of half-duplex communication is associated with inter-band TDD CA.

[0163] In some respects, based on the command to enable conflict handling at the UE, the NCD-SSB is output for transmission within a first set of time-domain resources or within a subset of time-domain resources in the first set.

[0164] In some respects, the first CC corresponds to a reference cell, and each of the first one or more symbols is configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0165] In some respects, the first CC corresponds to another cell, wherein the second CC corresponds to a reference cell, and wherein the first one or more symbols of the second CC are configured as at least one of a semi-static downlink or a radio resource configuration (RRC) downlink.

[0166] Figure 16 Figure 1600 illustrates an example of a hardware implementation for device 1602. Device 1602 is a BS and includes a baseband unit 1604. Baseband unit 1604 can communicate with UE 104 via a cellular RF transceiver. Baseband unit 1604 may include computer-readable medium / memory. Baseband unit 1604 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by baseband unit 1604, causes baseband unit 1604 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by baseband unit 1604 when executing the software. Baseband unit 1604 further includes a receiving component 1630, a communication manager 1632, and a transmitting component 1634. Communication manager 1632 includes one or more of the illustrated components. Components within communication manager 1632 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1604. The baseband unit 1604 may be a network entity or a component of the BS102 / 180, and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or memory 376. In various examples, the device 1602 may be a chip, SoC, chipset, package, or device that may include: one or more modems (such as a Wi-Fi (IEEE 802.11) modem or a cellular modem such as a 3GPP 4G LTE or 5G compatible modem); one or more processors, processing blocks, or processing elements (collectively, “processors”); one or more radio components (collectively, “radio components”); and one or more memories or blocks of memory (collectively, “memory”).

[0167] The communication manager 1632 includes a receiving component 1640 configured to obtain from the user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); and to communicate with the UE via a plurality of CCs including a first component carrier (CC) and a second CC using half-duplex inter-band TDD CA, for example, as described in conjunction with 1502 and 1516.

[0168] The communication manager 1632 further includes a transmission component 1642 configured to output a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on capabilities supported by the UE; outputting signaling configuring the UE for dynamic active BWP handover between multiple bandwidth portions (BWPs) for transmission to the UE, wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SSB); outputting the cell-defined synchronization signal block (CD-SSB) via a first CC of multiple component carriers (CCs) for transmission to the UE, its The middle CD-SSB is output for transmission within a first set of time-domain resources; a non-cell-defined synchronization signal block (NCD-SSB) is output via a second CC of a plurality of CCs within the first set of time-domain resources or within a subset of time-domain resources in the first set for transmission to the UE; and a non-cell-defined synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC and the second CC is output for transmission via a first CC corresponding to a reference cell or another cell, for example, as described in conjunction with 1504, 1508, 1510, 1512, 1516 and 1518.

[0169] The communication manager 1632 further includes an avoidance component 1644 configured to avoid configuring the UE for unrestricted dynamic active bandwidth portion (BWP) handover based on a command to enable conflict handling at the UE; and to avoid configuring non-cell-defined synchronization signal blocks (NCD-SSBs) for transmission outside the time-domain resources configured for cell-defined synchronization signal blocks (CD-SSBs) based on a command to enable conflict handling at the UE, for example, as described in conjunction with 1506 and 1514.

[0170] The device may include execution Figure 15 The aforementioned flowchart contains additional components for each box in the algorithm's boxes. Therefore, each box in the aforementioned flowchart can be executed by a component, and the apparatus may include one or more of these components. These components may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by a processor configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0171] In one configuration, device 1602 (and specifically, baseband unit 1604) includes components for obtaining from a user equipment (UE) an indication of whether the UE can support half-duplex communication via time-division duplex (TDD) carrier aggregation (CA); components for outputting a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE; components for avoiding configuring the UE for unrestricted dynamic active bandwidth portion (BWP) handover based on the command enabling conflict handling at the UE; and components for outputting signaling configuring the UE for dynamic active BWP handover between multiple bandwidth portions (BWPs) for transmission to the UE, wherein each of the multiple BWPs includes a cell-defined synchronization signal block (CD-SS). B); a component for outputting a cell-defined synchronization signal block (CD-SSB) via a first CC of a plurality of component carriers (CCs) for transmission to a UE, wherein the CD-SSB is output for transmission within a first set of time-domain resources; a component for outputting a non-cell-defined synchronization signal block (NCD-SSB) via a second CC of a plurality of CCs for transmission to a UE within the first set of time-domain resources or within a subset of time-domain resources in the first set; a component for avoiding the configuration of non-cell-defined synchronization signal blocks (NCD-SSBs) for transmission outside the time-domain resources configured for cell-defined synchronization signal blocks (CD-SSBs) based on a command enabling conflict handling at the UE; a component for communicating with the UE using half-duplex inter-band TDD CA via a plurality of CCs including a first component carrier (CC) and a second CC; and a component for outputting a non-cell-defined synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC and the second CC for transmission via a first CC corresponding to a reference cell or another cell.

[0172] The aforementioned components may be one or more of the aforementioned components of the device 1602 configured to perform the functions described therein. As described above, the device 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned components may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions described therein.

[0173] Additional Notes

[0174] The component used for receiving or obtaining may include a receiver, such as Figure 3 The receiver processors 356 / 370 and / or antennas 320 / 352 of BS 102 / 180 and UE 104 illustrated herein. Components for transmitting or for output may include transmitters, such as... Figure 3The transmitting processors 316 / 368 and / or antennas 320 / 352 of BS 102 / 180 and UE 104 illustrated herein. Components for communication may include both components for transmitting (or outputting for transmitting) and components for receiving (or acquiring). Components for discarding, for monitoring, for switching, and for avoiding may include a processing system and memory, which may include one or more processors and one or more memories, such as… Figure 3 The controllers / processors 375 / 359 and memories 176 / 360 of the illustrated BS 102 / 180 and UE 104.

[0175] As used herein, a processor configured to perform or be operable to perform a plurality of actions, at least one processor, and / or one or more processors (alone or in combination) are intended to include at least two different processors capable of performing different subsets, overlapping subsets, or non-overlapping subsets of the plurality of actions, or a single processor capable of performing all of the plurality of actions. In a non-limiting example of a plurality of processors capable of performing different combinations of the plurality of actions, the description of a processor configured to perform or be operable to perform actions X, Y, and Z, at least one processor, and / or one or more processors may include at least a first processor configured to perform or be operable to perform a first subset of X, Y, and Z (e.g., performing X) and at least a second processor configured to perform or be operable to perform a second subset of X, Y, and Z (e.g., performing Y and Z). Alternatively, the first, second, and third processors may be configured to perform corresponding actions in actions X, Y, and Z, respectively. It should be understood that any combination of one or more processors may each be configured to perform or be operable to perform any one of the plurality of actions or any combination of the plurality of actions.

[0176] As used herein, a memory, at least one memory, and / or one or more memories (individually or in combination) configured to store or have thereon instructions executable by one or more processors for performing multiple actions are intended to include at least two different memories capable of storing different subsets, overlapping subsets, or non-overlapping subsets of instructions for performing the multiple actions, or a single memory capable of storing instructions for performing all of the multiple actions. In a non-limiting example of one or more memories (alone or in combination) capable of storing different subsets of instructions for performing different actions among the plurality of actions, the description of a memory configured or operable to store or thereon instructions for performing actions X, Y, and Z, at least one memory, and / or one or more memories may include at least a first memory configured or operable to store or thereon instructions for performing a first subset of X, Y, and Z (e.g., instructions for performing X), and at least a second memory configured or operable to store or thereon instructions for performing a second subset of X, Y, and Z (e.g., instructions for performing Y and Z). Alternatively, the first, second, and third memories may be configured to store or thereon a corresponding one of the first subset of instructions for performing X, the second subset of instructions for performing Y, and the third subset of instructions for performing Z. It should be understood that any combination of one or more memories may be configured or operable to store or have thereon any instruction or any combination of instructions executable by one or more processors to perform any of a plurality of actions or any combination of such actions. Furthermore, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute instructions to perform the plurality of actions. For example, in the above non-limiting example of different subsets of instructions for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, and at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first and second processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, three processors may access one of three different memories, each storing instructions for performing action X, Y, or Z, and the three processors may combine to execute the respective subsets of instructions to complete the execution of actions X, Y, and Z. Alternatively, a single processor may execute instructions stored in a single memory or distributed across multiple memories to complete the execution of actions X, Y, and Z.

[0177] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but this does not imply limitation to the given specific order or hierarchy.

[0178] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more” unless specifically stated otherwise. Terms such as “if,” “when,” and “at the same time as” should be interpreted as “in the circumstances of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be interpreted as a functional component unless the element is explicitly stated using the phrase “component for…”.

[0179] Example

[0180] The following embodiments are merely illustrative and may be combined with other implementations or aspects of the teachings described herein, but are not limited thereto.

[0181] Clause 1. A method for wireless communication at a device, the method comprising: outputting an indication of whether the device is capable of supporting half-duplex communication via time-division duplex (TDD) carrier aggregation (CA) for transmission; and obtaining a command configured to enable collision handling by the device, the command being based on capabilities supported by the device.

[0182] Clause 2. The method described in Clause 1, wherein the half-duplex communication capability is associated with inter-band TDD CA.

[0183] Clause 3. The method according to any one of Clauses 1 and 2 further includes: obtaining signaling to configure the apparatus for dynamic active BWP handover between a plurality of bandwidth portions (BWPs), wherein each of the plurality of BWPs includes a cell-defined synchronization signal block (CD-SSB).

[0184] Clause 4. The method according to any one of Clauses 1 to 3 further comprises: communicating with a plurality of cells via a plurality of component carriers (CCs) using half-duplex inter-band TDD CA; obtaining a cell-defined synchronization signal block (CD-SSB) via a first CC of the plurality of CCs within a first set of time-domain resources; and obtaining a non-cell-defined synchronization signal block (NCD-SSB) via a second CC of the plurality of CCs within the first set of time-domain resources or within a subset of time-domain resources within the first set.

[0185] Clause 5. The method described in Clause 4, wherein the NCD-SSB is obtained via the downlink bandwidth portion (BWP) of the second CC.

[0186] Clause 6. The method according to any one of Clauses 1 to 5, wherein the method further comprises: communicating with a plurality of cells via a plurality of CCs including a first component carrier (CC) and a second CC using half-duplex interband TDD CA, wherein the plurality of cells includes a reference cell and another cell; and obtaining a first non-cell defined synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC via the first CC associated with the reference cell or the other cell.

[0187] Clause 7. The method according to Clause 6, wherein the first CC is associated with the reference cell, and wherein the first one or more symbols are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0188] Clause 8. The method according to any one of Clauses 6 and 7, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell, and wherein the first one or more symbols of the second CC are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0189] Clause 9. The method according to any one of Clauses 1 to 8, wherein the method further comprises: communicating with a plurality of cells including a reference cell and another cell via a plurality of component carriers (CCs) using half-duplex inter-band TDD CA, wherein the plurality of CCs includes a first CC associated with the reference cell and a second CC associated with the other cell; obtaining a non-cell defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC via the first CC; and discarding at least a first symbol of the one or more symbols of the second CC based on at least one of the following: the NCD-SSB occupies the one or more symbols, or at least the first symbol is an uplink symbol.

[0190] Clause 10. The method according to any one of Clauses 1 to 9, wherein the method further comprises: communicating with a plurality of cells including a reference cell and another cell via a plurality of CCs including a first component carrier (CC) and a second CC using half-duplex inter-band TDD CA, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell; and discarding a non-cell defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC, wherein the NCD-SSB is discarded based on the one or more symbols of the second CC being configured as a semi-static uplink or a radio resource control (RRC) uplink.

[0191] Clause 11. The method according to Clause 10, wherein the NCD-SSB is further dropped based on the second CC being associated with the reference cell and the reference cell having a higher priority than the other cell.

[0192] Clause 12. The method according to any one of Clauses 1 to 11, wherein the method further comprises: communicating with a plurality of cells via a plurality of component carriers (CCs) using half-duplex inter-band TDD CA; and outputting an indication that the apparatus is configured for non-legacy bandwidth portion (BWP) handover delay for transmission in response to the command to enable conflict handling.

[0193] Clause 13. The method according to Clause 12, wherein the one or more processors are further configured individually or in combination to cause the device to: monitor a first bandwidth portion (BWP) of one or more of the plurality of CCs; and switch from the first BWP to a second BWP within the non-legacy BWP switching delay.

[0194] Clause 14. The method according to any one of Clauses 12 and 13, wherein the non-legacy BWP handover delay has a longer duration relative to the legacy handover delay.

[0195] Clause 15. A method for wireless communication at a device, the method comprising: obtaining from a user equipment (UE) an indication of whether the UE is capable of supporting half-duplex communication via time division duplex (TDD) carrier aggregation (CA); and outputting a command configured to enable conflict handling at the UE for transmission to the UE, the command being output based on the capabilities supported by the UE.

[0196] Clause 16. The method described in Clause 15, wherein the half-duplex communication capability is associated with inter-band TDD CA.

[0197] Clause 17. The method according to any one of Clauses 15 and 16, wherein the method further comprises: avoiding configuring the UE for unrestricted dynamic active bandwidth portion (BWP) handover based on the command enabling conflict handling at the UE.

[0198] Clause 18. The method according to any one of Clauses 15 to 17, wherein the method further comprises: outputting signaling configuring the UE for dynamic active BWP handover between a plurality of bandwidth portions (BWPs) for transmission to the UE, wherein each of the plurality of BWPs includes a cell-defined synchronization signal block (CD-SSB).

[0199] Clause 19. The method according to any one of Clauses 15 to 18, wherein the method further comprises: outputting a cell-defined synchronization signal block (CD-SSB) via a first CC of a plurality of component carriers (CCs) for transmission to the UE, wherein the CD-SSB is output for transmission within a first set of time-domain resources; and outputting a non-cell-defined synchronization signal block (NCD-SSB) via a second CC of the plurality of CCs for transmission to the UE within the first set of time-domain resources or within a subset of time-domain resources within the first set.

[0200] Clause 20. The method according to Clause 19, wherein the NCD-SSB is output for transmission within the first set of time-domain resources or within the subset of time-domain resources in the first set, based on the command enabling conflict handling at the UE.

[0201] Clause 21. The method according to any one of Clauses 15 to 20, wherein the method further comprises: avoiding the configuration of non-cell-defined synchronization signal blocks (NCD-SSBs) to be transmitted outside the time-domain resources configured for cell-defined synchronization signal blocks (CD-SSBs) based on the command enabling conflict handling at the UE.

[0202] Clause 22. The method according to any one of Clauses 15 to 21, wherein the method further comprises: communicating with the UE via a plurality of CCs including a first component carrier (CC) and a second CC using half-duplex interband TDD CA; and outputting a non-cell defined synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC and the second CC for transmission via the first CC corresponding to a reference cell or another cell.

[0203] Clause 23. The method according to Clause 22, wherein the first CC corresponds to the reference cell, and wherein each of the first one or more symbols is configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

[0204] Clause 24. The method according to any one of Clauses 22 and 23, wherein the first CC corresponds to the other cell, wherein the second CC corresponds to the reference cell, and wherein the first one or more symbols of the second CC are configured as at least one of a semi-static downlink or a radio resource configuration (RRC) downlink.

[0205] Clause 25. A user equipment (UE) comprising: a transceiver; one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the UE to perform a method according to any one of Examples 1 to 14, wherein the transceiver is configured to: transmit the indication of whether the UE is capable of supporting half-duplex communication; and receive the command configured to enable conflict resolution by the UE.

[0206] Clause 26. A network entity comprising: a transceiver; one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the network entity to perform a method according to any one of Examples 15 to 24, wherein the transceiver is configured to: receive the indication of whether the UE is capable of supporting half-duplex communication; and send the command configured to enable conflict handling at the UE.

[0207] Clause 27. An apparatus for wireless communication, the apparatus comprising: a component for performing the method according to any one of Examples 1 to 14.

[0208] Clause 28. An apparatus for wireless communication, the apparatus comprising: a component for performing the method according to any one of Examples 15 to 24.

[0209] Clause 29. A non-transitory computer-readable medium comprising: instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 1 to 14.

[0210] Clause 30. A non-transitory computer-readable medium comprising: instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 15 to 24.

[0211] Clause 31. An apparatus for wireless communication, the apparatus comprising: one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the apparatus to perform the method according to any one of Examples 1 to 14.

[0212] Clause 32. An apparatus for wireless communication, the apparatus comprising: one or more memories having instructions individually or in combination; and one or more processors configured individually or in combination to execute the instructions and cause the apparatus to perform the method according to any one of Examples 15 to 24.

Claims

1. An apparatus for wireless communication, the apparatus comprising: one or more memories, individually or in combination, having instructions; and one or more processors, individually or in combination, configured to execute the instructions and cause the apparatus to: output an indication of whether the apparatus is capable of supporting half duplex communication via time division duplex (TDD) carrier aggregation (CA) for transmission; and obtain a command configured to enable collision handling by the apparatus, the command based on a capability supported by the apparatus.

2. The apparatus of claim 1, wherein the capability of half duplex communication is associated with inter-band TDD CA.

3. The apparatus of claim 1, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: obtain signaling configuring the apparatus for dynamic active bandwidth part (BWP) switching between a plurality of BWPs, wherein each BWP of the plurality of BWPs comprises a cell-defining synchronization signal block (CD-SSB).

4. The apparatus of claim 1, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: communicate with a plurality of cells using half duplex inter-band TDD CA via a plurality of component carriers (CCs); obtain a cell-defining synchronization signal block (CD-SSB) via a first CC of the plurality of CCs within a first set of time domain resources; and obtain a non-cell-defining synchronization signal block (NCD-SSB) via a second CC of the plurality of CCs within the first set of time domain resources or within a subset of time domain resources within the first set.

5. The apparatus of claim 4, wherein the NCD-SSB is obtained via a downlink bandwidth part (BWP) of the second CC.

6. The apparatus of claim 1, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: communicate with a plurality of cells using half duplex inter-band TDD CA via a plurality of component carriers (CCs), wherein the plurality of cells comprises a reference cell and another cell; and obtain a non-cell-defining synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC via the first CC associated with the reference cell or the other cell.

7. The apparatus of claim 6, wherein the first CC is associated with the reference cell, and wherein the first one or more symbols are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

8. The apparatus of claim 6, wherein the first CC is associated with the other cell and the second CC is associated with the reference cell, and wherein the first one or more symbols of the second CC are configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

9. The apparatus of claim 1, wherein the one or more processors are further configured to, individually or collectively, cause the apparatus to: communicate with a plurality of cells including a reference cell and another cell using half duplex inter-band TDD CA via a plurality of component carriers (CCs), wherein the plurality of CCs includes a first CC associated with the reference cell and a second CC associated with the another cell; obtain, via the first CC, a non-cell defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC; and drop at least a first symbol of the one or more symbols of the second CC based on at least one of: the NCD-SSB occupying the one or more symbols, or at least the first symbol being an uplink symbol.

10. The apparatus of claim 1, wherein the one or more processors are further configured to, individually or collectively, cause the apparatus to: communicate with a plurality of cells including a reference cell and another cell using half duplex inter-band TDD CA via a plurality of component carriers (CCs), wherein a first CC is associated with the another cell and a second CC is associated with the reference cell; and drop a non-cell defined synchronization signal block (NCD-SSB) occupying one or more symbols of the first CC, wherein the NCD-SSB is dropped based on the one or more symbols of the second CC being configured as a semi-static uplink or a radio resource control (RRC) uplink.

11. The apparatus of claim 10, wherein the NCD-SSB is further dropped based on the second CC being associated with the reference cell and the reference cell having a higher priority than the another cell.

12. The apparatus of claim 1, wherein the one or more processors are further configured to, individually or collectively, cause the apparatus to: communicate with a plurality of cells using half duplex inter-band TDD CA via a plurality of component carriers (CCs); and output an indication that the apparatus is configured for a non-legacy bandwidth part (BWP) switching delay for transmitting in response to the command to enable collision handling.

13. The apparatus of claim 12, wherein the one or more processors are further configured to, individually or collectively, cause the apparatus to: monitor a first bandwidth part (BWP) of one or more CCs of the plurality of CCs; and switch from the first BWP to a second BWP within the non-legacy BWP switching delay.

14. The apparatus of claim 12, wherein the non-legacy BWP switching delay has a longer duration relative to a legacy switching delay.

15. The apparatus of claim 1, further comprising a transceiver configured to: transmit the indication of whether the apparatus is capable of supporting half duplex communication via TDD CA; and transmit the indication of whether the apparatus is capable of supporting half duplex communication via TDD CA; and receive the command configured to enable conflict handling by the apparatus, wherein the apparatus is configured as a user equipment (UE).

16. An apparatus for wireless communication, the apparatus comprising: one or more memories, individually or in combination, having instructions; and one or more processors, individually or in combination, configured to execute the instructions and cause the apparatus to: obtain, from a user equipment (UE), an indication of whether the UE is capable of supporting half duplex communication via time division duplex (TDD) carrier aggregation (CA); and output, for transmission to the UE, a command configured to enable conflict handling at the UE, the command being output based on a capability supported by the UE.

17. The apparatus of claim 16, wherein the capability of half duplex communication is associated with inter-band TDD CA.

18. The apparatus of claim 16, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: avoid configuring the UE for unrestricted dynamic active bandwidth part (BWP) switching based on the command to enable conflict handling at the UE.

19. The apparatus of claim 16, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: output, for transmission to the UE, signaling to configure the UE for dynamic active bandwidth part (BWP) switching between a plurality of BWPs, wherein each BWP of the plurality of BWPs comprises a cell-defined synchronization signal block (CD-SSB).

20. The apparatus of claim 16, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: output, for transmission to the UE, a cell-defined synchronization signal block (CD-SSB) via a first component carrier (CC) of a plurality of CCs, wherein the CD-SSB is output for transmission within a first set of time domain resources; and output, for transmission to the UE, a non-cell-defined synchronization signal block (NCD-SSB) via a second CC of the plurality of CCs within the first set of time domain resources or within a subset of time domain resources of the first set.

21. The apparatus of claim 20, wherein the NCD-SSB is output for transmission within the first set of time domain resources or within the subset of time domain resources of the first set based on the command to enable conflict handling at the UE.

22. The apparatus of claim 16, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: avoid configuring a non-cell-defined synchronization signal block (NCD-SSB) for transmission outside of time domain resources configured for a cell-defined synchronization signal block (CD-SSB) based on the command to enable conflict handling at the UE.

23. The apparatus of claim 16, wherein the one or more processors, individually or in combination, are further configured to cause the apparatus to: communicate with the UE using half duplex inter-band TDD CA via a plurality of component carriers (CCs) including a first CC and a second CC; and output a non-cell defined synchronization signal block (NCD-SSB) occupying a first one or more symbols of the first CC and the second CC for transmission via the first CC corresponding to a reference cell or another cell.

24. The apparatus of claim 23, wherein the first CC corresponds to the reference cell, and wherein each symbol of the first one or more symbols is configured as at least one of a semi-static downlink symbol or a radio resource configuration (RRC) downlink symbol.

25. The apparatus of claim 23, wherein the first CC corresponds to the other cell, wherein the second CC corresponds to the reference cell, and wherein the first one or more symbols of the second CC are configured as at least one of a semi-static downlink or a radio resource configuration (RRC) downlink.

26. The apparatus of claim 16, further comprising a transceiver configured to: receive the indication of whether the UE is capable of supporting half duplex communication via TDD CA; and transmit the command configured to enable collision handling at the UE, wherein the apparatus is configured as a network entity.

27. A method for wireless communication at a wireless node, comprising: outputting, for transmission, an indication of whether the wireless node is capable of supporting half duplex communication via time division duplex (TDD) carrier aggregation (CA); and obtaining a command configured to enable collision handling by the wireless node, the command based on a capability supported by the wireless node. ​

Images