Conflict handling based on symbol types configured by SBFD

Abstract

Certain aspects of this disclosure provide a method for wireless communication at a user equipment (UE), the method generally comprising: obtaining a first signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; obtaining a second signaling indicating that directional collision handling is enabled for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC; and communicating with one or more serving cells based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Patent Application No. 18 / 426,121, filed January 29, 2024, which has been assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety, as fully set forth below and for all applicable purposes. Technical Field

[0003] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for subband full-duplex (SBFD) wireless communication.

[0004] Related technical descriptions

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0006] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0007] One aspect provides a method for wireless communication at a user equipment (UE). The method includes: obtaining a first signaling indicating that at least one symbol is configured as a sub-band full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; obtaining a second signaling indicating that directional collision handling is enabled for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC; and communicating with the one or more serving cells based on the symbol direction of the at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

[0008] On the other hand, a method for wireless communication at a user equipment (UE) is provided. The method includes: outputting a first signaling to a network entity, the first signaling instructing the UE to support sub-band full-duplex (SBFD) operation during a transmission time interval (TTI) having a designated downlink or flexible transmission direction; obtaining a second signaling from the network entity, the second signaling indicating a TTI for SBFD operation, wherein the TTI has a designated downlink or flexible transmission direction; and communicating with the network entity during the TTI according to the indicated capability.

[0009] On the other hand, a method for wireless communication at a network entity is provided. The method includes: outputting a first signaling indicating that at least one symbol is configured as a sub-band full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; outputting a second signaling indicating that directional collision handling is enabled for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC; and communicating with at least one user equipment (UE) based on the symbol direction of the at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

[0010] On the other hand, a method for wireless communication at a network entity is provided. The method includes: obtaining a first signaling indicating that a user equipment (UE) supports sub-band full-duplex (SBFD) operation during a transmission time interval (TTI) having a designated downlink or flexible transmission direction; outputting a second signaling indicating a TTI for SBFD operation, wherein the TTI has a designated downlink or flexible transmission direction; and communicating with the UE during the TTI according to the indicated capability.

[0011] Other aspects provide: an apparatus capable of operating to, being configured to, or otherwise adapted to perform one or more of the foregoing methods and / or those methods described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of the apparatus (e.g., directly, indirectly, after preprocessing, or without preprocessing), cause the apparatus to perform the foregoing methods and those methods described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising: code for performing the foregoing methods and those methods described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those methods described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0012] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0013] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0014] Figure 1 An example wireless communication network is depicted.

[0015] Figure 2 An example decomposed base station architecture is described.

[0016] Figure 3 Various aspects of the example base station and example user equipment are described.

[0017] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0018] Figures 5 to 8 Different use cases for full-duplex (FD) communication are described.

[0019] Figure 9A , Figure 9B and Figure 9C An example of the FD operation at gNodeB (gNB) is described.

[0020] Figure 10A and Figure 10B An example subband full-duplex (SBFD) time slot configuration is described.

[0021] Figure 11A and Figure 11B A sample SBFD slot configuration is depicted.

[0022] Figure 12 An example SBFD slot configuration for carrier aggregation (CA) is described.

[0023] Figure 13 A call flow diagram illustrating a scenario within a cell according to certain aspects of this disclosure is depicted.

[0024] Figure 14 A method for wireless communication is described.

[0025] Figure 15 A method for wireless communication is described.

[0026] Figure 16 A method for wireless communication is described.

[0027] Figure 17 A method for wireless communication is described.

[0028] Figure 18 Various aspects of the example communication device are described. Detailed Implementation

[0029] Various aspects of this disclosure relate to wireless communication, and more specifically to techniques for subband full-duplex (SBFD) wireless communication.

[0030] Half-duplex (HD) communication typically refers to a communication mode in which devices transmit or receive through a single communication channel but not simultaneously. In systems utilizing time-division duplex (TDD) carriers, different transmission time intervals (e.g., symbols or time slots) can be configured as uplink, downlink, or flexible (which can be dynamically indicated as uplink or downlink via a time slot format indicator (SFI)).

[0031] Full-duplex (FD) communication typically refers to a communication mode in which signals can be transmitted and received simultaneously through a single communication channel. In FD mode, simultaneous transmission between radio nodes (such as User Equipment (UE) and Base Station (BS)) is possible. Subband Full-Duplex (SBFD) typically refers to a mode in which a Time Division Duplex (TDD) carrier is split into uplink subbands and downlink subbands to achieve simultaneous transmission and reception in the same time slot consisting of multiple symbols (on different subbands).

[0032] In systems utilizing Time Division Duplex (TDD), collisions can occur where a Transmission Time Interval (TTI) (such as a time slot or symbol) is configured for one direction, while transmissions are scheduled in the opposite direction. For example, a collision might occur when a downlink transmission is scheduled on a symbol configured as an uplink symbol, or vice versa.

[0033] Some systems can utilize a configuration parameter (directionalCollisionHandling-r16) to enable handling of such collisions. However, in such systems, this configuration parameter is typically a per-serving cell parameter applicable only within the same frequency range and cell group. In other words, only cells configured with directionalCollisionHandling-r16 within the same cell group and frequency range are considered to determine the corresponding behavior for each such collision scenario.

[0034] Unfortunately, collision handling behavior may not be adequately defined in systems utilizing carrier aggregation (CA) where different cells are configured on different component carriers (CCs). For example, collision handling may not be adequately defined for SBFD operation, in which both the time and frequency positions of the subband used for SBFD operation are known to the SBFD-aware UE.

[0035] However, aspects of this disclosure can provide rules for collision handling in SBFD operations, such as SBFD operations based on CA. The various rules provided herein help define mechanisms for collision handling between downlink reception in the downlink subband CC and UL transmission in the UL subband CC within an SBFD symbol. This behavior can result in improved spectral efficiency and enhanced system performance.

[0036] An introduction to wireless communication networks

[0037] The techniques and methods described herein can be used in a variety of wireless communication networks. While aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0038] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0039] Generally, wireless communication network 100 includes various network entities (optionally, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, various functions of the network and various devices associated with and interacting with the network can be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects, such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects, such as satellite 140 and aircraft 145, which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0040] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0041] Figure 1 Various example UE 104s are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio 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, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, wireless communication devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0042] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., sending or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0043] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each BS in BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0044] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0045] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G 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). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0046] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0047] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0048] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1 The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0049] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0050] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The 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), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0051] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may 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 connectivity management.

[0052] Generally, user Internet Protocol (IP) packets are transmitted 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 services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0053] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to BS 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0054] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196.

[0055] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0056] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides UE IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0057] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0058] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0059] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via the transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0060] In some aspects, CU 210 can host one or more higher-level control functions. Such 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 CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling transmission as needed.

[0061] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 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 230 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 230 or with control functions hosted by CU 210.

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

[0063] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 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 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 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 210, DU 230, RU 240, and near-RT RIC 225. In some implementations, SMO framework 205 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, SMO framework 205 can communicate directly with one or more RU 240s via the O1 interface. SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of SMO framework 205.

[0064] The non-RT RIC 215 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 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

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

[0066] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0067] Generally, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a to 334t (collectively referred to as 334), transceivers 332a to 332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various wireless communication-related functions described herein.

[0068] Generally, UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a to 352r (collectively referred to as 352), transceivers 354a to 354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 362) and the wireless reception of data (e.g., provision to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various wireless communication-related functions described herein.

[0069] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. The control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical HARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Shared PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0070] The transmitter processor 320 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0071] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0072] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0073] The MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a-354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes the detected symbols (e.g., demodulation, deinterleaving, and decoding), provides the decoded data of UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0074] Regarding the example uplink transmission, UE 104 further includes a transmission processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmission processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmission processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0075] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected by MIMO detector 336 where applicable, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 339 and the decoded control information to controller / processor 340.

[0076] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0077] Scheduler 344 can schedule UE to send data on the downlink and / or uplink.

[0078] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0079] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0080] In some respects, one or more processors may be configured to perform various operations (such as those associated with the methods described herein) and respectively send (output) data to another interface configured to send data or receive (obtain) data from another interface configured to receive data.

[0081] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0082] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0083] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0084] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0085] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time 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). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0086] In some respects, the number of time slots within a subframe is based on the time slot configuration and parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 6 allow 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 time slots per subframe, respectively. Therefore, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2µ time slots per subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. Therefore, the parameter set... It has a subcarrier spacing of 15 kHz and a parameter set It has a subcarrier spacing of 960 kHz. The symbol length / duration is negatively correlated with the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides slot configuration 0 with 14 symbols per slot and parameter set with 4 slots per subframe. Example: The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0087] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0088] like Figure 4A As illustrated, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0089] Figure 4B 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, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0090] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0091] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0092] 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 DMRS. 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. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0093] like Figure 4CAs illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0094] Figure 4D 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 HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0095] Overview of Full-Duplex (FD) Systems

