Conflict handling for sub-band full duplex aware user equipment

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive an indication that a network node is operating in a symbol set in a sub-band full duplex mode. The UE may identify whether to receive at least one of a synchronization signal block communication or a physical downlink control channel communication associated with a common search space in the symbol set based at least in part on the indication. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 18 / 482,303, filed on October 6, 2023, and entitled “COLLISION HANDLING FOR SUB-BAND FULL DUPLEX AWARE USER EQUIPMENT” and U.S. Provisional Patent Application No. 63 / 378,896, filed on October 10, 2022, and entitled “COLLISION HANDLING FOR SUB-BAND FULL DUPLEX AWARE USER EQUIPMENT”. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for contention handling for sub-band full-duplex aware user equipment. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of performing wireless communications by a user equipment (UE). The method may include receiving an indication that a network node is operating in a sub-band full duplex (SBFD) mode in a symbol set. The method may include identifying whether to receive at least one of a synchronization signal block (SSB) communication or a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) in the symbol set based at least in part on the indication.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication that a network node is operating in an SBFD mode in a symbol set. The method may include identifying whether to send a communication in a random access channel (RACH) opportunity (RO) associated with the symbol set based at least in part on the indication.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive an indication that a network node is operating in an SBFD mode in a symbol set. The one or more processors may be configured to identify whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive an indication that a network node is operating in an SBFD mode in a symbol set. The one or more processors may also be configured to identify whether to send a communication in an RO associated with the symbol set based at least in part on the indication.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication that a network node is operating in an SBFD mode in a symbol set. The instruction set, when executed by one or more processors of the UE, may cause the UE to identify whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication that a network node is operating in an SBFD mode in a symbol set. The instruction set, when executed by one or more processors of the UE, may cause the UE to identify whether to send a communication in an RO associated with the symbol set based at least in part on the indication.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication that a network node is operating in an SBFD mode in a symbol set. The apparatus may include means for identifying whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication that a network node is operating in an SBFD mode in a symbol set. The apparatus may include means for identifying whether to send a communication in a RO associated with the symbol set based at least in part on the indication.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of a frame structure in a wireless communication network according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a full-duplex (FD) zone, a non-FD zone, and self-interference associated with FD communication according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a slot structure associated with a sub-band full-duplex (SBFD) scheme according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a conflict scenario of SBFD-aware UEs according to the present disclosure.

[0026] Figure 8 is a diagram of an example associated with conflict handling of SBFD-aware UEs according to the present disclosure.

[0027] Fig. 9 is a diagram of an example associated with conflict handling of SBFD-aware UEs according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0032] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0034] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0035] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0036] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0037] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0038] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communications between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0039] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0040] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0041] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, a processor component and a memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0043] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0044] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0047] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may receive an indication that the network node 110 is operating in a sub-band full-duplex (SBFD) mode in a symbol set, and identify, based at least in part on the indication, whether to receive at least one of a synchronization signal block (SSB) communication or a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) in the symbol set. In some other aspects, the communications manager 140 may receive an indication that the network node 110 is operating in a sub-band full-duplex (SBFD) mode in a symbol set, and identify, based at least in part on the indication, whether to send a communication in a random access channel (RACH) opportunity (RO) associated with the symbol set. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Described differently.

[0050] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0051] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0055] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 8 to 12 ) any aspects of any of the methods described herein.

[0056] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 8 to 12 ) any aspects of any of the methods described herein.

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components in the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or other processes described herein may include operations. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the UE 120 includes: means for receiving an indication that a network node is operating in an SBFD mode in a symbol set; and / or means for identifying whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0059] In some aspects, the UE 120 includes: a component for receiving an indication that a network node is operating in an SBFD mode in a symbol set; and / or a component for identifying whether to send a communication in an RO associated with the symbol set based at least in part on the indication. The components for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0060] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions together. For example, a first set of processors in the one or more processors (one or more processors) may perform a first function described as being performed by the one or more processors, and a second set of processors in the one or more processors (one or more processors) may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2 For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0061] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0062] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Described differently.

[0063] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0064] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0065] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0066] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0067] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, or both.

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

[0069] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0070] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions, or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on functional splitting (e.g., functional splitting defined by 3GPP). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0071] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

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

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

[0074] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Described differently.