[0096] Full-duplex (FD) allows simultaneous transmission between nodes (e.g., user equipment (UE) and base station (BS)). In a half-duplex (HD) system, communication flows in one direction at a time.

[0097] There are various motivations for utilizing FD communication, such as for simultaneous uplink (UL) / downlink (DL) transmission in frequency range 2 (FR2). In some cases, FD capability enables flexible time division duplex (TDD) capability and can be present at the base station (BS) or the UE, or both. For example, at the UE, UL transmission can be carried out from one antenna panel (e.g., one or more antenna panels), and DL reception can be performed at another antenna panel. In another example, at the gNodeB (gNB), UL transmission can originate from one panel, and DL reception can be performed at another panel.

[0098] FD capability can depend on beam splitting (e.g., self-interference between DL and UL, clutter echoes, etc.). FD capability can mean that the UE or gNB can use frequency division multiplexing (FDM) or space division multiplexing (SDM) on time slots that are conventionally reserved for UL-only or DL-only time slots (or flexible time slots that can be dynamically designated as UL or DL).

[0099] Potential benefits of FD communication include reduced latency (e.g., the possibility of receiving DL signals in time slots that would otherwise be considered UL-only time slots, resulting in latency savings), enhanced coverage, improved spectrum efficiency (e.g., per cell and / or per UE), and / or more efficient resource utilization overall.

[0100] Figures 5 to 7 An example use case for FD communication is shown. Figure 8 This summarizes some of the possible characteristics of these use cases.

[0101] Figure 5 Figure 500 illustrates a first use case for FD communication (e.g., use case 1). As illustrated, a UE 104 simultaneously communicates with a first transmitter-receiver point (TRP 1) on the DL and transmits to a second TRP on the UL. For this use case, FD is disabled at the gNB (i.e., TRP 1, TRP 2) and enabled at the UE.

[0102] Figure 6 Figure 600 illustrates a second use case (e.g., use case 2) for FD communication. As illustrated, a gNB102 simultaneously communicates with a first UE (UE 1) on the DL and with a second UE (UE 2) on the UL. For this use case, FD is enabled at the gNB and disabled at the UE. The use case where FD is enabled at the gNB and disabled at the UE is also suitable for Integrated Access and Backhaul (IAB) applications (e.g., such as...). Figure 8 (as exemplified in table 800).

[0103] Figure 7 Figure 700 illustrates a third use case (e.g., use case 3) for FD communication. As illustrated, UE 104 communicates simultaneously with gNB 102, thereby receiving on DL and transmitting on UL. For this use case, FD is enabled at both gNB and UE.

[0104] Overview of Subband Full-Duplex (SBFD)

[0105] Compared to older communication standards, the spectrum options for 5G New Radio (NR) have been significantly expanded. For example, the Frequency Range 2 (FR2) band has been extended from approximately 24 GHz to 60 GHz. Because wavelengths decrease with increasing frequency, the FR2 band is referred to as a millimeter-wave band due to its relatively short wavelength. Given this relatively short wavelength, radio frequency (RF) signals transmitted in the FR2 band behave somewhat like visible light. Therefore, like light, millimeter-wave signals are easily blocked by buildings and other obstacles. Furthermore, the received power per unit area of ​​the antenna element decreases with increasing frequency. For example, the width and length of a patch antenna element are typically a portion of the operating wavelength (e.g., half the wavelength). As the wavelength decreases (and therefore the size of the antenna element decreases), the signal energy received at the corresponding antenna element decreases. Due to the problems of blockage and reduced received signal strength, millimeter-wave cellular networks will typically require a relatively large number of base stations (BSs). Cellular providers must typically lease land for BSs, making widespread coverage of millimeter-wave cellular networks potentially very expensive.

[0106] Compared to the challenges faced by FR2, the electromagnetic characteristics of radio wave propagation in the sub-6 GHz band are more adaptable. For example, the 5G NR Frequency Range 1 (FR1) band extends from approximately 0.4 GHz to 7 GHz. At these lower frequencies, transmitted RF signals tend to refract around obstacles such as buildings, thus reducing shielding issues. Furthermore, the larger size of each antenna element means that FR1 antenna elements intercept more signal energy compared to FR2 antenna elements. Therefore, as demonstrated by older networks, 5G NR cellular networks operating in the FR1 band will not require excessive BS (Bottom Band). Given the advantageous characteristics of lower frequency bands, the sub-6 GHz band is often referred to as the "shoreband" due to its desirability.

[0107] One problem with operating in the sub-6 GHz band is the very limited available bandwidth. Therefore, the Federal Communications Commission (FCC) regulates radio waves and auctions off the limited bandwidth in the FR1 band. Given this limited bandwidth, achieving the high data rates that are more easily attainable in the FR2 band is challenging for cellular providers. To address these challenges, the Sub-Band Full-Duplex (SBFD) network architecture has been developed, which is highly advantageous because it provides users with the high data rates that would otherwise require the FR2 band. The SBFD network architecture described in this paper provides high data rates in the FR1 band and reduces costs due to the fewer base stations (BSs) per given coverage area achievable in the FR1 band compared to the FR2 band.

[0108] Typically, each millisecond (ms) subframe can consist of one or more adjacent time slots. For example, a subframe may consist of four time slots. In a four-time-slot structure, the first two time slots can be downlink (DL) time slots, while the last of the four time slots is an uplink (UL) time slot. The third time slot is a special time slot in which some symbols can be used for UL transmission, while others can be used for DL ​​transmission. Thus, the resulting UL and DL traffic is time-division duplex (TDD), as arranged by the dedicated time slot and as arranged by symbol assignment in the special time slot. Since the UL has only a single dedicated time slot, UL communication may suffer excessive latency due to the user equipment (UE) being restricted to transmission within a single dedicated UL time slot and the resource allocation within the special time slot. The resulting latency can be problematic, especially for low-latency applications such as vehicle-to-vehicle communication, because only one dedicated UL time slot exists in a repeating four-time-slot structure. Furthermore, the energy used for UL communication is limited by the single dedicated time slot for that UL communication.

[0109] To reduce uplink latency and increase power available for UL transmission, SBFD mode can be implemented. SBFD mode is a duplex mode where a TDD carrier is split into subbands to enable simultaneous transmission and reception in the same time slot. For example, in SBFD mode, some time slots are modified to SBFD time slots to support frequency duplexing for simultaneous UL and DL transmissions. Some time slots can remain as legacy TDD time slots, where one time slot is still dedicated to DL and another to UL. In an example four-slot configuration, in SBFD mode, the second and third time slots can be SBFD time slots modified to support frequency duplexing for simultaneous UL and DL transmissions. The first and fourth time slots can remain as legacy TDD time slots, such that the first time slot remains dedicated to DL and the fourth to UL. In other examples, any time slot can be used in SBFD mode.

[0110] In the sub-6 GHz spectrum, if a device participates in simultaneous UL and DL transmissions, the relatively limited spacing between antennas on the device will result in significant self-interference. In some cases, frequency duplexing in the SBFD time slot can be implemented by the BS transceiver.

[0111] For example, Figure 9A Figure 900 depicts full-duplex (FD) operation at gNodeB (gNB) 102. The antenna system for the gNB is subdivided into a first antenna array, which is separated from the second antenna array by an insulating distance (e.g., 10 cm to 30 cm). Figure 9BAs illustrated, during SBFD operation, one antenna array (e.g., transmitting to a first UE (UE1)) is transmitting, while another antenna array is receiving (e.g., from a second UE (UE2)). Figure 9C As illustrated, CLI may occur in both DL MU-MIMO and UL MU-MIMO. In DL MU-MIMO, DL transmissions from UE1 may potentially interfere with reception by UE2. In UL MU-MIMO, UL transmissions from UE1 may potentially interfere with UL transmissions from UE2. In FD scenarios, in addition to CLI, UEs may also experience self-interference and / or clutter.

[0112] Self-interference issues are partially addressed through physical separation between the antenna arrays of the gNB. Conductive shielding between the antenna arrays of the gNB can also be implemented to provide additional isolation. However, it should be understood that if the device implements sufficient self-interference cancellation, the device (or more generally, the UE) can also implement frequency duplex. In other cases, however, the UE may be limited to half-duplex (HD) transmission, such that the UE's antenna array is entirely dedicated to either transmitting or receiving only in the corresponding time slot.

[0113] exist Figure 10A and Figure 10B The example SBFD time slot is depicted. For example, Figure 10A The SBFD slot 1000 is depicted, and Figure 10B SBFD slot 1010 is depicted. It should be noted that the UL and DL in SBFD slots 1000 and 1010 cannot occupy the entire frequency resource range (e.g., frequency band) used for these SBFD slots.

[0114] like Figure 10A As depicted, UL occupies the center subband 1004 in the frequency band used for SBFD time slot 1000, while DL occupies the upper and lower subbands, as shown at 1002. Figure 10B In the example, SBFD slot 1010 includes only one DL subband 1002.

[0115] In some cases, subbands may be separated by guard bands. The DL also occupies the upper subband within the band and extends from the maximum frequency used for the UL center subband to the maximum frequency used for the band. In one example, the UL center subband may be symmetrical about the center frequency used for SBFD slot 1000. In such examples, the bandwidths of the DL upper and lower subbands will be equal. However, in other examples, the bandwidth of the DL lower subband may differ from that of the DL upper subband. In some examples, the DL upper and lower subbands may each have a bandwidth that can vary to 10MHz, 20MHz, 30MHz, or 40MHz depending on the DL data rate.

[0116] The use of SBFD time slots is advantageous in minimizing or reducing UE-UE interference and transmit-receive self-interference at the BS. In some cases, the use of SBFD time slots can also enhance system capacity, improve resource utilization and spectrum efficiency (e.g., by enabling flexible and dynamic UL / DL resource adaptation in a robust manner according to UL / DL services).

[0117] In some cases, SBFD operations can be enabled in symbols that are configured as flexible in TDD-UL-DL-ConfigCommon. For example, for SBFD operations in symbols that are configured as flexible in TDD-UL-DL-ConfigCommon, various options can be considered for SBFD-aware UEs.

[0118] refer to Figure 11A According to the first option, UL transmission may be permitted within the UL subband 1106 in the symbol, while UL transmission may be disallowed (e.g., prohibited) outside the UL subband 1106. The frequency position of the DL subband 1104 may be known to the SBFD-aware UE. Therefore, DL reception within the DL subband 1104 in the symbol may be permitted. Whether DL reception outside the DL subband may also be considered is also debatable.

[0119] refer to Figure 11B According to the second option, UL transmission within UL subband 1106 can be permitted in the symbol. From the gNB's perspective, RBs outside UL subband 1106 (within subband 1110) can be used as UL or DL ​​in the symbol (excluding the guard band if one is used), and all those RBs have the same transmission direction. Various types of SBFD-aware UE behavior can be considered, as well as whether signaling for guard band locations should exist, and whether the symbol can be converted to a DL-only symbol. The frequency location of the DL subband can be known to the SBFD-aware UE, allowing DL reception within the DL subband in the symbol.

[0120] In the notation for the two options described above, UL transmission can be within the active UL BWP, and DL reception can be within the active DL BWP. For all RBs outside the UL subband, the UE cannot use a single RB for both DL and UL simultaneously.

[0121] In some cases, SBFD operation for the UE at the gNB can be implemented under various assumptions. These assumptions may include, for example, that the SBFD operation is within a TDD carrier; that the SBFD scheme is within a single configured DL and ULBWP pair with aligned center frequencies; and that at most one UL subband can be configured for the SBFD operation within the SBFD symbols of the TDD carrier. In some cases, for a UE in the RRC_CONNECTED state, both the time and frequency positions of the subband used for the SBFD operation may be known to the SBFD-aware UE.

[0122] Various aspects of this disclosure can define certain UE behaviors of an SBFD-aware UE based on the time and frequency positions of the subband used for SBFD operation. In such cases, non-SBFD-aware UEs (including legacy UEs) and SBFD-aware UEs can coexist with SBFD operation in the cell at the gNB side. In addition to indicating the time and frequency positions of the SBFD subband to the UE, UE transmission, reception, and measurement behaviors and procedures in SBFD symbols and / or non-SBFD symbols can also be proposed.

[0123] All aspects related to conflict resolution against SBFD

[0124] Various aspects of this disclosure relate to wireless communications, and more specifically to techniques for handling directional collisions in subband full-duplex (SBFD) wireless communications.

[0125] As noted above, in systems utilizing Time Division Duplex (TDD), collisions can occur where a Transmission Time Interval (TTI) (such as a time slot or symbol) is configured for one direction, while transmissions are scheduled in the opposite direction. For example, a collision may occur when a downlink transmission is scheduled on a symbol configured as an uplink symbol, or vice versa.

[0126] Unfortunately, collision handling behavior may not be adequately defined in systems utilizing carrier aggregation (CA) where different cells are configured on different component carriers (CCs). For example, collision handling may not be adequately defined for SBFD operation, in which both the time and frequency positions of the subband used for SBFD operation are known to the SBFD-aware UE.

[0127] However, aspects of this disclosure can provide rules for collision handling in SBFD operations, such as SBFD operations based on CA. The various rules provided herein help define mechanisms for collision handling between downlink reception in the downlink subband CC and UL transmission in the UL subband CC within an SBFD symbol. This behavior can result in improved spectral efficiency and enhanced system performance.

[0128] The mechanisms proposed in this paper can be used in scenarios where CA-based SBFD operation is configured (e.g., for the FR2 band). These mechanisms propose rules for collision handling between DL reception in the DL subband CC and UL transmission in the UL subband CC within an SBFD symbol. These mechanisms effectively enhance the directional collision handling rules to support CA-based SBFD operation.

[0129] The technologies proposed in this article can be referenced. Figure 13 To understand this, refer to the call flowchart 1300. In some aspects, Figure 13 The UE shown can be about Figure 1 and Figure 3 Examples of UE 104 depicted and described. Similarly, Figure 13 The network entities shown can be about Figure 1 and Figure 3 The BS 102 (e.g., gNB) depicted and described or related to Figure 2 Examples of decomposed base stations depicted and described.

[0130] As illustrated at location 1302, the serving cell may send signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC.

[0131] As illustrated at location 1304, the serving cell may send a second signaling instruction to enable directed collision handling for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC.

[0132] As illustrated at 1306, the UE can then communicate with one or more serving cells based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

[0133] The rules proposed in this paper can consider using semi-statically configured SBFD symbols to determine symbol direction definitions. In previous (legacy) systems, these semi-statically configured SBFD symbols were originally downlink (D) symbols or flexible (F) symbols. Such rules can consider using CA-based SBFD operations, where uplink transmissions can be performed in uplink subband component carriers (UL SB CCs), while downlink transmissions can be performed in one or more downlink subband component carriers (DL SB CCs).

[0134] For UEs configured with multiple serving cells and with collision handling enabled (e.g., for a set of serving cells in a configured set of serving cells, the UE has directionalCollisionHandling-r16 = 'enabled'), the following rules can be used to determine the symbol direction for these cases of gNB SBFD. The UE may also indicate support for the half-DuplexTDD-CA-SameSCS-r16 capability and may not be configured to monitor the PDCCH to detect DCI format 2_0 on any of the multiple serving cells. In such cases, the UE may determine the reference cell for the symbol (e.g., to be used as a reference for direction determination purposes) as the active cell with the smallest cell index among the configured multiple serving cells (e.g., if the UE cannot simultaneously transmit and receive in multiple serving cells as indicated by simultaneousRxTxInterBandCA) or separately as the active cell with the smallest cell index in each frequency band (if the UE can simultaneously transmit and receive by simultaneousRxTxInterBandCA for the configured multiple serving cells).

[0135] The direction can be determined as: 1) downlink or uplink, as indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; 2) uplink, where the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH or PRACH on the symbol; or downlink, where the symbol is flexible and the UE is configured to receive PDCCH, PDSCH or CSI-RS on the symbol.

[0136] According to certain aspects of this disclosure, the symbol may be configured as: 1) an uplink symbol, where the symbol is indicated as an SBFD symbol and the UE is configured to transmit SRS, PUCCH, PUSCH or PRACH on the symbol; or a downlink symbol, where the symbol is indicated as an SBFD symbol and the UE is configured to transmit PDCCH, PDSCH or CSI-RS reception on the symbol.

[0137] If another cell in a cell configured using directionalCollisionHandling-r16 operates in the same frequency band as the reference cell, the UE may not expect certain conditions (e.g., and may consider such configurations valid). For example, the UE may not expect: symbols to be indicated as downlink or uplink respectively on the reference cell and as uplink or downlink on the other cell (e.g., via tdd-UL-DL-ConfigurationCommon or via tdd-UL-DL-ConfigurationDedicated); or, for tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, symbols to be indicated as downlink symbols or as SBFD symbols on the reference cell; and the UE is configured to transmit PDCCH, PDSCH, or CSI-RS reception on the reference cell or on a downlink subband cell operating under SBFD, and to detect the DCI format of transmissions scheduled on symbols on the other cell. The UE may also not expect to be configured by a higher layer to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol on a reference cell, or to be indicated as an SBFD symbol, but is instead configured by a higher layer to receive PDCCH, PDSCH, or CSI-RS on a reference cell or on a downlink subband cell in SBFD operation, and to detect the DCI format of transmissions scheduled on a symbol on another cell.