[0075] Figure 4 is a diagram illustrating an example 400 of a frame structure in a wireless communication network according to the present disclosure. Figure 4 The frame structure shown may be used for time division duplex (TDD) in telecommunication systems such as LTE or NR. The transmission timeline may be divided into units of multiple radio frames (sometimes referred to as frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into a set of Z (Z ≥ 1) subframes (e.g., with indices 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may include a set of time slots (e.g., in Figure 4 Each subframe 2 is shown m time slots, where m is the index of the parameter set used for transmission, such as 0, 1, 2, 3, 4, or other number). Each time slot may include a set of L symbol periods (sometimes simply referred to as symbols). For example, each time slot may include fourteen symbol periods (e.g., Figure 4 In the case where a subframe includes two slots (e.g., when m=1), the subframe may include 2L symbol periods, where the 2L symbol periods in each subframe may be assigned indices 0 to 2L–1.

[0076] In some examples, such as for communications employing TDD, a time slot may be semi-statically configured by the network node 110 as an uplink time slot (sometimes denoted by "U"), a downlink time slot (sometimes denoted by "D"), or a flexible time slot (sometimes denoted by "F"). An uplink time slot may be a time slot that is semi-statically configured for uplink communications (e.g., a time slot in which a symbol is reserved for uplink traffic). A downlink time slot may be a time slot that is semi-statically configured for downlink communications (e.g., a time slot in which a symbol is reserved for downlink traffic). A flexible time slot may be a time slot that includes both uplink and downlink symbols and / or a time slot that can be used for uplink traffic or downlink traffic. In other words, a semi-statically configured uplink time slot may be associated with uplink (UL)-centric traffic, a semi-statically configured downlink time slot may be associated with downlink (DL)-centric traffic, and a semi-statically configured flexible time slot may be used for UL-centric traffic or DL-centric traffic.

[0077] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Described differently.

[0078] Figure 5 5 is a diagram illustrating an example 500 of full-duplex (FD) zoning, non-FD zoning, and self-interference associated with FD communication according to the present disclosure. As shown, example 500 includes a network node (NN) (e.g., network node 110), UE1 (e.g., UE120), and UE2 (e.g., another UE 120). In some aspects, network node 110 may be capable of FD communication. FD communication may include simultaneous uplink communication and downlink communication using the same resources. For example, the network node may perform DL transmission to UE1 (shown by reference numeral 510) and may receive UL transmission from UE2 (shown by reference numeral 520) using the same frequency resources and at least partially overlapping in time.

[0079] As shown by reference numeral 530, DL transmissions from NN may self-interfere with UL transmissions to NN. This may be caused by a variety of factors, such as higher transmit power used for DL ​​transmissions (compared to UL transmissions) and / or RF leakage. In addition, as shown by reference numeral 540, UL transmissions from UE2 to NN may interfere with DL transmissions from NN to UE1, thereby reducing DL performance of UE1.

[0080] The FD zone is shown by reference numeral 550 and the non-FD zone is shown by reference numeral 560. "FD zone" may refer to a time period and / or frequency region in which a wireless communication device (e.g., network node 110, UE 120, or the like) performs FD communication, and "non-FD zone" may refer to a time period and / or frequency region in which a wireless communication device performs non-FD communication. Compared to non-FD zones, FD zones may be associated with higher self-interference and, therefore, lower signal to interference plus noise ratio (SINR).

[0081] In some cases, the network node 110 may operate using non-overlapping uplink and downlink subbands; for example, an SBFD scheme. An "SBFD scheme" may refer to an FD mode in which a time slot provides bidirectional transmission on different subbands within the same component carrier. Figure 6 An example time slot structure associated with the SBFD scheme is described in more detail.

[0082] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Described differently.

[0083] Figure 6 is a diagram illustrating an example 600 of a time slot structure associated with an SBFD scheme according to the present disclosure. In some cases, Figure 6 The example slot structure shown may be associated with SBFD operation within a TDD carrier.

[0084] As shown at reference numeral 602, in some examples, SBFD operation may be associated with multiple subbands within a bandwidth part (BWP), where each subband is associated with one of an uplink communication or a downlink communication by the network node 110 or another wireless communication device. In other words, the example time slot structure shown in conjunction with reference numeral 602 may correspond to a SBFD scheme with a single configured downlink and uplink BWP pair having aligned center frequencies.

[0085] More specifically, in time slot n, the wireless communication device (e.g., network node 110) may operate in downlink mode across the entire BWP (e.g., time slot n may be semi-statically configured as a downlink time slot or a D time slot), and in time slot n+4, the wireless communication device may operate in uplink mode across the entire BWP (e.g., time slot n may be semi-statically configured as an uplink time slot or a U time slot). In this regard, the wireless communication device may not operate in FD mode in time slots n and n+4 (e.g., the wireless communication device may operate in half-duplex (HD) mode in time slots n and n+4). However, in time slots n+1, n+2, and n+3, the wireless communication device may operate in FD mode, and more specifically, in SBFD mode. More specifically, the wireless communication device may use a portion of the BWP (e.g., a subband) for communication in the downlink, and use a portion of the BWP for communication in the uplink. In the example shown in conjunction with reference numeral 602, the wireless communication device may utilize two non-contiguous portions of the BWP for communications in the downlink and utilize one portion of the BWP for communications in the uplink. In some examples, time slots n+1, n+2, and n+3 may be semi-statically configured as downlink time slots (e.g., D time slots), but the network node 110 may still use subbands within these D time slots (e.g., subbands indicated by U) to schedule communications in the uplink.

[0086] In some other examples, the SBFD operation can be associated with multiple BWPs, each of which is associated with one of an uplink communication or a downlink communication by a wireless communication device, as shown at reference numeral 604. In other words, the example time slot structure shown in conjunction with reference numeral 604 can correspond to a SBFD scheme with more than one configured downlink and uplink BWPs having aligned or unaligned center frequencies.

[0087] More specifically, when operating in the SBFD mode shown in conjunction with reference numeral 604, the wireless communication device (e.g., the network node 110) may switch between BWPs when operating in a non-FD mode (e.g., HD mode) and a FD mode. For example, as shown in conjunction with a time slot 606 that may be semi-statically configured as a D time slot, the wireless communication device may communicate in the downlink using a first DL / UL BWP pair (shown as DL / UL BWP1) with aligned center frequencies. However, when switching to the FD mode (e.g., SBFD mode), the wireless communication device may use a different DL / UL BWP pair with or without aligned center frequencies. More specifically, in the time slot shown in conjunction with reference numeral 608, the wireless communication device may communicate in the downlink in a first BWP indicated as DL BWP2 (which may be two non-adjacent portions of DL / UL BWP1), and the wireless communication device may communicate in the uplink in a second BWP indicated as UL BWP2 (which may be a portion of DL / UL BWP 1).

[0088] When returning to half-duplex operation, the wireless communication may switch back to the first DL / UL BWP pair (e.g., DL / UL BWP1). More specifically, as shown in conjunction with time slot 610, which may be semi-statically configured as a U time slot, the wireless communication device may communicate in the uplink using the first DL / UL BWP pair (e.g., DL / UL BWP1) with aligned center frequencies. In some aspects, as shown by reference numeral 612, when switching between DL / UL BWP pairs, a delay (sometimes referred to as an optimized BWP switching delay) may be accounted for in the transmission timeline to provide a time period for the wireless communication device to switch between BWP configurations.

[0089] In some cases, such as by using a combination of Figure 6 A first wireless communication device (e.g., network node 110) operating in SBFD mode may cause a conflict at a second wireless communication device (e.g., UE 120) operating in HD mode and / or not having the capability to operate in SBFD mode. Figure 7 Examples of certain conflicts that may be caused by wireless communication devices operating in SBFD mode are described in more detail.

[0090] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 Described differently.

[0091] Figure 7 is a diagram illustrating an example 700 of a conflict scenario of SBFD-aware UEs according to the present disclosure.

[0092] In some examples, the network node 110 may be capable of operating in the SBFD mode, but the UE 120 in wireless communication with the network node 110 may not be capable of operating in the SBFD mode (e.g., the UE 120 may only have HD capabilities), resulting in time domain conflicts for uplink and downlink communications at the UE 120. In such aspects, the UE 120 may be referred to as an SBFD-aware half-duplex UE, meaning that the UE 120 is not capable of full-duplex operation but is aware that the network node 110 is operating in the full-duplex mode. More specifically, Figure 7 Depicted is an example conflict scenario that UE 120 may face when UE 120 operates in HD mode and network node 110 operates in FD mode (e.g., SBFD mode). For example, as shown by reference numeral 702, UE 120 may be scheduled to receive SSB communications in a downlink timeslot associated with SBFD operation of network node 110. SSBs (sometimes referred to as synchronization signal / physical broadcast channel (SS / PBCH) blocks) may carry information used for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. In some aspects, network node 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0093] Additionally or alternatively, and as also indicated by reference numeral 702, UE 120 may be scheduled to receive communications associated with a CSS (e.g., PDCCH communications) in a downlink timeslot associated with SBFD operation of network node 110. A "search space" may refer to a set of possible locations (e.g., in time and / or frequency) at which a PDCCH may be located. A control resource set (CORESET) may include one or more search spaces, such as a UE-specific search space, a group common search space, and / or a CSS. A "CSS" may refer to a set of all possible PDCCH locations across all UEs. In some aspects, a CSS may correspond to a type 0 PDCCH CSS (sometimes referred to as a type 0-PDCCH), a type 0A PDCCH CSS (sometimes referred to as a type 0A-PDCCH), a type 1 PDCCH CSS (sometimes referred to as a type 1-PDCCH), or a type 2 PDCCH CSS (sometimes referred to as a type 2-PDCCH). A Type 0 PDCCH CSS may be indicated using a system information (SI) radio network temporary identifier (RNTI) (SI-RNTI) of the remaining minimum system information (RMSI) of the primary cell and / or may be associated with a SIB decoding use case, such as for decoding SIB1. A Type 0A PDCCH CSS may be indicated using an SI-RNTI of the primary cell and / or may also be associated with a SIB decoding use case, such as for decoding other SIBs (e.g., SIBs other than SIB1). A Type 1 PDCCH CSS may be indicated using a random access RNTI (RA-RNTI), a temporary cell RNTI (TC-RNTI), or a cell RNTI (C-RNTI) of the primary cell and / or may be associated with message 2 (Msg2) and / or message 4 (Msg4) decoding in a RACH use case. A Type 2 PDCCH CSS may be indicated using a paging RNTI (P-RNTI) of the primary cell and / or may be associated with a paging decoding use case.

[0094] In the example depicted in conjunction with reference numeral 702, UE 120 is not scheduled to transmit uplink communications in an uplink subband of a downlink time slot. Thus, in such examples, UE 120 may receive one of an SSB communication or a PDCCH communication associated with a CSS with little risk of collision at UE 120. In other words, because the SSB communication or the PDCCH communication associated with the CSS is scheduled in a semi-static D time slot, and because UE 120 is not otherwise scheduled to transmit uplink traffic in an uplink subband of a D time slot, there is little risk of collision at UE 120 despite network node 110 operating in SBFD mode in the time slot. In some aspects, a downlink time slot may correspond to a time slot that is dynamically indicated as a downlink time slot and / or is similarly configured as Figure 7 ) (eg, a semi-static F time slot configured with similar uplink and downlink subbands, as shown in conjunction with reference numeral 702).

[0095] However, as indicated by reference numeral 704, in some other examples, UE 120 may be scheduled to send uplink transmissions in a subband of a downlink time slot in which UE 120 may be scheduled to receive one of SSB communications or PDCCH communications associated with a CSS. In other words, network node 110 operating in SBFD mode may schedule UE 120 to send uplink transmissions in a semi-statically configured downlink time slot. In such examples, there may be a time domain conflict between communications in a downlink subband (e.g., at least one of SSB communications and / or PDCCH communications associated with a CSS) and communications in an uplink subband (e.g., uplink transmissions) in a SBFD time slot at UE 120.

[0096] In some other examples, as indicated by reference numeral 706, UE 120 may be scheduled to transmit in a semi-statically configured uplink time slot (in Figure 7 , which may correspond to receiving SSB communications and / or PDCCH communications associated with a CSS in a time slot (e.g., a U time slot) that is configured as an uplink time slot by an RRC TDD configuration parameter (such as one of tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). In some other aspects, the time slot shown in conjunction with reference numeral 706 may be as shown in FIG. Figure 7. Similarly, as shown in reference numeral 708, UE 120 may be scheduled to send uplink communications in an uplink timeslot in which UE 120 is scheduled to receive one of SSB communications or PDCCH communications associated with CSS. In some cases, the uplink transmission may be a semi-static uplink transmission, such as a physical uplink control channel (PUCCH) communication, a physical uplink shared channel (PUSCH) communication, or a sounding reference signal (SRS) communication scheduled by a higher layer configuration (e.g., an RRC configuration). In some other cases, the uplink transmission may be a dynamic grant (DG) uplink transmission, such as a PUCCH communication, a PUSCH communication, or an SRS communication scheduled by downlink control information (DCI). Unlike the scenario shown in conjunction with reference numeral 702, each of the scenarios shown in conjunction with reference numerals 704, 706, and 708 may cause a risk of time domain collision at UE 120.

[0097] As another example, in some cases, the SBFD operation of the network node 110 may cause a collision risk associated with a RO (sometimes referred to as a PRACH opportunity) used by the UE 120 in conjunction with a random access procedure. "RO" may refer to a transmission opportunity (e.g., time and frequency resources) for the UE 120 associated with a RACH procedure (e.g., time and frequency resources used to transmit a message associated with the RACH procedure). For example, as indicated by reference numeral 710, in some cases, the UE 120 may transmit a message in a semi-statically configured downlink time slot (in Figure 7 , which may correspond to a time slot that is configured as a downlink time slot (e.g., a D time slot) by an RRC TDD configuration parameter (such as one of tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) and is scheduled with an RO (e.g., time and frequency resources that may be scheduled for performing a random access procedure and / or for sending communications associated with the random access procedure). In some other aspects, the time slot shown in conjunction with reference numeral 710 may be as shown in FIG. Figure 710 and 11. Similarly, as shown in reference numeral 712, UE 120 may be scheduled to receive a downlink transmission in a downlink slot in which UE 120 may be scheduled with an RO. In some cases, the downlink transmission may be a semi-static downlink transmission, such as a PDCCH communication, a physical downlink shared channel (PDSCH) communication, or a channel state information (CSI) reference signal (CSI-RS) reception scheduled by a higher layer configuration (e.g., an RRC configuration). In some other cases, the downlink transmission may be a DG downlink transmission, such as a PUSCH communication or CSI-RS reception scheduled by a DCI. Both scenarios shown in conjunction with reference numerals 710 and 712 may create a risk of conflict at UE 120.

[0098] In some other examples, as shown by reference numeral 714, UE 120 may be scheduled with RO in an uplink time slot. In this example, UE 120 is not scheduled to receive downlink communications in a downlink subband of the uplink time slot. Therefore, in such examples, UE 120 may use RO with little risk of collision at UE 120. However, as shown by reference numeral 716, in some examples, UE 120 may be scheduled to receive downlink transmissions in a downlink subband of an uplink time slot in which UE 120 may be scheduled with RO. In such examples, there may be a time domain collision between a downlink transmission in a downlink subband and an uplink communication transmitted in RO at UE 120 in an SBFD symbol.

[0099] In some examples, the SBFD operation of network entity 110 may be transparent to UE 120. In such cases, the time and frequency locations of the subbands used for SBFD are unknown to UE 120, and thus UE 120 may operate in a manner similar to if UE 120 was communicating with network node 110 that is not operating in SBFD mode. In this regard, UE 120 may not be able to mitigate disruptions caused by one or more of the conflict scenarios described above.

[0100] However, in some other cases, the SBFD operation of the network node 110 may be opaque to the UE 120 (e.g., the UE 120 may be aware of the SBFD operation of the network node 110). When the SBFD operation of the network node 110 is opaque to the UE 120, the UE 120 is sometimes referred to as an SBFD-aware UE. In some examples, the SBFD-aware UE may not be aware of the time and / or frequency location of the subbands used for SBFD operation, but the SBFD-aware UE may still be aware that the network node 110 is operating in the SBFD mode. In some other examples, the SBFD-aware UE is aware of the time location of the subbands used for SBFD operation (e.g., the UE 120 may be indicated with a symbol set and / or one or more time slots in which the network node 110 operates in the SBFD mode), but is not aware of the frequency location of the subbands used for SBFD operation. And in some other examples, the SBFD-aware UE is aware of both the time location and the frequency location of the subbands used for SBFD operation (e.g., UE 120 may be indicated with a symbol set and / or one or more time slots in which network node 110 operates in SBFD mode, and / or with the frequency locations of the respective subbands).

[0101] In some examples, the SBFD-aware UE may be in a poor position to mitigate disruptions caused by one or more of the above-described conflict scenarios. This may be because the SBFD-aware UE may not be configured or specified with one or more priorities and / or rules for handling conflict scenarios. Therefore, whether a particular UE 120 receives or sends a particular communication in a conflict scenario may depend on the specific implementation of the UE 120. This may cause the UE 120 to lose control information or other high priority traffic from the network node 110, and / or the UE 120 to selectively send or receive communications to the network node 110 in a transparent manner, resulting in increased communication errors; high power, computing, and communication resource consumption in order to correct communication errors; increased latency and reduced throughput associated with the communication channel between the network node 110 and the UE 120; and inefficient use of network resources in other ways.

[0102] Some techniques and apparatus described herein implement enhanced conflict handling for SBFD-aware UEs. In some aspects, UE 120 may receive an indication from network node 110 that network node 110 is operating in SBFD mode (e.g., UE 120 may be an SBFD-aware UE), and UE 120 may be configured, preconfigured, or otherwise specified with one or more conflict handling rules to perform a conflict handling process based at least in part on the indication. For example, in an aspect in which UE 120 is scheduled to receive one of SSB communications or PDCCH communications associated with a CSS in an SBFD symbol set, UE 120 may identify whether to receive SSB communications or PDCCH communications associated with a CSS in an SBFD symbol set based at least in part on the indication. And in an aspect in which UE 120 is configured with a RO in an SBFD symbol set, UE 120 may identify whether to send a communication in the RO based at least in part on the indication. Therefore, UE 120 and network node 110 can communicate and / or exchange control information or other high-priority services with greater transparency, thereby communicating with reduced communication errors, resulting in reduced power, computing, and communication resource consumption that would otherwise be used to correct communication errors; reduced latency and increased throughput associated with the communication channel between network node 110 and UE 120; and more efficient use of network resources in other ways.

[0103] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 Described differently.

[0104] Figure 8 8 is a diagram of an example 800 associated with conflict handling for SBFD-aware UEs according to the present disclosure. Figure 8 As shown, a network node 110 (e.g., a CU, DU, and / or RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless network 100). The UE 120 and the network node 110 may be in communication with each other. Figure 8 The operations shown have previously established a wireless connection. Figure 8 In the illustrated operation, the network node 110 may have the capability to operate in the SBFD mode and / or may operate in the SBFD mode and / or Figure 8In the illustrated operations, UE 120 may not have the capability to operate in SBFD mode and / or may not operate in SBFD mode. In addition, in some aspects, UE 120 may be a SBFD-aware UE, as described in more detail below in conjunction with reference numeral 810. In addition to UEs performing initial access (e.g., RRC idle UEs) and inactive UEs (e.g., RRC inactive UEs), aspects described herein also apply to UEs in connected mode (e.g., RRC connected UEs).

[0105] As indicated by reference numeral 805, the network node 110 may send, and the UE 120 may receive, configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., already known to the UE 120 and / or previously indicated by the network node 110 or other network device), and / or explicit configuration information for use by the UE 120 to configure the UE 120, etc.

[0106] In some aspects, the configuration information may indicate TDD configuration parameters that semi-statically configure certain symbols and / or time slots as downlink symbols and / or time slots (e.g., D time slots), uplink symbols and / or time slots (e.g., U time slots), and / or flexible symbols and / or time slots (e.g., F time slots). For example, as described in more detail below in conjunction with reference numeral 810, in some aspects, the UE 120 may receive an indication that the network node 110 is operating in an SBFD mode in a symbol set (e.g., an SBFD symbol set). In such aspects, the configuration information may indicate that the SBFD symbol set is associated with a semi-statically configured uplink time slot and / or symbol set, a semi-statically configured downlink time slot and / or symbol set, or a semi-statically configured flexible time slot and / or symbol set.

[0107] In some aspects, the configuration parameters may be associated with a TDD UL / DL common configuration information element (IE) (e.g., tdd-UL-DL-ConfigurationCommon) or a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated). The TDD UL / DL common configuration IE (e.g., tdd-UL-DL-ConfigurationCommon) may provide cell-specific DL / UL modes to all UEs in a cell and may be broadcast in a system information block (SIB), such as SIB1, or configured to the UE 120 using dedicated RRC signaling. The TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated) may be UE-specific (e.g., sent to a specific UE 120) and may further modify and / or allocate any flexible slots and symbols configured by the TDD UL / DL common configuration IE (e.g., tdd-UL-DL-ConfigurationCommon). The TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated) may be configured to the UE 120 using dedicated RRC signaling. The configuration information may include additional communication parameters. In some aspects, the configuration information may include an indication that the network node 110 is operating in SBFD mode, which is described in more detail below in conjunction with reference numeral 810.