[0138] According to certain aspects of this disclosure, for semi-statically configured SBFD symbols (e.g., on legacy D or F symbols), the symbol direction definition may take into account the case of operation in different frequency bands (e.g., regardless of whether the reference cell and another cell are operating in the same or different frequency bands).

[0139] For example, if the reference cell and another cell in the directional Collision Handling-r16 configuration operate in different frequency bands, when tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates the symbol as downlink or uplink on the other cell and as uplink or downlink for the reference cell, the UE may assume that for flexible symbols or SBFD symbols on which the UE can transmit or receive, the UE does not need to receive higher-layer configured PDCCH, PDSCH, or CSI-RS, and the UE may not be expected to transmit higher-layer configured SRS, PUCCH, PUSCH, or PRACH.

[0140] When a symbol is indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for a reference cell, or when a symbol is indicated as an SBFD symbol and the UE is configured to receive PDCCH, PDSCH, or CSI-RS reception on the symbol, the UE may also not expect to transmit signals / channels scheduled in DCI format on a symbol of another cell.

[0141] If the UE detects a DCI format transmitted on one or more symbols in a symbol set scheduled on another cell: the UE may not need to receive higher-layer configured PDCCH, PDSCH, or CSI-RS on the flexible symbols of the reference cell in the symbol set, or if the symbol is indicated as an SBFD symbol and the UE does not need to receive higher-layer configured PDCCH, PDSCH, or CSI-RS on the symbol, the UE may not need to receive higher-layer configured PDCCH, PDSCH, or CSI-RS on the flexible symbols of the reference cell in the symbol set.

[0142] Based on certain aspects, rules can be proposed to consider the following possibilities: in the case of SBFD operation within a CA, the uplink can occur in a UL SB CC, and the downlink can occur in a DL SB CC. Therefore, updates to certain UE behaviors (e.g., as described below) may be beneficial in considering those cases when configuring gNB SBFD operation.

[0143] Under such rules, a UE may not expect tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell to designate a symbol as uplink and detect the received DCI format on a symbol scheduled on another cell. In this case, the uplink direction can be defined by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell, or it can be defined if the symbol is designated as an SBFD symbol but has a symbol corresponding to the transmission of SRS, PUCCH, PUSCH, or PRACH configured by a higher layer on the reference cell or on the uplink (subband) cell operating under SBFD.

[0144] The UE may not expect to be configured by a higher layer to transmit SRS, PUCCH, PUSCH or PRACH on flexible symbols on a reference cell and to detect the received DCI format on symbols scheduled on another cell.

[0145] If at least one symbol from the symbol set of another cell is indicated as a downlink, the UE may not transmit the PUCCH, PUSCH, or PRACH configured by the higher layer on the symbol set. In this case, the downlink direction may be defined by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or it may be a symbol corresponding to a PDCCH, PDSCH, or CSI-RS configured by the higher layer on the reference cell, or a symbol indicated as an SBFD symbol but having a symbol corresponding to a PDCCH, PDSCH, or CSI-RS configured by the higher layer on the reference cell or on the downlink (subband cell) of SBFD operation.

[0146] If the symbol set on another cell is indicated as downlink, the UE may not transmit the SRS configured by the higher layer on the symbol set. In this case, the downlink direction may be defined by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or it may correspond to a symbol received by the PDCCH, PDSCH, or CSI-RS configured by the higher layer on the reference cell, or it may be a symbol indicated as SBFD symbol but having a symbol corresponding to a symbol received by the PDCCH, PDSCH, or CSI-RS configured by the higher layer on the reference cell or on the downlink subband cell in SBFD operation.

[0147] If at least one symbol from a symbol set on another cell is indicated as uplink, the UE may not receive PDCCH, PDSCH, or CSI-RS configured by a higher layer on the symbol set. The uplink direction may be defined by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for the reference cell, or by a symbol indicated as an SBFD symbol but having a symbol corresponding to the transmission of SRS, PUCCH, PUSCH, or PRACH configured by a higher layer on the reference cell or on the uplink (subband) cell where SBFD is operating.

[0148] The UE may assume that the symbol is flexible for transmission or reception via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, which is indicated as an SBFD symbol, and is not configured by a higher layer to transmit SRS, PUCCH, PUSCH, or PRACH or receive PDCCH, PDSCH, or CSI-RS on the reference cell or on the associated (subband) cell of the SBFD operation.

[0149] After the UE has applied the procedures for directional collision handling described above within the set of cells that have been configured using directionalCollisionHandling-r16, the UE may not expect that it cannot perform any directional collisions between serving cells that are simultaneously transmitting and receiving.

[0150] Depending on certain aspects, the UE may indicate (e.g., report) its UE capabilities regarding SBFD operation configured on the D or F symbol. (See above for reference.) Figure 11A and Figure 11B As described, there are two alternatives for configuring SBFD symbols or slots on legacy flexible (F) symbols or slots. For new SBFD-aware UEs, new UE capabilities can be defined to indicate whether the UE supports gNB configuration of SBFD symbols or slots on legacy flexible symbols or slots.

[0151] In some respects, regarding the second option described above (see reference) Figure 11BThis allows defining new UE capabilities for SBFD-aware UEs to indicate that the SBFD-aware UE supports SBFD operation in symbols configured as flexible in TDD-UL-DL-ConfigCommon. In this case, the gNB can only provide the UE with an indication of the UL subband frequency location. RBs outside the UL subband can be used as UL or DL ​​(excluding the guard band if one is used). SBFD-aware UEs may require additional algorithms or processing to support this type of UE feature. Furthermore, signaling can be provided to further indicate that RBs outside the UL subband are actually used as UL or DL ​​in F symbols. Therefore, a second option can be provided to indicate whether the UE supports SBFD operation in symbols configured as flexible in TDD-UL-DL-ConfigCommon.

[0152] In some cases, the two options described above can be achieved (see reference). Figure 11A and Figure 11B This situation is similar to that described above. A new UE capability can be implemented to indicate whether the UE supports the second option described above, which is used for SBFD operations in symbols where TDD-UL-DL-ConfigCommon is configured as flexible (see reference). Figure 11B As described). In some cases, the first option (see reference) Figure 11A (As described) can be used as the default UE feature to be supported.

[0153] In some cases, if only the first option is supported (see reference) Figure 11A (As described), then no new UE capability may be required. In this case, all SBFD-aware UEs can support the first option, where SBFD operation is configured as a flexible symbol in TDD-UL-DL-ConfigCommon with D / U / D or D / U configuration. The UE behavior is the same as SBFD operation configured as a downlink symbol in TDD-UL-DL-ConfigCommon. Alternatively, new UE capabilities can be defined for SBFD-aware UEs to support the first option of SBFD operation in symbols configured as flexible in TDD-UL-DL-ConfigCommon.

[0154] Example Operation

[0155] Figure 14 This shows the user equipment (UE) (such as Figure 1 and Figure 3 An example of a method 1400 for wireless communication at UE 104.

[0156] Method 1400 begins at step 1405, where a first signaling is obtained indicating that at least one symbol is configured as a sub-band full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC. In some cases, the operation of this step involves, as referenced... Figure 18 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0157] Method 1400 then proceeds to step 1410, where a second signaling is obtained instructing targeted collision handling to be enabled for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC. In some cases, the operation of this step involves, as referenced... Figure 18 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0158] Method 1400 then proceeds to step 1415, where communication is made with one or more serving cells based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code used for communication described herein, or that can be executed by the circuitry and / or the code.

[0159] In some respects, when the UE is configured to transmit uplink signals on SBFD symbols via higher-layer signaling, at least one of one or more rules indicates the symbol direction of the SBFD symbol as uplink.

[0160] In some respects, uplink signals include at least one of the following: a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a physical random access channel (PRACH).

[0161] In some respects, when the UE is configured to transmit uplink signals in an SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as uplink.

[0162] In some respects, when the UE is configured to receive downlink signals on an SBFD symbol via higher-layer signaling, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as downlink.

[0163] In some respects, downlink signals include at least one of the following: physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS).

[0164] In some respects, when the UE is configured to receive downlink signals on an SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as downlink.

[0165] In some respects, according to one or more rules, the UE ignores the configuration in the following cases: the symbol direction of at least one SBFD symbol is downlink with respect to at least the reference cell; and the UE is configured via higher-layer signaling to transmit uplink signals on SBFD symbols associated with the reference cell or another cell.

[0166] In some respects, according to one or more rules, a UE will be considered invalid if: the symbol direction of at least one SBFD symbol is uplink with respect to at least the reference cell; and the UE is configured via higher-layer signaling to receive downlink signals on SBFD symbols associated with the reference cell or another cell.

[0167] In some respects, according to one or more rules, at least one of the following exists: when the symbol direction of at least one SBFD symbol is uplink for a first cell and downlink for a second cell, the UE is not required to receive scheduled downlink signals and is not expected to transmit scheduled uplink signals; when at least one SBFD symbol is indicated as downlink for a reference cell, the UE ignores a configuration that schedules the UE to transmit uplink signals via downlink control information (DCI) through another cell, and the UE is scheduled to receive downlink signals on at least one SBFD symbol; or when the UE detects downlink control information (DCI) scheduled to be transmitted on at least one SBFD symbol associated with another cell, the UE is not required to receive scheduled downlink signals via the reference cell.

[0168] In some respects, the reference cell and another cell operate in the same frequency band.

[0169] In some respects, the reference cell and another cell operate in different frequency bands.

[0170] In some respects, the symbol direction of at least one SBFD symbol is considered as: uplink, in the case where at least one SBFD symbol is configured as uplink for a reference cell or in the case where the UE is scheduled to transmit uplink signals on at least one SBFD symbol via a reference cell or another cell; and downlink, in the case where at least one SBFD symbol is configured as uplink for a reference cell or in the case where the UE is scheduled to receive downlink signals on at least one SBFD symbol via a reference cell or another cell.

[0171] In some respects, according to one or more rules, at least one of the following exists: where the symbol direction of at least one SBFD symbol is considered uplink, the UE does not expect to be scheduled for reception on at least one SBFD symbol via another cell.

[0172] In some respects, according to one or more rules, at least one of the following exists: where the symbol direction of at least one SBFD symbol is considered uplink, the UE avoids transmitting uplink signals that are scheduled to be transmitted via another cell on at least one SBFD symbol.

[0173] In some respects, where at least one SBFD symbol is configured to be flexible via network signaling and the UE is not scheduled to transmit uplink signals or receive downlink signals on at least one SBFD symbol via a reference cell or another cell, the symbol direction of at least one SBFD symbol is considered to be flexible for transmission or reception.

[0174] In one aspect, method 1400 or any aspect thereof may be made by means of a device (such as...) Figure 18 The communication device 1800 is used to perform the method 1400, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1800 is described in further detail below.

[0175] It should be noted that Figure 14 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0176] Figure 15 This shows the network entities (such as Figure 1 and Figure 3 BS 102 or as about Figure 2 An example of a method 1500 for wireless communication at a decomposed base station (discussed in this paper).

[0177] Method 1500 begins at step 1505, where a first signaling is output indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code described for the output, or the code that can be executed by the circuitry and / or the code.

[0178] Method 1500 then proceeds to step 1510, where a second signaling is output, instructing targeted collision handling to be enabled for a set of one or more serving cells associated with at least one downlink CC and at least one uplink CC. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code described for the output, or the code that can be executed by the circuitry and / or the code.

[0179] Method 1500 then proceeds to step 1515, wherein communication is made with at least one user equipment (UE) based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code used for communication described herein, or that can be executed by the circuitry and / or the code.

[0180] In some respects, when the UE is configured to transmit uplink signals on SBFD symbols via higher-layer signaling, at least one of one or more rules indicates the symbol direction of the SBFD symbol as uplink.

[0181] In some respects, uplink signals include at least one of the following: a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a physical random access channel (PRACH).

[0182] In some respects, when the UE is configured to transmit uplink signals in an SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as uplink.

[0183] In some respects, when the UE is configured to receive downlink signals on an SBFD symbol via higher-layer signaling, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as downlink.

[0184] In some respects, downlink signals include at least one of the following: physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS).

[0185] In some respects, when the UE is configured to receive downlink signals on an SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of one or more rules determines the symbol direction of at least one SBFD symbol as downlink.

[0186] In some respects, the symbol direction of at least one SBFD symbol is considered as: uplink, in the case where at least one SBFD symbol is configured as uplink for a reference cell or in the case where the UE is scheduled to transmit uplink signals on at least one SBFD symbol via a reference cell or another cell; and downlink, in the case where at least one SBFD symbol is configured as uplink for a reference cell or in the case where the UE is scheduled to receive downlink signals on at least one SBFD symbol via a reference cell or another cell.

[0187] In some respects, where at least one SBFD symbol is configured to be flexible via network signaling and the UE is not scheduled to transmit uplink signals or receive downlink signals on at least one SBFD symbol via a reference cell or another cell, the symbol direction of at least one SBFD symbol is considered to be flexible for transmission or reception.

[0188] In one aspect, method 1500 or any aspect thereof may be made by means of a device (such as...) Figure 18 The communication device 1800 is used to perform the method 1500, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1800 is described in further detail below.

[0189] It should be noted that Figure 15 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0190] Figure 16 This shows the user equipment (UE) (such as Figure 1 and Figure 3 An example of a method 1600 for wireless communication at UE 104.

[0191] Method 1600 begins at step 1605, where a first signaling is output for transmission to a network entity, the first signaling instructing the UE to support subband full-duplex (SBFD) operation within a transmission time interval (TTI) designated as downlink or flexible transmission direction. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code described for the output, or the code that can be executed by the circuitry and / or the code.

[0192] Method 1600 then proceeds to step 1610, where a second signaling is obtained from the network entity, indicating a TTI for SBFD operation, wherein the TTI has a transmission direction specified as downlink or flexible. In some cases, the operation of this step involves, as described in the reference... Figure 18 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0193] Method 1600 then proceeds to step 1615, where communication with the network entity in the TTI is performed according to the indicated capabilities. In some cases, the operation of this step involves, as described in the reference... Figure 18 The circuitry and / or code used for communication described herein, or that can be executed by the circuitry and / or the code.

[0194] In some respects, TTI includes symbols or time slots.

[0195] In some respects, TTI is designated as a flexible symbol for uplink and downlink configuration via Time Division Duplex (TDD).

[0196] In some respects, the second signaling indicates at least one of the following: a first frequency position of an uplink subband configured for SBFD operation in a flexible symbol; or one or more second frequency positions of a downlink subband configured for SBFD operation in a flexible symbol and at least a third frequency position of an uplink subband configured for SBFD operation in a flexible symbol.

[0197] In some respects, communicating with network entities in a flexible symbol, depending on the indicated capability, includes at least one of the following: outputting a signal in an uplink subband, outputting a signal in a frequency resource outside the uplink subband, or acquiring a signal in a frequency resource outside the uplink subband.

[0198] In some aspects, communicating with network entities in a flexible symbol according to the indicated capability includes at least one of the following: outputting a signal in a frequency resource in an uplink subband and acquiring a signal in a downlink subband; or outputting a signal in a frequency resource in an uplink subband and acquiring a signal in a downlink subband, and at least one of the following: outputting or acquiring a signal in a frequency resource outside the uplink subband.

[0199] In some respects, the first signaling indicates the UE's ability to output signals in frequency resources in the uplink subband and to acquire signals in the downlink subband.

[0200] In one aspect, method 1600 or any aspect thereof may be made by means of a device (such as...) Figure 18 The communication device 1800 is used to perform the method 1600, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1800 is described in further detail below.