[0108] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0109] As indicated by reference numeral 810, the network node 110 may transmit, and the UE 120 may receive, an indication that the network node 110 is operating in a SBFD mode in a symbol set (e.g., a SBFD symbol set), which is shown as the SBFD symbol set indicated by reference numeral 815. In this regard, based at least in part on the indication, the UE 120 may be an SBFD-aware UE 120. In some aspects, the indication may indicate only a temporal location of the SBFD operation (e.g., the indication may indicate a temporal location of the SBFD symbol set in which the network node 110 is operating in the SBFD mode without indicating a frequency location). In some other aspects, the indication may indicate both a temporal location and a frequency location of the SBFD operation (e.g., the indication may indicate a temporal location and a frequency location of UL and DL subbands in the SBFD symbol set in which the network node 110 is operating in the SBFD mode). In some aspects, the indication that the network node 110 is operating in the symbol-centered SBFD mode may be sent by the network node 110 in a broadcast message, such as in a SIB (e.g., SIB1), and received by the UE 120. Additionally or alternatively, the indication that the network node 110 is operating in the symbol-centered SBFD mode may be sent by the network node 110 via an RRC message, such as an RRC configuration message or an RRC reconfiguration message, and received by the UE 120. In this regard, the indication may be provided as part of the configuration information described above in conjunction with reference numeral 805 (e.g., included in the same RRC message as the configuration information). The RRC message may be a cell-specific or UE-specific configuration.

[0110] In some respects, Figure 8 The SBFD symbol set shown using reference numeral 815 in the SBFD mode may be associated with an uplink symbol and / or an uplink time slot (e.g., a U time slot). More specifically, in some aspects, the symbol set (e.g., the SBFD symbol set) in which the network node 110 is operating in the SBFD mode may be indicated as an uplink symbol or a flexible symbol by TDD UL / DL configuration information (such as by one of a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated) or a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated)). In some other aspects, the symbol set in which the network node 110 is operating in the SBFD mode may be indicated by the TDD UL / DL configuration information as a downlink symbol or a flexible symbol. Additionally or alternatively, in some aspects, the symbol set may be associated with the reception of an SSB (sometimes referred to as an SS / PBCH block) and / or may be associated with a CSS (e.g., the symbol set may be used for the reception of a PDCCH communication associated with the CSS).