[0201] It should be noted that Figure 16 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0202] Figure 17 This shows the network entities (such as Figure 1 and Figure 3 BS 102 or as about Figure 2 An example of a method 1700 for wireless communication at a decomposed base station (discussed in this paper).

[0203] Method 1700 begins at step 1705, where a first signaling is obtained instructing the user equipment (UE) to support subband full-duplex (SBFD) operation within a transmission time interval (TTI) designated as downlink or flexible transmission direction. In some cases, the operation of this step involves, as referenced... Figure 18 The circuit and / or code described for obtaining, or that can be executed by the circuit and / or the code.

[0204] Method 1700 then proceeds to step 1710, where a second signaling is output, indicating the TTI for SBFD operation, wherein the TTI has a specified downlink or flexible transmission direction. In some cases, the operation of this step involves, as described in the reference... Figure 18 The circuitry and / or code described for the output, or the code that can be executed by the circuitry and / or the code.

[0205] Method 1700 then proceeds to step 1715, where communication with the UE is performed in the TTI according to the indicated capabilities. In some cases, the operation of this step involves, as referenced... Figure 18 The circuitry and / or code used for communication described herein, or that can be executed by the circuitry and / or the code.

[0206] In some respects, TTI includes symbols or time slots.

[0207] In some respects, TTI is designated as a flexible symbol for uplink and downlink configuration via Time Division Duplex (TDD).

[0208] In some respects, the second signaling indicates at least one of the following: a first frequency position of an uplink subband configured for SBFD operation in a flexible symbol; or one or more second frequency positions of a downlink subband configured for SBFD operation in a flexible symbol and at least a third frequency position of an uplink subband configured for SBFD operation in a flexible symbol.

[0209] In some aspects, communicating with the UE in a flexible symbol, depending on the indicated capability, includes at least one of the following: obtaining a signal in an uplink subband, obtaining a signal in frequency resources outside the uplink subband, or outputting a signal in frequency resources outside the uplink subband.

[0210] In some aspects, communicating with the UE in a flexible symbol according to the indicated capability includes at least one of the following: acquiring a signal in frequency resources in an uplink subband and outputting a signal in a downlink subband; or acquiring a signal in frequency resources in an uplink subband and outputting a signal in a downlink subband, and at least one of the following: acquiring or outputting a signal in frequency resources outside the uplink subband.

[0211] In some respects, the first signaling indicates the UE's ability to output signals in frequency resources in the uplink subband and to acquire signals in the downlink subband.

[0212] In one aspect, method 1700 or any aspect thereof may be made by means of a device (such as...) Figure 18 The communication device 1800 is used to perform the method 1700, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1800 is described in further detail below.

[0213] It should be noted that Figure 17 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0214] Example communication device

[0215] Figure 18 Various aspects of the example communication device 1800 are described. In some aspects, the communication device 1800 is user equipment, such as those mentioned above. Figure 1 and Figure 3 The UE 104 is described. In some respects, the communication device 1800 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0216] Communication device 1800 includes a processing system 1805 coupled to a transceiver 1855 (e.g., a transmitter and / or receiver). In some aspects (e.g., when communication device 1800 is a network entity), the processing system 1805 may be coupled to a network interface 1865, which is configured to communicate via a communication link (such as, as described herein, regarding...). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link acquire and transmit signals for communication device 1800. Transceiver 1855 is configured to transmit and receive signals for communication device 1800 via antenna 1860, such as the various signals described herein. Processing system 1805 may be configured to perform processing functions for communication device 1800, including processing signals received by communication device 1800 and / or to be transmitted by the communication device.

[0217] Processing system 1805 includes one or more processors 1810. In various aspects, the one or more processors 1810 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. In various respects, one or more processors 1810 may represent one or more of the following: receive processor 338, transmit processor 320, TX MIMO processor 330, and / or controller / processor 340, as per [reference to...]. Figure 3 As described. One or more processors 1810 are coupled to a computer-readable medium / memory 1830 via a bus 1850. In some aspects, the computer-readable medium / memory 1830 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1810, cause the one or more processors 1810 to perform actions related to... Figure 14 The described method 1400 or any aspect thereof; regarding Figure 15 The described method 1500 or any aspect thereof; regarding Figure 16 The described method 1600 or any aspect thereof; and regarding Figure 17The method 1700 described herein or any aspect thereof. It should be noted that references to a processor performing the functions of the communication device 1800 may include one or more processors 1810 performing those functions of the communication device 1800.

[0218] In the depicted example, computer-readable medium / memory 1830 stores code (e.g., executable instructions), such as code 1835 for acquisition, code 1840 for communication, and code 1845 for output. Processing the code 1835 for acquisition, the code 1840 for communication, and the code 1845 for output enables the communication device 1800 to execute instructions regarding... Figure 14 The described method 1400 or any aspect thereof; regarding Figure 15 The described method 1500 or any aspect thereof; regarding Figure 16 The described method 1600 or any aspect thereof; and regarding Figure 17 The method described is 1700 or any aspect thereof.

[0219] One or more processors 1810 include circuitry configured to implement (e.g., execute) code stored in a computer-readable medium / memory 1830, the circuitry including circuitry 1815 for acquisition, circuitry 1820 for communication, and circuitry 1825 for output. Processing using the acquisition circuitry 1815, the communication circuitry 1820, and the output circuitry 1825 enables the communication device 1800 to perform operations related to... Figure 14 The described method 1400 or any aspect thereof; regarding Figure 15 The described method 1500 or any aspect thereof; regarding Figure 16 The described method 1600 or any aspect thereof; and regarding Figure 17 The method described is 1700 or any aspect thereof.

[0220] The various components of the communication device 1800 can provide parts for performing the following: Figure 14 The described method 1400 or any aspect thereof; regarding Figure 15 The described method 1500 or any aspect thereof; regarding Figure 16 The described method 1600 or any aspect thereof; and regarding Figure 17 The described method 1700 or any aspect thereof. For example, components for transmitting, conveying, or outputting for transmission may include... Figure 3 The transceiver 354 and / or antenna 352 of the illustrated UE 104 Figure 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102, and / or Figure 18 The communication device 1800 includes a transceiver 1855 and an antenna 1860. Components for receiving or acquiring data may include... Figure 3 The transceiver 354 and / or antenna 352 of the illustrated UE 104 Figure 3 The transceiver 332 and / or antenna 334 of the illustrated BS 102, and / or Figure 18 The transceiver 1855 and antenna 1860 of the communication equipment 1800.

[0221] Example Terms

[0222] Specific implementation examples are described in the following numbered clauses:

[0223] Clause 1: A method for wireless communication at a network node (e.g., a UE), the method comprising: obtaining a first signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; obtaining a second signaling indicating that directional collision handling is enabled for a set of one or more serving cells associated with the at least one downlink CC and the at least one uplink CC; and communicating with the one or more serving cells based on the symbol direction of the at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

[0224] Clause 2: According to the method of Clause 1, wherein when the network node is configured to transmit uplink signals on the SBFD symbol via higher-layer signaling, at least one of the one or more rules indicates the symbol direction of the SBFD symbol as uplink.

[0225] Clause 3: The method according to Clause 2, wherein the uplink signal includes at least one of the following: a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a physical random access channel (PRACH).

[0226] Clause 4: According to the method of Clause 2, wherein when the network node is configured to transmit the uplink signal in the SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as uplink.

[0227] Clause 5: The method according to any one of Clauses 1 to 4, wherein, when the network node is configured via higher-layer signaling to receive downlink signals on the SBFD symbol, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

[0228] Clause 6: The method according to Clause 5, wherein the downlink signal includes at least one of the following: physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS).

[0229] Clause 7: According to the method of Clause 5, wherein when the network node is configured to receive the downlink signal on the SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

[0230] Clause 8: The method according to any one of Clauses 1 to 7, wherein, according to one or more of the rules, the network node ignores the configuration in the following cases: the symbol direction of the at least one SBFD symbol is downlink with respect to at least the reference cell; and the network node is configured via higher-layer signaling to transmit uplink signals on the SBFD symbol associated with the reference cell or another cell.

[0231] Clause 9: The method according to any one of Clauses 1 to 8, wherein, according to one or more of the rules, the network node is configured to be invalid if: the symbol direction of the at least one SBFD symbol is uplink with respect to at least the reference cell; and the network node is configured via higher-layer signaling to receive downlink signals on the SBFD symbol associated with the reference cell or another cell.

[0232] Clause 10: The method according to any one of Clauses 1 to 9, wherein, according to one or more rules, at least one of the following exists: when the symbol direction of the at least one SBFD symbol is uplink for a first cell and downlink for a second cell, the network node is not required to receive scheduled downlink signals and is not expected to transmit scheduled uplink signals; when the at least one SBFD symbol is indicated as downlink for a reference cell, the network node ignores a configuration that schedules the network node to transmit uplink signals via downlink control information (DCI) through another cell, and the network node is scheduled to receive downlink signals on the at least one SBFD symbol; or when the network node detects downlink control information (DCI) scheduled to be transmitted on the at least one SBFD symbol associated with another cell, the network node is not required to receive scheduled downlink signals via a reference cell.

[0233] Clause 11: The method according to Clause 10, wherein the reference cell and the other cell operate in the same frequency band.

[0234] Clause 12: The method described in Clause 10, wherein the reference cell and the other cell operate in different frequency bands.

[0235] Clause 13: In the method according to any one of Clauses 1 to 12, the symbol direction of the at least one SBFD symbol is regarded as: uplink, in the case where the at least one SBFD symbol is configured as an uplink for a reference cell or in the case where the network node is scheduled to transmit uplink signals on the at least one SBFD symbol via the reference cell or another cell; and downlink, in the case where the at least one SBFD symbol is configured as an uplink for a reference cell or in the case where the network node is scheduled to receive downlink signals on the at least one SBFD symbol via the reference cell or another cell.