[0111] As indicated by reference numeral 820, in some aspects, the network node 110 may transmit, and the UE 120 may receive, at least one of configuration information or DCI scheduling uplink transmissions in a symbol set, such as the SBFD symbol set indicated by reference numeral 815. In other words, in some aspects, the UE 120 may be configured by higher layer parameters for uplink transmissions in the symbol set, and / or the UE 120 may be dynamically scheduled by the DCI for uplink transmissions in the symbol set.

[0112] As indicated by reference numeral 825, UE 120 may identify how to handle potential or actual conflicts in a symbol set due to SBFD operation of network node 110 in the symbol set. Figure 7 As described, SBFD operation of the network node 110 may result in various conflict scenarios at the HD UE 120, such as when SSB communications and / or PDCCH communications associated with the CSS are scheduled to be received in a downlink subband in a semi-static uplink time slot (as described above in conjunction with reference numerals 706 and 708), or when SSB communications and / or PDCCH communications associated with the CSS are scheduled to be received in a semi-static downlink time slot and uplink transmissions are scheduled to be transmitted in an uplink subband of a semi-statically configured downlink time slot (as described above in conjunction with reference numeral 702), etc. Therefore, in the operations illustrated in conjunction with reference numeral 825, the UE 120 may identify whether to receive at least one of the SSB communications (e.g., SS / PBCH communications) or the PDCCH communications associated with the CSS in the symbol set (e.g., the SBFD symbol set indicated by reference numeral 815) based at least in part on the indication.

[0113] As shown by reference numerals 830 and 835, in some aspects, the UE 120 may receive SSB communications and / or PDCCH communications associated with the CSS in a SBFD symbol set, or the UE 120 may send uplink communications in a SBFD symbol set based at least in part on an identification of whether at least one of SSB communications (e.g., SS / PBCH communications) or PDCCH communications associated with the CSS is received in the SBFD symbol set. For example, in some aspects, the SBFD symbol set may be associated with an uplink time slot (e.g., the UE 120 may have received configuration information, such as tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, indicating that the symbol set is associated with an uplink time slot and / or a semi-static flexible time slot that is dynamically indicated as an uplink time slot). In addition, in some aspects, the UE 120 may be configured, preconfigured, or specified to always receive SSB communications and / or PDCCH communications associated with the CSS when they are sent in a SBFD symbol set associated with the uplink time slot. Thus, in such aspects, UE 120 may receive at least one of an SSB communication or a PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the SBFD symbol set is associated with the uplink time slot.

[0114] In some other aspects, the UE 120 may be configured, preconfigured, or specified to receive SSB communications and / or PDCCH communications associated with the CSS only when the SBFD symbol set is associated with the serving cell when the communications are sent in the SBFD symbol set associated with the uplink timeslot. For example, the configuration information described above in conjunction with reference numeral 805 may include serving cell configuration information indicating the location of the SSB associated with the serving cell. For example, the location of the SSB associated with the serving cell may be indicated in a SIB message (e.g., SIB1) via SSB positioning in burst parameters (sometimes referred to as ssb-PositionInBurst). Additionally or alternatively, the location of the SSB associated with the serving cell may be indicated in an RRC message (e.g., in the ServingCellConfigCommon IE) via SSB positioning in burst parameters (e.g., ssb-PositionInBurst). Thus, based at least in part on at least one of the SSB communications and / or PDCCH communications associated with the CSS being associated with the serving cell (e.g., as indicated by ssb-PositionInBurst), the UE 120 may identify that the SSB communications and / or PDCCH communications associated with the CSS should be received in the SBFD symbol set, and thereby receive the SSB communications and / or at least one of the PDCCH communications associated with the CSS, as indicated by reference numeral 830.

[0115] Similarly, UE 120 may be configured, preconfigured, or specified to refrain from receiving SSB communications and / or PDCCH communications associated with the CSS when the SSB communications and / or PDCCH communications associated with the CSS are not associated with the serving cell, such as when the SSB communications and / or PDCCH communications associated with the CSS are sent outside of an SSB measurement timing configuration (SMTC) window associated with the serving cell. In some aspects, the configuration information described above in conjunction with reference number 805 may indicate resources associated with the SMTC window of the serving cell, such as via SSB positioning in burst parameters (e.g., ssb-PositionInBurst) in a SIB message (e.g., SIB1) and / or via SSB positioning in burst parameters (e.g., ssb-PositionInBurst) in an RRC message (e.g., ServingCellConfigCommon). Thus, based at least in part on at least one of the SSB communications and / or PDCCH communications associated with the CSS being not associated with the serving cell (e.g., sent outside the SMTC window, as indicated by ssb-PositionInBurst), UE 120 may identify that SSB communications and / or PDCCH communications associated with the CSS should not be received in the SBFD symbol set, and thereby suppress reception of the communications shown in conjunction with reference numeral 830.

[0116] Additionally or alternatively, the UE 120 may be configured, preconfigured, or specified to always refrain from receiving SSB communications and / or PDCCH communications associated with the CSS when the SSB communications and / or PDCCH communications associated with the CSS are scheduled in a semi-static uplink time slot (e.g., a time slot indicated as a U time slot by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated or similar configuration information as described above in conjunction with reference numerals 706 and 708, and / or a semi-static flexible time slot dynamically indicated as an uplink time slot). In such an aspect, when the SSB communications and / or PDCCH communications associated with the CSS are scheduled to be received in the U time slot, the UE 120 may identify that the SSB communications and / or PDCCH communications associated with the CSS should not be received in the SBFD symbol set, and therefore refrain from receiving the communications shown in conjunction with reference numeral 830.

[0117] Additionally, as described above in conjunction with reference numeral 820, in some aspects, the UE 120 may be scheduled to transmit uplink transmissions in a symbol set (e.g., in a SBFD symbol set indicated by reference numeral 815), similar to the uplink transmissions described in conjunction with the conflicting scenarios illustrated by reference numerals 704 and 708. In such aspects, the UE 120 may be configured, preconfigured, or designated to perform one of receiving SSB communications and / or PDCCH communications associated with the CSS (as indicated by reference numeral 830) or transmitting uplink transmissions (as indicated by reference numeral 835) in the SBFD symbol set, and refrain from performing the other of receiving SSB communications and / or PDCCH communications associated with the CSS or transmitting uplink transmissions.

[0118] More specifically, in some aspects, the UE 120 may be configured, preconfigured, or designated to always receive SSB communications and / or PDCCH communications associated with the CSS, e.g., for the purpose of ensuring that the UE 120 receives control information or similar high priority communications. In such aspects, based at least in part on the configuration information or at least one of the DCI for uplink transmissions in the scheduling symbol set, the UE 120 may receive SSB communications and / or PDCCH communications associated with the CSS in the SBFD symbol set (as indicated by reference numeral 830), and refrain from sending uplink transmissions in the SBFD symbol set (e.g., refrain from sending the message shown in conjunction with reference numeral 835).

[0119] In some other aspects, the UE 120 may be configured, preconfigured, or specified to receive SSB communications and / or PDCCH communications associated with the CSS when the SSB communications and / or PDCCH communications associated with the CSS are associated with a serving cell, but to send uplink transmissions in other ways. For example, the UE 120 may receive SSB communications and / or PDCCH communications associated with the CSS in a SBFD symbol set (as shown by reference numeral 830) based at least in part on configuration information (e.g., ssb-PositionInBurst indicated in SIB1 and / or ServingCellConfigCommon) indicating that the SSB communications and / or PDCCH communications associated with the CSS are associated with a serving cell, and refrain from sending uplink transmissions in the SBFD symbol set (e.g., refrain from sending the message shown in conjunction with reference numeral 835). Alternatively, UE 120 may send uplink transmissions in the SBFD symbol set based at least in part on configuration information indicating that SSB communications and / or PDCCH communications associated with the CSS are not associated with the serving cell, and refrain from receiving at least one of SSB communications and / or PDCCH communications associated with the CSS in the SBFD symbol set. For example, configuration information (e.g., ssb-PositionInBurst indicated in SIB1 and / or ServingCellConfigCommon) may indicate that SSB communications and / or PDCCH communications associated with the CSS are sent outside of the SMTC window associated with the serving cell, and thus UE 120 may send uplink transmissions (as shown by reference numeral 835) and refrain from receiving SSB communications and / or PDCCH communications associated with the CSS (e.g., refrain from receiving the message shown in conjunction with reference numeral 830).

[0120] In some aspects, the UE 120 may be configured, preconfigured, or specified to always send uplink transmissions and refrain from receiving SSB communications and / or PDCCH communications associated with the CSS when the SSB communications and / or PDCCH communications associated with the CSS are scheduled in a time slot indicated as an uplink time slot. In such aspects, based at least in part on the UE 120 receiving configuration information indicating that an SBFD symbol set is associated with an uplink time slot (e.g., tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated indicating that the symbol set is associated with a U time slot and / or a semi-static flexible time slot dynamically indicated as an uplink time slot), the UE 120 may send uplink transmissions in the SBFD symbol set (as indicated by reference numeral 835) and refrain from receiving at least one of SSB communications or CSS communications in the SBFD symbol set (e.g., refrain from sending the message indicated in conjunction with reference numeral 830).

[0121] Based at least in part on the SBFD-aware UE 120 being configured, preconfigured, or designated to handle one or more conflict scenarios as described above, the UE 120 and / or the network entity 110 may communicate in a more transparent manner and / or conserve computational, power, network, and / or communication resources that may otherwise be consumed by communications that may be performed by a non-SBFD-aware UE 120 and / or communications performed by a SBFD-aware UE 120 that fails to prioritize high priority communications, such as control communications or similar messages. For example, based at least in part on the SBFD-aware UE 120 being configured, preconfigured, or designated to handle one or more conflict scenarios as described above, the UE 120 and the network entity 110 may communicate with a reduced error rate, which may conserve computational, power, network, and / or communication resources that may otherwise be consumed to detect and / or correct communication errors.

[0122] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Described differently.

[0123] Fig. 9 is a diagram of an example 900 associated with conflict handling of SBFD-aware UEs according to the present disclosure. Fig. 9 As shown, a network node 110 (e.g., a CU, DU, and / or RU) may communicate with a UE 120. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (e.g., the wireless network 100). The UE 120 and the network node 110 may be in communication with each other. Fig. 9 The operations shown have previously established a wireless connection. Fig. 9In the illustrated operation, the network node 110 may have the capability to operate in the SBFD mode and / or may operate in the SBFD mode and / or Fig. 9 In the illustrated operations, UE 120 may not have the capability to operate in SBFD mode and / or may not operate in SBFD mode. In addition, in some aspects, UE 120 may be a SBFD-aware UE, as described in more detail below in conjunction with reference numeral 910. In addition to UEs performing initial access (e.g., RRC idle UEs) and inactive UEs (e.g., RRC inactive UEs), aspects described herein also apply to UEs in connected mode (e.g., RRC connected UEs).

[0124] As indicated by reference numeral 905, the network node 110 may send, and the UE 120 may receive, configuration information. In some aspects, the UE 120 may receive the configuration information via one or more of RRC signaling, one or more MAC-CEs, and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by the UE 120 (e.g., already known to the UE 120 and / or previously indicated by the network node 110 or other network device), and / or explicit configuration information for use by the UE 120 to configure the UE 120, etc.

[0125] In some aspects, the configuration information may indicate TDD configuration parameters that semi-statically configure certain symbols and / or time slots as downlink symbols and / or time slots (e.g., D time slots), uplink symbols and / or time slots (e.g., U time slots), and / or flexible symbols and / or time slots (e.g., F time slots). For example, as described in more detail below in conjunction with reference numeral 910, in some aspects, UE 120 may receive an indication that network node 110 is operating in a SBFD mode in a symbol set. In such aspects, the configuration information may indicate that the SBFD symbol set is associated with a semi-statically configured uplink time slot and / or symbol set, a semi-statically configured downlink time slot and / or symbol set, or a semi-statically configured flexible time slot and / or symbol set. In a manner similar to that described above in conjunction with reference numeral 805, the configuration parameters may be associated with a TDD UL / DL IE (e.g., tdd-UL-DL-ConfigurationCommon) or a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated). The configuration information may include additional communication parameters. In some aspects, the configuration information may include an indication that the network node 110 is operating in SBFD mode, which is described in more detail below in conjunction with reference numeral 910.

[0126] UE 120 may configure itself based at least in part on the configuration information.In some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information.

[0127] As indicated by reference numeral 910, the network node 110 may send, and the UE 120 may receive, an indication that the network node 110 is operating in a SBFD mode in a symbol set, which is shown as a SBFD symbol set indicated by reference numeral 915. In this regard, based at least in part on the indication, the UE 120 may be an SBFD-aware UE 120. In some aspects, the indication may indicate only a temporal location of the SBFD operation (e.g., the indication may indicate a temporal location of the symbol set in which the network node 110 is operating in the SBFD mode without indicating a frequency location). In some other aspects, the indication may indicate both a temporal location and a frequency location of the SBFD operation (e.g., the indication may indicate a temporal location and a frequency location of the symbol set in which the network node 110 is operating in the SBFD mode). In some aspects, the indication that the network node 110 is operating in a SBFD mode in a symbol set may be sent by the network node 110 and received by the UE 120 in a broadcast message, such as in a SIB (e.g., SIB1). Additionally or alternatively, the indication that the network node 110 is operating in the symbol-focused SBFD mode may be sent by the network node 110 via an RRC message (such as an RRC configuration message or an RRC reconfiguration message) and received by the UE 120. In this regard, the indication may be provided as part of the configuration information described above in conjunction with reference numeral 805 (e.g., included in the same RRC message as the configuration information).

[0128] In some respects, Fig. 9The symbol set shown using reference numeral 915 in may be associated with a downlink symbol and / or a downlink time slot (e.g., a semi-static D time slot and / or a semi-static F time slot dynamically indicated as a downlink time slot). More specifically, in some aspects, the symbol set in which the network node 110 is operating in the SBFD mode may be indicated as a downlink symbol by TDD UL / DL configuration information (such as by one of a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated) or a TDD UL / DL dedicated configuration IE (e.g., tdd-UL-DL-ConfigurationDedicated). In some other aspects, the symbol set in which the network node 110 is operating in the SBFD mode may be indicated by the TDD UL / DL configuration information as an uplink symbol or a flexible symbol. Additionally or alternatively, in some aspects the set of symbols may be associated with a RO (e.g., the set of symbols may be associated with time and / or frequency resources scheduled for use by the UE 120 to send a RACH message or similar communication associated with a random access procedure).

[0129] As indicated by reference numeral 920, in some aspects, the network node 110 may transmit and the UE 120 may receive at least one of configuration information or DCI that schedules downlink transmission in a SBFD symbol set (e.g., the symbol set indicated by reference numeral 915). In other words, in some aspects, the UE 120 may be configured by higher layer parameters for downlink reception in a SBFD symbol set (e.g., the SBFD symbol set indicated by reference numeral 915), and / or the UE 120 may be dynamically scheduled by DCI for downlink reception in a SBFD symbol set. As described above in conjunction with the conflict scenarios indicated by reference numerals 712 and 716, the downlink transmission may be associated with PDCCH communication, CSI-RS reception, PDSCH communication, or similar downlink communication.

[0130] As shown by reference numeral 925, UE 120 may identify how to handle potential or actual conflicts in the SBFD symbol set due to SBFD operation of network node 110 in the symbol set. Figure 7As described, SBFD operation of the network node 110 may result in various conflict scenarios at the HD UE 120, such as when the RO is scheduled in an uplink subband in a semi-statically configured downlink timeslot (as described above in conjunction with reference numerals 710 and 712) or a similarly configured flexible timeslot, and / or when the RO is scheduled in a semi-statically configured uplink timeslot and the downlink transmission is scheduled to be received in a downlink subband of the semi-statically configured uplink timeslot (as described above in conjunction with reference numeral 716), etc. Therefore, in the operations illustrated in conjunction with reference numeral 925, the UE 120 may identify whether to transmit communications in the RO associated with the symbol set (e.g., the SBFD symbols indicated by reference numeral 915) based at least in part on the indication.

[0131] In some aspects, RO can be related to the gap (sometimes referred to as N 间隙 ), the gap may be the number of symbols before RO for switching between transmission modes. In other words, N 间隙 N may refer to the number of symbols during which UE 120 switches between downlink reception mode and uplink transmission mode, and thus may be a period of time during which UE 120 is unable to receive downlink communications. Thus, for the purposes of various conflict scenarios associated with RO, UE 120 may determine when the effective RO and N before the RO are equal. 间隙 When the symbol occurs in a semi-static downlink time slot and / or when the valid RO and the N before the RO 间隙 When a symbol overlaps with a downlink transmission scheduled by RRC or DG, there is a conflict or potential conflict.

[0132] As shown by reference numerals 930 and 935, based at least in part on an identification of whether to send a communication in the RO, the UE 120 may send a communication (e.g., a communication associated with a random access procedure) in the RO associated with the SBFD symbol set, or the UE 120 may receive a downlink transmission in the SBFD symbol set. For example, in some aspects, the symbol set may be associated with a downlink time slot (e.g., the UE 120 may have received configuration information, such as tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, indicating that the symbol set is associated with a downlink time slot or a flexible time slot that is dynamically indicated as a downlink time slot). In addition, in some aspects, the UE 120 may be configured, preconfigured, or specified to always send the communication in the RO when the communication is sent in the SBFD symbol set associated with the downlink time slot. Therefore, in such aspects, the UE 120 may send a communication in the RO (as shown by reference numeral 930) based at least in part on the configuration information indicating that the SBFD symbol set is associated with the downlink time slot.

[0133] In some other aspects, the UE 120 may be configured, preconfigured, or specified to send certain types of communications in the RO when the RO is associated with a SBFD symbol set associated with a downlink time slot. For example, the UE 120 may be configured, preconfigured, or specified to send communications associated with one of a contention-based random access (CBRA) process or a contention-free random access (CFRA) process, but not to send communications associated with the other of the two. More specifically, in some aspects, the UE 120 may send the communication in the RO based at least in part on the communication being associated with the CBRA process (as shown by reference numeral 930). In some other aspects, the UE may send the communication in the RO based at least in part on the communication being associated with the CFRA process (as shown by reference numeral 930).

[0134] In some aspects, when UE 120 is indicated with a valid RO in a downlink time slot, UE 120 may be configured, preconfigured, or specified to treat the symbol set as a flexible symbol and thus send communications in the RO (as indicated by reference numeral 930). In some other aspects, UE 120 may not desire to be indicated with a RO in a downlink time slot. Thus, in such aspects, UE 120 may identify that an error condition has occurred based at least in part on an indication that a network node is operating in an SBFD mode associated with the symbol set and configuration information indicates that the SBFD symbol set is associated with the downlink time slot (e.g., UE 120 may refrain from sending communications shown in conjunction with reference numeral 830 based at least in part on identifying that an error condition has occurred).