[0236] Clause 14: The method according to Clause 13, wherein, according to one or more rules, at least one of the following exists: where the symbol direction of the at least one SBFD symbol is considered an uplink, the network node does not expect to be scheduled for reception on the at least one SBFD symbol via the other cell.

[0237] Clause 15: The method according to Clause 13, wherein, according to one or more rules, at least one of the following exists: when the symbol direction of the at least one SBFD symbol is regarded as an uplink, the network node avoids transmitting uplink signals scheduled for transmission via the other cell on the at least one SBFD symbol.

[0238] Clause 16: The method according to any one of Clauses 1 to 15, wherein the symbol direction of the at least one SBFD symbol is considered flexible for transmission or reception when the at least one SBFD symbol is configured to be flexible via network signaling and the network node is not scheduled to transmit uplink signals or receive downlink signals on the at least one SBFD symbol via the reference cell or another cell.

[0239] Clause 17: A method for wireless communication at a first network node (e.g., a UE), the method comprising: outputting first signaling for transmission to a second network node, the first signaling indicating that the first network node supports sub-band full-duplex (SBFD) operation during a transmission time interval (TTI) having a designated downlink or flexible transmission direction; obtaining second signaling from the network node, the second signaling indicating a TTI for SBFD operation, wherein the TTI has a designated downlink or flexible transmission direction; and communicating with the network node during the TTI according to the indicated capability.

[0240] Clause 18: The method described in Clause 17, wherein the TTI includes a symbol or a time slot.

[0241] Clause 19: The method according to any one of Clauses 17 to 18, wherein the TTI is designated as a flexible symbol via a time-division duplex (TDD) uplink downlink configuration.

[0242] Clause 20: The method according to Clause 19, wherein the second signaling indicates at least one of the following: a first frequency position of an uplink subband configured for SBFD operation in the flexible symbol; or one or more second frequency positions of a downlink subband configured for SBFD operation in the flexible symbol and at least a third frequency position of an uplink subband configured for SBFD operation in the flexible symbol.

[0243] Clause 21: The method according to Clause 20, wherein communicating with the second network node in the flexible symbol according to the indicated capability includes at least one of: outputting a signal in the uplink subband, outputting a signal in frequency resources outside the uplink subband, or obtaining a signal in frequency resources outside the uplink subband.

[0244] Clause 22: The method according to Clause 20, wherein communicating with the second network node in the flexible symbol according to the indicated capability includes at least one of the following: outputting a signal in frequency resources in the uplink subband and acquiring a signal in the downlink subband; or outputting a signal in frequency resources in the uplink subband and acquiring a signal in the downlink subband, and at least one of the following: outputting or acquiring a signal in frequency resources outside the uplink subband.

[0245] Clause 23: The method according to Clause 20, wherein the first signaling indicates the ability of the first network node to output a signal in the frequency resources of the uplink subband and to obtain a signal in the downlink subband.

[0246] Clause 24: A method for wireless communication at a network node, the method comprising: outputting a first signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; outputting a second signaling indicating that directional collision handling is enabled for a set of one or more serving cells associated with the at least one downlink CC and the at least one uplink CC; and communicating with at least one user equipment (UE) based on the symbol direction of the at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

[0247] Clause 25: The method according to Clause 24, wherein, in the case where the UE is configured to transmit uplink signals on the SBFD symbol via higher-layer signaling, at least one of the one or more rules indicates the symbol direction of the SBFD symbol as uplink.

[0248] Clause 26: The method according to Clause 25, wherein the uplink signal includes at least one of the following: a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a physical random access channel (PRACH).

[0249] Clause 27: The method according to Clause 25, wherein, in the case where the UE is configured to transmit the uplink signal in the SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as uplink.

[0250] Clause 28: The method according to any one of Clauses 24 to 27, wherein, when the UE is configured via higher-layer signaling to receive downlink signals on the SBFD symbol, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

[0251] Clause 29: The method according to Clause 28, wherein the downlink signal includes at least one of the following: physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS).

[0252] Clause 30: The method according to Clause 28, wherein, in the case where the UE is configured to receive the downlink signal on the SBFD symbol via a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

[0253] Clause 31: In the method according to any one of Clauses 24 to 30, the symbol direction of the at least one SBFD symbol is regarded as: uplink, in the case where the at least one SBFD symbol is configured as an uplink for a reference cell or in the case where the UE is scheduled to transmit uplink signals on the at least one SBFD symbol via the reference cell or another cell; and downlink, in the case where the at least one SBFD symbol is configured as an uplink for a reference cell or in the case where the UE is scheduled to receive downlink signals on the at least one SBFD symbol via the reference cell or another cell.

[0254] Clause 32: The method according to any one of Clauses 24 to 31, wherein the symbol direction of the at least one SBFD symbol is considered to be flexible for transmission or reception when the at least one SBFD symbol is configured to be flexible via network signaling and the UE is not scheduled to transmit uplink signals or receive downlink signals on the at least one SBFD symbol via the reference cell or another cell.

[0255] Clause 33: A method for wireless communication at a network node, the method comprising: obtaining a first signaling indicating that a user equipment (UE) supports sub-band full-duplex (SBFD) operation in a transmission time interval (TTI) having a designated downlink or flexible transmission direction; outputting a second signaling indicating a TTI for SBFD operation, wherein the TTI has a designated downlink or flexible transmission direction; and communicating with the UE in the TTI according to the indicated capability.

[0256] Clause 34: The method described in Clause 33, wherein the TTI includes a symbol or a time slot.

[0257] Clause 35: The method according to any one of Clauses 33 to 34, wherein the TTI is designated as a flexible symbol via a time-division duplex (TDD) uplink downlink configuration.

[0258] Clause 36: The method according to Clause 35, wherein the second signaling indicates at least one of the following: a first frequency position of an uplink subband configured for SBFD operation in the flexible symbol; or one or more second frequency positions of a downlink subband configured for SBFD operation in the flexible symbol and at least a third frequency position of an uplink subband configured for SBFD operation in the flexible symbol.

[0259] Clause 37: The method according to Clause 36, wherein communicating with the UE in the flexible symbol according to the indicated capability includes at least one of: obtaining a signal in the uplink subband, obtaining a signal in frequency resources outside the uplink subband, or outputting a signal in frequency resources outside the uplink subband.

[0260] Clause 38: The method according to Clause 36, wherein communicating with the UE in the flexible symbol according to the indicated capability includes at least one of the following: obtaining a signal in the frequency resources of the uplink subband and outputting a signal in the downlink subband; or obtaining a signal in the frequency resources of the uplink subband and outputting a signal in the downlink subband, and at least one of the following: obtaining or outputting a signal in frequency resources outside the uplink subband.

[0261] Clause 39: The method according to Clause 36, wherein the first signaling indicates the UE's ability to output a signal in the frequency resources of the uplink subband and to obtain a signal in the downlink subband.

[0262] Clause 40: An apparatus comprising: at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the apparatus to perform a method according to any one of Clauses 1 to 39.

[0263] Clause 41: An apparatus comprising: a component for performing the method according to any one of Clauses 1 to 39.

[0264] Clause 42: A non-transitory computer-readable medium comprising executable instructions that, when executed by at least one processor of a device, cause the device to perform a method according to any one of Clauses 1 to 39.

[0265] Clause 43: A computer program product embodied on a computer-readable storage medium, the computer-readable storage medium including code for performing the method according to any one of Clauses 1 to 39.

[0266] Clause 44: A wireless node comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the wireless node to perform a method according to any one of Clauses 1 to 16, wherein the at least one transceiver is configured to receive the first signaling and receive the second signaling.

[0267] Clause 45: A wireless node comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the wireless node to perform a method according to any one of Clauses 17 to 23, wherein the at least one transceiver is configured to transmit the first signaling and receive the second signaling.

[0268] Clause 46: A network node comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the network node to perform a method according to any one of Clauses 24 to 32, wherein the at least one transceiver is configured to transmit the first signaling and transmit the second signaling.

[0269] Clause 47: A network node comprising: at least one transceiver; at least one memory including executable instructions; and at least one processor configured to execute the executable instructions and cause the network node to perform a method according to any one of Clauses 33 to 39, wherein the at least one transceiver is configured to receive the first signaling and transmit the second signaling.

[0270] Additional Notes

[0271] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. 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. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0272] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, graphics processing unit (GPU), neural processing unit (NPU), digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0273] As used herein, the term wireless node may refer to, for example, a network entity or a user equipment (UE). In this context, a network entity may be a base station (e.g., gNB) or a module of a disassembled base station (e.g., CU, DU, and / or RU).