[0135] Additionally, as described above in conjunction with reference numeral 920, in some aspects, UE 120 may be scheduled to receive downlink transmissions in a symbol set (e.g., in a SBFD symbol set indicated by reference numeral 915), similar to the conflict scenarios described above in conjunction with reference numerals 712 and 716. In such aspects, UE 120 may be configured, preconfigured, or designated to perform one of sending communications in a RO associated with the symbol set (as indicated by reference numeral 930) or receiving downlink transmissions (as indicated by reference numeral 935) in the SBFD symbol set, and refrain from performing the other of sending communications or receiving downlink transmissions in the RO associated with the SBFD symbol set.

[0136] More specifically, in some aspects, the UE 120 may be configured, preconfigured, or designated to always drop downlink transmissions (e.g., refrain from receiving the communication shown in conjunction with reference numeral 935), and therefore transmit communications in a RO associated with a SBFD symbol set (e.g., the UE 120 may refrain from receiving a PDCCH communication, a CSI-RS reception, a PDSCH communication, or the like if the timeslot associated with the reception would overlap with any symbol in the SBFD symbol set associated with the RO). In other words, in some aspects, the UE 120 may transmit communications in a RO associated with a SBFD symbol set and refrain from receiving downlink transmissions in the SBFD symbol set based at least in part on at least one of the configuration information or the DCI that schedules the downlink transmission in the SBFD symbol set.

[0137] In some aspects, the UE 120 may be configured, preconfigured, or designated to receive downlink transmissions when the UE 120 does not need to send random access communications at the SBFD symbol set. For example, the UE 120 may receive downlink transmissions in the SBFD symbol set (as shown by reference numeral 935) based at least in part on the UE 120 not having random access communications to send in the SBFD symbol set, and refrain from sending communications in the RO associated with the SBFD symbol set (e.g., refraining from sending the communications shown by reference numeral 930). In some aspects, the UE 120 may be configured, preconfigured, or designated to receive DG downlink transmissions in the SBFD symbol set based at least in part on the UE 120 not having random access communications to send in the SBFD symbol set. For example, UE 120 may be configured, preconfigured, or designated to receive downlink signals and / or channels (e.g., CSI-RS, PDSCH, etc.) scheduled by DCI communications without UE 120 needing to send random access communications (e.g., PRACH communications) at a SBFD symbol set and to send random access communications in other manners (e.g., sending communications in RO).

[0138] In some aspects, the UE 120 may be configured, preconfigured, or designated to receive downlink transmissions based at least in part on the type of downlink transmission being sent by the network node 110. For example, the UE 120 may be configured, preconfigured, or designated to receive downlink transmissions associated with a PDCCH monitoring opportunity. More specifically, in some aspects, the UE 120 may receive downlink transmissions in a SBFD symbol set (as shown by reference numeral 935) based at least in part on the SBFD symbol set being associated with a monitoring opportunity associated with a PDCCH communication, and refrain from sending communications in a RO associated with the SBFD symbol set (e.g., refraining from sending communications shown by reference numeral 930). In some aspects, whether the UE 120 receives downlink transmissions associated with a PDCCH monitoring opportunity may be based at least in part on whether the UE 120 has a random access communication to be sent in the RO. For example, in aspects where the UE 120 needs to send a random access communication, the UE 120 may send a communication in a RO associated with the SBFD symbol set, and refrain from receiving downlink transmissions in the SBFD symbol set. And in aspects where UE 120 does not need to send random access communications, UE 120 may receive downlink transmissions in a SBFD symbol set and refrain from sending communications in a RO associated with the SBFD symbol set.

[0139] Based at least in part on the SBFD-aware UE 120 being configured, preconfigured, or designated to handle one or more conflict scenarios as described above, the UE 120 and / or the network entity 110 may communicate with increased transparency and save computational, power, network, and / or communication resources that may otherwise be consumed by communications that may be performed by a non-SBFD-aware UE 120 and / or communications performed by a SBFD-aware UE 120 that fails to prioritize high priority communications, such as control communications or similar messages. For example, based at least in part on the SBFD-aware UE 120 being configured, preconfigured, or designated to handle one or more conflict scenarios as described above, the UE 120 and the network entity 110 may communicate with reduced error rates, which may save computational, power, network, and / or communication resources that may otherwise be consumed to detect and / or correct communication errors.

[0140] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 Described differently.

[0141] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a UE in accordance with the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120) performs operations associated with SBFD-aware UE contention handling.

[0142] like Fig.10 As shown, in some aspects, process 1000 may include receiving an indication that a network node is operating in a symbol-focused SBFD mode (block 1010). Fig.12 The communications manager 140 and / or receiving component 1202 depicted in FIG. 1 may receive an indication that the network node is operating in a symbol focused SBFD mode, as described above.

[0143] like Fig.10 As further shown in FIG. 1 , in some aspects, process 1000 may include identifying whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication (block 1020). Fig.12 The communication manager 140, identification component 1208 and / or SBFD component 1210 depicted in FIG. 1 may identify whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication, as described above.

[0144] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0145] In a first aspect, the indication is received via at least one of a broadcast message or a radio resource control message.

[0146] In a second aspect, alone or in combination with the first aspect, process 1000 includes receiving configuration information indicating that the symbol set is associated with an uplink timeslot.

[0147] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes receiving at least one of an SSB communication or a PDCCH communication associated with a CSS based at least in part on configuration information indicating that the symbol set is associated with an uplink time slot.

[0148] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 1000 includes receiving at least one of an SSB communication or a PDCCH communication associated with a CSS based at least in part on at least one of the SSB communication or the PDCCH communication associated with the CSS being associated with a serving cell.

[0149] In a fifth aspect, alone or in combination with one or more of aspects 1 to 4, process 1000 includes suppressing reception of SSB communications or PDCCH communications associated with the CSS based at least in part on at least one of the SSB communications or PDCCH communications associated with the CSS being sent outside of an SSB measurement timing configuration window associated with a serving cell.

[0150] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 1000 comprises suppressing reception of at least one of SSB communications or PDCCH communications associated with a CSS based at least in part on configuration information indicating that a symbol set is associated with an uplink time slot.

[0151] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1000 includes receiving at least one of configuration information or DCI for uplink transmission in a scheduling symbol set.

[0152] In an eighth aspect, alone or in combination with one or more of aspects one to seven, process 1000 includes receiving at least one of SSB communications or PDCCH communications associated with a CSS in a symbol set based at least in part on configuration information or at least one of DCIs for uplink transmissions in a scheduling symbol set, and suppressing sending uplink transmissions in the symbol set.

[0153] In a ninth aspect, alone or in combination with one or more of aspects one to eight, process 1000 includes receiving SSB communications or at least one of PDCCH communications associated with a CSS in a symbol set based at least in part on at least one of the SSB communications or PDCCH communications associated with the CSS being associated with a serving cell, and suppressing sending uplink transmissions in the symbol set.

[0154] In a tenth aspect, alone or in combination with one or more of aspects one to nine, process 1000 includes sending an uplink transmission in a symbol set based at least in part on at least one of an SSB communication or a PDCCH communication associated with a CSS being sent outside an SSB measurement timing configuration window associated with a serving cell, and suppressing receiving in the symbol set an SSB communication or at least one of a PDCCH communication associated with a CSS.

[0155] In an eleventh aspect, alone or in combination with one or more of aspects one to ten, process 1000 includes receiving configuration information indicating that a symbol set is associated with an uplink time slot, sending an uplink transmission in the symbol set based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot, and suppressing receiving at least one of SSB communications or PDCCH communications associated with the CSS in the symbol set.

[0156] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0157] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a UE, according to the present disclosure. The example process 1100 is an example in which a UE (eg, UE 120) performs operations associated with SBFD-aware UE contention handling.

[0158] like Fig.11 As shown, in some aspects, process 1100 may include receiving an indication that a network node is operating in a symbol-focused SBFD mode (block 1110). Fig.12 The communications manager 140 and / or receiving component 1202 depicted in FIG. 1 may receive an indication that the network node is operating in a symbol focused SBFD mode, as described above.

[0159] like Fig.11 As further shown, in some aspects, process 1100 may include identifying whether to send a communication in a RO associated with a symbol set based at least in part on the indication (block 1120). Fig.12 The communication manager 140, identification component 1208, and / or SBFD component 1210 depicted in FIG. 1 may identify whether to send a communication in a RO associated with the symbol set based at least in part on the indication, as described above.

[0160] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0161] In a first aspect, the indication is received via at least one of a broadcast message or a radio resource control message.

[0162] In a second aspect, alone or in combination with the first aspect, process 1100 includes receiving configuration information indicating that the symbol set is associated with a downlink time slot.

[0163] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes sending communications in the RO based at least in part on configuration information indicating that a symbol set is associated with a downlink time slot.

[0164] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1100 includes sending a communication in the RO based at least in part on the communication being associated with a contention-based random access procedure.

[0165] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending a communication in the RO based at least in part on the communication being associated with a contention-free random access procedure.

[0166] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1100 includes treating the symbol set as a flexible symbol and sending a communication in the RO.

[0167] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 1100 comprises identifying that an error condition has occurred based at least in part on an indication that the network node is operating in an SBFD mode associated with a symbol set and configuration information indicating that the symbol set is associated with a downlink timeslot.

[0168] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes receiving at least one of configuration information or DCI for a downlink transmission in a scheduling symbol set.

[0169] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, process 1100 comprises sending communications in an RO associated with a symbol set based at least in part on configuration information or at least one of DCIs for downlink transmissions in a scheduling symbol set, and suppressing receiving downlink transmissions in the symbol set.

[0170] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, process 1100 comprises receiving a downlink transmission in a symbol set based at least in part on the UE not having a random access communication to be sent in the symbol set, and suppressing sending communications in a RO associated with the symbol set.

[0171] In an eleventh aspect, either alone or in combination with one or more of aspects one to ten, process 1100 includes sending communications in a RO associated with a symbol set based at least in part on the UE having a random access communication to be sent in the symbol set, and suppressing receiving downlink transmissions in the symbol set.

[0172] In a twelfth aspect, either alone or in combination with one or more of aspects one to eleven, process 1100 comprises receiving downlink transmissions in a symbol set based at least in part on associating the symbol set with a monitoring opportunity associated with a physical downlink control channel communication, and suppressing sending communications in an RO associated with the symbol set.

[0173] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0174] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. The apparatus 1200 may be a UE 120, or the UE may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a network node, or another wireless communication device) using the receiving component 1202 and the sending component 1204. As further shown, the apparatus 1200 may include a communication manager 140. The communication manager 140 may include one or more of an identification component 1208 or a SBFD component 1210, etc.

[0175] In some aspects, the apparatus 1200 may be configured to perform Figures 8 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 The process of 1000 Fig.11 In some aspects, Fig.12 The apparatus 1200 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0176] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 The UE 120 is described as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0177] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted UE 120. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0178] Receiving component 1202 can receive an indication that the network node is operating in SBFD mode in a symbol set. Identifying component 1208 and / or SBFD component 1210 can identify whether to receive at least one of SSB communications or PDCCH communications associated with a CSS in the symbol set based at least in part on the indication.

[0179] Receiving component 1202 can receive configuration information indicating that a set of symbols is associated with an uplink time slot.

[0180] Receiving component 1202 and / or SBFD component 1210 can receive at least one of an SSB communication or a PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with an uplink time slot.

[0181] Receiving component 1202 and / or SBFD component 1210 may receive at least one of the SSB communication or the PDCCH communication associated with the CSS based at least in part on at least one of the SSB communication or the PDCCH communication associated with the CSS being associated with a serving cell.

[0182] The SBFD component 1210 may refrain from receiving SSB communications or PDCCH communications associated with the CSS based at least in part on at least one of the SSB communications or PDCCH communications associated with the CSS being sent outside of an SSB measurement timing configuration window associated with the serving cell.

[0183] The SBFD component 1210 can receive at least one of an SSB communication or a PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

[0184] Receiving component 1202 can receive at least one of configuration information or DCI for an uplink transmission in a scheduling symbol set.

[0185] The receiving component 1202 and / or the SBFD component 1210 may receive at least one of SSB communications or PDCCH communications associated with the CSS in the symbol set and refrain from sending uplink transmissions in the symbol set based at least in part on configuration information or at least one of DCIs for scheduling uplink transmissions in the symbol set.

[0186] The receiving component 1202 and / or the SBFD component 1210 may receive SSB communications or at least one of PDCCH communications associated with the CSS in a symbol set based at least in part on at least one of the SSB communications or PDCCH communications associated with the CSS being associated with a serving cell, and refrain from sending uplink transmissions in the symbol set.

[0187] The transmitting component 1204 and / or the SBFD component 1210 may transmit an uplink transmission in a symbol set based at least in part on at least one of the SSB communication or the PDCCH communication associated with the CSS being transmitted outside of an SSB measurement timing configuration window associated with the serving cell, and suppress receiving at least one of the SSB communication or the PDCCH communication associated with the CSS in the symbol set.

[0188] Receiving component 1202 can receive configuration information indicating that a set of symbols is associated with an uplink time slot.

[0189] Transmitting component 1204 and / or SBFD component 1210 may transmit uplink transmissions in a symbol set based at least in part on configuration information indicating that the symbol set is associated with an uplink time slot and refrain from receiving at least one of SSB communications or PDCCH communications associated with a CSS in the symbol set.

[0190] Identification component 1208 and / or SBFD component 1210 can identify whether to send the communication in the RO associated with the symbol set based at least in part on the indication.

[0191] Receiving component 1202 can receive configuration information indicating that a set of symbols is associated with a downlink time slot.

[0192] Transmitting component 1204 and / or SBFD component 1210 can transmit the communication in the RO based at least in part on the configuration information indicating that the symbol set is associated with the downlink time slot.

[0193] Transmitting component 1204 and / or SBFD component 1210 can transmit the communication in the RO based at least in part on the communication being associated with a contention-based random access procedure.

[0194] Transmitting component 1204 and / or SBFD component 1210 can transmit the communication in the RO based at least in part on the communication being associated with a contention-free random access procedure.

[0195] The SBFD component 1210 may treat the symbol set as a flexible symbol.

[0196] The sending component 1204 and / or the SBFD component 1210 can send the communication in the RO.

[0197] Identification component 1208 and / or SBFD component 1210 can identify that an error condition has occurred based at least in part on an indication that the network node is operating in a SBFD mode associated with the symbol set and the configuration information indicates that the symbol set is associated with a downlink timeslot.

[0198] Receiving component 1202 can receive at least one of configuration information or DCI for a downlink transmission in a scheduling symbol set.

[0199] Transmitting component 1204 and / or SBFD component 1210 can transmit communications in a RO associated with a symbol set based at least in part on at least one of configuration information or a DCI scheduling downlink transmissions in the symbol set and refrain from receiving downlink transmissions in the symbol set.

[0200] Receiving component 1202 and / or SBFD component 1210 can receive a downlink transmission in the symbol set and refrain from sending communications in a RO associated with the symbol set based at least in part on the UE not having a random access communication to send in the symbol set.

[0201] Transmitting component 1204 and / or SBFD component 1210 can transmit communications in a RO associated with the symbol set based at least in part on the UE having a random access communication to transmit in the symbol set and refrain from receiving downlink transmissions in the symbol set.

[0202] Receiving component 1202 and / or SBFD component 1210 can receive downlink transmissions in a symbol set based at least in part on the symbol set being associated with a monitoring opportunity associated with a physical downlink control channel communication and refrain from transmitting communications in a RO associated with the symbol set.

[0203] Fig.12 The number and arrangement of components shown are provided as examples. Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly (one or more components) of the components shown may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

[0204] The following provides an overview of some aspects of the disclosure:

[0205] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving an indication that a network node is operating in an SBFD mode in a symbol set; and identifying whether to receive at least one of an SSB communication or a PDCCH communication associated with a CSS in the symbol set based at least in part on the indication.

[0206] Aspect 2: The method according to aspect 1, wherein the indication is received via at least one of a broadcast message or a radio resource control message.

[0207] Aspect 3: The method according to any one of aspects 1 to 2, further comprising receiving configuration information indicating that the symbol set is associated with an uplink time slot.

[0208] Aspect 4: The method according to aspect 3 further includes receiving at least one of the SSB communication or the PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

[0209] Aspect 5: According to the method described in any one of Aspects 3 to 4, the method also includes receiving the SSB communication or the at least one of the PDCCH communications associated with the CSS based at least in part on the SSB communication or the at least one of the PDCCH communications associated with the CSS being associated with a serving cell.

[0210] Aspect 6: According to the method according to Aspect 3, the method also includes suppressing receiving the SSB communication or the PDCCH communication associated with the CSS based at least in part on the fact that at least one of the SSB communication or the PDCCH communication associated with the CSS is sent outside the SSB measurement timing configuration window associated with the serving cell.

[0211] Aspect 7: According to the method of aspect 3, the method also includes suppressing receiving at least one of the SSB communication or the PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

[0212] Aspect 8: The method according to any one of aspects 1 to 3, further comprising receiving at least one of configuration information or DCI scheduling uplink transmission in the symbol set.

[0213] Aspect 9: According to the method described in Aspect 8, the method also includes receiving the SSB communication or the at least one of the PDCCH communications associated with the CSS in the symbol set based at least in part on the configuration information or the at least one of the DCIs scheduling the uplink transmission in the symbol set, and suppressing the transmission of the uplink transmission in the symbol set.

[0214] Aspect 10: According to the method described in any one of Aspects 8 to 9, the method also includes receiving the SSB communication or the at least one of the PDCCH communications associated with the CSS in the symbol set based at least in part on the SSB communication or the at least one of the PDCCH communications associated with the CSS being associated with a serving cell, and suppressing sending the uplink transmission in the symbol set.

[0215] Aspect 11: According to the method of Aspect 8, the method also includes sending the uplink transmission in the symbol set at least in part based on the SSB communication or at least one of the PDCCH communications associated with the CSS being sent outside the SSB measurement timing configuration window associated with the serving cell, and suppressing receiving the SSB communication or at least one of the PDCCH communications associated with the CSS in the symbol set.

[0216] Aspect 12: According to the method described in Aspect 8, the method also includes: receiving configuration information indicating that the symbol set is associated with an uplink time slot; and sending the uplink transmission in the symbol set based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot, and suppressing receiving at least one of the SSB communication or the PDCCH communication associated with the CSS in the symbol set.