[0274] While this disclosure may describe certain operations as being performed by one type of wireless node, the same or similar operations may also be performed by another type of wireless node. For example, operations performed by a network entity may also (or alternatively) be performed by a UE. Similarly, operations performed by a UE may also (or alternatively) be performed by a network entity.

[0275] Furthermore, while this disclosure may describe certain types of communication between different types of wireless nodes (e.g., between a network entity and a UE), the same or similar types of communication may occur between the same type of wireless nodes (e.g., in a peer-to-peer scenario, between network entities or between UEs). Additionally, communication may occur in the opposite direction to what is described (e.g., a UE may send a request to a network entity, and the network entity may send a response; or a network entity may send a request to a UE, and the UE may send a response).

[0276] As used herein, "processor," "at least one processor," or "one or more processors" generally refers to a single processor configured to perform one or more operations, or multiple processors configured to collectively perform one or more operations. In the case of multiple processors, the execution of one or more operations may be divided among different processors, but one processor may perform multiple operations, and multiple processors may collectively perform a single operation. Similarly, "memory," "at least one memory," or "one or more memory" generally refers to a single memory configured to store data and / or instructions, or multiple memories configured to collectively store data and / or instructions.

[0277] The components for acquisition, communication, and output may include one or more processors, such as those mentioned above. Figure 18 One or more of the processors described.

[0278] As used in this article, the phrase “at least one of the items” refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, cc, and ccc, or any other ordering of a, b, and c).

[0279] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0280] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0281] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to the singular form of an element is not intended to mean “one and only one,” but rather “one or more.” Unless specifically stated otherwise, the term “some” means one or more. No element of any claim shall be interpreted in accordance with 35 USC §112(f) unless that element is explicitly stated using the phrase “for a component of.” All structural and functional equivalents of the elements throughout the various aspects described herein that are known to a person of ordinary skill in the art, or will later be known, 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 recited in the claims.

Claims

1. An apparatus for wireless communication, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the device to: Obtain first signaling, the first signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; A second signaling is obtained, which instructs the activation of directed collision handling for a set of one or more serving cells associated with the at least one downlink CC and the at least one uplink CC; as well as The communication with the one or more serving cells is based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

2. The apparatus of claim 1, wherein, when the apparatus is configured via higher-layer signaling to transmit uplink signals on the SBFD symbol, at least one of the one or more rules indicates the symbol direction of the SBFD symbol as uplink.

3. The apparatus of claim 2, wherein the uplink signal comprises at least one of the following: a sounding reference signal (SRS), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), or a physical random access channel (PRACH).

4. The apparatus of claim 2, wherein, when the apparatus is configured to transmit the uplink signal in the SBFD symbol via at least one of a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as uplink.

5. The apparatus of claim 1, wherein, when the apparatus is configured via higher-layer signaling to receive downlink signals on the SBFD symbol, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

6. The apparatus of claim 5, wherein the downlink signal includes at least one of the following: physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), or channel state information reference signal (CSI-RS).

7. The apparatus of claim 5, wherein, when the apparatus is configured to receive the downlink signal on the SBFD symbol via at least one of a reference cell or another cell configured for SBFD operation, at least one of the one or more rules determines the symbol direction of the at least one SBFD symbol as downlink.

8. The apparatus according to claim 1, wherein, According to one or more of the rules, the device ignores the configuration in the following situations: The symbol direction of the at least one SBFD symbol is downlink for at least the reference cell; and The device is configured via higher-layer signaling to transmit uplink signals on the SBFD symbol associated with the reference cell or another cell.

9. The apparatus according to claim 1, wherein, According to one or more of the rules, the device will be considered invalid under the following circumstances: The symbol direction of the at least one SBFD symbol is uplink for at least the reference cell; and The device is configured via higher-layer signaling to receive downlink signals on the SBFD symbol associated with the reference cell or another cell.

10. The apparatus according to claim 1, wherein, According to one or more of the rules, at least one of the following exists: When the symbol direction of the at least one SBFD symbol is uplink for the first cell and downlink for the second cell, the device is not required to receive scheduled downlink signals and is not expected to transmit scheduled uplink signals. In the case where at least one SBFD symbol is indicated as downlink for a reference cell, the device ignores the configuration that schedules the device to transmit uplink signals via downlink control information (DCI) through another cell, and the device is scheduled to receive downlink signals on the at least one SBFD symbol; or When the device detects downlink control information (DCI) being transmitted on at least one SBFD symbol associated with another cell, the device does not need to receive the scheduled downlink signal via a reference cell.

11. The apparatus of claim 10, wherein the reference cell and the other cell operate in the same frequency band.

12. The apparatus of claim 10, wherein the reference cell and the other cell operate in different frequency bands.

13. The apparatus of claim 1, wherein the symbol orientation of the at least one SBFD symbol is considered as: Uplink, in the case where at least one SBFD symbol is configured as an uplink for a reference cell, or in the case where the device is scheduled to transmit uplink signals on at least one SBFD symbol via the reference cell or another cell; and Downlink, in the case where at least one SBFD symbol is configured as an uplink for a reference cell or in the case where the device is scheduled to receive downlink signals on at least one SBFD symbol via the reference cell or another cell.

14. The apparatus according to claim 13, wherein, According to one or more of the rules: when the symbol direction of at least one SBFD symbol is regarded as an uplink, the device does not expect to be scheduled for reception on the at least one SBFD symbol via the other cell.

15. The apparatus according to claim 13, wherein, According to one or more of the rules: when the symbol direction of the at least one SBFD symbol is regarded as an uplink, the device avoids transmitting uplink signals that are scheduled to be transmitted on the at least one SBFD symbol via the other cell.

16. The apparatus of claim 1, wherein, when the at least one SBFD symbol is configured to be flexible via network signaling and the apparatus is not scheduled to transmit uplink signals or receive downlink signals on the at least one SBFD symbol via a reference cell or another cell, the symbol direction of the at least one SBFD symbol is considered to be flexible for transmission or reception.

17. The apparatus of claim 1, further comprising at least one transceiver configured to receive the first signaling, wherein the apparatus is configured as a user equipment (UE).

18. An apparatus for wireless communication, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the device to: Output a first signaling message for transmission to a network entity, the first signaling message indicating the device's ability to support subband full-duplex (SBFD) operation during a transmission time interval (TTI) that is designated as downlink or flexible transmission direction; A second signaling is obtained from the network entity, the second signaling indicating a TTI for SBFD operation, wherein the TTI has a transmission direction specified as downlink or flexible. as well as To communicate with the network entity in the TTI according to the indicated capabilities.

19. The apparatus of claim 18, wherein the TTI comprises a symbol or a time slot.

20. The apparatus of claim 18, wherein the TTI is designated as a flexible symbol via a time-division duplex (TDD) uplink-downlink configuration.

21. The apparatus of claim 20, wherein the second signaling indicates at least one of the following: The first frequency position of the uplink subband configured for SBFD operation in the flexible symbol; or One or more second frequency positions of the downlink subband configured for SBFD operation in the flexible symbol and at least a third frequency position of the uplink subband configured for SBFD operation in the flexible symbol.

22. The apparatus of claim 21, wherein communicating with the network entity in the flexible symbol according to the indicated capability comprises at least one of: outputting a signal in the uplink subband, outputting a signal in frequency resources outside the uplink subband, or obtaining a signal in frequency resources outside the uplink subband.

23. The apparatus of claim 21, wherein communicating with the network entity in the flexible symbol according to the indicated capability comprises at least one of the following: Output a signal in the frequency resources of the uplink subband and obtain a signal in the downlink subband; or Outputting a signal in a frequency resource within the uplink subband, acquiring a signal in the downlink subband, and at least one of the following: outputting or acquiring a signal in a frequency resource outside the uplink subband.

24. The apparatus of claim 21, wherein the first signaling indicates the apparatus's ability to output a signal in the frequency resources of the uplink subband and to obtain a signal in the downlink subband.

25. The apparatus of claim 1, further comprising at least one transceiver configured to transmit the first signaling, wherein the apparatus is configured as a user equipment (UE).

26. An apparatus for wireless communication, the apparatus comprising: At least one memory, the at least one memory including computer-executable instructions; and One or more processors, the one or more processors being configured to execute the computer-executable instructions and cause the device to: Output a first signaling, the first signaling indicating that at least one symbol is configured as a subband full-duplex (SBFD) symbol having at least one downlink component carrier (CC) and at least one uplink CC; Output a second signaling instruction that enables directed collision handling for a set of one or more serving cells associated with the at least one downlink CC and the at least one uplink CC; as well as To communicate with at least one user equipment (UE) based on the symbol direction of at least one SBFD symbol, wherein the symbol direction is based on one or more rules.

Images