[0217] Aspect 13: A method of wireless communication performed by a UE, the method comprising: receiving an indication that a network node is operating in an SBFD mode in a symbol set; and identifying whether to send a communication in a RO associated with the symbol set based at least in part on the indication.

[0218] Aspect 14: The method according to aspect 13, wherein the indication is received via at least one of a broadcast message or a radio resource control message.

[0219] Aspect 15: The method according to any one of aspects 13 to 14, the method further comprising receiving configuration information indicating that the symbol set is associated with a downlink time slot.

[0220] Aspect 16: The method of aspect 15, further comprising sending the communication in the RO based at least in part on the configuration information indicating that the symbol set is associated with the downlink time slot.

[0221] Aspect 17: The method according to any one of aspects 15 to 16, further comprising sending the communication in the RO based at least in part on the communication being associated with a contention-based random access procedure.

[0222] Aspect 18: The method according to any one of aspects 15 to 16, further comprising sending the communication in the RO based at least in part on the communication being associated with a contention-free random access procedure.

[0223] Aspect 19: The method according to any one of aspects 15 to 18, further comprising treating the symbol set as flexible symbols; and sending the communication in the RO.

[0224] Aspect 20: According to the method according to Aspect 15, the method also includes identifying that an error condition has occurred based at least in part on the indication that the network node is operating in the SBFD mode associated with the symbol set and the configuration information indicates that the symbol set is associated with the downlink time slot.

[0225] Aspect 21: The method according to any one of aspects 13 to 15, further comprising receiving at least one of configuration information or DCI scheduling downlink transmission in the symbol set.

[0226] Aspect 22: According to the method according to Aspect 21, the method also includes sending the communication in the RO associated with the symbol set based at least in part on the configuration information or the at least one of the DCIs scheduling the downlink transmission in the symbol set, and suppressing receiving the downlink transmission in the symbol set.

[0227] Aspect 23: According to the method according to Aspect 21, the method also includes receiving the downlink transmission in the symbol set at least in part based on the UE not having a random access communication to be sent in the symbol set, and refraining from sending the communication in the RO associated with the symbol set.

[0228] Aspect 24: The method according to aspect 21 also includes sending the communication in the RO associated with the symbol set based at least in part on the UE having a random access communication to be sent in the symbol set, and suppressing receiving the downlink transmission in the symbol set.

[0229] Aspect 25: According to the method of Aspect 21, the method also includes receiving the downlink transmission in the symbol set based at least in part on associating the symbol set with a monitoring opportunity associated with a physical downlink control channel communication, and suppressing sending the communication in the RO associated with the symbol set.

[0230] Aspect 26: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 12.

[0231] Aspect 27: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 12.

[0232] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 12.

[0233] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 12.

[0234] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 1 to 12.

[0235] Aspect 31: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 13 to 25.

[0236] Aspect 32: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 13 to 25.

[0237] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 13 to 25.

[0238] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 13 to 25.

[0239] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 13 to 25.

[0240] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0241] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0242] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0243] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0244] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; as well as one or more processors coupled to the one or more memories, the one or more processors configured to: receiving an indication that the network node is operating in a symbol concentrated sub-band full duplex (SBFD) mode; and Whether at least one of a synchronization signal block (SSB) communication or a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) is received in the symbol set is identified based at least in part on the indication. 2 . The UE of claim 1 , wherein the one or more processors are further configured to receive the indication via at least one of a broadcast message or a radio resource control message.

3. The UE of claim 1, wherein the one or more processors are further configured to receive configuration information indicating that the symbol set is associated with an uplink time slot.

4. The UE of claim 3, wherein the one or more processors are further configured to receive at least one of the SSB communication or the PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

5. The UE according to claim 3, wherein the one or more processors are further configured to receive the SSB communication or the at least one of the PDCCH communications associated with the CSS based at least in part on the SSB communication or the at least one of the PDCCH communications associated with the CSS being associated with a serving cell.

6. The UE according to claim 3, wherein the one or more processors are further configured to suppress receiving the SSB communication or the PDCCH communication associated with the CSS based at least in part on the fact that at least one of the SSB communication or the PDCCH communication associated with the CSS is sent outside an SSB measurement timing configuration window associated with a serving cell.

7. The UE of claim 3, wherein the one or more processors are further configured to suppress receiving at least one of the SSB communication or the PDCCH communication associated with the CSS based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

8. The UE of claim 1, wherein the one or more processors are further configured to receive at least one of configuration information or downlink control information (DCI) scheduling uplink transmissions in the symbol set.

9. A UE according to claim 8, wherein the one or more processors are also configured to receive the SSB communication or the at least one of the PDCCH communications associated with the CSS in the symbol set based at least in part on the configuration information or the at least one of the DCIs scheduling the uplink transmission in the symbol set, and to suppress sending the uplink transmission in the symbol set.

10. The UE of claim 8, wherein the one or more processors are further configured to receive the SSB communication or the at least one of the PDCCH communications associated with the CSS in the symbol set based at least in part on the at least one of the SSB communication or the PDCCH communication associated with the CSS being associated with a serving cell, and to suppress sending the uplink transmission in the symbol set.

11. The UE of claim 8, wherein the one or more processors are further configured to send the uplink transmission in the symbol set based at least in part on the SSB communication or the at least one of the PDCCH communications associated with the CSS being sent outside an SSB measurement timing configuration window associated with a serving cell, and to suppress receiving the SSB communication or the at least one of the PDCCH communications associated with the CSS in the symbol set.

12. The UE of claim 8, wherein the one or more processors are further configured to: receiving configuration information indicating that the symbol set is associated with an uplink time slot; and The uplink transmission is sent in the symbol set based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot, and the at least one of the SSB communication or the PDCCH communication associated with the CSS is suppressed from being received in the symbol set.

13. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: one or more memories; as well as one or more processors coupled to the one or more memories, the one or more processors configured to: receiving an indication that the network node is operating in a symbol concentrated sub-band full duplex (SBFD) mode; and Whether to send a communication in a random access channel (RACH) opportunity (RO) associated with the set of symbols is identified based at least in part on the indication.

14. The UE of claim 13, wherein the one or more processors are further configured to receive the indication via at least one of a broadcast message or a radio resource control message.

15. The UE of claim 13, wherein the one or more processors are further configured to receive configuration information indicating that the symbol set is associated with a downlink time slot.

16. The UE of claim 15, wherein the one or more processors are further configured to send the communication in the RO based at least in part on the configuration information indicating that the symbol set is associated with the downlink time slot.

17. The UE of claim 15, wherein the one or more processors are further configured to send the communication in the RO based at least in part on the communication being associated with a contention-based random access procedure.

18. The UE of claim 15, wherein the one or more processors are further configured to send the communication in the RO based at least in part on the communication being associated with a contention-free random access procedure.

19. The UE of claim 15, wherein the one or more processors are further configured to: Treating the set of symbols as flexible symbols; and The communication is sent in the RO.

20. The UE of claim 15, wherein the one or more processors are further configured to identify that an error condition has occurred based at least in part on the indication that the network node is operating in the SBFD mode associated with the symbol set and the configuration information indicates that the symbol set is associated with the downlink timeslot.

21. The UE of claim 13, wherein the one or more processors are further configured to receive at least one of configuration information or downlink control information (DCI) scheduling downlink transmissions in the set of symbols.

22. A UE according to claim 21, wherein the one or more processors are also configured to send the communication in the RO associated with the symbol set based at least in part on the configuration information or at least one of the DCIs scheduling the downlink transmission in the symbol set, and suppress receiving the downlink transmission in the symbol set.

23. The UE of claim 21, wherein the one or more processors are further configured to receive the downlink transmission in the symbol set and refrain from sending the communication in the RO associated with the symbol set based at least in part on the UE not having a random access communication to send in the symbol set.

24. The UE of claim 21, wherein the one or more processors are further configured to send the communication in the RO associated with the symbol set based at least in part on the UE having a random access communication to send in the symbol set, and to refrain from receiving the downlink transmission in the symbol set.

25. A UE according to claim 21, wherein the one or more processors are further configured to receive the downlink transmission in the symbol set based at least in part on the association of the symbol set with a monitoring opportunity associated with a physical downlink control channel communication, and to refrain from sending the communication in the RO associated with the symbol set.

26. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication that the network node is operating in a symbol concentrated sub-band full duplex (SBFD) mode; as well as Whether at least one of a synchronization signal block (SSB) communication or a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) is received in the symbol set is identified based at least in part on the indication.

27. The method according to claim 26, further comprising: receiving configuration information indicating that the symbol set is associated with an uplink time slot; as well as The at least one of the SSB communication or the PDCCH communication associated with the CSS is received based at least in part on the configuration information indicating that the symbol set is associated with the uplink time slot.

28. The method according to claim 26, further comprising: receiving configuration information indicating that the symbol set is associated with an uplink time slot; as well as The at least one of the SSB communication or the PDCCH communication associated with the CSS is received based at least in part on the at least one of the SSB communication or the PDCCH communication associated with the CSS being associated with a serving cell.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving an indication that the network node is operating in a symbol concentrated sub-band full duplex (SBFD) mode; as well as Whether to send a communication in a random access channel (RACH) opportunity (RO) associated with the set of symbols is identified based at least in part on the indication.

30. The method according to claim 29, further comprising: receiving configuration information indicating that the symbol set is associated with a downlink time slot; as well as The communication is sent in the RO based at least in part on the configuration information indicating that the set of symbols is associated with the downlink time slot.

Images